date:20210419

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

** Changed in: lm-sensors (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Fans switching on and off every 10 seconds after update to kernel
  5.8.0-34

Status in linux-signed-hwe-5.8 package in Ubuntu:
  Expired
Status in lm-sensors package in Ubuntu:
  Expired
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid

Bug description:
  After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel
  5.8.0-34 the fan on my machine started switching on (for an instant)
  and off every 10 seconds even when idle with CPU at 48/50°C.

  Switching back to previous kernel solves temporary the problem, i.e.
  fans are always off with light desktop work.

  The new behavior is really annoying and I guess not healthy for the
  fans.

  I'm on latest Dell bios, with every other package updated.

  Di something in the thermal policies change between those two kernels?
  Is it possible to go back to previous behavior ?

  Thanks in advance for help

  Machine: Dell Precison 7540, intel i7-9750

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  7 17:14:54 2021
  InstallationDate: Installed on 2020-05-06 (246 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1910562/+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 1910562] Re: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34

[Expired for linux-signed-hwe-5.8 (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: linux-signed-hwe-5.8 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Fans switching on and off every 10 seconds after update to kernel
  5.8.0-34

Status in linux-signed-hwe-5.8 package in Ubuntu:
  Expired
Status in lm-sensors package in Ubuntu:
  Expired
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid

Bug description:
  After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel
  5.8.0-34 the fan on my machine started switching on (for an instant)
  and off every 10 seconds even when idle with CPU at 48/50°C.

  Switching back to previous kernel solves temporary the problem, i.e.
  fans are always off with light desktop work.

  The new behavior is really annoying and I guess not healthy for the
  fans.

  I'm on latest Dell bios, with every other package updated.

  Di something in the thermal policies change between those two kernels?
  Is it possible to go back to previous behavior ?

  Thanks in advance for help

  Machine: Dell Precison 7540, intel i7-9750

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  7 17:14:54 2021
  InstallationDate: Installed on 2020-05-06 (246 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1910562/+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 1881941] Re: Ubuntu dock behaves crazy when hidden at the bottom of the screen

2021-04-19 Thread Michael Erdely

For myself, I'm only seeing this issue when IntelliJ is open and over
the dock location, versions 2020.3 and 2021.1 thus far. I can't
reproduce with any other application.

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

Title:
  Ubuntu dock behaves crazy when hidden at the bottom of the screen

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

Bug description:
  I had put the dock on the bottom of the screen and also set to hide 
automatically. 
  The dock works fine as expected but there are sometimes (actually like 90% of 
the time) that it behaves weird when I try to access it with the mouse pointer, 
the dock starts to bounce quickly without stopping and then it's kind of hard 
to press the icons on it (when I'm lucky I can click the icon), other times I 
had to move away the pointer from the bottom and then move it back to access 
the dock. 
  I made a video of it although it's very short but you can see for a brief of 
time how the dock starts to bounce.
  I haven't installed new packages or applications that change the behaviour of 
the dock in any way.

  
  tavoge@e6430s:~$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  
  tavoge@e6430s:~$ apt-cache policy xorg
  xorg:
Instalados: 1:7.7+19ubuntu14
Candidato:  1:7.7+19ubuntu14
Tabla de versión:
   *** 1:7.7+19ubuntu14 500
  500 http://mx.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  3 11:40:48 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:057d]
  InstallationDate: Installed on 2020-05-29 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Latitude E6430s
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 0XHTPW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd11/30/2018:svnDellInc.:pnLatitudeE6430s:pvr01:rvnDellInc.:rn0XHTPW:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430s
  dmi.product.sku: Latitude E6430s
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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-shell-extension-ubuntu-dock/+bug/1881941/+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 1925095] Re: GNOME Desktop selection is misallinged with the mouse on 21.04-dev

2021-04-19 Thread Matheus Reich

The bug is easily noticeable on the video attached here.

** Attachment added: "Bug happening while being recorded."
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1925095/+attachment/5489924/+files/2021-04-19%2021-58-16.mkv

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

Title:
  GNOME Desktop selection is misallinged with the mouse on 21.04-dev

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When dragging the mouse while selected on the Desktop, the selection
  box is misaligned with the mouse pointer. The issue only started
  happening on 21.04 after upgrading from 20.04 to the dev version of
  the OS.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 19 22:00:22 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-12-28 (112 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-04-13 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1925095/+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 1925095] [NEW] GNOME Desktop selection is misallinged with the mouse on 21.04-dev

2021-04-19 Thread Matheus Reich

Public bug reported:

When dragging the mouse while selected on the Desktop, the selection box
is misaligned with the mouse pointer. The issue only started happening
on 21.04 after upgrading from 20.04 to the dev version of the OS.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.4-1ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
Uname: Linux 5.11.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 19 22:00:22 2021
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2020-12-28 (112 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 LANG=pt_BR.UTF-8
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to hirsute on 2021-04-13 (6 days ago)

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


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

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

Title:
  GNOME Desktop selection is misallinged with the mouse on 21.04-dev

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When dragging the mouse while selected on the Desktop, the selection
  box is misaligned with the mouse pointer. The issue only started
  happening on 21.04 after upgrading from 20.04 to the dev version of
  the OS.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 19 22:00:22 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-12-28 (112 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-04-13 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1925095/+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 1925057] Re: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound

2021-04-19 Thread Hui Wang

when problems happens, please run:
$sudo sh -c 'echo 1 > /sys/module/snd_hda_codec/parameters/dump_coef'
Then run alsa-info to collect an alsa-info.txt (bad)


Then poweroff the machine and poweron it, make sure the audio works normally, 
run:
$sudo sh -c 'echo 1 > /sys/module/snd_hda_codec/parameters/dump_coef'
Then run alsa-info to collect an alsa-info.txt (good)

and upload the alsa-info.txt-bad and alsa-info.txt-good, let us compare
them.

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

Title:
  [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or
  crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,

  I'm using Ubuntu together with Windows on my laptop.

  If I boot in Ubuntu after Windows sound doesn't work well (instead of
  system sounds I can hear only shot noise). To fix the issue I need to
  completely shut down the system (call Power Off via Ubuntu GUI) and
  then boot again in Ubuntu. Please note, that reboot (called via Ubuntu
  GUI) doesn't help to fix the issue.

  Expected result: sound works well regardless of boot history.
  Actual result: every time I boot in Ubuntu after Windows sound doesn't work.

  Issue occurrence: 100%.

  Environment:
  $ lsb_release -rd
  Description: Ubuntu Hirsute Hippo (development branch)
  Release: 21.04
  $ uname -a
  Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux

  Thank you in advance!

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gluttton   1640 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 19 19:37:56 2021
  InstallationDate: Installed on 2021-03-06 (43 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 
'module-null-sink' was still loaded!
   кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded.
   кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded.
   кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded.
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or 
crackling sound
  UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago)
  dmi.bios.date: 01/14/2021
  dmi.bios.release: 1.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DHCN31WW
  dmi.board.asset.tag: ���
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: ���
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga Slim 7 14IIL05
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05:
  dmi.product.family: Yoga Slim 7 14IIL05
  dmi.product.name: 82A1
  dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05
  dmi.product.version: Yoga Slim 7 14IIL05
  dmi.sys.vendor: LENOVO

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

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

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

2021-04-19 Thread Bug Watch Updater

** Changed in: libreoffice-dictionaries (Debian)
   Status: Unknown => Fix Released

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

Title:
  en-gb thesaurus is missing

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1838038] Re: [snap] Snapped apps do not work with .local mdns/avahi name resolution

2021-04-19 Thread Till Kamppeter

Applied a Snap-side workaround to my Snaps which implements the fix
presented in the snapcraft.io thread mentioned in my previous post:

CUPS Snap:

https://github.com/OpenPrinting/cups-snap/commit/f241f3f02

PostScript Printer Application:

https://github.com/OpenPrinting/ps-printer-app/commit/1f6ca389

Note that doing this on any Snap which needs it in the future is
awkward, so we really need to fix core18 and core20.

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

Title:
  [snap] Snapped apps do not work with .local mdns/avahi name resolution

Status in snap-core18:
  New
Status in snap-core20:
  New
Status in snapd:
  Triaged
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  (initially reported at https://forum.snapcraft.io/t/chromium-does-not-
  work-with-local-mdns-avahi-name-resolution/12483)

  The current chromium snap does not allow to open any .local urls.

  This is most likely caused by https://forum.snapcraft.io/t/no-mdns-
  support-in-snaps-should-core-have-a-modified-nsswitch-conf/7603.

  With the removal of the chromium deb and the switch to a snap-only
  deployment for this browser this is a pretty solid regression that
  should be addressed…

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

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

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

2021-04-19 Thread Eric Van Horn

I should probably clarify - I know that these three packages were part
of the core extensions. However, I noticed that the timestamps for all
of the core extensions were the same _except_ for those three. I
reinstalled the gnome-shell-extensions package make sure they were
correct, but those three extensions were not updated, or at least their
timestamps did not change. I then purged the package and observed that
those three extensions were still present, so I deleted them and
reinstalled the gnome-shell-extensions package. I expected to see those
three extensions restored, but they were not reinstalled.

As for the non-core extensions, I was planning to test them one at a
time, but after taking the steps above I could not replicate the issue.
Since that time I have not had any problems with gnome-shell crashing.
If I could not repeat the issue with them installed, it seemed moot to
removing the extensions one by one.

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

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

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

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

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

  ---

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

    MUTTER_SYNC=1

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

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

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

[Desktop-packages] [Bug 1923305] Re: LibreOffice 6.4 OpenType Features unusable

2021-04-19 Thread Heather Ellsworth

Thank you for your suggestion to cherrypick this onto the 6.4 branch. We
try to keep the branches as in line with upstream as possible so if you
would like to use the newer 7.X then I suggest you try the snap out:
https://snapcraft.io/libreoffice

Remove the libreoffice deb and install the snap with:
$ sudo apt purge libreoffice*
$ sudo snap install libreoffice

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

Title:
  LibreOffice 6.4 OpenType Features unusable

Status in libreoffice package in Ubuntu:
  New

Bug description:
  When using OpenType features (Format - Character - Feature) from a
  capable font like EB Garamond 12, LibreOffice automatically enables a
  fractional style, which essentially makes all numerics unusable, and
  there's no obvious way to disable this in the GUI once you've opened
  the Features dialog.

  There are two workaround, as all OpenType features get disabled when
  selecting another font, and back again.

  And, of course, one can remove :frac=1 manually from the font name
  field.

  This has however been fixed in LibreOffice 7.0 onward, but somehow
  wasn't cherrypicked into 6.4.x, even though the change seems trivial:

  
https://github.com/LibreOffice/core/commit/d28c9d56df8a2629321bda116a6d2dcfa587d160

  Please consider including this cherrypick in a future package for
  Ubuntu Focal.

  The patch won't apply directly due to a filename typo getting
  corrected, which needs to be uncorrected in the patch:

  vcl/source/font/OpenTypeFeatureDefinitionList.cxx
  vcl/source/font/OpenTypeFeatureDefinitonList.cxx

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

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

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

2021-04-19 Thread Tanner McLoed

Since I applied the latest updates I've not had the issue. I will give
it a few days and if the problem arises I will apply your patch and see
if that resolves it.

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 17 15:06:08 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2021-04-16 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1838038] Re: [snap] Snapped apps do not work with .local mdns/avahi name resolution

2021-04-19 Thread Till Kamppeter

Adding snap-core18 and snap-core20 tasks as it is a problem of core18
and core20 missing support for looking up host names via mDNS/DNS-SD.
The problem occurs also in other Snaps not only in the Chromium Browser
Snap. Therefore the fix for this bug is essentially important and
urgently needed.

Note that installing nscd is only a workaround, which can cause security
problems (aacording to Jamie Strandboge) when seeding it and also it
would only help Ubuntu users.

Especially also the CUPS Snap (https://github.com/OpenPrinting/cups-
snap) and Printer Application Snaps (the way to snap printer and scanner
drivers, required for the CUPS Snap, currently, we have the PostScript
Printer Application, https://github.com/OpenPrinting/ps-printer-app) are
affected as they internally use mDNS .local addresses to access network
devices. As we want to switch over printing in Ubuntu to the CUPS Snap
and also want to give manufacturers a way to publish distribution-
independent snapped printer/scanner drivers this problem needs to get
urgently fixed.

A suggested fix can be found in this thread:

https://forum.snapcraft.io/t/no-mdns-support-in-snaps-should-core-have-a
-modified-nsswitch-conf/

The /etc/nsswitch.conf file needs a simple change, replacing the line

hosts:  files dns

by

hosts:  files mdns4_minimal [NOTFOUND=return] dns

and the libnss-mdns package (provides libnss_mdns*.so*) needs to get
installed into the coreXX images.

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

Title:
  [snap] Snapped apps do not work with .local mdns/avahi name resolution

Status in snap-core18:
  New
Status in snap-core20:
  New
Status in snapd:
  Triaged
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  (initially reported at https://forum.snapcraft.io/t/chromium-does-not-
  work-with-local-mdns-avahi-name-resolution/12483)

  The current chromium snap does not allow to open any .local urls.

  This is most likely caused by https://forum.snapcraft.io/t/no-mdns-
  support-in-snaps-should-core-have-a-modified-nsswitch-conf/7603.

  With the removal of the chromium deb and the switch to a snap-only
  deployment for this browser this is a pretty solid regression that
  should be addressed…

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-core18/+bug/1838038/+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 1925062] Re: package firefox 75.0+build3-0ubuntu1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2021-04-19 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: fsys-tarfile-error

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

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

Title:
  package firefox 75.0+build3-0ubuntu1 failed to install/upgrade: dpkg-
  deb --fsys-tarfile subprocess returned error exit status 2

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  I have been having trouble with system locking up and crashing.
  I installed a second copy of Ubuntu 20.04 alongside on the same hard drive - 
just the basic features. 
  I tested this on the internet and all seemed well.
  Firefox wanted to update - failed to install.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: firefox 75.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jackofalltrades   1294 F pulseaudio
   /dev/snd/controlC0:  jackofalltrades   1294 F pulseaudio
  BuildID: 20200403170909
  CasperMD5CheckResult: skip
  Channel: Unavailable
  Date: Mon Apr 19 18:25:46 2021
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-04-18 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.1.254 dev enp5s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp5s0 scope link metric 1000 
   192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.101 metric 
100
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 75.0+build3-0ubuntu1 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5409
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5409:bd01/07/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1925062/+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 1838038] Re: [snap] Snapped apps do not work with .local mdns/avahi name resolution

2021-04-19 Thread Till Kamppeter

** Also affects: snap-core20
   Importance: Undecided
   Status: New

** Also affects: snap-core18
   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/1838038

Title:
  [snap] Snapped apps do not work with .local mdns/avahi name resolution

Status in snap-core18:
  New
Status in snap-core20:
  New
Status in snapd:
  Triaged
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  (initially reported at https://forum.snapcraft.io/t/chromium-does-not-
  work-with-local-mdns-avahi-name-resolution/12483)

  The current chromium snap does not allow to open any .local urls.

  This is most likely caused by https://forum.snapcraft.io/t/no-mdns-
  support-in-snaps-should-core-have-a-modified-nsswitch-conf/7603.

  With the removal of the chromium deb and the switch to a snap-only
  deployment for this browser this is a pretty solid regression that
  should be addressed…

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-core18/+bug/1838038/+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 1925067] [NEW] Power Statistics has bad colors for dark color scheme

2021-04-19 Thread AndreK

Public bug reported:

When viewing graphs; the X and Y axis numbers are barely visible with the Dark 
color scheme.
Screenshot attached.

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

** Attachment added: "Screenshot from 2021-04-19 20-38-09.png"
   
https://bugs.launchpad.net/bugs/1925067/+attachment/5489877/+files/Screenshot%20from%202021-04-19%2020-38-09.png

** Summary changed:

- Power Statistics had bad colors for dark color scheme
+ Power Statistics has bad colors for dark color scheme

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

Title:
  Power Statistics has bad colors for dark color scheme

Status in gnome-power-manager package in Ubuntu:
  New

Bug description:
  When viewing graphs; the X and Y axis numbers are barely visible with the 
Dark color scheme.
  Screenshot attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1925067/+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 1925062] Re: package firefox 75.0+build3-0ubuntu1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2021-04-19 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package firefox 75.0+build3-0ubuntu1 failed to install/upgrade: dpkg-
  deb --fsys-tarfile subprocess returned error exit status 2

Status in firefox package in Ubuntu:
  New

Bug description:
  I have been having trouble with system locking up and crashing.
  I installed a second copy of Ubuntu 20.04 alongside on the same hard drive - 
just the basic features. 
  I tested this on the internet and all seemed well.
  Firefox wanted to update - failed to install.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: firefox 75.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jackofalltrades   1294 F pulseaudio
   /dev/snd/controlC0:  jackofalltrades   1294 F pulseaudio
  BuildID: 20200403170909
  CasperMD5CheckResult: skip
  Channel: Unavailable
  Date: Mon Apr 19 18:25:46 2021
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-04-18 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.1.254 dev enp5s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp5s0 scope link metric 1000 
   192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.101 metric 
100
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 75.0+build3-0ubuntu1 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5409
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5409:bd01/07/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1925062/+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 1925062] [NEW] package firefox 75.0+build3-0ubuntu1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2021-04-19 Thread Simon Denham

Public bug reported:

I have been having trouble with system locking up and crashing.
I installed a second copy of Ubuntu 20.04 alongside on the same hard drive - 
just the basic features. 
I tested this on the internet and all seemed well.
Firefox wanted to update - failed to install.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: firefox 75.0+build3-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jackofalltrades   1294 F pulseaudio
 /dev/snd/controlC0:  jackofalltrades   1294 F pulseaudio
BuildID: 20200403170909
CasperMD5CheckResult: skip
Channel: Unavailable
Date: Mon Apr 19 18:25:46 2021
ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
ForcedLayersAccel: False
InstallationDate: Installed on 2021-04-18 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
 default via 192.168.1.254 dev enp5s0 proto dhcp metric 100 
 169.254.0.0/16 dev enp5s0 scope link metric 1000 
 192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.101 metric 100
NoProfiles: True
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.5
RunningIncompatibleAddons: False
SourcePackage: firefox
Title: package firefox 75.0+build3-0ubuntu1 failed to install/upgrade: dpkg-deb 
--fsys-tarfile subprocess returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/07/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5409
dmi.board.asset.tag: Default string
dmi.board.name: PRIME A320M-K
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5409:bd01/07/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-package focal

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

Title:
  package firefox 75.0+build3-0ubuntu1 failed to install/upgrade: dpkg-
  deb --fsys-tarfile subprocess returned error exit status 2

Status in firefox package in Ubuntu:
  New

Bug description:
  I have been having trouble with system locking up and crashing.
  I installed a second copy of Ubuntu 20.04 alongside on the same hard drive - 
just the basic features. 
  I tested this on the internet and all seemed well.
  Firefox wanted to update - failed to install.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: firefox 75.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jackofalltrades   1294 F pulseaudio
   /dev/snd/controlC0:  jackofalltrades   1294 F pulseaudio
  BuildID: 20200403170909
  CasperMD5CheckResult: skip
  Channel: Unavailable
  Date: Mon Apr 19 18:25:46 2021
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-04-18 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.1.254 dev enp5s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp5s0 scope link metric 1000 
   192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.101 metric 
100
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 75.0+build3-0ubuntu1 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

[Desktop-packages] [Bug 1925056] [NEW] Dell XPS 13 9380 - System hangs when connecting bluetooth since kernel 5.6.0-1048-oem

2021-04-19 Thread da-phil

Public bug reported:

Since the kernel upgrade to 5.6.0-1048-oem my Dell XPS 13 9380 starts to
hang and finally freezes when I want to connect to my AV-receiver over
bluetooth. There is something funky going on in the kernel, hence I
attached the dmesg kernel messages since system boot.

All consecutive versions > 5.6.0-1048-oem show the same behaviour, hence
I'm still booting 5.6.0-1047-oem currently.

I tried the 5.4 kernel series and the latest one (5.4.0-72-generic) was
also working fine.

The only HW change I did to my Dell XPS 13 9380 was changing my SSD to a
bigger Samsung SSD 970 EVO Plus 1TB, everything is as I ordered it.

I read about bluetooth vulnerability fixes in exactly the version where the 
problem started here: https://ubuntu.com/security/notices/USN-4752-1
Maybe that has something to do with the issue?

Can somebody reproduce this issue?

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

** Affects: linux-meta-oem-5.6 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 9380 bluetooth crash dell xps

** Attachment added: "dmesg output"
   
https://bugs.launchpad.net/bugs/1925056/+attachment/5489843/+files/bluetooth_crash_dmesg.txt

** Package changed: gnome-shell (Ubuntu) => linux-meta-oem-5.6 (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/1925056

Title:
  Dell XPS 13 9380 - System hangs when connecting bluetooth since kernel
  5.6.0-1048-oem

Status in linux-meta-oem-5.6 package in Ubuntu:
  New

Bug description:
  Since the kernel upgrade to 5.6.0-1048-oem my Dell XPS 13 9380 starts
  to hang and finally freezes when I want to connect to my AV-receiver
  over bluetooth. There is something funky going on in the kernel, hence
  I attached the dmesg kernel messages since system boot.

  All consecutive versions > 5.6.0-1048-oem show the same behaviour,
  hence I'm still booting 5.6.0-1047-oem currently.

  I tried the 5.4 kernel series and the latest one (5.4.0-72-generic)
  was also working fine.

  The only HW change I did to my Dell XPS 13 9380 was changing my SSD to
  a bigger Samsung SSD 970 EVO Plus 1TB, everything is as I ordered it.

  I read about bluetooth vulnerability fixes in exactly the version where the 
problem started here: https://ubuntu.com/security/notices/USN-4752-1
  Maybe that has something to do with the issue?

  Can somebody reproduce this issue?

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-5.6/+bug/1925056/+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 1925057] [NEW] [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound

2021-04-19 Thread Gluttton

Public bug reported:

Hello,

I'm using Ubuntu together with Windows on my laptop.

If I boot in Ubuntu after Windows sound doesn't work well (instead of
system sounds I can hear only shot noise). To fix the issue I need to
completely shut down the system (call Power Off via Ubuntu GUI) and then
boot again in Ubuntu. Please note, that reboot (called via Ubuntu GUI)
doesn't help to fix the issue.

Expected result: sound works well regardless of boot history.
Actual result: every time I boot in Ubuntu after Windows sound doesn't work.

Issue occurrence: 100%.

Environment:
$ lsb_release -rd
Description: Ubuntu Hirsute Hippo (development branch)
Release: 21.04
$ uname -a
Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux

Thank you in advance!

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gluttton   1640 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 19 19:37:56 2021
InstallationDate: Installed on 2021-03-06 (43 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp
Symptom_Jack: Speaker, Internal
Symptom_PulseAudioLog:
 кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 
'module-null-sink' was still loaded!
 кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded.
 кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded.
 кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded.
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or 
crackling sound
UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago)
dmi.bios.date: 01/14/2021
dmi.bios.release: 1.31
dmi.bios.vendor: LENOVO
dmi.bios.version: DHCN31WW
dmi.board.asset.tag: ���
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40688 WIN
dmi.chassis.asset.tag: ���
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Yoga Slim 7 14IIL05
dmi.ec.firmware.release: 1.29
dmi.modalias: 
dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05:
dmi.product.family: Yoga Slim 7 14IIL05
dmi.product.name: 82A1
dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05
dmi.product.version: Yoga Slim 7 14IIL05
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug hirsute

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

Title:
  [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or
  crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,

  I'm using Ubuntu together with Windows on my laptop.

  If I boot in Ubuntu after Windows sound doesn't work well (instead of
  system sounds I can hear only shot noise). To fix the issue I need to
  completely shut down the system (call Power Off via Ubuntu GUI) and
  then boot again in Ubuntu. Please note, that reboot (called via Ubuntu
  GUI) doesn't help to fix the issue.

  Expected result: sound works well regardless of boot history.
  Actual result: every time I boot in Ubuntu after Windows sound doesn't work.

  Issue occurrence: 100%.

  Environment:
  $ lsb_release -rd
  Description: Ubuntu Hirsute Hippo (development branch)
  Release: 21.04
  $ uname -a
  Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux

  Thank you in advance!

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gluttton   1640 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 19 19:37:56 2021
  InstallationDate: Installed on 2021-03-06 (43 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through

[Desktop-packages] [Bug 1869734] Re: openjade segfaults on all arch

2021-04-19 Thread Bryce Harrington

Unless I've misunderstood, from the last few comments it sounds like this is 
now fixed for hirsute thanks to the sync'd package.
Please reopen if there is any followup work needed.

** Changed in: openjade (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  openjade segfaults on all arch

Status in openjade package in Ubuntu:
  Fix Released
Status in pgpool2 package in Ubuntu:
  New
Status in openjade package in Debian:
  Fix Released

Bug description:
  cpaelzer: fun, openjade segfaulting on focal/arm64
  I beg your pardon for my ignorance of the ecosystem, but how is 
this related to postgresql-apt
  for doc generation?
  cpaelzer: the postgresql-9.5 and -9.6 builds fail during doc 
generation on focal/arm64
  everything else (other archs, other dists) is fine
  
https://pgdgbuild.dus.dg-i.net/job/postgresql-9.5-binaries/architecture=arm64,distribution=focal/55/console

  Myon: only on arm64?
  only there, yes

  ./configure && make -C doc/src/sgml all  should reproduce it
  clone and build this branch ? 
https://github.com/postgres/postgres/tree/REL9_5_STABLE
  the crash is in /usr/lib/libostyle.so.1 from libostyle1c2
  here it is
  segfault

  I have this now http://paste.debian.net/1136839/
  https://paste.ubuntu.com/p/CfzrfWkqzs/

  well I wanted to get -O0 to see more int he debugger
  my build worked as well now
  the -O0 openjade installed doesn't segfault
  oh so like my -O0 then
  so maybe we should just always -O0 openjade then?
  TBH who cares about optimization in that
  But its usage is mostly build time and not runtime
  maybe -O0 on arm64 only
  I'm rebulding -O2 again to recheck if that really is it
  and then -O1 to check the in between
  it might "just" need a rebuild

  -O2 re-build segfault
  -O1 (for completeness) rebuild ... seems to hang?
  probably not really relevant
  agreed, but I want to rebuild -O0 again just to see it builds 
and then works
  -O0 on arm64 really seems to be a good choice

  I can try if rebuilding makes it fail on sid
  cpaelzer: recompiling openjade in arm64/sid doesn't make it 
segfault
  so it seems this needs a focal-only fix
  cpaelzer: the openjade segfault is also present in pgpool2, so 
not just in ancient PostgreSQL :(

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

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

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

it sounds similar to bug #1877194

could you try if commenting out switch-on-connect in
/etc/pulse/default.pa fixes the issue for you?

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

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

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

Bug description:
# Introduction

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

# How to reproduce

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

# Expected result

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

# Actual result

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

# System information

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

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

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

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

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

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

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

Title:
  Settings crashes as soon as it is opened

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

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

  
  ❯ gnome-control-center

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

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

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

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

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

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

  Inferior 1 [process 13233] will be killed.

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1924895/+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 1857552] Re: [81NX, Realtek ALC285, Speaker, Internal] No sound at all

2021-04-19 Thread Thomas Bousquet

That's awesome !
I can confirm that your patch works on Ubuntu 20.04. I can finally enjoy fully 
functional Linux on my laptop (Lenovo S740 15"). 
Thank you so much !

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

Title:
  [81NX, Realtek ALC285, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  In dual boot machine (lenove S740 laptop) sound is fine on windows
  side.

  Headphones work on linux side, but there is no sound at all from
  speakers on the ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hu-mka 1574 F pulseaudio
hu-mka 5552 F alsamixer
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 25 20:14:17 2019
  InstallationDate: Installed on 2019-12-22 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1126 F pulseaudio
hu-mka 1574 F pulseaudio
hu-mka 5552 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [81NX, Realtek ALC285, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BKCN20WW(V1.02)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S740-15IRH
  dmi.modalias: 
dmi:bvnLENOVO:bvrBKCN20WW(V1.02):bd07/15/2019:svnLENOVO:pn81NX:pvrLenovoYogaS740-15IRH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaS740-15IRH:
  dmi.product.family: Yoga S740-15IRH
  dmi.product.name: 81NX
  dmi.product.sku: LENOVO_MT_81NX_BU_idea_FM_Yoga S740-15IRH
  dmi.product.version: Lenovo Yoga S740-15IRH
  dmi.sys.vendor: LENOVO

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

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

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

2021-04-19 Thread Vadim Peretokin

Indeed I had the first two issues. Settings don't seem to crash after a
reboot - will update this when it happens again.

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

Title:
  Settings crashes as soon as it is opened

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

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

  
  ❯ gnome-control-center

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

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

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

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

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

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

  Inferior 1 [process 13233] will be killed.

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1924895/+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"

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

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

-- 
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 Mutter:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged

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/mutter/+bug/1923431/+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 1635810] Re: Xorg crashes with SEGV failing to access /usr/share/X11/xorg.conf.d

2021-04-19 Thread halfdog

I do not have any running Ubuntu machines any more, but on Debian
Bullseye with

ii  xserver-xorg-core2:1.20.10-3
amd64Xorg X server - core server

the crash does not happen any more, neither running just X or Xorg
-configure.

So unless this was a bug specific to Ubuntu, I would deem it fixed
upstream.

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

Title:
  Xorg crashes with SEGV failing to access /usr/share/X11/xorg.conf.d

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Trying to get "Xorg -configure" working again to create a monolithic
  configuration file for automated distribution (the "Xorg: No devices
  to configure.  Configuration failed." problem with -configure
  mentioned in forums), I moved away /usr/share/X11/xorg.conf.d to get
  rid of any interferences from that direction. This resulted in a crash
  starting Xorg on Ubuntu Xenial:

  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x52) [0x8024ff92]
  (EE) 1: /usr/lib/xorg/Xorg (0x800ae000+0x1a63f2) [0x802543f2]
  (EE) 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb7712c20]
  (EE) 3: /usr/lib/xorg/Xorg (xf86PlatformMatchDriver+0xb5) [0x80149565]
  (EE) 4: /usr/lib/xorg/Xorg (0x800ae000+0x9eb08) [0x8014cb08]
  (EE) 5: /usr/lib/xorg/Xorg (0x800ae000+0x9ecd1) [0x8014ccd1]
  (EE) 6: /usr/lib/xorg/Xorg (InitOutput+0x79a) [0x8012fa0a]
  (EE) 7: /usr/lib/xorg/Xorg (0x800ae000+0x3ed81) [0x800ecd81]
  (EE) 8: /usr/lib/xorg/Xorg (0x800ae000+0x28a3a) [0x800d6a3a]
  (EE) 9: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf7) [0xb71f9637]
  (EE) 10: /usr/lib/xorg/Xorg (0x800ae000+0x28a78) [0x800d6a78]
  (EE) 
  (EE) Segmentation fault at address 0x28

  # lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  # apt-cache policy xserver-xorg-core
  xserver-xorg-core:
Installed: 2:1.18.4-0ubuntu0.1
Candidate: 2:1.18.4-0ubuntu0.1
Version table:
   *** 2:1.18.4-0ubuntu0.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
  100 /var/lib/dpkg/status
   2:1.18.3-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1635810/+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 1690719] Re: Mouse pointer randomly pauses/stutters in gnome shell Wayland sessions

I keep seeing mentions of stutter in GNOME 40 Wayland sessions upstream,
and experience it myself. So the input thread wasn't a solution to this
anyway. It should stay open.

** Tags removed: fixed-in-40 fixed-upstream

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

Title:
  Mouse pointer randomly pauses/stutters in gnome shell Wayland sessions

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

Bug description:
  The mouse pointer randomly pauses/stutters in Gnome Shell (Wayland).
  It's not reliably smooth like you would see in Xorg or Mir demo
  servers.

  Feels like there is a blocking call being made in a GUI thread that
  shouldn't have any blocking calls. Although it's not clear if this is
  just a problem with pointer input or the shell compositing in general.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu7
  Architecture: amd64
  Date: Mon May 15 13:23:22 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  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/1690719/+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 1922438] Re: Firefox unusable on Kubuntu 21.04 Wayland session

2021-04-19 Thread Bevan

Mine is not unsusable but certainly is very sluggish. Can only type a
few characters in the address bar then nothing unless I completed the
URL or search term by hitting enter. The browser is very slow.

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

Title:
  Firefox unusable on Kubuntu 21.04 Wayland session

Status in firefox package in Ubuntu:
  Confirmed

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

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: firefox 87.0+build3-0ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kubuntu4308 F pulseaudio
  BuildID: 20210318103112
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sat Apr  3 15:54:32 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IpRoute:
   default via 192.168.10.1 dev enp0s31f6 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000 
   192.168.10.0/24 dev enp0s31f6 proto kernel scope link src 192.168.10.20 
metric 100
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=87.0/20210318103112 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd01/07/2021:br1.18:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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

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

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

** No longer affects: mesa (Ubuntu)

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

Title:
  Embedded browser display corruption under Wayland on Pi desktop

Status in gtk+3.0 package in Ubuntu:
  New
Status in webkit2gtk package in Ubuntu:
  New
Status in yelp package in Ubuntu:
  New

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

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

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

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

  Another reproduction case:

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

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

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

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

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

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

2021-04-19 Thread Filippo Ghibellini

In my specific case I have two output devices:

1. an audio card integrated in the motherboard
2. and an external microphone that has a monitoring output jack

Each of them results in two selectable options (there's always a second
"Digital Output (S/PDIF)" prefixed one) in the Ubuntu settings for a
total of 4.

After startup the usb microphone is selected as the output device so I
have to switch it to the integrated sound card analog output.

(you can see details about each device in the `pactl list sinks` output
in my "workaround" comment)

Also whenever I connect my guitar amp (also acts as sound output) it is
automatically selected as the active device and disconnecting it results
in the microphone being selected again no matter what I had selected
before connecting the amp.

There is no HDMI involved anywhere.

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

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

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

Bug description:
# Introduction

# How to reproduce

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

# Expected result

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

# Actual result

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

# System information

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

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

[Desktop-packages] [Bug 1924998] [NEW] Desktop freezes for one second then keeps going

2021-04-19 Thread Paolo Montrasio

Public bug reported:

> What you expected to happen

Normal operation: no delays when typing or moving windows around

> What happened instead

Since a few days ago I started noticing occasional lag when typing
(sometimes three words appearing together, as on a slow netword
connection) and when moving windows, as if the system was on a high
load. If I close almost everything it gets a little better, if I restart
Gnome Shell with ALT-F2 r RETURN it gets better for a few minutes.

Ghome Shell is always one of the top consumers of CPU and RAM, but this
was always the case. I don't have  particular problems with RAM, I'm
usually not using more than 20 GB out of 32 with many long running
programs (VMs, browsers, etc).

Sometimes I notice a Gnome Shell crash in the logs, as the one I
attached.

> The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu

Description:Ubuntu 20.04.2 LTS
Release:20.04

> The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center

gnome-shell:
  Installed: 3.36.7-0ubuntu0.20.04.1
  Candidate: 3.36.7-0ubuntu0.20.04.1
  Version table:
 *** 3.36.7-0ubuntu0.20.04.1 500
500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 3.36.4-1ubuntu1~20.04.2 500
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
 3.36.1-5ubuntu1 500
500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
Uname: Linux 5.4.0-70-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 19 11:28:45 2021
DisplayManager: gdm3
InstallationDate: Installed on 2019-10-19 (548 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-07-05 (288 days ago)

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


** Tags: amd64 apport-bug focal

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

Title:
  Desktop freezes for one second then keeps going

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  > What you expected to happen

  Normal operation: no delays when typing or moving windows around

  > What happened instead

  Since a few days ago I started noticing occasional lag when typing
  (sometimes three words appearing together, as on a slow netword
  connection) and when moving windows, as if the system was on a high
  load. If I close almost everything it gets a little better, if I
  restart Gnome Shell with ALT-F2 r RETURN it gets better for a few
  minutes.

  Ghome Shell is always one of the top consumers of CPU and RAM, but
  this was always the case. I don't have  particular problems with RAM,
  I'm usually not using more than 20 GB out of 32 with many long running
  programs (VMs, browsers, etc).

  Sometimes I notice a Gnome Shell crash in the logs, as the one I
  attached.

  > The release of Ubuntu you are using, via 'lsb_release -rd' or System
  -> About Ubuntu

  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  > The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  gnome-shell:
Installed: 3.36.7-0ubuntu0.20.04.1
Candidate: 3.36.7-0ubuntu0.20.04.1
Version table:
   *** 3.36.7-0ubuntu0.20.04.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.36.4-1ubuntu1~20.04.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   3.36.1-5ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
  Uname: Linux 5.4.0-70-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 19 11:28:45 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-10-19 (548 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-05 (288 days ago)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1923675] Re: package chromium-browser 1:85.0.4183.83-0ubuntu2 failed to install/upgrade: el subproceso nuevo paquete chromium-browser script pre-installation devolvió el código

2021-04-19 Thread Eduardo Barretto

Thanks for taking the time to report this bug and helping to make Ubuntu
better. Your bug report is more likely to get attention if it is made in
English, since this is the language understood by the majority of Ubuntu
developers.  Additionally, please only mark a bug as "security" if it
shows evidence of allowing attackers to cross privilege boundaries or to
directly cause loss of data/privacy. Please feel free to report any
other bugs you may find.

** Information type changed from Private Security to Public

** Changed in: chromium-browser (Ubuntu)
   Status: New => Incomplete

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

Title:
  package chromium-browser 1:85.0.4183.83-0ubuntu2 failed to
  install/upgrade: el subproceso nuevo paquete chromium-browser script
  pre-installation devolvió el código de salida de error 10

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  soy un novato en ubuntu, pero me guio mucho de tutoriales, he
  instalado ya varias paquetescon exito y es mi primera vez con un
  problema

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  AptOrdering:
   chromium-browser:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr 13 19:20:52 2021
  Dependencies:
   
  ErrorMessage: el subproceso nuevo paquete chromium-browser script 
pre-installation devolvió el código de salida de error 10
  InstallationDate: Installed on 2021-03-27 (17 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10ubuntu0.1
  SourcePackage: chromium-browser
  Title: package chromium-browser 1:85.0.4183.83-0ubuntu2 failed to 
install/upgrade: el subproceso nuevo paquete chromium-browser script 
pre-installation devolvió el código de salida de error 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1923675/+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

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

2021-04-19 Thread Gipsz Jakab

Yes, the bug occurred once, without any extensions active.

tg

On Mon, 19 Apr 2021 at 04:55, Daniel van Vugt
<1922...@bugs.launchpad.net> wrote:
>
> Can you rephrase that? Is this bug still occurring?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1922353
>
> Title:
>   Overview sometimes fails to appear or disappear fully when Ubuntu Dock
>   is loaded
>
> Status in gnome-shell package in Ubuntu:
>   Confirmed
> Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
>   Confirmed
>
> Bug description:
>   When I press the "windows" or "options" or "super" key a list of
>   running applications (like alt-tab) and a text window appears. I can
>   choose from the running applications or write a command into the text
>   window. After I chose an application or press ESC all this disappear
>   and I can do my thing.
>
>   Since trying 21.04 sometimes this
>   1. does not appear properly - there is no visible text window
>   2. does not disappear - despite what I click on or what keys do I press 
> this never disappear so I can not use my running applications or start 
> anything new even from the menu.
>
>   I have to log out and in to break this.
>
>   Disabling my gnome-shell extensions or using xorg instead of wayland
>   does not helps.
>
>   Since upgrading this morning this happens every time I press Super,
>   not just occasionally, thus making my desktop unusable.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 21.04
>   Package: gnome-shell 3.38.4-1ubuntu1
>   ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
>   Uname: Linux 5.11.0-13-generic x86_64
>   NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
>   ApportVersion: 2.20.11-0ubuntu61
>   Architecture: amd64
>   CasperMD5CheckResult: unknown
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Apr  2 14:07:39 2021
>   DisplayManager: gdm3
>   InstallationDate: Installed on 2020-03-19 (378 days ago)
>   InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
>   RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
>   SourcePackage: gnome-shell
>   UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922353/+subscriptions


-- 
we do what we must because we can

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

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

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

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

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

  I have to log out and in to break this.

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

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

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

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

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

[Desktop-packages] [Bug 1924184] Re: drive not showing

2021-04-19 Thread Eduardo Barretto

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  drive not showing

Status in xorg package in Ubuntu:
  New

Bug description:
  i coudnt find graphic drive

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 15 03:35:34 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0844]
 Subsystem: Dell Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] 
[1028:0844]
  InstallationDate: Installed on 2021-04-13 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Vostro 3578
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic 
root=UUID=7cf915de-bb29-49e2-a9cc-0079efc75ed1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2020
  dmi.bios.release: 1.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 01Y7V4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd01/09/2020:br1.10:svnDellInc.:pnVostro3578:pvr:rvnDellInc.:rn01Y7V4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3578
  dmi.product.sku: 0844
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

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

The settings only apply the changes, they have no backend side aiming at
enforcing the changes again after a restart, it's a pulseaudio problem
rather

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

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

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

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

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

Bug description:
# Introduction

# How to reproduce

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

# Expected result

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

# Actual result

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

# System information

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

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

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

Could you give some details on what output you select and which one is
on after restart? There a known problems around HDMI handling, unsure if
that's what you are seeing though

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

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

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

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

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

Bug description:
# Introduction

# How to reproduce

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

# Expected result

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

# Actual result

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

# System information

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

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

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

Thank you for your bug report. Similar issues are being discussed on
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/950 and
there are proposed fixes if you feel like trying how they work for you

** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #950
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/950

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

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

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

Status in pulseaudio package in Ubuntu:
  New

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

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

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

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

  Devices:

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

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

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

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

[Desktop-packages] [Bug 1820859] Re: nautilus --version segfaults in g_application_impl_get_dbus_object_path

The recent reports are probably due to the switch to desktop icons ng which 
calls nautilus to check if it's installed
https://gitlab.com/rastersoft/desktop-icons-ng/-/blob/master/desktopManager.js#L131

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

Title:
  nautilus --version segfaults in
  g_application_impl_get_dbus_object_path

Status in nautilus package in Ubuntu:
  Triaged

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820859/+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 1924988] [NEW] /usr/bin/software-properties-gtk:AttributeError:on_combobox_server_changed:init:init

2021-04-19 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

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

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: focal groovy hirsute kylin-21.04

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:on_combobox_server_changed:__init__:__init__

Status in software-properties package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1924988/+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 1924989] [NEW] /usr/bin/nautilus:11:g_application_get_dbus_object_path:update_dbus_opened_locations:bus_acquired_cb:connection_get_cb:g_task_return_now

2021-04-19 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

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

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


** Tags: hirsute

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

Title:
  
/usr/bin/nautilus:11:g_application_get_dbus_object_path:update_dbus_opened_locations:bus_acquired_cb:connection_get_cb:g_task_return_now

Status in nautilus package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1924989/+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 1924989] Re: /usr/bin/nautilus:11:g_application_get_dbus_object_path:update_dbus_opened_locations:bus_acquired_cb:connection_get_cb:g_task_return_now

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

** This bug has been marked a duplicate of bug 1820859
   nautilus --version segfaults in g_application_impl_get_dbus_object_path

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

Title:
  
/usr/bin/nautilus:11:g_application_get_dbus_object_path:update_dbus_opened_locations:bus_acquired_cb:connection_get_cb:g_task_return_now

Status in nautilus package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1924989/+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

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1924624, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1924624
   After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy 
Bridge) a lot of glitches render screen unusable

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

Title:
  Screen flickering

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  ubuntu whole screen flickering.

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

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

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

[Desktop-packages] [Bug 1924988] Re: /usr/bin/software-properties-gtk:AttributeError:on_combobox_server_changed:init:init

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

** This bug has been marked a duplicate of bug 1909918
   software-properties-gtk crashed with AttributeError in __init__(): 
'ElementTree' object has no attribute 'getiterator'

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:on_combobox_server_changed:__init__:__init__

Status in software-properties package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1924988/+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 1820859] Re: nautilus --version segfaults in g_application_impl_get_dbus_object_path

** Tags added: rls-hh-incoming

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

Title:
  nautilus --version segfaults in
  g_application_impl_get_dbus_object_path

Status in nautilus package in Ubuntu:
  Triaged

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820859/+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 1924964] Re: screen glitches

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1924778, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.

** Tags added: haswell regression-update

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

** Package changed: linux-hwe (Ubuntu) => linux-hwe-5.8 (Ubuntu)

** This bug has been marked a duplicate of bug 1924778
   i915 gen7: Screen flickers and flashes with kernel 5.8.0-50

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

Title:
  screen glitches

Status in linux-hwe-5.8 package in Ubuntu:
  New

Bug description:
  The issue is screen glitches

  issue is intermittent and temporary
  I think it started after a recent update

  But it gives the impression of an unstable system

  things flickering like a highlighted file in nautilus or in filezilla
  shadows under dialog boxes flickering

  the icons in the activities bar flickering like its displayed twice but 
scrolled vertically
  there are flickers of the other apps behind each, and some appear highlighted 
as they do when you put your mouse over them

  by scrolling them manually and running mouse over them seemed to get it to 
stop it
  didn't stop immediately but it did

  sometimes unresponsive apps like zoom
  sometimes zoom showing empty dialog

  a symptom that has existed for a while in nautilus when deep in a directory 
structure the top bar 
  containing directory names flickers like its scrolling horizontally.

  I click on a higher folder to get it to stop

  all the above happen regardless of where the mouse is

  in gedit with multiple tabs open one tab (the tab) appeared blank no
  file name, no flickering

  
  Ubuntu 20.04.2 LTS
  Laptop model Asus N550JV   old
  16GB RAM

  mouse is new but basic wired  J.BURROWS
  had to replace small one becuase button got stuck and it kept double clicking 
when i only single clicked

  
  Additional relevant
  I recently updated twice
  normally I wait a while perhaps a month before I update
  I think it started after a recent update

  Additional
  I do have many app running at the same time
  many opera windows 5+ with many tabs each 30+
  which drains my ram 16GB

  Has both NVIDIA and built in INTEL graphics
  at the time NVIDIA is turned off using INTEL

  could be related to RAM or maybe mouse

  Additional minor
  after latest update my desktop wallpaper which was just ubuntu 20.04 default 
now appears black
  in settings I can choose others and they display, but choose the one it was 
it stays black
  actually I would like an option for black. save power graphics CPU

  I really would like a ubuntu without screen glitches

  Thank you for your time

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 19 15:58:48 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:11cd]
 Subsystem: ASUSTeK Computer Inc. GK107M [GeForce GT 750M] [1043:11cd]
  InstallationDate: Installed on 2020-09-08 (222 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ASUSTeK COMPUTER INC. N550JV
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic 
root=UUID=18f3ecb2-cebb-4134-aa73-7d85d52089a3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N550JV.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N550JV
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias:

[Desktop-packages] [Bug 1924965] Re: Since 5.8.0-49 Screen flickers and becomes unusable

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1924778, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


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

** This bug has been marked a duplicate of bug 1924778
   i915 gen7 (Haswell and Ivy Bridge): Screen flickers and flashes with kernel 
5.8.0-50

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

Title:
  Since 5.8.0-49 Screen flickers and becomes unusable

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On ubuntu 20.10, x-org.  On upgrade kernel to 5.8.0-49, and then -50,
  after the desktop has been on for a while the screen starts to
  flicker.  Blocks of text go missing. Letters in a string disappear.
  Windows start flickering.  The panel starts flickering and icons
  disappear and reappear. The keyboard and mouse seem intermittently
  responsive.  After a restart it is OK for a little then starts again.

  ubuntu wayland is no better.

  Reverting to 5.8.0-48 fixes the problem completely.

  I originally commented on #1923632 but that has gone private, and I
  was asked to raise my own report. This one.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 19 07:42:02 2021
  DistUpgraded: 2020-10-26 15:35:51,446 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [19da:b220]
  InstallationDate: Installed on 2018-05-24 (1060 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ZOTAC ZBOX-ID92/ZBOX-IQ01
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=25b009b8-6f92-4bff-8f3f-8a9700abf672 ro quiet splash fsck.mode=force 
fsck.repair=yes vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2020-10-26 (174 days ago)
  dmi.bios.date: 05/21/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B220P007
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID92/ZBOX-IQ01
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB220P007:bd05/21/2014:br4.6:svnZOTAC:pnZBOX-ID92/ZBOX-IQ01:pvrXX:rvnZOTAC:rnZBOX-ID92/ZBOX-IQ01:rvrXX:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: NA
  dmi.product.name: ZBOX-ID92/ZBOX-IQ01
  dmi.product.sku: NA
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

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

2021-04-19 Thread Manu

manu@lari:~$ lpstat -a
Brother_MFC_L2710DW_series accepting requests since Mon 19 Apr 2021 10:46:49
followme accepting requests since Wed 11 Dec 2019 17:27:19
manu@lari:~$ lpstat -v
device for Brother_MFC_L2710DW_series: 
implicitclass://Brother_MFC_L2710DW_series/
device for followme: ipps://printer.mat.univie.ac.at/printers/followme
manu@lari:~$




The followme printer is not actually on my current network, it's on my 
(ex-)work network.
Also, it seems to me, your theory wouldn't explain why running pdftoraster 
directly also uses excessive memory.
When printing, I observe a single process consuming many gigabytes of RAM in 
htop.

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

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

Status in cups-filters package in Ubuntu:
  Confirmed

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

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

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

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

  Please let me know if you need more information.

  ## Further info:

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

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

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

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

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

  
  ## Trying to debug with cupsfilter:

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

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

  The latter uses gstoraster:

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

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

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

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

[Desktop-packages] [Bug 1924965] Re: Since 5.8.0-49 Screen flickers and becomes unusable

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

Title:
  Since 5.8.0-49 Screen flickers and becomes unusable

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  On ubuntu 20.10, x-org.  On upgrade kernel to 5.8.0-49, and then -50,
  after the desktop has been on for a while the screen starts to
  flicker.  Blocks of text go missing. Letters in a string disappear.
  Windows start flickering.  The panel starts flickering and icons
  disappear and reappear. The keyboard and mouse seem intermittently
  responsive.  After a restart it is OK for a little then starts again.

  ubuntu wayland is no better.

  Reverting to 5.8.0-48 fixes the problem completely.

  I originally commented on #1923632 but that has gone private, and I
  was asked to raise my own report. This one.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 19 07:42:02 2021
  DistUpgraded: 2020-10-26 15:35:51,446 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [19da:b220]
  InstallationDate: Installed on 2018-05-24 (1060 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ZOTAC ZBOX-ID92/ZBOX-IQ01
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=25b009b8-6f92-4bff-8f3f-8a9700abf672 ro quiet splash fsck.mode=force 
fsck.repair=yes vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2020-10-26 (174 days ago)
  dmi.bios.date: 05/21/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B220P007
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID92/ZBOX-IQ01
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB220P007:bd05/21/2014:br4.6:svnZOTAC:pnZBOX-ID92/ZBOX-IQ01:pvrXX:rvnZOTAC:rnZBOX-ID92/ZBOX-IQ01:rvrXX:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: NA
  dmi.product.name: ZBOX-ID92/ZBOX-IQ01
  dmi.product.sku: NA
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924965/+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 1924964] Re: screen glitches

2021-04-19 Thread Chris Guiver

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

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

Title:
  screen glitches

Status in xorg package in Ubuntu:
  New

Bug description:
  The issue is screen glitches

  issue is intermittent and temporary
  I think it started after a recent update

  But it gives the impression of an unstable system

  things flickering like a highlighted file in nautilus or in filezilla
  shadows under dialog boxes flickering

  the icons in the activities bar flickering like its displayed twice but 
scrolled vertically
  there are flickers of the other apps behind each, and some appear highlighted 
as they do when you put your mouse over them

  by scrolling them manually and running mouse over them seemed to get it to 
stop it
  didn't stop immediately but it did

  sometimes unresponsive apps like zoom
  sometimes zoom showing empty dialog

  a symptom that has existed for a while in nautilus when deep in a directory 
structure the top bar 
  containing directory names flickers like its scrolling horizontally.

  I click on a higher folder to get it to stop

  all the above happen regardless of where the mouse is

  in gedit with multiple tabs open one tab (the tab) appeared blank no
  file name, no flickering

  
  Ubuntu 20.04.2 LTS
  Laptop model Asus N550JV   old
  16GB RAM

  mouse is new but basic wired  J.BURROWS
  had to replace small one becuase button got stuck and it kept double clicking 
when i only single clicked

  
  Additional relevant
  I recently updated twice
  normally I wait a while perhaps a month before I update
  I think it started after a recent update

  Additional
  I do have many app running at the same time
  many opera windows 5+ with many tabs each 30+
  which drains my ram 16GB

  Has both NVIDIA and built in INTEL graphics
  at the time NVIDIA is turned off using INTEL

  could be related to RAM or maybe mouse

  Additional minor
  after latest update my desktop wallpaper which was just ubuntu 20.04 default 
now appears black
  in settings I can choose others and they display, but choose the one it was 
it stays black
  actually I would like an option for black. save power graphics CPU

  I really would like a ubuntu without screen glitches

  Thank you for your time

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 19 15:58:48 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:11cd]
 Subsystem: ASUSTeK Computer Inc. GK107M [GeForce GT 750M] [1043:11cd]
  InstallationDate: Installed on 2020-09-08 (222 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ASUSTeK COMPUTER INC. N550JV
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic 
root=UUID=18f3ecb2-cebb-4134-aa73-7d85d52089a3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N550JV.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N550JV
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN550JV.204:bd05/14/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N550JV
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1

[Desktop-packages] [Bug 1924965] Re: Since 5.8.0-49 Screen flickers and becomes unusable

2021-04-19 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  Since 5.8.0-49 Screen flickers and becomes unusable

Status in xorg package in Ubuntu:
  New

Bug description:
  On ubuntu 20.10, x-org.  On upgrade kernel to 5.8.0-49, and then -50,
  after the desktop has been on for a while the screen starts to
  flicker.  Blocks of text go missing. Letters in a string disappear.
  Windows start flickering.  The panel starts flickering and icons
  disappear and reappear. The keyboard and mouse seem intermittently
  responsive.  After a restart it is OK for a little then starts again.

  ubuntu wayland is no better.

  Reverting to 5.8.0-48 fixes the problem completely.

  I originally commented on #1923632 but that has gone private, and I
  was asked to raise my own report. This one.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 19 07:42:02 2021
  DistUpgraded: 2020-10-26 15:35:51,446 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [19da:b220]
  InstallationDate: Installed on 2018-05-24 (1060 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ZOTAC ZBOX-ID92/ZBOX-IQ01
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=25b009b8-6f92-4bff-8f3f-8a9700abf672 ro quiet splash fsck.mode=force 
fsck.repair=yes vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2020-10-26 (174 days ago)
  dmi.bios.date: 05/21/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B220P007
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID92/ZBOX-IQ01
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB220P007:bd05/21/2014:br4.6:svnZOTAC:pnZBOX-ID92/ZBOX-IQ01:pvrXX:rvnZOTAC:rnZBOX-ID92/ZBOX-IQ01:rvrXX:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: NA
  dmi.product.name: ZBOX-ID92/ZBOX-IQ01
  dmi.product.sku: NA
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924965/+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 1924965] [NEW] Since 5.8.0-49 Screen flickers and becomes unusable