date:20210413

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

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

** No longer affects: gnome-shell (Ubuntu)

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

Title:
  Settings App not opening on Primary Monitor

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

Bug description:
  After clean installation of Ubuntu 20.04 LTS I configured my second
  monitor and set it as my main monitor. When I change the monitor sides
  and change the primary monitor, the settings app is automatically
  moved to the laptop monitor (ie the current secondary monitor which
  was primary but is not now). Then every time I open the Settings app
  hereafter, it opens in the secondary monitor even if the pointer is on
  the primary.

  This only happens to the settings app, and I think because that is the
  only one open at the time of assigning primary monitor

  What was Expected:

  When opening Settings app - it should open on the monitor where the
  pointer is at.

  Thank You

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 26 10:21:37 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:390b]
  InstallationDate: Installed on 2021-03-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 80E5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=770e1fb5-b694-4671-97ac-165ef511ff61 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2015
  dmi.bios.release: 1.95
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0CN95WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo G50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-80
  dmi.ec.firmware.release: 1.95
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0CN95WW:bd08/03/2015:br1.95:efr1.95:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoG50-80:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80E5
  dmi.product.sku: LENOVO_MT_80E5_BU_idea_FM_Lenovo G50-80
  dmi.product.version: Lenovo G50-80
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1923431] Re: Chrome/Chromium is composited slower without "system title bar and borders"

** Description changed:

  Chrome/Chromium is composited slower without "system title bar and
  borders".
  
  I had a feeling I could see a difference on my 4K monitor and weak Intel
  GPU. Enabling "Use system title bar and borders" eliminated stutters and
  gave me a smoother experience. So now I've taken some measurements from
  gnome-shell (CLUTTER_SHOW_FPS=1) running Chromium, not stuttering but
  playing a smoothly rendered video:
  
  ---
  
  Xorg
  
  Use system title bar and borders ON:
  
  *** X11 screen frame timings over 1.0s: 59.96 FPS, average: 1.0ms, peak: 2.8ms
  *** X11 screen frame timings over 1.0s: 60.03 FPS, average: 0.9ms, peak: 2.4ms
  *** X11 screen frame timings over 1.0s: 59.99 FPS, average: 1.0ms, peak: 2.2ms
  *** X11 screen frame timings over 1.0s: 59.96 FPS, average: 1.3ms, peak: 2.9ms
  *** X11 screen frame timings over 1.0s: 59.99 FPS, average: 1.5ms, peak: 2.9ms
  
  Use system title bar and borders OFF:
  
  *** X11 screen frame timings over 1.0s: 56.92 FPS, average: 3.8ms, peak: 5.7ms
  *** X11 screen frame timings over 1.0s: 59.94 FPS, average: 3.9ms, peak: 5.5ms
  *** X11 screen frame timings over 1.0s: 60.11 FPS, average: 3.7ms, peak: 4.6ms
  *** X11 screen frame timings over 1.0s: 59.98 FPS, average: 3.8ms, peak: 4.8ms
  *** X11 screen frame timings over 1.0s: 60.00 FPS, average: 3.9ms, peak: 5.4ms
  
  ---
  
- Wayland
+ Xwayland
  
  Use system title bar and borders ON:
  
  *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 0.9ms, peak: 1.6ms
  *** DP-2 frame timings over 1.0s: 58.95 FPS, average: 1.2ms, peak: 2.0ms
  *** DP-2 frame timings over 1.0s: 60.02 FPS, average: 1.0ms, peak: 2.2ms
  *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 1.0ms, peak: 1.6ms
  *** DP-2 frame timings over 1.0s: 60.05 FPS, average: 1.0ms, peak: 1.7ms
  
  Use system title bar and borders OFF:
  
  *** DP-2 frame timings over 1.0s: 56.99 FPS, average: 1.4ms, peak: 2.9ms
  *** DP-2 frame timings over 1.0s: 58.98 FPS, average: 1.7ms, peak: 2.7ms
  *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 1.5ms, peak: 2.2ms
  *** DP-2 frame timings over 1.0s: 58.04 FPS, average: 1.5ms, peak: 2.6ms
  *** DP-2 frame timings over 1.0s: 59.99 FPS, average: 1.3ms, peak: 2.5ms

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

Title:
  Chrome/Chromium is composited slower without "system title bar and
  borders"

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chrome/Chromium is composited slower without "system title bar and
  borders".

  I had a feeling I could see a difference on my 4K monitor and weak
  Intel GPU. Enabling "Use system title bar and borders" eliminated
  stutters and gave me a smoother experience. So now I've taken some
  measurements from gnome-shell (CLUTTER_SHOW_FPS=1) running Chromium,
  not stuttering but playing a smoothly rendered video:

  ---

  Xorg

  Use system title bar and borders ON:

  *** X11 screen frame timings over 1.0s: 59.96 FPS, average: 1.0ms, peak: 2.8ms
  *** X11 screen frame timings over 1.0s: 60.03 FPS, average: 0.9ms, peak: 2.4ms
  *** X11 screen frame timings over 1.0s: 59.99 FPS, average: 1.0ms, peak: 2.2ms
  *** X11 screen frame timings over 1.0s: 59.96 FPS, average: 1.3ms, peak: 2.9ms
  *** X11 screen frame timings over 1.0s: 59.99 FPS, average: 1.5ms, peak: 2.9ms

  Use system title bar and borders OFF:

  *** X11 screen frame timings over 1.0s: 56.92 FPS, average: 3.8ms, peak: 5.7ms
  *** X11 screen frame timings over 1.0s: 59.94 FPS, average: 3.9ms, peak: 5.5ms
  *** X11 screen frame timings over 1.0s: 60.11 FPS, average: 3.7ms, peak: 4.6ms
  *** X11 screen frame timings over 1.0s: 59.98 FPS, average: 3.8ms, peak: 4.8ms
  *** X11 screen frame timings over 1.0s: 60.00 FPS, average: 3.9ms, peak: 5.4ms

  ---

  Xwayland

  Use system title bar and borders ON:

  *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 0.9ms, peak: 1.6ms
  *** DP-2 frame timings over 1.0s: 58.95 FPS, average: 1.2ms, peak: 2.0ms
  *** DP-2 frame timings over 1.0s: 60.02 FPS, average: 1.0ms, peak: 2.2ms
  *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 1.0ms, peak: 1.6ms
  *** DP-2 frame timings over 1.0s: 60.05 FPS, average: 1.0ms, peak: 1.7ms

  Use system title bar and borders OFF:

  *** DP-2 frame timings over 1.0s: 56.99 FPS, average: 1.4ms, peak: 2.9ms
  *** DP-2 frame timings over 1.0s: 58.98 FPS, average: 1.7ms, peak: 2.7ms
  *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 1.5ms, peak: 2.2ms
  *** DP-2 frame timings over 1.0s: 58.04 FPS, average: 1.5ms, peak: 2.6ms
  *** DP-2 frame timings over 1.0s: 59.99 FPS, average: 1.3ms, peak: 2.5ms

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

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

[Desktop-packages] [Bug 1921931] Re: Opening links results in "Firefox is already running, but is not responding"

2021-04-13 Thread Launchpad Bug Tracker

This bug was fixed in the package firefox - 87.0+build3-0ubuntu4

---
firefox (87.0+build3-0ubuntu4) hirsute; urgency=medium

  * Ensure that opening links from XWayland apps still works (LP:
#1921931)

 -- Olivier Tilloy   Tue, 13 Apr 2021
15:59:44 +0200

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

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

Title:
  Opening links results in "Firefox is already running, but is not
  responding"

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Since the latest package release enabling wayland, I often get the
  "Firefox is already running, but is not responding. To use Firefox,
  you must first close the existing Firefox process, restart your
  device, or use a different profile." message when trying to open links
  from other applications (eg geary, slack) instead of having the link
  open in the existing firefox window.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: firefox 87.0+build3-0ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jbarnett  829438 F pulseaudio
  BuildID: 20210318103112
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Tue Mar 30 09:14:13 2021
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2019-08-17 (591 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  IpRoute:
   default via 192.168.4.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.4.0/22 dev wlp2s0 proto kernel scope link src 192.168.4.89 metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-76c5697a-ecec-48ea-b09a-9db310190506
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  PrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js
   prefs.js
  Profiles: Profile0 (Default) - LastVersion=87.0/20210318103112
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs: bp-76c5697a-ecec-48ea-b09a-9db310190506
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to hirsute on 2021-02-23 (34 days ago)
  dmi.bios.date: 07/15/2020
  dmi.bios.release: 1.13
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd07/15/2020:br1.13:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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

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

Is the problem tearing or flickering? In which apps? Only when full
screen?

Please attach a video or photo of the problem so we can understand
better.

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

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

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

Title:
  Screen flickering

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  ubuntu whole screen flickering.

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

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

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

[Desktop-packages] [Bug 1923657] Re: the information was send by the system

Please explain what kind of problem you have.

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

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

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

Title:
  the information was send by the system

Status in Ubuntu:
  Incomplete

Bug description:
  the information was send by the system

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
  Uname: Linux 5.4.0-70-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Tue Apr 13 16:15:07 2021
  DistUpgraded: 2020-10-14 17:02:19,103 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:0782]
 Subsystem: Dell GM108M [GeForce 940MX] [1028:0782]
  InstallationDate: Installed on 2018-05-07 (1072 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 7560
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-70-generic 
root=UUID=21d7010c-b6c8-41b7-a8fc-3e0dfe929d16 ro nopat vesafb.invalid=1 
drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-10-14 (180 days ago)
  dmi.bios.date: 07/19/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.6
  dmi.board.name: 09WC1G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.6:bd07/19/2017:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn09WC1G:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7560
  dmi.product.sku: 0782
  dmi.sys.vendor: Dell Inc.
  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.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  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: Mon Jan 28 09:06:38 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1716 
   vendor BOE
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

I'm slightly worried you might be hitting multiple different bugs there.
But instead of worrying, maybe just try the 'modesetting' driver. It
might solve even more problems if you get both GPUs using the same
driver:

Section "OutputClass"
  Identifier "Use Modesetting"
  MatchDriver "radeon|amdgpu"
  Driver "modesetting"
EndSection

I'm not sure why those drivers don't yet prefer "modesetting" by default
because in Wayland sessions that's exactly what happens anyway.

-- 
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 1896171] Re: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)

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

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

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 1918666] Re: Cannot close the modal "Connect to Wifi" window to return to desktop

** Tags added: fixed-in-3.38.5

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

Title:
  Cannot close the modal "Connect to Wifi" window to return to desktop

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

Bug description:
  When I select the task bar menu, click on the Wifi and select "Select
  to network", a modal window appears that allows me to select a Wifi
  network.

  After I have clicked on one of the networks, normally, when I click
  Cancel or Connect, the modal window disappears and returns me to the
  desktop.

  With the current gnome-shell, this modal window persists and I cannot
  access the desktop - this is both in Wayland and in X. Connect doesn't
  seem to work - it's like the buttons are no longer accepting clicks.
  The ESC key also doesn't do anything. (If I don't click on a network,
  the ESC key does work, and so does Cancel.)

  I think I once managed to get Alt-Ctrl-F1 to bring back the GDM login
  window, but the modal window was still there when I went back into the
  desktop.

  Alt-F2 didn't work so I couldn't try re-starting gnome-shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.3-3ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 11 20:35:24 2021
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-02-24 (15 days ago)

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

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

[Desktop-packages] [Bug 1918738] Re: Regression: Onscreen Keyboard Backspace, Enter and Capitalize do not work

** Tags added: fixed-in-3.38.5

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

Title:
  Regression: Onscreen Keyboard Backspace, Enter and  Capitalize do not
  work

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

Bug description:
  Title pretty much says it all: I'm testing Ubuntu Hirsute (21.04), fully 
upgraded as of today (Gnome-shell 3.38.3) and the osk keys for Backspace, Enter 
and Capitalize as well as for collapsing the keyboard do not work. Pressing 
them just does nothing.
  Related logs in jouralctl output:

  
_press@resource:///org/gnome/shell/ui/keyboard.js:337:39
  
_makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22
  Mär 11 23:06:02 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is 
out of range for uint32
  
_getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24
  
_release@resource:///org/gnome/shell/ui/keyboard.js:370:36
  
_makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22
  Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is 
out of range for uint32
  
_getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24
  
_press@resource:///org/gnome/shell/ui/keyboard.js:337:39
  
_makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22
  Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is 
out of range for uint32
  
_getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24
  
_release@resource:///org/gnome/shell/ui/keyboard.js:370:36
  
_makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22
  Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is 
out of range for uint32
  
_getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24
  
_press@resource:///org/gnome/shell/ui/keyboard.js:337:39
  
_makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22
  Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is 
out of range for uint32
  
_getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24
  
_release@resource:///org/gnome/shell/ui/keyboard.js:370:36
  
_makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22
  Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is 
out of range for uint32
  
_getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24
  
_press@resource:///org/gnome/shell/ui/keyboard.js:337:39
  
_makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22
  Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is 
out of range for uint32
  
_getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24
  
_release@resource:///org/gnome/shell/ui/keyboard.js:370:36
  
_makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22

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

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

Seeds have now been updated:

https://code.launchpad.net/~waveform/ubuntu-seeds/+git/ubuntu-seeds/+merge/400932
https://code.launchpad.net/~waveform/ubuntu-seeds/+git/ubuntu-seeds/+merge/400933

And the meta package has been updated to incorporate these changes in
1.467

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

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Fix Released

** Changed in: ubuntu-settings (Ubuntu)
Milestone: None => ubuntu-21.04

-- 
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 1923090] Re: autopkgtest fails in hirsute on armhf

But I'm still unable to reproduce the test failure on armhf.

-- 
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 1923672] [NEW] [FFe] Provide access to GPIO to default user

2021-04-13 Thread Dave Jones

Public bug reported:

At present, access to the GPIO pins is provided to the dialout group by
the udev rules from the rpi.gpio-common package. However, rpi.gpio is a
single GPIO library, and the device(s) it provides access to are not
specific to it. Moreover, the interface used is deprecated and the
/dev/gpiochip* interface is now the favoured mechanism for controlling
the GPIO pins.

The choice of the dialout group appears reasonable (historically it's
used to provide access to the serial ports, and indeed the serial ports
are part of the GPIO header on Raspberry Pi devices), but the rules
should be extended to cover the modern /dev/gpiochip* devices, the
related /dev/spidev* and /dev/i2c-* devices, and should be placed in a
central location (i.e. ubuntu-raspi-settings) rather than in a specific
GPIO library (like rpi.gpio).

Related to this is LP: #1923363 which seeks to ensure equal access
across images (the default user is currently granted "dialout" group
membership on the pi server images, but not the desktop ones).

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Status: New

** Summary changed:

- Provide access to GPIO to default user
+ [FFe] Provide access to GPIO to default user

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

Title:
  [FFe] Provide access to GPIO to default user

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  At present, access to the GPIO pins is provided to the dialout group
  by the udev rules from the rpi.gpio-common package. However, rpi.gpio
  is a single GPIO library, and the device(s) it provides access to are
  not specific to it. Moreover, the interface used is deprecated and the
  /dev/gpiochip* interface is now the favoured mechanism for controlling
  the GPIO pins.

  The choice of the dialout group appears reasonable (historically it's
  used to provide access to the serial ports, and indeed the serial
  ports are part of the GPIO header on Raspberry Pi devices), but the
  rules should be extended to cover the modern /dev/gpiochip* devices,
  the related /dev/spidev* and /dev/i2c-* devices, and should be placed
  in a central location (i.e. ubuntu-raspi-settings) rather than in a
  specific GPIO library (like rpi.gpio).

  Related to this is LP: #1923363 which seeks to ensure equal access
  across images (the default user is currently granted "dialout" group
  membership on the pi server images, but not the desktop ones).

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

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

This is the UA string of the desktop version on armhf:

Mozilla/5.0 (X11; Ubuntu; Linux armv8l; rv:87.0) Gecko/20100101
Firefox/87.0

-- 
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 1923654] Re: gnome-terminal-server crashed with SIGABRT in g_assertion_message_expr()

2021-04-13 Thread bruno dias da silva

I noticed that when using mutt through some pseudo-terminal (like tmux),
the bug takes longer to happen.

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

Title:
  gnome-terminal-server crashed with SIGABRT in
  g_assertion_message_expr()

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  When resizing a gnome-terminal window while mutt (email client) is open when 
reading email,
  all open terminals are automatically closed. The same is true for other 
emulators, like: Terminator and Tilix.

  The update-notifier-crash shows that the problem binary is in
  "/usr/libexec/gnome-terminal-server"

  1. Ubuntu release:
  bsilva@krypton:~$ lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  2. Package version:
  bsilva@krypton:~$ apt-cache policy gnome-terminal
  gnome-terminal:
Installed: 3.36.2-1ubuntu1~20.04
Candidate: 3.36.2-1ubuntu1~20.04
Version table:
   *** 3.36.2-1ubuntu1~20.04 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   3.36.1.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  bsilva@krypton:~$ apt-cache policy tilix
  tilix:
Installed: 1.9.3-4build3
Candidate: 1.9.3-4build3
Version table:
   *** 1.9.3-4build3 500
  500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

  bsilva@krypton:~$ apt-cache policy terminator
  terminator:
Installed: 1.91-4ubuntu1
Candidate: 1.91-4ubuntu1
Version table:
   *** 1.91-4ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  500 http://archive.ubuntu.com/ubuntu focal/universe i386 Packages
  100 /var/lib/dpkg/status

  3. Expected behavior:
  Resize the size of the terminal without any complications.

  4. Actual behavior:
  All terminals are closed.

  Logs:
  bsilva@krypton:~$ grep gnome-terminal-server /var/log/syslog.1

  Apr 12 09:21:52 krypton gnome-terminal-server[3480]:
  VTE:ERROR:../src/vteaccess.cc:625:void
  vte_terminal_accessible_text_scrolled(VteTerminal*, gint, gpointer):
  assertion failed: (i >= 1)

  Apr 12 09:21:52 krypton gnome-terminal-server[3480]: Bail out!
  VTE:ERROR:../src/vteaccess.cc:625:void
  vte_terminal_accessible_text_scrolled(VteTerminal*, gint, gpointer):
  assertion failed: (i >= 1)

  Apr 12 09:21:54 krypton systemd[2537]: gnome-terminal-server.service:
  Main process exited, code=dumped, status=6/ABRT

  Apr 12 09:21:54 krypton systemd[2537]: gnome-terminal-server.service:
  Failed with result 'core-dump'.

  Apr 12 09:21:54 krypton update-notifier-crash[25556]: gnome-terminal-
  server

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

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

[Desktop-packages] [Bug 1923654] [NEW] gnome-terminal-server crashed with SIGABRT in g_assertion_message_expr()

2021-04-13 Thread bruno dias da silva

Public bug reported:

When resizing a gnome-terminal window while mutt (email client) is open when 
reading email,
all open terminals are automatically closed. The same is true for other 
emulators, like: Terminator and Tilix.

The update-notifier-crash shows that the problem binary is in
"/usr/libexec/gnome-terminal-server"

1. Ubuntu release:
bsilva@krypton:~$ lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04

2. Package version:
bsilva@krypton:~$ apt-cache policy gnome-terminal
gnome-terminal:
  Installed: 3.36.2-1ubuntu1~20.04
  Candidate: 3.36.2-1ubuntu1~20.04
  Version table:
 *** 3.36.2-1ubuntu1~20.04 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
100 /var/lib/dpkg/status
 3.36.1.1-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

bsilva@krypton:~$ apt-cache policy tilix
tilix:
  Installed: 1.9.3-4build3
  Candidate: 1.9.3-4build3
  Version table:
 *** 1.9.3-4build3 500
500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status

bsilva@krypton:~$ apt-cache policy terminator
terminator:
  Installed: 1.91-4ubuntu1
  Candidate: 1.91-4ubuntu1
  Version table:
 *** 1.91-4ubuntu1 500
500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
500 http://archive.ubuntu.com/ubuntu focal/universe i386 Packages
100 /var/lib/dpkg/status

3. Expected behavior:
Resize the size of the terminal without any complications.

4. Actual behavior:
All terminals are closed.

Logs:
bsilva@krypton:~$ grep gnome-terminal-server /var/log/syslog.1

Apr 12 09:21:52 krypton gnome-terminal-server[3480]:
VTE:ERROR:../src/vteaccess.cc:625:void
vte_terminal_accessible_text_scrolled(VteTerminal*, gint, gpointer):
assertion failed: (i >= 1)

Apr 12 09:21:52 krypton gnome-terminal-server[3480]: Bail out!
VTE:ERROR:../src/vteaccess.cc:625:void
vte_terminal_accessible_text_scrolled(VteTerminal*, gint, gpointer):
assertion failed: (i >= 1)

Apr 12 09:21:54 krypton systemd[2537]: gnome-terminal-server.service:
Main process exited, code=dumped, status=6/ABRT

Apr 12 09:21:54 krypton systemd[2537]: gnome-terminal-server.service:
Failed with result 'core-dump'.

Apr 12 09:21:54 krypton update-notifier-crash[25556]: gnome-terminal-
server

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

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

Title:
  gnome-terminal-server crashed with SIGABRT in
  g_assertion_message_expr()

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  When resizing a gnome-terminal window while mutt (email client) is open when 
reading email,
  all open terminals are automatically closed. The same is true for other 
emulators, like: Terminator and Tilix.

  The update-notifier-crash shows that the problem binary is in
  "/usr/libexec/gnome-terminal-server"

  1. Ubuntu release:
  bsilva@krypton:~$ lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  2. Package version:
  bsilva@krypton:~$ apt-cache policy gnome-terminal
  gnome-terminal:
Installed: 3.36.2-1ubuntu1~20.04
Candidate: 3.36.2-1ubuntu1~20.04
Version table:
   *** 3.36.2-1ubuntu1~20.04 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   3.36.1.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  bsilva@krypton:~$ apt-cache policy tilix
  tilix:
Installed: 1.9.3-4build3
Candidate: 1.9.3-4build3
Version table:
   *** 1.9.3-4build3 500
  500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

  bsilva@krypton:~$ apt-cache policy terminator
  terminator:
Installed: 1.91-4ubuntu1
Candidate: 1.91-4ubuntu1
Version table:
   *** 1.91-4ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  500 http://archive.ubuntu.com/ubuntu focal/universe i386 Packages
  100 /var/lib/dpkg/status

  3. Expected behavior:
  Resize the size of the terminal without any complications.

  4. Actual behavior:
  All terminals are closed.

  Logs:
  bsilva@krypton:~$ grep gnome-terminal-server /var/log/syslog.1

  Apr 12 09:21:52 krypton gnome-terminal-server[3480]:
  VTE:ERROR:../src/vteaccess.cc:625:void
  vte_terminal_accessible_text_scrolled(VteTerminal*, gint, gpointer):
  assertion failed: (i >= 1)

  Apr 12 09:21:52 krypton gnome-terminal-server[3480]: Bail out!
  VTE:ERROR:../src/vteaccess.cc:625:void
  vte_terminal_accessible_text_scrolled(VteTerminal*, gint, gpointer):
  assertion failed: (i >= 1)

  Apr 12 09:21:54 krypton systemd[2537]: gnome-terminal-server.service:
  Main process exited, code=dumped, status=6/ABRT

  Apr 12 09:21:54 krypton

[Desktop-packages] [Bug 1923657] [NEW] the information was send by the system

2021-04-13 Thread Manoel

Public bug reported:

the information was send by the system

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
Uname: Linux 5.4.0-70-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Tue Apr 13 16:15:07 2021
DistUpgraded: 2020-10-14 17:02:19,103 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 620 [1028:0782]
   Subsystem: Dell GM108M [GeForce 940MX] [1028:0782]
InstallationDate: Installed on 2018-05-07 (1072 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. Inspiron 7560
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-70-generic 
root=UUID=21d7010c-b6c8-41b7-a8fc-3e0dfe929d16 ro nopat vesafb.invalid=1 
drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-10-14 (180 days ago)
dmi.bios.date: 07/19/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.6
dmi.board.name: 09WC1G
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.6:bd07/19/2017:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn09WC1G:rvrA01:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7560
dmi.product.sku: 0782
dmi.sys.vendor: Dell Inc.
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.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
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: Mon Jan 28 09:06:38 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1716 
 vendor BOE
xserver.version: 2:1.18.4-0ubuntu0.8

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  the information was send by the system

Status in xorg package in Ubuntu:
  New

Bug description:
  the information was send by the system

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
  Uname: Linux 5.4.0-70-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Tue Apr 13 16:15:07 2021
  DistUpgraded: 2020-10-14 17:02:19,103 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:0782]
 Subsystem: Dell GM108M [GeForce 940MX] [1028:0782]
  InstallationDate: Installed on 2018-05-07 (1072 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 7560
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-70-generic 
root=UUID=21d7010c-b6c8-41b7-a8fc-3e0dfe929d16 ro nopat vesafb.invalid=1 
drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-10-14 (180 days ago)
  dmi.bios.date: 07/19/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.6
  dmi.board.name: 09WC1G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.6:bd07/19/2017:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn09WC1G:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7560
  dmi.product.sku: 0782
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz

[Desktop-packages] [Bug 1616332] Re: gnome-software using hundreds of MB of memory when not in use

2021-04-13 Thread G.C. Hassink

yes also 20.04 starts at 50-60 MB grows to 600 MB in a couple of hours,
is there a workaround? e.g. kill every hour?

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

Title:
  gnome-software using hundreds of MB of memory when not in use

Status in GNOME Software:
  Unknown
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  It seems gnome-software is running in the background all the time. Not
  a big deal if it was lightweight, but it seems to use hundreds of MB
  (from smem output):

PID User Command Swap  USS  PSS  
RSS 
   2291 jan  /usr/bin/gnome-software --g   285436   112576   117982   
134036 

  A total of over 400MB in RAM and swap combined.

  After killing and restarting, it takes "only" a bit over 100MB.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug 24 09:45:53 2016
  InstallationDate: Installed on 2012-11-10 (1382 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to xenial on 2016-06-19 (65 days ago)

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

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

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

2021-04-13 Thread Linux NN

Hello,

I was affected by the same bug as you following the Linux
5.8.0-49-generic kernel update (everything is ok with the
5.8.0-48-generic kernel)

However, the problem has been solved with the X.org update which has
been available for a few hours.

Can you look for new updates available and test after updating the X.org
server and restarting the PC?

My PC :
- Dell Inc. Inspiron 3847/088DT1, BIOS A11 05/07/2019
- EFI v2.31 by American Megatrends - Secure boot disable
- CPU : Intel(R) Core(TM) i3-4150 CPU @ 3.50GHz
- GPU : Intel Corporation 4th Generation Core Processor Family Integrated 
Graphics Controller (rev 06)
- A single screen connected via HDMI. Resolution: 1920x1080
- RAM : 16 GB DDR3

My Ubuntu 20.10 :
- Linux 5.8.0-49-generic #55-Ubuntu SMP Wed Mar 24 14:45:45 UTC 2021
- X11
- GNOME 3.38.2
- French language

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

Title:
  Screen flickering

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  ubuntu whole screen flickering.

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

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

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

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

2021-04-13 Thread Launchpad Bug Tracker

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

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

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

Title:
  Screen flickering

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  ubuntu whole screen flickering.

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

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

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

[Desktop-packages] [Bug 1923323] Re: Bluetooth will not stay OFF upon resume

2021-04-13 Thread John Saare

..., or maybe the gsd-rfkill plugin...

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

Title:
Bluetooth will not stay OFF upon resume

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

Bug description:
First: apologies for the possibly incorrect package assignment...,
but "ubuntu-bug" required I select something.

Second..., this is pasted from two postings I made in Ubuntu Forums...

---

Thinkpad P15gen1, Ubuntu 20.04:

Repeat-by:
Enable BT using the top menu bar dropdown and connect with a BT speaker (a BT
stereo adapter in this case).
Play some music..., whatever.
Disable BT using the top menu bar dropdown.
Sleep the machine (close the lid). Note: machine is set to suspend and lock
screen upon lid closure.
Wake the machine (open the lid) and unlock screen.
BT is enabled and connects even though it was disabled prior to suspend.

Heh, the funny thing is that BT has been very reliable in every other way.

How do I get BT to stay OFF when I turn it off? (..., and still have
it turn on, and work, when I turn it on ).

---

I've spent some time trying to characterize the problem. None of the
settings related to power management seemed to relate to the BT
failing to stay OFF problem, however..., along the way, I did find
another interesting and perhaps related problem:

The following setting:

"Power"->"Power Saving"->"Bluetooth (Bluetooth can be turned off to
save power)"->OFF/ON

appears to duplicate the function of the "Bluetooth"->OFF/ON switch
setting.

They do the EXACT same thing. They mirror each other.

E.g., when BT is turned on, the BT power save switch will be on. Turn BT
off..., and the BT power save switch will turn off.
Now..., turn BT back on, and then turn the BT power save switch off..., the
entirety of BT will turn off..., EVEN if there is an active, running
connection. Turn the BT power save switch back ON..., and BT will turn back ON.

This is bogus. If the mapping of the GUI functionality to BT settings
is broken, it's not a long stretch to think some other mapping or
use/management of BT settings is broken as well..., especially since
it's in the neighborhood of power management.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-power-manager 3.32.0-2
ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 10 12:08:47 2021
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
InstallationDate: Installed on 2020-10-22 (170 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20201012-17:03
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-power-manager
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1923323] Re: Bluetooth will not stay OFF upon resume

2021-04-13 Thread John Saare

After a little searching around, it seems like the gsd-power plugin is a
possible culprit. Again..., apologies if I've miscategorized this bug.

** Package changed: gnome-power-manager (Ubuntu) => gnome-settings-
daemon (Ubuntu)

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

Title:
Bluetooth will not stay OFF upon resume

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

Bug description:
First: apologies for the possibly incorrect package assignment...,
but "ubuntu-bug" required I select something.

Second..., this is pasted from two postings I made in Ubuntu Forums...

---

Thinkpad P15gen1, Ubuntu 20.04:

Heh, the funny thing is that BT has been very reliable in every other way.

How do I get BT to stay OFF when I turn it off? (..., and still have
it turn on, and work, when I turn it on ).

---

The following setting:

"Power"->"Power Saving"->"Bluetooth (Bluetooth can be turned off to
save power)"->OFF/ON

appears to duplicate the function of the "Bluetooth"->OFF/ON switch
setting.

They do the EXACT same thing. They mirror each other.

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

[Desktop-packages] [Bug 1923187] Re: [FFe] Enable opencc support

2021-04-13 Thread Iain Lane

We've discussed this on IRC but reporting here for the record-

I think we should wait until next cycle for this change. It's
unfortunate because the delays aren't Gunnar's fault (mainly waiting for
the MIR), but now we don't have much time to find any bugs - if there
are any - before the release, and we don't have people on hand skilled
in the stack that

Given that there isn't a pressing driver or a known super compelling
feature that requires this to be in *this* release, it's safer to wait.

Please feel free to get this uploaded at the start of the 21.10 cycle.
Cheers!

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

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

Title:
  [FFe] Enable opencc support

Status in ibus-libpinyin package in Ubuntu:
  Won't Fix

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

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

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

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

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

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

[Desktop-packages] [Bug 1921931] Re: Opening links results in "Firefox is already running, but is not responding"

2021-04-13 Thread Joe Barnett

ok that makes sense, I think opening links from slack (electron/x11) was
likely the culprit that "poisoned" the running firefox instance

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

Title:
  Opening links results in "Firefox is already running, but is not
  responding"

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  In Progress

Bug description:
  Since the latest package release enabling wayland, I often get the
  "Firefox is already running, but is not responding. To use Firefox,
  you must first close the existing Firefox process, restart your
  device, or use a different profile." message when trying to open links
  from other applications (eg geary, slack) instead of having the link
  open in the existing firefox window.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: firefox 87.0+build3-0ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jbarnett  829438 F pulseaudio
  BuildID: 20210318103112
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Tue Mar 30 09:14:13 2021
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2019-08-17 (591 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  IpRoute:
   default via 192.168.4.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.4.0/22 dev wlp2s0 proto kernel scope link src 192.168.4.89 metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-76c5697a-ecec-48ea-b09a-9db310190506
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  PrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js
   prefs.js
  Profiles: Profile0 (Default) - LastVersion=87.0/20210318103112
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs: bp-76c5697a-ecec-48ea-b09a-9db310190506
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to hirsute on 2021-02-23 (34 days ago)
  dmi.bios.date: 07/15/2020
  dmi.bios.release: 1.13
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd07/15/2020:br1.13:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1917705] Re: "profile will be deleted" at startup after chromium 89 update

No. The status of the bug is "Won't Fix", meaning there's no plan to
further invest effort in it.

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

Title:
  "profile will be deleted" at startup after chromium 89 update

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  After updating the chromium-browser snap from 1497 to 1506, Chromium
  refuses to work with profiles that are linked to Google accounts. Each
  of them is deleted whenever first opening it. And turning on profile
  synchronization does not work.

  See the attached file for a screenshot of the issue.

  Workaround:
  1. Kill the current chromium process.
  2. Revert the snap back to an older version.
  Warning 1: Running on an older version of Chromium comes at its own issues.
  Warning 2: Any already deleted profile will not be restored by going back to 
an older version of Chromium. You will have to create and link the profile 
again.

  This bug is severe and means that Chromium has become unusable in a
  professional environment.

  "We also need:"

  1) The release of Ubuntu you are using
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.2 LTS
  Release:20.04
  Codename:   focal

  2) The version of the package you are using
  $ snap list chromium
  Name  VersionRev   Tracking   Publisher   Notes
  chromium  89.0.4389.72   1506  latest/stable  canonical*  -

  3) What you expected to happen
  Chromium works as usual, linked profiles work, new profiles can be linked to 
sync with Google accounts.

  4) What happened instead
  Chromium cannot work with linked profiles. Existing profiles from older 
versions of Chromium that are linked to sync with a Google account are deleted 
upon start, and the feature of linking a profile to a Google account for 
syncing is broken.

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

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

[Desktop-packages] [Bug 1917705] Re: "profile will be deleted" at startup after chromium 89 update

2021-04-13 Thread Efthimios Chaskaris

@Olivier Tilloy Are there any plans to remedy this issue? Like releasing
api keys to be used by distros?

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

Title:
  "profile will be deleted" at startup after chromium 89 update

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  After updating the chromium-browser snap from 1497 to 1506, Chromium
  refuses to work with profiles that are linked to Google accounts. Each
  of them is deleted whenever first opening it. And turning on profile
  synchronization does not work.

  See the attached file for a screenshot of the issue.

  Workaround:
  1. Kill the current chromium process.
  2. Revert the snap back to an older version.
  Warning 1: Running on an older version of Chromium comes at its own issues.
  Warning 2: Any already deleted profile will not be restored by going back to 
an older version of Chromium. You will have to create and link the profile 
again.

  This bug is severe and means that Chromium has become unusable in a
  professional environment.

  "We also need:"

  1) The release of Ubuntu you are using
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.2 LTS
  Release:20.04
  Codename:   focal

  2) The version of the package you are using
  $ snap list chromium
  Name  VersionRev   Tracking   Publisher   Notes
  chromium  89.0.4389.72   1506  latest/stable  canonical*  -

  3) What you expected to happen
  Chromium works as usual, linked profiles work, new profiles can be linked to 
sync with Google accounts.

  4) What happened instead
  Chromium cannot work with linked profiles. Existing profiles from older 
versions of Chromium that are linked to sync with a Google account are deleted 
upon start, and the feature of linking a profile to a Google account for 
syncing is broken.

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

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

[Desktop-packages] [Bug 1923632] [NEW] Screen flickering

2021-04-13 Thread siva

Public bug reported:

ubuntu whole screen flickering.

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

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


** Tags: amd64 apport-bug groovy ubuntu

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

Title:
  Screen flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu whole screen flickering.

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

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

2021-04-13 Thread Heather Ellsworth

Hey coeur-noir, could you please test this snap and see if it fixes your
dark theme icon issue?

https://launchpad.net/~hellsworth/+snap/libreoffice-
lp-1915677/+build/1368383/+files/libreoffice_7.1.2.2_amd64.snap

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

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

Status in libreoffice package in Ubuntu:
  In Progress

Bug description:
  Hi,

  trying LibreOffice 7 as a snap on UbuntuBudgie 20.04.

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

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

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

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

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

[Desktop-packages] [Bug 1891682] Re: [MIR] sane-airscan

2021-04-13 Thread Didier Roche

$ ./change-override -c main -S sane-airscan
Override component to main
sane-airscan 0.99.25-0ubuntu1 in hirsute: universe/misc -> main
sane-airscan 0.99.25-0ubuntu1 in hirsute amd64: universe/graphics/optional/100% 
-> main
sane-airscan 0.99.25-0ubuntu1 in hirsute arm64: universe/graphics/optional/100% 
-> main
sane-airscan 0.99.25-0ubuntu1 in hirsute armhf: universe/graphics/optional/100% 
-> main
sane-airscan 0.99.25-0ubuntu1 in hirsute ppc64el: 
universe/graphics/optional/100% -> main
sane-airscan 0.99.25-0ubuntu1 in hirsute riscv64: 
universe/graphics/optional/100% -> main
sane-airscan 0.99.25-0ubuntu1 in hirsute s390x: universe/graphics/optional/100% 
-> main
Override [y|N]? y
7 publications overridden.


** Changed in: sane-airscan (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR] sane-airscan

Status in sane-airscan package in Ubuntu:
  Fix Released

Bug description:
  Driverless Scanning
  ---

  TL;DR: sane-airscan provides perfect support for driverless scanning,
  making thousands of devices working

  Printer manufacturers have introduced driverless printing standards to
  allow easy use of their (usually network) printers also from mobile
  phones, tablets, and IoT devices and not only from desktop computers
  which in most cases run Windows or Mac OS. This we have made use of to
  be able to print on a huge amount of printers from Linux and other
  free software operating systems.

  But multi-function devices with a scanner do also allow scanning from
  mobile devices and have a scan standard for that. Every device which
  supports Apple's AirPrint supports also AirScan and AirScan means that
  the device either scans via eSCL (from HP and Apple) or via WSD (from
  Microsoft and W3C).

  Also of this we make use to get a wide range of devices "just" working
  under Linux. This covers practically any modern network multi-function
  device, thousands of models. Finally we can also scan on multi-
  function devices which are not from HP (but scanning on the HP ones
  gets also easier, without needing HPLIP). And we even have discovered
  a USB-only stand-alone scanner doing driverless scanning, the Canon
  Lide 400.

  sane-airscan is the a SANE backend for supporting this. It supports
  both eSCL and WSD to their full extent, especially also for scanners
  with extra functionality like an Automatic Document Feeder (ADF). It
  is designed as a universal SANE backend for high-level scanning
  protocols, as much of the code as possible is shared between
  protocols, the protocol-specific parts are small. So easily new
  protocols, like TWAIN Direct or IPP Scan, can get added later. IPP
  Scan is especially important as it will help us to make scanner
  drivers snappable in the future.

  Why not sane-escl which sane-backends already ships?
  

  TL;DR: sane-escl is deprecated in favor of sane-airscan

  The first approach of driverless scanning which made it into Ubuntu
  was the sane-escl SANE backend, as part of the sane-backends package
  which we already include. This was easier to get in before Feature
  Freeze of 20.04 back in February, not requiring to get sane-airscan
  through NEW and then through a MIR. Also it was unclear in that time
  whether sane-airscan would be integrated into sane-backends.

  Now a lot has changed with the time:

  The authors of sane-escl and sane-airscan started their projects
  independently both also only supporting eSCL and not yet WSD. They
  were competing with each other and had some different priorities in
  their developments. I talked with them and asked them why they would
  not collaborate and succeeded to make them agree with each other. Now
  development of sane-escl has stopped and all effort goes into sane-
  airscan.

  In addition, WSD support was added to sane-airscan and sane-airscan
  has matured a lot, with a lot of users reporting their devices working
  and the author having fixed a lot of bugs based on reports and logs
  from users.

  sane-airscan supports both WSD and eSCL, sane-escl only eSCL.

  sane-airscan supports ADF scanning, sane-escl only scanning from the
  glass.

  Why not add sane-airscan to sane-backends upstream?
  ---

  Tl;DR: Developemnt and release pace is much faster than of SANE, with
  the IPP-Scan-based scanning architecture in the future only sane-
  airscan and not the scanner driver arsenal of sane-backends will be
  needed by applications.

  The author of sane-airscan asked for adding his backend to sane-
  backends in the beginning:

  https://gitlab.com/sane-project/backends/-/issues/202

  In the end it seems that they have settled to keep sane-airscan
  separate, mainly due to its much faster

[Desktop-packages] [Bug 1921931] Re: Opening links results in "Firefox is already running, but is not responding"

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

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

Title:
  Opening links results in "Firefox is already running, but is not
  responding"

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  In Progress

Bug description:
  Since the latest package release enabling wayland, I often get the
  "Firefox is already running, but is not responding. To use Firefox,
  you must first close the existing Firefox process, restart your
  device, or use a different profile." message when trying to open links
  from other applications (eg geary, slack) instead of having the link
  open in the existing firefox window.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: firefox 87.0+build3-0ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jbarnett  829438 F pulseaudio
  BuildID: 20210318103112
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Tue Mar 30 09:14:13 2021
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2019-08-17 (591 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  IpRoute:
   default via 192.168.4.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.4.0/22 dev wlp2s0 proto kernel scope link src 192.168.4.89 metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-76c5697a-ecec-48ea-b09a-9db310190506
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  PrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js
   prefs.js
  Profiles: Profile0 (Default) - LastVersion=87.0/20210318103112
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs: bp-76c5697a-ecec-48ea-b09a-9db310190506
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to hirsute on 2021-02-23 (34 days ago)
  dmi.bios.date: 07/15/2020
  dmi.bios.release: 1.13
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd07/15/2020:br1.13:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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

Hi Daniel,

Thanks for sharing comment#27.

Let me summarize the reproduce scenarios in Intel + AMD case.

1. Boot from iGPU -> switch to dGPU -> switch back to iGPU -> iGPU lag.
2. Boot from iGPU -> connect secondary monitor to dGPU -> remove 1st monitor 
from iGPU -> dGPU lag.
3. Boot from iGPU -> connect secondary monitor to dGPU -> set iGPU as primary 
display -> moving an application (e.g. glxgear) from secondary display (dGPU) 
to primary display (iGPU) -> iGPU lag.

The comment#27 could workaround case#1 and case #3.

but switch to wayland could fix these three cases.

-- 
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 1921931] Re: Opening links results in "Firefox is already running, but is not responding"

https://mastransky.wordpress.com/2020/03/16/wayland-x11-how-to-run-
firefox-in-mixed-environment/ is useful to understand the problem.

As suggested there, exporting MOZ_DBUS_REMOTE=1 when running in a
wayland session works around the problem.

I can observe the problem in a wayland session if I launch e.g. vlc with
GDK_BACKEND=x11 and then click a link in the app (e.g. in the about
dialog). With MOZ_DBUS_REMOTE set, the problem is gone.

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

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

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

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

Title:
  Opening links results in "Firefox is already running, but is not
  responding"

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Since the latest package release enabling wayland, I often get the
  "Firefox is already running, but is not responding. To use Firefox,
  you must first close the existing Firefox process, restart your
  device, or use a different profile." message when trying to open links
  from other applications (eg geary, slack) instead of having the link
  open in the existing firefox window.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: firefox 87.0+build3-0ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jbarnett  829438 F pulseaudio
  BuildID: 20210318103112
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Tue Mar 30 09:14:13 2021
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2019-08-17 (591 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  IpRoute:
   default via 192.168.4.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.4.0/22 dev wlp2s0 proto kernel scope link src 192.168.4.89 metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-76c5697a-ecec-48ea-b09a-9db310190506
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  PrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js
   prefs.js
  Profiles: Profile0 (Default) - LastVersion=87.0/20210318103112
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs: bp-76c5697a-ecec-48ea-b09a-9db310190506
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to hirsute on 2021-02-23 (34 days ago)
  dmi.bios.date: 07/15/2020
  dmi.bios.release: 1.13
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd07/15/2020:br1.13:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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

** Description changed:

+ 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 "N/A" (not available), when trying to run ld-linux on a
- release with glibc (<< 2.33).
+ 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
+   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
+   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
+   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}')
+   $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.

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

Title:
  add metric for new glibc hwcaps

Status in ubuntu-report package in Ubuntu:
  Confirmed

Bug description:
  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 1921991] Re: [SRU] Support isdv4-aes stylus group and multiple AES stylus definitions

2021-04-13 Thread Sebastien Bacher

@Bin, thanks for the work there. By SRU rule the issue needs to be fixed
in the current serie first. Are the patches in 1.8/hirsute? If not could
you prepare a debdiff for that serie?

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

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)

Combining the above two ideas you could add a new config file (make sure
its name loads before "10-radeon.conf"):

Section "OutputClass"
Identifier "MyRadeon"
MatchDriver "radeon"
Driver "modesetting"
EndSection

-- 
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)

Or just remove/edit /usr/share/X11/xorg.conf.d/10-radeon.conf

-- 
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)

As a workaround you should be able to avoid the radeon Xorg driver with
a custom config, something like:

   Section "Device"
 Identifier "MyRadeon"
 Driver "modesetting"
 BusID  "pci:1:0:0"
   EndSection

Then it will use the same interfaces as in a Wayland session.

-- 
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)

As a workaround you should be able to avoid the radeon Xorg driver with
a custom config, something like:

   Section "Device"
 Identifier "devname"
 Driver "modesetting"
 BusID  "pci:bus:dev:func"
 ...
   EndSection

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

2021-04-13 Thread Treviño

** Tags removed: rls-ff-incoming
** Tags added: 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]

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

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

2021-04-13 Thread Treviño

** Tags added: rls-ff-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 1923602] [NEW] Sound "Output" level shows input level

2021-04-13 Thread Wiktor Nizio

Public bug reported:

In sound setting in the "Output" section there is a dashed line that I
suppose should be the current output level. Instead, it shows input
level, just like the line in the "Input" section.

Clap your hands next to the microphone, and you will see both lines
moving.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-control-center 1:3.38.5-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu62
Architecture: amd64
CasperMD5json:
 {
   "result": "skip"
 }
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 13 12:46:54 2021
InstallationDate: Installed on 2021-04-08 (5 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
RebootRequiredPkgs: network-manager
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "bitmap.png"
   https://bugs.launchpad.net/bugs/1923602/+attachment/5487271/+files/bitmap.png

** Summary changed:

- "Output level" shows input level
+ Sound "output level" shows input level

** Summary changed:

- Sound "output level" shows input level
+ Sound "output" level shows input level

** Summary changed:

- Sound "output" level shows input level
+ Sound "Output" level shows input level

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

Title:
  Sound "Output" level shows input level

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

Bug description:
  In sound setting in the "Output" section there is a dashed line that I
  suppose should be the current output level. Instead, it shows input
  level, just like the line in the "Input" section.

  Clap your hands next to the microphone, and you will see both lines
  moving.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-control-center 1:3.38.5-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  CasperMD5json:
   {
 "result": "skip"
   }
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 13 12:46:54 2021
  InstallationDate: Installed on 2021-04-08 (5 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  RebootRequiredPkgs: network-manager
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1902801] Re: Encrypted attachments cannot be opened or saved as decrypted files

2021-04-13 Thread Tobias

Hi, I've stumbled across this post here after I've searched for the
error message "rnp_op_verify_execute returned unexpected" on Google.

@yg-info I've tested the beta version "88.0b2" (simply downloading the
.tar.bz2 for Linux and executing the "thunderbird" binary) and it's now
working. The two emails, which can't be open by Thunderbird "78.9.1",
can be open with Thunderbird "88.0b2".

The first email has no attachments and the second email has one
attachment (simple csv file), which I can open.

I'm using (Manjaro Arch) Linux, Kernel 5.11.10-1-MANJARO, x64.

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

Title:
  Encrypted attachments cannot be opened or saved as decrypted files

Status in thunderbird package in Ubuntu:
  Fix Released
Status in Arch Linux:
  Fix Released

Bug description:
  I have been using enigmail in thunderbird until I upgraded Ubuntu and
  with it thunderbird to the latest version 1:78.3.2+build1-0ubuntu1

  As enigmail is now integrated in thunderbird, I have gone through the
  painful upgrade process (it does not allow to look into
  passwordmanager for the pasphrase of the gpg keys it wants to import
  by blocking all other windows), and decryption of emails now works.

  But when looking at a decrypted email, fully being able to read the
  text content, when I want to use the Menu option "Decrypt and Open" by
  right clicking on an attachment (pdf in this case), nothing happens.

  What I expect to happen: The pdf file being shown to me in the pdf
  viewer. Or some error being displayed, or maybe I am asked for my gpg
  passphrase again for additional security.

  
  When trying the option "Decrypt and save as", next I can select a folder and 
filename, (the pdf name without .gpg) and chose "save" - but when looking into 
that folder, there is no decrypted file. (I tried this plenty of time, I am 
sure its not there, and I did this action before the upgrade many times 
successfully).

  What I would expect: the attached file without the .gpg suffix (the
  filename proposed when opening the dialog, which I did not change) in
  the selected directory.

  
  $ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  
  $ apt-cache policy  thunderbird
  thunderbird:
Installed: 1:78.3.2+build1-0ubuntu1
Candidate: 1:78.3.2+build1-0ubuntu1
Version table:
   *** 1:78.3.2+build1-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1923593] [NEW] Default menu entry [Web Browser] does not working in xubuntu 20.04 LTS

2021-04-13 Thread Robert Gruber

Public bug reported:

In case of the first startup: The chromium-browser pops up with the
question [Yes] or [No]. In case of [Yes] the menu entry
Menu->Favorites->Web Browser stops working. In case of [No] the menu
entry Web Browser is working in the right way, however, the chromium-
browser has to be set under Menu->Settings->Preferred
Applications->Internet to default Web Browser.

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Default menu entry [Web Browser] does not working in xubuntu 20.04 LTS

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  In case of the first startup: The chromium-browser pops up with the
  question [Yes] or [No]. In case of [Yes] the menu entry
  Menu->Favorites->Web Browser stops working. In case of [No] the menu
  entry Web Browser is working in the right way, however, the chromium-
  browser has to be set under Menu->Settings->Preferred
  Applications->Internet to default Web Browser.

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

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

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

2021-04-13 Thread Rik Mills

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

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

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

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

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

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

  Cases where the crash can be triggered:

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

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

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

  Try/Install crash:

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

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

  Live session crash:

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

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

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

   /var/log/installer/debug 

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

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

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

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

** Changed in: oem-priority
   Status: Confirmed => In Progress

-- 
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)

Hi Daniel,

I could reproduce this issue when using today hirsute daily build

$ sha256sum ~/Downloads/hirsute-desktop-amd64.iso 
4908a5c919f4b796a856be69a044334eb1a910727180618348db0a8a1ef70360  
/home/jeremysu/Downloads/hirsute-desktop-amd64.iso

after switching back to xorg (hirsute default uses Wayland)

-- 
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)

The other finding for comment#20.

If connecting two monitors then there is a way to reproduce it.

1. Set iGPU as primary monitor
2. Run an application from secondary display (dGPU) (e.g. glxgear)
3. Moving the application from secondary display (dGPU) to primary display 
(iGPU) then the issue occur.

For comment#19, I'm preparing hirsute using today daily build. Will
update the result here later.

-- 
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:
  Confirmed
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)

Comment #19 is probably important to answer because we need to know if
we're looking for a backport or a whole new upstream fix.

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

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

Status in OEM Priority Project:
  Confirmed
Status in xorg-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 1923564] [NEW] BlueZ 5.58 release

Public bug reported:

BlueZ 5.58 has been released. We should look at it for the 21.10
cycle...

http://www.bluez.org/release-of-bluez-5-58-and-5-57/
https://mirrors.edge.kernel.org/pub/linux/bluetooth/

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

** Description changed:

  BlueZ 5.58 has been released. We should look at it for the 21.10
  cycle...
  
+ http://www.bluez.org/release-of-bluez-5-58-and-5-57/
  https://mirrors.edge.kernel.org/pub/linux/bluetooth/

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

Title:
  BlueZ 5.58 release

Status in bluez package in Ubuntu:
  New

Bug description:
  BlueZ 5.58 has been released. We should look at it for the 21.10
  cycle...

  http://www.bluez.org/release-of-bluez-5-58-and-5-57/
  https://mirrors.edge.kernel.org/pub/linux/bluetooth/

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

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

** Tags added: originate-from-1907016 sutton

** Tags added: originate-from-1910795

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

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)

BTW, for i915 case, it's not 100% reproduce if the boot-vga-device is
i915.

Which means in Intel + AMD platform.

Sometime the system laggy when output from dGPU (AMD 430).
Sometime the system laggy when output from iGPU (intel) AFTER switching the 
monitor between dGPU and iGPU (e.g. boot vga: i915 -> moving monitor to dGPU -> 
moving monitor back to iGPU).

but all works smoothly when connecting two monitor from both iGPU and
dGPU (this scenario works good on AMD + AMD platform).

-- 
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:
  Confirmed
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 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

2021-04-13 Thread xiconfjs

Hi @osomon,

what is the latest status on the Ubuntu 18.04 release of thunderbird
78.7.x? Can I/we help in any way?


Thanks
xiconfjs

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

Title:
  Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

Status in enigmail package in Ubuntu:
  Fix Released
Status in thunderbird package in Ubuntu:
  Fix Released
Status in jsunit source package in Bionic:
  In Progress
Status in thunderbird source package in Bionic:
  In Progress
Status in enigmail source package in Focal:
  Fix Released
Status in jsunit source package in Focal:
  Fix Released
Status in thunderbird source package in Focal:
  Fix Released
Status in tinyjsd source package in Focal:
  Fix Released
Status in thunderbird source package in Groovy:
  Fix Released

Bug description:
  Upstream Thunderbird version 78.2.2 should be a candidate for
  backporting to stable Ubuntu releases.

  I've successfully built 78.2.1 against both with forcing nodejs
  version (20.04, 18.04) and disabling AV1 support due to too old nasm
  (18.04). Attaching debdiffs here.

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

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

[Desktop-packages] [Bug 1923130] Re: duplicate folders in "show application" menu