date:20210116

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

2021-01-16 Thread Philippe

Same issue with Ubuntu Mate HWE 20.04 with kernel 5.8 and latest AMD
driver from oibaf PPA.

$ inxi -SMG
System:Host: ACER-xk2308 Kernel: 5.8.0-38-generic x86_64 bits: 64 Desktop: 
MATE 1.24.0 
   Distro: Ubuntu 20.04.1 LTS (Focal Fossa) 
Machine:   Type: Desktop System: MSI product: MS-7798 v: 1.0 serial: 
 
   Mobo: MSI model: B75MA-P45 (MS-7798) v: 1.0 serial:  BIOS: American Megatrends v: 1.9 
   date: 09/30/2013 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 
OEM/5600 XT / 5700/5700 XT] driver: amdgpu 
   v: kernel 
   Display: x11 server: X.Org 1.20.9 driver: amdgpu,ati unloaded: 
fbdev,modesetting,radeon,vesa 
   resolution: 1366x768~60Hz 
   OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.38.0 
5.8.0-38-generic LLVM 11.0.1) 
   v: 4.6 Mesa 21.1.0-devel (git-7b48d5d 2021-01-16 focal-oibaf-ppa)
$ hwe-support-status --verbose
Your Hardware Enablement Stack (HWE) is supported until avril 2025

Please, let me know what to do, for testing what you want.

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

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

Status in Linux:
  Unknown
Status in libxcb package in Ubuntu:
  Confirmed
Status in xfwm4 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Update based on further research.

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

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

  The underlying bug is in the AMD driver.

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1900167] Re: gnome-software Unable to install updates

2021-01-16 Thread Launchpad Bug Tracker

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

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

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

Title:
  gnome-software Unable to install updates

Status in gnome-software package in Ubuntu:
  Expired

Bug description:
  Click on 'Updates' and then on 'Restart & Update' I have a message:
  Unable to install updates: GDBus.error... Prepared update not 
found:/var/lib/PackageKit/prepared-update

  corrado@corrado-x2-gg-1009:~$ apt policy gnome-software
  gnome-software:
Installed: 3.38.0-2build1
Candidate: 3.38.0-2build1
Version table:
   *** 3.38.0-2build1 500
  500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-x2-gg-1009:~$ inxi -Fx
  System:
Host: corrado-x2-gg-1009 Kernel: 5.8.0-23-generic x86_64 bits: 64 
compiler: gcc v: 10.2.0 Desktop: N/A Distro: Ubuntu 20.10 (Groovy Gorilla) 
  Machine:
Type: Desktop Mobo: ASRock model: H110M-G/M.2 
serial:  UEFI: American Megatrends v: P1.10 
date: 05/11/2017 
  CPU:
Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP 
arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 
3: 800 4: 800 
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel 
bus ID: 00:02.0 
Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa 
resolution: 1920x1080~60Hz 
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.2.0 
direct render: Yes 
  Audio:
Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock 
driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
Device-2: Logitech QuickCam Pro 9000 type: USB 
driver: snd-usb-audio,uvcvideo bus ID: 1-8:4 
Sound Server: ALSA v: k5.8.0-23-generic 
  Network:
Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k 
port: f040 bus ID: 00:1f.6 
IF: enp0s31f6 state: up speed: 100 Mbps duplex: full 
mac: 70:85:c2:44:7b:86 
  Drives:
Local Storage: total: 2.05 TiB used: 9.42 GiB (0.4%) 
ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB 
ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB 
  Partition:
ID-1: / size: 31.25 GiB used: 9.41 GiB (30.1%) fs: ext4 
dev: /dev/nvme0n1p2 
  Swap:
ID-1: swap-1 type: partition size: 8.00 GiB used: 0 KiB (0.0%) 
dev: /dev/sda2 
  Sensors:
System Temperatures: cpu: 43.5 C mobo: N/A 
Fan Speeds (RPM): N/A 
  Info:
Processes: 224 Uptime: 3h 13m Memory: 7.48 GiB used: 1.66 GiB (22.2%) 
Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1874 Shell: Bash 
v: 5.0.17 inxi: 3.1.07 
  corrado@corrado-x2-gg-1009:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-software 3.38.0-2build1
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 16 18:20:00 2020
  InstallationDate: Installed on 2020-10-10 (6 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201009.1)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.38.0-2build1
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1904597] Re: Minimizing a fullscreen window causes Graphical issues

2021-01-16 Thread Launchpad Bug Tracker

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

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

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

Title:
  Minimizing a fullscreen window causes Graphical issues

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Upon minimizing or tabbing out of a fullscreen window, the cursor will lag 
behind, and other applications will slow drastically. I have an AMD 5700XT and 
I believe the included driver is causing the issue but I am not certain.
  I am using ubuntu 20.04 lts

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

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

[Desktop-packages] [Bug 1912083] [NEW] the icons are longer

2021-01-16 Thread Kent Tai

Public bug reported:

the icons are longer than they should be

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
Uname: Linux 5.8.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
BootLog: Error: [Errno 13] 拒絕不符權限的操作: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 17 11:12:46 2021
DistUpgraded: 2021-01-17 10:47:32,279 DEBUG openCache()
DistroCodename: groovy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.16, 5.8.0-36-generic, x86_64: installed
 virtualbox, 6.1.16, 5.8.0-38-generic, x86_64: installed
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company UHD Graphics [103c:86cd]
ImageMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 13d3:56c9 IMC Networks HP TrueVision HD Camera
 Bus 001 Device 002: ID 145f:021f Trust 2.4G Mouse
 Bus 001 Device 004: ID 8087:0026 Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP 348 G7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=aea93e03-8fb8-49c7-8081-a18a438e7864 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to groovy on 2021-01-17 (0 days ago)
dmi.bios.date: 06/11/2020
dmi.bios.release: 15.21
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 86CD
dmi.board.vendor: HP
dmi.board.version: 98.08
dmi.chassis.asset.tag: 5CG0351KMK
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 98.8
dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd06/11/2020:br15.21:efr98.8:svnHP:pnHP348G7:pvrType1ProductConfigId:rvnHP:rn86CD:rvr98.08:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5336AN HP Notebook
dmi.product.name: HP 348 G7
dmi.product.sku: 7HC08AV
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
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.1~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-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 third-party-packages 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/1912083

Title:
  the icons are longer

Status in xorg package in Ubuntu:
  New

Bug description:
  the icons are longer than they should be

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog: Error: [Errno 13] 拒絕不符權限的操作: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 17 11:12:46 2021
  DistUpgraded: 2021-01-17 10:47:32,279 DEBUG openCache()
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.8.0-36-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-38-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics [103c:86cd]
  ImageMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56c9 IMC Networks HP TrueVision HD Camera
   Bus 001 Device 002: ID 145f:021f Trust 2.4G Mouse
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP 348 G7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=aea93e03-8fb8-49c7-8081-a18a438e7864 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2021-01-17 (0 days ago)
  dmi.bios.date: 06/11/2020
  dmi.bios.release: 15.21
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 86CD
  dmi.board.vendor: HP
  dmi.board.version: 98.08
  dmi.chassis.asset.tag: 5CG0351KMK
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version

[Desktop-packages] [Bug 1905054]

2021-01-16 Thread Ryanvm

Is this something we should consider uplifting to Beta for 85?

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

Title:
  Firefox 83 Breaks WebGL

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

Bug description:
  Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working.
  Ubuntu 20.10 with Wayland.

  When I try to launch a webGL game:
  Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is 
not hardware-accelerated.

  Specifically Pixi says:
  Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback 
canvas2d support.

  Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build
  issue or Firefox, so I also filed upstream as well:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1678652

  I need this functionality for work, and pinning to version 82 will be
  problematic in the long-term.

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

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

[Desktop-packages] [Bug 1867996] Re: Segfault in app_indicator_set_icon_full [patch attached]

2021-01-16 Thread Mathew Hodson

** Tags removed: removal-candidate verification-needed

** Package changed: libappindicator (Arch Linux) => ubuntu-translations

** No longer affects: ubuntu-translations

** Changed in: libappindicator (Ubuntu)
   Importance: Undecided => Medium

** Changed in: libappindicator (Ubuntu Bionic)
   Importance: Undecided => Medium

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

Title:
  Segfault in app_indicator_set_icon_full [patch attached]

Status in libappindicator package in Ubuntu:
  Fix Released
Status in libappindicator source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  Discord and several other applications using libappindicator are
  widely reported to have been crashing for several years. See:
  https://github.com/flathub/com.discordapp.Discord/issues/30 (and
  others)

  [ Test case ]

  - Run discord application
  - It must not crash in ubuntu (or when indicators are enabled)

  [ Regression potential ]

  Very low, icons might not appear in some cases, if any.

  -

  This is the backtrace:
  (gdb) bt full
  #0  0x7fe1d5d2e00e in  () at /app/lib/libappindicator.so
  #1  0x7fe1f5a6f3c5 in g_closure_invoke () at /lib/libgobject-2.0.so.0
  #2  0x7fe1f5a813d2 in  () at /lib/libgobject-2.0.so.0
  #3  0x7fe1f5a8a02c in g_signal_emit_valist () at /lib/libgobject-2.0.so.0
  #4  0x7fe1f5a8a40f in g_signal_emit () at /lib/libgobject-2.0.so.0
  #5  0x7fe1d5d2ed4f in app_indicator_set_icon_full () at 
/app/lib/libappindicator.so
  #6  0x0077851a in  ()
  #7  0x01de7123 in  ()
  #8  0x01e4bd4e in  ()
  #9  0x01e6e34c in  ()
  #10 0x01e6e668 in  ()
  #11 0x01e6e9cb in  ()
  #12 0x01df971a in  ()
  #13 0x7fe1f354b1c7 in g_main_context_dispatch () at /lib/libglib-2.0.so.0
  #14 0x7fe1f354b430 in  () at /lib/libglib-2.0.so.0
  #15 0x7fe1f354b4dc in g_main_context_iteration () at /lib/libglib-2.0.so.0
  #16 0x01df9606 in  ()
  #17 0x01e6e0e7 in  ()
  #18 0x01e29570 in  ()
  #19 0x00c37ec8 in  ()
  #20 0x00c37d15 in  ()
  #21 0x00c1da7d in  ()
  #22 0x00a9282e in  ()
  #23 0x007892d4 in  ()
  #24 0x007896e0 in  ()
  #25 0x03b830a3 in main ()

  Happens in all versions of libappindicator built from latest sources
  available on launchpad.

  I ran into the issue yesterday when installing Discord for the first
  time. I have tracked the problem down to libappindicator passing in an
  extra vararg item to g_signal_emit that the signal's definition in
  libappindicator was not declaring, causing the crash you see above in
  gobject's g_signal dispatch machinery.

  Patch is attached.

  I am presuming this is 'upstream' for libappindicator, whatever that
  may mean for what appears to be an unmaintained project. If it is not,
  and since it is an Ubuntu/Canonical-sourced project originally, I
  respectfully request that you assist in upstreaming it since this bug
  is causing severe breakage for users across all distros.

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

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

[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector

2021-01-16 Thread Rob David

** Bug watch added: github.com/keepassxreboot/keepassxc/issues #1598
   https://github.com/keepassxreboot/keepassxc/issues/1598

** Also affects: chromium-browser via
   https://github.com/keepassxreboot/keepassxc/issues/1598
   Importance: Unknown
   Status: Unknown

** Project changed: chromium-browser => keepassxc-snap

** Project changed: keepassxc-snap => keepassxc-browser (Ubuntu)

** Package changed: keepassxc-browser (Ubuntu) => keepassxc-snap

** Changed in: keepassxc-snap
 Remote watch: github.com/keepassxreboot/keepassxc/issues #1598 => 
github.com/keepassxreboot/keepassxc-browser/issues #405

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

Title:
  [snap] chrome-gnome-shell extension fails to detect native host
  connector

Status in KeePassXC Snap Builds:
  Unknown
Status in chromium-browser package in Ubuntu:
  Triaged
Status in goopg package in Ubuntu:
  Confirmed
Status in kdeconnect package in Ubuntu:
  Confirmed

Bug description:
  (initially reported at https://forum.snapcraft.io/t/chrome-gnome-
  shell-does-not-work-with-chromium-snap/3377)

  See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keepassxc-snap/+bug/1741074/+subscriptions

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

[Desktop-packages] [Bug 1911432] Re: [SRU] wslu 3.2.1-0ubuntu1 to focal

2021-01-16 Thread Mathew Hodson

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

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

** Tags added: upgrade-software-version

** Changed in: wslu (Ubuntu)
   Status: New => Fix Released

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

Title:
  [SRU] wslu 3.2.1-0ubuntu1 to focal

Status in wslu package in Ubuntu:
  Fix Released
Status in wslu source package in Focal:
  New

Bug description:
  [Impact]

  it is proposed to be updated from 2.x to 3.x in 20.10/21.04 circle.
  The detailed impact can be found on LP: #1895525.

  [Test Case]

   * Follow the testing process outlined in https://wiki.ubuntu.com/wslu-Updates
   * Run the autopktest in a WSL environment.
   * View the result of the test, with 7 Windows Explorer open and 3 webpage 
open on the default browzer.

  [Regression Potential]

  This is a large version update from 2.x to 3.x. according to the
  previous process merging to groovy on bug LP: #1895525, there is no
  clear issue. Potential regressions would be a result of badly
  generated ~/.config/wslu/.

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

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

[Desktop-packages] [Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:2

2021-01-16 Thread Mathew Hodson

** Tags removed: verification-needed

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

Title:
  gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed:
  (priv->child == NULL) called from
  DesktopManager::_destroyDesktopIcons() [desktopManager.js:234]

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Groovy:
  Fix Committed
Status in gnome-shell-extension-desktop-icons source package in Groovy:
  Fix Committed
Status in gnome-shell source package in Hirsute:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Gnome Shell crashes at random times when the Desktop or home directory
  is modified, and the desktop-icons extension tries to refresh.

  https://errors.ubuntu.com/problem/fcc5c581fc0a8c2f8f68314fa383690423a3dc02

  [Test Case]

  Open a nautilus (Files) window and tap Ctrl+H repeatedly. The shell
  should not crash or freeze.

  [Where problems could occur]

  An extension with syntax errors may fail to load leaving the user with
  reduced shell functionality. A more faulty extension might crash the
  entire shell after loading, like this bug.

  [Other Info]

  See also bug 1898910

  ---

  Sorry, I missed what was happening when this crashed.  I'll try to
  catch it next time.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 30 08:38:45 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1879927] Re: Please merge wpa 2:2.9.0-13 (main) from Debian unstable (main)

2021-01-16 Thread Mathew Hodson

** Summary changed:

- Merge wpa 2:2.9.0-13 (main) from Debian unstable (main)
+ Please merge wpa 2:2.9.0-13 (main) from Debian unstable (main)

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

Title:
  Please merge wpa 2:2.9.0-13 (main) from Debian unstable (main)

Status in wpa package in Ubuntu:
  New

Bug description:
  Please merge wpa 2:2.9.0-13 (main) from Debian unstable (main)

  The Debian package carries some upstream cherry-picks that are nice to
  have in Ubuntu, plus the packaging updates.

  Sorry, I can't work on this merge myself.

  These Ubuntu changes can be dropped because they are already in Debian:
 * debian/patches/git_realtek_macrand.patch:
  - backport an upstream patch to fix issues with some realtek cards
when MAC address randomization is enabled (lp: #1867908)
 * SECURITY UPDATE: Incorrect indication of disconnection in certain
   situations
   - debian/patches/CVE-2019-16275.patch: silently ignore management
 frame from unexpected source address in src/ap/drv_callbacks.c,
 src/ap/ieee882_11.c.
   - CVE-2019-16275

  Remaining changes specific to Ubuntu:
 * debian/patches/wpa_service_ignore-on-isolate.patch: add
   IgnoreOnIsolate=yes so that when switching "runlevels" in oem-config
   will not kill off wpa and cause wireless to be unavailable on first
   boot.
 * debian/patches/session-ticket.patch: disable the TLS Session Ticket
   extension to fix auth with 802.1x PEAP on some hardware.

  Changelog entries since current groovy version 2:2.9-1ubuntu7:

  wpa (2:2.9.0-13) unstable; urgency=medium

* Apply upstream patches:
  - Avoid sending invalid mgmt frames at startup
  - Increase introspection buffer size for D-Bus

   -- Andrej Shadura   Tue, 19 May 2020 14:29:29
  +0200

  wpa (2:2.9.0-12) unstable; urgency=medium

* Add an upstream patch to fix the MAC randomisation issue with some cards
  (LP: #1867908).

   -- Andrej Shadura   Tue, 24 Mar 2020 11:13:16
  +0100

  wpa (2:2.9.0-11) unstable; urgency=medium

* Actually add autopkgtest for libwpa-client-dev and libwpa_test.c.

   -- Andrej Shadura   Sat, 07 Mar 2020 13:18:19
  +0100

  wpa (2:2.9.0-10) unstable; urgency=medium

* Rename the package with the client library to libwpa-client-dev.

   -- Andrej Shadura   Tue, 25 Feb 2020 20:19:52
  +0100

  wpa (2:2.9.0-9) unstable; urgency=medium

[ Terry Burton ]
* Build and install eapol_test in eapoltest package (Closes: #700870)

[ Didier Raboud ]
* Backport upstream patch to fix build with Debian's VERSION_STR.

[ Andrew Lee (李健秋) ]
* Build libwpa-dev binary package which contains a static
  libwpa_client library and the wpa_ctrl header with an example program.

[ Andrej Shadura ]
* Add a patch to provide the BIT() macro locally in wpa_ctrl.h.
* Patch the example to use stddef.h and wpa_ctrl.h from the global location.
* Add an autopkgtest for libwpa-dev and libwpa_test.c.

   -- Andrej Shadura   Tue, 25 Feb 2020 18:21:35
  +0100

  wpa (2:2.9.0-8) unstable; urgency=medium

* Reupload as 2.9.0 to undo an accidental experimental upload to
  unstable.

   -- Andrej Shadura   Sat, 22 Feb 2020 11:25:29
  +0300

  wpa (2:2.9-7) unstable; urgency=medium

* Apply upstream patches:
  - trace: handle binutils bfd.h breakage
  - Check for FT support when selecting FT suites (Closes: #942164)

   -- Andrej Shadura   Sat, 15 Feb 2020 16:42:04
  +0100

  wpa (2:2.9-6) unstable; urgency=medium

[ Debian Janitor ]
* Use secure URI in Homepage field.
* Move source package lintian overrides to debian/source.
* Use canonical URL in Vcs-Browser.
* Rely on pre-initialized dpkg-architecture variables.
* Update standards version to 4.4.1, no changes needed.

[ Andrej Shadura ]
* Disable CONFIG_DRIVER_MACSEC_QCA on kfreebsd.

   -- Andrej Shadura   Mon, 13 Jan 2020 16:28:58
  +0100

  wpa (2:2.9-5) unstable; urgency=medium

* Fix erroneously inverted logic in postinst.

   -- Andrej Shadura   Mon, 13 Jan 2020 10:48:26
  +0100

  wpa (2:2.9-4) unstable; urgency=medium

[ Helmut Grohne ]
* Fix FTCBFS: Don’t export CC=cc (Closes: #921998).

[ Andrej Shadura ]
* Don’t act in hostapd.postinst if we’re running in a chrootless root.
* Apply an upstream patch:
  - wpa_supplicant: Do not try to detect PSK mismatch during PTK rekeying.

   -- Andrej Shadura   Mon, 13 Jan 2020 10:37:10
  +0100

  wpa (2:2.9-3) unstable; urgency=medium

* Add pkg.wpa.nogui and noudeb build profiles.

   -- Andrej Shadura   Fri, 04 Oct 2019 11:47:15
  +0200

  wpa (2:2.9-2) unstable; urgency=medium

* SECURITY UPDATE:
  - AP mode PMF disconnection protection bypass.
More details:
 + https://w1.fi/security/2019-7/
Closes: #940080 (CVE-2019-16275)

   --

[Desktop-packages] [Bug 1639531] Re: GCC compiles programs to shared object instead of executable, preventing GUI file managers from executing programs

2021-01-16 Thread Sergey

20.10 bug still not fixed

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

Title:
  GCC compiles programs to shared object instead of executable,
  preventing GUI file managers from executing programs

Status in gcc-defaults:
  Unknown
Status in shared-mime-info:
  Unknown
Status in shared-mime-info package in Ubuntu:
  Triaged

Bug description:
  Release of Ubuntu being used
  

  Description:Ubuntu 16.10
  Release:16.10

  Version of the package being used
  =

  gcc:
    Installed: 4:6.1.1-1ubuntu2
    Candidate: 4:6.1.1-1ubuntu2
    Version table:
   *** 4:6.1.1-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status

  What was expected
  =

  Programs compiled using `gcc -o program program.c` should be runnable
  by double-clicking them from a GUI file manager.

  Compiling a simple program (`void main() { }`) using Xubuntu 16.04's
  current version of `gcc` (`gcc version 5.4.0 20160609 (Ubuntu
  5.4.0-6ubuntu1~16.04.2)`) produces the following output from
  `/usr/bin/file program`:

  program: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
  dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
  GNU/Linux 2.6.32, BuildID[sha1]=signature_here, not stripped

  This is correct behavior, allowing the executables to run from
  Nautilus and Thunar.

  What happened instead
  =

  Programs compiled using `gcc -o program program.c` are not runnable by
  double-clicking them from a GUI file manager, even though they are
  runnable from the terminal.

  Compiling a simple program (`void main() { }`) using the current
  version of `gcc` (`6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)`) produces
  the following output from `/usr/bin/file program`:

  program: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV),
  dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
  GNU/Linux 2.6.32, BuildID[sha1]=signature_here, not stripped

  The program is also identified as a "shared library" instead of an
  "executable" in Thunar, causing it to not be runnable from the GUI.
  Others are unable to run such programs from Nautilus.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc-defaults/+bug/1639531/+subscriptions

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

[Desktop-packages] [Bug 1912069] [NEW] app-notification style class does not appear correctly

2021-01-16 Thread Pojar Gheorghe–Ioan

Public bug reported:

app-notification style class show without transparency like in
attachment.

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


** Tags: visual-quality

** Attachment added: "incorect.png"
   
https://bugs.launchpad.net/bugs/1912069/+attachment/5453791/+files/incorect.png

** Tags added: visual-quality

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

Title:
  app-notification style class does not appear correctly

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  app-notification style class show without transparency like in
  attachment.

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

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

[Desktop-packages] [Bug 1900679] Re: [snap] chromium spams dmesg

2021-01-16 Thread Oliver Grawert

snap run --strace chromium

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

Title:
  [snap] chromium spams dmesg

Status in chromium-browser package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Incomplete

Bug description:
  [T okt   20 12:25:09 2020] audit: type=1326 audit(1603185912.099:210734): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:09 2020] audit: type=1326 audit(1603185912.099:210735): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:12 2020] audit: type=1326 audit(1603185915.095:210736): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:12 2020] audit: type=1326 audit(1603185915.095:210737): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:14 2020] audit: type=1326 audit(1603185917.419:210738): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:14 2020] audit: type=1326 audit(1603185917.419:210739): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5

  Things like these just get repeated endlessly and very often, making
  any potential debugging very annoying.

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

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

[Desktop-packages] [Bug 1908921] Re: No system tray detected by hp-systray

2021-01-16 Thread Christopher Hamer

This also affects seadrive and seafile clients. I also see this on hp-
systray and nextcloud. Enpass is not affected.

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

Title:
  No system tray detected by hp-systray

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed

Bug description:
  I have hp-systray -x as one of the startup applications when I login.
  This app exits with the following error:

  HPLIP Status service
  No system tray detected on this system.
  Unable to start, exiting.

  Once logged in, if I start hp-systray -x from the terminal it works
  fine. This started happening after updating gnome-shell-extension-
  appindicator from version 33-1 to version 33.1-0ubuntu0.20.04.1.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 21 11:41:23 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-06-10 (1655 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1857383] Re: Fractional scaling applies to both monitors when you only want it on one

2021-01-16 Thread Antonio Cardoso Martins

I continue to see this issue under ubuntu 20.10 and Wayland

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.10
Release:20.10
Codename:   groovy

$ loginctl
SESSION  UID USER   SEAT  TTY 
  2 1000 an-crd seat0 tty2

1 sessions listed.
$ loginctl show-session 2 -p Type
Type=wayland

It seemed that we would not see a fix for X11, but how about Wayland?

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

Title:
  Fractional scaling applies to both monitors when you only want it on
  one

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

Bug description:
  I have installed Ubuntu 20.04 about 2-3 weeks ago (for the single
  motive that has fractional scalling) and when activating fractional
  scalling worked fine, in the meantime i reinstalled again Ubuntu 20.04
  (laptop warranty issue) on same hardware but using the latest Ubuntu
  20.04 version and now when i activate fractional scalling it does not
  work anymore.

  The issue is that it basically zooms both the displays, i can explain
  best by attaching the printscreens and a picture with my phone on the
  same thing.You will see in the photo taken with the phone how it
  actually scales now and how the screenshots are taken...

  Let me know what logs/commands etc is needed to pinpoint this which i
  think is a regression.

  The monitor on which i want to scale is 4k and is connecting through DELL 
DA300 adapter through USB-C/Thunderbolt ( i have also tried using Dell Dock 
WD19 but same issue).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  GsettingsChanges: b'org.gnome.mutter' b'experimental-features' 
b"['scale-monitor-framebuffer']"
  InstallationDate: Installed on 2019-12-18 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191127)
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1
  Tags:  focal
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1900679] Re: [snap] chromium spams dmesg

2021-01-16 Thread Avamander

> Can someone who is experiencing this bug run an strace to determine
what argument chromium is trying to use with sched_setaffinity ?

I'm not sure how its possible to strace a snap container ran under a
specific user. Could you provide the command?

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

Title:
  [snap] chromium spams dmesg

Status in chromium-browser package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Incomplete

Bug description:
  [T okt   20 12:25:09 2020] audit: type=1326 audit(1603185912.099:210734): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:09 2020] audit: type=1326 audit(1603185912.099:210735): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:12 2020] audit: type=1326 audit(1603185915.095:210736): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:12 2020] audit: type=1326 audit(1603185915.095:210737): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:14 2020] audit: type=1326 audit(1603185917.419:210738): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:14 2020] audit: type=1326 audit(1603185917.419:210739): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5

  Things like these just get repeated endlessly and very often, making
  any potential debugging very annoying.

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

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

[Desktop-packages] [Bug 1900679] Re: [snap] chromium spams dmesg

2021-01-16 Thread Avamander

It doesn't break it visibly. I would prefer if it were allowed to set
its affinity, but if that can't be done, silencing is a must. This is
incredibly spammy.

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

Title:
  [snap] chromium spams dmesg

Status in chromium-browser package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Incomplete

Bug description:
  [T okt   20 12:25:09 2020] audit: type=1326 audit(1603185912.099:210734): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:09 2020] audit: type=1326 audit(1603185912.099:210735): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:12 2020] audit: type=1326 audit(1603185915.095:210736): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:12 2020] audit: type=1326 audit(1603185915.095:210737): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:14 2020] audit: type=1326 audit(1603185917.419:210738): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:14 2020] audit: type=1326 audit(1603185917.419:210739): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5

  Things like these just get repeated endlessly and very often, making
  any potential debugging very annoying.

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

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

[Desktop-packages] [Bug 1910598] Re: Ejecting a Blanc CD/DVD/BluRay-R disk writes to it.

2021-01-16 Thread Guillaume Bottex

Unfortunately, I don't have any crash report for udisk in /var/crash.

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

Title:
  Ejecting a Blanc CD/DVD/BluRay-R disk writes to it.

Status in caja package in Ubuntu:
  New
Status in udisks2 package in Ubuntu:
  Incomplete

Bug description:
  I used the "eject" contextual menu on the icon of a blank Bluray-R on
  the caja desktop, and I got a message saying that I need to wait for
  data to be written on the disc before being able to remove it safely
  (same message as when trying to eject an usb stick, when some data
  syncing is left to be done).

  Afterwards, when I tried to burn data to it, the app (k3b) told that
  the disc was not empty thus not writeable.

  This bug cost me a brand new Bluray-R M-Disc of 100GB, which is a
  quite pricey medium.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: caja 1.20.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-129.132-generic 4.15.18
  Uname: Linux 4.15.0-129-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Jan  7 22:42:25 2021
  SourcePackage: caja
  UpgradeStatus: Upgraded to bionic on 2019-02-16 (691 days ago)

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

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

[Desktop-packages] [Bug 1912055] [NEW] FF screensharing works under Plasma but not Gnome

2021-01-16 Thread monochromec

Public bug reported:

Firefox is 84.0.2
xdg-desktop-portal is 1.8.0-1 (same as xdg-desktop-portal-gtk)
gnome-shell is 3.38.1-1ubuntu1.1
plasma-desktop is 5.19.5-0ubuntu1

(all packages per latest Groovy versions)

Another hint: Running FF offers me a selection of app windows when
starting to share the screen (for example in a Jitsi session), doing the
same under Gnome only allows me to share my entire screen.

Happy to provide more info, just let me know.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xdg-desktop-portal-gtk 1.8.0-1
ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
Uname: Linux 5.8.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Sat Jan 16 14:25:57 2021
InstallationDate: Installed on 2017-08-31 (1233 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: xdg-desktop-portal-gtk
UpgradeStatus: Upgraded to groovy on 2020-10-23 (84 days ago)

** Affects: xdg-desktop-portal-gtk (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  FF screensharing works under Plasma but not Gnome

Status in xdg-desktop-portal-gtk package in Ubuntu:
  New

Bug description:
  Firefox is 84.0.2
  xdg-desktop-portal is 1.8.0-1 (same as xdg-desktop-portal-gtk)
  gnome-shell is 3.38.1-1ubuntu1.1
  plasma-desktop is 5.19.5-0ubuntu1

  (all packages per latest Groovy versions)

  Another hint: Running FF offers me a selection of app windows when
  starting to share the screen (for example in a Jitsi session), doing
  the same under Gnome only allows me to share my entire screen.

  Happy to provide more info, just let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xdg-desktop-portal-gtk 1.8.0-1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sat Jan 16 14:25:57 2021
  InstallationDate: Installed on 2017-08-31 (1233 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: xdg-desktop-portal-gtk
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (84 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1912055/+subscriptions

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

[Desktop-packages] [Bug 1905825] Re: [SRU] Disable CRTCs when system becomes headless

2021-01-16 Thread Amr Ibrahim

mutter 3.36.8 is now out with the desired fixes:
https://gitlab.gnome.org/GNOME/mutter/-/blob/gnome-3-36/NEWS

It can be SRUed in Focal.

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

Title:
  [SRU] Disable CRTCs when system becomes headless

Status in HWE Next:
  New
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Focal:
  New
Status in mutter source package in Groovy:
  New
Status in mutter source package in Hirsute:
  In Progress

Bug description:
  [Impact]
  On new Intel SoCs, after all connectors are unplugged and the system becomes 
headless, it cannot detect monitor hotplug event from type-c port.

  [Fix]
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1561

  Based on "drm/i915 Intel GFX Driver, Hotplug" [1]:
  "Finally, the userspace is responsible for triggering a modeset upon 
receiving the hotplug uevent, disabling or enabling the crtc as needed."

  [Test]
  Unplug type-c monitor from an Intel Tiger Lake desktop. Replug the monitor 
back, monitor is blank.
  With the fix applied, the system can detect monitor again.

  [Where problems could occur]
  This fix disables CRTCs when there's no monitor, if driver has trouble 
dealing with it, we may see something break.

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

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

[Desktop-packages] [Bug 1912052] [NEW] external headset microphone not working on Ubuntu 20.10 (not even wired, cable headset)

2021-01-16 Thread crysman

Public bug reported:

Recently, external microphone has stopped working while using classic
wired audio combo jack headset.

Basics:

1) Headset's microphone works fine both in MS Windows on the same machine and 
on older Xubuntu on another machine.
2) Internal laptop mic works normally.
3) Yes, I have mic unmuted in settings.

I've followed whole step1 from this troubleshoot guide:
https://help.ubuntu.com/community/SoundTroubleshootingProcedure

Did not help.

There are more information with screenshots here:
https://askubuntu.com/questions/1305942/external-headset-microphone-not-
working-on-ubuntu-20-10-not-even-wired-cable-h:

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.2-1ubuntu2.1
ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
Uname: Linux 5.8.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  crysman2301 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 16 13:31:13 2021
InstallationDate: Installed on 2020-06-19 (210 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago)
dmi.bios.date: 07/17/2020
dmi.bios.release: 1.5
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.05
dmi.board.name: Caboom_IL
dmi.board.vendor: IL
dmi.board.version: V1.05
dmi.chassis.type: 31
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.05
dmi.ec.firmware.release: 1.2
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05:
dmi.product.family: Spin 5
dmi.product.name: Spin SP513-54N
dmi.product.sku: 
dmi.product.version: V1.05
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug groovy

** Description changed:

  Recently, external microphone has stopped working while using classic
  wired audio combo jack headset.
  
  Basics:
  
  1) Headset's microphone works fine both in MS Windows on the same machine and 
on older Xubuntu on another machine.
  2) Internal laptop mic works normally.
  3) Yes, I have mic unmuted in settings.
  
  I've followed whole step1 from this troubleshoot guide:
  https://help.ubuntu.com/community/SoundTroubleshootingProcedure
  
  Did not help.
  
- There are more informationhttps://askubuntu.com/questions/1305942
- /external-headset-microphone-not-working-on-ubuntu-20-10-not-even-wired-
- cable-h with screenshot here:
+ There are more information with screenshots here:
+ https://askubuntu.com/questions/1305942/external-headset-microphone-not-
+ working-on-ubuntu-20-10-not-even-wired-cable-h:
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  crysman2301 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  crysman2301 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 16 13:31:13 2021
  InstallationDate: Installed on 2020-06-19 (210 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago)
  dmi.bios.date: 07/17/2020
  dmi.bios.release: 1.5
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.name: Caboom_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.05
  dmi.chassis.type: 31
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05:
  dmi.product.family: Spin 5
  dmi.product.name: Spin SP513-54N
  dmi.product.sku: 
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

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

Title:
  external headset microphone not working on Ubuntu 20.10 (not even
  wired, cable headset)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Recently, external microphone has stopped working while using classic
  wired audio combo jack headset.

  Basics:

  1) Headset's microphone works fine both in MS Windows on the same machine and 
on older Xubuntu on another machine.
  2) Internal laptop mic works normally.
  3) Yes, I have mic unmuted in settings.

  I've followed whole step1 from this troubleshoot guide:
  https://help.ubuntu.com/community/SoundTroubleshootingProcedure

  Did not

[Desktop-packages] [Bug 1911133] Re: [Regression] RS482M [Mobility Radeon Xpress 200]

2021-01-16 Thread Six

I can also confirm issues with the same graphics card on two Dell
Inspirion 1501 laptops that occurred around the same time after a recent
update.

[AMD/ATI] RS482M [Mobility Radeon Xpress 200] - Ubuntu Mate 20.04

Issues include:-
> Message of error occurred with "mate-session-check-accelerated-gl-helper" 
> after boot.
> Reports of r300 module missing then segfault when playing video in VLC
> Segfault when you run glxinfo
> WebGL items not working in Firefox.


** Attachment added: "vlc.crash"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1911133/+attachment/5453666/+files/vlc.crash

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

Title:
  [Regression] RS482M [Mobility Radeon Xpress 200]

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  RS482M [Mobility Radeon Xpress 200] crash gnome desktop at startup with Oh 
no! Something has gone wrong after latest updates
  It works fine before them
  System: Hp Nx6325
  Video: Advanced Micro Deviceº Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 
200] (prog-if 00 [VGA controller])

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

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

[Desktop-packages] [Bug 1911133] Re: [Regression] RS482M [Mobility Radeon Xpress 200]

2021-01-16 Thread Launchpad Bug Tracker

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

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

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

Title:
  [Regression] RS482M [Mobility Radeon Xpress 200]

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  RS482M [Mobility Radeon Xpress 200] crash gnome desktop at startup with Oh 
no! Something has gone wrong after latest updates
  It works fine before them
  System: Hp Nx6325
  Video: Advanced Micro Deviceº Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 
200] (prog-if 00 [VGA controller])

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

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

[Desktop-packages] [Bug 1908167] Autopkgtest regression report (pulseaudio/1:13.99.2-1ubuntu2.3)

2021-01-16 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted pulseaudio (1:13.99.2-1ubuntu2.3) for 
groovy have finished running.
The following regressions have been reported in tests triggered by the package:

openjdk-8/8u275-b01-0ubuntu1~20.10 (armhf)


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

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

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

Thank you!

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

Title:
  [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be
  selected automatically if there is no internal mic

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

Bug description:
  [Impact]
  On the Dell AIO machines, there is no internal mic, after plugging a
  headset, users expect the headset-mic or headphone-mic could be selected
  automatically. But with the current rule, the headset-mic/headphone-mic will 
not be selected automatically and even users manually select them, they will 
not show up in the gnome sound setting, and users could not record sound by 
headset-mic/headphone-mic.

  [Fix]
  backport a patch from pulseaudio mergerequest, the patch is going to be
  merged to pulseaudio 14.1. This patch could be backported to hirsute without 
any change, but need to be changed if backport it to groovy and focal.

  [Test]
  With the old pulseaudio (prior to 1:13.99.1-1ubuntu3.10), plugging in a 
headset to the problematic Dell AIO machine will not automatically select 
headset-mic/headphone-mic, and they also do not show up in Gnome sound 
settings, leading to failure to record any sound.

  With the new proposed package, on those Dell AIO, plug a headset, open
  the gnome sound setting, the headset-mic is selected automatically,
  use the headset-mic to record the sound, the sound could be recorded
  and the sound quality is good.

  [Where problems could occur]
  This patch could change the policy of audio device switching, it will not
  affect all audio devices, but only the devices which has AVAIL_UNKNOWN 
available status, that means it has possibility to introduce the regression on 
headphone-mic ,headset-mic, internal mic and internal speaker's switching since 
they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, 
the input device will not switch to internal mic automatically or after unplug 
the headphone, the output device will not switch to internal speaker 
automatically. But this possibility is very low, we have tested the patch on 
many Dell and Lenovo machines, all worked well.

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

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

[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340

2021-01-16 Thread Meluco

@therealsujitk @ubuntu-iremonger

It's my fault.

WiFi failed because I manually removed all linux-5.8.0-34 packages when
nvidia brokes. When reinstall linux packages I forgot install linux-
modules-extra-5.8.0-34-generic.

I install it and mark it as 'auto' and WiFi comes again.

Thank you everybody.

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

Title:
  DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released

Bug description:
  [Impact]
  nvidia-340 dkms fails to build against the current HWE kernel in focal, 
regressing the user experience.

  [Test case]
  Install the update, check that the dkms builds and works.

  [Where things could go wrong]
  The changes only add support for newer kernels so that the module can build, 
and it's identical to what's in groovy. In theory it could break the build 
against 5.4 but that's highly unlikely.

  
  --

  Last linux kernel update "linux-headers-5.8.0-34-generic" broke
  nvidia-340 driver and Desktop access. In make log:

  [...]
  echo >&2; \
  echo >&2 "  ERROR: Kernel configuration is invalid."; \
  echo >&2 " include/generated/autoconf.h or include/config/auto.conf 
are missing.";\
  echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix 
it.";\
  echo >&2 ;
  [...]

  Full DKMS log file attacked.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-04 (64 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Gigabyte Technology Co., Ltd. H81M-D3H
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-59-generic N/A
   linux-backports-modules-5.4.0-59-generic  N/A
   linux-firmware1.187.7
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 01/20/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: H81M-D3H
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-04 (64 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Gigabyte Technology Co., Ltd. H81M-D3H
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-59-generic N/A
   linux-backports-modules-5.4.0-59-generic  N/A
   linux-firmware1.187.7
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True

[Desktop-packages] [Bug 1900906] Re: Can't use dead keys or input e.g. Chinese characters in GNOME shell

2021-01-16 Thread Gunnar Hjalmarsson

On 2021-01-16 08:48, Fernando wrote:
> The bug persists with accented characters if the dead key is the first
> character you type. I mean, open the overview, type "á" and you see just
> "a". Then type another "á" and it shows correctly. Same if you type
> "lá", the accent shows correctly because the dead key wasn't the first
> thing you typed.

That happens to me if the search field is not focused when you start
typing, which it seems to not be initially by default. If I first click
the search field, also the first letter can be typed using a dead key.

Can you maybe report it as a separate issue, preferably upstream:

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

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

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

Title:
  Can't use dead keys or input e.g. Chinese characters in GNOME shell

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

Bug description:
  I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. 
Under X, if I try to input an accentuated character, such as á or ü, in places 
like the search field in the overview or when writing a folder name in the app 
grid, nothing appears. Under Wayland, it fails each time on the first input of 
an accentuated character, then it works.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-01 (174 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Package: ibus
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-09-29 (22 days ago)
  UserGroups: sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1891739] Re: 4. and 5. mouse-button on thumb does not react during save-dialogue in LO

2021-01-16 Thread Matthias Sprau

Problem still observed with:

LibreOffice
Version: 6.4.6.2
Build-ID: 1:6.4.6-0ubuntu0.20.04.1

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

Title:
  4. and 5. mouse-button on thumb does not react during save-dialogue in
  LO

Status in libreoffice package in Ubuntu:
  New

Bug description:
  While "saving" the mouse-buttons don't react to browse in the menu structure 
as usual e.g. in a filebrowser like nautilus.
  (But I'm not sure if it has something to do with the gnome-shell of Ubuntu.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-core 1:6.4.4-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 15 09:37:11 2020
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2020-05-23 (83 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   LD_LIBRARY_PATH=
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2021-01-16 Thread Sander Jonkers

I bumped into the same: disk full.

After inspection:
/var/log/syslog 20GB
/var/log/syslog.1 60GB

... removing /var/log/syslog.1 same some disk space free, but
/var/log/syslog keep on growing, so I'm going to reboot.


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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  Uname: Linux 5.4.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Dec 16 18:56:56 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-01 (258 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1901829] Re: thunderbird fails to open, xml parse error

2021-01-16 Thread Simon Iremonger

This seems to be related to important suggestion to merge packaging
efforts as best as possible:-

https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1894090

...Not sure if merging-efforts will help with this specific bug, or
otherwise, Debian can be learned-from somehow-or-other!.

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

Title:
  thunderbird fails to open, xml parse error

Status in thunderbird package in Ubuntu:
  Confirmed
Status in thunderbird source package in Groovy:
  Confirmed

Bug description:
  launching thunderbird opens a small browser window displaying the
  following error:

  XML Parsing Error: undefined entity
  Location: chrome://messenger/content/messenger.xhtml
  Line Number 905, Column 3:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+subscriptions

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

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

[Desktop-packages] [Bug 1900167] Re: gnome-software Unable to install updates

[Desktop-packages] [Bug 1904597] Re: Minimizing a fullscreen window causes Graphical issues

[Desktop-packages] [Bug 1912083] [NEW] the icons are longer

[Desktop-packages] [Bug 1905054]

[Desktop-packages] [Bug 1867996] Re: Segfault in app_indicator_set_icon_full [patch attached]

[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector

[Desktop-packages] [Bug 1911432] Re: [SRU] wslu 3.2.1-0ubuntu1 to focal

[Desktop-packages] [Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:2

[Desktop-packages] [Bug 1879927] Re: Please merge wpa 2:2.9.0-13 (main) from Debian unstable (main)

[Desktop-packages] [Bug 1639531] Re: GCC compiles programs to shared object instead of executable, preventing GUI file managers from executing programs

[Desktop-packages] [Bug 1912069] [NEW] app-notification style class does not appear correctly

[Desktop-packages] [Bug 1900679] Re: [snap] chromium spams dmesg

[Desktop-packages] [Bug 1908921] Re: No system tray detected by hp-systray

[Desktop-packages] [Bug 1857383] Re: Fractional scaling applies to both monitors when you only want it on one

[Desktop-packages] [Bug 1900679] Re: [snap] chromium spams dmesg

[Desktop-packages] [Bug 1900679] Re: [snap] chromium spams dmesg

[Desktop-packages] [Bug 1910598] Re: Ejecting a Blanc CD/DVD/BluRay-R disk writes to it.

[Desktop-packages] [Bug 1912055] [NEW] FF screensharing works under Plasma but not Gnome

[Desktop-packages] [Bug 1905825] Re: [SRU] Disable CRTCs when system becomes headless

[Desktop-packages] [Bug 1912052] [NEW] external headset microphone not working on Ubuntu 20.10 (not even wired, cable headset)

[Desktop-packages] [Bug 1911133] Re: [Regression] RS482M [Mobility Radeon Xpress 200]

[Desktop-packages] [Bug 1911133] Re: [Regression] RS482M [Mobility Radeon Xpress 200]

[Desktop-packages] [Bug 1908167] Autopkgtest regression report (pulseaudio/1:13.99.2-1ubuntu2.3)

[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340

[Desktop-packages] [Bug 1900906] Re: Can't use dead keys or input e.g. Chinese characters in GNOME shell

[Desktop-packages] [Bug 1891739] Re: 4. and 5. mouse-button on thumb does not react during save-dialogue in LO

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

[Desktop-packages] [Bug 1901829] Re: thunderbird fails to open, xml parse error

29 matches

Site Navigation

Mail list logo

Footer information