date:20210409

[Expired for ubuntu-drivers-common (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  gpu-manager crashes

Status in ubuntu-drivers-common package in Ubuntu:
  Expired

Bug description:
  gpu-manager has no man page and when running with -h it crashes:

  $ gpu-manager -h
  Segmentation fault (core dumped)
  $ gpu-manager --help 
  gpu-manager: unrecognized option '--help'

  If this is really something that should not be run, better hide it
  away from $PATH...

  But the command line option handling should be fixed anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-drivers-common 1:0.2.91.9
  ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11
  Uname: Linux 3.16.0-41-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jul  7 08:55:08 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-04-08 (89 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1914877] Re: Stuttering video playback

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

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

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

Title:
  Stuttering video playback

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Something has regressed recently to cause stuttering video playback.
  especially at the Cmore.fi. This makes sports broadcasts very
  uncomfortable to look at. The issue appeared about 1-2 weeks ago, so
  it is very recent.

  It used to work fine on this HW for months, but not anymore.

  It does not depend on the browser, as the issue is the same on Firefox or 
Chrome.
  It does not depend on the DE, as KDE Neon suffers from the same issue.

  I had to install Windows 10, which of course is a tragedy. Posting
  this report from a 20.04.2 live USB session and the issue is
  reproduced with this as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-decode-450_450.102.04-0ubuntu0.20.04.1_amd64.deb
  CasperMD5CheckResult: skip
  CasperVersion: 1.445.1
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  6 20:01:13 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Generation Core Processor Family Integrated Graphics 
Controller [17aa:309e]
  LiveMediaBuild: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  MachineType: LENOVO 10AXS1NG00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2019
  dmi.bios.release: 1.82
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FHKT82AUS
  dmi.board.name: SHARKBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  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.ec.firmware.release: 1.36
  dmi.modalias: 
dmi:bvnLENOVO:bvrFHKT82AUS:bd05/06/2019:br1.82:efr1.36:svnLENOVO:pn10AXS1NG00:pvrThinkCentreM73:rvnLENOVO:rnSHARKBAY:rvr0B98401WIN:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 10AXS1NG00
  dmi.product.sku: LENOVO_MT_10AX
  dmi.product.version: ThinkCentre M73
  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.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1922464] Re: GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'

This bug was fixed in the package gtk+3.0 - 3.24.25-1ubuntu4

---
gtk+3.0 (3.24.25-1ubuntu4) hirsute; urgency=medium

  * debian/patches/git_wayland_fonts.patch:
- cherry pick a fix for GTK applications hitting errors under wayland
  on GNOME40, it isn't in Ubuntu yet but it should make testing the
  new version easier and also updates packages are provided in ppa
  already for testing so it should avoid surprises for those users
  (lp: #1922464)

 -- Sebastien Bacher   Thu, 08 Apr 2021 11:17:35
+0200

** Changed in: gtk+3.0 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings-
  daemon.plugins.xsettings' does not contain a key named 'antialiasing'

Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  Applications running with GTK < 3.24.26 crash when running under GNOME
  40. This was fixed in GTK 3.24.26 by MR
  https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/3219

  Please package either current GTK 3 (3.24.28) or include the given MR
  in the current build.

  Thanks!

  Example crash:

  ```
  Starting program: /home/mjog/Projects/GNOME/geary/+build/test/test-client
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffeb8a7640 (LWP 58239)]
  [New Thread 0x7fffeb086640 (LWP 58240)]
  [New Thread 0x7fffea839640 (LWP 58241)]

  (test-client:58235): GLib-GIO-ERROR **: 10:42:55.448: Settings schema
  'org.gnome.settings-daemon.plugins.xsettings' does not contain a key
  named 'antialiasing'

  Thread 1 "test-client" received signal SIGTRAP, Trace/breakpoint trap.
  0x774a5ea7 in g_log_structured_array () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  (gdb) bt
  #0  0x774a5ea7 in g_log_structured_array ()
  at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #1  0x774a62b9 in g_log_default_handler () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x774a64fe in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #3  0x774a67b3 in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #4  0x7735d9d1 in  () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
  #5  0x7735e030 in  () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
  #6  0x773625d1 in g_settings_get_enum () at 
/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #7  0x710d90ea in update_xft_settings (screen=0x55a8d810)
  at wayland/../../../../../gdk/wayland/gdkscreen-wayland.c:404
  #8  0x710d3c7d in init_settings (screen=0x55a8d810)
  at wayland/../../../../../gdk/wayland/gdkscreen-wayland.c:828
  #9  _gdk_wayland_screen_new (display=0x55a8a0e0)
  at wayland/../../../../../gdk/wayland/gdkscreen-wayland.c:1320
  #10 _gdk_wayland_display_open (display_name=)
  at wayland/../../../../../gdk/wayland/gdkdisplay-wayland.c:617
  #11 0x71072635 in gdk_display_manager_open_display
  (manager=, name=0x0) at 
../../../../gdk/gdkdisplaymanager.c:462
  #12 0x76d011fb in gtk_init_check (argc=, 
argv=)
  at ../../../../gtk/gtkmain.c:1110
  #13 gtk_init_check (argc=, argv=)
  at ../../../../gtk/gtkmain.c:1102
  #14 0x76d0122d in gtk_init (argc=, argv=)
  at ../../../../gtk/gtkmain.c:1167
  #15 0x555b4854 in _vala_main (args=0x7fffdda8, args_length1=1)
  at ../test/test-client.vala:32
  #16 0x555b5213 in main (argc=1, argv=0x7fffdda8) at 
../test/test-client.vala:9
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libgtk-3-0 3.24.25-1ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sun Apr  4 11:11:05 2021
  InstallationDate: Installed on 2018-08-13 (964 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to hirsute on 2021-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1922464/+subscriptions

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

[Desktop-packages] [Bug 1923273] Re: libcaca buffer-overflow

2021-04-09 Thread Seth Arnold

** Information type changed from Private Security to Public Security

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

Title:
  libcaca buffer-overflow

Status in libcaca package in Ubuntu:
  New

Bug description:
  Hello Ubuntu Security Team
  I use libfuzzer to test libcaca api .I found two crash

  - https://github.com/cacalabs/libcaca/issues/53

  - https://github.com/cacalabs/libcaca/issues/54

  
  ## Vendor of Product
  https://github.com/cacalabs/libcaca

  
  ## Affected Product Code Base
  libcaca e4968ba
  
  ## Affected Component
  affected component:libcaca.so
  
  ## Affected source code file
  affected source code file(As call stack):

 ->caca_export_canvas_to_memory()  in
  libcaca/caca/codec/export.c

 ->caca_export_memory()in
  libcaca/caca/codec/export.c

 -> export_tga()in  
libcaca/caca/codec/export.c

-> export_troff()   in  
libcaca/caca/codec/export.c

   
  ## Attack Type
  Context-dependent

  
  ## Impact Denial of Service
  true

  
  ## Reference
  https://github.com/cacalabs/libcaca

  
  ## Discoverer
  fdgnneig

  
  ## Verification process and POC

  ### Verification steps：

  1.Get the source code of libcaca:

  2.Compile the libcaca.so library:

  ```shell
  $ cd libcaca
  $ apt-get install automake libtool pkg-config -y
  $ ./bootstrap
  $ ./configure
  $ make

  3.Run POC.sh to compile poc_troff.cc 、poc_tga.cc

  4.Run POC

  
  POC.sh
  ```
  cat << EOF > poc_troff.cc
  #include "config.h"
  #include "caca.h"
  //#include "common-image.h"
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  using namespace std;

  extern "C"  int LLVMFuzzerTestOneInput(const uint8_t *Data, size_t
  Size) {

   if(Size<8) return 0;
   size_t len=0;
   char* buffer = (char*)malloc(Size+1);
   memset(buffer,0,Size);
   memcpy(buffer,Data,Size);
   buffer[Size]='\0';
   caca_canvas_t *cv;
   cv = caca_create_canvas(0,0);
   for(int i=0;i<4;i++)
 caca_create_frame(cv,0);
   for(int i=0;i<4;i++){
 caca_set_frame(cv,i);
 caca_import_canvas_from_memory(cv,buffer,strlen(buffer),"");
   }
   void* reData = caca_export_canvas_to_memory(cv,"troff",&len);
   if(reData!=NULL) free(reData);
   caca_free_canvas(cv);
   cv=NULL;
   free(buffer);
   buffer=NULL;

  }

  
  int main(int args,char* argv[]){

 size_t  len = 0;
 unsigned char buffer[] = 
{0x5f,0x20,0x6f,0x75,0x6e,0x64,0x0a,0x40,0x11};
 len = sizeof(buffer)/sizeof(unsigned char);
 LLVMFuzzerTestOneInput((const uint8_t*)buffer,len);
 printf("%d\n",sizeof(buffer)/sizeof(unsigned char));

 return 0;

  }
  EOF

  clang++ -g poc_troff.cc -O2 -fno-omit-frame-pointer -fsanitize=address
  -I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/  -o
  poc_troff

  
  cat << EOF > poc_tga.cc
  #include "config.h"
  #include "caca.h"
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  using namespace std;

  extern "C"  int LLVMFuzzerTestOneInput(const uint8_t *Data, size_t
  Size) {

   if(Size<8) return 0;
   size_t len=0;
   char* buffer = (char*)malloc(Size+1);
   memset(buffer,0,Size);
   memcpy(buffer,Data,Size);
   buffer[Size]='\0';
   caca_canvas_t *cv;
   cv = caca_create_canvas(0,0);
   for(int i=0;i<4;i++)
 caca_create_frame(cv,0);
   for(int i=0;i<4;i++){
 caca_set_frame(cv,i);
 caca_import_canvas_from_memory(cv,buffer,strlen(buffer),"");
   }
   void* reData = caca_export_canvas_to_memory(cv,"tga",&len);
   if(reData!=NULL) free(reData);
   caca_free_canvas(cv);
   cv=NULL;
   free(buffer);
   buffer=NULL;
 return 0;
  }

  int main(int args,char* argv[]){

 size_t  len = 0;
 unsigned char buffer[] = 
{0x00,0xff,0xff,0x23,0x64,0x72,0x23,0x20,0x11};
 len = sizeof(buffer)/sizeof(unsigned char);
 LLVMFuzzerTestOneInput((const uint8_t*)buffer,len);
 printf("%d\n",sizeof(buffer)/sizeof(unsigned char));

 return 0;
  }
  EOF

  clang++ -g poc_tga.cc -O2 -fno-omit-frame-pointer -fsanitize=addre

Re: [Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2021-04-09 Thread Coiby Xu

On Mon, Apr 05, 2021 at 03:22:24PM -, James Hennig wrote:
>Since this is the main thread on the Internet about this issue, I
>suppose it is appropriate to post here even though I am using Manjaro.
>
>- This issue is non-present on a Thinkpad 3 14ADA05 with touchpad
>MSFT0001:00 06CB:CE2D on kernel 5.9.16-1 which uses i2c_hid. It is not
>elantech or designware (doesn't load the associated specific i2c
>drivers). Installing an entirely new keyboard panel with a new touchpad,
>essentially rebuilding the entire laptop does not address this issue. It
>is the same model touchpad for this specific laptop model even if you
>order a new one (unless I got bad luck of the draw).

If kernel 5.9.16-1 with i2c_hid driver worked for you, I'd suggest you
stick with the i2c_hid that comes with kernel 5.9.16-1 and build a
stand-alone driver for newer kernel and replace newer i2c_hid driver.

>
>- The issue becomes present on kernel 5.10.23-1 (and previous versions
>of 5.10) up to 5.12rc3. Have not tried compiling 5.12rc5, but no reason
>to believe it would work.
>
>The touchpad will fail to be recognized and work on bootup between 1-30
>reboots. I have tried many things such as different kernels and
>GRUB_CMDLINE_LINUX_DEFAULT options, yes even checking to set the kernel
>config option others are suggesting (Manjaro removed then reinstated the
>CONFIG_I2C_HID_ACPI=m option). I also tore apart kernels 5.9 and 5.10 to
>look at the pinctrl-amd.c driver and found that there was no difference
>between the two on these kernels, so it is something other than what
>https://launchpadlibrarian.net/500948605/0303-pinctrl-amd2.patch
>addresses since it works on the former kernel but not the latter. Also,
>the patch fails to apply on 5.12rc5.
>
>I don't really know how to compare the entire torn-apart kernels 5.9 and
>5.10 to try and find what change(s) could possibly cause this bug.
>Hopefully someone else knows how to?
>
>Might be able to get somewhere if so...
>
>Other mods might be replacing the touchpad with a model not designed for
>the laptop, but I don't know where to start with that either.
>

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  point

Re: [Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2021-04-09 Thread Coiby Xu

On Sat, Mar 06, 2021 at 03:24:35PM -, Shatadru Banerjee wrote:
>I want to politely point out that this thread is not helping anymore; it
>has become mere chit-chat. Things were confusing to begin with and
>unfortunately it is becoming more confusing. What is the fix? Does is
>work with a particular kernel? The use of mainline kernel 5.11 should
>solve all the problems? Is this nvidia gpu issue related to the solution
>to the trackpad? Why can't the external monitor work, even with the AMD
>iGPU? Most importantly, what one should do to have a working touchpad,
>working nvida gpu and working external monitor? Please reply only if you
>know what are you going to write.


On Sat, Mar 13, 2021 at 03:17:55AM -, Shatadru Banerjee wrote:
>I did not mention brightness issue. With 5.11.3 the brightness does not
>work flawlessly however there are more serious problems. 1. External
>monitor not detected via HDMI, 2. still the wifi is not stable, 3.
>cannot switch to nvidia.

On Thu, Apr 01, 2021 at 03:06:02AM -, Shatadru Banerjee wrote:
>This thread has gone from stupid to completely pointless.

Sorry to know this thread didn't help you. This thread only deals with 
the touchpad issue and it's too long to follow. But I've summarized
what's needed in the beginning of the bug report. As far as I know, the
fix for the touchpad doesn't affect nvidia issue. In fact, I don't
experience any of the issues you mentioned including external monitor 
not detected and brightness issue on Manjara with kernel=5.11.6-1 
after installing optimus manager [1]. [1] is "a port to Archlinux of the
nvidia-prime solution created by Canonical for Ubuntu" so I assume the
issues of external monitor and brightness don't bother Ubuntu users
either.

[1] https://github.com/Askannz/optimus-manager/

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Button

[Desktop-packages] [Bug 1923270] [NEW] NVIDIA 340.108 Random Core Dump With Xorg on Linux Kernel 5.12.0-rc5

2021-04-09 Thread Ejmarkow

Public bug reported:

NVIDIA 340.108 with all patches (up to the 5.11 patch) is randomly
crashing (Core Dump) with Xorg 1.20.10 on Linux Kernel 5.12.0-rc5. It
works fine on the previous Kernel 5.11.

The Core Dumps (crashes) are not frequent, but randomly occur, and are
always triggered while using Google Chrome.

When the bug occurs, Chrome closes, Xorg closes and the system logs out
from Lightdm, but doesn't completely shut down the computer. I'm able to
log back in via Lightdm.

The NVIDIA driver modules build process with required patches (which I
apply and compile manually) is FINE, with NO errors during the
compilation or after it. Both nvidia and nvidia_uvm modules load without
any problem.

I'm using openSUSE Linux, but always use the patches provided here which
always work for me.

uname -a:

Linux galicia 5.12.0-rc5-git-5e46d1b-Pogorze-Karpackie-CUSTOM-KERNEL #3
SMP Wed Mar 31 08:36:13 CEST 2021 x86_64 GNU/Linux

I've reported this issue previously in the following bug threads:

- https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-340/+bug/1916640/comments/8

- https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-340/+bug/1916640/comments/9

Provided is the latest, relevant fragment of output from 'journalctl',
and the full 'Xorg.0.log' from a Core Dump (crash):

https://pastebin.com/raw/vz4x6eLe

A patch for NVIDIA 340.108 on Linux Kernel 5.12 MAY possibly be required.

Please test for similar results to determine whether a new patch for
5.12 is needed.

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
Importance: Undecided
Status: New

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

Title:
NVIDIA 340.108 Random Core Dump With Xorg on Linux Kernel 5.12.0-rc5

Status in nvidia-graphics-drivers-340 package in Ubuntu:
New

Bug description:
NVIDIA 340.108 with all patches (up to the 5.11 patch) is randomly
crashing (Core Dump) with Xorg 1.20.10 on Linux Kernel 5.12.0-rc5. It
works fine on the previous Kernel 5.11.

The Core Dumps (crashes) are not frequent, but randomly occur, and are
always triggered while using Google Chrome.

When the bug occurs, Chrome closes, Xorg closes and the system logs
out from Lightdm, but doesn't completely shut down the computer. I'm
able to log back in via Lightdm.

I'm using openSUSE Linux, but always use the patches provided here
which always work for me.

uname -a:

Linux galicia 5.12.0-rc5-git-5e46d1b-Pogorze-Karpackie-CUSTOM-KERNEL
#3 SMP Wed Mar 31 08:36:13 CEST 2021 x86_64 GNU/Linux

I've reported this issue previously in the following bug threads:

- https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-340/+bug/1916640/comments/8

- https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-340/+bug/1916640/comments/9

Provided is the latest, relevant fragment of output from 'journalctl',
and the full 'Xorg.0.log' from a Core Dump (crash):

https://pastebin.com/raw/vz4x6eLe

A patch for NVIDIA 340.108 on Linux Kernel 5.12 MAY possibly be required.

Please test for similar results to determine whether a new patch for
5.12 is needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1923270/+subscriptions

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

[Desktop-packages] [Bug 1923267] [NEW] indicator-multiload app broken after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1

2021-04-09 Thread fprietog

Public bug reported:

Problem tested in two different environments:
- Ubuntu 21.04 Beta amd64 
- Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8GB)

After upgrading these packages:

libglib2.0-02.67.5-2 to 2.68.0-1
libglib2.0-bin  2.67.5-2 to 2.68.0-1
libglib2.0-data 2.67.5-2 to 2.68.0-1

The app indicator-multiload (0.4-0ubuntu5) doesn't work showing only
three dots (...) instead of the graphic expected. It's throwing error
messages to the system journal every second or so (depends of the
refresh interval selected in the app settings):

abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]: multiload,
Impossible to read image from path '/run/user/1026/multiload-icons-
Wc8kck/icons/indicator-multiload-graphs-0.png': TypeError: method
Gio.File.read_async: At least 3 arguments required, but only 2 passed

Don't know if this is a documented change of that method and the bug
should be open for the indicator-multiload app. Please, if that's the
case just let me know to do it.

Thanks and best reagrds

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

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

Title:
  indicator-multiload app broken after upgrading libglib2.0-0 2.67.5-2
  to 2.68.0-1

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Problem tested in two different environments:
  - Ubuntu 21.04 Beta amd64 
  - Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8GB)

  After upgrading these packages:

  libglib2.0-02.67.5-2 to 2.68.0-1
  libglib2.0-bin  2.67.5-2 to 2.68.0-1
  libglib2.0-data 2.67.5-2 to 2.68.0-1

  The app indicator-multiload (0.4-0ubuntu5) doesn't work showing only
  three dots (...) instead of the graphic expected. It's throwing error
  messages to the system journal every second or so (depends of the
  refresh interval selected in the app settings):

  abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]:
  multiload, Impossible to read image from path '/run/user/1026
  /multiload-icons-Wc8kck/icons/indicator-multiload-graphs-0.png':
  TypeError: method Gio.File.read_async: At least 3 arguments required,
  but only 2 passed

  Don't know if this is a documented change of that method and the bug
  should be open for the indicator-multiload app. Please, if that's the
  case just let me know to do it.

  Thanks and best reagrds

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

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

[Desktop-packages] [Bug 1922540] Re: Display orientation resets on reboot with USB-C external monitor and refresh rate dropdown disappears when setting it sometimes

2021-04-09 Thread Freeman

Then this is the xrandr after switching refresh rate to 100hz
(successful) in Ubuntu on Xorg.

** Attachment added: "xorgxrandr_afterswitchingrefreshrateto100hz.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922540/+attachment/5486249/+files/xorgxrandr_afterswitchingrefreshrateto100hz.txt

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

Title:
  Display orientation resets on reboot with USB-C external monitor and
  refresh rate dropdown disappears when setting it sometimes

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When rebooting with USB-C external monitor (3440x1440) attached,
  display orientation in "gnome-control-center display" resets requiring
  one to reposition the windows on boot. Very annoying.

  In addition, refresh rate drop down for external display sometimes
  goes missing when setting refresh rate to 100hz instead of default
  60?Hz. Refresh rate listing and dropdown box disappears until setting
  monitor resolution to different resolution and back or reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-control-center 1:3.38.5-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  5 01:09:38 2021
  InstallationDate: Installed on 2021-04-05 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1922540] Re: Display orientation resets on reboot with USB-C external monitor and refresh rate dropdown disappears when setting it sometimes

2021-04-09 Thread Freeman

And then this is the xrandr after rebooting and losing my screen
orientation under Ubuntu on Xorg and having the refresh rate reset to
60hz on the external monitor.


** Attachment added: 
"xorgxrandr_afterswitchingrefreshrateto100hz_and_rebooting.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922540/+attachment/5486250/+files/xorgxrandr_afterswitchingrefreshrateto100hz_and_rebooting.txt

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

Title:
  Display orientation resets on reboot with USB-C external monitor and
  refresh rate dropdown disappears when setting it sometimes

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When rebooting with USB-C external monitor (3440x1440) attached,
  display orientation in "gnome-control-center display" resets requiring
  one to reposition the windows on boot. Very annoying.

  In addition, refresh rate drop down for external display sometimes
  goes missing when setting refresh rate to 100hz instead of default
  60?Hz. Refresh rate listing and dropdown box disappears until setting
  monitor resolution to different resolution and back or reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-control-center 1:3.38.5-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  5 01:09:38 2021
  InstallationDate: Installed on 2021-04-05 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1922540] Re: Display orientation resets on reboot with USB-C external monitor and refresh rate dropdown disappears when setting it sometimes

2021-04-09 Thread Freeman

This is the xrandr after just switching to gnome of xorg

** Attachment added: "xorgxrandr.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922540/+attachment/5486248/+files/xorgxrandr.txt

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

Title:
  Display orientation resets on reboot with USB-C external monitor and
  refresh rate dropdown disappears when setting it sometimes

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When rebooting with USB-C external monitor (3440x1440) attached,
  display orientation in "gnome-control-center display" resets requiring
  one to reposition the windows on boot. Very annoying.

  In addition, refresh rate drop down for external display sometimes
  goes missing when setting refresh rate to 100hz instead of default
  60?Hz. Refresh rate listing and dropdown box disappears until setting
  monitor resolution to different resolution and back or reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-control-center 1:3.38.5-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  5 01:09:38 2021
  InstallationDate: Installed on 2021-04-05 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1897784] Autopkgtest regression report (libreoffice/1:6.4.7-0ubuntu0.20.04.1)

2021-04-09 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted libreoffice (1:6.4.7-0ubuntu0.20.04.1) 
for focal have finished running.
The following regressions have been reported in tests triggered by the package:

libreoffice/1:6.4.7-0ubuntu0.20.04.1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#libreoffice

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  
/usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Triaged
Status in libreoffice source package in Focal:
  Fix Committed
Status in libreoffice source package in Groovy:
  Fix Committed

Bug description:
  [Verification and regression analysis is all handled via the main SRU
  bug of LP: #1913353 (for groovy) and LP: #1906684 (for focal)]

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

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

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

[Desktop-packages] [Bug 1906684] Autopkgtest regression report (libreoffice/1:6.4.7-0ubuntu0.20.04.1)

2021-04-09 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted libreoffice (1:6.4.7-0ubuntu0.20.04.1) 
for focal have finished running.
The following regressions have been reported in tests triggered by the package:

libreoffice/1:6.4.7-0ubuntu0.20.04.1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#libreoffice

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [SRU] libreoffice 6.4.7 for Focal

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

Bug description:
  [Impact]

  * LibreOffice 6.4.7 is in its seventh bug-fix release of the 6.4 line:
  https://wiki.documentfoundation.org/ReleasePlan/6.4#6.4.7_release

  * Version 6.4.6 is currently released in focal. For a list of fixed bugs 
compared to 6.4.6 see the list of bugs fixed in the two release candidates:
  https://wiki.documentfoundation.org/Releases/6.4.7/RC1
  https://wiki.documentfoundation.org/Releases/6.4.7/RC2
  (that's a total of 72 bugs)

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

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

  * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_64/1808/

  * More information about the upstream QA testing can be found here:
  * Automated tests
https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

  * Launchpad testing. The libreoffice packages include autopkgtests
  that were run and verified as passing.

  * [amd64] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ricotz-ppa/focal/amd64/libr/libreoffice/20210310_155918_ee47e@/log.gz
  * [arm64] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ricotz-ppa/focal/arm64/libr/libreoffice/20210310_200818_ee47e@/log.gz
  * [armhf] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ricotz-ppa/focal/armhf/libr/libreoffice/20210310_174648_abb49@/log.gz
  * [ppc64el] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ricotz-ppa/focal/ppc64el/libr/libreoffice/20210310_165457_abb49@/log.gz
  * [s390x] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ricotz-ppa/focal/s390x/libr/libreoffice/20210310_160307_abb49@/log.gz

  * General smoke testing of all the applications in the office suite
  were carried out by going through the manual testplan as documented
  by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

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

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

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

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

[Desktop-packages] [Bug 1916786] Autopkgtest regression report (libreoffice/1:6.4.7-0ubuntu0.20.04.1)

2021-04-09 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted libreoffice (1:6.4.7-0ubuntu0.20.04.1) 
for focal have finished running.
The following regressions have been reported in tests triggered by the package:

libreoffice/1:6.4.7-0ubuntu0.20.04.1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#libreoffice

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  weak dependency to libreoffice-sdbc-hsqldb

Status in libreoffice package in Ubuntu:
  Fix Committed
Status in libreoffice source package in Focal:
  Fix Committed
Status in libreoffice source package in Groovy:
  Fix Committed

Bug description:
  [Verification and regression analysis is all handled via the main SRU
  bug of LP: #1913353 (for groovy) and LP: #1906684 (for focal)]

  The user can't create a new Base file with the wizard if the
  libreoffice-sdbc-hsqldb package isn't installed. The package
  libreoffice-base-drivers has only a "suggests" dependency to
  libreoffice-sdbc-hsqldb. It should have a "depends" dependency.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-base-drivers 1:6.4.6-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed Feb 24 18:32:22 2021
  InstallationDate: Installed on 2020-10-12 (134 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.logrotate.d.apport: 2021-02-03T16:41:54.752959

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

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

[Desktop-packages] [Bug 1873429] Re: Problem with printing in 20.04 version

2021-04-09 Thread Norm

Same problem with an old Epson Stylus NX215.  I can scan but not print.  The 
prompt tells be it was completed but the printer doesn't do anything.  I 
imagine I have the drivers installed as it recognizes the printer, scans and 
thinks it's printing. Seems like a common problem with 20.04.
Not overly techy with terminal etc. Has this been resolved?

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

Title:
  Problem with printing in 20.04 version

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  In previous 19.10 my Epson Stylus CX3600 both prints & scans fine.

  In 20.04 it scans fine, but in print mode the process banners show the
  job is sent to the printer, then printing is complete. However there
  is no print output. I reinstalled the Epson print drivers but without
  success.

  I'm staying on 20.04, but by running Ubuntu 19.10 from a USB drive the
  printing issue is solved. The Epson is recognised and my documents
  print and scan fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 17 10:59:10 2020
  InstallationDate: Installed on 2019-12-10 (128 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-04-01 (15 days ago)

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

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

[Desktop-packages] [Bug 1906684] Re: [SRU] libreoffice 6.4.7 for Focal

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

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

Title:
  [SRU] libreoffice 6.4.7 for Focal

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

Bug description:
  [Impact]

  * LibreOffice 6.4.7 is in its seventh bug-fix release of the 6.4 line:
  https://wiki.documentfoundation.org/ReleasePlan/6.4#6.4.7_release

  * Version 6.4.6 is currently released in focal. For a list of fixed bugs 
compared to 6.4.6 see the list of bugs fixed in the two release candidates:
  https://wiki.documentfoundation.org/Releases/6.4.7/RC1
  https://wiki.documentfoundation.org/Releases/6.4.7/RC2
  (that's a total of 72 bugs)

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

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

  * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_64/1808/

  * More information about the upstream QA testing can be found here:
  * Automated tests
https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

  * Launchpad testing. The libreoffice packages include autopkgtests
  that were run and verified as passing.

  * [amd64] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ricotz-ppa/focal/amd64/libr/libreoffice/20210310_155918_ee47e@/log.gz
  * [arm64] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ricotz-ppa/focal/arm64/libr/libreoffice/20210310_200818_ee47e@/log.gz
  * [armhf] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ricotz-ppa/focal/armhf/libr/libreoffice/20210310_174648_abb49@/log.gz
  * [ppc64el] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ricotz-ppa/focal/ppc64el/libr/libreoffice/20210310_165457_abb49@/log.gz
  * [s390x] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ricotz-ppa/focal/s390x/libr/libreoffice/20210310_160307_abb49@/log.gz

  * General smoke testing of all the applications in the office suite
  were carried out by going through the manual testplan as documented
  by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

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

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

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

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

[Desktop-packages] [Bug 1913353] Re: [SRU] libreoffice 7.0.5 for groovy

Upgraded libreoffice from 1:7.0.3-0ubuntu0.20.10.1 to
1:7.0.5-0ubuntu0.20.10.1 from groovy-proposed in a clean and up-to-date
groovy amd64 VM, and successfully ran test plan at
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice.

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

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

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

Title:
  [SRU] libreoffice 7.0.5 for groovy

Status in libreoffice package in Ubuntu:
  In Progress
Status in libreoffice source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 7.0.5 is in its fifth bugfix release of the 7.0 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.0#7.0.5_release

   * Version 7.0.3 is currently released in groovy. For a list of fixed bugs 
compared to 7.0.3 see the list of bugs fixed in the release candidates of 7.0.4 
and 7.0.5 (that's a total of 114 bugs for 7.0.4 + 104 for 7.0.5):
   https://wiki.documentfoundation.org/Releases/7.0.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.0.4/RC2#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.0.5/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.0.5/RC2#List_of_fixed_bugs

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

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_linux_gcc_release/82662/console

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  * [amd64] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-ricotz-ppa/groovy/amd64/libr/libreoffice/20210315_130836_8dcc6@/log.gz
  * [arm64] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-ricotz-ppa/groovy/arm64/libr/libreoffice/20210315_164144_5c625@/log.gz
  * [armhf] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-ricotz-ppa/groovy/armhf/libr/libreoffice/20210315_140616_5c625@/log.gz
  * [ppc64el] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-ricotz-ppa/groovy/ppc64el/libr/libreoffice/20210315_141909_5c625@/log.gz
  * [s390x] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-ricotz-ppa/groovy/s390x/libr/libreoffice/20210315_131937_5c625@/log.gz

   * General smoke testing of all the applications in the office suite
  were carried out by going through the manual testplan as documented
  by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

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

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

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

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

[Desktop-packages] [Bug 1906684] Re: [SRU] libreoffice 6.4.7 for Focal

Upgraded libreoffice from 1:6.4.6-0ubuntu0.20.04.1 to
1:6.4.7-0ubuntu0.20.04.1 from focal-proposed in a clean and up-to-date
focal amd64 VM, and successfully ran test plan at
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice.

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

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

Title:
  [SRU] libreoffice 6.4.7 for Focal

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

Bug description:
  [Impact]

  * LibreOffice 6.4.7 is in its seventh bug-fix release of the 6.4 line:
  https://wiki.documentfoundation.org/ReleasePlan/6.4#6.4.7_release

  * Version 6.4.6 is currently released in focal. For a list of fixed bugs 
compared to 6.4.6 see the list of bugs fixed in the two release candidates:
  https://wiki.documentfoundation.org/Releases/6.4.7/RC1
  https://wiki.documentfoundation.org/Releases/6.4.7/RC2
  (that's a total of 72 bugs)

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

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

  * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_64/1808/

  * More information about the upstream QA testing can be found here:
  * Automated tests
https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

  * Launchpad testing. The libreoffice packages include autopkgtests
  that were run and verified as passing.

  * [amd64] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ricotz-ppa/focal/amd64/libr/libreoffice/20210310_155918_ee47e@/log.gz
  * [arm64] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ricotz-ppa/focal/arm64/libr/libreoffice/20210310_200818_ee47e@/log.gz
  * [armhf] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ricotz-ppa/focal/armhf/libr/libreoffice/20210310_174648_abb49@/log.gz
  * [ppc64el] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ricotz-ppa/focal/ppc64el/libr/libreoffice/20210310_165457_abb49@/log.gz
  * [s390x] 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ricotz-ppa/focal/s390x/libr/libreoffice/20210310_160307_abb49@/log.gz

  * General smoke testing of all the applications in the office suite
  were carried out by going through the manual testplan as documented
  by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

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

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

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

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

[Desktop-packages] [Bug 1923233] Re: Computer is very slow

2021-04-09 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  Computer is very slow

Status in xorg package in Ubuntu:
  New

Bug description:
  Lap Top Computer is very slow

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog:
   [[0;32m  OK  [0m] Started [0;1;39mManage, Install and Generate Color 
Profiles[0m.
   [[0;32m  OK  [0m] Started [0;1;39mGNOME Display Manager[0m.
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Apr  9 12:49:55 2021
  DistUpgraded: 2020-10-01 06:06:52,217 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso 
hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev da) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Stoney [Radeon R2/R3/R4/R5 Graphics] 
[103c:8330]
  InstallationDate: Installed on 2018-02-18 (1145 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: HP HP Laptop 15-bw0xx
  ProcEnviron:
   LANGUAGE=es_MX:es
   PATH=(custom, no user)
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic 
root=UUID=eb8ec2b9-9416-44bb-bd9a-da00109b6198 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-10-01 (190 days ago)
  dmi.bios.date: 11/01/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.20
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8330
  dmi.board.vendor: HP
  dmi.board.version: 27.31
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.20:bd11/01/2017:svnHP:pnHPLaptop15-bw0xx:pvrType1ProductConfigId:rvnHP:rn8330:rvr27.31:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-bw0xx
  dmi.product.sku: 1GR30LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  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.1
  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
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Tue Nov 20 10:27:42 2018
  xserver.configfile: default
  xserver.errors: AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: amdgpu

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

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

[Desktop-packages] [Bug 1923233] [NEW] Computer is very slow

You have been subscribed to a public bug:

Lap Top Computer is very slow

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
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog:
 [[0;32m  OK  [0m] Started [0;1;39mManage, Install and Generate Color 
Profiles[0m.
 [[0;32m  OK  [0m] Started [0;1;39mGNOME Display Manager[0m.
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Apr  9 12:49:55 2021
DistUpgraded: 2020-10-01 06:06:52,217 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso 
hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8))
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev da) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Stoney [Radeon R2/R3/R4/R5 Graphics] 
[103c:8330]
InstallationDate: Installed on 2018-02-18 (1145 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: HP HP Laptop 15-bw0xx
ProcEnviron:
 LANGUAGE=es_MX:es
 PATH=(custom, no user)
 LANG=es_MX.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic 
root=UUID=eb8ec2b9-9416-44bb-bd9a-da00109b6198 ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-10-01 (190 days ago)
dmi.bios.date: 11/01/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.20
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8330
dmi.board.vendor: HP
dmi.board.version: 27.31
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.20:bd11/01/2017:svnHP:pnHPLaptop15-bw0xx:pvrType1ProductConfigId:rvnHP:rn8330:rvr27.31:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 15-bw0xx
dmi.product.sku: 1GR30LA#ABM
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
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.1
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
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Tue Nov 20 10:27:42 2018
xserver.configfile: default
xserver.errors: AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
xserver.video_driver: amdgpu

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


** Tags: amd64 apport-bug focal ubuntu
-- 
Computer is very slow
https://bugs.launchpad.net/bugs/1923233
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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

[Desktop-packages] [Bug 1916301] Re: I can't play live videos on YouTube (problem with live transmission) - Ubuntu 18.04.5

2021-04-09 Thread madbiologist

Hmm, that might need to be updated.  Where does it say that?

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

Title:
  I can't play live videos on YouTube (problem with live transmission) -
  Ubuntu 18.04.5

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Dear Launchpad Team,

  I can't play live videos from Youtube. I have problem only with live
  transmission. Normal videos works fine. I noticed that I also have
  this same problem on Focal (now I checked this on Bionic - Ubuntu
  18.04.5). On Lubuntu 18.04.5 on other machine I don't have this
  problem. I can play on Lubuntu all Youtube videos. What is a problem?
  Do you know? I think that by default Ubuntu have not necessary package
  to play live videos on Youtube. Have I right or this is a bug? On
  Answers section on launchpad anyone can't tell me if it is a bug so
  this is why I report this bug now. If it is not a bug I am very sorry
  and you can delete this report now.

  Example I have problem with this video:
  https://www.youtube.com/watch?v=21X5lGlDOfg

  I used debugger by youtube and this is output of this:

  "debug_error": {
  "errorCode": "html5.unsupportedlive",
  "errorMessage": "Ten format wideo nie jest obsługiwany.",
  "Nx": "HTML5_NO_AVAILABLE_FORMATS_FALLBACK",
  "cj": "","

  If it is a bug can you fix it?

  UPDATE: Today I updated my firefox to the newest version 86.0. This
  bug still exists.

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

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

[Desktop-packages] [Bug 1922712] Re: add metric for new glibc hwcaps

2021-04-09 Thread Sebastien Bacher

Thanks! I've added a trello card to review the PR in our trello backlog

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

Title:
  add metric for new glibc hwcaps

Status in ubuntu-report package in Ubuntu:
  Confirmed

Bug description:
  we want to collect information which most recent hwcap is supported by
  a machine.  The result should be a string like "x86-64-v2",
  "x86-64-v3", "x86-64-v4", "z13", "z14", "p9", "p10" depending on "ld-
  linux --help" output.  The string should be empty for architectures
  without glibc hwcaps (currently armhf, arm64, i386, riscv64). The
  string should be empty if no specific hwcaps is supported (e.g. on a
  power8 machine). The string should be "N/A" (not available), when
  trying to run ld-linux on a release with glibc (<< 2.33).

  Note that lexical sorting won't work for "p9", "p10".

  if test -x /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2; then
lddynload=/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
  elif test -x /lib/powerpc64le-linux-gnu/ld64.so.2; then
lddynload=/lib/powerpc64le-linux-gnu/ld64.so.2
  elif test -x /lib/s390x-linux-gnu/ld64.so.1; then
lddynload=/lib/s390x-linux-gnu/ld64.so.1
  fi

  supported=
  if [ -n "$lddynload" ]; then
$lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/'
supported=$($lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/' | awk 
'/supported/ {print $1}')
  fi

  Here, $supported has listed all supported hwcaps, not just the best
  supported one.

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

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

[Desktop-packages] [Bug 1915677] Re: [ snap ] libreoffice-style-* packages are missing ?

2021-04-09 Thread Coeur Noir

Don't worry - no emergency on my side ;-)

Take your time.

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

Title:
  [ snap ] libreoffice-style-* packages are missing ?

Status in libreoffice package in Ubuntu:
  In Progress

Bug description:
  Hi,

  trying LibreOffice 7 as a snap on UbuntuBudgie 20.04.

  I generally use dark gtk theme style system wide - and some are available as 
snap ( Adapta ).
  I often use Papirus icons set - and those are also ( partly ) available as 
snap ( through Adpata gtk theme ).

  I can't see if the same choice exists while using LO as a snap : I can
  find some icons theme ( elementary, colibre, breeze, and so on ) but
  they all look designed for global light gtk themes.

  In other words icons in my LO are black on black.

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

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

[Desktop-packages] [Bug 1922712] Re: add metric for new glibc hwcaps

2021-04-09 Thread William Wilson

Seb, I have made a PR in the github repo. This PR also pulls in the
changes in version 1.6.3, which were previously not present.

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

Title:
  add metric for new glibc hwcaps

Status in ubuntu-report package in Ubuntu:
  Confirmed

Bug description:
  we want to collect information which most recent hwcap is supported by
  a machine.  The result should be a string like "x86-64-v2",
  "x86-64-v3", "x86-64-v4", "z13", "z14", "p9", "p10" depending on "ld-
  linux --help" output.  The string should be empty for architectures
  without glibc hwcaps (currently armhf, arm64, i386, riscv64). The
  string should be empty if no specific hwcaps is supported (e.g. on a
  power8 machine). The string should be "N/A" (not available), when
  trying to run ld-linux on a release with glibc (<< 2.33).

  Note that lexical sorting won't work for "p9", "p10".

  if test -x /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2; then
lddynload=/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
  elif test -x /lib/powerpc64le-linux-gnu/ld64.so.2; then
lddynload=/lib/powerpc64le-linux-gnu/ld64.so.2
  elif test -x /lib/s390x-linux-gnu/ld64.so.1; then
lddynload=/lib/s390x-linux-gnu/ld64.so.1
  fi

  supported=
  if [ -n "$lddynload" ]; then
$lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/'
supported=$($lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/' | awk 
'/supported/ {print $1}')
  fi

  Here, $supported has listed all supported hwcaps, not just the best
  supported one.

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

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

[Desktop-packages] [Bug 1916301] Re: I can't play live videos on YouTube (problem with live transmission) - Ubuntu 18.04.5

Packages in universe don't migrate to main in a released version of
Ubuntu. Please read again comment #11, one can be fairly confident that
critical security issues will be fixed in such an important package,
even after the official support period has ended. If you don't trust the
Ubuntu community on this matter, you should upgrade to the next LTS
(focal).

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

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

Title:
  I can't play live videos on YouTube (problem with live transmission) -
  Ubuntu 18.04.5

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Dear Launchpad Team,

  I can't play live videos from Youtube. I have problem only with live
  transmission. Normal videos works fine. I noticed that I also have
  this same problem on Focal (now I checked this on Bionic - Ubuntu
  18.04.5). On Lubuntu 18.04.5 on other machine I don't have this
  problem. I can play on Lubuntu all Youtube videos. What is a problem?
  Do you know? I think that by default Ubuntu have not necessary package
  to play live videos on Youtube. Have I right or this is a bug? On
  Answers section on launchpad anyone can't tell me if it is a bug so
  this is why I report this bug now. If it is not a bug I am very sorry
  and you can delete this report now.

  Example I have problem with this video:
  https://www.youtube.com/watch?v=21X5lGlDOfg

  I used debugger by youtube and this is output of this:

  "debug_error": {
  "errorCode": "html5.unsupportedlive",
  "errorMessage": "Ten format wideo nie jest obsługiwany.",
  "Nx": "HTML5_NO_AVAILABLE_FORMATS_FALLBACK",
  "cj": "","

  If it is a bug can you fix it?

  UPDATE: Today I updated my firefox to the newest version 86.0. This
  bug still exists.

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

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

[Desktop-packages] [Bug 1923116] Re: Broken WebGL in Firefox 87.0 on Kubuntu 21.04 Beta (Xorg)

Until this is fixed upstream (apparently in firefox 88, thanks Paweł for
the link), this should work around the problem:
https://bazaar.launchpad.net/~mozillateam/firefox/firefox.hirsute/revision/1478.

** Changed in: firefox (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

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

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

** Summary changed:

- Broken WebGL in Firefox 87.0 on Kubuntu 21.04 Beta (Xorg)
+ Broken WebGL in Firefox 87.0 in xorg session

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

Title:
  Broken WebGL in Firefox 87.0 in xorg session

Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  Firefox 87.0 on Kubuntu 21.04 Beta running on Xorg seems to have broken WebGL.
  Tested using https://get.webgl.org on fresh a Firefox profile.
  I found the following in the console output:

  `[GFX1-]: glxtest: Could not connect to wayland socket`

  and this seems to be the cause of the problem - due to failing
  glxtest, all additional HW acceleration is disabled as seen by
  `FEATURE_FAILURE_GLXTEST_FAILED` in all `gfx.blacklist` entries in
  about:config.

  The binary release downloaded from Mozilla (https://download-
  installer.cdn.mozilla.net/pub/firefox/releases/87.0/linux-x86_64/en-
  US/firefox-87.0.tar.bz2) does *not* show the same behaviour - WebGL is
  working just fine.

  ```
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  firefox:
Installed: 87.0+build3-0ubuntu2
Candidate: 87.0+build3-0ubuntu2
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: firefox 87.0+build3-0ubuntu2
  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
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  woody  1838 F pulseaudio
  BuildID: 20210318103112
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Fri Apr  9 01:40:17 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ExecutablePath: /usr/lib/firefox/firefox
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-04-05 (3 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  IpRoute:
   default via 192.168.184.1 dev wlp0s20f3 proto dhcp metric 600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 
   192.168.184.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.184.198 
metric 600
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profile2Extensions: extensions.sqlite corrupt or missing
  Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile2Locales: extensions.sqlite corrupt or missing
  Profile2PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  Profile2PrefSources: prefs.js
  Profile2Themes: extensions.sqlite corrupt or missing
  Profile3Extensions: extensions.sqlite corrupt or missing
  Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile3Locales: extensions.sqlite corrupt or missing
  Profile3PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  Profile3PrefSources: prefs.js
  Profile3Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile3 - LastVersion=87.0/20210318103112
   Profile1 (Default) - LastVersion=87.0/20210318103112
   Profile0 - LastVersion=87.0/20210318103112 (In use)
   Profile2 - LastVersion=87.0/20210318103112
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2020
  dmi.bios.release: 1.15
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET25W (1.15 )
  d

[Desktop-packages] [Bug 1915677] Re: [ snap ] libreoffice-style-* packages are missing ?

Actually, I'm hitting a slight build problem so please stand by coeur-
noir and I'll direct you to download the snap from a build shortly
(rather than the store).

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

Title:
  [ snap ] libreoffice-style-* packages are missing ?

Status in libreoffice package in Ubuntu:
  In Progress

Bug description:
  Hi,

  trying LibreOffice 7 as a snap on UbuntuBudgie 20.04.

  I generally use dark gtk theme style system wide - and some are available as 
snap ( Adapta ).
  I often use Papirus icons set - and those are also ( partly ) available as 
snap ( through Adpata gtk theme ).

  I can't see if the same choice exists while using LO as a snap : I can
  find some icons theme ( elementary, colibre, breeze, and so on ) but
  they all look designed for global light gtk themes.

  In other words icons in my LO are black on black.

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

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

[Desktop-packages] [Bug 1923116] Re: Broken WebGL in Firefox 87.0 on Kubuntu 21.04 Beta (Xorg)

** Branch linked: lp:firefox

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

Title:
  Broken WebGL in Firefox 87.0 in xorg session

Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  Firefox 87.0 on Kubuntu 21.04 Beta running on Xorg seems to have broken WebGL.
  Tested using https://get.webgl.org on fresh a Firefox profile.
  I found the following in the console output:

  `[GFX1-]: glxtest: Could not connect to wayland socket`

  and this seems to be the cause of the problem - due to failing
  glxtest, all additional HW acceleration is disabled as seen by
  `FEATURE_FAILURE_GLXTEST_FAILED` in all `gfx.blacklist` entries in
  about:config.

  The binary release downloaded from Mozilla (https://download-
  installer.cdn.mozilla.net/pub/firefox/releases/87.0/linux-x86_64/en-
  US/firefox-87.0.tar.bz2) does *not* show the same behaviour - WebGL is
  working just fine.

  ```
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  firefox:
Installed: 87.0+build3-0ubuntu2
Candidate: 87.0+build3-0ubuntu2
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: firefox 87.0+build3-0ubuntu2
  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
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  woody  1838 F pulseaudio
  BuildID: 20210318103112
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Fri Apr  9 01:40:17 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ExecutablePath: /usr/lib/firefox/firefox
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-04-05 (3 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  IpRoute:
   default via 192.168.184.1 dev wlp0s20f3 proto dhcp metric 600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 
   192.168.184.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.184.198 
metric 600
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profile2Extensions: extensions.sqlite corrupt or missing
  Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile2Locales: extensions.sqlite corrupt or missing
  Profile2PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  Profile2PrefSources: prefs.js
  Profile2Themes: extensions.sqlite corrupt or missing
  Profile3Extensions: extensions.sqlite corrupt or missing
  Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile3Locales: extensions.sqlite corrupt or missing
  Profile3PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  Profile3PrefSources: prefs.js
  Profile3Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile3 - LastVersion=87.0/20210318103112
   Profile1 (Default) - LastVersion=87.0/20210318103112
   Profile0 - LastVersion=87.0/20210318103112 (In use)
   Profile2 - LastVersion=87.0/20210318103112
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2020
  dmi.bios.release: 1.15
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET25W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET25W(1.15):bd12/07/2020:br1.15:efr1.8:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_Th

[Desktop-packages] [Bug 1923219] Re: I couldn't launch apps

It doesn't look like it's a chromium bug. Please be more specific in
what the problem is, otherwise we're not going to be able to help you
resolve it.

** Package changed: chromium-browser (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 chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1923219

Title:
  I couldn't launch apps

Status in Ubuntu:
  Incomplete

Bug description:
  I couldn't launch  many apps, i have tried launching them from the
  terminal but it's same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  9 18:42:13 2021
  InstallationDate: Installed on 2020-07-05 (278 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1923222] [NEW] Can't leave "Activities Overview "

2021-04-09 Thread michel

Public bug reported:

Ubuntu 21.04 Beta with all updates installed.
When pressing "Super Key", activities overview is displayed. But I'm stuck 
there: I can close windows and apps and even start new apps, and they are 
highlighted when mouse is placed over one of them, but they won't maximize wenn 
I click on one of them. Selecting an App through "tab key" doesn't work either. 
So I'm stuck.

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

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

Title:
  Can't leave "Activities Overview "

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 21.04 Beta with all updates installed.
  When pressing "Super Key", activities overview is displayed. But I'm stuck 
there: I can close windows and apps and even start new apps, and they are 
highlighted when mouse is placed over one of them, but they won't maximize wenn 
I click on one of them. Selecting an App through "tab key" doesn't work either. 
So I'm stuck.

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

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

[Desktop-packages] [Bug 1923219] [NEW] I couldn't launch apps

2021-04-09 Thread Yaya Usman

Public bug reported:

I couldn't launch  many apps, i have tried launching them from the
terminal but it's same issue.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser (not installed)
ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  9 18:42:13 2021
InstallationDate: Installed on 2020-07-05 (278 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  I couldn't launch apps

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I couldn't launch  many apps, i have tried launching them from the
  terminal but it's same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  9 18:42:13 2021
  InstallationDate: Installed on 2020-07-05 (278 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1922379] Re: scanner not configured

2021-04-09 Thread Paul White

Ok, thanks for your reply.
Invalidating the Ubuntu task that you created.

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

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

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

Title:
  scanner not configured

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Invalid

Bug description:
  hp-check[24965]: info: :
  hp-check[24965]: info: :HP Linux Imaging and Printing System (ver. 3.19.12)
  hp-check[24965]: info: :Dependency/Version Check Utility ver. 15.1
  openSUSE Leap 15.2
  HP Officejet Pro 8025

  Following is the output of hp-check -t
  The scan part is not addressed when initializing the printer by hplip
  Please tell me what i did wrong and how to remediate the malfunction
  Many thanks

  
  hp-check[24965]: info: :
  hp-check[24965]: info: :Copyright (c) 2001-18 HP Development Company, LP
  hp-check[24965]: info: :This software comes with ABSOLUTELY NO WARRANTY.
  hp-check[24965]: info: :This is free software, and you are welcome to 
distribute it
  hp-check[24965]: info: :under certain conditions. See COPYING file for more 
details.
  hp-check[24965]: info: :
  hp-check[24965]: info: :Note: hp-check can be run in three modes:
  hp-check[24965]: info: :1. Compile-time check mode (-c or --compile): Use 
this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to 
determine if the proper dependencies are installed to successfully compile 
HPLIP. 
  hp-check[24965]: info: :2. Run-time check mode (-r or --run): Use this mode 
to determine if a distro supplied package (.deb, .rpm, etc) or an already built 
HPLIP supplied tarball has the proper dependencies installed to successfully 
run.  
  hp-check[24965]: info: :3. Both compile- and run-time check mode (-b or 
--both) (Default): This mode will check both of the above cases (both compile- 
and run-time dependencies). 

  hp-check[24965]: info: :
  hp-check[24965]: info: :Check types:  


 
  hp-check[24965]: info: :a. EXTERNALDEP - External Dependencies


 
  hp-check[24965]: info: :b. GENERALDEP - General Dependencies (required both 
at compile and run time)

   
  hp-check[24965]: info: :c. COMPILEDEP - Compile time Dependencies 


 
  hp-check[24965]: info: :d. [All are run-time checks]  


 
  hp-check[24965]: info: :PYEXT SCANCONF QUEUES PERMISSION  


 
  hp-check[24965]: info: :
  hp-check[24965]: info: :Status Types:
  hp-check[24965]: info: :OK
  hp-check[24965]: info: :MISSING   - Missing Dependency or Permission 
or Plug-in
  hp-check[24965]: info: :INCOMPAT  - Incompatible dependency-version 
or Plugin-version
  hp-check[24965]: info: :
  warning: 3-15.2 version is not supported. Using 3-15.1 versions dependencies 
to verify and install...
  hp-check[24965]: info: :
  hp-check[24965]: info: :---
  hp-check[24965]: info: :| SYSTEM INFO |
  hp-check[24965]: info: :---
  hp-check[24965]: info: :
  hp-check[24965]: info: : Kernel: 5.3.18-lp152.66-default #1 SMP Tue Mar 2 
13:18:19 UTC 2021 (73933a3) GNU/Linux
   Host: ClaRoN152
   Proc: 5.3.18-lp152.66-default #1 SMP Tue Mar 2 13:18:19 UTC 2021 (73933a3) 
GNU/Linux
   Distribution: 3 15.2
  hp-check[24965]: info: : Bitness: 64 bit

  hp-check[24965]: i

Re: [Desktop-packages] [Bug 1922379] Re: scanner not configured

2021-04-09 Thread Roger Cooreman

I am deeply sorry, but I am not running  hplip under Ubuntu but I'm 
using openSUSE Leap 15.2; apparently this OS doesn't know the command 
apport-collect 1922379.
An amazing fact is that with the command  hp-scan -f ~/temp/output.pdf 
from the command line, the printer scans a document correctly!
The big inconvenance is that I have to set a lot of parameters each time.

Op 06-04-2021 om 17:42 schreef Paul White:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please execute the following command only once, as it
> will automatically gather debugging information, in a terminal:
> 
> apport-collect 1922379
> 
> When reporting bugs in the future please use apport by using 'ubuntu-
> bug' and the name of the package affected.
> 
> You can learn more about this functionality at
> https://wiki.ubuntu.com/ReportingBugs.
> 
> ** Package changed: ubuntu => hplip (Ubuntu)
> 
> ** Changed in: hplip (Ubuntu)
> Status: New => Incomplete
> 
> ** Changed in: hplip
> Status: New => Incomplete
>

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

Title:
  scanner not configured

Status in HPLIP:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  hp-check[24965]: info: :
  hp-check[24965]: info: :HP Linux Imaging and Printing System (ver. 3.19.12)
  hp-check[24965]: info: :Dependency/Version Check Utility ver. 15.1
  openSUSE Leap 15.2
  HP Officejet Pro 8025

  Following is the output of hp-check -t
  The scan part is not addressed when initializing the printer by hplip
  Please tell me what i did wrong and how to remediate the malfunction
  Many thanks

  
  hp-check[24965]: info: :
  hp-check[24965]: info: :Copyright (c) 2001-18 HP Development Company, LP
  hp-check[24965]: info: :This software comes with ABSOLUTELY NO WARRANTY.
  hp-check[24965]: info: :This is free software, and you are welcome to 
distribute it
  hp-check[24965]: info: :under certain conditions. See COPYING file for more 
details.
  hp-check[24965]: info: :
  hp-check[24965]: info: :Note: hp-check can be run in three modes:
  hp-check[24965]: info: :1. Compile-time check mode (-c or --compile): Use 
this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to 
determine if the proper dependencies are installed to successfully compile 
HPLIP. 
  hp-check[24965]: info: :2. Run-time check mode (-r or --run): Use this mode 
to determine if a distro supplied package (.deb, .rpm, etc) or an already built 
HPLIP supplied tarball has the proper dependencies installed to successfully 
run.  
  hp-check[24965]: info: :3. Both compile- and run-time check mode (-b or 
--both) (Default): This mode will check both of the above cases (both compile- 
and run-time dependencies). 

  hp-check[24965]: info: :
  hp-check[24965]: info: :Check types:  


 
  hp-check[24965]: info: :a. EXTERNALDEP - External Dependencies


 
  hp-check[24965]: info: :b. GENERALDEP - General Dependencies (required both 
at compile and run time)

   
  hp-check[24965]: info: :c. COMPILEDEP - Compile time Dependencies 


 
  hp-check[24965]: info: :d. [All are run-time checks]  


 
  hp-check[24965]: info: :PYEXT SCANCONF QUEUES PERMISSION  


 
  hp-check[24965]: info: :
  hp-check[24965

[Desktop-packages] [Bug 1923167] Re: Screen flickering- QHD Benq

2021-04-09 Thread Brian Murray

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

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

Title:
  Screen flickering- QHD Benq

Status in xorg package in Ubuntu:
  New

Bug description:
  The Display continuously flickers when we are using the Displayport 
connection with QHD (2560x1440) Benq-Monitors.
  The affected Hardware is:
  Igel UD3-LX 60 (AMD Ryzen Embedded R1505G with Radeon Vega Gfx)

  Using a DP to HDMI-Adapter solves the problem with the given resolution. 
  This error occurs in both Ubuntu Releases 18.04 and 20.10.

  This is what we see in the Logs:

  [27.144] (II) AMDGPU(0): EDID vendor "BNQ", prod id 32795
  [27.144] (II) AMDGPU(0): Using hsync ranges from config file
  [27.144] (II) AMDGPU(0): Using vrefresh ranges from config file
  [27.144] (II) AMDGPU(0): Printing DDC gathered Modelines:
  [27.144] (II) AMDGPU(0): Modeline "2560x1440"x0.0  241.50  2560 2608 2640 
2720  1440 1443 1448 1481 +hsync -vsync (88.8 kHz eP)
  [27.144] (II) AMDGPU(0): Modeline "720x480"x0.0   27.00  720 736 798 858  
480 489 495 525 -hsync -vsync (31.5 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1280x720"x0.0   74.25  1280 1390 1430 
1650  720 725 730 750 +hsync +vsync (45.0 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1280x720"x0.0   74.25  1280 1720 1760 
1980  720 725 730 750 +hsync +vsync (37.5 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "720x576"x0.0   27.00  720 732 796 864  
576 581 586 625 -hsync -vsync (31.2 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052 
2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1920x1080"x0.0  148.50  1920 2448 2492 
2640  1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1920x1080i"x0.0   74.25  1920 2008 
2052 2200  1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1920x1080i"x0.0   74.25  1920 2448 
2492 2640  1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "640x480"x0.0   25.18  640 656 752 800  
480 490 492 525 -hsync -vsync (31.5 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1440x480i"x0.0   27.00  1440 1478 1602 
1716  480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1440x576i"x0.0   27.00  1440 1464 1590 
1728  576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "800x600"x0.0   40.00  800 840 968 1056 
 600 601 605 628 +hsync +vsync (37.9 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "640x480"x0.0   31.50  640 656 720 840  
480 481 484 500 -hsync -vsync (37.5 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "720x400"x0.0   28.32  720 738 846 900  
400 412 414 449 -hsync +vsync (31.5 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 
1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 
1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 
1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "832x624"x0.0   57.28  832 864 928 1152 
 624 625 628 667 -hsync -vsync (49.7 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "800x600"x0.0   49.50  800 816 896 1056 
 600 601 604 625 +hsync +vsync (46.9 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 
1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1680x1050"x0.0  119.00  1680 1728 1760 
1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1600x900"x60.0  119.00  1600 1696 1864 
2128  900 901 904 932 -hsync +vsync (55.9 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
  [27.144] (II) AMDGPU(0): Modeline "1280x800"x0.0   71.00  1280 1328 1360 
1440  800 803 809 823 +hsync -vsync (49.3 kHz e)
  [30.040] (DB) IGEL-SCREEN-LOCK: Window [layer=1] locked
  [33.163] (DB) IGEL-SCREEN-LOCK: Window [layer=1] destroyed

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

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

[Desktop-packages] [Bug 1923167] [NEW] Screen flickering- QHD Benq

You have been subscribed to a public bug:

The Display continuously flickers when we are using the Displayport connection 
with QHD (2560x1440) Benq-Monitors.
The affected Hardware is:
Igel UD3-LX 60 (AMD Ryzen Embedded R1505G with Radeon Vega Gfx)

Using a DP to HDMI-Adapter solves the problem with the given resolution. 
This error occurs in both Ubuntu Releases 18.04 and 20.10.

This is what we see in the Logs:

[27.144] (II) AMDGPU(0): EDID vendor "BNQ", prod id 32795
[27.144] (II) AMDGPU(0): Using hsync ranges from config file
[27.144] (II) AMDGPU(0): Using vrefresh ranges from config file
[27.144] (II) AMDGPU(0): Printing DDC gathered Modelines:
[27.144] (II) AMDGPU(0): Modeline "2560x1440"x0.0  241.50  2560 2608 2640 
2720  1440 1443 1448 1481 +hsync -vsync (88.8 kHz eP)
[27.144] (II) AMDGPU(0): Modeline "720x480"x0.0   27.00  720 736 798 858  
480 489 495 525 -hsync -vsync (31.5 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1280x720"x0.0   74.25  1280 1390 1430 
1650  720 725 730 750 +hsync +vsync (45.0 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1280x720"x0.0   74.25  1280 1720 1760 
1980  720 725 730 750 +hsync +vsync (37.5 kHz e)
[27.144] (II) AMDGPU(0): Modeline "720x576"x0.0   27.00  720 732 796 864  
576 581 586 625 -hsync -vsync (31.2 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052 
2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1920x1080"x0.0  148.50  1920 2448 2492 
2640  1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1920x1080i"x0.0   74.25  1920 2008 2052 
2200  1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1920x1080i"x0.0   74.25  1920 2448 2492 
2640  1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
[27.144] (II) AMDGPU(0): Modeline "640x480"x0.0   25.18  640 656 752 800  
480 490 492 525 -hsync -vsync (31.5 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1440x480i"x0.0   27.00  1440 1478 1602 
1716  480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1440x576i"x0.0   27.00  1440 1464 1590 
1728  576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
[27.144] (II) AMDGPU(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  
600 601 605 628 +hsync +vsync (37.9 kHz e)
[27.144] (II) AMDGPU(0): Modeline "640x480"x0.0   31.50  640 656 720 840  
480 481 484 500 -hsync -vsync (37.5 kHz e)
[27.144] (II) AMDGPU(0): Modeline "720x400"x0.0   28.32  720 738 846 900  
400 412 414 449 -hsync +vsync (31.5 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 
1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 
1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 
1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[27.144] (II) AMDGPU(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  
624 625 628 667 -hsync -vsync (49.7 kHz e)
[27.144] (II) AMDGPU(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  
600 601 604 625 +hsync +vsync (46.9 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 
1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1680x1050"x0.0  119.00  1680 1728 1760 
1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1600x900"x60.0  119.00  1600 1696 1864 
2128  900 901 904 932 -hsync +vsync (55.9 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 
1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[27.144] (II) AMDGPU(0): Modeline "1280x800"x0.0   71.00  1280 1328 1360 
1440  800 803 809 823 +hsync -vsync (49.3 kHz e)
[30.040] (DB) IGEL-SCREEN-LOCK: Window [layer=1] locked
[33.163] (DB) IGEL-SCREEN-LOCK: Window [layer=1] destroyed

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


** Tags: bot-comment flickering igel monitor qhd
-- 
Screen flickering- QHD Benq
https://bugs.launchpad.net/bugs/1923167
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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

[Desktop-packages] [Bug 1923196] [NEW] Background noise when intel hd audio enters power save

2021-04-09 Thread Thomas Frans

Public bug reported:

There is a very high noise level whenever the audio driver doesn't get
used for a while (after 5-10 seconds). The problem goes away whenever
any sound plays, even a completely silent video. There is a solution
online that sets two values to prevent the audio driver going into power
save state, but the solution isn't permanent and isn't a real solution.
That 'hacky' solution uses the following two commands:

echo 0 | sudo tee /sys/module/snd_hda_intel/parameters/power_save_controller
echo 0 | sudo tee /sys/module/snd_hda_intel/parameters/power_save

Power save sounds like a good feature to have, but there should be an
option to disable it or something when the motherboard/audio card has
high noise levels when it enters power save...

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  thomas 2761 F pulseaudio
 /dev/snd/pcmC1D0p:   thomas 2761 F...m pulseaudio
 /dev/snd/controlC0:  thomas 2761 F pulseaudio
 /dev/snd/timer:  thomas 2761 f pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  9 14:34:09 2021
InstallationDate: Installed on 2021-02-09 (58 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful
Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic
Symptom_Jack: Green Headphone Out, Front
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: High background noise, or volume is too low
Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] 
Background noise or low volume
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/18/2020
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P4.20
dmi.board.name: B450 Pro4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.20:bd06/18/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4: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.

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


** Tags: amd64 apport-bug groovy

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

Title:
  Background noise when intel hd audio enters power save

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  There is a very high noise level whenever the audio driver doesn't get
  used for a while (after 5-10 seconds). The problem goes away whenever
  any sound plays, even a completely silent video. There is a solution
  online that sets two values to prevent the audio driver going into
  power save state, but the solution isn't permanent and isn't a real
  solution. That 'hacky' solution uses the following two commands:

  echo 0 | sudo tee /sys/module/snd_hda_intel/parameters/power_save_controller
  echo 0 | sudo tee /sys/module/snd_hda_intel/parameters/power_save

  Power save sounds like a good feature to have, but there should be an
  option to disable it or something when the motherboard/audio card has
  high noise levels when it enters power save...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  thomas 2761 F pulseaudio
   /dev/snd/pcmC1D0p:   thomas 2761 F...m pulseaudio
   /dev/snd/controlC0:  thomas 2761 F pulseaudio
   /dev/snd/timer:  thomas 2761 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  9 14:34:09 2021
  InstallationDate: Installed on 2021-02-09 (58 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful
  Symptom_Card: Starship/Matisse HD

[Desktop-packages] [Bug 1916640] Re: Nvidia 340.108 fails to install with kernels 5.11.x - new patches needeed

2021-04-09 Thread Ejmarkow

Bug Report Continued from #8:

Also included in the Core Dump is "libglx.so", related to Nvidia.

So, that's 2 Nvidia files: libglx.so & nvidia_drv.so


galicia:/home/ejm # cd /usr/lib64/xorg/modules/extensions
galicia:/usr/lib64/xorg/modules/extensions # ls
libglx.so  libglx.so.340.108  libvnc.so  xorg
galicia:/usr/lib64/xorg/modules/extensions # ls -al
total 16840
drwxr-xr-x 3 root root 4096 Apr  5 09:18 .
drwxr-xr-x 5 root root 4096 Apr  5 09:18 ..
lrwxrwxrwx 1 root root   17 Apr  5 09:18 libglx.so -> libglx.so.340.108
-rwxr-xr-x 1 root root 16603688 Apr  5 09:18 libglx.so.340.108
-rwxr-xr-x 1 root root   625424 Mar 26 07:39 libvnc.so
drwxr-xr-x 2 root root 4096 Mar 13 17:35 xorg
galicia:/usr/lib64/xorg/modules/extensions # cd /usr/lib64/xorg/modules/drivers
galicia:/usr/lib64/xorg/modules/drivers # ls
fbdev_drv.so  modesetting_drv.so  nouveau_drv.so  nv_drv.so  nvidia_drv.so  
vesa_drv.so
galicia:/usr/lib64/xorg/modules/drivers # ls -al
total 10104
drwxr-xr-x 2 root root4096 Apr  5 09:18 .
drwxr-xr-x 5 root root4096 Apr  5 09:18 ..
-rwxr-xr-x 1 root root   27792 Mar  9 04:05 fbdev_drv.so
-rwxr-xr-x 1 root root  115504 Mar 10 12:42 modesetting_drv.so
-rwxr-xr-x 1 root root  212536 Mar 26 04:09 nouveau_drv.so
-rwxr-xr-x 1 root root  176072 Mar 26 04:08 nv_drv.so
-rwxr-xr-x 1 root root 9761088 Apr  5 09:18 nvidia_drv.so
-rwxr-xr-x 1 root root   36040 Mar 26 04:04 vesa_drv.so

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

Title:
  Nvidia 340.108 fails to install with kernels 5.11.x - new patches
  needeed

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  As usual I have opened this (no more) new bug report...

  As ALWAYS happened in the past, EVERY TWO MONTHS new patches are
  needed for old Nvidia 340.108 drivers, that is, with each release of a
  new kernel...

  Nvidia 340.108 fails to install with kernels 5.11.x - new patches
  needeed

  Just to inform develepers that a new patch for Nvidia 340.108 and
  kernel 5.11 is not yet available here:

  
https://github.com/warpme/minimyth2/blob/master/script/nvidia/nvidia-340.108/files/

  Anyway thanks for your great contribution to community and hope you
  publish new patched drivers without having to always report the same
  bug...

  Good day to all the developers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1916640/+subscriptions

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

[Desktop-packages] [Bug 1916640] Re: Nvidia 340.108 fails to install with kernels 5.11.x - new patches needeed

2021-04-09 Thread Ejmarkow

Hi Butterfly (kelebek333),

On the contrary, an Nvidia 340.108 patch is probably required for Linux
Kernel 5.12.

I've been testing Linux kernel 5.12 with the all the Nvidia 340.108
patches including for kernel 5.11) and I'm getting random 'core dump'
crashes. It works fine with kernel 5.11, but not with 5.12.

Here is some info:

uname -a:
Linux galicia 5.12.0-rc5-git-5e46d1b-Pogorze-Karpackie-CUSTOM-KERNEL #3 SMP Wed 
Mar 31 08:36:13 CEST 2021 x86_64 GNU/Linux

dmesg:
NVRM: loading NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019

nvidia_uvm: Loaded the UVM driver, major device number 243

lsmod:
Both nvidia & nvidia_uvm modules are loaded fine


The issue:

Interesting thing is, the shim build for nvidia.ko and nvidia_uvm.ko is
compiling FINE, with NO ERRORS during or after the build. So, no problem
there.

The problem is, I'm getting a random 'core dump' when navigating in the
Google Chrome browser. Chrome isn't the problem though because it is not
mentioned in the 'core dump', but "nvidia_drv.so" is mentioned.

What happens is: Chrome will close first, Xorg will crash and then I'm
logged out of Lightdm.

Both Xorg.bin and Lightdm are mentioned in the following 'core dump',
along with Nvidia. Here is the output for journalctl and dmesg (also
link to pastebin [ https://pastebin.com/raw/9DXR6MY1 ]:

# journalctl

Apr 09 01:15:50 galicia systemd[1]: Starting Hostname Service...
Apr 09 01:15:51 galicia dbus-daemon[457]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
Apr 09 01:15:51 galicia systemd[1]: Started Hostname Service.
Apr 09 01:16:21 galicia systemd[1]: systemd-hostnamed.service: Succeeded.
Apr 09 01:20:30 galicia nscd[476]: 476 checking for monitored file 
`/etc/services': No such file or directory
Apr 09 01:20:45 galicia nscd[476]: 476 checking for monitored file 
`/etc/services': No such file or directory
Apr 09 01:24:13 galicia smartd[463]: Device: /dev/sda [SAT], SMART Usage 
Attribute: 195 Hardware_ECC_Recovered changed from 71 to 70
Apr 09 01:27:55 galicia systemd[1]: Created slice 
system-systemd\x2dcoredump.slice.
Apr 09 01:27:55 galicia systemd[1]: Started Process Core Dump (PID 16933/UID 0).
Apr 09 01:27:58 galicia systemd-coredump[16934]: Process 1126 (Xorg.bin) of 
user 0 dumped core.
 
 Stack trace of thread 1126:
 #0  0x7f34154764a5 raise 
(libc.so.6 + 0x3d4a5)
 #1  0x7f341545f864 abort 
(libc.so.6 + 0x26864)
 #2  0x556b3271138c OsAbort 
(Xorg.bin + 0x1c838c)
 #3  0x556b32712130 
FatalError (Xorg.bin + 0x1c9130)
 #4  0x556b32714df9 n/a 
(Xorg.bin + 0x1cbdf9)
 #5  0x7f341561ba30 
__restore_rt (libpthread.so.0 + 0x13a30)
 #6  0x7f34147fd986 n/a 
(libglx.so + 0xa1f986)
 #7  0x7f3410ad23c7 n/a 
(nvidia_drv.so + 0x6d13c7)
 #8  0x7f3410ad2cdc n/a 
(nvidia_drv.so + 0x6d1cdc)
 #9  0x556b32593f0d n/a 
(Xorg.bin + 0x4af0d)
 #10 0x7f3415460b25 
__libc_start_main (libc.so.6 + 0x27b25)
 #11 0x556b325942ce _start 
(Xorg.bin + 0x4b2ce)
 
 Stack trace of thread 1142:
 #0  0x7f34155396fe 
epoll_wait (libc.so.6 + 0x1006fe)
 #1  0x556b32717ba7 n/a 
(Xorg.bin + 0x1ceba7)
 #2  0x556b3270dee1 n/a 
(Xorg.bin + 0x1c4ee1)
 #3  0x7f3415611299 
start_thread (libpthread.so.0 + 0x9299)
 #4  0x7f34155393b3 __clone 
(libc.so.6 + 0x1003b3)
Apr 09 01:27:58 galicia systemd[1]: systemd-coredump@0-16933-0.service: 
Succeeded.
Apr 09 01:27:58 galicia at-spi-bus-launcher[1420]: X connection to :0 broken 
(explicit kill or server shutdown).
Apr 09 01:27:58 galicia su[1870]: pam_unix(su:session): session closed for user 
root
Apr 09 01:27:58 galicia lightdm[1196]: pam_unix(lightdm:session): session 
closed for user ejm
Apr 09 01:27:58 galicia systemd-logind[552]: Session 2 logged out. Waiting for 
processes to exit.
Apr 09 01:27:58 galicia kernel: show_signal_msg: 34 callbacks suppressed
Apr 09 01:27:58 galicia kernel: lightdm[16941]: segfault at 8 ip 
7fdea653cbba sp 7ffeb03c9568 error 4 in 
libc-2.33.so[7fdea64c

[Desktop-packages] [Bug 1923187] [NEW] [FFe] Enable opencc support

2021-04-09 Thread Gunnar Hjalmarsson

Public bug reported:

opencc is a tool for conversion between traditional and simplified
Chinese. In Debian ibus-libpinyin with opencc support has been in
testing since the year end, and no bugs have been reported as a result
of that.

On the Ubuntu side we had to disable opencc support, since the required
additional dependencies - libopencc1.1, libopencc-data and libmarisa0 -
were in universe.

libopencc1.1 and libopencc-data have since been promoted to main (bug
#1909665), and as regards libmarisa0 it has been cleared for main
promoting by both the MIR team and the security team (bug #1914808).

Accordingly I'm asking the release team for permission to enable opencc
support in Ubuntu hirsute too.

** Affects: ibus-libpinyin (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: ibus-libpinyin (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  [FFe] Enable opencc support

Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  opencc is a tool for conversion between traditional and simplified
  Chinese. In Debian ibus-libpinyin with opencc support has been in
  testing since the year end, and no bugs have been reported as a result
  of that.

  On the Ubuntu side we had to disable opencc support, since the
  required additional dependencies - libopencc1.1, libopencc-data and
  libmarisa0 - were in universe.

  libopencc1.1 and libopencc-data have since been promoted to main (bug
  #1909665), and as regards libmarisa0 it has been cleared for main
  promoting by both the MIR team and the security team (bug #1914808).

  Accordingly I'm asking the release team for permission to enable
  opencc support in Ubuntu hirsute too.

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

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

[Desktop-packages] [Bug 1882143] Re: /usr/lib/libreoffice/program/soffice.bin:11:SvtBroadcaster::Add:SvtListener::StartListening:SwAccessibleNoTextFrame::SwAccessibleNoTextFrame:SwAccessibleGraphic::S

2021-04-09 Thread Bug Watch Updater

Launchpad has imported 5 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=141307.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2021-03-28T21:40:31+00:00 Hugotrip wrote:

Created attachment 170798
the "faulty" macro

This bug was filed from the crash reporting server and is 
br-33ed96ed-3b13-48f2-93d2-e18c54fef244.
=

I made a Basic macro to hide/unhide some texts selected by their style,
and now running it frequently crash LibreOffice, but not always.

It works fine with LibreOffice 6.3.6

I attach the macro for the record.

(this crash was on a fresh parallel install of LibreOffice 7.1.1 -
following instructions from
https://wiki.documentfoundation.org/Installing_in_parallel, with just
the macro copy/pasted.

And if you need context, I'm a teacher, and I use this macro to allow me
to produce from a same document a student version and a (enhanced)
teacher one.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1882143/comments/1


On 2021-03-29T09:17:43+00:00 Xiscofauli wrote:

Thank you for reporting the bug. Please attach a sample document, as this makes 
it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 
'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive 
information before attaching it. 
See 
https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F
 for help on how to do so.)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1882143/comments/2


On 2021-03-29T20:29:23+00:00 Pakifi6818 wrote:

MPL Pro Apk Download latest version 2021 https://mplappguide.in
/download-mpl-apk-for-android/ mpl referral code https://mplappguide.in
/mpl-referral-code/

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1882143/comments/3


On 2021-03-29T20:31:37+00:00 Hugotrip wrote:

Created attachment 170816
A sample documents with fonts needed

I added a crashing document and the fonts used in the styles within it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1882143/comments/4


On 2021-03-29T20:45:41+00:00 Hugotrip wrote:

As I was looking for a sample document, I found out that it seems it's not the 
macro itself that makes Libreoffice 7 crashing, but the attribute hidden to the 
paragraph style 'Prof' : more precisely it's when I check this attribute that 
the crash occurs (you may need to scroll within the document, once the change 
is done to see the crash) :
Indeed, I have another style in my macro that doesn't crash at all, and I tried 
to  open the sample document with the attribute hidden already given (done by 
using a 6.3.6 version of LibreOffice) to the style 'Prof' and it doesn't make 
LibreOffice 7 crash, neither then unhiding the style (but re hiding it will 
make a crash again)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1882143/comments/5


** Changed in: df-libreoffice
   Status: Unknown => New

** Changed in: df-libreoffice
   Importance: Unknown => Low

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

Title:
  
/usr/lib/libreoffice/program/soffice.bin:11:SvtBroadcaster::Add:SvtListener::StartListening:SwAccessibleNoTextFrame::SwAccessibleNoTextFrame:SwAccessibleGraphic::SwAccessibleGraphic:SwAccessibleMap::GetContext

Status in LibreOffice:
  New
Status in libreoffice package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

XFCE has the same result.

I'm able to reproduce this issue on XFCE.

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

Title:
  Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New
Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  [Steps to reproduce this issue]

  1. Install a focal base image
  2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it.
  3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or 
AMD(amdgpu)).
  4. After logging it, the display shows laggy.

  [Additional information]
  1. doesn't see this issue if selecting 'Wayland'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18
  Uname: Linux 5.10.0-1019-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  9 16:23:42 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [103c:3375]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:872b]
  InstallationDate: Installed on 2021-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210324-23:53
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem 
root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 2.0
  dmi.bios.vendor: HP
  dmi.bios.version: S09 Ver. 02.02.00
  dmi.board.name: 872B
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.94.00
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.148
  dmi.modalias: 
dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53307F HP EliteDesk
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1710060] Re: Sound Chipmunks on playback with Jabra Evolve 65 UC Headset

2021-04-09 Thread Snufkin

hello

I'have Ubuntu and this work around not work for me how can I fix it
Please :(

below details:

Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename:   focal


Demons.conf:

# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = (depends on architecture)

; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa

; log-target = auto
; log-level = notice
; log-meta = no
; log-time = no
; log-backtrace = 0

; resample-method = speex-float-1
; avoid-resampling = false
; enable-remixing = yes
; remixing-use-all-sink-channels = yes
; remixing-produce-lfe = no
; remixing-consume-lfe = no
; lfe-crossover-freq = 0

; flat-volumes = no

; rescue-streams = yes

; rlimit-fsize = -1
; rlimit-data = -1
; rlimit-stack = -1
; rlimit-core = -1
; rlimit-as = -1
; rlimit-rss = -1
; rlimit-nproc = -1
; rlimit-nofile = 256
; rlimit-memlock = -1
; rlimit-locks = -1
; rlimit-sigpending = -1
; rlimit-msgqueue = -1
; rlimit-nice = 31
; rlimit-rtprio = 9
; rlimit-rttime = 20

; default-sample-format = s16le
; default-sample-rate = 48000
; alternate-sample-rate = 48000
; default-sample-channels = 2
; default-channel-map = front-left,front-right

; default-fragments = 4
; default-fragment-size-msec = 25

; enable-deferred-volume = yes
deferred-volume-safety-margin-usec = 1
; deferred-volume-extra-delay-usec = 0

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

Title:
  Sound Chipmunks on playback with Jabra Evolve 65 UC Headset

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Fedora:
  Confirmed

Bug description:
  Whenever I choose the Jabra Evolve 65 UC Headset as the playback
  device, there are sound chipmunks. The same was the case with Jabra
  Motion Headset as well. But those two headsets worked perfectly in
  Windows, Mac OS and Android.

  There was a workaround mentioned in
  https://bugzilla.redhat.com/show_bug.cgi?id=1282285 by editing the
  contents of /etc/pulseaudio/daemon.conf :

  Changing

   ;default-sample-rate=44100

  to

   default-sample-rate=48000

  and then running

   pulseaudio -k

  made the sound on Jabra good (no more chipmunks). Also, when I opened
  the Sound Settings with the changes in daemon.conf in place, there
  seems to be some distortions in headset sound, which goes away few
  seconds after I close the sound settings window.

  This problem should be fixed, as many new Linux users will find it
  difficult to edit files requiring root access, and those who do not
  use command line won't be okay with it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   itachi10880 F...m pulseaudio
   /dev/snd/controlC2:  itachi10880 F pulseaudio
   /dev/snd/controlC1:  itachi10880 F pulseaudio
   /dev/snd/controlC0:  itachi10880 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Aug 10 21:11:18 2017
  InstallationDate: Installed on 2016-08-27 (349 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Giga

[Desktop-packages] [Bug 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

@Daniel,

ok, let me try the other desktops.

BTW, the cursor moves smoothly but other operations laggy (e.g. move the
terminal window).

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

Title:
  Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New
Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  [Steps to reproduce this issue]

  1. Install a focal base image
  2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it.
  3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or 
AMD(amdgpu)).
  4. After logging it, the display shows laggy.

  [Additional information]
  1. doesn't see this issue if selecting 'Wayland'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18
  Uname: Linux 5.10.0-1019-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  9 16:23:42 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [103c:3375]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:872b]
  InstallationDate: Installed on 2021-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210324-23:53
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem 
root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 2.0
  dmi.bios.vendor: HP
  dmi.bios.version: S09 Ver. 02.02.00
  dmi.board.name: 872B
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.94.00
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.148
  dmi.modalias: 
dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53307F HP EliteDesk
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

backport the patches from
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/460 doesn't
help.

---

* d5016e5b61f96496f9b31d14eae16f5f0148b748 (HEAD -> 
backport-7-patches-from-Łukasz-sync_present_to_slave_outputs) Remove unused 
function ms_covering_xf86_crtc()
* d892481c2a3d67462f6d2c0d762c43b63cdcd45c xserver/output: rename some badly 
named variables/APIs.
* 1fb0dc09a60e97306088d75fefeed17a39e622ea (master) modesetting: Remove few 
common functions from ms namespace
* a1f28e05d602f5cde825111ca0654311c2aba73b modesetting: remove unnecessary 
ms_covering_xf86_crtc dup of ms_covering_randr_crtc
* d1b3204d1f1357426864c5125bf2ff8b84827d23 modesetting: Find crtc on secondary 
outputs as fallback instead of returning primary crtc
* 028688ba6dc50fbc6430812c608f69912e4196d4 randr: Fix link errors after 
previous commit
* 327441e28fa50fef18c0d15f377e61479fa956a4 present: fix msc offset calculation 
in screen mode
* 8477111ac5e3dee4066efc689d4507fa1b245900 present: Use crtc's screen present 
operation for syncing
* c271560a66d1d0a36dd7b784e75822ee00acc216 modesetting: Initialize present 
extension despite glamor is disabled
* 9f5b6b400462dd5b979c40361c4fcb35d08f9dd1 apt source xserver-xorg-core

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

Title:
  Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New
Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  [Steps to reproduce this issue]

  1. Install a focal base image
  2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it.
  3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or 
AMD(amdgpu)).
  4. After logging it, the display shows laggy.

  [Additional information]
  1. doesn't see this issue if selecting 'Wayland'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18
  Uname: Linux 5.10.0-1019-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  9 16:23:42 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [103c:3375]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:872b]
  InstallationDate: Installed on 2021-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210324-23:53
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem 
root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 2.0
  dmi.bios.vendor: HP
  dmi.bios.version: S09 Ver. 02.02.00
  dmi.board.name: 872B
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.94.00
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.148
  dmi.modalias: 
dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53307F HP EliteDesk
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"

2021-04-09 Thread Bob H

I understand, thanks Rik.

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

Title:
  Ubiquity KDE crash on try/install and from live session with
  "malloc(): unaligned tcache chunk detected"

Status in mesa package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Incomplete
Status in mesa source package in Hirsute:
  Fix Released
Status in ubiquity source package in Hirsute:
  Incomplete

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: KDE
  Date: Sun Mar 21 11:53:44 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

  Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try
  install screen) and from the live session is crashing on launch or
  shortly after.

  Cases where the crash can be triggered:

  - Using a Virtualbox VM, where graphics acceleration is handled by mesa with 
LLVMPIPE
  - Start the ISO on real hardware in 'safe graphics mode'

  Cases where the crash is not encountered:
  - Start the ISO on real intel (HD graphics) hardware with full acceleration.

  NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to
  the previous 20.3.4 in hirsute.

  Try/Install crash:

  Screen fails to start, or starts then crashes on any user action. The
  user is presented with:

  "Installation failed - The installer encountered an unrecoverable error.
  A desktop session will now be run so that you may investigate the problem or 
try installing again"

  Live session crash:

  The installer does not start from the desktop icon. Starting ubiquity
  from the terminal results in an "Aborted (core dumped)" message and
  nothing else.

  The crash is most commonly "malloc(): unaligned tcache chunk
  detected", but inevitably from this sort of memory issue can be
  something like "realloc(): invalid next size"

  An example /var/log/installer/debug log from a session where both
  crashes were triggered is below.

   /var/log/installer/debug 

  Ubiquity 21.04.11
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Write', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-initramfs is disabled since running on read-only media
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  munmap_chunk(): invalid pointer
  Ubiquity 21.04.11
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  malloc(): unaligned tcache chunk detected

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

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

[Desktop-packages] [Bug 1882143] Re: /usr/lib/libreoffice/program/soffice.bin:11:SvtBroadcaster::Add:SvtListener::StartListening:SwAccessibleNoTextFrame::SwAccessibleNoTextFrame:SwAccessibleGraphic::S

2021-04-09 Thread Rico Tzschichholz

** Bug watch added: Document Foundation Bugzilla #141307
   https://bugs.documentfoundation.org/show_bug.cgi?id=141307

** Also affects: df-libreoffice via
   https://bugs.documentfoundation.org/show_bug.cgi?id=141307
   Importance: Unknown
   Status: Unknown

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

Title:
  
/usr/lib/libreoffice/program/soffice.bin:11:SvtBroadcaster::Add:SvtListener::StartListening:SwAccessibleNoTextFrame::SwAccessibleNoTextFrame:SwAccessibleGraphic::SwAccessibleGraphic:SwAccessibleMap::GetContext

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

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

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

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

[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"

2021-04-09 Thread Rik Mills

The ISO file integrity check was recently changed so it now runs in the
background. It does not show while booting or delay boot.

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

Title:
  Ubiquity KDE crash on try/install and from live session with
  "malloc(): unaligned tcache chunk detected"

Status in mesa package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Incomplete
Status in mesa source package in Hirsute:
  Fix Released
Status in ubiquity source package in Hirsute:
  Incomplete

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: KDE
  Date: Sun Mar 21 11:53:44 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

  Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try
  install screen) and from the live session is crashing on launch or
  shortly after.

  Cases where the crash can be triggered:

  - Using a Virtualbox VM, where graphics acceleration is handled by mesa with 
LLVMPIPE
  - Start the ISO on real hardware in 'safe graphics mode'

  Cases where the crash is not encountered:
  - Start the ISO on real intel (HD graphics) hardware with full acceleration.

  NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to
  the previous 20.3.4 in hirsute.

  Try/Install crash:

  Screen fails to start, or starts then crashes on any user action. The
  user is presented with:

  "Installation failed - The installer encountered an unrecoverable error.
  A desktop session will now be run so that you may investigate the problem or 
try installing again"

  Live session crash:

  The installer does not start from the desktop icon. Starting ubiquity
  from the terminal results in an "Aborted (core dumped)" message and
  nothing else.

  The crash is most commonly "malloc(): unaligned tcache chunk
  detected", but inevitably from this sort of memory issue can be
  something like "realloc(): invalid next size"

  An example /var/log/installer/debug log from a session where both
  crashes were triggered is below.

   /var/log/installer/debug 

  Ubiquity 21.04.11
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Write', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-initramfs is disabled since running on read-only media
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  munmap_chunk(): invalid pointer
  Ubiquity 21.04.11
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  malloc(): unaligned tcache chunk detected

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

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

[Desktop-packages] [Bug 1902673] Re: LibreOffice Base : connection to embedded HSQLDB impossible

2021-04-09 Thread Rico Tzschichholz

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

** This bug has been marked a duplicate of bug 1916786
   weak dependency to libreoffice-sdbc-hsqldb

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

Title:
  LibreOffice Base : connection to embedded HSQLDB impossible

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Ubuntu 20.10 64 bits, GNOME
  LibreOffice 7.0.2.2 included in the distribution (not snap).
  French

  I try only to create a new database with LO Base using the default
  HSQLDB system.

  I create a new database choosing the first option : embedded HSQLBD 
  When I try to select the tables to create one, I get an error :
  
/build/libreoffice-pLFcgN/libreoffice-7.0.2/connectivity/source/-commmontools/dbexception.cxx:399

  The problem is the same with Ubuntu 20.04 (LO 6.4) but this problem
  doesn't exist with Ubuntu 18.04 (LO 6.0.7.3)

  Maybe same issue than n° 1875477

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

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

[Desktop-packages] [Bug 1923033] Re: Archive manager drag to extract doesn't work on Gnome with Wayland

2021-04-09 Thread Karol

Also tracked here: https://gitlab.gnome.org/GNOME/file-
roller/-/issues/122

** Bug watch added: gitlab.gnome.org/GNOME/file-roller/-/issues #122
   https://gitlab.gnome.org/GNOME/file-roller/-/issues/122

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

Title:
  Archive manager drag to extract doesn't work on Gnome with Wayland

Status in file-roller package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04

  Opening an archive and dragging a folder/file from it into nautilus
  doesn't extract it.

  file-roller:
    Installed: 3.38.0-1
    Candidate: 3.38.0-1
    Version table:
   *** 3.38.0-1 500
  500 http://pl.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  nautilus:
    Installed: 1:3.38.2-1ubuntu1
    Candidate: 1:3.38.2-1ubuntu1
    Version table:
   *** 1:3.38.2-1ubuntu1 500
  500 http://pl.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  Tested archives: tar.xz, tar.bz2, .zip

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: file-roller 3.38.0-1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  8 12:50:31 2021
  SourcePackage: file-roller
  UpgradeStatus: Upgraded to hirsute on 2021-04-02 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1923033/+subscriptions

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

[Desktop-packages] [Bug 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

Ooops, single monitor, I see.

Next we should probably verify whether it is mutter-specific or a
general Xorg problem. Can you try a desktop that is not GNOME?

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

Title:
  Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New
Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  [Steps to reproduce this issue]

  1. Install a focal base image
  2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it.
  3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or 
AMD(amdgpu)).
  4. After logging it, the display shows laggy.

  [Additional information]
  1. doesn't see this issue if selecting 'Wayland'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18
  Uname: Linux 5.10.0-1019-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  9 16:23:42 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [103c:3375]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:872b]
  InstallationDate: Installed on 2021-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210324-23:53
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem 
root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 2.0
  dmi.bios.vendor: HP
  dmi.bios.version: S09 Ver. 02.02.00
  dmi.board.name: 872B
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.94.00
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.148
  dmi.modalias: 
dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53307F HP EliteDesk
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1923178] [NEW] synaptic fingerprint device(06cb:00df) doesn't work on focal

2021-04-09 Thread Andy Chi

Public bug reported:

[Release]
Focal - 20.04
[libfprint version]
1:1.90.2+tod1-0ubuntu1
[Device]
ZBook Studio G7
[BIOS version]
S91 Ver. 01.04.01
[Fingerprint reader]
06cb:00df Synaptics, Inc.
[Fingerprint reader firmware version]
10.01.3273255

[Expected]
Enroll fingerprint successfully.
[Result]
When enrolling new finger, settings will pop up "Failed to enroll new 
fingerprint".

** Affects: oem-priority
 Importance: Medium
 Assignee: Andy Chi (andch)
 Status: Triaged

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


** Tags: oem-priority originate-from-1866761 stella

** Attachment added: "fprintd-2021-04-09.log"
   
https://bugs.launchpad.net/bugs/1923178/+attachment/5485984/+files/fprintd-2021-04-09.log

** Tags added: oem-priority originate-from-1866761 stella

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

Title:
  synaptic fingerprint device(06cb:00df) doesn't work on focal

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

Bug description:
  [Release]
  Focal - 20.04
  [libfprint version]
  1:1.90.2+tod1-0ubuntu1
  [Device]
  ZBook Studio G7
  [BIOS version]
  S91 Ver. 01.04.01
  [Fingerprint reader]
  06cb:00df Synaptics, Inc.
  [Fingerprint reader firmware version]
  10.01.3273255

  [Expected]
  Enroll fingerprint successfully.
  [Result]
  When enrolling new finger, settings will pop up "Failed to enroll new 
fingerprint".

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

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

[Desktop-packages] [Bug 1871728] Re: geoclue agent process persists after user logout

2021-04-09 Thread Daniel Richard G.

KillUserProcesses=yes is a sledgehammer of a solution. I would advise
just removing the geoclue package.

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

Title:
  geoclue agent process persists after user logout

Status in geoclue-2.0 package in Ubuntu:
  Confirmed

Bug description:
  This concerns geoclue-2.0 2.5.6-0ubuntu1 in Ubuntu focal.

  I am using the Xfce desktop. When a user logs in, a
  /usr/libexec/geoclue-2.0/demos/agent process is started.

  However, when the user logs out, and the associated "systemd --user"
  instance is killed, the geoclue process remains---apparently because
  it is running outside of the process group in which all the other
  session-related processes were in.

  Not only does this prevent the process from being cleaned up
  correctly, if the user logs in again, *another* geoclue process starts
  up. And when they log out, and everything else gets cleaned up...
  *two* useless geoclue processes remain. Repeat ad infinitum.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1871728/+subscriptions

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

[Desktop-packages] [Bug 1896171] Re: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)

Also proposed to Ubuntu in: https://salsa.debian.org/gnome-
team/mutter/-/merge_requests/72

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

Title:
  Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)

Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver).

  Seen in glmark2-wayland, glmark2-es2-wayland, weston-simple-egl.

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

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

[Desktop-packages] [Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver

2021-04-09 Thread Timo Aaltonen

ok, something weird happened, will fix :)

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

Title:
  Cursor bleeds on the platform with Mali armsoc driver

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  [Impact]

  The cursor bleeds because of the bug in xorg which does not refresh the 
sprite background. (LP: #1911479)
  The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu).

  [Test Case]

  Check if cursor is still bleeding with the patched xorg-server

  [ Regression potential ]

  The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver.
  It won't impact other platforms.

  ---
  Xilinx is trying to upstream the patch. It's still under review.
  https://lists.x.org/archives/xorg-devel/2021-March/058672.html

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

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

[Desktop-packages] [Bug 1922712] Re: add metric for new glibc hwcaps

2021-04-09 Thread Sebastien Bacher

** Changed in: ubuntu-report (Ubuntu)
   Importance: Undecided => Low

** Changed in: ubuntu-report (Ubuntu)
   Status: New => Confirmed

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

Title:
  add metric for new glibc hwcaps

Status in ubuntu-report package in Ubuntu:
  Confirmed

Bug description:
  we want to collect information which most recent hwcap is supported by
  a machine.  The result should be a string like "x86-64-v2",
  "x86-64-v3", "x86-64-v4", "z13", "z14", "p9", "p10" depending on "ld-
  linux --help" output.  The string should be empty for architectures
  without glibc hwcaps (currently armhf, arm64, i386, riscv64). The
  string should be empty if no specific hwcaps is supported (e.g. on a
  power8 machine). The string should be "N/A" (not available), when
  trying to run ld-linux on a release with glibc (<< 2.33).

  Note that lexical sorting won't work for "p9", "p10".

  if test -x /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2; then
lddynload=/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
  elif test -x /lib/powerpc64le-linux-gnu/ld64.so.2; then
lddynload=/lib/powerpc64le-linux-gnu/ld64.so.2
  elif test -x /lib/s390x-linux-gnu/ld64.so.1; then
lddynload=/lib/s390x-linux-gnu/ld64.so.1
  fi

  supported=
  if [ -n "$lddynload" ]; then
$lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/'
supported=$($lddynload --help 2>&1 | awk '/^Subdirectories/,/^$/' | awk 
'/supported/ {print $1}')
  fi

  Here, $supported has listed all supported hwcaps, not just the best
  supported one.

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

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

[Desktop-packages] [Bug 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

** Attachment added: "xrandr-verbose"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1923153/+attachment/5485957/+files/xrandr-verbose

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

Title:
  Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New
Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  [Steps to reproduce this issue]

  1. Install a focal base image
  2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it.
  3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or 
AMD(amdgpu)).
  4. After logging it, the display shows laggy.

  [Additional information]
  1. doesn't see this issue if selecting 'Wayland'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18
  Uname: Linux 5.10.0-1019-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  9 16:23:42 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [103c:3375]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:872b]
  InstallationDate: Installed on 2021-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210324-23:53
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem 
root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 2.0
  dmi.bios.vendor: HP
  dmi.bios.version: S09 Ver. 02.02.00
  dmi.board.name: 872B
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.94.00
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.148
  dmi.modalias: 
dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53307F HP EliteDesk
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

BTW, the FPS is 1.

$ DISPLAY=:0 glxgears 
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
344 frames in 5.6 seconds = 61.884 FPS
5 frames in 5.0 seconds =  0.997 FPS
6 frames in 6.0 seconds =  1.002 FPS
6 frames in 6.0 seconds =  1.000 FPS

---

I did confirm the i915(iGPU) + amdgpu(dGPU) could reproduce this issue
as well.

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

Title:
  Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New
Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  [Steps to reproduce this issue]

  1. Install a focal base image
  2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it.
  3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or 
AMD(amdgpu)).
  4. After logging it, the display shows laggy.

  [Additional information]
  1. doesn't see this issue if selecting 'Wayland'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18
  Uname: Linux 5.10.0-1019-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  9 16:23:42 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [103c:3375]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:872b]
  InstallationDate: Installed on 2021-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210324-23:53
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem 
root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 2.0
  dmi.bios.vendor: HP
  dmi.bios.version: S09 Ver. 02.02.00
  dmi.board.name: 872B
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.94.00
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.148
  dmi.modalias: 
dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53307F HP EliteDesk
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1871728] Re: geoclue agent process persists after user logout

2021-04-09 Thread Erik Devriendt

As a workaround, I changed /etc/systemd/logind.conf by putting: 
KillUserProcesses=yes


There might be sideeffects though, like the 'screen' command not surviving the 
logout.

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

Title:
  geoclue agent process persists after user logout

Status in geoclue-2.0 package in Ubuntu:
  Confirmed

Bug description:
  This concerns geoclue-2.0 2.5.6-0ubuntu1 in Ubuntu focal.

  I am using the Xfce desktop. When a user logs in, a
  /usr/libexec/geoclue-2.0/demos/agent process is started.

  However, when the user logs out, and the associated "systemd --user"
  instance is killed, the geoclue process remains---apparently because
  it is running outside of the process group in which all the other
  session-related processes were in.

  Not only does this prevent the process from being cleaned up
  correctly, if the user logs in again, *another* geoclue process starts
  up. And when they log out, and everything else gets cleaned up...
  *two* useless geoclue processes remain. Repeat ad infinitum.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1871728/+subscriptions

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

[Desktop-packages] [Bug 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

What is the output from 'xrandr --verbose' ?

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

Title:
  Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New
Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  [Steps to reproduce this issue]

  1. Install a focal base image
  2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it.
  3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or 
AMD(amdgpu)).
  4. After logging it, the display shows laggy.

  [Additional information]
  1. doesn't see this issue if selecting 'Wayland'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18
  Uname: Linux 5.10.0-1019-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  9 16:23:42 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [103c:3375]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:872b]
  InstallationDate: Installed on 2021-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210324-23:53
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem 
root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 2.0
  dmi.bios.vendor: HP
  dmi.bios.version: S09 Ver. 02.02.00
  dmi.board.name: 872B
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.94.00
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.148
  dmi.modalias: 
dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53307F HP EliteDesk
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

Xorg actually doesn't have support for synchronizing multiple screens
very well. The compositor can only paint all screens at once, and then
the Xorg drivers have to output their areas at separate times later.

The 'modeset' Xorg driver will just sync to one and tear on the others.
And I am not sure how radeon/amdgpu are expected to interplay. If they
support a TearFree feature then that means at least one of them has to
delay each frame, which you might see as lag. Also, if the monitors have
different refresh rates then there's no guarantee Xorg will sync to the
fastest one -- it might sync to the slowest, which has to be worked
around in the drivers.

I suggest the first thing to investigate here is to see if you can get
both GPUs using the same driver (from the kernel onward). Because using
both 'radeon' and 'amdgpu' at the same time might be causing this.

GNOME Wayland sessions don't have this problem at all because there is
no Xorg and it schedules each display separately.

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

** Also affects: xserver-xorg-video-ati (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New
Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  [Steps to reproduce this issue]

  1. Install a focal base image
  2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it.
  3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or 
AMD(amdgpu)).
  4. After logging it, the display shows laggy.

  [Additional information]
  1. doesn't see this issue if selecting 'Wayland'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18
  Uname: Linux 5.10.0-1019-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  9 16:23:42 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [103c:3375]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:872b]
  InstallationDate: Installed on 2021-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210324-23:53
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem 
root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 2.0
  dmi.bios.vendor: HP
  dmi.bios.version: S09 Ver. 02.02.00
  dmi.board.name: 872B
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.94.00
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.148
  dmi.modalias: 
dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53307F HP EliteDesk
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

** Tags added: amdgpu radeon

** Package changed: xorg (Ubuntu) => xorg-server (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/1923153

Title:
  Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New
Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  [Steps to reproduce this issue]

  1. Install a focal base image
  2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it.
  3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or 
AMD(amdgpu)).
  4. After logging it, the display shows laggy.

  [Additional information]
  1. doesn't see this issue if selecting 'Wayland'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18
  Uname: Linux 5.10.0-1019-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  9 16:23:42 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [103c:3375]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:872b]
  InstallationDate: Installed on 2021-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210324-23:53
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem 
root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 2.0
  dmi.bios.vendor: HP
  dmi.bios.version: S09 Ver. 02.02.00
  dmi.board.name: 872B
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.94.00
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.148
  dmi.modalias: 
dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53307F HP EliteDesk
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

When I attached another monitor to dGPU (which means connecting monitor
to each iGPU and dGPU), then there is no problem.

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

Title:
  Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  Confirmed
Status in xorg package in Ubuntu:
  New

Bug description:
  [Steps to reproduce this issue]

  1. Install a focal base image
  2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it.
  3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or 
AMD(amdgpu)).
  4. After logging it, the display shows laggy.

  [Additional information]
  1. doesn't see this issue if selecting 'Wayland'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18
  Uname: Linux 5.10.0-1019-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  9 16:23:42 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [103c:3375]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:872b]
  InstallationDate: Installed on 2021-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210324-23:53
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem 
root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 2.0
  dmi.bios.vendor: HP
  dmi.bios.version: S09 Ver. 02.02.00
  dmi.board.name: 872B
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.94.00
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.148
  dmi.modalias: 
dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53307F HP EliteDesk
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1896171] Re: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)

Second fix proposed in:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1817

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

Title:
  Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)

Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver).

  Seen in glmark2-wayland, glmark2-es2-wayland, weston-simple-egl.

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

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

[Desktop-packages] [Bug 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

I tried to install hirsute daily build
(495fe189e32d873ba79d7753134c22353ea89e8e6d62498f6c825a5de6a8a4a7) and
didn't see this issue.

but the xorg might have some problems when using hirsute.

here is the result of $ xrandr -d :0 --prop
---
PRIME Synchronization: 0 
supported: 0, 1
GAMMA_LUT_SIZE: 4096 
range: (0, -1)
DEGAMMA_LUT_SIZE: 4096 
range: (0, -1)
GAMMA_LUT: 0 
range: (0, 65535)
CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 
0 1 
DEGAMMA_LUT: 0 
range: (0, 65535)
TearFree: auto 
supported: off, on, auto
subconnector: HDMI 
supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native
HDCP Content Type: HDCP Type0 
supported: HDCP Type0, HDCP Type1
Content Protection: Undesired 
supported: Undesired, Desired, Enabled
vrr_capable: 0 
range: (0, 1)
max bpc: 8 
range: (8, 16)
underscan vborder: 0 
range: (0, 128)
underscan hborder: 0 
range: (0, 128)
underscan: off 
supported: off, on, auto
scaling mode: None 
supported: None, Full, Center, Full aspect
link-status: Good 
supported: Good, Bad
CONNECTOR_ID: 80 
supported: 80
non-desktop: 0 
range: (0, 1)
---

When issuing the same command on hirsute daily build, it shows
---
non-desktop: 0 
range: (0, 1)
---
only.


Tried packages from 
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers doesn't help.

** Tags added: oem-priority originate-from-1916427 stella

** Changed in: oem-priority
 Assignee: (unassigned) => jeremyszu (os369510)

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
   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/1923153

Title:
  Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  Confirmed
Status in xorg package in Ubuntu:
  New

Bug description:
  [Steps to reproduce this issue]

  1. Install a focal base image
  2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it.
  3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or 
AMD(amdgpu)).
  4. After logging it, the display shows laggy.

  [Additional information]
  1. doesn't see this issue if selecting 'Wayland'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18
  Uname: Linux 5.10.0-1019-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  9 16:23:42 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [103c:3375]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:872b]
  InstallationDate: Installed on 2021-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210324-23:53
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem 
root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 2.0
  dmi.bios.vendor: HP
  dmi.bios.version: S09 Ver. 02.02.00
  dmi.board.name: 872B
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 09.94.00
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 9.148
  dmi.modalias: 
dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53307F HP EliteDesk
  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 N/A
  version.xserver-xorg-core: xserver-xorg-co

[Desktop-packages] [Bug 1923130] Re: duplicate folders in "show application" menu

2021-04-09 Thread Ubuntu Foundations Team Bug Bot

The attachment "duplicate folders" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  duplicate folders in "show application" menu

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I see more duplicate folders in the "show application" menu. I open
  this and I see all folders have the same applications

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  9 11:02:02 2021
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1923153] [NEW] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

Public bug reported:

[Steps to reproduce this issue]

1. Install a focal base image
2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it.
3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or 
AMD(amdgpu)).
4. After logging it, the display shows laggy.

[Additional information]
1. doesn't see this issue if selecting 'Wayland'

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18
Uname: Linux 5.10.0-1019-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Apr  9 16:23:42 2021
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [103c:3375]
 Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company Renoir [103c:872b]
InstallationDate: Installed on 2021-04-09 (0 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem 
root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/30/2020
dmi.bios.release: 2.0
dmi.bios.vendor: HP
dmi.bios.version: S09 Ver. 02.02.00
dmi.board.name: 872B
dmi.board.vendor: HP
dmi.board.version: KBC Version 09.94.00
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 9.148
dmi.modalias: 
dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr:
dmi.product.family: 103C_53307F HP EliteDesk
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 N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: oem-priority
 Importance: Critical
 Assignee: jeremyszu (os369510)
 Status: Confirmed

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


** Tags: amd64 apport-bug focal oem-priority originate-from-1916427 stella 
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/1923153

Title:
  Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  Confirmed
Status in xorg package in Ubuntu:
  New

Bug description:
  [Steps to reproduce this issue]

  1. Install a focal base image
  2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it.
  3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or 
AMD(amdgpu)).
  4. After logging it, the display shows laggy.

  [Additional information]
  1. doesn't see this issue if selecting 'Wayland'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18
  Uname: Linux 5.10.0-1019-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  9 16:23:42 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / 
Radeon 520 OEM] [103c:3375]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:872b]

[Desktop-packages] [Bug 1923090] Re: autopkgtest fails in hirsute on armhf

I am seeing the redirection when using firefox on android. It might be
that Google uses the UA string to serve a mobile version of the consent
page, and for some reason it thinks the UA string of the desktop version
on armhf is that of a mobile device. Not sure why I'm not able to
reproduce this in an armhf container though.

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

Title:
  autopkgtest fails in hirsute on armhf

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  https://autopkgtest.ubuntu.com/packages/f/firefox/hirsute/armhf

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  hirsute/hirsute/armhf/f/firefox/20210408_154741_90187@/log.gz

  ...
  autopkgtest [15:44:53]: test command3: [---
  Traceback (most recent call last):
File "/tmp/autopkgtest.D3W44g/build.bPt/src/debian/tests/search-engines", 
line 51, in 
  search URL for Google: 
https://consent.google.com/ml?continue=https://www.google.com/search%3Fchannel%3Dfs%26client%3Dubuntu%26q%3Dfoobarbaz&gl=GB&m=1&pc=srp&hl=en&src=1
  assert url.netloc == v['netloc']
  AssertionError
  autopkgtest [15:45:08]: test command3: ---]
  autopkgtest [15:45:11]: test command3:  - - - - - - - - - - results - - - - - 
- - - - -
  command3 FAIL non-zero exit status 1
  autopkgtest [15:45:12]: test command3:  - - - - - - - - - - stderr - - - - - 
- - - - -
  Traceback (most recent call last):
File "/tmp/autopkgtest.D3W44g/build.bPt/src/debian/tests/search-engines", 
line 51, in 
  assert url.netloc == v['netloc']
  AssertionError
  ...

  Most likely an infrastructure proxy/networking error.

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

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

[Desktop-packages] [Bug 1923140] Re: Xorg freeze

Thanks for the bug report. We will need to see a screenshot or original
log of the problem while it is happening. Not just a vague recollection
that there was a problem.

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

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

** Summary changed:

- Xorg freeze
+ Freeze

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

Title:
  Freeze

Status in Ubuntu:
  Incomplete

Bug description:
  Actually this is not the version that freezes the boot. With a clean
  install both of groovy and focal I can use the computer with no
  problem. The bug appears after installing the prompted updates at
  first login.

  I have three different outcomes when it comes to booting:
  - Blinking underscore cursor (with no error messages on the screen)
  - iwlwifi unhandled algorithm 0x707 error
  - FAULT found at  [IBUS] not exactly this message

  I guess I could install updates one by one and see which one faults at
  boot, then boot through tty4 (it is the only way I've found to do it
  after boot fails, or freezes) and then link the logs to this  issue.

  I could really use some guidance from a more experienced user because
  I don't really know how to debug this things :D

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-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: Fri Apr  9 08:51:36 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9a49] (rev 01) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics [1028:09d9]
 Subsystem: Dell GP107M [GeForce MX350] [1028:09d9]
  InstallationDate: Installed on 2021-04-08 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Dell Inc. Inspiron 7400
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b912e5af-f189-4002-8e26-306f96626d10 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2021
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 072W08
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd02/26/2021:br1.5:svnDellInc.:pnInspiron7400:pvr:rvnDellInc.:rn072W08:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7400
  dmi.product.sku: 09D9
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-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/+bug/1923140/+subscriptions

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

[Desktop-packages] [Bug 1923140] Re: Xorg freeze

2021-04-09 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  Freeze

Status in Ubuntu:
  Incomplete

Bug description:
  Actually this is not the version that freezes the boot. With a clean
  install both of groovy and focal I can use the computer with no
  problem. The bug appears after installing the prompted updates at
  first login.

  I have three different outcomes when it comes to booting:
  - Blinking underscore cursor (with no error messages on the screen)
  - iwlwifi unhandled algorithm 0x707 error
  - FAULT found at  [IBUS] not exactly this message

  I guess I could install updates one by one and see which one faults at
  boot, then boot through tty4 (it is the only way I've found to do it
  after boot fails, or freezes) and then link the logs to this  issue.

  I could really use some guidance from a more experienced user because
  I don't really know how to debug this things :D

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-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: Fri Apr  9 08:51:36 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9a49] (rev 01) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics [1028:09d9]
 Subsystem: Dell GP107M [GeForce MX350] [1028:09d9]
  InstallationDate: Installed on 2021-04-08 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Dell Inc. Inspiron 7400
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=b912e5af-f189-4002-8e26-306f96626d10 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2021
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 072W08
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd02/26/2021:br1.5:svnDellInc.:pnInspiron7400:pvr:rvnDellInc.:rn072W08:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7400
  dmi.product.sku: 09D9
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-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/+bug/1923140/+subscriptions

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

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