[Desktop-packages] [Bug 1882354] Re: [Intel T4200] all application open in black

[Launchpad Bug Tracker]

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

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

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

Title:
  [Intel T4200] all application open in black

Status in mutter package in Ubuntu:
  Expired

Bug description:
  all application open in black

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 18:13:44 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated 
Graphics Controller [144d:c540]
 Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated 
Graphics Controller [144d:c540]
  InstallationDate: Installed on 2020-06-05 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R468/R418
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=c84a78a6-96a8-49ab-9350-c471429971dd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/28/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 04NG.MP01.20090728.HCW
  dmi.board.name: R468/R418
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr04NG.MP01.20090728.HCW:bd07/28/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnR468/R418:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR468/R418:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: R468/R418
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1882267] Re: nautilus Find function stuck in 'full text' search mode

[Launchpad Bug Tracker]

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

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

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

Title:
  nautilus Find function stuck in 'full text' search mode

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  After searching in "Full Text" mode in Nautilus, then changing to
  "Filename" search mode, Nautilus continues to return results based on
  "Full Text" mode. Example: I opened Files program, clicked on Find,
  then clicked the drop-down and selected "File Name". I then searched
  for the word "atlantic." The results returned not only file names with
  "atlantic" in them, but file names that did not contain "atlantic" in
  the file title, but where the word "atlantic" could be found in the
  body of the file's text.

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

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

[Desktop-packages] [Bug 1882340] Re: Alert sounds are captured by the microphone

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Alert sounds are captured by the microphone

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  On my Fossa the system sounds (e.g., the alert sound) are also
  captured by my microphone. Thus, if I press backspace in an empty
  terminal, my contacts in a video-call can hear the default bell sound
  making *pling*.

  When opening the System > Audio on Gnome I can see a rise on the
  volume bar as well.

  A workaround exists by disabling the alert sounds as described in the
  docs: https://help.ubuntu.com/stable/ubuntu-help/sound-alert.html.en

  This has been the default since installation for me and drives my
  contacts crazy. :-)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jl 3027 F pulseaudio
   /dev/snd/controlC0:  jl 3027 F pulseaudio
   /dev/snd/pcmC0D0p:   jl 3027 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 10:53:55 2020
  InstallationDate: Installed on 2020-04-24 (42 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: ThinkPad Thunderbolt 3 Dock USB Audio - ThinkPad Thunderbolt 3 
Dock USB
  Symptom_PulseAudioLog:
   Jun 05 20:03:08 x1c dbus-daemon[1617]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.37' (uid=125 pid=2067 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
   Jun 05 20:03:24 x1c systemd[2021]: pulseaudio.service: Succeeded.
   Jun 05 20:03:34 x1c systemd[2021]: pulseaudio.socket: Succeeded.
  Symptom_Type: Volume slider, or mixer problems
  Title: [sof-hda-dsp - sof-hda-dsp, recording] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET47W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QES01L00
  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:bvrN2HET47W(1.30):bd03/18/2020:svnLENOVO:pn20QES01L00:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QES01L00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QES01L00
  dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1882446] Re: package thunderbird 1:68.7.0+build1-0ubuntu2 failed to install/upgrade: unable to make backup link of './usr/lib/thunderbird/libxul.so' before installing new versi

[Launchpad Bug Tracker]

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

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

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

Title:
  package thunderbird 1:68.7.0+build1-0ubuntu2 failed to
  install/upgrade: unable to make backup link of
  './usr/lib/thunderbird/libxul.so' before installing new version:
  Input/output error

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  installing update crashed

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: thunderbird 1:68.7.0+build1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4753 F pulseaudio
  BuildID: 20200407160932
  CasperMD5CheckMismatches: ./casper/filesystem.squashfs
  CasperMD5CheckResult: fail
  CasperVersion: 1.445
  Channel: Unavailable
  Date: Sun Jun  7 18:00:23 2020
  DuplicateSignature:
   package:thunderbird:1:68.7.0+build1-0ubuntu2
   Unpacking thunderbird (1:68.8.0+build2-0ubuntu0.20.04.2) over 
(1:68.7.0+build1-0ubuntu2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-PDmKzG/169-thunderbird_1%3a68.8.0+build2-0ubuntu0.20.04.2_amd64.deb
 (--unpack):
unable to make backup link of './usr/lib/thunderbird/libxul.so' before 
installing new version: Input/output error
  ErrorMessage: unable to make backup link of './usr/lib/thunderbird/libxul.so' 
before installing new version: Input/output error
  ForcedLayersAccel: False
  IpRoute:
   default via 192.168.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.104 metric 600
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Title: package thunderbird 1:68.7.0+build1-0ubuntu2 failed to 
install/upgrade: unable to make backup link of 
'./usr/lib/thunderbird/libxul.so' before installing new version: Input/output 
error
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX504GD.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX504GD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX504GD.312:bd07/13/2018:svnASUSTeKCOMPUTERINC.:pnTUFGAMINGFX504GD_FX80GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX504GD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF GAMING
  dmi.product.name: TUF GAMING FX504GD_FX80GD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1882490] Re: gsd-media-keys unable to get default source or sink

[Launchpad Bug Tracker]

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

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

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

Title:
  gsd-media-keys unable to get default source or sink

Status in gnome-settings-daemon package in Ubuntu:
  Expired

Bug description:
  jlquinn@cerberus:~$ lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  jlquinn@cerberus:~$ apt-cache policy gnome-settings-daemon
  gnome-settings-daemon:
Installed: 3.28.1-0ubuntu1.3
Candidate: 3.28.1-0ubuntu1.3
Version table:
   *** 3.28.1-0ubuntu1.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  In my log, I see the following messages:

  Jun 08 00:27:19 cerberus gsd-media-keys[3584]: Unable to get default sink
  Jun 08 00:27:19 cerberus gsd-media-keys[3584]: Unable to get default source

  This seems like something is amiss.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1.3
  ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-53-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  8 01:03:33 2020
  InstallationDate: Installed on 2020-05-29 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1890866] [NEW] Ubuntu 20.04 don't recognize my USB 3.0 Monitor (Works well in Win10)

[HackerMan]

Public bug reported:

I have a USB 3.0 Portable Monitor that works well under Win10, but when
I reboot the same laptop under Ubuntu 20.04, it's not recognized...

Downloaded the Asus MB169B+ Driver:
https://www.asus.com/ca-en/Monitors/MB169BPlus/HelpDesk_Download/
Version 5.3.1 2020/06/15
https://dlcdnets.asus.com/pub/ASUS/LCD%20Monitors/MB16AP/ASUS_MB_Series_driver_for_Ubuntu_5.3.1.zip

Extracted the zip file:
ASUS_MB_Series_driver_for_Ubuntu_5.3.1.zip

Ran the command to make it executable:
chmod 755 displaylink-driver-5.3.1.34.run

Executed the file:
sudo ./displaylink-driver-5.3.1.34.run

Install completed, rebooted the machine

Monitor still in idle mode (orange button - if it was recognized, it
would be white)

FYI - I don't have a graphic card, just the one embedded in the Intel i5
6th gen

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug  7 23:57:14 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: evdi, 1.7.0, 5.4.0-42-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:81cb]
InstallationDate: Installed on 2020-04-28 (101 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: HP HP ENVY Notebook
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=981629fe-8e85-4ada-bacb-8fa11c48b000 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/26/2019
dmi.bios.vendor: Insyde
dmi.bios.version: F.36
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81CB
dmi.board.vendor: HP
dmi.board.version: KBC Version 60.27
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd11/26/2019:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81CB:rvrKBCVersion60.27:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
dmi.product.name: HP ENVY Notebook
dmi.product.sku: W7E04UA#ABL
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

** Attachment added: "Monitor driver for Ubuntu 20.04"
   
https://bugs.launchpad.net/bugs/1890866/+attachment/5399732/+files/ASUS_MB_Series_driver_for_Ubuntu_5.3.1.zip

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

Title:
  Ubuntu 20.04 don't recognize my USB 3.0 Monitor (Works well in Win10)

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a USB 3.0 Portable Monitor that works well under Win10, but
  when I reboot the same laptop under Ubuntu 20.04, it's not
  recognized...

  Downloaded the Asus MB169B+ Driver:
  https://www.asus.com/ca-en/Monitors/MB169BPlus/HelpDesk_Download/
  Version 5.3.1 2020/06/15
  
https://dlcdnets.asus.com/pub/ASUS/LCD%20Monitors/MB16AP/ASUS_MB_Series_driver_for_Ubuntu_5.3.1.zip

  Extracted the zip file:
  ASUS_MB_Series_driver_for_Ubuntu_5.3.1.zip

  Ran the command to make it executable:
  chmod 755 displaylink-driver-5.3.1.34.run

  Executed the file:
  sudo ./displaylink-driver-5.3.1.34.run

  Install completed, rebooted the machine

  Monitor still in idle mode (orange button - if it was recognized, it
  would be white)

  FYI - I don't have a graphic card, just the one embedded in the Intel
  i5 6th gen

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  7 23:57:14 2020
  DistUpgraded: Fresh install
  DistroCodename: 

[Desktop-packages] [Bug 1888942] Re: marked url in firefox by using one click isn't copied to clipboard, only with a triple mouse-click

[Bug Watch Updater]

** Changed in: firefox
   Status: New => Invalid

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

Title:
  marked url in firefox by using one click isn't copied to clipboard,
  only with a triple mouse-click

Status in Mozilla Firefox:
  Invalid
Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Hi, if I click in an url in firefox, the whole url ist marked, i.e.
  highlighted.

  If I now use a click on the mousewheel to paste the content of the clipboard 
into another software, I discover that the url wasn't copied into the clipboard 
- the previous content ist filled in.
  That's confusing to me.

  I would expect: If I can mark an url in Firefox with a single mouse-click, 
which looks like a marking with a triple click, then it should be copied also 
in the clipboard.
  That would be a consisting behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 78.0.2+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matthias   1453 F pulseaudio
   /dev/snd/controlC1:  matthias   1453 F pulseaudio
   /dev/snd/pcmC1D0c:   matthias   1453 F...m pulseaudio
   /dev/snd/pcmC1D0p:   matthias   1453 F...m pulseaudio
  BuildID: 20200708170202
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 25 16:44:27 2020
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:730
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ExecutablePath: /usr/lib/firefox/firefox
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-04-24 (92 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.11.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.11.0/24 dev wlp4s0 proto kernel scope link src 192.168.11.66 metric 
600
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:730
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 - LastVersion=74.0.1/20200403064753 (Out of date)
   Profile0 (Default) - LastVersion=78.0.2/20200708170202 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET53W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTS06G0J
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: R90GJVAH
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET53W(1.31):bd11/12/2019:svnLENOVO:pn20BTS06G0J:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS06G0J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 3rd
  dmi.product.name: 20BTS06G0J
  dmi.product.sku: LENOVO_MT_20BT_BU_Think_FM_ThinkPad X1 Carbon 3rd
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1873184] Re: Wired and wireless connection details have not enough height and items overlap

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-control-center -
1:3.37.3-1ubuntu1

---
gnome-control-center (1:3.37.3-1ubuntu1) groovy; urgency=medium

  * New upstream version based on Debian
  * d/p/git-nongnome-segfault.patch,
d/p/git-user-accounts-Use-newly-designed-fingerprint-enroll-dialo.patch,
d/p/0029-applications-Use-new-snapd-glib-API-for-labelling-Sn.patch:
- removed, included in the new version
  * debian/patches/gitlab_details_layout.patch:
   - correctly layout the ethernet details so they don't overlap,
 thanks Bin Li (lp: #1873184)

 -- Sebastien Bacher   Fri, 07 Aug 2020 23:07:10
+0200

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

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

Title:
  Wired and wireless connection details have not enough height and items
  overlap

Status in gnome-control-center:
  Unknown
Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  There is a display bug when you unplug the network cable on focal.
  Please see attachment

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

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

[Desktop-packages] [Bug 1888942]

[Stransky]

This is an address bar issue, the text is highlighted but not copied to
clipboard.

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

Title:
  marked url in firefox by using one click isn't copied to clipboard,
  only with a triple mouse-click

Status in Mozilla Firefox:
  Invalid
Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Hi, if I click in an url in firefox, the whole url ist marked, i.e.
  highlighted.

  If I now use a click on the mousewheel to paste the content of the clipboard 
into another software, I discover that the url wasn't copied into the clipboard 
- the previous content ist filled in.
  That's confusing to me.

  I would expect: If I can mark an url in Firefox with a single mouse-click, 
which looks like a marking with a triple click, then it should be copied also 
in the clipboard.
  That would be a consisting behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 78.0.2+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matthias   1453 F pulseaudio
   /dev/snd/controlC1:  matthias   1453 F pulseaudio
   /dev/snd/pcmC1D0c:   matthias   1453 F...m pulseaudio
   /dev/snd/pcmC1D0p:   matthias   1453 F...m pulseaudio
  BuildID: 20200708170202
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 25 16:44:27 2020
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:730
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ExecutablePath: /usr/lib/firefox/firefox
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-04-24 (92 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.11.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.11.0/24 dev wlp4s0 proto kernel scope link src 192.168.11.66 metric 
600
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:730
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 - LastVersion=74.0.1/20200403064753 (Out of date)
   Profile0 (Default) - LastVersion=78.0.2/20200708170202 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET53W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTS06G0J
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: R90GJVAH
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET53W(1.31):bd11/12/2019:svnLENOVO:pn20BTS06G0J:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS06G0J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 3rd
  dmi.product.name: 20BTS06G0J
  dmi.product.sku: LENOVO_MT_20BT_BU_Think_FM_ThinkPad X1 Carbon 3rd
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1888942]

[Adw-mozilla]

*** This bug has been marked as a duplicate of bug 1653191 ***

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

Title:
  marked url in firefox by using one click isn't copied to clipboard,
  only with a triple mouse-click

Status in Mozilla Firefox:
  Invalid
Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Hi, if I click in an url in firefox, the whole url ist marked, i.e.
  highlighted.

  If I now use a click on the mousewheel to paste the content of the clipboard 
into another software, I discover that the url wasn't copied into the clipboard 
- the previous content ist filled in.
  That's confusing to me.

  I would expect: If I can mark an url in Firefox with a single mouse-click, 
which looks like a marking with a triple click, then it should be copied also 
in the clipboard.
  That would be a consisting behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 78.0.2+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matthias   1453 F pulseaudio
   /dev/snd/controlC1:  matthias   1453 F pulseaudio
   /dev/snd/pcmC1D0c:   matthias   1453 F...m pulseaudio
   /dev/snd/pcmC1D0p:   matthias   1453 F...m pulseaudio
  BuildID: 20200708170202
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 25 16:44:27 2020
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:730
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ExecutablePath: /usr/lib/firefox/firefox
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-04-24 (92 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.11.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.11.0/24 dev wlp4s0 proto kernel scope link src 192.168.11.66 metric 
600
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:730
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 - LastVersion=74.0.1/20200403064753 (Out of date)
   Profile0 (Default) - LastVersion=78.0.2/20200708170202 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET53W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTS06G0J
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: R90GJVAH
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET53W(1.31):bd11/12/2019:svnLENOVO:pn20BTS06G0J:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS06G0J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 3rd
  dmi.product.name: 20BTS06G0J
  dmi.product.sku: LENOVO_MT_20BT_BU_Think_FM_ThinkPad X1 Carbon 3rd
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1888942]

[Marcela-calderon]

Hi, this sounds like an enhancement, I will set a component to have a starting 
point for this. 
Widget: Gtk team, if this is not the right component please feel free to route 
this ticket to the corresponding team, thanks!

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

Title:
  marked url in firefox by using one click isn't copied to clipboard,
  only with a triple mouse-click

Status in Mozilla Firefox:
  Invalid
Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Hi, if I click in an url in firefox, the whole url ist marked, i.e.
  highlighted.

  If I now use a click on the mousewheel to paste the content of the clipboard 
into another software, I discover that the url wasn't copied into the clipboard 
- the previous content ist filled in.
  That's confusing to me.

  I would expect: If I can mark an url in Firefox with a single mouse-click, 
which looks like a marking with a triple click, then it should be copied also 
in the clipboard.
  That would be a consisting behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 78.0.2+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matthias   1453 F pulseaudio
   /dev/snd/controlC1:  matthias   1453 F pulseaudio
   /dev/snd/pcmC1D0c:   matthias   1453 F...m pulseaudio
   /dev/snd/pcmC1D0p:   matthias   1453 F...m pulseaudio
  BuildID: 20200708170202
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 25 16:44:27 2020
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:730
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ExecutablePath: /usr/lib/firefox/firefox
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-04-24 (92 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.11.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.11.0/24 dev wlp4s0 proto kernel scope link src 192.168.11.66 metric 
600
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:730
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 - LastVersion=74.0.1/20200403064753 (Out of date)
   Profile0 (Default) - LastVersion=78.0.2/20200708170202 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET53W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTS06G0J
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: R90GJVAH
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET53W(1.31):bd11/12/2019:svnLENOVO:pn20BTS06G0J:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS06G0J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 3rd
  dmi.product.name: 20BTS06G0J
  dmi.product.sku: LENOVO_MT_20BT_BU_Think_FM_ThinkPad X1 Carbon 3rd
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1890865] [NEW] Nouveau X.org: Stale texture data and flicker in small SDL2 program

[Kevin Cahalan]

Public bug reported:

Video of bug: https://youtu.be/O0__VNN9G_o

At 0:11 in the video you see old web browser data showing up in my
program.

At 0:19 when I close a window in my program the texture for my piano key letters
flicker. By luck the texture for my keys sometimes flickers to stuff previously
displayed on my desktop. This flickering is linked to my mouse 
movement/placement.

When I run my program with the proprietary 440 NVIDIA driver things work fine.
I am on Ubuntu budgie 20.04 using XFCE on X.org X11.

The SDL2 program source:

https://github.com/kevinacahalan/piano_waterfall

git hash 553bb6c8ca18b23494a6c92f4551baa1649f0374

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: XFCE
Date: Fri Aug  7 23:35:05 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 v4l2loopback, 0.12.3, 5.4.0-40-generic, x86_64: installed
 v4l2loopback, 0.12.3, 5.4.0-42-generic, x86_64: installed
 virtualbox, 6.1.10, 5.4.0-40-generic, x86_64: installed
 virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050 Ti] [3842:6251]
InstallationDate: Installed on 2020-05-05 (95 days ago)
InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
MachineType: Dell Inc. OptiPlex 3010
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=5fe179e5-be36-426b-9297-8ef7a1af2c0c ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/31/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 042P49
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd01/31/2013:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA01:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 3010
dmi.product.version: 01
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.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Fri Aug  7 21:38:07 2020
xserver.configfile: default
xserver.errors: client bug: timer event11 debounce short: scheduled expiry is 
in the past (-2ms), your system is too slow
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.8-2ubuntu2.2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug focal ubuntu

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/bugs/1890865/+attachment/5399711/+files/kernel_log.txt

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

Title:
  Nouveau X.org: Stale texture data and flicker in small SDL2 program

Status in xorg package in Ubuntu:
  New

Bug description:
  Video of bug: https://youtu.be/O0__VNN9G_o

  At 0:11 in the video you see old web browser data showing up in my
  program.

  At 0:19 when I close a window in my program the texture for my piano key 
letters
  flicker. By luck the texture for my keys sometimes flickers to stuff 
previously
  displayed on my desktop. This flickering is linked to my mouse 
movement/placement.

  When I run my program with the proprietary 440 NVIDIA driver things work fine.
  I am on Ubuntu budgie 20.04 using XFCE on X.org X11.

  The SDL2 program source:

  https://github.com/kevinacahalan/piano_waterfall

  git hash 553bb6c8ca18b23494a6c92f4551baa1649f0374

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Fri Aug  7 23:35:05 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback, 0.12.3, 5.4.0-40-generic, x86_64: installed
   v4l2loopback, 0.12.3, 

[Desktop-packages] [Bug 1890863] [NEW] Display does not come on after suspend

[Nick]

Public bug reported:

After coming out of suspend the display is not receiving any data and
stays in power saving mode.  Only power cycling the system brings it
back.  Unsure whether this is related to amdgpu or something else.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug  8 12:51:28 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 XT 
/ 5700/5700 XT] [1458:2314]
InstallationDate: Installed on 2020-01-08 (212 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=d1ce6274-5a98-4eab-93b4-393469cec0d9 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2603
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd08/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal third-party-packages 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/1890863

Title:
  Display does not come on after suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  After coming out of suspend the display is not receiving any data and
  stays in power saving mode.  Only power cycling the system brings it
  back.  Unsure whether this is related to amdgpu or something else.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 12:51:28 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 
XT / 5700/5700 XT] [1458:2314]
  InstallationDate: Installed on 2020-01-08 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=d1ce6274-5a98-4eab-93b4-393469cec0d9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Desktop-packages] [Bug 1815036] Re: uri defined for connectivity check does not have IPv6 address

[Valtteri Vuorikoski]

1.5 years on this is still broken: connectivity-check.ubuntu.com has no
 record.

Workaround: remove network-manager-config-connectivity-ubuntu and
install network-manager-config-connectivity-debian instead.

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

Title:
  uri defined for connectivity check does not have IPv6 address

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  As per subject. This package defines the file
  /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf, which
  defines the uri for the connectivity check to be http://connectivity-
  check.ubuntu.com

  This hostname does not resolve to an IPv6 address. Therefore, even if
  the user has fully working IPv6, the connectivity check for IPv6 will
  fail. As a result, the IPv6 default routes will be heavily
  deprioritised (ie: having 2 added to the metric) rendering them
  effectively inoperable absent a deliberate effort to use IPv6-only
  addresses.

  NB: This was discovered by-the-by during reporting of bug #1814262
  upstream at
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/116#note_114448

  It seems to be irrelevant to the main thrust of that bug, which is
  that IPv4 wired routes are not being identified as working correctly.
  In fact, when I switch to network-manager-config-connectivity-debian,
  the hostname defined there *does* have a working IPv6 address, and the
  issue actually being reported in that other bug does not affect the
  IPv6 routes, only the IPv4 ones.

  The bug here probably doesn't need any change made to the package
  itself, but rather to the networking of the actual target URL. It
  needs an IPv6 () DNS record, and for it to function on that
  address.

  I note in passing the debian connectivity check URL resolves to
  several IP addresses - four IPv4 addresses and 3 IPv6 addresses,
  presumably geographically diverse. (It's actually a CNAME to
  static.debian.org) This looks like it would be a more reliable target
  for connectivity checks. The ubuntu URL only resolves to a single IPv4
  address.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager-config-connectivity-ubuntu 1.15.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  7 12:35:24 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-09-11 (148 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  IpRoute:
   default via 192.168.1.254 dev enp63s0 proto dhcp metric 100 
   default via 192.168.1.254 dev wlp2s0 proto dhcp metric 20600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev enp63s0 proto kernel scope link src 192.168.1.106 metric 
100 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PackageArchitecture: all
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to disco on 2019-01-13 (24 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.15.2   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815036/+subscriptions

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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Marc Lijour]

Tested the snap package and it works fine!
Running on DELL XPS13
Version 84.0.4147.89 (Official Build) snap (64-bit)
+ using the h264ify extension in the browser to force Youtube (VP9 by default) 
to run on h264


$ sudo snap install --channel=candidate/vaapi chromium

$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS"

$ vainfo
libva info: VA-API version 1.7.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_7
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.7 (libva 2.6.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 20.1.1 ()
vainfo: Supported profile and entrypoints
  VAProfileMPEG2Simple: VAEntrypointVLD
  VAProfileMPEG2Main  : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointEncSliceLP
  VAProfileH264High   : VAEntrypointVLD
  VAProfileH264High   : VAEntrypointEncSliceLP
  VAProfileJPEGBaseline   : VAEntrypointVLD
  VAProfileJPEGBaseline   : VAEntrypointEncPicture
  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
  VAProfileVP8Version0_3  : VAEntrypointVLD
  VAProfileHEVCMain   : VAEntrypointVLD
  VAProfileHEVCMain10 : VAEntrypointVLD
  VAProfileVP9Profile0: VAEntrypointVLD
  VAProfileVP9Profile2: VAEntrypointVLD


chrome://media-internals/

Timestamp   PropertyValue
00:00:00.000origin_url  "https://www.youtube.com/;
00:00:00.000kFrameUrl   "https://www.youtube.com/watch?v=LXb3EKWsInQ;
00:00:00.000kFrameTitle "COSTA RICA IN 4K 60fps HDR (ULTRA HD) - 
YouTube"
00:00:00.000url 
"blob:https://www.youtube.com/bd1489d5-5381-4f8a-b3c0-90023da92ae9;
00:00:00.000info"ChunkDemuxer"
00:00:00.000pipeline_state  "kStarting"
00:00:00.036kVideoTracks[{"alpha 
mode":"is_opaque","codec":"h264","coded size":"1920x1080","color 
space":"{primaries:BT709, transfer:BT709, matrix:BT709, 
range:LIMITED}","encryption scheme":"Unencrypted","has extra data":false,"hdr 
metadata":"unset","natural size":"1920x1080","orientation":"0°","profile":"h264 
high","visible rect":"0,0 1920x1080"}]
00:00:00.036kAudioTracks[{"bytes per channel":2,"bytes per 
frame":4,"channel layout":"STEREO","channels":2,"codec":"aac","codec 
delay":0,"discard decoder delay":false,"encryption scheme":"Unencrypted","has 
extra data":false,"profile":"unknown","sample format":"Signed 16-bit","samples 
per second":44100,"seek preroll":"0us"}]
00:00:00.039info"Effective playback rate changed from 0 to 1"
00:00:00.039event   "kPlay"
00:00:00.045kIsAudioDecryptingDemuxerStream false
00:00:00.045kAudioDecoderName   "FFmpegAudioDecoder"
00:00:00.045kIsPlatformAudioDecoder false
00:00:00.045info"Selected FFmpegAudioDecoder for audio decoding, 
config: codec: aac, profile: unknown, bytes_per_channel: 2, channel_layout: 
STEREO, channels: 2, samples_per_second: 44100, sample_format: Signed 16-bit, 
bytes_per_frame: 4, seek_preroll: 0us, codec_delay: 0, has extra data: false, 
encryption scheme: Unencrypted, discard decoder delay: false"
00:00:00.046error   
"{\"causes\":[{\"causes\":[],\"data\":{},\"stack\":[{\"file\":\"../../media/filters/decrypting_video_decoder.cc\",\"line\":53}],\"status_code\":264,\"status_message\":\"\"}],\"data\":{\"Decoder
 
name\":\"DecryptingVideoDecoder\"},\"stack\":[{\"file\":\"../../media/filters/decoder_selector.cc\",\"line\":172}],\"status_code\":265,\"status_message\":\"\"}"
00:00:00.065kIsVideoDecryptingDemuxerStream false
00:00:00.065kVideoDecoderName   "MojoVideoDecoder"
00:00:00.065kIsPlatformVideoDecoder true
00:00:00.065info"Selected MojoVideoDecoder for video decoding, config: 
codec: h264, profile: h264 high, level: not available, alpha_mode: is_opaque, 
coded size: [1920,1080], visible rect: [0,0,1920,1080], natural size: 
[1920,1080], has extra data: false, encryption scheme: Unencrypted, rotation: 
0°, flipped: 0, color space: {primaries:BT709, transfer:BT709, matrix:BT709, 
range:LIMITED}"
00:00:00.065pipeline_state  "kPlaying"
(...)

$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 
v5/6th Gen Core Processor Thermal Subsystem (rev 08)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
00:15.0 Signal processing controller: 

[Desktop-packages] [Bug 1888157] Re: Thunderbird 78

[Sebastien Bacher]

https://launchpad.net/ubuntu/+source/thunderbird/1:78.1.1+build1-0ubuntu1

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

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

Title:
  Thunderbird 78

Status in thunderbird package in Ubuntu:
  Fix Committed

Bug description:
  There is a new ESR release of Thunderbird and I don't see an issue
  about the plans for the move to that new version. There looks to be
  some changes to the profile that are one way--once you have moved that
  profile to version 78, you can't work with it on older versions of
  Thunderbird.

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

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

[Desktop-packages] [Bug 1873184] Re: Wired and wireless connection details have not enough height and items overlap

[Sebastien Bacher]

** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress => 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/1873184

Title:
  Wired and wireless connection details have not enough height and items
  overlap

Status in gnome-control-center:
  Unknown
Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  There is a display bug when you unplug the network cable on focal.
  Please see attachment

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

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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Marc Lijour]

This used to do the trick for me. Since an upgrade to 20.04 the decoding is not 
working properly. Chromium (86 here) is not calling MojoVideoDecoder.
https://www.linuxuprising.com/2018/08/how-to-enable-hardware-accelerated.html


That may be related to a switch to the iHD driver (active now according to 
vainfo). I noticed other problems with ffpmeg for screengrabbing.

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  News :

  - Candidate Chromium 83 Snap with vaapi enabled can be installed with
  :

  sudo snap install --channel=candidate/vaapi chromium

  Check that your vidéo is gpu decoded but checking "MojoVideoDecoder"
  in about:media-internals

  Widevine DRM streams will have DecryptingVideoDecoder

  Please report success/failure with

  - distro version
  - GPU Hardware used
  - Codec used

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

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

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

[Desktop-packages] [Bug 1860671] Re: "Utilities" folder in Shell Overview is not created until Ubuntu Software is opened for a first time

[AsciiWolf]

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

** Also affects: snap-store-desktop
   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/1860671

Title:
  "Utilities" folder in Shell Overview is not created until Ubuntu
  Software is opened for a first time

Status in snap-store-desktop:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New

Bug description:
  This happens on the latest Ubuntu Focal clean installation. When
  opening the list of installed apps in Shell Overview, the "Utilities"
  folder in Shell Overview is missing (and all apps that should be in
  the folder are displayed in the main list) until Ubuntu Software is
  opened for a first time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-store-desktop/+bug/1860671/+subscriptions

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

[Desktop-packages] [Bug 1890843] [NEW] Xorg freeze

[Phil Marsh]

Public bug reported:

I am running Ubuntu 18.04 64 bit with Gnome III. Action to see bug:
1. double left mouse click on launcher icon on left toolbar (usually happens 
with Chromium Browser icon)
2. Desired result: Drop down menu appears with options to open Chromium browser 
3. Actual result when bug appears: Drop down menu appears then whole desktop 
freezes. No further mouseclicks on display work. Dropdown menu remains frozen 
on display.
4. Current workaround:
When bug appears, the  desktop can be unfrozen via cntl-alt-del keys but the 
drop-down menu remains frozen in place. Next, the frozen drop-down menu can now 
be closed by clicking on the "Activities" menu on the upper-left corner of the 
desktop and then clicking on the icon with the frozen drop-down menu. These 
actions close the frozen drop-down menu and restore normal operation of the 
Gnome III for a while until the bug pops up again. This bug has become 
especially common now rendering the desktop almost unusable and I'm thinking of 
replacing Gnome III due to this.
Thanks, Phil

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
Uname: Linux 4.15.0-112-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
.proc.driver.nvidia.gpus..82.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:82:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.138  Thu May 14 01:01:53 
PDT 2020
 GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
ApportVersion: 2.20.9-0ubuntu7.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug  7 12:37:36 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GM206 [GeForce GTX 950] [3842:2951]
InstallationDate: Installed on 2018-06-01 (798 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Supermicro X9DR3-F
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=89151cf5-98dc-43fa-9046-917fe8211331 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.0a
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X9DR3-F
dmi.board.vendor: Supermicro
dmi.board.version: 0123456789
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd07/31/2013:svnSupermicro:pnX9DR3-F:pvr0123456789:rvnSupermicro:rnX9DR3-F:rvr0123456789:cvnSupermicro:ct3:cvr0123456789:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: X9DR3-F
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic freeze third-party-packages 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/1890843

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I am running Ubuntu 18.04 64 bit with Gnome III. Action to see bug:
  1. double left mouse click on launcher icon on left toolbar (usually happens 
with Chromium Browser icon)
  2. Desired result: Drop down menu appears with options to open Chromium 
browser 
  3. Actual result when bug appears: Drop down menu appears then whole desktop 
freezes. No further mouseclicks on display work. Dropdown menu remains frozen 
on display.
  4. 

[Desktop-packages] [Bug 1888575] Re: Split motd-news config into a new package

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/388922

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in base-files source package in Xenial:
  In Progress
Status in ubuntu-meta source package in Xenial:
  In Progress
Status in base-files source package in Bionic:
  In Progress
Status in ubuntu-meta source package in Bionic:
  In Progress
Status in base-files source package in Focal:
  In Progress
Status in ubuntu-meta source package in Focal:
  In Progress
Status in base-files source package in Groovy:
  In Progress
Status in ubuntu-meta source package in Groovy:
  In Progress

Bug description:
  The motd-news script is largely useless for desktop users, as they
  rarely login via a text console. It makes more sense for server users.

  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a NEW package 
(motd-news-config)
  - have ubuntu-server depend on motd-news-config (or recommends)
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends (or recommends) on motd-news-config

  Care must be taken to preserve a changed /etc/default/motd-news when
  the upgrade installs the new motd-news-config package. For example, on
  a server that has set ENABLED=0 in /etc/default/motd-news and upgrades
  to the new base-files and ubuntu-server, and gets the new motd-config-
  news package, ENABLED=0 must remain set.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888575/+subscriptions

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

[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[tim474]

It seems that I have found the workaround. I copied
/lib/firmware/intel/ibt* from ubuntu 18.04 to 20.04

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1: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.

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

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

[Desktop-packages] [Bug 1890001] Re: Random stuttering while in game

[Strick Mcfingle]

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

Didn't mean to attatch it twice.

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

Title:
  Random stuttering while in game

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Updated kernel to 5.7.12 and updated nvidia driver to 450 yesterday
  but only experiencing this today.

  Random stuttering while playing minecraft, no clue what's causing it
  but I checked system monitor and it shows random spikes of a cpu
  thread to 100% and some spikes staying at 100% for a prolonged period.

  It may be related to me updating my video driver that is not
  recommended so I will see if switching down will resolve the issue.  I
  never had this issue on driver 440.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.7.12-050712-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .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  450.57  Sun Jul  5 14:42:25 
UTC 2020
   GCC version:  gcc version 10.2.0 (GCC)
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  1 13:57:56 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] [10de:1e87] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] TU104 [GeForce RTX 
2080 Rev. A] [1462:3726]
  InstallationDate: Installed on 2020-07-31 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. Z390 AORUS MASTER
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.7.12-050712-lowlatency 
root=UUID=76f51654-be39-4436-80da-a240e8149ca5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: Default string
  dmi.board.name: Z390 AORUS MASTER-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/04/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ390AORUSMASTER:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ390AORUSMASTER-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z390 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1890001] Re: Random stuttering while in game

[Strick Mcfingle]

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


** Attachment added: "journal-again.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890001/+attachment/5399606/+files/journal-again.txt

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

Title:
  Random stuttering while in game

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Updated kernel to 5.7.12 and updated nvidia driver to 450 yesterday
  but only experiencing this today.

  Random stuttering while playing minecraft, no clue what's causing it
  but I checked system monitor and it shows random spikes of a cpu
  thread to 100% and some spikes staying at 100% for a prolonged period.

  It may be related to me updating my video driver that is not
  recommended so I will see if switching down will resolve the issue.  I
  never had this issue on driver 440.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.7.12-050712-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .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  450.57  Sun Jul  5 14:42:25 
UTC 2020
   GCC version:  gcc version 10.2.0 (GCC)
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  1 13:57:56 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] [10de:1e87] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] TU104 [GeForce RTX 
2080 Rev. A] [1462:3726]
  InstallationDate: Installed on 2020-07-31 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. Z390 AORUS MASTER
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.7.12-050712-lowlatency 
root=UUID=76f51654-be39-4436-80da-a240e8149ca5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: Default string
  dmi.board.name: Z390 AORUS MASTER-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/04/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ390AORUSMASTER:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ390AORUSMASTER-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z390 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1890001] Re: Random stuttering while in game

[Strick Mcfingle]

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


** Attachment added: "journal-again.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890001/+attachment/5399607/+files/journal-again.txt

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

Title:
  Random stuttering while in game

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Updated kernel to 5.7.12 and updated nvidia driver to 450 yesterday
  but only experiencing this today.

  Random stuttering while playing minecraft, no clue what's causing it
  but I checked system monitor and it shows random spikes of a cpu
  thread to 100% and some spikes staying at 100% for a prolonged period.

  It may be related to me updating my video driver that is not
  recommended so I will see if switching down will resolve the issue.  I
  never had this issue on driver 440.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.7.12-050712-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .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  450.57  Sun Jul  5 14:42:25 
UTC 2020
   GCC version:  gcc version 10.2.0 (GCC)
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  1 13:57:56 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] [10de:1e87] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] TU104 [GeForce RTX 
2080 Rev. A] [1462:3726]
  InstallationDate: Installed on 2020-07-31 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. Z390 AORUS MASTER
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.7.12-050712-lowlatency 
root=UUID=76f51654-be39-4436-80da-a240e8149ca5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: Default string
  dmi.board.name: Z390 AORUS MASTER-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/04/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ390AORUSMASTER:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ390AORUSMASTER-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z390 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[tim474]

PLEASE HELP!!! ANY WORKAROUND PLEASE!!!

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1: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.

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

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

[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[tim474]

Bluetooth device is 8087:0aaa

HSP works on the same device with ubuntu 18.04 with OEM kernel (as I
remember 5.0)

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1: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.

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

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

[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[tim474]

Same problem, liquorix didn't help.

```
$ sudo dmesg | grep blue -i
[   18.829608] Bluetooth: Core ver 2.22
[   18.829633] Bluetooth: HCI device and connection manager initialized
[   18.829638] Bluetooth: HCI socket layer initialized
[   18.829641] Bluetooth: L2CAP socket layer initialized
[   18.829645] Bluetooth: SCO socket layer initialized
[   18.951265] Bluetooth: hci0: Bootloader revision 0.0 build 0 week 30 2018
[   18.952080] Bluetooth: hci0: Device revision is 2
[   18.952082] Bluetooth: hci0: Secure boot is enabled
[   18.952083] Bluetooth: hci0: OTP lock is enabled
[   18.952084] Bluetooth: hci0: API lock is enabled
[   18.952085] Bluetooth: hci0: Debug lock is disabled
[   18.952086] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   18.955123] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-0.sfi
[   20.470860] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   20.470862] Bluetooth: BNEP filters: protocol multicast
[   20.470879] Bluetooth: BNEP socket layer initialized
[   20.480262] Bluetooth: hci0: Waiting for firmware download to complete
[   20.481072] Bluetooth: hci0: Firmware loaded in 1494799 usecs
[   20.481147] Bluetooth: hci0: Waiting for device to boot
[   20.495259] Bluetooth: hci0: Device booted in 13804 usecs
[   20.495772] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-0.ddc
[   20.496201] Bluetooth: hci0: Failed to send Intel_Write_DDC (-22)
[   20.498169] Bluetooth: hci0: Firmware revision 0.0 build 128 week 11 2020
[   23.936736] Bluetooth: RFCOMM TTY layer initialized
[   23.936747] Bluetooth: RFCOMM socket layer initialized
[   23.936753] Bluetooth: RFCOMM ver 1.11
```

Headset Afresshokz Air.

It works as HSP on Fedora with kernel 5.6

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1: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.

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

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

[Desktop-packages] [Bug 1878330] Re: wrong icon used in the about dialog

[crvi]

This issue was fixed in:

https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1775

This is different from the "About dialog" icon issue. Both were
regressions introduced after the new icon update.

** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/-/issues #1775
   https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1775

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

Title:
  wrong icon used in the about dialog

Status in rhythmbox package in Ubuntu:
  Fix Committed

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

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

  Rhythmbox Plugins: Tray Icon, ReplyGain, Notification,  MPRIS D-Bus
  interface, MediaServer2 D-Bus interface, and Hine rhythmbox on start

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rhythmbox 3.4.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed May 13 00:03:50 2020
  InstallationDate: Installed on 2018-04-29 (744 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1890650] Re: Activities button, Alt-F1, and super not working after upgrade to 20.04

[Andy Howell]

Daniel,

Thanks for you help. The gsettings showed that there some bindings
involving "super". I tried those an they all worked. I tried
"Activities" again and it worked.

I did remove some packages after I noticed the problem. I've attached
that history in case it helps someone else with this issue.


** Attachment added: "dpkg history"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890650/+attachment/5399600/+files/history.log

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

Title:
  Activities button, Alt-F1, and super not working after upgrade to
  20.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  If I hit the Activities button, all open applications are hidden.
  There is no way to get the applications to display again. The
  application I select is started, and shows up on the vertical bar in
  the left with an orange dot by it.

  What magic is needed to bring the applications back?

  They are still there. I see them when I go to log out. Logging out is
  the only option for restoring Gnome.

  The same problem happens if I hit Alt-F1 or Super. Shouldn't these
  toggle?

  The only way to get a screen shot it with my phone. Sorry for the
  quality. You can see on the left that I started gimp.Up to 19.10, when
  I used "Activities", it would launch the app and then return to my
  running applications.

  Originally asked here:

  https://askubuntu.com/questions/1264414/activities-button-alt-f1-and-
  super-not-working-after-upgrade-to-20-04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.23
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  6 13:29:43 2020
  InstallationDate: Installed on 2018-10-14 (661 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-08-03 (2 days ago)
  VarLogDistupgradeTermlog:

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

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

[Desktop-packages] [Bug 1890650] Re: Activities button, Alt-F1, and super not working after upgrade to 20.04

[Andy Howell]

My gsettings.

** Attachment added: "gsettings list-recursively org.gnome.shell"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890650/+attachment/5399601/+files/settings.txt

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

Title:
  Activities button, Alt-F1, and super not working after upgrade to
  20.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  If I hit the Activities button, all open applications are hidden.
  There is no way to get the applications to display again. The
  application I select is started, and shows up on the vertical bar in
  the left with an orange dot by it.

  What magic is needed to bring the applications back?

  They are still there. I see them when I go to log out. Logging out is
  the only option for restoring Gnome.

  The same problem happens if I hit Alt-F1 or Super. Shouldn't these
  toggle?

  The only way to get a screen shot it with my phone. Sorry for the
  quality. You can see on the left that I started gimp.Up to 19.10, when
  I used "Activities", it would launch the app and then return to my
  running applications.

  Originally asked here:

  https://askubuntu.com/questions/1264414/activities-button-alt-f1-and-
  super-not-working-after-upgrade-to-20-04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.23
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  6 13:29:43 2020
  InstallationDate: Installed on 2018-10-14 (661 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-08-03 (2 days ago)
  VarLogDistupgradeTermlog:

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

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

[Desktop-packages] [Bug 1886692] Re: [SRU] libreoffice 6.4.5 for focal

[Iain Lane]

Hello Heather, or anyone else affected,

Accepted libreoffice into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libreoffice/1:6.4.5-0ubuntu0.20.04.1
in a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: libreoffice (Ubuntu Focal)
   Status: New => Fix Committed

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

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

Title:
   [SRU] libreoffice 6.4.5 for focal

Status in libreoffice package in Ubuntu:
  In Progress
Status in libreoffice source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 6.4.5 is in its fifth bugfix release of the 6.4 line. Version 
6.4.4 is currently in focal.
 For a list of fixed bugs compared to 6.4.4 see the list of bugs fixed in 
the two release candidates:
   https://wiki.documentfoundation.org/Releases/6.4.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.4.4/RC2#List_of_fixed_bugs
 (that's a total of 96 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 96 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

[Desktop-packages] [Bug 1890632] Re: Can't open preferences

[crvi]

Start rhythmbox from command line ( gnome-terminal ), as below:

$ rhythmbox --disable-plugins

The preferences should be visible. This is probably an issue with
alternative-toolbar plugin. You can disable the plugin in preferences,
and restart rhythmbox normally. If the issue goes away, please report a
bug at:

https://github.com/fossfreedom/alternative-toolbar/issues/new

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

Title:
  Can't open preferences

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  I can't seem to access the rhymbox preferences.
  'Preferences' does not appear in the application menu (see attachment) since 
ubuntu 17.10.
  I was still able to edit the preferences from the menu under the song slider, 
but I have now accidentally removed the whole top bar (with the current song, 
the previous, next, pause buttons, and that menu button).

  So now I can't open the preferences, nor see the current song anymore,
  or have it display again.

  Note that the option in the view menu might have been from the
  Alternative-Toolbar plugin

  A temporary fix to get the view menu again would be appreciated too.

  $ lsb_release -rd
  Description: Ubuntu 20.04.1 LTS
  Release: 20.04

  $ apt-cache policy rhythmbox
  rhythmbox:
Installed: 3.4.4-1ubuntu2
Candidate: 3.4.4-1ubuntu2
Version table:
   *** 3.4.4-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Mirror of the attachment (screenshot of the application menu):
  https://i.imgur.com/CJUVoRZ.png

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

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

[Desktop-packages] [Bug 1890494] Re: Closing Rhythmbox does not free the media keys

[crvi]

What happens when you start rhythmbox with all plugins disabled, in
command line as below:

$ rhythmbox --disable-plugins

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

Title:
  Closing Rhythmbox does not free the media keys

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Closing Rhythmbox, does not free the media keys, and no program can
  use them after that, not even Rhythmbox if you restart it.

  This seems to be very close to bug #1036489, but that one was active 8
  years ago, and was marked as expired 6 years ago.

  Restarting the machine frees the media keys again.

  Steps to reproduce:

  1. Verify that the media keys work (restart the machine if not)
  2. close rhythmbox with right click on the taskbar icon, use "stop & quit"
  3. reopen rhythmbox, the media keys do not work.

  1. Verify that the media keys work (restart the machine if not)
  2. End the 'rhythmbox' process
  3. reopen rhythmbox, the media keys do not work.

  1. Verify that the media keys work (restart the machine if not)
  2. in rhythmbox go to preferences -> plugins -> click preferences for any 
plugin
  3. click the 'restart' next to "Restart the player for the changes to take 
effect"
  4. once rhythmbox restarts, the media keys do not work anymore.

  
  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  
  $ apt-cache policy rhythmbox
  rhythmbox:
Installed: 3.4.4-1ubuntu2
Candidate: 3.4.4-1ubuntu2
Version table:
   *** 3.4.4-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1889106] Re: [SRU] Upgrading from 18.04 to 20.04 will keep the 18.04 chromium-browser due to a higher version than the transitional deb in 20.04

[Olivier Tilloy]

Thanks Łukasz.

In the meantime the 84.0.4147.105 update was published to
{xenial,bionic}-{security,updates}, so the version number needs bumping
again, for the upgrade path to really work.

I have uploaded 84.0.4147.105-0ubuntu1 to groovy-proposed, and
84.0.4147.105-0ubuntu0.20.04.1 is now in the focal unapproved queue,
could you please accept it, to supersede 84.0.4147.89-0ubuntu0.20.04.1 ?

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

Title:
  [SRU] Upgrading from 18.04 to 20.04 will keep the 18.04 chromium-
  browser due to a higher version than the transitional deb in 20.04

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Focal:
  Fix Committed

Bug description:
  This bug is another manifestation of bug #1858500, but with a different 
upgrade path.
  bionic-{security,updates} will soon have chromium-browser 
84.0.4147.89-0ubuntu0.18.04.2 (pending sponsoring by the security team), and 
when that happens the version number in focal will be lower, meaning that 
chromium-browser won't be updated to the new package that installs the snap for 
a user upgrading from 18.04 to 20.04.

  Since chromium-browser in 20.04 is a mostly empty transitional package
  that installs the chromium snap, all that's needed to fix this is to
  bump its version number.

  [Impact]

  Users upgrading from 18.04 to 20.04 will not get the latest chromium snap 
replacing the chromium-browser deb package as intended.
  This is because the version number in 18.04 is (will soon be) greater than 
the version in 20.04. Bumping the version number in 20.04 is enough to fix this.

  [Test Case]

   * Ensure that chromium-browser 84.0.4147.89-0ubuntu0.18.04.2 is available in 
bionic-{security,updates}
   * On a machine running 18.04, ensure that the chromium snap is *not* 
installed, then install the chromium-browser deb package: sudo apt install 
chromium-browser
   * Upgrade that machine to Ubuntu 20.04
   * When upgrading, the chromium-browser package becomes a transitional 
package that installs the chromium snap
   * Verify that the chromium snap is installed

  [Regression Potential]

   * The chromium snap has some known shortcomings and regressions
  compared to the deb package, they are being tracked at
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bugs?field.tag=snap. Auto-upgrading users from the deb to the
  snap is the desired behaviour though.

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

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

[Desktop-packages] [Bug 1889106] Re: [SRU] Upgrading from 18.04 to 20.04 will keep the 18.04 chromium-browser due to a higher version than the transitional deb in 20.04

[Launchpad Bug Tracker]

** Branch linked: lp:~chromium-team/chromium-browser/groovy-stable

** Branch linked: lp:~chromium-team/chromium-browser/focal-stable

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

Title:
  [SRU] Upgrading from 18.04 to 20.04 will keep the 18.04 chromium-
  browser due to a higher version than the transitional deb in 20.04

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Focal:
  Fix Committed

Bug description:
  This bug is another manifestation of bug #1858500, but with a different 
upgrade path.
  bionic-{security,updates} will soon have chromium-browser 
84.0.4147.89-0ubuntu0.18.04.2 (pending sponsoring by the security team), and 
when that happens the version number in focal will be lower, meaning that 
chromium-browser won't be updated to the new package that installs the snap for 
a user upgrading from 18.04 to 20.04.

  Since chromium-browser in 20.04 is a mostly empty transitional package
  that installs the chromium snap, all that's needed to fix this is to
  bump its version number.

  [Impact]

  Users upgrading from 18.04 to 20.04 will not get the latest chromium snap 
replacing the chromium-browser deb package as intended.
  This is because the version number in 18.04 is (will soon be) greater than 
the version in 20.04. Bumping the version number in 20.04 is enough to fix this.

  [Test Case]

   * Ensure that chromium-browser 84.0.4147.89-0ubuntu0.18.04.2 is available in 
bionic-{security,updates}
   * On a machine running 18.04, ensure that the chromium snap is *not* 
installed, then install the chromium-browser deb package: sudo apt install 
chromium-browser
   * Upgrade that machine to Ubuntu 20.04
   * When upgrading, the chromium-browser package becomes a transitional 
package that installs the chromium snap
   * Verify that the chromium snap is installed

  [Regression Potential]

   * The chromium snap has some known shortcomings and regressions
  compared to the deb package, they are being tracked at
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bugs?field.tag=snap. Auto-upgrading users from the deb to the
  snap is the desired behaviour though.

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

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

[Desktop-packages] [Bug 1888380] Re: Give better experience of migration of deb to snap

[Olivier Tilloy]

Fixed with https://git.launchpad.net/~chromium-team/chromium-
browser/+git/snap-from-
source/commit/?id=9dfbfe4fd02e254354ec038a9aa3da26980b89d2.

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Give better experience of migration of deb to snap

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Summary of current state:

  Back in 19.10 we migrated the deb of chromium to a snap. Users who
  installed the deb, got snapd and the snap of chromium. Users who
  already had the deb of chromium, and upgraded, got snapd and the snap.

  The goal of making the snap was (largely) to reduce the workload on
  the desktop team in packaging chromium, and to enable the desktop team
  to publish updates to users very quickly across all supported
  releases. For users, the goal is to have an up to date chromium
  browser.

  For people upgrading, the migration goal was to ensure they kept the
  browser they'd installed (chromium has never been a default on Ubuntu,
  but has been on at least one flavour).

  Feedback from the field:

   * Some have complained that the Chromium snap has bugs which didn't manifest 
in the deb (see this very bug tracker)
   * Some complained that there was no indication that they'd have a deb 
replaced by a snap (hard to know how many users actually care about this)
   * Derivative distributions have complained that snapd is being installed 
"under the covers" or "via the backdoor" (or other pejorative statements)

  Suggestion for improvement:

  I believe a fair amount of critique comes from the ignorance of why
  chromium was migrated to a snap, as most users don't read our blog
  posts, news articles or release notes. In addition, there's not a
  tremendous number of user-facing packages which have gone through the
  deb-to-snap migration, so not a lot of prior art in the field.

  So it's my believe we should document this better, inform the users
  better.

  * At the point of installation of the deb, make it clear that snapd will be 
installed, followed by the chromium snap (and whatever other content and base 
snaps are required). 
  * During an upgrade from the deb to the snap, make it clear the deb is being 
replaced, with similar information to when the snap is installed.
  * Link to documentation / blog / specific release notes in visible places 
which makes it clear why this is happening.

  I'll refrain from suggesting technical solutions because I think we
  need to discuss the options.

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

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

[Desktop-packages] [Bug 1811530] Re: Impress embeded video files show flickering white stripes

[klinge]

I can confirm the behaviour Muench describes on Ubuntu 20.04 with LO
6.4.4.2.

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

Title:
  Impress embeded video files show flickering white stripes

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Description:
  I have slide shows with embeded video files from previous versions of 
LibreOffice / Impress and they all worked well. If I play the video files with 
Ubuntu 18.04 and LibreOffice 6.0.7.3 they show flickering white stripes. the 
stripes are about 1 centimeter wide and move up and down in the picture of the 
video.

  Steps to Reproduce:
  1. Embed a video file in a slide show.
  2. Play the slide show / the video.

  Actual Results:
  The video plays but shows a disrupted picture with whiteish flickering 
stripes.

  Expected Results:
  The video should play as it is in a video player whithout a disrupted picture.

  It seems to be connected wit hardware acceleration, that is greyed out. The 
newest appimage of LibreOffice is working as expected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-12 (278 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-11 (280 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1811530/+subscriptions

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

[Desktop-packages] [Bug 1890814] Re: Handle PPP non-compliant success packets

[Douglas Kosovic]

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

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

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

Title:
  Handle PPP non-compliant success packets

Status in ppp package in Ubuntu:
  New
Status in ppp package in Debian:
  Unknown

Bug description:
  [Impact]
  According to RFC2759, the format of PPP success packets is :

  "S= M="

  Recently Windows Server 2019 has started producing non-complaint PPP
  success packets which have a space missing before the M= characters.

  PPP based (e.g. PPTP, L2TP, etc) VPN clients connecting to an affected
  Windows Server 2019 VPN server will get the following error message
  during MS-CHAPv2 authentication :

 MS-CHAPv2 Success packet is badly formed

  
  If the following upstream ppp patch is applied, it will handle the 
non-compliant, missing-space before M= success packets :

  
https://github.com/paulusmack/ppp/commit/3cd95baf3f1de1d5a9bc89be0f4c3215ceb5aefe.patch

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

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

[Desktop-packages] [Bug 1890814] Re: Handle PPP non-compliant success packets

[Douglas Kosovic]

macOS already handles the missing space before M=, extract from :
https://opensource.apple.com/source/ppp/ppp-862.120.2/Helpers/pppd/chap_ms.c.auto.html

//we'll allow the missing-space case from the server, even though
//it's non-conforming to spec!
dbglog("Rcvd non-conforming MSCHAPv2 Success packet, len=%d", len);
if(len >= 2 && !strncmp((char*)msg, "M=", 2))
msg += 2;
else
{
error("MS-CHAPv2 Success packet is badly formed.");
return 0;
}

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

Title:
  Handle PPP non-compliant success packets

Status in ppp package in Ubuntu:
  New
Status in ppp package in Debian:
  Unknown

Bug description:
  [Impact]
  According to RFC2759, the format of PPP success packets is :

  "S= M="

  Recently Windows Server 2019 has started producing non-complaint PPP
  success packets which have a space missing before the M= characters.

  PPP based (e.g. PPTP, L2TP, etc) VPN clients connecting to an affected
  Windows Server 2019 VPN server will get the following error message
  during MS-CHAPv2 authentication :

 MS-CHAPv2 Success packet is badly formed

  
  If the following upstream ppp patch is applied, it will handle the 
non-compliant, missing-space before M= success packets :

  
https://github.com/paulusmack/ppp/commit/3cd95baf3f1de1d5a9bc89be0f4c3215ceb5aefe.patch

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

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

[Desktop-packages] [Bug 1890814] [NEW] Handle PPP non-compliant success packets

[Douglas Kosovic]

Public bug reported:

[Impact]
According to RFC2759, the format of PPP success packets is :

"S= M="

Recently Windows Server 2019 has started producing non-complaint PPP
success packets which have a space missing before the M= characters.

PPP based (e.g. PPTP, L2TP, etc) VPN clients connecting to an affected
Windows Server 2019 VPN server will get the following error message
during MS-CHAPv2 authentication :

   MS-CHAPv2 Success packet is badly formed


If the following upstream ppp patch is applied, it will handle the 
non-compliant, missing-space before M= success packets :

https://github.com/paulusmack/ppp/commit/3cd95baf3f1de1d5a9bc89be0f4c3215ceb5aefe.patch

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


** Tags: sru

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

Title:
  Handle PPP non-compliant success packets

Status in ppp package in Ubuntu:
  New

Bug description:
  [Impact]
  According to RFC2759, the format of PPP success packets is :

  "S= M="

  Recently Windows Server 2019 has started producing non-complaint PPP
  success packets which have a space missing before the M= characters.

  PPP based (e.g. PPTP, L2TP, etc) VPN clients connecting to an affected
  Windows Server 2019 VPN server will get the following error message
  during MS-CHAPv2 authentication :

 MS-CHAPv2 Success packet is badly formed

  
  If the following upstream ppp patch is applied, it will handle the 
non-compliant, missing-space before M= success packets :

  
https://github.com/paulusmack/ppp/commit/3cd95baf3f1de1d5a9bc89be0f4c3215ceb5aefe.patch

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

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

[Desktop-packages] [Bug 1811530] Re: Impress embeded video files show flickering white stripes

[Muench]

I am also affected by the problem with the flickering video.
May be my observation helps someone to find a solution or workfix.

I test it with LO 6.3.5.2 / LO 6.4.5 / LO 7.0.0.1 at ubuntu 19.10 with a
simple impress document embedded a mp4 movie. Flickering appears in all
versions at the full presentation screen.


But, if I use the right mouse key in the presentation mode the control window 
(with Next, Got to Slide, ... menus) appears on the presentation screen and the 
flickering stops immediately. As long as the control window appears, the movie 
runs how it should be. Unfortunately the control window is to large for using 
this as a interim solution.

May be, somebody can find a workaround to produce a smaller window with
the mouse key, like this control window?


Meanwhile I install a new ubuntu 20.04 LTS from scratch. 
Unfortunately the problem remains.

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

Title:
  Impress embeded video files show flickering white stripes

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Description:
  I have slide shows with embeded video files from previous versions of 
LibreOffice / Impress and they all worked well. If I play the video files with 
Ubuntu 18.04 and LibreOffice 6.0.7.3 they show flickering white stripes. the 
stripes are about 1 centimeter wide and move up and down in the picture of the 
video.

  Steps to Reproduce:
  1. Embed a video file in a slide show.
  2. Play the slide show / the video.

  Actual Results:
  The video plays but shows a disrupted picture with whiteish flickering 
stripes.

  Expected Results:
  The video should play as it is in a video player whithout a disrupted picture.

  It seems to be connected wit hardware acceleration, that is greyed out. The 
newest appimage of LibreOffice is working as expected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-12 (278 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-11 (280 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1811530/+subscriptions

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

[Desktop-packages] [Bug 1857335] Re: System volume slider only works between ~90% and 100% with a USB 2.0 speaker

[Max Waterman]

I can't change the status to confirmed. What's the point in instructions
that people are prevented from following? Very frustrating.

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

Title:
  System volume slider only works between ~90% and 100% with a USB 2.0
  speaker

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  This is only with my USB 2.0 speaker[1] - with other devices, it works
  fine and the slider's 0% corresponds to silent and 100% full. With my
  USB 2.0 speaker, with the 'output' set to 'Analogue Output - USB2.0
  Device', it only has an effect between about 90% and 100%.

  I took a video of the problem and uploaded it here:

  http://davidmaxwaterman.fastmail.co.uk/xfer/ubuntu_volume_problem.mp4

  [1]
  
https://www.amazon.co.uk/gp/product/B07W1KN1XD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8=1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 23 10:00:17 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-07-19 (156 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2019-10-28 (56 days ago)

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

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

[Desktop-packages] [Bug 1857335] Re: System volume slider only works between ~90% and 100% with a USB 2.0 speaker

[Max Waterman]

Still a problem: Ubuntu 20.04.1 LTS

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

Title:
  System volume slider only works between ~90% and 100% with a USB 2.0
  speaker

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  This is only with my USB 2.0 speaker[1] - with other devices, it works
  fine and the slider's 0% corresponds to silent and 100% full. With my
  USB 2.0 speaker, with the 'output' set to 'Analogue Output - USB2.0
  Device', it only has an effect between about 90% and 100%.

  I took a video of the problem and uploaded it here:

  http://davidmaxwaterman.fastmail.co.uk/xfer/ubuntu_volume_problem.mp4

  [1]
  
https://www.amazon.co.uk/gp/product/B07W1KN1XD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8=1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 23 10:00:17 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-07-19 (156 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2019-10-28 (56 days ago)

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

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

[Desktop-packages] [Bug 1890802] [NEW] Big performance degradation in X11 + 4K resolution + fractional scaling in second monitor compared to Wayland

[Amr Ibrahim]

Public bug reported:

Laptop: Lenovo ThinkPad L480
Graphics: Intel UHD Graphics 620 (KBL GT2)
Second monitor: Philips 276E8VJSB/00 4K UHD

There is a big performance degradation in an X11 session + 4K resolution
+ 125% fractional scaling in the second monitor compared to a Wayland
session. The mouse cursor moves very slow, dragging Windows is very
slow, scrolling in Firefox is very laggy, so everything becomes
unusable. The performance degradation applies in both displays even
though fractional scaling is only applied in the second 4K monitor.

Whereas in Wayland, the performance is much better in 4K resolution +
fractional scaling in the second monitor, the mouse cursor and dragging
windows are a lot smoother. I just sometimes notice a slight jump in the
mouse cursor but only in the second monitor, the built-in monitor
behaves normally.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: mutter 3.36.3-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug  7 12:00:26 2020
InstallationDate: Installed on 2020-04-26 (102 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Big performance degradation in X11 + 4K resolution + fractional
  scaling in second monitor compared to Wayland

Status in mutter package in Ubuntu:
  New

Bug description:
  Laptop: Lenovo ThinkPad L480
  Graphics: Intel UHD Graphics 620 (KBL GT2)
  Second monitor: Philips 276E8VJSB/00 4K UHD

  There is a big performance degradation in an X11 session + 4K
  resolution + 125% fractional scaling in the second monitor compared to
  a Wayland session. The mouse cursor moves very slow, dragging Windows
  is very slow, scrolling in Firefox is very laggy, so everything
  becomes unusable. The performance degradation applies in both displays
  even though fractional scaling is only applied in the second 4K
  monitor.

  Whereas in Wayland, the performance is much better in 4K resolution +
  fractional scaling in the second monitor, the mouse cursor and
  dragging windows are a lot smoother. I just sometimes notice a slight
  jump in the mouse cursor but only in the second monitor, the built-in
  monitor behaves normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  7 12:00:26 2020
  InstallationDate: Installed on 2020-04-26 (102 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Desktop-packages] [Bug 1838919] Re: Slow and lost keyboard and mouse events

[Brian Burch]

Daniel

I am Brian's wife, Jane

I am devastated to let you know that Brian succumbed to his prostate 
cancer and died a few weeks ago
Please let everyone know

Thanks

Jane Burch

On 7/8/20 7:50 pm, Daniel van Vugt wrote:
> Thank you for reporting this bug to Ubuntu.
> Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
>
> See this document for currently supported Ubuntu releases:
> https://wiki.ubuntu.com/Releases
>
> We appreciate that this bug may be old and you might not be interested
> in discussing it any more. But if you are then please upgrade to the
> latest Ubuntu version and re-test. If you then find the bug is still
> present in the newer Ubuntu version, please add a comment here telling
> us which new version it is in and change the bug status to Confirmed.
>
> ** Changed in: gnome-shell (Ubuntu)
> Status: Incomplete => Won't Fix
>
> ** Changed in: mutter (Ubuntu)
> Status: Incomplete => Won't Fix
>

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

Title:
  Slow and lost keyboard and mouse events

Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  This was a fresh amd64 installation with 18.10 desktop, upgraded to
  19.04 as soon as available. It has been getting worse over the last
  few weeks and is now so bad I can hardly type an email (or this bug
  report!) without having to fix many typos.

  journalctl shows many different gnome errors, so it is difficult to
  figure out which is the underlying cause and which are simply
  collateral damage.

  There are two sequences that appear first after a reboot, and the
  first of these has been reported many times on ubuntu releases going
  back for years:-

  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ module 
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be 
loaded.
  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ 2.x symbols 
detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # Failed to load module 
"canberra-gtk-module"

    and 

  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.89/org/ayatana/NotificationItem/software_update_available
  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
  Aug 05 09:12:19 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091219.948098:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
  Aug 05 09:12:21 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091221.376983:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
  Aug 05 09:12:22 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091222.542169:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <-

  Is this a recent regression? I know for sure the system wasn't this
  unresponsive 3 weeks ago, but I cannot be sure when it started to go
  wrong. My mouse/keyboard combo has a USB-wireless dongle and I've
  fiddled around with distance and battery state until I was sure the
  problem was somewhere else and started to check the system 

[Desktop-packages] [Bug 1890801] [NEW] eog and its child windows stay in dark theme regardless of general appearance setting

[Hilbricht]

Public bug reported:

Eog, including child windows such as the printing dialog, stays dark
themed, despite the general appearance setting as "standard" or "light".
Other applications respect the chosen appearance setting.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: eog 3.36.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug  7 11:54:54 2020
InstallationDate: Installed on 2019-01-22 (562 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: eog
UpgradeStatus: Upgraded to focal on 2020-08-04 (3 days ago)

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

Title:
  eog and its child windows stay in dark theme regardless of general
  appearance setting

Status in eog package in Ubuntu:
  New

Bug description:
  Eog, including child windows such as the printing dialog, stays dark
  themed, despite the general appearance setting as "standard" or
  "light". Other applications respect the chosen appearance setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: eog 3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  7 11:54:54 2020
  InstallationDate: Installed on 2019-01-22 (562 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: eog
  UpgradeStatus: Upgraded to focal on 2020-08-04 (3 days ago)

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

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

[Desktop-packages] [Bug 1868131] Re: [Toshiba NB250] Integrated speakers always muted

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

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

Title:
  [Toshiba NB250] Integrated speakers always muted

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Speakers are muted at boot and remains muted after plug and unplug 
headphones. Only can be activated from alsamixer, unmuting the headphones while 
the headphones are unplugged. Both speakers and
  headphones muting seems to be controlled in the Headphones area using 
alsamixer.

  Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia
  base: Ubuntu 18.04 bionic.

  I've "solved" it Linux Mint 19.3 Tricia in a not very good way,
  keeping automute activated in alsamixer, modifiyng
  /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf
  and executing a bash script at boot (sonido.sh) with the command
  "amixer set -c 0 Headphone unmute 100%" in order to prevent the
  speakers being muted.

  There are some issues reported to pulseaudio manteiners. Not the same
  but related:

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu1881 F pulseaudio
  CasperVersion: 1.427
  CurrentDesktop: XFCE
  Date: Thu Mar 19 15:58:26 2020
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2010
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.60
  dmi.board.name: PAV10 DDR2
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ
  dmi.product.name: TOSHIBA NB250
  dmi.product.sku: 012345678912345678912345678
  dmi.product.version: PLL2XE-005003AS
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1025388] Re: Internal mic stops working when plugging in headphones

[Daniel van Vugt]

** Tags removed: eoan quantal

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

Title:
  Internal mic stops working when plugging in headphones

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I am currently running Quantal and when I plug headphones into my
  headphone socket (which has an icon of a headset next to it, so I
  presume it can take some kind of headset), the internal mic on my
  laptop stops working. If I unplug the headphones the internal mic
  works as normal.

  I tried this with two different sets of headphones (one of which has a
  mic, and the other I think has a mic too).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: pulseaudio 1:2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
  Uname: Linux 3.5.0-4-generic i686
  ApportVersion: 2.3-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jono   1860 F pulseaudio
   /dev/snd/pcmC0D0c:   jono   1860 F...m pulseaudio
  Date: Mon Jul 16 11:01:32 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET56WW (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4239CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4239CTO
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1583840] Re: pulseaudio crashed with SIGSEGV in avahi_client_get_state() from publish_service() from once_callback() from dispatch_defer()

[Daniel van Vugt]

** Tags removed: eoan

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

Title:
  pulseaudio crashed with SIGSEGV in avahi_client_get_state() from
  publish_service() from once_callback() from dispatch_defer()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/e533a6f758cf595e0b31c717374dfed1acf6b2e9
  https://errors.ubuntu.com/problem/183fda6a99b85219cd01c114e0b5f8d6c3ae1090

  ---
  Not sure error report popped up on reboot of system...

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:8.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-23.41-lowlatency 4.4.10
  Uname: Linux 4.4.0-23-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  johndoe3047 F pulseaudio
    johndoe3120 F panel-6-mixer
  CurrentDesktop: XFCE
  Date: Thu May 19 18:39:25 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-03-04 (76 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160229)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   avahi_client_get_state () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? () from /usr/lib/pulse-8.0/modules/module-zeroconf-publish.so
   ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
  Title: pulseaudio crashed with SIGSEGV in avahi_client_get_state()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax kismet lpadmin plugdev 
pulse-access sambashare sudo video
  dmi.bios.date: 11/28/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0T656F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd11/28/2008:svnDellInc.:pnOptiPlex360:pvr:rvnDellInc.:rn0T656F:rvrA01:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 360
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

[Daniel van Vugt]

** Tags removed: eoan
** Tags added: focal groovy

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1852018] Re: Audio Stops Playing Briefly When Emptying Trash

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
   Status: Confirmed => Won't Fix

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

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

Title:
  Audio Stops Playing Briefly When Emptying Trash

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  I am running Ubuntu 19.10 and encountered this issue. I had a podcast
  playing in the background on Firefox v. 70.0.1 and I was deleting some
  files. I then proceeded to empty the trash and saw that the audio
  stops briefly till the "Empty all items from Trash?" prompt shows up.

  I was able to duplicate this many times and it even occurred with
  audio on Chrome.

  The expected way for things to work would be the audio keeps on
  playing, if I just empty the trash.

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

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

[Desktop-packages] [Bug 1631161] Re: Preferred output device is not remembered between logins

[Daniel van Vugt]

** Tags removed: eoan

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

Title:
  Preferred output device is not remembered between logins

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Whenever I reboot anew, pulseaudio has forgotten the correct audio
  port which I have set using the kde pulseaudio tool.

  I use line out, but it defaults to headphones, which is incorrect for
  my current setup. I expect it to remember that I wanted line out every
  time.

  Once selected, everything runs fine for that session, but it doesn't
  get saved and defaults back to the wrong output every time.

  Guessing this is pulseaudio as it happens with the gnome tool also.

  Tested not working in 16.04, 16.10 and Mint 18 (packages from 16.04).

  Policy installed: 1:8.0-0ubuntu3

  Cheers
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   kvd1577 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kvd1577 F...m pulseaudio
   /dev/snd/controlC0:  kvd1577 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Linux 18
  InstallationDate: Installed on 2016-10-02 (5 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160904
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: pulseaudio 1:8.0-0ubuntu3 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Tags: sarah third-party-packages
  Uname: Linux 4.4.0-38-generic x86_64
  UnreportableReason: This is not an official Linux package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/24/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F5f
  dmi.board.name: GA-770T-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5f:bd09/24/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-770T-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-770T-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-770T-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1839580] Re: LucidSound LS31 only outputs mono sound

[Daniel van Vugt]

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

** Tags added: fixed-in-13.99.1

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

Title:
  LucidSound LS31 only outputs mono sound

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  LucidSound LS31 only outputs mono sound.

  The usb vendor:prod = 2f12:0109.

  The fix is incoming.

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

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

[Desktop-packages] [Bug 1707611] Re: Sound does not automatically switch to HDMI when connected

[Daniel van Vugt]

** Tags removed: eoan

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

Title:
  Sound does not automatically switch to HDMI when connected

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When connecting a HDMI cable or other audio device, the user must
  manually click on the "sound volume" in the top-right and switch to
  the newly connected device.

  Example: you connect a HDMI cable to the television, but then you must
  manually choose the HDMI sound option; it does not get selected
  automatically.

  Often times e.g. when the HDMI cable is disconnected, the user must
  then manually click on the "speakers" or "line out" setting - EVEN IF
  IT'S ALREADY SELECTED, it must be clicked on again for the sound to
  work through the computer's speakers.

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

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

[Desktop-packages] [Bug 1853762] Re: Headphones stop working until pairing again

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Headphones stop working until pairing again

Status in bluez package in Ubuntu:
  Won't Fix
Status in gnome-control-center package in Ubuntu:
  Won't Fix

Bug description:
  I'm using Marshall MID ANC headphones with Ubuntu 19.10.
  Every now and then, I won't be able to use them without re-pairing first 
(like today - see logs).
  After re-pairing, everything works again for a while : I can switch off and 
on the headphones, reboot... Until it breaks again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov 24 19:13:40 2019
  InstallationDate: Installed on 2018-07-28 (483 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (37 days ago)
  dmi.bios.date: 11/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:AB:C5:7E:41:26  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:319948 acl:71 sco:0 events:45583 errors:0
TX bytes:37324973 acl:43061 sco:0 commands:2478 errors:0

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

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

[Desktop-packages] [Bug 1859996] Re: pulseaudio-equalizer make pulseaudio's start fail

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Won't Fix

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

Title:
  pulseaudio-equalizer make pulseaudio's start fail

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  After installing pulseaudio-equalizer package, Pulseaudio doesn't work
  anymore. Due to that, no device can be configured glad to KDE's sound
  widget: https://askubuntu.com/questions/976375/kubuntu-17-10-no-audio-
  devices-found-no-settings-no-sound

  sudo cat /var/log/syslog | grep pulseaudio
  [pulseaudio] module-equalizer-sink.c: module-equalizer-sink is currently 
unsupported, and can sometimes cause PulseAudio crashes, increased latency or 
audible artifacts.
  [pulseaudio] module-equalizer-sink.c: If you're facing audio problems, try 
unloading this module as a potential workaround.
  [pulseaudio] module-equalizer-sink.c: Master sink not found
  [pulseaudio] module.c: Failed to load module "module-equalizer-sink" 
(argument: ""): initialization failed.

  Also, "apt purge pulseaudio-equalizer" doesn't remove "load-module
  module-equalizer-sink" from the .config/pulse/default.pa so it
  continues to fail at start afterwards.

  sudo cat /var/log/syslog | grep pulseaudio
  [pulseaudio] ltdl-bind-now.c: Failed to open module module-equalizer-sink.so 
: module-equalizer-sink.so: cannot open shared object file: No such file or 
directory
  [pulseaudio] module.c: Failed to open module "module-equalizer-sink".

  
  NB: I cannot choose pulseaudio-equalizer as targeted package for this bug as 
it's not listed despite this:
  sudo apt search pulseaudio-equalizer
  pulseaudio-equalizer/eoan-updates 1:13.0-1ubuntu1.1 amd64
Equalizer sink module for PulseAudio sound server
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jean   1301 F pulseaudio
   /dev/snd/pcmC0D0p:   jean   1301 F...m pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-07 (131 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: pulseaudio 1:13.0-1ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Tags: eoan third-party-packages
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-28 (50 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo tty 
uucp www-data
  _MarkForUpload: True
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET59W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KG004JFR
  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:bvrN23ET59W(1.34):bd11/08/2018:svnLENOVO:pn20KG004JFR:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KG004JFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KG004JFR
  dmi.product.sku: LENOVO_MT_20KG_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/ubuntu/+source/pulseaudio/+bug/1859996/+subscriptions

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

[Desktop-packages] [Bug 1857335] Re: System volume slider only works between ~90% and 100% with a USB 2.0 speaker

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: pulseaudio (Ubuntu)
   Status: New => Won't Fix

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

Title:
  System volume slider only works between ~90% and 100% with a USB 2.0
  speaker

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  This is only with my USB 2.0 speaker[1] - with other devices, it works
  fine and the slider's 0% corresponds to silent and 100% full. With my
  USB 2.0 speaker, with the 'output' set to 'Analogue Output - USB2.0
  Device', it only has an effect between about 90% and 100%.

  I took a video of the problem and uploaded it here:

  http://davidmaxwaterman.fastmail.co.uk/xfer/ubuntu_volume_problem.mp4

  [1]
  
https://www.amazon.co.uk/gp/product/B07W1KN1XD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8=1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 23 10:00:17 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-07-19 (156 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2019-10-28 (56 days ago)

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

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

[Desktop-packages] [Bug 1855693] Re: Apple EarPods microphone is not detected (on a Macbook)

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Apple EarPods microphone is not detected (on a Macbook)

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  I have a set of headphones that work as speakers and microphone
  without problem on an android phone or on macos. Under ubuntu they are
  only detected as outputs, but not as microphone. in the audio settings
  I can select the output to be one of: internal speakers, hdmi monitor,
  or these headphones. The only input is the internal microphone of the
  laptop. When I make a call with microsoft teams, the other end
  confirms that they hear the sound from the room.

  The headphones are similar to these: https://www.ebay.com/itm
  /Earphones-Handsfree-Headphones-for-Samsung-
  Galaxy-S8-A5-A7-A8-A9-J1-J3-J5-J7-UK/163465454907 with a connector
  with four segments. I also tried another set of headphones, different
  brand, same behaviour: work fine in other devices, work as output-only
  in ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  1577 F pulseaudio
   /dev/snd/controlC1:  peter  1577 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  9 11:00:07 2019
  InstallationDate: Installed on 2019-11-14 (24 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2019
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 187.0.0.0.0
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvr187.0.0.0.0:bd07/22/2019:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Desktop-packages] [Bug 1866681] Re: [HP Pavilion dv9000] Mute toggles on/off while plugged into the headphone/speaker jack (19.04+)

[Daniel van Vugt]

** Tags removed: eoan
** Tags added: 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/1866681

Title:
  [HP Pavilion dv9000] Mute toggles on/off while plugged into the
  headphone/speaker jack (19.04+)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm on an HP Pavilion dv9000 (https://www.cnet.com/products/hp-
  pavilion-dv9000/specs/) built many years ago.

  
  Whenever I'm using any distro that's based on Ubuntu which was published from 
Version 19.04 onwards, I've been having a major issue with the mute button 
toggling on and off whenever I have something plugged into the audio out jack. 
I know that it's not the fault of XFCE, because I also use the latest version 
of Manjaro with XFCE on this same computer, and it works fine. I also know it's 
not any Red Hat-based distro, because I use Stella (which is a remix of CentOS 
6) also on this exact same computer, and it also works fine. Qubes, Mageia, and 
Fedora 31 also work perfectly fine and don't have this issue.

  My "lsb-release" is:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=19.10
  DISTRIB_CODENAME=eoan
  DISTRIB_DESCRIPTION="Ubuntu 19.10"

  and "apt-cache policy pulseaudio" outputs:
  pulseaudio:
Installed: 1:13.0-1ubuntu1.1
Candidate: 1:13.0-1ubuntu1.1
Version table:
   *** 1:13.0-1ubuntu1.1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  I've uploaded a short video of the problem that I recorded with my phone here:
  https://www.youtube.com/watch?v=GXaHXQA-5uQ

  
  The problem appears with Kali 2019 and 2020, Peppermint 19.04, Lubuntu 19.04, 
Xubuntu 19.04, and Sparky 5.10 and 2020.02.

  
  I've checked pretty much everything I can think of. There's a log for my ALSA 
help diagnostics results on my current computer (which works properly with 
18.04) at:
  http://alsa-project.org/db/?f=4859b85cd7fc32e7f01f8df63591b5a43dbf6829

  
  the result output of lspci is:
  [code]00:00.0 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2)
  00:00.1 RAM memory: NVIDIA Corporation C51 Memory Controller 0 (rev a2)
  00:00.2 RAM memory: NVIDIA Corporation C51 Memory Controller 1 (rev a2)
  00:00.3 RAM memory: NVIDIA Corporation C51 Memory Controller 5 (rev a2)
  00:00.4 RAM memory: NVIDIA Corporation C51 Memory Controller 4 (rev a2)
  00:00.5 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2)
  00:00.6 RAM memory: NVIDIA Corporation C51 Memory Controller 3 (rev a2)
  00:00.7 RAM memory: NVIDIA Corporation C51 Memory Controller 2 (rev a2)
  00:02.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:03.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:04.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:09.0 RAM memory: NVIDIA Corporation MCP51 Host Bridge (rev a2)
  00:0a.0 ISA bridge: NVIDIA Corporation MCP51 LPC Bridge (rev a3)
  00:0a.1 SMBus: NVIDIA Corporation MCP51 SMBus (rev a3)
  00:0a.3 Co-processor: NVIDIA Corporation MCP51 PMU (rev a3)
  00:0b.0 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3)
  00:0b.1 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3)
  00:0d.0 IDE interface: NVIDIA Corporation MCP51 IDE (rev f1)
  00:0e.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1)
  00:0f.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1)
  00:10.0 PCI bridge: NVIDIA Corporation MCP51 PCI Bridge (rev a2)
  00:10.1 Audio device: NVIDIA Corporation MCP51 High Definition Audio (rev a2)
  00:14.0 Bridge: NVIDIA Corporation MCP51 Ethernet Controller (rev a3)
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
Address Map
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
  03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4311 802.11b/g 
WLAN (rev 01)
  05:00.0 VGA compatible controller: NVIDIA Corporation G73M [GeForce Go 7600] 
(rev a1)
  07:05.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
  07:05.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host 
Adapter (rev 19)
  07:05.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter 
(rev 0a)
  07:05.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 
05)[/code]

  and my output for arecord -l is:
  [code] List of CAPTURE Hardware Devices 
  card 0: NVidia [HDA NVidia], device 0: 

[Desktop-packages] [Bug 1853374] Re: pulseaudio disables GP107GL output every so often

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: linux (Ubuntu)
   Status: Incomplete => Won't Fix

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

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

Title:
  pulseaudio disables GP107GL output every so often

Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Debian:
  New

Bug description:
  Since upgrading to 19.10, the sound output on this PC stops.

  Looking at the volume control's 'sound settings', the GP107GL High
  Definition Audio Controller (digital stereo HMDI 2 output) is
  disabled.

  Doing

  pluseaudio -k

  restores it.

  Possibly relevant from syslog:

  Nov 18 07:48:51 example kernel: [42392.063211] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 3
  Nov 18 07:51:04 example kernel: [42524.900935] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 2
  Nov 18 08:05:23 example kernel: [43383.465647] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 3
  Nov 18 09:34:08 example kernel: [48708.806452] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 4
  Nov 18 13:32:46 example kernel: [63026.605375] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 3
  Nov 18 13:34:13 example kernel: [63114.281953] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 3
  Nov 18 13:34:40 example kernel: [63141.350110] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 2

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

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

[Desktop-packages] [Bug 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

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

Title:
  CSR8510 based BTA-402 Bluetooth device cannot be started

Status in bluez package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  In the GUI, I can go to the Bluetooth settings and it shows BT to be
  off. I turn on the little switch at the top but nothing else changes.
  If I navigate away from this page and then back, the switch is off
  again.

  If I try to reset the device on the command line I get:

  seb@eragon:~$ sudo hciconfig hci0 reset
  Can't init device hci0: Connection timed out (110)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu5.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: Mon Apr 20 14:39:55 2020
  EcryptfsInUse: Yes
  InterestingModules: bnep btusb bluetooth
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash 
vt.handoff=1 pti=off
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990FXA-UD3
  dmi.board.vendor: AMD Corporation
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:1 errors:1
  rfkill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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

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

[Desktop-packages] [Bug 1861063] Re: Dualshock4 controller doesn't stay connected

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

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

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

Title:
  Dualshock4 controller doesn't stay connected

Status in bluez package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Pairing the Dualshock4 controller works somehow, after several
  attempts. I expected this to work out of the box but it does not work
  well at all.

  Once the pairing is completed, if I try to connect it it doesn't stay
  connected.

  I have checked the dmesg and apparently there is a buffer overflow
  somewhere.

  I can pair a bluetooth headset to my laptop and the Dualshock4 pairs
  with my samsung tablet without problems but when I try to pair the
  dualshock4 to the laptop, running Ubuntu 19.10, it does not work.

  Dmesg output:

  
  [4.099796] Bluetooth: Core ver 2.22
  [4.099833] Bluetooth: HCI device and connection manager initialized
  [4.099837] Bluetooth: HCI socket layer initialized
  [4.099839] Bluetooth: L2CAP socket layer initialized
  [4.099842] Bluetooth: SCO socket layer initialized
  [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018
  [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.855413] Bluetooth: BNEP filters: protocol multicast
  [6.855416] Bluetooth: BNEP socket layer initialized
  [   14.234706] Bluetooth: RFCOMM TTY layer initialized
  [   14.234711] Bluetooth: RFCOMM socket layer initialized
  [   14.234715] Bluetooth: RFCOMM ver 1.11
  [  117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow


  
  Release: 
  Description:  Ubuntu 19.10
  Release:  19.10

  
  Package Info:
  bluez:
Installed: 5.50-0ubuntu4
Candidate: 5.50-0ubuntu4
Version table:
   *** 5.50-0ubuntu4 500
  500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 28 14:11:19 2020
  InstallationDate: Installed on 2019-11-26 (62 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FCS33A00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago)
  dmi.bios.date: 03/13/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET68W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FCS33A00
  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:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FCS33A00
  dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:A7:A0:C6:7F:AE  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:8289 acl:41 sco:0 events:268 errors:0
TX bytes:9494 acl:44 sco:0 commands:163 errors:0
  syslog:

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

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

[Desktop-packages] [Bug 1860930] Re: [Asus GX531GX] Internal speakers are sometimes noisy - distorted audio

[Daniel van Vugt]

** Tags removed: eoan
** Tags added: 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/1860930

Title:
  [Asus GX531GX] Internal speakers are sometimes noisy - distorted audio

Status in PulseAudio:
  Unknown
Status in alsa-driver package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have an Asus Zephyrus S GX531GX laptop and a pair of Asus Delta USB
  headphones. When the headphones are plugged in during boot the
  internal speakers won't work. There is only crackling sound coming
  from them. It doesn't help in I unplug the headphones. There is no
  problem if they are not plugged in during boot. I'm using Ubuntu
  19.10.

  Please let me know if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Jan 26 19:26:35 2020
  InstallationDate: Installed on 2019-12-19 (38 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GX531GXR.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GX531GXR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGX531GXR.304:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnZephyrusSGX531GXR_GX531GXR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX531GXR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: Zephyrus S
  dmi.product.name: Zephyrus S GX531GXR_GX531GXR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

[Daniel van Vugt]

** Tags removed: eoan

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 304393] Re: rpcbind grabs ports used by other daemons such as cupsd

[Timo Aaltonen]

Hello Alvin, or anyone else affected,

Accepted rpcbind into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/rpcbind/0.2.3-0.6ubuntu0.18.04.1 in
a few hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-bionic

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

Title:
  rpcbind grabs ports used by other daemons such as cupsd

Status in cups package in Ubuntu:
  Invalid
Status in rpcbind package in Ubuntu:
  Fix Released
Status in rpcbind source package in Xenial:
  In Progress
Status in rpcbind source package in Bionic:
  Fix Committed
Status in rpcbind package in Debian:
  Fix Released
Status in Fedora:
  Confirmed

Bug description:
  [impact]

  rpcbind binds to a 'random' reserved port at startup, which can
  conflict with the reserved port number for other applications that
  actually 'own' the reserved port number. One example is cups, which
  uses the reserved port 631.

  This prevents the actual 'owner' of the reserved port from starting,
  since it can't bind to its reserved port.

  Additionally, this can raise alarms from security monitoring software
  that does not expect programs to be listening on random reserved
  ports.

  [test case]

  start rpcbind and check which ports it is listening on, e.g.:

  $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc
  udp0  0 0.0.0.0:614 0.0.0.0:* 
  4678/rpcbind

  each time rpcbind is restarted, it will be listening to a different
  'random' port.

  [regression potential]

  this adds a way to disable rpcbind from listening to the 'random'
  port. any regression would likely prevent rpcbind from starting, or
  may cause problems with the interaction between rpcinfo and rpcbind,
  as rpcinfo may use the random reserved port in some cases, as detailed
  in the Debian bug.

  [scope]

  This is needed only for Bionic and earlier.

  In Focal and later, and in Debian, rpcbind defaults to not opening the
  random reserved port.  The admin can use the -r parameter to cause
  rpcbind to restore the old behavior of opening the random reserved
  port.

  [other info]

  Note that the -r parameter is a Debian addition, and the upstream
  rpcbind has disabled the random port functionality at build time;
  there is no runtime parameter to allow the admin to choose the
  behavior.

  Also, as discussed in the Debian bug, disabling this rpcbind 'feature'
  is known to cause problems for the rpcinfo program, which is why
  Debian introduced the -r parameter. So, when this -r parameter is
  backported to Bionic and earlier, we must retain the default behavior
  for those releases, which is for rpcbind to open the random reserved
  port.

  Thus, the patch for this will first backport the upstream patch that adds 
functionality to be able to disable the 'remote calls' function, and also 
backports the debian patch to change that from a compile-time to run-time 
option. Then, another patch is added, which changes the default back to the 
behavior of x/b, which is for remote calls to be enabled by default,
  and also adds a check for the existence of an environment variable 
"RPCBIND_RMTCALL_DEFAULT_DISABLED" which, if defined (to anything), will change 
the default to disabled.

  This allows 1) retaining the existing default behavior of rpcbind in x
  and b, while also 2) providing a mechanism to change that default for
  anyone who does *not* want remote calls to be enabled, and 3) allowing
  the mechanism to change the default to remain in place after an
  upgrade to Focal. Using the environment variable allows anyone to
  disable the remote calls in x and/or b, and then upgrade to Focal
  without breaking rpcbind 

[Desktop-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices

[Daniel van Vugt]

** Tags removed: eoan

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

Title:
  Annoying "call from" message when connecting Bose devices

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each
  time I initially connect to listen to an audio or video, I hear an
  annoying "Call from" on my headset. My headset seems to think a
  connection to a phone call is taking place. This is annoying because
  the audio will start to play and after a little while the "call from"
  voice talks over the audio.

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

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

[Desktop-packages] [Bug 1821427] Re: gnome-shell crashed with SIGTRAP in g_log_writer_default() from g_log_structured_array() from g_log_structured_array() from g_log_structured_standard("The program

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

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

Title:
  gnome-shell crashed with SIGTRAP in g_log_writer_default() from
  g_log_structured_array() from g_log_structured_array() from
  g_log_structured_standard("The program 'gnome-shell' received an X
  Window System error.\nThis probably reflects a bug in the
  program.\nThe error was 'BadWindow (invalid Window parameter)'.\n
  (Details: serial 333851 error_code 3 r");

Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  https://errors.ubuntu.com/problem/e622155ae760525198ab9d778ae25686a5e55978

  Had this happen a few times now, where closing the main evolution
  window (last visible window on desktop) results in a gnome-shell crash
  (see bug 1821262)

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 22 18:49:10 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-09-26 (177 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to disco on 2019-03-11 (11 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1825626] Re: nvLock: client timed out, taking the lock

[Daniel van Vugt]

** Tags removed: eoan

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

Title:
  nvLock: client timed out, taking the lock

Status in gnome-desktop:
  New
Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed

Bug description:
  While launching an app or performing an operation, the screen has a
  certain chance to freeze for a few seconds and then recover.

  [ System Info ]
  Version : Ubuntu 19.04
  Kernel : x86_64 Linux 5.0.0-13-generic
  GPU : NVIDIA GeForce GTX 1050
  Xorg version : 1:7.7+19ubuntu12
  Product Name : Aspire VX5-591G (Acer)

  [ Log File ]
  Uploaded as an attachment

  *Sorry for my not-good English.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 17:19:29 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127]
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1128]
  MachineType: Acer Aspire VX5-591G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Wish_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire VX 15
  dmi.product.name: Aspire VX5-591G
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1831578] Re: gnome-shell crashed with SIGSEGV in stack_do_window_deletions() from stack_ensure_sorted() from get_default_focus_window() from meta_stack_get_default_focus_window

[Daniel van Vugt]

No crashes after 19.10 so consider it fixed.

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: mutter (Ubuntu)
   Status: In Progress => 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/1831578

Title:
  gnome-shell crashed with SIGSEGV in stack_do_window_deletions() from
  stack_ensure_sorted() from get_default_focus_window() from
  meta_stack_get_default_focus_window() from
  focus_ancestor_or_top_window()

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.32.2-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/d1fe1bf113ed5e4e2c08f3369df65b32f13ceee7 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1799103] Re: [radeon] Screen corrupted (skewed stride) after boot

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

Title:
  [radeon] Screen corrupted (skewed stride) after boot

Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  after reboot during upgrade 18.04 to 18.10, screen doesn't show login, see 
pic.
  However, if I mouseover the line, colors/lines change, and if I click middle 
of screen I see the cursor changing from 'arrow' to 'vertical line where you 
can type'. I then type the login password and voilà! I get the cosmic 
cuttlefish desktop and everything works fine :-D

  I have 2 more pics for the blind/hidden login sequence

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 01:57:20 2018
  DistUpgraded: 2018-10-20 12:00:41,261 DEBUG icon theme changed, re-reading
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS690 [Radeon X1200] [1002:791e] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. RS690 [Radeon X1200] [1043:826d]
  InstallationDate: Installed on 2018-10-05 (16 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=ed7ef936-bff3-46c8-887d-205d5a70d4d4 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (1 days ago)
  dmi.bios.date: 06/26/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 0901
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision0901:bd06/26/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Sat Oct 20 22:32:39 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.1-3ubuntu2

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

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

[Desktop-packages] [Bug 1755779] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_writer_default() from g_log_structured_array() from g_log_structured_standard() from _gdk_x11_display

[Daniel van Vugt]

** Tags removed: eoan

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_writer_default() from g_log_structured_array() from
  g_log_structured_standard() from _gdk_x11_display_error_event()
  ["BadPixmap (invalid Pixmap parameter)"] from ...
  meta_pre_paint_func()

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

Bug description:
  https://errors.ubuntu.com/problem/37a88e96048de35d02939c3dd8fe220f716448ee
  https://gitlab.gnome.org/GNOME/mutter/issues/253

  ---

  don't know why, maybe related to printer

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 14 10:02:43 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'thunderbird.desktop', 'libreoffice-calc.desktop', 
'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 
'libreoffice-writer.desktop', 'yelp.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-02-12 (29 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1825625] Re: Some apps appear blurry with framebuffer scaling

[Daniel van Vugt]

** Tags removed: eoan

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

Title:
  Some apps appear blurry with framebuffer scaling

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Microsoft VScode bug: https://github.com/Microsoft/vscode/issues/72759
  Chromium bug?: https://bugs.chromium.org/p/chromium/issues/detail?id=578890

  Setting the framebuffer scaling (with gsettings set org.gnome.mutter
  experimental-features "['scale-monitor-framebuffer']") allows the
  display on HiDPi to be scaled to something different than
  100%/200%/300%.

  Which would be fine.

  However, the display is rendered such that most applications provide
  blurred display of text and graphics.

  This is not always the case (e.g. system settings are displayed
  correctly, Thunderbird and Firefox are blurred).

  Also the screen flickers when selection menus or resizing the windows.
  A black border appears around the windows where the shadow should appear. It 
gets removed a few seconds later but still is irritating.

  This issue is not urgent, just annoying. It can be worked around by
  removing the settings in gsetting / dconf.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mutter 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 11:11:55 2019
  InstallationDate: Installed on 2018-04-30 (355 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)

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

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

[Desktop-packages] [Bug 1833558] Re: gnome-shell crashed with SIGSEGV in meta_monitor_manager_get_monitor_for_connector() from

[Daniel van Vugt]

** Tags removed: eoan

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

Title:
  gnome-shell crashed with SIGSEGV in
  meta_monitor_manager_get_monitor_for_connector() from 

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

Bug description:
  https://errors.ubuntu.com/problem/6651d911f833729ccc39cf01ed5e393b95cb0c3f

  gnome shell crashes when I go to Settings -> Devices -> Displays

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 19 11:01:41 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-04-29 (1146 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f49b8116bf0 
:mov0x18(%rax),%eax
   PC (0x7f49b8116bf0) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_manager_get_monitor_for_connector () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in 
meta_monitor_manager_get_monitor_for_connector()
  UpgradeStatus: Upgraded to bionic on 2018-08-04 (319 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin plugdev 
sambashare sudo

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

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

[Desktop-packages] [Bug 1752680] Re: Night light does not work after resume from suspend or unlock.

[Daniel van Vugt]

** Tags removed: eoan

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

Title:
  Night light does not work after resume from suspend or unlock.

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  The night light feature does not work in these cases
   * Computer's screen shuts off due to timeout, and then is reactivated.
   * Computer is brought back from suspend
   * Computer desktop is locked, and unlocked using the password

  In all these cases, the night light icon is present in the
  notification area, and it says "Night Light On". But the screen
  temperature is that of normal daylight.

  In all these cases, disabling and re-enabling the night light using
  the notification area icon reactivates the night light.

  Version information

  Gnome desktop on Ubuntu 4.13.0-36.40-generic 4.13.13

  4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64
  x86_64 x86_64 GNU/Linux

  17.10 Artful Aardvark

  Hardware : MSI GP62 QE - with i5-6300HQ, using the Intel graphics driver.
  ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/pcmC0D0p: talonx 2732 F...m pulseaudio
   /dev/snd/controlC0: talonx 2732 F pulseaudio
  CurrentDesktop: GNOME-Classic:GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7808c7a8-dd4d-41e7-a2f2-032701229a6a
  InstallationDate: Installed on 2016-05-05 (659 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Micro-Star International Co., Ltd. GP62 6QE
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=70280d26-8667-4d1b-9bbd-683373c14707 ro priority=low quiet splash 
acpi_osi= i8042.nomux=1 i8042.reset i8042.nopnp i8042.noloop 
usbcore.autosuspend=-1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic N/A
   linux-firmware 1.169.3
  Tags: artful
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-02 (114 days ago)
  UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J5IMS.113
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J5IMS.113:bd04/25/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP626QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J5:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.name: GP62 6QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Desktop-packages] [Bug 1804568] Re: [HP Spectre x360 Convertible 13] click position is flipped to cursor position when in tent mode

[Daniel van Vugt]

** Tags removed: eoan

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

Title:
  [HP Spectre x360 Convertible 13] click position is flipped to cursor
  position when in tent mode

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

Bug description:
  Hello,

  same bug is present 18.04 and 18.10:

  after I log in in tent mode the screen goes upside down, and after

  xrandr --output eDP-1 --rotate normal

  it goes back to normal however now the cursor is upside down, and
  click position and cursor position isnt the same, they are flipped

  thank you for the fix in advance

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: coreutils 8.28-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 04:28:21 2018
  ExecutablePath: /bin/sleep
  InstallationDate: Installed on 2018-11-22 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   LANG=hu_HU.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imi1950 F pulseaudio
   /dev/snd/controlC1:  imi1950 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-03-30 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190329)
  MachineType: HP HP Spectre x360 Convertible 13-w0XX
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.31
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827E
  dmi.board.vendor: HP
  dmi.board.version: 94.60
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.31:bd04/27/2017:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.60:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible 13-w0XX
  dmi.product.sku: Z9E46EA#ABV
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imi1333 F pulseaudio
   /dev/snd/controlC1:  imi1333 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-23 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190917)
  MachineType: HP HP Spectre x360 Convertible 13-w0XX
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-10-generic N/A
   linux-backports-modules-5.3.0-10-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.49
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827E
  dmi.board.vendor: HP
  dmi.board.version: 94.71
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.49:bd05/03/2019:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.71:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible 13-w0XX
  dmi.product.sku: Z9E46EA#ABV
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  

[Desktop-packages] [Bug 1800749] Re: Ubuntu doesn't like fullscreen mode for sauerbraten(game)

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

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

Title:
  Ubuntu doesn't like fullscreen mode for sauerbraten(game)

Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  When I run sauerbraten in fullscreen mode in Ubuntu 18.10, there are
  "skips" in the animation of the rotating cubes.  Upon further
  "evaluation", I noticed the system mouse pointer "popping up" briefly
  at the moment of the glitch(near the crosshair) about once a second.
  When not in fullscreen, the animation is smooth(no visible
  skips/glitches) and I don't see the system mouse pointer "popping up"
  every second.  It works fine in fullscreen mode in Ubuntu 18.04.

  To recreate/observe the problem:
  0. Boot into Ubuntu 18.10
  1. Install sauerbraten
  2. Start sauerbraten
  3. Set sauerbraten to fullscreen 
mode(sauerbraten->options..->display->fullscreen)
  4. Start a game(I like sauerbraten->bot match->start match->ctf->europium)
  5. Move forward with the 'w' key(steer with the mouse) to some rotating 
cubes.  Here you should notice the glitch in rotation and the _system_ mouse 
pointer flickering in and out near the crosshair at a rate of about once a 
second.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.399
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 30 21:46:28 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:2102]
  LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
  MachineType: ASUSTeK COMPUTER INC. K55A
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz boot=casper 
iso-scan/filename=/Downloads/username-18.10-desktop-amd64.iso ipv6.disable=1 
net.ifnames=0 quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K55A.407
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK55A.407:bd12/25/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K55A
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1844575] Re: Pixelated fonts sometimes

[Daniel van Vugt]

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

** Tags added: fixed-in-3.36.1

** No longer affects: 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/1844575

Title:
  Pixelated fonts sometimes

Status in GNOME Shell:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Running under wayland, with fractional scaling enabled and set to 175%
  on laptop screen, 100% on external screen, sometimes windows like
  nautilus or the file chooser get pixelated fonts (see screenshot).
  Seen this mostly on the 100% external screen, and it goes away if
  maximizing the window or moving the window back and forth between
  screens a few times.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep 18 12:59:50 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-17 (32 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-18 (0 days ago)

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

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

[Desktop-packages] [Bug 1842009] Re: [Wayland] Screen blanks for a second whenever discrete GPU is powered up

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Won't Fix

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

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

Title:
  [Wayland] Screen blanks for a second whenever discrete GPU is powered
  up

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  On this Kaby Lake G laptop, GNOME Shell blanks the screen for a second
  each time the AMD GPU is powered up. Triggers for powering up include:
  launching something which loads GL such as Steam or glxinfo, loading
  the Display configuration page, and so on.

  This behaviour does *not* occur with GNOME Shell under X, so it's
  probably something to do with mutter's KMS interactions.

  Because the GPU powers down quite aggressively (I think it's about
  5sec without activity) this can be quite annoying :)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.33.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic 
5.1.2
  Uname: Linux 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 30 09:48:25 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-29 (0 days ago)
  InstallationMedia: Ubuntu 19.10 bcachefs (20190828)
  RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1848086] Re: Keyboard shortcuts to launch apps sometimes launch twice in Wayland sessions

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

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

Title:
  Keyboard shortcuts to launch apps sometimes launch twice in Wayland
  sessions

Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  Noticed that recently (past few days? since 3.34.1?) the key
  combinations that I have set to launch web browser or launch terminal
  end up launching two browsers or terminals instead of just one.  Only
  happens ~50% of the time, but still pretty frequently.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: mutter 3.34.1-1ubuntu1
  Uname: Linux 5.3.0-custom x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 14 12:56:44 2019
  InstallationDate: Installed on 2019-08-17 (58 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to eoan on 2019-09-18 (26 days ago)

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

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

[Desktop-packages] [Bug 1846201] Re: Rendering is delayed on laptop display (works in external display)

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: mesa (Ubuntu)
   Status: New => Won't Fix

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

** Changed in: xorg-server (Ubuntu)
   Status: New => Won't Fix

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

Title:
   Rendering is delayed on laptop display (works in external display)

Status in mesa package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix
Status in xorg-server package in Ubuntu:
  Won't Fix

Bug description:
  This is a very wierd behavior I get on the Lenovo Yoga S940 after upgrading 
to 19.10.
  This makes the laptop almost unusable with its own display.
  This happens only on the laptop display, not on the external display.

  
  The render of portions of the screen does not happen after some events 
(listed below) resulting in all or part of the screen not being re-rendered. 
The UX is that nothing happened, but it has. 
  This happens after:

  * key-stroke while typing sometimes
  * alt-tab
  * shift-right to align window to the right
  * ctrl-pgup/down to switch tab in multi tabs apps. 

  
  Please note that:
  * screenshots can't see the problem
  * also screenrecorder always seem ok, despite rendering being broken.


  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 13:13:40 2019
  DistUpgraded: 2019-09-21 10:16:26,647 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3801]
  InstallationDate: Installed on 2019-09-12 (18 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (10 days ago)
  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
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-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/mesa/+bug/1846201/+subscriptions

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

[Desktop-packages] [Bug 1843952] Re: Diagonal stride artifacts appear when I un-maximize Chromium or Firefox windows [Intel N3350]

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

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

Title:
  Diagonal stride artifacts appear when I un-maximize Chromium or
  Firefox windows [Intel N3350]

Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  It's GNOME on Wayland bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: mutter 3.34.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 00:13:57 2019
  InstallationDate: Installed on 2019-09-09 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1849135] Re: Clicking Activities in the corner doesn't work

[Daniel van Vugt]

** Tags removed: eoan

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

Title:
  Clicking Activities in the corner doesn't work

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in mutter source package in Eoan:
  Won't Fix

Bug description:
  [ Impact ]

  Starting from Ubuntu 19.10, the top-left corner of the screen is
  unclickable. It's where the Activities button is. It is unresponsive
  to clicks to open the overlay, BUT it responds to clicks to close it.

  The unclickable spot is exactly one pixel large.

  Edit: At first it seemed to be reproducible only on Xorg sessions, but
  after using it for a while on Wayland, I am having the issue again.

  Specs:
  - Graphics: AMD RX 560
  - CPU: Intel Core i3-8100
  - Ubuntu 19.10 Eoan

  [ Test case ]

  - Move the mouse to the top-left corner pixel and click on it
  - Activities should open

  [ Regression potential ]

  Mouse picking location could be wrong in all clutter operations

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

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

[Desktop-packages] [Bug 1838919] Re: Slow and lost keyboard and mouse events

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Won't Fix

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

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

Title:
  Slow and lost keyboard and mouse events

Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  This was a fresh amd64 installation with 18.10 desktop, upgraded to
  19.04 as soon as available. It has been getting worse over the last
  few weeks and is now so bad I can hardly type an email (or this bug
  report!) without having to fix many typos.

  journalctl shows many different gnome errors, so it is difficult to
  figure out which is the underlying cause and which are simply
  collateral damage.

  There are two sequences that appear first after a reboot, and the
  first of these has been reported many times on ubuntu releases going
  back for years:-

  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ module 
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be 
loaded.
  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ 2.x symbols 
detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # Failed to load module 
"canberra-gtk-module"

    and 

  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.89/org/ayatana/NotificationItem/software_update_available
  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
  Aug 05 09:12:19 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091219.948098:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
  Aug 05 09:12:21 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091221.376983:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
  Aug 05 09:12:22 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091222.542169:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <-

  Is this a recent regression? I know for sure the system wasn't this
  unresponsive 3 weeks ago, but I cannot be sure when it started to go
  wrong. My mouse/keyboard combo has a USB-wireless dongle and I've
  fiddled around with distance and battery state until I was sure the
  problem was somewhere else and started to check the system log.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-software 3.30.6-2ubuntu4.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: 

[Desktop-packages] [Bug 1844809] Re: clicking desktop notifications to bring up linked up works intermittently in 19.10?

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

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

Title:
  clicking desktop notifications to bring up linked up works
  intermittently in 19.10?

Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  This is not going to be the highest quality bug report :-(, since it's
  an intermittent issue and I don't know exactly what triggers it and I
  can't even say with 100% certainty that it's new in 19.10, but I
  _think_ it is so I wanted to give people a heads-up just in case.

  I just upgrade to 19.10 from 19.04. I use the Google Hangouts Chrome
  app. When I get a text message in Hangouts it pops up a desktop
  notification. Usually clicking on the notification causes the Hangouts
  window to open. When I clicked on the notification nothing happened.
  Then I got a second notification later and clicked on that one and the
  window opened as it should have. Then I got a third notification later
  and clicked on that one and again the window didn't open.

  I _believe_, though I can't say for certain, that this worked
  consistently in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 20 11:20:19 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (0 days ago)

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

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

[Desktop-packages] [Bug 1849415] Re: Desktop zoom makes app windows unresponsive to the mouse in Wayland sessions

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => Won't Fix

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

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

Title:
  Desktop zoom makes app windows unresponsive to the mouse in Wayland
  sessions

Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix
Status in mutter package in Fedora:
  Unknown

Bug description:
  I tried to use the gnome magnifier after updating to 19.10 today.
  After enabling zoom from the control panel, I could no longer send
  mouse input anywhere other than the desktop.  This made it impossible
  to turn zoom off using the mouse and it doesn't seem to be possible to
  turn off using keyboard navigation either.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 23 00:20:13 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-18 (127 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (0 days ago)

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

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

[Desktop-packages] [Bug 1835521] Re: [regression] Windows flicker to black when resizing (Intel Apollo Lake)

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

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

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

Title:
  [regression] Windows flicker to black when resizing (Intel Apollo
  Lake)

Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mesa package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  I see the black zones, small windows breaks. For additional details, I use 
eoan-proposed and eoan-backports packages.
  You can see this problem in my video: 
https://photos.app.goo.gl/3rvLkqJj6hZwSscw9

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul  5 13:39:13 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (3 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1821415] Re: pkexec fails in a non-graphical environment

[Timo Aaltonen]

sru upload for bionic: needs sru template, and the bug doesn't seem
fixed in newer releases?

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  New
Status in apport package in Ubuntu:
  Triaged
Status in policykit-1 package in Ubuntu:
  Triaged

Bug description:
  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not
  in a non-graphical one.

  N.B. you first need to create a /var/log/plymouth-debug.log file for
  the plymouth apport package hook to actually trigger this.

  ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  Subsequently, bug reports from servers will contain less information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1821415/+subscriptions

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

[Desktop-packages] [Bug 1850874] Re: gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen (on Wayland only)

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Won't Fix

** Changed in: mesa (Ubuntu)
   Status: New => Won't Fix

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

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

Title:
  gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU
  cores just to update the screen (on Wayland only)

Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mesa package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  This started to happen with Ubuntu 19.10.

  When an animated gif is displayed in a browser, gnome-shell begins
  using 100% CPU on all cores.

  To reproduce:

  1) open Firefox, or Chromium

  2) load an URL where an animated gif is displayed - you can also use
  this direct link to https://i.stack.imgur.com/h6viz.gif

  3) gnome-shell will start using 100% CPU on all cores (as long as 
Firefox/Chromium window is in the foreground)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-05-12 (172 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (15 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend

[Daniel van Vugt]

** Tags removed: eoan

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

Title:
  [nvidia] Background image corrupted after standby or resume from
  suspend

Status in mutter package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix

Bug description:
  Looks similar to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407

  When the computer goes to standby, the background image becomes
  corrupted.

  I am able to fix by "killall Xorg" , change the background image
  (settings > background) and restart.  Haven't tried login logout.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: 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.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  9 10:58:35 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed
   nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c]
  InstallationDate: Installed on 2019-11-29 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTek Computer Inc. G60JX
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G60JX
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.family: PEGA Family
  dmi.product.name: G60JX
  dmi.product.sku: 0
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTek Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.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/mutter/+bug/1855757/+subscriptions

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

[Desktop-packages] [Bug 1852023] Re: Wayland doesn't work in GMA500

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

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

Title:
  Wayland doesn't work in GMA500

Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  I had to disable Wayland in GDM3 in order to be able to login.
  I guess an udev rule to disable Wayland for GMA500 is all that is needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 10 19:14:19 2019
  DistUpgraded: 2019-11-10 16:17:45,811 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso 
hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller 
[8086:0be1] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Atom Processor D2xxx/N2xxx 
Integrated Graphics Controller [1179:fc10]
  InstallationDate: Installed on 2012-07-29 (2660 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: TOSHIBA TOSHIBA NB515
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=5febd6a0-8053-4b1c-92f5-df934f0ea50b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to eoan on 2019-11-10 (0 days ago)
  dmi.bios.date: 4/3/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.30
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.30:bd4/3/2012:svnTOSHIBA:pnTOSHIBANB515:pvrPLL72P-013LM1:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Dolphin10
  dmi.product.name: TOSHIBA NB515
  dmi.product.sku: PLL72P-013LM1
  dmi.product.version: PLL72P-013LM1
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.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
  xserver.bootTime: Mon Jul  1 17:43:10 2019
  xserver.configfile: default
  xserver.errors:
   modeset(0): glamor initialization failed
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1859955] Re: Long delays and repeated flashing when docking laptop with multiple monitors

[Daniel van Vugt]

** Tags removed: eoan

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

Title:
  Long delays and repeated flashing when docking laptop with multiple
  monitors

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

Bug description:
  Running Focal on my ThinkPad T450, but not unique to this release as
  it happened on 19.10 (and probably older releases too).

  Steps to reproduce.

  While running GNOME Shell, attach the laptop to additional external monitors.
  (I'm using a docking station, but equally you can attach them via the video 
ports on the laptop itself)

  Expected outcome

  Desktop on 1 monitor goes away.
  Desktop comes back on N monitors.

  Actual outcome

  Laptop display goes black
  Laptop display comes back, moved 50% horizontally
  One external monitor comes on
  Laptop display goes back to normal
  Second external monitor comes on
  All three displays go off again
  Laptop display comes on again alone
  Laptop display goes off again
  laptop display comes on again
  External monitors come back on again
  System is usable.

  The entire process takes twenty seconds.

  https://www.youtube.com/watch?v=QuSudpxVOao

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 10:21:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-04 (710 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago)

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

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

[Desktop-packages] [Bug 1868614] Re: Login starts at native resolution before visibly switching to the configured resolution

[Daniel van Vugt]

** Tags removed: eoan

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

Title:
  Login starts at native resolution before visibly switching to the
  configured resolution

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

Bug description:
  This happens on Ubuntu 19.10 and still happening on Ubuntu 20.04

  Let me give a little background

  My laptop (Razer Stealth) has a built in display with default 3840 by 2160.
  I currently have it set up to 1920 by 1080, as it drains the battery faster 
using the higher resolution.

  At login, the resolution show at 1920 by 1080, but after entering the
  password, the screen changes the resolution back to the default (3840
  by 2160), but once the desktop of the user loads it changes back to
  1920 by 1080.

  The change of resolution can be noticeable because the size of the mouse 
pointer becomes much smaller when logging in.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2020-03-17 08:21:46,611 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.4, 5.3.0-42-generic, x86_64: installed
   virtualbox, 6.1.4, 5.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. Skylake GT2 [HD Graphics 520] [1a58:674d]
  InstallationDate: Installed on 2019-09-28 (178 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  MachineType: Razer Blade Stealth
  Package: xorg 1:7.7+19ubuntu14
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=3eed045c-673f-4583-9b55-d04adb18adc3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Tags:  wayland-session focal ubuntu reproducible
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-03-17 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: ABCDEF
  dmi.board.name: SKYBAY
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: ABCDEF
  dmi.chassis.type: 9
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/30/2015:svnRazer:pnBladeStealth:pvr1.04:rvnINTELCorporation:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct9:cvrDefaultstring:
  dmi.product.name: Blade Stealth
  dmi.product.sku: RZ09-01682E24
  dmi.product.version: 1.04
  dmi.sys.vendor: Razer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1860204] Re: [nvidia] GNOME3 notification background layer paints over notification text if mouse is moved in notification area

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-shell (Ubuntu)
   Status: New => Won't Fix

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

** Changed in: nvidia-graphics-drivers-435 (Ubuntu)
   Status: New => Won't Fix

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

Title:
  [nvidia] GNOME3 notification background layer paints over notification
  text if  mouse is moved in notification area

Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I do not know if it is a problem of the current proprietary driver or
  xorg or GNOME. I tried my best to include all the info you might need.

  Problem:

  When I receive a notification in the notification centre of GNOME, it
  shows up in the notification bubble. If the text in the notification
  bubble is longer than the amount of text can be shown at once, the it
  needs to be opened. If I click on the bubble, it opens, but if I move
  my mouse pointer inside the said notification the light greyish
  background color of the notification area paints over the text
  rendering it to be unreadable. If I wait some seconds then this
  'layer' disappears partly or completely.

  Since my VGA works fine under heavy load (GPU intensive applications
  and games) I guess it is a software related bug

  ---

  Release:  19.10
  xorg:
Installed: 1:7.7+19ubuntu12
Candidate: 1:7.7+19ubuntu12

  NVIDIA Driver Version: 435.21 
  VGA: GTX 960 4GB

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:07:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 18 11:21:51 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-18-generic, x86_64: installed
   nvidia, 435.21, 5.3.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GM206 [GeForce GTX 960] [1458:36c2]
  InstallationDate: Installed on 2020-01-17 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 

[Desktop-packages] [Bug 1856553] Re: libinput error: client bug: timer event3 debounce short: offset negative (-0ms) (#2041)

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

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

Title:
  libinput error: client bug: timer event3 debounce short: offset
  negative (-0ms) (#2041)

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  1) Ubuntu 19.10
  2) mutter 3.34.1
  3) No error.
  4) Error in log app.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: mutter 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 16 05:36:05 2019
  InstallationDate: Installed on 2019-10-28 (49 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1890632] Re: Can't open preferences

[Sebastien Bacher]

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

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

Title:
  Can't open preferences

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  I can't seem to access the rhymbox preferences.
  'Preferences' does not appear in the application menu (see attachment) since 
ubuntu 17.10.
  I was still able to edit the preferences from the menu under the song slider, 
but I have now accidentally removed the whole top bar (with the current song, 
the previous, next, pause buttons, and that menu button).

  So now I can't open the preferences, nor see the current song anymore,
  or have it display again.

  Note that the option in the view menu might have been from the
  Alternative-Toolbar plugin

  A temporary fix to get the view menu again would be appreciated too.

  $ lsb_release -rd
  Description: Ubuntu 20.04.1 LTS
  Release: 20.04

  $ apt-cache policy rhythmbox
  rhythmbox:
Installed: 3.4.4-1ubuntu2
Candidate: 3.4.4-1ubuntu2
Version table:
   *** 3.4.4-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Mirror of the attachment (screenshot of the application menu):
  https://i.imgur.com/CJUVoRZ.png

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

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

[Desktop-packages] [Bug 1851715] Re: Screen brightness adjustment delay in Xorg sessions only

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

** Changed in: xorg-server (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Screen brightness adjustment delay in Xorg sessions only

Status in mutter package in Ubuntu:
  Won't Fix
Status in xorg-server package in Ubuntu:
  Won't Fix

Bug description:
  Every time I adjust my laptop's screen brightness using the dedicated
  brightness keys, there is a substantial delay between when I press the
  button and the screen adjusts. Sometimes it even "twitches" and
  decreasing the brightness by tapping the button two times will quickly
  drop the brightness all the way to the lowest setting after the delay
  takes place. I've noticed the issue in the default Ubuntu session and
  in my current vanilla gnome-session. It also doesn't matter which
  extensions I have installed. The keys work flawlessly in Windows so it
  isn't a hardware issue. I have been meaning to report this for a while
  and have just never gotten around to it until just now.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu Nov  7 14:37:43 2019
  DistUpgraded: 2019-10-21 20:16:37,104 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-19-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04]
 Subsystem: Huawei Technologies Co., Ltd. GP108M [GeForce MX150] [19e5:3e04]
  InstallationDate: Installed on 2019-09-08 (59 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HD Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HUAWEI MACH-WX9
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=75fe2138-1abd-47b2-a73f-83280ff782ff ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-10-22 (16 days ago)
  dmi.bios.date: 03/15/2019
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.28
  dmi.board.name: MACH-WX9-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M14
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M14
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:svnHUAWEI:pnMACH-WX9:pvrM14:rvnHUAWEI:rnMACH-WX9-PCB:rvrM14:cvnHUAWEI:ct10:cvrM14:
  dmi.product.family: MateBook X
  dmi.product.name: MACH-WX9
  dmi.product.sku: C128
  dmi.product.version: M14
  dmi.sys.vendor: HUAWEI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  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/mutter/+bug/1851715/+subscriptions

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

[Desktop-packages] [Bug 1863472] Re: Switching keyboard layout with Ctrl+Shift in Ubuntu 19.10

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-shell (Ubuntu)
   Status: New => Won't Fix

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

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

Title:
  Switching keyboard layout with Ctrl+Shift in Ubuntu 19.10

Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  During using Ubuntu 18.04 i set switching keyboard layout combination to 
Ctrl+Shift by tweak-tool.
  The combination worked great - with Shift-Ctrl and Ctrl-Shift both, no matter 
in which order keys were being pressed.
  But after upgrade to 19.10 and setting the same combination through the same 
tweak-tool it seems like only Ctrl-Shift is working and Shift-Ctrl is not 
anymore. 

  Ubuntu release: 19.10
  gnome-tweak-tool: 3.34.0-2

  Steps to reproduce:
  - Launch "Tweaks" tool
  - Choose Keyboard & Mouse
  - Press Additional Layout Options
  - Choose "Switching to another layout"
  - Pick "Ctrl+Shift" by setting the checkbox active

  What was expected:
  Shift-Ctrl combination doing the same as Ctrl-Shift

  What happened instead:
  Ctrl-Shift is working and Shift-Ctrl is not

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

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

[Desktop-packages] [Bug 1851568] Re: monitor configuration restored incorrectly upon Wayland login

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

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

Title:
  monitor configuration restored incorrectly upon Wayland login

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  I have an ultrawide monitor plugged into my laptop. When I log into a
  Wayland session, my monitor configuration (resolution, relative
  position, which monitor is the primary) is not restored correctly.
  When I unplug the monitor cable after logging in and plug it in again,
  the correct configuration is restored.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  6 15:45:21 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (55 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596

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

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

[Desktop-packages] [Bug 1890716] Re: xdg-mime query filetype index.html reports wrong type

[Sebastien Bacher]

Thank you for your bug report, the file types are determined from the
content and not only the name. An html is supposed to start with 

** Package changed: xdg-utils (Ubuntu) => shared-mime-info (Ubuntu)

** Changed in: shared-mime-info (Ubuntu)
   Importance: Undecided => Low

** Changed in: shared-mime-info (Ubuntu)
   Status: New => Invalid

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

Title:
  xdg-mime query filetype index.html reports wrong type

Status in shared-mime-info package in Ubuntu:
  Invalid

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+subscriptions

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