date:20210418

** Tags added: hirsute

** Tags added: hdmi

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

Title:
  PulseAudio automatically switches to HDMI sound output on every boot

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After upgrading to an AMD laptop (Thinkpad T14) and Ubuntu 21.04, when
  I boot the laptop my audio device has changed to HDMI, instead of
  remembering my headphones from last session.

  Screen remains plugged in, but takes a few seconds to wake up while
  booting.

  Commenting out
   load-module module-switch-on-port-available
  in  /etc/pulse/default.pa fixes the issue.

  Might be related to:
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570

  Devices:

  Family 17h (Models 10h-1fh) HD Audio Controller Speaker + Headphones
  Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) 
HD Audio Controller
Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller

  
  HD-Audio Generic HDMI1 Output
  Multimedia controller: Advanced Micro Devices, Inc. [AMD] 
Raven/Raven2/FireFlight/Renoir Audio Processor (rev 01)
Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor

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

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

[Desktop-packages] [Bug 1924895] Re: Settings crashes as soon as it is opened

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

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

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

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

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


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

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

Title:
  Settings crashes as soon as it is opened

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

Bug description:
  Just opening the settings causes it to almost immediately crash.

  
  ❯ gnome-control-center

  
  (gnome-control-center:12969): dconf-WARNING **: 09:14:26.286: failed to 
commit changes to dconf: Could not connect: Connection refused
  Error creating rfkill proxy: (null)
  Segmentation fault (core dumped)
  ~ 
  ❯ 
  ~ 
  ❯ gnome-control-center user-accounts

  (gnome-control-center:13142): dconf-WARNING **: 09:15:10.855: failed
  to commit changes to dconf: Could not connect: Connection refused

  (gnome-control-center:13142): dconf-WARNING **: 09:15:11.085: failed to 
commit changes to dconf: Could not connect: Connection refused
  Segmentation fault (core dumped)
  ~ took 16s 
  ❯ gdb gnome-control-center
  GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
  Copyright (C) 2020 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from gnome-control-center...
  (No debugging symbols found in gnome-control-center)
  (gdb) r
  Starting program: /usr/bin/gnome-control-center 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffea9e0700 (LWP 13237)]
  [New Thread 0x7fffdf05b700 (LWP 13238)]
  [New Thread 0x7fffde85a700 (LWP 13239)]
  [New Thread 0x7fffde059700 (LWP 13240)]
  [New Thread 0x7fffdd858700 (LWP 13241)]
  [New Thread 0x7fffdcc17700 (LWP 13242)]
  [New Thread 0x7fffc7fff700 (LWP 13243)]
  [New Thread 0x7fffc77fe700 (LWP 13244)]
  [New Thread 0x7fffc6ffd700 (LWP 13245)]

  (gnome-control-center:13233): dconf-WARNING **: 09:15:38.054: failed to 
commit changes to dconf: Could not connect: Connection refused
  Error creating rfkill proxy: (null)

  Thread 8 "pool-gnome-cont" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7fffc7fff700 (LWP 13243)]
  0x77ca6ac3 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  (gdb) bt
  #0  0x77ca6ac3 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #1  0x77ca6e1c in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x7637e5a1 in __nptl_deallocate_tsd () at pthread_create.c:301
  #3  0x7637f62a in __nptl_deallocate_tsd () at pthread_create.c:256
  #4  start_thread (arg=) at pthread_create.c:488
  #5  0x762a6293 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
  (gdb) q
  A debugging session is active.

  Inferior 1 [process 13233] will be killed.

  Quit anyway? (y or n) y
  ~ took 20s 
  ❯ gnome-control-center --version
  gnome-control-center 3.36.5
  ~ 
  ❯ ubuntu-bug gnome-control-center

  (gio open:15213): GLib-GIO-CRITICAL **: 09:17:11.048:
  g_dbus_connection_flush: assertion 'G_IS_DBUS_CONNECTION (connection)'
  failed

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.5-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
  Uname: Linux 5.4.0-71-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 18 09:16:22 2021
  EcryptfsInUse: Yes

[Desktop-packages] [Bug 1924882] Re: Random freezing of the computer during testing.

Thanks for the bug report. Please try booting into an older kernel
version. You can select it in the Grub menu before boot starts by
tapping the Escape key.

** Tags added: ivybridge

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Random freezing of the computer during testing.

Status in Ubuntu:
  Incomplete

Bug description:
  I1m using UBUNTU 20.04

  Problem: Occasionally there is a failure to display on the screen with
  parts alternating colors and characters exchanged in the terminal
  (only in the terminal). Control characters are displayed on the
  terminal and "blink" effects occur on some lines.

  First symptom: The firefox update made the browser screen (just inside
  the browser screen) appear many black blocks over the texts and
  images, corrected with the deactivation of the use of graphical
  acceleration.

  Second symptom: after an update of ubuntu, he started to have a
  problem in the terminal, with control characters being displayed and a
  change in the mapping of the keyboard keys BUT this error does not
  happen in GEdit.

  Current symptom: when I open the terminal, the favorite icons on the edge of 
the screen where the terminal was opened change color alternately. The terminal 
screen has control characters and changes from character mapping to some keys.
  The browser is not fluent in scrolling a web page.

  Reboot the computer everything is normal and after a while it happens
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sat Apr 17 22:13:54 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  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:100d]
  InstallationDate: Installed on 2021-02-23 (53 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. K46CA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=ec0afab4-cb78-44a3-8868-cf6565dfb058 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K46CA.315
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K46CA
  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.:bvrK46CA.315:bd05/17/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnK46CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK46CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K46CA
  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.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/+bug/1924882/+subscriptions

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

[Desktop-packages] [Bug 1924861] Re: nvidia random crashes back to login screen

Thanks for the bug report. This appears to be a crash in the Nvidia
kernel driver. Please try using the 'Additional Drivers' app to see if a
newer version of the driver than 450 is available for your system.

Please also check for any other crashes that might be relevant using these 
steps:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

** Tags added: nvidia

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

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

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

Title:
  nvidia random crashes back to login screen

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

Bug description:
  sometimes, when I click on some application in the panel e.g
  discord/firefox/chrome Xorg crashes and takes me back to login screen

  dmesg error:
  [205084.240560] NVRM: Xid (PCI::01:00): 31, pid=1673, Ch 0009, intr 
1000. MMU Fault: ENGINE CE0 HUBCLIENT_CE0 faulted @ 0x1_02764000. Fault is 
of type FAULT_PTE ACCESS_TYPE_READ

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
  Uname: Linux 5.4.0-70-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.102.04  Tue Dec 29 
06:51:23 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog:

  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Apr 17 17:12:48 2021
  DistUpgraded: 2020-11-28 16:24:27,019 DEBUG entry '# deb 
http://ppa.launchpad.net/jeremysanders/ppa/ubuntu focal main # Bei 
Aktualisierung zu bionic deaktiviert Bei Aktualisierung zu focal deaktiviert' 
was disabled (unknown mirror)
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.102.04, 5.4.0-70-generic, x86_64: installed
   nvidia, 450.102.04, 5.4.0-72-generic, x86_64: installed
   virtualbox, 6.1.16, 5.4.0-70-generic, x86_64: installed
   virtualbox, 6.1.16, 5.4.0-71-generic, x86_64: installed
   virtualbox, 6.1.16, 5.4.0-72-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 
1060 6GB] [1462:3283]
  InstallationDate: Installed on 2016-09-09 (1681 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic 
root=UUID=21ee0900-9162-4298-bd0e-5dbd103514f0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-11-28 (139 days ago)
  dmi.bios.date: 01/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0501
  dmi.board.asset.tag: Default string
  dmi.board.name: B150 PRO GAMING/AURA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/26/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150PROGAMING/AURA:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1

[Desktop-packages] [Bug 1924859] Re: Virtual machine not grabbing alt+tab input

** Tags added: wayland wayland-session

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

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

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

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

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

** Summary changed:

- Virtual machine not grabbing alt+tab input
+ VMware not grabbing Alt+Tab input in Wayland sessions

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

Title:
  VMware not grabbing Alt+Tab input in Wayland sessions

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

Bug description:
  I am currently running VMware workstation pro 16.1. When pressing
  alt+tab to toggle the windows in the guest OS, the input is instead
  applied to the host OS and not the guest. When switching from Wayland
  to Xorg the problem is resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: 
Error executing command as another user: Request dismissed
  Date: Sat Apr 17 15:48:45 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: ASRock Incorporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [1849:0112]
   NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GM206 [GeForce GTX 
960] [1462:3202]
  InstallationDate: Installed on 2021-04-16 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic 
root=UUID=739968f7-1aa4-47f1-8d68-55af0ffb428d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 07/11/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.30
  dmi.board.name: Z77 OC Formula
  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.:bvrP2.30:bd07/11/2013:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77OCFormula: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.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

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

[Desktop-packages] [Bug 1924814] Re: Lag in laptop + ununtu20.04 + dock = 3 Displays

Thanks for the bug report. While the lag is happening please run:

  journalctl -b0 > journal.txt

and attach the resulting text file here.


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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Lag in laptop + ununtu20.04 + dock = 3 Displays

Status in Ubuntu:
  Incomplete

Bug description:
  Hi

  1)
  $ lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

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


  
  3) What you expected to happen

  I have a "HP EliteBook 840 G5 (3RF31LT#ABM)" laptop with ubuntu 20.04
  Also I have a Dell dock model k17a connected with 2 monitors.
  The physical display is the following:
  laptop(landscape) | monitor 1 (landscape) | monitor 2 (portrait right)

  When I connect the USB-C plug, I expect nothing special but having 2
  more display


  4) What happened instead

  When I connect the USB-C plug, the whole UX gets super slow
  Xorg and gnome-shell are the top 2 cpu-consuming process and both inside the 
same CPU2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 16 16:50:08 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b2]
  InstallationDate: Installed on 2021-04-04 (11 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: HP HP EliteBook 840 G5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=e6947647-3679-496c-8309-dbae876553c4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2018
  dmi.bios.release: 3.0
  dmi.bios.vendor: HP
  dmi.bios.version: Q78 Ver. 01.03.00
  dmi.board.name: 83B2
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 04.53.00
  dmi.chassis.asset.tag: 5CG8364L0N
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 4.83
  dmi.modalias: 
dmi:bvnHP:bvrQ78Ver.01.03.00:bd07/18/2018:br3.0:efr4.83:svnHP:pnHPEliteBook840G5:pvr:rvnHP:rn83B2:rvrKBCVersion04.53.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G5
  dmi.product.sku: 3RF31LT#ABM
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/+bug/1924814/+subscriptions

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

[Desktop-packages] [Bug 1924855] Re: Dock is sporadically blank when booting up or when waking from hibernation

Thanks for the bug report. Please try this (from bug 1874578):

gsettings set org.gnome.shell.extensions.dash-to-dock show-mounts false

and then log in again.

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

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

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

Title:
  Dock is sporadically blank when booting up or when waking from
  hibernation

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

Bug description:
  The dock is blank and only regains the icons if clicking on it or if I
  give it a few seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 17 15:06:08 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2021-04-16 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  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-extension-ubuntu-dock/+bug/1924855/+subscriptions

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

[Desktop-packages] [Bug 1924851] Re: intel display drivers not working

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

** This bug has been marked a duplicate of bug 1924889
   i915 :00:02.0: Your graphics device 4c8a is not properly supported by 
the driver in this kernel version.

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

Title:
  intel display drivers not working

Status in xorg package in Ubuntu:
  New

Bug description:
  Getting llvmpipe (LLVM 11.0.0, 256 bits) as display instead of intel
  drivers. Only available Resolution 1024X768

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 17 18:35:34 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus: rtl8821ce, 5.5.2.1, 5.8.0-50-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2021-04-17 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Gigabyte Technology Co., Ltd. B560M DS3H AC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=f0b245ca-169e-4fdc-80d3-14f66691147b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F1
  dmi.board.asset.tag: Default string
  dmi.board.name: B560M DS3H AC
  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:bvnAmericanMegatrendsInternational,LLC.:bvrF1:bd01/11/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560MDS3HAC:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560MDS3HAC:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B560 MB
  dmi.product.name: B560M DS3H AC
  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.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/1924851/+subscriptions

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

[Desktop-packages] [Bug 1924889] Re: i915 0000:00:02.0: Your graphics device 4c8a is not properly supported by the driver in this kernel version.

Does the same bug occur with an officially supported Ubuntu kernel?

** Summary changed:

- intel display drivers not working
+ i915 :00:02.0: Your graphics device 4c8a is not properly supported by the 
driver in this kernel version.

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

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

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

Title:
  i915 graphics driver not loading for Rocket Lake i7-11700K [8086:4c8a]

Status in linux package in Ubuntu:
  New

Bug description:
  intel display drivers UHD intel graphics 750 not working in ubuntu
  20.10

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  Uname: Linux 5.11.15-051115-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 18 10:04:50 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus: rtl8821ce, 5.5.2.1, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation RocketLake-S GT1 [UHD Graphics 750] [8086:4c8a] (rev 04) 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2021-04-17 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Gigabyte Technology Co., Ltd. B560M DS3H AC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.15-051115-generic 
root=UUID=f0b245ca-169e-4fdc-80d3-14f66691147b ro quiet splash 
modprobe.blacklist=nouveau vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
   Identifier "Card0"
   Driver "intel"
   Option "AccelMethod" "sna"
   EndSection
  dmi.bios.date: 01/11/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F1
  dmi.board.asset.tag: Default string
  dmi.board.name: B560M DS3H AC
  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:bvnAmericanMegatrendsInternational,LLC.:bvrF1:bd01/11/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560MDS3HAC:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560MDS3HAC:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B560 MB
  dmi.product.name: B560M DS3H AC
  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.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/1924889/+subscriptions

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

[Desktop-packages] [Bug 1924778] Re: Xorg buggy

Thanks for the bug report. Can you please attach a video showing the
problem?

I don't experience any such problem myself with the same software.

** Summary changed:

- Xorg buggy
+ Login the screen flashes and when i open i.e. Firefox i can see the desktop 
icons flashing

** Changed in: xorg (Ubuntu)
   Importance: Undecided => High

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

** Changed in: ubuntu
   Status: Confirmed => Incomplete

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

Title:
  Login the screen flashes and when i open i.e. Firefox i can see the
  desktop icons flashing

Status in Ubuntu:
  Incomplete

Bug description:
  After boot and login the screen flashes and when i open i.e. Firefox i
  can see the desktop icons flashing

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 16 17:28:13 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2021-02-21 (53 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20ARS20N00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=d09e8852-af20-45ea-8147-e76491467e1b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/27/2020
  dmi.bios.release: 2.54
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJETA4WW (2.54 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARS20N00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJETA4WW(2.54):bd03/27/2020:br2.54:efr1.14:svnLENOVO:pn20ARS20N00:pvrThinkPadT440s:rvnLENOVO:rn20ARS20N00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARS20N00
  dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/+bug/1924778/+subscriptions

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

[Desktop-packages] [Bug 1924910] Re: Massive screen flashing artefacts - tearing

Please try booting a slightly older kernel version. You can do that by
selecting it from the Grub menu, which is accessed by tapping Escape
before boot starts.

** Tags added: haswell regression-update

** Changed in: xorg (Ubuntu)
   Importance: Undecided => High

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Massive screen flashing artefacts - tearing

Status in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 20.10 x64 frequently updated.

  I noticed in the last week that after a while there are huge screen
  artefacts, that I would describe as flashing. Squares of screen flash,
  normally linked to widgets on screen.

  E.g.: the app bars on the left can start flashing blue, or parts of editors.
  I noticed it more in firefox, made worse by scrolling.
  VirtualBox is severely affected too.
  VS Code.

  It does not happen immediately and the feeling I get is that it starts
  happening when there is a lot on screen. For example has not happened
  at all in this session, but I have done little or nothing screen-
  heavy.

  The issue gets worse, then might settle down for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 18 13:53:28 2021
  DistUpgraded: 2020-11-27 20:39:33,916 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: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2020-02-01 (441 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic 
root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2020-11-27 (141 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/+bug/1924910/+subscriptions

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

[Desktop-packages] [Bug 1924689] Re: Can see some garbage at the edge of the window after changing scale

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

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

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

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

Title:
  Can see some garbage at the edge of the window after changing scale

Status in OEM Priority Project:
  New
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Ubuntu release:
  Ubuntu 20.04.2 LTS

  Issue description:
  When the gnome-initial-setup launched, if user changes the scale 200 -> 400 
or 100 -> 200.
  There is some garbage on the edge of the window.

  The issue is not seen if we login in wayland session.

  A video is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1924689/+subscriptions

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

[Desktop-packages] [Bug 1924852] Re: Selected output device in Sound settings is not persisted across restarts

** Tags added: focal

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

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

Title:
Selected output device in Sound settings is not persisted across
restarts

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

Bug description:
# Introduction

My computer has multiple audio devices, so I had to select the correct
one in the "Sound" section of "Settings". This worked fine, except
that whenever I restart the computer this setting resets to the
original one. Effectively I have to visit the sound settings on each
system startup in order to hear anything.

# How to reproduce

1. have system with multiple audio outputs
2. open sound settings
3. select non-default output device
4. restart computer
5. open sound settings

# Expected result

Selected audio device is the same as the one selected right before
restart.

# Actual result

The active output device is the original default one (i.e. not the one
that we selected).

# System information

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

$ apt-cache policy gnome-control-center
gnome-control-center:
Installed: 1:3.36.5-0ubuntu1
Candidate: 1:3.36.5-0ubuntu1
Version table:
*** 1:3.36.5-0ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64
Packages
100 /var/lib/dpkg/status
1:3.36.1-1ubuntu5 500
500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

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

[Desktop-packages] [Bug 1923632] Re: Screen flickering

I'm going to make this bug temporarily private until we get a response
from the original reporter because it's getting confused with me-toos.
Everyone other than siva please open your own bugs.

** Information type changed from Public to Private

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

Title:
  Screen flickering

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  ubuntu whole screen flickering.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 13 20:36:04 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Generation Core 
Processor Family Integrated Graphics Controller [1462:7817]
  InstallationDate: Installed on 2021-04-13 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: MSI MS-7817
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic 
root=UUID=03a76041-a4c2-4e9f-a936-29041654a888 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V6.7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-E33 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV6.7:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-E33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.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-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/1923632/+subscriptions

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

[Desktop-packages] [Bug 1923632] Re: Screen flickering

siva, please answer comment #4.

Everyone else, please open your own separate bugs.

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

Title:
  Screen flickering

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  ubuntu whole screen flickering.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 13 20:36:04 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Generation Core 
Processor Family Integrated Graphics Controller [1462:7817]
  InstallationDate: Installed on 2021-04-13 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: MSI MS-7817
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic 
root=UUID=03a76041-a4c2-4e9f-a936-29041654a888 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V6.7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-E33 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV6.7:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-E33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.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-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/1923632/+subscriptions

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

[Desktop-packages] [Bug 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]

You don't need to remove 'ubuntu-appindicat...@ubuntu.com', 'ubuntu-
d...@ubuntu.com', and 'desktop-icons@csoriano' because those are the
core Ubuntu extensions.

Also the set of 'enabled-extensions' does not have to correlate at all
with the set of installed extensions. You can install an extension and
have it disabled, although disabled extensions can still break things in
some cases. That's probably not an issue here.

If you can identify a single extension (or extensions) that causes this
crash then we would appreciate it.

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

Title:
  gnome-shell crashed with assertion failure
  "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]

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

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

  Similar errors:
  https://errors.ubuntu.com/problem/14911e4a22eec995bc364278c0490d8bfea557dd
  https://errors.ubuntu.com/problem/e3f9ab8232005403e935c6038edd99f13e609e01
  https://errors.ubuntu.com/problem/9d421ecaba25357f5c3ef73f438313e40ac24e77
  https://errors.ubuntu.com/problem/42cfd76250a81cca07f8c548ec27e245315b5e01

  ---

  Anyone experiencing this crash reliably, please help us to find its
  root cause by editing your /etc/environment and adding a line:

    MUTTER_SYNC=1

  and then reboot. Then next time a crash happens please tell us (here)
  the bug ID or error URL of the new crash.

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

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

[Desktop-packages] [Bug 1924753] Re: gnome-shell repeatedly crashing and core dumping

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

Thanks for the bug report. The log seems to confirm this is a duplicate
of bug 1886059, however what we really need is a stack trace from a
core/dump file. Please follow these instructions to get that:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

** This bug has been marked a duplicate of bug 1886059
   gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" 
[xcb_io.c:260]

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

Title:
  gnome-shell repeatedly crashing and core dumping

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This is a repeat of bug 1886059 with "MUTTER_SYNC=1" added to
  /etc/environment.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 16 06:26:22 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-31 (625 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-05-09 (341 days ago)

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

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

[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear fully when Ubuntu Dock is loaded

Can you rephrase that? Is this bug still occurring?

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

Title:
  Overview sometimes fails to appear or disappear fully when Ubuntu Dock
  is loaded

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

Bug description:
  When I press the "windows" or "options" or "super" key a list of
  running applications (like alt-tab) and a text window appears. I can
  choose from the running applications or write a command into the text
  window. After I chose an application or press ESC all this disappear
  and I can do my thing.

  Since trying 21.04 sometimes this 
  1. does not appear properly - there is no visible text window
  2. does not disappear - despite what I click on or what keys do I press this 
never disappear so I can not use my running applications or start anything new 
even from the menu. 

  I have to log out and in to break this.

  Disabling my gnome-shell extensions or using xorg instead of wayland
  does not helps.

  Since upgrading this morning this happens every time I press Super,
  not just occasionally, thus making my desktop unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  2 14:07:39 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-19 (378 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago)

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

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

[Desktop-packages] [Bug 1924889] Re: intel display drivers not working

2021-04-18 Thread Daniel Letzeisen

Probably a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905466

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

Title:
  intel display drivers not working

Status in xorg package in Ubuntu:
  New

Bug description:
  intel display drivers UHD intel graphics 750 not working in ubuntu
  20.10

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  Uname: Linux 5.11.15-051115-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 18 10:04:50 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus: rtl8821ce, 5.5.2.1, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation RocketLake-S GT1 [UHD Graphics 750] [8086:4c8a] (rev 04) 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2021-04-17 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Gigabyte Technology Co., Ltd. B560M DS3H AC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.15-051115-generic 
root=UUID=f0b245ca-169e-4fdc-80d3-14f66691147b ro quiet splash 
modprobe.blacklist=nouveau vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
   Identifier "Card0"
   Driver "intel"
   Option "AccelMethod" "sna"
   EndSection
  dmi.bios.date: 01/11/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F1
  dmi.board.asset.tag: Default string
  dmi.board.name: B560M DS3H AC
  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:bvnAmericanMegatrendsInternational,LLC.:bvrF1:bd01/11/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560MDS3HAC:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560MDS3HAC:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B560 MB
  dmi.product.name: B560M DS3H AC
  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.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/1924889/+subscriptions

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

[Desktop-packages] [Bug 1924889] Re: intel display drivers not working

2021-04-18 Thread Daniel Letzeisen

[6.039555] i915 :00:02.0: Your graphics device 4c8a is not
properly supported by the driver in this kernel version. To force driver
probe anyway, use i915.force_probe=4c8a module parameter or
CONFIG_DRM_I915_FORCE_PROBE=4c8a configuration option,or (recommended)
check for kernel updates.

So, boot with "i915.force_probe=4c8a" kernel parameter.

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

Title:
  intel display drivers not working

Status in xorg package in Ubuntu:
  New

Bug description:
  intel display drivers UHD intel graphics 750 not working in ubuntu
  20.10

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  Uname: Linux 5.11.15-051115-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 18 10:04:50 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus: rtl8821ce, 5.5.2.1, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation RocketLake-S GT1 [UHD Graphics 750] [8086:4c8a] (rev 04) 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2021-04-17 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Gigabyte Technology Co., Ltd. B560M DS3H AC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.15-051115-generic 
root=UUID=f0b245ca-169e-4fdc-80d3-14f66691147b ro quiet splash 
modprobe.blacklist=nouveau vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
   Identifier "Card0"
   Driver "intel"
   Option "AccelMethod" "sna"
   EndSection
  dmi.bios.date: 01/11/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F1
  dmi.board.asset.tag: Default string
  dmi.board.name: B560M DS3H AC
  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:bvnAmericanMegatrendsInternational,LLC.:bvrF1:bd01/11/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560MDS3HAC:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560MDS3HAC:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B560 MB
  dmi.product.name: B560M DS3H AC
  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.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/1924889/+subscriptions

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

[Desktop-packages] [Bug 1924899] Re: [TravelMate 8572G, Conexant CX20585, Speaker, Internal] fails after a while

2021-04-18 Thread Hui Wang

When speaker can't output sound, please run 'alsa-info' and 'pacmd list
> pacmd-list.txt', then check if speaker could work or not.  And upload
the alsa-info.txt and pacmd-list.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/1924899

Title:
  [TravelMate 8572G, Conexant CX20585, Speaker, Internal] fails after a
  while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After some time, about 30s speakers stop work, but headphones still
  work. After switching off to on  sound card profile sound in speakers
  can hear again until 30s.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giedrius   1981 F pulseaudio
   /dev/snd/controlC0:  giedrius   1981 F pulseaudio
   /dev/snd/pcmC0D0p:   giedrius   1981 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 18 11:57:39 2021
  InstallationDate: Installed on 2018-09-13 (947 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Sound works for a while, then breaks
  Title: [TravelMate 8572G, Conexant CX20585, Speaker, Internal] fails after a 
while
  UpgradeStatus: Upgraded to focal on 2020-08-16 (244 days ago)
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V1.28
  dmi.board.name: BAP50-CP
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrV1.28:bd07/20/2011:svnAcer:pnTravelMate8572G:pvrNotApplicable:rvnAcer:rnBAP50-CP:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
  dmi.product.name: TravelMate 8572G
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1923040] Re: en-gb thesaurus is missing

2021-04-18 Thread Gunnar Hjalmarsson

Hmm Mattia... This is the commit you made to fix that Debian bug 6 years
ago:

https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice-
dictionaries/-/commit/675b6f4f

Is there a reason to reconsider?

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

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

Title:
  en-gb thesaurus is missing

Status in libreoffice-dictionaries package in Ubuntu:
  Won't Fix
Status in libreoffice-dictionaries package in Debian:
  Unknown

Bug description:
  Problem: The EN-GB thesaurus is missing for LibreOffice.

  To observe: 
  1. Fresh install of 21.04, set Location to United Kingdom.
  2. Start LibreOffice Writer, choose the Tools menu.
  3. The "Thesaurus" item is greyed out.

  Root cause: there is no mythes-en-gb package available (but there is
  mythes-en-us).

  Workaround: 
  Give British English speakers the American English thesaurus i.e.
  symlink the US thesaurus by the GB one. 
  cd /usr/share/mythes; ln -s th_en_US_v2.dat th_en_GB_v2.dat;  ln -s 
th_en_US_v2.idx th_en_GB_v2.idx;

  Note: this report and tested workaround is on a fresh install of
  21.04, although this problem has been extant for years. There appears
  to be no GB version of the thesaurus. However, as UK-english and USA-
  english language is so similar, it would be OK to provide the
  thesaurus from the US package in the meantime as a symlink.

  
  For others who find this bug report while searching the same issue, note that 
  en-us is "english united-states"
  en-gb is "english great-britain", 
  -ukis "ukraine".  
  (Don't look for "english united-kingdom", en-uk, which doesn't exist).

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

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

[Desktop-packages] [Bug 1923040] Re: en-gb thesaurus is missing

2021-04-18 Thread RichardNeill

Thanks for your response. I looked a bit more into it, and it seems that
the official recommended way of dealing with this problem is the symlink
approach, and that en-GB is explicitly provided by the en-US package -
the compiler of the thesaurus intentionally combined both languages'
spelling variants as synonyms within the same thesaurus.

http://astarix.co.uk/2012/06/proper-british-language-tools-libreoffice/
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749204
https://askubuntu.com/questions/42850/how-do-i-add-english-uk-thesaurus-and-other-locales-to-libreoffice

In fact, it even gives the right British-English options. When I test it
in LibreOffice, and search for the word "hue", it prompts me with both
"color" (USA) and "colour" (GB). Similarly, it offers "aluminium" and
"aluminum" as synonyms, and "pavement" and "sidewalk".

So, please reconsider - or at least create a metapackage "mythes-en-GB"
which depends on "mythes-en" and contains the symlinks.

(After all, should a better solution arise i.e. someone compiles a
dedicated en-GB thesaurus, we can always improve, but this approach gets
99.9% of the way there, vs. nothing, - and in the unlikely event that
the GB-user ends up with a US-english word, such as "color", it is
already caught by the GB-english spellchecker).

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

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

Title:
  en-gb thesaurus is missing

Status in libreoffice-dictionaries package in Ubuntu:
  Won't Fix

Bug description:
  Problem: The EN-GB thesaurus is missing for LibreOffice.

  To observe: 
  1. Fresh install of 21.04, set Location to United Kingdom.
  2. Start LibreOffice Writer, choose the Tools menu.
  3. The "Thesaurus" item is greyed out.

  Root cause: there is no mythes-en-gb package available (but there is
  mythes-en-us).

  Workaround: 
  Give British English speakers the American English thesaurus i.e.
  symlink the US thesaurus by the GB one. 
  cd /usr/share/mythes; ln -s th_en_US_v2.dat th_en_GB_v2.dat;  ln -s 
th_en_US_v2.idx th_en_GB_v2.idx;

  Note: this report and tested workaround is on a fresh install of
  21.04, although this problem has been extant for years. There appears
  to be no GB version of the thesaurus. However, as UK-english and USA-
  english language is so similar, it would be OK to provide the
  thesaurus from the US package in the meantime as a symlink.

  
  For others who find this bug report while searching the same issue, note that 
  en-us is "english united-states"
  en-gb is "english great-britain", 
  -ukis "ukraine".  
  (Don't look for "english united-kingdom", en-uk, which doesn't exist).

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

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

[Desktop-packages] [Bug 1924932] Re: Nautilus default behaviour for executable scripts is poor

2021-04-18 Thread Rick

I agree

I think the default behavior in Nautilus Preferences should be "Ask what
to do" for "Executable Text Files"

gsettings set org.gnome.nautilus.preferences executable-text-activation
ask

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

Title:
  Nautilus default behaviour for executable scripts is poor

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  This is a papercut / quality of life issue that's really annoying me.

  On other file managers, if you set an .sh file as executable, it will
  offer to do something. With Ubuntu + Nautilus, it always by default
  just opens it in a text editor. This is really annoying and frankly a
  bad default to have.

  I know there's the right click menu to run as program, but since
  Ubuntu is trying to appeal to the masses here, good default behaviour
  is needed IMO.

  Example: you download a Linux game from GOG, you make it executable
  and then you double click to run -> wait a while as text editor tries
  to load a multiple GB installer .sh script, which is made with
  MojoSetup (it's a graphical app).

  Other file managers first ask what to do with a box like: "run? open
  as file? run in terminal?". Ubuntu should ideally do this too.

  I just don't think auto-opening big .sh executable files by default,
  in a text editor, is very good for users.

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

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

[Desktop-packages] [Bug 1924932] Re: Nautilus default behaviour for executable scripts is poor

2021-04-18 Thread Launchpad Bug Tracker

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

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

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

Title:
  Nautilus default behaviour for executable scripts is poor

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  This is a papercut / quality of life issue that's really annoying me.

  On other file managers, if you set an .sh file as executable, it will
  offer to do something. With Ubuntu + Nautilus, it always by default
  just opens it in a text editor. This is really annoying and frankly a
  bad default to have.

  I know there's the right click menu to run as program, but since
  Ubuntu is trying to appeal to the masses here, good default behaviour
  is needed IMO.

  Example: you download a Linux game from GOG, you make it executable
  and then you double click to run -> wait a while as text editor tries
  to load a multiple GB installer .sh script, which is made with
  MojoSetup (it's a graphical app).

  Other file managers first ask what to do with a box like: "run? open
  as file? run in terminal?". Ubuntu should ideally do this too.

  I just don't think auto-opening big .sh executable files by default,
  in a text editor, is very good for users.

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

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

[Desktop-packages] [Bug 1924932] [NEW] Nautilus default behaviour for executable scripts is poor

2021-04-18 Thread liamdawe

Public bug reported:

This is a papercut / quality of life issue that's really annoying me.

On other file managers, if you set an .sh file as executable, it will
offer to do something. With Ubuntu + Nautilus, it always by default just
opens it in a text editor. This is really annoying and frankly a bad
default to have.

I know there's the right click menu to run as program, but since Ubuntu
is trying to appeal to the masses here, good default behaviour is needed
IMO.

Example: you download a Linux game from GOG, you make it executable and
then you double click to run -> wait a while as text editor tries to
load a multiple GB installer .sh script, which is made with MojoSetup
(it's a graphical app).

Other file managers first ask what to do with a box like: "run? open as
file? run in terminal?". Ubuntu should ideally do this too.

I just don't think auto-opening big .sh executable files by default, in
a text editor, is very good for users.

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Description changed:

  This is a papercut / quality of life issue that's really annoying me.
  
  On other file managers, if you set an .sh file as executable, it will
  offer to do something. With Ubuntu + Nautilus, it always by default just
- opens it in a text editor. This is really annoying.
+ opens it in a text editor. This is really annoying and frankly a bad
+ default to have.
  
  I know there's the right click menu to run as program, but since Ubuntu
  is trying to appeal to the masses here, good default behaviour is needed
  IMO.
  
  Example: you download a Linux game from GOG, you make it executable and
  then you double click to run -> wait a while as text editor tries to
  load a multiple GB installer .sh script, which is made with MojoSetup
  (it's a graphical app).
  
  Other file managers first ask what to do with a box like: "run? open as
- file? run in terminal?"
+ file? run in terminal?". Ubuntu should ideally do this too.
  
  I just don't think auto-opening big .sh executable files by default, in
  a text editor, is very good for users.

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

Title:
  Nautilus default behaviour for executable scripts is poor

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  This is a papercut / quality of life issue that's really annoying me.

  On other file managers, if you set an .sh file as executable, it will
  offer to do something. With Ubuntu + Nautilus, it always by default
  just opens it in a text editor. This is really annoying and frankly a
  bad default to have.

  I know there's the right click menu to run as program, but since
  Ubuntu is trying to appeal to the masses here, good default behaviour
  is needed IMO.

  Example: you download a Linux game from GOG, you make it executable
  and then you double click to run -> wait a while as text editor tries
  to load a multiple GB installer .sh script, which is made with
  MojoSetup (it's a graphical app).

  Other file managers first ask what to do with a box like: "run? open
  as file? run in terminal?". Ubuntu should ideally do this too.

  I just don't think auto-opening big .sh executable files by default,
  in a text editor, is very good for users.

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

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

[Desktop-packages] [Bug 1924778] Re: Xorg buggy

2021-04-18 Thread 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/1924778

Title:
  Xorg buggy

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After boot and login the screen flashes and when i open i.e. Firefox i
  can see the desktop icons flashing

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 16 17:28:13 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2021-02-21 (53 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20ARS20N00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=d09e8852-af20-45ea-8147-e76491467e1b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/27/2020
  dmi.bios.release: 2.54
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJETA4WW (2.54 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARS20N00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJETA4WW(2.54):bd03/27/2020:br2.54:efr1.14:svnLENOVO:pn20ARS20N00:pvrThinkPadT440s:rvnLENOVO:rn20ARS20N00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARS20N00
  dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/1924778/+subscriptions

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

[Desktop-packages] [Bug 1924910] Re: Massive screen flashing artefacts - tearing

Firefox screenshot example

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924910/+attachment/5489522/+files/20210418_180028.jpg

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

Title:
  Massive screen flashing artefacts - tearing

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.10 x64 frequently updated.

  I noticed in the last week that after a while there are huge screen
  artefacts, that I would describe as flashing. Squares of screen flash,
  normally linked to widgets on screen.

  E.g.: the app bars on the left can start flashing blue, or parts of editors.
  I noticed it more in firefox, made worse by scrolling.
  VirtualBox is severely affected too.
  VS Code.

  It does not happen immediately and the feeling I get is that it starts
  happening when there is a lot on screen. For example has not happened
  at all in this session, but I have done little or nothing screen-
  heavy.

  The issue gets worse, then might settle down for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 18 13:53:28 2021
  DistUpgraded: 2020-11-27 20:39:33,916 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: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2020-02-01 (441 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic 
root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2020-11-27 (141 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/1924910/+subscriptions

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

[Desktop-packages] [Bug 1924910] Re: Massive screen flashing artefacts - tearing

Screenshot of damaged application bar.
See the blue square below VLC and compare with the other image.

There should be the zoom icon.

** Attachment added: "20210418_180321.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924910/+attachment/5489525/+files/20210418_180321.jpg

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

Title:
  Massive screen flashing artefacts - tearing

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.10 x64 frequently updated.

  I noticed in the last week that after a while there are huge screen
  artefacts, that I would describe as flashing. Squares of screen flash,
  normally linked to widgets on screen.

  E.g.: the app bars on the left can start flashing blue, or parts of editors.
  I noticed it more in firefox, made worse by scrolling.
  VirtualBox is severely affected too.
  VS Code.

  It does not happen immediately and the feeling I get is that it starts
  happening when there is a lot on screen. For example has not happened
  at all in this session, but I have done little or nothing screen-
  heavy.

  The issue gets worse, then might settle down for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 18 13:53:28 2021
  DistUpgraded: 2020-11-27 20:39:33,916 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: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2020-02-01 (441 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic 
root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2020-11-27 (141 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/1924910/+subscriptions

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

[Desktop-packages] [Bug 1924910] Re: Massive screen flashing artefacts - tearing

Screenshot of the normal application bar.

** Attachment added: "20210418_180315.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924910/+attachment/5489524/+files/20210418_180315.jpg

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

Title:
  Massive screen flashing artefacts - tearing

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.10 x64 frequently updated.

  I noticed in the last week that after a while there are huge screen
  artefacts, that I would describe as flashing. Squares of screen flash,
  normally linked to widgets on screen.

  E.g.: the app bars on the left can start flashing blue, or parts of editors.
  I noticed it more in firefox, made worse by scrolling.
  VirtualBox is severely affected too.
  VS Code.

  It does not happen immediately and the feeling I get is that it starts
  happening when there is a lot on screen. For example has not happened
  at all in this session, but I have done little or nothing screen-
  heavy.

  The issue gets worse, then might settle down for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 18 13:53:28 2021
  DistUpgraded: 2020-11-27 20:39:33,916 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: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2020-02-01 (441 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic 
root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2020-11-27 (141 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/1924910/+subscriptions

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

[Desktop-packages] [Bug 1924910] Re: Massive screen flashing artefacts - tearing

Firefox screenshot example

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924910/+attachment/5489523/+files/20210418_180038.jpg

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

Title:
  Massive screen flashing artefacts - tearing

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.10 x64 frequently updated.

  I noticed in the last week that after a while there are huge screen
  artefacts, that I would describe as flashing. Squares of screen flash,
  normally linked to widgets on screen.

  E.g.: the app bars on the left can start flashing blue, or parts of editors.
  I noticed it more in firefox, made worse by scrolling.
  VirtualBox is severely affected too.
  VS Code.

  It does not happen immediately and the feeling I get is that it starts
  happening when there is a lot on screen. For example has not happened
  at all in this session, but I have done little or nothing screen-
  heavy.

  The issue gets worse, then might settle down for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 18 13:53:28 2021
  DistUpgraded: 2020-11-27 20:39:33,916 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: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2020-02-01 (441 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic 
root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2020-11-27 (141 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/1924910/+subscriptions

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

[Desktop-packages] [Bug 1924910] Re: Massive screen flashing artefacts - tearing

Firefox screenshot example

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924910/+attachment/5489521/+files/20210418_180021.jpg

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

Title:
  Massive screen flashing artefacts - tearing

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.10 x64 frequently updated.

  I noticed in the last week that after a while there are huge screen
  artefacts, that I would describe as flashing. Squares of screen flash,
  normally linked to widgets on screen.

  E.g.: the app bars on the left can start flashing blue, or parts of editors.
  I noticed it more in firefox, made worse by scrolling.
  VirtualBox is severely affected too.
  VS Code.

  It does not happen immediately and the feeling I get is that it starts
  happening when there is a lot on screen. For example has not happened
  at all in this session, but I have done little or nothing screen-
  heavy.

  The issue gets worse, then might settle down for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 18 13:53:28 2021
  DistUpgraded: 2020-11-27 20:39:33,916 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: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2020-02-01 (441 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic 
root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2020-11-27 (141 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/1924910/+subscriptions

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

[Desktop-packages] [Bug 1924586] Re: Dead keys for French accents not working on Firefox Ubuntu package

2021-04-18 Thread baptx

The problem was fixed in about:config by changing the preference 
focusmanager.testmode from true to false and restarting Firefox. It looks like 
the preference was added when I tried to use a custom profile with Selenium 
WebDriver:
https://twitter.com/baptx/status/1383767656608632836
https://github.com/mozilla/geckodriver/issues/1773

** Bug watch added: github.com/mozilla/geckodriver/issues #1773
   https://github.com/mozilla/geckodriver/issues/1773

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

Title:
  Dead keys for French accents not working on Firefox Ubuntu package

Status in firefox package in Ubuntu:
  New

Bug description:
  Hello,

  Since at least last year, Firefox from the Ubuntu package fails French 
accents that require a combination of keys like ê and ï.
  However dead keys work on other programs like Thunderbird or Firefox binary 
from Mozilla.

  I guess this issue happened after an update of the Firefox Ubuntu
  package, can you fix it?

  Thanks.

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

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

[Desktop-packages] [Bug 1924910] [NEW] Massive screen flashing artefacts - tearing

Public bug reported:

On Ubuntu 20.10 x64 frequently updated.

I noticed in the last week that after a while there are huge screen
artefacts, that I would describe as flashing. Squares of screen flash,
normally linked to widgets on screen.

E.g.: the app bars on the left can start flashing blue, or parts of editors.
I noticed it more in firefox, made worse by scrolling.
VirtualBox is severely affected too.
VS Code.

It does not happen immediately and the feeling I get is that it starts
happening when there is a lot on screen. For example has not happened at
all in this session, but I have done little or nothing screen-heavy.

The issue gets worse, then might settle down for a while.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 18 13:53:28 2021
DistUpgraded: 2020-11-27 20:39:33,916 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: groovy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed
 virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
InstallationDate: Installed on 2020-02-01 (441 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic 
root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to groovy on 2020-11-27 (141 days ago)
dmi.bios.date: 11/11/2015
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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 groovy 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/1924910

Title:
  Massive screen flashing artefacts - tearing

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.10 x64 frequently updated.

  I noticed in the last week that after a while there are huge screen
  artefacts, that I would describe as flashing. Squares of screen flash,
  normally linked to widgets on screen.

  E.g.: the app bars on the left can start flashing blue, or parts of editors.
  I noticed it more in firefox, made worse by scrolling.
  VirtualBox is severely affected too.
  VS Code.

  It does not happen immediately and the feeling I get is that it starts
  happening when there is a lot on screen. For example has not happened
  at all in this session, but I have done little or nothing screen-
  heavy.

  The issue gets worse, then might settle down for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax
  ApportVersion: 2.20.11-0ubuntu50.5

[Desktop-packages] [Bug 1923040] Re: en-gb thesaurus is missing

2021-04-18 Thread Mattia Rizzolo

Thinking about this, I declie your proposal to symlink the en-us
thesaurus dictionary into en-gb.

en-gb and en-us are sufficiently different than I don't think we should
do it.

** Changed in: libreoffice-dictionaries (Ubuntu)
   Status: New => Won't Fix

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

Title:
  en-gb thesaurus is missing

Status in libreoffice-dictionaries package in Ubuntu:
  Won't Fix

Bug description:
  Problem: The EN-GB thesaurus is missing for LibreOffice.

  To observe: 
  1. Fresh install of 21.04, set Location to United Kingdom.
  2. Start LibreOffice Writer, choose the Tools menu.
  3. The "Thesaurus" item is greyed out.

  Root cause: there is no mythes-en-gb package available (but there is
  mythes-en-us).

  Workaround: 
  Give British English speakers the American English thesaurus i.e.
  symlink the US thesaurus by the GB one. 
  cd /usr/share/mythes; ln -s th_en_US_v2.dat th_en_GB_v2.dat;  ln -s 
th_en_US_v2.idx th_en_GB_v2.idx;

  Note: this report and tested workaround is on a fresh install of
  21.04, although this problem has been extant for years. There appears
  to be no GB version of the thesaurus. However, as UK-english and USA-
  english language is so similar, it would be OK to provide the
  thesaurus from the US package in the meantime as a symlink.

  
  For others who find this bug report while searching the same issue, note that 
  en-us is "english united-states"
  en-gb is "english great-britain", 
  -ukis "ukraine".  
  (Don't look for "english united-kingdom", en-uk, which doesn't exist).

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

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

[Desktop-packages] [Bug 1908429] Re: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::

2021-04-18 Thread Damien Lecan

Disk full today! Same error messages

syslog.* files about 30-40GB

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

Title:
  gnome-shell fills syslog: Attempting to run a JS callback during
  garbage collection. This is most likely caused by destroying a Clutter
  actor or GTK widget with ::destroy signal connected, or using the
  destroy(), dispose(), or remove() vfuncs. Because it would crash the
  application, it has been blocked. The offending callback was
  SourceFunc().

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

Bug description:
  Issue is explained in detail here: https://gitlab.gnome.org/GNOME
  /gnome-shell/-/issues/1868

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  Uname: Linux 5.4.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Dec 16 18:56:56 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-01 (258 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  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/1908429/+subscriptions

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

[Desktop-packages] [Bug 1924899] Re: [TravelMate 8572G, Conexant CX20585, Speaker, Internal] fails after a while

2021-04-18 Thread Ubuntu Foundations Team Bug Bot

** Package changed: ubuntu => alsa-driver (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/1924899

Title:
  [TravelMate 8572G, Conexant CX20585, Speaker, Internal] fails after a
  while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After some time, about 30s speakers stop work, but headphones still
  work. After switching off to on  sound card profile sound in speakers
  can hear again until 30s.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giedrius   1981 F pulseaudio
   /dev/snd/controlC0:  giedrius   1981 F pulseaudio
   /dev/snd/pcmC0D0p:   giedrius   1981 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 18 11:57:39 2021
  InstallationDate: Installed on 2018-09-13 (947 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Sound works for a while, then breaks
  Title: [TravelMate 8572G, Conexant CX20585, Speaker, Internal] fails after a 
while
  UpgradeStatus: Upgraded to focal on 2020-08-16 (244 days ago)
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V1.28
  dmi.board.name: BAP50-CP
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrV1.28:bd07/20/2011:svnAcer:pnTravelMate8572G:pvrNotApplicable:rvnAcer:rnBAP50-CP:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
  dmi.product.name: TravelMate 8572G
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1924899] [NEW] [TravelMate 8572G, Conexant CX20585, Speaker, Internal] fails after a while

2021-04-18 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

After some time, about 30s speakers stop work, but headphones still
work. After switching off to on  sound card profile sound in speakers
can hear again until 30s.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
Uname: Linux 5.4.0-72-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  giedrius   1981 F pulseaudio
 /dev/snd/controlC0:  giedrius   1981 F pulseaudio
 /dev/snd/pcmC0D0p:   giedrius   1981 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Sun Apr 18 11:57:39 2021
InstallationDate: Installed on 2018-09-13 (947 days ago)
InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel MID
Symptom_Jack: Speaker, Internal
Symptom_Type: Sound works for a while, then breaks
Title: [TravelMate 8572G, Conexant CX20585, Speaker, Internal] fails after a 
while
UpgradeStatus: Upgraded to focal on 2020-08-16 (244 days ago)
dmi.bios.date: 07/20/2011
dmi.bios.vendor: Phoenix
dmi.bios.version: V1.28
dmi.board.name: BAP50-CP
dmi.board.vendor: Acer
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenix:bvrV1.28:bd07/20/2011:svnAcer:pnTravelMate8572G:pvrNotApplicable:rvnAcer:rnBAP50-CP:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
dmi.product.name: TravelMate 8572G
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal
-- 
[TravelMate 8572G, Conexant CX20585, Speaker, Internal] fails after a while
https://bugs.launchpad.net/bugs/1924899
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 1924906] [NEW] [HP 350 G1, IDT 92HD95, Black Headphone Out, Right] No sound at all

2021-04-18 Thread iman ghassemi

Public bug reported:

i use ubuntu 20.04 in dual boot mood with windows 10. my laptop is hp probook 
350 G1
my laptop built in speakers works correctly but when i plug in my headphone 
there is no sound
would you please provide me a solution to hear sounds from my headphones?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  iman   1651 F pulseaudio
 /dev/snd/controlC1:  iman   1651 F pulseaudio
 /dev/snd/pcmC1D0c:   iman   1651 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 18 14:49:18 2021
InstallationDate: Installed on 2020-05-27 (325 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  iman   1651 F pulseaudio
 /dev/snd/controlC1:  iman   1651 F pulseaudio
 /dev/snd/pcmC1D0c:   iman   1651 F...m pulseaudio
Symptom_Jack: Black Headphone Out, Right
Symptom_Type: No sound at all
Title: [HP 350 G1, IDT 92HD95, Black Headphone Out, Right] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/04/2016
dmi.bios.release: 15.22
dmi.bios.vendor: Insyde
dmi.bios.version: F.16
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 21B8
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 46.20
dmi.chassis.asset.tag: 5CG420FPHC
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 70.32
dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd08/04/2016:br15.22:efr70.32:svnHewlett-Packard:pnHP350G1:pvr099810167:rvnHewlett-Packard:rn21B8:rvrKBCVersion46.20:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5336AN G=N L=CON B=HP S=242
dmi.product.name: HP 350 G1
dmi.product.sku: J4R60ES#ABV
dmi.product.version: 099810167
dmi.sys.vendor: Hewlett-Packard

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  [HP 350 G1, IDT 92HD95, Black Headphone Out, Right] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  i use ubuntu 20.04 in dual boot mood with windows 10. my laptop is hp probook 
350 G1
  my laptop built in speakers works correctly but when i plug in my headphone 
there is no sound
  would you please provide me a solution to hear sounds from my headphones?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  iman   1651 F pulseaudio
   /dev/snd/controlC1:  iman   1651 F pulseaudio
   /dev/snd/pcmC1D0c:   iman   1651 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 18 14:49:18 2021
  InstallationDate: Installed on 2020-05-27 (325 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  iman   1651 F pulseaudio
   /dev/snd/controlC1:  iman   1651 F pulseaudio
   /dev/snd/pcmC1D0c:   iman   1651 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Right
  Symptom_Type: No sound at all
  Title: [HP 350 G1, IDT 92HD95, Black Headphone Out, Right] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/04/2016
  dmi.bios.release: 15.22
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 21B8
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 46.20
  dmi.chassis.asset.tag: 5CG420FPHC
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 70.32
  dmi.modalias:

[Desktop-packages] [Bug 1920190] Re: Printing to ipp printer uses multiple GB of ram. pdftoraster and/or filter chain selection at fault?

2021-04-18 Thread Pratyush Ranjan

@manu
Can you please run the command "lpstat -a"  and "lpstat -v" in terminal and 
attach the listed output here.
In the error log I can see lots of these statements "HTTP_STATE_WAITING Closing 
for error 32 (Broken pipe)". This is typically related with cups-browsed not 
able to find print destinations. This may be related with the ram usage issue 
is there are too many calls.

Ideally these commands should list out all the destinations (ie.
printers). Your printer (Brother MFC L2710DW) should be listed. If not
then it will imply that the destinations are not discoverable or wrong
defaults has been set. In that case you may have to set the printer
using its PPD.

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

Title:
  Printing to ipp printer uses multiple GB of ram. pdftoraster and/or
  filter chain selection at fault?

Status in cups-filters package in Ubuntu:
  Confirmed

Bug description:
  I have an ipp/AirPrint capable printer (Brother MFC L2710DW) which 
automatically got added by Ubuntu (I'm on XUbuntu).
  Printing larger documents will easily use multiple gigabytes of ram. If the 
document is large enough this makes printing impossible or _very_ slow, as the 
process either gets killed or starts swapping.

  By watching htop and /proc/$pid/exe I was able to determine that the filter 
at fault seems to be /usr/lib/cups/filter/pdftoraster.
  Indeed, manually calling pdftoraster with similar arguments as passed by cups 
(taken from /proc/$pid/cmdline) I can observe the same memory use behaviour.
  Memory used seems to be linear in the number of pages and will reach around 
7GB for a 48 page test-document.

  I am not sure if the resolution should be to fix the memory usage of
  pdftoraster or to make cups select a different filter chain. I
  describe below how I first tried to debug the issue with the help of
  the Debian wiki on cupsfilter and wasn't able to get the same
  behaviour because cupsfilter would select a different filter chain
  (involving gstoraster instead of pdftoraster).

  For my current situation it would also be nice to know if there's some
  way for me to work around the issue until it's fixed by printing via
  the filter chain selected by cupsfilter. Should adding the printer
  manually via the xfce interface or the cups webinterface work?

  Please let me know if you need more information.

  ## Further info:

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

  $ apt-cache policy cups-filters
  cups-filters:
Installed: 1.27.4-1
Candidate: 1.27.4-1
Version table:
   *** 1.27.4-1 500
  500 http://at.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  In the system print settings the printer has the device URI 
"implicitclass://Brother_MFC_L2710DW_series/".
  From watching htop I get the impression that somewhere along the way that 
changes to "ipp://Brother%20MFC-L2710DW%20series._ipp._tcp.local/" (that's the 
argv[0] of the offending process, the binary for which is 
/usr/lib/cups/filter/pdftoraster).

  I am attaching test pdfs which exhibit the described memory use when used 
with pdftoraster like this:
  /usr/bin/time -v /usr/lib/cups/filter/pdftoraster 99 manu sometitle 1 
'PageSize=A4 output-format=apple-raster Resolution=600dpi' testdoc/test48.pdf > 
pdftorast.out

  The memory use and timings I get are in memory_use.txt.
  Information about the processes involved and their arguments when printing is 
in watching_printing.txt.

  
  ## Trying to debug with cupsfilter:

  I also tried to reproduce the issue by following the steps on the debian wiki 
about cupsfilter:
  https://wiki.debian.org/CUPSFilter
  Interestingly, I could not get cupsfilter to select the same filter chain.
  I am not sure which ppd I should be using, though. I tried with 
/etc/cups/ppd/Brother_MFC_L2710DW_series.ppd and with a ppd generated by
  driverless cat 'ipp://Brother%20MFC-L2710DW%20series._ipp._tcp.local/'
  The former only outputs pdf:

  $ /usr/sbin/cupsfilter -p Brother_MFC_L2710DW_series.ppd -m printer/foo -o 
number-up=2 testdoc/test96.pdf -e --list-filters
  pdftopdf

  The latter uses gstoraster:

  $ /usr/sbin/cupsfilter -p driverless.ppd -m printer/foo -o number-up=2 
testdoc/test96.pdf -e --list-filters
  pdftopdf
  gstoraster
  rastertopwg

  Running either without the --list-filters option finishes reasonably
  fast and doesn't use excessive ram.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1920190/+subscriptions

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

[Desktop-packages] [Bug 1924852] Re: Selected output device in Sound settings is not persisted across restarts

2021-04-18 Thread Filippo Ghibellini

# Temporary Workaround for others who face this

Get the list of available sinks:

```
$ pactl list sinks

Sink #1
State: IDLE
Name: 
alsa_output.usb-Audio_Technica_Corp_ATR2100x-USB_Microphone-00.analog-stereo
Description: ATR2100x-USB Microphone Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 26
Mute: no
Volume: front-left: 5282 /   8% / -65.62 dB,   front-right: 49145 /  
75% / -7.50 dB
balance 0.89
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: 
alsa_output.usb-Audio_Technica_Corp_ATR2100x-USB_Microphone-00.analog-stereo.monitor
Latency: 34631 usec, configured 4 usec
Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY 
Properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "USB Audio"
alsa.id = "USB Audio"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "3"
alsa.card_name = "ATR2100x-USB Microphone"
alsa.long_card_name = "Audio Technica Corp ATR2100x-USB 
Microphone at usb-:08:00.3-3.3, full speed"
alsa.driver_name = "snd_usb_audio"
device.bus_path = "pci-:08:00.3-usb-0:3.3:1.0"
sysfs.path = 
"/devices/pci:00/:00:08.1/:08:00.3/usb3/3-3/3-3.3/3-3.3:1.0/sound/card3"
udev.id = "usb-Audio_Technica_Corp_ATR2100x-USB_Microphone-00"
device.bus = "usb"
device.vendor.id = "0909"
device.vendor.name = "Audio-Technica Corp."
device.product.id = "004d"
device.product.name = "ATR2100x-USB Microphone"
device.serial = "Audio_Technica_Corp_ATR2100x-USB_Microphone"
device.form_factor = "microphone"
device.string = "front:3"
device.buffering.buffer_size = "352800"
device.buffering.fragment_size = "176400"
device.access_mode = "mmap+timer"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "ATR2100x-USB Microphone Analog Stereo"
module-udev-detect.discovered = "1"
device.icon_name = "audio-input-microphone-usb"
Ports:
analog-output-headphones: Headphones (priority: 9900)
Active Port: analog-output-headphones
Formats:
pcm

Sink #2
State: SUSPENDED
Name: alsa_output.pci-_08_00.4.analog-stereo
Description: Starship/Matisse HD Audio Controller Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 27
Mute: no
Volume: front-left: 19660 /  30% / -31.37 dB,   front-right: 19660 /  
30% / -31.37 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: alsa_output.pci-_08_00.4.analog-stereo.monitor
Latency: 0 usec, configured 0 usec
Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY 
Properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "ALC1220 Analog"
alsa.id = "ALC1220 Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "2"
alsa.card_name = "HD-Audio Generic"
alsa.long_card_name = "HD-Audio Generic at 0xfc80 irq 73"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:08:00.4"
sysfs.path = 
"/devices/pci:00/:00:08.1/:08:00.4/sound/card2"
device.bus = "pci"
device.vendor.id = "1022"
device.vendor.name = "Advanced Micro Devices, Inc. [AMD]"
device.product.id = "1487"
device.product.name = "Starship/Matisse HD Audio Controller"
device.string = "front:2"
device.buffering.buffer_size = "17664"
device.buffering.fragment_size = "2944"
device.access_mode = "mmap"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Starship/Matisse HD Audio

[Desktop-packages] [Bug 1924903] [NEW] PulseAudio automatically switches to HDMI sound output on every boot

2021-04-18 Thread jixbo

Public bug reported:

After upgrading to an AMD laptop (Thinkpad T14) and Ubuntu 21.04, when I
boot the laptop my audio device has changed to HDMI, instead of
remembering my headphones from last session.

Screen remains plugged in, but takes a few seconds to wake up while
booting.

Commenting out
 load-module module-switch-on-port-available
in  /etc/pulse/default.pa fixes the issue.

Might be related to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570

Devices:

Family 17h (Models 10h-1fh) HD Audio Controller Speaker + Headphones
Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD 
Audio Controller
Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller


HD-Audio Generic HDMI1 Output
Multimedia controller: Advanced Micro Devices, Inc. [AMD] 
Raven/Raven2/FireFlight/Renoir Audio Processor (rev 01)
Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor

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

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

Title:
  PulseAudio automatically switches to HDMI sound output on every boot

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After upgrading to an AMD laptop (Thinkpad T14) and Ubuntu 21.04, when
  I boot the laptop my audio device has changed to HDMI, instead of
  remembering my headphones from last session.

  Screen remains plugged in, but takes a few seconds to wake up while
  booting.

  Commenting out
   load-module module-switch-on-port-available
  in  /etc/pulse/default.pa fixes the issue.

  Might be related to:
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570

  Devices:

  Family 17h (Models 10h-1fh) HD Audio Controller Speaker + Headphones
  Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) 
HD Audio Controller
Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller

  
  HD-Audio Generic HDMI1 Output
  Multimedia controller: Advanced Micro Devices, Inc. [AMD] 
Raven/Raven2/FireFlight/Renoir Audio Processor (rev 01)
Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor

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

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

[Desktop-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

** Also affects: xfwm4 via
   https://bugzilla.xfce.org/show_bug.cgi?id=16716
   Importance: Unknown
   Status: Unknown

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

Title:
  Regression: block staircase display with side-by-side monitors of
  different pixel widths

Status in xf86-video-amd:
  Unknown
Status in Xfwm4:
  Unknown
Status in xfwm4 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Triaged
Status in xfwm4 source package in Focal:
  In Progress
Status in xserver-xorg-video-amdgpu source package in Focal:
  Triaged
Status in xfwm4 source package in Groovy:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Groovy:
  Triaged

Bug description:
  [Impact]

   * This issue affects AMD graphics on Xfwm4 4.14.1.

   * Windows are displayed staggered with a multi-window layout

  [Test Plan]

   * Use AMD graphics drivers

   * Connect a second display at a different resolution

   * Open multiple windows

   * While the issue is present, the windows and desktop will appeared
  staggered

   * Once fixed, they display normally.

  [Where problems could occur]

   * Regression potential should be relatively low, as the release
  between 4.14.1 and 4.14.5 are bug releases.

   * With window managers, some changes could lead to different behavior
  and other broken displays. Non-AMD graphics users should also test for
  regressions.

  [Other Info]
   
   * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: 
https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44

  [Original Report]

  Update based on further research.

  This only happens when the secondary external display is operating at
  a different pixel width to the internal. In this case eDP is 1920x1080
  whereas the external HDMI-A-0 is natively 1680x1050.

  It is caused by xfwm4's recent switch from using glx to xpresent for
  AMD GPUs.

  The underlying bug is in the AMD driver.

  I was able to reproduce on an external 1920x1200 display only when it
  was set to a non-native 1680x1050 resolution.

  ---
  Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred 
initially on the laptop that is having package upgrades applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET32W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias:

[Desktop-packages] [Bug 1924895] [NEW] Settings crashes as soon as it is opened

2021-04-18 Thread Vadim Peretokin

Public bug reported:

Just opening the settings causes it to almost immediately crash.


❯ gnome-control-center


(gnome-control-center:12969): dconf-WARNING **: 09:14:26.286: failed to commit 
changes to dconf: Could not connect: Connection refused
Error creating rfkill proxy: (null)
Segmentation fault (core dumped)
~ 
❯ 
~ 
❯ gnome-control-center user-accounts

(gnome-control-center:13142): dconf-WARNING **: 09:15:10.855: failed to
commit changes to dconf: Could not connect: Connection refused

(gnome-control-center:13142): dconf-WARNING **: 09:15:11.085: failed to commit 
changes to dconf: Could not connect: Connection refused
Segmentation fault (core dumped)
~ took 16s 
❯ gdb gnome-control-center
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gnome-control-center...
(No debugging symbols found in gnome-control-center)
(gdb) r
Starting program: /usr/bin/gnome-control-center 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffea9e0700 (LWP 13237)]
[New Thread 0x7fffdf05b700 (LWP 13238)]
[New Thread 0x7fffde85a700 (LWP 13239)]
[New Thread 0x7fffde059700 (LWP 13240)]
[New Thread 0x7fffdd858700 (LWP 13241)]
[New Thread 0x7fffdcc17700 (LWP 13242)]
[New Thread 0x7fffc7fff700 (LWP 13243)]
[New Thread 0x7fffc77fe700 (LWP 13244)]
[New Thread 0x7fffc6ffd700 (LWP 13245)]

(gnome-control-center:13233): dconf-WARNING **: 09:15:38.054: failed to commit 
changes to dconf: Could not connect: Connection refused
Error creating rfkill proxy: (null)

Thread 8 "pool-gnome-cont" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffc7fff700 (LWP 13243)]
0x77ca6ac3 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
(gdb) bt
#0  0x77ca6ac3 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x77ca6e1c in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7637e5a1 in __nptl_deallocate_tsd () at pthread_create.c:301
#3  0x7637f62a in __nptl_deallocate_tsd () at pthread_create.c:256
#4  start_thread (arg=) at pthread_create.c:488
#5  0x762a6293 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
(gdb) q
A debugging session is active.

Inferior 1 [process 13233] will be killed.

Quit anyway? (y or n) y
~ took 20s 
❯ gnome-control-center --version
gnome-control-center 3.36.5
~ 
❯ ubuntu-bug gnome-control-center

(gio open:15213): GLib-GIO-CRITICAL **: 09:17:11.048:
g_dbus_connection_flush: assertion 'G_IS_DBUS_CONNECTION (connection)'
failed

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.5-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
Uname: Linux 5.4.0-71-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 18 09:16:22 2021
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-02-15 (1522 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Settings crashes as soon as it is opened

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

Bug description:
  Just opening the settings causes it to almost immediately crash.

  
  ❯ gnome-control-center

  
  (gnome-control-center:12969): dconf-WARNING **: 09:14:26.286: failed to 
commit changes to dconf: Could not connect: Connection refused
  Error creating rfkill proxy: (null)
  Segmentation fault (core dumped)
  ~ 
  ❯ 
  ~ 
  ❯ gnome-control-center user-accounts

  (gnome-control-center:13142): dconf-WARNING **: 09:15:10.855: failed
  to commit changes to dconf: Could not connect: Connection refused

  (gnome-control-center:13142): dconf-WARNING **: 09:15:11.085: failed to 
commit changes to dconf: Could not connect: Connection refused
  Segmentation fault (core dumped)
  ~ took 16s 
  ❯ gdb gnome-control-center

[Desktop-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

** No longer affects: libxcb (Ubuntu)

** No longer affects: libxcb (Ubuntu Focal)

** No longer affects: libxcb (Ubuntu Groovy)

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: xserver-xorg-video-amdgpu (Ubuntu Focal)
   Status: Incomplete => Triaged

** Changed in: xserver-xorg-video-amdgpu (Ubuntu Groovy)
   Status: Incomplete => Triaged

** Changed in: xserver-xorg-video-amdgpu (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: xserver-xorg-video-amdgpu (Ubuntu Groovy)
   Importance: Undecided => High

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

Title:
  Regression: block staircase display with side-by-side monitors of
  different pixel widths

Status in xf86-video-amd:
  Unknown
Status in xfwm4 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Triaged
Status in xfwm4 source package in Focal:
  In Progress
Status in xserver-xorg-video-amdgpu source package in Focal:
  Triaged
Status in xfwm4 source package in Groovy:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Groovy:
  Triaged

Bug description:
  [Impact]

   * This issue affects AMD graphics on Xfwm4 4.14.1.

   * Windows are displayed staggered with a multi-window layout

  [Test Plan]

   * Use AMD graphics drivers

   * Connect a second display at a different resolution

   * Open multiple windows

   * While the issue is present, the windows and desktop will appeared
  staggered

   * Once fixed, they display normally.

  [Where problems could occur]

   * Regression potential should be relatively low, as the release
  between 4.14.1 and 4.14.5 are bug releases.

   * With window managers, some changes could lead to different behavior
  and other broken displays. Non-AMD graphics users should also test for
  regressions.

  [Other Info]
   
   * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: 
https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44

  [Original Report]

  Update based on further research.

  This only happens when the secondary external display is operating at
  a different pixel width to the internal. In this case eDP is 1920x1080
  whereas the external HDMI-A-0 is natively 1680x1050.

  It is caused by xfwm4's recent switch from using glx to xpresent for
  AMD GPUs.

  The underlying bug is in the AMD driver.

  I was able to reproduce on an external 1920x1200 display only when it
  was set to a non-native 1680x1050 resolution.

  ---
  Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred 
initially on the laptop that is having package upgrades applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO

[Desktop-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

xfwm4 (4.14.2-1) unstable; urgency=medium

  * Team upload.

  [ Debian Janitor ]
  * Trim trailing whitespace.
  * Bump debhelper from old 11 to 12.
  * Set upstream metadata fields: Name (from ./configure), Repository.
  * Fix day-of-week for changelog entry 4.0.0.final-1.

  [ Mateusz Łukasik ]
  * d/watch: Update to working version.
  * New upstream version 4.14.1
- Fix raise delay (Closes: #940796)
  * d/control: update standards version to 4.5.0

  [ Unit 193 ]
  * New upstream version 4.14.2.
- Fix window title alignment (Closes: #953112)
  * d/control: R³: no.

 -- Unit 193   Sun, 03 May 2020 08:29:52 -0400

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

** Tags added: regression-release

** Changed in: xfwm4 (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: xfwm4 (Ubuntu Groovy)
   Importance: Undecided => High

** Project changed: linux => xf86-video-amd

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

Title:
  Regression: block staircase display with side-by-side monitors of
  different pixel widths

Status in xf86-video-amd:
  Unknown
Status in libxcb package in Ubuntu:
  Incomplete
Status in xfwm4 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete
Status in libxcb source package in Focal:
  Incomplete
Status in xfwm4 source package in Focal:
  In Progress
Status in xserver-xorg-video-amdgpu source package in Focal:
  Incomplete
Status in libxcb source package in Groovy:
  Incomplete
Status in xfwm4 source package in Groovy:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Groovy:
  Incomplete

Bug description:
  [Impact]

   * This issue affects AMD graphics on Xfwm4 4.14.1.

   * Windows are displayed staggered with a multi-window layout

  [Test Plan]

   * Use AMD graphics drivers

   * Connect a second display at a different resolution

   * Open multiple windows

   * While the issue is present, the windows and desktop will appeared
  staggered

   * Once fixed, they display normally.

  [Where problems could occur]

   * Regression potential should be relatively low, as the release
  between 4.14.1 and 4.14.5 are bug releases.

   * With window managers, some changes could lead to different behavior
  and other broken displays. Non-AMD graphics users should also test for
  regressions.

  [Other Info]
   
   * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: 
https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44

  [Original Report]

  Update based on further research.

  This only happens when the secondary external display is operating at
  a different pixel width to the internal. In this case eDP is 1920x1080
  whereas the external HDMI-A-0 is natively 1680x1050.

  It is caused by xfwm4's recent switch from using glx to xpresent for
  AMD GPUs.

  The underlying bug is in the AMD driver.

  I was able to reproduce on an external 1920x1200 display only when it
  was set to a non-native 1680x1050 resolution.

  ---
  Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred 
initially on the laptop that is having package upgrades applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64

[Desktop-packages] [Bug 1922792] Re: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi