[Desktop-packages] [Bug 1870184] Re: Snap store not showing ubuntu repository apt apps inthe store

[corrado venturini]

Two new installations on different hardware from Ubuntu 20.04 LTS "Focal Fossa" 
- Beta amd64 (20200409)
After install of gnome-software, update+upgrade, snap refresh and various 
reboot snap-store still ignores apt apps.
snaps are not integrated with the system, ubuntu-bug does not work so users 
can't give a good feedback to developers.

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

Title:
  Snap store not showing ubuntu repository apt apps inthe store

Status in snap-store:
  Confirmed
Status in gnome-desktop package in Ubuntu:
  Invalid
Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  OS : Ubuntu 20.04 (20200401)
  Problem : repository (apt) apps are not showing

  Problem Simulation:
  Install ubuntu 20.04 current daily build > open Snap Store> Search 
gnome tweak (or anyother apt apps) > no results

  Expected Solution:
  The Snap store should show repository apps or the gnome software 
should have installed by default.
  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-store/+bug/1870184/+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 1867763] Re: gnome-shell crashed with SIGABRT: assertion failure in st_bin_destroy: assertion failed: (priv->child == NULL)

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-shell crashed with SIGABRT: assertion failure in st_bin_destroy:
  assertion failed: (priv->child == NULL)

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

Bug description:
  https://errors.ubuntu.com/problem/d24a5ac63e9b00cde36f6c46ecbcc5b20442be90
  https://errors.ubuntu.com/problem/fcc5c581fc0a8c2f8f68314fa383690423a3dc02

  ---

  I do not know what is happened, just a reporter appeared. But 10
  minutes ago when I came to my computer after 5 minutes, it was
  restarted. It should not be restarted, just should be sleep or locked.
  However I do not know even this issue related with this report or not.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 17 13:32:09 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-03-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200312)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867763/+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 1872330] Re: Cannot open gear icon of an input source in Region & Language

[Launchpad Bug Tracker]

This bug was fixed in the package ibus-unikey - 0.6.1-1.1ubuntu1

---
ibus-unikey (0.6.1-1.1ubuntu1) focal; urgency=medium

  * debian/ibus-setup-Unikey.desktop, debian/rules:
- Install .desktop file for setup (LP: #1872330)

 -- Gunnar Hjalmarsson   Sun, 12 Apr 2020 23:54:00
+0200

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

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

Title:
  Cannot open gear icon of an input source in Region & Language

Status in ibus-unikey package in Ubuntu:
  Fix Released

Bug description:
  Using the Ubuntu 20.04 Focal Fossa Beta version.

  Using the gnome-control-center version 1:3.36.1-1ubuntu4

  What should happen: Clicking on the gear icon of an input source in
  the Input Sources section in Region & Language should open the
  respective settings menu.

  What happened: Clicking on the gear icon does nothing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-unikey/+bug/1872330/+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 1855546] Re: Desktop freezes a while than logs out

[Launchpad Bug Tracker]

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

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

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

Title:
  Desktop freezes a while than logs out

Status in gnome-shell package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  In the last few months I often experience the following symptom. The
  Ubuntu desktop freezes for 2-3 minutes, then automatically logs out
  without any user interaction.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laca   2067 F pulseaudio
   /dev/snd/controlC2:  laca   2067 F pulseaudio
   /dev/snd/controlC1:  laca   2067 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 16:01:15 2019
  HibernationDevice: RESUME=UUID=9b9553b2-3060-4b74-9890-16e50d306f43
  InstallationDate: Installed on 2018-08-25 (469 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Inspiron 5548
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-72-generic N/A
   linux-backports-modules-4.15.0-72-generic  N/A
   linux-firmware 1.173.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 079JDM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A02
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/04/2014:svnDellInc.:pnInspiron5548:pvrA02:rvnDellInc.:rn079JDM:rvrA00:cvnDellInc.:ct8:cvrA02:
  dmi.product.name: Inspiron 5548
  dmi.product.version: A02
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855546/+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 1855546] Re: Desktop freezes a while than logs out

[Launchpad Bug Tracker]

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

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

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

Title:
  Desktop freezes a while than logs out

Status in gnome-shell package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  In the last few months I often experience the following symptom. The
  Ubuntu desktop freezes for 2-3 minutes, then automatically logs out
  without any user interaction.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laca   2067 F pulseaudio
   /dev/snd/controlC2:  laca   2067 F pulseaudio
   /dev/snd/controlC1:  laca   2067 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 16:01:15 2019
  HibernationDevice: RESUME=UUID=9b9553b2-3060-4b74-9890-16e50d306f43
  InstallationDate: Installed on 2018-08-25 (469 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Inspiron 5548
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-72-generic N/A
   linux-backports-modules-4.15.0-72-generic  N/A
   linux-firmware 1.173.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 079JDM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A02
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/04/2014:svnDellInc.:pnInspiron5548:pvrA02:rvnDellInc.:rn079JDM:rvrA00:cvnDellInc.:ct8:cvrA02:
  dmi.product.name: Inspiron 5548
  dmi.product.version: A02
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855546/+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 1862792] Re: gnome-shell always crash after boot

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-shell always crash after boot

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  gnome-shell always crash after boot with an UnreportableReason. This is in a 
Wayland session. 
  There are no stability issues after boot. 

  I get this information in the terminal after the command ubuntu-bug

  p-i@pi-asus-b450f-gaming:~$ ubuntu-bug gnome-shell
  p-i@pi-asus-b450f-gaming:~$ 
[8196:8196:0211/164342.764494:ERROR:edid_parser.cc(102)] Too short EDID data: 
manufacturer id
  [8232:8232:0211/164342.881085:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.
  [8232:8232:0211/164344.007722:ERROR:gl_surface_presentation_helper.cc(259)] 
GetVSyncParametersIfAvailable() failed for 1 times!

  ERROR:gl goes from 1 to 19.

  In Settings the Display is named Microstep 27"
  The problem might be hardware related:
  Mobo: ASUSTeK model: ROG STRIX B450-F GAMING
  GPU: AMD Navi 10 Radeon RX 5700

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 11 16:43:08 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-02-08 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200207.2)
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  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/1862792/+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 1872376] Re: Application menu displays on right hand side of screen

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Application menu displays on right hand side of screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Unsure if this bug should fall under xorg or Gnome.

  
  When I click the "Show Applications" button, all the applications are 
displayed over on the right hand side of the primary screen. The dots to 
indicate which application page you're viewing appear over on the second 
monitor.

  This only happens when using a second display.

  Running Ubuntu 19.10.

  Link to screenshot: https://i.stack.imgur.com/dkxgy.jpg

  Output of ls -al ~/.local/share/gnome-shell/extensions:

  total 64
  drwxr-xr-x 5 luke luke  4096 Apr 12 16:32 .
  drwx-- 3 luke luke  4096 Apr 12 16:29 ..
  -rw-r--r-- 1 luke luke  4014 Apr  5 21:38 convenience.js
  -rw-r--r-- 1 luke luke 11442 Apr  5 21:38 extension.js
  drwxr-xr-x 2 luke luke  4096 Apr  5 21:38 icons
  -rw-r--r-- 1 luke luke  4211 Apr  5 21:38 indicator.js
  drwxr-xr-x 8 luke luke  4096 Apr  5 21:38 locale
  -rw-r--r-- 1 luke luke   388 Apr  5 21:38 metadata.json
  -rw-r--r-- 1 luke luke  9559 Apr  5 21:38 prefs.js
  drwxr-xr-x 2 luke luke  4096 Apr  5 21:38 schemas
  -rw-r--r-- 1 luke luke   451 Apr  5 21:38 stylesheet.css
  Output of ls -al /usr/share/gnome-shell/extensions:

  total 20
  drwxr-xr-x 5 root root 4096 Oct 17 13:27 .
  drwxr-xr-x 6 root root 4096 Mar 28 13:33 ..
  drwxr-xr-x 2 root root 4096 Oct 17 13:27 desktop-icons@csoriano
  drwxr-xr-x 3 root root 4096 Oct 17 13:27 ubuntu-appindicat...@ubuntu.com
  drwxr-xr-x 3 root root 4096 Mar 17 13:39 ubuntu-d...@ubuntu.com
  I've also tried resetting Gnome with dconf reset -f /org/gnome/

  Issue persists after a reset.

  Cheers!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 13 01:17:10 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:506a]
  InstallationDate: Installed on 2020-01-28 (75 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20LSCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET59W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LSCTO1WW
  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:bvrR0QET59W(1.36):bd10/16/2019:svnLENOVO:pn20LSCTO1WW:pvrThinkPadL480:rvnLENOVO:rn20LSCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L480
  dmi.product.name: 20LSCTO1WW
  dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
  dmi.product.version: ThinkPad L480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/xorg/+bug/1872376/+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 1872376] [NEW] Application menu displays on right hand side of screen

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Unsure if this bug should fall under xorg or Gnome.


When I click the "Show Applications" button, all the applications are displayed 
over on the right hand side of the primary screen. The dots to indicate which 
application page you're viewing appear over on the second monitor.

This only happens when using a second display.

Running Ubuntu 19.10.

Link to screenshot: https://i.stack.imgur.com/dkxgy.jpg

Output of ls -al ~/.local/share/gnome-shell/extensions:

total 64
drwxr-xr-x 5 luke luke  4096 Apr 12 16:32 .
drwx-- 3 luke luke  4096 Apr 12 16:29 ..
-rw-r--r-- 1 luke luke  4014 Apr  5 21:38 convenience.js
-rw-r--r-- 1 luke luke 11442 Apr  5 21:38 extension.js
drwxr-xr-x 2 luke luke  4096 Apr  5 21:38 icons
-rw-r--r-- 1 luke luke  4211 Apr  5 21:38 indicator.js
drwxr-xr-x 8 luke luke  4096 Apr  5 21:38 locale
-rw-r--r-- 1 luke luke   388 Apr  5 21:38 metadata.json
-rw-r--r-- 1 luke luke  9559 Apr  5 21:38 prefs.js
drwxr-xr-x 2 luke luke  4096 Apr  5 21:38 schemas
-rw-r--r-- 1 luke luke   451 Apr  5 21:38 stylesheet.css
Output of ls -al /usr/share/gnome-shell/extensions:

total 20
drwxr-xr-x 5 root root 4096 Oct 17 13:27 .
drwxr-xr-x 6 root root 4096 Mar 28 13:33 ..
drwxr-xr-x 2 root root 4096 Oct 17 13:27 desktop-icons@csoriano
drwxr-xr-x 3 root root 4096 Oct 17 13:27 ubuntu-appindicat...@ubuntu.com
drwxr-xr-x 3 root root 4096 Mar 17 13:39 ubuntu-d...@ubuntu.com
I've also tried resetting Gnome with dconf reset -f /org/gnome/

Issue persists after a reset.

Cheers!

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 13 01:17:10 2020
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics 620 [17aa:506a]
InstallationDate: Installed on 2020-01-28 (75 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 20LSCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/16/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET59W (1.36 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LSCTO1WW
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:bvrR0QET59W(1.36):bd10/16/2019:svnLENOVO:pn20LSCTO1WW:pvrThinkPadL480:rvnLENOVO:rn20LSCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LSCTO1WW
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug eoan ubuntu
-- 
Application menu displays on right hand side of screen
https://bugs.launchpad.net/bugs/1872376
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg 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 1872393] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1858414, so 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.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1872393/+attachment/5353006/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1872393/+attachment/5353008/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1872393/+attachment/5353012/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1872393/+attachment/5353013/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1872393/+attachment/5353014/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1872393/+attachment/5353016/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1872393/+attachment/5353017/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1858414
   gnome-shell crashed with signal 5 in 
ObjectInstance::disassociate_js_gobject()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  it just crashed, now I'm filing a report.  Not sure what happened, but
  I've been adding programs with apt.

  ProblemType: Crash
  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: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 22:35:47 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-04-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872393/+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 1870637] Re: Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 300000KHz

[Paul Berkx]

I just downloaded a daily build (12-04-2020)
And am very happy to report 4K 60 is working flawless on this version on the 
nvidia driver.

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

Title:
  Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 30KHz

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

Bug description:
  When i do get it to work, on reboot it'll be back to fullhd.
  this happens on nvidia 440, 435 and 390.

  On X.Org X server it does work.

  Graphics card: nVidia GT1030
  Amp: Onkyo TX-NR646

  On 19.10 there are no problems.
  A couple of weeks ago i tested a daily build and there were no troubles also, 
so this is new.

  My favourite setting: 3840x2160 200% 60hz.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..10.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:10: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  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 01:02:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:2476]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=99bd1cce-b30c-44fb-8ead-90317474c33f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 (MS-7B84)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  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.7-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+git20190815-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-435/+bug/1870637/+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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

[Bug Watch Updater]

** Changed in: pango1.0 (Debian)
   Status: Unknown => New

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  Fix Released
Status in pango1.0 package in Debian:
  New

Bug description:
  I just updated my machine, and when I did libpango1.0-0 was removed.
  This removed minecraft-launcher - the (very) popular launcher for
  Minecraft Java edition.

  I have reported this upstream, in case they can update their package
  https://bugs.mojang.com/browse/MCL-13512

  I am filing this bug so we can track it internally. I personally think
  this shouldn't have been done this late in the cycle, but there may
  well have been good reasons for it.

  As a result of the change though, it's now not possible to install
  Minecraft on Ubuntu 20.04.

  $ sudo apt install ./Minecraft\(1\).deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1872390] [NEW] 193% CPU usage while using webex with chromium

[Chia-Hao Hsu]

Public bug reported:

193% CPU usage while using webex with chromium. The process seems
associated with audio. When the process was killed. The voice was muted.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: chromium-browser 80.0.3987.163-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
DRM.card0-HDMI-A-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: 
AP///wAEaeIgAQEBASAbAQOAKxh46tr1pFVSnycOUFS/7gCBwAEBAQEBAQEBAQEBAQEBZiFWqlEAHjBGjzMAsuwQAAAe/QAyTB5TDgAKICAgICAg/ABWWDIwNwogICAgICAg/wBIOExNUVMwMTg1ODUKAbQCAxthIwkHB4MBAABnAwwAIACALUOQhALiAA+MCtCKIOAtEBA+lgCgWgAAKQ==
 modes: 1366x768 1920x1080 1920x1080 1280x720 1280x720 1280x720 1024x768 
1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x480 720x480 
720x480 640x480 640x480 640x480 640x480 640x480 720x400
DRM.card0-eDP-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: 
AP///wAGr+1hAAAaAQSlIhN4Alklk1hZkykmUFQBAQEBAQEBAQEBAQEBAQEBeDeAtHA4LkBsMKoAWMEQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTU2SEFOMDYuMSAKANo=
 modes: 1920x1080
Date: Mon Apr 13 11:01:39 2020
Desktop-Session:
 'gnome'
 '/etc/xdg/xdg-gnome:/etc/xdg'
 '/usr/share/gnome:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
DetectedPlugins:
 
Env:
 'None'
 'None'
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2018-04-29 (714 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
Load-Avg-1min: 6.54
Load-Processes-Running-Percent:   0.3%
MachineType: ASUSTeK COMPUTER INC. FX503VD
ProcEnviron:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=8d5334b6-ef1c-42d3-880c-f5d4c937cba2 ro quiet splash 
tpm_tis.interrupts=0 acpi_osi=Linux i915.preliminary_hw_support=1 idle=nomwait 
mds=full,nosmt quiet splash tpm_tis.interrupts=0 acpi_osi=Linux 
acpi_backlight=vendor i915.preliminary_hw_support=1 idle=nomwait mds=full,nosmt 
vt.handoff=1
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to bionic on 2019-12-20 (114 days ago)
dmi.bios.date: 04/29/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FX503VD.308
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: FX503VD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX503VD.308:bd04/29/2019:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: TUF Gaming
dmi.product.name: FX503VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
modified.conffile..etc.default.chromium-browser: [deleted]

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  193% CPU usage while using webex with chromium

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  193% CPU usage while using webex with chromium. The process seems
  associated with audio. When the process was killed. The voice was
  muted.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 80.0.3987.163-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEaeIgAQEBASAbAQOAKxh46tr1pFVSnycOUFS/7gCBwAEBAQEBAQEBAQEBAQEBZiFWqlEAHjBGjzMAsuwQAAAe/QAyTB5TDgAKICAgICAg/ABWWDIwNwogICAgICAg/wBIOExNUVMwMTg1ODUKAbQCAxthIwkHB4MBAABnAwwAIACALUOQhALiAA+MCtCKIOAtEBA+lgCgWgAAKQ==
   modes: 1366x768 1920x1080 1920x1080 1280x720 1280x720 1280x720 1024x768 
1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x480 720x480 
720x480 640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGr+1hAAAaAQSlIhN4Alklk1hZkykmUFQBAQEBAQEBAQEBAQEBAQEBeDeAtHA4LkBsMKoAWMEQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTU2SEFOMDYuMSAKANo=
   modes: 1920x1080
  Date: Mon Apr 13 11:01:39 2020
  Desktop-Session:
   'gnome'
   '/etc/xdg/xdg-gnome:/etc/xdg'
   

[Desktop-packages] [Bug 1872377] [NEW] No menus in Unity after upgrading to 20.04

[Alistair Cunningham]

Public bug reported:

In Ubuntu 19.10, the Firefox menus appeared as normal. After upgrading
to Ubuntu 20.04 beta, with Firefox 75.0+build3-0ubuntu1, the Firefox
menus no longer appear either on the window or the title bar. This
happens both when the window is maximised and when it isn't.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 75.0+build3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  alistair   2490 F pulseaudio
BuildID: 20200403170909
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: Unity:Unity7:ubuntu
Date: Mon Apr 13 09:55:56 2020
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
 dns-search integrics.com
IncompatibleExtensions:
 English (GB) Language Pack - langpack-en...@firefox.mozilla.org
 English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
 Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2017-08-16 (970 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
IpRoute:
 default via 10.12.0.1 dev enp0s31f6 proto dhcp metric 100 
 10.12.0.0/21 dev enp0s31f6 proto kernel scope link src 10.12.3.219 metric 100 
 169.254.0.0/16 dev enp0s31f6 scope link metric 1000
MostRecentCrashID: bp-3d145359-2f62-4b35-a046-86be50191125
PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=75.0/20200403170909 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to focal on 2020-04-12 (0 days ago)
dmi.bios.date: 11/29/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1WET57W (1.36 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET57W(1.36):bd11/29/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470s
dmi.product.name: 20HFCTO1WW
dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
dmi.product.version: ThinkPad T470s
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

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

Title:
  No menus in Unity after upgrading to 20.04

Status in firefox package in Ubuntu:
  New

Bug description:
  In Ubuntu 19.10, the Firefox menus appeared as normal. After upgrading
  to Ubuntu 20.04 beta, with Firefox 75.0+build3-0ubuntu1, the Firefox
  menus no longer appear either on the window or the title bar. This
  happens both when the window is maximised and when it isn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 75.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   2490 F pulseaudio
  BuildID: 20200403170909
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Apr 13 09:55:56 2020
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   dns-search integrics.com
  IncompatibleExtensions:
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2017-08-16 (970 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 10.12.0.1 dev enp0s31f6 proto dhcp metric 100 
   10.12.0.0/21 dev enp0s31f6 proto kernel scope link src 10.12.3.219 metric 
100 
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000
  MostRecentCrashID: bp-3d145359-2f62-4b35-a046-86be50191125
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=75.0/20200403170909 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to focal on 2020-04-12 (0 days ago)
  

[Desktop-packages] [Bug 1853007] Re: nsemail and nscopy files left in /tmp

[Alistair Cunningham]

This bug still happens on Ubuntu 20.04 beta running Thunderbird
1:68.7.0+build1-0ubuntu1.

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

Title:
  nsemail and nscopy files left in /tmp

Status in Mozilla Thunderbird:
  New
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  thunderbird leaves nsemail and nscopy files in /tmp:

  # ls -l /tmp/ns*
  -rw--- 1 alistair alistair   5522 Nov 18 08:42 /tmp/nscopy-1.tmp
  -rw--- 1 alistair alistair   8883 Nov 18 08:43 /tmp/nscopy-2.tmp
  -rw--- 1 alistair alistair   8311 Nov 18 08:49 /tmp/nscopy-3.tmp
  -rw--- 1 alistair alistair   3455 Nov 18 08:38 /tmp/nscopy.tmp
  -rw--- 1 alistair alistair  25790 Nov 15 09:26 /tmp/nsemail-10.eml
  -rw--- 1 alistair alistair   5840 Nov 15 09:28 /tmp/nsemail-11.eml
  -rw--- 1 alistair alistair  25442 Nov 15 09:29 /tmp/nsemail-12.eml
  -rw--- 1 alistair alistair   2838 Nov 15 09:29 /tmp/nsemail-13.eml
  -rw--- 1 alistair alistair   8556 Nov 15 10:10 /tmp/nsemail-14.eml
  -rw--- 1 alistair alistair   1659 Nov 15 10:32 /tmp/nsemail-15.eml
  -rw--- 1 alistair alistair   3240 Nov 15 10:47 /tmp/nsemail-16.eml
  -rw--- 1 alistair alistair   3260 Nov 15 10:57 /tmp/nsemail-17.eml
  -rw--- 1 alistair alistair 107975 Nov 15 13:43 /tmp/nsemail-18.eml
  -rw--- 1 alistair alistair   4878 Nov 15 13:44 /tmp/nsemail-19.eml
  -rw--- 1 alistair alistair  21150 Nov 13 08:43 /tmp/nsemail-1.eml
  -rw--- 1 alistair alistair   2974 Nov 18 08:41 /tmp/nsemail-1.html
  -rw--- 1 alistair alistair   6328 Nov 15 13:45 /tmp/nsemail-20.eml
  -rw--- 1 alistair alistair 134689 Nov 15 13:49 /tmp/nsemail-21.eml
  -rw--- 1 alistair alistair   2733 Nov 15 17:15 /tmp/nsemail-22.eml
  -rw--- 1 alistair alistair  53857 Nov 16 09:23 /tmp/nsemail-23.eml
  -rw--- 1 alistair alistair  89392 Nov 16 09:39 /tmp/nsemail-24.eml
  -rw--- 1 alistair alistair  80120 Nov 17 10:52 /tmp/nsemail-25.eml
  -rw--- 1 alistair alistair   6361 Nov 17 18:45 /tmp/nsemail-26.eml
  -rw--- 1 alistair alistair   3455 Nov 18 08:38 /tmp/nsemail-27.eml
  -rw--- 1 alistair alistair   5522 Nov 18 08:41 /tmp/nsemail-28.eml
  -rw--- 1 alistair alistair   8883 Nov 18 08:43 /tmp/nsemail-29.eml
  -rw--- 1 alistair alistair  29937 Nov 13 09:37 /tmp/nsemail-2.eml
  -rw--- 1 alistair alistair   5057 Nov 18 08:43 /tmp/nsemail-2.html
  -rw--- 1 alistair alistair   8311 Nov 18 08:49 /tmp/nsemail-30.eml
  -rw--- 1 alistair alistair   2015 Nov 13 09:40 /tmp/nsemail-3.eml
  -rw--- 1 alistair alistair   4949 Nov 18 08:49 /tmp/nsemail-3.html
  -rw--- 1 alistair alistair 183446 Nov 14 08:48 /tmp/nsemail-4.eml
  -rw--- 1 alistair alistair  59817 Nov 15 08:41 /tmp/nsemail-5.eml
  -rw--- 1 alistair alistair   9751 Nov 15 08:47 /tmp/nsemail-6.eml
  -rw--- 1 alistair alistair   2967 Nov 15 08:49 /tmp/nsemail-7.eml
  -rw--- 1 alistair alistair   2983 Nov 15 08:54 /tmp/nsemail-8.eml
  -rw--- 1 alistair alistair  19780 Nov 15 09:14 /tmp/nsemail-9.eml
  -rw--- 1 alistair alistair  27900 Nov 13 08:34 /tmp/nsemail.eml
  -rw--- 1 alistair alistair   1317 Nov 18 08:38 /tmp/nsemail.html
  -rw--- 1 alistair alistair   1115 Nov 18 08:41 /tmp/nsmail-1.tmp
  -rw--- 1 alistair alistair   2424 Nov 18 08:43 /tmp/nsmail-2.tmp
  -rw--- 1 alistair alistair   2000 Nov 18 08:49 /tmp/nsmail-3.tmp
  -rw--- 1 alistair alistair967 Nov 18 08:38 /tmp/nsmail.tmp

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: thunderbird 1:68.1.2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   2211 F pulseaudio
  BuildID: 20191010144232
  Channel: Unavailable
  Date: Mon Nov 18 08:50:15 2019
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   dns-search integrics.com
  InstallationDate: Installed on 2017-08-16 (823 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 1.0.0.1 dev wlp58s0 proto dhcp metric 600 
   1.0.0.0/21 dev wlp58s0 proto kernel scope link src 1.0.1.146 metric 600 
   169.254.0.0/16 dev wlp58s0 scope link metric 1000
  NoProfiles: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: 

[Desktop-packages] [Bug 1854753] Re: Unity menus aren't initially populated

[Alistair Cunningham]

This problem still happens on Ubuntu 20.04 beta. Is there any progress
in fixing it?

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

Title:
  Unity menus aren't initially populated

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  If you navigate using the mouse to a menu that has a submenu, for
  example View -> Toolbars, sometimes the first time you do so, the
  submenu is empty and only shows as a very small grey rectangle. If you
  then move the mouse pointer away from the menu, click in the middle of
  a web page, wait a few seconds, and then try the submenu again, the
  submenu is appears correctly.

  Thunderbird 68.2.1 is also affected by this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 70.0.1+build1-0ubuntu0.19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   2189 F pulseaudio
  BuildID: 20191031091608
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Dec  2 10:31:01 2019
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   dns-search integrics.com
  IncompatibleExtensions:
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2017-08-16 (837 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 172.20.0.1 dev wlp58s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp58s0 scope link metric 1000 
   172.20.0.0/20 dev wlp58s0 proto kernel scope link src 172.20.0.120 metric 600
  MostRecentCrashID: bp-3d145359-2f62-4b35-a046-86be50191125
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=70.0.1/20191031091608 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (58 days ago)
  dmi.bios.date: 08/30/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET56W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1854753/+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 1872372] [NEW] emacs instantly crashes when used in gui mode

[Sadon Albader]

Public bug reported:

Terminal output:
Fatal error 6: Aborted
Backtrace:
emacs[0x5194a2]
emacs[0x4febb1]
emacs[0x519559]
emacs[0x445315]
emacs[0x4fea4a]
emacs[0x4caadd]
emacs[0x4ce828]
emacs[0x4ce8be]
/lib/x86_64-linux-gnu/libX11.so.6(_XError+0xfb)[0x7fe9d10a10db]
/lib/x86_64-linux-gnu/libX11.so.6(+0x3de47)[0x7fe9d109de47]
/lib/x86_64-linux-gnu/libX11.so.6(+0x3dee5)[0x7fe9d109dee5]
/lib/x86_64-linux-gnu/libX11.so.6(_XEventsQueued+0x52)[0x7fe9d109e832]
/lib/x86_64-linux-gnu/libX11.so.6(XFlush+0x1e)[0x7fe9d107fcee]
/lib/x86_64-linux-gnu/libX11.so.6(+0x5df16)[0x7fe9d10bdf16]
/lib/x86_64-linux-gnu/libX11.so.6(XDestroyIC+0x16)[0x7fe9d10abee6]
emacs[0x4e09b0]
emacs[0x4d88bc]
emacs[0x4d8faf]
emacs[0x42d8ac]
emacs[0x4caa93]
emacs[0x4ce828]
emacs[0x4ce8be]
/lib/x86_64-linux-gnu/libX11.so.6(_XError+0xfb)[0x7fe9d10a10db]
/lib/x86_64-linux-gnu/libX11.so.6(+0x3de47)[0x7fe9d109de47]
/lib/x86_64-linux-gnu/libX11.so.6(+0x3dee5)[0x7fe9d109dee5]
/lib/x86_64-linux-gnu/libX11.so.6(_XEventsQueued+0x52)[0x7fe9d109e832]
/lib/x86_64-linux-gnu/libX11.so.6(XPending+0x61)[0x7fe9d1090171]
/lib/x86_64-linux-gnu/libgdk-3.so.0(+0x7020f)[0x7fe9d173b20f]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_prepare+0x19f)[0x7fe9d121772f]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x520db)[0x7fe9d12180db]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_pending+0x2c)[0x7fe9d121827c]
/lib/x86_64-linux-gnu/libgtk-3.so.0(gtk_events_pending+0x12)[0x7fe9d1a20392]
emacs[0x4cb38d]
emacs[0x505f82]
emacs[0x506625]
emacs[0x55eced]
emacs[0x57799d]
emacs[0x5b2504]
emacs[0x57a57a]
emacs[0x577afb]
emacs[0x5b2504]
...
[1]21618 abort (core dumped)  emacs

Tested on multiple machines (two amd64 laptops and one ppc64el Talos 
workstation) all have same issue. Runs fine on 18.04 LTS
Also works fine on focal if used in tty or explicitly disable GTK using  "emacs 
--no-window-system"

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: emacs 1:26.3+1-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: Unity:Unity7:ubuntu
Date: Mon Apr 13 02:13:31 2020
PackageArchitecture: all
SourcePackage: emacs
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal ppc64el

** Tags added: ppc64el

** Description changed:

  Terminal output:
  Fatal error 6: Aborted
  Backtrace:
  emacs[0x5194a2]
  emacs[0x4febb1]
  emacs[0x519559]
  emacs[0x445315]
  emacs[0x4fea4a]
  emacs[0x4caadd]
  emacs[0x4ce828]
  emacs[0x4ce8be]
  /lib/x86_64-linux-gnu/libX11.so.6(_XError+0xfb)[0x7fe9d10a10db]
  /lib/x86_64-linux-gnu/libX11.so.6(+0x3de47)[0x7fe9d109de47]
  /lib/x86_64-linux-gnu/libX11.so.6(+0x3dee5)[0x7fe9d109dee5]
  /lib/x86_64-linux-gnu/libX11.so.6(_XEventsQueued+0x52)[0x7fe9d109e832]
  /lib/x86_64-linux-gnu/libX11.so.6(XFlush+0x1e)[0x7fe9d107fcee]
  /lib/x86_64-linux-gnu/libX11.so.6(+0x5df16)[0x7fe9d10bdf16]
  /lib/x86_64-linux-gnu/libX11.so.6(XDestroyIC+0x16)[0x7fe9d10abee6]
  emacs[0x4e09b0]
  emacs[0x4d88bc]
  emacs[0x4d8faf]
  emacs[0x42d8ac]
  emacs[0x4caa93]
  emacs[0x4ce828]
  emacs[0x4ce8be]
  /lib/x86_64-linux-gnu/libX11.so.6(_XError+0xfb)[0x7fe9d10a10db]
  /lib/x86_64-linux-gnu/libX11.so.6(+0x3de47)[0x7fe9d109de47]
  /lib/x86_64-linux-gnu/libX11.so.6(+0x3dee5)[0x7fe9d109dee5]
  /lib/x86_64-linux-gnu/libX11.so.6(_XEventsQueued+0x52)[0x7fe9d109e832]
  /lib/x86_64-linux-gnu/libX11.so.6(XPending+0x61)[0x7fe9d1090171]
  /lib/x86_64-linux-gnu/libgdk-3.so.0(+0x7020f)[0x7fe9d173b20f]
  
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_prepare+0x19f)[0x7fe9d121772f]
  /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x520db)[0x7fe9d12180db]
  
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_pending+0x2c)[0x7fe9d121827c]
  /lib/x86_64-linux-gnu/libgtk-3.so.0(gtk_events_pending+0x12)[0x7fe9d1a20392]
  emacs[0x4cb38d]
  emacs[0x505f82]
  emacs[0x506625]
  emacs[0x55eced]
  emacs[0x57799d]
  emacs[0x5b2504]
  emacs[0x57a57a]
  emacs[0x577afb]
  emacs[0x5b2504]
  ...
  [1]21618 abort (core dumped)  emacs
  
- Tested on multiple machines (two amd64 laptops and one ppc64el Talos
- workstation) all have same issue. Runs fine on 18.04 LTS
+ Tested on multiple machines (two amd64 laptops and one ppc64el Talos 
workstation) all have same issue. Runs fine on 18.04 LTS
+ Also works fine on focal if used in tty or explicitly disable GTK using  
"emacs --no-window-system"
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: emacs 1:26.3+1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Apr 13 02:13:31 

[Desktop-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver

[jman6495]

This additionally crashes gnome-shell (see further dmesg)

** Attachment added: "newmydmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1849084/+attachment/5352867/+files/newmydmesg.log

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 

[Desktop-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver

[jman6495]

I also believe i'm experiencing this or something similar. The issue is
much wider than plasma though, this is a general issue with the amdgpu
driver, i believe.

If it could be reclassified as such that would probably help get it to
the right people.

Experiencing the same issues on both Ubuntu 18.04LTS, Ubuntu 20.04 Beta
and Manjaro.

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  

[Desktop-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver

[jman6495]

Also here is my dmesg when I attemt the suspend

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1849084/+attachment/5352861/+files/dmesg

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 

[Desktop-packages] [Bug 1872370] [NEW] gedit current line is illegibly highlighted on Breeze-Dark theme

[Daniel Tang]

Public bug reported:

When gedit is launched in KDE with the Breeze-Dark theme active, the
line with the cursor is highlighted white even though the text is white.
This makes it impossible to read the text.

"lsb_release -rd":

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

"apt-cache policy gedit"

gedit:
  Installed: 3.36.1-1
  Candidate: 3.36.1-1
  Version table:
 *** 3.36.1-1 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

"apt-cache policy kde-config-gtk-style"

kde-config-gtk-style:
  Installed: 4:5.18.4.1-0ubuntu1
  Candidate: 4:5.18.4.1-0ubuntu1
  Version table:
 *** 4:5.18.4.1-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status

"apt-cache policy breeze-gtk-theme"

breeze-gtk-theme:
  Installed: 5.18.4.1-0ubuntu1
  Candidate: 5.18.4.1-0ubuntu1
  Version table:
 *** 5.18.4.1-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status

Procedure:

1. Spin up a VirtualBox VM
2. Insert 
http://cdimage.ubuntu.com/kubuntu/daily-live/20200412/focal-desktop-amd64.iso 
as the CD
3. Click on "Try Kubuntu"
4. Open Konsole
5. Run "sudo apt install gedit"
6. Open System Settings
7. Go into "Global Theme"
8. Select "Breeze Dark"
9. Click "Apply"
10. Click the home icon
11. Go into "Application Style"
12. Click "Configure GNOME/GTK Application Style"
13. Set both the "GTK2 theme" and "GTK3 theme" dropdowns to "Breeze-Dark"
14. Click "Apply"
15. Open gedit
16. Type some text

Expected behavior:

To be able to read the line I'm typing on.

This was the behavior before Ubuntu 20.04 unified GTK and Qt themes.
While restoring the behavior would be better than having completely
illegible text, it would be preferred to get gedit and the Breeze-Dark
theme to actually work together.

Actual behavior:

The current line is illegible. The line is highlighted white even though
the text is white.

A screenshot of this behavior is attached.

Workaround:

Move the cursor to another line before trying to read the text, or
select the text before trying to read it. This workaround is very
annoying.

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

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

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

** Attachment added: "Screenshot_20200412_175310.png"
   
https://bugs.launchpad.net/bugs/1872370/+attachment/5352860/+files/Screenshot_20200412_175310.png

** Also affects: kde-gtk-config (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  gedit current line is illegibly highlighted on Breeze-Dark theme

Status in breeze package in Ubuntu:
  New
Status in gedit package in Ubuntu:
  New
Status in kde-gtk-config package in Ubuntu:
  New

Bug description:
  When gedit is launched in KDE with the Breeze-Dark theme active, the
  line with the cursor is highlighted white even though the text is
  white. This makes it impossible to read the text.

  "lsb_release -rd":

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

  "apt-cache policy gedit"

  gedit:
Installed: 3.36.1-1
Candidate: 3.36.1-1
Version table:
   *** 3.36.1-1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  "apt-cache policy kde-config-gtk-style"

  kde-config-gtk-style:
Installed: 4:5.18.4.1-0ubuntu1
Candidate: 4:5.18.4.1-0ubuntu1
Version table:
   *** 4:5.18.4.1-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

  "apt-cache policy breeze-gtk-theme"

  breeze-gtk-theme:
Installed: 5.18.4.1-0ubuntu1
Candidate: 5.18.4.1-0ubuntu1
Version table:
   *** 5.18.4.1-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

  Procedure:

  1. Spin up a VirtualBox VM
  2. Insert 
http://cdimage.ubuntu.com/kubuntu/daily-live/20200412/focal-desktop-amd64.iso 
as the CD
  3. Click on "Try Kubuntu"
  4. Open Konsole
  5. Run "sudo apt install gedit"
  6. Open System Settings
  7. Go into "Global Theme"
  8. Select "Breeze Dark"
  9. Click "Apply"
  10. Click the home icon
  11. Go into "Application Style"
  12. Click "Configure GNOME/GTK Application 

[Desktop-packages] [Bug 1872330] Re: Cannot open gear icon of an input source in Region & Language

[Gunnar Hjalmarsson]

Thanks for your report!

While this is vaguely related to this upstream issue:

https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/630

it's at first hand a problem with the ibus-unikey package. I have
uploaded an Ubuntu only fix for now.

** Package changed: gnome-control-center (Ubuntu) => ibus-unikey
(Ubuntu)

** Changed in: ibus-unikey (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ibus-unikey (Ubuntu)
   Status: New => Fix Committed

** Changed in: ibus-unikey (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #630
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/630

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

Title:
  Cannot open gear icon of an input source in Region & Language

Status in ibus-unikey package in Ubuntu:
  Fix Committed

Bug description:
  Using the Ubuntu 20.04 Focal Fossa Beta version.

  Using the gnome-control-center version 1:3.36.1-1ubuntu4

  What should happen: Clicking on the gear icon of an input source in
  the Input Sources section in Region & Language should open the
  respective settings menu.

  What happened: Clicking on the gear icon does nothing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-unikey/+bug/1872330/+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 871133] Re: Volume Step not changeable in Unity and GNOME desktops

[Sergio]

It's fixed in version 3.35. Sadly Ubuntu 19.10 and older will not get
the update.

On Ubuntu 20.04 or newer you can change step like this:

dconf write /org/gnome/settings-daemon/plugins/media-keys/volume-step 2

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

Title:
  Volume Step not changeable in Unity and GNOME desktops

Status in GNOME Settings Daemon:
  Fix Released
Status in Ubuntu GNOME:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Changing the volume step in gconf-editor does not do anything when adjusting 
the volume on a hardware dial.
  --- 
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  DistroRelease: Ubuntu 11.10
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
  Package: gnome-settings-daemon 3.2.0-0ubuntu5
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-12-generic i686
  UpgradeStatus: Upgraded to oneiric on 2011-10-08 (3 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/871133/+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 1872327] Re: OLED brightness control on Intel Iris Plus Graphics G7 on 20.4 beta

[Daniel Blatter]

That describes a work around:
https://wiki.archlinux.org/index.php/HP_Spectre_x360_13-4231ng#Brightness_/_backlight

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

Title:
  OLED brightness control on Intel Iris Plus Graphics G7 on 20.4 beta

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi

  I'm testing kubuntu 20.4 with my HP spectre x360 13 aw0720nz.
  The hotkeys to adjust the OLED brightness do not work.

  Adjusting the display brightness editing the file brightness in
  /sys/class/backlight/intel_backlight doesn't work either. At
  /etc/default/grub I already added "acpi_backlight=vendor"

  I found an article, that fits to the topic:
  
http://reddit.com/r/linux/comments/cmf0vi/the_state_of_oled_brightness_on_linux

  Regards Daniel

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  CompositorRunning: None
  Date: Sun Apr 12 18:42:36 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:86fa]
  InstallationDate: Installed on 2020-04-03 (8 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  MachineType: HP HP Spectre x360 Convertible 13-aw0xxx
  ProcEnviron:
   LANGUAGE=de_CH:de
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=UUID=61d60ac7-8b29-4729-a6a0-e3b0300dba97 ro rootflags=subvol=@ quiet 
splash acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FA
  dmi.board.vendor: HP
  dmi.board.version: 87.46
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd03/02/2020:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.46:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
  dmi.product.sku: 8KZ06EA#UUZ
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-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/xorg/+bug/1872327/+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 1871009] Re: Firefox doesn't restart after update

[fabtagon]

Yes, Firefox works well.

No, this seems to happen for about 50% of Firefox updates. In case of
past occourences, one problem was that command line parameters (that had
been given to the instances that had been stopped) were not passed to
the restarted instance. But this bug is, afaik, fixed. And in my current
setup, Firefox doesn't require any parameters to restart gracefully.

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

Title:
  Firefox doesn't restart after update

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to firefox amd64 74.0.1+build1-0ubuntu0.18.04.1 (using
  apt-get), a message appeared in the running Firefox session: 'Firefox
  needs to be restarted' (as usual, nothing wrong with that). After
  clicking ok (or 'do it now' or what the exact message was), Firefox
  terminates.

  Expected behaviour: Firefox actually restarts

  Experienced behaviour: Nothing seemed to happen. Firefox terminated
  but never came back. (Starting Firefox again by hand worked
  flawlessly.)

  I have no profiles defined. I don't usually pass any options when
  starting Firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 74.0.1+build1-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab3616 F pulseaudio
   /dev/snd/controlC1:  fab3616 F pulseaudio
  BrokenPermissions:
   saved-telemetry-pings/a1103722-309c-47da-b9da-2bc9411237b9 (0o600, wrong 
owner)
   saved-telemetry-pings/e1cac187-9dd1-48b9-bb99-8c67374c7212 (0o600, wrong 
owner)
   saved-telemetry-pings/fbf7331c-39a9-4539-97fa-280e7d343563 (0o600, wrong 
owner)
  BuildID: 20200403064753
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  6 03:13:58 2020
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-04-27 (1805 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.23.1 dev eth0 proto dhcp metric 100 
   10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.23.0/24 dev eth0 proto kernel scope link src 192.168.23.136 metric 
100
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-f8832267-2764-4f52-b9df-136771180712
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:732
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=74.0.1/20200403064753 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-f8832267-2764-4f52-b9df-136771180712
   bp-f03b7d3e-1a66-441d-be5d-cedc11180201
   bp-610fb53c-4664-4692-8e37-62c501180107
   bp-708689c3-ba2d-427e-a43b-605df2141112
   bp-b2e12bb9-63b8-494d-9390-f5d722140521
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to bionic on 2018-08-18 (596 days ago)
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd08/06/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1871009/+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 1872327] Re: OLED brightness control on Intel Iris Plus Graphics G7 on 20.4 beta

[Daniel Blatter]

** Summary changed:

- Backlight brightness control on Intel Iris Plus Graphics G7 on 20.4 beta
+ OLED brightness control on Intel Iris Plus Graphics G7 on 20.4 beta

** Description changed:

  Hi
  
  I'm testing kubuntu 20.4 with my HP spectre x360 13 aw0720nz.
- The hotkeys to adjust the backlight brightness do not work.
- It's no bug in KDE, as adjusting the brightness editing the file brightness 
in /sys/class/backlight/intel_backlight doesn't work either.
- At /etc/default/grub I already added "acpi_backlight=vendor"
+ The hotkeys to adjust the OLED brightness do not work.
+ 
+ Adjusting the display brightness editing the file brightness in
+ /sys/class/backlight/intel_backlight doesn't work either. At
+ /etc/default/grub I already added "acpi_backlight=vendor"
+ 
+ I found an article, that fits to the topic:
+ 
http://reddit.com/r/linux/comments/cmf0vi/the_state_of_oled_brightness_on_linux
  
  Regards Daniel
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  CompositorRunning: None
  Date: Sun Apr 12 18:42:36 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
-  Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
-Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:86fa]
+  Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
+    Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:86fa]
  InstallationDate: Installed on 2020-04-03 (8 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  MachineType: HP HP Spectre x360 Convertible 13-aw0xxx
  ProcEnviron:
-  LANGUAGE=de_CH:de
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=de_CH.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=de_CH:de
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=de_CH.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=UUID=61d60ac7-8b29-4729-a6a0-e3b0300dba97 ro rootflags=subvol=@ quiet 
splash acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FA
  dmi.board.vendor: HP
  dmi.board.version: 87.46
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd03/02/2020:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.46:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
  dmi.product.sku: 8KZ06EA#UUZ
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

Title:
  OLED brightness control on Intel Iris Plus Graphics G7 on 20.4 beta

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi

  I'm testing kubuntu 20.4 with my HP spectre x360 13 aw0720nz.
  The hotkeys to adjust the OLED brightness do not work.

  Adjusting the display brightness editing the file brightness in
  /sys/class/backlight/intel_backlight doesn't work either. At
  /etc/default/grub I already added "acpi_backlight=vendor"

  I found an article, that fits to the topic:
  
http://reddit.com/r/linux/comments/cmf0vi/the_state_of_oled_brightness_on_linux

  Regards Daniel

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  CompositorRunning: None
  Date: Sun Apr 12 18:42:36 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:86fa]
  InstallationDate: Installed on 2020-04-03 (8 days ago)
  InstallationMedia: Kubuntu 20.04 

[Desktop-packages] [Bug 871133] Re: Volume Step not changeable in Unity and GNOME desktops

[Sergio]

This is an open issue on the project's GitLab:
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/474

Still not sure it's getting any attention :( Would really like this
feature.

** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #474
   https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/474

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

Title:
  Volume Step not changeable in Unity and GNOME desktops

Status in GNOME Settings Daemon:
  Fix Released
Status in Ubuntu GNOME:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Changing the volume step in gconf-editor does not do anything when adjusting 
the volume on a hardware dial.
  --- 
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  DistroRelease: Ubuntu 11.10
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
  Package: gnome-settings-daemon 3.2.0-0ubuntu5
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-12-generic i686
  UpgradeStatus: Upgraded to oneiric on 2011-10-08 (3 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/871133/+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 1872336] Re: Text on Snap Store is garbled

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Text on Snap Store is garbled

Status in xorg package in Ubuntu:
  New

Bug description:
  Details:
  lsb_release -rd:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  Steps:
  1. Launch Snap Store

  Expect:
  All the text to be in human-readable format/font.

  Actual:
  The text is garbled (Screenshot attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Apr 12 10:48:55 2020
  DistUpgraded: 2020-04-05 11:46:42,999 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, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:063e]
  InstallationDate: Installed on 2019-12-14 (119 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 5547
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=6ab1d432-fbe5-4e12-98f6-886bc4101897 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-05 (6 days ago)
  dmi.bios.date: 11/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0598GM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A06
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd11/05/2014:svnDellInc.:pnInspiron5547:pvrA06:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA06:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5547
  dmi.product.sku: Inspiron 5547
  dmi.product.version: A06
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-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/xorg/+bug/1872336/+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 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs

[Joseph Yasi]

I currently have the package patched in my PPA to resolve the bug. It is
a difficult to debug problem that has been sending users upstream to
kodi with bug reports and confusing stack traces. This will get more
exposure when focal is released due to the LTS status.

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

Title:
  libjack-jackd2-0 double close on a failure to connect to jackd which
  causes crashes in multithreaded programs

Status in alsa-plugins package in Ubuntu:
  New
Status in jackd2 package in Ubuntu:
  Confirmed
Status in jackd2 package in Debian:
  Confirmed

Bug description:
  After upgrading to Ubuntu 19.04, I started experiencing sporadic
  crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded
  alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin
  is enabled by default in /etc/alsa/conf.d/50-jack.conf.

  The crashes are caused by a race condition when kodi's audio engine
  thread is enumerating the ALSA sound devices, and the udev thread is
  enumerating the udev devices triggered by the sound device add from
  turning the AVR on.

  When enumerating the ALSA jack plugin device, it tries to connect to
  connect to jackd. Since I don't have jackd installed, it fails to
  connect. libjack closes the socket on error, and then closes it again
  in it's cleanup code. Since it's closing the same file descriptor
  twice, it interacts with other threads that have potentially opened
  file descriptors, and causes the crash.

  This same bug could potentially affect other multi-threaded programs
  that enumerate ALSA devices.

  Fix committed upstream:
  
https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1833479/+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 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs

[Joseph Yasi]

Is this going to make it for focal? This bug causes kodi to crash when
turning my TV screen off.

** Tags added: focal

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

Title:
  libjack-jackd2-0 double close on a failure to connect to jackd which
  causes crashes in multithreaded programs

Status in alsa-plugins package in Ubuntu:
  New
Status in jackd2 package in Ubuntu:
  Confirmed
Status in jackd2 package in Debian:
  Confirmed

Bug description:
  After upgrading to Ubuntu 19.04, I started experiencing sporadic
  crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded
  alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin
  is enabled by default in /etc/alsa/conf.d/50-jack.conf.

  The crashes are caused by a race condition when kodi's audio engine
  thread is enumerating the ALSA sound devices, and the udev thread is
  enumerating the udev devices triggered by the sound device add from
  turning the AVR on.

  When enumerating the ALSA jack plugin device, it tries to connect to
  connect to jackd. Since I don't have jackd installed, it fails to
  connect. libjack closes the socket on error, and then closes it again
  in it's cleanup code. Since it's closing the same file descriptor
  twice, it interacts with other threads that have potentially opened
  file descriptors, and causes the crash.

  This same bug could potentially affect other multi-threaded programs
  that enumerate ALSA devices.

  Fix committed upstream:
  
https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1833479/+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 1872336] [NEW] Text on Snap Store is garbled

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Details:
lsb_release -rd:
Description:Ubuntu Focal Fossa (development branch)
Release:20.04

Steps:
1. Launch Snap Store

Expect:
All the text to be in human-readable format/font.

Actual:
The text is garbled (Screenshot attached)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
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
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sun Apr 12 10:48:55 2020
DistUpgraded: 2020-04-05 11:46:42,999 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, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:063e]
InstallationDate: Installed on 2019-12-14 (119 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Dell Inc. Inspiron 5547
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=6ab1d432-fbe5-4e12-98f6-886bc4101897 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-05 (6 days ago)
dmi.bios.date: 11/05/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0598GM
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A06
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd11/05/2014:svnDellInc.:pnInspiron5547:pvrA06:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA06:
dmi.product.family: 00
dmi.product.name: Inspiron 5547
dmi.product.sku: Inspiron 5547
dmi.product.version: A06
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption focal third-party-packages ubuntu 
wayland-session
-- 
Text on Snap Store is garbled
https://bugs.launchpad.net/bugs/1872336
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg 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 1853830] Re: [FFe] gamemode

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-mate-meta - 1.263

---
ubuntu-mate-meta (1.263) focal; urgency=medium

  * Refreshed dependencies
  * Added gamemode to core-recommends [amd64], desktop-recommends
[amd64] (LP: #1853830)

 -- Martin Wimpress   Sun, 12 Apr 2020
11:35:14 +0100

** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [FFe] gamemode

Status in gamemode package in Ubuntu:
  Fix Committed
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released

Bug description:
  [Availability]

  Builds on amd64 only in Ubuntu and syncs from Debian. GameMode was
  designed primarily as a  solution to the Intel and AMD CPU powersave
  or ondemand governors, and intended for gaming; hence why it is amd64
  only.

  [Rationale]

  We would like to enable GameMode as it allows games to request a set
  of optimisations be temporarily applied to the host OS and improve
  gaming performance.

  The Ubuntu desktop team intend to seed gamemode.

  [Security]

  No CVE/known security issue. GameMode includes an user daemon that
  modifies the CPU governors and GPU clock state through pkexec-ed
  helpers.

  [Quality assurance]

  - The desktop-packages team is subscribed to the package
  - 2 bugs in Debian BTS which are being investigated. None in LP.
  - The package is actively maintained in Debian and in sync in Ubuntu.
  - No test suite, but difficult to integrate with autopkgtest due to hardware 
requirements.

  [Dependencies]

  All the Depends: are currently in main. There are no Recommends:

  - init-system-helpers (>= 1.52)
  - libc6 (>= 2.27)
  - libsystemd0 (>= 221)
  - libdbus-1-3 (>= 1.9.14)

  [Standards compliance]

  The package is using current (dh12) standards, the standards-version
  is 4.4.0, the package is in sync from Debian.

  [Maintenance]

  Upstream is active and the desktop team is going to look after the
  package in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/1853830/+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 1869568] Re: Unlock takes a long time

[Roger Lipscombe]

> see if something's leaking registered handlers.

It looks like clutter handlers are stored in two different hash tables:
g_handlers and g_handler_list_bsa_ht.

On the PC that's really slow, g_handlers.size = 8388608 (that's ~8M); on
the PC that's not, g_handlers.size = 65536 (~65K). So, yeah, something's
leaking, afaict.

Gonna see if the hash table entries (signal_id, instance, closure) point
to anything that gives me a clue. Given that the extensions are written
mostly in JS, this is gonna be all kinds of interesting...

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

Title:
  Unlock takes a long time

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I searched and found related bugs #1774188 and #1847566, but one of
  those is against 19.04, which is end-of-support, and the other was
  abandoned with no feedback from the OP. So, let's try again.

  When unlocking my screen, it takes progressively longer to unlock.
  After a fresh restart, it's pretty quick. After about a day, it takes
  about a second. After a longer period, it takes up to 5 seconds.

  When I press Enter at the lock screen to get to the password entry,
  the "wipe" effect commonly stalls as it gets near the top of the
  screen; not sure if this is related.

  After correctly entering my password, it takes several seconds before
  my desktop is visible. It's _there_, because moving the mouse around
  changes the mouse pointer according to what's under it (e.g. it turns
  into an I-bar on the Firefox search/address box and a finger icon on a
  link). It just takes several seconds to actually draw the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 11:10:07 2020
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-10 (78 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  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/1869568/+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 1872330] [NEW] Cannot open gear icon of an input source in Region & Language

[Falling Snowdin]

Public bug reported:

Using the Ubuntu 20.04 Focal Fossa Beta version.

Using the gnome-control-center version 1:3.36.1-1ubuntu4

What should happen: Clicking on the gear icon of an input source in the
Input Sources section in Region & Language should open the respective
settings menu.

What happened: Clicking on the gear icon does nothing.

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

** Attachment added: "Gif showing the bug"
   
https://bugs.launchpad.net/bugs/1872330/+attachment/5352677/+files/ibus_unikey_bug.gif

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

Title:
  Cannot open gear icon of an input source in Region & Language

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

Bug description:
  Using the Ubuntu 20.04 Focal Fossa Beta version.

  Using the gnome-control-center version 1:3.36.1-1ubuntu4

  What should happen: Clicking on the gear icon of an input source in
  the Input Sources section in Region & Language should open the
  respective settings menu.

  What happened: Clicking on the gear icon does nothing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1872330/+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 1872327] [NEW] Backlight brightness control on Intel Iris Plus Graphics G7 on 20.4 beta

[Daniel Blatter]

Public bug reported:

Hi

I'm testing kubuntu 20.4 with my HP spectre x360 13 aw0720nz.
The hotkeys to adjust the backlight brightness do not work.
It's no bug in KDE, as adjusting the brightness editing the file brightness in 
/sys/class/backlight/intel_backlight doesn't work either.
At /etc/default/grub I already added "acpi_backlight=vendor"

Regards Daniel

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
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
CompositorRunning: None
Date: Sun Apr 12 18:42:36 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:86fa]
InstallationDate: Installed on 2020-04-03 (8 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
MachineType: HP HP Spectre x360 Convertible 13-aw0xxx
ProcEnviron:
 LANGUAGE=de_CH:de
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=de_CH.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=UUID=61d60ac7-8b29-4729-a6a0-e3b0300dba97 ro rootflags=subvol=@ quiet 
splash acpi_backlight=vendor vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/02/2020
dmi.bios.vendor: AMI
dmi.bios.version: F.13
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 86FA
dmi.board.vendor: HP
dmi.board.version: 87.46
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd03/02/2020:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.46:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Spectre
dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
dmi.product.sku: 8KZ06EA#UUZ
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Backlight brightness control on Intel Iris Plus Graphics G7 on 20.4
  beta

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi

  I'm testing kubuntu 20.4 with my HP spectre x360 13 aw0720nz.
  The hotkeys to adjust the backlight brightness do not work.
  It's no bug in KDE, as adjusting the brightness editing the file brightness 
in /sys/class/backlight/intel_backlight doesn't work either.
  At /etc/default/grub I already added "acpi_backlight=vendor"

  Regards Daniel

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  CompositorRunning: None
  Date: Sun Apr 12 18:42:36 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:86fa]
  InstallationDate: Installed on 2020-04-03 (8 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  MachineType: HP HP Spectre x360 Convertible 13-aw0xxx
  ProcEnviron:
   LANGUAGE=de_CH:de
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=UUID=61d60ac7-8b29-4729-a6a0-e3b0300dba97 ro rootflags=subvol=@ quiet 
splash acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FA
  dmi.board.vendor: HP
  dmi.board.version: 87.46
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd03/02/2020:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.46:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 

[Desktop-packages] [Bug 1872318] Re: During Focal Beta install: nm-online crashed with SIGSEGV in g_source_set_ready_time()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1866783, so 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.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1872318/+attachment/5352637/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1872318/+attachment/5352639/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1872318/+attachment/5352648/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1872318/+attachment/5352649/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1872318/+attachment/5352650/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1872318/+attachment/5352652/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1872318/+attachment/5352653/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1866783

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  During Focal Beta install: nm-online crashed with SIGSEGV in
  g_source_set_ready_time()

Status in network-manager package in Ubuntu:
  New

Bug description:
  Apport pops up with this error during a clean installation of the
  Focal beta on my Dell XPS 9360 DE.

  The error popped up during the step after connecting with the wifi.
  Setup and installation proceed normally.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CasperVersion: 1.443
  Date: Sun Apr 12 16:29:55 2020
  ExecutablePath: /usr/bin/nm-online
  IpRoute:
   default via 192.168.178.1 dev wlp58s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp58s0 scope link metric 1000 
   192.168.178.0/24 dev wlp58s0 proto kernel scope link src 192.168.178.28 
metric 600
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcCmdline: /usr/bin/nm-online -s -q --timeout=30
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f55981eabf3 :   cmp
0x10(%rax),%rbp
   PC (0x7f55981eabf3) ok
   source "0x10(%rax)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   g_source_set_ready_time () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nm-online crashed with SIGSEGV in g_source_set_ready_time()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  nmcli-con:
   NAME   UUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE   STATE  
ACTIVE-PATH SLAVE  FILENAME 
 
   HEINZ!Box  3e2eb0c4-8e64-4703-bbe0-81e8492c21f3  wifi  1586709045  Sun Apr 
12 16:30:45 2020  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlp58s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/etc/NetworkManager/system-connections/HEINZ!Box.nmconnection
  nmcli-dev:
   DEVICE   TYPE  STATE IP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTION  CON-UUID 
 CON-PATH   
   wlp58s0  wifi  connected full  limited   
/org/freedesktop/NetworkManager/Devices/2  HEINZ!Box   
3e2eb0c4-8e64-4703-bbe0-81e8492c21f3  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   p2p-dev-wlp58s0  wifi-p2p  

[Desktop-packages] [Bug 1872325] [NEW] Cannot press Meta key when being used as input source

[Falling Snowdin]

Public bug reported:

Using the Ubuntu 20.04 Focal Fossa Beta version.

The ibus-unikey package is at version 0.6.1-1.1build1

What should happen: I should be able to press the Meta key regardless of
input sources chosen.

What happened: When Vietnamese (Unikey) is chosen as the input source,
the Meta key cannot be pressed.

** Affects: ibus-unikey (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Cannot press Meta key when being used as input source

Status in ibus-unikey package in Ubuntu:
  New

Bug description:
  Using the Ubuntu 20.04 Focal Fossa Beta version.

  The ibus-unikey package is at version 0.6.1-1.1build1

  What should happen: I should be able to press the Meta key regardless
  of input sources chosen.

  What happened: When Vietnamese (Unikey) is chosen as the input source,
  the Meta key cannot be pressed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-unikey/+bug/1872325/+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 1872319] [NEW] Changing input method in top bar dropdown menu automatically sets it to STelex2 instead

[Falling Snowdin]

Public bug reported:

Using the Ubuntu 20.04 Focal Fossa Beta version.

The ibus-unikey package is at version 0.6.1-1.1build1

What should happen: Changing the input method through the Input Sources
top bar dropdown menu should change the current input method to the
chosen one.

What happened: Choosing any of the input methods (VNI, Telex, etc.)
provided in the top bar dropdown menu will result in STelex2 being
chosen instead. The only way to correctly set the input method correctly
is to go to Options > Full setup... in the top bar dropdown menu and
change the input method in the popup window.

** Affects: ibus-unikey (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Video showing the bug"
   
https://bugs.launchpad.net/bugs/1872319/+attachment/5352655/+files/ibus-unikey-stelex2-bug.mp4

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

Title:
  Changing input method in top bar dropdown menu automatically sets it
  to STelex2 instead

Status in ibus-unikey package in Ubuntu:
  New

Bug description:
  Using the Ubuntu 20.04 Focal Fossa Beta version.

  The ibus-unikey package is at version 0.6.1-1.1build1

  What should happen: Changing the input method through the Input
  Sources top bar dropdown menu should change the current input method
  to the chosen one.

  What happened: Choosing any of the input methods (VNI, Telex, etc.)
  provided in the top bar dropdown menu will result in STelex2 being
  chosen instead. The only way to correctly set the input method
  correctly is to go to Options > Full setup... in the top bar dropdown
  menu and change the input method in the popup window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-unikey/+bug/1872319/+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 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf

[Klaus Bielke]

Sorry for bad handling. #4 is attachment belonging to #5

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

Title:
  wpasupplicant: unknown keys in no-mac-addr-change.conf

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  NetworkManager warns that no-mac-addr-change.conf contains unknown
  configuration directives:

  # journalctl | grep no-mac-addr-change
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] Read 
config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 
20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 
10-globally-managed-devices.conf, default-wifi-powersave-on.conf)
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'wifi.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'ethernet.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: wpasupplicant 2:2.6-21ubuntu3
  Uname: Linux 5.0.9-050009-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 27 13:15:27 2019
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+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 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf

[Klaus Bielke]

Suggested workaround:

1. Copy file /lib/NetworkManager/conf.d/no-mac-addr-change.conf to dir
/etc/NetworkManager/conf.d/

2. Edit file /etc/NetworkManager/conf.d/no-mac-addr-change.conf: Move 2
lines with cloned-mac-address to new chapter [connection-mac-addr-
change-wifi], cf. attachment.

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

Title:
  wpasupplicant: unknown keys in no-mac-addr-change.conf

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  NetworkManager warns that no-mac-addr-change.conf contains unknown
  configuration directives:

  # journalctl | grep no-mac-addr-change
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] Read 
config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 
20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 
10-globally-managed-devices.conf, default-wifi-powersave-on.conf)
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'wifi.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'ethernet.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: wpasupplicant 2:2.6-21ubuntu3
  Uname: Linux 5.0.9-050009-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 27 13:15:27 2019
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+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 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf

[Klaus Bielke]

** Attachment added: "no-mac-addr-change.conf"
   
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+attachment/5352633/+files/no-mac-addr-change.conf

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

Title:
  wpasupplicant: unknown keys in no-mac-addr-change.conf

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  NetworkManager warns that no-mac-addr-change.conf contains unknown
  configuration directives:

  # journalctl | grep no-mac-addr-change
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] Read 
config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 
20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 
10-globally-managed-devices.conf, default-wifi-powersave-on.conf)
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'wifi.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'ethernet.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: wpasupplicant 2:2.6-21ubuntu3
  Uname: Linux 5.0.9-050009-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 27 13:15:27 2019
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+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 1872303] Re: A print screen button doesn't work

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  A print screen button doesn't work

Status in xorg package in Ubuntu:
  New

Bug description:
  When I push a print screen button - nothing happens, instead of taking
  a screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Apr 12 14:03:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:0459]
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:0459]
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411)
  MachineType: Acer Aspire 5734Z
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2010
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.01
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5734Z
  dmi.board.vendor: Acer
  dmi.board.version: V1.01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.01
  dmi.modalias: 
dmi:bvnAcer:bvrV1.01:bd04/16/2010:svnAcer:pnAspire5734Z:pvrV1.01:rvnAcer:rnAspire5734Z:rvrV1.01:cvnAcer:ct10:cvrV1.01:
  dmi.product.family: Intel_Mobile
  dmi.product.name: Aspire 5734Z
  dmi.product.sku: Montevina_Fab
  dmi.product.version: V1.01
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-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/xorg/+bug/1872303/+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 1872303] [NEW] A print screen button doesn't work

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When I push a print screen button - nothing happens, instead of taking a
screenshot

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CasperVersion: 1.445
CompositorRunning: None
CurrentDesktop: XFCE
Date: Sun Apr 12 14:03:09 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:0459]
   Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:0459]
LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411)
MachineType: Acer Aspire 5734Z
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash --- maybe-ubiquity
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/16/2010
dmi.bios.vendor: Acer
dmi.bios.version: V1.01
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Aspire 5734Z
dmi.board.vendor: Acer
dmi.board.version: V1.01
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.01
dmi.modalias: 
dmi:bvnAcer:bvrV1.01:bd04/16/2010:svnAcer:pnAspire5734Z:pvrV1.01:rvnAcer:rnAspire5734Z:rvrV1.01:cvnAcer:ct10:cvrV1.01:
dmi.product.family: Intel_Mobile
dmi.product.name: Aspire 5734Z
dmi.product.sku: Montevina_Fab
dmi.product.version: V1.01
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu
-- 
A print screen button doesn't work
https://bugs.launchpad.net/bugs/1872303
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg 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 1871417] Re: kernel update to 5.3.0-46.38 broke wifi

[Michael]

I was able to solve the problem.

1. 5.3.0-42 wifi worked
2. 5.3.0-46 wifi didn't work
3. booted into 5.3.0-42 with working wifi system
4. I used sudo lshw > lshw-42.txt to capture data
5. booted into 5.3.0-46 without working wifi
6. use sudo lshw > lshw-46.txt to capture data
7. I used diff command to compare the two .txt files
8. I determined that my hardware uses rtl8821ce driver but it wasn't working in 
5.3.0-46
9. stopping and starting network-manager didn't work
10. I used cd rtl8821ce/ then sudo ./dkms-remove.sh to change directories and 
remove the driver
11. when I attempted to reinstall the rtl8821ce drivers in 5.3.0-46, I 
discovered that the kernel update hadn't installed the 5.3.0-46 headers which 
prevented the wifi drivers from working.
11a. I was able to connect using bluetooth and my samsung G8 phone as hotspot.
12. I have Synaptic Program Manager so I was able to see the kernel headers 
weren't installed with the kernel update to 5.3.0-46.
13. After installing the 5.3.0-46 headers, the "paused" rtl8821ce driver 
install continued and "magically" the wifi started working!
14. performed restart and cold boot to verify wifi works again!

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

Title:
  kernel update to 5.3.0-46.38 broke wifi

Status in network-manager package in Ubuntu:
  New

Bug description:
  my system updated to 5.3.0-46.38 and now I no longer have wifi. The
  driver doesn't seem to be installed since when I go to setup, wifi
  isn't an available option.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.4-2ubuntu2.2
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 11:00:53 2020
  InstallationDate: Installed on 2019-10-29 (160 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEIP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
   enp2s0  ethernet  unavailable  none  none  
/org/freedesktop/NetworkManager/Devices/2  --  ----   
   lo  loopback  unmanagedunknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  ----
  nmcli-nm:
   RUNNING  VERSION  STATE STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.4   disconnected  started  none  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1871417/+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 1826597] Re: Synaptic touchpad not responding in ubuntu 19.04 when using nvidia drivers

[zob]

Ok. So I finally found a viable workaround (or fix). In BIOS the GPU
must be set to "Hybrid Graphics" NOT "Discrete".

This fixed my issues with running nvdia-drivers and using my touchpad at
the same time in ubuntu 20.04.

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

Title:
  Synaptic touchpad not responding in ubuntu 19.04  when using nvidia
  drivers

Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  
  On a Lenovo Thinkpad P50 with a Synaptics touchpad, the touchpad (or 
trackpoint), does not respond to any input after installing ubuntu 19.04.

  The same machine has been working fine with ubuntu 16.04 and 18.10. To
  be more correct it is still working in 16.04 hwe which I'm dual
  booting.

  If I uninstall the nvidia drivers (right now 418.56-0ubuntu1), and
  replace with noveau drivers it works just fine (by the way there seems
  to be no other issues with the nvidia driver as of yet).

  I have also the nvidia-driver-390 also suggested in the graphical
  software updates tool, to no avail.

  I will attach relevant logs. Please let me know if there is more I should 
supply.
  And thanks for all your hard (and brilliant) work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-libinput 0.28.2-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Adgang nægtet: '/var/log/boot.log'
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 20:36:18 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  InstallationDate: Installed on 2019-04-26 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b596 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 0458:0007 KYE Systems Corp. (Mouse Systems) 
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20EQS0PQ00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=21f288a0-da9c-46ea-8b64-056770908297 ro quiet splash 
synaptic_intertouch=0 vt.handoff=1
  SourcePackage: xserver-xorg-input-libinput
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET83W (1.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS0PQ00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EQS0PQ00:pvrThinkPadP50:rvnLENOVO:rn20EQS0PQ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EQS0PQ00
  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.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/xserver-xorg-input-libinput/+bug/1826597/+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 1826597] Re: Synaptic touchpad not responding in ubuntu 19.04 when using nvidia drivers

[zob]

Ahh. Actually xinput now (with kubuntu-desktop installed) now has
registered my touchpad as a standard mouse it seems (I don't have
multitouch functionality, so no two-finger scrolling, etc).

$ xinput list
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ Logitech MX Masterid=10   [slave  pointer  (2)]
⎜   ↳ Logitech K800 id=11   [slave  pointer  (2)]
⎜   ↳ PS/2 Synaptics TouchPad   id=14   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Sleep Button  id=8[slave  keyboard (3)]
↳ Jabra Link 370id=9[slave  keyboard (3)]
↳ Integrated Camera: Integrated C   id=12   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=13   [slave  keyboard (3)]
↳ ThinkPad Extra Buttonsid=15   [slave  keyboard (3)]
↳ Logitech MX Masterid=16   [slave  keyboard (3)]
↳ Logitech K800 id=17   [slave  keyboard (3)]


As can be seen from this:
xinput --list-props 14
Device 'PS/2 Synaptics TouchPad':
Device Enabled (154):   1
Coordinate Transformation Matrix (156): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Natural Scrolling Enabled (290):   0
libinput Natural Scrolling Enabled Default (291):   0
libinput Scroll Methods Available (292):0, 0, 1
libinput Scroll Method Enabled (293):   0, 0, 1
libinput Scroll Method Enabled Default (294):   0, 0, 1
libinput Button Scrolling Button (295): 2
libinput Button Scrolling Button Default (296): 2
libinput Middle Emulation Enabled (297):0
libinput Middle Emulation Enabled Default (298):0
libinput Accel Speed (299): 0.00
libinput Accel Speed Default (300): 0.00
libinput Accel Profiles Available (301):1, 1
libinput Accel Profile Enabled (302):   1, 0
libinput Accel Profile Enabled Default (303):   1, 0
libinput Left Handed Enabled (304): 0
libinput Left Handed Enabled Default (305): 0
libinput Send Events Modes Available (275): 1, 0
libinput Send Events Mode Enabled (276):0, 0
libinput Send Events Mode Enabled Default (277):0, 0
Device Node (278):  "/dev/input/event8"
Device Product ID (279):2, 1
libinput Drag Lock Buttons (306):   
libinput Horizontal Scroll Enabled (307):   1


So for me the only viable workaround is still to use the nouveau-drivers

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

Title:
  Synaptic touchpad not responding in ubuntu 19.04  when using nvidia
  drivers

Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  
  On a Lenovo Thinkpad P50 with a Synaptics touchpad, the touchpad (or 
trackpoint), does not respond to any input after installing ubuntu 19.04.

  The same machine has been working fine with ubuntu 16.04 and 18.10. To
  be more correct it is still working in 16.04 hwe which I'm dual
  booting.

  If I uninstall the nvidia drivers (right now 418.56-0ubuntu1), and
  replace with noveau drivers it works just fine (by the way there seems
  to be no other issues with the nvidia driver as of yet).

  I have also the nvidia-driver-390 also suggested in the graphical
  software updates tool, to no avail.

  I will attach relevant logs. Please let me know if there is more I should 
supply.
  And thanks for all your hard (and brilliant) work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-libinput 0.28.2-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Adgang nægtet: '/var/log/boot.log'
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 20:36:18 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  InstallationDate: Installed on 2019-04-26 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b596 Chicony Electronics Co., Ltd 
   

[Desktop-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

[Jeremy Bicha]

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

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

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  Fix Released
Status in pango1.0 package in Debian:
  Unknown

Bug description:
  I just updated my machine, and when I did libpango1.0-0 was removed.
  This removed minecraft-launcher - the (very) popular launcher for
  Minecraft Java edition.

  I have reported this upstream, in case they can update their package
  https://bugs.mojang.com/browse/MCL-13512

  I am filing this bug so we can track it internally. I personally think
  this shouldn't have been done this late in the cycle, but there may
  well have been good reasons for it.

  As a result of the change though, it's now not possible to install
  Minecraft on Ubuntu 20.04.

  $ sudo apt install ./Minecraft\(1\).deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1863608] Re: version 80 does not start using remote display (X11)

[Uwe Mock]

There is a related bug in the Vivaldi forum. The command line argument
--no-xshm fixes the bug. And the bug seems to only affect the 64bit
version.

See:
https://forum.vivaldi.net/topic/42875/2-10-gives-totally-blank-window-on-remote-display/20?_=1586702697879

and

https://forum.vivaldi.net/topic/1/upgrade-from-2-10-to-2-11-gives-
uniform-yellow-root-window-ltsp5-setup-a-thin-client/16

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

Title:
  version 80 does not start using remote display (X11)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  chromium-browser version 80.0.3987.87-0ubuntu0.16.04.1_amd64 does not
  work when using remote display; the browser window is a solid pink
  area without any menu (see picture).

  Same with the (existing?) command line option "--disable-gpu"

  Downgrading to 
  chromium-browser_79.0.3945.130-0ubuntu0.16.04.1_amd64.deb
  chromium-browser-l10n_79.0.3945.130-0ubuntu0.16.04.1_all.deb
  chromium-codecs-ffmpeg-extra_79.0.3945.130-0ubuntu0.16.04.1_amd64.deb
  resolve the issue.

  Description: Ubuntu 16.04.6 LTS
  All packages are up to date on 2020-02-17 on xenial, xenial-updates and 
xenial-security

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1863608/+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 1872308] [NEW] wifi gets automatically disabled when screen is locked and can be enabled only after a reboot

[Sai Satvik Vuppala]

Public bug reported:

The wifi option gets automatically disabled when screen is locked and is
left unused for few hours and it can only be enabled once it is
rebooted.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
Uname: Linux 5.3.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 12 20:13:31 2020
InstallationDate: Installed on 2019-10-30 (164 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: gdm3
UpgradeStatus: Upgraded to eoan on 2020-02-16 (55 days ago)

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


** Tags: amd64 apport-bug eoan

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

Title:
  wifi gets automatically disabled when screen is locked and can be
  enabled only after a reboot

Status in gdm3 package in Ubuntu:
  New

Bug description:
  The wifi option gets automatically disabled when screen is locked and
  is left unused for few hours and it can only be enabled once it is
  rebooted.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 20:13:31 2020
  InstallationDate: Installed on 2019-10-30 (164 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to eoan on 2020-02-16 (55 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1872308/+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 1826597] Re: Synaptic touchpad not responding in ubuntu 19.04 when using nvidia drivers

[zob]

I though I might experiment a little. I installed xubuntu-desktop with the 
lightdm display manager. Didn't work either. Then I installed kubuntu-desktop 
with sddm display manger and the suddenly my touchpad started working.
I then did a dpkg-reconfigure gdm3, rebooted and logged back into the 
"standard" gnome session. And now my touchpad is working with the Nvidia 
drivers installed and working. I have no clue why but, to resume, there are 2 
workarounds:
1: use nouveau drivers instead of nvidia
2: install kubuntu-desktop (and log into ubuntu-desktop or whatever floats your 
boat).

This also indicates that it's "just" a config issue somewhere.

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

Title:
  Synaptic touchpad not responding in ubuntu 19.04  when using nvidia
  drivers

Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  
  On a Lenovo Thinkpad P50 with a Synaptics touchpad, the touchpad (or 
trackpoint), does not respond to any input after installing ubuntu 19.04.

  The same machine has been working fine with ubuntu 16.04 and 18.10. To
  be more correct it is still working in 16.04 hwe which I'm dual
  booting.

  If I uninstall the nvidia drivers (right now 418.56-0ubuntu1), and
  replace with noveau drivers it works just fine (by the way there seems
  to be no other issues with the nvidia driver as of yet).

  I have also the nvidia-driver-390 also suggested in the graphical
  software updates tool, to no avail.

  I will attach relevant logs. Please let me know if there is more I should 
supply.
  And thanks for all your hard (and brilliant) work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-libinput 0.28.2-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Adgang nægtet: '/var/log/boot.log'
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 20:36:18 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  InstallationDate: Installed on 2019-04-26 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b596 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 0458:0007 KYE Systems Corp. (Mouse Systems) 
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20EQS0PQ00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=21f288a0-da9c-46ea-8b64-056770908297 ro quiet splash 
synaptic_intertouch=0 vt.handoff=1
  SourcePackage: xserver-xorg-input-libinput
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET83W (1.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS0PQ00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EQS0PQ00:pvrThinkPadP50:rvnLENOVO:rn20EQS0PQ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EQS0PQ00
  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.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/xserver-xorg-input-libinput/+bug/1826597/+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 1868474] Re: Lenovo ThinkPad P73 touchpad does not work *after* installation

[AaronMa]

Please use hybrid GPU mode in BIOS.
Or use psmouse.elantech_smbus=0 as workaround for now.

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

Title:
  Lenovo ThinkPad P73 touchpad does not work *after* installation

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  The installation scripts loads the correct drivers so the touch pad
  and pointer works during the install. However after the install
  neither work.

  I've worked around it by using a wireless USB from Vilros for mouse input 
while logging in. Then issuing (found on 
https://askubuntu.com/questions/1143663):
   sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol'

  So it's a bug for me but one I can work around and should be fixed before 
20.04 goes live.
  --- 
  ProblemType: Bug
  .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-5ubuntu1)
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-14-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] 
(rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b]
  InstallationDate: Installed on 2020-03-21 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  MachineType: LENOVO 20QRCTO1WW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: xorg 1:7.7+19ubuntu14
  PackageArchitecture: amd64
  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-18-generic 
root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Tags:  focal ubuntu reproducible has-workaround
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2NET35W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40104 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P73
  dmi.product.name: 20QRCTO1WW
  dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73
  dmi.product.version: ThinkPad P73
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-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/linux/+bug/1868474/+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 1872302] [NEW] Bluetooth-Settings Connect button must be pressed multiple times to achieve connection

[Rob Frohne]

Public bug reported:

When connecting my headphones, I have to press the Connect button over
and over again before the connection finally takes place.  I am filing
this with gnome-bluetoooth, because with my Android phone, it works
flawlessly.  I took a screenshot of the page where this happens in the
settings and am including it here.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-bluetooth 3.34.1-1
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: ubuntu:GNOME
Date: Sun Apr 12 07:03:31 2020
InstallationDate: Installed on 2019-04-19 (359 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-bluetooth
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "bluetooth_not_connecting.png"
   
https://bugs.launchpad.net/bugs/1872302/+attachment/5352549/+files/bluetooth_not_connecting.png

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

Title:
  Bluetooth-Settings Connect button must be pressed multiple times to
  achieve connection

Status in gnome-bluetooth package in Ubuntu:
  New

Bug description:
  When connecting my headphones, I have to press the Connect button over
  and over again before the connection finally takes place.  I am filing
  this with gnome-bluetoooth, because with my Android phone, it works
  flawlessly.  I took a screenshot of the page where this happens in the
  settings and am including it here.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-bluetooth 3.34.1-1
  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: ubuntu:GNOME
  Date: Sun Apr 12 07:03:31 2020
  InstallationDate: Installed on 2019-04-19 (359 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1872302/+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 1868474] Re: Lenovo ThinkPad P73 touchpad does not work *after* installation

[zob]

Hi D.

Can you try uninstalling the nvidia-drivers from the "Additional
Drivers" interface, just by choosing the nouveau drivers. Then reboot.
Does the touchpad work now?

Then you might have a similar issue as I do on the P50:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1826597

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

Title:
  Lenovo ThinkPad P73 touchpad does not work *after* installation

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  The installation scripts loads the correct drivers so the touch pad
  and pointer works during the install. However after the install
  neither work.

  I've worked around it by using a wireless USB from Vilros for mouse input 
while logging in. Then issuing (found on 
https://askubuntu.com/questions/1143663):
   sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol'

  So it's a bug for me but one I can work around and should be fixed before 
20.04 goes live.
  --- 
  ProblemType: Bug
  .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-5ubuntu1)
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-14-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] 
(rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b]
  InstallationDate: Installed on 2020-03-21 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  MachineType: LENOVO 20QRCTO1WW
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: xorg 1:7.7+19ubuntu14
  PackageArchitecture: amd64
  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-18-generic 
root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 
quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Tags:  focal ubuntu reproducible has-workaround
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2NET35W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40104 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P73
  dmi.product.name: 20QRCTO1WW
  dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73
  dmi.product.version: ThinkPad P73
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-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/linux/+bug/1868474/+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 1872298] [NEW] No permission to access files on storage device

[Ivan Shkarbut]

Public bug reported:

1. Insert an encrypted flash drive (by cryptsetup)
2. Enter the password
Expected result - get access to files
Actual result - Error message: Failed to open directory "fleshka"
Error opening directory '/media/xubuntu/fleshka':Permission denied

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: udisks2 2.8.4-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: XFCE
Date: Sun Apr 12 12:51:39 2020
LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411)
MachineType: Acer Aspire 5734Z
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash --- maybe-ubiquity
SourcePackage: udisks2
Symptom: storage
Title: No permission to access files on storage device
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/16/2010
dmi.bios.vendor: Acer
dmi.bios.version: V1.01
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Aspire 5734Z
dmi.board.vendor: Acer
dmi.board.version: V1.01
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.01
dmi.modalias: 
dmi:bvnAcer:bvrV1.01:bd04/16/2010:svnAcer:pnAspire5734Z:pvrV1.01:rvnAcer:rnAspire5734Z:rvrV1.01:cvnAcer:ct10:cvrV1.01:
dmi.product.family: Intel_Mobile
dmi.product.name: Aspire 5734Z
dmi.product.sku: Montevina_Fab
dmi.product.version: V1.01
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug focal

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

Title:
  No permission to access files on storage device

Status in udisks2 package in Ubuntu:
  New

Bug description:
  1. Insert an encrypted flash drive (by cryptsetup)
  2. Enter the password
  Expected result - get access to files
  Actual result - Error message: Failed to open directory "fleshka"
  Error opening directory '/media/xubuntu/fleshka':Permission denied

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udisks2 2.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CurrentDesktop: XFCE
  Date: Sun Apr 12 12:51:39 2020
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411)
  MachineType: Acer Aspire 5734Z
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash --- maybe-ubiquity
  SourcePackage: udisks2
  Symptom: storage
  Title: No permission to access files on storage device
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2010
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.01
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5734Z
  dmi.board.vendor: Acer
  dmi.board.version: V1.01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.01
  dmi.modalias: 
dmi:bvnAcer:bvrV1.01:bd04/16/2010:svnAcer:pnAspire5734Z:pvrV1.01:rvnAcer:rnAspire5734Z:rvrV1.01:cvnAcer:ct10:cvrV1.01:
  dmi.product.family: Intel_Mobile
  dmi.product.name: Aspire 5734Z
  dmi.product.sku: Montevina_Fab
  dmi.product.version: V1.01
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1872298/+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 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)

[Tim Richardson]

I installed 20.04 beta on a usb drive on the same machine, and reinstalled 
packages to resemble my main install as closely as possible. The bug does not 
occur when booting from the usb drive. 
The most significant difference I can think of is that the main install is on 
an lvm partition (unencrypted).

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

Title:
  booting with splash hangs when external monitors are connected (pure
  intel 8th gen laptop)

Status in plymouth package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  I think this is a problem with the splash boot loader. This problem is
  not reproduced if using nosplash.

  I have installed 20.04 to this laptop. Thinkpad T480, i7, intel
  graphics.

  Clean install of 20.04 beta, not an upgrade.
  When booting from the install, the greeter screen is never reached if 
external monitors are connected at startup.
  I get the spinning ubuntu logo, and nothing more. I can not change to virtual 
terminals. The fsck step does not commence.

  In recovery mood, I can log in.

  With no external monitors attached, it works.

  I am used to having such problems with Nvidia graphics is involved,
  but this is not the case on this laptop. It has been happily running
  18.04.

  External displays are recognised if they are connected after login.

  Also, when I edit /etc/default/grub so that it reads
  GRUB_CMDLINE_LINUX_DEFAULT=""
  (that is, splash disabled)
  it works fine with two external monitors attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 11 13:58:19 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
  InstallationDate: Installed on 2020-04-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: LENOVO 20L5S00F00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/myvg-root ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5S00F00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5S00F00
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-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/plymouth/+bug/1872159/+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 1603324] Re: file-roller crashed with SIGSEGV in confirmation_dialog_response()

[Apport retracing service]

** Tags added: focal

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

Title:
  file-roller crashed with SIGSEGV in confirmation_dialog_response()

Status in file-roller package in Ubuntu:
  Confirmed

Bug description:
  Error after unzip a file. It seems to have unzipped it correctly
  though

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: file-roller 3.20.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
  Uname: Linux 4.4.0-30-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 15 14:53:45 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/file-roller
  InstallationDate: Installed on 2012-11-25 (1328 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627)
  ProcCmdline: file-roller --extract-here --notify 
file:///home/username/aaa/bbb/ccc/ddd.zip 
file:///home/username/aaa/bbb/ccc/eee.zip
  ProcEnviron:
   LANGUAGE=en_SG:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_SG.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: file-roller
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: file-roller crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to yakkety on 2015-03-14 (488 days ago)
  UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo 
vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1603324/+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 1872294] Re: file-roller crashed with SIGSEGV in g_closure_invoke()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1603324, so 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.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1872294/+attachment/5352495/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1872294/+attachment/5352497/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1872294/+attachment/5352501/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1872294/+attachment/5352502/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1872294/+attachment/5352503/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1872294/+attachment/5352504/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1872294/+attachment/5352505/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1603324
   file-roller crashed with SIGSEGV in confirmation_dialog_response()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  file-roller crashed with SIGSEGV in g_closure_invoke()

Status in file-roller package in Ubuntu:
  New

Bug description:
  Selecting multiple rar files to "extract here" produces multiple pop-
  ups informing that extraction has been completed; dismissing the
  second one causes file-roller to crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: file-roller 3.36.1-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 13:40:35 2020
  ExecutablePath: /usr/bin/file-roller
  InstallationDate: Installed on 2020-04-05 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: file-roller --extract-here --notify 
file:///home/username/Downloads/bx/IT/R%20Data%20Analysis%20Cookbook%202nd%20Edition%20(2017).rar
 
file:///home/username/Downloads/bx/IT/R%20Data%20Visualization%20Recipes%20(2017).rar
 
file:///home/username/Downloads/bx/IT/Security%20Tokens%20and%20Stablecoins%20Quick%20Start%20Guide%20-%20Learn%20how%20to%20build%20STO%20and%20stablecoin%20decentralized%20applications%20(2019).rar
  SegvAnalysis:
   Segfault happened at: 0x565215c7a647:mov0x1e0(%rax),%r12
   PC (0x565215c7a647) ok
   source "0x1e0(%rax)" (0x01e0) not located in a known VMA region (needed 
readable region)!
   destination "%r12" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: file-roller
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: file-roller crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1872294/+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 1826597] Re: Synaptic touchpad not responding in ubuntu 19.04 when using nvidia drivers

[zob]

I just tested installing the Nvidia binaries directly from the web-site. That 
did not fix the issue with the non-functional touchpad either.
That was the driver version 440.82

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

Title:
  Synaptic touchpad not responding in ubuntu 19.04  when using nvidia
  drivers

Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  
  On a Lenovo Thinkpad P50 with a Synaptics touchpad, the touchpad (or 
trackpoint), does not respond to any input after installing ubuntu 19.04.

  The same machine has been working fine with ubuntu 16.04 and 18.10. To
  be more correct it is still working in 16.04 hwe which I'm dual
  booting.

  If I uninstall the nvidia drivers (right now 418.56-0ubuntu1), and
  replace with noveau drivers it works just fine (by the way there seems
  to be no other issues with the nvidia driver as of yet).

  I have also the nvidia-driver-390 also suggested in the graphical
  software updates tool, to no avail.

  I will attach relevant logs. Please let me know if there is more I should 
supply.
  And thanks for all your hard (and brilliant) work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-libinput 0.28.2-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Adgang nægtet: '/var/log/boot.log'
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 20:36:18 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  InstallationDate: Installed on 2019-04-26 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b596 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 0458:0007 KYE Systems Corp. (Mouse Systems) 
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20EQS0PQ00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=21f288a0-da9c-46ea-8b64-056770908297 ro quiet splash 
synaptic_intertouch=0 vt.handoff=1
  SourcePackage: xserver-xorg-input-libinput
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET83W (1.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS0PQ00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EQS0PQ00:pvrThinkPadP50:rvnLENOVO:rn20EQS0PQ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EQS0PQ00
  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.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/xserver-xorg-input-libinput/+bug/1826597/+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 1863097] Re: apparmor messages for libreoffice about mesa

[dinar qurbanov]

i added to usr.lib.libreoffice.program.soffice.bin:
/usr/share/drirc.d/*r,
owner @{HOME}/.cache/mesa_shader_cache/**rw,

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

Title:
  apparmor messages for libreoffice about mesa

Status in libreoffice package in Ubuntu:
  New

Bug description:
  i started today an empty libreoffice writer and see 5 messages of this
  type:

  Feb 13 15:33:04 dinar-Lenovo-G580 kernel: [14684.517380] audit:
  type=1400 audit(1581597184.725:87): apparmor="ALLOWED"
  operation="open" profile="libreoffice-soffice"
  name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=8830
  comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000
  ouid=0

  several days ago i started it by clicking a document, and together
  with these messages there also was one this:

  Feb  6 20:47:08 dinar-Lenovo-G580 kernel: [104275.544663] audit:
  type=1400 audit(1581011228.808:876): apparmor="ALLOWED"
  operation="open" profile="libreoffice-soffice"
  name="/home/dinar/.cache/mesa_shader_cache/index" pid=15667
  comm="soffice.bin" requested_mask="wrc" denied_mask="wrc" fsuid=1000
  ouid=1000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1863097/+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 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

[Marcos R. Tosetti]

I have the same issue. Everything was working fine on 18.04, it only
stopped working after upgrading to 20.04. My phone (Android) can see the
wifi network (hotspot), it connects to it, it says it is connected but
there is no internet. I tried many different configurations, different
software, but nothing worked.

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a machine with a wired network connection and a wifi card. I've
  been using the machine as a wireless router and server in my house.
  I've attached a screenshot of the Wi-Fi network settings. It looks as
  expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  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-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359/+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 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

[Launchpad Bug Tracker]

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

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

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a machine with a wired network connection and a wifi card. I've
  been using the machine as a wireless router and server in my house.
  I've attached a screenshot of the Wi-Fi network settings. It looks as
  expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  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-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359/+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 1826597] Re: Synaptic touchpad not responding in ubuntu 19.04 when using nvidia drivers

[zob]

Yes. This is still an issue on the P50, same machine as above.
Now on kernel: 5.4.0-21-generic
xserver-xorg-input-libinput v. 0.29.0-1

And I've tested with the 3 different Nvidia drivers listed in the additional 
drivers interface.
That would be nvidia-drivers:
440.64-0ubuntu3
435.21-0ubuntu7
390.132-0ubuntu2

As before, touchpad and trackpoint work just fine with noveau drivers
and mesa.

If you have this error @Simon and @Nikolay, please choose the "This bug
affects me" at the top of the page.

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

Title:
  Synaptic touchpad not responding in ubuntu 19.04  when using nvidia
  drivers

Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  
  On a Lenovo Thinkpad P50 with a Synaptics touchpad, the touchpad (or 
trackpoint), does not respond to any input after installing ubuntu 19.04.

  The same machine has been working fine with ubuntu 16.04 and 18.10. To
  be more correct it is still working in 16.04 hwe which I'm dual
  booting.

  If I uninstall the nvidia drivers (right now 418.56-0ubuntu1), and
  replace with noveau drivers it works just fine (by the way there seems
  to be no other issues with the nvidia driver as of yet).

  I have also the nvidia-driver-390 also suggested in the graphical
  software updates tool, to no avail.

  I will attach relevant logs. Please let me know if there is more I should 
supply.
  And thanks for all your hard (and brilliant) work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-libinput 0.28.2-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Adgang nægtet: '/var/log/boot.log'
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 20:36:18 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  InstallationDate: Installed on 2019-04-26 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b596 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 0458:0007 KYE Systems Corp. (Mouse Systems) 
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20EQS0PQ00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=21f288a0-da9c-46ea-8b64-056770908297 ro quiet splash 
synaptic_intertouch=0 vt.handoff=1
  SourcePackage: xserver-xorg-input-libinput
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET83W (1.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS0PQ00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EQS0PQ00:pvrThinkPadP50:rvnLENOVO:rn20EQS0PQ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EQS0PQ00
  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.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/xserver-xorg-input-libinput/+bug/1826597/+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 1872289] [NEW] Printer is Rady and has a job in queue but does not print

[Aleksandar]

Public bug reported:

.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.7
ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 12 13:05:24 2020
InstallationDate: Installed on 2019-12-08 (125 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Lpstat: device for HP-LaserJet-Pro-MFP-M125a: 
usb://HP/LaserJet%20Pro%20MFP%20M125a?serial=CNB6H97FLN=1
MachineType: HP HP Laptop 15-db1xxx
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-LaserJet-Pro-MFP-M125a.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-LaserJet-Pro-MFP-M125a.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=3bc8529f-571b-4178-b2b7-86c77fd3128f ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/27/2019
dmi.bios.vendor: Insyde
dmi.bios.version: F.12
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 85EA
dmi.board.vendor: HP
dmi.board.version: 51.16
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.12:bd06/27/2019:svnHP:pnHPLaptop15-db1xxx:pvrType1ProductConfigId:rvnHP:rn85EA:rvr51.16:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 15-db1xxx
dmi.product.sku: 8KP03EA#BED
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apparmor apport-bug bionic

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

Title:
  Printer is Rady and has a job in queue but does not print

Status in cups package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.7
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 13:05:24 2020
  InstallationDate: Installed on 2019-12-08 (125 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lpstat: device for HP-LaserJet-Pro-MFP-M125a: 
usb://HP/LaserJet%20Pro%20MFP%20M125a?serial=CNB6H97FLN=1
  MachineType: HP HP Laptop 15-db1xxx
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-LaserJet-Pro-MFP-M125a.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-LaserJet-Pro-MFP-M125a.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=3bc8529f-571b-4178-b2b7-86c77fd3128f ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.12
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 85EA
  dmi.board.vendor: HP
  dmi.board.version: 51.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.12:bd06/27/2019:svnHP:pnHPLaptop15-db1xxx:pvrType1ProductConfigId:rvnHP:rn85EA:rvr51.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-db1xxx
  dmi.product.sku: 8KP03EA#BED
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1872289/+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 1872287] [NEW] I'm getting CPU freezing issues.

[vivek gangwar]

Public bug reported:

The bugs are related to CSGO, getting fps drops after few minutes of
usage.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-46-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  430.50  Thu Sep  5 22:36:31 
CDT 2019
 GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 12 16:23:27 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 acpi-call, 1.1.0, 5.3.0-46-generic, x86_64: installed
 nvidia, 430.50, 5.3.0-46-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:15e0]
   Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:15e0]
InstallationDate: Installed on 2020-04-10 (1 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
MachineType: ASUSTeK COMPUTER INC. GL553VD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=e042896c-2375-42c9-9d7d-2af9ed9e2121 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/02/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL553VD.306
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL553VD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: GL
dmi.product.name: GL553VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  I'm getting CPU freezing issues.

Status in xorg package in Ubuntu:
  New

Bug description:
  The bugs are related to CSGO, getting fps drops after few minutes of
  usage.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-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  430.50  Thu Sep  5 22:36:31 
CDT 2019
   GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 16:23:27 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.3.0-46-generic, x86_64: installed
   nvidia, 430.50, 5.3.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:15e0]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:15e0]
  InstallationDate: 

[Desktop-packages] [Bug 1870776] Re: No smooth scrolling on Firefox (and Chrome)

[Launchpad Bug Tracker]

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

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

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

Title:
  No smooth scrolling on Firefox (and Chrome)

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  I'm on Ubuntu Beta 20.04 and I observe that smooth scrolling is not
  working in Firefox or Chrome, while it works well in other apps, like
  Nautilus/Files GNOME settings or within GNOME shell applications
  listing.

  I tried with Firefox in safe mode (so without any extension) with the
  same result. I also tried with a completely new GNOME user account
  (without any customization), with the same result. While I'm not so
  used to Chrome, it seems that smooth scrolling is not working with it
  either.

  Another test I did is to boot from a Fedora Workstation 32 Beta USB
  stick (with GNOME) and the smooth scrolling was working well in
  Firefox.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1870776/+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 1872286] [NEW] gio - cifs mount smb not possible "Location is not mountable"

[Dirk Heumann]

Public bug reported:

1) Release
$ lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04

2) Package
$ apt-cache policy libglib2.0-bin
libglib2.0-bin:
  Installed: 2.64.1-1
  Candidate: 2.64.1-1
  Version table:
 *** 2.64.1-1 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

3) Expected to happen
The path should be mounted at
/run/user/1000/gvfs/smb-share:server=192.168.178.1,share=PathName/

4) What happened instead:
Error Message:
gio: smb://192.168.178.1/PathName/: Location is not mountable

5) Long description / explanation
Since some years, I mount a Windows drive with

gio mount smb://192.168.178.1/PathName

After upgrading from 19.04 to 20.04 beta, this does not work any more, I
get the error message

gio: smb://192.168.178.1/PathName/: Location is not mountable

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libglib2.0-bin 2.64.1-1
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: XFCE
Date: Sun Apr 12 12:43:53 2020
InstallationDate: Installed on 2019-02-17 (420 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: glib2.0
UpgradeStatus: Upgraded to focal on 2020-04-05 (7 days ago)

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  gio - cifs mount smb not possible "Location is not mountable"

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  1) Release
  $ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2) Package
  $ apt-cache policy libglib2.0-bin
  libglib2.0-bin:
Installed: 2.64.1-1
Candidate: 2.64.1-1
Version table:
   *** 2.64.1-1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) Expected to happen
  The path should be mounted at
  /run/user/1000/gvfs/smb-share:server=192.168.178.1,share=PathName/

  4) What happened instead:
  Error Message:
  gio: smb://192.168.178.1/PathName/: Location is not mountable

  5) Long description / explanation
  Since some years, I mount a Windows drive with

  gio mount smb://192.168.178.1/PathName

  After upgrading from 19.04 to 20.04 beta, this does not work any more,
  I get the error message

  gio: smb://192.168.178.1/PathName/: Location is not mountable

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-bin 2.64.1-1
  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: XFCE
  Date: Sun Apr 12 12:43:53 2020
  InstallationDate: Installed on 2019-02-17 (420 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: glib2.0
  UpgradeStatus: Upgraded to focal on 2020-04-05 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1872286/+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 1866070] Re: extension not compatible with gnome-shell 3.36 (Focal Fossa)

[Paride Legovini]

This bug has been fixed in version 31-1 of the package, now in Focal as
a Debian sync, so I'm marking it a Fix Released.

** Changed in: gnome-shell-extension-dash-to-panel (Ubuntu Focal)
   Status: Confirmed => Fix Released

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

Title:
  extension not compatible with gnome-shell 3.36 (Focal Fossa)

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell-extension-dash-to-panel package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Invalid
Status in gnome-shell-extension-dash-to-panel source package in Focal:
  Fix Released

Bug description:
  This extension is not working anymore with the latest version of
  gnome-shell available in Focal. Fixed upstream by:

  https://github.com/home-sweet-gnome/dash-to-
  panel/commit/32410a7e4178d871d6c799ad9da71d3614bdb9e9

  Error log:

  JS ERROR: Extension dash-to-pa...@jderose9.github.com: Error: second argument 
to Lang.bind() must be a function, not undefined
  bind@resource:///org/gnome/gjs/modules/lang.js:75:15
  
_init@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/appIcons.js:1593:43
  
C@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/utils.js 
line 76 > eval:1:52
  
_init@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/taskbar.js:195:37
  
C@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/utils.js 
line 76 > eval:1:52
  
enable@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/panel.js:260:24
  
_createPanel@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/panelManager.js:290:9
  
enable@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/panelManager.js:74:29
  
_enable@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/extension.js:94:5
  
enable@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/extension.js:62:5
  _callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:161:13
  loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:312:21
  _loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:545:13
  collectFromDatadirs@resource:///org/gnome/shell/misc/fileUtils.js:27:17
  _loadExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:520:9
  _enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:554:13
  _sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:585:13
  init@resource:///org/gnome/shell/ui/extensionSystem.js:55:9
  _initializeUI@resource:///org/gnome/shell/ui/main.js:245:5
  start@resource:///org/gnome/shell/ui/main.js:141:5
  @:1:31

  
  Usage of indicator.indicators is deprecated for Indicator
  get indicators@resource:///org/gnome/shell/ui/panelMenu.js:213:25
  
enable@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/panel.js:208:13
  
_createPanel@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/panelManager.js:290:9
  
enable@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/panelManager.js:74:29
  
_enable@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/extension.js:94:5
  
enable@/usr/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/extension.js:62:5
  _callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:161:13
  loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:312:21
  _loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:545:13
  collectFromDatadirs@resource:///org/gnome/shell/misc/fileUtils.js:27:17
  _loadExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:520:9
  _enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:554:13
  _sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:585:13
  init@resource:///org/gnome/shell/ui/extensionSystem.js:55:9
  _initializeUI@resource:///org/gnome/shell/ui/main.js:245:5
  start@resource:///org/gnome/shell/ui/main.js:141:5
  @:1:31

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866070/+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 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()

[Vikas Gill]

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

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

Title:
  gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from deep_count_more_files_callback()

Status in glib2.0 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec
  https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9

  ---

  Happened during normal use of the desktop.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 29 19:51:58 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  InstallationDate: Installed on 2020-01-25 (35 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax
   PC (0x7f5f54fa6444) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1865300/+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 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Ori Avtalion]

I'm seeing the "Could not install 'gconf2'" error during upgrade from
19.10 to the 20.04 beta.

The crash reports says the error is "dependency problems - leaving
triggers unprocessed"

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

Title:
  [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  During system upgrades, triggers for gconf2 might activate too early,
  while some of its dependencies aren't configured yet. This happens
  several times in a loop and stops the upgrade in the end.

  The attached debdiffs fix this issue by changing interest to interest-
  noawait in debian/gconf2.triggers file. The triggers will now activate
  near the end of upgrade.

  In addition, the debdiff for Bionic also contains a fix for FTBFS (bug
  1834211).

  [Test Case]

  Triggers for gconf2 are usually activated on changes in
  /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with
  GNOME) is most suitable for reproducing the issue. To reproduce it,
  install that edition, apply all updates, then try upgrading to the
  next release.

  [Regression Potential]

  None, interest-noawait trigger is known to work well in other packages
  (comment 31).

  [Other Info]

  Even if Cosmic goes EOL next month, the fix for it might be worth it
  for release upgrades.

  [Original Description]

  When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome.
  Notice that despite all warnings and errors, finally, the system remained 
functional.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+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 1872276] Re: Gnome shell huge app's icon size in the app folder

[keshavbhatt]

This bug is not related to the title issue, thats a seperate bug.

This is about the size of app icons in the apps thats are grouped
together using app folder. Their size is far bigger than the other apps
which are not grouped. This is UI/UX bug nothing serious. If one want to
focus on UI/UX this must probably be fixed.

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

Title:
  Gnome shell huge app's icon size in the app folder

Status in gnome-shell package in Ubuntu:
  New

Bug description:

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

  Bug: Gnome shell while opening app folder created in app launcher, the
  resulting dialog holding apps of app folder are having icon size
  larger than the other apps shown in the app launcher.

  How to reproduce: 1- Click on 9 dots qt bottom corner of dash (the app 
launcher button), wait for the app grid to show up.
  2- Drag app icon to create apps folder.
  3- As the app folder gets created, click to open it and observe the size of 
app icons shown by the folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:48:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872276/+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 1869568] Re: Unlock takes a long time

[Roger Lipscombe]

This is proving to be really difficult to reproduce -- it's getting
slower (but really slowly) on my spare PC. The memory use for gnome-
shell is, essentially, static.

So: I sampled some perf data from the PC where it consistently happens
and threw up a flame graph.

It spends a bunch of time in 'clutter_actor_destroy' ->
'destroy_closure_array' -> 'handler_lookup'.

This suggests to me that some extension or other is registering a
handler for something multiple times, and not cleaning it up, which
means it takes longer and longer to iterate through the list of
handlers.

I'm gonna have a rummage through the source code to see which function
adds handlers, and then I'll attach a debugger to it to see if
something's leaking registered handlers.

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

Title:
  Unlock takes a long time

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I searched and found related bugs #1774188 and #1847566, but one of
  those is against 19.04, which is end-of-support, and the other was
  abandoned with no feedback from the OP. So, let's try again.

  When unlocking my screen, it takes progressively longer to unlock.
  After a fresh restart, it's pretty quick. After about a day, it takes
  about a second. After a longer period, it takes up to 5 seconds.

  When I press Enter at the lock screen to get to the password entry,
  the "wipe" effect commonly stalls as it gets near the top of the
  screen; not sure if this is related.

  After correctly entering my password, it takes several seconds before
  my desktop is visible. It's _there_, because moving the mouse around
  changes the mouse pointer according to what's under it (e.g. it turns
  into an I-bar on the Firefox search/address box and a finger icon on a
  link). It just takes several seconds to actually draw the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 11:10:07 2020
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-10 (78 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  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/1869568/+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 1872276] Re: Gnome shell huge app's icon size in the app folder

[Alan Pope  濾]

This seems somewhat dependent on the screen resolution.

At 1920x1080 (the most popular screen resolution) our default web browser is 
"Firefox Web br..."
At 1366x768 (the next most popular screen resolution) it's "Firefox W..."

It looks like the GNOME stock application names have been optimised for
this behaviour, being called short names like "Calendar", "Calculator",
"Terminal", "Settings", "Fonts" which fit beneath their icons.

Perhaps our stock .desktop files should be examined, and developers
encouraged to use shorter names. In 2020, does anyone on Linux really
not know that Firefox is a Web browser for example?

** Attachment added: "1366x768.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872276/+attachment/5352415/+files/1366x768.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/1872276

Title:
  Gnome shell huge app's icon size in the app folder

Status in gnome-shell package in Ubuntu:
  New

Bug description:

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

  Bug: Gnome shell while opening app folder created in app launcher, the
  resulting dialog holding apps of app folder are having icon size
  larger than the other apps shown in the app launcher.

  How to reproduce: 1- Click on 9 dots qt bottom corner of dash (the app 
launcher button), wait for the app grid to show up.
  2- Drag app icon to create apps folder.
  3- As the app folder gets created, click to open it and observe the size of 
app icons shown by the folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:48:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872276/+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 1872276] Re: Gnome shell huge app's icon size in the app folder

[Alan Pope  濾]

** Attachment added: "1920x1080.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872276/+attachment/5352416/+files/1920x1080.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/1872276

Title:
  Gnome shell huge app's icon size in the app folder

Status in gnome-shell package in Ubuntu:
  New

Bug description:

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

  Bug: Gnome shell while opening app folder created in app launcher, the
  resulting dialog holding apps of app folder are having icon size
  larger than the other apps shown in the app launcher.

  How to reproduce: 1- Click on 9 dots qt bottom corner of dash (the app 
launcher button), wait for the app grid to show up.
  2- Drag app icon to create apps folder.
  3- As the app folder gets created, click to open it and observe the size of 
app icons shown by the folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:48:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872276/+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 1872269] Re: Gnome Shell App Launch Grid random vertical navigation Buttons

[Alan Pope  濾]

Confirmed here on up to date 20.04

1) Click app launcher
2) Click a group
3) Click the page icon on the right
4) Click outside the group

Expected behaviour: Group closes

Actual behaviour: Additional pages are created, app grid zooms out
weirdly.

Video showing it: https://www.youtube.com/watch?v=tCnTXBzhU9s

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

Title:
  Gnome Shell App Launch Grid random vertical navigation Buttons

Status in gnome-shell package in Ubuntu:
  Confirmed

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

  Bug: Gnome shell while opening app drawer, shows random number of grid
  page navigation button on right side.

  How to reproduce: 1- Click on 9 dots at bottom corner of dash (the app 
launcher button), wait for the app grid to show up.
  2- Drag app icon to create apps folder.
  3- As the app folder gets created check the number of vertical navigation 
buttons on the right side, few of them are not clickable. And this wont get fix 
until you will restart the shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:09:23 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872269/+subscriptions

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

[Desktop-packages] [Bug 1872268] Re: Gnome Shell completely freezes Ubuntu 20.04

[keshavbhatt]

** Description changed:

- 
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  
  Bug: Gnome shell while opening app drawer, clicking on an app folder and
  clicking on the blank area freezes gnome shell and it makes the session
  completely unusable and non recoverable.
  
- How to reproduce:  1-open 9 dots on bottom corner of dash (the app
+ How to reproduce:  1- Click 9 dots on bottom corner of dash (the app
  launcher button), wait for the app grid to show up.
  
  2- Click on an app folder to open it.
  3- Click on the blank area outside of the opened folder dialog.
  4- Gnome shell gets freezes and never come back from this state, on both 
wayland session and x11 session.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:00:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Gnome Shell completely freezes Ubuntu 20.04

Status in gnome-shell package in Ubuntu:
  Confirmed

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:00:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872268/+subscriptions

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

[Desktop-packages] [Bug 1872269] Re: Gnome Shell App Launch Grid random vertical navigation Buttons

[Launchpad Bug Tracker]

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

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

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

Title:
  Gnome Shell App Launch Grid random vertical navigation Buttons

Status in gnome-shell package in Ubuntu:
  Confirmed

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

  Bug: Gnome shell while opening app drawer, shows random number of grid
  page navigation button on right side.

  How to reproduce: 1- Click on 9 dots at bottom corner of dash (the app 
launcher button), wait for the app grid to show up.
  2- Drag app icon to create apps folder.
  3- As the app folder gets created check the number of vertical navigation 
buttons on the right side, few of them are not clickable. And this wont get fix 
until you will restart the shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:09:23 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872269/+subscriptions

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

[Desktop-packages] [Bug 1872268] Re: Gnome Shell completely freezes Ubuntu 20.04

[Launchpad Bug Tracker]

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

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

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

Title:
  Gnome Shell completely freezes Ubuntu 20.04

Status in gnome-shell package in Ubuntu:
  Confirmed

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:00:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872268/+subscriptions

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

[Desktop-packages] [Bug 1872268] Re: Gnome Shell completely freezes Ubuntu 20.04

[Alan Pope  濾]

Reproduced this on up to date 20.04

1. Drag two icons into a group
2. Click group
3. Click group title
4. Click outside group title

Shell locks up

Video showing it: https://www.youtube.com/watch?v=7nqyHx0WMPY

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

Title:
  Gnome Shell completely freezes Ubuntu 20.04

Status in gnome-shell package in Ubuntu:
  Confirmed

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:00:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872268/+subscriptions

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

[Desktop-packages] [Bug 1872269] Re: Gnome Shell App Launch Grid random vertical navigation Buttons

[keshavbhatt]

** Description changed:

- 
  Description: Ubuntu Focal Fossa (development branch)
  Release: 20.04
  
  Bug: Gnome shell while opening app drawer, shows random number of grid
  page navigation button on right side.
  
- How to reproduce: 1-open 9 dots on bottom corner of dash (the app launcher 
button), wait for the app grid to show up.
+ How to reproduce: 1- Click on 9 dots at bottom corner of dash (the app 
launcher button), wait for the app grid to show up.
  2- Drag app icon to create apps folder.
  3- As the app folder gets created check the number of vertical navigation 
buttons on the right side, few of them are not clickable. And this wont get fix 
until you will restart the shell.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:09:23 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Gnome Shell App Launch Grid random vertical navigation Buttons

Status in gnome-shell package in Ubuntu:
  Confirmed

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

  Bug: Gnome shell while opening app drawer, shows random number of grid
  page navigation button on right side.

  How to reproduce: 1- Click on 9 dots at bottom corner of dash (the app 
launcher button), wait for the app grid to show up.
  2- Drag app icon to create apps folder.
  3- As the app folder gets created check the number of vertical navigation 
buttons on the right side, few of them are not clickable. And this wont get fix 
until you will restart the shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:09:23 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872269/+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 1872269] Re: Gnome Shell App Launch Grid random vertical navigation Buttons

[keshavbhatt]

** Description changed:

- Am on latest version of Ubuntu 20.04 and gnome shell is completely  un-
- usable due to random crashes and glitches everywhere.
  
  Description: Ubuntu Focal Fossa (development branch)
  Release: 20.04
  
  Bug: Gnome shell while opening app drawer, shows random number of grid
  page navigation button on right side.
  
  How to reproduce: 1-open 9 dots on bottom corner of dash (the app launcher 
button), wait for the app grid to show up.
  2- Drag app icon to create apps folder.
  3- As the app folder gets created check the number of vertical navigation 
buttons on the right side, few of them are not clickable. And this wont get fix 
until you will restart the shell.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:09:23 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Gnome Shell App Launch Grid random vertical navigation Buttons

Status in gnome-shell package in Ubuntu:
  New

Bug description:

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

  Bug: Gnome shell while opening app drawer, shows random number of grid
  page navigation button on right side.

  How to reproduce: 1-open 9 dots on bottom corner of dash (the app launcher 
button), wait for the app grid to show up.
  2- Drag app icon to create apps folder.
  3- As the app folder gets created check the number of vertical navigation 
buttons on the right side, few of them are not clickable. And this wont get fix 
until you will restart the shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:09:23 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872269/+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 1872275] Re: Gnome shell App grid, App Icon selector padding and indicator position

[keshavbhatt]

** Description changed:

- Am on latest version of Ubuntu 20.04 and gnome shell is completely  un-
- usable due to random crashes and glitches everywhere.
  
  Description: Ubuntu Focal Fossa (development branch)
  Release: 20.04
  
  Bug: This bug is an UI which is blocking the text from visual sight of
  user and hence producing a bad User experience.
  
- 
- Steps to reproduce: 
+ Steps to reproduce:
  
  1- Click on 9 dots at bottom corner of dash (the app launcher button), wait 
for the app grid to show up.
  2- Notice any app icon carefully and observe if it is showing up similar to 
what i have attached in the screenshot in this bug.
  
- Things to notice: 
+ Things to notice:
  (a) Bottom padding of icon selector (not equal to the top one).
  (b) Position of the orange indicator which shows that an instance of app is 
running.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:28:41 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Gnome shell App grid, App Icon selector padding and indicator position

Status in gnome-shell package in Ubuntu:
  New

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

  Bug: This bug is an UI which is blocking the text from visual sight of
  user and hence producing a bad User experience.

  Steps to reproduce:

  1- Click on 9 dots at bottom corner of dash (the app launcher button), wait 
for the app grid to show up.
  2- Notice any app icon carefully and observe if it is showing up similar to 
what i have attached in the screenshot in this bug.

  Things to notice:
  (a) Bottom padding of icon selector (not equal to the top one).
  (b) Position of the orange indicator which shows that an instance of app is 
running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:28:41 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872275/+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 1872278] [NEW] Gnome shell app name/title is elided too much on right and is not readable

[keshavbhatt]

Public bug reported:

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

Bug: Gnome shell's default app launcher UI/UX issue -  App title in app
grid is elided too much and is not readable.

How to reproduce:
1- Click on 9 dots at bottom corner of dash (the app launcher button), wait for 
the app grid to show up.
2- Read try to observe the title of some applications. (Check screenshot for 
more).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-4ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 12 13:10:24 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-04-11 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot from 2020-04-12 13-49-35.png"
   
https://bugs.launchpad.net/bugs/1872278/+attachment/5352408/+files/Screenshot%20from%202020-04-12%2013-49-35.png

** Description changed:

- Am on latest version of Ubuntu 20.04 and gnome shell is completely
- unusable due to random crashes and glitches everywhere.
- 
  Description: Ubuntu Focal Fossa (development branch)
  Release: 20.04
  
  Bug: Gnome shell's default app launcher UI/UX issue -  App title in app
  grid is elided too much and is not readable.
  
  How to reproduce:
  1- Click on 9 dots at bottom corner of dash (the app launcher button), wait 
for the app grid to show up.
  2- Read try to observe the title of some applications. (Check screenshot for 
more).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 13:10:24 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Gnome shell app name/title is elided too much on right and is not
  readable

Status in gnome-shell package in Ubuntu:
  New

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

  Bug: Gnome shell's default app launcher UI/UX issue -  App title in
  app grid is elided too much and is not readable.

  How to reproduce:
  1- Click on 9 dots at bottom corner of dash (the app launcher button), wait 
for the app grid to show up.
  2- Read try to observe the title of some applications. (Check screenshot for 
more).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 13:10:24 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872278/+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 1872270] Re: Inconsistent Gnome shell App grid Icon size

[keshavbhatt]

** Description changed:

- Am on latest version of Ubuntu 20.04 and gnome shell is completely
- unusable due to random crashes and glitches everywhere.
  
  Description: Ubuntu Focal Fossa (development branch)
  Release: 20.04
  
  Bug: Gnome shell starts showing inconsistency in app icon sizes as i use
  it.
  
  How to reproduce: 1- Click on 9 dots on bottom corner of dash (the app 
launcher button), wait for the app grid to show up.
  2- Drag app icon to create apps folder.
  3- As the app folder gets created, click on it to open it.
  4- Click outside the app folder dialog.
  5- Gnome shell will either crash,or it will freeze, or if it doesn't it will 
resize the app icon size in launcher, or will completely hide the launcher.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:20:21 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Inconsistent Gnome shell App grid Icon size

Status in gnome-shell package in Ubuntu:
  New

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

  Bug: Gnome shell starts showing inconsistency in app icon sizes as i
  use it.

  How to reproduce: 1- Click on 9 dots on bottom corner of dash (the app 
launcher button), wait for the app grid to show up.
  2- Drag app icon to create apps folder.
  3- As the app folder gets created, click on it to open it.
  4- Click outside the app folder dialog.
  5- Gnome shell will either crash,or it will freeze, or if it doesn't it will 
resize the app icon size in launcher, or will completely hide the launcher.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:20:21 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872270/+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 1872276] Re: Gnome shell huge app's icon size in the app folder

[keshavbhatt]

** Description changed:

- Am on latest version of Ubuntu 20.04 and gnome shell is completely
- unusable due to random crashes and glitches everywhere.
  
  Description: Ubuntu Focal Fossa (development branch)
  Release: 20.04
  
  Bug: Gnome shell while opening app folder created in app launcher, the
  resulting dialog holding apps of app folder are having icon size larger
  than the other apps shown in the app launcher.
  
  How to reproduce: 1- Click on 9 dots qt bottom corner of dash (the app 
launcher button), wait for the app grid to show up.
  2- Drag app icon to create apps folder.
  3- As the app folder gets created, click to open it and observe the size of 
app icons shown by the folder.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:48:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Gnome shell huge app's icon size in the app folder

Status in gnome-shell package in Ubuntu:
  New

Bug description:

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

  Bug: Gnome shell while opening app folder created in app launcher, the
  resulting dialog holding apps of app folder are having icon size
  larger than the other apps shown in the app launcher.

  How to reproduce: 1- Click on 9 dots qt bottom corner of dash (the app 
launcher button), wait for the app grid to show up.
  2- Drag app icon to create apps folder.
  3- As the app folder gets created, click to open it and observe the size of 
app icons shown by the folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:48:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872276/+subscriptions

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

[Desktop-packages] [Bug 1872268] Re: Gnome Shell completely freezes Ubuntu 20.04

[keshavbhatt]

** Description changed:

- Am on latest version of Ubuntu 20.04 and gnome-shell is completely
- unusable due to random crashes and glitches everywhere.
  
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  
  Bug: Gnome shell while opening app drawer, clicking on an app folder and
  clicking on the blank area freezes gnome shell and it makes the session
  completely unusable and non recoverable.
  
  How to reproduce:  1-open 9 dots on bottom corner of dash (the app
  launcher button), wait for the app grid to show up.
  
  2- Click on an app folder to open it.
  3- Click on the blank area outside of the opened folder dialog.
  4- Gnome shell gets freezes and never come back from this state, on both 
wayland session and x11 session.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:00:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Gnome Shell completely freezes Ubuntu 20.04

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:00:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872268/+subscriptions

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

[Desktop-packages] [Bug 1872276] [NEW] Gnome shell huge app's icon size in the app folder

[keshavbhatt]

Public bug reported:

Am on latest version of Ubuntu 20.04 and gnome shell is completely
unusable due to random crashes and glitches everywhere.

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

Bug: Gnome shell while opening app folder created in app launcher, the
resulting dialog holding apps of app folder are having icon size larger
than the other apps shown in the app launcher.

How to reproduce: 1- Click on 9 dots qt bottom corner of dash (the app launcher 
button), wait for the app grid to show up.
2- Drag app icon to create apps folder.
3- As the app folder gets created, click to open it and observe the size of app 
icons shown by the folder.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-4ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 12 12:48:05 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-04-11 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Gnome shell huge app's icon size in the app folder

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Am on latest version of Ubuntu 20.04 and gnome shell is completely
  unusable due to random crashes and glitches everywhere.

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

  Bug: Gnome shell while opening app folder created in app launcher, the
  resulting dialog holding apps of app folder are having icon size
  larger than the other apps shown in the app launcher.

  How to reproduce: 1- Click on 9 dots qt bottom corner of dash (the app 
launcher button), wait for the app grid to show up.
  2- Drag app icon to create apps folder.
  3- As the app folder gets created, click to open it and observe the size of 
app icons shown by the folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:48:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872276/+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 1872275] Re: Gnome shell App grid, App Icon selector padding and indicator position

[keshavbhatt]

Screenshot to understand the bug's point (b).

** Attachment added: "k.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872275/+attachment/5352398/+files/k.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/1872275

Title:
  Gnome shell App grid, App Icon selector padding and indicator position

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Am on latest version of Ubuntu 20.04 and gnome shell is completely
  un-usable due to random crashes and glitches everywhere.

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

  Bug: This bug is an UI which is blocking the text from visual sight of
  user and hence producing a bad User experience.

  
  Steps to reproduce: 

  1- Click on 9 dots at bottom corner of dash (the app launcher button), wait 
for the app grid to show up.
  2- Notice any app icon carefully and observe if it is showing up similar to 
what i have attached in the screenshot in this bug.

  Things to notice: 
  (a) Bottom padding of icon selector (not equal to the top one).
  (b) Position of the orange indicator which shows that an instance of app is 
running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:28:41 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872275/+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 1872275] [NEW] Gnome shell App grid, App Icon selector padding and indicator position

[keshavbhatt]

Public bug reported:

Am on latest version of Ubuntu 20.04 and gnome shell is completely  un-
usable due to random crashes and glitches everywhere.

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

Bug: This bug is an UI which is blocking the text from visual sight of
user and hence producing a bad User experience.


Steps to reproduce: 

1- Click on 9 dots at bottom corner of dash (the app launcher button), wait for 
the app grid to show up.
2- Notice any app icon carefully and observe if it is showing up similar to 
what i have attached in the screenshot in this bug.

Things to notice: 
(a) Bottom padding of icon selector (not equal to the top one).
(b) Position of the orange indicator which shows that an instance of app is 
running.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-4ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 12 12:28:41 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-04-11 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Summary changed:

- Gnome shell App grid  app Icon selector padding 
+ Gnome shell App grid, App Icon selector padding and indicator position

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

Title:
  Gnome shell App grid, App Icon selector padding and indicator position

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Am on latest version of Ubuntu 20.04 and gnome shell is completely
  un-usable due to random crashes and glitches everywhere.

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

  Bug: This bug is an UI which is blocking the text from visual sight of
  user and hence producing a bad User experience.

  
  Steps to reproduce: 

  1- Click on 9 dots at bottom corner of dash (the app launcher button), wait 
for the app grid to show up.
  2- Notice any app icon carefully and observe if it is showing up similar to 
what i have attached in the screenshot in this bug.

  Things to notice: 
  (a) Bottom padding of icon selector (not equal to the top one).
  (b) Position of the orange indicator which shows that an instance of app is 
running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:28:41 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872275/+subscriptions

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

[Desktop-packages] [Bug 1792085] Re: Regression: MTP not working/very slow

[Karl Kastner]

I have a similar problem in 18.04, extremely slow mpt access to a Huawei
P20. Installation of libmtp9_1.1.17-2, libmtp-common_1.1.17-2 and
libmtp-runtime_1.1.17-2 did not result in any improvement.

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

Title:
  Regression: MTP not working/very slow

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

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

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

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

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

  That's all!

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions

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

[Desktop-packages] [Bug 1872270] [NEW] Inconsistent Gnome shell App grid Icon size

[keshavbhatt]

Public bug reported:

Am on latest version of Ubuntu 20.04 and gnome shell is completely
unusable due to random crashes and glitches everywhere.

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

Bug: Gnome shell starts showing inconsistency in app icon sizes as i use
it.

How to reproduce: 1- Click on 9 dots on bottom corner of dash (the app launcher 
button), wait for the app grid to show up.
2- Drag app icon to create apps folder.
3- As the app folder gets created, click on it to open it.
4- Click outside the app folder dialog.
5- Gnome shell will either crash,or it will freeze, or if it doesn't it will 
resize the app icon size in launcher, or will completely hide the launcher.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-4ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 12 12:20:21 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-04-11 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Inconsistent Gnome shell App grid Icon size

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Am on latest version of Ubuntu 20.04 and gnome shell is completely
  unusable due to random crashes and glitches everywhere.

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

  Bug: Gnome shell starts showing inconsistency in app icon sizes as i
  use it.

  How to reproduce: 1- Click on 9 dots on bottom corner of dash (the app 
launcher button), wait for the app grid to show up.
  2- Drag app icon to create apps folder.
  3- As the app folder gets created, click on it to open it.
  4- Click outside the app folder dialog.
  5- Gnome shell will either crash,or it will freeze, or if it doesn't it will 
resize the app icon size in launcher, or will completely hide the launcher.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:20:21 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872270/+subscriptions

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

[Desktop-packages] [Bug 1872268] Re: Gnome Shell completely freezes Ubuntu 20.04

[keshavbhatt]

** Description changed:

- Am on latest version of Ubuntu 20.04 and gnome-shell is completely un-
- usable due to random crashes and glitches everywhere.
+ Am on latest version of Ubuntu 20.04 and gnome-shell is completely
+ unusable due to random crashes and glitches everywhere.
  
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  
  Bug: Gnome shell while opening app drawer, clicking on an app folder and
  clicking on the blank area freezes gnome shell and it makes the session
  completely unusable and non recoverable.
  
  How to reproduce:  1-open 9 dots on bottom corner of dash (the app
  launcher button), wait for the app grid to show up.
  
  2- Click on an app folder to open it.
  3- Click on the blank area outside of the opened folder dialog.
  4- Gnome shell gets freezes and never come back from this state, on both 
wayland session and x11 session.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:00:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Gnome Shell completely freezes Ubuntu 20.04

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Am on latest version of Ubuntu 20.04 and gnome-shell is completely
  unusable due to random crashes and glitches everywhere.

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:00:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872268/+subscriptions

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

[Desktop-packages] [Bug 1872269] [NEW] Gnome Shell App Launch Grid random vertical navigation Buttons

[keshavbhatt]

Public bug reported:

Am on latest version of Ubuntu 20.04 and gnome shell is completely  un-
usable due to random crashes and glitches everywhere.

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

Bug: Gnome shell while opening app drawer, shows random number of grid
page navigation button on right side.

How to reproduce: 1-open 9 dots on bottom corner of dash (the app launcher 
button), wait for the app grid to show up.
2- Drag app icon to create apps folder.
3- As the app folder gets created check the number of vertical navigation 
buttons on the right side, few of them are not clickable. And this wont get fix 
until you will restart the shell.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-4ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 12 12:09:23 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-04-11 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Gnome Shell App Launch Grid random vertical navigation Buttons

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Am on latest version of Ubuntu 20.04 and gnome shell is completely
  un-usable due to random crashes and glitches everywhere.

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

  Bug: Gnome shell while opening app drawer, shows random number of grid
  page navigation button on right side.

  How to reproduce: 1-open 9 dots on bottom corner of dash (the app launcher 
button), wait for the app grid to show up.
  2- Drag app icon to create apps folder.
  3- As the app folder gets created check the number of vertical navigation 
buttons on the right side, few of them are not clickable. And this wont get fix 
until you will restart the shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:09:23 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872269/+subscriptions

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

[Desktop-packages] [Bug 1872268] [NEW] Gnome Shell completely freezes Ubuntu 20.04

[keshavbhatt]

Public bug reported:

Am on latest version of Ubuntu 20.04 and gnome-shell is completely un-
usable due to random crashes and glitches everywhere.

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

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

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

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

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-4ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 12 12:00:13 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-04-11 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Description changed:

- Am on latest version of Ubuntu 20.04 and gnome is completely not usable
- due to random crashes and glitches everywhere.
- 
+ Am on latest version of Ubuntu 20.04 and gnome-shell is completely un-
+ usable due to random crashes and glitches everywhere.
  
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  
- Bug: Gnome shell while opening app drawer, cilicking on an app folder
- and clicking on the blank area freezes gnome shell and it makes the
- session completely unusable and non recoverable.
+ Bug: Gnome shell while opening app drawer, clicking on an app folder and
+ clicking on the blank area freezes gnome shell and it makes the session
+ completely unusable and non recoverable.
  
  How to reproduce:  1-open 9 dots on bottom corner of dash (the app
  launcher button), wait for the app grid to show up.
  
  2- Click on an app folder to open it.
  3- Click on the blank area outside of the opened folder dialog.
  4- Gnome shell gets freezes and never come back from this state, on both 
wayland session and x11 session.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:00:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Gnome Shell completely freezes Ubuntu 20.04

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Am on latest version of Ubuntu 20.04 and gnome-shell is completely un-
  usable due to random crashes and glitches everywhere.

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:00:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about 

[Desktop-packages] [Bug 1867548] Re: Right Alt key is suddenly switched off after invoking Settings - Keyboard Shortcuts in Focal

[Gunnar Hjalmarsson]

If there is not enough time to fix this properly before release, can we
drop the whole thing for now?

I submitted a merge request which does that:

https://salsa.debian.org/gnome-team/gnome-control-
center/-/merge_requests/14

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

Title:
  Right Alt key is suddenly switched off after invoking Settings -
  Keyboard Shortcuts in Focal

Status in gnome-control-center:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-control-center source package in Focal:
  Confirmed

Bug description:
  As soon as the Keyboard Shortcuts tab window is invoked in the
  Settings Application, Right Alt key is switched off system-wide. This
  happens suddenly even without any action from the user - just simple
  invoking of the window is enough to break the settings.

  This obviously happens because of the new setting in the Keyboard
  Shortcuts appeared in focal: Alternate Characters Key. It sets Right
  Alt by default immediately as this window is opened. This setting
  doesn't have the Not Set option, so it is even not easy to switch back
  to the normal behavior. This setting can be unset only through the
  GNOME Tweaks application: Keyboard & Mouse - Additional Layout Options
  - Key to choose the 3rd level - uncheck the box Right Alt. But this is
  not a good workaround since the Alt key setting will be destroyed
  again as soon as Keyboard Shortcuts are visited in Settings next time.

  The reasonable workaround seems to be introduction an option Not Set
  in the setting Alternate Characters Key and making it default. This
  will fix this bug and will introduce a sane default value because not
  every keyboard layout has a third-option for the keys.

  This is quite significant UX flaw since nothing should be changed
  without explicit user action.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 15 22:33:08 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-04-25 (325 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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