[Desktop-packages] [Bug 1878293] Re: xterm resize is wonky

[Daniel van Vugt]

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Low

** Changed in: xterm (Ubuntu)
   Importance: Undecided => Low

** Changed in: xterm (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  xterm resize is wonky

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Triaged
Status in xterm package in Ubuntu:
  Triaged

Bug description:
  % lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04 LTS
  Release:20.04
  Codename:   focal

  % wmctrl -m
  Name: GNOME Shell
  Class: N/A
  PID: N/A
  Window manager's "showing the desktop" mode: OFF

  Terms:
  window has four sides: top, bottom, left, and right
  when referring to corners, "upper" means "top", and "lower" means "bottom",
  so the four corners are upper-right, lower-right, lower-left, and  upper-left.
  wonky: works wrong, as detailed below ("cases that work wrong...")

  Description:

  I can resize a gnome-terminal window, everything works fine.
  (Grab it, using the mouse, by the upper-right corner (click-and-hold);
  the size changes as the mouse is moved, because the position
  of the upper-right corner follows the mouse.  (Only the upper-right corner 
moves.))
  But when I try to resize an xterm window the same way,
  this happens instead: as the mouse is moved, the upper-right corner
  does move, but it doesn't track with the mouse pointer like it should.
  Meanwhile, the lower-left corner also moves (it should have remained anchored 
in its original x-y position on the screen).

  Cases that work correctly:
  If the xterm window is grabbed by the lower-right corner and resized, this 
case works properly.
  If the xterm window is grabbed by the bottom edge and resized, this case 
works properly.
  If the xterm window is grabbed by the right edge and resized, this case works 
properly.

  Cases that work wrong ("wonky"):
  If the xterm window is grabbed by the left edge and resized, then the 
opposite (i.e. right) edge (incorrectly) migrates.
  If the xterm window is grabbed by the top edge and resized, then the opposite 
(i.e. bottom) edge (incorrectly) migrates.
  If the xterm window is grabbed by the upper-right corner and resized, then 
the window (incorrectly) migrates.
  If the xterm window is grabbed by the lower-left corner and resized, then the 
window (incorrectly) migrates.
  If the xterm window is grabbed by the upper-left corner and resized, then the 
window (incorrectly) migrates.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xterm 353-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue May 12 13:52:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GT 740] [10de:0fc8] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: PNY GK107 [GeForce GT 740] [196e:109a]
  InstallationDate: Installed on 2020-05-06 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=7f55a3c5-bff9-45ea-8979-583e4fbfec07 ro quiet splash vt.handoff=7
  SourcePackage: xterm
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0705
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  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.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A99XEVO:rvrRev1.xx: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

[Desktop-packages] [Bug 1878301] Re: Focal regression: poor discoverability for search in Ubuntu Software Center

[Dan Dascalescu]

https://gitlab.gnome.org/GNOME/gnome-software/-/issues/986

** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/-/issues #986
   https://gitlab.gnome.org/GNOME/gnome-software/-/issues/986

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

Title:
  Focal regression: poor discoverability for search in Ubuntu Software
  Center

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  I wanted to install a new package. Launched Ubuntu Software and... how
  do I search for anything?

  Search is a key function. It should be front and center. I couldn't
  see it.

  That was annoying enough that I wanted to file a bug against it. In
  the process I did notice the lens icon in the top left, but seriously
  - does that look easily discoverable to anyone? There's usually
  nothing in that cornerl so users don't look there, and the contrast is
  poor, which makes it very easy to not notice.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1878301/+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 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)

[Bug Watch Updater]

** Changed in: spice-vdagent (Debian)
   Status: Unknown => Fix Released

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

Title:
  Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM
  guests)

Status in qemu package in Ubuntu:
  Invalid
Status in spice package in Ubuntu:
  Invalid
Status in spice-vdagent package in Ubuntu:
  Fix Released
Status in virt-manager package in Ubuntu:
  Invalid
Status in spice-vdagent source package in Focal:
  Triaged
Status in spice-vdagent package in Debian:
  Fix Released
Status in spice package in Fedora:
  Unknown

Bug description:
  https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9

  ---

  I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta.

  I installed Kubuntu 20.04 and virt-manager as I did many times on
  Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt,
  libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest
  or with Ubuntu 20.04 guest then clipboard doesn't work right.

  To test it, please install Kubuntu 20.04 and then install Kubuntu /
  Ubuntu 20.04 as VM (guest). Open some simple text editor and start
  Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of
  time it won't.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: virt-manager 1:2.2.1-3ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 13 15:02:22 2020
  InstallationDate: Installed on 2020-04-09 (4 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  PackageArchitecture: all
  SourcePackage: virt-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872527/+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 1878292] Re: firefox FTBFS on s390x

[Launchpad Bug Tracker]

** Branch linked: lp:firefox

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

Title:
  firefox FTBFS on s390x

Status in firefox package in Ubuntu:
  In Progress

Bug description:
  Builds hang when trying to compile the third-party sqlite3 copy,
  during 7+ hours, before being killed. See e.g.
  
https://launchpad.net/ubuntu/+source/firefox/76.0.1+build1-0ubuntu1/+build/19276095:

  436:55.58 make[6]: *** 
[/<>/firefox-76.0.1+build1/config/rules.mk:673: sqlite3.o] Killed
  436:55.59 make[6]: Leaving directory 
'/<>/firefox-76.0.1+build1/obj-s390x-linux-gnu/third_party/sqlite3/src'
  436:55.59 make[5]: *** 
[/<>/firefox-76.0.1+build1/config/recurse.mk:74: 
third_party/sqlite3/src/target-objects] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1878292/+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 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus

[Martin Měřinský]

Ubuntu 20.04 LTS still contains this bug.

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

Title:
  Pressing any global keyboard shortcut causes temporary loss of focus

Status in Mutter:
  Confirmed
Status in compiz package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-settings-daemon package in ALT Linux:
  Unknown
Status in gnome-shell package in Fedora:
  Confirmed
Status in gnome package in openSUSE:
  Unknown

Bug description:
  When pressing any global keyboard shourtcut (configurable via System
  settings -> Keyboard -> Shortcuts; i.e. for switching keyboard layout,
  volume up/down), focus temporary switches from active text input to
  something else, then restores back shortly. Maybe even active window
  loses focus, but window frame does not shows this (window header
  remains to look active).

  For example: when I press ctrl+shift here to switch keyboard layout,
  when writing this description, yellow frame disappears from text input
  box, text caret disappears too; they appear again when releasing
  ctrl+shift. The same occurs in all other programs, i.e. terminal.

  It causes serious annoyance, for example in Twitter when losing focus
  in Reply text box, reply rolls up and I have to click it again with
  mouse and set caret to correct place each time I switch keyboard
  layouts.

  Other key combinations, not only ctrl+shift, also cause this.

  It is especially annoying when using keyboard layout switch shortcut
  handled by the same subsystem (media-keys plugin):

  case SWITCH_INPUT_SOURCE_KEY:
  case SWITCH_INPUT_SOURCE_BACKWARD_KEY:
  do_switch_input_source_action (manager, type);
  break;

  (Original gnome-settings-daemon, from which unity-settings-daemon was
  forked, does not use media-keys plugin to switch keyboard layout).

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-session 3.9.90-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Thu Oct 24 11:42:19 2013
  InstallationDate: Installed on 2013-10-23 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1244090/+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 1878293] Re: xterm resize is wonky

[Timo Aaltonen]

** Project changed: xterm => mutter

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

Title:
  xterm resize is wonky

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Triaged
Status in xterm package in Ubuntu:
  Confirmed

Bug description:
  % lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04 LTS
  Release:20.04
  Codename:   focal

  % wmctrl -m
  Name: GNOME Shell
  Class: N/A
  PID: N/A
  Window manager's "showing the desktop" mode: OFF

  Terms:
  window has four sides: top, bottom, left, and right
  when referring to corners, "upper" means "top", and "lower" means "bottom",
  so the four corners are upper-right, lower-right, lower-left, and  upper-left.
  wonky: works wrong, as detailed below ("cases that work wrong...")

  Description:

  I can resize a gnome-terminal window, everything works fine.
  (Grab it, using the mouse, by the upper-right corner (click-and-hold);
  the size changes as the mouse is moved, because the position
  of the upper-right corner follows the mouse.  (Only the upper-right corner 
moves.))
  But when I try to resize an xterm window the same way,
  this happens instead: as the mouse is moved, the upper-right corner
  does move, but it doesn't track with the mouse pointer like it should.
  Meanwhile, the lower-left corner also moves (it should have remained anchored 
in its original x-y position on the screen).

  Cases that work correctly:
  If the xterm window is grabbed by the lower-right corner and resized, this 
case works properly.
  If the xterm window is grabbed by the bottom edge and resized, this case 
works properly.
  If the xterm window is grabbed by the right edge and resized, this case works 
properly.

  Cases that work wrong ("wonky"):
  If the xterm window is grabbed by the left edge and resized, then the 
opposite (i.e. right) edge (incorrectly) migrates.
  If the xterm window is grabbed by the top edge and resized, then the opposite 
(i.e. bottom) edge (incorrectly) migrates.
  If the xterm window is grabbed by the upper-right corner and resized, then 
the window (incorrectly) migrates.
  If the xterm window is grabbed by the lower-left corner and resized, then the 
window (incorrectly) migrates.
  If the xterm window is grabbed by the upper-left corner and resized, then the 
window (incorrectly) migrates.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xterm 353-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue May 12 13:52:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GT 740] [10de:0fc8] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: PNY GK107 [GeForce GT 740] [196e:109a]
  InstallationDate: Installed on 2020-05-06 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=7f55a3c5-bff9-45ea-8979-583e4fbfec07 ro quiet splash vt.handoff=7
  SourcePackage: xterm
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0705
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  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.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A99XEVO:rvrRev1.xx: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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.

[Desktop-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

[Kai-Heng Feng]

IIUC, I should attach new debdiff for both Focal and Bionic, am I right?

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

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

[Max Waterman]

I have a similar problem on my Dell XPS 13 - if I boot the laptop with the 
headphones (3.5mm) plugged in, then it essentially disabled the 3.5mm headphone 
jack - nothing I've tried re-enabled it again (eg unplugging/replugging the 
headphone, all the settings, etc). Only a reboot without the headphones plugged 
in and plugging them in after logging in, fixes the problem.
I don't have this problem on my Lenovo T480s.
Perhaps this is a different problem?

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

Title:
  External audio device shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker, or none at
  all.

Status in gnome-control-center:
  Unknown
Status in PulseAudio:
  New
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  In Progress
Status in gnome-control-center source package in Focal:
  Invalid
Status in pulseaudio source package in Focal:
  In Progress

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

  1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
  2. Make sure it's the one selected as "Output device"
  3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  5. Try to switch back to the BT device and click Test
  -> same result as in step 3

  Tested with 2 different BT devices (one headset and one speaker) as
  well as a USB audio interface (Zoom H2N microphone).

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

[Daniel van Vugt]

^^^
https://git.launchpad.net/~ubuntu-audio-dev/pulseaudio/commit/?h=ubuntu-bionic&id=7d39b0106bd422

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

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1873942] Re: [wayland] gnome-screenshot takes a screenshot of the wrong screen

[Guillaume Michaud]

I have upgraded to mutter 3.36.2-1ubuntu1~20.04.1 this morning and rebooted.
I can confirm this new version fixes the problem for me.
Thanks!

Le mar. 12 mai 2020 à 22:36, Brian Murray  a écrit :

> Hello Guillaume, or anyone else affected,
>
> Accepted mutter into focal-proposed. The package will build now and be
> available at
> https://launchpad.net/ubuntu/+source/mutter/3.36.2-1ubuntu1~20.04.1 in a
> few hours, and then in the -proposed repository.
>
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed.  Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested, what testing has been
> performed on the package and change the tag from verification-needed-
> focal to verification-done-focal. If it does not fix the bug for you,
> please add a comment stating that, and change the tag to verification-
> failed-focal. In either case, without details of your testing we will
> not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance for helping!
>
> N.B. The updated package will be released to -updates after the bug(s)
> fixed by this package have been verified and the package has been in
> -proposed for a minimum of 7 days.
>
> ** Tags added: verification-needed verification-needed-focal
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1873942
>
> Title:
>   [wayland] gnome-screenshot takes a screenshot of the wrong screen
>
> Status in GNOME Shell:
>   Unknown
> Status in mutter package in Ubuntu:
>   Fix Released
> Status in mutter source package in Focal:
>   Fix Committed
> Status in mutter source package in Groovy:
>   Fix Released
>
> Bug description:
>   I have a dual monitor setup, with the external monitor defined as the
> "primary" one (and the laptop one secondary).
>   When using the Shift +  PrtScr shortcut and choosing an area on the
> external monitor, the screenshot saved in ~/Pictures shows this area but on
> the _laptop_ screen.
>   (Choosing an area on the laptop screen works OK.)
>
>   I use the vanilla Gnome session (with Wayland), installed with apt.
>
>   [ Impact ]
>
>   gnome-screenshot takes a screenshot of the wrong screen
>
>   [ Test case ]
>
>   In dual monitor setup, use Shift+PrtScr to take a screenshot in an
>   area in the external monitor.
>
>   The saved area should respect the one you selected
>
>   [ Regression potential ]
>
>   Screenshot or screencasting may have not espected behavior
>
>
>   ProblemType: BugDistroRelease: Ubuntu 20.04
>   Package: gnome-screenshot 3.36.0-1ubuntu1
>   ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
>   Uname: Linux 5.4.0-25-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: GNOME
>   Date: Mon Apr 20 20:58:46 2020
>   InstallationDate: Installed on 2020-04-11 (9 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=fr_FR.UTF-8
>SHELL=/bin/bashSourcePackage: gnome-screenshot
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
>   CasperMD5CheckResult: skip
>   CompositorRunning: None
>   CurrentDesktop: GNOME
>   DistUpgraded: Fresh install
>   DistroCodename: focalDistroRelease: Ubuntu 20.04
>   DistroVariant: ubuntu
>   DkmsStatus:
>acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
>acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed
>acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed
>   GraphicsCard:
>Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA
> controller])
>  Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0]
>   InstallationDate: Installed on 2020-04-11 (9 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 004: ID 8087:0a2b Intel Corp.
>Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD
> UVC WebCam
>Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: ASUSTeK COMPUTER INC. UX410UAK
>   Package: wayland (not installed)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=fr_FR.UTF-8
>SHELL=/bin/bash
>   ProcKernelCm

[Desktop-packages] [Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)

[Christian Ehrhardt ]

Since Daniel split up the "related but not the same" mutter changes to
bug 1852183 (thanks for that work BTW!) let us here focus on the spice
component.

Thanks lwk32 for identifying a fix for that, I'll be taking a look if
that is SRU-safely backportable to Focal.

** Also affects: spice-vdagent (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: virt-manager (Ubuntu)
   Status: Confirmed => Invalid

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

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

** Bug watch added: Debian Bug tracker #854936
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854936

** Also affects: spice-vdagent (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854936
   Importance: Unknown
   Status: Unknown

** Also affects: qemu (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: virt-manager (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: spice (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: spice-vdagent (Ubuntu Focal)
   Importance: Undecided
   Status: New

** No longer affects: spice (Ubuntu Focal)

** No longer affects: qemu (Ubuntu Focal)

** No longer affects: virt-manager (Ubuntu Focal)

** Changed in: spice-vdagent (Ubuntu)
   Status: New => Fix Released

** Changed in: spice-vdagent (Ubuntu Focal)
   Status: New => Triaged

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

Title:
  Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM
  guests)

Status in qemu package in Ubuntu:
  Invalid
Status in spice package in Ubuntu:
  Invalid
Status in spice-vdagent package in Ubuntu:
  Fix Released
Status in virt-manager package in Ubuntu:
  Invalid
Status in spice-vdagent source package in Focal:
  Triaged
Status in spice-vdagent package in Debian:
  Unknown
Status in spice package in Fedora:
  Unknown

Bug description:
  https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9

  ---

  I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta.

  I installed Kubuntu 20.04 and virt-manager as I did many times on
  Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt,
  libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest
  or with Ubuntu 20.04 guest then clipboard doesn't work right.

  To test it, please install Kubuntu 20.04 and then install Kubuntu /
  Ubuntu 20.04 as VM (guest). Open some simple text editor and start
  Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of
  time it won't.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: virt-manager 1:2.2.1-3ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 13 15:02:22 2020
  InstallationDate: Installed on 2020-04-09 (4 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  PackageArchitecture: all
  SourcePackage: virt-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872527/+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 1875605] Re: SRU the current 0.20.3 stable update

[Mathew Hodson]

** Changed in: libsecret (Ubuntu Focal)
   Importance: Undecided => Low

** Tags added: upgrade-software-version

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

Title:
   SRU the current 0.20.3 stable update

Status in libsecret package in Ubuntu:
  Fix Released
Status in libsecret source package in Focal:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes
  https://gitlab.gnome.org/GNOME/libsecret/-/blob/master/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that using passwords in GNOME applications or gpg/ssh keys still
  work correctly

  * Regression potential

  There is a segfault fix for flapak portals, testing that usecase would
  be useful

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1875605/+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 1875893] Re: package cups-bsd 2.3.1-9ubuntu1.1 failed to install/upgrade: installed cups-bsd package post-installation script subprocess was killed by signal (Broken pipe)

[Launchpad Bug Tracker]

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

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

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

Title:
  package cups-bsd 2.3.1-9ubuntu1.1 failed to install/upgrade: installed
  cups-bsd package post-installation script subprocess was killed by
  signal (Broken pipe)

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  i do not know
  ubuntu reported an error
  and i thought a good idea to inform you

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: cups-bsd 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CupsErrorLog: W [29/Apr/2020:16:44:13 +0300] Notifier for subscription 2 
(dbus://) went away, retrying!
  Date: Wed Apr 29 16:43:04 2020
  DuplicateSignature:
   package:cups-bsd:2.3.1-9ubuntu1.1
   Setting up cups (2.3.1-9ubuntu1.1) ...
   dpkg: error processing package cups (--configure):
installed cups package post-installation script subprocess was killed by 
signal (Broken pipe)
  ErrorMessage: installed cups-bsd package post-installation script subprocess 
was killed by signal (Broken pipe)
  InstallationDate: Installed on 2020-04-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU 
802.11n WLAN Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7996
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=d22d9622-9ef8-403d-81fd-82c8ebf28e19 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=d22d9622-9ef8-403d-81fd-82c8ebf28e19 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: cups
  Title: package cups-bsd 2.3.1-9ubuntu1.1 failed to install/upgrade: installed 
cups-bsd package post-installation script subprocess was killed by signal 
(Broken pipe)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.A0
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M PRO-VH (MS-7996)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.A0:bd10/19/2016:svnMSI:pnMS-7996:pvr1.0:rvnMSI:rnH110MPRO-VH(MS-7996):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7996
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1875893/+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 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Rajasekharan N]

I think the regression made my audio/internal speakers as Dummy Output.
See bug #1878327.

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
   State: RUNNING
   Name: alsa_input.pci-_00_1f.3.analog-stereo
   Description: Built-in Audio Analog Stereo
   Driver: module-alsa-card.c
   Sample Specification: s16le 2ch 44100Hz
   Channel Map: front-left,front-right
   Owner Module: 7
   Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+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 1866655] Re: corrupt graphics during startup

[Launchpad Bug Tracker]

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  corrupt graphics during startup

Status in firefox package in Ubuntu:
  Expired

Bug description:
  1) Ubuntu 19.10
  2) 73
  3) No corrupt graphics during Firefox startup.
  4) There are corrupt graphics during Firefox startup. Firefox was maximized 
before I closed it. When I start Firefox, it switches from minimize to 
maximized.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1866655/+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 1878330] Re: Primary hicolor icons are missing

[pqwoerituytrueiwoq]

Here are the icons i pulled from my backup

This can be fixed on a existing install by doing this

sudo cp -a ./hicolor /usr/share/icons/
sudo touch /usr/share/icons/hicolor
sudo gtk-update-icon-cache

** Attachment added: "The missing files"
   
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1878330/+attachment/5370737/+files/Rhythmbox-hicolor_Ubuntu-18.04.zip

** Description changed:

  These files are missing:
- hicolor/
+ /usr/share/icons/hicolor/
  ├── 16x16
  │   └── apps
  │   └── rhythmbox.png
  ├── 22x22
  │   └── apps
  │   └── rhythmbox.png
  ├── 24x24
  │   └── apps
  │   └── rhythmbox.png
  ├── 256x256
  │   └── apps
  │   └── rhythmbox.png
  ├── 32x32
  │   └── apps
  │   └── rhythmbox.png
  ├── 48x48
  │   └── apps
  │   └── rhythmbox.png
  └── scalable
- └── apps
- └── rhythmbox-symbolic.svg
+ └── apps
+ └── rhythmbox-symbolic.svg
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rhythmbox 3.4.4-1ubuntu2
  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: XFCE
  Date: Wed May 13 00:03:50 2020
  InstallationDate: Installed on 2018-04-29 (744 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

+ Broken image icon appears in the title bar, notifications, and in the
+ about dialog
+ 
  These files are missing:
  /usr/share/icons/hicolor/
  ├── 16x16
  │   └── apps
  │   └── rhythmbox.png
  ├── 22x22
  │   └── apps
  │   └── rhythmbox.png
  ├── 24x24
  │   └── apps
  │   └── rhythmbox.png
  ├── 256x256
  │   └── apps
  │   └── rhythmbox.png
  ├── 32x32
  │   └── apps
  │   └── rhythmbox.png
  ├── 48x48
  │   └── apps
  │   └── rhythmbox.png
  └── scalable
  └── apps
  └── rhythmbox-symbolic.svg
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rhythmbox 3.4.4-1ubuntu2
  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: XFCE
  Date: Wed May 13 00:03:50 2020
  InstallationDate: Installed on 2018-04-29 (744 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Primary hicolor icons are missing

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Broken image icon appears in the title bar, notifications, and in the
  about dialog

  These files are missing:
  /usr/share/icons/hicolor/
  ├── 16x16
  │   └── apps
  │   └── rhythmbox.png
  ├── 22x22
  │   └── apps
  │   └── rhythmbox.png
  ├── 24x24
  │   └── apps
  │   └── rhythmbox.png
  ├── 256x256
  │   └── apps
  │   └── rhythmbox.png
  ├── 32x32
  │   └── apps
  │   └── rhythmbox.png
  ├── 48x48
  │   └── apps
  │   └── rhythmbox.png
  └── scalable
  └── apps
  └── rhythmbox-symbolic.svg

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rhythmbox 3.4.4-1ubuntu2
  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: XFCE
  Date: Wed May 13 00:03:50 2020
  InstallationDate: Installed on 2018-04-29 (744 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1878330/+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 1878330] [NEW] Primary hicolor icons are missing

[pqwoerituytrueiwoq]

Public bug reported:

Broken image icon appears in the title bar, notifications, and in the
about dialog

These files are missing:
/usr/share/icons/hicolor/
├── 16x16
│   └── apps
│   └── rhythmbox.png
├── 22x22
│   └── apps
│   └── rhythmbox.png
├── 24x24
│   └── apps
│   └── rhythmbox.png
├── 256x256
│   └── apps
│   └── rhythmbox.png
├── 32x32
│   └── apps
│   └── rhythmbox.png
├── 48x48
│   └── apps
│   └── rhythmbox.png
└── scalable
└── apps
└── rhythmbox-symbolic.svg

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: rhythmbox 3.4.4-1ubuntu2
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: XFCE
Date: Wed May 13 00:03:50 2020
InstallationDate: Installed on 2018-04-29 (744 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: rhythmbox
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "The problem"
   
https://bugs.launchpad.net/bugs/1878330/+attachment/5370730/+files/Screenshot_2020-05-11_11-44-10.png

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

Title:
  Primary hicolor icons are missing

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Broken image icon appears in the title bar, notifications, and in the
  about dialog

  These files are missing:
  /usr/share/icons/hicolor/
  ├── 16x16
  │   └── apps
  │   └── rhythmbox.png
  ├── 22x22
  │   └── apps
  │   └── rhythmbox.png
  ├── 24x24
  │   └── apps
  │   └── rhythmbox.png
  ├── 256x256
  │   └── apps
  │   └── rhythmbox.png
  ├── 32x32
  │   └── apps
  │   └── rhythmbox.png
  ├── 48x48
  │   └── apps
  │   └── rhythmbox.png
  └── scalable
  └── apps
  └── rhythmbox-symbolic.svg

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rhythmbox 3.4.4-1ubuntu2
  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: XFCE
  Date: Wed May 13 00:03:50 2020
  InstallationDate: Installed on 2018-04-29 (744 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1878330/+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 1878327] Re: [Dell Inspiron 1525] Pulse audio update made internal speakers as Dummy Output

[Daniel van Vugt]

I think that might make this a duplicate of bug 1876065, whose posed fix
got clobbered and lost today.

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

Title:
  [Dell Inspiron 1525] Pulse audio update made internal speakers as
  Dummy Output

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I had already reported bug #1876238 where internal speakers are not
  detected but shown as Dummy Output after upgrading Ubuntu from 19.10
  to 20.04 LTS Focal.

  It was solved by this patch:
  https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819

  The current PulseAudio update today reversed that again. Internal
  speakers are not being detected and are shown as Dummy Output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raj2016 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 13 09:02:53 2020
  InstallationDate: Installed on 2016-12-20 (1239 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878327/+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 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Daniel van Vugt]

** Tags removed: verification-needed
** Tags added: regression-update verification-failed

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
   State: RUNNING
   Name: alsa_input.pci-_00_1f.3.analog-stereo
   Description: Built-in Audio Analog Stereo
   Driver: module-alsa-card.c
   Sample Specification: s16le 2ch 44100Hz
   Channel Map: front-left,front-right
   Owner Module: 7
   Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+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 1878327] Re: [Dell Inspiron 1525] Pulse audio update made internal speakers as Dummy Output

[Daniel van Vugt]

See bug 1876065.

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

Title:
  [Dell Inspiron 1525] Pulse audio update made internal speakers as
  Dummy Output

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I had already reported bug #1876238 where internal speakers are not
  detected but shown as Dummy Output after upgrading Ubuntu from 19.10
  to 20.04 LTS Focal.

  It was solved by this patch:
  https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819

  The current PulseAudio update today reversed that again. Internal
  speakers are not being detected and are shown as Dummy Output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raj2016 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 13 09:02:53 2020
  InstallationDate: Installed on 2016-12-20 (1239 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878327/+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 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Daniel van Vugt]

Yes the proposed update 1:13.99.1-1ubuntu3.1 got lost and overwritten by
update 1:13.99.1-1ubuntu3.2

Sorry about that. Please repropose it as 1:13.99.1-1ubuntu3.3

** Tags removed: verification-done verification-done-focal
** Tags added: verification-failed-focal verification-needed

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
   State: RUNNING
   Name: alsa_input.pci-_00_1f.3.analog-stereo
   Description: Built-in Audio Analog Stereo
   Driver: module-alsa-card.c
   Sample Specification: s16le 2ch 44100Hz
   Channel Map: front-left,front-right
   Owner Module: 7
   Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+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 1878327] Re: [Dell Inspiron 1525] Pulse audio update made internal speakers as Dummy Output

[Daniel van Vugt]

** Summary changed:

- Pulse audio update made internal speakers as Dummy Output
+ [Dell Inspiron 1525] Pulse audio update made internal speakers as Dummy Output

** Tags added: regression regression-update

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

Title:
  [Dell Inspiron 1525] Pulse audio update made internal speakers as
  Dummy Output

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I had already reported bug #1876238 where internal speakers are not
  detected but shown as Dummy Output after upgrading Ubuntu from 19.10
  to 20.04 LTS Focal.

  It was solved by this patch:
  https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819

  The current PulseAudio update today reversed that again. Internal
  speakers are not being detected and are shown as Dummy Output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raj2016 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 13 09:02:53 2020
  InstallationDate: Installed on 2016-12-20 (1239 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878327/+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 1878293] Re: xterm resize is wonky

[Daniel van Vugt]

** Also affects: xterm (Ubuntu)
   Importance: Undecided
   Status: New

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

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #543
   https://gitlab.gnome.org/GNOME/mutter/-/issues/543

** Also affects: xterm via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/543
   Importance: Unknown
   Status: Unknown

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

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

Title:
  xterm resize is wonky

Status in xterm:
  Unknown
Status in mutter package in Ubuntu:
  Triaged
Status in xterm package in Ubuntu:
  Confirmed

Bug description:
  % lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04 LTS
  Release:20.04
  Codename:   focal

  % wmctrl -m
  Name: GNOME Shell
  Class: N/A
  PID: N/A
  Window manager's "showing the desktop" mode: OFF

  Terms:
  window has four sides: top, bottom, left, and right
  when referring to corners, "upper" means "top", and "lower" means "bottom",
  so the four corners are upper-right, lower-right, lower-left, and  upper-left.
  wonky: works wrong, as detailed below ("cases that work wrong...")

  Description:

  I can resize a gnome-terminal window, everything works fine.
  (Grab it, using the mouse, by the upper-right corner (click-and-hold);
  the size changes as the mouse is moved, because the position
  of the upper-right corner follows the mouse.  (Only the upper-right corner 
moves.))
  But when I try to resize an xterm window the same way,
  this happens instead: as the mouse is moved, the upper-right corner
  does move, but it doesn't track with the mouse pointer like it should.
  Meanwhile, the lower-left corner also moves (it should have remained anchored 
in its original x-y position on the screen).

  Cases that work correctly:
  If the xterm window is grabbed by the lower-right corner and resized, this 
case works properly.
  If the xterm window is grabbed by the bottom edge and resized, this case 
works properly.
  If the xterm window is grabbed by the right edge and resized, this case works 
properly.

  Cases that work wrong ("wonky"):
  If the xterm window is grabbed by the left edge and resized, then the 
opposite (i.e. right) edge (incorrectly) migrates.
  If the xterm window is grabbed by the top edge and resized, then the opposite 
(i.e. bottom) edge (incorrectly) migrates.
  If the xterm window is grabbed by the upper-right corner and resized, then 
the window (incorrectly) migrates.
  If the xterm window is grabbed by the lower-left corner and resized, then the 
window (incorrectly) migrates.
  If the xterm window is grabbed by the upper-left corner and resized, then the 
window (incorrectly) migrates.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xterm 353-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue May 12 13:52:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GT 740] [10de:0fc8] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: PNY GK107 [GeForce GT 740] [196e:109a]
  InstallationDate: Installed on 2020-05-06 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=7f55a3c5-bff9-45ea-8979-583e4fbfec07 ro quiet splash vt.handoff=7
  SourcePackage: xterm
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0705
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  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.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUS

[Desktop-packages] [Bug 1878293] Re: xterm resize is wonky

[Timo Aaltonen]

** Package changed: xterm (Ubuntu) => mutter (Ubuntu)

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

Title:
  xterm resize is wonky

Status in xterm:
  Unknown
Status in mutter package in Ubuntu:
  Triaged
Status in xterm package in Ubuntu:
  Confirmed

Bug description:
  % lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04 LTS
  Release:20.04
  Codename:   focal

  % wmctrl -m
  Name: GNOME Shell
  Class: N/A
  PID: N/A
  Window manager's "showing the desktop" mode: OFF

  Terms:
  window has four sides: top, bottom, left, and right
  when referring to corners, "upper" means "top", and "lower" means "bottom",
  so the four corners are upper-right, lower-right, lower-left, and  upper-left.
  wonky: works wrong, as detailed below ("cases that work wrong...")

  Description:

  I can resize a gnome-terminal window, everything works fine.
  (Grab it, using the mouse, by the upper-right corner (click-and-hold);
  the size changes as the mouse is moved, because the position
  of the upper-right corner follows the mouse.  (Only the upper-right corner 
moves.))
  But when I try to resize an xterm window the same way,
  this happens instead: as the mouse is moved, the upper-right corner
  does move, but it doesn't track with the mouse pointer like it should.
  Meanwhile, the lower-left corner also moves (it should have remained anchored 
in its original x-y position on the screen).

  Cases that work correctly:
  If the xterm window is grabbed by the lower-right corner and resized, this 
case works properly.
  If the xterm window is grabbed by the bottom edge and resized, this case 
works properly.
  If the xterm window is grabbed by the right edge and resized, this case works 
properly.

  Cases that work wrong ("wonky"):
  If the xterm window is grabbed by the left edge and resized, then the 
opposite (i.e. right) edge (incorrectly) migrates.
  If the xterm window is grabbed by the top edge and resized, then the opposite 
(i.e. bottom) edge (incorrectly) migrates.
  If the xterm window is grabbed by the upper-right corner and resized, then 
the window (incorrectly) migrates.
  If the xterm window is grabbed by the lower-left corner and resized, then the 
window (incorrectly) migrates.
  If the xterm window is grabbed by the upper-left corner and resized, then the 
window (incorrectly) migrates.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xterm 353-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue May 12 13:52:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GT 740] [10de:0fc8] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: PNY GK107 [GeForce GT 740] [196e:109a]
  InstallationDate: Installed on 2020-05-06 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=7f55a3c5-bff9-45ea-8979-583e4fbfec07 ro quiet splash vt.handoff=7
  SourcePackage: xterm
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0705
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  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.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A99XEVO:rvrRev1.xx: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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: li

[Desktop-packages] [Bug 1878293] Re: xterm resize is wonky

[Launchpad Bug Tracker]

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

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

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

Title:
  xterm resize is wonky

Status in xterm:
  Unknown
Status in mutter package in Ubuntu:
  Triaged
Status in xterm package in Ubuntu:
  Confirmed

Bug description:
  % lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04 LTS
  Release:20.04
  Codename:   focal

  % wmctrl -m
  Name: GNOME Shell
  Class: N/A
  PID: N/A
  Window manager's "showing the desktop" mode: OFF

  Terms:
  window has four sides: top, bottom, left, and right
  when referring to corners, "upper" means "top", and "lower" means "bottom",
  so the four corners are upper-right, lower-right, lower-left, and  upper-left.
  wonky: works wrong, as detailed below ("cases that work wrong...")

  Description:

  I can resize a gnome-terminal window, everything works fine.
  (Grab it, using the mouse, by the upper-right corner (click-and-hold);
  the size changes as the mouse is moved, because the position
  of the upper-right corner follows the mouse.  (Only the upper-right corner 
moves.))
  But when I try to resize an xterm window the same way,
  this happens instead: as the mouse is moved, the upper-right corner
  does move, but it doesn't track with the mouse pointer like it should.
  Meanwhile, the lower-left corner also moves (it should have remained anchored 
in its original x-y position on the screen).

  Cases that work correctly:
  If the xterm window is grabbed by the lower-right corner and resized, this 
case works properly.
  If the xterm window is grabbed by the bottom edge and resized, this case 
works properly.
  If the xterm window is grabbed by the right edge and resized, this case works 
properly.

  Cases that work wrong ("wonky"):
  If the xterm window is grabbed by the left edge and resized, then the 
opposite (i.e. right) edge (incorrectly) migrates.
  If the xterm window is grabbed by the top edge and resized, then the opposite 
(i.e. bottom) edge (incorrectly) migrates.
  If the xterm window is grabbed by the upper-right corner and resized, then 
the window (incorrectly) migrates.
  If the xterm window is grabbed by the lower-left corner and resized, then the 
window (incorrectly) migrates.
  If the xterm window is grabbed by the upper-left corner and resized, then the 
window (incorrectly) migrates.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xterm 353-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue May 12 13:52:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GT 740] [10de:0fc8] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: PNY GK107 [GeForce GT 740] [196e:109a]
  InstallationDate: Installed on 2020-05-06 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=7f55a3c5-bff9-45ea-8979-583e4fbfec07 ro quiet splash vt.handoff=7
  SourcePackage: xterm
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0705
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  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.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A99XEVO:rvrRev1.xx: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.
  version.compi

[Desktop-packages] [Bug 1878301] Re: Focal regression: poor discoverability for search in Ubuntu Software Center

[Daniel van Vugt]

Please report the issue to the developers at:

  https://gitlab.gnome.org/GNOME/gnome-software/-/issues

and then tell us the new issue ID.

** Package changed: gnome-shell (Ubuntu) => gnome-software (Ubuntu)

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

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

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

Title:
  Focal regression: poor discoverability for search in Ubuntu Software
  Center

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  I wanted to install a new package. Launched Ubuntu Software and... how
  do I search for anything?

  Search is a key function. It should be front and center. I couldn't
  see it.

  That was annoying enough that I wanted to file a bug against it. In
  the process I did notice the lens icon in the top left, but seriously
  - does that look easily discoverable to anyone? There's usually
  nothing in that cornerl so users don't look there, and the contrast is
  poor, which makes it very easy to not notice.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1878301/+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 1878298] Re: Authentication window that cannot be closed in the upper left corner

[Daniel van Vugt]

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

Thanks for the bug report. This issue has already been reported as bug
1824874 so please look there.

** This bug has been marked a duplicate of bug 1824874
   undismissable, unclickable authentication dialog left on screen (top-left 
corner) after policykit authentication [pushModal: invocation of begin_modal 
failed]

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

Title:
  Authentication window that cannot be closed in the upper left corner

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I updated my computer from Ubuntu 19.10 to 20.04. Normally my MySql server is 
not starting at boot. After the update, it started working at boot. Normally I 
was starting this server manually when I need.
  Currently, when I put my computer to snooze mode and turn it on again, a 
dialog titled "Authentication Required" opens in the upper left corner of the 
screen (after I login to system). This dialog is not moving in any way, the 
cancel button is not working, it is not reacting when I enter password. I tried 
enter the correct password and wrong passwords, but the result is the same.
  In order to close this dialog, I have to either restart the computer or 
re-login.
  I tried to find the package name with the command 'ubuntu-bug -w', but it did 
not work. So I haven't got information about package name/version.

  
  DistroRelease: Ubuntu 20.04
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Package: gnome-shell 3.36.1-5ubuntu2
  UpgradeStatus: Upgraded to Focal Fossa on 2020-05-11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878298/+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 1878293] [NEW] xterm resize is wonky

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

% lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
Codename:   focal

% wmctrl -m
Name: GNOME Shell
Class: N/A
PID: N/A
Window manager's "showing the desktop" mode: OFF

Terms:
window has four sides: top, bottom, left, and right
when referring to corners, "upper" means "top", and "lower" means "bottom",
so the four corners are upper-right, lower-right, lower-left, and  upper-left.
wonky: works wrong, as detailed below ("cases that work wrong...")

Description:

I can resize a gnome-terminal window, everything works fine.
(Grab it, using the mouse, by the upper-right corner (click-and-hold);
the size changes as the mouse is moved, because the position
of the upper-right corner follows the mouse.  (Only the upper-right corner 
moves.))
But when I try to resize an xterm window the same way,
this happens instead: as the mouse is moved, the upper-right corner
does move, but it doesn't track with the mouse pointer like it should.
Meanwhile, the lower-left corner also moves (it should have remained anchored 
in its original x-y position on the screen).

Cases that work correctly:
If the xterm window is grabbed by the lower-right corner and resized, this case 
works properly.
If the xterm window is grabbed by the bottom edge and resized, this case works 
properly.
If the xterm window is grabbed by the right edge and resized, this case works 
properly.

Cases that work wrong ("wonky"):
If the xterm window is grabbed by the left edge and resized, then the opposite 
(i.e. right) edge (incorrectly) migrates.
If the xterm window is grabbed by the top edge and resized, then the opposite 
(i.e. bottom) edge (incorrectly) migrates.
If the xterm window is grabbed by the upper-right corner and resized, then the 
window (incorrectly) migrates.
If the xterm window is grabbed by the lower-left corner and resized, then the 
window (incorrectly) migrates.
If the xterm window is grabbed by the upper-left corner and resized, then the 
window (incorrectly) migrates.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xterm 353-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: GNOME
Date: Tue May 12 13:52:47 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GK107 [GeForce GT 740] [10de:0fc8] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: PNY GK107 [GeForce GT 740] [196e:109a]
InstallationDate: Installed on 2020-05-06 (6 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=7f55a3c5-bff9-45ea-8979-583e4fbfec07 ro quiet splash vt.handoff=7
SourcePackage: xterm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/23/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0705
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A99X EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
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.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A99XEVO:rvrRev1.xx: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.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
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

** Affects: mutter (Ubuntu)
 

[Desktop-packages] [Bug 1878285] Re: gnome-control-center crashes on setting up fingerprint

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

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

Title:
  gnome-control-center crashes on setting up fingerprint

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

Bug description:
  When I try to setup my fingerprint in gnome-control-center, I first
  have to choose which finger I would use, and when I press the "next"
  button, it crashes : "Unable to access device "Validity VFS0050"
  GDBus.Error:org.freedesktop.DBus.Error.NoReply:Message recipient
  disconnected from message bus without replying".

  
  For information, my fingerprint sensor is :
  - lsusb
  Bus 001 Device 005: ID 138a:0050 Validity Sensors, Inc. Swipe Fingerprint 
Sensor

  
  Ubuntu 20.04

  gnome-control-center:
Installé : 1:3.36.1-1ubuntu5
Candidat : 1:3.36.1-1ubuntu5
   Table de version :
   *** 1:3.36.1-1ubuntu5 500
  500 http://be.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  What I expected to happen, is that everything works and that I can set up my 
finger for unlocking.

  What happened instead : it crashes with the information "Unable to
  access device "Validity VFS0050"
  GDBus.Error:org.freedesktop.DBus.Error.NoReply:Message recipient
  disconnected from message bus without replying".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 22:00:30 2020
  InstallationDate: Installed on 2020-05-11 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   LANGUAGE=fr_BE:fr
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  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/1878285/+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 1878327] [NEW] Pulse audio update made internal speakers as Dummy Output

[Rajasekharan N]

Public bug reported:

I had already reported bug #1876238 where internal speakers are not
detected but shown as Dummy Output after upgrading Ubuntu from 19.10 to
20.04 LTS Focal.

It was solved by this patch:
https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819

The current PulseAudio update today reversed that again. Internal
speakers are not being detected and are shown as Dummy Output.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.2
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  raj2016 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed May 13 09:02:53 2020
InstallationDate: Installed on 2016-12-20 (1239 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/27/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 1525
dmi.sys.vendor: Dell Inc.

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

Title:
  Pulse audio update made internal speakers as Dummy Output

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I had already reported bug #1876238 where internal speakers are not
  detected but shown as Dummy Output after upgrading Ubuntu from 19.10
  to 20.04 LTS Focal.

  It was solved by this patch:
  https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819

  The current PulseAudio update today reversed that again. Internal
  speakers are not being detected and are shown as Dummy Output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raj2016 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 13 09:02:53 2020
  InstallationDate: Installed on 2016-12-20 (1239 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878327/+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 1775999] Re: Cannot set vino preferences in Lubuntu 18.04

[Julio Mejia]

Hello I also had the same problem but the cause was the desktop I use
kubuntu 19.10 and obviously KDE desktop when installing came I saw the
suggestion to install an additional program for wine which allows its
configuration in gnome and when trying to install this program suggests
installing all the gnome desktop hahaha, solution? install krfb which is
for KDE and that's it.

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

Title:
  Cannot set vino preferences in Lubuntu 18.04

Status in vino package in Ubuntu:
  Confirmed

Bug description:
  Apparently the functionality of vino-preferences was merged into
  gnome-control-center for 18.04. But since Lubuntu does not include
  gnome-control-center, there is no way to set up vino.,

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vino 3.22.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic i686
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sat Jun  9 08:40:31 2018
  InstallationDate: Installed on 2018-03-09 (91 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180306.1)
  SourcePackage: vino
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1775999/+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 1878278] Re: Xorg freeze after mouse pointer size change

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1878105, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1878105
   [nvidia] Xorg crashes in ?? from FreeCursor() from ChangeWindowAttributes()

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

Title:
  Xorg freeze after mouse pointer size change

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I've attempted to change the size of my mouse pointer (Settings /
  Universal Access / Cursor Size) from the default. As soon as I did
  this the desktop froze and eventually turned black.

  I could ssh in and would see the Xorg process consuming 100% cpu (per
  top). After killing -9 that Xorg process, and resetting dconf reset
  /org/gnome/desktop/interface/cursor-size  I could log in to a new
  session.

  This seems reproducible, i.e. setting up pointer size again would give
  me the same symptoms.

  
  Apport probably collected this but jic, could see this in Xorg.log:

  [  1552.379] (EE) 
  [  1552.380] (EE) Backtrace:
  [  1552.380] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x563325a93dec]
  [  1552.381] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) 
[0x7f2f998ab41f]
  [  1552.381] (EE) 2: /usr/lib/xorg/Xorg (RamDacHandleColormaps+0xb2f) 
[0x5633259b337f]
  [  1552.381] (EE) 3: /usr/lib/xorg/Xorg (AddTraps+0x5d58) [0x563325a11648]
  [  1552.382] (EE) 4: /usr/lib/xorg/Xorg (FreeCursor+0x67) [0x563325926267]
  [  1552.382] (EE) 5: /usr/lib/xorg/Xorg (ChangeWindowAttributes+0xa41) 
[0x563325960cf1]
  [  1552.382] (EE) 6: /usr/lib/xorg/Xorg (ProcBadRequest+0x223) 
[0x56332592cad3]
  [  1552.382] (EE) 7: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) 
[0x563325932f44]
  [  1552.382] (EE) 8: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x563325936fd4]
  [  1552.382] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) 
[0x7f2f996c90b3]
  [  1552.383] (EE) 10: /usr/lib/xorg/Xorg (_start+0x2e) [0x563325920a3e]
  [  1552.383] (EE) 
  [  1552.383] (EE) Segmentation fault at address 0x7
  [  1552.383] (EE) 
  Fatal server error:
  [  1552.383] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [  1552.383] (EE) 
  [  1552.383] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [  1552.383] (EE) Please also check the log file at "/var/log/Xorg.1.log" for 
additional information.
  [  1552.383] (EE) 
  [  1552.383] (EE) NVIDIA(0): The NVIDIA X driver has encountered an error; 
attempting to
  [  1552.383] (EE) NVIDIA(0): recover...
  [  1555.389] (EE) NVIDIA(GPU-0): Failed to initialize DMA.
  [  1556.391] (EE) NVIDIA(0): Failed to allocate push buffer
  [  1556.391] (EE) NVIDIA(0): Error recovery failed.
  [  1556.391] (EE) NVIDIA(0):  *** Aborting ***
  [  1556.391] (EE) 
  FatalError re-entered, aborting
  [  1556.391] (EE) Failed to recover from error!

  Let me know if I can help with diagnostics / repro

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp nvidia_modeset zcommon znvpair 
nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 21:18:28 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:225b]
 Subsystem: Lenovo GP108GLM [Quadro P500 Mobile] [17aa:225b]
  InstallationDate: Installed on 2020-04-25 (17 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423

[Desktop-packages] [Bug 1878275] Re: wayland session hard freezes on login from GDM (X11 session works fine)

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** Package changed: gdm3 (Ubuntu) => mutter (Ubuntu)

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

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

Title:
  wayland session hard freezes on login from GDM (X11 session works
  fine)

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When I login to my laptop running Ubuntu 20.04, after entering my
  username, when I choose the "gear" button and select Ubuntu on Wayland
  as the session type, my laptop freezes hard. Mouse and keyboard do not
  respond, and the first three times I hit this issue I had to forcibly
  power off. The normal (X11) Ubuntu session works fine.

  However, I realized that I could still ping and ssh in, and doing that
  gave me some clues to the issue.

  I have keychain installed for password-less SSH, and my bash_profile has:
  ---
  #!/bin/bash
  # Get the aliases and functions
  if [ -f $HOME/.bashrc ] ; then
source $HOME/.bashrc
  fi

  # Setup password-less SSH
  [ -z "$HOSTNAME" ] && HOSTNAME=`uname -n`
  keychain $HOME/.ssh/id_rsa
  source $HOME/.keychain/${HOSTNAME}-sh
  ---

  When I login via SSH from another machine after hitting the issue, I get:
  [johnjaco@johnjaco-m-v02f: ~/Downloads] ssh john@192.168.1.10
  Welcome to Ubuntu 20.04 LTS (GNU/Linux 5.4.0-29-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

  
  0 updates can be installed immediately.
  0 of these updates are security updates.

  Your Hardware Enablement Stack (HWE) is supported until April 2025.
  Last login: Mon Apr 27 19:41:17 2020 from 192.168.1.3

   * keychain 2.8.5 ~ http://www.funtoo.org
   * Waiting 5 seconds for lock...
   * Found existing ssh-agent: 2086
   * Adding 1 ssh key(s): /home/john/.ssh/id_rsa
  Enter passphrase for /home/john/.ssh/id_rsa: 
   * ssh-add: Identities added: /home/john/.ssh/id_rsa
  [john@andromeda: ~] pstree
  systemd─┬─NetworkManager───2*[{NetworkManager}]
  ├─accounts-daemon───2*[{accounts-daemon}]
  ├─acpid
  ├─avahi-daemon───avahi-daemon
  ├─bluetoothd
  ├─boltd───2*[{boltd}]
  ├─colord───2*[{colord}]
  ├─containerd───13*[{containerd}]
  ├─cron
  ├─cups-browsed───2*[{cups-browsed}]
  ├─cupsd
  ├─dbus-daemon
  ├─dnsmasq───dnsmasq
  
├─gdm3─┬─gdm-session-wor─┬─gdm-wayland-ses─┬─gnome-session-b───3*[{gnom+
  │  │ │ └─2*[{gdm-wayland-ses}]
  │  │ └─2*[{gdm-session-wor}]
  │  ├─gdm-session-wor─┬─gdm-wayland-ses─┬─bash───keychain───ssh-add
  │  │ │ └─2*[{gdm-wayland-ses}]
  │  │ └─2*[{gdm-session-wor}]
  │  └─2*[{gdm3}]
  ├─gnome-keyring-d───2*[{gnome-keyring-d}]
  ├─iio-sensor-prox───2*[{iio-sensor-prox}]
  ├─irqbalance───{irqbalance}
  ├─2*[kerneloops]
  ├─libvirtd───16*[{libvirtd}]
  ├─networkd-dispat
  ├─packagekitd───2*[{packagekitd}]
  ├─polkitd───2*[{polkitd}]
  ├─rsyslogd───3*[{rsyslogd}]
  ├─rtkit-daemon───2*[{rtkit-daemon}]
  ├─ssh-agent
  ├─sshd───sshd───sshd───bash───pstree
  ├─switcheroo-cont───2*[{switcheroo-cont}]
  ├─systemd─┬─(sd-pam)
  │ ├─at-spi-bus-laun─┬─dbus-daemon
  │ │ └─3*[{at-spi-bus-laun}]
  │ ├─at-spi2-registr───2*[{at-spi2-registr}]
  │ ├─dbus-daemon
  │ ├─dconf-service───2*[{dconf-service}]
  │ ├─gjs───10*[{gjs}]
  │ ├─gnome-keyring-d───3*[{gnome-keyring-d}]
  │ ├─gnome-session-b───3*[{gnome-session-b}]
  │ ├─gnome-session-c───{gnome-session-c}
  │ ├─gnome-shell─┬─Xwayland───20*[{Xwayland}]
  │ │ ├─ibus-daemon─

[Desktop-packages] [Bug 1878105] Re: [nvidia] Xorg crashes in ?? from FreeCursor() from ChangeWindowAttributes()

[Daniel van Vugt]

>From duplicate bug 1878278:

[ 1552.380] (EE) Backtrace:
[ 1552.380] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x563325a93dec]
[ 1552.381] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) 
[0x7f2f998ab41f]
[ 1552.381] (EE) 2: /usr/lib/xorg/Xorg (RamDacHandleColormaps+0xb2f) 
[0x5633259b337f]
[ 1552.381] (EE) 3: /usr/lib/xorg/Xorg (AddTraps+0x5d58) [0x563325a11648]
[ 1552.382] (EE) 4: /usr/lib/xorg/Xorg (FreeCursor+0x67) [0x563325926267]
[ 1552.382] (EE) 5: /usr/lib/xorg/Xorg (ChangeWindowAttributes+0xa41) 
[0x563325960cf1]
[ 1552.382] (EE) 6: /usr/lib/xorg/Xorg (ProcBadRequest+0x223) [0x56332592cad3]
[ 1552.382] (EE) 7: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) 
[0x563325932f44]
[ 1552.382] (EE) 8: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x563325936fd4]
[ 1552.382] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) 
[0x7f2f996c90b3]
[ 1552.383] (EE) 10: /usr/lib/xorg/Xorg (_start+0x2e) [0x563325920a3e]
[ 1552.383] (EE)
[ 1552.383] (EE) Segmentation fault at address 0x7

** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
   Status: Incomplete => Confirmed

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

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

Title:
  [nvidia] Xorg crashes in ?? from FreeCursor() from
  ChangeWindowAttributes()

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Crash is caused when visiting websites that attempt to customize the
  cursor layout. (Tested with Firefox 76.0 (64-bit))

  The website on which the crash first occurred was the following:
  https://www.yellibeanz.com/
  the crash is triggered after moving the cursor around. 

  To test the hypothesis of the cursor causing the bug I also tested the
  following website with identical outcome:

  http://www.flockofsiegel.tv/

  I am sure that one can find more examples here:

  https://onextrapixel.com/10-websites-that-replace-mouse-cursors-for-a
  -better-cause/

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu14
Candidate: 1:7.7+19ubuntu14
Version table:
   *** 1:7.7+19ubuntu14 500
  500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 11 23:58:41 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-28-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Mobile) [1043:1fc0]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:1fc0]
  InstallationDate: Installed on 2020-05-03 (8 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 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X580GD_N580GD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=04dedfb2-c5a9-4447-af72-16999d76fce2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X580GD.309
  dmi.board.asset.tag: ATN123456789012345

[Desktop-packages] [Bug 1878278] Re: Xorg freeze after mouse pointer size change

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

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

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

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

Title:
  Xorg freeze after mouse pointer size change

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I've attempted to change the size of my mouse pointer (Settings /
  Universal Access / Cursor Size) from the default. As soon as I did
  this the desktop froze and eventually turned black.

  I could ssh in and would see the Xorg process consuming 100% cpu (per
  top). After killing -9 that Xorg process, and resetting dconf reset
  /org/gnome/desktop/interface/cursor-size  I could log in to a new
  session.

  This seems reproducible, i.e. setting up pointer size again would give
  me the same symptoms.

  
  Apport probably collected this but jic, could see this in Xorg.log:

  [  1552.379] (EE) 
  [  1552.380] (EE) Backtrace:
  [  1552.380] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x563325a93dec]
  [  1552.381] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) 
[0x7f2f998ab41f]
  [  1552.381] (EE) 2: /usr/lib/xorg/Xorg (RamDacHandleColormaps+0xb2f) 
[0x5633259b337f]
  [  1552.381] (EE) 3: /usr/lib/xorg/Xorg (AddTraps+0x5d58) [0x563325a11648]
  [  1552.382] (EE) 4: /usr/lib/xorg/Xorg (FreeCursor+0x67) [0x563325926267]
  [  1552.382] (EE) 5: /usr/lib/xorg/Xorg (ChangeWindowAttributes+0xa41) 
[0x563325960cf1]
  [  1552.382] (EE) 6: /usr/lib/xorg/Xorg (ProcBadRequest+0x223) 
[0x56332592cad3]
  [  1552.382] (EE) 7: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) 
[0x563325932f44]
  [  1552.382] (EE) 8: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x563325936fd4]
  [  1552.382] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) 
[0x7f2f996c90b3]
  [  1552.383] (EE) 10: /usr/lib/xorg/Xorg (_start+0x2e) [0x563325920a3e]
  [  1552.383] (EE) 
  [  1552.383] (EE) Segmentation fault at address 0x7
  [  1552.383] (EE) 
  Fatal server error:
  [  1552.383] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [  1552.383] (EE) 
  [  1552.383] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [  1552.383] (EE) Please also check the log file at "/var/log/Xorg.1.log" for 
additional information.
  [  1552.383] (EE) 
  [  1552.383] (EE) NVIDIA(0): The NVIDIA X driver has encountered an error; 
attempting to
  [  1552.383] (EE) NVIDIA(0): recover...
  [  1555.389] (EE) NVIDIA(GPU-0): Failed to initialize DMA.
  [  1556.391] (EE) NVIDIA(0): Failed to allocate push buffer
  [  1556.391] (EE) NVIDIA(0): Error recovery failed.
  [  1556.391] (EE) NVIDIA(0):  *** Aborting ***
  [  1556.391] (EE) 
  FatalError re-entered, aborting
  [  1556.391] (EE) Failed to recover from error!

  Let me know if I can help with diagnostics / repro

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp nvidia_modeset zcommon znvpair 
nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 21:18:28 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  Graphic

[Desktop-packages] [Bug 1878247] Re: CTRL-Shift-PrntScreen Somtimes does not work

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

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

** Summary changed:

- CTRL-Shift-PrntScreen Somtimes does not work
+ CTRL-Shift-PrntScreen screenshots sometimes don't work

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

Title:
  CTRL-Shift-PrntScreen screenshots sometimes don't work

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Im not sure what exactly happens, but it seems like the print screen
  function does not work.  I'll press ctrl-shift-prntscrn and it creates
  the pointer to select region, then nothing actually gets captured. If
  I just press print screen, then it takes a whole desktop screen shot
  and then after that it will let me screenshot an area.

  
  Ive had this happen a few times now.  Anyway, I figured Id report it.  I know 
its not really enough to go on, but I wanted to report that its happening.

  
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 12:22:59 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.6, 5.4.0-28-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP104 [GeForce GTX 1070 Ti] 
[19da:2445]
  InstallationDate: Installed on 2020-04-24 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6b3bc0f9-1ec0-49ae-9a4f-972d83e14ce4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.00
  dmi.board.name: Z390 Phantom Gaming-ITX/ac
  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.:bvrP4.00:bd03/15/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming-ITX/ac: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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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/1878247/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Daniel van Vugt]

** Summary changed:

- Bluetooth headset not working when selecting HSP/HFP audio profile in Focal 
Fossa
+ [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting 
HSP/HFP audio profile in Focal Fossa

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878194/+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 1878193] Re: Re-logging occurs continuously during ubuntu operation

[Daniel van Vugt]

Thanks for the bug reports. I don't yet fully understand what kind of
problem you are trying to report, but I can see a couple of problems in
the attached files:

 (1) The Nvidia driver is not properly installed and not functioning.
Please uninstall the Nvidia driver and then reinstall it using the
'Additional Drivers' app. Do not install the the driver manually.

 (2) The connection to your 4K display seems faulty and constantly being
redetected. That might be a cable problem or it might be a software
problem caused by (1).

Please reinstall the Nvidia driver as described above, and let me know
if those are not the issues you are trying to describe.

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-440
(Ubuntu)

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

** Tags added: nvidia

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

Title:
  Re-logging occurs continuously during ubuntu operation

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Incomplete

Bug description:
  from https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875435

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 14:52:03 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation TU104BM [GeForce RTX 2080 Mobile] [10de:1ed0] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TU104BM [GeForce RTX 2080 Mobile] 
[103c:8603]
  InstallationDate: Installed on 2020-04-24 (17 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=c8a52116-acb9-4b90-b5b4-8f3641a10385 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 5VX37AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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/nvidia-graphics-drivers-440/+bug/1878193/+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 1878187] Re: Re-logging occurs continuously during ubuntu operation

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1875435
   Re-logging occurs continuously during ubuntu operation
** This bug has been marked a duplicate of bug 1878193
   Re-logging occurs continuously during ubuntu operation

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

Title:
  Re-logging occurs continuously during ubuntu operation

Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  I was asked to recreate this bug
  https://bugs.launchpad.net/ubuntu/+bug/1875435

  I shot 2 videos of how this happens
  https://youtu.be/THUdqpTpMSQ
  https://youtu.be/M-T3Go76jqI

  I booted from the kernel version 5.4.0-31-generic without the nvidia
  driver. This you can see in the second video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1878187/+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 1875435] Re: Re-logging occurs continuously during ubuntu operation

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1878193
   Re-logging occurs continuously during ubuntu operation

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

Title:
  Re-logging occurs continuously during ubuntu operation

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I thought that I had some kind of problem with the video driver and all the 
detailed logs are contained here 
https://forums.developer.nvidia.com/t/ubuntu-kernel-v5-6-v5-7-for-hp-omen-17t-bc000-gforce-rtx2080-unstable-driver-nvidia-linux-x86-64-440-82-run/120027/25
  But I installed ubuntu 20.04 and the problem is repeated not only on new 
kernels ubuntu 5.6 and 5.7.0-rc but also on kernel 5.4 with the Nouveau driver
  The system constantly logs onto the standard screen and requires a password 
to close all current programs
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation TU104BM [GeForce RTX 2080 Mobile] [10de:1ed0] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TU104BM [GeForce RTX 2080 Mobile] 
[103c:8603]
  InstallationDate: Installed on 2020-04-24 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  Package: xorg 1:7.7+19ubuntu14
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=c8a52116-acb9-4b90-b5b4-8f3641a10385 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Tags:  focal possible-manual-nvidia-install ubuntu
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 5VX37AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation TU104BM [GeForce RTX 2080 Mobile] [10de:1ed0] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TU104BM [GeForce RTX 2080 Mobile] 
[103c:8603]
  InstallationDate: Installed on 2020-04-24 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  Package: xorg 1:7.7+19ubuntu14
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=c8a52116-acb9-4b90-b5b4-8f3641a10385 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Tags:  focal possible-manual-nvidia-install ubuntu
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603

[Desktop-packages] [Bug 1877735] Re: Video playback is choppy

[Daniel van Vugt]

Please also try selecting 'Ubuntu on Wayland' from the login screen.
Plenty of people including myself feel that is performing better at the
moment.


** Summary changed:

- Video playback is choppy
+ Video playback is choppy [Haswell 1080p]

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

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

Title:
  Video playback is choppy [Haswell 1080p]

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  After upgrade from 19.10 to 20.04 video playback is choppy

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 
5.4.0-7626.30~1588169883~20.04~bbe668a~dev-generic 5.4.30
  Uname: Linux 5.4.0-7626-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 06:43:40 2020
  DistUpgraded: 2020-05-08 18:55:15,812 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  MachineType: System76, Inc. Wild Dog Performance
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-7626-generic 
root=UUID=6ce8ac8b-f6ef-47b4-9428-b35e00870dfa ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-05-08 (0 days ago)
  dmi.bios.date: 01/20/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0806
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: wilp10
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0806:bd01/20/2014:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp10:rvnASUSTeKCOMPUTERINC.:rnH87-PLUS:rvrRevX.0x:cvnSystem76,Inc.:ct3:cvrwilp10:
  dmi.product.family: ASUS MB
  dmi.product.name: Wild Dog Performance
  dmi.product.sku: All
  dmi.product.version: wilp10
  dmi.sys.vendor: System76, Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-05-27T19:28:01.524954
  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.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  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
  xserver.bootTime: Thu Nov  9 16:56:44 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1.3
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877735/+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 1877735] Re: Video playback is choppy

[Daniel van Vugt]

Thanks. Choppy video in a windowed browser is probably either a browser
bug or a compositor bug.

Please run 'top' in a Terminal window while it's happening so we can see
if anything is using particularly high CPU during the problem.


** Package changed: ubuntu => mutter (Ubuntu)

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

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

Title:
  Video playback is choppy [Haswell 1080p]

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  After upgrade from 19.10 to 20.04 video playback is choppy

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 
5.4.0-7626.30~1588169883~20.04~bbe668a~dev-generic 5.4.30
  Uname: Linux 5.4.0-7626-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 06:43:40 2020
  DistUpgraded: 2020-05-08 18:55:15,812 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  MachineType: System76, Inc. Wild Dog Performance
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-7626-generic 
root=UUID=6ce8ac8b-f6ef-47b4-9428-b35e00870dfa ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-05-08 (0 days ago)
  dmi.bios.date: 01/20/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0806
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: wilp10
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0806:bd01/20/2014:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp10:rvnASUSTeKCOMPUTERINC.:rnH87-PLUS:rvrRevX.0x:cvnSystem76,Inc.:ct3:cvrwilp10:
  dmi.product.family: ASUS MB
  dmi.product.name: Wild Dog Performance
  dmi.product.sku: All
  dmi.product.version: wilp10
  dmi.sys.vendor: System76, Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-05-27T19:28:01.524954
  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.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  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
  xserver.bootTime: Thu Nov  9 16:56:44 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1.3
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877735/+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 1878322] [NEW] cupsaddsmb

[anthony olszynski]

Public bug reported:

this app is not into this package !

ubuntu server 20.04

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

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

Title:
  cupsaddsmb

Status in cups package in Ubuntu:
  New

Bug description:
  this app is not into this package !

  ubuntu server 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1878322/+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 1877746] Re: Lock screen not working

[Daniel van Vugt]

DPI is toolkit-specific and I won't go further into that because it is
off-topic. Please open a separate bug for that.

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

Title:
  Lock screen not working

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The screen will not automatically lock on the specified timer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 08:54:58 2020
  DistUpgraded: 2020-04-27 21:42:55,589 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-28-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1660 Ti] 
[1458:3fbe]
  InstallationDate: Installed on 2018-07-01 (678 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6998b6fb-9ba7-4ce9-a023-b36dab34d51a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-28 (11 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: X470 AORUS ULTRA GAMING-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X470 AORUS ULTRA GAMING
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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/1877746/+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 1877746] Re: Lock screen not working

[Daniel van Vugt]

In comment #7 I meant please disable Bluetooth, Wifi, and unplug all USB
devices. Does that allow the system to sleep? If so then please
reintroduce them individually to find out which is the problem.

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

Title:
  Lock screen not working

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The screen will not automatically lock on the specified timer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 08:54:58 2020
  DistUpgraded: 2020-04-27 21:42:55,589 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-28-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1660 Ti] 
[1458:3fbe]
  InstallationDate: Installed on 2018-07-01 (678 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6998b6fb-9ba7-4ce9-a023-b36dab34d51a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-28 (11 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: X470 AORUS ULTRA GAMING-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X470 AORUS ULTRA GAMING
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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/1877746/+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 1877735] [NEW] Video playback is choppy

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After upgrade from 19.10 to 20.04 video playback is choppy

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a~dev-generic 
5.4.30
Uname: Linux 5.4.0-7626-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat May  9 06:43:40 2020
DistUpgraded: 2020-05-08 18:55:15,812 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
MachineType: System76, Inc. Wild Dog Performance
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-7626-generic 
root=UUID=6ce8ac8b-f6ef-47b4-9428-b35e00870dfa ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-05-08 (0 days ago)
dmi.bios.date: 01/20/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0806
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: wilp10
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0806:bd01/20/2014:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp10:rvnASUSTeKCOMPUTERINC.:rnH87-PLUS:rvrRevX.0x:cvnSystem76,Inc.:ct3:cvrwilp10:
dmi.product.family: ASUS MB
dmi.product.name: Wild Dog Performance
dmi.product.sku: All
dmi.product.version: wilp10
dmi.sys.vendor: System76, Inc.
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2014-05-27T19:28:01.524954
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.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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
xserver.bootTime: Thu Nov  9 16:56:44 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.3
xserver.video_driver: modeset

** Affects: mutter (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug focal performance third-party-packages ubuntu
-- 
Video playback is choppy
https://bugs.launchpad.net/bugs/1877735
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to mutter in Ubuntu.

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

[Desktop-packages] [Bug 1877686] Re: Mouse lags during desktop zoom

[Daniel van Vugt]

** Summary changed:

- Mouse lags since 20.04 update
+ Mouse lags during desktop zoom

** Package changed: ubuntu => mutter (Ubuntu)

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

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

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

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Medium

** Tags added: a11y

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

Title:
  Mouse lags during desktop zoom

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  After installing ubuntu 20.04, I have an issue with my mouse pointer
  lagging a lot.

  It happens on my trackpad, physical mouse, wacom tablet, and
  trackpoint.

  It's only a graphical issue (ie: The underlying whatever is actually
  moving. The visible pointer just isn't).

  Other mouse moving related actions do not exhibit the same behaviour.
  Window dragging is smooth. Applications that use custom mouse
  pointers, such as krita, work smoothly.

  The issue persists both on nVidia graphics and intel integrated
  graphics.

  I am using a lenovo thinkpad p50.

  The issue persists constantly when I am using the in built laptop
  screen. However, when I connect a second monitor, it only happens
  occasionally.

  I installed ubuntu 20.04 from a usb drive, keeping my home partition
  from 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 01:28:03 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 530 [17aa:222e]
   NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:222e]
  InstallationDate: Installed on 2020-05-08 (0 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 003: ID 138a:0090 Validity Sensors, Inc. VFS7500 Touch 
Fingerprint Sensor
   Bus 001 Device 002: ID 04ca:7058 Lite-On Technology Corp. Integrated Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
   |__ Port 8: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
   |__ Port 8: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
   |__ Port 9: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
  MachineType: LENOVO 20EQS2BH00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=9eb4b789-a22e-455b-8e8b-19e78e0ef3d6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET86W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS2BH00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET86W(1.59):bd08/28/2019:svnLENOVO:pn20EQS2BH00:pvrThinkPadP50:rvnLENOVO:rn20EQS2BH00:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EQS2BH00
  dmi.product.sku: LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserve

[Desktop-packages] [Bug 1878152] Re: [Dell Vostro 5568] no sound out of headphones

[Daniel van Vugt]

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

Sounds related to bug 1876065 so let's track it there first. If the fix
for bug 1876065 does not work then we can separate it again.

** Summary changed:

- no sound out of headphones
+ [Dell Vostro 5568] no sound out of headphones

** This bug has been marked a duplicate of bug 1876065
   After unplug headphones and plug them again no sound can be heard

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

Title:
  [Dell Vostro 5568] no sound out of headphones

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to 20.04, when plugging an headphone with integrated
  microphone in my Dell Vostro15 the system makes a display of changing
  sounds settings (i.e. a volume bar is showed with the headphones sound
  level) but no sound is coming out either from the headphones or the
  system speakers.

  Opening the audio mixer settings, I can see that the selected output
  device is "Headphones (plugged in)" (the other displayed alternative
  being "Speakers (plugged in)". The selected input device is
  "Microphone (plugged in)" and there are two other alternatives:
  "Headset Microphone (plugged in)" and "Internal Microphone (plugged
  in)".

  If I change the setting for the *input* device from "Microphone" to
  "Headset Microphone" sound magically starts coming out of the
  headphones.

  It may or may not be useful to remark that if I unplug the settings for 
output device changes to "Speakers (plugged in)" while the "Headphones" 
alternative is now correctly marked as unplugged and sound comes out of the 
speakers as expected. The situation for the input device, however, is slightly 
surprising:
   - If I changed the settings as described above the settings stay the same, 
i.e. "Headset microphone (plugged in)"
   - If I let the input device unchanged (i.e. "Microphone (plugged in)", it 
switches back to "Internal Microphone (plugged in)" while the "Microphone" 
device has its status reported as "unplugged".
  In both cases, the input device "Headphone microphone" keeps the "plugged in" 
status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hobbit 1935 F pulseaudio
   /dev/snd/pcmC0D0c:   hobbit 1935 F...m pulseaudio
   /dev/snd/pcmC0D0p:   hobbit 1935 F...m pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue May 12 08:52:12 2020
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2019-02-09 (457 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-05-08 (3 days ago)
  dmi.bios.date: 09/11/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0XT0D3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd09/11/2017:svnDellInc.:pnVostro5568:pvr:rvnDellInc.:rn0XT0D3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5568
  dmi.product.sku: 0786
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878152/+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 1877686] [NEW] Mouse lags during desktop zoom

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After installing ubuntu 20.04, I have an issue with my mouse pointer
lagging a lot.

It happens on my trackpad, physical mouse, wacom tablet, and trackpoint.

It's only a graphical issue (ie: The underlying whatever is actually
moving. The visible pointer just isn't).

Other mouse moving related actions do not exhibit the same behaviour.
Window dragging is smooth. Applications that use custom mouse pointers,
such as krita, work smoothly.

The issue persists both on nVidia graphics and intel integrated
graphics.

I am using a lenovo thinkpad p50.

The issue persists constantly when I am using the in built laptop
screen. However, when I connect a second monitor, it only happens
occasionally.

I installed ubuntu 20.04 from a usb drive, keeping my home partition
from 18.04.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat May  9 01:28:03 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 530 [17aa:222e]
 NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:222e]
InstallationDate: Installed on 2020-05-08 (0 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 003: ID 138a:0090 Validity Sensors, Inc. VFS7500 Touch 
Fingerprint Sensor
 Bus 001 Device 002: ID 04ca:7058 Lite-On Technology Corp. Integrated Camera
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
 |__ Port 8: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
 |__ Port 8: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
 |__ Port 9: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
MachineType: LENOVO 20EQS2BH00
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=9eb4b789-a22e-455b-8e8b-19e78e0ef3d6 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/28/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1EET86W (1.59 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20EQS2BH00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET86W(1.59):bd08/28/2019:svnLENOVO:pn20EQS2BH00:pvrThinkPadP50:rvnLENOVO:rn20EQS2BH00:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P50
dmi.product.name: 20EQS2BH00
dmi.product.sku: LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50
dmi.product.version: ThinkPad P50
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
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

** Affects: mutter (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug focal performance ubuntu
-- 
Mouse lags during desktop zoom
https://bugs.launchpad.net/bugs/1877686
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to mutter in Ubuntu.

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

[Desktop-packages] [Bug 1877746] Re: Lock screen not working

[Byron]

No, but I did do a dconf -f, and that at least lets me do it manually
now. It will not lock automatically.

Of course, it reset everything, which as introduced others problems.

Question, what call is exposed to applications to get to determine DPI?

I am having scaling issues in Maple 2017.3 and Maple 2020. If I use
Gnome (default) it works fine.

I am unable to get Wayland up.

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

Title:
  Lock screen not working

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The screen will not automatically lock on the specified timer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 08:54:58 2020
  DistUpgraded: 2020-04-27 21:42:55,589 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-28-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1660 Ti] 
[1458:3fbe]
  InstallationDate: Installed on 2018-07-01 (678 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6998b6fb-9ba7-4ce9-a023-b36dab34d51a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-28 (11 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: X470 AORUS ULTRA GAMING-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X470 AORUS ULTRA GAMING
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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/1877746/+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 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)

[Daniel van Vugt]

Please report the bug to the Mutter developers at:

  https://gitlab.gnome.org/GNOME/mutter/-/issues

and then tell us the new issue ID.

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

Title:
  WL: compositor bug: The compositor tried to use an object from one
  client in a 'wl_pointer.enter' for a different client (resulting in
  Gnome terminal crashing)

Status in gnome-terminal package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in wayland package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to 20.04 and switching to Wayland, Gnome terminal
  occasionally crashes. I interpret the corresponding logs to mean that
  it's actually Wayland that fails to do something in the background,
  which then takes down Gnome terminal:

  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: compositor bug: The 
compositor tried to use an object from one client in a 'wl_pointer.enter' for a 
different client.
  touko 08 11:35:16 saegusa gnome-shell[4227]: WL: error in client 
communication (pid 11639)
  touko 08 11:35:16 saegusa gnome-terminal-[11639]: Error reading events 
from display: Katkennut putki
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-bbca1723-5987-4ccf-98cb-3389ad05641e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: 
vte-spawn-fbe02208-95df-4cf4-bfbe-fffc71d6bc7e.scope: Succeeded.
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Main process exited, code=exited, status=1/FAILURE
  touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: 
Failed with result 'exit-code'.

  I have yet to nail down the precise circumstances, as this has (so
  far) been somewhat rare, having occurred perhaps once or twice a week.

  Since the log mentions pointer, I should perhaps mention that I've set
  `org.gnome.desktop.wm.preferences` > `focus-mode` to `mouse`. Gnome
  terminal also exhibits other misbehaviour wrt. to this, occasionally
  refusing to get focus, or alternatively losing the focus, despite
  mouse cursor being over the terminal window.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xwayland 2:1.20.8-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34
  Uname: Linux 5.4.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  8 15:22:28 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 20.03.00, 5.4.0-29-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms, 20.03.00, 5.4.0-30-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   xtables-addons, 3.8, 5.4.0-29-generic, x86_64: installed
   xtables-addons, 3.8, 5.4.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
  InstallationDate: Installed on 2016-10-13 (1302 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-30-generic 
root=UUID=45ed9550-28e7-4af4-a625-9f31663dce9b ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2

[Desktop-packages] [Bug 1878286] Re: top-bar icons stretched out

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1872026, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1872026
   App icon aspect ratio in the panel is broken

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

Title:
  top-bar icons stretched out

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Some applications, such as Minecraft (Not the launcher, but the game
  itself running under Java) have a stretched-out icon in the app menu.

  I'm guessing this a bug with  `gnome-shell` but I am unsure.

  To reproduce:

  - Start an application, such as Minecraft. Observe the stretched out
  icon in the top-bar app menu.

  Expected behavior:

  - The icon should show next to the application name in gray scale

  Actual behavior:

  - The icon does appear gray scale, but is stretched to match the
  height of the top-bar.

  Ubuntu: 20.04 LTS (Upgraded from 18.04 LTS)

  Gnome: 3.36.1

  
  I attached an image demonstrating the bug.


  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 15:59:58 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-12-25 (503 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-05-07 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878286/+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 1877457] Re: Gnome ignores key presses for minutes after I wake up my laptop

[Daniel van Vugt]

* If you have any gnome-shell extensions installed, please uninstall
those and reboot.

* Is your keyboard wireless?

* Is Terminal the only app affected? I have noticed similar issues in
Terminal myself.

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

Title:
  Gnome ignores key presses for minutes after I wake up my laptop

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  However, clicks are processed without issue. This causes me to wait
  and type until my text went into the terminal, and the cursor square
  on the terminal kept being clear instead of white. Almost a full
  minute after I sign back in does ubuntu start processing and inputting
  my text.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  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
  Date: Thu May  7 17:18:32 2020
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-05-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  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/1877457/+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 1877746] Re: Lock screen not working

[Daniel van Vugt]

Please try disabling Bluetooth and/or other peripherals. Does that allow
the lock screen to work?

I'm reminded of bug 1823076.

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

Title:
  Lock screen not working

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The screen will not automatically lock on the specified timer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 08:54:58 2020
  DistUpgraded: 2020-04-27 21:42:55,589 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-28-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1660 Ti] 
[1458:3fbe]
  InstallationDate: Installed on 2018-07-01 (678 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6998b6fb-9ba7-4ce9-a023-b36dab34d51a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-28 (11 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: X470 AORUS ULTRA GAMING-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X470 AORUS ULTRA GAMING
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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/1877746/+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 1873052] Re: GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps another not scaled cursor mid screen

[Daniel]

Confirming that WaylandEnable=false in /etc/gdm3/custom.conf fixes the
issue (thanks Marco!)

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

Title:
  GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps
  another not scaled cursor mid screen

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  In Progress

Bug description:
  Showing two cursors after login to ubuntu-desktop.

  One cursor moves and is scaled, and one is stationary mid screen and
  not scaled.

  The moving cursor does not appear on screenshots, making it difficult
  to upload a screenshot.

  Previously reported:
  https://gitlab.gnome.org/GNOME/mutter/issues/904
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428

  Package: mutter 3.36.1-3ubuntu1

  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: Wed Apr 15 20:06:53 2020
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+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 1825593] Re: Display scale and layout not remembered when X11 Fractional Scaling is enabled

[Daniel van Vugt]

The cursor issue is bug 1873052.

** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

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

Title:
  Display scale and layout not remembered when X11 Fractional Scaling is
  enabled

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  After upgrading to 19.04, I enabled the experimental 'x11-randr-
  fractional-scaling' setting.  If I set scaling to 125, 150, or 200%,
  the setting is remembered and used the next time I log in.  If I set
  scaling to 100%, however, the next time I log in the scaling switches
  back to 200% automatically.  I only want to use fractional scaling for
  external monitors.

  [ Test case ]

  - Use a multi-monitor setup
  - Enable Fractional scaling under X11 (from display settings)
  - Setup mixed-DPI settings in gnome-control-center
  - Log-out
  - Log-in again
+ Settings should be preserved

  [ Regression potential ]

  It's not possible to set some scaling combinations any more with
  multiple or single monitors.

  - Configuration is not restored at all.

  [ Known issue ]

  Monitor settings won't be preserved disabling fractional scaling or
  enabling it in the wayland session.

  
  -

  Background: This is on a Dell XPS 9360 with a 1920x1080 ~168 DPI
  screen.  Pretty standard configuration.  I have my DisplaySize set to
  294x165 in Xorg.conf, Xft.dpi=168, GTK font scaling factor 1.0.

  I have been unable to find an appropriate combination of settings
  where 168 DPI is respected for accurate font rendering, while at the
  same time not scaling up the rest of the UI to unusable proportions.
  Fractional scaling seems to be the only way to adjust some Gnome UI
  elements.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593/+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 1724557] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()

[Daniel van Vugt]

WHK,

This bug is closed. Please open a new bug for 20.04 by running:

  ubuntu-bug 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/1724557

Title:
  gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Hi all, 
  Originally I was reporting bug 1717170, about session crash after monitor 
disconnect/switch-off/input change on desktop PC and the bug was fixed 
according to bug tracker. But now, after gnome-shell and mutter update, the 
crash goes worse. Now it is not just session kick-out but complete crash. Same 
events can be used to reproduce the crash. This time also crash files was 
created.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 13:52:07 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-09-11 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f475acbac30 :   
movss  0x38(%rdi),%xmm0
   PC (0x7f475acbac30) ok
   source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_logical_monitor_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_wayland_get_geometry_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_sync_state () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1724557/+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 1877850] Re: Super key is logically stuck down

[Daniel van Vugt]

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

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

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

Title:
  Super key is logically stuck down

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  There are shortcuts like 'Super + P' to change the display mode or
  'Super + l' to go to login screen. However, after i upgraded ubuntu
  18.04 to 20.04, if i press P or l or any other character which there
  is a 'super + key' for it, it's does the same thing. It's like the
  super key is always on!

  My keyboard works fine in Unity so it's not a hardware problem.

  GNOME Shell 3.36.1
  Ubuntu 20.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877850/+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 1844808] Re: Can't delete file from desktop by clicking it and hitting delete key

[Daniel van Vugt]

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
   Status: In Progress => Fix Committed

** Tags added: fixed-upstream

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

Title:
  Can't delete file from desktop by clicking it and hitting delete key

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Committed

Bug description:
  Just upgraded to 19.10 today. Previously, in 19.04, I could delete a
  file from the desktop by clicking on it and hitting the delete key.
  That no longer works.

  It's probably relevant that it doesn't appear to be possible to direct
  keyboard focus to the desktop itself any longer. When I click on an
  icon on the desktop and then hit the delete key, the keystroke is sent
  to the window that had focus before I clicked. This appears to be true
  regardless of what window focus mode I'm using (Click to Focus, Focus
  on Hover, or Secondary-Click). Note that the description of Secondary-
  Click, "Window is focused when hovered with the pointer. Hovering the
  desktop removes focus from the previous window," does not appear to be
  true. When I select that focus mode and hover my mouse over the
  desktop I remain focused on the previously focused window.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell-extension-desktop-icons 19.01.4-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 20 11:12:42 2019
  InstallationDate: Installed on 2019-09-12 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1844808/+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 1873052] Re: GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps another not scaled cursor mid screen

[Daniel van Vugt]

Two more duplicates reported of this bug today. So if "Won't Fix" is the
right answer then I think more of us need some time to understand why
that is.

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

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

** Changed in: mutter (Ubuntu)
   Status: Won't Fix => Confirmed

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

Title:
  GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps
  another not scaled cursor mid screen

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  In Progress

Bug description:
  Showing two cursors after login to ubuntu-desktop.

  One cursor moves and is scaled, and one is stationary mid screen and
  not scaled.

  The moving cursor does not appear on screenshots, making it difficult
  to upload a screenshot.

  Previously reported:
  https://gitlab.gnome.org/GNOME/mutter/issues/904
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428

  Package: mutter 3.36.1-3ubuntu1

  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: Wed Apr 15 20:06:53 2020
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+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 1878230] Re: After starting the session the mouse cursor remains on the screen but the mouse works well

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1873052, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1873052
   GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps 
another not scaled cursor mid screen

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

Title:
  After starting the session the mouse cursor remains on the screen but
  the mouse works well

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  nothing to add

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  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: Tue May 12 17:28:32 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-20 (52 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  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/1878230/+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 1878282] Re: Second (dead) mouse pointer on screen after applying fractional scaling

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1873052, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1873052
   GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps 
another not scaled cursor mid screen

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

Title:
  Second (dead) mouse pointer on screen after applying fractional
  scaling

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After setting fractional scaling to 150%, a dead mouse pointer stays
  visible on screen. It is smaller than the functional one (it seems to
  be the size it should have at 100%).

  My configuration:
  - Ubuntu 20.04
  - AMD Radeon 5700 XT using open source drivers
  - Logitech MX Master 3 over Bluetooth
  - 4k LG Monitor

  I saw similar bugs reported for other hardware configs, but they got 
closed/duped (with a request to reopen, so I am doing that here):
  - Nvidia: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428
  - https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1829221

  I see the following work-arounds:
   - Move the mouse to the bottom right edge of the screen. This needs to be 
done on every login however, as the login screen itself is at 100%
   - Install a mainline kernel (I tried 5.6 and didn't see the issue with it) - 
however, that breaks other things

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  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: Tue May 12 12:44:34 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-12-10 (154 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-25 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878282/+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 1873321] Re: The Show Applications button should be clickable in the corner or bottom of the screen

[Treviño]

setting back to verification-needed as yaru is going to be accepted to
focal soon, so no need to mark it as a failure (as when using Ubuntu
dock in the gnome session this it will work properly)

** Tags removed: verification-failed-focal
** Tags added: verification-needed-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/1873321

Title:
  The Show Applications button should be clickable in the corner or
  bottom of the screen

Status in Dash to dock:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Focal:
  Fix Committed
Status in yaru-theme source package in Focal:
  In Progress

Bug description:
  [ Impact ]

  After one of the recent updates, clicking the Show Applications button in the 
very corner of the screen and at its bottom edge doesn't work. This bug applies 
in the cases of left and right positions of the dock and there is no this bug 
in the case of bottom position.
  This issue is very annoying since the mouse pointer runs at the very corner 
of the screen in vast majority of cases as you intent to press the Show Apps 
button.

  [ Test case ]

  - Ensure the dock is positioned on the left side of the screen
  - Move the cursor at the bottom left corner
  - Clicking should open the app grid

  [ Regression potential ]

  Dash has missing padding

  

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 16 20:34:32 2020
  InstallationDate: Installed on 2019-04-25 (356 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425)
  PackageArchitecture: allSourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1873321/+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 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values

[Stephan Pearce]

Any ETA at all, by chance?

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

Title:
  [nvidia] Screen turns off when trying to set some fractional scaling
  values

Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed

Bug description:
  When the nvidia driver is installed, the screen turns off when trying
  to set some fractional scaling values like 150%. And it stays off even
  after rebooting and logging in again.

  And from ssh I can see there's no current mode set anymore (just like
  in bug 1869750):

  $ xrandr
  Screen 0: minimum 8 x 8, current 960 x 600, maximum 16384 x 16384
  DVI-I-0 disconnected (normal left inverted right x axis y axis)
  DVI-I-1 disconnected (normal left inverted right x axis y axis)
  DP-0 disconnected (normal left inverted right x axis y axis)
  DP-1 connected primary (normal left inverted right x axis y axis)
     1920x1200 59.95 +  59.88

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.1-3ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 17 15:51:15 2020
  InstallationDate: Installed on 2020-02-03 (73 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  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/1873403/+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 1878286] Re: top-bar icons stretched out

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => gnome-shell (Ubuntu)

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

Title:
  top-bar icons stretched out

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Some applications, such as Minecraft (Not the launcher, but the game
  itself running under Java) have a stretched-out icon in the app menu.

  I'm guessing this a bug with  `gnome-shell` but I am unsure.

  To reproduce:

  - Start an application, such as Minecraft. Observe the stretched out
  icon in the top-bar app menu.

  Expected behavior:

  - The icon should show next to the application name in gray scale

  Actual behavior:

  - The icon does appear gray scale, but is stretched to match the
  height of the top-bar.

  Ubuntu: 20.04 LTS (Upgraded from 18.04 LTS)

  Gnome: 3.36.1

  
  I attached an image demonstrating the bug.


  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 15:59:58 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-12-25 (503 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-05-07 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878286/+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 1878286] [NEW] top-bar icons stretched out

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Some applications, such as Minecraft (Not the launcher, but the game
itself running under Java) have a stretched-out icon in the app menu.

I'm guessing this a bug with  `gnome-shell` but I am unsure.

To reproduce:

- Start an application, such as Minecraft. Observe the stretched out
icon in the top-bar app menu.

Expected behavior:

- The icon should show next to the application name in gray scale

Actual behavior:

- The icon does appear gray scale, but is stretched to match the height
of the top-bar.

Ubuntu: 20.04 LTS (Upgraded from 18.04 LTS)

Gnome: 3.36.1


I attached an image demonstrating the bug.


ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue May 12 15:59:58 2020
DisplayManager: gdm3
InstallationDate: Installed on 2018-12-25 (503 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-05-07 (5 days ago)

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


** Tags: amd64 apport-bug focal
-- 
top-bar icons stretched out
https://bugs.launchpad.net/bugs/1878286
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 1878285] Re: gnome-control-center crashes on setting up fingerprint

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  gnome-control-center crashes on setting up fingerprint

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

Bug description:
  When I try to setup my fingerprint in gnome-control-center, I first
  have to choose which finger I would use, and when I press the "next"
  button, it crashes : "Unable to access device "Validity VFS0050"
  GDBus.Error:org.freedesktop.DBus.Error.NoReply:Message recipient
  disconnected from message bus without replying".

  
  For information, my fingerprint sensor is :
  - lsusb
  Bus 001 Device 005: ID 138a:0050 Validity Sensors, Inc. Swipe Fingerprint 
Sensor

  
  Ubuntu 20.04

  gnome-control-center:
Installé : 1:3.36.1-1ubuntu5
Candidat : 1:3.36.1-1ubuntu5
   Table de version :
   *** 1:3.36.1-1ubuntu5 500
  500 http://be.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  What I expected to happen, is that everything works and that I can set up my 
finger for unlocking.

  What happened instead : it crashes with the information "Unable to
  access device "Validity VFS0050"
  GDBus.Error:org.freedesktop.DBus.Error.NoReply:Message recipient
  disconnected from message bus without replying".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 22:00:30 2020
  InstallationDate: Installed on 2020-05-11 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   LANGUAGE=fr_BE:fr
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  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/1878285/+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 1878285] Re: gnome-control-center crashes on setting up fingerprint

[Sebastien Bacher]

Could you also add your 'journalctl -b 0' log after getting the issue?

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

Title:
  gnome-control-center crashes on setting up fingerprint

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

Bug description:
  When I try to setup my fingerprint in gnome-control-center, I first
  have to choose which finger I would use, and when I press the "next"
  button, it crashes : "Unable to access device "Validity VFS0050"
  GDBus.Error:org.freedesktop.DBus.Error.NoReply:Message recipient
  disconnected from message bus without replying".

  
  For information, my fingerprint sensor is :
  - lsusb
  Bus 001 Device 005: ID 138a:0050 Validity Sensors, Inc. Swipe Fingerprint 
Sensor

  
  Ubuntu 20.04

  gnome-control-center:
Installé : 1:3.36.1-1ubuntu5
Candidat : 1:3.36.1-1ubuntu5
   Table de version :
   *** 1:3.36.1-1ubuntu5 500
  500 http://be.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  What I expected to happen, is that everything works and that I can set up my 
finger for unlocking.

  What happened instead : it crashes with the information "Unable to
  access device "Validity VFS0050"
  GDBus.Error:org.freedesktop.DBus.Error.NoReply:Message recipient
  disconnected from message bus without replying".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 22:00:30 2020
  InstallationDate: Installed on 2020-05-11 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   LANGUAGE=fr_BE:fr
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  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/1878285/+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 1871543] Re: rtkit fails to start in focal "pthread_create failed: Resource temporarily unavailable"

[RussianNeuroMancer]

I can reliably reproduce this:
1. Inside several aarch64 systemd-machined containers (with PrivateUsers=0 in 
nspawn conf) with focal and running Gnome Shell session (accessed via TigerVNC 
server). Hosts in NanoPC-T4.
2. On one bare metal NanoPC-T4 host with focal, running Gnome Shell Wayland 
session. No container/virtualization stuff, only bare metal.

Symptoms looks the same?

~$ sudo /usr/libexec/rtkit-daemon --stderr
rtkit-daemon[5786]: Successfully called chroot.
rtkit-daemon[5786]: Successfully dropped privileges.
rtkit-daemon[5786]: Successfully limited resources.
rtkit-daemon[5786]: pthread_create failed: Resource temporarily unavailable
rtkit-daemon[5786]: Demoting known real-time threads.
rtkit-daemon[5786]: Demoted 0 threads.

With --no-drop-privileges  it works:
~$ sudo /usr/libexec/rtkit-daemon --stderr --no-drop-privileges 
rtkit-daemon[5781]: Successfully called chroot.
rtkit-daemon[5781]: Successfully limited resources.
rtkit-daemon[5781]: Running.
rtkit-daemon[5781]: Canary thread running.
rtkit-daemon[5781]: Watchdog thread running.

However, in both cases I have to use Armbian kernel. 
For the record, on RPi3B running generic Ubuntu 20.04 aarch64 image (boot via 
UEFI) this issue is not reproducible.

I can help with further debug here, or my issue is different and I have
to go to Armbian forum? In the former case what exactly I need to de to
help debug this?

** Changed in: rtkit (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  rtkit fails to start in focal "pthread_create failed: Resource
  temporarily unavailable"

Status in rtkit package in Ubuntu:
  Confirmed

Bug description:
  I was debugging something else and found rtkit broken on my system.

  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully called 
chroot.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully dropped 
privileges.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Successfully limited 
resources.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Canary thread running.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Exiting canary thread.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoting known real-time 
threads.
  Apr 08 06:09:22 Keschdeichel rtkit-daemon[1726502]: Demoted 0 threads

  That state is reproducible through restarts.
  I haven't looked any further yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  8 07:59:58 2020
  InstallationDate: Installed on 2018-10-12 (543 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-03 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1871543/+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 1878301] [NEW] Focal regression: poor discoverability for search in Ubuntu Software Center

[Dan Dascalescu]

Public bug reported:

I wanted to install a new package. Launched Ubuntu Software and... how
do I search for anything?

Search is a key function. It should be front and center. I couldn't see
it.

That was annoying enough that I wanted to file a bug against it. In the
process I did notice the lens icon in the top left, but seriously - does
that look easily discoverable to anyone? There's usually nothing in that
cornerl so users don't look there, and the contrast is poor, which makes
it very easy to not notice.

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

** Attachment added: "Poorly discoverable Search.png"
   
https://bugs.launchpad.net/bugs/1878301/+attachment/5370677/+files/Poorly%20discoverable%20Search.png

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

Title:
  Focal regression: poor discoverability for search in Ubuntu Software
  Center

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I wanted to install a new package. Launched Ubuntu Software and... how
  do I search for anything?

  Search is a key function. It should be front and center. I couldn't
  see it.

  That was annoying enough that I wanted to file a bug against it. In
  the process I did notice the lens icon in the top left, but seriously
  - does that look easily discoverable to anyone? There's usually
  nothing in that cornerl so users don't look there, and the contrast is
  poor, which makes it very easy to not notice.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878301/+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 1825593] Re: Display scale and layout not remembered when X11 Fractional Scaling is enabled

[Oscar Parada]

Also to add, the cursor from GDM gets stuck after shell loads, now i
have two cursors on the screen, one I control and a second on from gdm
thats just stuck there.

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

Title:
  Display scale and layout not remembered when X11 Fractional Scaling is
  enabled

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  After upgrading to 19.04, I enabled the experimental 'x11-randr-
  fractional-scaling' setting.  If I set scaling to 125, 150, or 200%,
  the setting is remembered and used the next time I log in.  If I set
  scaling to 100%, however, the next time I log in the scaling switches
  back to 200% automatically.  I only want to use fractional scaling for
  external monitors.

  [ Test case ]

  - Use a multi-monitor setup
  - Enable Fractional scaling under X11 (from display settings)
  - Setup mixed-DPI settings in gnome-control-center
  - Log-out
  - Log-in again
+ Settings should be preserved

  [ Regression potential ]

  It's not possible to set some scaling combinations any more with
  multiple or single monitors.

  - Configuration is not restored at all.

  [ Known issue ]

  Monitor settings won't be preserved disabling fractional scaling or
  enabling it in the wayland session.

  
  -

  Background: This is on a Dell XPS 9360 with a 1920x1080 ~168 DPI
  screen.  Pretty standard configuration.  I have my DisplaySize set to
  294x165 in Xorg.conf, Xft.dpi=168, GTK font scaling factor 1.0.

  I have been unable to find an appropriate combination of settings
  where 168 DPI is respected for accurate font rendering, while at the
  same time not scaling up the rest of the UI to unusable proportions.
  Fractional scaling seems to be the only way to adjust some Gnome UI
  elements.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593/+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 1825593] Re: Display scale and layout not remembered when X11 Fractional Scaling is enabled

[Oscar Parada]

Went ahead and enabled proposed updates, updated the machine and
rebooted, fractional scaling and display arrangement was remembered.
When logging into x11 there was a "big" flicker and display fragments
but cleared up once shell loaded. on wayland I dont get the options for
frac. scaling even when its enabled. I think thats a separate issue
though.

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

Title:
  Display scale and layout not remembered when X11 Fractional Scaling is
  enabled

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  After upgrading to 19.04, I enabled the experimental 'x11-randr-
  fractional-scaling' setting.  If I set scaling to 125, 150, or 200%,
  the setting is remembered and used the next time I log in.  If I set
  scaling to 100%, however, the next time I log in the scaling switches
  back to 200% automatically.  I only want to use fractional scaling for
  external monitors.

  [ Test case ]

  - Use a multi-monitor setup
  - Enable Fractional scaling under X11 (from display settings)
  - Setup mixed-DPI settings in gnome-control-center
  - Log-out
  - Log-in again
+ Settings should be preserved

  [ Regression potential ]

  It's not possible to set some scaling combinations any more with
  multiple or single monitors.

  - Configuration is not restored at all.

  [ Known issue ]

  Monitor settings won't be preserved disabling fractional scaling or
  enabling it in the wayland session.

  
  -

  Background: This is on a Dell XPS 9360 with a 1920x1080 ~168 DPI
  screen.  Pretty standard configuration.  I have my DisplaySize set to
  294x165 in Xorg.conf, Xft.dpi=168, GTK font scaling factor 1.0.

  I have been unable to find an appropriate combination of settings
  where 168 DPI is respected for accurate font rendering, while at the
  same time not scaling up the rest of the UI to unusable proportions.
  Fractional scaling seems to be the only way to adjust some Gnome UI
  elements.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593/+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 1873321] Re: The Show Applications button should be clickable in the corner or bottom of the screen

[Alexey Kulik]

I have updated gnome-shell-extension-ubuntu-dock from focal-proposed and it 
doesn't fix the issue for me at the moment. I can guess that this is because 
yaru-theme is not yet updated in focal-proposed.
gnome-shell-extension-ubuntu-dock (68ubuntu1~20.04.1)
yaru-theme-gnome-shell (20.04.6)

** Tags removed: verification-needed-focal
** Tags added: verification-failed-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/1873321

Title:
  The Show Applications button should be clickable in the corner or
  bottom of the screen

Status in Dash to dock:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Focal:
  Fix Committed
Status in yaru-theme source package in Focal:
  In Progress

Bug description:
  [ Impact ]

  After one of the recent updates, clicking the Show Applications button in the 
very corner of the screen and at its bottom edge doesn't work. This bug applies 
in the cases of left and right positions of the dock and there is no this bug 
in the case of bottom position.
  This issue is very annoying since the mouse pointer runs at the very corner 
of the screen in vast majority of cases as you intent to press the Show Apps 
button.

  [ Test case ]

  - Ensure the dock is positioned on the left side of the screen
  - Move the cursor at the bottom left corner
  - Clicking should open the app grid

  [ Regression potential ]

  Dash has missing padding

  

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 16 20:34:32 2020
  InstallationDate: Installed on 2019-04-25 (356 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425)
  PackageArchitecture: allSourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1873321/+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 1878298] [NEW] Authentication window that cannot be closed in the upper left corner

[Uygar Demir Koç]

Public bug reported:

I updated my computer from Ubuntu 19.10 to 20.04. Normally my MySql server is 
not starting at boot. After the update, it started working at boot. Normally I 
was starting this server manually when I need.
Currently, when I put my computer to snooze mode and turn it on again, a dialog 
titled "Authentication Required" opens in the upper left corner of the screen 
(after I login to system). This dialog is not moving in any way, the cancel 
button is not working, it is not reacting when I enter password. I tried enter 
the correct password and wrong passwords, but the result is the same.
In order to close this dialog, I have to either restart the computer or 
re-login.
I tried to find the package name with the command 'ubuntu-bug -w', but it did 
not work. So I haven't got information about package name/version.


DistroRelease: Ubuntu 20.04
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Package: gnome-shell 3.36.1-5ubuntu2
UpgradeStatus: Upgraded to Focal Fossa on 2020-05-11

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


** Tags: focal

** Attachment added: "This is the dialog which I can't close any way."
   
https://bugs.launchpad.net/bugs/1878298/+attachment/5370671/+files/Ekran%20g%C3%B6r%C3%BCnt%C3%BCs%C3%BC%202020-05-12%2023-24-20.png

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

Title:
  Authentication window that cannot be closed in the upper left corner

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I updated my computer from Ubuntu 19.10 to 20.04. Normally my MySql server is 
not starting at boot. After the update, it started working at boot. Normally I 
was starting this server manually when I need.
  Currently, when I put my computer to snooze mode and turn it on again, a 
dialog titled "Authentication Required" opens in the upper left corner of the 
screen (after I login to system). This dialog is not moving in any way, the 
cancel button is not working, it is not reacting when I enter password. I tried 
enter the correct password and wrong passwords, but the result is the same.
  In order to close this dialog, I have to either restart the computer or 
re-login.
  I tried to find the package name with the command 'ubuntu-bug -w', but it did 
not work. So I haven't got information about package name/version.

  
  DistroRelease: Ubuntu 20.04
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Package: gnome-shell 3.36.1-5ubuntu2
  UpgradeStatus: Upgraded to Focal Fossa on 2020-05-11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878298/+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 1867480] Re: scp-dbus-service.py crashed with SIGSEGV in _PyObject_GC_UNTRACK_impl()

[El jinete sin cabeza]

** Tags added: groovy

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

Title:
  scp-dbus-service.py crashed with SIGSEGV in
  _PyObject_GC_UNTRACK_impl()

Status in System Config Printer:
  New
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  not sure what it is I just saw there was n bug - I am new to Linux

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: system-config-printer-common 1.5.12-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sun Mar 15 02:22:17 2020
  ExecutablePath: /usr/share/system-config-printer/scp-dbus-service.py
  InstallationDate: Installed on 2020-03-14 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200312)
  InterpreterPath: /usr/bin/python3.8
  Lpstat: device for L365: 
dnssd://EPSON%20L365%20Series._pdl-datastream._tcp.local/
  MachineType: Universal Exports Group Limited ITL 1403-I3 128
  PackageArchitecture: all
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/L365.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/L365.ppd: Permission denied
  ProcCmdline: /usr/bin/python3 
/usr/share/system-config-printer/scp-dbus-service.py
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=464449a8-03b3-4536-9504-744640ef4b27 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  SegvAnalysis:
   Segfault happened at: 0x506f57:  mov%rcx,(%rdx)
   PC (0x00506f57) ok
   source "%rcx" ok
   destination "(%rdx)" (0x0004) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: system-config-printer
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/python3/dist-packages/cups.cpython-38-x86_64-linux-gnu.so
   __nptl_deallocate_tsd () at pthread_create.c:301
   __nptl_deallocate_tsd () at pthread_create.c:256
   start_thread (arg=) at pthread_create.c:488
  Title: scp-dbus-service.py crashed with SIGSEGV in __nptl_deallocate_tsd()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 0429
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Default
  dmi.board.vendor: Default
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr0429:bd04/29/2019:svnUniversalExportsGroupLimited:pnITL1403-I3128:pvrTBDbyOEM:rvnDefault:rnDefault:rvrType2-BoardVersion:cvnChassisManufacture:ct10:cvrChassisVersion:
  dmi.product.family: Notepad
  dmi.product.name: ITL 1403-I3 128
  dmi.product.sku: ITL 1403-I3 128
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Universal Exports Group Limited
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/system-config-printer/+bug/1867480/+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 1870995] Re: i8042: Warning: Keylock active

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  i8042: Warning: Keylock active

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I see "i8042: Warning: Keylock active" in my dmesg.  Since this is a
  warning, I get, ergo, warned.  Well, about what do I get warned?  I
  feel warned, but I don't know what's wrong and what do I have to avoid
  doing so that I don't get into trouble.  Is there an issue there that
  needs to be solved?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870995/+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 1873321] Re: The Show Applications button should be clickable in the corner or bottom of the screen

[Alexey Kulik]

I confirm that the issue is fixed for me in groovy.
gnome-shell-extension-ubuntu-dock (68ubuntu1)
yaru-theme-gnome-shell (20.10.1)

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

Title:
  The Show Applications button should be clickable in the corner or
  bottom of the screen

Status in Dash to dock:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Focal:
  Fix Committed
Status in yaru-theme source package in Focal:
  In Progress

Bug description:
  [ Impact ]

  After one of the recent updates, clicking the Show Applications button in the 
very corner of the screen and at its bottom edge doesn't work. This bug applies 
in the cases of left and right positions of the dock and there is no this bug 
in the case of bottom position.
  This issue is very annoying since the mouse pointer runs at the very corner 
of the screen in vast majority of cases as you intent to press the Show Apps 
button.

  [ Test case ]

  - Ensure the dock is positioned on the left side of the screen
  - Move the cursor at the bottom left corner
  - Clicking should open the app grid

  [ Regression potential ]

  Dash has missing padding

  

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 16 20:34:32 2020
  InstallationDate: Installed on 2019-04-25 (356 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425)
  PackageArchitecture: allSourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1873321/+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 1877746] Re: Lock screen not working

[Byron]

No crash files for Wayland.


May 12 16:21:46 apollo systemd[2574]: Starting GNOME Shell on Wayland...
May 12 16:21:46 apollo rtkit-daemon[2201]: Successfully made thread 3777373 of 
process 3777373 owned by '1000' high priority at nice level -11.
May 12 16:21:46 apollo rtkit-daemon[2201]: Supervising 4 threads of 2 processes 
of 2 users.
May 12 16:21:46 apollo rtkit-daemon[2201]: Supervising 4 threads of 2 processes 
of 2 users.
May 12 16:21:46 apollo rtkit-daemon[2201]: Successfully made thread 3777422 of 
process 3777373 owned by '1000' RT at priority 5.
May 12 16:21:46 apollo rtkit-daemon[2201]: Supervising 5 threads of 2 processes 
of 2 users.
May 12 16:21:46 apollo gnome-shell[3777410]: Failed to open gpu 
'/dev/dri/card0': Failed to activate universal planes: Operation not permitted
May 12 16:21:46 apollo gnome-shell[3777410]: Failed to create backend: No GPUs 
found
May 12 16:21:46 apollo systemd[2574]: Started Sound Service.
May 12 16:21:46 apollo systemd[2574]: gnome-shell-wayland.service: Failed with 
result 'protocol'.
May 12 16:21:46 apollo systemd[2574]: Failed to start GNOME Shell on Wayland.
May 12 16:21:46 apollo systemd[2574]: Dependency failed for GNOME Shell on 
Wayland.
May 12 16:21:46 apollo systemd[2574]: Dependency failed for GNOME Wayland 
Session.
May 12 16:21:46 apollo systemd[2574]: Dependency failed for GNOME Wayland 
Session (session: ubuntu).
May 12 16:21:46 apollo systemd[2574]: gnome-session-wayland@ubuntu.target: Job 
gnome-session-wayland@ubuntu.target/start failed with result 'dependency'.
May 12 16:21:46 apollo systemd[2574]: gnome-session-wayland.target: Job 
gnome-session-wayland.target/start failed with result 'dependency'.
May 12 16:21:46 apollo systemd[2574]: gnome-shell-wayland.target: Job 
gnome-shell-wayland.target/start failed with result 'dependency'.
May 12 16:21:46 apollo systemd[2574]: gnome-shell-wayland.service: Triggering 
OnFailure= dependencies.
May 12 16:21:46 apollo systemd[2574]: unicast-local-avahi.path: Succeeded.
May 12 16:21:46 apollo systemd[2574]: Stopped Path trigger for Avahi .local 
domain notifications.
May 12 16:21:46 apollo systemd[2574]: update-notifier-release.path: Succeeded.
May 12 16:21:46 apollo systemd[2574]: Stopped Path trigger for new release of 
Ubuntu notifications.
May 12 16:21:46 apollo systemd[2574]: Condition check resulted in Disable GNOME 
Shell extensions after failure being skipped.
May 12 16:21:46 apollo systemd[2574]: Stopped target GNOME Session Manager is 
ready.
May 12 16:21:46 apollo systemd[2574]: Stopping GNOME Session Manager (session: 
ubuntu)...
May 12 16:21:46 apollo systemd[2574]: gnome-session-manager@ubuntu.service: 
Succeeded.
May 12 16:21:46 apollo systemd[2574]: Stopped GNOME Session Manager (session: 
ubuntu).
May 12 16:21:46 apollo systemd[2574]: Stopped target Tasks to be run before 
GNOME Session starts.
May 12 16:21:46 apollo systemd[2574]: Stopped target Session services which 
should run early before the graphical session is brought up.
May 12 16:21:46 apollo systemd[2574]: Reached target Shutdown running GNOME 
Session.
May 12 16:21:46 apollo systemd[2574]: Stopping Start gnome-keyring as SSH 
agent...
May 12 16:21:46 apollo systemd[2574]: Stopping Monitor Session leader for GNOME 
Session...
May 12 16:21:46 apollo systemd[2574]: Starting Restart DBus after GNOME Session 
shutdown...
May 12 16:21:46 apollo systemd[2574]: Stopped target Shutdown running GNOME 
Session.
May 12 16:21:46 apollo systemd[2574]: gnome-keyring-ssh.service: Succeeded.
May 12 16:21:46 apollo systemd[2574]: Stopped Start gnome-keyring as SSH agent.
May 12 16:21:46 apollo systemd[2574]: Reached target Shutdown running GNOME 
Session.
May 12 16:21:46 apollo systemd[2574]: Stopped target Shutdown running GNOME 
Session.
May 12 16:21:46 apollo systemd[2574]: Started Restart DBus after GNOME Session 
shutdown.
May 12 16:21:46 apollo systemd[2574]: gnome-session-monitor.service: Succeeded.
May 12 16:21:46 apollo systemd[2574]: Stopped Monitor Session leader for GNOME 
Session.
May 12 16:21:46 apollo gvfsd[3777335]: A connection to the bus can't be made
May 12 16:21:46 apollo systemd[2574]: Stopping D-Bus User Message Bus...
May 12 16:21:46 apollo systemd[2574]: gnome-session-restart-dbus.service: 
Succeeded.
May 12 16:21:46 apollo systemd[2574]: run-user-1000-gvfs.mount: Succeeded.
May 12 16:21:46 apollo systemd[3776558]: run-user-1000-gvfs.mount: Succeeded.
May 12 16:21:46 apollo systemd[2574]: gvfs-daemon.service: Succeeded.
May 12 16:21:46 apollo systemd[1]: run-user-1000-gvfs.mount: Succeeded.
May 12 16:21:46 apollo systemd[2574]: dbus.service: Succeeded.
May 12 16:21:46 apollo systemd[2574]: Stopped D-Bus User Message Bus.
May 12 16:21:46 apollo systemd[2574]: Started D-Bus User Message Bus.


  *-display 
   description: VGA compatible controller
   product: TU116 [GeForce GTX 1660 Ti]
   vendor: NVIDIA Corporation
   physical id: 0
   bus info: pci@:09:00.0
   version: a1
   

[Desktop-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Jamie Strandboge]

Rather than superseding 1:13.99.1-1ubuntu4 in groovy-proposed, I instead
based the changes in 1:13.99.1-1ubuntu5 on top of 1:13.99.1-1ubuntu4 to
address the CVE that was fixed in https://usn.ubuntu.com/4355-1/.

** Also affects: pulseaudio (Ubuntu Groovy)
   Importance: High
 Assignee: Kai-Heng Feng (kaihengfeng)
   Status: Fix Committed

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
   State: RUNNING
   Name: alsa_input.pci-_00_1f.3.analog-stereo
   Description: Built-in Audio Analog Stereo
   Driver: module-alsa-card.c
   Sample Specification: s16le 2ch 44100Hz
   Channel Map: front-left,front-right
   Owner Module: 7
   Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+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 1877093] Re: [SRU] New stable release 2.34.2

[Brian Murray]

Hello Iain, or anyone else affected,

Accepted at-spi2-atk into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/at-
spi2-atk/2.34.2-0ubuntu2~20.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: at-spi2-atk (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  [SRU] New stable release 2.34.2

Status in at-spi2-atk package in Ubuntu:
  Fix Released
Status in at-spi2-atk source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  GNOME upstream have released a new stable version of at-spi2-atk.

  Changes:

  What's new in at-spi2-atk 2.34.2:

  * Meson: don't hard-code shared_library (!19).

  * Mitigate missing window events at startup.

  * Set C standard to gnu99 (#10).

  * Tests: include sys/time.h (#14).

  [ QA ]

  GNOME has a micro release exception that covers this package.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  So we don't need to verify the fixes explicitly.

  Install the desktop and exercise the screen reader in a variety of
  situations.

  Optionally, but ideally, test the installer too.

  [ Regression potential ]

  If this update is busted the screen reader might not work. This
  changes the C standard too, which should be fine, but make sure to do
  some QA.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1877093/+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 1877746] Re: Lock screen not working

[Byron]

Wayland won't launch.

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

Title:
  Lock screen not working

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The screen will not automatically lock on the specified timer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 08:54:58 2020
  DistUpgraded: 2020-04-27 21:42:55,589 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-28-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1660 Ti] 
[1458:3fbe]
  InstallationDate: Installed on 2018-07-01 (678 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6998b6fb-9ba7-4ce9-a023-b36dab34d51a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-28 (11 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: X470 AORUS ULTRA GAMING-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X470 AORUS ULTRA GAMING
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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/1877746/+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 1878178] Re: EPSON WF 3520 driver problem - PpdFiles: Error

[Seth Arnold]

** Information type changed from Private Security to Public

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

Title:
  EPSON WF 3520 driver problem - PpdFiles: Error

Status in cups package in Ubuntu:
  New

Bug description:
  After an upgrade from Ubuntu 18.04.2 to 19.10 my printer EPSON WF-3520
  won't work. It is recognized on the printer menu but after finding the
  proper driver from EPSON it gives en error in the process. There is a
  ppdfiles:error

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1.1
  ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CupsErrorLog:
   E [12/May/2020:10:44:55 +0300] [Client 16] Returning IPP 
server-error-not-accepting-jobs for Print-Job 
(ipp://localhost/printers/EPSON_WF_3520_Series) from localhost.
   E [12/May/2020:10:45:59 +0300] [Client 22] Returning IPP 
server-error-not-accepting-jobs for Print-Job 
(ipp://localhost/printers/EPSON_WF_3520_Series) from localhost.
   E [12/May/2020:11:23:51 +0300] [Client 16] Returning IPP 
server-error-not-accepting-jobs for Print-Job 
(ipp://localhost/printers/EPSON_WF_3520_Series) from localhost.
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 12:28:09 2020
  InstallationDate: Installed on 2019-12-21 (142 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lpstat: device for EPSON_WF_3520_Series: ///dev/null
  MachineType: Dell Inc. Precision M4600
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_WF_3520_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_WF_3520_Series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=a5d00ddf-aa19-41bf-8139-ac7c317aa04c ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to eoan on 2020-05-04 (7 days ago)
  dmi.bios.date: 09/14/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 08V9YG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd09/14/2018:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1878178/+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 1877102] Re: snap policy module can be unloaded, circumventing audio recording restrictions for snaps

[Jamie Strandboge]

Uploaded
https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu5 to
groovy based on 1:13.99.1-1ubuntu4 from groovy-proposed.

** Changed in: pulseaudio (Ubuntu Groovy)
   Status: In Progress => Fix Committed

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

Title:
  snap policy module can be unloaded, circumventing audio recording
  restrictions for snaps

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  This collates information about a security vulnerability discussed in
  email.  It has been assigned CVE-2020-11931.

  Ubuntu's PulseAudio package is shipped with a custom "module-snap-
  policy" module intended to restrict snap confined clients from
  recording audio unless they have the "audio-record" plug connected.
  However, it does not restrict access to the "PA_COMMAND_UNLOAD_MODULE"
  command.

  This allows a snap that has only plugged "audio-playback" to request
  that PulseAudio unload the security policy module, which in turn makes
  it possible to record audio.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877102/+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 1846718] Re: Pressing and holding the Super key should display numbers [1-9] on the dock icons before pressing any number key

[Michael Mayo]

This issue is one of a several reasons why I have continued using 14 and 16.
It still has not been fixed in 20.   So now I am reinstalling 16.

Is there a reason not to overlay numbers on the relevant icons
immediately then the super key is pressed?  Why wait?

Showing the numbers after the number key is pressed is both useless and
makes Linux look as stupid as Windows. That's an optic worth avoiding,
surely.

When I first encountered this useful feature, in Stupid Windows, where
they make no attempt to show the numbers, I immediately wrote the
numbers on the bezel of the monitor. Which was slightly OK until Windows
shifted the icons.

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

Title:
  Pressing and holding the Super key should display numbers [1-9] on the
  dock icons before pressing any number key

Status in Dash to dock:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Triaged

Bug description:
  Currently, this feature is incomplete, pressing and holding the Super
  key should display numbers [1-9] on the dock icons before actually
  pressing any number key.

  Steps to reproduce the bug:
  1. Press and hold the Super key
  2. Notice that no numbers appear on the dock icons
  3. Press 0 (zero) key while still holding the Super key
  4. Numbers appear on the dock icons for 2 seconds then disappear
  5. Press any number key [1-9] that corresponds to an icon
  6. Numbers appear on the dock icons for 2 seconds then disappear and the app 
launches

  What should happen:
  Numbers should appear on the dock icons while holding the Super key before 
pressing any number key in order to choose which number key to press to launch 
the corresponding app. I believe that's how this feature is supposed to work. 
And that's how it is working in Unity7 in Ubuntu 16.04 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Oct  4 13:21:32 2019
  InstallationDate: Installed on 2018-11-29 (308 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1846718/+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 1868117] Re: [snap] Adapt chromium user agent to avoid "not supported browser"

[Michel-Ekimia]

You are offtopic here , the same problems happens in 18.04 with the repo
version of chromium.

it is just that we try to focus on snap, but we shall backport this use
agent patch on repo version

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

Title:
  [snap] Adapt chromium user agent to avoid "not supported browser"

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  Currently some websites like netflix.com and web.whatsapp.com does not
  recognize chromium Ubuntu as chrome because of the different user
  agent.

  We need to find a way like vivaldi to avoid such problems for casual
  users.

  Current snap chromium UA :

  Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko)
  snap Chromium/80.0.3987.132 Chrome/80.0.3987.132 Safari/537.36

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1868117/+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 1878292] Re: firefox FTBFS on s390x

[Olivier Tilloy]

This is the full compiler invokation used to build the sqlite3 copy:

/usr/bin/clang-10 -std=gnu99 -o sqlite3.o -c  -U_FORTIFY_SOURCE 
-D_FORTIFY_SOURCE=2 -fstack-protector-strong -DNDEBUG=1 -DTRIMMED=1 
-DSQLITE_SECUR
E_DELETE=1 -DSQLITE_THREADSAFE=1 -DSQLITE_CORE=1 -DSQLITE_ENABLE_FTS3=1 
-DSQLITE_ENABLE_UNLOCK_NOTIFY=1 -DSQLITE_ENABLE_DBSTAT_VTAB=1 
-DSQLITE_DEFAULT_PAGE_SIZE=32768 -DSQLITE_MAX_DEFAULT_PAGE_SIZE=32768 
-DSQLITE_OMIT_DEPRECAT
ED -DSQLITE_OMIT_BUILTIN_TEST -DSQLITE_OMIT_DECLTYPE -DSQLITE_TEMP_STORE=2 
'-DSQLITE_TEMP_FILE_PREFIX="mz_etilqs_"' 
-I/home/ubuntu/firefox.focal/third_party/sqlite3/src 
-I/home/ubuntu/firefox.focal/obj-s390x-linux-gnu/third_pa
rty/sqlite3/src -I/home/ubuntu/firefox.focal/obj-s390x-linux-gnu/dist/include 
-I/home/ubuntu/firefox.focal/obj-s390x-linux-gnu/dist/include/nspr 
-I/home/ubuntu/firefox.focal/obj-s390x-linux-gnu/dist/include/nss -fPIC 
-include 
/home/ubuntu/firefox.focal/obj-s390x-linux-gnu/mozilla-config.h 
-DMOZILLA_CLIENT -Qunused-arguments -fno-strict-aliasing -ffunction-sections 
-fdata-sections -fno-math-errno -pthread -fPIC -pipe -g -O2 
-fomit-frame-pointer -fun
wind-tables -Qunused-arguments -Wall -Wbitfield-enum-conversion -Wempty-body 
-Wignored-qualifiers -Wpointer-arith -Wshadow-field-in-constructor-modified 
-Wsign-compare -Wtype-limits -Wunreachable-code -Wunreachable-code-return
 -Wclass-varargs -Wfloat-overflow-conversion -Wfloat-zero-conversion 
-Wloop-analysis -Wstring-conversion -Wtautological-overlap-compare 
-Wtautological-unsigned-enum-zero-compare -Wtautological-unsigned-zero-compare 
-Wno-error=
tautological-type-limit-compare -Wno-error=deprecated-declarations 
-Wno-error=array-bounds -Wno-error=backend-plugin -Wno-error=return-std-move 
-Wno-error=atomic-alignment -Wno-error=deprecated-copy -Wformat 
-Wformat-security 
-Wno-gnu-zero-variadic-macro-arguments -Wno-sign-compare -Wno-type-limits 
-fexperimental-new-pass-manager  -MD -MP -MF .deps/sqlite3.o.pp   
/home/ubuntu/firefox.focal/third_party/sqlite3/src/sqlite3.c


I can reliably reproduce the indefinite hang on s390x. If I replace the 
optimization flag "-O2" by "-O0", the build succeeds almost instantly. "-O1" 
seems to hang too, so it looks like clang on s390x has trouble optimizing the 
sqlite3 code.

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

Title:
  firefox FTBFS on s390x

Status in firefox package in Ubuntu:
  In Progress

Bug description:
  Builds hang when trying to compile the third-party sqlite3 copy,
  during 7+ hours, before being killed. See e.g.
  
https://launchpad.net/ubuntu/+source/firefox/76.0.1+build1-0ubuntu1/+build/19276095:

  436:55.58 make[6]: *** 
[/<>/firefox-76.0.1+build1/config/rules.mk:673: sqlite3.o] Killed
  436:55.59 make[6]: Leaving directory 
'/<>/firefox-76.0.1+build1/obj-s390x-linux-gnu/third_party/sqlite3/src'
  436:55.59 make[5]: *** 
[/<>/firefox-76.0.1+build1/config/recurse.mk:74: 
third_party/sqlite3/src/target-objects] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1878292/+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 1724557] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()

[WHK]

Same problem on Ubuntu 20.04. SegvReason: reading NULL VMA. Only open
nautilus and try mount a external luks disk.

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

Title:
  gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Hi all, 
  Originally I was reporting bug 1717170, about session crash after monitor 
disconnect/switch-off/input change on desktop PC and the bug was fixed 
according to bug tracker. But now, after gnome-shell and mutter update, the 
crash goes worse. Now it is not just session kick-out but complete crash. Same 
events can be used to reproduce the crash. This time also crash files was 
created.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 13:52:07 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-09-11 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f475acbac30 :   
movss  0x38(%rdi),%xmm0
   PC (0x7f475acbac30) ok
   source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_logical_monitor_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_wayland_get_geometry_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_sync_state () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1724557/+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 1878292] [NEW] firefox FTBFS on s390x

[Olivier Tilloy]

Public bug reported:

Builds hang when trying to compile the third-party sqlite3 copy, during
7+ hours, before being killed. See e.g.
https://launchpad.net/ubuntu/+source/firefox/76.0.1+build1-0ubuntu1/+build/19276095:

436:55.58 make[6]: *** 
[/<>/firefox-76.0.1+build1/config/rules.mk:673: sqlite3.o] Killed
436:55.59 make[6]: Leaving directory 
'/<>/firefox-76.0.1+build1/obj-s390x-linux-gnu/third_party/sqlite3/src'
436:55.59 make[5]: *** 
[/<>/firefox-76.0.1+build1/config/recurse.mk:74: 
third_party/sqlite3/src/target-objects] Error 2

** Affects: firefox (Ubuntu)
 Importance: High
 Assignee: Olivier Tilloy (osomon)
 Status: In Progress

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

Title:
  firefox FTBFS on s390x

Status in firefox package in Ubuntu:
  In Progress

Bug description:
  Builds hang when trying to compile the third-party sqlite3 copy,
  during 7+ hours, before being killed. See e.g.
  
https://launchpad.net/ubuntu/+source/firefox/76.0.1+build1-0ubuntu1/+build/19276095:

  436:55.58 make[6]: *** 
[/<>/firefox-76.0.1+build1/config/rules.mk:673: sqlite3.o] Killed
  436:55.59 make[6]: Leaving directory 
'/<>/firefox-76.0.1+build1/obj-s390x-linux-gnu/third_party/sqlite3/src'
  436:55.59 make[5]: *** 
[/<>/firefox-76.0.1+build1/config/recurse.mk:74: 
third_party/sqlite3/src/target-objects] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1878292/+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 1868117] Re: [snap] Adapt chromium user agent to avoid "not supported browser"

[Justin]

Agree. This Chromium snap package is installed, even when users install
chromium-browser from the Ubuntu repositories. Please allow users to
stick to the default open source Ubuntu repositories; don't steer them
away to the proprietary Chrome browser.

Severe usability problems with popular websites caused by a custom user
agent will result in the opposite.

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

Title:
  [snap] Adapt chromium user agent to avoid "not supported browser"

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  Currently some websites like netflix.com and web.whatsapp.com does not
  recognize chromium Ubuntu as chrome because of the different user
  agent.

  We need to find a way like vivaldi to avoid such problems for casual
  users.

  Current snap chromium UA :

  Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko)
  snap Chromium/80.0.3987.132 Chrome/80.0.3987.132 Safari/537.36

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

[Brian Murray]

Hello Bob, or anyone else affected,

Accepted gnome-shell-extension-ubuntu-dock into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-
dock/68ubuntu1~20.04.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-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
Status in gnome-shell-extension-ubuntu-dock source package in Focal:
  Fix Committed

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 1873321] Re: The Show Applications button should be clickable in the corner or bottom of the screen

[Brian Murray]

Hello Doctor, or anyone else affected,

Accepted gnome-shell-extension-ubuntu-dock into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-
dock/68ubuntu1~20.04.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Focal)
   Status: Fix Released => Fix Committed

** Tags added: verification-needed verification-needed-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/1873321

Title:
  The Show Applications button should be clickable in the corner or
  bottom of the screen

Status in Dash to dock:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Focal:
  Fix Committed
Status in yaru-theme source package in Focal:
  In Progress

Bug description:
  [ Impact ]

  After one of the recent updates, clicking the Show Applications button in the 
very corner of the screen and at its bottom edge doesn't work. This bug applies 
in the cases of left and right positions of the dock and there is no this bug 
in the case of bottom position.
  This issue is very annoying since the mouse pointer runs at the very corner 
of the screen in vast majority of cases as you intent to press the Show Apps 
button.

  [ Test case ]

  - Ensure the dock is positioned on the left side of the screen
  - Move the cursor at the bottom left corner
  - Clicking should open the app grid

  [ Regression potential ]

  Dash has missing padding

  

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 16 20:34:32 2020
  InstallationDate: Installed on 2019-04-25 (356 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425)
  PackageArchitecture: allSourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1873321/+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 1793496] Re: scaling changes when closing/re-opening the lid

[Brian Murray]

Hello Matthias, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.2-1ubuntu1~20.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mutter (Ubuntu Focal)
   Status: Fix Released => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  scaling changes when closing/re-opening the lid

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in mutter source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  scaling changes when closing/re-opening the lid. Seen in bionic.

  My scaling is set to 100%, but the laptop is considered highdpi by
  mutter, and during suspend/resume it changes back to default ignoring
  settings.

  $ xprop -spy -root RESOURCE_MANAGER
  [...]
  RESOURCE_MANAGER(STRING) = 
"*customization:\t-color\nXft.dpi:\t192\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t48\nXcursor.theme:\tDMZ-White\n"
  RESOURCE_MANAGER(STRING) = 
"*customization:\t-color\nXft.dpi:\t96\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t24\nXcursor.theme:\tDMZ-White\n"

  xrandr
  Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
  eDP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y 
axis) 309mm x 174mm
 2560x1440 60.00*+  59.9959.9959.9659.95

  [ Test case ]

  In a laptop with HiDPI screen, force the scaling to 1:

  Run this and close the lid:
   xprop -spy -root RESOURCE_MANAGER

  Once reopened the value should not change and if it does the
  `Xft.dpi:\t96` value should stay constant, and not change to 192.

  [ Regression potential ]

  Wrong resolution is set for the laptop lid

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1793496/+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 1825593] Re: Display scale and layout not remembered when X11 Fractional Scaling is enabled

[Brian Murray]

Hello hackel, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.2-1ubuntu1~20.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mutter (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  Display scale and layout not remembered when X11 Fractional Scaling is
  enabled

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  After upgrading to 19.04, I enabled the experimental 'x11-randr-
  fractional-scaling' setting.  If I set scaling to 125, 150, or 200%,
  the setting is remembered and used the next time I log in.  If I set
  scaling to 100%, however, the next time I log in the scaling switches
  back to 200% automatically.  I only want to use fractional scaling for
  external monitors.

  [ Test case ]

  - Use a multi-monitor setup
  - Enable Fractional scaling under X11 (from display settings)
  - Setup mixed-DPI settings in gnome-control-center
  - Log-out
  - Log-in again
+ Settings should be preserved

  [ Regression potential ]

  It's not possible to set some scaling combinations any more with
  multiple or single monitors.

  - Configuration is not restored at all.

  [ Known issue ]

  Monitor settings won't be preserved disabling fractional scaling or
  enabling it in the wayland session.

  
  -

  Background: This is on a Dell XPS 9360 with a 1920x1080 ~168 DPI
  screen.  Pretty standard configuration.  I have my DisplaySize set to
  294x165 in Xorg.conf, Xft.dpi=168, GTK font scaling factor 1.0.

  I have been unable to find an appropriate combination of settings
  where 168 DPI is respected for accurate font rendering, while at the
  same time not scaling up the rest of the UI to unusable proportions.
  Fractional scaling seems to be the only way to adjust some Gnome UI
  elements.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593/+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 1873942] Re: [wayland] gnome-screenshot takes a screenshot of the wrong screen

[Brian Murray]

Hello Guillaume, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.2-1ubuntu1~20.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags added: verification-needed verification-needed-focal

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

Title:
  [wayland] gnome-screenshot takes a screenshot of the wrong screen

Status in GNOME Shell:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  I have a dual monitor setup, with the external monitor defined as the 
"primary" one (and the laptop one secondary).
  When using the Shift +  PrtScr shortcut and choosing an area on the external 
monitor, the screenshot saved in ~/Pictures shows this area but on the _laptop_ 
screen.
  (Choosing an area on the laptop screen works OK.)

  I use the vanilla Gnome session (with Wayland), installed with apt.

  [ Impact ]

  gnome-screenshot takes a screenshot of the wrong screen

  [ Test case ]

  In dual monitor setup, use Shift+PrtScr to take a screenshot in an
  area in the external monitor.

  The saved area should respect the one you selected

  [ Regression potential ]

  Screenshot or screencasting may have not espected behavior

  
  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Apr 20 20:58:46 2020
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: focalDistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-24-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-25-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
     Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:16e0]
  InstallationDate: Installed on 2020-04-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  Package: wayland (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Tags:  focal wayland-session ubuntu
  Uname: Linux 5.4.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUploa

[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93)

[Brian Murray]

Hello Adam, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.2-1ubuntu1~20.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags added: verification-needed verification-needed-focal

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

Title:
  [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see
  comment 93)

Status in LibreOffice:
  Won't Fix
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Triaged
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  [ Test case ]

  1. Use use libreoffice writer/calc
  2. Copy text around
  3. Paste it and ensure it always work

  [ Regression potential ]

  Copy/paste won't work as expected, for non-text types

  -

  
  I use LibreOffice Writer a lot, and I now see this problem very often, i.e. 
many times every day.

  There is some discussion of the problem here:

     https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

     https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+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 1878245] Re: Cannot use PRIME render offloading on AMD CPUs

[Ubuntu Foundations Team Bug Bot]

The attachment "prime-offloading-with-amd.patch" seems to be a patch.
If it isn't, please remove the "patch" flag from the attachment, remove
the "patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Cannot use PRIME render offloading on AMD CPUs

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  Release: Ubuntu 20.04
  Package version: 1:0.8.1

  gpu-manager will only configure X for PRIME render offloading when
  using an Intel CPU with integrated graphics. AMD CPUs also have
  integrated graphics that can support GPU offloading.

  Upstream report: https://github.com/tseliot/ubuntu-drivers-
  common/issues/39

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

[Brian Murray]

Hello Danial, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.2-1ubuntu1~20.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mutter (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  super key does not work with secondary keyboard layout

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  When keyboard layout is set in a secondary layout (i.e. Persian)
  pressing Super does not open Activities overview. It just works when
  the input is set on English.

  [ Test case ]

  - Enable a secondary keyboard layout
  - Switch to this layout
  - Hit super
  - Overview should open

  [ Regression potential ]

  Modifiers may no work well in shell context

  ProblemType: BugDistroRelease: 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-3ubuntu1SourcePackage: 
gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+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 1874207] Re: Compiler warnings in x11-Add-support-for-fractional-scaling-using-Randr.patch

[Brian Murray]

Hello Daniel, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.2-1ubuntu1~20.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mutter (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  Compiler warnings in x11-Add-support-for-fractional-scaling-using-
  Randr.patch

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  There are a couple of compiler warnings apparently caused by x11-Add-
  support-for-fractional-scaling-using-Randr.patch:

  
  [427/1390] Compiling C object 
'src/25a...ends_meta-monitor-config-manager.c.o'.
  ../src/backends/meta-monitor-config-manager.c: In function 
‘assign_monitor_crtc’:
  ../src/backends/meta-monitor-config-manager.c:226:3: warning: enumeration 
value ‘META_LOGICAL_MONITOR_LAYOUT_MODE_GLOBAL_UI_LOGICAL’ not handled in 
switch [-Wswitch]
    226 |   switch (data->config->layout_mode)
    |   ^~
  [471/1390] Compiling C object 
'src/25a..._x11_meta-monitor-manager-xrandr.c.o'.
  ../src/backends/x11/meta-monitor-manager-xrandr.c: In function 
‘meta_monitor_manager_xrandr_get_capabilities’:
  ../src/backends/x11/meta-monitor-manager-xrandr.c:1169:18: warning: 
‘capabilities’ may be used uninitialized in this function 
[-Wmaybe-uninitialized]
   1169 | capabilities |= META_MONITOR_MANAGER_CAPABILITY_TILING;
    | ~^

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1874207/+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 1877209] Re: Update to 3.36.2 and SRU it

[Brian Murray]

Hello Marco, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.2-1ubuntu1~20.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mutter (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  Update to 3.36.2 and SRU it

Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.2

  [ Test case ]

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  GNOME Shell and its components should continue working

  [ Regression potential ]

  There have been quite lots of changes in monitors and clipboard
  management, so ensure there are no problems with those.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1877209/+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 1874818] Re: Please pull Mutter/Wayland fixes for desktop freeze

[Brian Murray]

Hello Ppaalanen, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.2-1ubuntu1~20.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags added: verification-needed verification-needed-focal

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

Title:
  Please pull Mutter/Wayland fixes for desktop freeze

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Fix Committed
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  I have upstreamed a GNOME/Wayland desktop freeze fix in:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1209 (master)
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1215 (3.36 branch)
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1216 (3.34 branch)

  [ Impact ]

  I diagnosed the freeze on Mutter 3.34 Ubuntu 19.10 flavour first, with
  DisplayLink hardware. Any DRM driver that may temporarily fail
  drmModePageFlip() calls might trigger this.

  [ Test case ]

  I triggered the freeze particularly by trying to make a DisplayLink
  output the only active output via GNOME display settings. Other
  triggers are possible.

  This fix may help with
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853357 but I
  don't know for sure.

  [ Regression potential ]

  Higher page flips could happen using native backend (wayland)

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