date:20210415

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

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

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

Title:
  Gnome Shell fails to list some apps with .desktop files

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  VirtualBox does not show up anywhere in Gnome-shell as an application.

  Wine doesn't show up anywhere in Gnome-shell as an application.

  Those are two of the more egregious examples. I can run them from the
  command line. The .desktop entries clearly exist in
  /usr/share/applications. I've verified and reverified all the .desktop
  entries and checked them against the Gnome documentation to verify
  everything is correct. Yet it simply refuses to load these apps. A
  dump of the VirtualBox entry dumped below (even editted it to use
  absolute path).Similar problems with Wine which was installed via
  Ubuntu software so no reason for it to be rejected/disappear.

  Ubuntu: 20.10
  VirtualBox:   Installed: 6.1.16-dfsg-6~ubuntu1.20.10.1 (from ubuntu Groovy 
repository)
  Wine:   Candidate: 5.0-3ubuntu1 (also from Groovy repository)

  ...so...all are pointing to the current repository (Groovy). I'm at a
  loss here even how to fix it since I can't really "upgrade" or "fix"
  the .desktop entry since nothing is wrong with those. They are just
  "ghosts" as far as Gnome-shell is concerned.

  [Desktop Entry]
  Name=VirtualBox
  GenericName=PC virtualization solution
  Type=Application
  Exec=/usr/bin/VirtualBox
  TryExec=VirtualBox
  Keywords=virtualization;
  Keywords[de]=Virtualisierung;
  Keywords[ru]=виртуализация;
  
MimeType=application/x-virtualbox-vbox;application/x-virtualbox-vbox-extpack;application/x-virtualbox-ovf;application/x-virtualbox-ova;
  Icon=virtualbox
  Categories=Emulator;System;Utility;
  Actions=Manager;
  Comment=Run several virtual systems on a single host computer
  Comment[de]=Mehrere virtuelle Maschinen auf einem einzigen Rechner ausführen
  Comment[it]=Esegui più macchine virtuali su un singolo computer
  Comment[ko]=가상 머신
  Comment[pl]=Uruchamianie wielu systemów wirtualnych na jednym komputerze 
gospodarza
  Comment[ru]=Запуск нескольких виртуальных машин на одном компьютере
  Comment[sv]=Kör flera virtuella system på en enda värddator

  [Desktop Action Manager]
  Exec=VirtualBox
  Name=Open Oracle VM Manager
  Name[de]=Oracle VM Manager öffnen

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.2-1ubuntu1~20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 10 08:01:17 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-07 (552 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs:
   linux-image-5.8.0-43-generic
   linux-base
  RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2021-02-07 (3 days ago)

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

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

[Desktop-packages] [Bug 1915565] Re: screen fades for about 10 seconds then returns to normal

[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/1915565

Title:
  screen fades for about 10 seconds then returns to normal

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  The fading happens online at . But it also happens offline in 
games.
  Using Ubuntu 20.04
  Unable to locate package pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Feb 12 13:14:56 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 5.4.0-64-generic, x86_64: installed
   bbswitch, 0.8, 5.4.0-65-generic, x86_64: installed
   nvidia, 390.141, 5.4.0-64-generic, x86_64: installed
   nvidia, 390.141, 5.4.0-65-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:820c]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:820c]
  InstallationDate: Installed on 2017-04-14 (1400 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0eef:c04d D-WAV Scientific Co., Ltd eGalaxTouch 
EXC3000-0367-44.01.00
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0408:5090 Quanta Computer, Inc. HP Wide version HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic 
root=UUID=07e929a4-0ebf-4ecc-bedd-3f5fbf79e6d8 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 820C
  dmi.board.vendor: HP
  dmi.board.version: 82.29
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd09/21/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn820C:rvr82.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion Notebook
  dmi.product.sku: X0S49UA#ABA
  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: Sat Oct 17 14:45:19 2020
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.8-2ubuntu2.4

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

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

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

2021-04-15 Thread James Hennig

The solution has been found and should have been rather obvious in the
first place... Just try a different distribution.

I decided to try out Linux Mint 20.1 and have been testing it for the
past ~6 hours, completely stock (except for all updates installed), no
kernel modifications or GRUB options and it works every time on bootup
with the touchpad. I am rather surprised that such a relatively old
kernel (5.4) works with this new-ish laptop. Perhaps this was why I was
so falsely focused on having newer kernels available in a distribution
in the first place.

I even tried 40 consecutive reboots whilst messing with the touchpad as
the machine was booting and it still worked every time. Let it be known
that the fix for the Lenovo IdeaPad 3 14ADA05 is to simply install Linux
Mint. I have to imagine that other Ubuntu-based installs also work with
this particular laptop, especially since it says "Fix Released" under
Ubuntu and Ubuntu-related distributions.

As far as Manjaro goes, also let it be known that something was
introduced after Kernel 5.9.16-1 which breaks the ability for the
touchpad to reliably work with this laptop. My best educated guess is
that something is loaded too early or too late during bootup which gets
jumbled up at random. No idea what that could possibly be, but I hope
that Manjaro devs might take note. I know that at least @Helmut Stult
might still be looking in this thread.

I consider this fixed for my laptop :)

-- 
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 Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Button

[Desktop-packages] [Bug 1922438] Re: Firefox unusable on Kubuntu 21.04 Wayland session

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

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

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

Title:
  Firefox unusable on Kubuntu 21.04 Wayland session

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  I tried Wayland session on a Kubuntu 21.04 beta live usb.
  Firefox is practically unusable since it refreshes the screen only on 
re-focusing like described in this bug report: 
https://bugzilla.mozilla.org/show_bug.cgi?id=1616894
  Unfortunately, setting widget.wayland_vsync.enabled to false does not make 
any difference.
  Also tried starting firefox from terminal with MOZ_ENABLE_WAYLAND=1, again no 
difference.
  According to the above bug report this should be fixed, no?

  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
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kubuntu4308 F pulseaudio
  BuildID: 20210318103112
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sat Apr  3 15:54:32 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
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IpRoute:
   default via 192.168.10.1 dev enp0s31f6 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000 
   192.168.10.0/24 dev enp0s31f6 proto kernel scope link src 192.168.10.20 
metric 100
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  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
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=87.0/20210318103112 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd01/07/2021:br1.18:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1924667] [NEW] Once in a while, xorg crashes after a restart.

2021-04-15 Thread 朱云鹏

Public bug reported:

[  1681.827] (II) FBDEV: driver for framebuffer: fbdev
[  1681.827] (II) VESA: driver for VESA chipsets: vesa
[  1681.828] (**) modeset(0): claimed PCI slot 0@0:2:0
[  1681.828] (II) modeset(0): using default device
[  1681.828] (WW) Falling back to old probe method for fbdev
[  1681.828] (II) Loading sub module "fbdevhw"
[  1681.828] (II) LoadModule: "fbdevhw"
[  1681.828] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[  1681.828] (II) Module fbdevhw: vendor="X.Org Foundation"
[  1681.828]compiled for 1.20.8, module version = 0.0.2
[  1681.828]ABI class: X.Org Video Driver, version 24.1
[  1681.828] (II) modeset(0): Creating default Display subsection in Screen 
section
"Default Screen Section" for depth/fbbpp 24/32
[  1681.828] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[  1681.828] (EE) 
[  1681.828] (EE) Backtrace:
[  1681.829] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x563983d6277c]
[  1681.829] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) 
[0x7f7d9807041f]
[  1681.829] (EE) 2: /usr/lib/xorg/Xorg (xf86PlatformMatchDriver+0x5b0) 
[0x563983c5c400]
[  1681.829] (EE) 3: /usr/lib/xorg/Xorg (xf86CollectOptions+0x77) 
[0x563983c3f227]
[  1681.829] (EE) unw_get_proc_name failed: no unwind info found [-10]
[  1681.829] (EE) 4: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) 
[0x7f7d97845bd0]
[  1681.829] (EE) 5: /usr/lib/xorg/Xorg (InitOutput+0xb94) [0x563983c42be4]
[  1681.829] (EE) 6: /usr/lib/xorg/Xorg (InitFonts+0x1d4) [0x563983c04e34]
[  1681.829] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) 
[0x7f7d97e8e0b3]
[  1681.829] (EE) 8: /usr/lib/xorg/Xorg (_start+0x2e) [0x563983beea7e]
[  1681.829] (EE) 
[  1681.829] (EE) Segmentation fault at address 0x124
[  1681.829] (EE) 
Fatal server error:
[  1681.829] (EE) Caught signal 11 (Segmentation fault). Server aborting
[  1681.829] (EE) 
[  1681.829] (EE) 

I am using Ubuntu 20.04. When I reboot my laptop, the screen will
probably go grey. After checking the log, I find the error message
above.

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

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

Title:
  Once in a while, xorg crashes after a restart.

Status in xorg package in Ubuntu:
  New

Bug description:
  [  1681.827] (II) FBDEV: driver for framebuffer: fbdev
  [  1681.827] (II) VESA: driver for VESA chipsets: vesa
  [  1681.828] (**) modeset(0): claimed PCI slot 0@0:2:0
  [  1681.828] (II) modeset(0): using default device
  [  1681.828] (WW) Falling back to old probe method for fbdev
  [  1681.828] (II) Loading sub module "fbdevhw"
  [  1681.828] (II) LoadModule: "fbdevhw"
  [  1681.828] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
  [  1681.828] (II) Module fbdevhw: vendor="X.Org Foundation"
  [  1681.828]  compiled for 1.20.8, module version = 0.0.2
  [  1681.828]  ABI class: X.Org Video Driver, version 24.1
  [  1681.828] (II) modeset(0): Creating default Display subsection in Screen 
section
"Default Screen Section" for depth/fbbpp 24/32
  [  1681.828] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
  [  1681.828] (EE) 
  [  1681.828] (EE) Backtrace:
  [  1681.829] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x563983d6277c]
  [  1681.829] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) 
[0x7f7d9807041f]
  [  1681.829] (EE) 2: /usr/lib/xorg/Xorg (xf86PlatformMatchDriver+0x5b0) 
[0x563983c5c400]
  [  1681.829] (EE) 3: /usr/lib/xorg/Xorg (xf86CollectOptions+0x77) 
[0x563983c3f227]
  [  1681.829] (EE) unw_get_proc_name failed: no unwind info found [-10]
  [  1681.829] (EE) 4: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) 
[0x7f7d97845bd0]
  [  1681.829] (EE) 5: /usr/lib/xorg/Xorg (InitOutput+0xb94) [0x563983c42be4]
  [  1681.829] (EE) 6: /usr/lib/xorg/Xorg (InitFonts+0x1d4) [0x563983c04e34]
  [  1681.829] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) 
[0x7f7d97e8e0b3]
  [  1681.829] (EE) 8: /usr/lib/xorg/Xorg (_start+0x2e) [0x563983beea7e]
  [  1681.829] (EE) 
  [  1681.829] (EE) Segmentation fault at address 0x124
  [  1681.829] (EE) 
  Fatal server error:
  [  1681.829] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [  1681.829] (EE) 
  [  1681.829] (EE) 

  I am using Ubuntu 20.04. When I reboot my laptop, the screen will
  probably go grey. After checking the log, I find the error message
  above.

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

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

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

Bug 1924625 shows this crash happening on a machine with lots of
extensions installed, which might explain why we've had trouble finding
the cause.

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

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

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

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

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

  ---

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

    MUTTER_SYNC=1

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

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

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

[Desktop-packages] [Bug 1924625] Re: gnome-shell repeatedly restarting and core dumping

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

Thanks for the bug report. Your log appears to show you are experiencing
bug 1886059 which nobody else has been able to reproduce. Please follow
the instructions in bug 1886059.

Please also try uninstalling all of these:

'openweather-extens...@jenslody.de', 'arc-m...@linxgem33.com', 
'window-corner-prev...@jak.io', 'window-corner-prev...@fabiomereu.it', 
'cpupo...@mko-sl.de', 'gsconn...@andyholmes.github.io', 'lockk...@vaina.lt', 
'arcm...@arcmenu.com', 'caffe...@patapon.info', 
'clipboard-indica...@tudmotu.com', 'dash-to-d...@micxgx.gmail.com', 
'noannoya...@sindex.com', 'shellt...@emasab.it', 
'workspaces-to-d...@passingthru67.gmail.com', 'cpufreq@konkor', 
'drive-m...@gnome-shell-extensions.gcampax.github.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'putwin...@clemens.lab21.org']"
b'org.gnome.shell' b'disabled-extensions' b"['desktop-icons@csoriano', 
'ubuntu-d...@ubuntu.com', 'miniv...@thesecretaryofwar.com'

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

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

Title:
  gnome-shell repeatedly restarting and core dumping

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Yesterday (2021-04-14) I ran apt update/upgrade, then rebooted my
  laptop overnight. With the upgrade Linux 5.4.0-71 was installed. Now I
  have an issue where gnome-shell restarts repeatedly. Looking in the
  logs, I see that gnome-shell is core dumping when this occurs. I have
  not (yet) identified any behavior that causes the problem.

  I disabled extensions with the Gnome Tweak Tool and rebooted into the
  previous Linux version but the problem remains. This may be related to
  https://bugs.launchpad.net/bugs/1923864 and
  https://bugs.launchpad.net/bugs/1924606 as the symptoms are similar
  and both have been reported in within the correct time frame.

  The contents of the log file from an instance of this occurring is
  attached.

  I am using Ubuntu 20.04.2
  gnome-shell version is 3.36.7-0ubuntu0.20.04.1

  Please let me know if you have any questions.

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

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

-- 
Mailing list: https://launchpad.net/~desktop-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: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

** Also affects: xserver-xorg-driver-ati via
   https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/194
   Importance: Unknown
   Status: Unknown

-- 
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:
  [radeon] Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  In Progress
Status in xserver-xorg-driver-ati:
  Unknown
Status in xorg-server 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 1917939] Re: Windows maximise underneath dock after monitor sleep

Sorry for the confusion but it is confusing...

* The first gnome-shell fix in comment #8 is bogus. It never worked and
was removed in comment #14 because it had also caused regression bug
1922772.

* The first mutter fix included in 3.38.4-1ubuntu1 (comment #6) did work
but also caused regression bug 1922034. So the mutter fix has now been
removed.

* The second gnome-shell fix in comment #14 is the only fix we are now
using.

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

Title:
  Windows maximise underneath dock after monitor sleep

Status in Dash to dock:
  New
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Under wayland on 21.04 windows keep maximising underneath the dock. So
  I can see icons "through" the dock, when I shouldn't. In the attached
  screenshot you can see Telegram showing through the dock.

  If I switch to the application in question, unmaximise and re-
  maximise, it goes back to maximising inside the usable area of my
  desktop.

  But when I suspend and resume, then login, I'm left with windows under
  the dock again. Never seen this under xorg. I only discovered I was in
  wayland when I tried to ALT+F2, R to restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.3-2ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  5 19:21:39 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-06-11 (267 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2020-12-14 (81 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1917939/+subscriptions

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

[Desktop-packages] [Bug 1917939] Re: Windows maximise underneath dock after monitor sleep

The mutter fix for this was removed in order to fix regression bug
1922772. It was replaced by the gnome-shell fix above.

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

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

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

Title:
  Windows maximise underneath dock after monitor sleep

Status in Dash to dock:
  New
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Under wayland on 21.04 windows keep maximising underneath the dock. So
  I can see icons "through" the dock, when I shouldn't. In the attached
  screenshot you can see Telegram showing through the dock.

  If I switch to the application in question, unmaximise and re-
  maximise, it goes back to maximising inside the usable area of my
  desktop.

  But when I suspend and resume, then login, I'm left with windows under
  the dock again. Never seen this under xorg. I only discovered I was in
  wayland when I tried to ALT+F2, R to restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.3-2ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  5 19:21:39 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-06-11 (267 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2020-12-14 (81 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1917939/+subscriptions

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

[Desktop-packages] [Bug 1922266] Re: eth0 interface name change fails on Pi 3/3+

2021-04-15 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  eth0 interface name change fails on Pi 3/3+

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-meta source package in Hirsute:
  Fix Released
Status in ubuntu-settings source package in Hirsute:
  New

Bug description:
  The netplan configuration in ubuntu-raspi-settings (and more widely,
  the network-config in the gadget used on the server images) fails to
  rename the internal ethernet interface on Pi 3B and 3B+ models from
  "en" to "eth0". In the netplan case this is because the
  driver matching logic doesn't handle space-separate driver matches
  (although the underlying networkd system does); in the cloud-init case
  it simply refuses to rename interfaces that aren't matched by full MAC
  address.

  The intended fix is to stop attempting to do this via netplan or
  cloud-init, and simply handle this via a networkd .link file in
  ubuntu-raspi-settings. This will require an update to the relevant
  seeds as this package is currently only pulled into ubuntu-desktop-
  raspi, not ubuntu-server-raspi.

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

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

[Desktop-packages] [Bug 1914230] Re: On-screen keyboard for Japanese doesn't display Japanese characters, only English

This bug was fixed in the package gnome-shell - 3.38.4-1ubuntu2

---
gnome-shell (3.38.4-1ubuntu2) hirsute; urgency=medium

  [ Daniel van Vugt ]
  * Add layout-Try-to-allocate-before-getting-size-of-tracke.patch.
To fix LP: #1919979 and also to re-fix LP: #1917939
(LP: #1919979, #1917939)
  * Drop layout-Allow-updating-struts-in-Overview.patch.
Because it caused a regression and doesn't seem to have been necessary
anyway. (LP: #1922772)

  [ Marco Trevisan (Treviño) ]
  * debian/patches: Fix suggestions box actor population in non-latin languages
(LP: #1914230)
  * debian/patches: Enable to use Escape to cancel auth requests (with limits)
(LP: #1921929)
  * debian/patches: Refresh

 -- Marco Trevisan (Treviño)   Thu, 15 Apr 2021
06:20:27 +0200

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

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

Title:
  On-screen keyboard for Japanese doesn't display Japanese characters,
  only English

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

Bug description:
  This is about touch keyboard.
  Screen keyboard doesn't display other languages characters, only english 
characters. I noticed many users concern about that on forums

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

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

[Desktop-packages] [Bug 1917939] Re: Windows maximise underneath dock after monitor sleep

This bug was fixed in the package gnome-shell - 3.38.4-1ubuntu2

---
gnome-shell (3.38.4-1ubuntu2) hirsute; urgency=medium

  [ Daniel van Vugt ]
  * Add layout-Try-to-allocate-before-getting-size-of-tracke.patch.
To fix LP: #1919979 and also to re-fix LP: #1917939
(LP: #1919979, #1917939)
  * Drop layout-Allow-updating-struts-in-Overview.patch.
Because it caused a regression and doesn't seem to have been necessary
anyway. (LP: #1922772)

  [ Marco Trevisan (Treviño) ]
  * debian/patches: Fix suggestions box actor population in non-latin languages
(LP: #1914230)
  * debian/patches: Enable to use Escape to cancel auth requests (with limits)
(LP: #1921929)
  * debian/patches: Refresh

 -- Marco Trevisan (Treviño)   Thu, 15 Apr 2021
06:20:27 +0200

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

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

Title:
  Windows maximise underneath dock after monitor sleep

Status in Dash to dock:
  New
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Under wayland on 21.04 windows keep maximising underneath the dock. So
  I can see icons "through" the dock, when I shouldn't. In the attached
  screenshot you can see Telegram showing through the dock.

  If I switch to the application in question, unmaximise and re-
  maximise, it goes back to maximising inside the usable area of my
  desktop.

  But when I suspend and resume, then login, I'm left with windows under
  the dock again. Never seen this under xorg. I only discovered I was in
  wayland when I tried to ALT+F2, R to restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.3-2ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  5 19:21:39 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-06-11 (267 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2020-12-14 (81 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1917939/+subscriptions

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

[Desktop-packages] [Bug 1919979] Re: Dock covers the top panel during the login animation

This bug was fixed in the package gnome-shell - 3.38.4-1ubuntu2

---
gnome-shell (3.38.4-1ubuntu2) hirsute; urgency=medium

  [ Daniel van Vugt ]
  * Add layout-Try-to-allocate-before-getting-size-of-tracke.patch.
To fix LP: #1919979 and also to re-fix LP: #1917939
(LP: #1919979, #1917939)
  * Drop layout-Allow-updating-struts-in-Overview.patch.
Because it caused a regression and doesn't seem to have been necessary
anyway. (LP: #1922772)

  [ Marco Trevisan (Treviño) ]
  * debian/patches: Fix suggestions box actor population in non-latin languages
(LP: #1914230)
  * debian/patches: Enable to use Escape to cancel auth requests (with limits)
(LP: #1921929)
  * debian/patches: Refresh

 -- Marco Trevisan (Treviño)   Thu, 15 Apr 2021
06:20:27 +0200

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

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

Title:
  Dock covers the top panel during the login animation

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Dock covers the top panel during the login animation (top left corner
  of the screen).

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

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

[Desktop-packages] [Bug 1922772] Re: Overview search causes the workarea to reshape, desktop-icons-ng to restart and the new window to lose focus

This bug was fixed in the package gnome-shell - 3.38.4-1ubuntu2

---
gnome-shell (3.38.4-1ubuntu2) hirsute; urgency=medium

  [ Daniel van Vugt ]
  * Add layout-Try-to-allocate-before-getting-size-of-tracke.patch.
To fix LP: #1919979 and also to re-fix LP: #1917939
(LP: #1919979, #1917939)
  * Drop layout-Allow-updating-struts-in-Overview.patch.
Because it caused a regression and doesn't seem to have been necessary
anyway. (LP: #1922772)

  [ Marco Trevisan (Treviño) ]
  * debian/patches: Fix suggestions box actor population in non-latin languages
(LP: #1914230)
  * debian/patches: Enable to use Escape to cancel auth requests (with limits)
(LP: #1921929)
  * debian/patches: Refresh

 -- Marco Trevisan (Treviño)   Thu, 15 Apr 2021
06:20:27 +0200

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

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

Title:
  Overview search causes the workarea to reshape, desktop-icons-ng to
  restart and the new window to lose focus

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Release: Ubuntu 21.04 (20210406 iso image)

  Software, version: gnome-shell, 3.38.4-1ubuntu1

  How to reproduce:
  1) Boot up Ubuntu 21.04 image (live session or installed)
  2) Once inside shell, go to overview (either using Super key or clicking on 
Activities)
  3) Search for any application (eg., terminal) and launch it.

  Expected:
  The application launches normally and usable.

  Actual:
  The application launches but the window looses focus. When the application is 
launching, the desktop icons disappear for few seconds and reappear. When they 
reappear the launched application window will not have focus.

  If we launch the application from the app grid (without searching
  first) or from the dock, the window retains the focus.

  Tested on VM (quickemu and virt-manager).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  6 22:14:04 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-04-06 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210405)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  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/1922772/+subscriptions

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

[Desktop-packages] [Bug 1924625] [NEW] gnome-shell repeatedly restarting and core dumping

2021-04-15 Thread Eric Van Horn

Public bug reported:

Yesterday (2021-04-14) I ran apt update/upgrade, then rebooted my laptop
overnight. With the upgrade Linux 5.4.0-71 was installed. Now I have an
issue where gnome-shell restarts repeatedly. Looking in the logs, I see
that gnome-shell is core dumping when this occurs. I have not (yet)
identified any behavior that causes the problem.

I disabled extensions with the Gnome Tweak Tool and rebooted into the
previous Linux version but the problem remains. This may be related to
https://bugs.launchpad.net/bugs/1923864 and
https://bugs.launchpad.net/bugs/1924606 as the symptoms are similar and
both have been reported in within the correct time frame.

The contents of the log file from an instance of this occurring is
attached.

I am using Ubuntu 20.04.2
gnome-shell version is 3.36.7-0ubuntu0.20.04.1

Please let me know if you have any questions.

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

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


** Tags: amd64 apport-bug focal third-party-packages

** Attachment added: "Log message from gnome-shell core dump"
   
https://bugs.launchpad.net/bugs/1924625/+attachment/5488539/+files/log%20messages

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

Title:
  gnome-shell repeatedly restarting and core dumping

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Yesterday (2021-04-14) I ran apt update/upgrade, then rebooted my
  laptop overnight. With the upgrade Linux 5.4.0-71 was installed. Now I
  have an issue where gnome-shell restarts repeatedly. Looking in the
  logs, I see that gnome-shell is core dumping when this occurs. I have
  not (yet) identified any behavior that causes the problem.

  I disabled extensions with the Gnome Tweak Tool and rebooted into the
  previous Linux version but the problem remains. This may be related to
  https://bugs.launchpad.net/bugs/1923864 and
  https://bugs.launchpad.net/bugs/1924606 as the symptoms are similar
  and both have been reported in within the correct time frame.

  The contents of the log file from an instance of this occurring is
  attached.

  I am using Ubuntu 20.04.2
  gnome-shell version is 3.36.7-0ubuntu0.20.04.1

  Please let me know if you have any questions.

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

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

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

[Desktop-packages] [Bug 1924623] [NEW] Bluetooth headset pairing issue

2021-04-15 Thread Mykyta

Public bug reported:

I am unable to connect a HOCO ES32 PLUS bluetooth headset. Device is
visible and in pairable mode, but after running:

bluetoothctl

[bluetooth]# show
Controller 04:33:C2:AA:17:60 (public)
 Name: mykyt
 Alias: mykyt
 Class: 0x001c010c
 Powered: yes
 Discoverable: yes
 DiscoverableTimeout: 0x
 Pairable: yes
 UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
 UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
 UUID: OBEX Object Push  (1105--1000-8000-00805f9b34fb)
 UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
 UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
 UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
 UUID: Vendor specific   (5005--1000-8000-0002ee01)
 UUID: Headset AG(1112--1000-8000-00805f9b34fb)
 UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
 UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
 UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
 UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
 UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
 UUID: Headset   (1108--1000-8000-00805f9b34fb)
 UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
 UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
 Modalias: usb:v1D6Bp0246d0535
 Discovering: yes
Advertising Features:
 ActiveInstances: 0x00
 SupportedInstances: 0x05
 SupportedIncludes: tx-power
 SupportedIncludes: appearance
 SupportedIncludes: local-name
 SupportedSecondaryChannels: 1M
 SupportedSecondaryChannels: 2M
 SupportedSecondaryChannels: Coded

i get:

Failed to pair: org.bluez.Error.AuthenticationTimeout

or

Failed to pair: org.bluez.Error.AuthenticationCanceled

or

Failed to pair: org.bluez.Error.Failed

I tried every single solution i was able to find for similar problems,
including changing controller mode to bredr, reinstalling pulseaudio,
unblocking rfkill, checking if my device is in pairable mode, using
blueman and so on.

The fact is, bluetooth is working on my laptop (I can connect to my
phone and my other bluetooth headset MEIZU EP51) and also my headset
HOCO ES32 PLUS is working and is able to connect to my phone and my
other laptop DELL INSPIRON 7359 which is running on ubuntu 18.04.

I really hope you can help me. Please tell me if you need more information and 
I will provide it.
Thank you!
--

lsb_release -rd

Description:Ubuntu 20.04.2 LTS
Release:20.04

apt-cache policy bluez

bluez:
  Installed: 5.53-0ubuntu3
  Candidate: 5.53-0ubuntu3
  Version table:
 *** 5.53-0ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

--

Expected behavior:

After turning on bluetooth and clicking on device name in settings ->
bluetooth device is connecting and pairing successfully.

Current behavior:

Pairing fails.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-49-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 16 00:28:19 2021
InstallationDate: Installed on 2020-08-27 (231 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Acer Swift SF314-57G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic 
root=UUID=59c2b478-ae5a-4c28-8c13-6b3721fe1f3b ro nouveau.modeset=0 quiet 
splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/06/2020
dmi.bios.release: 1.14
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.14
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Floris_IL
dmi.board.vendor: IL
dmi.board.version: V1.14
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.14
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd05/06/2020:br1.14:efr1.14:svnAcer:pnSwiftSF314-57G:pvrV1.14:rvnIL:rnFloris_IL:rvrV1.14:cvnAcer:ct10:cvrChassisVersion:
dmi.product.family: Swift 3
dmi.product.name: Swift SF314-57G
dmi.product.sku: 
dmi.product.version: V1.14
dmi.sys.vendor: Acer
hciconfig:
 hci0:  Type: Primary  Bus: USB
  BD Address: 04:33:C2:AA:17:60  ACL MTU: 1021:4  SCO MTU: 96:6
  UP RUNNING PSCAN
  RX bytes:39055 acl:127 sco:0 events:3605 errors:0
  TX bytes:791744 acl:182 sco:0 commands:3327 errors:0
mtime.conffile..etc.bluetooth.network.conf: 2021-04-15T23:51:23.664531

** Affects: bluez (Ubuntu)
 Importance:

[Desktop-packages] [Bug 1922266] Re: eth0 interface name change fails on Pi 3/3+

2021-04-15 Thread Brian Murray

** Also affects: ubuntu-meta (Ubuntu Hirsute)
   Importance: Undecided
   Status: Fix Released

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

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

Title:
  eth0 interface name change fails on Pi 3/3+

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-meta source package in Hirsute:
  Fix Released
Status in ubuntu-settings source package in Hirsute:
  New

Bug description:
  The netplan configuration in ubuntu-raspi-settings (and more widely,
  the network-config in the gadget used on the server images) fails to
  rename the internal ethernet interface on Pi 3B and 3B+ models from
  "en" to "eth0". In the netplan case this is because the
  driver matching logic doesn't handle space-separate driver matches
  (although the underlying networkd system does); in the cloud-init case
  it simply refuses to rename interfaces that aren't matched by full MAC
  address.

  The intended fix is to stop attempting to do this via netplan or
  cloud-init, and simply handle this via a networkd .link file in
  ubuntu-raspi-settings. This will require an update to the relevant
  seeds as this package is currently only pulled into ubuntu-desktop-
  raspi, not ubuntu-server-raspi.

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

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

This bug was fixed in the package ubuntu-report - 1.6.4

---
ubuntu-report (1.6.4) hirsute; urgency=medium

  * Add new metric for glibc hwcaps (LP: #1922712)

 -- William 'jawn-smith' Wilson   Wed, 07
Apr 2021 16:52:26 -0500

** Changed in: ubuntu-report (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
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:
  Fix Released

Bug description:
  FFe: We would like to collect that information with 21.04 to get a
  better view of supported hardware for the new hwcaps.  The risk should
  be minimal, only adding an extra flag, and the server side collecting
  the data can handle that, according to Didier.

  pull request at https://github.com/ubuntu/ubuntu-report/pull/34

  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 "" (empty), when trying to run
  ld-linux on a release with glibc (<< 2.33). The string should be "-"
  (dash) when not having any hwcaps mentioned.

  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 1922266] Re: eth0 interface name change fails on Pi 3/3+

2021-04-15 Thread Dave Jones

Attaching debdiff; test builds are available from the following PPA:

https://launchpad.net/~waveform/+archive/ubuntu/ubuntu-
settings/+packages

** Patch added: "1-1922266.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1922266/+attachment/5488517/+files/1-1922266.debdiff

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

Title:
  eth0 interface name change fails on Pi 3/3+

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  The netplan configuration in ubuntu-raspi-settings (and more widely,
  the network-config in the gadget used on the server images) fails to
  rename the internal ethernet interface on Pi 3B and 3B+ models from
  "en" to "eth0". In the netplan case this is because the
  driver matching logic doesn't handle space-separate driver matches
  (although the underlying networkd system does); in the cloud-init case
  it simply refuses to rename interfaces that aren't matched by full MAC
  address.

  The intended fix is to stop attempting to do this via netplan or
  cloud-init, and simply handle this via a networkd .link file in
  ubuntu-raspi-settings. This will require an update to the relevant
  seeds as this package is currently only pulled into ubuntu-desktop-
  raspi, not ubuntu-server-raspi.

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

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

[Desktop-packages] [Bug 1921187] Re: Illegal instruction at start − sse3 required on i386

2021-04-15 Thread Joao Dias

This situation also affects me.
When I updated the chromium-browser, it stopped to function.
I tried to install an older version (65.0.3325.181-0ubuntu1), but there are 
conflicts with needed packages (chromium-codecs-ffmpeg-extra 
chromium-codecs-ffmpeg) once it doesn't try to install the older version of 
them but the most recent version.

Any help?

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

Title:
  Illegal instruction at start − sse3 required on i386

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  From dpkg.log:
  2021-03-13 17:56:19 upgrade chromium-browser:i386 
87.0.4280.66-0ubuntu0.18.04.1 89.0.4389.82-0ubuntu0.18.04.1
  Won't start at all after this upgrade. Downgrading to 65.0.3325.181-0ubuntu1 
works. Downgrading to 87.0.4280.66-0ubuntu0.18.04.1 is not possible anymore.
  OS: Ubuntu 18.04.5 LTS (Lubuntu)
  cat /proc/cpuinfo 
  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 13
  model name: Intel(R) Pentium(R) M processor 1.60GHz
  stepping  : 6
  microcode : 0x18
  cpu MHz   : 600.000
  cache size: 2048 KB
  physical id   : 0
  siblings  : 1
  core id   : 0
  cpu cores : 1
  apicid: 0
  initial apicid: 0
  fdiv_bug  : no
  f00f_bug  : no
  coma_bug  : no
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 2
  wp: yes
  flags : fpu vme de pse tsc msr mce cx8 sep mtrr pge mca cmov clflush 
dts acpi mmx fxsr sse sse2 ss tm pbe bts cpuid est tm2 pti
  bugs  : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs itlb_multihit
  bogomips  : 1199.98
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 32 bits virtual
  power management:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: i386
  CurrentDesktop: LXDE
  DRM.card0-LVDS-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
   modes: 1024x768
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Desktop-Session:
   'Lubuntu'
   '/etc/xdg/lubuntu:/etc/xdg/xdg-Lubuntu:/etc/xdg'
   
'/etc/xdg/lubuntu:/usr/share/gdm:/var/lib/menu-xdg:/usr/share/Lubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  DistroRelease: Ubuntu 18.04
  Env:
   'None'
   'None'
  InstalledPlugins:
   
  Load-Avg-1min: 3.84
  Load-Processes-Running-Percent:   0.7%
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: FUJITSU SIEMENS LIFEBOOK C1110
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-140-generic 
root=UUID=29d733a6-7024-41fc-bbe4-2d58c0c1d500 ro splash quiet vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-140.144-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-140-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/25/2005
  dmi.bios.vendor: Phoenix/FUJITSU
  dmi.bios.version: Version 1.30
  dmi.board.name: FJNB16F
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.modalias: 
dmi:bvnPhoenix/FUJITSU:bvrVersion1.30:bd03/25/2005:svnFUJITSUSIEMENS:pnLIFEBOOKC1110:pvr:rvnFUJITSU:rnFJNB16F:rvr:cvnFUJITSUSIEMENS:ct10:cvr:
  dmi.product.name: LIFEBOOK C1110
  dmi.sys.vendor: FUJITSU SIEMENS
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1274613] Re: module-bluetooth-discover does not load on login

2021-04-15 Thread Mykyta

Same problem still persists on focal. module-bluetooth-discover is not
loaded when the system is started up and can`t be manually loaded too.
Please reach out if you need more info.

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

Title:
  module-bluetooth-discover does not load on login

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  The following lines appear in /etc/pulse/default.pa, which I have not
  modified:

  .ifexists module-bluetooth-discover.so
  load-module module-bluetooth-discover
  .endif

  Expected: module-bluetooth-discover is loaded on login, as configured.

  Observed: pulseaudio's module-bluetooth-discover does not load on
  login. My system does not detect and set up sinks when I connect to
  Bluetooth devices (including an A2DP speaker and a headset).

  If I issue, in a terminal window:

  $ pactl load-module module-bluetooth-discover 
  24

  …then the devices are detected and sinks set up correctly.

  $ lsb_release -rd && apt-cache policy pulseaudio-module-bluetooth
  Description:Ubuntu 13.10
  Release:13.10
  pulseaudio-module-bluetooth:
Installed: 1:4.0-0ubuntu6
Candidate: 1:4.0-0ubuntu6
Version table:
   *** 1:4.0-0ubuntu6 0
  500 http://mirrors.mit.edu/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: pulseaudio 1:4.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-17.30-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  khaeru 2051 F pulseaudio
  Date: Thu Jan 30 12:18:50 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-10-29 (457 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to saucy on 2013-09-11 (140 days ago)
  dmi.bios.date: 05/15/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 085VR5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn085VR5:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1923841] Re: [SRU] Increase recording quality

This bug was fixed in the package alsa-utils - 1.2.4-1ubuntu3

---
alsa-utils (1.2.4-1ubuntu3) hirsute; urgency=medium

  * d/p/0013-aplay-try-to-use-16-bit-format-to-increase-capture-q.patch
- aplay: try to use 16-bit format to increase capture quality
(LP: #1923841)

 -- Kai-Heng Feng   Wed, 14 Apr 2021
16:27:22 +0800

** Changed in: alsa-utils (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Increase recording quality

Status in HWE Next:
  New
Status in alsa-utils package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  Audio gets recorded by "arecord" has really bad sound quality when the volume 
is low.

  [Fix]
  https://github.com/alsa-project/alsa-utils/pull/69
  Switch the default audio format from 8 bits to 16 bits if hardware supports 
it.

  [Test]
  1. Plug a microphone.
  2. Run `arecord | aplay` and say something to the microphone.
  3. Only noise can be heard.

  With the fix applied, the recording is clear.

  [Where problems could occur]
  If there's any hardware falsely advertised to support 16 bits, this change 
will break them.
  However, this is effectively using `arecord -f cd` or `arecord -f cdr`, so 
that's not likely.

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

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

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

2021-04-15 Thread Manu

** Attachment added: "'tail -f -c 0 /var/log/cups/error_log > error_log_12' 
while printing test12.pdf"
   
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1920190/+attachment/5488474/+files/error_log_12

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

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

Status in cups-filters package in Ubuntu:
  Confirmed

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

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

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

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

  Please let me know if you need more information.

  ## Further info:

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

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

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

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

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

  
  ## Trying to debug with cupsfilter:

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

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

  The latter uses gstoraster:

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

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

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

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

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

2021-04-15 Thread Manu

** Attachment added: "'tail -f -c 0 /var/log/cups/error_log > error_log_48' 
while printing test48.pdf"
   
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1920190/+attachment/5488475/+files/error_log_48

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

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

Status in cups-filters package in Ubuntu:
  Confirmed

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

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

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

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

  Please let me know if you need more information.

  ## Further info:

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

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

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

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

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

  
  ## Trying to debug with cupsfilter:

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

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

  The latter uses gstoraster:

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

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

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

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

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

2021-04-15 Thread Manu

@Pratyush
I attached both logs as seperate files. I only put 3 sheets of paper in the 
tray each time and cancelled on the printer once those were out, as I didn't 
want to print that many useless pages, but as the processing happens before the 
printer starts printing I think this shouldn't matter.

I would call the RAM usage signifcant in both cases. I think I observed
a little over 3GB for the 12 page file in htop (RES column) and at least
16.3GB peak for the 48 page file. This seems to be even more (roughly
double) than in my experiment calling pdftoraster manually.

The 48 page file took almost 10 minutes before the printer started
printing.

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

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

Status in cups-filters package in Ubuntu:
  Confirmed

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

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

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

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

  Please let me know if you need more information.

  ## Further info:

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

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

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

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

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

  
  ## Trying to debug with cupsfilter:

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

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

  The latter uses gstoraster:

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

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

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

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

[Desktop-packages] [Bug 1924606] [NEW] gnome-shell somethimes freeze and crash

2021-04-15 Thread Dmytrii

Public bug reported:

gnome-shell somethimes freeze and crash

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-49-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 15 22:03:14 2021
DisplayManager: gdm3
InstallationDate: Installed on 2020-10-03 (194 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal third-party-packages

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

Title:
  gnome-shell somethimes freeze and crash

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  gnome-shell somethimes freeze and crash

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 15 22:03:14 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-03 (194 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  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/1924606/+subscriptions

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

[Desktop-packages] [Bug 1922539] Re: Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead.

2021-04-15 Thread Laurent Bonnaud

Thanks for the fix!

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

Title:
  Option "-listen" for file descriptors is deprecated. Please use
  "-listenfd" instead.

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  I see this warning message in the logs:

  # journalctl | grep -e -listen
  Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: (WW) Option "-listen" 
for file descriptors is deprecated
  Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: Please use "-listenfd" 
instead.
  Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: (WW) Option "-listen" 
for file descriptors is deprecated
  Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: Please use "-listenfd" 
instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  Uname: Linux 5.11.11-05-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Mon Apr  5 10:07:15 2021
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  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/mutter/+bug/1922539/+subscriptions

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

[Desktop-packages] [Bug 1922034] Re: Resizing gnome-terminal moves the window

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

---
mutter (3.38.4-1ubuntu2) hirsute; urgency=medium

  [ Daniel van Vugt ]
  * Revert "debian/patches: Properly handle configuration events on windows"
to fix a regression making some windows to move on resize (LP: #1922034).
  * Add 61-mutter.rules-Enable-KMS-modifiers-for-Raspberry-P.patch.
To enable KMS modifiers on Raspberry Pi, which means to enable the
first fix in wayland-dma-buf-Add-support-for-DRM_FORMAT_ABGR2101010.patch
(LP: #1896171)

  [ Marco Trevisan (Treviño) ]
  * debian/patches: Backport workspace fixes from upstream gnome-3-38 branch
  * debian/patches: Use Xwayland pkg-config if available
  * debian/patches: Use -listenfd to invoke XWayland if available (LP: #1922539)

 -- Marco Trevisan (Treviño)   Thu, 15 Apr 2021
06:28:51 +0200

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

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

Title:
  Resizing gnome-terminal moves the window

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  When slowly resizing a gnome-terminal window from either the top edge
  or the left edge, the window is moved. The top/left edge moves with
  the cursor, but the bottom/right edge doesn't stay in place.

  I assume this is because of how gnome-terminal can only be resized one
  line/column at a time. I assume resizing the window from the top or
  left edge works by moving the window up or to the left and expanding
  the width to make the bottom or right edge stay in place, and
  something about this logic has changed in a recent gnome-shell update
  to make it not account for windows which can't be resized pixel by
  pixel.

  Attached is a video which shows the bug in action.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 31 11:17:23 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-21 (495 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago)

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

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

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

---
mutter (3.38.4-1ubuntu2) hirsute; urgency=medium

  [ Daniel van Vugt ]
  * Revert "debian/patches: Properly handle configuration events on windows"
to fix a regression making some windows to move on resize (LP: #1922034).
  * Add 61-mutter.rules-Enable-KMS-modifiers-for-Raspberry-P.patch.
To enable KMS modifiers on Raspberry Pi, which means to enable the
first fix in wayland-dma-buf-Add-support-for-DRM_FORMAT_ABGR2101010.patch
(LP: #1896171)

  [ Marco Trevisan (Treviño) ]
  * debian/patches: Backport workspace fixes from upstream gnome-3-38 branch
  * debian/patches: Use Xwayland pkg-config if available
  * debian/patches: Use -listenfd to invoke XWayland if available (LP: #1922539)

 -- Marco Trevisan (Treviño)   Thu, 15 Apr 2021
06:28:51 +0200

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Fix Released

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 1922539] Re: Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead.

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

---
mutter (3.38.4-1ubuntu2) hirsute; urgency=medium

  [ Daniel van Vugt ]
  * Revert "debian/patches: Properly handle configuration events on windows"
to fix a regression making some windows to move on resize (LP: #1922034).
  * Add 61-mutter.rules-Enable-KMS-modifiers-for-Raspberry-P.patch.
To enable KMS modifiers on Raspberry Pi, which means to enable the
first fix in wayland-dma-buf-Add-support-for-DRM_FORMAT_ABGR2101010.patch
(LP: #1896171)

  [ Marco Trevisan (Treviño) ]
  * debian/patches: Backport workspace fixes from upstream gnome-3-38 branch
  * debian/patches: Use Xwayland pkg-config if available
  * debian/patches: Use -listenfd to invoke XWayland if available (LP: #1922539)

 -- Marco Trevisan (Treviño)   Thu, 15 Apr 2021
06:28:51 +0200

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

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

Title:
  Option "-listen" for file descriptors is deprecated. Please use
  "-listenfd" instead.

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  I see this warning message in the logs:

  # journalctl | grep -e -listen
  Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: (WW) Option "-listen" 
for file descriptors is deprecated
  Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: Please use "-listenfd" 
instead.
  Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: (WW) Option "-listen" 
for file descriptors is deprecated
  Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: Please use "-listenfd" 
instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  Uname: Linux 5.11.11-05-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Mon Apr  5 10:07:15 2021
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  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/mutter/+bug/1922539/+subscriptions

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

[Desktop-packages] [Bug 1916488] Re: SRU 1.64.5 to focal

2021-04-15 Thread Treviño

Testing this for a while now, no problem noticed

❯ apt-cache policy gjs   
gjs:
  Installato: 1.64.5-0ubuntu0.20.04.01
  Candidato:  1.64.5-0ubuntu0.20.04.01
  Tabella versione:
 *** 1.64.5-0ubuntu0.20.04.01 400


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

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

Title:
  SRU 1.64.5 to focal

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

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some performance 
improvements and crash fixes backported from the development branch.
  https://gitlab.gnome.org/GNOME/gjs/-/tags/1.64.5

  [ Test case ]

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

  GNOME Shell and its components should continue working with no
  javascript related errors, as well other gjs based apps like polari

  [ Regression potential ]

  GJS based GTK4 should work properly, resolution of GI types was
  changed and so exported GI types should continue working.

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

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

[Desktop-packages] [Bug 1919924] Re: Scrolling on label doesn't work

2021-04-15 Thread Treviño

Using test indicator, and scrolling on a test label

Signal "scroll-event" emitted. Steps: 1, Direction: 1
Signal "scroll-event" emitted. Steps: 1, Direction: 1
Signal "scroll-event" emitted. Steps: 1, Direction: 1
Signal "scroll-event" emitted. Steps: 1, Direction: 1
Signal "scroll-event" emitted. Steps: 1, Direction: 1
Signal "scroll-event" emitted. Steps: 1, Direction: 1
Signal "scroll-event" emitted. Steps: 1, Direction: 1
Signal "scroll-event" emitted. Steps: 1, Direction: 1
Signal "scroll-event" emitted. Steps: 1, Direction: 3
Signal "scroll-event" emitted. Steps: 1, Direction: 1
Signal "scroll-event" emitted. Steps: 1, Direction: 1
Signal "scroll-event" emitted. Steps: 1, Direction: 1
Signal "scroll-event" emitted. Steps: 1, Direction: 1
Signal "scroll-event" emitted. Steps: 1, Direction: 3
Signal "scroll-event" emitted. Steps: 1, Direction: 1
Signal "scroll-event" emitted. Steps: 1, Direction: 0
Signal "scroll-event" emitted. Steps: 1, Direction: 2

gnome-shell-extension-appindicator:
  Installato: 33.1-0ubuntu0.20.04.2
  Candidato:  33.1-0ubuntu0.20.04.2
  Tabella versione:
 *** 33.1-0ubuntu0.20.04.2 400
400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
400 http://archive.ubuntu.com/ubuntu focal-proposed/main i386 Packages


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

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

Title:
  Scrolling on label doesn't work

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

Bug description:
  [ Impact ]

  Scrolling on indicator label doesn't cause the scroll appindicator
  event to be emitted

  [ Test case ]

  Using the appindicator test tool:
   
https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js

  1. Run it with gjs
  2. Show a label
  3. Ensure that scroll events are printed in the terminal and that the icon is 
changed

  [ Regression potential ]

  Scroll events on icon doesn't work anymore

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

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

[Desktop-packages] [Bug 1919927] Re: Wrong (or no) signals are emitted when icons are added / removed

2021-04-15 Thread Treviño

Confirmed working:


method call time=1618505915.474415 sender=:1.35592 -> destination=:1.34 
serial=17 path=/StatusNotifierWatcher; interface=org.kde.StatusNotifierWatcher; 
member=RegisterStatusNotifierItem
   string "/org/ayatana/NotificationItem/Hello"
signal time=1618505915.487399 sender=:1.34 -> destination=(null destination) 
serial=179639 path=/StatusNotifierWatcher; 
interface=org.kde.StatusNotifierWatcher; member=StatusNotifierItemRegistered
   string ":1.35592/org/ayatana/NotificationItem/Hello"


signal time=1618505925.70 sender=:1.34 -> destination=(null destination) 
serial=179654 path=/StatusNotifierWatcher; 
interface=org.kde.StatusNotifierWatcher; member=StatusNotifierItemUnregistered
   string ":1.35592/org/ayatana/NotificationItem/Hello


gnome-shell-extension-appindicator:
  Installato: 33.1-0ubuntu0.20.04.2
  Candidato:  33.1-0ubuntu0.20.04.2
  Tabella versione:
 *** 33.1-0ubuntu0.20.04.2 400
400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
400 http://archive.ubuntu.com/ubuntu focal-proposed/main i386 Packages


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

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

Title:
  Wrong (or no) signals are emitted when icons are added / removed

Status in gnome-shell-extension-appindicator package in Ubuntu:
  In Progress
Status in gnome-shell-extension-appindicator source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  When adding and removing signals the indicators extension should emit signals 
following the protocol

https://www.freedesktop.org/wiki/Specifications/StatusNotifierItem/StatusNotifierWatcher/

  So we should emit the service name by default when known

  [ Test case ]

  Run
   dbus-monitor --session "interface='org.kde.StatusNotifierWatcher'"

  When an indicator is added, signals such as should be emitted:

  signal time=1616029764.911986 sender=:1.34490 -> destination=(null 
destination) serial=3905 path=/StatusNotifierWatcher; 
interface=org.kde.StatusNotifierWatcher; member=StatusNotifierItemRegistered
 string ":1.109/org/ayatana/NotificationItem/psensor"
  signal time=1616029764.928864 sender=:1.34490 -> destination=(null 
destination) serial=3991 path=/StatusNotifierWatcher; 
interface=org.kde.StatusNotifierWatcher; member=StatusNotifierItemRegistered
 string ":1.34459/StatusNotifierItem"
   
  When removed:
  signal time=1616033768.529066 sender=:1.34490 -> destination=(null 
destination) serial=8711 path=/StatusNotifierWatcher; 
interface=org.kde.StatusNotifierWatcher; member=StatusNotifierItemUnregistered
 string ":1.34649/StatusNotifierItem"

  Removed events should be also emitted when the extension is disabled
  via gnome-shell-extension-prefs

  [ Regression potential ]

  Some clients won't interpret the events correctly causing the
  indicator not to work as expected

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

-- 
Mailing list: https://launchpad.net/~desktop-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-15 Thread Matthias Klose

** Changed in: ubuntu-report (Ubuntu)
   Status: Triaged => Fix Committed

-- 
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:
  Fix Committed

Bug description:
  FFe: We would like to collect that information with 21.04 to get a
  better view of supported hardware for the new hwcaps.  The risk should
  be minimal, only adding an extra flag, and the server side collecting
  the data can handle that, according to Didier.

  pull request at https://github.com/ubuntu/ubuntu-report/pull/34

  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 "" (empty), when trying to run
  ld-linux on a release with glibc (<< 2.33). The string should be "-"
  (dash) when not having any hwcaps mentioned.

  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 1922712] Re: add metric for new glibc hwcaps

2021-04-15 Thread Didier Roche

I reviewed the branch and after some fixes, we +1 on it.
CI is passing, the new code is covered by the same amount of testing than the 
rest of the code.

I did a run-try locally with ubuntu-report --show:
{
  "Version": "21.04",
  "OEM": {
"Vendor": "Entroware",
"Product": "Kratos",
"Family": "Not Applicable"
  },
  "BIOS": {
"Vendor": "American Megatrends Inc.",
"Version": "1.05.02E"
  },
  "CPU": {
"OpMode": "32-bit, 64-bit",
"CPUs": "8",
"Threads": "2",
"Cores": "4",
"Sockets": "1",
"Vendor": "GenuineIntel",
"Family": "6",
"Model": "158",
"Stepping": "10",
"Name": "Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz",
"Virtualization": "VT-x"
  },
  "Arch": "amd64",
  "HwCap": "x86-64-v3",
  "GPU": [
{
  "Vendor": "8086",
  "Model": "3e9b"
},
{
  "Vendor": "10de",
  "Model": "1c8d"
}
  ],
  "RAM": 16.2,
  "Partitions": [
0.5
  ],
  "Screens": [
{
  "Size": "344mmx194mm",
  "Resolution": "1920x1080",
  "Frequency": "60.02"
},
{
  "Size": "527mmx296mm",
  "Resolution": "1920x1080",
  "Frequency": "60.00"
}
  ],
  "Autologin": false,
  "LivePatch": false,
  "Session": {
"DE": "ubuntu:GNOME",
"Name": "ubuntu",
"Type": "x11"
  },
  "Language": "fr_FR",
  "Timezone": "Europe/Paris",
  "Install": {
"Media": "Ubuntu 20.04 LTS \"Focal Fossa\" - Release amd64 (20200423)",
"Type": "GTK",
"OEM": false,
"PartitionMethod": "use_zfs",
"DownloadUpdates": true,
"Language": "fr",
"Minimal": false,
"RestrictedAddons": true,
"Stages": {
  "0": "language",
  "3": "console_setup",
  "53": "wireless",
  "82": "prepare",
  "130": "partman",
  "135": "partman",
  "137": "start_install",
  "141": "timezone",
  "142": "usersetup",
  "156": "user_done",
  "406": "done"
}
  }
}


You can note the new entry is present:   "HwCap": "x86-64-v3",

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

Bug description:
  FFe: We would like to collect that information with 21.04 to get a
  better view of supported hardware for the new hwcaps.  The risk should
  be minimal, only adding an extra flag, and the server side collecting
  the data can handle that, according to Didier.

  pull request at https://github.com/ubuntu/ubuntu-report/pull/34

  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 "" (empty), when trying to run
  ld-linux on a release with glibc (<< 2.33). The string should be "-"
  (dash) when not having any hwcaps mentioned.

  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 1924586] Re: Dead keys for French accents not working on Firefox Ubuntu package

2021-04-15 Thread baptx

I noticed that typing the character ` works but I still cannot type the
French accents mentioned earlier.

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

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

Status in firefox package in Ubuntu:
  New

Bug description:
  Hello,

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

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

  Thanks.

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

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

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

2021-04-15 Thread baptx

Currently I am using Firefox 87.0 (64-bit) package from Lubuntu 20.04.
My laptop is Dell XPS 13 Developer Edition, revision 2 (French
keyboard).

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

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

Status in firefox package in Ubuntu:
  New

Bug description:
  Hello,

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

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

  Thanks.

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

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

[Desktop-packages] [Bug 1924583] Re: ASPEED AST driver seems unstable in 20.04.2 LTS

2021-04-15 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/1924583

Title:
  ASPEED AST driver seems unstable in 20.04.2 LTS

Status in xorg package in Ubuntu:
  New

Bug description:
  I have had the screen go blank several times.  Each time that this
  occurred, I was selecting the "Settings" item from the upper right
  corner arrow.  Perhaps there are a lot of low level accesses that
  occur when this menu item is selected that somehow locks up the ASPEED
  AST driver or some other part of the display?  When this problem
  occurs, the only way I have been able to recover is to power cycle the
  system.  The info collected for this bug report was taken after
  rebooting the system.

  I originally had a problem that the initial login screen did not
  display (blank screen) but I came across the following that provided a
  solution of disable Wayland:

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

  I am not able to reproduce the problem at will.  I can usually access
  the "Settings" without a problem.  However, each time the screen has
  gone blank it was right after clicking on the "Settings" menu item.  I
  have six identical machines (Supermicro SYS-5019C-FL) and this problem
  has occurred on several of them.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 15 08:16:08 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 41) (prog-if 
00 [VGA controller])
 Subsystem: Super Micro Computer Inc ASPEED Graphics Family [15d9:1b0e]
  InstallationDate: Installed on 2021-04-13 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Supermicro Super Server
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic 
root=UUID=9242ef3a-0904-41c6-8ee2-4c224bb71e1a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X11SCL-IF
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.5:bd10/05/2020:br5.13:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SCL-IF:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1919402] Re: Desktop icons are blurry at scale 200%

This bug was fixed in the package gnome-shell-extension-desktop-icons-ng
- 0.15.0-0ubuntu4

---
gnome-shell-extension-desktop-icons-ng (0.15.0-0ubuntu4) hirsute; urgency=medium

  * d/p/latest_upstream_translations.patch:
- Dropped - those translations are in LP now, so the patch has
  served its purpose.

  [ Daniel van Vugt ]
  * d/p/fileItem.js_Add_support_for_rendering_at_high_DPI_scales.patch:
- Cherry picked upstream merge request (LP: #1919402)

 -- Gunnar Hjalmarsson   Wed, 14 Apr 2021 16:28:04
+0200

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

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

Title:
  Desktop icons are blurry at scale 200%

Status in Gnome Shell Extension Desktop Icons Ng:
  Unknown
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Fix Released

Bug description:
  Desktop icons are blurry at scale 200%

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

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

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

2021-04-15 Thread baptx

Public bug reported:

Hello,

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

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

Thanks.

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

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

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

Status in firefox package in Ubuntu:
  New

Bug description:
  Hello,

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

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

  Thanks.

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

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

[Desktop-packages] [Bug 1924583] [NEW] ASPEED AST driver seems unstable in 20.04.2 LTS

You have been subscribed to a public bug:

I have had the screen go blank several times.  Each time that this
occurred, I was selecting the "Settings" item from the upper right
corner arrow.  Perhaps there are a lot of low level accesses that occur
when this menu item is selected that somehow locks up the ASPEED AST
driver or some other part of the display?  When this problem occurs, the
only way I have been able to recover is to power cycle the system.  The
info collected for this bug report was taken after rebooting the system.

I originally had a problem that the initial login screen did not display
(blank screen) but I came across the following that provided a solution
of disable Wayland:

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

I am not able to reproduce the problem at will.  I can usually access
the "Settings" without a problem.  However, each time the screen has
gone blank it was right after clicking on the "Settings" menu item.  I
have six identical machines (Supermicro SYS-5019C-FL) and this problem
has occurred on several of them.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-49-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 15 08:16:08 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 41) (prog-if 
00 [VGA controller])
   Subsystem: Super Micro Computer Inc ASPEED Graphics Family [15d9:1b0e]
InstallationDate: Installed on 2021-04-13 (1 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: Supermicro Super Server
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic 
root=UUID=9242ef3a-0904-41c6-8ee2-4c224bb71e1a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/05/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X11SCL-IF
dmi.board.vendor: Supermicro
dmi.board.version: 1.01
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.5:bd10/05/2020:br5.13:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SCL-IF:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Super Server
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu
-- 
ASPEED AST driver seems unstable in 20.04.2 LTS
https://bugs.launchpad.net/bugs/1924583
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 1922712] Re: add metric for new glibc hwcaps

Oh man, this is *late*. It's also quite a big change too - only
collecting new information, but still. But yeah, it's either now or in
21.10, so eh. If the desktop team +1's the PR and considers it 'safe' to
land, this has a +1 from the release team.

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

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

Bug description:
  FFe: We would like to collect that information with 21.04 to get a
  better view of supported hardware for the new hwcaps.  The risk should
  be minimal, only adding an extra flag, and the server side collecting
  the data can handle that, according to Didier.

  pull request at https://github.com/ubuntu/ubuntu-report/pull/34

  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 "" (empty), when trying to run
  ld-linux on a release with glibc (<< 2.33). The string should be "-"
  (dash) when not having any hwcaps mentioned.

  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 1922839] Re: Opening new tab in gnome-terminal launched from nautilus loses most environment variables

2021-04-15 Thread Iain Lane

I'll handle this, probably after Hirsute releases. Thanks!

** Changed in: gnome-terminal (Ubuntu Hirsute)
Assignee: (unassigned) => Iain Lane (laney)

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

Title:
Opening new tab in gnome-terminal launched from nautilus loses most
environment variables

Status in gnome-terminal package in Ubuntu:
New
Status in gnome-terminal source package in Hirsute:
New

Bug description:
[Impact]

If you launch gnome-terminal by right clicking a directory in
Nautilus, selecting "Open in Terminal", you get a fully functional
terminal window.

If you then press the new tab button, or ctrl-shift-t to open a new
terminal tab, you will find that most environment variables have
become unset, and you see the text:

To run a command as administrator (user "root"), use "sudo ".
See "man sudo_root" for details.

Comparing printenv between:

Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/
Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/

Most commands won't run in the new terminal tab, due to $HOME and
$USER not being set.

Note, if you launch gnome-terminal from gnome-shell or the dock, and
create a new tab, everything works perfectly. Is something wrong with
the Nautilus option for "Open in Terminal"?

[Testcase]

1. Launch Nautilus to home directory
2. Right click > "Open in Terminal"
3. Run "printenv" to see full list of env variables
4. Click new tab button, or ctrl-shift-t
5. Run "printenv" see the lack of env variables

I have a test package available in the below ppa:

https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test

The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
reverted.

If you install this package, environment variables will be set
correctly.

[Where problems could occur]

I think there is some risk with re-instating a commit which has been
reverted, and users could run into similar issues as found in the
upstream bug.

We do have some supporting evidence that the commit isn't too harmful,
since it is applied to Groovy currently, things work as intended
there, and users haven't complained about the issues in the upstream
bug applying to Groovy.

If a regression were to occur, then launching a new gnome-terminal or
opening a new tab could land the user with a terminal with little to
no environment variables set. A workaround will be to launch gnome-
terminal from gnome-shell overview.

[Other info]

Focal and Groovy have the following commit applied:

commit fd5ac772154426e2da5afd633b336414bca33be9
Author: Christian Persch
Date: Mon Mar 23 09:57:56 2020 +0100
Subject: screen: Use clean env when creating new tab
Link:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/fd5ac772154426e2da5afd633b336414bca33be9

This was then reverted in 3.38.1 due to the upstream bug:

https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253

The reverted commit is:

commit 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
Author: Christian Persch
Date: Thu Sep 17 17:10:47 2020 +0200
Subject: Revert "screen: Use clean env when creating new tab"
Link:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac

This revert seems to have broken Hirsute. If we revert the revert,
that is, apply the commit again, things work as intended.

To fix this, we need to re-apply
fd5ac772154426e2da5afd633b336414bca33be9.

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

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

[Desktop-packages] [Bug 1923090] Re: autopkgtest fails in hirsute on armhf

** Merge proposal linked:
   https://code.launchpad.net/~rbalint/britney/+git/hints-ubuntu/+merge/401228

-- 
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:
  Fix Committed

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=GB=1=srp=en=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 1918985] Re: Xorg crashed with SIGABRT (caught SIGSEGV) in libinput_device_config_send_events_get_modes(device=NULL) from LibinputApplyConfig() from LibinputSetProperty() from

2021-04-15 Thread Iain Lane

thanks. Timo, could you SRU this one please?

** Also affects: xserver-xorg-input-libinput (Ubuntu Hirsute)
   Importance: High
   Status: Triaged

** Changed in: xserver-xorg-input-libinput (Ubuntu Hirsute)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Tags removed: rls-hh-incoming

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

Title:
  Xorg crashed with SIGABRT (caught SIGSEGV) in
  libinput_device_config_send_events_get_modes(device=NULL) from
  LibinputApplyConfig() from LibinputSetProperty() from
  XIChangeDeviceProperty()

Status in xserver-xorg-input-libinput:
  Unknown
Status in xserver-xorg-input-libinput package in Ubuntu:
  Triaged
Status in xserver-xorg-input-libinput source package in Hirsute:
  Triaged

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

  ---

  W: Fehlschlag beim Holen von 
http://de.archive.ubuntu.com/ubuntu/dists/hirsute/InRelease Verbindung 
fehlgeschlagen [IP: 141.30.62.24 80]
  W: Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden 
ignoriert oder alte an ihrer Stelle benutzt.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: xserver-xorg-core 2:1.20.10-3ubuntu3
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  BootLog:
    Fr Mär 12 12:21:23 CET 2021 
    Fr Mär 12 22:40:02 CET 2021 
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  Date: Fri Mar 12 23:05:07 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 460.39, 5.10.0-14-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) 
[103c:850d]
  InstallationDate: Installed on 2020-12-17 (85 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0408:5300 Quanta Computer, Inc. HP Wide Vision HD 
Camera
   Bus 001 Device 002: ID 1d57:fa60 Xenta 2.4G Wireless Mouse
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible 15-cn1xxx
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/126/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty 
-novtswitch -verbose 3
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic 
root=UUID=826c1aaa-9eb3-447b-aede-b8f0b5ef3ee2 ro recovery nomodeset 
dis_ucode_ldr
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   System ()
   ()
   ()
   ()
    () at /lib/x86_64-linux-gnu/libpthread.so.0
  Title: Xorg crashed with SIGABRT in System()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  dmi.bios.date: 11/16/2020
  dmi.bios.release: 15.24
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 850D
  dmi.board.vendor: HP
  dmi.board.version: 70.76
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 70.76
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd11/16/2020:br15.24:efr70.76:svnHP:pnHPENVYx360Convertible15-cn1xxx:pvrType1ProductConfigId:rvnHP:rn850D:rvr70.76:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-cn1xxx
  dmi.product.sku: 5WA69EA#ABD
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.4-1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.3.4-1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-input-libinput/+bug/1918985/+subscriptions

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

[Desktop-packages] [Bug 1921405] Re: preseeded snaps prevent installing chromium-browser deb2snap in chroot, again

2021-04-15 Thread Ken VanDine

Please followup with @osomon if this is reproduced.

** Tags removed: rls-hh-incoming

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

Title:
  preseeded snaps prevent installing chromium-browser deb2snap in
  chroot, again

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  preseeded snaps prevent installing chromium-browser deb2snap in
  chroot, again

  potentially https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1882232 regressed since preseeded snaps landed in focal
  desktop.

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

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

[Desktop-packages] [Bug 1922839] Re: Opening new tab in gnome-terminal launched from nautilus loses most environment variables

2021-04-15 Thread Ken VanDine

** Tags removed: rls-hh-incoming

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

Title:
Opening new tab in gnome-terminal launched from nautilus loses most
environment variables

Status in gnome-terminal package in Ubuntu:
New
Status in gnome-terminal source package in Hirsute:
New

Bug description:
[Impact]

If you launch gnome-terminal by right clicking a directory in
Nautilus, selecting "Open in Terminal", you get a fully functional
terminal window.

If you then press the new tab button, or ctrl-shift-t to open a new
terminal tab, you will find that most environment variables have
become unset, and you see the text:

To run a command as administrator (user "root"), use "sudo ".
See "man sudo_root" for details.

Comparing printenv between:

Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/
Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/

Most commands won't run in the new terminal tab, due to $HOME and
$USER not being set.

Note, if you launch gnome-terminal from gnome-shell or the dock, and
create a new tab, everything works perfectly. Is something wrong with
the Nautilus option for "Open in Terminal"?

[Testcase]

I have a test package available in the below ppa:

https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test

The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
reverted.

If you install this package, environment variables will be set
correctly.

[Where problems could occur]

I think there is some risk with re-instating a commit which has been
reverted, and users could run into similar issues as found in the
upstream bug.

[Other info]

Focal and Groovy have the following commit applied:

This was then reverted in 3.38.1 due to the upstream bug:

https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253

The reverted commit is:

This revert seems to have broken Hirsute. If we revert the revert,
that is, apply the commit again, things work as intended.

To fix this, we need to re-apply
fd5ac772154426e2da5afd633b336414bca33be9.

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

[Desktop-packages] [Bug 1890924] Re: Location services work with location services off, 20.04

2021-04-15 Thread Iain Lane

(sorry, just noticed I didn't assign this last week when I was supposed
to)

** Changed in: geoclue-2.0 (Ubuntu Focal)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  Location services work with location services off, 20.04

Status in geoclue-2.0 package in Ubuntu:
  Fix Released
Status in geoclue-2.0 source package in Focal:
  Triaged
Status in geoclue-2.0 source package in Groovy:
  Won't Fix

Bug description:
  * Impact

  Disabling the location service in settings isn't reflection on
  traditional deb applications

  * Test case

  - Log in an Ubuntu desktop session
  - install geoclue-2-demo
  - go to gnome-control-center, privacy, location and ensure the service is 
disabled
  - $ /usr/libexec/geoclue-2.0/demos/where-am-i

  the script should return a permission error and not a location

  * Regression potential

  [racb] Users who are currently relying on a working location service
  despite having a setting disabling it will find that the location
  service will stop working because the setting will start to be
  honoured.

  The change is in the client library, try a few applications, deb and
  snap or flatpak and make sure the status is correct respected

  -

  Not sure if this is the right package, but in the privacy -> location
  settings, in 18.04 I had to have my application be approved by user to
  access location with Geoclue. Now it seems this is working without the
  location services "enabled"??

  My application is repeater-START: https://sourceforge.net/projects
  /repeater-start/

  Steps to see issue:
  1) install Repeater-START and click the locate me button circle to the left. 
It goes to your rough location on map.

  2) Go to settings, privacy, location, note that location is turned
  off!?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-settings-daemon 3.36.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Aug  8 19:38:12 2020
  InstallationDate: Installed on 2017-07-29 (1106 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to focal on 2020-06-22 (47 days ago)

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

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

[Desktop-packages] [Bug 1922772] Re: Overview search causes the workarea to reshape, desktop-icons-ng to restart and the new window to lose focus

2021-04-15 Thread Ken VanDine

** Tags removed: rls-hh-incoming

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

Title:
  Overview search causes the workarea to reshape, desktop-icons-ng to
  restart and the new window to lose focus

Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Release: Ubuntu 21.04 (20210406 iso image)

  Software, version: gnome-shell, 3.38.4-1ubuntu1

  How to reproduce:
  1) Boot up Ubuntu 21.04 image (live session or installed)
  2) Once inside shell, go to overview (either using Super key or clicking on 
Activities)
  3) Search for any application (eg., terminal) and launch it.

  Expected:
  The application launches normally and usable.

  Actual:
  The application launches but the window looses focus. When the application is 
launching, the desktop icons disappear for few seconds and reappear. When they 
reappear the launched application window will not have focus.

  If we launch the application from the app grid (without searching
  first) or from the dock, the window retains the focus.

  Tested on VM (quickemu and virt-manager).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  6 22:14:04 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-04-06 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210405)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  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/1922772/+subscriptions

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

[Desktop-packages] [Bug 1923090] Re: autopkgtest fails in hirsute on armhf

** 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/1923090

Title:
  autopkgtest fails in hirsute on armhf

Status in firefox package in Ubuntu:
  Fix Committed

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=GB=1=srp=en=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 1923090] Re: autopkgtest fails in hirsute on armhf

2021-04-15 Thread Olivier Tilloy

Tentative fix:
https://bazaar.launchpad.net/~mozillateam/firefox/firefox.hirsute/revision/1484.

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

-- 
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:
  Fix Committed

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=GB=1=srp=en=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 1905370] Re: Qt-based tray icons not displayed on start-up

2021-04-15 Thread Sushenjit Bandyopadhyay

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

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

Title:
  Qt-based tray icons not displayed on start-up

Status in Ubuntu AppIndicators:
  Unknown
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Focal:
  Fix Committed
Status in gnome-shell-extension-appindicator source package in Groovy:
  Won't Fix
Status in gnome-shell-extension-appindicator source package in Hirsute:
  Fix Released

Bug description:
  [ Impact ]

  My system version is 20.10. I upgraded from 20.04. I found such a
  problem, the tray icon cannot be displayed when the system is turned
  on or restarted, but if I kill the process and restart it, it will be
  fine.

  I searched on Google and didn't see a similar problem.This is my
  hardware configuration:

  CPU: Two Intel® Xeon(R) CPU E5-2680 v4 @ 2.40GHz × 56
  GPU: NVIDIA Corporation GP106 [P106-100] / NVIDIA Corporation GP106 
[GeForce 1060]

  https://i.stack.imgur.com/ybiVj.png

  [  Test case ]

  - Install a Qt app with a tray icon that should show on startup
  - At login the icon should be visible.

  An example is hp-systray, from the package hplip-gui:
   - Add it to the autostart (if you don't have HP printers just add the command
     `hp-systray -x`).

  Expect the icon to show

  [ Regression Potential ]

  No status icon service is ever initialized by the shell and so no app
  indicator is visible.

  

  ProblemType: BugDistroRelease: Ubuntu 20.10
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14
  Uname: Linux 5.8.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 24 16:34:31 2020
  InstallationDate: Installed on 2020-10-24 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs:
   gnome-shell
   linux-image-5.8.0-29-generic
   linux-baseSourcePackage: meta-gnome3
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (29 days ago)

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

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

[Desktop-packages] [Bug 1905370] Re: Qt-based tray icons not displayed on start-up

2021-04-15 Thread Sushenjit Bandyopadhyay

I tested the version 33.1-0ubuntu0.20.04.2 from focal-proposed. It
works!

HP System trey service starts as expected at login. Does not popup the
error message.

When Zoom is started at startup the Zoom app indicator icon is visible
and it works as expected.

Thanks!

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

Title:
  Qt-based tray icons not displayed on start-up

Status in Ubuntu AppIndicators:
  Unknown
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Focal:
  Fix Committed
Status in gnome-shell-extension-appindicator source package in Groovy:
  Won't Fix
Status in gnome-shell-extension-appindicator source package in Hirsute:
  Fix Released

Bug description:
  [ Impact ]

  My system version is 20.10. I upgraded from 20.04. I found such a
  problem, the tray icon cannot be displayed when the system is turned
  on or restarted, but if I kill the process and restart it, it will be
  fine.

  I searched on Google and didn't see a similar problem.This is my
  hardware configuration:

  CPU: Two Intel® Xeon(R) CPU E5-2680 v4 @ 2.40GHz × 56
  GPU: NVIDIA Corporation GP106 [P106-100] / NVIDIA Corporation GP106 
[GeForce 1060]

  https://i.stack.imgur.com/ybiVj.png

  [  Test case ]

  - Install a Qt app with a tray icon that should show on startup
  - At login the icon should be visible.

  An example is hp-systray, from the package hplip-gui:
   - Add it to the autostart (if you don't have HP printers just add the command
     `hp-systray -x`).

  Expect the icon to show

  [ Regression Potential ]

  No status icon service is ever initialized by the shell and so no app
  indicator is visible.

  

  ProblemType: BugDistroRelease: Ubuntu 20.10
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14
  Uname: Linux 5.8.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 24 16:34:31 2020
  InstallationDate: Installed on 2020-10-24 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs:
   gnome-shell
   linux-image-5.8.0-29-generic
   linux-baseSourcePackage: meta-gnome3
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (29 days ago)

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

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

[Desktop-packages] [Bug 1924550] [NEW] High CPU from gnome-shell with high errors for recvmsg

2021-04-15 Thread Kareem

Public bug reported:

I am getting high CPU from gnome-shell and I can't track down whats
causing the issue.


$ strace: Process 2793 detached
% time seconds  usecs/call callserrors syscall
-- --- --- - - 
 38.270.047677   1 26640 13464 recvmsg
 35.760.044550   1 26406   poll
 25.770.032103   2 13191   writev
  0.080.000100   237   write
  0.050.68   0   144   mprotect
  0.040.44   06052 stat
  0.010.18   022 3 futex
  0.010.13   072   getpid
  0.000.06   023   read
  0.000.03   3 1   sendmsg
  0.000.00   0 3   mmap
  0.000.00   0 2   munmap
  0.000.00   086   ioctl
-- --- --- - - 
100.000.124582 66687 13519 total

$ sudo strace -p 2793 -e trace=recvmsg
recvmsg(19, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
recvmsg(19, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="\34\0J\356\7\0`\0\301\1\0\0\32\344HM\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
 iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(19, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
recvmsg(19, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="\34\0K\356\7\0`\0\301\1\0\0\32\344HM\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
 iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(19, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
recvmsg(19, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="\34\0L\356\7\0`\0\301\1\0\0\33\344HM\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
 iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 32

$ ls -al /proc/2793/fd/19
lrwx-- 1   64 Apr 15 09:07 /proc/2793/fd/19 -> 
'socket:[59892]'

lsof |grep 59892
lsof: WARNING: can't stat() nsfs file system /run/docker/netns/11c4a1f5359b
  Output information may be incomplete.
lsof: WARNING: can't stat() nsfs file system /run/docker/netns/d603ef1fe841
  Output information may be incomplete.
lsof: WARNING: can't stat() nsfs file system /run/docker/netns/a9c329decb40
  Output information may be incomplete.
gnome-she279319u unix 
0x   0t0  59892 type=STREAM
gnome-she27932802 gmain  19u unix 
0x   0t0  59892 type=STREAM
gnome-she27932805 gdbus  19u unix 
0x   0t0  59892 type=STREAM
gnome-she27932806 dconf\x20  19u unix 
0x   0t0  59892 type=STREAM
gnome-she27932808 gnome-s:d  19u unix 
0x   0t0  59892 type=STREAM
gnome-she27932809 gnome-s:d  19u unix 
0x   0t0  59892 type=STREAM
gnome-she27932810 gnome-s:d  19u unix 
0x   0t0  59892 type=STREAM
gnome-she27932811 gnome-s:d  19u unix 
0x   0t0  59892 type=STREAM
gnome-she27932813 JS\x20Hel  19u unix 
0x   0t0  59892 type=STREAM
gnome-she27932814 JS\x20Hel  19u unix 
0x   0t0  59892 type=STREAM
gnome-she27932815 JS\x20Hel  19u unix 
0x   0t0  59892 type=STREAM
gnome-she27932816 JS\x20Hel  19u unix 
0x   0t0  59892 type=STREAM
gnome-she27932817 JS\x20Hel  19u unix 
0x   0t0  59892 type=STREAM
gnome-she27932818 JS\x20Hel  19u unix 
0x   0t0  59892 type=STREAM
gnome-she27932819 JS\x20Hel  19u unix 
0x   0t0  59892 type=STREAM
gnome-she27932820 JS\x20Hel  19u unix 
0x   0t0  59892 type=STREAM
gnome-she27935764 threaded-  19u unix 
0x   0t0  59892 type=STREAM

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
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 15 08:53:43 2021
DisplayManager: gdm3
InstallationDate: Installed on 2021-02-05 (68 days ago)
InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=

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

2021-04-15 Thread Pratyush Ranjan

@Manu 
Can you please attach the error_log too. It is located in the var/log/cups 
directory.
Please make sure to enable the log level to debug or debug2 before uploading. 
You can get an idea about how to do it in the following link:- 
https://www.thegeekdiary.com/how-to-enable-cups-debugging-on-centos-rhel/

Also if possible then try to separate the error logs of different print
jobs. For example you can send the print job first for test12.pdf and
then copy from the error_log and then you can erase that log and can
send a print job again for test48.pdf(which causes significant RAM
usage.) and then copy the new error log.

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

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

Status in cups-filters package in Ubuntu:
  Confirmed

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

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

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

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

  Please let me know if you need more information.

  ## Further info:

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

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

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

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

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

  
  ## Trying to debug with cupsfilter:

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

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

  The latter uses gstoraster:

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

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

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

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

[Desktop-packages] [Bug 1917010] Re: Hard to detect double-clicks on the HiDPI touchscreen system

2021-04-15 Thread Kai-Heng Feng

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

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

Title:
  Hard to detect double-clicks on the HiDPI touchscreen system

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

Bug description:
  Double-clicks touchscreen on HiDPI system, sometime it will not be detected.
  Here is a related patch on upstream
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1487

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

-- 
Mailing list: https://launchpad.net/~desktop-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: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

2021-04-15 Thread jeremyszu

Hi Daniel,

Thank you for sharing.
We are not allow to provide a customization as workaround before we know the 
fix plan.

I reported an upstream issue:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/194

-- 
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:
  [radeon] Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  In Progress
Status in xorg-server 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: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

2021-04-15 Thread jeremyszu

Hi Daniel,

Thank you for sharing.
OEM team is not allow the provide a customization as workaround before we don't 
know the plan to fix.

I reported an issue as 
https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/194

** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues 
#194
   https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/194

-- 
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:
  [radeon] Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  In Progress
Status in xorg-server 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 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)

2021-04-15 Thread Jeff Francus

I noticed this issue with Kubuntu (Plasma) host and Ubuntu (GNOME)
guest.

I thought I was the only one affected since this makes almost impossible
to use VMs with GUI (desktop). Not that you wouldn't be able to run them
but that you realize that you use Ctrl+c/Ctrl+v so often that when it
doesn't work 100% it sooo bad experience that you rather not to use VMs
at all. And VirtualBox is not an answer ;-).

Btw. Windows 10 guest is all right.

Thank you Christian for asking and investigating.

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

Title:
  Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM
  guests)

Status in qemu package in Ubuntu:
  Invalid
Status in spice package in Ubuntu:
  Invalid
Status in spice-gtk package in Ubuntu:
  Fix Released
Status in spice-protocol package in Ubuntu:
  Fix Released
Status in spice-vdagent package in Ubuntu:
  Fix Released
Status in virt-manager package in Ubuntu:
  Invalid
Status in spice-gtk source package in Focal:
  Triaged
Status in spice-protocol source package in Focal:
  Triaged
Status in spice-vdagent source package in Focal:
  Invalid
Status in spice-vdagent package in Debian:
  Fix Released
Status in spice package in Fedora:
  Unknown

Bug description:
  https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9

  ---

  I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta.

  I installed Kubuntu 20.04 and virt-manager as I did many times on
  Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt,
  libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest
  or with Ubuntu 20.04 guest then clipboard doesn't work right.

  To test it, please install Kubuntu 20.04 and then install Kubuntu /
  Ubuntu 20.04 as VM (guest). Open some simple text editor and start
  Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of
  time it won't.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: virt-manager 1:2.2.1-3ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 13 15:02:22 2020
  InstallationDate: Installed on 2020-04-09 (4 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  PackageArchitecture: all
  SourcePackage: virt-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1924282] [NEW] /etc/hp is empty after installing hplip package - 20.04LTS

2021-04-15 Thread Allan W. Macdonald

Public bug reported:

After upgrading to 20.04LTS, my HP-LaserJet 1018 printer stopped printing.  
Looking at the logs, I found the following errors:
E [04/Apr/2021:12:12:55] common/utils.c 177: validate_plugin_version() Plugin 
version[3.17.10] mismatch with HPLIP version[3.20.3]
E [04/Apr/2021:12:12:55] common/utils.c 210: Plugin version is not matching

I tried completely purging and re-installing the hplip package and the
problem still exists.

I then tried installing the correct plugin - here is what happened:

*
$ sudo apt update
Hit:1 http://ca.archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://ca.archive.ubuntu.com/ubuntu focal-updates InRelease   
Hit:3 http://ca.archive.ubuntu.com/ubuntu focal-backports InRelease 
Get:4 http://ppa.launchpad.net/system76-dev/stable/ubuntu focal InRelease [17.5 
kB]
Hit:5 http://security.ubuntu.com/ubuntu focal-security InRelease
Fetched 17.5 kB in 1s (22.0 kB/s)
Reading package lists... Done
Building dependency tree   
Reading state information... Done
All packages are up to date.
$ sudo apt install hplip --reinstall
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 204 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 hplip amd64 
3.20.3+dfsg0-2 [204 kB]
Fetched 204 kB in 0s (781 kB/s)
(Reading database ... 303799 files and directories currently installed.)
Preparing to unpack .../hplip_3.20.3+dfsg0-2_amd64.deb ...
Unpacking hplip (3.20.3+dfsg0-2) over (3.20.3+dfsg0-2) ...
Setting up hplip (3.20.3+dfsg0-2) ...
Creating/updating hplip user account...
Can't open /etc/hp/hplip.conf: No such file or directory.
Can't open /etc/hp/hplip.conf: No such file or directory.
Processing triggers for dbus (1.12.16-2ubuntu2.1) ...
Processing triggers for man-db (2.9.1-1) ...
$ wget https://developers.hp.com/sites/default/files/hplip-3.20.3-plugin.run
--2021-04-15 08:51:22--  
https://developers.hp.com/sites/default/files/hplip-3.20.3-plugin.run
Resolving developers.hp.com (developers.hp.com)... 35.167.236.162, 34.210.182.99
Connecting to developers.hp.com (developers.hp.com)|35.167.236.162|:443... 
connected.
HTTP request sent, awaiting response... 200 OK
Length: 11514166 (11M)
Saving to: ‘hplip-3.20.3-plugin.run.2’

hplip-3.20.3-plugin 100%[===>]  10.98M  8.32MB/sin
1.3s

2021-04-15 08:51:24 (8.32 MB/s) - ‘hplip-3.20.3-plugin.run.2’ saved
[11514166/11514166]

$ sh hplip-3.20.3-plugin.run
Verifying archive integrity... All good.
Uncompressing HPLIP 3.20.3 Plugin Self Extracting 
Archive..
Error setting home directory: /etc/hp/hplip.conf not found. Is HPLIP installed?
$
*

I looked in the directory /etc/hp and it was indeed empty!

See this question for more info:
https://answers.launchpad.net/hplip/+question/696517

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


** Tags: installation missing-files

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

Title:
  /etc/hp is empty after installing hplip package - 20.04LTS

Status in hplip package in Ubuntu:
  New

Bug description:
  After upgrading to 20.04LTS, my HP-LaserJet 1018 printer stopped printing.  
Looking at the logs, I found the following errors:
  E [04/Apr/2021:12:12:55] common/utils.c 177: validate_plugin_version() Plugin 
version[3.17.10] mismatch with HPLIP version[3.20.3]
  E [04/Apr/2021:12:12:55] common/utils.c 210: Plugin version is not matching

  I tried completely purging and re-installing the hplip package and the
  problem still exists.

  I then tried installing the correct plugin - here is what happened:

  
*
  $ sudo apt update
  Hit:1 http://ca.archive.ubuntu.com/ubuntu focal InRelease
  Hit:2 http://ca.archive.ubuntu.com/ubuntu focal-updates InRelease   
  Hit:3 http://ca.archive.ubuntu.com/ubuntu focal-backports InRelease 
  Get:4 http://ppa.launchpad.net/system76-dev/stable/ubuntu focal InRelease 
[17.5 kB]
  Hit:5 http://security.ubuntu.com/ubuntu focal-security InRelease
  Fetched 17.5 kB in 1s (22.0 kB/s)
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  All packages are up to date.
  $ sudo apt install hplip --reinstall
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 upgraded, 0 newly

[Desktop-packages] [Bug 1923090] Re: autopkgtest fails in hirsute on armhf

2021-04-15 Thread Olivier Tilloy

That token in the UA string corresponds to the machine field of the
result of the uname syscall (== `uname -m`).

-- 
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=GB=1=srp=en=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 1921991] Re: [SRU] Support isdv4-aes stylus group and multiple AES stylus definitions

2021-04-15 Thread Bin Li

@seb128,

 Thanks a lot!

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

Title:
  [SRU] Support isdv4-aes stylus group and multiple AES stylus
  definitions

Status in OEM Priority Project:
  Triaged
Status in libwacom package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * There are lots of stylus couldn't be used on Lenovo's platform, our
  OEM customer request to support ThinkPad P15 Gen 1, ThinkPad X1 Yoga
  Gen5, ThinkPad P1 G3.

   * I reviewed and tested the below patches from upstream. It could
  support the stylus very well on P15, P1 or X1 Yoga.

   * a864679 - Add multiple AES stylus definitions 
     I applied into libwacom2 1.3-2ubuntu1, no errors.

   * 8652aa3 - Add isdv4-aes stylus group to all AES sensors
    I tried to apply this patch, but there are not 'data/isdv4-48ca.tablet' and 
'data/isdv4-48ce.tablet', it failed for these two files.

   * ba02abf - Add ISDv4 51e9 (Lenovo ThinkPad P15 Gen 1) (#325)

  [Test Plan]

   * Need your laptop have AES stylus, check the pen setting at gnome-
  control-center when the pen touch the screen. It could not
  set/customize the stylus, such as the second button as right click.

   * After updated the new packages with these patches, you could
  customize the stylus at gnome-control-center.

  [Where problems could occur]

   * It only changes the data/ parts to support more stylus from
  upstream, so it's low risk.

  [Other Info]

   * Related bug:
  https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1869059

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

-- 
Mailing list: https://launchpad.net/~desktop-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: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

Anyway, for this bug my thinking is that if a different config satisfies
the OEM then that can be considered as a semipermanent workaround.

Other than that, it looks like the bug needs to be reported upstream to
https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati

-- 
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:
  [radeon] Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  In Progress
Status in xorg-server 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: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

Good point. Running 'man amdgpu' I can immediately see one such good
reason:

  Option "TearFree" "boolean"

-- 
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:
  [radeon] Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  In Progress
Status in xorg-server 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 1906684] Update Released

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to 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 1897784] Re: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Re

This bug was fixed in the package libreoffice - 1:6.4.7-0ubuntu0.20.04.1

---
libreoffice (1:6.4.7-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #1906684)
  * Move libreoffice-sdbc-hsqldb to Recommends (LP: #1916786)
  * Fix Calc crash in ScSelectionTransferObj (LP: #1897784)

 -- Rico Tzschichholz   Mon, 15 Mar 2021 19:12:01
+0100

** 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/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 Released
Status in libreoffice source package in Groovy:
  Fix Released

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 1897784] Re: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Re

Focal verified via LP: #1906684.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to 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 Released
Status in libreoffice source package in Groovy:
  Fix Released

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 1916786] Re: weak dependency to libreoffice-sdbc-hsqldb

Focal verified via LP: #1906684.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to 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 Released
Status in libreoffice source package in Groovy:
  Fix Released

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 1916786] Re: weak dependency to libreoffice-sdbc-hsqldb

This bug was fixed in the package libreoffice - 1:6.4.7-0ubuntu0.20.04.1

---
libreoffice (1:6.4.7-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #1906684)
  * Move libreoffice-sdbc-hsqldb to Recommends (LP: #1916786)
  * Fix Calc crash in ScSelectionTransferObj (LP: #1897784)

 -- Rico Tzschichholz   Mon, 15 Mar 2021 19:12:01
+0100

** 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/1916786

Title:
  weak dependency to libreoffice-sdbc-hsqldb

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

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 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)

2021-04-15 Thread Timo Aaltonen

because the native drivers have features that modesetting_drv does not
have, and how AMD expects them to be used

-- 
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:
  [radeon] Display output laggy from iGPU when operating on desktop with
  attaching AMD R7 430 graphic (dGPU)

Status in OEM Priority Project:
  In Progress
Status in xorg-server 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 1924251] [NEW] Embedded browser display corruption under Wayland on Pi desktop

2021-04-15 Thread Dave Jones

Public bug reported:

On the hirsute Pi desktop, under a wayland session with the "full" KMS
overlay enabled, and "kms-modifiers" present in the org.gnome.mutter
/experimental-features, the body of a window containing an HTML renderer
(e.g. help text or a login page) displays corruption.

These reproduction cases may not be entirely reliable given that *some*
pages appear to render correctly, but I'll include a couple in the hopes
of making it reliably reproducible:

1. Open the Lights Off game
2. Select "Help" from the menu
3. In the help window that appears, select any link

"Basics", "Rules", and "Strategy" all reliably reproduce the issue for
me, but "Help Translate" doesn't so you may need to click around some
links until the corruption appears -- however, once it does even
navigating back to the prior page which rendered happily now displays
the same corruption.

Another reproduction case:

1. Open the Settings application
2. Select the Online Applications option from the left
3. Select the Google entry in the list
4. The login window that appears always displays corruption for me

The Microsoft option always reliably corrupts for me, but the Facebook
one doesn't so again I wonder how reproducible this may be for others
(might be worth trying several options if the first doesn't display
corruption).

The corruption appears in the form of "shredded" content as if a
horizontal stride is set incorrectly somewhere, but only appears in the
body of the window; the window decorations are unaffected. I'll attach a
screenshot of the corrupted help window to illustrate.

** Affects: mutter (Ubuntu)
Importance: Undecided
Assignee: Daniel van Vugt (vanvugt)
Status: New

** Tags: hirsute raspi raspi-gfx

** Attachment added: "Screenshot from 2021-04-15 10-07-46.png"

https://bugs.launchpad.net/bugs/1924251/+attachment/5488263/+files/Screenshot%20from%202021-04-15%2010-07-46.png

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

Title:
Embedded browser display corruption under Wayland on Pi desktop

Status in mutter package in Ubuntu:
New

Bug description:
On the hirsute Pi desktop, under a wayland session with the "full" KMS
overlay enabled, and "kms-modifiers" present in the org.gnome.mutter
/experimental-features, the body of a window containing an HTML
renderer (e.g. help text or a login page) displays corruption.

These reproduction cases may not be entirely reliable given that
*some* pages appear to render correctly, but I'll include a couple in
the hopes of making it reliably reproducible:

1. Open the Lights Off game
2. Select "Help" from the menu
3. In the help window that appears, select any link

Another reproduction case:

1. Open the Settings application
2. Select the Online Applications option from the left
3. Select the Google entry in the list
4. The login window that appears always displays corruption for me

The corruption appears in the form of "shredded" content as if a
horizontal stride is set incorrectly somewhere, but only appears in
the body of the window; the window decorations are unaffected. I'll
attach a screenshot of the corrupted help window to illustrate.

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

[Desktop-packages] [Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Tags added: hirsute raspi raspi-gfx

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

Title:
  Embedded browser display corruption under Wayland on Pi desktop

Status in mutter package in Ubuntu:
  New

Bug description:
  On the hirsute Pi desktop, under a wayland session with the "full" KMS
  overlay enabled, and "kms-modifiers" present in the org.gnome.mutter
  /experimental-features, the body of a window containing an HTML
  renderer (e.g. help text or a login page) displays corruption.

  These reproduction cases may not be entirely reliable given that
  *some* pages appear to render correctly, but I'll include a couple in
  the hopes of making it reliably reproducible:

  1. Open the Lights Off game
  2. Select "Help" from the menu
  3. In the help window that appears, select any link

  "Basics", "Rules", and "Strategy" all reliably reproduce the issue for
  me, but "Help Translate" doesn't so you may need to click around some
  links until the corruption appears -- however, once it does even
  navigating back to the prior page which rendered happily now displays
  the same corruption.

  Another reproduction case:

  1. Open the Settings application
  2. Select the Online Applications option from the left
  3. Select the Google entry in the list
  4. The login window that appears always displays corruption for me

  The Microsoft option always reliably corrupts for me, but the Facebook
  one doesn't so again I wonder how reproducible this may be for others
  (might be worth trying several options if the first doesn't display
  corruption).

  The corruption appears in the form of "shredded" content as if a
  horizontal stride is set incorrectly somewhere, but only appears in
  the body of the window; the window decorations are unaffected. I'll
  attach a screenshot of the corrupted help window to illustrate.

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

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

[Desktop-packages] [Bug 1785262] Re: arm64 autopkgtests are flaky

Groovy verified per LP: #1913353.

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

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

Title:
  arm64 autopkgtests are flaky

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Groovy:
  Fix Released

Bug description:
  [Verification and regression analysis is all handled via the main SRU
  bug of LP: #1913353]

  See http://autopkgtest.ubuntu.com/packages/libreoffice/cosmic/arm64.

  In the past 30 days, 8 out of 45 test runs failed. That a 18% failure
  rate. It would be good to understand if all those failures are
  similar, what's causing them, and if they can easily be made more
  robust.

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

-- 
Mailing list: https://launchpad.net/~desktop-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] Re: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Re

This bug was fixed in the package libreoffice - 1:7.0.5-0ubuntu0.20.10.1

---
libreoffice (1:7.0.5-0ubuntu0.20.10.1) groovy; urgency=medium

  * New upstream release (LP: #1913353)

  [ Rico Tzschichholz ]
  * Update yaru icon style "2021-01-31"
  * Move libreoffice-sdbc-hsqldb to Recommends (LP: #1916786)
  * Fix Calc crash in ScSelectionTransferObj (LP: #1897784)
  * Drop fix-bluez-external.diff and unowinreg-static-libgcc.diff,
applied upstream

  [ Heather Ellsworth ]
  * Add timeout to uicheck-sw test to allow it to handle timeouts under
load better (LP: #1785262)

libreoffice (1:7.0.4-3) unstable; urgency=medium

  * debian/tests/control.in: *really* add libreoffice-writer dependency
to uicheck-sc test

libreoffice (1:7.0.4-2) unstable; urgency=medium

  * debian/test/control: make uicheck-sc depend on libreoffice-writer, too
(the openDialogs/uno.Show:License Dialog test opens a new "Writer/Web"
document...)

libreoffice (1:7.0.4-1) unstable; urgency=medium

  * LibreOffice 7.0.4 final release (identical to rc2)

  * debian/patches/pdfium-m68k.diff: fix pdfium build on m68k

  * debian/rules, debian/control*in: s/noinsttests/noinsttest/, thanks
lintian
  * debian/rules:
- revert clang (>= 1:11) build-dep for buster-backports; doesn't exist in
  buster and we resort back to gcc
- don't rm LICENSE.html, it is used by
  Help -> License Information -> Show License
  * debian/control.mediawiki.in: remove Homepage: (closes: #978713)
  * debian/*.mime: stop quoting %s (closes: #950319)

libreoffice (1:7.0.4~rc2-1) unstable; urgency=medium

  * New upstream release candidate

libreoffice (1:7.0.4~rc1-1) unstable; urgency=medium

  * New upstream release candidate

  * debian/patches/unowinreg-static-libgcc.diff: use -static-libgcc, see
LO master commit 01241113947fc7bd7f7b765dd897bb023c8ca99c

  * debian/rules:
- set MYSQL_FLAVOUR=mariadb (as it's used anyway, and upstreams internal
  copy is mariadb-connector-c anyway) and build-depend on libmariadb-dev
  instead of libmariadbclient-dev-compat (closes: #975481)
- build-depend on clang (>= 1:11) on armel
- fix nocheck -b builds...
- use nowindows build profile for (not) building unowinreg
  * debian/rules, debian/control*in:
- honour noinsttests build profile for (not) building
  -subsequentcheckbase/-smoketest-test-data
  * debian/rules, debian/control*in:
- move unowinreg.dll into /usr/lib/i686-w64-mingw32 (the mingw g++
  compiler installs its .dlls into /usr/lib/gcc/i686-w64-mingw32)

 -- Rico Tzschichholz   Mon, 15 Mar 2021 19:01:12
+0100

** 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/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 Released

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 1897784] Update Released

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to 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 Released

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 1785262] Re: arm64 autopkgtests are flaky

This bug was fixed in the package libreoffice - 1:7.0.5-0ubuntu0.20.10.1

---
libreoffice (1:7.0.5-0ubuntu0.20.10.1) groovy; urgency=medium

  * New upstream release (LP: #1913353)

  [ Rico Tzschichholz ]
  * Update yaru icon style "2021-01-31"
  * Move libreoffice-sdbc-hsqldb to Recommends (LP: #1916786)
  * Fix Calc crash in ScSelectionTransferObj (LP: #1897784)
  * Drop fix-bluez-external.diff and unowinreg-static-libgcc.diff,
applied upstream

  [ Heather Ellsworth ]
  * Add timeout to uicheck-sw test to allow it to handle timeouts under
load better (LP: #1785262)

libreoffice (1:7.0.4-3) unstable; urgency=medium

  * debian/tests/control.in: *really* add libreoffice-writer dependency
to uicheck-sc test

libreoffice (1:7.0.4-2) unstable; urgency=medium

  * debian/test/control: make uicheck-sc depend on libreoffice-writer, too
(the openDialogs/uno.Show:License Dialog test opens a new "Writer/Web"
document...)

libreoffice (1:7.0.4-1) unstable; urgency=medium

  * LibreOffice 7.0.4 final release (identical to rc2)

  * debian/patches/pdfium-m68k.diff: fix pdfium build on m68k

  * debian/rules, debian/control*in: s/noinsttests/noinsttest/, thanks
lintian
  * debian/rules:
- revert clang (>= 1:11) build-dep for buster-backports; doesn't exist in
  buster and we resort back to gcc
- don't rm LICENSE.html, it is used by
  Help -> License Information -> Show License
  * debian/control.mediawiki.in: remove Homepage: (closes: #978713)
  * debian/*.mime: stop quoting %s (closes: #950319)

libreoffice (1:7.0.4~rc2-1) unstable; urgency=medium

  * New upstream release candidate

libreoffice (1:7.0.4~rc1-1) unstable; urgency=medium

  * New upstream release candidate

  * debian/patches/unowinreg-static-libgcc.diff: use -static-libgcc, see
LO master commit 01241113947fc7bd7f7b765dd897bb023c8ca99c

  * debian/rules:
- set MYSQL_FLAVOUR=mariadb (as it's used anyway, and upstreams internal
  copy is mariadb-connector-c anyway) and build-depend on libmariadb-dev
  instead of libmariadbclient-dev-compat (closes: #975481)
- build-depend on clang (>= 1:11) on armel
- fix nocheck -b builds...
- use nowindows build profile for (not) building unowinreg
  * debian/rules, debian/control*in:
- honour noinsttests build profile for (not) building
  -subsequentcheckbase/-smoketest-test-data
  * debian/rules, debian/control*in:
- move unowinreg.dll into /usr/lib/i686-w64-mingw32 (the mingw g++
  compiler installs its .dlls into /usr/lib/gcc/i686-w64-mingw32)

 -- Rico Tzschichholz   Mon, 15 Mar 2021 19:01:12
+0100

** 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/1785262

Title:
  arm64 autopkgtests are flaky

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Groovy:
  Fix Released

Bug description:
  [Verification and regression analysis is all handled via the main SRU
  bug of LP: #1913353]

  See http://autopkgtest.ubuntu.com/packages/libreoffice/cosmic/arm64.

  In the past 30 days, 8 out of 45 test runs failed. That a 18% failure
  rate. It would be good to understand if all those failures are
  similar, what's causing them, and if they can easily be made more
  robust.

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

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

[Desktop-packages] [Bug 1785262] Update Released

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

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

Title:
  arm64 autopkgtests are flaky

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Groovy:
  Fix Released

Bug description:
  [Verification and regression analysis is all handled via the main SRU
  bug of LP: #1913353]

  See http://autopkgtest.ubuntu.com/packages/libreoffice/cosmic/arm64.

  In the past 30 days, 8 out of 45 test runs failed. That a 18% failure
  rate. It would be good to understand if all those failures are
  similar, what's causing them, and if they can easily be made more
  robust.

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

-- 
Mailing list: https://launchpad.net/~desktop-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] Re: weak dependency to libreoffice-sdbc-hsqldb

This bug was fixed in the package libreoffice - 1:7.0.5-0ubuntu0.20.10.1

---
libreoffice (1:7.0.5-0ubuntu0.20.10.1) groovy; urgency=medium

  * New upstream release (LP: #1913353)

  [ Rico Tzschichholz ]
  * Update yaru icon style "2021-01-31"
  * Move libreoffice-sdbc-hsqldb to Recommends (LP: #1916786)
  * Fix Calc crash in ScSelectionTransferObj (LP: #1897784)
  * Drop fix-bluez-external.diff and unowinreg-static-libgcc.diff,
applied upstream

  [ Heather Ellsworth ]
  * Add timeout to uicheck-sw test to allow it to handle timeouts under
load better (LP: #1785262)

libreoffice (1:7.0.4-3) unstable; urgency=medium

  * debian/tests/control.in: *really* add libreoffice-writer dependency
to uicheck-sc test

libreoffice (1:7.0.4-2) unstable; urgency=medium

  * debian/test/control: make uicheck-sc depend on libreoffice-writer, too
(the openDialogs/uno.Show:License Dialog test opens a new "Writer/Web"
document...)

libreoffice (1:7.0.4-1) unstable; urgency=medium

  * LibreOffice 7.0.4 final release (identical to rc2)

  * debian/patches/pdfium-m68k.diff: fix pdfium build on m68k

  * debian/rules, debian/control*in: s/noinsttests/noinsttest/, thanks
lintian
  * debian/rules:
- revert clang (>= 1:11) build-dep for buster-backports; doesn't exist in
  buster and we resort back to gcc
- don't rm LICENSE.html, it is used by
  Help -> License Information -> Show License
  * debian/control.mediawiki.in: remove Homepage: (closes: #978713)
  * debian/*.mime: stop quoting %s (closes: #950319)

libreoffice (1:7.0.4~rc2-1) unstable; urgency=medium

  * New upstream release candidate

libreoffice (1:7.0.4~rc1-1) unstable; urgency=medium

  * New upstream release candidate

  * debian/patches/unowinreg-static-libgcc.diff: use -static-libgcc, see
LO master commit 01241113947fc7bd7f7b765dd897bb023c8ca99c

  * debian/rules:
- set MYSQL_FLAVOUR=mariadb (as it's used anyway, and upstreams internal
  copy is mariadb-connector-c anyway) and build-depend on libmariadb-dev
  instead of libmariadbclient-dev-compat (closes: #975481)
- build-depend on clang (>= 1:11) on armel
- fix nocheck -b builds...
- use nowindows build profile for (not) building unowinreg
  * debian/rules, debian/control*in:
- honour noinsttests build profile for (not) building
  -subsequentcheckbase/-smoketest-test-data
  * debian/rules, debian/control*in:
- move unowinreg.dll into /usr/lib/i686-w64-mingw32 (the mingw g++
  compiler installs its .dlls into /usr/lib/gcc/i686-w64-mingw32)

 -- Rico Tzschichholz   Mon, 15 Mar 2021 19:01:12
+0100

** 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/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 Released

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 1913353] Update Released

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to 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 1916786] Update Released

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to 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 Released

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 1897784] Re: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Re

Groovy verified per LP: #1913353.

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

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

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 1916786] Re: weak dependency to libreoffice-sdbc-hsqldb

Groovy verified per LP: #1913353.

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

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

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 1921991] Re: [SRU] Support isdv4-aes stylus group and multiple AES stylus definitions

Uploaded to focal

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

Title:
  [SRU] Support isdv4-aes stylus group and multiple AES stylus
  definitions

Status in OEM Priority Project:
  Triaged
Status in libwacom package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * There are lots of stylus couldn't be used on Lenovo's platform, our
  OEM customer request to support ThinkPad P15 Gen 1, ThinkPad X1 Yoga
  Gen5, ThinkPad P1 G3.

   * I reviewed and tested the below patches from upstream. It could
  support the stylus very well on P15, P1 or X1 Yoga.

   * a864679 - Add multiple AES stylus definitions 
     I applied into libwacom2 1.3-2ubuntu1, no errors.

   * 8652aa3 - Add isdv4-aes stylus group to all AES sensors
    I tried to apply this patch, but there are not 'data/isdv4-48ca.tablet' and 
'data/isdv4-48ce.tablet', it failed for these two files.

   * ba02abf - Add ISDv4 51e9 (Lenovo ThinkPad P15 Gen 1) (#325)

  [Test Plan]

   * Need your laptop have AES stylus, check the pen setting at gnome-
  control-center when the pen touch the screen. It could not
  set/customize the stylus, such as the second button as right click.

   * After updated the new packages with these patches, you could
  customize the stylus at gnome-control-center.

  [Where problems could occur]

   * It only changes the data/ parts to support more stylus from
  upstream, so it's low risk.

  [Other Info]

   * Related bug:
  https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1869059

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

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

[Desktop-packages] [Bug 1923841] Re: [SRU] Increase recording quality

2021-04-15 Thread Kai-Heng Feng

Yes we can skip groovy. Thanks!

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

Title:
  [SRU] Increase recording quality

Status in HWE Next:
  New
Status in alsa-utils package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]
  Audio gets recorded by "arecord" has really bad sound quality when the volume 
is low.

  [Fix]
  https://github.com/alsa-project/alsa-utils/pull/69
  Switch the default audio format from 8 bits to 16 bits if hardware supports 
it.

  [Test]
  1. Plug a microphone.
  2. Run `arecord | aplay` and say something to the microphone.
  3. Only noise can be heard.

  With the fix applied, the recording is clear.

  [Where problems could occur]
  If there's any hardware falsely advertised to support 16 bits, this change 
will break them.
  However, this is effectively using `arecord -f cd` or `arecord -f cdr`, so 
that's not likely.

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

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

[Desktop-packages] [Bug 1923841] Re: [SRU] Increase recording quality

Thanks, I've uploaded to focal and hirsute. Do you care about 20.10 at
this point? It feels like we could probably skip this one to spare some
verification work since it's about to be replaced by a new stable and
isn't a LTS

** Changed in: alsa-utils (Ubuntu)
   Importance: Undecided => Low

** Changed in: alsa-utils (Ubuntu)
   Status: New => Fix Committed

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

Title:
  [SRU] Increase recording quality

Status in HWE Next:
  New
Status in alsa-utils package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]
  Audio gets recorded by "arecord" has really bad sound quality when the volume 
is low.

  [Fix]
  https://github.com/alsa-project/alsa-utils/pull/69
  Switch the default audio format from 8 bits to 16 bits if hardware supports 
it.

  [Test]
  1. Plug a microphone.
  2. Run `arecord | aplay` and say something to the microphone.
  3. Only noise can be heard.

  With the fix applied, the recording is clear.

  [Where problems could occur]
  If there's any hardware falsely advertised to support 16 bits, this change 
will break them.
  However, this is effectively using `arecord -f cd` or `arecord -f cdr`, so 
that's not likely.

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

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

[Desktop-packages] [Bug 1923817] Re: The balsa/armhf tests are failing with the hirsute-proposed update

** Tags removed: update-excuse

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

Title:
  The balsa/armhf tests are failing with the hirsute-proposed update

Status in webkit2gtk package in Ubuntu:
  Triaged

Bug description:
  The update is failing the balsa tests for some reason.

  The failure can be reproduced on ubuntu/ubuntu-hirsute-daily-
  arm64-server-20201125-disk1.img small instance on canonistack

  $ autopkgtest-build-lxd images:ubuntu/hirsute/armhf
  $ autopkgtest --shell-fail --apt-pocket=proposed=src:webkit2gtk --apt-upgrade 
balsa -- lxd autopkgtest/ubuntu/hirsute/armhf

  starting the tests manually in the shell opened after failure it
  success though...

  Getting the balsa source and editing debian/tests/screenshot to add
  some debug output

  xvfb-run bash -c 'NO_AT_BRIDGE=1 balsa --check-mail & sleep 15 ;
  xwininfo -tree -root; xwd -root | gm convert - /tmp/debug.png; xwd
  -name balsa | gm convert - /tmp/lower.png; xwd -debug -name Balsa | gm
  convert - $workdir/current.png; killall balsa; wait %1; true'

  $ autopkgtest --shell-fail --apt-pocket=proposed=src:webkit2gtk --apt-
  upgrade . --no-built-binaries -- lxd autopkgtest/ubuntu/hirsute/armhf

  gives

  'working directory: /tmp/autopkgtest.Uzr6TF/screenshot-artifacts

  xwininfo: Window id: 0x50e (the root window) (has no name)

Root window id: 0x50e (the root window) (has no name)
Parent window id: 0x0 (none)
   1 child:
   0x21 "balsa": ("balsa" "Balsa")  10x10+10+10  +10+10

  X Error of failed request:  BadMatch (invalid parameter attributes)
Major opcode of failed request:  73 (X_GetImage)
Serial number of failed request:  22
Current serial number in output stream:  22
  gm convert: Improper image header (/tmp/gmea3yq0).
  xwd: error: No window with name Balsa exists!
  gm convert: Improper image header (/tmp/gmH5TBcq).
  gm compare: Request did not return an image.
  autopkgtest [09:50:24]: test screenshot: ---]
  autopkgtest [09:50:25]: test screenshot:  - - - - - - - - - - results - - - - 
- - - - - -
  screenshot   FAIL non-zero exit status 1
  '

  doing a ssh -X to the instance it seems to start the right dialog...

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

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

[Desktop-packages] [Bug 1923817] Re: The balsa/armhf tests are failing with the hirsute-proposed update

Seems it has to do with portals? The recent depends adding has been
reverted and now the test is successful?

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

** Changed in: webkit2gtk (Ubuntu)
   Importance: High => Low

** Changed in: webkit2gtk (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  The balsa/armhf tests are failing with the hirsute-proposed update

Status in webkit2gtk package in Ubuntu:
  Triaged

Bug description:
  The update is failing the balsa tests for some reason.

  The failure can be reproduced on ubuntu/ubuntu-hirsute-daily-
  arm64-server-20201125-disk1.img small instance on canonistack

  $ autopkgtest-build-lxd images:ubuntu/hirsute/armhf
  $ autopkgtest --shell-fail --apt-pocket=proposed=src:webkit2gtk --apt-upgrade 
balsa -- lxd autopkgtest/ubuntu/hirsute/armhf

  starting the tests manually in the shell opened after failure it
  success though...

  Getting the balsa source and editing debian/tests/screenshot to add
  some debug output

  xvfb-run bash -c 'NO_AT_BRIDGE=1 balsa --check-mail & sleep 15 ;
  xwininfo -tree -root; xwd -root | gm convert - /tmp/debug.png; xwd
  -name balsa | gm convert - /tmp/lower.png; xwd -debug -name Balsa | gm
  convert - $workdir/current.png; killall balsa; wait %1; true'

  $ autopkgtest --shell-fail --apt-pocket=proposed=src:webkit2gtk --apt-
  upgrade . --no-built-binaries -- lxd autopkgtest/ubuntu/hirsute/armhf

  gives

  'working directory: /tmp/autopkgtest.Uzr6TF/screenshot-artifacts

  xwininfo: Window id: 0x50e (the root window) (has no name)

Root window id: 0x50e (the root window) (has no name)
Parent window id: 0x0 (none)
   1 child:
   0x21 "balsa": ("balsa" "Balsa")  10x10+10+10  +10+10

  X Error of failed request:  BadMatch (invalid parameter attributes)
Major opcode of failed request:  73 (X_GetImage)
Serial number of failed request:  22
Current serial number in output stream:  22
  gm convert: Improper image header (/tmp/gmea3yq0).
  xwd: error: No window with name Balsa exists!
  gm convert: Improper image header (/tmp/gmH5TBcq).
  gm compare: Request did not return an image.
  autopkgtest [09:50:24]: test screenshot: ---]
  autopkgtest [09:50:25]: test screenshot:  - - - - - - - - - - results - - - - 
- - - - - -
  screenshot   FAIL non-zero exit status 1
  '

  doing a ssh -X to the instance it seems to start the right dialog...

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

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

[Desktop-packages] [Bug 1919924] Re: Scrolling on label doesn't work

2021-04-15 Thread Chris Halse Rogers

Hello Marco, or anyone else affected,

Accepted gnome-shell-extension-appindicator into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-
appindicator/33.1-0ubuntu0.20.04.2 in a few hours, and then in the
-proposed repository.

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

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

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

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

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

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

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

Title:
  Scrolling on label doesn't work

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

Bug description:
  [ Impact ]

  Scrolling on indicator label doesn't cause the scroll appindicator
  event to be emitted

  [ Test case ]

  Using the appindicator test tool:
   
https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js

  1. Run it with gjs
  2. Show a label
  3. Ensure that scroll events are printed in the terminal and that the icon is 
changed

  [ Regression potential ]

  Scroll events on icon doesn't work anymore

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

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

[Desktop-packages] [Bug 1919927] Re: Wrong (or no) signals are emitted when icons are added / removed

2021-04-15 Thread Chris Halse Rogers

Hello Marco, or anyone else affected,

Accepted gnome-shell-extension-appindicator into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-
appindicator/33.1-0ubuntu0.20.04.2 in a few hours, and then in the
-proposed repository.

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

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

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

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

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

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

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

Title:
  Wrong (or no) signals are emitted when icons are added / removed

Status in gnome-shell-extension-appindicator package in Ubuntu:
  In Progress
Status in gnome-shell-extension-appindicator source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  When adding and removing signals the indicators extension should emit signals 
following the protocol

https://www.freedesktop.org/wiki/Specifications/StatusNotifierItem/StatusNotifierWatcher/

  So we should emit the service name by default when known

  [ Test case ]

  Run
   dbus-monitor --session "interface='org.kde.StatusNotifierWatcher'"

  When an indicator is added, signals such as should be emitted:

  signal time=1616029764.911986 sender=:1.34490 -> destination=(null 
destination) serial=3905 path=/StatusNotifierWatcher; 
interface=org.kde.StatusNotifierWatcher; member=StatusNotifierItemRegistered
 string ":1.109/org/ayatana/NotificationItem/psensor"
  signal time=1616029764.928864 sender=:1.34490 -> destination=(null 
destination) serial=3991 path=/StatusNotifierWatcher; 
interface=org.kde.StatusNotifierWatcher; member=StatusNotifierItemRegistered
 string ":1.34459/StatusNotifierItem"
   
  When removed:
  signal time=1616033768.529066 sender=:1.34490 -> destination=(null 
destination) serial=8711 path=/StatusNotifierWatcher; 
interface=org.kde.StatusNotifierWatcher; member=StatusNotifierItemUnregistered
 string ":1.34649/StatusNotifierItem"

  Removed events should be also emitted when the extension is disabled
  via gnome-shell-extension-prefs

  [ Regression potential ]

  Some clients won't interpret the events correctly causing the
  indicator not to work as expected

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

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

[Desktop-packages] [Bug 1905370] Re: Qt-based tray icons not displayed on start-up

2021-04-15 Thread Chris Halse Rogers

Hello lizhiyuan, or anyone else affected,

Accepted gnome-shell-extension-appindicator into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-
appindicator/33.1-0ubuntu0.20.04.2 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal)
   Status: Confirmed => Fix Committed

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

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

Title:
  Qt-based tray icons not displayed on start-up

Status in Ubuntu AppIndicators:
  Unknown
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Focal:
  Fix Committed
Status in gnome-shell-extension-appindicator source package in Groovy:
  Won't Fix
Status in gnome-shell-extension-appindicator source package in Hirsute:
  Fix Released

Bug description:
  [ Impact ]

  My system version is 20.10. I upgraded from 20.04. I found such a
  problem, the tray icon cannot be displayed when the system is turned
  on or restarted, but if I kill the process and restart it, it will be
  fine.

  I searched on Google and didn't see a similar problem.This is my
  hardware configuration:

  CPU: Two Intel® Xeon(R) CPU E5-2680 v4 @ 2.40GHz × 56
  GPU: NVIDIA Corporation GP106 [P106-100] / NVIDIA Corporation GP106 
[GeForce 1060]

  https://i.stack.imgur.com/ybiVj.png

  [  Test case ]

  - Install a Qt app with a tray icon that should show on startup
  - At login the icon should be visible.

  An example is hp-systray, from the package hplip-gui:
   - Add it to the autostart (if you don't have HP printers just add the command
     `hp-systray -x`).

  Expect the icon to show

  [ Regression Potential ]

  No status icon service is ever initialized by the shell and so no app
  indicator is visible.

  

  ProblemType: BugDistroRelease: Ubuntu 20.10
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14
  Uname: Linux 5.8.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 24 16:34:31 2020
  InstallationDate: Installed on 2020-10-24 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs:
   gnome-shell
   linux-image-5.8.0-29-generic
   linux-baseSourcePackage: meta-gnome3
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (29 days ago)

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

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

[Desktop-packages] [Bug 1919093] Re: [ThinkPad P1 Gen 3 w/ Intel + Nvidia Quadro T2000] Desktop does not load after login - purple screen with mouse