[Desktop-packages] [Bug 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output

[Timo Aaltonen]

Hello Yuan-Chen, or anyone else affected,

Accepted pulseaudio into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.10 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.

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

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

Title:
  [SRU] plug headset won't proper reconfig ouput to it on machine with
  default output

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux-oem package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed

Bug description:
  This is for pulseaudio bionic:

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, the active profile is Off, after users plug a
  headset to it and users select the headset from the pop-up dialogue,
  users expect the profile changes to analog-stereo (headset is on it),
  but the active_profile is still Off.

  [Fix]
  Upstream already has a patch to fix it, cherrypiack that patch to bionic.
  And that patch is already in the eoan, focal, ...

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and select the headset from UI, the profile changes to
  analog-stereo, and play some sound, we could hear it from the headset

  [Regression Risk]
  Low, this patch is already in the upstream for a long time, and it is
  already in the eoan and focal.


  
  For linux kernel (oem-b):

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, and users plug a headset, the sound couldn't
  output from headset.

  [Fix]
  reverse the order of headset mic and headphone mic

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and play sound, we could hear the sound from headset.

  [Regression Risk]
  Low, this patch only affects the machine without internal mic and
  internal spk, and I already tested this patch on the machine without
  internal mic and internal spk, it worked well.

  target machine does not have built-in speaker, and the monitor does
  not have an audio output (like d-sub VGA)

  As first boot, there will be a "dummy output" in g-c-c.

  After plug-in headset, there will be a headset appear in g-c-c, but it
  won't be automatically selected even it's chosen in the pop-up window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions

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

[Desktop-packages] [Bug 1887718] Re: Screen freeze

[Paramjeet Dhiman]

After updating my ubuntu last week my computer gets freeze after some
time and then showing this below error continuously...

EXT-fs error (device nvme0n1p6): __extf4_find_entry:1531 inode #6439215: comm 
main: reading
directory Iblock 0

https://errors.ubuntu.com/user/b6b2debb011c22cafae7187e930b22521e8059ec374323d39925592b77bd81b172a3da5cf5bd01d468258bfef39d1f6f13575df0bf6711b73d0990e20683bd48

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889008

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

Title:
  Screen freeze

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Freezes randomly without any traceable pattern. Windows become unresponsive 
while the cursor works. 
  To unfreeze I have to press the OFF button of my HP ProBook and then click on 
"Cancel" in the shutdown dialogue. That unfreezes the windows. May happen 
several times per session, may not happen at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 15 22:32:43 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:822c]
  InstallationDate: Installed on 2020-06-19 (26 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint 
Reader
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 05c8:03a0 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProBook 430 G4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=36191f51-931b-47be-bfdb-1553e0425aad ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2016
  dmi.bios.vendor: HP
  dmi.bios.version: P85 Ver. 01.03
  dmi.board.name: 822C
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 42.61
  dmi.chassis.asset.tag: 5CD7065D4K
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP85Ver.01.03:bd12/05/2016:svnHP:pnHPProBook430G4:pvr:rvnHP:rn822C:rvrKBCVersion42.61:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G4
  dmi.product.sku: Y7Z51EA#ACB
  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 20.0.8-0ubuntu1~20.04.1
  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/gnome-shell/+bug/1887718/+subscriptions

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

[Desktop-packages] [Bug 1888088] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  [amdgpu] [AMD Renoir] Display won't rotate, nor do fractional scaling,
  but amdgpu.exp_hw_support=1 fixes it

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Opening Settings -> Display and selecting an orientation other than
  Landscape doesn't work.  Similarly, selecting Fractional Scaling and
  then picking a scale factor has no effect.

  This is a recently installed Ubuntu 20.04, fully updated, on a
  recently released laptop/tablet that uses an AMD Ryzen 4500U
  integrated CPU/GPU.  It is possible that the GPU is not being detected
  by Ubuntu and that is the root cause of the problem.  I couldn't find
  an easy explanation online about how to tell whether a GPU was
  detected or is in use.  I did try running "tlp-stat -g" to get
  graphics status, but it returns without printing anything except its
  version number (1.3.1).

  When I choose an orientation, such as Portrait Right, the setting
  changes and an "Apply" button appears in the top of the Settings
  window.  When I press it, up pops up a dialog asking whether I want to
  "Keep these display settings?" with two options, keep or revert.  The
  rest of the screen goes grey behind the dialog box, but I can already
  see behind the popup that the screen did not change its orientation,
  and the "Orientation" setting back in the Settings->Display window has
  been reverted to "Landscape" without me doing it.  Whether I choose
  keep or revert, or merely let it time out after 20 seconds, the result
  remains the same -- the display stays in Landscape mode and the
  setting that I had made is reverted.

  Regarding scaling, I can set the display scale to 100% (default) or
  200%, successfully.  But when I turn on the "Fractional Scaling"
  slider, the graphics around the edge of the screen immediately
  increase in size (the icons in the left-hand dock, the text in the top
  bar), even though I have not changed the scale setting.  I have
  included two screenshots (original screen, and with Fractional Scaling
  on).  There is also some strangeness about whether sliding the
  Fractional Scaling slider updates the Scale menu to allow more scales
  - sometimes it does, sometimes it doesn't.

  When I attempt to set a fractional scale such as 125%, the "Apply"
  button appears in the upper right corner.  When I press that, the
  display does not actually scale, and a pop-up asks if I want to keep
  or revert the setting.  But looking back at the Displays settings, the
  Scale has already reverted to 100% (as above with the Orientation).
  Screenshot enclosed.

  The display has been rock-solid before this, but now it started
  showing artifacts, such as previous copies of the Displays window.
  I've enclosed a screen shot, which shows checkerboard in the screen
  locations that (in reality) were displaying prior versions of the
  window.  Hmm, examining that screenshot, it looks like the display DID
  start occupying 25% more space horizontally and vertically, but
  something about the video scanning versus the screen updating got out
  of whack.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog:

  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sat Jul 18 14:00:38 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Renoir [17aa:3f1a]
  InstallationDate: Installed on 2020-07-16 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81X2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EECN20WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Flex 5 14ARE05
  dmi.modalias: 

[Desktop-packages] [Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)

[Daniel van Vugt]

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

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

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

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

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

** No longer affects: xserver-xorg-video-nouveau (Ubuntu)

** Summary changed:

- Unusable graphics, nouveau + G73 (GEForce 7600)
+ [nouveau] Unusable graphics (screen is broken into triangles) with G73 
(GEForce 7600, 6600)

** Summary changed:

- [nouveau] Unusable graphics (screen is broken into triangles) with G73 
(GEForce 7600, 6600)
+ [nouveau] Unusable graphics (screen is broken into triangles) with GEForce 
7600, 6600

** Summary changed:

- [nouveau] Unusable graphics (screen is broken into triangles) with GEForce 
7600, 6600
+ [nouveau] Unusable graphics (screen is broken into triangles) with GeForce 
7600, 6600

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

Title:
  [nouveau] Unusable graphics (screen is broken into triangles) with
  GeForce 7600, 6600

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  This is an older card, but it worked well on ubuntu 12.x :)

  Booting "Try Ubuntu" on 20.04 get the correct resolution and 2
  displays, but the video glitches and shows all sorts of noise.  It is
  largely unusable (which makes filing this bug very hard).

  Safe Graphics works in low-res.

  The nvidia proprietary driver seems to not support this device any
  more.  I like this card because it has no fan (and I don't do a lot of
  graphics-intense stuff).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 18:13:48 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd G73 [GeForce 7600 GT] [1458:3417]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd  
---  priority=low
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: X58 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd12/30/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1880991] Re: [nvidia] Xorg freeze

[Launchpad Bug Tracker]

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

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

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

Title:
  [nvidia] Xorg freeze

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Sometimes there is an X11 freeze. Usually it happens when I connect to
  a Zoom conference, but latest (and at least one previous) it happened
  when I wasn't using Zoom. The symptoms were same: still image, but
  mouse cursor could be moved. I can switch to another terminal
  (ctrl+alt+f1), when I return to the GUI, there is only black screen
  with moving mouse cursor.

  I can only restart lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: 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  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed May 27 19:49:30 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.108, 5.4.0-29-generic, x86_64: installed
   nvidia-340, 340.108, 5.4.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: Gigabyte Technology Co., Ltd GT218 [GeForce 210] [1458:3525]
  InstallationDate: Installed on 2020-05-09 (17 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic 
root=/dev/mapper/vgxubuntu-root ro iommu=soft quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FC
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrTobefilledbyO.E.M.: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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1880991/+subscriptions

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

[Desktop-packages] [Bug 1881190] Re: dock missing

[Launchpad Bug Tracker]

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

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

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

Title:
  dock missing

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  The dock missed after a reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 28 20:44:15 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-18 (496 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1888520] Re: gnome-shell crashed with SIGABRT in g_assertion_message_expr()

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1889090
   GNOME Shell doesn't start Ubuntu session with 3.36.4 as per assertion in 
meta_monitor_manager_xrandr_update_screen_size

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

Title:
  gnome-shell crashed with SIGABRT in g_assertion_message_expr()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Doing nothing, just firefox is open but i was not using the computer,
  found the problem returning from the shower.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.36.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu42
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 22 15:30:22 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-05-11 (72 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200511)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.4-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0
   meta_monitor_manager_rebuild_derived () from 
/lib/x86_64-linux-gnu/libmutter-6.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0
  Title: gnome-shell crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1888800] Re: Resolution of external monitor goes back to its default resolution when laptop lid is closed

[Daniel van Vugt]

This bug is now closed as Invalid since it does seem to be the issue
described in comments #2 and #3. So not a bug, but an interesting point
of confusion that other users might encounter. To "fix" it though would
be an enhancement request. If you like then we can turn this into an
enhancement request...

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

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

Title:
  Resolution of external monitor goes back to its default resolution
  when laptop lid is closed

Status in mutter package in Ubuntu:
  Invalid

Bug description:
  The default resolution of my external monitor is 4K UHD (3840 ⨉ 2160).
  I set its resolution to a lower value (2560 ⨉ 1440). The external
  monitor is attached to a laptop. When I close the laptop lid, the
  built-in display is turned off, which is desired, however, the
  external monitor goes back to its default resolution (3840 ⨉ 2160),
  which is not desired. When I open back the lid, the built-in display
  is turned on, and the external monitor resolution stays with the
  default value (3840 ⨉ 2160), which is also not desired.

  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.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 24 08:56:58 2020
  InstallationDate: Installed on 2020-04-26 (88 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/100/+subscriptions

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

[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen

[Daniel van Vugt]

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

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

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

Title:
  Ubuntu 20.04 gnome-shell places windows on second screen when started
  from primary screen

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

Bug description:
  Ubuntu 20.04 LTS

  gnome-shell:
Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2

  What I expected to happen:
  When clicking a button on the primary screen to open a new window in any 
application, that window should always open on the same monitor. 

  What happened instead:
  Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary 
monitor.

  Why this is a problem:
  My setup are Point of Sale terminals and the primary (a touchscreen) and 
secondary monitors are back to back. When the cashier presses the payment type 
button, the payment type pop-up is opening on the secondary screen which is 
displayed to the customer and not accessible to the cashier who needs to 
complete the transaction. The cashier can't move the pop-up on their own as 
there is no keyboard access (all buttons needed are in the application it 
self), and the touchscreen touches on itself (most of the time).   

  In the past I was able to fix this with devilspie. As this problem has been 
around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell.
   But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps 
opening all the windows on the secondary screen. 

  I've tried various gnome extensions and gnome-tweaks but none of them
  will open all windows (except the customer display) on the primary
  monitor only.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.3-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 19 01:21:39 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-14 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  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/1888098/+subscriptions

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

[Desktop-packages] [Bug 1888088] Re: [amdgpu] [AMD Renoir] Display won't rotate, nor do fractional scaling, but amdgpu.exp_hw_support=1 fixes it

[Daniel van Vugt]

John,

Thanks for figuring that out. Indeed it appears your hardware is a
little too new for kernel 5.4 right now.

** Summary changed:

- [amdgpu] [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do 
fractional scaling
+ [amdgpu] [AMD Renoir] Display won't rotate, nor do fractional scaling, but 
amdgpu.exp_hw_support=1 fixes it

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

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

Title:
  [amdgpu] [AMD Renoir] Display won't rotate, nor do fractional scaling,
  but amdgpu.exp_hw_support=1 fixes it

Status in linux package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Opening Settings -> Display and selecting an orientation other than
  Landscape doesn't work.  Similarly, selecting Fractional Scaling and
  then picking a scale factor has no effect.

  This is a recently installed Ubuntu 20.04, fully updated, on a
  recently released laptop/tablet that uses an AMD Ryzen 4500U
  integrated CPU/GPU.  It is possible that the GPU is not being detected
  by Ubuntu and that is the root cause of the problem.  I couldn't find
  an easy explanation online about how to tell whether a GPU was
  detected or is in use.  I did try running "tlp-stat -g" to get
  graphics status, but it returns without printing anything except its
  version number (1.3.1).

  When I choose an orientation, such as Portrait Right, the setting
  changes and an "Apply" button appears in the top of the Settings
  window.  When I press it, up pops up a dialog asking whether I want to
  "Keep these display settings?" with two options, keep or revert.  The
  rest of the screen goes grey behind the dialog box, but I can already
  see behind the popup that the screen did not change its orientation,
  and the "Orientation" setting back in the Settings->Display window has
  been reverted to "Landscape" without me doing it.  Whether I choose
  keep or revert, or merely let it time out after 20 seconds, the result
  remains the same -- the display stays in Landscape mode and the
  setting that I had made is reverted.

  Regarding scaling, I can set the display scale to 100% (default) or
  200%, successfully.  But when I turn on the "Fractional Scaling"
  slider, the graphics around the edge of the screen immediately
  increase in size (the icons in the left-hand dock, the text in the top
  bar), even though I have not changed the scale setting.  I have
  included two screenshots (original screen, and with Fractional Scaling
  on).  There is also some strangeness about whether sliding the
  Fractional Scaling slider updates the Scale menu to allow more scales
  - sometimes it does, sometimes it doesn't.

  When I attempt to set a fractional scale such as 125%, the "Apply"
  button appears in the upper right corner.  When I press that, the
  display does not actually scale, and a pop-up asks if I want to keep
  or revert the setting.  But looking back at the Displays settings, the
  Scale has already reverted to 100% (as above with the Orientation).
  Screenshot enclosed.

  The display has been rock-solid before this, but now it started
  showing artifacts, such as previous copies of the Displays window.
  I've enclosed a screen shot, which shows checkerboard in the screen
  locations that (in reality) were displaying prior versions of the
  window.  Hmm, examining that screenshot, it looks like the display DID
  start occupying 25% more space horizontally and vertically, but
  something about the video scanning versus the screen updating got out
  of whack.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog:

  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sat Jul 18 14:00:38 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Renoir [17aa:3f1a]
  InstallationDate: Installed on 2020-07-16 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81X2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EECN20WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  

[Desktop-packages] [Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)

[Daniel van Vugt]

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

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

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

Title:
  Unusable graphics, nouveau + G73 (GEForce 7600)

Status in linux package in Ubuntu:
  Won't Fix
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Won't Fix

Bug description:
  This is an older card, but it worked well on ubuntu 12.x :)

  Booting "Try Ubuntu" on 20.04 get the correct resolution and 2
  displays, but the video glitches and shows all sorts of noise.  It is
  largely unusable (which makes filing this bug very hard).

  Safe Graphics works in low-res.

  The nvidia proprietary driver seems to not support this device any
  more.  I like this card because it has no fan (and I don't do a lot of
  graphics-intense stuff).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 18:13:48 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd G73 [GeForce 7600 GT] [1458:3417]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd  
---  priority=low
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: X58 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd12/30/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)

[Launchpad Bug Tracker]

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

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

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

Title:
  Unusable graphics, nouveau + G73 (GEForce 7600)

Status in linux package in Ubuntu:
  Won't Fix
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Won't Fix

Bug description:
  This is an older card, but it worked well on ubuntu 12.x :)

  Booting "Try Ubuntu" on 20.04 get the correct resolution and 2
  displays, but the video glitches and shows all sorts of noise.  It is
  largely unusable (which makes filing this bug very hard).

  Safe Graphics works in low-res.

  The nvidia proprietary driver seems to not support this device any
  more.  I like this card because it has no fan (and I don't do a lot of
  graphics-intense stuff).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 18:13:48 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd G73 [GeForce 7600 GT] [1458:3417]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd  
---  priority=low
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: X58 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd12/30/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)

[Daniel van Vugt]

Sadly I think you are right. Fixing the nouveau driver, and particularly
for older cards, is an open-ended problem.

Officially Nvidia only supports the GeForce 7600 hardware in driver
version 304. But driver version 304 is too old for inclusion in Ubuntu
20.04.

A newer Nvidia card (and using the latest proprietary Nvidia driver)
would also have solved the problem.

** Package changed: mesa (Ubuntu) => xserver-xorg-video-nouveau (Ubuntu)

** Changed in: xserver-xorg-video-nouveau (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/1875712

Title:
  Unusable graphics, nouveau + G73 (GEForce 7600)

Status in linux package in Ubuntu:
  Won't Fix
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Won't Fix

Bug description:
  This is an older card, but it worked well on ubuntu 12.x :)

  Booting "Try Ubuntu" on 20.04 get the correct resolution and 2
  displays, but the video glitches and shows all sorts of noise.  It is
  largely unusable (which makes filing this bug very hard).

  Safe Graphics works in low-res.

  The nvidia proprietary driver seems to not support this device any
  more.  I like this card because it has no fan (and I don't do a lot of
  graphics-intense stuff).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 18:13:48 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd G73 [GeForce 7600 GT] [1458:3417]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd  
---  priority=low
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: X58 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd12/30/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

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

[Daniel van Vugt]

It would be a problem in gnome-shell's dialog code so someone please
report it to the gnome-shell developers at:

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

and then tell us the new issue ID.

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed

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

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

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

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

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

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

[Desktop-packages] [Bug 1888846] Re: Ubuntu 20.04 Background and lockscreen image turns into white noise after sleep and wakeup

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1855757
   [nvidia] Background image corrupted after standby or resume from suspend

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

Title:
  Ubuntu 20.04 Background and lockscreen image turns into white noise
  after sleep and wakeup

Status in xorg package in Ubuntu:
  New

Bug description:
  I think it maybe related with gsettings, as you can see in the screeshoot 
that I will attach i change the dock form and I also add the option one click 
minimize. But it can be alse related with xorg, i dont really kwon, bu if you 
need some extra log just tell me how.
  There is a for 19.04 which looks the same but it closed.

  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
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/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.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 24 14:04:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.108, 5.4.0-26-generic, x86_64: installed
   nvidia-340, 340.108, 5.4.0-42-generic, x86_64: installed
  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:124d]
 Subsystem: ASUSTeK Computer Inc. GeForce GT 720M [1043:124d]
  InstallationDate: Installed on 2020-07-22 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. X550CC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=29de19f8-8723-4a14-b713-657be2a231c9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550CC.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550CC
  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.:bvrX550CC.300:bd03/24/2014:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550CC
  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.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.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/xorg/+bug/146/+subscriptions

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

[Desktop-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation

[Daniel van Vugt]

This bug is closed. Please use bug 1855757 instead.

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend or
  hibernation

Status in GNOME Shell:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Disco:
  Won't Fix
Status in mutter source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  The Nvidia (Xorg) driver corrupts the desktop wallpaper (by design
  (1)) upon resuming from suspend. This creates a poor user experience
  and gives the impression of severe memory corruption.

  (1)
  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  [Test Case]

  0. Set up an Nvidia-only system using the proprietary Nvidia Xorg driver.
  1. Suspend and resume the machine.
  Expect: The wallpaper still looks like it did before suspending.

  [Regression Potential]

  Low. The exact same patch is in Gnome 3.34 (Ubuntu 19.10) already and
  has been used for a couple of months without issue.

  [Original Report]

  https://trello.com/c/i5hENxSO

  Every other wake from sleep presents a corrupted screen with no unlock
  app.  There's a dock and system menu on a black background with pixel
  garbage.  Some personal information in the dock's large window
  thumbnails.  Bitmap garbage flashes on the screen when interacting
  with anything.  Only workaround is doing another sleep-wake cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:4b:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  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: Thu Dec 20 22:19:29 2018
  DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-11-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-12-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
  InstallationDate: Installed on 2018-10-28 (54 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: X99P-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  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.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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: 

[Desktop-packages] [Bug 1848951] Re: High CPU when just moving the mouse

[Daniel van Vugt]

Jegor,

This bug is closed for Gnome Shell. Please open a new bug by running
this command from the affected machine:

  ubuntu-bug gnome-shell

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

Title:
  High CPU when just moving the mouse

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

Bug description:
  I have installed fresh Ubuntu 18.04.03 on my PC. Previously I had
  Ubuntu 16.04 version but didn't have any such problems with the cpu
  usage.

  But I have saw in terminal that somehow the processes Xorg and gnome-
  shell use always 20% when just moving the mouse around for 18.04
  version.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 20:54:50 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / 
R7 250X] [1002:683d] (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 
[1462:2710]
  InstallationDate: Installed on 2019-10-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D2V
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D2V
  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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  module-switch-on-port-avaiable: switch the port on ucm devices based
  on the priority

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * On the Dell machines with multi function audio jack, the
     headphone/headset can't output sound automatically, which is different
     from ubuntu 18.04. The headphone/headset should be able to  output
     sound automatically after plugging in the audio jack.

  [Test Case]

   * On Tiger Lake platform
     Reproduce step:
     1. plug headphone/headset
     2. open g-c-c sound to check

     Expect result: The output device should switch to headphone or headset,
    since headphone's priority is higher in ucm2 config.
     Actual result: The output device is still internal speaker.

  [Regression Potential]

   * The change insert the ucm device by its priority, the potential
 regression is low, since if the change is not working properly, the 
 side effect is that the order of ucm devices are wrong, and it won't 
 switch to the correct output device as expect, but user can still
 config it manually.

  [Other]

   * This bug originates from an OEM private bug #1875597, then ubuntu users
     reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329
     and the 1st issue of #1881659 have the same root cause as #1875597

   * The root cause is the ucm2 conf defines 2 input devices: the Mic2 and
     Headset MIC, and the pulseaudio parse the input device Headset MIC
     first then Mic2, finally the audio jack is set to Mic2 mode, this make
     the audio jack can't output sound anymore. To fix it, let the audio
     jack set to Headset MIC mode by default (Headset MIC has higher
     priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the
     device event to module-switch-on-port-available by the order of
     priority in the umc2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882161/+subscriptions

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

[Desktop-packages] [Bug 1884703] Re: package libvdpau1 1.3-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other instances of package l

[Launchpad Bug Tracker]

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

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

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

Title:
  package libvdpau1 1.3-1ubuntu2 failed to install/upgrade: trying to
  overwrite shared '/etc/vdpau_wrapper.cfg', which is different from
  other instances of package libvdpau1:i386

Status in libvdpau package in Ubuntu:
  Confirmed

Bug description:
  when i try to install update getting error

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libvdpau1 1.3-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sun Jun 21 09:31:41 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ErrorMessage: trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is 
different from other instances of package libvdpau1:i386
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Foxconn International, Inc. Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller [105b:0d8d]
  InstallationDate: Installed on 2020-06-17 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=b74d3c53-33d4-4d68-85f8-26dec8a235d2 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: libvdpau
  Title: package libvdpau1 1.3-1ubuntu2 failed to install/upgrade: trying to 
overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other 
instances of package libvdpau1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61MXE
  dmi.board.vendor: Foxconn
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/05/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnFoxconn:rnH61MXE:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.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/libvdpau/+bug/1884703/+subscriptions

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

[Desktop-packages] [Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling

[Daniel van Vugt]

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

Title:
  GNOME Shell should support fractional (non-integer) Hi-DPI scaling

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

Bug description:
  https://trello.com/c/r12LY9iA (for 17.04 was
  https://trello.com/c/TvwNvXOo)

  ---

  I'm using fully updated Ubuntu GNOME 17.04.

  In Ubuntu Gnome, you only allow for integer scaling of things for high
  DPI monitors. While in theory this sounds good, on a 27 inch 4k
  monitor like mine, restricting it to integers is a problem. 1x is
  annoyingly small, and 2x is WAY too big. You need a 1.5x, and
  presumably to just allow most noninteger values to future proof the
  distribution given 8k monitors and all sorts of new and weird things
  coming out, like windows 10 has.

  Photos of the two annoying sizes are available here (it won't let me
  attach two files):

  http://i.imgur.com/vWrvZxq.jpg
  http://i.imgur.com/11p19k7.jpg

  I apologize for my photography skills in advance., you'll have to look
  at the ruler for scale to see the problem. Please contact me if you
  need any more information etc.

  Workaround
  ==
  You can enable experimental fractional scaling in Ubuntu 17.10 or 18.04 LTS 
by running the following command in a terminal and then restarting your 
computer. Note that this is an experimental feature and is not fully supported 
by either Ubuntu or GNOME.

  gsettings set org.gnome.mutter experimental-features "['scale-monitor-
  framebuffer']"

  After restarting your computer, you should find additional scale
  options in Settings > Devices > Displays.

  If you change your mind and want to get back to supported status, run:

  gsettings reset org.gnome.mutter experimental-features

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

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

[Desktop-packages] [Bug 1888810] Re: Ubuntu 20.04 screen tearing intel graphics

[Daniel van Vugt]

This could be one of a number of bugs.

If you are using the old 'intel' driver then it's bug 1867668.

If you are using multiple monitors then it's bug 1853094.

If you are using fullscreen apps then it's bug 1754284.

If none of the above then this should probably move to the window
manager ("marco"?).

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

** Summary changed:

- Ubuntu 20.04 screen tearing intel graphics
+ MATE desktop in Ubuntu 20.04 screen tearing intel graphics

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

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

Title:
  MATE desktop in Ubuntu 20.04 screen tearing intel graphics

Status in marco package in Ubuntu:
  New

Bug description:
  Running a Ubuntu 20.04 with its default (kmodesetting ?) driver.
  Screen tearing is present and shows artefacts while scrolling in
  browsers (firefox and chromium) and videos.

  Ubuntu 5.4.0-40.44-generic 5.4.44

  Processor/GPU is a core m5-6y54 (Skylake)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 515 [8086:191e] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 515 [103c:8170]
  InstallationDate: Installed on 2020-05-10 (78 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b560 Chicony Electronics Co., Ltd HP HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteBook Folio G1
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=UUID=92c467dc-e394-4f19-a6a2-e7cf918f0ffb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal ubuntu
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/05/2020
  dmi.bios.vendor: HP
  dmi.bios.version: N91 Ver. 01.45
  dmi.board.name: 8170
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 29.73
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN91Ver.01.45:bd01/05/2020:svnHP:pnHPEliteBookFolioG1:pvr:rvnHP:rn8170:rvrKBCVersion29.73:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook Folio G1
  dmi.product.sku: V1C39EA#ABD
  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

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

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

[Desktop-packages] [Bug 1757280] Re: Night Light only works on one Monitor

[fermulator]

similar issue in 18.04.4, `gnome-shell 3.28.4`

$ xrandr | grep " connected"
eDP-1 connected (normal left inverted right x axis y axis)
DP-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 
521mm x 293mm
DP-1-2 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 521mm x 293mm

eDP-1 is the built-in laptop monitor; (lid is closed) [1st]
DP-1-X are the external monitors over display port; (in active use, dual 
monitor) [2nd,3rd]

primary display is 2nd, secondary display is 3rd

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

Title:
  Night Light only works on one Monitor

Status in gnome-control-center:
  Expired
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released

Bug description:
  
  Hi

  If I activate the Night Light mode with an external monitor connected,
  the mode is only on the external monitor activated.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Mar 20 23:12:36 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:224b]
  InstallationDate: Installed on 2018-03-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319)
  MachineType: LENOVO 20HF0016MZ
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET45W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HF0016MZ
  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:bvrN1WET45W(1.24):bd02/26/2018:svnLENOVO:pn20HF0016MZ:pvrThinkPadT470s:rvnLENOVO:rn20HF0016MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HF0016MZ
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-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

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

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

[Desktop-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

[Launchpad Bug Tracker]

This bug was fixed in the package linux-azure - 5.4.0-1022.22

---
linux-azure (5.4.0-1022.22) focal; urgency=medium

  * focal/linux-azure: 5.4.0-1022.22 -proposed tracker (LP: #1887060)

  [ Ubuntu: 5.4.0-42.46 ]

  * focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
  * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups"

linux-azure (5.4.0-1021.21) focal; urgency=medium

  * focal/linux-azure: 5.4.0-1021.21 -proposed tracker (LP: #1885845)

  * module intel_sgx appears to be blacklisted by the kernel.  (LP: #1862201)
- Revert "UBUNTU: [Packaging] linux-azure: Prevent intel_sgx from being
  automatically loaded"
- [Packaging] linux-azure: Divert conf files blacklisting intel_sgx

  * Add XDP support to hv_netvsc driver (LP: #1877654)
- hv_netvsc: Add XDP support
- hv_netvsc: Update document for XDP support
- hv_netvsc: Fix XDP refcnt for synthetic and VF NICs

  * Request to include two NUMA related commits in Azure kernels (LP: #1880975)
- PCI: hv: Decouple the func definition in hv_dr_state from VSP message
- PCI: hv: Add support for protocol 1.3 and support PCI_BUS_RELATIONS2

  [ Ubuntu: 5.4.0-41.45 ]

  * focal/linux: 5.4.0-41.45 -proposed tracker (LP: #1885855)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * CVE-2019-19642
- kernel/relay.c: handle alloc_percpu returning NULL in relay_open
  * CVE-2019-16089
- SAUCE: nbd_genl_status: null check for nla_nest_start
  * CVE-2020-11935
- aufs: do not call i_readcount_inc()
  * ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4
kernel (LP: #1826848)
- selftests: net: ip_defrag: ignore EPERM
  * Update lockdown patches (LP: #1884159)
- SAUCE: acpi: disallow loading configfs acpi tables when locked down
  * seccomp_bpf fails on powerpc (LP: #1885757)
- SAUCE: selftests/seccomp: fix ptrace tests on powerpc
  * Introduce the new NVIDIA 418-server and 440-server series, and update the
current NVIDIA drivers (LP: #1881137)
- [packaging] add signed modules for the 418-server and the 440-server
  flavours

 -- Khalid Elmously   Fri, 10 Jul 2020
01:51:58 -0400

** Changed in: linux-oracle (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-riscv package in Ubuntu:
  Fix Released
Status in rtkit package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Released
Status in linux-azure source package in Focal:
  Fix Released
Status in linux-gcp source package in Focal:
  Fix Released
Status in linux-kvm source package in Focal:
  Fix Released
Status in linux-oracle source package in Focal:
  Fix Released
Status in linux-riscv source package in Focal:
  Fix Released
Status in rtkit source package in Focal:
  Confirmed

Bug description:
  SRU Justification

  Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the
  lowlatency kernel since we expected most RT users to use that kernel.
  However we are getting RT regressions with the generic kernel. Digging
  deeper into this option, it seems to be pretty specialized and to
  require quite a bit of workload-specific configuration/tuning to be
  useful, so it doesn't really seem to make sense for a general-purpose
  kernel.

  Fix: Turn this option back off.

  Test Case: See comment #4.

  Regression Potential: This was turned on to support some docker
  functionality, so this functionality will no longer be available.
  We've had this option off for all releases prior to focal, so this
  seems acceptable.

  ---

  These errors started right after upgrading to 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 10:31:43 2020
  InstallationDate: Installed on 2019-06-18 (315 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago)

To manage notifications 

[Desktop-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

[Launchpad Bug Tracker]

This bug was fixed in the package linux-gcp - 5.4.0-1021.21

---
linux-gcp (5.4.0-1021.21) focal; urgency=medium

  * focal/linux-gcp: 5.4.0-1021.21 -proposed tracker (LP: #1887062)

  [ Ubuntu: 5.4.0-42.46 ]

  * focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
  * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups"

linux-gcp (5.4.0-1020.20) focal; urgency=medium

  * focal/linux-gcp: 5.4.0-1020.20 -proposed tracker (LP: #1885847)

  [ Ubuntu: 5.4.0-41.45 ]

  * focal/linux: 5.4.0-41.45 -proposed tracker (LP: #1885855)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * CVE-2019-19642
- kernel/relay.c: handle alloc_percpu returning NULL in relay_open
  * CVE-2019-16089
- SAUCE: nbd_genl_status: null check for nla_nest_start
  * CVE-2020-11935
- aufs: do not call i_readcount_inc()
  * ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4
kernel (LP: #1826848)
- selftests: net: ip_defrag: ignore EPERM
  * Update lockdown patches (LP: #1884159)
- SAUCE: acpi: disallow loading configfs acpi tables when locked down
  * seccomp_bpf fails on powerpc (LP: #1885757)
- SAUCE: selftests/seccomp: fix ptrace tests on powerpc
  * Introduce the new NVIDIA 418-server and 440-server series, and update the
current NVIDIA drivers (LP: #1881137)
- [packaging] add signed modules for the 418-server and the 440-server
  flavours

 -- Khalid Elmously   Fri, 10 Jul 2020
02:31:42 -0400

** Changed in: linux-gcp (Ubuntu)
   Status: Invalid => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-16089

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-19642

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-11935

** Changed in: linux-azure (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-riscv package in Ubuntu:
  Fix Released
Status in rtkit package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Released
Status in linux-azure source package in Focal:
  Fix Released
Status in linux-gcp source package in Focal:
  Fix Released
Status in linux-kvm source package in Focal:
  Fix Released
Status in linux-oracle source package in Focal:
  Fix Released
Status in linux-riscv source package in Focal:
  Fix Released
Status in rtkit source package in Focal:
  Confirmed

Bug description:
  SRU Justification

  Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the
  lowlatency kernel since we expected most RT users to use that kernel.
  However we are getting RT regressions with the generic kernel. Digging
  deeper into this option, it seems to be pretty specialized and to
  require quite a bit of workload-specific configuration/tuning to be
  useful, so it doesn't really seem to make sense for a general-purpose
  kernel.

  Fix: Turn this option back off.

  Test Case: See comment #4.

  Regression Potential: This was turned on to support some docker
  functionality, so this functionality will no longer be available.
  We've had this option off for all releases prior to focal, so this
  seems acceptable.

  ---

  These errors started right after upgrading to 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 10:31:43 2020
  InstallationDate: Installed on 2019-06-18 (315 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago)

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

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

[Desktop-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oracle - 5.4.0-1021.21

---
linux-oracle (5.4.0-1021.21) focal; urgency=medium

  * focal/linux-oracle: 5.4.0-1021.21 -proposed tracker (LP: #1887065)

  [ Ubuntu: 5.4.0-42.46 ]

  * focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
  * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups"

linux-oracle (5.4.0-1020.20) focal; urgency=medium

  * focal/linux-oracle: 5.4.0-1020.20 -proposed tracker (LP: #1885851)

  [ Ubuntu: 5.4.0-41.45 ]

  * focal/linux: 5.4.0-41.45 -proposed tracker (LP: #1885855)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * CVE-2019-19642
- kernel/relay.c: handle alloc_percpu returning NULL in relay_open
  * CVE-2019-16089
- SAUCE: nbd_genl_status: null check for nla_nest_start
  * CVE-2020-11935
- aufs: do not call i_readcount_inc()
  * ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4
kernel (LP: #1826848)
- selftests: net: ip_defrag: ignore EPERM
  * Update lockdown patches (LP: #1884159)
- SAUCE: acpi: disallow loading configfs acpi tables when locked down
  * seccomp_bpf fails on powerpc (LP: #1885757)
- SAUCE: selftests/seccomp: fix ptrace tests on powerpc
  * Introduce the new NVIDIA 418-server and 440-server series, and update the
current NVIDIA drivers (LP: #1881137)
- [packaging] add signed modules for the 418-server and the 440-server
  flavours

 -- Khalid Elmously   Fri, 10 Jul 2020
02:11:06 -0400

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-riscv package in Ubuntu:
  Fix Released
Status in rtkit package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Released
Status in linux-azure source package in Focal:
  Fix Released
Status in linux-gcp source package in Focal:
  Fix Released
Status in linux-kvm source package in Focal:
  Fix Released
Status in linux-oracle source package in Focal:
  Fix Released
Status in linux-riscv source package in Focal:
  Fix Released
Status in rtkit source package in Focal:
  Confirmed

Bug description:
  SRU Justification

  Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the
  lowlatency kernel since we expected most RT users to use that kernel.
  However we are getting RT regressions with the generic kernel. Digging
  deeper into this option, it seems to be pretty specialized and to
  require quite a bit of workload-specific configuration/tuning to be
  useful, so it doesn't really seem to make sense for a general-purpose
  kernel.

  Fix: Turn this option back off.

  Test Case: See comment #4.

  Regression Potential: This was turned on to support some docker
  functionality, so this functionality will no longer be available.
  We've had this option off for all releases prior to focal, so this
  seems acceptable.

  ---

  These errors started right after upgrading to 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 10:31:43 2020
  InstallationDate: Installed on 2019-06-18 (315 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago)

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

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

[Desktop-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.4.0-42.46

---
linux (5.4.0-42.46) focal; urgency=medium

  * focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)

  * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups"

linux (5.4.0-41.45) focal; urgency=medium

  * focal/linux: 5.4.0-41.45 -proposed tracker (LP: #1885855)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * CVE-2019-19642
- kernel/relay.c: handle alloc_percpu returning NULL in relay_open

  * CVE-2019-16089
- SAUCE: nbd_genl_status: null check for nla_nest_start

  * CVE-2020-11935
- aufs: do not call i_readcount_inc()

  * ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4
kernel (LP: #1826848)
- selftests: net: ip_defrag: ignore EPERM

  * Update lockdown patches (LP: #1884159)
- SAUCE: acpi: disallow loading configfs acpi tables when locked down

  * seccomp_bpf fails on powerpc (LP: #1885757)
- SAUCE: selftests/seccomp: fix ptrace tests on powerpc

  * Introduce the new NVIDIA 418-server and 440-server series, and update the
current NVIDIA drivers (LP: #1881137)
- [packaging] add signed modules for the 418-server and the 440-server
  flavours

 -- Khalid Elmously   Thu, 09 Jul 2020
19:50:26 -0400

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-riscv package in Ubuntu:
  Fix Released
Status in rtkit package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Released
Status in linux-azure source package in Focal:
  Fix Released
Status in linux-gcp source package in Focal:
  Fix Released
Status in linux-kvm source package in Focal:
  Fix Released
Status in linux-oracle source package in Focal:
  Fix Released
Status in linux-riscv source package in Focal:
  Fix Released
Status in rtkit source package in Focal:
  Confirmed

Bug description:
  SRU Justification

  Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the
  lowlatency kernel since we expected most RT users to use that kernel.
  However we are getting RT regressions with the generic kernel. Digging
  deeper into this option, it seems to be pretty specialized and to
  require quite a bit of workload-specific configuration/tuning to be
  useful, so it doesn't really seem to make sense for a general-purpose
  kernel.

  Fix: Turn this option back off.

  Test Case: See comment #4.

  Regression Potential: This was turned on to support some docker
  functionality, so this functionality will no longer be available.
  We've had this option off for all releases prior to focal, so this
  seems acceptable.

  ---

  These errors started right after upgrading to 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 10:31:43 2020
  InstallationDate: Installed on 2019-06-18 (315 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-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]

This bug was fixed in the package chromium-browser -
84.0.4147.89-0ubuntu1

---
chromium-browser (84.0.4147.89-0ubuntu1) groovy; urgency=medium

  * New upstream release: 84.0.4147.89 (LP: #1889106)

 -- Olivier Tilloy   Mon, 27 Jul 2020
18:39:43 +0200

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

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 1888992] Re: [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones

[Hui Wang]

If you don't use "options snd_hda_intel power_save=0", instead you use
"options snd_hda_intel power_save_controller=0", is it a valid
workaround too?

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

Title:
  [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching
  to front jack after plugging in headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I boot my system without any sound devices plugged into any jacks;
  checking Gnome settings Sound, Output Device is "Dummy Output" (no
  other options available in drop-down list). I plug in headphones into
  the front jack and play some audio, but do not hear any sound from the
  headphones; checking Gnome settings Sound, the Output Device is still
  "Dummy Output", with no other options available.

  This is a regression from previous behaviour, when plugging in
  headphones into the front jack would automatically enable/switch to
  the front jack and its associated controller "Family 17h (Models 00h-
  0fh) HD Audio Controller" (this is the motherboard's onboard audio
  hardware).

  I can currently workaround this each time I plug in the headphones by
  installing and running pavucontrol, and under Configuration selecting
  "Analogue Stereo Output (unplugged) (unavailable)" - this option
  becomes "Analogue Stereo Output" after I select it.

  This seems to be a regression in pulseaudio after an upgrade from from
  1:13.99.1-1ubuntu3.3 to 1:13.99.1-1ubuntu3.5.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chinf  1741 F pulseaudio
   /dev/snd/pcmC1D0p:   chinf  1741 F...m pulseaudio
   /dev/snd/controlC0:  chinf  1741 F pulseaudio
   /dev/snd/timer:  chinf  1741 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 26 12:46:52 2020
  InstallationDate: Installed on 2018-10-29 (635 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful
  Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chinf  1741 F pulseaudio
   /dev/snd/controlC0:  chinf  1741 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] 
No sound at all
  UpgradeStatus: Upgraded to focal on 2020-05-04 (83 days ago)
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1888060] Re: Update to 3.36.4 and SRU it

[Łukasz Zemczak]

Hello Marco, or anyone else affected,

Accepted gnome-shell into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.36.4-1ubuntu1~20.04.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

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

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

Title:
  Update to 3.36.4 and SRU it

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.4

  [ Test case ]

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

  GNOME Shell and its components should continue working

  [ Regression potential ]

  Calendar server received a major change, so need to ensure that events
  are still properly populating the gnome-shell calendar.

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

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

[Desktop-packages] [Bug 1885346] Re: gnome-shell-calendar-server leaks GBs of memory every few days

[Łukasz Zemczak]

Hello Heewa, or anyone else affected,

Accepted gnome-shell into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.36.4-1ubuntu1~20.04.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

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

Title:
  gnome-shell-calendar-server leaks GBs of memory every few days

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Committed
Status in gnome-shell package in Debian:
  Fix Released

Bug description:
  [ Impact ]

  gnome-shell-calendar-server memory usage increases daily

  [ Test case ]

  Monitor the memory usage of gnome-shell-calendar-server process using
  top or similar tools and ensure that its memory usage is stable.

  [ Regression potential ]

  Events in gnome-shell calendar aren't visible anymore

  ---

  It's been happening repeatedly over the last maybe week? I have to
  manually kill it about once a day, when I start to feel everything
  slow down as the OS starts to swap.

  Actually, I tracked down and fixed a few leaks in the code, and it
  looks stable so far. I'll submit a patch soon, as well as send the fix
  upstream to Gnome.

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

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

[Desktop-packages] [Bug 1871868] Re: Shell dialog text is truncated and ellipsized

[Łukasz Zemczak]

Hello Jani, or anyone else affected,

Accepted gnome-shell into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.36.4-1ubuntu1~20.04.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

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

Title:
  Shell dialog text is truncated and ellipsized

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

Bug description:
  [ Impact ]

  Shell modal dialogs contain text that may be truncated when using
  certain locales

  [ Test case ]

  - Start a virtual machine with GNOME Boxes
  - The keyboard prompt should be all visible

  [ Regression potential ]

  Text isn't properly rendered or the dialog is not all visible in the
  display

  

  When trying to start a virtual machine with Gnome Boxes, I get a
  prompt about keyboard shortcuts. The prompt text is localized, but
  translated back to English (I think, based on [1]) it says:

  Boxes wants to inhibit shortcuts

  You can restore shortcuts by pressing Super+Escape.

  In my locale (Finnish), it says

  Sovellus Boksit haluaa rajoittaa pikanäppäinten toimintaa.

  Voit palauttaa pikanäppäinten toiminnan painamalla Super...

  (sic; see attached photo)

  So the actual key combination is truncated, defeating the point of
  that part of the text.

  This isn't a localization error (AFAICT; see [2]). It's caused by the
  text being forced to fit on a single line of an arbitrarily fixed
  width, instead of wrapping to span as many lines as needed.

  (I'm reporting this against gnome-shell as opposed gnome-boxes based
  on [3]. Feel free to reassign as necessary.)

  * [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874526#28
  * [2] 
https://translations.launchpad.net/ubuntu/focal/+source/gnome-shell/+pots/gnome-shell/fi/+translate?batch=10show=allsearch=pikan%C3%A4pp%C3%A4inten
  * [3] https://bugzilla.redhat.com/show_bug.cgi?id=1668036

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
  Uname: Linux 5.4.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 18:29:14 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-10-13 (1274 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1SourcePackage: 
gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-05 (4 days ago)

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

-- 
Mailing list: https://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 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)

[Tim Hockin]

Buy a cheap Radeon card.  This fight is not worth having.

On Mon, Jul 27, 2020 at 3:15 PM Adrian Nida <1875...@bugs.launchpad.net> wrote:
>
> Hi,  Upgraded an old desktop from 19.10 to 20.04 and hit this graphics
> display issue.  I also have the same graphics card:
>
> >From lspci:
> 03:00.0 VGA compatible controller: NVIDIA Corporation G73 [GeForce 7600 GT] 
> (rev a1)
>
> Is there any workaround I can perform to make this desktop usable? Other
> than blowing away the install and going back to 19.10?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1875712
>
> Title:
>   Unusable graphics, nouveau + G73 (GEForce 7600)
>
> Status in mesa package in Ubuntu:
>   Confirmed
> Status in mutter package in Ubuntu:
>   New
>
> Bug description:
>   This is an older card, but it worked well on ubuntu 12.x :)
>
>   Booting "Try Ubuntu" on 20.04 get the correct resolution and 2
>   displays, but the video glitches and shows all sorts of noise.  It is
>   largely unusable (which makes filing this bug very hard).
>
>   Safe Graphics works in low-res.
>
>   The nvidia proprietary driver seems to not support this device any
>   more.  I like this card because it has no fan (and I don't do a lot of
>   graphics-intense stuff).
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: xorg 1:7.7+19ubuntu14
>   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
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CasperVersion: 1.445
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Apr 28 18:13:48 2020
>   DistUpgraded: Fresh install
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 
> [VGA controller])
>  Subsystem: Gigabyte Technology Co., Ltd G73 [GeForce 7600 GT] [1458:3417]
>   LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
>   MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=C.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd  
> ---  priority=low
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/30/2010
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: P1.40
>   dmi.board.name: X58 Extreme6
>   dmi.board.vendor: ASRock
>   dmi.chassis.asset.tag: To Be Filled By O.E.M.
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: To Be Filled By O.E.M.
>   dmi.chassis.version: To Be Filled By O.E.M.
>   dmi.modalias: 
> dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd12/30/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
>   dmi.product.family: To Be Filled By O.E.M.
>   dmi.product.name: To Be Filled By O.E.M.
>   dmi.product.sku: To Be Filled By O.E.M.
>   dmi.product.version: To Be Filled By O.E.M.
>   dmi.sys.vendor: To Be Filled By O.E.M.
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.101-2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel 
> 2:2.99.917+git20200226-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1875712/+subscriptions

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

Title:
  Unusable graphics, nouveau + G73 (GEForce 7600)

Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New

Bug description:
  This is an older card, but it worked well on ubuntu 12.x :)

  Booting "Try Ubuntu" on 20.04 get the correct resolution and 2
  displays, but the video glitches and shows all sorts of noise.  It is
  largely unusable (which makes filing this bug very hard).

  Safe Graphics works in low-res.

  The nvidia proprietary driver seems to not support this device any
  more.  I like this card because it has no fan (and I don't do a lot of
  graphics-intense stuff).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 

[Desktop-packages] [Bug 1870867] Re: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl))

[dngreengas]

I switched to proposed and I have not had the bug appear. I used to
experience it every 10 minutes or so when scrolling with my finger in
Firefox and Chrome.

Now if we can only fix the bug where the on-screen keyboard appears when
a physical keyboard is plugged in (grin).

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

Title:
  gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion
  failed: (META_IS_STAGE_X11 (impl))

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

Bug description:
  [ Impact ]

  GNOME Shell crashes in meta_x11_get_stage_window.

  [ Test case ]

  Perform touch events via touchpad or touchscreen, eventually the shell
  will crash.

  Errors can be monitored at:
   https://errors.ubuntu.com/problem/1d4cdd9f2e9cd378a3e0aeed140079f319454bf2

  [ Regression potential ]

  Windows might not be closed correctly when requested via delete-events
  (clicking on clientside decoration close button).

  ---

  ProblemType: CrashDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 22:08:06 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1Signal: 6SourcePackage: 
gnome-shell
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0
  Title: gnome-shell crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2020-04-05 (0 days ago)
  UserGroups: adm cdrom dialout dip docker input libvirt lpadmin plugdev 
sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1889054] Re: No audio on TRX40 platform

[Daniel Letzeisen]

Eduardo, if possible, please try out latest mainline kernel to confirm it 
actually fixes the problem:
https://wiki.ubuntu.com/Kernel/MainlineBuilds#How_do_I_install_an_upstream_kernel.3F
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7.10/

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

Title:
  No audio on TRX40 platform

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have Ubuntu 20.04 running on a computer based on AMD Threadripper
  3960x, TRX40 platform (Gigabyte TRX40 AORUS PRO). Audio hasn't worked
  so far.

  I read about audio problems on this platform from the beginning but
  they should be fixed in kernel 5.6 according to this
  https://www.phoronix.com/scan.php?page=news_item=Linux-AMD-TRX40
  -Audio-Quirks

  Kernel bug reports should be related to these ones:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873
  https://bugzilla.kernel.org/show_bug.cgi?id=206543

  Since it should be fixed in recent kernel versions, I guess the
  solution for Ubuntu 20.04 using 5.4 kernel is backporting the fixes.

  Is Ubuntu planning to do this?

  Thanks
  Eduardo

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jul 27 10:41:15 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-03-05 (143 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to focal on 2020-04-06 (111 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eduardo1907 F pulseaudio
   /dev/snd/controlC0:  eduardo1907 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-05 (144 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-06 (112 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: TRX40 AORUS PRO WIFI
  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.:bvrF2:bd10/24/2019:svnGigabyteTechnologyCo.,Ltd.:pnTRX40AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnTRX40AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: TRX40 AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1889054] Re: No audio on TRX40 platform

[Daniel Letzeisen]

@Eduardo, the HDMI is not built into the motherboard and is part of your
Nvidia card, correct?

@sohail, sorry for false duplicate. Do you remember which kernel version
solved the problem?

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

Title:
  No audio on TRX40 platform

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have Ubuntu 20.04 running on a computer based on AMD Threadripper
  3960x, TRX40 platform (Gigabyte TRX40 AORUS PRO). Audio hasn't worked
  so far.

  I read about audio problems on this platform from the beginning but
  they should be fixed in kernel 5.6 according to this
  https://www.phoronix.com/scan.php?page=news_item=Linux-AMD-TRX40
  -Audio-Quirks

  Kernel bug reports should be related to these ones:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873
  https://bugzilla.kernel.org/show_bug.cgi?id=206543

  Since it should be fixed in recent kernel versions, I guess the
  solution for Ubuntu 20.04 using 5.4 kernel is backporting the fixes.

  Is Ubuntu planning to do this?

  Thanks
  Eduardo

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jul 27 10:41:15 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-03-05 (143 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to focal on 2020-04-06 (111 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eduardo1907 F pulseaudio
   /dev/snd/controlC0:  eduardo1907 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-05 (144 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-06 (112 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: TRX40 AORUS PRO WIFI
  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.:bvrF2:bd10/24/2019:svnGigabyteTechnologyCo.,Ltd.:pnTRX40AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnTRX40AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: TRX40 AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)

[Adrian Nida]

Hi,  Upgraded an old desktop from 19.10 to 20.04 and hit this graphics
display issue.  I also have the same graphics card:

>From lspci:
03:00.0 VGA compatible controller: NVIDIA Corporation G73 [GeForce 7600 GT] 
(rev a1)

Is there any workaround I can perform to make this desktop usable? Other
than blowing away the install and going back to 19.10?

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

Title:
  Unusable graphics, nouveau + G73 (GEForce 7600)

Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New

Bug description:
  This is an older card, but it worked well on ubuntu 12.x :)

  Booting "Try Ubuntu" on 20.04 get the correct resolution and 2
  displays, but the video glitches and shows all sorts of noise.  It is
  largely unusable (which makes filing this bug very hard).

  Safe Graphics works in low-res.

  The nvidia proprietary driver seems to not support this device any
  more.  I like this card because it has no fan (and I don't do a lot of
  graphics-intense stuff).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 18:13:48 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd G73 [GeForce 7600 GT] [1458:3417]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd  
---  priority=low
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: X58 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd12/30/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1881490] Re: Onboard sound not detected for Zenith ROG after upgrade to 20.04

[Daniel Letzeisen]

** This bug is no longer a duplicate of bug 1889054
   No audio on TRX40 platform

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

Title:
  Onboard sound not detected for Zenith ROG after upgrade to 20.04

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After upgrading to 20.04, my onboard sound no longer seems to work.
  The motherboard is ROG Zenith. dmesg shows the following:

  [9.266092] snd_hda_intel :09:00.1: dmic_detect option is deprecated, 
pass snd-intel-dspcfg.dsp_driver=1 option instead
  [9.266556] snd_hda_intel :09:00.1: Disabling MSI
  [9.266586] snd_hda_intel :09:00.1: Handle vga_switcheroo audio client
  [9.267181] snd_hda_intel :0b:00.3: Skipping the blacklisted device

  After searching for this message in kernel source, I happened upon
  this line:

  
https://github.com/torvalds/linux/blob/052c467cb58748e302a95546925928e637025acc/sound/pci/hda/hda_intel.c#L2082

  static const struct pci_device_id driver_blacklist[] = {
{ PCI_DEVICE_SUB(0x1022, 0x1487, 0x1043, 0x874f) }, /* ASUS ROG Zenith 
II / Strix */
{ PCI_DEVICE_SUB(0x1022, 0x1487, 0x1462, 0xcb59) }, /* MSI TRX40 
Creator */
{ PCI_DEVICE_SUB(0x1022, 0x1487, 0x1462, 0xcb60) }, /* MSI TRX40 */
{}
  };

  Which led me to this bug report:

  https://lore.kernel.org/alsa-
  devel/20200424061222.19792-1-ti...@suse.de/

  I confirmed that the PCI device that is not working appears to match
  the vendor ID:

  $  lspci | grep 0b:00.3
  0b:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 
00h-0fh) HD Audio Controller

  $ lspci -n | grep 0b:00.3
  0b:00.3 0403: 1022:1457

  Unfortunately, I am unsure how to test a Ubuntu compatible kernel with
  these changes but it appears there has been some jiggery pokery in
  Linux kernel land in this regard.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sohail 4693 F pulseaudio
   /dev/snd/pcmC1D0p:   sohail 4693 F...m pulseaudio
   /dev/snd/controlC0:  sohail 4693 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 31 11:14:39 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-07-16 (1049 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to focal on 2020-05-24 (6 days ago)
  dmi.bios.date: 07/16/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1304
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1304:bd07/16/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx: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

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

-- 
Mailing list: https://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 1888238] Re: Ubuntu 20.04 simple-scan brightness and contrast controls have no effect

[tkbuntu]

Hello,

me again.
the first file I sent you had perhaps more activity than you need, or want, it 
is verbose.  I actually scanned a document, deleted the scan, changed the 
brightness and contrast controls and did a scan again, at least two times.
The v2 file I am attaching now contains only - run simple-scan  -d, did no scan 
a document, changed the brightness and contrast controls, closed simple-scan.
Regards,Tony

On Sunday, July 26, 2020, 9:55:41 AM CDT, Bartosz Kosiorek 
<1888...@bugs.launchpad.net> wrote:  
 
 Please run application with command:

`simple-scan -d`

and attach the output.

It seems that it is duplication of the upstream issue:
https://gitlab.gnome.org/GNOME/simple-scan/-/issues/185


** Bug watch added: gitlab.gnome.org/GNOME/simple-scan/-/issues #185
  https://gitlab.gnome.org/GNOME/simple-scan/-/issues/185

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

** Also affects: simple-scan via
  https://gitlab.gnome.org/GNOME/simple-scan/-/issues/185
  Importance: Unknown
      Status: Unknown

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1888238

Title:
  Ubuntu 20.04 simple-scan brightness and contrast controls have no
  effect

Status in Simple Scan:
  Unknown
Status in simple-scan package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 simple-scan.  The Brightness and Contrast controls have
  no effect.  No matter how I position the sliders the scan image
  remains the same, ie, a dark background.  It is as if the controls are
  not 'connected'.

  Ubuntu 20.04 is up to date.  The scanner is a Cannon LiDE60.

  I have 19.10 in another partition. Simple-scan works as expected.
  Ditto for 18.04.

  Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: simple-scan 3.36.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 09:47:52 2020
  InstallationDate: Installed on 2020-05-12 (68 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Hewlett-Packard HP EliteBook 8570p
  ProcEnviron:
  PATH=(custom, no user)
  XDG_RUNTIME_DIR=
  LANG=en_US.UTF-8
  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=dc547d11-1deb-404b-988a-a88d4772e66d ro quiet splash vt.handoff=7
  SimpleScanLog:
  
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ICF Ver. F.32
  dmi.board.name: 17A7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 42.32
  dmi.chassis.asset.tag: 8022456
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.32:bd12/05/2012:svnHewlett-Packard:pnHPEliteBook8570p:pvrA1029D1102:rvnHewlett-Packard:rn17A7:rvrKBCVersion42.32:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 8570p
  dmi.product.sku: D2C13UP#ABA
  dmi.product.version: A1029D1102
  dmi.sys.vendor: Hewlett-Packard

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

** Attachment added: 
"=?UTF-8?b?MTg4ODIzOC1VYnVudHUyMDA0LUNhbm5vbkxpREUtdjIudHh0?="
   
https://bugs.launchpad.net/bugs/1888238/+attachment/5396387/+files/%3D%3FUTF-8%3Fb%3FMTg4ODIzOC1VYnVudHUyMDA0LUNhbm5vbkxpREUtdjIudHh0%3F%3D

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

Title:
  Ubuntu 20.04 simple-scan brightness and contrast controls have no
  effect

Status in Simple Scan:
  Unknown
Status in simple-scan package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 simple-scan.  The Brightness and Contrast controls have
  no effect.  No matter how I position the sliders the scan image
  remains the same, ie, a dark background.  It is as if the controls are
  not 'connected'.

  Ubuntu 20.04 is up to date.  The scanner is a Cannon LiDE60.

  I have 19.10 in another partition. Simple-scan works as expected.
  Ditto for 18.04.

  Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: simple-scan 3.36.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 09:47:52 2020
  InstallationDate: Installed on 2020-05-12 (68 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Hewlett-Packard HP EliteBook 8570p
  ProcEnviron:
   PATH=(custom, no user)
   

[Desktop-packages] [Bug 1889090] Re: GNOME Shell doesn't start Ubuntu session with 3.36.4 as per assertion in meta_monitor_manager_xrandr_update_screen_size

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.36.4-1ubuntu2

---
mutter (3.36.4-1ubuntu2) groovy; urgency=medium

  * xrandr-scaling: Never try to set invalid screen sizes (LP: #1889090)

 -- Marco Trevisan (Treviño)   Mon, 27 Jul 2020
16:44:52 +0200

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

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

Title:
  GNOME Shell doesn't start Ubuntu session with 3.36.4 as per assertion
  in meta_monitor_manager_xrandr_update_screen_size

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

Bug description:
  Reported initially as comments of bug #1887998:

  [ Impact ]

  Ubuntu session doesn't start with some particular monitor
  configurations, as per this fatal assertion:

  Jul 27 00:30:33 jojda gnome-shell[15068]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda gnome-shell[15068]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with 
result 'core-dump'.

  [ Test case ]

  Start ubuntu session, you should be able to log-in and no error
  fallback dialog is shown.

  [ Regression potential ]

  Screen size is not set properly for the session, panning is enabled.

  
  ---

  https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1
  does not fix it. Unfortunately I cannot switch to Wayland because it
  doesn't start on my system (video card: 00:02.0 VGA compatible
  controller: Intel Corporation Iris Plus Graphics 655 (rev 01)).

  Symptom is that after waking up from sleep I get white screen of death
  that says what the bug description says ("Oh no! Something has gone
  wrong. A problem has occurred and the system can't recover. Please log
  out and try again.") and I have to click the Log out button at which
  points it lets me log in again. Sometime it does the same thing again
  right after logging in.

  Syslog message are also pretty much the same as from other comments,
  here you can see it failing twice, first up while running then right
  after re-login.

  Jul 27 00:30:31 jojda gnome-shell[4633]: gvc_mixer_card_get_index: assertion 
'GVC_IS_MIXER_CARD (card)' failed
  Jul 27 00:30:32 jojda gnome-shell[4633]: **
  Jul 27 00:30:32 jojda gnome-shell[4633]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:32 jojda gnome-shell[4633]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:32 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Scheduled 
restart job, restart counter is at 1.
  Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session 
(session: ubuntu).
  Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session (session: 
ubuntu).
  Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session.
  Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session.
  Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME Shell on X11.
  Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME Shell on X11.
  Jul 27 00:30:33 jojda systemd[4297]: Stopped GNOME Shell on X11.
  Jul 27 00:30:33 jojda systemd[4297]: Starting GNOME Shell on X11...
  Jul 27 00:30:33 jojda gnome-shell[15068]: Enabling experimental feature 
'x11-randr-fractional-scaling'
  Jul 27 00:30:33 jojda gnome-shell[15068]: **
  Jul 27 00:30:33 jojda gnome-shell[15068]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda gnome-shell[15068]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
  Jul 27 00:30:33 jojda 

Re: [Desktop-packages] [Bug 1888238] Re: Ubuntu 20.04 simple-scan brightness and contrast controls have no effect

[tkbuntu]

Greetings,
thank you for your quick response ti my bug report.
Please find attached the output from running "simple-scan -d"
Regards,Tony

On Sunday, July 26, 2020, 9:55:41 AM CDT, Bartosz Kosiorek 
<1888...@bugs.launchpad.net> wrote:  
 
 Please run application with command:

`simple-scan -d`

and attach the output.

It seems that it is duplication of the upstream issue:
https://gitlab.gnome.org/GNOME/simple-scan/-/issues/185


** Bug watch added: gitlab.gnome.org/GNOME/simple-scan/-/issues #185
  https://gitlab.gnome.org/GNOME/simple-scan/-/issues/185

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

** Also affects: simple-scan via
  https://gitlab.gnome.org/GNOME/simple-scan/-/issues/185
  Importance: Unknown
      Status: Unknown

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1888238

Title:
  Ubuntu 20.04 simple-scan brightness and contrast controls have no
  effect

Status in Simple Scan:
  Unknown
Status in simple-scan package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 simple-scan.  The Brightness and Contrast controls have
  no effect.  No matter how I position the sliders the scan image
  remains the same, ie, a dark background.  It is as if the controls are
  not 'connected'.

  Ubuntu 20.04 is up to date.  The scanner is a Cannon LiDE60.

  I have 19.10 in another partition. Simple-scan works as expected.
  Ditto for 18.04.

  Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: simple-scan 3.36.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 09:47:52 2020
  InstallationDate: Installed on 2020-05-12 (68 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Hewlett-Packard HP EliteBook 8570p
  ProcEnviron:
  PATH=(custom, no user)
  XDG_RUNTIME_DIR=
  LANG=en_US.UTF-8
  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=dc547d11-1deb-404b-988a-a88d4772e66d ro quiet splash vt.handoff=7
  SimpleScanLog:
  
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ICF Ver. F.32
  dmi.board.name: 17A7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 42.32
  dmi.chassis.asset.tag: 8022456
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.32:bd12/05/2012:svnHewlett-Packard:pnHPEliteBook8570p:pvrA1029D1102:rvnHewlett-Packard:rn17A7:rvrKBCVersion42.32:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 8570p
  dmi.product.sku: D2C13UP#ABA
  dmi.product.version: A1029D1102
  dmi.sys.vendor: Hewlett-Packard

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

** Attachment added: "=?UTF-8?b?MTg4ODIzOC1VYnVudHUyMDA0LUNhbm5vbkxpREUudHh0?="
   
https://bugs.launchpad.net/bugs/1888238/+attachment/5396370/+files/%3D%3FUTF-8%3Fb%3FMTg4ODIzOC1VYnVudHUyMDA0LUNhbm5vbkxpREUudHh0%3F%3D

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

Title:
  Ubuntu 20.04 simple-scan brightness and contrast controls have no
  effect

Status in Simple Scan:
  Unknown
Status in simple-scan package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 simple-scan.  The Brightness and Contrast controls have
  no effect.  No matter how I position the sliders the scan image
  remains the same, ie, a dark background.  It is as if the controls are
  not 'connected'.

  Ubuntu 20.04 is up to date.  The scanner is a Cannon LiDE60.

  I have 19.10 in another partition. Simple-scan works as expected.
  Ditto for 18.04.

  Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: simple-scan 3.36.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 09:47:52 2020
  InstallationDate: Installed on 2020-05-12 (68 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Hewlett-Packard HP EliteBook 8570p
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=dc547d11-1deb-404b-988a-a88d4772e66d ro quiet splash vt.handoff=7
  SimpleScanLog:
   
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh 

[Desktop-packages] [Bug 1883819] Re: Update to 3.36.3

[Bartosz Kosiorek]

I have tested simple-scan from proposed:

$ apt-cache policy simple-scan
simple-scan:
  Installed: 3.36.3-0ubuntu0.20.04.0
  Candidate: 3.36.3-0ubuntu0.20.04.0
  Version table:
 *** 3.36.3-0ubuntu0.20.04.0 100
100 /var/lib/dpkg/status
 3.36.0-0ubuntu1 500
500 http://pl.archive.ubuntu.com/ubuntu focal/main amd64 Packages

It is working perfectly fine for me. Tested with HP Laser MFP 135a

** Changed in: simple-scan (Ubuntu)
 Assignee: (unassigned) => Bartosz Kosiorek (gang65)

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

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

Title:
  Update to 3.36.3

Status in simple-scan package in Ubuntu:
  Confirmed
Status in simple-scan source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  GNOME upstream have released a new stable version of simple-scan.

  Overview of changes in simple-scan 3.36.3

    * Change the size of the paper to avoid visual glitches.
    * Disable possibility of scanning if no device is found, to avoid 
unnecessary
  errors.

  Overview of changes in simple-scan 3.36.2.1

    * Revert the higher bit depth text scans changes - they aren't working with
  PDF saving.

  Overview of changes in simple-scan 3.36.2

    * Use higher bit depth on text scans.
    * Fix size of first page on second scan.
    * Don't interrupt scanning if the device is busy.
    * Support saving files to FUSE file systems.
    * Update known USB scanner IDs.
    * Add initial Lexmark printers support.
    * Add ADF duplex support for Brother DS-720.
    * Fix setting source for Epson scanner.

  Overview of changes in simple-scan 3.36.1

    * Stop disabling compression to fix slow scanning

  [ QA ]

  GNOME has a micro release exception that covers this package.

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

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

  [ Regression Potential ]

  Changes could break existing functionality. Issue would be confined to
  simple-scan app.

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

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

[Desktop-packages] [Bug 1888238] Re: Ubuntu 20.04 simple-scan brightness and contrast controls have no effect

[Bartosz Kosiorek]

** Changed in: simple-scan (Ubuntu)
 Assignee: (unassigned) => Bartosz Kosiorek (gang65)

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

Title:
  Ubuntu 20.04 simple-scan brightness and contrast controls have no
  effect

Status in Simple Scan:
  Unknown
Status in simple-scan package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 simple-scan.  The Brightness and Contrast controls have
  no effect.  No matter how I position the sliders the scan image
  remains the same, ie, a dark background.  It is as if the controls are
  not 'connected'.

  Ubuntu 20.04 is up to date.  The scanner is a Cannon LiDE60.

  I have 19.10 in another partition. Simple-scan works as expected.
  Ditto for 18.04.

  Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: simple-scan 3.36.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 09:47:52 2020
  InstallationDate: Installed on 2020-05-12 (68 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Hewlett-Packard HP EliteBook 8570p
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=dc547d11-1deb-404b-988a-a88d4772e66d ro quiet splash vt.handoff=7
  SimpleScanLog:
   
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ICF Ver. F.32
  dmi.board.name: 17A7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 42.32
  dmi.chassis.asset.tag: 8022456
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.32:bd12/05/2012:svnHewlett-Packard:pnHPEliteBook8570p:pvrA1029D1102:rvnHewlett-Packard:rn17A7:rvrKBCVersion42.32:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 8570p
  dmi.product.sku: D2C13UP#ABA
  dmi.product.version: A1029D1102
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1551515] Re: My phone's bluetooth is displayed dozens of times under the network list (wifi icon)

[teo1978]

Still an issue in 20.04.

Fucking unbelievable.

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

Title:
  My phone's bluetooth  is displayed dozens of times under the network
  list (wifi icon)

Status in One Hundred Papercuts:
  Confirmed
Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I can hardly even start describing how screwed up this is.
  Have a look at the screenshot.

  I had seen this before and hadn't even realized that "XT1039 Network"
  repeated like 37 times had something to do with my own Android phone,
  a motorola Moto G. Needless to say I have only one.

  Out of curiosity I clicked on one of "them" (thinking this was some
  neighboor's device, obviously suspecting it was just one device
  repeated several times because of a bug), and then my phone vibrated
  prompting me whether to accept the connection from the computer.

  Which I did. As a result, the bluetooth indicator next to the network
  indicator showed a lock icon for a fraction of a second, which
  immediately disappeared. I guess that means that the computer and the
  phone peered via bluetooth for a few instants. At the same time, the
  wifi icon started animating (as if the computer was connecting to a
  wifi network... or a network of any kind I guess, since the same
  stupidly designed wifi-like animation is used when connecting to LAN
  via an ethernet cable). After that, the small lock below the bluetooth
  icon disappeared, the wifi icon stopped animating and went back to its
  normal "connected" status (I was previously and still connected to my
  home router's wifi network), and a baloon saying "Disconnected [NL]
  Network" appeared and disappeared.

  Then I repeated the test several times with the same result, except
  that the phone didn't prompt me any more to accept the connection.

  
  This is totally screwed up in several ways.

  First, there's no reason "XT1039 Network" should be listed AT ALL
  together with wifi and ethernet networks. What kind of "network" is it
  supposed to be?? Of course I have not turned on bluetooth tethering on
  the phone, and bluetooth connection to the phone is already available
  under the bluetooth indicator.

  If it makes any sense at all to show the mobile device as a "network" 
alongside with wifi and cable networks because, well, bluetooth is a network as 
well, then
  1) the list of bluetooth "networks" should have a header, just like "wifi 
networks" and "ethernet network". Right now, there is just a list of networks 
that you don't know what kind they are
  2) the device should be only listed once, not 37  times
  3) I also suspect the 3 items called just "network" are related
  4) If it is there at all, it must work. What is it supposed to do? The same 
as unfolding the menu under the Bluetooth indicator, hovering on the device 
there (which is listed only once there) and turning on the "Connection" switch? 
That one does work. This one (in the list of networks) doesn't. And if it is 
supposed to do something different, it's clearly failing as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu5.2
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  1 03:29:50 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-10-11 (871 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.167  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to wily on 2016-01-18 (42 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-20T16:52:59.722501
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation

[mistr]

This bug is still present in a fresh install of Ubuntu 20.04.1 LTS on a
Lenovo T510.

Nvidia driver is 340.108

The work-around mentioned in #73 is working.

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend or
  hibernation

Status in GNOME Shell:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Disco:
  Won't Fix
Status in mutter source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  The Nvidia (Xorg) driver corrupts the desktop wallpaper (by design
  (1)) upon resuming from suspend. This creates a poor user experience
  and gives the impression of severe memory corruption.

  (1)
  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  [Test Case]

  0. Set up an Nvidia-only system using the proprietary Nvidia Xorg driver.
  1. Suspend and resume the machine.
  Expect: The wallpaper still looks like it did before suspending.

  [Regression Potential]

  Low. The exact same patch is in Gnome 3.34 (Ubuntu 19.10) already and
  has been used for a couple of months without issue.

  [Original Report]

  https://trello.com/c/i5hENxSO

  Every other wake from sleep presents a corrupted screen with no unlock
  app.  There's a dock and system menu on a black background with pixel
  garbage.  Some personal information in the dock's large window
  thumbnails.  Bitmap garbage flashes on the screen when interacting
  with anything.  Only workaround is doing another sleep-wake cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:4b:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  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: Thu Dec 20 22:19:29 2018
  DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-11-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-12-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
  InstallationDate: Installed on 2018-10-28 (54 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: X99P-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  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.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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  

[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen

[Damiön la Bagh]

As recommended by the Gnome-shell developers a bug upstream with Mutter is 
opened.
https://gitlab.gnome.org/GNOME/mutter/-/issues/1356

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

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

Title:
  Ubuntu 20.04 gnome-shell places windows on second screen when started
  from primary screen

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

Bug description:
  Ubuntu 20.04 LTS

  gnome-shell:
Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2

  What I expected to happen:
  When clicking a button on the primary screen to open a new window in any 
application, that window should always open on the same monitor. 

  What happened instead:
  Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary 
monitor.

  Why this is a problem:
  My setup are Point of Sale terminals and the primary (a touchscreen) and 
secondary monitors are back to back. When the cashier presses the payment type 
button, the payment type pop-up is opening on the secondary screen which is 
displayed to the customer and not accessible to the cashier who needs to 
complete the transaction. The cashier can't move the pop-up on their own as 
there is no keyboard access (all buttons needed are in the application it 
self), and the touchscreen touches on itself (most of the time).   

  In the past I was able to fix this with devilspie. As this problem has been 
around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell.
   But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps 
opening all the windows on the secondary screen. 

  I've tried various gnome extensions and gnome-tweaks but none of them
  will open all windows (except the customer display) on the primary
  monitor only.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.3-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 19 01:21:39 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-14 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  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/1888098/+subscriptions

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

[Desktop-packages] [Bug 1889054] Re: No audio on TRX40 platform

[sohail]

I'm not sure if this is a duplicate because the problem is solved for me
with 5.4 kernel on Ubuntu.

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

Title:
  No audio on TRX40 platform

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have Ubuntu 20.04 running on a computer based on AMD Threadripper
  3960x, TRX40 platform (Gigabyte TRX40 AORUS PRO). Audio hasn't worked
  so far.

  I read about audio problems on this platform from the beginning but
  they should be fixed in kernel 5.6 according to this
  https://www.phoronix.com/scan.php?page=news_item=Linux-AMD-TRX40
  -Audio-Quirks

  Kernel bug reports should be related to these ones:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873
  https://bugzilla.kernel.org/show_bug.cgi?id=206543

  Since it should be fixed in recent kernel versions, I guess the
  solution for Ubuntu 20.04 using 5.4 kernel is backporting the fixes.

  Is Ubuntu planning to do this?

  Thanks
  Eduardo

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jul 27 10:41:15 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-03-05 (143 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to focal on 2020-04-06 (111 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eduardo1907 F pulseaudio
   /dev/snd/controlC0:  eduardo1907 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-05 (144 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-06 (112 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: TRX40 AORUS PRO WIFI
  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.:bvrF2:bd10/24/2019:svnGigabyteTechnologyCo.,Ltd.:pnTRX40AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnTRX40AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: TRX40 AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1173150] Re: Can't turn off 'Airplane Mode' after toggling hardware wifi switch

[Eduard Masip]

The problem it keeps in Ubuntu 20.04
In my case I use a Notebook HP 15s-fq1042ns, it uses a iwlwifi driver.

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

Title:
  Can't turn off 'Airplane Mode' after toggling hardware wifi switch

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

Bug description:
  Airplane Mode is stuck on 'On' after I turn off + turn on wifi via the
  hardware switch on my laptop (Asus N53SV-S1827V), resulting in having
  no wifi. If I go to 'Network' and turn off Airplane Mode the switch
  does flip visually (though wifi doesn't start connecting), but when I
  reopen the Network window the switch depicts Airplane mode to be on
  again.

  I tried 'sudo rfkill unblock all' but this doesn't solve it. I have to
  restart my laptop after which Airplane Mode is still on, but now I can
  effectively toggle the switch in the Network window. This results in a
  crash of the Network window, but wifi starts to connect again and when
  reopening the Network window it shows that Airplane Mode is off.

  The above behavior doesn't happen when I turn off wifi via the
  software switch, so it must be related to toggling the hardware
  switch.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.4.0-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40
  Uname: Linux 3.2.0-40-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.2
  Architecture: amd64
  Date: Fri Apr 26 13:41:32 2013
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  IpRoute:
   default via 192.168.1.254 dev eth0  proto static
   169.254.0.0/16 dev eth0  scope link  metric 1000
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.67  metric 1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/1
   wlan0  802-11-wireless   unavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN
   running 0.9.4.0connected   enabled   enabled 
disabled   enabled enabled

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

-- 
Mailing list: https://launchpad.net/~desktop-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]

** Summary changed:

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

-- 
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:
  In Progress
Status in chromium-browser source package in Focal:
  In Progress

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 1881586] Re: Add support for the new NVIDIA -server driver series

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-drivers-common -
1:0.8.4~0.20.04.2

---
ubuntu-drivers-common (1:0.8.4~0.20.04.2) focal; urgency=medium

  * gpu-manager.c:
- Use the full multiarch path for the X11 libraries.

ubuntu-drivers-common (1:0.8.4~0.20.04.1) focal; urgency=medium

  * UbuntuDrivers/detect.py,
detect-plugins/sl-modem.py:
- Avoid triggering test_static.py
  with "E741 ambiguous variable name 'l'" error.
  * ubuntu-drivers:
- Rework the argument parser to allow passing in
  driver and vendor for the "install" case
  (LP: #1881586).
- Do not print an error when linux-modules cannot
  be found. This prevents the ubuntu-drivers tools
  from printing misleading warnings, as seen in
  LP:#1882402.
- Add support for the new -server NVIDIA drivers
  (LP: #1881586).
  * debian/control:
- Depend on python3-click (for the argument
  parsing code).
- Drop dependency on dpkg-dev (LP: #1880564).
  * gpu-manager.c:
- Add get_system_architecture() (to drop the
  dpkg-dev dependency).

 -- Alberto Milone   Mon, 27 Jul 2020
16:10:25 +0200

** Changed in: ubuntu-drivers-common (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Add support for the new NVIDIA -server driver series

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  In Progress
Status in ubuntu-drivers-common source package in Focal:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The ubuntu drivers tool requires support for the new NVIDIA -server
  series (introduced by LP: #1881137)

  As already made possible when passing in the "--gpgpu" to the
  "install" argument, ubuntu drivers should be consistent and allow
  specifying a driver series regardless of whether the --gpgpu argument
  is used or not. The new parser code takes care of this.

  [Test Case]

  1) Enable the -proposed repository, and install the new ubuntu-
  drivers-common (0.8.4~0.20.04.1).

  2) Check that specifying an NVIDIA driver flavour works (e.g. "ubuntu-
  drivers install nvidia:440", if your card is supported by the driver)

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  4) Remove all the nvidia drivers:
  sudo apt-get --purge remove '*nvidia*'

  5) Test the auto-detection:
  ubuntu-drivers install

  6) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  7) Check that the correct driver was installed for your card:
  ubuntu-drivers debug

  [Regression Potential]
  Medium-Low. The new code should not affect the current functioning of the 
ubuntu-drivers tool.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1881586/+subscriptions

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

[Desktop-packages] [Bug 1848951] Re: High CPU when just moving the mouse

[Jegor van Opdorp]

still affects GNOME Shell 3.36.3

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

Title:
  High CPU when just moving the mouse

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

Bug description:
  I have installed fresh Ubuntu 18.04.03 on my PC. Previously I had
  Ubuntu 16.04 version but didn't have any such problems with the cpu
  usage.

  But I have saw in terminal that somehow the processes Xorg and gnome-
  shell use always 20% when just moving the mouse around for 18.04
  version.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 20:54:50 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / 
R7 250X] [1002:683d] (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 
[1462:2710]
  InstallationDate: Installed on 2019-10-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D2V
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D2V
  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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1881586] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for ubuntu-drivers-common
has completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Add support for the new NVIDIA -server driver series

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  In Progress
Status in ubuntu-drivers-common source package in Focal:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The ubuntu drivers tool requires support for the new NVIDIA -server
  series (introduced by LP: #1881137)

  As already made possible when passing in the "--gpgpu" to the
  "install" argument, ubuntu drivers should be consistent and allow
  specifying a driver series regardless of whether the --gpgpu argument
  is used or not. The new parser code takes care of this.

  [Test Case]

  1) Enable the -proposed repository, and install the new ubuntu-
  drivers-common (0.8.4~0.20.04.1).

  2) Check that specifying an NVIDIA driver flavour works (e.g. "ubuntu-
  drivers install nvidia:440", if your card is supported by the driver)

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  4) Remove all the nvidia drivers:
  sudo apt-get --purge remove '*nvidia*'

  5) Test the auto-detection:
  ubuntu-drivers install

  6) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  7) Check that the correct driver was installed for your card:
  ubuntu-drivers debug

  [Regression Potential]
  Medium-Low. The new code should not affect the current functioning of the 
ubuntu-drivers tool.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1881586/+subscriptions

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

[Desktop-packages] [Bug 1880564] Re: ubuntu-drivers-common now pulls in build tools on end-user systems

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-drivers-common -
1:0.8.4~0.20.04.2

---
ubuntu-drivers-common (1:0.8.4~0.20.04.2) focal; urgency=medium

  * gpu-manager.c:
- Use the full multiarch path for the X11 libraries.

ubuntu-drivers-common (1:0.8.4~0.20.04.1) focal; urgency=medium

  * UbuntuDrivers/detect.py,
detect-plugins/sl-modem.py:
- Avoid triggering test_static.py
  with "E741 ambiguous variable name 'l'" error.
  * ubuntu-drivers:
- Rework the argument parser to allow passing in
  driver and vendor for the "install" case
  (LP: #1881586).
- Do not print an error when linux-modules cannot
  be found. This prevents the ubuntu-drivers tools
  from printing misleading warnings, as seen in
  LP:#1882402.
- Add support for the new -server NVIDIA drivers
  (LP: #1881586).
  * debian/control:
- Depend on python3-click (for the argument
  parsing code).
- Drop dependency on dpkg-dev (LP: #1880564).
  * gpu-manager.c:
- Add get_system_architecture() (to drop the
  dpkg-dev dependency).

 -- Alberto Milone   Mon, 27 Jul 2020
16:10:25 +0200

** Changed in: ubuntu-drivers-common (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  ubuntu-drivers-common now pulls in build tools on end-user systems

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Released

Bug description:
  SRU Request:

  [Test Case]

  1) Uninstall the dpkg-dev package.

  2) Enable the -proposed repository, and install the new ubuntu-
  drivers-common (0.8.4~0.20.04.1).

  3) Check that the dpkg-dev package was not installed.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low. The new get_system_architecture() function is very small, and replaces 
dpkg-architecture for our use-case.
  ___
  In bug 1875339, a depends on dpkg-dev was added. This is pulling in all of 
build-essential on upgrades (or just binutils and make and patch if you pass 
--no-install-recommends).

  This needs to be reverted and fixed differently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1880564/+subscriptions

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

[Desktop-packages] [Bug 1880564] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for ubuntu-drivers-common
has completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  ubuntu-drivers-common now pulls in build tools on end-user systems

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Released

Bug description:
  SRU Request:

  [Test Case]

  1) Uninstall the dpkg-dev package.

  2) Enable the -proposed repository, and install the new ubuntu-
  drivers-common (0.8.4~0.20.04.1).

  3) Check that the dpkg-dev package was not installed.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low. The new get_system_architecture() function is very small, and replaces 
dpkg-architecture for our use-case.
  ___
  In bug 1875339, a depends on dpkg-dev was added. This is pulling in all of 
build-essential on upgrades (or just binutils and make and patch if you pass 
--no-install-recommends).

  This needs to be reverted and fixed differently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1880564/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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] [NEW] [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]

Public bug reported:

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.

** Affects: chromium-browser (Ubuntu)
 Importance: High
 Assignee: Olivier Tilloy (osomon)
 Status: In Progress

** Affects: chromium-browser (Ubuntu Focal)
 Importance: High
 Assignee: Olivier Tilloy (osomon)
 Status: In Progress

** Also affects: chromium-browser (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Changed in: chromium-browser (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: chromium-browser (Ubuntu Focal)
   Status: New => In Progress

-- 
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:
  In Progress
Status in chromium-browser source package in Focal:
  In Progress

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 1889054] Re: No audio on TRX40 platform

[Eduardo]

I have to say that I have tried the audio through HDMI and it works fine

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

Title:
  No audio on TRX40 platform

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have Ubuntu 20.04 running on a computer based on AMD Threadripper
  3960x, TRX40 platform (Gigabyte TRX40 AORUS PRO). Audio hasn't worked
  so far.

  I read about audio problems on this platform from the beginning but
  they should be fixed in kernel 5.6 according to this
  https://www.phoronix.com/scan.php?page=news_item=Linux-AMD-TRX40
  -Audio-Quirks

  Kernel bug reports should be related to these ones:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873
  https://bugzilla.kernel.org/show_bug.cgi?id=206543

  Since it should be fixed in recent kernel versions, I guess the
  solution for Ubuntu 20.04 using 5.4 kernel is backporting the fixes.

  Is Ubuntu planning to do this?

  Thanks
  Eduardo

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jul 27 10:41:15 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-03-05 (143 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to focal on 2020-04-06 (111 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eduardo1907 F pulseaudio
   /dev/snd/controlC0:  eduardo1907 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-05 (144 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-06 (112 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: TRX40 AORUS PRO WIFI
  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.:bvrF2:bd10/24/2019:svnGigabyteTechnologyCo.,Ltd.:pnTRX40AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnTRX40AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: TRX40 AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1881586] Re: Add support for the new NVIDIA -server driver series

[Alberto Milone]

Calling "ubuntu-drivers install" picks the correct UDA driver. I also
tested specifying the driver manually, with "ubuntu-drivers install
nvidia:440-server", and I got the correct driver again.

:~$ apt-cache policy ubuntu-drivers-common
ubuntu-drivers-common:
  Installed: 1:0.8.4~0.20.04.2
  Candidate: 1:0.8.4~0.20.04.2
  Version table:
 *** 1:0.8.4~0.20.04.2 400
400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 1:0.8.1.1 500
500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
 1:0.8.1 500
500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
 1:0.8.1~ppa3 500
500 http://ppa.launchpad.net/albertomilone/u-d-c-release/ubuntu 
focal/main amd64 Packages

:~$ apt-cache policy dpkg-dev
dpkg-dev:
  Installed: (none)
  Candidate: 1.19.7ubuntu3
  Version table:
 1.19.7ubuntu3 500
500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
500 http://it.archive.ubuntu.com/ubuntu focal/main i386 Packages
100 /var/lib/dpkg/status


:~$ prime-select query
nvidia

:~$ nvidia-smi
Mon Jul 27 18:16:39 2020   
+-+
| NVIDIA-SMI 440.95.01Driver Version: 440.95.01CUDA Version: 10.2 |
|---+--+--+
| GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. |
|===+==+==|
|   0  GeForce RTX 2060Off  | :01:00.0 Off |  N/A |
| N/A   44CP8 3W /  N/A |452MiB /  5934MiB |  0%  Default |
+---+--+--+
   
+-+
| Processes:   GPU Memory |
|  GPU   PID   Type   Process name Usage  |
|=|
|0  1107  G   /usr/lib/xorg/Xorg   134MiB |
|0  1656  G   /usr/lib/xorg/Xorg   135MiB |
|0  1906  G   /usr/bin/gnome-shell 165MiB |
+-+

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

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

Title:
  Add support for the new NVIDIA -server driver series

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  In Progress
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]

  The ubuntu drivers tool requires support for the new NVIDIA -server
  series (introduced by LP: #1881137)

  As already made possible when passing in the "--gpgpu" to the
  "install" argument, ubuntu drivers should be consistent and allow
  specifying a driver series regardless of whether the --gpgpu argument
  is used or not. The new parser code takes care of this.

  [Test Case]

  1) Enable the -proposed repository, and install the new ubuntu-
  drivers-common (0.8.4~0.20.04.1).

  2) Check that specifying an NVIDIA driver flavour works (e.g. "ubuntu-
  drivers install nvidia:440", if your card is supported by the driver)

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  4) Remove all the nvidia drivers:
  sudo apt-get --purge remove '*nvidia*'

  5) Test the auto-detection:
  ubuntu-drivers install

  6) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  7) Check that the correct driver was installed for your card:
  ubuntu-drivers debug

  [Regression Potential]
  Medium-Low. The new code should not affect the current functioning of the 
ubuntu-drivers tool.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1881586/+subscriptions

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

[Desktop-packages] [Bug 1889054] Re: No audio on TRX40 platform

[Daniel Letzeisen]

** Also affects: linux-oem-5.6 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-oem-5.6 (Ubuntu)
   Status: New => Confirmed

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

Title:
  No audio on TRX40 platform

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have Ubuntu 20.04 running on a computer based on AMD Threadripper
  3960x, TRX40 platform (Gigabyte TRX40 AORUS PRO). Audio hasn't worked
  so far.

  I read about audio problems on this platform from the beginning but
  they should be fixed in kernel 5.6 according to this
  https://www.phoronix.com/scan.php?page=news_item=Linux-AMD-TRX40
  -Audio-Quirks

  Kernel bug reports should be related to these ones:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873
  https://bugzilla.kernel.org/show_bug.cgi?id=206543

  Since it should be fixed in recent kernel versions, I guess the
  solution for Ubuntu 20.04 using 5.4 kernel is backporting the fixes.

  Is Ubuntu planning to do this?

  Thanks
  Eduardo

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jul 27 10:41:15 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-03-05 (143 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to focal on 2020-04-06 (111 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eduardo1907 F pulseaudio
   /dev/snd/controlC0:  eduardo1907 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-05 (144 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-06 (112 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: TRX40 AORUS PRO WIFI
  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.:bvrF2:bd10/24/2019:svnGigabyteTechnologyCo.,Ltd.:pnTRX40AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnTRX40AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: TRX40 AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1880564] Re: ubuntu-drivers-common now pulls in build tools on end-user systems

[Alberto Milone]

1:0.8.4~0.20.04.2 solves the problem, and LP: #1875339 is definitely
fixed too:

:~$ apt-cache policy ubuntu-drivers-common
ubuntu-drivers-common:
  Installed: 1:0.8.4~0.20.04.2
  Candidate: 1:0.8.4~0.20.04.2
  Version table:
 *** 1:0.8.4~0.20.04.2 400
400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 1:0.8.1.1 500
500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
 1:0.8.1 500
500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
 1:0.8.1~ppa3 500
500 http://ppa.launchpad.net/albertomilone/u-d-c-release/ubuntu 
focal/main amd64 Packages

:~$ apt-cache policy dpkg-dev
dpkg-dev:
  Installed: (none)
  Candidate: 1.19.7ubuntu3
  Version table:
 1.19.7ubuntu3 500
500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
500 http://it.archive.ubuntu.com/ubuntu focal/main i386 Packages
100 /var/lib/dpkg/status


:~$ prime-select query
nvidia

:~$ nvidia-smi
Mon Jul 27 18:16:39 2020   
+-+
| NVIDIA-SMI 440.95.01Driver Version: 440.95.01CUDA Version: 10.2 |
|---+--+--+
| GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. |
|===+==+==|
|   0  GeForce RTX 2060Off  | :01:00.0 Off |  N/A |
| N/A   44CP8 3W /  N/A |452MiB /  5934MiB |  0%  Default |
+---+--+--+
   
+-+
| Processes:   GPU Memory |
|  GPU   PID   Type   Process name Usage  |
|=|
|0  1107  G   /usr/lib/xorg/Xorg   134MiB |
|0  1656  G   /usr/lib/xorg/Xorg   135MiB |
|0  1906  G   /usr/bin/gnome-shell 165MiB |
+-+


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

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

Title:
  ubuntu-drivers-common now pulls in build tools on end-user systems

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed

Bug description:
  SRU Request:

  [Test Case]

  1) Uninstall the dpkg-dev package.

  2) Enable the -proposed repository, and install the new ubuntu-
  drivers-common (0.8.4~0.20.04.1).

  3) Check that the dpkg-dev package was not installed.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low. The new get_system_architecture() function is very small, and replaces 
dpkg-architecture for our use-case.
  ___
  In bug 1875339, a depends on dpkg-dev was added. This is pulling in all of 
build-essential on upgrades (or just binutils and make and patch if you pass 
--no-install-recommends).

  This needs to be reverted and fixed differently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1880564/+subscriptions

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

[Desktop-packages] [Bug 1889091] Re: When saving a copy save dialog cannot create directory on nfs share

[Sebastien Bacher]

you could also try to disabling the apparmor profile with

$ sudo apparmor_parser -R /etc/apparmor.d/usr.bin.evince

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

Title:
  When saving a copy save dialog cannot create directory on nfs share

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  i stumbled upon a weird oddity with evince...

  # Steps creating the problem

  1. I downloaded a pdf document from the internet using firefox.
  2. Firefox offered to open the pdf in a document reader
  3. Evince opened and displayed the pdf (correctly)
  4. I used the hamburger menu and choose "Speichern unter" ("save as")
  5. Filedialog opened. I navigated to an nfs mounted directory.
  6. I ordered "Ordner anlegen" ("create folder") via the + symbol
  7. I am prompted for the name of the new folder
  8. It sais: "Der Ordner kann nicht angelegt werden -- Fehler beim ERstellen 
des Ordners <...> Keine Berechtigung" ("The folder cannot be created - Error 
creating the folder -- Not Authorized"
  9. If I go to the terminal and mkdir the folder is created all right. (I 
expected that the directory would be created -- if chmod is set correctly and 
the shell can do it evince should also be able to do it...)

  # More info

  My `/etc/fstab` reads as follows:

  ```
  # /etc/fstab: static file system information.
  #
  # 

  192.168.178.52:/home /nfs nfs noauto,user,exec 0 0
  <...>
  ```

  192.168.178.52 (nathan) uses the kernel-nfs-server and the following 
`/etc/exports`-file:
  ```
  # /etc/exports: the access control list for filesystems which may be exported
  # to NFS clients.  See exports(5).
  #
  # Example for NFSv2 and NFSv3:
  # /srv/homes   hostname1(rw,sync,no_subtree_check) 
hostname2(ro,sync,no_subtree_check)
  #
  # Example for NFSv4:
  # /srv/nfs4gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
  # /srv/nfs4/homes  gss/krb5i(rw,sync,no_subtree_check)
  #
  # /etc/exports: the access control list for filesystems which may be exported
  # to NFS clients.  See exports(5).
  #
  /home/ *(rw,sync,insecure,no_root_squash)
  <...>
  ```

  Which is surely not too strict but rather to permissive... :o/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: evince 3.36.5-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.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Mon Jul 27 16:12:17 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1847196] Re: BackendException: PyDrive backend requires PyDrive installation

[Sebastien Bacher]

Thew new Ubuntu series includes pydrive now

** Changed in: deja-dup (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  BackendException: PyDrive backend requires PyDrive installation

Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  I have deja-dup configured to do a back up to Google Drive. This
  worked until like a month or two ago, at which point it started to
  print

  BackendException: PyDrive backend requires PyDrive installation.  Please read 
the manpage for setup details.
  Exception: No module named 'pydrive'

  There does not seem to be a pydrive module in the archive; and I
  thought it is using GOA anyway?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: deja-dup 40.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct  8 09:02:38 2019
  InstallationDate: Installed on 2018-03-14 (572 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to eoan on 2018-11-20 (321 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1847196/+subscriptions

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

[Desktop-packages] [Bug 1889091] Re: When saving a copy save dialog cannot create directory on nfs share

[Sebastien Bacher]

Thank you for your bug report. The fileselector is from GTK, it should
have the same issue in other applications unless it's the apparmor
profile blocking the access ... could you do

$ journalctl -f

try to create the directory and copy any warning or error printed in the
log?

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

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

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

Title:
  When saving a copy save dialog cannot create directory on nfs share

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  i stumbled upon a weird oddity with evince...

  # Steps creating the problem

  1. I downloaded a pdf document from the internet using firefox.
  2. Firefox offered to open the pdf in a document reader
  3. Evince opened and displayed the pdf (correctly)
  4. I used the hamburger menu and choose "Speichern unter" ("save as")
  5. Filedialog opened. I navigated to an nfs mounted directory.
  6. I ordered "Ordner anlegen" ("create folder") via the + symbol
  7. I am prompted for the name of the new folder
  8. It sais: "Der Ordner kann nicht angelegt werden -- Fehler beim ERstellen 
des Ordners <...> Keine Berechtigung" ("The folder cannot be created - Error 
creating the folder -- Not Authorized"
  9. If I go to the terminal and mkdir the folder is created all right. (I 
expected that the directory would be created -- if chmod is set correctly and 
the shell can do it evince should also be able to do it...)

  # More info

  My `/etc/fstab` reads as follows:

  ```
  # /etc/fstab: static file system information.
  #
  # 

  192.168.178.52:/home /nfs nfs noauto,user,exec 0 0
  <...>
  ```

  192.168.178.52 (nathan) uses the kernel-nfs-server and the following 
`/etc/exports`-file:
  ```
  # /etc/exports: the access control list for filesystems which may be exported
  # to NFS clients.  See exports(5).
  #
  # Example for NFSv2 and NFSv3:
  # /srv/homes   hostname1(rw,sync,no_subtree_check) 
hostname2(ro,sync,no_subtree_check)
  #
  # Example for NFSv4:
  # /srv/nfs4gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
  # /srv/nfs4/homes  gss/krb5i(rw,sync,no_subtree_check)
  #
  # /etc/exports: the access control list for filesystems which may be exported
  # to NFS clients.  See exports(5).
  #
  /home/ *(rw,sync,insecure,no_root_squash)
  <...>
  ```

  Which is surely not too strict but rather to permissive... :o/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: evince 3.36.5-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.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Mon Jul 27 16:12:17 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1882258] Re: XRDP to Ubuntu 19.10 request many popup dialog for creating a colorprofile

[Sebastien Bacher]

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

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

Title:
  XRDP to Ubuntu 19.10 request many popup dialog for creating a
  colorprofile

Status in policykit-1-gnome package in Ubuntu:
  New

Bug description:
  While searching abougt a solution I found this Blogpost which was able to 
help me in this case:
  https://c-nergy.be/blog/?p=12073

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

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

[Desktop-packages] [Bug 1889102] Re: Bug with Applications menu

[Sebastien Bacher]

Thank you for your bug report. What menu are you talking about exactly?
Could you make a screenshot or video showing the issue? (using a phone
could be a good solution in such cases)

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

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

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

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

Title:
  Bug with Applications menu

Status in gnome-shell package in Ubuntu:
  Incomplete

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

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

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

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

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

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

[Desktop-packages] [Bug 1875568] Re: The “show on” option in Ubuntu-settings-appearance-Dock has a bug

[Launchpad Bug Tracker]

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

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

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

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

Title:
  The “show on” option in Ubuntu-settings-appearance-Dock has a bug

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

Bug description:
  The “show on” option in Ubuntu-settings-appearance-Dock has a bug.
  When I would select a monitor   instead of  “All display”, nothing
  changes and it reverts to “All display” again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 10:54:55 2020
  InstallationDate: Installed on 2020-04-28 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1889054] Re: No audio on TRX40 platform

[Eduardo]

I have already tried the oem version but no luck. No sound at all. Not
sure if the patch is included or if so, if it solves the issue.

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

Title:
  No audio on TRX40 platform

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have Ubuntu 20.04 running on a computer based on AMD Threadripper
  3960x, TRX40 platform (Gigabyte TRX40 AORUS PRO). Audio hasn't worked
  so far.

  I read about audio problems on this platform from the beginning but
  they should be fixed in kernel 5.6 according to this
  https://www.phoronix.com/scan.php?page=news_item=Linux-AMD-TRX40
  -Audio-Quirks

  Kernel bug reports should be related to these ones:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873
  https://bugzilla.kernel.org/show_bug.cgi?id=206543

  Since it should be fixed in recent kernel versions, I guess the
  solution for Ubuntu 20.04 using 5.4 kernel is backporting the fixes.

  Is Ubuntu planning to do this?

  Thanks
  Eduardo

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jul 27 10:41:15 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-03-05 (143 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to focal on 2020-04-06 (111 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eduardo1907 F pulseaudio
   /dev/snd/controlC0:  eduardo1907 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-05 (144 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-06 (112 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: TRX40 AORUS PRO WIFI
  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.:bvrF2:bd10/24/2019:svnGigabyteTechnologyCo.,Ltd.:pnTRX40AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnTRX40AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: TRX40 AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1715764] Re: Flickering Screen

[Launchpad Bug Tracker]

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

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

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

Title:
  Flickering Screen

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Screen flickers particularly when I use Discord but have also
  experienced it with Minecraft. Occasionally have issues with misplaced
  pixels in slack and mozilla firefox, but much less frequently with
  firefox. Only have experienced pixels being misplayed whilst being on
  vox and maybe one or two others I'm forgetting, have not had any
  issues when using most websites.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Sep  8 00:19:34 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80a1]
  InstallationDate: Installed on 2016-09-01 (371 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b50d Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic.efi.signed 
root=UUID=93999ca7-5b83-4851-969c-5482f1b9ee8d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.77
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A1
  dmi.board.vendor: HP
  dmi.board.version: 91.1C
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.77:bd12/18/2015:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A1:rvr91.1C:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Sep  5 00:34:29 2017
  xserver.configfile: default
  xserver.errors:
   intel(0): Failed to submit rendering commands (No such file or directory), 
disabling acceleration.
   intel(0): When reporting this, please include /sys/class/drm/card0/error and 
the full dmesg.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   20049 
   vendor SDC
  xserver.version: 2:1.18.4-0ubuntu0.3

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

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

[Desktop-packages] [Bug 1889102] [NEW] Bug with Applications menu

[Treve Winchcombe]

Public bug reported:

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

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

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

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

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Bug with Applications menu

Status in xorg package in Ubuntu:
  New

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.4
  

[Desktop-packages] [Bug 1889100] [NEW] Screen bug

[Treve Winchcombe]

Public bug reported:

I have this weird screen bug that was not present on Windows, the OS I
used before Ubuntu. I have reinstalled Ubuntu but this has not fixed the
issue. When scrolling or watching a video in full screen, there are two
bars that appear in the middle of the screen widthways.

The bars are transparent but you can still see the outline of them and
they also move around slightly meaning it can be quite distracting. The
bars are not there when doing other tasks like general work like web
browsing and email unless you scroll.

It seems to only be an issue when a large part of the screen has to
refresh at any one time.

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

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


** Tags: amd64 apport-bug corruption focal ubuntu

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

Title:
  Screen bug

Status in xorg package in Ubuntu:
  New

Bug description:
  I have this weird screen bug that was not present on Windows, the OS I
  used before Ubuntu. I have reinstalled Ubuntu but this has not fixed
  the issue. When scrolling or watching a video in full screen, there
  are two bars that appear in the middle of the screen widthways.

  The bars are transparent but you can still see the outline of them and
  they also move around slightly meaning it can be quite distracting.
  The bars are not there when doing other tasks like general work like
  web browsing and email unless you scroll.

  It seems to only be an issue when a large part of the screen has to
  refresh at any one time.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 27 16:22:20 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: 

[Desktop-packages] [Bug 1889054] Re: No audio on TRX40 platform

[Daniel Letzeisen]

Eduardo. You're welcome, although I wish I could answer your question.

One thing you may want to try is the linux-oem kernel, which is based off 5.6.x:
sudo apt-get install linux-oem-20.04

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

Title:
  No audio on TRX40 platform

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have Ubuntu 20.04 running on a computer based on AMD Threadripper
  3960x, TRX40 platform (Gigabyte TRX40 AORUS PRO). Audio hasn't worked
  so far.

  I read about audio problems on this platform from the beginning but
  they should be fixed in kernel 5.6 according to this
  https://www.phoronix.com/scan.php?page=news_item=Linux-AMD-TRX40
  -Audio-Quirks

  Kernel bug reports should be related to these ones:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873
  https://bugzilla.kernel.org/show_bug.cgi?id=206543

  Since it should be fixed in recent kernel versions, I guess the
  solution for Ubuntu 20.04 using 5.4 kernel is backporting the fixes.

  Is Ubuntu planning to do this?

  Thanks
  Eduardo

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jul 27 10:41:15 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-03-05 (143 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to focal on 2020-04-06 (111 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eduardo1907 F pulseaudio
   /dev/snd/controlC0:  eduardo1907 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-05 (144 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-06 (112 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: TRX40 AORUS PRO WIFI
  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.:bvrF2:bd10/24/2019:svnGigabyteTechnologyCo.,Ltd.:pnTRX40AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnTRX40AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: TRX40 AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1889090] Re: GNOME Shell doesn't start Ubuntu session with 3.36.4 as per assertion in meta_monitor_manager_xrandr_update_screen_size

[Treviño]

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

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

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

** Changed in: mutter (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  GNOME Shell doesn't start Ubuntu session with 3.36.4 as per assertion
  in meta_monitor_manager_xrandr_update_screen_size

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

Bug description:
  Reported initially as comments of bug #1887998:

  [ Impact ]

  Ubuntu session doesn't start with some particular monitor
  configurations, as per this fatal assertion:

  Jul 27 00:30:33 jojda gnome-shell[15068]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda gnome-shell[15068]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with 
result 'core-dump'.

  [ Test case ]

  Start ubuntu session, you should be able to log-in and no error
  fallback dialog is shown.

  [ Regression potential ]

  Screen size is not set properly for the session, panning is enabled.

  
  ---

  https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1
  does not fix it. Unfortunately I cannot switch to Wayland because it
  doesn't start on my system (video card: 00:02.0 VGA compatible
  controller: Intel Corporation Iris Plus Graphics 655 (rev 01)).

  Symptom is that after waking up from sleep I get white screen of death
  that says what the bug description says ("Oh no! Something has gone
  wrong. A problem has occurred and the system can't recover. Please log
  out and try again.") and I have to click the Log out button at which
  points it lets me log in again. Sometime it does the same thing again
  right after logging in.

  Syslog message are also pretty much the same as from other comments,
  here you can see it failing twice, first up while running then right
  after re-login.

  Jul 27 00:30:31 jojda gnome-shell[4633]: gvc_mixer_card_get_index: assertion 
'GVC_IS_MIXER_CARD (card)' failed
  Jul 27 00:30:32 jojda gnome-shell[4633]: **
  Jul 27 00:30:32 jojda gnome-shell[4633]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:32 jojda gnome-shell[4633]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:32 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Scheduled 
restart job, restart counter is at 1.
  Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session 
(session: ubuntu).
  Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session (session: 
ubuntu).
  Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session.
  Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session.
  Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME Shell on X11.
  Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME Shell on X11.
  Jul 27 00:30:33 jojda systemd[4297]: Stopped GNOME Shell on X11.
  Jul 27 00:30:33 jojda systemd[4297]: Starting GNOME Shell on X11...
  Jul 27 00:30:33 jojda gnome-shell[15068]: Enabling experimental feature 
'x11-randr-fractional-scaling'
  Jul 27 00:30:33 jojda gnome-shell[15068]: **
  Jul 27 00:30:33 jojda gnome-shell[15068]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda gnome-shell[15068]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
  Jul 27 00:30:33 jojda 

[Desktop-packages] [Bug 1847196] Re: BackendException: PyDrive backend requires PyDrive installation

[Daniel Hererra Diaz]

** This bug is no longer a duplicate of bug 1852069
   Failed to backup to google drive on ubuntu 19.10

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

Title:
  BackendException: PyDrive backend requires PyDrive installation

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  I have deja-dup configured to do a back up to Google Drive. This
  worked until like a month or two ago, at which point it started to
  print

  BackendException: PyDrive backend requires PyDrive installation.  Please read 
the manpage for setup details.
  Exception: No module named 'pydrive'

  There does not seem to be a pydrive module in the archive; and I
  thought it is using GOA anyway?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: deja-dup 40.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct  8 09:02:38 2019
  InstallationDate: Installed on 2018-03-14 (572 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to eoan on 2018-11-20 (321 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1847196/+subscriptions

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

[Desktop-packages] [Bug 1889090] Re: GNOME Shell doesn't start Ubuntu session with 3.36.4 as per assertion in meta_monitor_manager_xrandr_update_screen_size

[Treviño]

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

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

Title:
  GNOME Shell doesn't start Ubuntu session with 3.36.4 as per assertion
  in meta_monitor_manager_xrandr_update_screen_size

Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Reported initially as comments of bug #1887998:

  [ Impact ]

  Ubuntu session doesn't start with some particular monitor
  configurations, as per this fatal assertion:

  Jul 27 00:30:33 jojda gnome-shell[15068]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda gnome-shell[15068]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with 
result 'core-dump'.

  [ Test case ]

  Start ubuntu session, you should be able to log-in and no error
  fallback dialog is shown.

  [ Regression potential ]

  Screen size is not set properly for the session, panning is enabled.

  
  ---

  https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1
  does not fix it. Unfortunately I cannot switch to Wayland because it
  doesn't start on my system (video card: 00:02.0 VGA compatible
  controller: Intel Corporation Iris Plus Graphics 655 (rev 01)).

  Symptom is that after waking up from sleep I get white screen of death
  that says what the bug description says ("Oh no! Something has gone
  wrong. A problem has occurred and the system can't recover. Please log
  out and try again.") and I have to click the Log out button at which
  points it lets me log in again. Sometime it does the same thing again
  right after logging in.

  Syslog message are also pretty much the same as from other comments,
  here you can see it failing twice, first up while running then right
  after re-login.

  Jul 27 00:30:31 jojda gnome-shell[4633]: gvc_mixer_card_get_index: assertion 
'GVC_IS_MIXER_CARD (card)' failed
  Jul 27 00:30:32 jojda gnome-shell[4633]: **
  Jul 27 00:30:32 jojda gnome-shell[4633]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:32 jojda gnome-shell[4633]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:32 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Scheduled 
restart job, restart counter is at 1.
  Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session 
(session: ubuntu).
  Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session (session: 
ubuntu).
  Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session.
  Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session.
  Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME Shell on X11.
  Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME Shell on X11.
  Jul 27 00:30:33 jojda systemd[4297]: Stopped GNOME Shell on X11.
  Jul 27 00:30:33 jojda systemd[4297]: Starting GNOME Shell on X11...
  Jul 27 00:30:33 jojda gnome-shell[15068]: Enabling experimental feature 
'x11-randr-fractional-scaling'
  Jul 27 00:30:33 jojda gnome-shell[15068]: **
  Jul 27 00:30:33 jojda gnome-shell[15068]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda gnome-shell[15068]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
  Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
  Jul 27 00:30:33 jojda systemd[4297]: Failed to start GNOME Shell on X11.
  Jul 27 00:30:33 jojda systemd[4297]: Dependency failed for GNOME Shell on X11.
  Jul 27 00:30:33 jojda systemd[4297]: Dependency failed for GNOME X11 Session.
  Jul 27 00:30:33 jojda systemd[4297]: Dependency failed for GNOME X11 Session 
(session: ubuntu).
  Jul 27 

[Desktop-packages] [Bug 1880564] Please test proposed package

[Łukasz Zemczak]

Hello Julian, or anyone else affected,

Accepted ubuntu-drivers-common into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-drivers-common/1:0.8.4~0.20.04.2 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.

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

Title:
  ubuntu-drivers-common now pulls in build tools on end-user systems

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed

Bug description:
  SRU Request:

  [Test Case]

  1) Uninstall the dpkg-dev package.

  2) Enable the -proposed repository, and install the new ubuntu-
  drivers-common (0.8.4~0.20.04.1).

  3) Check that the dpkg-dev package was not installed.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low. The new get_system_architecture() function is very small, and replaces 
dpkg-architecture for our use-case.
  ___
  In bug 1875339, a depends on dpkg-dev was added. This is pulling in all of 
build-essential on upgrades (or just binutils and make and patch if you pass 
--no-install-recommends).

  This needs to be reverted and fixed differently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1880564/+subscriptions

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

[Desktop-packages] [Bug 1888992] Re: [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones

[Francis Chin]

Last known working kernel: 5.4.0-33, next installable Ubuntu kernel
5.4.0-37 introduces the bug.

I have tested that saving "options snd_hda_intel power_save=0" to a file
under /etc/modprobe.d and rebooting to a kernel from -37 onwards is a
valid workaround.

Lines mentioning ALSA from
http://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_5.4.0-37.41/changelog:

  * Focal update: v5.4.40 upstream stable release (LP: #1878040)
- ALSA: hda: Match both PCI ID and SSID for driver blacklist

  * Focal update: v5.4.39 upstream stable release (LP: #1877592)
- ALSA: hda/realtek - Two front mics on a Lenovo ThinkCenter
- ALSA: usb-audio: Correct a typo of NuPrime DAC-10 USB ID
- ALSA: hda/hdmi: fix without unlocked before return
- ALSA: line6: Fix POD HD500 audio playback
- ALSA: pcm: oss: Place the plugin buffer overflow checks correctly
- ALSA: opti9xx: shut up gcc-10 range warning

  * Focal update: v5.4.37 upstream stable release (LP: #1876765)
- ALSA: hda: Release resources at error in delayed probe
- ALSA: hda: Keep the controller initialization even if no codecs found
- ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported
- ALSA: hda: call runtime_allow() for all hda controllers

  * Focal update: v5.4.36 upstream stable release (LP: #1876361)
- ALSA: usb-audio: Add Pioneer DJ DJM-250MK2 quirk
- ALSA: hda: Remove ASUS ROG Zenith from the blacklist
- ALSA: usb-audio: Add static mapping table for ALC1220-VB-based mobos
- ALSA: usb-audio: Add connector notifier delegation
- ALSA: usx2y: Fix potential NULL dereference
- ALSA: hda/realtek - Fix unexpected init_amp override
- ALSA: hda/realtek - Add new codec supported for ALC245
- ALSA: hda/hdmi: Add module option to disable audio component binding
- ALSA: usb-audio: Fix usb audio refcnt leak when getting spdif
- ALSA: usb-audio: Filter out unsupported sample rates on Focusrite devices

  * Focal update: v5.4.35 upstream stable release (LP: #1875660)
- ALSA: hda: Honor PM disablement in PM freeze and thaw_noirq ops
- ALSA: hda: Don't release card at firmware loading error

  * Support DMIC micmute LED on HP platforms (LP: #1876859)
- ALSA: hda/realtek - Introduce polarity for micmute LED GPIO
- ALSA: hda/realtek - Enable micmute LED on and HP system
- ALSA: hda/realtek - Add LED class support for micmute LED
- ALSA: hda/realtek - Fix unused variable warning w/o
  CONFIG_LEDS_TRIGGER_AUDIO

  * alsa/sof: kernel oops on the machine without Intel hdmi audio codec (a
regression in the  asoc machine driver) (LP: #1874359)
- SAUCE: ASoC: intel/skl/hda - fix oops on systems without i915 audio codec

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

Title:
  [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching
  to front jack after plugging in headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I boot my system without any sound devices plugged into any jacks;
  checking Gnome settings Sound, Output Device is "Dummy Output" (no
  other options available in drop-down list). I plug in headphones into
  the front jack and play some audio, but do not hear any sound from the
  headphones; checking Gnome settings Sound, the Output Device is still
  "Dummy Output", with no other options available.

  This is a regression from previous behaviour, when plugging in
  headphones into the front jack would automatically enable/switch to
  the front jack and its associated controller "Family 17h (Models 00h-
  0fh) HD Audio Controller" (this is the motherboard's onboard audio
  hardware).

  I can currently workaround this each time I plug in the headphones by
  installing and running pavucontrol, and under Configuration selecting
  "Analogue Stereo Output (unplugged) (unavailable)" - this option
  becomes "Analogue Stereo Output" after I select it.

  This seems to be a regression in pulseaudio after an upgrade from from
  1:13.99.1-1ubuntu3.3 to 1:13.99.1-1ubuntu3.5.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chinf  1741 F pulseaudio
   /dev/snd/pcmC1D0p:   chinf  1741 F...m pulseaudio
   /dev/snd/controlC0:  chinf  1741 F pulseaudio
   /dev/snd/timer:  chinf  1741 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 26 12:46:52 2020
  InstallationDate: Installed on 2018-10-29 (635 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: 

[Desktop-packages] [Bug 1881586] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted ubuntu-drivers-common into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-drivers-common/1:0.8.4~0.20.04.2 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.

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

Title:
  Add support for the new NVIDIA -server driver series

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  In Progress
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]

  The ubuntu drivers tool requires support for the new NVIDIA -server
  series (introduced by LP: #1881137)

  As already made possible when passing in the "--gpgpu" to the
  "install" argument, ubuntu drivers should be consistent and allow
  specifying a driver series regardless of whether the --gpgpu argument
  is used or not. The new parser code takes care of this.

  [Test Case]

  1) Enable the -proposed repository, and install the new ubuntu-
  drivers-common (0.8.4~0.20.04.1).

  2) Check that specifying an NVIDIA driver flavour works (e.g. "ubuntu-
  drivers install nvidia:440", if your card is supported by the driver)

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  4) Remove all the nvidia drivers:
  sudo apt-get --purge remove '*nvidia*'

  5) Test the auto-detection:
  ubuntu-drivers install

  6) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  7) Check that the correct driver was installed for your card:
  ubuntu-drivers debug

  [Regression Potential]
  Medium-Low. The new code should not affect the current functioning of the 
ubuntu-drivers tool.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1881586/+subscriptions

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

[Desktop-packages] [Bug 1889054] ProcEnviron.txt

[Eduardo]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1889054/+attachment/5396263/+files/ProcEnviron.txt

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

Title:
  No audio on TRX40 platform

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have Ubuntu 20.04 running on a computer based on AMD Threadripper
  3960x, TRX40 platform (Gigabyte TRX40 AORUS PRO). Audio hasn't worked
  so far.

  I read about audio problems on this platform from the beginning but
  they should be fixed in kernel 5.6 according to this
  https://www.phoronix.com/scan.php?page=news_item=Linux-AMD-TRX40
  -Audio-Quirks

  Kernel bug reports should be related to these ones:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873
  https://bugzilla.kernel.org/show_bug.cgi?id=206543

  Since it should be fixed in recent kernel versions, I guess the
  solution for Ubuntu 20.04 using 5.4 kernel is backporting the fixes.

  Is Ubuntu planning to do this?

  Thanks
  Eduardo

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jul 27 10:41:15 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-03-05 (143 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to focal on 2020-04-06 (111 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eduardo1907 F pulseaudio
   /dev/snd/controlC0:  eduardo1907 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-05 (144 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-06 (112 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: TRX40 AORUS PRO WIFI
  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.:bvrF2:bd10/24/2019:svnGigabyteTechnologyCo.,Ltd.:pnTRX40AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnTRX40AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: TRX40 AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1889054] Re: No audio on TRX40 platform

[Eduardo]

Dear Daniel,

Thanks a lot for your response and changes. Sure, I've already run the
apport-collect command.

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

Title:
  No audio on TRX40 platform

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have Ubuntu 20.04 running on a computer based on AMD Threadripper
  3960x, TRX40 platform (Gigabyte TRX40 AORUS PRO). Audio hasn't worked
  so far.

  I read about audio problems on this platform from the beginning but
  they should be fixed in kernel 5.6 according to this
  https://www.phoronix.com/scan.php?page=news_item=Linux-AMD-TRX40
  -Audio-Quirks

  Kernel bug reports should be related to these ones:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873
  https://bugzilla.kernel.org/show_bug.cgi?id=206543

  Since it should be fixed in recent kernel versions, I guess the
  solution for Ubuntu 20.04 using 5.4 kernel is backporting the fixes.

  Is Ubuntu planning to do this?

  Thanks
  Eduardo

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jul 27 10:41:15 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-03-05 (143 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to focal on 2020-04-06 (111 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eduardo1907 F pulseaudio
   /dev/snd/controlC0:  eduardo1907 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-05 (144 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-06 (112 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: TRX40 AORUS PRO WIFI
  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.:bvrF2:bd10/24/2019:svnGigabyteTechnologyCo.,Ltd.:pnTRX40AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnTRX40AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: TRX40 AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1889054] PulseList.txt

[Eduardo]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1889054/+attachment/5396264/+files/PulseList.txt

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

Title:
  No audio on TRX40 platform

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have Ubuntu 20.04 running on a computer based on AMD Threadripper
  3960x, TRX40 platform (Gigabyte TRX40 AORUS PRO). Audio hasn't worked
  so far.

  I read about audio problems on this platform from the beginning but
  they should be fixed in kernel 5.6 according to this
  https://www.phoronix.com/scan.php?page=news_item=Linux-AMD-TRX40
  -Audio-Quirks

  Kernel bug reports should be related to these ones:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873
  https://bugzilla.kernel.org/show_bug.cgi?id=206543

  Since it should be fixed in recent kernel versions, I guess the
  solution for Ubuntu 20.04 using 5.4 kernel is backporting the fixes.

  Is Ubuntu planning to do this?

  Thanks
  Eduardo

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jul 27 10:41:15 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-03-05 (143 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to focal on 2020-04-06 (111 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eduardo1907 F pulseaudio
   /dev/snd/controlC0:  eduardo1907 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-05 (144 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-06 (112 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: TRX40 AORUS PRO WIFI
  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.:bvrF2:bd10/24/2019:svnGigabyteTechnologyCo.,Ltd.:pnTRX40AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnTRX40AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: TRX40 AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1887998] Re: Update to 3.36.4 and SRU it

[Treviño]

Thanks for the reports, let's move the discussion in bug #1889090

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

Title:
  Update to 3.36.4 and SRU it

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

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.4

  [ Test case ]

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

  GNOME Shell and its components should continue working

  [ Regression potential ]

  There have been fixes in X11 screencasting and touch-interaction, so
  ensure there are no problems with those.

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

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

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

[Eduardo]

apport information

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

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

Title:
  No audio on TRX40 platform

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have Ubuntu 20.04 running on a computer based on AMD Threadripper
  3960x, TRX40 platform (Gigabyte TRX40 AORUS PRO). Audio hasn't worked
  so far.

  I read about audio problems on this platform from the beginning but
  they should be fixed in kernel 5.6 according to this
  https://www.phoronix.com/scan.php?page=news_item=Linux-AMD-TRX40
  -Audio-Quirks

  Kernel bug reports should be related to these ones:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873
  https://bugzilla.kernel.org/show_bug.cgi?id=206543

  Since it should be fixed in recent kernel versions, I guess the
  solution for Ubuntu 20.04 using 5.4 kernel is backporting the fixes.

  Is Ubuntu planning to do this?

  Thanks
  Eduardo

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jul 27 10:41:15 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-03-05 (143 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to focal on 2020-04-06 (111 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eduardo1907 F pulseaudio
   /dev/snd/controlC0:  eduardo1907 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-05 (144 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-06 (112 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: TRX40 AORUS PRO WIFI
  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.:bvrF2:bd10/24/2019:svnGigabyteTechnologyCo.,Ltd.:pnTRX40AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnTRX40AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: TRX40 AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1889090] [NEW] GNOME Shell doesn't start Ubuntu session with 3.36.4 as per assertion in meta_monitor_manager_xrandr_update_screen_size

[Treviño]

Public bug reported:

Reported initially as comments of bug #1887998:

[ Impact ]

Ubuntu session doesn't start with some particular monitor
configurations, as per this fatal assertion:

Jul 27 00:30:33 jojda gnome-shell[15068]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:33 jojda gnome-shell[15068]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with 
result 'core-dump'.

[ Test case ]

Start ubuntu session, you should be able to log-in and no error fallback
dialog is shown.

[ Regression potential ]

Screen size is not set properly for the session, panning is enabled.


---

https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1 does
not fix it. Unfortunately I cannot switch to Wayland because it doesn't
start on my system (video card: 00:02.0 VGA compatible controller: Intel
Corporation Iris Plus Graphics 655 (rev 01)).

Symptom is that after waking up from sleep I get white screen of death
that says what the bug description says ("Oh no! Something has gone
wrong. A problem has occurred and the system can't recover. Please log
out and try again.") and I have to click the Log out button at which
points it lets me log in again. Sometime it does the same thing again
right after logging in.

Syslog message are also pretty much the same as from other comments,
here you can see it failing twice, first up while running then right
after re-login.

Jul 27 00:30:31 jojda gnome-shell[4633]: gvc_mixer_card_get_index: assertion 
'GVC_IS_MIXER_CARD (card)' failed
Jul 27 00:30:32 jojda gnome-shell[4633]: **
Jul 27 00:30:32 jojda gnome-shell[4633]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:32 jojda gnome-shell[4633]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:32 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Scheduled restart 
job, restart counter is at 1.
Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session (session: 
ubuntu).
Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session (session: 
ubuntu).
Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session.
Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session.
Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME Shell on X11.
Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME Shell on X11.
Jul 27 00:30:33 jojda systemd[4297]: Stopped GNOME Shell on X11.
Jul 27 00:30:33 jojda systemd[4297]: Starting GNOME Shell on X11...
Jul 27 00:30:33 jojda gnome-shell[15068]: Enabling experimental feature 
'x11-randr-fractional-scaling'
Jul 27 00:30:33 jojda gnome-shell[15068]: **
Jul 27 00:30:33 jojda gnome-shell[15068]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:33 jojda gnome-shell[15068]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
Jul 27 00:30:33 jojda systemd[4297]: Failed to start GNOME Shell on X11.
Jul 27 00:30:33 jojda systemd[4297]: Dependency failed for GNOME Shell on X11.
Jul 27 00:30:33 jojda systemd[4297]: Dependency failed for GNOME X11 Session.
Jul 27 00:30:33 jojda systemd[4297]: Dependency failed for GNOME X11 Session 
(session: ubuntu).
Jul 27 00:30:33 jojda systemd[4297]: gnome-session-x11@ubuntu.target: Job 
gnome-session-x11@ubuntu.target/start failed with result 'dependency'.
Jul 27 00:30:33 jojda systemd[4297]: gnome-session-x11.target: Job 
gnome-session-x11.target/start failed with result 'dependency'.
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.target: Job 
gnome-shell-x11.target/start failed with result 'dependency'.
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Scheduled restart 
job, restart counter is at 2.
Jul 27 00:30:33 jojda 

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

[Eduardo]

apport information

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

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

Title:
  No audio on TRX40 platform

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have Ubuntu 20.04 running on a computer based on AMD Threadripper
  3960x, TRX40 platform (Gigabyte TRX40 AORUS PRO). Audio hasn't worked
  so far.

  I read about audio problems on this platform from the beginning but
  they should be fixed in kernel 5.6 according to this
  https://www.phoronix.com/scan.php?page=news_item=Linux-AMD-TRX40
  -Audio-Quirks

  Kernel bug reports should be related to these ones:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873
  https://bugzilla.kernel.org/show_bug.cgi?id=206543

  Since it should be fixed in recent kernel versions, I guess the
  solution for Ubuntu 20.04 using 5.4 kernel is backporting the fixes.

  Is Ubuntu planning to do this?

  Thanks
  Eduardo

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jul 27 10:41:15 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-03-05 (143 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to focal on 2020-04-06 (111 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eduardo1907 F pulseaudio
   /dev/snd/controlC0:  eduardo1907 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-05 (144 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-06 (112 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: TRX40 AORUS PRO WIFI
  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.:bvrF2:bd10/24/2019:svnGigabyteTechnologyCo.,Ltd.:pnTRX40AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnTRX40AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: TRX40 AORUS PRO WIFI
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1889054] Re: No audio on TRX40 platform

[Eduardo]

apport information

** Tags added: apport-collected

** Description changed:

  Hello,
  
  I have Ubuntu 20.04 running on a computer based on AMD Threadripper
  3960x, TRX40 platform (Gigabyte TRX40 AORUS PRO). Audio hasn't worked so
  far.
  
  I read about audio problems on this platform from the beginning but they
  should be fixed in kernel 5.6 according to this
  https://www.phoronix.com/scan.php?page=news_item=Linux-AMD-TRX40
  -Audio-Quirks
  
  Kernel bug reports should be related to these ones:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873
  https://bugzilla.kernel.org/show_bug.cgi?id=206543
  
  Since it should be fixed in recent kernel versions, I guess the solution
  for Ubuntu 20.04 using 5.4 kernel is backporting the fixes.
  
  Is Ubuntu planning to do this?
  
  Thanks
  Eduardo
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jul 27 10:41:15 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-03-05 (143 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to focal on 2020-04-06 (111 days ago)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.4
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  eduardo1907 F pulseaudio
+  /dev/snd/controlC0:  eduardo1907 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-03-05 (144 days ago)
+ InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: alsa-driver (not installed)
+ ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
+ Tags:  focal
+ Uname: Linux 5.4.0-42-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-04-06 (112 days ago)
+ UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 10/24/2019
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: F2
+ dmi.board.asset.tag: Default string
+ dmi.board.name: TRX40 AORUS PRO WIFI
+ 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.:bvrF2:bd10/24/2019:svnGigabyteTechnologyCo.,Ltd.:pnTRX40AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnTRX40AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
+ dmi.product.family: Default string
+ dmi.product.name: TRX40 AORUS PRO WIFI
+ dmi.product.sku: Default string
+ dmi.product.version: -CF
+ dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1889054/+attachment/5396260/+files/AlsaInfo.txt

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

Title:
  No audio on TRX40 platform

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have Ubuntu 20.04 running on a computer based on AMD Threadripper
  3960x, TRX40 platform (Gigabyte TRX40 AORUS PRO). Audio hasn't worked
  so far.

  I read about audio problems on this platform from the beginning but
  they should be fixed in kernel 5.6 according to this
  https://www.phoronix.com/scan.php?page=news_item=Linux-AMD-TRX40
  -Audio-Quirks

  Kernel bug reports should be related to these ones:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873
  https://bugzilla.kernel.org/show_bug.cgi?id=206543

  Since it should be fixed in recent kernel versions, I guess the
  solution for Ubuntu 20.04 using 5.4 kernel is backporting the fixes.

  Is Ubuntu planning to do this?

  Thanks
  Eduardo

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jul 27 10:41:15 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-03-05 (143 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: ubiquity
  Symptom: installer
  

[Desktop-packages] [Bug 1889091] [NEW] When saving a copy save dialog cannot create directory on nfs share

[1448412]

Public bug reported:

Hi,

i stumbled upon a weird oddity with evince...

# Steps creating the problem

1. I downloaded a pdf document from the internet using firefox.
2. Firefox offered to open the pdf in a document reader
3. Evince opened and displayed the pdf (correctly)
4. I used the hamburger menu and choose "Speichern unter" ("save as")
5. Filedialog opened. I navigated to an nfs mounted directory.
6. I ordered "Ordner anlegen" ("create folder") via the + symbol
7. I am prompted for the name of the new folder
8. It sais: "Der Ordner kann nicht angelegt werden -- Fehler beim ERstellen des 
Ordners <...> Keine Berechtigung" ("The folder cannot be created - Error 
creating the folder -- Not Authorized"
9. If I go to the terminal and mkdir the folder is created all right. (I 
expected that the directory would be created -- if chmod is set correctly and 
the shell can do it evince should also be able to do it...)

# More info

My `/etc/fstab` reads as follows:

```
# /etc/fstab: static file system information.
#
#   

192.168.178.52:/home /nfs nfs noauto,user,exec 0 0
<...>
```

192.168.178.52 (nathan) uses the kernel-nfs-server and the following 
`/etc/exports`-file:
```
# /etc/exports: the access control list for filesystems which may be exported
#   to NFS clients.  See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes   hostname1(rw,sync,no_subtree_check) 
hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes  gss/krb5i(rw,sync,no_subtree_check)
#
# /etc/exports: the access control list for filesystems which may be exported
#   to NFS clients.  See exports(5).
#
/home/ *(rw,sync,insecure,no_root_squash)
<...>
```

Which is surely not too strict but rather to permissive... :o/

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: evince 3.36.5-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.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: Budgie:GNOME
Date: Mon Jul 27 16:12:17 2020
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/zsh
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apparmor apport-bug focal

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

Title:
  When saving a copy save dialog cannot create directory on nfs share

Status in evince package in Ubuntu:
  New

Bug description:
  Hi,

  i stumbled upon a weird oddity with evince...

  # Steps creating the problem

  1. I downloaded a pdf document from the internet using firefox.
  2. Firefox offered to open the pdf in a document reader
  3. Evince opened and displayed the pdf (correctly)
  4. I used the hamburger menu and choose "Speichern unter" ("save as")
  5. Filedialog opened. I navigated to an nfs mounted directory.
  6. I ordered "Ordner anlegen" ("create folder") via the + symbol
  7. I am prompted for the name of the new folder
  8. It sais: "Der Ordner kann nicht angelegt werden -- Fehler beim ERstellen 
des Ordners <...> Keine Berechtigung" ("The folder cannot be created - Error 
creating the folder -- Not Authorized"
  9. If I go to the terminal and mkdir the folder is created all right. (I 
expected that the directory would be created -- if chmod is set correctly and 
the shell can do it evince should also be able to do it...)

  # More info

  My `/etc/fstab` reads as follows:

  ```
  # /etc/fstab: static file system information.
  #
  # 

  192.168.178.52:/home /nfs nfs noauto,user,exec 0 0
  <...>
  ```

  192.168.178.52 (nathan) uses the kernel-nfs-server and the following 
`/etc/exports`-file:
  ```
  # /etc/exports: the access control list for filesystems which may be exported
  # to NFS clients.  See exports(5).
  #
  # Example for NFSv2 and NFSv3:
  # /srv/homes   hostname1(rw,sync,no_subtree_check) 
hostname2(ro,sync,no_subtree_check)
  #
  # Example for NFSv4:
  # /srv/nfs4gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
  # /srv/nfs4/homes  gss/krb5i(rw,sync,no_subtree_check)
  #
  # /etc/exports: the access control list for filesystems which may be exported
  # to NFS clients.  See exports(5).
  #
  /home/ *(rw,sync,insecure,no_root_squash)
  <...>
  ```

  Which is surely not too strict but rather to permissive... :o/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: evince 3.36.5-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.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
 

[Desktop-packages] [Bug 1870867] Re: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl))

[Treviño]

Mh, I've tried to inspect that crash file, but it looks like that the
core-dump it contains isn't complete enough as I can't get the symbols
on it:

warning: Unexpected size of section `.reg-xstate/4998' in core file.
#0  __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
50  ../sysdeps/unix/sysv/linux/raise.c: File o directory non esistente.
[Current thread is 1 (Thread 0x7f2e7a72fcc0 (LWP 4998))]
(gdb) bt
#0  __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x55f2fef3752a in dump_gjs_stack_on_signal_handler (signo=6) at 
../src/main.c:421
#2  
#3  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#4  0x7f2e7fa8b859 in __GI_abort () at abort.c:79
#5  0x7f2e808aeb63 in ?? ()
#6  0x7ffe00303738 in ?? ()
#7  0x05b53dd8ea0b9800 in ?? ()
#8  0x55f2ff3ae310 in ?? ()
#9  0x7f2e7fda0c44 in ?? ()
#10 0x7f2e8093d7c1 in ?? ()
#11 0x05b53dd8ea0b9800 in ?? ()
#12 0x55f307c4a9b0 in ?? ()
#13 0x55f3028399d0 in ?? ()
#14 0x7f2e7fd9ed3b in ?? ()
#15 0x7f2e7fda0c60 in ?? ()
#16 0x0366 in ?? ()
#17 0x7f2e8090bb4f in ?? ()
#18 0x in ?? ()
(gdb) sharedlibrary mutter
Symbols already loaded for 
/usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0
Symbols already loaded for 
/usr/lib/x86_64-linux-gnu/mutter-6/libmutter-cogl-pango-6.so.0
Symbols already loaded for 
/usr/lib/x86_64-linux-gnu/mutter-6/libmutter-cogl-6.so.0
Symbols already loaded for 
/usr/lib/x86_64-linux-gnu/mutter-6/libmutter-cogl-path-6.so.0
(gdb)

---

However, are you sure we're talking of the same crash?
As so far, we've not got any crash with the same signature of this bug in 
errors.ubuntu.com

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

Title:
  gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion
  failed: (META_IS_STAGE_X11 (impl))

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

Bug description:
  [ Impact ]

  GNOME Shell crashes in meta_x11_get_stage_window.

  [ Test case ]

  Perform touch events via touchpad or touchscreen, eventually the shell
  will crash.

  Errors can be monitored at:
   https://errors.ubuntu.com/problem/1d4cdd9f2e9cd378a3e0aeed140079f319454bf2

  [ Regression potential ]

  Windows might not be closed correctly when requested via delete-events
  (clicking on clientside decoration close button).

  ---

  ProblemType: CrashDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 22:08:06 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1Signal: 6SourcePackage: 
gnome-shell
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0
  Title: gnome-shell crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2020-04-05 (0 days ago)
  UserGroups: adm cdrom dialout dip docker input libvirt lpadmin plugdev 
sambashare sudo
  separator:

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

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

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

[Nicolas Rogues]

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

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

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

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

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

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

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

[Desktop-packages] [Bug 1889084] [NEW] Dock appears on top of windows in overview on a second monitor

[Amr Ibrahim]

Public bug reported:

Steps to reproduce the issue:

1. Attach a second monitor
2. Show the Dock on all monitors from Settings
3. Open many windows in the second monitor
4. Press the Super key for overview

See the attached screenshot.

What happens:
Dock appears on top of windows in overview on a second monitor.

What should happen instead:
Dock should not appear on top of windows in overview on a second monitor.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~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.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 27 15:49:50 2020
InstallationDate: Installed on 2020-04-26 (92 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Dock_second_monitor.png"
   
https://bugs.launchpad.net/bugs/1889084/+attachment/5396254/+files/Dock_second_monitor.png

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

Title:
  Dock appears on top of windows in overview on a second monitor

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

Bug description:
  Steps to reproduce the issue:

  1. Attach a second monitor
  2. Show the Dock on all monitors from Settings
  3. Open many windows in the second monitor
  4. Press the Super key for overview

  See the attached screenshot.

  What happens:
  Dock appears on top of windows in overview on a second monitor.

  What should happen instead:
  Dock should not appear on top of windows in overview on a second monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~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.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 27 15:49:50 2020
  InstallationDate: Installed on 2020-04-26 (92 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1889085] [NEW] GTK File chooser search doesn't find files with a dot

[Saverio Miroddi]

Public bug reported:

(I'm not sure this is the correct package to file the bug against)

The (I assume) GTK 3.0 File chooser dialog doesn't allow searching files
with a dot.

In the previous, but working, File chooser, in order to search files,
the typeahead would be used. In order to search dotfiles (files starting
with dot), one would enable display of hidden files if required, then
just type the filename (starting with the dot character).

With the new search functionality, the dot character is not searched (or
not considered valid, it's not clear), so one can't search dotfiles, and
they need to manually go through the files in order to find the intended
one(s).

In order to reproduce, for example:

- Open a webpage in Firefox
- Click "Save As..." on an image
- Tap Ctrl+H, if the hidden files are not displayed
- Tap Ctrl+F, in order to search
- Tap dot (`.`)

no files show.

I hope this is not another case of the (in)famous group of devs who's
trying to reduce the whole desktop experience to a single blinking dot.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libgtk-3-0 3.24.18-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
Uname: Linux 5.4.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Mon Jul 27 15:52:53 2020
InstallationDate: Installed on 2020-07-01 (26 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
SourcePackage: gtk+3.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  GTK File chooser search doesn't find files with a dot

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  (I'm not sure this is the correct package to file the bug against)

  The (I assume) GTK 3.0 File chooser dialog doesn't allow searching
  files with a dot.

  In the previous, but working, File chooser, in order to search files,
  the typeahead would be used. In order to search dotfiles (files
  starting with dot), one would enable display of hidden files if
  required, then just type the filename (starting with the dot
  character).

  With the new search functionality, the dot character is not searched
  (or not considered valid, it's not clear), so one can't search
  dotfiles, and they need to manually go through the files in order to
  find the intended one(s).

  In order to reproduce, for example:

  - Open a webpage in Firefox
  - Click "Save As..." on an image
  - Tap Ctrl+H, if the hidden files are not displayed
  - Tap Ctrl+F, in order to search
  - Tap dot (`.`)

  no files show.

  I hope this is not another case of the (in)famous group of devs who's
  trying to reduce the whole desktop experience to a single blinking
  dot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgtk-3-0 3.24.18-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Jul 27 15:52:53 2020
  InstallationDate: Installed on 2020-07-01 (26 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1889085/+subscriptions

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

[Desktop-packages] [Bug 1888992] Re: [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones

[Francis Chin]

Ignore my last comment about last known working kernel, I've rebooted to
5.4.0.40 and I still see this issue, will try and do more testing on
kernel versions to see if I can find where it changes, and will also
look into the power_save options.

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

Title:
  [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching
  to front jack after plugging in headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I boot my system without any sound devices plugged into any jacks;
  checking Gnome settings Sound, Output Device is "Dummy Output" (no
  other options available in drop-down list). I plug in headphones into
  the front jack and play some audio, but do not hear any sound from the
  headphones; checking Gnome settings Sound, the Output Device is still
  "Dummy Output", with no other options available.

  This is a regression from previous behaviour, when plugging in
  headphones into the front jack would automatically enable/switch to
  the front jack and its associated controller "Family 17h (Models 00h-
  0fh) HD Audio Controller" (this is the motherboard's onboard audio
  hardware).

  I can currently workaround this each time I plug in the headphones by
  installing and running pavucontrol, and under Configuration selecting
  "Analogue Stereo Output (unplugged) (unavailable)" - this option
  becomes "Analogue Stereo Output" after I select it.

  This seems to be a regression in pulseaudio after an upgrade from from
  1:13.99.1-1ubuntu3.3 to 1:13.99.1-1ubuntu3.5.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chinf  1741 F pulseaudio
   /dev/snd/pcmC1D0p:   chinf  1741 F...m pulseaudio
   /dev/snd/controlC0:  chinf  1741 F pulseaudio
   /dev/snd/timer:  chinf  1741 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 26 12:46:52 2020
  InstallationDate: Installed on 2018-10-29 (635 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful
  Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chinf  1741 F pulseaudio
   /dev/snd/controlC0:  chinf  1741 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] 
No sound at all
  UpgradeStatus: Upgraded to focal on 2020-05-04 (83 days ago)
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1889054] Re: No audio on TRX40 platform

[Daniel Letzeisen]

** Tags removed: ubiquity-is

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

Title:
  No audio on TRX40 platform

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have Ubuntu 20.04 running on a computer based on AMD Threadripper
  3960x, TRX40 platform (Gigabyte TRX40 AORUS PRO). Audio hasn't worked
  so far.

  I read about audio problems on this platform from the beginning but
  they should be fixed in kernel 5.6 according to this
  https://www.phoronix.com/scan.php?page=news_item=Linux-AMD-TRX40
  -Audio-Quirks

  Kernel bug reports should be related to these ones:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873
  https://bugzilla.kernel.org/show_bug.cgi?id=206543

  Since it should be fixed in recent kernel versions, I guess the
  solution for Ubuntu 20.04 using 5.4 kernel is backporting the fixes.

  Is Ubuntu planning to do this?

  Thanks
  Eduardo

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jul 27 10:41:15 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-03-05 (143 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to focal on 2020-04-06 (111 days ago)

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

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

[Desktop-packages] [Bug 1888992] Re: [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones

[Francis Chin]

The output of cat /proc/asound/card1/codec#0 after running alsa-info
differs slightly to that included within the alsa-info log itself (in
#8):

26c335
<   Converter: stream=0, channel=0
---
>   Converter: stream=5, channel=0
38c347
<   Converter: stream=0, channel=0
---
>   Converter: stream=5, channel=0
52c361
<   Converter: stream=0, channel=0
---
>   Converter: stream=5, channel=0
64c373
<   Converter: stream=0, channel=0
---
>   Converter: stream=5, channel=0


** Attachment added: "/proc/asound/card1/codec#0 output after running alsa-info 
with headphones plugged in"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1888992/+attachment/5396233/+files/proc_asound_card1_codec0.txt

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

Title:
  [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching
  to front jack after plugging in headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I boot my system without any sound devices plugged into any jacks;
  checking Gnome settings Sound, Output Device is "Dummy Output" (no
  other options available in drop-down list). I plug in headphones into
  the front jack and play some audio, but do not hear any sound from the
  headphones; checking Gnome settings Sound, the Output Device is still
  "Dummy Output", with no other options available.

  This is a regression from previous behaviour, when plugging in
  headphones into the front jack would automatically enable/switch to
  the front jack and its associated controller "Family 17h (Models 00h-
  0fh) HD Audio Controller" (this is the motherboard's onboard audio
  hardware).

  I can currently workaround this each time I plug in the headphones by
  installing and running pavucontrol, and under Configuration selecting
  "Analogue Stereo Output (unplugged) (unavailable)" - this option
  becomes "Analogue Stereo Output" after I select it.

  This seems to be a regression in pulseaudio after an upgrade from from
  1:13.99.1-1ubuntu3.3 to 1:13.99.1-1ubuntu3.5.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chinf  1741 F pulseaudio
   /dev/snd/pcmC1D0p:   chinf  1741 F...m pulseaudio
   /dev/snd/controlC0:  chinf  1741 F pulseaudio
   /dev/snd/timer:  chinf  1741 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 26 12:46:52 2020
  InstallationDate: Installed on 2018-10-29 (635 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful
  Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chinf  1741 F pulseaudio
   /dev/snd/controlC0:  chinf  1741 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] 
No sound at all
  UpgradeStatus: Upgraded to focal on 2020-05-04 (83 days ago)
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1888992] Re: [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones

[Hui Wang]

So this is a kernel driver issue instead of pulseaudio issue. It has sth
to do with power management, and it is difficult to debug this kind of
issue without a physical machine.

you could use a workaround like snd_hda_intel.power_save=0 or
snd_hda_intel.power_save=,0  I don't whchi one is correct workaround,
please test them and choose one of them.

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

Title:
  [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching
  to front jack after plugging in headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I boot my system without any sound devices plugged into any jacks;
  checking Gnome settings Sound, Output Device is "Dummy Output" (no
  other options available in drop-down list). I plug in headphones into
  the front jack and play some audio, but do not hear any sound from the
  headphones; checking Gnome settings Sound, the Output Device is still
  "Dummy Output", with no other options available.

  This is a regression from previous behaviour, when plugging in
  headphones into the front jack would automatically enable/switch to
  the front jack and its associated controller "Family 17h (Models 00h-
  0fh) HD Audio Controller" (this is the motherboard's onboard audio
  hardware).

  I can currently workaround this each time I plug in the headphones by
  installing and running pavucontrol, and under Configuration selecting
  "Analogue Stereo Output (unplugged) (unavailable)" - this option
  becomes "Analogue Stereo Output" after I select it.

  This seems to be a regression in pulseaudio after an upgrade from from
  1:13.99.1-1ubuntu3.3 to 1:13.99.1-1ubuntu3.5.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chinf  1741 F pulseaudio
   /dev/snd/pcmC1D0p:   chinf  1741 F...m pulseaudio
   /dev/snd/controlC0:  chinf  1741 F pulseaudio
   /dev/snd/timer:  chinf  1741 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 26 12:46:52 2020
  InstallationDate: Installed on 2018-10-29 (635 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful
  Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chinf  1741 F pulseaudio
   /dev/snd/controlC0:  chinf  1741 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] 
No sound at all
  UpgradeStatus: Upgraded to focal on 2020-05-04 (83 days ago)
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1888992] Re: [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones

[Francis Chin]

To add to #9, as well as the headphones being detected after running
alsa-info, I can confirm that they still work as expected after
detection.

As this may be a bug introduced by a kernel change, the current kernel
running is 5.4.0.42.45 (generic, x86_64), whereas the previous one I was
running when I didn't see this bug was 5.4.0.40.43.

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

Title:
  [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching
  to front jack after plugging in headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I boot my system without any sound devices plugged into any jacks;
  checking Gnome settings Sound, Output Device is "Dummy Output" (no
  other options available in drop-down list). I plug in headphones into
  the front jack and play some audio, but do not hear any sound from the
  headphones; checking Gnome settings Sound, the Output Device is still
  "Dummy Output", with no other options available.

  This is a regression from previous behaviour, when plugging in
  headphones into the front jack would automatically enable/switch to
  the front jack and its associated controller "Family 17h (Models 00h-
  0fh) HD Audio Controller" (this is the motherboard's onboard audio
  hardware).

  I can currently workaround this each time I plug in the headphones by
  installing and running pavucontrol, and under Configuration selecting
  "Analogue Stereo Output (unplugged) (unavailable)" - this option
  becomes "Analogue Stereo Output" after I select it.

  This seems to be a regression in pulseaudio after an upgrade from from
  1:13.99.1-1ubuntu3.3 to 1:13.99.1-1ubuntu3.5.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chinf  1741 F pulseaudio
   /dev/snd/pcmC1D0p:   chinf  1741 F...m pulseaudio
   /dev/snd/controlC0:  chinf  1741 F pulseaudio
   /dev/snd/timer:  chinf  1741 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 26 12:46:52 2020
  InstallationDate: Installed on 2018-10-29 (635 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful
  Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chinf  1741 F pulseaudio
   /dev/snd/controlC0:  chinf  1741 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] 
No sound at all
  UpgradeStatus: Upgraded to focal on 2020-05-04 (83 days ago)
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1889067] Re: Can't login to Ubuntu One from gnome-control-center (20.04)

[Sebastien Bacher]

is using snapd from the command line working to install snaps for
example?

reassigning to snapd in any case because it sounds like the auth issue
is due to the service

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

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

** Summary changed:

- Can't login to Ubuntu One from gnome-control-center (20.04)
+ Error logging in snapd: (most recent call last): (snapd-error-quark, 10) when 
trying to log in from settings

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

Title:
  Error logging in snapd: (most recent call last): (snapd-error-quark,
  10) when trying to log in from settings

Status in snapd package in Ubuntu:
  New

Bug description:
  viator@viator-acronis-laptop:/etc/apt/sources.list.d$ gnome-control-center -v
  14:23:51.0206  GLib:DEBUG: setenv()/putenv() are not 
thread-safe and should not be used after threads are created
  14:23:51.0219  diagnostics-cc-panel:DEBUG: ABRT vanished
  14:24:08.0178  GLib:DEBUG: posix_spawn avoided (fd 
close requested) (child_setup specified) 
  14:24:08.0236GoaBackend:  WARNING: Error logging in snapd: 
(most recent call last): (snapd-error-quark, 10)

  I created a question on askubuntu.com before, but nobody was able to
  answer to me: https://askubuntu.com/questions/1259280/cant-login-to-
  ubuntu-one-from-gnome-control-center-20-04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.4-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-41.45-generic 5.4.44
  Uname: Linux 5.4.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 27 14:03:45 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-03-19 (496 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-07-07 (19 days ago)

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

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

[Desktop-packages] [Bug 1889054] Re: No audio on TRX40 platform

[Launchpad Bug Tracker]

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

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

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

Title:
  No audio on TRX40 platform

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have Ubuntu 20.04 running on a computer based on AMD Threadripper
  3960x, TRX40 platform (Gigabyte TRX40 AORUS PRO). Audio hasn't worked
  so far.

  I read about audio problems on this platform from the beginning but
  they should be fixed in kernel 5.6 according to this
  https://www.phoronix.com/scan.php?page=news_item=Linux-AMD-TRX40
  -Audio-Quirks

  Kernel bug reports should be related to these ones:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873
  https://bugzilla.kernel.org/show_bug.cgi?id=206543

  Since it should be fixed in recent kernel versions, I guess the
  solution for Ubuntu 20.04 using 5.4 kernel is backporting the fixes.

  Is Ubuntu planning to do this?

  Thanks
  Eduardo

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jul 27 10:41:15 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-03-05 (143 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to focal on 2020-04-06 (111 days ago)

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

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

[Desktop-packages] [Bug 1889054] Re: No audio on TRX40 platform

[Daniel Letzeisen]

Also, I removed the CPU model from the title, since there are duplicate
reports problem is independent of CPU model.

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

Title:
  No audio on TRX40 platform

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have Ubuntu 20.04 running on a computer based on AMD Threadripper
  3960x, TRX40 platform (Gigabyte TRX40 AORUS PRO). Audio hasn't worked
  so far.

  I read about audio problems on this platform from the beginning but
  they should be fixed in kernel 5.6 according to this
  https://www.phoronix.com/scan.php?page=news_item=Linux-AMD-TRX40
  -Audio-Quirks

  Kernel bug reports should be related to these ones:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873
  https://bugzilla.kernel.org/show_bug.cgi?id=206543

  Since it should be fixed in recent kernel versions, I guess the
  solution for Ubuntu 20.04 using 5.4 kernel is backporting the fixes.

  Is Ubuntu planning to do this?

  Thanks
  Eduardo

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jul 27 10:41:15 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-03-05 (143 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to focal on 2020-04-06 (111 days ago)

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

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

[Desktop-packages] [Bug 1881490] Re: Onboard sound not detected for Zenith ROG after upgrade to 20.04

[Daniel Letzeisen]

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

** This bug has been marked a duplicate of bug 1889054
   No audio on TRX40 platform

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

Title:
  Onboard sound not detected for Zenith ROG after upgrade to 20.04

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After upgrading to 20.04, my onboard sound no longer seems to work.
  The motherboard is ROG Zenith. dmesg shows the following:

  [9.266092] snd_hda_intel :09:00.1: dmic_detect option is deprecated, 
pass snd-intel-dspcfg.dsp_driver=1 option instead
  [9.266556] snd_hda_intel :09:00.1: Disabling MSI
  [9.266586] snd_hda_intel :09:00.1: Handle vga_switcheroo audio client
  [9.267181] snd_hda_intel :0b:00.3: Skipping the blacklisted device

  After searching for this message in kernel source, I happened upon
  this line:

  
https://github.com/torvalds/linux/blob/052c467cb58748e302a95546925928e637025acc/sound/pci/hda/hda_intel.c#L2082

  static const struct pci_device_id driver_blacklist[] = {
{ PCI_DEVICE_SUB(0x1022, 0x1487, 0x1043, 0x874f) }, /* ASUS ROG Zenith 
II / Strix */
{ PCI_DEVICE_SUB(0x1022, 0x1487, 0x1462, 0xcb59) }, /* MSI TRX40 
Creator */
{ PCI_DEVICE_SUB(0x1022, 0x1487, 0x1462, 0xcb60) }, /* MSI TRX40 */
{}
  };

  Which led me to this bug report:

  https://lore.kernel.org/alsa-
  devel/20200424061222.19792-1-ti...@suse.de/

  I confirmed that the PCI device that is not working appears to match
  the vendor ID:

  $  lspci | grep 0b:00.3
  0b:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 
00h-0fh) HD Audio Controller

  $ lspci -n | grep 0b:00.3
  0b:00.3 0403: 1022:1457

  Unfortunately, I am unsure how to test a Ubuntu compatible kernel with
  these changes but it appears there has been some jiggery pokery in
  Linux kernel land in this regard.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sohail 4693 F pulseaudio
   /dev/snd/pcmC1D0p:   sohail 4693 F...m pulseaudio
   /dev/snd/controlC0:  sohail 4693 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 31 11:14:39 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-07-16 (1049 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to focal on 2020-05-24 (6 days ago)
  dmi.bios.date: 07/16/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1304
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1304:bd07/16/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx: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

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

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

[Desktop-packages] [Bug 1889054] Re: No audio on TRX40 platform (Threadripper 3960x)

[Daniel Letzeisen]

Eduardo, the issue seems well-defined, but if possible, please run the 
following command in terminal to collect the audio information just in case:
apport-collect 1889054

** Package changed: ubiquity (Ubuntu) => alsa-driver (Ubuntu)

** Summary changed:

- No audio on TRX40 platform (Threadripper 3960x)
+ No audio on TRX40 platform

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

Title:
  No audio on TRX40 platform

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have Ubuntu 20.04 running on a computer based on AMD Threadripper
  3960x, TRX40 platform (Gigabyte TRX40 AORUS PRO). Audio hasn't worked
  so far.

  I read about audio problems on this platform from the beginning but
  they should be fixed in kernel 5.6 according to this
  https://www.phoronix.com/scan.php?page=news_item=Linux-AMD-TRX40
  -Audio-Quirks

  Kernel bug reports should be related to these ones:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873
  https://bugzilla.kernel.org/show_bug.cgi?id=206543

  Since it should be fixed in recent kernel versions, I guess the
  solution for Ubuntu 20.04 using 5.4 kernel is backporting the fixes.

  Is Ubuntu planning to do this?

  Thanks
  Eduardo

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jul 27 10:41:15 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-03-05 (143 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: Upgraded to focal on 2020-04-06 (111 days ago)

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

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

[Desktop-packages] [Bug 1889054] [NEW] No audio on TRX40 platform (Threadripper 3960x)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hello,

I have Ubuntu 20.04 running on a computer based on AMD Threadripper
3960x, TRX40 platform (Gigabyte TRX40 AORUS PRO). Audio hasn't worked so
far.

I read about audio problems on this platform from the beginning but they
should be fixed in kernel 5.6 according to this
https://www.phoronix.com/scan.php?page=news_item=Linux-AMD-TRX40
-Audio-Quirks

Kernel bug reports should be related to these ones:
https://bugzilla.kernel.org/show_bug.cgi?id=206873
https://bugzilla.kernel.org/show_bug.cgi?id=206543

Since it should be fixed in recent kernel versions, I guess the solution
for Ubuntu 20.04 using 5.4 kernel is backporting the fixes.

Is Ubuntu planning to do this?

Thanks
Eduardo

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Mon Jul 27 10:41:15 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
InstallationDate: Installed on 2020-03-05 (143 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: ubiquity
Symptom: installer
UpgradeStatus: Upgraded to focal on 2020-04-06 (111 days ago)

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubiquity-is
-- 
No audio on TRX40 platform (Threadripper 3960x)
https://bugs.launchpad.net/bugs/1889054
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to alsa-driver in Ubuntu.

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

[Desktop-packages] [Bug 1888992] Re: [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones

[Francis Chin]

Then after the fresh boot, I connected the headphones, verified no
sound, then re-ran alsa-info which gave the following attached log.

** Attachment added: "alsa-info log with headphones plugged in"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1888992/+attachment/5396230/+files/alsa-info_headphones_not_working.log

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

Title:
  [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching
  to front jack after plugging in headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I boot my system without any sound devices plugged into any jacks;
  checking Gnome settings Sound, Output Device is "Dummy Output" (no
  other options available in drop-down list). I plug in headphones into
  the front jack and play some audio, but do not hear any sound from the
  headphones; checking Gnome settings Sound, the Output Device is still
  "Dummy Output", with no other options available.

  This is a regression from previous behaviour, when plugging in
  headphones into the front jack would automatically enable/switch to
  the front jack and its associated controller "Family 17h (Models 00h-
  0fh) HD Audio Controller" (this is the motherboard's onboard audio
  hardware).

  I can currently workaround this each time I plug in the headphones by
  installing and running pavucontrol, and under Configuration selecting
  "Analogue Stereo Output (unplugged) (unavailable)" - this option
  becomes "Analogue Stereo Output" after I select it.

  This seems to be a regression in pulseaudio after an upgrade from from
  1:13.99.1-1ubuntu3.3 to 1:13.99.1-1ubuntu3.5.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chinf  1741 F pulseaudio
   /dev/snd/pcmC1D0p:   chinf  1741 F...m pulseaudio
   /dev/snd/controlC0:  chinf  1741 F pulseaudio
   /dev/snd/timer:  chinf  1741 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 26 12:46:52 2020
  InstallationDate: Installed on 2018-10-29 (635 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful
  Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chinf  1741 F pulseaudio
   /dev/snd/controlC0:  chinf  1741 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] 
No sound at all
  UpgradeStatus: Upgraded to focal on 2020-05-04 (83 days ago)
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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