[Desktop-packages] [Bug 1873164] [NEW] my Bug Report

[Hrishikesh Sathaye]

Public bug reported:

I am using Lenovo Ideapad D330 2 in 1 Laptop. It has Intel UHD Graphics
600. and its a touchscreen laptop. The Problem is i'm facing with g
sensor and screen orientation

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
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 16 11:08:58 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics 605 [17aa:39ff]
InstallationDate: Installed on 2020-04-16 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: LENOVO 81H3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=c7483622-a4a6-415a-9767-7aa10bb670db ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/30/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: 8NCN37WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0Q55724 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 32
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad D330-10IGM
dmi.modalias: 
dmi:bvnLENOVO:bvr8NCN37WW:bd10/30/2019:svnLENOVO:pn81H3:pvrLenovoideapadD330-10IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct32:cvrLenovoideapadD330-10IGM:
dmi.product.family: ideapad D330-10IGM
dmi.product.name: 81H3
dmi.product.sku: LENOVO_MT_81H3_BU_idea_FM_ideapad D330-10IGM
dmi.product.version: Lenovo ideapad D330-10IGM
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+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/1873164

Title:
  my Bug Report

Status in xorg package in Ubuntu:
  New

Bug description:
  I am using Lenovo Ideapad D330 2 in 1 Laptop. It has Intel UHD
  Graphics 600. and its a touchscreen laptop. The Problem is i'm facing
  with g sensor and screen orientation

  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 16 11:08:58 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 605 [17aa:39ff]
  InstallationDate: Installed on 2020-04-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: LENOVO 81H3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=c7483622-a4a6-415a-9767-7aa10bb670db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8NCN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55724 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 32
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad D330-10IGM
  dmi.modalias: 
dmi:bvnLENOVO:bvr8NCN37WW:bd10/30/2019:svnLENOVO:pn81H3:pvrLenovoideapadD330-10IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct32:cvrLenovoideapadD330-10IGM:
  dmi.product.family: ideapad D330-10IGM
  dmi.product.name: 81H3
  dmi.product.sku: LENOVO_MT_81H3_BU_idea_FM_ideapad D330-10IGM
  dmi.product.version: Lenovo ideapad D330-10IGM
  dmi.sys.vendor: LENOVO
  version.compiz: 

[Desktop-packages] [Bug 1868420] Re: File Operation Progress Display Pauses If Files Is Closed During An Active File Operation

[Treviño]

I suppose this is due to nautilus not sending signals anymore...

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

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

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

Title:
  File Operation Progress Display Pauses If Files Is Closed During An
  Active File Operation

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete
Status in nautilus package in Ubuntu:
  New

Bug description:
  Files (Nautilus) displays progress for things like file
  transfers/deletions/etc as a small progress bar as part of its icon in
  the Ubuntu Dock. However, if Files is closed, the progress bar freezes
  in place rather than tracking the actual file operation, which
  continues in the background as signaled by GNOME's notification. If
  you re-open Files during this time, the progress bar will update to
  the proper position and keep tracking, but stop once the window is
  closed again.

  Ubuntu 20.04 (development branch) running GNOME 3.36.

  An `inxi -Fxzc0`

  System:Kernel: 5.4.0-18-generic x86_64 bits: 64 compiler: gcc v: 9.2.1 
Desktop: Gnome 3.35.91 
 Distro: Ubuntu 20.04 LTS (Focal Fossa) 
  Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x 
serial:  
 UEFI: American Megatrends v: 5407 date: 12/31/2019 
  CPU:   Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP 
arch: Zen+ rev: 2 
 L2 cache: 4096 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 108792 
 Speed: 1377 MHz min/max: 1550/3400 MHz Core speeds (MHz): 1: 1374 
2: 1378 3: 1372 4: 1378 
 5: 1360 6: 1360 7: 3365 8: 1359 9: 1375 10: 1375 11: 1360 12: 1360 
13: 3398 14: 1360 
 15: 1377 16: 1378 
  Graphics:  Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] 
vendor: XFX Pine 
 driver: amdgpu v: kernel bus ID: 0c:00.0 
 Display: x11 server: X.Org 1.20.7 driver: amdgpu resolution: 
3840x1080~144Hz 
 OpenGL: renderer: AMD NAVI10 (DRM 3.35.0 5.4.0-18-generic LLVM 
9.0.1) v: 4.6 Mesa 20.0.0 
 direct render: Yes 
  Audio: Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / 
Z-Series] 
 driver: snd_hda_intel v: kernel bus ID: 09:00.0 
 Device-2: AMD Navi 10 HDMI Audio driver: snd_hda_intel v: kernel 
bus ID: 0c:00.1 
 Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: 
snd_hda_intel v: kernel 
 bus ID: 0e:00.3 
 Device-4: Logitech HD Pro Webcam C920 type: USB driver: 
snd-usb-audio,uvcvideo 
 bus ID: 3-1.3:3 
 Device-5: C-Media Blue Snowball type: USB driver: 
hid-generic,snd-usb-audio,usbhid 
 bus ID: 1-2:2 
 Device-6: Kingston HyperX Virtual Surround Sound type: USB 
 driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-9:5 
 Sound Server: ALSA v: k5.4.0-18-generic 
  Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
vendor: ASUSTeK 
 driver: r8169 v: kernel port: f000 bus ID: 04:00.0 
 IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac:  
  Drives:Local Storage: total: 6.82 TiB used: 483.31 GiB (6.9%) 
 ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB size: 
232.89 GiB 
 ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50 
size: 465.76 GiB 
 ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50 
size: 465.76 GiB 
 ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50 
size: 465.76 GiB 
 ID-5: /dev/sdd type: USB vendor: Western Digital model: WD 
easystore 2624 size: 4.55 TiB 
 ID-6: /dev/sde vendor: Western Digital model: WDS500G2B0A-00SM50 
size: 465.76 GiB 
 ID-7: /dev/sdf type: USB vendor: SanDisk model: Cruzer Glide 3.0 
size: 232.50 GiB 
  Partition: ID-1: / size: 223.52 GiB used: 50.52 GiB (22.6%) fs: btrfs dev: 
/dev/nvme0n1p3 
 ID-2: /boot size: 945.6 MiB used: 143.0 MiB (15.1%) fs: ext4 dev: 
/dev/nvme0n1p2 
 ID-3: /home size: 223.52 GiB used: 50.52 GiB (22.6%) fs: btrfs 
dev: /dev/nvme0n1p3 
 ID-4: swap-1 size: 7.46 GiB used: 4.2 MiB (0.1%) fs: swap dev: 
/dev/nvme0n1p4 
  Sensors:   System Temperatures: cpu: 30.1 C mobo: N/A gpu: amdgpu temp: 48 C 
 Fan Speeds (RPM): N/A gpu: amdgpu fan: 0 
  Info:  Processes: 511 Uptime: 21h 39m Memory: 31.36 GiB used: 4.79 GiB 
(15.3%) Init: systemd 
 runlevel: 5 Compilers: gcc: N/A Shell: bash v: 5.0.16 inxi: 3.0.38

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.2
  

[Desktop-packages] [Bug 1845797]

[jon.reeve]

This issue persists even after the latest (March 2020) BIOS update from
Lenovo. I posted about this here on the Lenovo forums:

https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/After-latest-
BIOS-update-audio-not-working-on-Yoga-C930/m-p/5009564

Is our only hope getting the Lenovo BIOS devs to release a fix? Can we
fix this in the BIOS ourselves?

I rate the probability of ever hearing from Lenovo about this at around
0%.

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

Title:
  Microphone not detected Lenovo Yoga S940

Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo
  Yoga S940

  Attached the screen of gnome sound control panel.

  Inxi output:

  System:Host:  Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: 
Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga 
S940-14IWL serial:  
 Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial:  UEFI: LENOVO v: AKCN34WW date: 06/12/2019 
  CPU:   Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT 
MCP L2 cache: 8192 KiB 
 Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 
2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 
 8: 2229 
  Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: 
snd_hda_intel 
 Sound Server: ALSA v: k5.3.0-13-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniele2239 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-12 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-13-generic N/A
   linux-backports-modules-5.3.0-13-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-13-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago)
  UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S940-14IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
  dmi.product.family: Yoga S940-14IWL
  dmi.product.name: 81Q7
  dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
  dmi.product.version: Lenovo Yoga S940-14IWL
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1845797/+subscriptions

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

[Desktop-packages] [Bug 1867613] Re: Ubuntu dock does not allow drag and move icons at bottom of screen

[Treviño]

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

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

Title:
  Ubuntu dock does not allow drag and move icons at bottom of screen

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

Bug description:
  Ubuntu 20.04 daily development branch @ 16/3/2020

  After a clean install daily at 14/3/2020 the ubuntu dock does not allow
  drag and move icons anymore with the dock placed at bottom
  you can still mouseclick and hold the icon, but it does not make space
  between other icons to release

  starting an application still showing the icon, and add to favorites
  still works

  the dock placed left or right it works better

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 16 12:31:30 2020
  InstallationDate: Installed on 2020-03-14 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1872111] Re: gnome-software should not provide ubuntu-software

[Robert Ancell]

** Changed in: gnome-software (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  gnome-software should not provide ubuntu-software

Status in gnome-software package in Ubuntu:
  Fix Committed

Bug description:
  The gnome-software deb provides an ubuntu-software desktop file.  This
  is now provided by the snap-store snap so should be removed from the
  deb to prevent confusion

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

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

[Desktop-packages] [Bug 1867548] Re: Right Alt key is suddenly switched off after invoking Settings - Keyboard Shortcuts in Focal

[Robert Ancell]

** Changed in: gnome-control-center (Ubuntu Focal)
   Status: Confirmed => Triaged

-- 
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:
  Triaged
Status in gnome-control-center source package in Focal:
  Triaged

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

[Desktop-packages] [Bug 1870600] Re: permissions pane only shows currently-connected snap interfaces

[Robert Ancell]

Fixed in commit https://gitlab.gnome.org/Community/Ubuntu/gnome-control-
center/-/commit/e1477b1e053afc907a1174b24ce7e5d94a8ba23c

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Triaged

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

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

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

Title:
  permissions pane only shows currently-connected snap interfaces

Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  The applications applet in Gnome Control Center shows permissions that
  can be toggled on and off for installed applications and snap
  packages. When viewing a Snap package, only permissions that are
  currently enabled (interface is connected in Snap terms). Viewing the
  same Snap package's permissions in Gnome Software or the Snap Store
  Snap you can see that there are more permissions that can be enabled
  which are not currently.

  I have uploaded an example of both views to highlight the discrepency
  in a screenshot at:
  https://www.dropbox.com/s/zqr35hll94d37yg/photo_2020-04-03_19-49-06.jpg?dl=0

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 19:48:07 2020
  InstallationDate: Installed on 2020-03-03 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1871195] Re: The adaptive layouts aren't working properly

[Robert Ancell]

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

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

Title:
  The adaptive layouts aren't working properly

Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  Using 3.36.1 in focal, depending of the local/labels the pages can
  lead to have the list of panels on the left hidding, that's quite a
  confusing experience (layout change, not obvious how to change back to
  another panel and when going back the mainview is empty)

  Video showing the issue on focal in french:
  
https://gitlab.gnome.org/GNOME/gnome-control-center/uploads/205957358c22144ba761eaca649f99a7/gcc.webm

  That's reported on https://gitlab.gnome.org/GNOME/gnome-control-
  center/-/issues/942 which is about bluetooth but other panels have the
  same bug, e.g https://gitlab.gnome.org/GNOME/gnome-control-
  center/-/issues/763. The selection bug is reported as
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/764

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

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

[Desktop-packages] [Bug 1867548] Re: Right Alt key is suddenly switched off after invoking Settings - Keyboard Shortcuts in Focal

[Robert Ancell]

I agree dropping this feature is the best thing to do at this time.

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

[Desktop-packages] [Bug 1871195] Re: The adaptive layouts aren't working properly

[Robert Ancell]

Fixed in commit https://gitlab.gnome.org/Community/Ubuntu/gnome-control-
center/-/commit/0a20a64137852b9952aae364aef1161ecd98a2a9

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

Title:
  The adaptive layouts aren't working properly

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

Bug description:
  Using 3.36.1 in focal, depending of the local/labels the pages can
  lead to have the list of panels on the left hidding, that's quite a
  confusing experience (layout change, not obvious how to change back to
  another panel and when going back the mainview is empty)

  Video showing the issue on focal in french:
  
https://gitlab.gnome.org/GNOME/gnome-control-center/uploads/205957358c22144ba761eaca649f99a7/gcc.webm

  That's reported on https://gitlab.gnome.org/GNOME/gnome-control-
  center/-/issues/942 which is about bluetooth but other panels have the
  same bug, e.g https://gitlab.gnome.org/GNOME/gnome-control-
  center/-/issues/763. The selection bug is reported as
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/764

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

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

[Desktop-packages] [Bug 1872968] Re: dash to dock settings fail because gnome-shell-extension-prefs is not installed, but even installing doesn't fix it.

[Daniel van Vugt]

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

I think the main issue is that the settings option is visible at all. So
let's bundle this into bug 1869635.

** This bug has been marked a duplicate of bug 1869635
   the menu "Dash to Dock Settings" is visible

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

Title:
  dash to dock settings fail because gnome-shell-extension-prefs is not
  installed, but even installing doesn't fix it.

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

Bug description:
  Ubuntu 20.04 daily build 20.04.14

  Steps to reproduce:

  Right click in the bottom left corner of the screen (on the nine dots).
  Choose Dash to Dock Settings.

  You will get a warning that gnome-shell-extension-prefs is not installed.
  Install it in a terminal window (apt install gnome-shell-extension-prefs).

  Then right click on the nine dots again, choose Dash to Dock Settings.

  You then get a window titled Ubuntu Dock, with the following error
  message:

  Something's gone wrong.
  We're very sorry, but there's been a problem: the settings for this extension 
can't be displayed. We recommend that you report the issue to the extension 
authors.

  The following Technical Details are provided:

  ImportError: No JS module 'prefs' found in search path

  Stack trace:
_init@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:204:33

OpenExtensionPrefsAsync/<@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:122:28
asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132:13
run@resource:///org/gnome/Shell/Extensions/js/dbusService.js:175:20
main@resource:///org/gnome/Shell/Extensions/js/main.js:19:13
run@resource:///org/gnome/gjs/modules/script/package.js:222:19
start@resource:///org/gnome/gjs/modules/script/package.js:206:5
@/usr/share/gnome-shell/org.gnome.Shell.Extensions:1:17

  --

  However, opening the dash and choosing gnome-shell-extension-prefs
  manually does seem to work, although that window is titled Extensions
  and not Ubuntu Dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gjs 1.64.1-2
  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: pass
  CasperVersion: 1.445
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 11:37:20 2020
  ExecutablePath: /usr/bin/gjs-console
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200414)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: gjs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1872968] Re: dash to dock settings fail because gnome-shell-extension-prefs is not installed, but even installing doesn't fix it.

[Daniel van Vugt]

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

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

Title:
  dash to dock settings fail because gnome-shell-extension-prefs is not
  installed, but even installing doesn't fix it.

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

Bug description:
  Ubuntu 20.04 daily build 20.04.14

  Steps to reproduce:

  Right click in the bottom left corner of the screen (on the nine dots).
  Choose Dash to Dock Settings.

  You will get a warning that gnome-shell-extension-prefs is not installed.
  Install it in a terminal window (apt install gnome-shell-extension-prefs).

  Then right click on the nine dots again, choose Dash to Dock Settings.

  You then get a window titled Ubuntu Dock, with the following error
  message:

  Something's gone wrong.
  We're very sorry, but there's been a problem: the settings for this extension 
can't be displayed. We recommend that you report the issue to the extension 
authors.

  The following Technical Details are provided:

  ImportError: No JS module 'prefs' found in search path

  Stack trace:
_init@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:204:33

OpenExtensionPrefsAsync/<@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:122:28
asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132:13
run@resource:///org/gnome/Shell/Extensions/js/dbusService.js:175:20
main@resource:///org/gnome/Shell/Extensions/js/main.js:19:13
run@resource:///org/gnome/gjs/modules/script/package.js:222:19
start@resource:///org/gnome/gjs/modules/script/package.js:206:5
@/usr/share/gnome-shell/org.gnome.Shell.Extensions:1:17

  --

  However, opening the dash and choosing gnome-shell-extension-prefs
  manually does seem to work, although that window is titled Extensions
  and not Ubuntu Dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gjs 1.64.1-2
  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: pass
  CasperVersion: 1.445
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 11:37:20 2020
  ExecutablePath: /usr/bin/gjs-console
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200414)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: gjs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1873086] Re: sound stutters when playing on a bluetooth receiver

[Daniel van Vugt]

Also I notice your kernel log mentions ath10k so bug 1746164 might be
relevant.

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

Title:
  sound stutters when playing on a bluetooth receiver

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I can play via bluetooth from my laptop or my mobile phone. I have a
  set of bluetooth headphones and bluetooth speakers.

  Any combination of output with the smartphone as the player works,
  which is as it should be.

  Any combination of output with the laptop as the player is miserable:
  sound stutters, sometimes randomly, sometimes seemingly when I touch
  the laptop or come close to it...had similar or identical problems
  with a previous Ubuntu laptop. Bluetooth audio seems to be in very bad
  shape.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  laptop Dell XPS 9370

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.4
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tna2174 F pulseaudio
   /dev/snd/pcmC0D0p:   tna2174 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 22:55:05 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-05-10 (706 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to bionic on 2020-03-04 (42 days ago)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0W970W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA05:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+subscriptions

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

[Desktop-packages] [Bug 1873086] Re: sound stutters when playing on a bluetooth receiver

[Daniel van Vugt]

The main fix for Bluetooth audio stutter is one that you already have,
released in pulseaudio 1:11.1-1ubuntu7.1 (bug 405294). People generally
don't report problems since then so any remaining issues are likely to
be hardware-specific or environment-specific.

Please run these commands:

  lsusb > lsusb.txt
  lspci -k > lspci.txt

and then attach the resulting two files.

Please also test with:

  * wifi disabled completely; and
  * using a 5GHz network instead of 2.4GHz


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

** Tags added: a2dp-skip

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

Title:
  sound stutters when playing on a bluetooth receiver

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I can play via bluetooth from my laptop or my mobile phone. I have a
  set of bluetooth headphones and bluetooth speakers.

  Any combination of output with the smartphone as the player works,
  which is as it should be.

  Any combination of output with the laptop as the player is miserable:
  sound stutters, sometimes randomly, sometimes seemingly when I touch
  the laptop or come close to it...had similar or identical problems
  with a previous Ubuntu laptop. Bluetooth audio seems to be in very bad
  shape.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  laptop Dell XPS 9370

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.4
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tna2174 F pulseaudio
   /dev/snd/pcmC0D0p:   tna2174 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 22:55:05 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-05-10 (706 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to bionic on 2020-03-04 (42 days ago)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0W970W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA05:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+subscriptions

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

[Desktop-packages] [Bug 1873086] Re: sound stutters when playing on a bluetooth receiver

[Daniel van Vugt]

** Tags added: a2dp

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

Title:
  sound stutters when playing on a bluetooth receiver

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I can play via bluetooth from my laptop or my mobile phone. I have a
  set of bluetooth headphones and bluetooth speakers.

  Any combination of output with the smartphone as the player works,
  which is as it should be.

  Any combination of output with the laptop as the player is miserable:
  sound stutters, sometimes randomly, sometimes seemingly when I touch
  the laptop or come close to it...had similar or identical problems
  with a previous Ubuntu laptop. Bluetooth audio seems to be in very bad
  shape.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  laptop Dell XPS 9370

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.4
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tna2174 F pulseaudio
   /dev/snd/pcmC0D0p:   tna2174 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 22:55:05 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-05-10 (706 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to bionic on 2020-03-04 (42 days ago)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0W970W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA05:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+subscriptions

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

[Desktop-packages] [Bug 1873052] Re: GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps another not scaled cursor mid screen

[Daniel van Vugt]

Does the problem still happen if you choose 'Ubuntu on Wayland' from the
login screen? I am wondering if it is unique to the Xrandr scaling
feature.

See also https://gitlab.gnome.org/GNOME/mutter/-/issues/1108

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

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

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

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

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

Status in mutter package in Ubuntu:
  Incomplete

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

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

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

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

  Package: mutter 3.36.1-3ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 20:06:53 2020
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873052/+subscriptions

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

[Desktop-packages] [Bug 1872970] Re: pulseaudio (1:13.99.1-1ubuntu2) no sound on Bay and Cherry trail device

[Daniel van Vugt]

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

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

** Tags added: fixed-in-13.99.2 fixed-upstream focal

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

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

Title:
  pulseaudio (1:13.99.1-1ubuntu2) no sound on Bay and Cherry trail
  device

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio package in Fedora:
  Unknown

Bug description:
  I install ubuntu focal, no sound on my Cherry trail device, it has a es8316 
sound card.
  downgrade pulseaudio_13.0-1ubuntu1.1 sound work.

  https://bugzilla.redhat.com/show_bug.cgi?id=1818883
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/276/

  please build next pulseaudio include patch, ucm: fix the port / ucm device 
activation on boot
  alsa sink/source: fix the mixer initialization

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872970/+subscriptions

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

[Desktop-packages] [Bug 1873005] Re: [Bluetooth Bose Headphones, playback] Sound plays exclusively from laptop speakers even when headset is selected as output device

[Daniel van Vugt]

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

Note that:

 * after you delete ~/.config/pulse you at least need to log out and in
again.

 * even if deleting ~/.config/pulse doesn't work then we should use bug
1866194 still. The workaround is also not confirmed to work in that bug,
but it's the same bug.

** This bug has been marked a duplicate of bug 1866194
   External audio device shows up in the sound output options but the sound 
keeps being emitted from the internal laptop speaker, or none at all.

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

Title:
  [Bluetooth Bose Headphones, playback] Sound plays exclusively from
  laptop speakers even when headset is selected as output device

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The computer will not send any sound output to the headset, and
  instead does all playback through the built in speakers. If headphones
  are connected by AUX sound will be sent there.

  Bluetooth media buttons work - I can pause music by tapping the
  bluetooth headset.

  If I change bluetooth audio quality the headset makes a notification
  sound, but playback continues as before through computer speakers.

  Audio tests (front left, front right) are also channelled through
  computer speakers.

  The same headset with the same setup worked flawlessly in 19.10.

  Thank you so much for your work! 20.04 is a joy to use.

  Edit: I tried deleting .config/pulse. This didn't make any difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu2
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steinarne   1509 F pulseaudio
   /dev/snd/pcmC0D0c:   steinarne   1509 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 16:30:16 2020
  InstallationDate: Installed on 2019-08-08 (251 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: LE-Bose NC 700 Headphones
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steinarne   1509 F pulseaudio
   /dev/snd/pcmC0D0c:   steinarne   1509 F...m pulseaudio
  Symptom_Type: No sound at all
  Title: [LE-Bose NC 700 Headphones, playback] No sound at all
  UpgradeStatus: Upgraded to focal on 2020-04-13 (2 days ago)
  dmi.bios.date: 05/05/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET56W (1.33 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LS0017MX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET56W(1.33):bd05/05/2019:svnLENOVO:pn20LS0017MX:pvrThinkPadL480:rvnLENOVO:rn20LS0017MX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L480
  dmi.product.name: 20LS0017MX
  dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
  dmi.product.version: ThinkPad L480
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873005/+subscriptions

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

[Desktop-packages] [Bug 1872986] Re: Super key press is ignored in certain keyboard layouts

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1871913
   super key does not work with secondary keyboard layout

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

Title:
  Super key press is ignored in certain keyboard layouts

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I use english (us) and portuguese keyboard layouts. The super key only
  launches the activities menu on gnome if I am using english layout. If
  I am using portuguese layout this key press is ignored.

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

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

[Desktop-packages] [Bug 1872853] Re: Keys stuck on repeat when key triggers sound, and output device is ClearOne Chat 50

[Daniel van Vugt]

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

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

Title:
  Keys stuck on repeat when key triggers sound, and output device is
  ClearOne Chat 50

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

Bug description:
  When I am typing in a gnome terminal, any time I press a key that
  triggers a sound (e.g., hitting "backspace" when already at the
  beginning of the command line, hitting "tab" for tab completion when
  there are multiple possible completion options), the key gets stuck on
  repeat. The sound plays over and over. If I move the mouse to other
  windows and focus on them, the repeated key continues there. (I have
  focus-follows-mouse enabled, if that matters.)

  This is 100% reproducible. But I have tracked it down to only occuring
  when I go into Settings->Sounds, select the "Output" tab, and choose
  the "Analog Output - Chat 50" device for sound output.

  I do have a ClearOne Chat 50 plugged into my computer via USB. It
  seems to be operating correctly for both input and output sound
  (ignoring the key repeat issue).

  Before figuring out that changing the sound output to be something
  other than the Chat 50, I ruled out the keyboard being the problem by
  swapping in a different model of USB keyboard. I also rebooted the
  system, and that made no difference either.

  I saw other bugs about repeating keys, such as bug #124406. I did try
  disabling repeat with "xset r off". This seems to stop the repeated
  key from taking effect in, say, Gnome terminal. But the repeating key
  is probably still being issued somewhere in the system because when I
  then trigger the bug the keyboard becomes unusable until I unplug it
  and plug it back in again.

  In all cases, unplugging the USB keyboard and plugging it back in
  again eliminates the stuck repeating key.

  I apologize for not selecting a particular package for this bug. This
  bug does only seem to occur when the ClearOne Chat 50 is selected as
  the output sound device, but I'm completely unclear about how an
  output sound device could case key presses to operate incorrectly. I
  does not seem like the sound device should be able to cause a keypress
  to repeat even if the sound driver is buggy.

  
  Ubuntu 18.04.4 LTS.
  Linux mal 4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1864274] Re: [iris regression] gfx corruption

[Bug Watch Updater]

** Changed in: mesa
   Status: New => Fix Released

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

Title:
  [iris regression] gfx corruption

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Focal:
  Confirmed

Bug description:
  Hello, after upgrading firefox (and many other packages) on focal
  today, I've got some video artifacts in firefox.

  When typing in text boxes and text fields, the new character is drawn
  very slowly, pixel-by-pixel, and isn't complete until the cursor has
  moved on. When larger portions of the screen are updated, it looks a
  lot like the entire window is being run through a video codec or you
  can see parts of the video memory from other processes. (But it looks
  more deliberate and predictable than either of these descriptions.)

  So far Firefox is the only application I've found that is affected.
  urxvt, libreoffice, xfontsel, glxgears all seem to work as expected.

  I did get cairo package update today, but the changelog is just:

  pango1.0 (1.44.7-1ubuntu2) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
   -- Matthias Klose   Sat, 08 Feb 2020 11:15:23 +

  And an xorg update:

  xorg (1:7.7+19ubuntu14) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
   -- Matthias Klose   Sat, 08 Feb 2020 11:21:28 +

  
  So I don't believe these are involved.

  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620
  (rev 07)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 73.0.1+build1-0ubuntu1
  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
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sarnold3296 F pulseaudio
   /dev/snd/controlC0:  sarnold3296 F pulseaudio
  BuildID: 20200217142647
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 144'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  Channel: Unavailable
  Date: Sat Feb 22 05:41:10 2020
  ForcedLayersAccel: False
  IncompatibleExtensions:
   Pentadactyl - pentadac...@dactyl.googlecode.com
   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}
  IpRoute:
   default via 192.168.0.1 dev enp0s31f6 proto dhcp metric 100 
   10.23.231.0/24 dev lxdbr0 proto kernel scope link src 10.23.231.1 
   192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.34 metric 
100 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MostRecentCrashID: bp-ea952d4d-f25a-4ced-893c-8cabb2160112
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:737
  PrefSources: prefs.js
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to focal on 2020-01-24 (28 days ago)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  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:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1864274/+subscriptions

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

[Desktop-packages] [Bug 1799073] Re: Full screen key chorded zoom (Alt+Super+=) fails in 18.04.1/18.10

[Christopher Patti]

This works great in 20.04

** Changed in: gnome-shell (Ubuntu)
   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/1799073

Title:
  Full screen key chorded zoom (Alt+Super+=) fails in 18.04.1/18.10

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Hi all. I noticed this problem when I upgraded from 18.04 to 18.04.1
  (Worked perfectly in stock 18.04) and then I was testing the 18.10
  beta and hoped it would be fixed there but it's not.

  To reproduce: login to the regular Ubuntu desktop, hit Super+Alt+=
  (You can validate that your keyboard shortcut is set to the default in
  Settings->Keyboard.)

  I also tried changing the keyboard mapping for this action in case
  there was a conflict, and no matter what I set it to I couldn't zoom
  from the keyboard.

  As a partially blind user, this is a show stopper for me - I require
  screen zoom to be able to use Ubuntu at all for any serious work.

  Thanks for everything you do!
  -Chris
  (Happy to try any work-arounds or testing people can think up to help fix 
this problem)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
  InstallationDate: Installed on 2018-10-07 (14 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Package: gnome-shell 3.30.1-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  cosmic
  Uname: Linux 4.19.0-041900rc8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1697122] Re: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures

[Daniel van Vugt]

** Tags added: 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/1697122

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1697122/+subscriptions

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

[Desktop-packages] [Bug 1811893] Re: In Ubuntu on Virtualbox, the screen is blank after sign-in

[Serge Hallyn]

Thanks for reporting this bug.  This looks to be a bug with either
xubuntu login manager or xubuntu default X11 session, so I'm reassigning
it to lightdm.

** Package changed: shadow (Ubuntu) => lightdm (Ubuntu)

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

Title:
  In Ubuntu on Virtualbox, the screen is blank after sign-in

Status in lightdm package in Ubuntu:
  New

Bug description:
  I installed xubuntu in my Windows box using the latest VBOX (6.0). It
  installed perfectly however after I log in the screen kind of freezes.
  I see the background however the icons and title bar do not appear.
  Also mouse inputs like right click do not work. Function keys do not
  work either like alt F2.

  Xubuntu system is updated and the guest addons are installed.

  I have tried disbling the 3d acceleration however that did not work.

  The only way I can get this to load the icons is to go to Devices ->
  Insert Guest Additions CD Image. Once I click on Insert Guest
  Additions the icons and title bar load and everything works fine.

  I checked online for solutions but have not found any that work.

  This also seems to be a problem with other versions of Ubuntu and
  other Linux distributions.

  xubuntu 10.04.1

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: login 1:4.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jan 15 15:20:31 2019
  InstallationDate: Installed on 2019-01-15 (0 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1811893/+subscriptions

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

[Desktop-packages] [Bug 1872146] Re: Audio on Headphones stopped working

[Daniel van Vugt]

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

OK, we can track this as a duplicate of bug 1866194 then, until proven
otherwise.

** This bug has been marked a duplicate of bug 1866194
   External audio device shows up in the sound output options but the sound 
keeps being emitted from the internal laptop speaker, or none at all.

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

Title:
  Audio on Headphones stopped working

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Audio via my headphones worked yesterday, Today no such luck.

  When I plug in my headphone, Plasma picks it up but no sound.

  Bluetooth headset still works.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  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
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Fri Apr 10 23:03:09 2020
  InstallationDate: Installed on 2020-04-05 (5 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200404)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872146/+subscriptions

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

[Desktop-packages] [Bug 1873104] Re: Defaults to USB audio after every reboot

[Hui Wang]

You could temporarily remove the module-switch-on-connect from the
/etc/pulse/default.pa, reboot and redo the test.

To check if switch-on-connect is loaded or not, run "pactl list modules
| grep connect"

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

Title:
  Defaults to USB audio after every reboot

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I manually set my audio output to the Line Out. Every reboot this
  settings is lost and the system defaults back to the USB output. I
  have several other distros to test - Ubuntu and its flavors are the
  only ones that have this problem. Something changed in 19.04 or 19.10
  that broke this, and it continues to be an issue in 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  caleb  1778 F pulseaudio
   /dev/snd/controlC3:  caleb  1778 F pulseaudio
   /dev/snd/controlC1:  caleb  1778 F pulseaudio
   /dev/snd/controlC0:  caleb  1778 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Wed Apr 15 19:32:36 2020
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.30
  dmi.board.name: 8437
  dmi.board.vendor: HP
  dmi.board.version: 1.3
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd09/06/2018:svnHP:pnOMENbyHPDesktopPC880-p1xx:pvr:rvnHP:rn8437:rvr1.3:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53311M HP Omen
  dmi.product.name: OMEN by HP Desktop PC 880-p1xx
  dmi.product.sku: 2TB61AV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1873104/+subscriptions

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

[Desktop-packages] [Bug 638659] Re: Enable Auto-Scroll and Smooth Scrolling by Default in Firefox

[Daniel van Vugt]

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

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

Title:
  Enable Auto-Scroll and Smooth Scrolling by Default in Firefox

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  By default, Firefox does not have Auto-Scrolling and Smooth Scrolling
  by default. This makes it seem like the middle click is 'broken'.

  There are numerous threads on the forum about this:
  http://ubuntuforums.org/showthread.php?t=478418
  http://ubuntuforums.org/showthread.php?t=767335
  http://ubuntuforums.org/showthread.php?t=36824
  http://ubuntuforums.org/showthread.php?t=410876

  Clearly, this is a big problem, and the first thing I have to fix
  after any install I do.

  The fix is very simple: Enable these two options! Tada! Feels like
  it's supposed to. It seems like a lot of linux-heads don't notice this
  one because it's been broken for so long, but for anybody coming from
  the big W, this is totally crucial.

  R

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/638659/+subscriptions

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

[Desktop-packages] [Bug 1811893] [NEW] In Ubuntu on Virtualbox, the screen is blank after sign-in

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I installed xubuntu in my Windows box using the latest VBOX (6.0). It
installed perfectly however after I log in the screen kind of freezes. I
see the background however the icons and title bar do not appear. Also
mouse inputs like right click do not work. Function keys do not work
either like alt F2.

Xubuntu system is updated and the guest addons are installed.

I have tried disbling the 3d acceleration however that did not work.

The only way I can get this to load the icons is to go to Devices ->
Insert Guest Additions CD Image. Once I click on Insert Guest Additions
the icons and title bar load and everything works fine.

I checked online for solutions but have not found any that work.

This also seems to be a problem with other versions of Ubuntu and other
Linux distributions.

xubuntu 10.04.1

Description:Ubuntu 18.04.1 LTS
Release:18.04

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: login 1:4.5-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Jan 15 15:20:31 2019
InstallationDate: Installed on 2019-01-15 (0 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: shadow
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic
-- 
In Ubuntu on Virtualbox, the screen is blank after sign-in
https://bugs.launchpad.net/bugs/1811893
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to lightdm 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 1869141] Re: [UIFe] Icon View Captions labels in Nautilus are hard to read when selected

[Daniel van Vugt]

** Bug watch added: github.com/ubuntu/yaru/issues #2110
   https://github.com/ubuntu/yaru/issues/2110

** Also affects: yaru via
   https://github.com/ubuntu/yaru/issues/2110
   Importance: Unknown
   Status: Unknown

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

Title:
  [UIFe] Icon View Captions labels in Nautilus are hard to read when
  selected

Status in Yaru Theme:
  Unknown
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  First reported here: https://github.com/ubuntu/yaru/issues/2110

  The "Icon View Captions" label in Nautilus is hard to read when the
  file is selected.

  Steps to Reproduce the Problem
  - open Preferences > View Tab
  - in the "Icon View Captions" section select at least one "information to be 
displayed beneath file and folders name"
  - Go back to Nautilus main window and select Icon View. Below the file name 
is expected to be a new label with color gray
  - Select the icon. The caption label keeps the gray color, which is hard to 
read on an orange background

  Yaru version

  - Version 20.04.4 in current Focal daily

  
  The fix has a low impact, since it only applies to Yaru's stylesheet part 
dedicated to Nautilus, and specifically to this caption labels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/1869141/+subscriptions

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

[Desktop-packages] [Bug 1870823] Re: temporary mouse freeze on sticky edge between displays

[Daniel van Vugt]

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

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

Title:
  temporary mouse freeze on sticky edge between displays

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  i'm running ubuntu 20.04 focal fossa, development branch, on a lenovo
  T460s (internal display 2560x1440, 200% scaling) with a dell external
  display (1920x1200, 100% scaling) set to "join displays".  fractional
  scaling is enabled.

  on wayland, since upgrading from ubuntu 19.10, the mouse pointer
  freezes for about 10-20 seconds when slowly moved between displays
  ("sticky edge").  the freeze behavior depends on the exact position
  between displays.  the machine is unresponsive during these freezes.
  if the mouse is moved quickly, the freeze does not occur.  the freeze
  only happens on wayland -- the problem does not occur on Xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xwayland 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 12:50:21 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2233]
  InstallationDate: Installed on 2018-01-24 (800 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 20FAS05P00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=be1e4f31-e9c9-41ac-9f95-cdbd8d5fc22a ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET79W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS05P00
  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:bvrN1CET79W(1.47):bd11/25/2019:svnLENOVO:pn20FAS05P00:pvrThinkPadT460s:rvnLENOVO:rn20FAS05P00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS05P00
  dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s
  dmi.product.version: ThinkPad T460s
  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.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-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/mutter/+bug/1870823/+subscriptions

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

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

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1697122
   Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel 
scrolling with touchpad and touch gestures

-- 
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:
  Incomplete

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 1869635] Re: the menu "Dash to Dock Settings" is visible

[Treviño]

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  the menu "Dash to Dock Settings" is visible

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

Bug description:
  When the user performs a right-button mouse click on the "Show
  Applications" button of the Ubuntu Dock then a "Dash to Dock Settings"
  menu option appears as shown in the attached image.

  Normally, this menu option is only available on the original "Dash to
  Dock" GNOME shell extension used as the basis for the Ubuntu Dock and
  it should not be visible or functional on the Ubuntu Dock itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 30 02:31:58 2020
  InstallationDate: Installed on 2020-02-12 (46 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to focal on 2020-03-27 (2 days ago)

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

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

[Desktop-packages] [Bug 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled

[Treviño]

Do you have many indicators running?

If yes, could you try just disabling the indicators extension?

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

Title:
  gnome-shell animations are noticeably stuttery when the Ubuntu
  extensions are enabled

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

Bug description:
  I have a Dell XPS 9360 with a FHD screen and a Intel HD620 iGPU, running 
Ubuntu 20.04. On this system animations should be smooth and at 60fps, but this 
is not always the case.
  The applications animation (the icons coming from the bottom left) is 
specially stuttery most of the time. Sometimes it is buttery smooth, but most 
of the times it is not. It is difficult to pinpoint when.

  Some exploration that may help to find the issue:
  * I also have a desktop with 20.04 and a Nvidia 750ti and it seems to be much 
smoother. This seems to indicate that the problem is somehow related to the 
Intel iGPU.
  * Animations seem smoother under Wayland. But, because of other limitations, 
I am staying on Xorg for now.
  * The application animation is super stuttery the first time it is opened in 
a session. It gets slowly better with subsequent uses, although never totally 
smooth.
  " The animation is noticeably more stuttery if it opens the “All” 
applications tab instead of “Frequent” apps. Maybe the number of apps (icons) 
is a factor?
  * Vanilla gnome-session seems to be smoother. Maybe the problem is related to 
Dash-to-dock or another Ubuntu extension? (In my ubuntu session only default 
extensions are enabled).

  These datapoints are mainly subjective as I have no means of properly
  measure animations performance.

  Don't get my wrong, 20.04 is a clear improvement over 18.04. But it
  seems there is some room for improvement at least in this hardware.

  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
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 15:23:40 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-23 (780 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  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/1872796/+subscriptions

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

[Desktop-packages] [Bug 1312112] Re: Chromium should watch the escale setting "Scale for menu and title bars" in Display Settings at runtime

[Daniel van Vugt]

Ubuntu 14.04 reached end of standard support in April 2019:

  https://wiki.ubuntu.com/Releases

If you would like to continue with free support then please update to a
newer Ubuntu version and tell us if the problem still occurs.

If you would like to continue with Ubuntu 14.04 then there is a paid
support option detailed at https://www.ubuntu.com/esm

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Chromium should watch the escale setting "Scale for menu and title
  bars" in Display Settings at runtime

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  Chromium scales correctly on start up based on the setting applied to
  "Scale for menu and title bars" in Display Settings.

  However, ideally, Chromium should watch this setting also at runtime
  and scale if it gets modified, as the GTK applications currently do.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 24 12:42:05 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  DetectedPlugins:
   
  DiskUsage:
   b'Filesystem Type  Size  Used Avail Use% Mounted on\n/dev/sda2  
ext4  286G   13G  258G   5% /\nnone   tmpfs 4,0K 0  4,0K   
0% /sys/fs/cgroup\nudev   devtmpfs  3,9G  4,0K  3,9G   1% /dev\ntmpfs   
   tmpfs 785M  1,1M  784M   1% /run\nnone   tmpfs 5,0M 
0  5,0M   0% /run/lock\nnone   tmpfs 3,9G  292K  3,9G   1% 
/run/shm\nnone   tmpfs 100M   80K  100M   1% /run/user\n/dev/sda1   
   vfat  487M  3,4M  483M   1% /boot/efi\n'
   
   Inodes:
   b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda2 19M  
259K   18M2% /\nnone 982K 2  982K1% 
/sys/fs/cgroup\nudev 979K   538  978K1% /dev\ntmpfs
982K   538  981K1% /run\nnone 982K 3  982K1% 
/run/lock\nnone 982K 9  982K1% /run/shm\nnone 
982K36  982K1% /run/user\n/dev/sda1   0 0 0 - 
/boot/efi\n'
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-03-26 (29 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to trusty on 2014-04-07 (16 days ago)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1312112/+subscriptions

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

[Desktop-packages] [Bug 1533000] Re: Need to --force-device-scale-factor=2 Chromium on HiDPI screen

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1316847
   Chromium launch script should follow ubuntu Scaling setting to work on HiDPI 
screens

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

Title:
  Need to --force-device-scale-factor=2 Chromium on HiDPI screen

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  On my HiDPI macbook running Ubuntu GNOME 15.10, I still have to run
  Chromium with the --force-device-scale-factor=2 flag to get a properly
  scaled browser window and controls, otherwise everything is too small.
  (Not sure if this is the same under Unity -- maybe Chromium reads some
  Unity specific configuration setting?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1533000/+subscriptions

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

[Desktop-packages] [Bug 1872926] Re: font scaling

[Daniel van Vugt]

Thanks for the bug report.

It is the responsibility of the graphics toolkit used by an app, or the
app itself, to honour font scaling settings. So please report this issue
to each application. It looks like Chrome (Chromium) is already covered
by bug 1316847?

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

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

Title:
  font scaling

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  i use font scaling at 1.20 an it doesn't work on skype, chrome,
  discord whatsdesk etc

  i need to edit all the launcher to use it

  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] Permesso negato: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 10:43:40 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:5036]
  InstallationDate: Installed on 2020-04-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Lsusb:
   Bus 001 Device 002: ID 8087:8001 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 003: ID 04f2:b449 Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20BWS3MG00
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=e64bf22d-6dd2-4ba5-9de7-df6dbf8d2dc4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS3MG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BWS3MG00:pvrThinkPadT450s:rvnLENOVO:rn20BWS3MG00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS3MG00
  dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+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/1872926/+subscriptions

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

[Desktop-packages] [Bug 1868162] Re: snap chromium does not respect the dpi setting of xfce

[Daniel van Vugt]

Isn't this bug 1538256?

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

Title:
  snap chromium does not respect the dpi setting of xfce

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  on a 4k monitor the default 96dpi setting is typically too small to
  work with. setting it to eg 120dpi the guis become more readable.
  unfortunately, chromium browser from the snap package on ubuntu 19.04
  does still comes with ultra tiny font for the url text window.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 79.0.3945.79-0ubuntu0.19.10.2
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAebQd3LF0AAAwdAQS1PCJ4nj4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QA4PR6HOAAKICAgICAg/ABMRyBIRFIgNEsKICAgAdoCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ==
   modes: 3840x2160 3840x2160 2560x1440 1920x1080 1920x1080 1920x1080 1600x900 
1280x1024 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 
720x480 640x480 640x480 640x480
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Thu Mar 19 20:06:13 2020
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sda2  ext4   149G   18G  123G  13% /
   tmpfs  tmpfs  3.9G  157M  3.7G   4% /dev/shm
   /dev/sda2  ext4   149G   18G  123G  13% /
  InstallationDate: Installed on 2020-03-18 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. CML-U PRO Cubi 5 (MS-B183)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=55264ebb-0214-408c-9b11-5009818e9ad4 ro pti=off spectre_v2=off 
l1tf=off nospec_store_bypass_disable no_stf_barrier quiet
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   3Done2020-03-18T21:46:44+01:00  2020-03-18T21:47:20+01:00  Install 
"chromium" snap
  Snap.ChromeDriverVersion: ChromeDriver 80.0.3987.132 
(fcea73228632975e052eb90fcf6cd1752d3b42b4-refs/branch-heads/3987@{#974})
  Snap.ChromiumVersion:
   /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
   Chromium 80.0.3987.132 snap
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 8.20
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-B1831
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr8.20:bd11/13/2019:svnMicro-StarInternationalCo.,Ltd.:pnCML-UPROCubi5(MS-B183):pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-B1831:rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: Desktop
  dmi.product.name: CML-U PRO Cubi 5 (MS-B183)
  dmi.product.sku: B183.8
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1868162/+subscriptions

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

[Desktop-packages] [Bug 1873013] Re: Chromium 83.0.4103.7 is randomly crashing tab

[guest271314]

Following instructions at https://wiki.ubuntu.com/Chromium/Debugging.
(The UI displays timeout error when uploading the file)

# Env:
# LD_LIBRARY_PATH=
#
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
#GTK_PATH=
# CHROMIUM_USER_FLAGS=
#  CHROMIUM_FLAGS=  --enable-pinch
/usr/bin/gdb /usr/lib/chromium-browser/chromium-browser -x 
/tmp/chromiumargs.x2aQQO
GNU gdb (Ubuntu 8.1-0ubuntu3.2) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/chromium-browser/chromium-browser...Reading 
symbols from 
/usr/lib/debug/.build-id/1b/e9a48bbeed75ce14d5b4ab231a72aef655f4bb.debug...done.
done.
(gdb) handle SIG33 pass nostop noprint
SignalStop  Print   Pass to program Description
SIG33 NoNo  Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/lib/chromium-browser/chromium-browser --enable-pinch 
warning: the debug information found in 
"/usr/lib/debug//lib/i386-linux-gnu/ld-2.27.so" does not match 
"/lib/ld-linux.so.2" (CRC mismatch).

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xb4358b40 (LWP 16234)]
[New Thread 0xb39ffb40 (LWP 16240)]
[New Thread 0xb1f39b40 (LWP 16241)]
[New Thread 0xb1738b40 (LWP 16242)]
[New Thread 0xb0bffb40 (LWP 16243)]
[New Thread 0xb03feb40 (LWP 16244)]
[New Thread 0xaf9ffb40 (LWP 16245)]
[New Thread 0xaf1feb40 (LWP 16246)]
[New Thread 0xae7c3b40 (LWP 16247)]
[New Thread 0xadfc2b40 (LWP 16248)]

(chromium-browser:16230): Gtk-WARNING **: 01:33:49.990: Theme parsing
error: gtk.css:597:14: not a number

(chromium-browser:16230): Gtk-WARNING **: 01:33:49.990: Theme parsing
error: gtk.css:597:14: Expected a string.

(chromium-browser:16230): Gtk-WARNING **: 01:33:49.990: Theme parsing
error: gtk.css:600:17: Expected a string.

(chromium-browser:16230): Gtk-WARNING **: 01:33:49.991: Theme parsing
error: gtk.css:784:14: not a number

(chromium-browser:16230): Gtk-WARNING **: 01:33:49.991: Theme parsing
error: gtk.css:784:14: Expected a string.

(chromium-browser:16230): Gtk-WARNING **: 01:33:49.991: Theme parsing
error: gtk.css:787:17: Expected a string.

(chromium-browser:16230): Gtk-WARNING **: 01:33:49.993: Theme parsing
error: gtk.css:1096:14: not a number

(chromium-browser:16230): Gtk-WARNING **: 01:33:49.993: Theme parsing
error: gtk.css:1096:14: Expected a string.

(chromium-browser:16230): Gtk-WARNING **: 01:33:49.993: Theme parsing
error: gtk.css:1099:17: Expected a string.

(chromium-browser:16230): Gtk-WARNING **: 01:33:49.999: Theme parsing
error: gtk.css:2286:8: not a number

(chromium-browser:16230): Gtk-WARNING **: 01:33:49.999: Theme parsing
error: gtk.css:2286:18: Using Pango syntax for the font: style property
is deprecated; please use CSS syntax

(chromium-browser:16230): Gtk-WARNING **: 01:33:49.999: Theme parsing
error: gtk.css:2291:8: not a number

(chromium-browser:16230): Gtk-WARNING **: 01:33:49.999: Theme parsing
error: gtk.css:2291:18: Using Pango syntax for the font: style property
is deprecated; please use CSS syntax

(chromium-browser:16230): Gtk-WARNING **: 01:33:50.005: Theme parsing
error: gtk.css:4357:14: not a number

(chromium-browser:16230): Gtk-WARNING **: 01:33:50.005: Theme parsing
error: gtk.css:4357:14: Expected a string.

(chromium-browser:16230): Gtk-WARNING **: 01:33:50.005: Theme parsing
error: gtk.css:4419:12: not a number

(chromium-browser:16230): Gtk-WARNING **: 01:33:50.005: Theme parsing
error: gtk.css:4419:12: Expected a string.

(chromium-browser:16230): Gtk-WARNING **: 01:33:50.005: Theme parsing
error: gtk.css:4428:16: not a number

(chromium-browser:16230): Gtk-WARNING **: 01:33:50.006: Theme parsing
error: gtk.css:4428:16: Expected a string.

(chromium-browser:16230): Gtk-WARNING **: 01:33:50.006: Theme parsing
error: gtk.css:4443:22: not a number

(chromium-browser:16230): Gtk-WARNING **: 01:33:50.006: Theme parsing
error: gtk.css:4443:22: Expected a string.

(chromium-browser:16230): Gtk-WARNING **: 01:33:50.006: Theme parsing
error: gtk.css:4499:12: Expected a string.

(chromium-browser:16230): Gtk-WARNING **: 01:33:50.006: Theme parsing
error: gtk.css:4501:16: not a number

(chromium-browser:16230): Gtk-WARNING **: 01:33:50.006: Theme parsing
error: 

[Desktop-packages] [Bug 1868207] Re: Fractional scaling window sizes incorrect after resume from suspend

[Daniel van Vugt]

Sounds like bug 1793496 might cover this. Let's see if that fix resolves
it...

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

Title:
  Fractional scaling window sizes incorrect after resume from suspend

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  LP bug as requested at
  https://gitlab.gnome.org/GNOME/mutter/issues/1122

  From the summary there:

  With fractional scaling enabled, after resume from suspend, maximised
  & half tiled windows have been resized/scaled so they are too large
  for the screen, and as a result no longer fit on the screen.  Not sure
  if it also happens to windows that aren't in either of these states, I
  rarely have any. Further, most but not all windows are scaled like
  this. Epiphany and Terminal definitely are, maybe XWindows clients
  like Emacs aren't?

  Under 3.34, shell/mutter seemed to notice this and would visibly snap
  the window sizes back to what they should be. Under 3.36, that no
  longer seems to happen - the windows stay too big and I need to
  manually fix them.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.35.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 20 16:54:48 2020
  InstallationDate: Installed on 2018-08-13 (584 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to focal on 2020-03-07 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1868207/+subscriptions

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

[Desktop-packages] [Bug 1872971] Re: Xorg crash

[Daniel van Vugt]

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

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

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

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

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


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

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

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

Title:
  Xorg crash

Status in xorg-server package in Ubuntu:
  Incomplete

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

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

  I was running the game Into the Breach
  (https://store.steampowered.com/app/590380/Into_the_Breach/) through
  Steam Play (Proton 5.0-5). When I continue my game and mouse over a
  character which has been placed on the play field, my session crashes
  and I am returned to the login screen. This consistently happens every
  time I load my game and perform the mouseover.

  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..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.82  Wed Apr  1 20:04:33 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu1)
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed Apr 15 13:38:42 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.82, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0819]
 Subsystem: Dell GM108M [GeForce MX130] [1028:0819]
  InstallationDate: Installed on 2020-04-09 (6 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Dell Inc. Latitude 5591
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=595cdefb-5445-4df8-99e9-6a60485a8c97 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.1
  dmi.board.name: 0DVVG1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.1:bd01/11/2019:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5591
  dmi.product.sku: 0819
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+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-server/+bug/1872971/+subscriptions

-- 
Mailing list: 

[Desktop-packages] [Bug 1859509] Re: wsl-integration.sh shows error when .cache/ can't be created

[Patrick Wu]

SRU process will take some time, but yes, it will make to both bionic or
xenial

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

Title:
  wsl-integration.sh shows error when .cache/ can't be created

Status in wslu package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

   * When $HOME/.cache can't be created an error is shown:
 mkdir: cannot create directory ‘//.cache’: Permission denied

  [Test Case]
   * TODO

  [Regression Potential]
   * TODO
  [Other Info]

  Originally reported to:
  https://github.com/wslutilities/wslu/issues/101

  In addition to suppressing the error message it would probably be also
  useful to disable the detection by default for system users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1859509/+subscriptions

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

[Desktop-packages] [Bug 1873003] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1865300
   gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from 
g_hash_table_lookup() from deep_count_more_files_callback()

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

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

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

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2643

  ---

  I don't know what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  Uname: Linux 5.6.4-050604-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 10:11:16 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/libexec/gnome-shell-hotplug-sniffer
  InstallationDate: Installed on 2018-12-02 (499 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/libexec/gnome-shell-hotplug-sniffer
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=es_CL:es
   LANG=es_CL.UTF-8
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f89b635e494 : movsbl (%rdi),%eax
   PC (0x7f89b635e494) 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 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ()
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: Upgraded to focal on 2018-12-02 (499 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1871416] Re: alt-TAB hightlight colour almost indistinguishable from the background

[Daniel van Vugt]

yaru-theme (20.04.5) focal; urgency=medium

  [ Carlo Lobrano ]
  * apps/nautilus: fix dim-label in selection and backdrop (LP: #1869141)
  * tweaks: use outline for tabs accessibility
  * gnome-shell/calendar: darken event dot (LP: #1870938)
  * gnome-shell/calendar: do not change color of day with events
  * shell/switcher-popup: improve contrast of highlighted app

  [ ubuntujaggers ]
  * Updating symbols for Tweaks and Configurator
  * Remove new legacy icons and include some from Humanity (LP: #1870925)
  * Adding symbols for system-reboot and system-log-out (LP: #1868385)
  * Adding missing symlinks for extensions app (Fixes: #2096)
  * suggested (more yaru-style) icon for extensions
  * adding dialog-warning and symlinks (Fixes: #2103)

 -- Carlo Lobrano   Tue, 14 Apr 2020 17:45:05 +0200


** Changed in: yaru-theme (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  alt-TAB hightlight colour almost indistinguishable from the background

Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  Almost impossible to see which item is highlighted.  See attached
  image.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  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-0ubuntu24
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 15:53:23 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-02-28 (1500 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160226)
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  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/yaru-theme/+bug/1871416/+subscriptions

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

[Desktop-packages] [Bug 1871972] Re: Update pango for Unicode 13.0

[Launchpad Bug Tracker]

This bug was fixed in the package pango1.0 - 1.44.7-2ubuntu3

---
pango1.0 (1.44.7-2ubuntu3) focal; urgency=medium

  [ Laurent Bigonville ]
  * debian/control.in: Add libcairo2-doc, libgtk-3-doc and libharfbuzz-doc
to BDI to fix more links between gtk-doc files

  [ Jeremy Bicha ]
  * Cherry-pick Update-pango-emoji-table.h-to-Unicode-Emoji-Data-13.0.patch:
- Prepare for Unicode 13.0 (LP: #1871972)

 -- Jeremy Bicha   Thu, 09 Apr 2020 21:27:07 -0400

** Changed in: pango1.0 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Update pango for Unicode 13.0

Status in pango1.0 package in Ubuntu:
  Fix Released

Bug description:
  Unicode 13 was released a month ago. The Pango library needs to be
  updated for the new emoji sequences for emoji that are implemented by
  multiple emoji in sequence to appear as a single character instead of
  as separate parts. For instance, https://emojipedia.org/black-cat/

  By doing this update for Ubuntu 20.04 LTS now, it will be easier to
  get full Unicode 13 support once Ubuntu's color emoji font (fonts-
  noto-color-emoji) is released with Unicode 13 support in a few months.

  I don't believe a freeze exception is necessary for this improvement
  now.

  https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1871972/+subscriptions

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

[Desktop-packages] [Bug 1769322] Re: Trackpoint reacts jumpy and isn't precise when moved a short distance

[Daniel van Vugt]

** Bug watch added: gitlab.freedesktop.org/libinput/libinput/issues #176
   https://gitlab.freedesktop.org/libinput/libinput/issues/176

** Also affects: libinput via
   https://gitlab.freedesktop.org/libinput/libinput/issues/176
   Importance: Unknown
   Status: Unknown

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

Title:
  Trackpoint reacts jumpy and isn't precise when moved a short distance

Status in libinput:
  Unknown
Status in libinput package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.freedesktop.org/libinput/libinput/issues/176

  ---

  I made a fresh install of Ubuntu 18.04 on a thinkPad t450s and t480s. The 
trackpoint reacts, especially if i want to move it only a small distance, very 
jumpy and erratic.
  It is very difficult to hit a precise spot on the screen because if I press 
with very littel pressure the cursor doesn't move and with a little more it 
makes a big jump. Somethimes it moves backwards first and then makes a jump in 
the intended direction. To summ up the trackpoint is very difficult to handle 
and changing the speedsettings doesn't change the issue.

  With Ubuntu 16.04 at least on the t450s everything worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libinput/+bug/1769322/+subscriptions

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

[Desktop-packages] [Bug 1872967] Re: Xorg crash

[Daniel van Vugt]

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

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

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

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

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

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

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

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

Title:
  Xorg crash

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Screen freezes when using LibreOffice writer, then crashes.

  After around a minute, the X session restarts and presents me with the
  login prompt.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 13:56:21 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:8a52] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:08b0]
  InstallationDate: Installed on 2019-12-02 (134 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 13 7390 2-in-1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash i915.enable_psr=0 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.9
  dmi.board.name: 06CDVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.9:bd08/02/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.
  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 19.2.8-0ubuntu0~19.10.3
  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-server/+bug/1872967/+subscriptions

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

[Desktop-packages] [Bug 1397045] Re: Words are not auto completed until user presses spacebar or some special keys

[Gunnar Hjalmarsson]

** Changed in: ibus-unikey (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Words are not auto completed until user presses spacebar or some
  special keys

Status in ibus-unikey package in Ubuntu:
  Confirmed

Bug description:
  Chatting in Facebook chat, I'm typing like in the middle of the word,
  then I press Enter. And then I notice that the last word which I was
  typing recently is sent but not in a complete form.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-unikey/+bug/1397045/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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] Re: Changing input method in top bar dropdown menu automatically sets it to STelex2 instead

[Falling Snowdin]

The maintainer seems to have looking for a successor for a year now;
they've maintained the package since 2012 which is extremely laudable.

Also I actually filed the GitHub issue you mentioned :)

-- 
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:
  In Progress

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 1873104] [NEW] Defaults to USB audio after every reboot

[Caleb McKay]

Public bug reported:

I manually set my audio output to the Line Out. Every reboot this
settings is lost and the system defaults back to the USB output. I have
several other distros to test - Ubuntu and its flavors are the only ones
that have this problem. Something changed in 19.04 or 19.10 that broke
this, and it continues to be an issue in 20.04.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  caleb  1778 F pulseaudio
 /dev/snd/controlC3:  caleb  1778 F pulseaudio
 /dev/snd/controlC1:  caleb  1778 F pulseaudio
 /dev/snd/controlC0:  caleb  1778 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Wed Apr 15 19:32:36 2020
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: USB sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/06/2018
dmi.bios.vendor: AMI
dmi.bios.version: F.30
dmi.board.name: 8437
dmi.board.vendor: HP
dmi.board.version: 1.3
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd09/06/2018:svnHP:pnOMENbyHPDesktopPC880-p1xx:pvr:rvnHP:rn8437:rvr1.3:cvnHP:ct3:cvr:
dmi.product.family: 103C_53311M HP Omen
dmi.product.name: OMEN by HP Desktop PC 880-p1xx
dmi.product.sku: 2TB61AV
dmi.sys.vendor: HP

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

Title:
  Defaults to USB audio after every reboot

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I manually set my audio output to the Line Out. Every reboot this
  settings is lost and the system defaults back to the USB output. I
  have several other distros to test - Ubuntu and its flavors are the
  only ones that have this problem. Something changed in 19.04 or 19.10
  that broke this, and it continues to be an issue in 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  caleb  1778 F pulseaudio
   /dev/snd/controlC3:  caleb  1778 F pulseaudio
   /dev/snd/controlC1:  caleb  1778 F pulseaudio
   /dev/snd/controlC0:  caleb  1778 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Wed Apr 15 19:32:36 2020
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.30
  dmi.board.name: 8437
  dmi.board.vendor: HP
  dmi.board.version: 1.3
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd09/06/2018:svnHP:pnOMENbyHPDesktopPC880-p1xx:pvr:rvnHP:rn8437:rvr1.3:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53311M HP Omen
  dmi.product.name: OMEN by HP Desktop PC 880-p1xx
  dmi.product.sku: 2TB61AV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1873104/+subscriptions

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

[Desktop-packages] [Bug 1397045] Re: Words are not auto completed until user presses spacebar or some special keys

[Falling Snowdin]

Yes, it's present in the 2 PPAs, the bug can act a bit different but the
core issue is the same.

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

Title:
  Words are not auto completed until user presses spacebar or some
  special keys

Status in ibus-unikey package in Ubuntu:
  Incomplete

Bug description:
  Chatting in Facebook chat, I'm typing like in the middle of the word,
  then I press Enter. And then I notice that the last word which I was
  typing recently is sent but not in a complete form.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-unikey/+bug/1397045/+subscriptions

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

[Desktop-packages] [Bug 1873013] Re: Chromium 83.0.4103.7 is randomly crashing tab

[guest271314]

Are these instructions https://wiki.ubuntu.com/Chromium/Debugging and
this package https://launchpad.net/~chromium-
team/+archive/ubuntu/dev/+build/19158997/+files/chromium-browser-
dbgsym_83.0.4103.7-0ubuntu0.18.04.1_i386.ddeb appliable for "Chromium
team" dev channel ppa?

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

Title:
  Chromium 83.0.4103.7 is randomly crashing tab

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1071071
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CasperVersion: 1.394
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGrz0RABEXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAaFDeAuHA4JEAQED4ANa0QAAAa/gBYVFJZOYBCMTQwSEFOQQKeAAoBCiAgAHg=
   modes: 1920x1080
  Desktop-Session:
   'ubuntustudio'
   '/etc/xdg/xdg-ubuntustudio:/etc/xdg:/etc/xdg'
   
'/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  DistroRelease: Ubuntu 18.04
  Env:
   'None'
   'None'
  InstalledPlugins:
   
  LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
  Load-Avg-1min: 0.44
  Load-Processes-Running-Percent:   0.1%
  MachineType: Dell Inc. Latitude E7440
  NonfreeKernelModules: overlay
  Package: chromium-browser 83.0.4103.7-0ubuntu0.18.04.1 [origin: 
LP-PPA-chromium-team-dev]
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz 
quiet splash --- BOOT_IMAGE=/casper/vmlinuz
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Tags: third-party-packages bionic
  ThirdParty: True
  Uname: Linux 4.15.0-20-lowlatency i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 03HFCG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1873013/+subscriptions

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

[Desktop-packages] [Bug 837285] Re: lightdm assert failure: lightdm: pam_mount.c:417: modify_pm_count: Assertion `user != ((void *)0)' failed.

[Bug Watch Updater]

** Changed in: libpam-mount (Debian)
   Status: New => Fix Released

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

Title:
  lightdm assert failure: lightdm: pam_mount.c:417: modify_pm_count:
  Assertion `user != ((void *)0)' failed.

Status in lightdm package in Ubuntu:
  Fix Released
Status in libpam-mount package in Debian:
  Fix Released

Bug description:
  Logged in with GNOME as session.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.9.3-0ubuntu8
  ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
  Uname: Linux 3.0.0-9-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  AssertionMessage: lightdm: pam_mount.c:417: modify_pm_count: Assertion `user 
!= ((void *)0)' failed.
  CrashCounter: 1
  Date: Tue Aug 30 12:18:08 2011
  ExecutablePath: /usr/sbin/lightdm
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  ProcCmdline: lightdm
  ProcEnviron: PATH=(custom, no user)
  Signal: 6
  SourcePackage: lightdm
  StacktraceTop:
   __GI___assert_fail (assertion=0x7f0c2294a63c "user != ((void *)0)", 
file=, line=417, function=) at assert.c:81
   ?? () from /lib/security/pam_mount.so
   pam_sm_close_session () from /lib/security/pam_mount.so
   ?? () from /lib/x86_64-linux-gnu/libpam.so.0
   ?? ()
  Title: lightdm assert failure: lightdm: pam_mount.c:417: modify_pm_count: 
Assertion `user != ((void *)0)' failed.
  UpgradeStatus: Upgraded to oneiric on 2011-08-19 (10 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/837285/+subscriptions

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

[Desktop-packages] [Bug 1603131] Re: Bengali Language already has its short code bn, so this package name is supposed to be fonts-bn-extra in place of fonts-beng-extra.

[Gunnar Hjalmarsson]

The package is included in a family of packages whose names all have
four letter language abbreviations. Examples:

fonts-deva-extra
fonts-guru-extra

No one would find a name change worth the effort. Closing.

** Changed in: fonts-beng-extra (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Bengali Language already has its short code bn, so this package name
  is supposed to be fonts-bn-extra in place of fonts-beng-extra.

Status in fonts-beng-extra package in Ubuntu:
  Won't Fix

Bug description:
  Bengali Language already has its short code bn, so this package name
  is supposed to be fonts-bn-extra in place of fonts-beng-extra and it
  sounds odd and looks like unprofessional naming.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-beng-extra/+bug/1603131/+subscriptions

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

[Desktop-packages] [Bug 1873013] Dependencies.txt

[guest271314]

apport information

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

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

Title:
  Chromium 83.0.4103.7 is randomly crashing tab

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1071071
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CasperVersion: 1.394
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGrz0RABEXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAaFDeAuHA4JEAQED4ANa0QAAAa/gBYVFJZOYBCMTQwSEFOQQKeAAoBCiAgAHg=
   modes: 1920x1080
  Desktop-Session:
   'ubuntustudio'
   '/etc/xdg/xdg-ubuntustudio:/etc/xdg:/etc/xdg'
   
'/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  DistroRelease: Ubuntu 18.04
  Env:
   'None'
   'None'
  InstalledPlugins:
   
  LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
  Load-Avg-1min: 0.44
  Load-Processes-Running-Percent:   0.1%
  MachineType: Dell Inc. Latitude E7440
  NonfreeKernelModules: overlay
  Package: chromium-browser 83.0.4103.7-0ubuntu0.18.04.1 [origin: 
LP-PPA-chromium-team-dev]
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz 
quiet splash --- BOOT_IMAGE=/casper/vmlinuz
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Tags: third-party-packages bionic
  ThirdParty: True
  Uname: Linux 4.15.0-20-lowlatency i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 03HFCG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1873013/+subscriptions

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

[Desktop-packages] [Bug 1873013] Re: Chromium 83.0.4103.7 is randomly crashing tab

[guest271314]

apport information

** Tags added: apport-collected bionic third-party-packages

** Description changed:

  https://bugs.chromium.org/p/chromium/issues/detail?id=1071071
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.14
+ Architecture: i386
+ CasperVersion: 1.394
+ CrashDB: ubuntu
+ CurrentDesktop: XFCE
+ DRM.card0-DP-1:
+  enabled: disabled
+  dpms: Off
+  status: disconnected
+  edid-base64: 
+  modes:
+ DRM.card0-HDMI-A-1:
+  enabled: disabled
+  dpms: Off
+  status: disconnected
+  edid-base64: 
+  modes:
+ DRM.card0-HDMI-A-2:
+  enabled: disabled
+  dpms: Off
+  status: disconnected
+  edid-base64: 
+  modes:
+ DRM.card0-eDP-1:
+  enabled: enabled
+  dpms: On
+  status: connected
+  edid-base64: 
AP///wAGrz0RABEXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAaFDeAuHA4JEAQED4ANa0QAAAa/gBYVFJZOYBCMTQwSEFOQQKeAAoBCiAgAHg=
+  modes: 1920x1080
+ Desktop-Session:
+  'ubuntustudio'
+  '/etc/xdg/xdg-ubuntustudio:/etc/xdg:/etc/xdg'
+  
'/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
+ DetectedPlugins:
+  
+ DistroRelease: Ubuntu 18.04
+ Env:
+  'None'
+  'None'
+ InstalledPlugins:
+  
+ LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
+ Load-Avg-1min: 0.44
+ Load-Processes-Running-Percent:   0.1%
+ MachineType: Dell Inc. Latitude E7440
+ NonfreeKernelModules: overlay
+ Package: chromium-browser 83.0.4103.7-0ubuntu0.18.04.1 [origin: 
LP-PPA-chromium-team-dev]
+ PackageArchitecture: i386
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C.UTF-8
+  SHELL=/bin/bash
+ ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz 
quiet splash --- BOOT_IMAGE=/casper/vmlinuz
+ ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
+ Tags: third-party-packages bionic
+ ThirdParty: True
+ Uname: Linux 4.15.0-20-lowlatency i686
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 05/01/2014
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: A09
+ dmi.board.name: 03HFCG
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 9
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr:
+ dmi.product.name: Latitude E7440
+ dmi.product.version: 01
+ dmi.sys.vendor: Dell Inc.
+ modified.conffile..etc.default.chromium-browser: [deleted]

** Attachment added: "ChromiumPrefs.txt"
   
https://bugs.launchpad.net/bugs/1873013/+attachment/5354960/+files/ChromiumPrefs.txt

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

Title:
  Chromium 83.0.4103.7 is randomly crashing tab

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1071071
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CasperVersion: 1.394
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGrz0RABEXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAaFDeAuHA4JEAQED4ANa0QAAAa/gBYVFJZOYBCMTQwSEFOQQKeAAoBCiAgAHg=
   modes: 1920x1080
  Desktop-Session:
   'ubuntustudio'
   '/etc/xdg/xdg-ubuntustudio:/etc/xdg:/etc/xdg'
   
'/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  DistroRelease: Ubuntu 18.04
  Env:
   'None'
   'None'
  InstalledPlugins:
   
  LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
  Load-Avg-1min: 0.44
  Load-Processes-Running-Percent:   0.1%
  MachineType: Dell Inc. Latitude E7440
  NonfreeKernelModules: overlay
  Package: chromium-browser 83.0.4103.7-0ubuntu0.18.04.1 [origin: 
LP-PPA-chromium-team-dev]
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz 
quiet splash --- BOOT_IMAGE=/casper/vmlinuz
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Tags: third-party-packages bionic
  ThirdParty: True
  Uname: Linux 

[Desktop-packages] [Bug 1873013] Lspci.txt

[guest271314]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1873013/+attachment/5354964/+files/Lspci.txt

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

Title:
  Chromium 83.0.4103.7 is randomly crashing tab

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1071071
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CasperVersion: 1.394
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGrz0RABEXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAaFDeAuHA4JEAQED4ANa0QAAAa/gBYVFJZOYBCMTQwSEFOQQKeAAoBCiAgAHg=
   modes: 1920x1080
  Desktop-Session:
   'ubuntustudio'
   '/etc/xdg/xdg-ubuntustudio:/etc/xdg:/etc/xdg'
   
'/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  DistroRelease: Ubuntu 18.04
  Env:
   'None'
   'None'
  InstalledPlugins:
   
  LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
  Load-Avg-1min: 0.44
  Load-Processes-Running-Percent:   0.1%
  MachineType: Dell Inc. Latitude E7440
  NonfreeKernelModules: overlay
  Package: chromium-browser 83.0.4103.7-0ubuntu0.18.04.1 [origin: 
LP-PPA-chromium-team-dev]
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz 
quiet splash --- BOOT_IMAGE=/casper/vmlinuz
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Tags: third-party-packages bionic
  ThirdParty: True
  Uname: Linux 4.15.0-20-lowlatency i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 03HFCG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1873013/+subscriptions

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

[Desktop-packages] [Bug 1873013] Re: Chromium 83.0.4103.7 is randomly crashing tab

[guest271314]

Ok. Ran the command and clicked "Send" at the prompt when the Chromium
crash report dialog was  launched.

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

Title:
  Chromium 83.0.4103.7 is randomly crashing tab

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1071071
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CasperVersion: 1.394
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGrz0RABEXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAaFDeAuHA4JEAQED4ANa0QAAAa/gBYVFJZOYBCMTQwSEFOQQKeAAoBCiAgAHg=
   modes: 1920x1080
  Desktop-Session:
   'ubuntustudio'
   '/etc/xdg/xdg-ubuntustudio:/etc/xdg:/etc/xdg'
   
'/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  DistroRelease: Ubuntu 18.04
  Env:
   'None'
   'None'
  InstalledPlugins:
   
  LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
  Load-Avg-1min: 0.44
  Load-Processes-Running-Percent:   0.1%
  MachineType: Dell Inc. Latitude E7440
  NonfreeKernelModules: overlay
  Package: chromium-browser 83.0.4103.7-0ubuntu0.18.04.1 [origin: 
LP-PPA-chromium-team-dev]
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz 
quiet splash --- BOOT_IMAGE=/casper/vmlinuz
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Tags: third-party-packages bionic
  ThirdParty: True
  Uname: Linux 4.15.0-20-lowlatency i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 03HFCG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1873013/+subscriptions

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

[Desktop-packages] [Bug 1873013] CurrentDmesg.txt

[guest271314]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1873013/+attachment/5354961/+files/CurrentDmesg.txt

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

Title:
  Chromium 83.0.4103.7 is randomly crashing tab

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1071071
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CasperVersion: 1.394
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGrz0RABEXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAaFDeAuHA4JEAQED4ANa0QAAAa/gBYVFJZOYBCMTQwSEFOQQKeAAoBCiAgAHg=
   modes: 1920x1080
  Desktop-Session:
   'ubuntustudio'
   '/etc/xdg/xdg-ubuntustudio:/etc/xdg:/etc/xdg'
   
'/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  DistroRelease: Ubuntu 18.04
  Env:
   'None'
   'None'
  InstalledPlugins:
   
  LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
  Load-Avg-1min: 0.44
  Load-Processes-Running-Percent:   0.1%
  MachineType: Dell Inc. Latitude E7440
  NonfreeKernelModules: overlay
  Package: chromium-browser 83.0.4103.7-0ubuntu0.18.04.1 [origin: 
LP-PPA-chromium-team-dev]
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz 
quiet splash --- BOOT_IMAGE=/casper/vmlinuz
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Tags: third-party-packages bionic
  ThirdParty: True
  Uname: Linux 4.15.0-20-lowlatency i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 03HFCG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1873013/+subscriptions

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

[Desktop-packages] [Bug 1873013] ProcInterrupts.txt

[guest271314]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1873013/+attachment/5354968/+files/ProcInterrupts.txt

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

Title:
  Chromium 83.0.4103.7 is randomly crashing tab

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1071071
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CasperVersion: 1.394
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGrz0RABEXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAaFDeAuHA4JEAQED4ANa0QAAAa/gBYVFJZOYBCMTQwSEFOQQKeAAoBCiAgAHg=
   modes: 1920x1080
  Desktop-Session:
   'ubuntustudio'
   '/etc/xdg/xdg-ubuntustudio:/etc/xdg:/etc/xdg'
   
'/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  DistroRelease: Ubuntu 18.04
  Env:
   'None'
   'None'
  InstalledPlugins:
   
  LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
  Load-Avg-1min: 0.44
  Load-Processes-Running-Percent:   0.1%
  MachineType: Dell Inc. Latitude E7440
  NonfreeKernelModules: overlay
  Package: chromium-browser 83.0.4103.7-0ubuntu0.18.04.1 [origin: 
LP-PPA-chromium-team-dev]
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz 
quiet splash --- BOOT_IMAGE=/casper/vmlinuz
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Tags: third-party-packages bionic
  ThirdParty: True
  Uname: Linux 4.15.0-20-lowlatency i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 03HFCG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1873013/+subscriptions

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

[Desktop-packages] [Bug 1873013] UdevDb.txt

[guest271314]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1873013/+attachment/5354972/+files/UdevDb.txt

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

Title:
  Chromium 83.0.4103.7 is randomly crashing tab

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1071071
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CasperVersion: 1.394
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGrz0RABEXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAaFDeAuHA4JEAQED4ANa0QAAAa/gBYVFJZOYBCMTQwSEFOQQKeAAoBCiAgAHg=
   modes: 1920x1080
  Desktop-Session:
   'ubuntustudio'
   '/etc/xdg/xdg-ubuntustudio:/etc/xdg:/etc/xdg'
   
'/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  DistroRelease: Ubuntu 18.04
  Env:
   'None'
   'None'
  InstalledPlugins:
   
  LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
  Load-Avg-1min: 0.44
  Load-Processes-Running-Percent:   0.1%
  MachineType: Dell Inc. Latitude E7440
  NonfreeKernelModules: overlay
  Package: chromium-browser 83.0.4103.7-0ubuntu0.18.04.1 [origin: 
LP-PPA-chromium-team-dev]
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz 
quiet splash --- BOOT_IMAGE=/casper/vmlinuz
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Tags: third-party-packages bionic
  ThirdParty: True
  Uname: Linux 4.15.0-20-lowlatency i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 03HFCG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1873013/+subscriptions

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

[Desktop-packages] [Bug 1873013] ProcModules.txt

[guest271314]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1873013/+attachment/5354969/+files/ProcModules.txt

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

Title:
  Chromium 83.0.4103.7 is randomly crashing tab

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1071071
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CasperVersion: 1.394
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGrz0RABEXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAaFDeAuHA4JEAQED4ANa0QAAAa/gBYVFJZOYBCMTQwSEFOQQKeAAoBCiAgAHg=
   modes: 1920x1080
  Desktop-Session:
   'ubuntustudio'
   '/etc/xdg/xdg-ubuntustudio:/etc/xdg:/etc/xdg'
   
'/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  DistroRelease: Ubuntu 18.04
  Env:
   'None'
   'None'
  InstalledPlugins:
   
  LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
  Load-Avg-1min: 0.44
  Load-Processes-Running-Percent:   0.1%
  MachineType: Dell Inc. Latitude E7440
  NonfreeKernelModules: overlay
  Package: chromium-browser 83.0.4103.7-0ubuntu0.18.04.1 [origin: 
LP-PPA-chromium-team-dev]
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz 
quiet splash --- BOOT_IMAGE=/casper/vmlinuz
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Tags: third-party-packages bionic
  ThirdParty: True
  Uname: Linux 4.15.0-20-lowlatency i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 03HFCG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1873013/+subscriptions

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

[Desktop-packages] [Bug 1873013] ProcCpuinfo.txt

[guest271314]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1873013/+attachment/5354966/+files/ProcCpuinfo.txt

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

Title:
  Chromium 83.0.4103.7 is randomly crashing tab

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1071071
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CasperVersion: 1.394
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGrz0RABEXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAaFDeAuHA4JEAQED4ANa0QAAAa/gBYVFJZOYBCMTQwSEFOQQKeAAoBCiAgAHg=
   modes: 1920x1080
  Desktop-Session:
   'ubuntustudio'
   '/etc/xdg/xdg-ubuntustudio:/etc/xdg:/etc/xdg'
   
'/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  DistroRelease: Ubuntu 18.04
  Env:
   'None'
   'None'
  InstalledPlugins:
   
  LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
  Load-Avg-1min: 0.44
  Load-Processes-Running-Percent:   0.1%
  MachineType: Dell Inc. Latitude E7440
  NonfreeKernelModules: overlay
  Package: chromium-browser 83.0.4103.7-0ubuntu0.18.04.1 [origin: 
LP-PPA-chromium-team-dev]
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz 
quiet splash --- BOOT_IMAGE=/casper/vmlinuz
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Tags: third-party-packages bionic
  ThirdParty: True
  Uname: Linux 4.15.0-20-lowlatency i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 03HFCG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1873013/+subscriptions

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

[Desktop-packages] [Bug 1873013] RelatedPackagesPolicy.txt

[guest271314]

apport information

** Attachment added: "RelatedPackagesPolicy.txt"
   
https://bugs.launchpad.net/bugs/1873013/+attachment/5354971/+files/RelatedPackagesPolicy.txt

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

Title:
  Chromium 83.0.4103.7 is randomly crashing tab

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1071071
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CasperVersion: 1.394
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGrz0RABEXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAaFDeAuHA4JEAQED4ANa0QAAAa/gBYVFJZOYBCMTQwSEFOQQKeAAoBCiAgAHg=
   modes: 1920x1080
  Desktop-Session:
   'ubuntustudio'
   '/etc/xdg/xdg-ubuntustudio:/etc/xdg:/etc/xdg'
   
'/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  DistroRelease: Ubuntu 18.04
  Env:
   'None'
   'None'
  InstalledPlugins:
   
  LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
  Load-Avg-1min: 0.44
  Load-Processes-Running-Percent:   0.1%
  MachineType: Dell Inc. Latitude E7440
  NonfreeKernelModules: overlay
  Package: chromium-browser 83.0.4103.7-0ubuntu0.18.04.1 [origin: 
LP-PPA-chromium-team-dev]
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz 
quiet splash --- BOOT_IMAGE=/casper/vmlinuz
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Tags: third-party-packages bionic
  ThirdParty: True
  Uname: Linux 4.15.0-20-lowlatency i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 03HFCG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1873013/+subscriptions

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

[Desktop-packages] [Bug 1873013] DiskUsage.txt

[guest271314]

apport information

** Attachment added: "DiskUsage.txt"
   
https://bugs.launchpad.net/bugs/1873013/+attachment/5354963/+files/DiskUsage.txt

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

Title:
  Chromium 83.0.4103.7 is randomly crashing tab

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1071071
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CasperVersion: 1.394
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGrz0RABEXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAaFDeAuHA4JEAQED4ANa0QAAAa/gBYVFJZOYBCMTQwSEFOQQKeAAoBCiAgAHg=
   modes: 1920x1080
  Desktop-Session:
   'ubuntustudio'
   '/etc/xdg/xdg-ubuntustudio:/etc/xdg:/etc/xdg'
   
'/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  DistroRelease: Ubuntu 18.04
  Env:
   'None'
   'None'
  InstalledPlugins:
   
  LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
  Load-Avg-1min: 0.44
  Load-Processes-Running-Percent:   0.1%
  MachineType: Dell Inc. Latitude E7440
  NonfreeKernelModules: overlay
  Package: chromium-browser 83.0.4103.7-0ubuntu0.18.04.1 [origin: 
LP-PPA-chromium-team-dev]
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz 
quiet splash --- BOOT_IMAGE=/casper/vmlinuz
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Tags: third-party-packages bionic
  ThirdParty: True
  Uname: Linux 4.15.0-20-lowlatency i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 03HFCG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1873013/+subscriptions

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

[Desktop-packages] [Bug 1873013] RelatedPackageVersions.txt

[guest271314]

apport information

** Attachment added: "RelatedPackageVersions.txt"
   
https://bugs.launchpad.net/bugs/1873013/+attachment/5354970/+files/RelatedPackageVersions.txt

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

Title:
  Chromium 83.0.4103.7 is randomly crashing tab

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1071071
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CasperVersion: 1.394
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGrz0RABEXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAaFDeAuHA4JEAQED4ANa0QAAAa/gBYVFJZOYBCMTQwSEFOQQKeAAoBCiAgAHg=
   modes: 1920x1080
  Desktop-Session:
   'ubuntustudio'
   '/etc/xdg/xdg-ubuntustudio:/etc/xdg:/etc/xdg'
   
'/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  DistroRelease: Ubuntu 18.04
  Env:
   'None'
   'None'
  InstalledPlugins:
   
  LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
  Load-Avg-1min: 0.44
  Load-Processes-Running-Percent:   0.1%
  MachineType: Dell Inc. Latitude E7440
  NonfreeKernelModules: overlay
  Package: chromium-browser 83.0.4103.7-0ubuntu0.18.04.1 [origin: 
LP-PPA-chromium-team-dev]
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz 
quiet splash --- BOOT_IMAGE=/casper/vmlinuz
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Tags: third-party-packages bionic
  ThirdParty: True
  Uname: Linux 4.15.0-20-lowlatency i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 03HFCG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1873013/+subscriptions

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

[Desktop-packages] [Bug 1873093] Re: Gnome-terminal tab bar steals keyboard focus

[Nick Phillips]

See upstream bug report for more details.

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

Title:
  Gnome-terminal tab bar steals keyboard focus

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I'm not sure when it started, but using the version of Gnome-Terminal
  in latest ubuntu (GT 3.34.2), I regularly find the tab bar stealing
  keyboard focus.

  This is dangerous.

  The problem is usually that I click on a tab, leave the mouse there,
  and start typing. The tab bar then steals the first character typed.
  Sometimes I click in the terminal window, and then move the mouse out
  of the way (to the tab bar). Sometimes it happens later, when the
  mouse drifts onto a tab (maybe I knock it slightly while typing).

  There are many cases in which the unexpected loss of a character typed
  could lead to significant damage. For example,

  rm *~

  losing the tilde. Or

  sudo rm -rf /mnt/1/*

  losing the 1.

  I have preferred click to focus (as opposed to focus-follows-mouse) in
  X for nearly 30 years. Gnome-Terminal should not pervert this
  preference.

  Reported upstream - https://gitlab.gnome.org/GNOME/gnome-
  terminal/-/issues/245

  Not clear that this is 100% a bug with gnome-terminal, or whether it
  is an interaction between it and another part of the XWayland/gnome
  /gnome-shell setup.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-terminal 3.34.2-1ubuntu1
  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: GNOME
  Date: Thu Apr 16 10:16:15 2020
  InstallationDate: Installed on 2020-03-15 (31 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1873013] ProcCpuinfoMinimal.txt

[guest271314]

apport information

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

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

Title:
  Chromium 83.0.4103.7 is randomly crashing tab

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1071071
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CasperVersion: 1.394
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGrz0RABEXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAaFDeAuHA4JEAQED4ANa0QAAAa/gBYVFJZOYBCMTQwSEFOQQKeAAoBCiAgAHg=
   modes: 1920x1080
  Desktop-Session:
   'ubuntustudio'
   '/etc/xdg/xdg-ubuntustudio:/etc/xdg:/etc/xdg'
   
'/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  DistroRelease: Ubuntu 18.04
  Env:
   'None'
   'None'
  InstalledPlugins:
   
  LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
  Load-Avg-1min: 0.44
  Load-Processes-Running-Percent:   0.1%
  MachineType: Dell Inc. Latitude E7440
  NonfreeKernelModules: overlay
  Package: chromium-browser 83.0.4103.7-0ubuntu0.18.04.1 [origin: 
LP-PPA-chromium-team-dev]
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz 
quiet splash --- BOOT_IMAGE=/casper/vmlinuz
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Tags: third-party-packages bionic
  ThirdParty: True
  Uname: Linux 4.15.0-20-lowlatency i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 03HFCG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1873013/+subscriptions

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

[Desktop-packages] [Bug 1873013] Lsusb.txt

[guest271314]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1873013/+attachment/5354965/+files/Lsusb.txt

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

Title:
  Chromium 83.0.4103.7 is randomly crashing tab

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1071071
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CasperVersion: 1.394
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGrz0RABEXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAaFDeAuHA4JEAQED4ANa0QAAAa/gBYVFJZOYBCMTQwSEFOQQKeAAoBCiAgAHg=
   modes: 1920x1080
  Desktop-Session:
   'ubuntustudio'
   '/etc/xdg/xdg-ubuntustudio:/etc/xdg:/etc/xdg'
   
'/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  DistroRelease: Ubuntu 18.04
  Env:
   'None'
   'None'
  InstalledPlugins:
   
  LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
  Load-Avg-1min: 0.44
  Load-Processes-Running-Percent:   0.1%
  MachineType: Dell Inc. Latitude E7440
  NonfreeKernelModules: overlay
  Package: chromium-browser 83.0.4103.7-0ubuntu0.18.04.1 [origin: 
LP-PPA-chromium-team-dev]
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz 
quiet splash --- BOOT_IMAGE=/casper/vmlinuz
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Tags: third-party-packages bionic
  ThirdParty: True
  Uname: Linux 4.15.0-20-lowlatency i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 03HFCG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1873013/+subscriptions

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

[Desktop-packages] [Bug 1872162] Re: crash report fail to submit

[Brian Murray]

apport does create or use a submit.log file.

** Package changed: apport (Ubuntu) => firefox (Ubuntu)

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

Title:
  crash report fail to submit

Status in firefox package in Ubuntu:
  New

Bug description:
  Since 2020-03-19, firefox crashed about 17 times (it did not crash 1,5
  years before). Though, all crash reports failed to submit. My firefox
  crash report submit.log reads:

  [Mo 17 Dez 2018 00:14:42 CET] Crash report submitted successfully
  [Do 19 Mär 2020 00:06:24 CET] Crash report submission failed: Couldn't 
connect to server
  [Sa 21 Mär 2020 15:14:19 CET] Crash report submission failed: Couldn't 
connect to server
  [Di 24 Mär 2020 23:22:51 CET] Crash report submission failed: Couldn't 
connect to server
  [Mi 25 Mär 2020 14:22:41 CET] Crash report submission failed: Couldn't 
connect to server
  [Do 26 Mär 2020 17:40:46 CET] Crash report submission failed: Couldn't 
connect to server
  [Sa 28 Mär 2020 10:59:32 CET] Crash report submission failed: Couldn't 
connect to server
  [Mo 30 Mär 2020 01:03:56 CEST] Crash report submission failed: Couldn't 
connect to server
  [Mi 01 Apr 2020 16:01:11 CEST] Crash report submission failed: Couldn't 
connect to server
  [Do 02 Apr 2020 20:39:29 CEST] Crash report submission failed: Couldn't 
connect to server
  [Fr 03 Apr 2020 21:07:53 CEST] Crash report submission failed: Couldn't 
connect to server
  [So 05 Apr 2020 22:38:08 CEST] Crash report submission failed: Couldn't 
connect to server
  [Di 07 Apr 2020 21:40:43 CEST] Crash report submission failed: Couldn't 
connect to server
  [Mi 08 Apr 2020 13:05:39 CEST] Crash report submission failed: Couldn't 
connect to server
  [Mi 08 Apr 2020 20:16:28 CEST] Crash report submission failed: Couldn't 
connect to server
  [Mi 08 Apr 2020 22:27:58 CEST] Crash report submission failed: Couldn't 
connect to server
  [Do 09 Apr 2020 23:36:31 CEST] Crash report submission failed: Couldn't 
connect to server
  [Fr 10 Apr 2020 20:07:48 CEST] Crash report submission failed: Couldn't 
connect to server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1872162/+subscriptions

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

[Desktop-packages] [Bug 1872853] Re: Keys stuck on repeat when key triggers sound, and output device is ClearOne Chat 50

[Brian Murray]

** Tags added: bionic

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

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

Title:
  Keys stuck on repeat when key triggers sound, and output device is
  ClearOne Chat 50

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I am typing in a gnome terminal, any time I press a key that
  triggers a sound (e.g., hitting "backspace" when already at the
  beginning of the command line, hitting "tab" for tab completion when
  there are multiple possible completion options), the key gets stuck on
  repeat. The sound plays over and over. If I move the mouse to other
  windows and focus on them, the repeated key continues there. (I have
  focus-follows-mouse enabled, if that matters.)

  This is 100% reproducible. But I have tracked it down to only occuring
  when I go into Settings->Sounds, select the "Output" tab, and choose
  the "Analog Output - Chat 50" device for sound output.

  I do have a ClearOne Chat 50 plugged into my computer via USB. It
  seems to be operating correctly for both input and output sound
  (ignoring the key repeat issue).

  Before figuring out that changing the sound output to be something
  other than the Chat 50, I ruled out the keyboard being the problem by
  swapping in a different model of USB keyboard. I also rebooted the
  system, and that made no difference either.

  I saw other bugs about repeating keys, such as bug #124406. I did try
  disabling repeat with "xset r off". This seems to stop the repeated
  key from taking effect in, say, Gnome terminal. But the repeating key
  is probably still being issued somewhere in the system because when I
  then trigger the bug the keyboard becomes unusable until I unplug it
  and plug it back in again.

  In all cases, unplugging the USB keyboard and plugging it back in
  again eliminates the stuck repeating key.

  I apologize for not selecting a particular package for this bug. This
  bug does only seem to occur when the ClearOne Chat 50 is selected as
  the output sound device, but I'm completely unclear about how an
  output sound device could case key presses to operate incorrectly. I
  does not seem like the sound device should be able to cause a keypress
  to repeat even if the sound driver is buggy.

  
  Ubuntu 18.04.4 LTS.
  Linux mal 4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1872162] [NEW] crash report fail to submit

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Since 2020-03-19, firefox crashed about 17 times (it did not crash 1,5
years before). Though, all crash reports failed to submit. My firefox
crash report submit.log reads:

[Mo 17 Dez 2018 00:14:42 CET] Crash report submitted successfully
[Do 19 Mär 2020 00:06:24 CET] Crash report submission failed: Couldn't connect 
to server
[Sa 21 Mär 2020 15:14:19 CET] Crash report submission failed: Couldn't connect 
to server
[Di 24 Mär 2020 23:22:51 CET] Crash report submission failed: Couldn't connect 
to server
[Mi 25 Mär 2020 14:22:41 CET] Crash report submission failed: Couldn't connect 
to server
[Do 26 Mär 2020 17:40:46 CET] Crash report submission failed: Couldn't connect 
to server
[Sa 28 Mär 2020 10:59:32 CET] Crash report submission failed: Couldn't connect 
to server
[Mo 30 Mär 2020 01:03:56 CEST] Crash report submission failed: Couldn't connect 
to server
[Mi 01 Apr 2020 16:01:11 CEST] Crash report submission failed: Couldn't connect 
to server
[Do 02 Apr 2020 20:39:29 CEST] Crash report submission failed: Couldn't connect 
to server
[Fr 03 Apr 2020 21:07:53 CEST] Crash report submission failed: Couldn't connect 
to server
[So 05 Apr 2020 22:38:08 CEST] Crash report submission failed: Couldn't connect 
to server
[Di 07 Apr 2020 21:40:43 CEST] Crash report submission failed: Couldn't connect 
to server
[Mi 08 Apr 2020 13:05:39 CEST] Crash report submission failed: Couldn't connect 
to server
[Mi 08 Apr 2020 20:16:28 CEST] Crash report submission failed: Couldn't connect 
to server
[Mi 08 Apr 2020 22:27:58 CEST] Crash report submission failed: Couldn't connect 
to server
[Do 09 Apr 2020 23:36:31 CEST] Crash report submission failed: Couldn't connect 
to server
[Fr 10 Apr 2020 20:07:48 CEST] Crash report submission failed: Couldn't connect 
to server

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

-- 
crash report fail to submit
https://bugs.launchpad.net/bugs/1872162
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to firefox 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 1872853] [NEW] Keys stuck on repeat when key triggers sound, and output device is ClearOne Chat 50

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When I am typing in a gnome terminal, any time I press a key that
triggers a sound (e.g., hitting "backspace" when already at the
beginning of the command line, hitting "tab" for tab completion when
there are multiple possible completion options), the key gets stuck on
repeat. The sound plays over and over. If I move the mouse to other
windows and focus on them, the repeated key continues there. (I have
focus-follows-mouse enabled, if that matters.)

This is 100% reproducible. But I have tracked it down to only occuring
when I go into Settings->Sounds, select the "Output" tab, and choose the
"Analog Output - Chat 50" device for sound output.

I do have a ClearOne Chat 50 plugged into my computer via USB. It seems
to be operating correctly for both input and output sound (ignoring the
key repeat issue).

Before figuring out that changing the sound output to be something other
than the Chat 50, I ruled out the keyboard being the problem by swapping
in a different model of USB keyboard. I also rebooted the system, and
that made no difference either.

I saw other bugs about repeating keys, such as bug #124406. I did try
disabling repeat with "xset r off". This seems to stop the repeated key
from taking effect in, say, Gnome terminal. But the repeating key is
probably still being issued somewhere in the system because when I then
trigger the bug the keyboard becomes unusable until I unplug it and plug
it back in again.

In all cases, unplugging the USB keyboard and plugging it back in again
eliminates the stuck repeating key.

I apologize for not selecting a particular package for this bug. This
bug does only seem to occur when the ClearOne Chat 50 is selected as the
output sound device, but I'm completely unclear about how an output
sound device could case key presses to operate incorrectly. I does not
seem like the sound device should be able to cause a keypress to repeat
even if the sound driver is buggy.


Ubuntu 18.04.4 LTS.
Linux mal 4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

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


** Tags: bionic bot-comment
-- 
Keys stuck on repeat when key triggers sound, and output device is ClearOne 
Chat 50
https://bugs.launchpad.net/bugs/1872853
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 1793496] Re: scaling changes when closing/re-opening the lid

[Treviño]

Ok, finally found the root issue.

Handled at https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1200

** Changed in: mutter
   Importance: Unknown => Undecided

** Changed in: mutter
   Status: Fix Released => New

** Changed in: mutter
 Remote watch: gitlab.gnome.org/GNOME/mutter/issues #407 => None

** Changed in: mutter (Ubuntu Focal)
   Status: Triaged => In Progress

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

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

Title:
  scaling changes when closing/re-opening the lid

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Bionic:
  Confirmed
Status in mutter source package in Focal:
  In Progress

Bug description:
  scaling changes when closing/re-opening the lid. Seen in bionic.

  Mz scaling is set to 100%, but the laptop is considered highdpi by
  mutter, and during suspend/resume it changes back to default ignoring
  settings.

  $ xprop -spy -root RESOURCE_MANAGER
  [...]
  RESOURCE_MANAGER(STRING) = 
"*customization:\t-color\nXft.dpi:\t192\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t48\nXcursor.theme:\tDMZ-White\n"
  RESOURCE_MANAGER(STRING) = 
"*customization:\t-color\nXft.dpi:\t96\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t24\nXcursor.theme:\tDMZ-White\n"

  xrandr
  Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
  eDP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y 
axis) 309mm x 174mm
 2560x1440 60.00*+  59.9959.9959.9659.95

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1793496/+subscriptions

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

[Desktop-packages] [Bug 1397045] Re: Words are not auto completed until user presses spacebar or some special keys

[Gunnar Hjalmarsson]

Is this issue present in the versions in these PPAs:

https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-unikey

https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-unikey2

** Changed in: ibus-unikey (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Words are not auto completed until user presses spacebar or some
  special keys

Status in ibus-unikey package in Ubuntu:
  Incomplete

Bug description:
  Chatting in Facebook chat, I'm typing like in the middle of the word,
  then I press Enter. And then I notice that the last word which I was
  typing recently is sent but not in a complete form.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-unikey/+bug/1397045/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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] Re: Changing input method in top bar dropdown menu automatically sets it to STelex2 instead

[Gunnar Hjalmarsson]

Thanks for the feedback! I'm glad you appreciate it.

The deprecation message is included in ppa:gunnarhj/ibus-unikey. If you
have that version installed, the message is located in the
/usr/share/doc/ibus-unikey/README.md file. That message is a downer, of
course. Is the project really maintained when the author/maintainer has
expressed an intention to step down? See also .

Anyway, it's good that you agree that we should still use that version
for now.

On 2020-04-15 21:59, Falling Snowdin wrote:
> Moreover, both your PPAs correctly used my Colemak keyboard layout
> and solved the Super key issue I mentioned in bug #1872325. That's a
> plus from me.

That's a coincidence. The explanation is that while English (US) is hard
coded as underlying layout in the version in the archive, ibus-unikey in
the PPAs use "default" instead. So in your case you now have Colemak as
the underlying layout when using ibus-unikey. You would probably have
been less happy if e.g. Russian had been your supplementary input
source. ;)

In other words: That gnome-shell bug is not fixed, even if it doesn't
affect you any longer.

> It would be preferable if there was an option to change the input
> method from the top bar dropdown menu like in the second PPA and the
> original ibus-unikey, it's important as basically the only thing
> users change in Unikey is the input method.

The only thing I can say about that is that the difference is just one
click, i.e. you need to click "More settings..." before you can switch
input method.

@Lê Quốc Tuấn: If you see this, do you have any thoughts?

** Bug watch added: github.com/vn-input/ibus-unikey/issues #24
   https://github.com/vn-input/ibus-unikey/issues/24

-- 
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:
  In Progress

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 1866841] Re: Add chrome-gnome-shell to ubuntu-desktop recommends

[Jeremy Bicha]

@AsciiWorld, unless things changed in Ubuntu 20.04 LTS, you can use the
Software app to install GNOME Shell extensions.

chrome-gnome-shell is in universe. It needs to be in main before it can
be installed by default in the Canonical-supported flavors. See
https://wiki.ubuntu.com/MainInclusionProcess and bug 1695565

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

Title:
  Add chrome-gnome-shell to ubuntu-desktop recommends

Status in One Hundred Papercuts:
  Opinion
Status in chrome-gnome-shell package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Opinion

Bug description:
  Please, consider adding the chrome-gnome-shell package as a
  recommended dependency for ubuntu-desktop package in Ubuntu 20.04. The
  chrome-gnome-shell package provides GNOME Shell integration
  (connector) for Firefox, Chrome, Chromium and other web browsers that
  is necessary for users to be able to manage GNOME Shell extensions
  using a extensions.gnome.org website. Since the Shell Extensions
  support was removed from gnome-software since 3.36 and the replacement
  Extensions application cannot be used to find and install new
  extensions, there is not any user friendly way to install new Shell
  Extensions without having the chrome-gnome-shell package installed.

  More information:
  https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1866841/+subscriptions

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

[Desktop-packages] [Bug 1795109] Re: gnome-software spams syslog with assertion errors: json_object_has_member: assertion 'member_name != NULL' failed | g_strsplit: assertion 'string != NULL' failed |

[mgfrobozz]

In my system, this started with ...

Apr 15 06:04:21 localhost dbus-daemon[1208]: [system] Activating via systemd: 
service name='org.freedesktop.fwupd' unit='fwupd.service' requested by ':1.175' 
(uid=1000 pid=5172 comm="/usr/bin/gnome-software --gapplication-service " 
label="unconfined")
Apr 15 06:04:21 localhost systemd[1]: Starting Firmware update daemon...
Apr 15 06:04:21 localhost fwupd[23190]: 13:04:21:0837 FuPluginUefi 
kernel efivars support missing: /sys/firmware/efi/efivars
Apr 15 06:04:21 localhost dbus-daemon[1208]: [system] Successfully activated 
service 'org.freedesktop.fwupd'
Apr 15 06:04:21 localhost systemd[1]: Started Firmware update daemon.
Apr 15 06:04:23 localhost gnome-software[5172]: json_object_has_member: 
assertion 'member_name != NULL' failed

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

Title:
  gnome-software spams syslog with assertion errors:
  json_object_has_member: assertion 'member_name != NULL' failed |
  g_strsplit: assertion 'string != NULL' failed | g_strv_length:
  assertion 'str_array != NULL' failed

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  The fan and cpu is very active during this event, thousands of
  assertions reported. Syslog case attached.

  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  apt-cache policy gnome-software
  gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.3
Candidate: 3.28.1-0ubuntu4.18.04.3
Version table:
   *** 3.28.1-0ubuntu4.18.04.3 500
  500 http://ftp.acc.umu.se/ubuntu bionic-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   3.28.1-0ubuntu4 500
  500 http://ftp.acc.umu.se/ubuntu bionic/main amd64 Package

  apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.28.3-0ubuntu0.18.04.2
Candidate: 3.28.3-0ubuntu0.18.04.2
Version table:
   *** 3.28.3-0ubuntu0.18.04.2 500
  500 http://ftp.acc.umu.se/ubuntu bionic-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   3.28.1-0ubuntu2 500
  500 http://ftp.acc.umu.se/ubuntu bionic/main amd64 Packages

  uname -a
  Linux computer 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  gnome-shell --version
  GNOME Shell 3.28.3

  Sep 29 06:58:01 computer gnome-software[2694]: json_object_has_member: 
assertion 'member_name != NULL' failed 
  Sep 29 06:58:01 computer gnome-software[2694]: g_strsplit: assertion 'string 
!= NULL' failed 
  Sep 29 06:58:01 computer gnome-software[2694]: g_strv_length: assertion 
'str_array != NULL' failed 
  Sep 29 06:58:01 computer gnome-software[2694]: json_object_has_member: 
assertion 'member_name != NULL' failed 
  Sep 29 06:58:01 computer gnome-software[2694]: g_strsplit: assertion 'string 
!= NULL' failed 
  Sep 29 06:58:01 computer gnome-software[2694]: g_strv_length: assertion 
'str_array != NULL' failed 
  Sep 29 06:58:01 computer gnome-software[2694]: json_object_has_member: 
assertion 'member_name != NULL' failed 
  Sep 29 06:58:01 computer gnome-software[2694]: g_strsplit: assertion 'string 
!= NULL' failed
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2015-07-18 (1168 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed

[dann frazier]

The ubuntu-drivers-common task here appears to be to change it to prefer
the pre-built/signed drivers (linux-modules-nvidia-*) over the DKMS
counterparts. I'd recommend at that point that we start seeding linux-
modules-nvidia-[0-9]+-generic onto the desktop ISO instead of the DKMS
counterparts, so the offline install experiences matches.

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  nvidia-435 is in eoan, linux-restricted-modules only builds against
  430, ubiquity gives me the self-signed modules experience instead of
  using the Canonical-signed modules

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  New
Status in linux source package in Eoan:
  Fix Released
Status in linux-restricted-modules source package in Eoan:
  Fix Released
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed
Status in ubuntu-drivers-common source package in Eoan:
  Confirmed
Status in ubuntu-meta source package in Eoan:
  New

Bug description:
  SRU Justification

  Impact: The nvidia-435 drivers are missing from linux-restricted-
  modules in eoan. On install ubuntu-drivers picks 435 as the newest
  version, and users must use self-signed dkms drivers and enroll a MOK.

  Fix: Add nvidia-435 dkms builds to linux and l-r-m for eoan.

  Test Case: A test build is available in ppa:sforshee/test-builds.
  Verify that signed drivers for nvidia-435 can be installed for eoan
  via the linux-modules-nvidia-435-{generic,lowlatency} packages.

  Regression Potential: The nvidia-435 l-r-m drivers are new packages
  built from the same source as the nvidia-435 dkms driver, so
  regressions are unlikely.

  ---

  The linux-restricted-modules package exists so that users who install
  the nvidia drivers can get known-good, signed modules instead of
  having to locally self-sign and enroll a signing key through MOK.  But
  lrm in eoan is only building driver packages for nvidia 390 and 430,
  and nvidia 435 is present in eoan.

  So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
  newest driver instead of using the signed 430 driver.

  We should never allow the archive to get into this situation.  We
  should be enforcing that any version of the nvidia driver that we
  expect ubuntu-drivers to install by default on any hardware is
  integrated into linux-restricted-modules, and we should ensure that
  ubuntu-drivers always prefers the signed drivers over other options.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+subscriptions

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

[Desktop-packages] [Bug 1873093] [NEW] Gnome-terminal tab bar steals keyboard focus

[Nick Phillips]

Public bug reported:

I'm not sure when it started, but using the version of Gnome-Terminal in
latest ubuntu (GT 3.34.2), I regularly find the tab bar stealing
keyboard focus.

This is dangerous.

The problem is usually that I click on a tab, leave the mouse there, and
start typing. The tab bar then steals the first character typed.
Sometimes I click in the terminal window, and then move the mouse out of
the way (to the tab bar). Sometimes it happens later, when the mouse
drifts onto a tab (maybe I knock it slightly while typing).

There are many cases in which the unexpected loss of a character typed
could lead to significant damage. For example,

rm *~

losing the tilde. Or

sudo rm -rf /mnt/1/*

losing the 1.

I have preferred click to focus (as opposed to focus-follows-mouse) in X
for nearly 30 years. Gnome-Terminal should not pervert this preference.

Reported upstream - https://gitlab.gnome.org/GNOME/gnome-
terminal/-/issues/245

Not clear that this is 100% a bug with gnome-terminal, or whether it is
an interaction between it and another part of the XWayland/gnome/gnome-
shell setup.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-terminal 3.34.2-1ubuntu1
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: GNOME
Date: Thu Apr 16 10:16:15 2020
InstallationDate: Installed on 2020-03-15 (31 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Gnome-terminal tab bar steals keyboard focus

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I'm not sure when it started, but using the version of Gnome-Terminal
  in latest ubuntu (GT 3.34.2), I regularly find the tab bar stealing
  keyboard focus.

  This is dangerous.

  The problem is usually that I click on a tab, leave the mouse there,
  and start typing. The tab bar then steals the first character typed.
  Sometimes I click in the terminal window, and then move the mouse out
  of the way (to the tab bar). Sometimes it happens later, when the
  mouse drifts onto a tab (maybe I knock it slightly while typing).

  There are many cases in which the unexpected loss of a character typed
  could lead to significant damage. For example,

  rm *~

  losing the tilde. Or

  sudo rm -rf /mnt/1/*

  losing the 1.

  I have preferred click to focus (as opposed to focus-follows-mouse) in
  X for nearly 30 years. Gnome-Terminal should not pervert this
  preference.

  Reported upstream - https://gitlab.gnome.org/GNOME/gnome-
  terminal/-/issues/245

  Not clear that this is 100% a bug with gnome-terminal, or whether it
  is an interaction between it and another part of the XWayland/gnome
  /gnome-shell setup.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-terminal 3.34.2-1ubuntu1
  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: GNOME
  Date: Thu Apr 16 10:16:15 2020
  InstallationDate: Installed on 2020-03-15 (31 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1721674] Re: Scan All Pages From Feeder action scans the first page and feeds the rest without scanning

[Bartosz Kosiorek]

Please attach debug logs from simple-scan after scanning

** Changed in: simple-scan (Ubuntu)
   Status: New => Invalid

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

Title:
  Scan All Pages From Feeder action scans the first page and feeds the
  rest without scanning

Status in simple-scan package in Ubuntu:
  Invalid

Bug description:
  "Scan All Pages From Feeder" action scans the first page and feeds the
  rest without scanning them.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: simple-scan 3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  5 18:31:19 2017
  InstallationDate: Installed on 2017-10-03 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=a393d6b9-0886-4a0a-b2be-5111bfcf9ada ro quiet splash
  SimpleScanLog:
   
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1721674/+subscriptions

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

[Desktop-packages] [Bug 1709890] Re: Simple Scan Ignores Back or Front & Back Selections Fujitsu ScanSnap iX500

[Bartosz Kosiorek]

** Changed in: simple-scan (Ubuntu)
   Status: New => Invalid

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

Title:
  Simple Scan Ignores Back or Front & Back Selections Fujitsu ScanSnap
  iX500

Status in simple-scan package in Ubuntu:
  Invalid

Bug description:
  What I expect to happen: I expect to get scan output from the back of
  the page when back is selected, front and back output when front &
  back is selected in preferences.

  What happens: only front is shown.

  
  $ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  $ apt-cache policy simple-scan
  simple-scan:
Installed: 3.20.0-0ubuntu1
Candidate: 3.20.0-0ubuntu1
Version table:
   *** 3.20.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1709890/+subscriptions

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

[Desktop-packages] [Bug 1714636] Re: simple-scan does not communicate with scanner, also it is found with "lsusb" and "scanimage -L"

[Bartosz Kosiorek]

** Changed in: simple-scan (Ubuntu)
   Status: New => Invalid

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

Title:
  simple-scan does not communicate with scanner, also it is found with
  "lsusb" and "scanimage -L"

Status in simple-scan package in Ubuntu:
  Invalid

Bug description:
  It seems simple-scan can no longer communicate with my scanner,
  although it was able to scan with the same hardware before. The
  hardware is found, but simple-scan reports communication errors. The
  hardware itself works.

  user@host:$ lsusb
  Bus 002 Device 002: ID 058f:9380 Alcor Micro Corp. Flash Drive
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 005: ID 04a9:176d Canon, Inc. PIXMA MG2550
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

  

  user@host:$ lsusb
  Bus 002 Device 002: ID 058f:9380 Alcor Micro Corp. Flash Drive
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

  

  user@host:$ sudo scanimage -L
  [sudo] Passwort für user: 
  device `pixma:04A9176D_1B4C43' is a CANON Canon PIXMA MG2500 Series 
multi-function peripheral

  

  user@host:$ groups
  user adm cdrom sudo dip plugdev lpadmin sambashare

  user@host:$ sudo adduser user lpadmin
  Der Benutzer »user« ist bereits ein Mitglied der Gruppe »lpadmin«.

  user@host:$ sudo chmod o+wr /dev/bus/usb/00*/*

  

  ==> still the same error

  user@host:$ ubuntu-bug -w
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: simple-scan 3.20.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep  2 08:48:09 2017
  ExecutablePath: /usr/bin/simple-scan
  InstallationDate: Installed on 2014-11-24 (1012 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard HP Compaq dc7900 Convertible Minitower
  ProcEnviron:
   PATH=(custom, username)
   SHELL=/bin/bash
   LANG=de_DE.UTF-8
   LANGUAGE=de_DE
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to xenial on 2016-11-07 (298 days ago)
  dmi.bios.date: 03/05/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G1 v01.16
  dmi.board.asset.tag: CZC9368N0K
  dmi.board.name: 3032h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC9368N0K
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G1v01.16:bd03/05/2009:svnHewlett-Packard:pnHPCompaqdc7900ConvertibleMinitower:pvr:rvnHewlett-Packard:rn3032h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq dc7900 Convertible Minitower
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1714636/+subscriptions

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

[Desktop-packages] [Bug 1398151] Re: Clicking the "Text"/"Photo" items in the toolbar doesn't update the selected option in the menu

[Bartosz Kosiorek]

** Changed in: simple-scan (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Clicking the "Text"/"Photo" items in the toolbar doesn't update the
  selected option in the menu

Status in simple-scan package in Ubuntu:
  Fix Released

Bug description:
  The Document>Scan menu has two radio buttons: "Text" and "Photo".
  The toolbar menu (arrow after the "Scan" button) also contains those radio 
buttons.

  If you select one of those buttons in the Document>Scan menu, the selected 
option in the toolbar menu is also updated.
  However, when you select one of the radio buttons in the toolbar menu, the 
selected option in the Document>Scan menu is NOT updated. The scan quality is 
successfully changed, though!

  Also, it's very difficult to see which option is selected in the
  toolbar menu, at least with the default Ubuntu theme. The menu has a
  dark background and the "selected" mark is gray.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: simple-scan 3.12.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec  1 19:29:26 2014
  DriverPackageVersions:
   libsane 1.0.23-3ubuntu3.1
   libsane-extras N/A
   hplip 3.14.3-0ubuntu3.2
   hpoj N/A
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (49 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Acer Aspire 5742G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-40-generic 
root=UUID=b4482598-1b35-4927-a61c-9e0529c1c609 ro locale=pt_PT quiet splash 
video.use_native_backlight=1
  SimpleScanLog:

  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5742G
  dmi.board.vendor: Acer
  dmi.board.version: V1.30
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.30
  dmi.modalias: 
dmi:bvnAcer:bvrV1.30:bd08/13/2012:svnAcer:pnAspire5742G:pvrV1.30:rvnAcer:rnAspire5742G:rvrV1.30:cvnAcer:ct10:cvrV1.30:
  dmi.product.name: Aspire 5742G
  dmi.product.version: V1.30
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1398151/+subscriptions

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

[Desktop-packages] [Bug 1759889] Re: Simple scan multiple page issue - Unable to read frame from device - Canon mf244dw

[Bartosz Kosiorek]

Please provide full debug logs from simple-scanner

** Changed in: simple-scan (Ubuntu)
   Status: New => Incomplete

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

Title:
  Simple scan multiple page issue - Unable to read frame from device -
  Canon mf244dw

Status in simple-scan package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  When scanning multiple pages from a Canon mf244dw via the LAN I only
  get the first page scanned, then an error message.

  Running "simple-scan -d" and looking at the output I see the
  following:

  [+123.87s] DEBUG: scanner.vala:1321: sane_read (7651) -> 
(SANE_STATUS_CANCELLED, 0)
  [+123.87s] WARNING: scanner.vala:1337: Unable to read frame from device: 
Operation was cancelled
  [+123.87s] DEBUG: scanner.vala:768: sane_cancel ()
  [+123.87s] DEBUG: scanner.vala:771: sane_close ()

  I do notice that the scanner is already feeding in the second page
  before the first page has completely rendered on screen - perhaps it's
  going too fast?

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1759889/+subscriptions

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

[Desktop-packages] [Bug 1811593] Re: jpeg compression slider on save

[Bartosz Kosiorek]

** Changed in: simple-scan (Ubuntu)
   Status: New => Confirmed

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

Title:
  jpeg compression slider on save

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  Simple scan 3.28 on Ubuntu 18.04.

  When saving files as jpg, there is an option for compression there.
  And a level selector slider line.

  Get there by clicking save button on simple-scan after scanning.  Then
  select "jpeg (compressed)" as file format.  Then click save.

  Expected result: the higher the level of compression, the more image
  is compressed the lower the quality.

  Actual result:  Further forward to the right the selected point on the
  selector line, the higher the quality and lower the compression.

  Need better design for less confusion for users who recently upgraded
  to latest version (or those who use gimp).

  Option A: Can put the word "Compression" on one side, and "Quality" on
  further right side.  Or something better.

  B: Or at least just replace the word "Compression" with the word
  "Quality".

  C: Or put "Smaller File Size" on the left and "Better Quality" on the
  right.

  D: Or at least "File Size" on the left and "Quality" on the right

  E: Or an even clearer more concise better solution that maintainers
  can come up with. (see B again, which is how gimp does it)

  
  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  apt-cache policy simple-scan
  simple-scan:
Installed: 3.28.0-0ubuntu1
Candidate: 3.28.0-0ubuntu1
Version table:
   *** 3.28.0-0ubuntu1 500

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1811593/+subscriptions

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

[Desktop-packages] [Bug 1823339] Re: Ubuntu 19.04: Simple scan found network scanner but could not connect to scanner

[Bartosz Kosiorek]

Please attach debug logs from simple scanner.

** Changed in: simple-scan (Ubuntu)
   Status: New => Incomplete

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

Title:
  Ubuntu 19.04: Simple scan found network scanner but could not connect
  to scanner

Status in simple-scan package in Ubuntu:
  Incomplete

Bug description:
  Upon trying to scan to network scanner, simple scan found the scanner
  but could not connect to scan. Tried multiple times with a reboot in
  b/t

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1823339/+subscriptions

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

[Desktop-packages] [Bug 1701047] Re: Renaming of conf file fails

[Bug Watch Updater]

** Changed in: fonts-deva-extra (Debian)
   Status: New => Fix Released

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

Title:
  Renaming of conf file fails

Status in fonts-beng-extra package in Ubuntu:
  Fix Released
Status in fonts-deva-extra package in Ubuntu:
  Fix Released
Status in fonts-gujr-extra package in Ubuntu:
  Fix Released
Status in fonts-guru-extra package in Ubuntu:
  Fix Released
Status in fonts-orya-extra package in Ubuntu:
  Fix Released
Status in fonts-beng-extra source package in Bionic:
  Fix Released
Status in fonts-deva-extra source package in Bionic:
  Fix Released
Status in fonts-gujr-extra source package in Bionic:
  Fix Released
Status in fonts-guru-extra source package in Bionic:
  Fix Released
Status in fonts-orya-extra source package in Bionic:
  Fix Released
Status in fonts-beng-extra package in Debian:
  Fix Released
Status in fonts-deva-extra package in Debian:
  Fix Released
Status in fonts-gujr-extra package in Debian:
  New
Status in fonts-guru-extra package in Debian:
  Fix Released
Status in fonts-orya-extra package in Debian:
  Fix Released

Bug description:
  [Impact]
  The fix of  wasn't accomplished properly. 
Renamings of conf files weren't addressed in maintainer scripts, upgrades from 
previous versions fail in this respect, and the package system generates 
warning messages.

  The problem has been reported in Debian, and the purpose of this bug
  report is to keep track of the progress.

  [Justification]
  This config file is broken in xenial and will still be broken on upgrade to 
bionic, which means the fonts in question will not be available to the system 
as intended if the user has upgraded.

  [Test case]
  For each of
  - fonts-beng-extra
  - fonts-deva-extra
  - fonts-gujr-extra
  - fonts-guru-extra
  - fonts-orya-extra
  - fonts-telu-extra:

  * Purge the package if installed and clean up possible leftovers
    due to the issue.

  * Install the Xenial version of the package and find that the symlink
    in /etc/fonts/conf.d incorrectly points to a directory.

  * Install the version in bionic-release and find that the attempt
    to fix the issue fails

  * Install the version in bionic-proposed and find that it fixes the
    issue and that the symlink now correctly points to the conf file.

  [Regression potential]
  Because this modifies maintainer scripts there is possibility of introducing 
a regression that will cause the package to fail to unpack.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-beng-extra/+bug/1701047/+subscriptions

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

[Desktop-packages] [Bug 1865263] Re: [Focal] xkb-data 2.29-1 breaks AZERTY keyboard

[Bug Watch Updater]

** Changed in: xkeyboard-config
   Status: Unknown => Fix Released

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

Title:
  [Focal] xkb-data 2.29-1 breaks AZERTY keyboard

Status in xkeyboard-config:
  Fix Released
Status in x11-xkb-utils package in Ubuntu:
  Fix Released

Bug description:
  Running :
  Ubuntu GNOME session 20.04 up to date
  GNOME Shell + Mutter 3.35.91
  Wayland session
  French language configuration (fr in kb config files)
  AZERTY keyboard

  Upgrading from 2.26-2ubuntu4 to 2.29-1 caused my French AZERTY keyboard to be 
QWERTY.
  If I run :
  setxkbmap fr
  in a terminal, then everything becomes ok again.
  The issue is not present in GNOME Terminal but is present in Synaptic or 
Firefox e.g., I guess it could be X/Wayland apps difference ?

  Anyway, downgrading to xkb-data 2.26-2ubuntu4 did solve the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1865263/+subscriptions

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

[Desktop-packages] [Bug 1872124] Re: Please integrate ubuntu-drivers --gpgpu into Ubuntu Server

[Lee Trager]

MAAS contains a way to automatically install drivers. Every region has a
file, /etc/maas/drivers.yaml, which specifies drivers which should be
automatically installed. I don't have access to any test hardware but I
*think* this should work. One thing I noticed is there isn't a meta
package for the nVidia driver which points to the latest version for
each Ubuntu release. We would need that before adding this to MAAS.

diff --git a/drivers-orig.yaml b/drivers.yaml
index 2d3724c..97a4eb2 100644
--- a/drivers-orig.yaml
+++ b/drivers.yaml
@@ -82,3 +82,10 @@ drivers:
   repository: http://downloads.linux.hpe.com/SDR/repo/ubuntu-hpdsa
   series:
 - trusty
+- blacklist: nouveau
+  comment: nVidia driver
+  modaliases:
+  - 'pci:v10DEd*sv*sd*bc03sc02i00*'
+  - 'pci:v10DEd*sv*sd*bc03sc00i00*'
+  - module: nvidia
+  - package: nvidia-headless-440

** Changed in: maas
   Status: New => Triaged

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

Title:
  Please integrate ubuntu-drivers --gpgpu into Ubuntu Server

Status in cloud-init:
  New
Status in MAAS:
  Triaged
Status in subiquity:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Could subiquity provide an option in the UI to install and execute
  ubuntu-drivers-common on the target? The use case I'm interested in is
  an "on-rails" installation of Nvidia drivers for servers being
  installed for deep learning workloads.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1872124/+subscriptions

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

[Desktop-packages] [Bug 1870925] Re: UI freeze exception to remove problematic legacy action icons

[Launchpad Bug Tracker]

This bug was fixed in the package yaru-theme - 20.04.5

---
yaru-theme (20.04.5) focal; urgency=medium

  [ Carlo Lobrano ]
  * apps/nautilus: fix dim-label in selection and backdrop (LP: #1869141)
  * tweaks: use outline for tabs accessibility
  * gnome-shell/calendar: darken event dot (LP: #1870938)
  * gnome-shell/calendar: do not change color of day with events
  * shell/switcher-popup: improve contrast of highlighted app

  [ ubuntujaggers ]
  * Updating symbols for Tweaks and Configurator
  * Remove new legacy icons and include some from Humanity (LP: #1870925)
  * Adding symbols for system-reboot and system-log-out (LP: #1868385)
  * Adding missing symlinks for extensions app (Fixes: #2096)
  * suggested (more yaru-style) icon for extensions
  * adding dialog-warning and symlinks (Fixes: #2103)

 -- Carlo Lobrano   Tue, 14 Apr 2020 17:45:05 +0200

** Changed in: yaru-theme (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  UI freeze exception to remove problematic legacy action icons

Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  The Yaru team added some icons to the theme for use in legacy GTK2
  apps (e.g., document-new, document-export and so on).

  These looked good in apps like Inkscape.  However, during regression
  testing, it was found that the icons caused unpredictable behaviour in
  other GTK2 apps.  https://github.com/ubuntu/yaru/issues/2108 includes
  screenshots.

  The only way to fix is this to provide a 100% complete legacy icon set
  including all sizes, which isn't achievable for 20.04.

  So, our PR https://github.com/ubuntu/yaru/pull/2127 has removed the
  legacy icons from Yaru for now.  It would be great to have a feature
  freeze exception for this.  Any existing screenshots shouldn't be
  affected unless they show third party GTK2 apps on the desktop, and it
  would be a minor cosmetic difference if there's a difference at all.

  If we don't have the freeze exception, some legacy apps will look
  poor, as you can see from the issue
  https://github.com/ubuntu/yaru/issues/2108.  Apologies for not
  realising this before the freeze!  The benefit is a more consistent
  and professional visual experience for users who install and use GTK2
  apps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1870925/+subscriptions

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

[Desktop-packages] [Bug 1840185] Re: simple-scan app closes with a big delay

[Bartosz Kosiorek]

** Changed in: simple-scan (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  simple-scan app closes with a big delay

Status in simple-scan package in Ubuntu:
  Fix Released

Bug description:
  When I touch closing button I will wait for a while for exiting from this 
program. There are details in my video.
  Information from console:
  ubuntenok@ubuntenok-HP-250-G6-Notebook-PC:~$ simple-scan
  (simple-scan:13544): Gtk-WARNING **: 22:15:55.501: Failed to register client: 
GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register 
client

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: simple-scan 3.33.90-0ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 14 22:45:14 2019
  InstallationDate: Installed on 2019-08-14 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05c8:0233 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Webcam
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 248a:8514 Maxxter Wireless Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP 250 G6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-10-generic 
root=UUID=b1b8960c-e09c-4671-bcc2-1b3bd70c7ed4 ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.52
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 832E
  dmi.board.vendor: HP
  dmi.board.version: 26.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.52:bd03/04/2019:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn832E:rvr26.35:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN HP 200
  dmi.product.name: HP 250 G6 Notebook PC
  dmi.product.sku: 3DN65ES#ACB
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1840185/+subscriptions

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

[Desktop-packages] [Bug 1869524] Re: Simple Scan doesn't load

[Bartosz Kosiorek]

** Changed in: simple-scan (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Simple Scan doesn't load

Status in simple-scan package in Ubuntu:
  Invalid

Bug description:
  Simple Scan version 3.28.0-0ubuntu1 fails to load in Ubuntu 18.04 LTS

  simple-scan: error while loading shared libraries: libcolord.so.1:
  cannot open shared object file: No such file or directory

  Related to bug# 1869522
  https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1869522

  Not sure if I should be reporting the bug against Simple Scan, Gnome,
  or Ubuntu 18.04 LTS.

  Gnome project said it's not a bug with Simple Scan.  Something about not 
having the latest version of Gnome bundled with Ubuntu 18.04 LTS.
  https://gitlab.gnome.org/GNOME/simple-scan/-/issues/159

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: simple-scan 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 28 15:53:47 2020
  InstallationDate: Installed on 2014-08-08 (2059 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: MSI MS-7922
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic 
root=UUID=12cc7d65-8589-4aab-a77b-566ea7af9984 ro pci=assign-busses quiet 
splash vt.handoff=1
  SimpleScanLog:
   
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to bionic on 2020-01-05 (83 days ago)
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 U3 PLUS (MS-7922)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.10:bd02/16/2016:svnMSI:pnMS-7922:pvr1.0:rvnMSI:rnZ97U3PLUS(MS-7922):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7922
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1869524/+subscriptions

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

[Desktop-packages] [Bug 1870938] Re: calendar in gnome notification area: no dots for days having appointments

[Launchpad Bug Tracker]

This bug was fixed in the package yaru-theme - 20.04.5

---
yaru-theme (20.04.5) focal; urgency=medium

  [ Carlo Lobrano ]
  * apps/nautilus: fix dim-label in selection and backdrop (LP: #1869141)
  * tweaks: use outline for tabs accessibility
  * gnome-shell/calendar: darken event dot (LP: #1870938)
  * gnome-shell/calendar: do not change color of day with events
  * shell/switcher-popup: improve contrast of highlighted app

  [ ubuntujaggers ]
  * Updating symbols for Tweaks and Configurator
  * Remove new legacy icons and include some from Humanity (LP: #1870925)
  * Adding symbols for system-reboot and system-log-out (LP: #1868385)
  * Adding missing symlinks for extensions app (Fixes: #2096)
  * suggested (more yaru-style) icon for extensions
  * adding dialog-warning and symlinks (Fixes: #2103)

 -- Carlo Lobrano   Tue, 14 Apr 2020 17:45:05 +0200

** Changed in: yaru-theme (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  calendar in gnome notification area: no dots for days having
  appointments

Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  Dear All,
  in a fresh install of Ubuntu 20.04 beta:
  luca@blpcfl1:~$ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  luca@blpcfl1:~$ apt-cache policy yaru-theme-gnome-shell
  yaru-theme-gnome-shell:
Installato: 20.04.4
Candidato:  20.04.4

  
  What Expected:

  in the calendar in the gnome notification area, dots of days having an
  appointments are visible, or however, the days having an appointment
  are highlighted in some way.

  What happen:

  in the default Yaru shell theme, in the calendar in the gnome
  notification area, dots of days having an appointments are not
  visible.

  Note:
  in the Yaru-dark shell theme the dots are visible.

  Best regards,
  Luca

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: yaru-theme-gnome-shell 20.04.4
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  5 17:33:34 2020
  Dependencies:
   
  InstallationDate: Installed on 2020-04-05 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: yaru-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1870938/+subscriptions

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

[Desktop-packages] [Bug 1868385] Re: 'system-log-out-symbolic' and 'system-reboot-symbolic' do not exist in Yaru

[Launchpad Bug Tracker]

This bug was fixed in the package yaru-theme - 20.04.5

---
yaru-theme (20.04.5) focal; urgency=medium

  [ Carlo Lobrano ]
  * apps/nautilus: fix dim-label in selection and backdrop (LP: #1869141)
  * tweaks: use outline for tabs accessibility
  * gnome-shell/calendar: darken event dot (LP: #1870938)
  * gnome-shell/calendar: do not change color of day with events
  * shell/switcher-popup: improve contrast of highlighted app

  [ ubuntujaggers ]
  * Updating symbols for Tweaks and Configurator
  * Remove new legacy icons and include some from Humanity (LP: #1870925)
  * Adding symbols for system-reboot and system-log-out (LP: #1868385)
  * Adding missing symlinks for extensions app (Fixes: #2096)
  * suggested (more yaru-style) icon for extensions
  * adding dialog-warning and symlinks (Fixes: #2103)

 -- Carlo Lobrano   Tue, 14 Apr 2020 17:45:05 +0200

** Changed in: yaru-theme (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  'system-log-out-symbolic' and 'system-reboot-symbolic' do not exist in
  Yaru

Status in Yaru Theme:
  Unknown
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  'system-log-out-symbolic' and 'system-reboot-symbolic' do not exist in
  Yaru. These icons are supposed to be used in gnome-shell when you
  search for "logout" and "reboot".

  As a result, gnome-shell shows the icon 'application-exit-symbolic',
  which is basically an X, instead when you search for "logout".

  *Adwaita icons*

  system-log-out-symbolic
  
https://gitlab.gnome.org/GNOME/adwaita-icon-theme/-/blob/master/Adwaita/scalable/actions/system-log-out-symbolic.svg

  system-reboot-symbolic
  
https://gitlab.gnome.org/GNOME/adwaita-icon-theme/-/blob/master/Adwaita/scalable/actions/system-reboot-symbolic.svg

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: yaru-theme-icon 20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 21 15:16:22 2020
  Dependencies:

  InstallationDate: Installed on 2020-01-21 (59 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: yaru-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/1868385/+subscriptions

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

[Desktop-packages] [Bug 1873084] [NEW] Seahorse has 100% cpu

[Lyubomir Parvanov]

Public bug reported:

Seahorse has 100 % CPU. Submitting Ubuntu-bug. How can i take a
performance profile if it happens again?

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: seahorse 3.32.2-1
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 16 00:16:42 2020
InstallationDate: Installed on 2020-02-08 (67 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: seahorse
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "2020-04-16_00-18.png"
   
https://bugs.launchpad.net/bugs/1873084/+attachment/5354927/+files/2020-04-16_00-18.png

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

Title:
  Seahorse has 100% cpu

Status in seahorse package in Ubuntu:
  New

Bug description:
  Seahorse has 100 % CPU. Submitting Ubuntu-bug. How can i take a
  performance profile if it happens again?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: seahorse 3.32.2-1
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 16 00:16:42 2020
  InstallationDate: Installed on 2020-02-08 (67 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: seahorse
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1873084/+subscriptions

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

[Desktop-packages] [Bug 1869141] Re: [UIFe] Icon View Captions labels in Nautilus are hard to read when selected

[Launchpad Bug Tracker]

This bug was fixed in the package yaru-theme - 20.04.5

---
yaru-theme (20.04.5) focal; urgency=medium

  [ Carlo Lobrano ]
  * apps/nautilus: fix dim-label in selection and backdrop (LP: #1869141)
  * tweaks: use outline for tabs accessibility
  * gnome-shell/calendar: darken event dot (LP: #1870938)
  * gnome-shell/calendar: do not change color of day with events
  * shell/switcher-popup: improve contrast of highlighted app

  [ ubuntujaggers ]
  * Updating symbols for Tweaks and Configurator
  * Remove new legacy icons and include some from Humanity (LP: #1870925)
  * Adding symbols for system-reboot and system-log-out (LP: #1868385)
  * Adding missing symlinks for extensions app (Fixes: #2096)
  * suggested (more yaru-style) icon for extensions
  * adding dialog-warning and symlinks (Fixes: #2103)

 -- Carlo Lobrano   Tue, 14 Apr 2020 17:45:05 +0200

** Changed in: yaru-theme (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [UIFe] Icon View Captions labels in Nautilus are hard to read when
  selected

Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  First reported here: https://github.com/ubuntu/yaru/issues/2110

  The "Icon View Captions" label in Nautilus is hard to read when the
  file is selected.

  Steps to Reproduce the Problem
  - open Preferences > View Tab
  - in the "Icon View Captions" section select at least one "information to be 
displayed beneath file and folders name"
  - Go back to Nautilus main window and select Icon View. Below the file name 
is expected to be a new label with color gray
  - Select the icon. The caption label keeps the gray color, which is hard to 
read on an orange background

  Yaru version

  - Version 20.04.4 in current Focal daily

  
  The fix has a low impact, since it only applies to Yaru's stylesheet part 
dedicated to Nautilus, and specifically to this caption labels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1869141/+subscriptions

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

[Desktop-packages] [Bug 1873086] [NEW] sound stutters when playing on a bluetooth receiver

[Tomislav]

Public bug reported:

I can play via bluetooth from my laptop or my mobile phone. I have a set
of bluetooth headphones and bluetooth speakers.

Any combination of output with the smartphone as the player works, which
is as it should be.

Any combination of output with the laptop as the player is miserable:
sound stutters, sometimes randomly, sometimes seemingly when I touch the
laptop or come close to it...had similar or identical problems with a
previous Ubuntu laptop. Bluetooth audio seems to be in very bad shape.

$ lsb_release -rd
Description:Ubuntu 18.04.4 LTS
Release:18.04

laptop Dell XPS 9370

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.4
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tna2174 F pulseaudio
 /dev/snd/pcmC0D0p:   tna2174 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 15 22:55:05 2020
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
InstallationDate: Installed on 2018-05-10 (706 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to bionic on 2020-03-04 (42 days ago)
dmi.bios.date: 12/11/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.1
dmi.board.name: 0W970W
dmi.board.vendor: Dell Inc.
dmi.board.version: A05
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA05:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9370
dmi.product.sku: 07E6
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  sound stutters when playing on a bluetooth receiver

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I can play via bluetooth from my laptop or my mobile phone. I have a
  set of bluetooth headphones and bluetooth speakers.

  Any combination of output with the smartphone as the player works,
  which is as it should be.

  Any combination of output with the laptop as the player is miserable:
  sound stutters, sometimes randomly, sometimes seemingly when I touch
  the laptop or come close to it...had similar or identical problems
  with a previous Ubuntu laptop. Bluetooth audio seems to be in very bad
  shape.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  laptop Dell XPS 9370

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.4
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tna2174 F pulseaudio
   /dev/snd/pcmC0D0p:   tna2174 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 22:55:05 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-05-10 (706 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to bionic on 2020-03-04 (42 days ago)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0W970W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA05:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+subscriptions

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

[Desktop-packages] [Bug 1872124] Re: ubuntu-drivers-common integration

[Dimitri John Ledkov]

I don't think that implementing just subiquity is enough. Ubiquity was
the last piece of ubuntu-drivers integration on the Desktop, as update-
manager continiously was already checking for any new drivers that are
available for the systems' hardware, and continiously providing
notifications to install / switch between new alternatives / dismiss
installing drivers, on continuous basis post-install / post-upgrade.
Doing this during install, simply moved that step from post-install to
pre-install.

Ubuntu Server currently does not have ubuntu-drivers integration with
motd, unattanded upgrades, and apt output to notify users of the newly
available driver implementations, and how to opt into them.

Command line tooling exists, but currently only used non-interactively
by cloud-init on some compatible public clouds.

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-drivers-common (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: maas
   Importance: Undecided
   Status: New

** Summary changed:

- ubuntu-drivers-common integration
+ Please integrate ubuntu-drivers --gpgpu into Ubuntu Server

** Also affects: cloud-init
   Importance: Undecided
   Status: New

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

Title:
  Please integrate ubuntu-drivers --gpgpu into Ubuntu Server

Status in cloud-init:
  New
Status in MAAS:
  New
Status in subiquity:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Could subiquity provide an option in the UI to install and execute
  ubuntu-drivers-common on the target? The use case I'm interested in is
  an "on-rails" installation of Nvidia drivers for servers being
  installed for deep learning workloads.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1872124/+subscriptions

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

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

[Egmont Koblinger]

See also bug #1859123.

-- 
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:
  Won't Fix

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)
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1872377/+subscriptions

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

[Desktop-packages] [Bug 1859123] Re: No global menus (panel-appmenu / dbus) in Firefox 72.0.1

[Egmont Koblinger]

I was severely annoyed by the new behavior of the Alt key (FF 75, Ubuntu
20.04, Unity 7).

If I move the window using Alt + mouse drag (which I frequently do), the
menu opens up. Subsequent letters I type aren't sent to the webpage, but
navigate the menu. Another lone Alt keypress doesn't close it either
(well, pressing it closes, but then releasing the key opens the menu bar
again), so I have to reach out to Esc to close it. This behavior was
unacceptable for me.

I first found the workaround of enabling View -> Toolbars -> Menu bar.
This way the menu bar is always visible, and the super annoying behavior
of Alt is gone. Alas, there's a price to pay in terms of wasted screen
real estate.

After a bit more searching I found an even better workaround. Instead of
the previous one, go to about:config and set ui.key.menuAccessKey to -1.
Then the browser needs to be restarted. A lone Alt key (or Alt + moving
the window) no longer opens up the menu bar. However, Alt+F, Alt+E etc.,
as well as F10 still open it up, so all the functionality, in their
familiar layout is still conveniently available.

It's not as good as Unity integration used to be, but almost as good; to
me it's an acceptable minor inconvenience.

I hope I could help some people with this comment.

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

Title:
  No global menus (panel-appmenu / dbus) in Firefox 72.0.1

Status in firefox package in Ubuntu:
  Won't Fix

Bug description:
  No global menus are displayed in latest Firefox 72.0.1 (possibly in a
  slightly earlier version).

  This issue was observed on three different systems all running Ubuntu
  MATE 20.04 Focal (development), and I first noticed it on each system
  upon updating to 72.0.1 today.

  The symptoms are identical to https://bugs.launchpad.net/ubuntu-
  mate/+bug/1743687 , but running `env UBUNTU_MENUPROXY=0 firefox` does
  not resolve the issue. `env UBUNTU_MENUPROXY=1 firefox` does not
  resolve the issue either.

  My first guess is that the issue is a change in Firefox, due to how
  the previous solution with the environment variable no longer works.
  (Perhaps a change to the Unity menu patch?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1859123/+subscriptions

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