[Desktop-packages] [Bug 1903524] Re: System state with 'space' in name prevent update-grub to create menu entries in grub.cfg

[Jean-Baptiste Lallement]

** Changed in: grubzfs-testsuite (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  System state with 'space' in name prevent update-grub to create menu
  entries in grub.cfg

Status in grub2 package in Ubuntu:
  In Progress
Status in grubzfs-testsuite package in Ubuntu:
  Triaged
Status in zsys package in Ubuntu:
  Fix Released
Status in grub2 source package in Focal:
  Triaged
Status in zsys source package in Focal:
  Triaged
Status in grub2 source package in Groovy:
  Triaged
Status in zsys source package in Groovy:
  Triaged

Bug description:
  [Impact]
  Some characters are not supported in snapshot names by either zfs, grub or 
init. As a consequence a system cannot be reverted to a snapshot created with 
such characters, and the system fails to boot with various errors.

  This patch forces the name of snapshot created with zsysctl to the
  following characters: a-z, A-Z, 0-9, _, -, .

  Space is not unsupported by ZFS and would be perfectly correct to
  create a snapshot with a space in it. However it creates issues in
  GRUB when it generates the boot command line due to the way it quotes
  the argument root= by adding a double before root which is then
  wrongly interpreted by init. It also creates issues in init which uses
  for loop to read the command line and splits it on spaces, and in the
  middle of the root argument while it should be a single argument.
  Fixing space handling in GRUB and init is really intrusive and beyond
  the scope of this bug so we decided to prevent spaces too in snapshot
  names.

  [Test Case]
  1. Boot a system with zsys without the patch

  * Positive test *
  2. Create a system snapshot with a valid character. Valid characters are 
"a-z", "A-Z", "0-9", "_", "-", "." Name must not start by . or -
  => Verify that the snapshot is created successfully
  3. Reboot to the grub menu and in the history menu select the snapshot you 
just created.
  => Verify that the system boot to the reverted state of the snapshot

  * Negative test 1*
  4. Create a snapshot with an invalid character.
  => Verify that the creation fails with an error message listing the invalid 
character/s

  * Negative test 2*
  5. Create a snapshot that starts with '-'
  => Verify that the snapshot cannot be created.

  * Negative test 3*
  5. Create a snapshot names '.' or '..'
  => Verify that the snapshot cannot be created.

  [Regression potential]
  If filtering is not done properly the patch can either:
  1. prevent supported characters to be used in snapshot names but snapshots 
can still be created and names generated by auto snapshots are supported.
  2. allow unsupported characters to be used in snapshot names. In this case we 
are back to current situation.

  The patch is covered by several tests in the included test suite.


  [Original Description]
  From https://github.com/ubuntu/zsys/issues/169

  Describe the bug
  I did create few days ago a System state with a 'space' in the name : 
"pool/ROOT/ubuntu_u7dn3s@Stable Plex"

  server:~$ zsysctl show
  Name:   rpool/ROOT/ubuntu_u7dn3s
  ZSys:   true
  Last Used:  current
  History:
    - Name:   rpool/ROOT/ubuntu_u7dn3s@autozsys_ceqh6a
  Created on: 2020-10-16 06:49:59
    - Name:   rpool/ROOT/ubuntu_u7dn3s@autozsys_ahzb7l
  Created on: 2020-10-15 06:40:13
    - Name:   rpool/ROOT/ubuntu_u7dn3s@autozsys_a00j2k
  Created on: 2020-10-08 06:46:34
     - Name:   rpool/ROOT/ubuntu_u7dn3s@autozsys_b7t6lj
   Created on: 2020-10-07 06:20:00
     - Name:   rpool/ROOT/ubuntu_u7dn3s@Stable Plex
   Created on: 2020-10-03 19:18:18
     - Name:   rpool/ROOT/ubuntu_u7dn3s@autozsys_a81mbp
   Created on: 2020-10-03 17:58:19
  (truncated)...
  I found myself in the impossibility to boot the server few days after as the 
Grub menu had only the UEFI entry in it. No more entries for current kernel or 
zsys history.

  server:~$ cat /boot/grub/grub.cfg
  ...(truncated)
  ### END /etc/grub.d/20_linux_xen ###

  ### BEGIN /etc/grub.d/30_os-prober ###
  ### END /etc/grub.d/30_os-prober ###

  ### BEGIN /etc/grub.d/30_uefi-firmware ###
  menuentry 'UEFI Firmware Settings' $menuentry_id_option 'uefi-firmware' {
   fwsetup
  }
  ### END /etc/grub.d/30_uefi-firmware ###

  ### BEGIN /etc/grub.d/40_custom ###
  # This file provides an easy way to add custom menu entries.  Simply type the
  # menu entries you want to add after this comment.  Be careful not to change
  # the 'exec tail' line above.
  ### END /etc/grub.d/40_custom ###
  (truncated)...
  After chrooting into the server, I tried to rebuild the menu with update-grub 
and got a weird error message on ignoring datasets:

  server:~$ update-grub
  Sourcing file `/etc/default/grub'
  Sourcing file `/etc/default/grub.d/init-select.cfg'
  Generating grub configuration 

[Desktop-packages] [Bug 1903524] Re: System state with 'space' in name prevent update-grub to create menu entries in grub.cfg

[Launchpad Bug Tracker]

This bug was fixed in the package grubzfs-testsuite - 0.4.14

---
grubzfs-testsuite (0.4.14) hirsute; urgency=medium

  * Revert "Add testcases to cover names with spaces and dashes", as
matching grub upload is not in hirsute.

grubzfs-testsuite (0.4.13) hirsute; urgency=medium

  * Switch to upstream branch of go-libzfs with 2.0.x support.

grubzfs-testsuite (0.4.12) hirsute; urgency=medium

  [ Jean-Baptiste Lallement ]
  [ Didier Roche ]
  * Added test cases to cover snapshot names with spaces or dashes
(LP: #1898177, #1903524)

 -- Dimitri John Ledkov   Fri, 05 Feb 2021 19:18:25
+

** Changed in: grubzfs-testsuite (Ubuntu)
   Status: New => Fix Released

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

Title:
  System state with 'space' in name prevent update-grub to create menu
  entries in grub.cfg

Status in grub2 package in Ubuntu:
  In Progress
Status in grubzfs-testsuite package in Ubuntu:
  Fix Released
Status in zsys package in Ubuntu:
  Fix Released
Status in grub2 source package in Focal:
  Triaged
Status in zsys source package in Focal:
  Triaged
Status in grub2 source package in Groovy:
  Triaged
Status in zsys source package in Groovy:
  Triaged

Bug description:
  [Impact]
  Some characters are not supported in snapshot names by either zfs, grub or 
init. As a consequence a system cannot be reverted to a snapshot created with 
such characters, and the system fails to boot with various errors.

  This patch forces the name of snapshot created with zsysctl to the
  following characters: a-z, A-Z, 0-9, _, -, .

  Space is not unsupported by ZFS and would be perfectly correct to
  create a snapshot with a space in it. However it creates issues in
  GRUB when it generates the boot command line due to the way it quotes
  the argument root= by adding a double before root which is then
  wrongly interpreted by init. It also creates issues in init which uses
  for loop to read the command line and splits it on spaces, and in the
  middle of the root argument while it should be a single argument.
  Fixing space handling in GRUB and init is really intrusive and beyond
  the scope of this bug so we decided to prevent spaces too in snapshot
  names.

  [Test Case]
  1. Boot a system with zsys without the patch

  * Positive test *
  2. Create a system snapshot with a valid character. Valid characters are 
"a-z", "A-Z", "0-9", "_", "-", "." Name must not start by . or -
  => Verify that the snapshot is created successfully
  3. Reboot to the grub menu and in the history menu select the snapshot you 
just created.
  => Verify that the system boot to the reverted state of the snapshot

  * Negative test 1*
  4. Create a snapshot with an invalid character.
  => Verify that the creation fails with an error message listing the invalid 
character/s

  * Negative test 2*
  5. Create a snapshot that starts with '-'
  => Verify that the snapshot cannot be created.

  * Negative test 3*
  5. Create a snapshot names '.' or '..'
  => Verify that the snapshot cannot be created.

  [Regression potential]
  If filtering is not done properly the patch can either:
  1. prevent supported characters to be used in snapshot names but snapshots 
can still be created and names generated by auto snapshots are supported.
  2. allow unsupported characters to be used in snapshot names. In this case we 
are back to current situation.

  The patch is covered by several tests in the included test suite.


  [Original Description]
  From https://github.com/ubuntu/zsys/issues/169

  Describe the bug
  I did create few days ago a System state with a 'space' in the name : 
"pool/ROOT/ubuntu_u7dn3s@Stable Plex"

  server:~$ zsysctl show
  Name:   rpool/ROOT/ubuntu_u7dn3s
  ZSys:   true
  Last Used:  current
  History:
    - Name:   rpool/ROOT/ubuntu_u7dn3s@autozsys_ceqh6a
  Created on: 2020-10-16 06:49:59
    - Name:   rpool/ROOT/ubuntu_u7dn3s@autozsys_ahzb7l
  Created on: 2020-10-15 06:40:13
    - Name:   rpool/ROOT/ubuntu_u7dn3s@autozsys_a00j2k
  Created on: 2020-10-08 06:46:34
     - Name:   rpool/ROOT/ubuntu_u7dn3s@autozsys_b7t6lj
   Created on: 2020-10-07 06:20:00
     - Name:   rpool/ROOT/ubuntu_u7dn3s@Stable Plex
   Created on: 2020-10-03 19:18:18
     - Name:   rpool/ROOT/ubuntu_u7dn3s@autozsys_a81mbp
   Created on: 2020-10-03 17:58:19
  (truncated)...
  I found myself in the impossibility to boot the server few days after as the 
Grub menu had only the UEFI entry in it. No more entries for current kernel or 
zsys history.

  server:~$ cat /boot/grub/grub.cfg
  ...(truncated)
  ### END /etc/grub.d/20_linux_xen ###

  ### BEGIN /etc/grub.d/30_os-prober ###
  ### END /etc/grub.d/30_os-prober ###

  ### BEGIN /etc/grub.d/30_uefi-firmware ###
  menuentry 'UEFI Firmware Settings' $menuentry_id_option 'uefi-firmware' {
   

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

[BitBurners.com]

Thanks @vanvugt,

I had to wipe the setup and replace with Windows to quickly work around
from the issue. However:

- Wayland vs. X11 makes no difference. I usually prefer Wayland, but tried X 
too. Also, KDE Neon uses X as default.
- I investigated a bit further, and indeed the time-line of the issue matches 
quite accurately with the kernel 5.8 upgrade. Also, the KDE Neon installation 
media comes with 5.8 currently.

Since I can now only debug with live media, I guess I need to try 20.04
vs 20.04.2, unless someone else is able to repro this.

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

Title:
  Stuttering video playback

Status in xorg-server package in Ubuntu:
  Incomplete

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1914983] [NEW] LightDM restarts continously

[Alessandro Del Prete]

Public bug reported:

Noticed in the log that lightdm restarts every few seconds.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: lightdm 1.30.0-0ubuntu3.1
ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14
Uname: Linux 5.8.0-1006-raspi aarch64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: arm64
CasperMD5CheckResult: skip
Date: Mon Feb  8 07:18:18 2021
ImageMediaBuild: 20201028
LightdmConfig:
 [Seat:*]
 autologin-guest=false
 autologin-user=alexdelprete
 autologin-user-timeout=0
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug arm64 groovy

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

Title:
  LightDM restarts continously

Status in lightdm package in Ubuntu:
  New

Bug description:
  Noticed in the log that lightdm restarts every few seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: lightdm 1.30.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14
  Uname: Linux 5.8.0-1006-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Mon Feb  8 07:18:18 2021
  ImageMediaBuild: 20201028
  LightdmConfig:
   [Seat:*]
   autologin-guest=false
   autologin-user=alexdelprete
   autologin-user-timeout=0
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Qa-admin-q]

Dear karaluh,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information 
from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to 
RESOLVED-WORKSFORME and leave a comment that includes the information from Help 
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular 
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a 
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your 
bug pertains to a feature added after 3.3) from 
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: 
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

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

Title:
  [Upstream] Calc makes cells protected when it shouldn't

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: openoffice.org

  1) lsb_release -rd
  Description:  Ubuntu precise (development branch)
  Release:  12.04

  2) apt-cache policy libreoffice-calc
  libreoffice-calc:
Installed: 1:3.5.2-2ubuntu1
Candidate: 1:3.5.2-2ubuntu1
Version table:
   *** 1:3.5.2-2ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in LibreOffice Calc via the Terminal:
  cd ~/Desktop && wget -c 
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/704789/+attachment/3075997/+files/Test%20case.ods
 -O example.ods && localc --nologo example.ods

  open www.ubuntu.com in a web browser, copy "Fast, secure and stylishly
  simple," into A1, then try to delete the pasted text and it is
  deleted.

  4) What happens instead is the text isn't deleted and the cell becomes
  protected.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: openoffice.org-calc 1:3.2.1-7ubuntu1
  ProcVersionSignature: Ubuntu 2.6.35-25.43-generic 2.6.35.10
  Uname: Linux 2.6.35-25-generic i686
  Architecture: i386
  Date: Tue Jan 18 16:02:24 2011
  ProcEnviron:
   LANGUAGE=pl_PL:pl:en_GB:en
   PATH=(custom, no user)
   LANG=pl_PL.utf8
   SHELL=/bin/bash
  SourcePackage: openoffice.org
  ---
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  DistroRelease: Ubuntu 11.10
  Package: libreoffice-calc 1:3.4.5-0ubuntu1
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=pl_PL:pl:en_GB:en
   PATH=(custom, user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  Tags:  oneiric
  Uname: Linux 3.3.0-030300-generic i686
  UpgradeStatus: Upgraded to oneiric on 2011-10-18 (180 days ago)
  UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin 
plugdev sambashare scanner video

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/704789/+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 1907190] Re: package chromium-browser (not installed) failed to install/upgrade: o subprocesso do pacote chromium-browser, novo script pre-installation retornou erro do status

[Launchpad Bug Tracker]

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

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

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

Title:
  package chromium-browser (not installed) failed to install/upgrade: o
  subprocesso do pacote chromium-browser, novo script pre-installation
  retornou erro do status de saída 1

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  The software Chromium is not install or reinstall for the apt command,
  the repository is correct.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  AptOrdering:
   chromium-browser:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Dec  8 00:55:24 2020
  ErrorMessage: o subprocesso do pacote chromium-browser, novo script 
pre-installation retornou erro do status de saída 1
  InstallationDate: Installed on 2020-12-05 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  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.2ubuntu0.1
  SourcePackage: chromium-browser
  Title: package chromium-browser (not installed) failed to install/upgrade: o 
subprocesso do pacote chromium-browser, novo script pre-installation retornou 
erro do status de saída 1
  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/1907190/+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 893366] Re: default resolution too high when used inside kvm with vmvga graphics

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Tags added: precise

** Changed in: xserver-xorg-video-vmware (Ubuntu)
   Status: New => Won't Fix

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

Title:
  default resolution too high when used inside kvm with vmvga graphics

Status in xserver-xorg-video-vmware package in Ubuntu:
  Won't Fix

Bug description:
  xserver-xorg-video-vmware (1:11.0.99.901-1) in Precise incorrectly
  sets the default resolution when used inside a kvm virtual machine. It
  defaults to 2048x1536 instead of 1024x768 as it was doing in Oneiric.

  See the attached log files. One is from Oneiric, and is working
  properly. The other is from Precise.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/893366/+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 943328] Re: pangolin vmware 4.0.2 screen in 3d does not return after host computer unlocks screen

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: xserver-xorg-video-vmware (Ubuntu)
   Status: New => Won't Fix

** Tags added: precise

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

Title:
  pangolin vmware 4.0.2 screen in 3d does not return after host computer
  unlocks screen

Status in xserver-xorg-video-vmware package in Ubuntu:
  Won't Fix

Bug description:
  i have pangolin alpha2 with all updates loaded in a vmware 4.0.2
  session with vmware tools compiled.  I lock the host system (winxp)
  for security. Then when I come back and unlock the host computer,
  pangolin does not come back.  This is only happening with accelerate
  3d graphics and regular unity running ( not 2d).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/943328/+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 1914947] Re: [vmwgfx] My display is so slow

[Daniel van Vugt]

If you are experiencing crashes then please follow these instructions:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

** Summary changed:

- My display is so slow 
+ [vmwgfx] My display is so slow

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

** Tags added: performance vmwgfx

** Tags added: vmware

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

Title:
  [vmwgfx] My display is so slow

Status in xserver-xorg-video-vmware package in Ubuntu:
  New

Bug description:
  My display performance is so slow sometimes it will crash or
  resolution is bad

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: hostname 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-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: Sun Feb  7 23:02:45 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2021-02-05 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. VMware Virtual USB Mouse
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware7,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=fd8451d8-78e6-471e-aa1e-cae417c043fb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2020
  dmi.bios.vendor: VMware, Inc.
  dmi.bios.version: VMW71.00V.16722896.B64.2008100651
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnVMware,Inc.:bvrVMW71.00V.16722896.B64.2008100651:bd08/10/2020:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware7,1
  dmi.product.version: None
  dmi.sys.vendor: VMware, 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 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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/xserver-xorg-video-vmware/+bug/1914947/+subscriptions

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

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

[Daniel van Vugt]

Also, while the stuttering is happening, please:

1. Use 'top' to identify any process(es) using high CPU.

2. Use 'journalctl -f' to identify any recurring log messages.

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

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

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

Title:
  Stuttering video playback

Status in xorg-server package in Ubuntu:
  Incomplete

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

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

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

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

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

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

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

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

[Daniel van Vugt]

Thanks for the bug report.

Please try each of these separately:

* Logging into 'Ubuntu on Wayland' (select it on the login screen before
entering your password).

* An older kernel, like 5.4 from https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.4.96/

* A video player like 'mpv':

  sudo apt install mpv
  mpv

** Tags added: 5.8-gfx

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

Title:
  Stuttering video playback

Status in xorg-server package in Ubuntu:
  Incomplete

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1856553] Re: libinput error: client bug: timer event3 debounce short: offset negative (-0ms) (#2041)

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1870597
   libinput says: scheduled expiry is in the past... your system is too slow

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

Title:
  libinput error: client bug: timer event3 debounce short: offset
  negative (-0ms) (#2041)

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  1) Ubuntu 19.10
  2) mutter 3.34.1
  3) No error.
  4) Error in log app.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: mutter 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 16 05:36:05 2019
  InstallationDate: Installed on 2019-10-28 (49 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1856553/+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 1914806] Re: (EE) client bug: timer event3 debounce short: scheduled expiry is in the past (-28ms), your system is too slow

[Daniel van Vugt]

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

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 1870597, 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.


** This bug has been marked a duplicate of bug 1870597
   libinput says: scheduled expiry is in the past... your system is too slow

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

Title:
  (EE) client bug: timer event3 debounce short: scheduled expiry is in
  the past (-28ms), your system is too slow

Status in libinput package in Ubuntu:
  New
Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  Feb  5 13:17:35 H61N-USB3 /usr/lib/gdm3/gdm-x-session[4812]: (EE) client bug: 
timer event3 debounce: scheduled expiry is in the past (-15ms), your system is 
too slow
  Feb  5 13:17:35 H61N-USB3 /usr/lib/gdm3/gdm-x-session[4812]: (EE) client bug: 
timer event3 debounce short: scheduled expiry is in the past (-28ms), your 
system is too slow
  Feb  5 13:17:46 H61N-USB3 /usr/lib/gdm3/gdm-x-session[4812]: (EE) client bug: 
timer event3 debounce short: scheduled expiry is in the past (-4ms), your 
system is too slow

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.7+git20201123-0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  5 13:19:11 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-26 (2355 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: Upgraded to focal on 2020-09-30 (128 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1914806/+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 1588009] Re: "libinput bug: timer offset negative" keeps coming up in syslog

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1870597
   libinput says: scheduled expiry is in the past... your system is too slow

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

Title:
  "libinput bug: timer offset negative" keeps coming up in syslog

Status in libinput:
  Invalid
Status in Ubuntu GNOME:
  New
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in libinput package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  I have just recently looked in my syslog and discovered that the
  following message shows up a lot daily so I thought I should report
  it:

  /usr/lib/gdm3/gdm-x-session[1707]: (EE) libinput bug: timer offset
  negative

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libinput10 1.2.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jun  1 18:39:08 2016
  InstallationDate: Installed on 2016-05-15 (17 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: libinput
  UpgradeStatus: Upgraded to xenial on 2016-05-28 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libinput/+bug/1588009/+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 1870597] Re: libinput says: scheduled expiry is in the past... your system is too slow

[Daniel van Vugt]

** Also affects: xserver-xorg-input-libinput (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xserver-xorg-input-libinput (Ubuntu)
   Status: New => Confirmed

** Tags added: performance

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

Title:
  libinput says: scheduled expiry is in the past... your system is too
  slow

Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  During the freeze, the output of the install had a message from
  "gdm-x-session" saying "your system is too slow".

  To reproduce:
  1. Launch the Ubuntu installer
  2. Begin the installation process
  3. When the installation process begins, move the cursor around
  4. Notice how the PC freezes and drops mouse events

  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  gnome-shell:
Installed: 3.36.0-2ubuntu2
Candidate: 3.36.0-2ubuntu2
Version table:
   *** 3.36.0-2ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CasperVersion: 1.442
  Date: Fri Apr  3 14:24:21 2020
  DisplayManager: gdm3
  GsettingsChanges:
   
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Dell Inc. Inspiron 5570
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/hostname.seed quiet splash ---
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-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/mutter/+bug/1870597/+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 1797729] Re: libinput error: client bug: timer event8 debounce short: offset negative (-NUMBERms)

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1588009
   "libinput bug: timer offset negative" keeps coming up in syslog
** This bug has been marked a duplicate of bug 1870597
   libinput says: scheduled expiry is in the past... your system is too slow

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

Title:
  libinput error: client bug: timer event8 debounce short: offset
  negative (-NUMBERms)

Status in libinput package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm reviewing the logs and that message appears repeatedly.

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libinput10 1.12.1-1
  Uname: Linux 4.18.14-041814-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 13 19:33:05 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.13-gnu, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0d7]
  InstallationDate: Installed on 2017-10-13 (365 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.14-041814-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: libinput
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.sku: System SKUNumber
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Fri Jul 20 17:46:48 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1797729/+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 1914806] Re: (EE) client bug: timer event3 debounce short: scheduled expiry is in the past (-28ms), your system is too slow

[Daniel van Vugt]

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

Thanks for the bug report. That message seems to come from libinput.
It's an attempt to tell you the client code (Xorg in this case) is not
performing well enough.

Usually this should be considered a bug in the client (Xorg) but also it
might be a poor design/assumption on the part of libinput to expect all
clients to perform better. So I will assign the bug to libinput too.

** Summary changed:

- Seeing this error in the logs while looking for any indication of Chrome long 
load time
+ (EE) client bug: timer event3 debounce short: scheduled expiry is in the past 
(-28ms), your system is too slow

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

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

** Also affects: libinput (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  (EE) client bug: timer event3 debounce short: scheduled expiry is in
  the past (-28ms), your system is too slow

Status in libinput package in Ubuntu:
  New
Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  Feb  5 13:17:35 H61N-USB3 /usr/lib/gdm3/gdm-x-session[4812]: (EE) client bug: 
timer event3 debounce: scheduled expiry is in the past (-15ms), your system is 
too slow
  Feb  5 13:17:35 H61N-USB3 /usr/lib/gdm3/gdm-x-session[4812]: (EE) client bug: 
timer event3 debounce short: scheduled expiry is in the past (-28ms), your 
system is too slow
  Feb  5 13:17:46 H61N-USB3 /usr/lib/gdm3/gdm-x-session[4812]: (EE) client bug: 
timer event3 debounce short: scheduled expiry is in the past (-4ms), your 
system is too slow

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.7+git20201123-0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  5 13:19:11 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-26 (2355 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: Upgraded to focal on 2020-09-30 (128 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1914806/+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 1914573] Re: [DisplayLink] Xorg crashes and return to login screen

[Daniel van Vugt]

It looks like the information we're missing is in /usr/lib/x86_64-linux-
gnu/dri/iris_dri.so so please install:

  https://launchpad.net/ubuntu/+archive/primary/+files/libgl1-mesa-dri-
dbgsym_20.2.6-0ubuntu0.20.04.1_amd64.ddeb

and then after the next crash and reboot, send us another:

  journalctl -b-1 > prevboot.txt

Or if you didn't need to reboot then please:

  journalctl -b0 > curboot.txt

Also, you don't need to rename .ddeb files. You can just install them
with:

  sudo dpkg -i *.ddeb

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

Title:
  [DisplayLink] Xorg crashes and return to login screen

Status in evdi package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  The bug is that all at a sudden gnome reset to login screen. When i
  log again, the only "sound output" allowed is simulation, my devices
  are not displayed.

  I'm using 
  - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug 
was present at that moment but i used less my ubuntu station). 
  - Portable PC

  The bug happen
  - When I use my PC with screen pluged directly : some times
  - When I use my docking station with 144Hz display in DVI 
(https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
  - When à Use my docking station and watch some full screen video : very 
frequently

  It seems to be linked to displayLink use, but not only because it
  happen too when i don't use the docking station. It seems to be
  frequently when i "Stress" the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 10:17:54 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-08 (1183 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1914573/+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 1913217] Re: nvidia kernel module freezing/crashing repeatedly on GeForce GT 330M

[Daniel van Vugt]

** Summary changed:

- [nvidia] Screen going black and not responding to input
+ nvidia kernel module freezing/crashing repeatedly on GeForce GT 330M

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

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: Incomplete => New

** Summary changed:

- nvidia kernel module freezing/crashing repeatedly on GeForce GT 330M
+ nvidia (v340) kernel module freezing/crashing repeatedly on GeForce GT 330M

** Tags removed: 5.8-gfx

** No longer affects: linux-signed-hwe-5.8 (Ubuntu)

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

Title:
  nvidia (v340) kernel module freezing/crashing repeatedly on GeForce GT
  330M

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

Bug description:
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  xorg:
Installed: 1:7.7+19ubuntu14
Candidate: 1:7.7+19ubuntu14
Version table:
   *** 1:7.7+19ubuntu14 500
  500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Expecting:
  (usually after opening a new application): window to open

  Happened instead:
  Screen going black. System not responding to inputs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 25 21:49:05 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.108, 5.4.0-42-generic, x86_64: installed
   nvidia-340, 340.108, 5.8.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
   NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Apple Inc. GT216M [GeForce GT 330M] [106b:00c7]
  InstallationDate: Installed on 2021-01-24 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Apple Inc. MacBookPro6,2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic 
root=UUID=22238608-1c5f-40aa-a8f4-1fded14f6b84 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2019
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 99.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F22586C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro6,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22586C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvr99.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro6,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: 

[Desktop-packages] [Bug 1903986] Re: Ubuntu 20.04 freezes with remmina in full-screen

[Daniel van Vugt]

Thanks for all that. It certainly looks like a freeze because gnome-
shell is still running when you reboot the machine.

As a potential workaround, please try 'Ubuntu on Wayland' which is an
option on the login screen just before you enter your password.

Please also confirm you are not using any gnome-shell extensions other
than the Ubuntu ones (look in the 'Extensions' app).

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

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

Title:
  Ubuntu 20.04 freezes with remmina in full-screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 20.04 using Remmina accessing remote Windows session to my
  work and everything was working fine for 5 hours and then suddenly
  Reminna freezes. Mouse pointer still working fine, but Remmina not
  responding and also keyboard not responding (maybe because all of the
  keys are controller by Remmina).

  This problem is now third time the problem appeared:
  - bug 1902051
  - bug 1903710
  with no response. :(

  Work-around: hard press power button to power off  laptop and power on
  it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: remmina 1.4.2+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 12 12:38:25 2020
  InstallationDate: Installed on 2019-10-23 (386 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: remmina
  UpgradeStatus: Upgraded to focal on 2020-08-14 (89 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-23 (392 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-08-14 (95 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+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 1886345] Re: [i915][snb] Icons and text corrupted and/or missing in 20.04

[Daniel van Vugt]

Sorry to hear that. Also if the corruption regressed further then that
was probably a different bug.

If you can still reproduce the regressed behaviour on a 20.04 machine
then please open a new bug about it with photos or video.

If you are not able to keep using 20.04 then no future fixes would be
verifiable and this bug will automatically close after 60 days.

If such problems ever happen again then instead of downgrading the OS
you should try just installing an older kernel from
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D


** Summary changed:

- [i915][snb] Icons and text corrupted and/or missing
+ [i915][snb] Icons and text corrupted and/or missing in 20.04

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

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

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

Title:
  [i915][snb] Icons and text corrupted and/or missing in 20.04

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

Bug description:
  This is a fresh install of 2020.04.
  Issue is that the display routinely gets corrupted and flickers with blocks 
of previously open windows. 
  If left without a restart, the system menu text will get replaced by odd 
characters and system dialog boxes will not display, buttons for the dialog 
boxes will briefly appear with no text when cursor is over them.
  Very occasionally, the system will stop responding to the mouse and keyboard 
after clicking an icon on the dash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  5 15:24:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-05-03 (63 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886345/+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 1875037] Re: Turning off high contrast does not revert the desktop icons' appearance

[Daniel van Vugt]

** Tags added: groovy

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

Title:
  Turning off high contrast does not revert the desktop icons'
  appearance

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Confirmed

Bug description:
  When going to Settings -> Universal Access and selecting "High
  Contrast" to view the difference in appearance, then switching "High
  Contrast" to off, the icons do not return to their normal appearance.
  I did not find a place in this bug submission interface to submit
  attachments or I would show you screen capture of the changes in the
  icon appearance.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 25 10:48:21 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA 
controller])
 Subsystem: Gigabyte Technology Co., Ltd UHD Graphics 630 (Desktop) 
[1458:d000]
  InstallationDate: Installed on 2020-03-31 (24 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330)
  MachineType: Gigabyte Technology Co., Ltd. H370 WIFI
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=8d24e3f8-c08c-444a-8467-4f9473fa4a22 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F14
  dmi.board.asset.tag: Default string
  dmi.board.name: H370N WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF14:bd06/05/2019:svnGigabyteTechnologyCo.,Ltd.:pnH370WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: H370 WIFI
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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 20.0.4-2ubuntu1
  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-control-center/+bug/1875037/+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 660504] Re: pacat --file-format option doesn't work

[Daniel van Vugt]

Since this bug was closed 10 years ago it would be best to open a new
open to track the problem in 20.04. Please run this command to open a
new bug:

  ubuntu-bug pulseaudio

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

Title:
  pacat --file-format option doesn't work

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  When I want to record audio with pacat I run a command like this:

  $ pacat -r outfile

  This works, but if I want the output file to have a specific format
  other than raw, e.g. WAV or AU format, the man page states that I can
  use "--file-format=FFORMAT". But this doesn't work, it always just
  creates an empty file and then prints "Failed to open audio file."
  Like this:

  $ pacat -r --file-format=wav outfile.wav
  Failed to open audio file.
  $ ls -l outfile.wav
  -rw-r--r-- 1 th th 0 2010-10-14 13:23 outfile.wav

  Pretty useless error message too, if you ask me, because obviously it
  succeeded in opening the file (since it was created)..

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: pulseaudio-utils 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  th10977 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfdffc000 irq 45'
 Mixer name : 'Analog Devices AD1984'
 Components : 'HDA:11d41984,10280214,00100400'
 Controls  : 21
 Simple ctrls  : 14
  Date: Thu Oct 14 12:20:28 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 
(20100419.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  dmi.bios.date: 08/14/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0TP412
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/14/2008:svnDellInc.:pnPrecisionWorkStationT3400:pvr:rvnDellInc.:rn0TP412:rvr:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T3400
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/660504/+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 1754069] Re: Restore type-ahead find in Ubuntu 17.10 and later

[Ubuntu Foundations Team Bug Bot]

The attachment "completely untested debdiff for hirsute" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  Restore type-ahead find in Ubuntu 17.10 and later

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I'm opening this because I can't change back the status of issue
  1164016 back from "fix released" (which is so stupid by the way: IF I
  can change the status from any other status, why shouldn't I be able
  to change it from "fix released"? Nonsense)

  https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1164016

  Many users have reported the bug is back on 17.10.
  I can't think of any reason why it should take more than a few minutes to fix 
it back for 17.10, other than maybe nobody among the people who were 
responsible for the fix have noticed yet.

  Feel free to mark this as duplicate *after* you reopen #1164016

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar  7 16:29:37 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1254x928+65+124'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (1607 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754069/+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 1754069] Re: Restore type-ahead find in Ubuntu 17.10 and later

[Rolf Leggewie]

unfortunately, this fails to build in bionic ATM

https://launchpad.net/~r0lf/+archive/ubuntu/stable/+build/20997867

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

Title:
  Restore type-ahead find in Ubuntu 17.10 and later

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I'm opening this because I can't change back the status of issue
  1164016 back from "fix released" (which is so stupid by the way: IF I
  can change the status from any other status, why shouldn't I be able
  to change it from "fix released"? Nonsense)

  https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1164016

  Many users have reported the bug is back on 17.10.
  I can't think of any reason why it should take more than a few minutes to fix 
it back for 17.10, other than maybe nobody among the people who were 
responsible for the fix have noticed yet.

  Feel free to mark this as duplicate *after* you reopen #1164016

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar  7 16:29:37 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1254x928+65+124'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (1607 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

[Simon Iremonger]

Although in this bug, marked 'fix committed' for focal a while now, I can't 
find the new thunderbird package in either focal-proposed nor focal-security .  
Also not shown on https://launchpad.net/ubuntu/focal/+queue      Any ideas? 
 -- be useful to see what package queues/links should be known about, and in 
any case, what happened to the committed fix.
With thanks!.

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

Title:
  Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Bionic:
  Triaged
Status in thunderbird source package in Focal:
  Fix Committed
Status in thunderbird source package in Groovy:
  Fix Released

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

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

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

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

[Desktop-packages] [Bug 1754069] Re: Restore type-ahead find in Ubuntu 17.10 and later

[Rolf Leggewie]

found a previous patch that applies cleanly to bionic

** Patch added: "completely untested debdiff for bionic"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754069/+attachment/5461155/+files/lp1754069-hirsute.debdiff

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

Title:
  Restore type-ahead find in Ubuntu 17.10 and later

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I'm opening this because I can't change back the status of issue
  1164016 back from "fix released" (which is so stupid by the way: IF I
  can change the status from any other status, why shouldn't I be able
  to change it from "fix released"? Nonsense)

  https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1164016

  Many users have reported the bug is back on 17.10.
  I can't think of any reason why it should take more than a few minutes to fix 
it back for 17.10, other than maybe nobody among the people who were 
responsible for the fix have noticed yet.

  Feel free to mark this as duplicate *after* you reopen #1164016

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar  7 16:29:37 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1254x928+65+124'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (1607 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754069/+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 1754069] Re: Restore type-ahead find in Ubuntu 17.10 and later

[Rolf Leggewie]

Unfortunately, the sources do not apply cleanly to bionic.  We probably
need an older patch.

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

Title:
  Restore type-ahead find in Ubuntu 17.10 and later

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I'm opening this because I can't change back the status of issue
  1164016 back from "fix released" (which is so stupid by the way: IF I
  can change the status from any other status, why shouldn't I be able
  to change it from "fix released"? Nonsense)

  https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1164016

  Many users have reported the bug is back on 17.10.
  I can't think of any reason why it should take more than a few minutes to fix 
it back for 17.10, other than maybe nobody among the people who were 
responsible for the fix have noticed yet.

  Feel free to mark this as duplicate *after* you reopen #1164016

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar  7 16:29:37 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1254x928+65+124'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (1607 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754069/+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 1754069] Re: Restore type-ahead find in Ubuntu 17.10 and later

[Rolf Leggewie]

** Patch added: "completely untested debdiff for hirsute"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754069/+attachment/5461153/+files/lp1754069-hirsute.debdiff

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

Title:
  Restore type-ahead find in Ubuntu 17.10 and later

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I'm opening this because I can't change back the status of issue
  1164016 back from "fix released" (which is so stupid by the way: IF I
  can change the status from any other status, why shouldn't I be able
  to change it from "fix released"? Nonsense)

  https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1164016

  Many users have reported the bug is back on 17.10.
  I can't think of any reason why it should take more than a few minutes to fix 
it back for 17.10, other than maybe nobody among the people who were 
responsible for the fix have noticed yet.

  Feel free to mark this as duplicate *after* you reopen #1164016

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar  7 16:29:37 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1254x928+65+124'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (1607 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754069/+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 1754069] Re: Restore type-ahead find in Ubuntu 17.10 and later

[Rolf Leggewie]

$ QUILT_PATCHES=debian/patches/ quilt push
Applying patch debian/patches//nautilus-restore-typeahead.patch
patching file data/org.gnome.nautilus.gschema.xml
Hunk #1 succeeded at 195 (offset 3 lines).
patching file src/nautilus-global-preferences.h
patching file src/nautilus-list-view.c
Hunk #1 succeeded at 3121 (offset 41 lines).
Hunk #2 succeeded at 3153 (offset 41 lines).
Hunk #3 succeeded at 4187 (offset 97 lines).
patching file src/nautilus-list-view.h
patching file src/nautilus-window-slot.c
Hunk #2 succeeded at 131 with fuzz 2 (offset 2 lines).
Hunk #3 succeeded at 263 (offset 22 lines).
Hunk #4 succeeded at 794 (offset 30 lines).
Hunk #5 succeeded at 1411 (offset 44 lines).
Hunk #6 succeeded at 3272 (offset 61 lines).
Hunk #7 succeeded at  (offset 61 lines).
Hunk #8 succeeded at 3862 (offset 122 lines).
Hunk #9 succeeded at 3948 with fuzz 2 (offset 157 lines).

Now at patch debian/patches//nautilus-restore-typeahead.patch

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

Title:
  Restore type-ahead find in Ubuntu 17.10 and later

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I'm opening this because I can't change back the status of issue
  1164016 back from "fix released" (which is so stupid by the way: IF I
  can change the status from any other status, why shouldn't I be able
  to change it from "fix released"? Nonsense)

  https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1164016

  Many users have reported the bug is back on 17.10.
  I can't think of any reason why it should take more than a few minutes to fix 
it back for 17.10, other than maybe nobody among the people who were 
responsible for the fix have noticed yet.

  Feel free to mark this as duplicate *after* you reopen #1164016

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar  7 16:29:37 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1254x928+65+124'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (1607 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754069/+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 1754069] Re: Restore type-ahead find in Ubuntu 17.10 and later

[Rolf Leggewie]

FWIW, the patch from arch at least still applies cleanly to the hirsute
sources

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

Title:
  Restore type-ahead find in Ubuntu 17.10 and later

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I'm opening this because I can't change back the status of issue
  1164016 back from "fix released" (which is so stupid by the way: IF I
  can change the status from any other status, why shouldn't I be able
  to change it from "fix released"? Nonsense)

  https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1164016

  Many users have reported the bug is back on 17.10.
  I can't think of any reason why it should take more than a few minutes to fix 
it back for 17.10, other than maybe nobody among the people who were 
responsible for the fix have noticed yet.

  Feel free to mark this as duplicate *after* you reopen #1164016

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar  7 16:29:37 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1254x928+65+124'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (1607 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754069/+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 1164016] Re: restore type-ahead find

[Rolf Leggewie]

This discussion should be continued in the following places in a civil
(!) manner.

Uncivilized language, no matter how angry you are, is likely only to
have the effect of alienating the people in charge.  It's in your own
interest to stay civil if you want to get the old behaviour restored.
No need for any comments, really, just upvote as "being affected" in the
two below tickets if you'd like to see this problem fixed.

bug 1914962: replace nautilus with alternative default file manager
bug 1751069: restore type-ahead find in nautilus itself

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1754069] Re: Restore type-ahead find in Ubuntu 17.10 and later

[Rolf Leggewie]

@teo1978: I (and hundreds others as seen in bug 1164016 share your
pain), but your tone and choice of language isn't helping your case.

At this point in time, it's probably best to use one of the alternatives
and possibly push for them to be made the default.  I opened bug
1914962.  If you prefer to keep using nautilus, I'm happy to see if the
Arch patch being offered in bug 1164016 comment 149 can fix this issue
once more and if Ubuntu is willing to consider using it as well.

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

Title:
  Restore type-ahead find in Ubuntu 17.10 and later

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I'm opening this because I can't change back the status of issue
  1164016 back from "fix released" (which is so stupid by the way: IF I
  can change the status from any other status, why shouldn't I be able
  to change it from "fix released"? Nonsense)

  https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1164016

  Many users have reported the bug is back on 17.10.
  I can't think of any reason why it should take more than a few minutes to fix 
it back for 17.10, other than maybe nobody among the people who were 
responsible for the fix have noticed yet.

  Feel free to mark this as duplicate *after* you reopen #1164016

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar  7 16:29:37 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1254x928+65+124'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (1607 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754069/+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 1914962] [NEW] consider replacing nautilus as default file-manager in favor of one of the alternatives

[Rolf Leggewie]

Public bug reported:

There is a vocal group of users with at times good and reasonable
arguments pushing hard to replace nautilus as the default browser in
Ubuntu.  I'd like to open up this discussion here in public.  I kindly
ask to please keep it open for a while to allow some discussion.  I'll
equally strongly appeal to everyone to keep discussion civil or else
this ticket shall be closed prematurely.

bug 1164016
Gnome made search instead of type-ahead the default, Ubuntu devs agreed this 
was a poor choice and patched the new behaviour out.  But this regressed back 
to upstream behaviour in 18.04. and is still the behaviour in Ubuntu+1.

Please let me hear your (again, civil!) arguments about why you think
nautilus is a poor default choice for Ubuntu and I will include them in
this initial comment for everyone's benefit.

Options put forward:
- nemo (a nautilus fork available in Ubuntu univers, Cinnamon default)

** Affects: ubuntu
 Importance: Undecided
 Status: New

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

** Description changed:

  There is a vocal group of users with at times good and reasonable
  arguments pushing hard to replace nautilus as the default browser in
  Ubuntu.  I'd like to open up this discussion here in public.  I kindly
  ask to please keep it open for a while to allow some discussion.  I'll
  equally strongly appeal to everyone to keep discussion civil or else
  this ticket shall be closed prematurely.
  
  bug 1164016
  Gnome made search instead of type-ahead the default, Ubuntu devs agreed this 
was a poor choice and patched the new behaviour out.  But this regressed back 
to upstream behaviour in 18.04. and is still the behaviour in Ubuntu+1.
  
  Please let me hear your (again, civil!) arguments about why you think
  nautilus is a poor default choice for Ubuntu and I will include them in
  this initial comment for everyone's benefit.
+ 
+ Options put forward:
+ - nemo (a nautilus fork available in Ubuntu univers, Cinnamon default)

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

Title:
  consider replacing nautilus as default file-manager in favor of one of
  the alternatives

Status in Ubuntu:
  New

Bug description:
  There is a vocal group of users with at times good and reasonable
  arguments pushing hard to replace nautilus as the default browser in
  Ubuntu.  I'd like to open up this discussion here in public.  I kindly
  ask to please keep it open for a while to allow some discussion.  I'll
  equally strongly appeal to everyone to keep discussion civil or else
  this ticket shall be closed prematurely.

  bug 1164016
  Gnome made search instead of type-ahead the default, Ubuntu devs agreed this 
was a poor choice and patched the new behaviour out.  But this regressed back 
to upstream behaviour in 18.04. and is still the behaviour in Ubuntu+1.

  Please let me hear your (again, civil!) arguments about why you think
  nautilus is a poor default choice for Ubuntu and I will include them
  in this initial comment for everyone's benefit.

  Options put forward:
  - nemo (a nautilus fork available in Ubuntu univers, Cinnamon default)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1914962/+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 1914918] Re: The snap being updated in the background causes both old and new tabs to die to SIGTRAP

[Launchpad Bug Tracker]

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

Title:
  The snap being updated in the background causes both old and new tabs
  to die to SIGTRAP

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  The last few background updates of chromium have made some old tabs
  suddenly crash with SIGTRAP and it also makes it impossible to open
  new tabs, those die instantly with a SIGTRAP as well.

  This is incredibly destructive to whatever might be the dying tabs'
  unsaved state and there's no warning about it. Yet again a snap-
  related change rolled out to users with absolutely amateur-tier
  testing.

  Ubuntu: 20.04.2
  Snap: 2.48+20.04
  Chromium: 88.0.4324.150

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1914918/+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 1747706] Re: 'copy to clipboard' only copy/pastes the first 127 rows into gimp

[Rolf Leggewie]

FWIW, works fine for me in bionic

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

Title:
  'copy to clipboard' only copy/pastes the first 127 rows into gimp

Status in gimp package in Ubuntu:
  New
Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  0) have a gimp running
  1) run gnome-screenshot
  2) take screen shot
  3) click copy to clipboard
  4) alt-tab to gimp
  5) edit
  6) paste as new image

  The new image has 127 rows of the screenshot data followed by the
  correct number of other rows EXCEPT the other rows are of a single
  greyish colour (0x979899).

  (Saving the screenshot to file, and opening file in gimp works fine as
  a workaround for opening screen data in gimp)

  What should happen

  When you 'copy to clipboard' it should copy the whole image to clipboard.
  and 'paste' should retrieve the image data from clipboard into the gimp 
canvas.

  (Whether this is a gimp issue retrieving from clipboard or gnome-
  screenshot giving the data to clipboard I am not sure, but somewhere
  the clipboard data is not being passed properly)

   Ubuntu : 17.10 artful
   Desktop: gnome/wayland
   gimp : 2.8.20-1
   gnome-screenshot : 3.25.0-0ubuntu2

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-screenshot 3.25.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  6 11:07:59 2018
  InstallationDate: Installed on 2017-04-18 (293 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to artful on 2017-10-19 (109 days ago)

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

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

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

[Bill (franksmcb)]

Some follow-up with users from the Ubuntu MATE Community forums show
that this is occurring on Focal and Groovy; with 5.4, 5.8, and 5.10
kernels.


Following is a list of hardware and graphics information from affected users:

System:
  Host: huppyryzen Kernel: 5.4.0-54-generic x86_64 bits: 64 
  Desktop: MATE 1.24.0 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) 
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x 
  serial:  UEFI: American Megatrends v: 5602 
  date: 07/14/2020 
Graphics:
  Device-1: AMD Vega 10 XL/XT [Radeon RX Vega 56/64] driver: amdgpu 
  v: kernel 
  Display: x11 server: X.Org 1.20.8 driver: amdgpu,ati 
  unloaded: fbdev,modesetting,vesa resolution: 3440x1440~60Hz 
  OpenGL: 
  renderer: Radeon RX Vega (VEGA10 DRM 3.35.0 5.4.0-54-generic LLVM 11.0.0) 
  v: 4.6 Mesa 20.3.0-rc2

System:
  Host: marptop Kernel: 5.4.0-54-generic x86_64 bits: 64 
  Desktop: MATE 1.24.0 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) 
Machine:
  Type: Laptop System: HP product: HP Laptop 17-ca0xxx v: N/A 
  serial:  
  Mobo: HP model: 84D2 v: 91.17 serial:  UEFI: AMI 
  v: F.21 date: 11/15/2018 
Graphics:
  Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] 
  driver: amdgpu v: kernel 
  Display: x11 server: X.Org 1.20.8 driver: amdgpu,ati 
  unloaded: fbdev,modesetting,vesa resolution: 1600x900~60Hz 
  OpenGL: renderer: AMD RAVEN (DRM 3.35.0 5.4.0-54-generic LLVM 10.0.0) 
  v: 4.6 Mesa 20.0.8

System:
Host: duck-laptop2 Kernel: 5.8.0-29-generic x86_64 bits: 64 Desktop: MATE 
1.24.1 
Distro: Ubuntu 20.10 (Groovy Gorilla) 
Machine:   
Type: Laptop System: HP product: HP Laptop 15-db0xxx v: 
Type1ProductConfigId serial:  
Mobo: HP model: 84AE v: 86.20 serial:  UEFI: 
Insyde v: F.10 date: 05/31/2018 
Graphics: 
Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] 
driver: amdgpu v: kernel 
Device-2: Lite-On 1351 type: USB driver: uvcvideo 
Display: x11 server: X.Org 1.20.9 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa resolution: 1920x1080~60Hz 
OpenGL: renderer: AMD RAVEN (DRM 3.38.0 5.8.0-29-generic LLVM 11.0.0) v: 
4.6 Mesa 20.2.1

System:
Host: jgjmate-ThinkPad-E595 Kernel: 5.8.0-32-generic x86_64 bits: 64
Desktop: MATE 1.24.1 Distro: Ubuntu 20.10 (Groovy Gorilla)
Machine:
Type: Laptop System: LENOVO product: 20NF0012US v: ThinkPad E595
serial: 
Mobo: LENOVO model: 20NF0012US serial: 
UEFI: LENOVO v: R11ET39W (1.19 ) date: 09/11/2020
Graphics:
Device-1: AMD Picasso driver: amdgpu v: kernel
Device-2: Acer SunplusIT Integrated Camera type: USB driver: uvcvideo
Display: x11 server: X.Org 1.20.9 driver: amdgpu,ati
unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: AMD RAVEN (DRM 3.38.0 5.8.0-32-generic LLVM 11.0.0)
v: 4.6 Mesa 20.2.1

System:
Host:  Kernel: 5.4.0-58-generic x86_64 bits: 64
Desktop: MATE 1.24.0 Distro: Ubuntu 20.04.1 LTS (Focal Fossa)
Machine:
Type: Laptop System: HP product: HP Laptop 15-db0xxx
v: Type1ProductConfigId serial: 
Mobo: HP model: 84AC v: 85.26 serial: 
UEFI: Insyde v: F.22 date: 11/06/2019
Graphics:
Device-1: AMD Stoney [Radeon R2/R3/R4/R5 Graphics] driver: amdgpu
v: kernel
Display: x11 server: X.Org 1.20.8 driver: amdgpu,ati
unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz
OpenGL: renderer: AMD STONEY (DRM 3.35.0 5.4.0-58-generic LLVM 10.0.0)
v: 4.5 Mesa 20.0.8

System:
Host: pc Kernel: 5.4.0-58-generic x86_64 bits: 64 Desktop: MATE 1.24.0 
Distro: Ubuntu 20.04.1 LTS (Focal Fossa) 
Machine:   
Type: Desktop Mobo: MSI model: B75MA-P45 (MS-7798) v: 1.0 serial: 
 
BIOS: American Megatrends v: 1.9 date: 09/30/2013 
Graphics:  
Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 
XT / 5700/5700 XT] driver: amdgpu 
v: kernel 
Display: x11 server: X.Org 1.20.8 driver: amdgpu,ati unloaded: 
fbdev,modesetting,radeon,vesa 
resolution: 1366x768~60Hz 
OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.38.0 5.4.0-58-generic 
LLVM 11.0.0) 
v: 4.6 Mesa 21.0.0-devel (git-6a34a68 2020-12-13 focal-oibaf-ppa)

System:
Host: ACER-xk2308 Kernel: 5.10.4-051004-generic x86_64 bits: 64 Desktop: 
MATE 1.24.0 
Distro: Ubuntu 20.04.1 LTS (Focal Fossa) 
Machine:   
Type: Desktop Mobo: MSI model: B75MA-P45 (MS-7798) v: 1.0 serial: 
 
BIOS: American Megatrends v: 1.9 date: 09/30/2013 
Graphics:  
Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 
XT / 5700/5700 XT] driver: amdgpu 
v: kernel 
Display: x11 server: X.Org 1.20.8 driver: amdgpu,ati unloaded: 
fbdev,modesetting,radeon,vesa 
resolution: 1366x768~60Hz 
OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.40.0 
5.10.4-051004-generic LLVM 11.0.0) 
v: 4.6 Mesa 21.0.0-devel (git-24dcdc3 2021-01-04 focal-oibaf-ppa)

System:
Host: ACER-xk2308 Kernel: 5.8.0-38-generic 

[Desktop-packages] [Bug 1887804] Re: chromium-browser does not follow XDG base directory specification

[Mike Carifio]

I'm also confused about the expected settings of
XDG_{CACHE,CONFIG,DATA}_HOME in a snap and their relationship(s) to
SNAP_USER_{COMMON,DATA}. Unfortunately, chromium isn't a good example to
disentagle them. Chromium (or chrome) doesn't seem to respect these
values either.

Rather than state what chromium uses (and yes, it's an important
example), can you @osoman state what they _should_ be? My understanding
is that XDG_CACHE_HOME defaults to $HOME/.cache, XDG_CONFIG_HOME
defaults to $HOME/.config and XDG_DATA_HOME defaults to
$HOME/.local/share. And it would appear that well-behaved snaps do that.
However, since $HOME in a snap includes it's revision (not classic
containment), that means that a new revision starts those locations
afresh (or the first start of the new revision copies over the previous
directories). I find this behavior a little surprising, even given the
"security benefit" that confinement brings. In a sense, "my" data in
.local/**, .config/** and ./cache/** is really now less mine and I have
to know a little bit more about the directory tree at
~mcarifio/snap/${snap}/**. And I have to pay attention to when snaps
update because my configuration(s) might disappear for a misbehaving
snap.

It appears that the Intellij tools use classic confinement for this
reason, since a new major revision will "copy over" the previous
configuration when it first starts. But the app does that, not the
underlying snap machinery.

xdg also adds to the potential confusion with .config/user-dirs.dirs,
used when XDG_* isn't exported. And unfortunately SNAP_USER_{COMMON,
DATA} seem to actually be independent of XDG_* although the names
suggest (to me anyways) that SNAP_USER_DATA might play a role similar to
XDG_DATA_HOME. Yes, that's because I can't read :-), not because that's
stated at https://snapcraft.io/docs/environment-variables. Nonetheless,
the descriptions are terse. Perhaps a sentence like "not be confused
with XDG_DATA_HOME" would help.

I understand I'm recapitulating some of the thread above with less ummm
enthusiasm and this is better discussed in the snapcraft forum. I think
snaps bring a lot to the table, but when something breaks or is
confusing, then I think we (the snap consumers) suddenly become very
interested in the details of the packaging. And not by choice. Snaps are
different. They make different assumptions (sandboxing, interfaces,
multiple versions). And "personal configuration" e.g. .config/${sofware}
and .local/share/${software}, is in that gray area between what's "mine"
and what's "the app's". I don't have an answer to that. Just look at all
the github repos for dotfiles. There are even directories of dotfiles
https://github.com/webpro/awesome-dotfiles and dotfile managers like
stow. But I would like to understand a little better how the "snap game"
is played so I can leverage it's strengths and avoid its pitfalls. I do
work to incorporate a tool into my workflow and XDG tells me to put that
work in certain locations e.g. $HOME/.config/${pkg} and
$HOME/.local/share/${pkg} for XDG compliant apps. HOME can't just move
around willynilly for security's sake. It's nice to "know where to go"
and go to one place. Snap's packages can respect XDG and still confuse
because HOME is remapped on each revision and when a program is run. If
you miss that detail, you're in for a world of hurt. Historically
software updates didn't touch the XDG directories. Snap does. In
something of an intelligent way certainly. But packaging mistakes happen
all the time. Configuration files are missing. Or wrong. At some point,
I know I'll be forced to repair something somewhere because I do it at
least every week. Currently snaps make that a little harder, but perhaps
in time will make it a lot better.

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

Title:
  chromium-browser does not follow XDG base directory specification

Status in Chromium Browser:
  Invalid
Status in chromium-browser package in Ubuntu:
  Opinion

Bug description:
  Currently Chromium does not follow the XDG base directory
  specification which means that the cache and configuration folder
  aren't properly used.

  This causes the issue that it's nearly impossible to properly migrate
  or back up Chromium configuration (between computers) and it makes for
  example mounting cache as tmpfs or wiping it very very difficult.

  I felt those both immensely when trying to migrate my home folder,
  gigabytes of cache in ~/snap/chromium/[id]/.config/chromium/[folder]
  (and ~/snap itself is also not XDG base directory specification
  compliant, shame!).

  There's also the issue that the previous configuration that is located
  properly, isn't migrated by the migrational package.

  In order to fix this bug, it would require making the snap package
  follow the XDG base directory specification.

To manage notifications 

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

[Nicolas Rogues]

Hi Coiby

To answer your question in message #359
> In hybrid mode, does external monitor work for you?

The answer is yes, it works. I tested the hotplug of an HDMI external
monitor, it was detected by Ubuntu 20.04 and worked by default as an
extended desktop (both internal & external display used, not cloned).

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

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

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

Bug description:
  Update (based on #296)
  =

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

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

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

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

  Original bug report
  ===

  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  

[Desktop-packages] [Bug 1914947] [NEW] My display is so slow

[Balashanmugam]

Public bug reported:

My display performance is so slow sometimes it will crash or resolution
is bad

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: hostname 5.8.0-41.46~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-41-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: Sun Feb  7 23:02:45 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2021-02-05 (1 days ago)
InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. VMware Virtual USB Mouse
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware7,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=fd8451d8-78e6-471e-aa1e-cae417c043fb ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/10/2020
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW71.00V.16722896.B64.2008100651
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnVMware,Inc.:bvrVMW71.00V.16722896.B64.2008100651:bd08/10/2020:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware7,1
dmi.product.version: None
dmi.sys.vendor: VMware, 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 20.2.6-0ubuntu0.20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal resolution 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/1914947

Title:
  My display is so slow

Status in xorg package in Ubuntu:
  New

Bug description:
  My display performance is so slow sometimes it will crash or
  resolution is bad

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: hostname 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-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: Sun Feb  7 23:02:45 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2021-02-05 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. VMware Virtual USB Mouse
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware7,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=fd8451d8-78e6-471e-aa1e-cae417c043fb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2020
  dmi.bios.vendor: VMware, Inc.
  dmi.bios.version: VMW71.00V.16722896.B64.2008100651
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 

[Desktop-packages] [Bug 660504] Re: pacat --file-format option doesn't work

[guest271314]

#5 This is still an issue on 20.04 LTS
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/822

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

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

Title:
  pacat --file-format option doesn't work

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  When I want to record audio with pacat I run a command like this:

  $ pacat -r outfile

  This works, but if I want the output file to have a specific format
  other than raw, e.g. WAV or AU format, the man page states that I can
  use "--file-format=FFORMAT". But this doesn't work, it always just
  creates an empty file and then prints "Failed to open audio file."
  Like this:

  $ pacat -r --file-format=wav outfile.wav
  Failed to open audio file.
  $ ls -l outfile.wav
  -rw-r--r-- 1 th th 0 2010-10-14 13:23 outfile.wav

  Pretty useless error message too, if you ask me, because obviously it
  succeeded in opening the file (since it was created)..

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: pulseaudio-utils 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  th10977 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfdffc000 irq 45'
 Mixer name : 'Analog Devices AD1984'
 Components : 'HDA:11d41984,10280214,00100400'
 Controls  : 21
 Simple ctrls  : 14
  Date: Thu Oct 14 12:20:28 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 
(20100419.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  dmi.bios.date: 08/14/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0TP412
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/14/2008:svnDellInc.:pnPrecisionWorkStationT3400:pvr:rvnDellInc.:rn0TP412:rvr:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T3400
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/660504/+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 1853784] Re: Format button has no effect when I right click a USB and select Format

[Eugene]

Same problem in Ubuntu 20.04.2 LTS
"org.gnome.Nautilus[12977]: Не удалось разобрать целочисленное значение 
«2a7» для --xid"

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

Title:
  Format button has no effect when I right click a USB and select Format

Status in Nautilus:
  New
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Whenever I boot up ubuntu and attempt to format a plugged-in or
  mounted USB, the Format button has no effect when clicked on; not even
  an error message. If there is an error, Ubuntu should let me know or
  not allow me to format by disabling to format option.

  Steps to Reproduce:
  1. Boot up Ubuntu on the hard disk with a live-usb of ubuntu plugged in (this 
will be the USB to attempt to format)
  2. Log in and open Files
  3. Right-click the USB and select "Format"

  Expected Results:
  Either the Format menu appears, an error message appears if I am unable to 
format the disk, or the Format button is disabled.

  Actual Results:
  Files allows the format button to be clicked, but nothing happens when it is 
clicked on.

  Description:  Ubuntu 19.10
  Release:  19.10

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 24 17:22:27 2019
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'260'
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
  InstallationDate: Installed on 2019-11-20 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-24T17:17:29.098099
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1853784/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

[Francisco A . Hernández]

Same issue here. As many others here, I need to use the mic at work's
meetings and I needed to spent extra money on a wired headset because of
this bug made my airpods useless for the task.

elementary OS 5.1.7 Hera, Built on Ubuntu 18.04.4 LTS.
Linux 4.15.0-135-generic.

$pactl list cards
Card #0
Name: alsa_card.pci-_00_1b.0
Driver: module-alsa-card.c
Owner Module: 7
Properties:
alsa.card = "0"
alsa.card_name = "HDA Intel"
alsa.long_card_name = "HDA Intel at 0xf000 irq 26"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1b.0"
sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "27d8"
device.product.name = "NM10/ICH7 Family High Definition Audio 
Controller"
device.form_factor = "internal"
device.string = "0"
device.description = "Built-in Audio"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
Profiles:
input:analog-stereo: Analog Stereo Input (sinks: 0, sources: 1, 
priority: 60, available: no)
output:analog-stereo: Analog Stereo Output (sinks: 1, sources: 
0, priority: 6000, available: yes)
output:analog-stereo+input:analog-stereo: Analog Stereo Duplex 
(sinks: 1, sources: 1, priority: 6060, available: yes)
output:iec958-stereo: Digital Stereo (IEC958) Output (sinks: 1, 
sources: 0, priority: 5500, available: yes)
output:iec958-stereo+input:analog-stereo: Digital Stereo 
(IEC958) Output + Analog Stereo Input (sinks: 1, sources: 1, priority: 5560, 
available: yes)
off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
Active Profile: output:analog-stereo+input:analog-stereo
Ports:
analog-input-mic: Microphone (priority: 8700, latency offset: 0 
usec, not available)
Properties:
device.icon_name = "audio-input-microphone"
Part of profile(s): input:analog-stereo, 
output:analog-stereo+input:analog-stereo, 
output:iec958-stereo+input:analog-stereo
analog-output-speaker: Speakers (priority: 1, latency 
offset: 0 usec)
Properties:
device.icon_name = "audio-speakers"
Part of profile(s): output:analog-stereo, 
output:analog-stereo+input:analog-stereo
analog-output-headphones: Headphones (priority: 9000, latency 
offset: 0 usec, not available)
Properties:
device.icon_name = "audio-headphones"
Part of profile(s): output:analog-stereo, 
output:analog-stereo+input:analog-stereo
iec958-stereo-output: Digital Output (S/PDIF) (priority: 0, 
latency offset: 0 usec)
Part of profile(s): output:iec958-stereo, 
output:iec958-stereo+input:analog-stereo

Card #7
Name: bluez_card.AC_80_1C_01_34_B0
Driver: module-bluez5-device.c
Owner Module: 33
Properties:
device.description = "Baseus Encok W04 Pro"
device.string = "AC:80:1C:01:34:B0"
device.api = "bluez"
device.class = "sound"
device.bus = "bluetooth"
device.form_factor = "headset"
bluez.path = "/org/bluez/hci0/dev_AC_80_1C_01_34_B0"
bluez.class = "0x240404"
bluez.alias = "Baseus Encok W04 Pro"
device.icon_name = "audio-headset-bluetooth"
device.intended_roles = "phone"
Profiles:
a2dp_sink: High Fidelity Playback (A2DP Sink) (sinks: 1, 
sources: 0, priority: 40, available: yes)
headset_head_unit: Headset Head Unit (HSP/HFP) (sinks: 1, 
sources: 1, priority: 30, available: no)
off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
Active Profile: off
Ports:
headset-output: Headset (priority: 0, latency offset: 0 usec)
Part of profile(s): a2dp_sink, headset_head_unit
headset-input: Headset (priority: 0, latency offset: 0 usec, 
not available)
Part of profile(s): headset_head_unit

$ bluetoothctl

[NEW] Controller 00:1A:7D:DA:71:11 siemens-AMILO-Pi-1505 [default]
[NEW] Device AC:80:1C:01:34:B0 Fran Hdez's Airpods
[NEW] Device 4B:A3:18:BC:21:5B Sony Home Sound System
[NEW] Device 2B:20:C2:C6:E1:5D Bose QC25
[NEW] Device B1:81:AE:C5:1D:20 Home Living Room Pioneer Sound System
Agent registered
[Fran Hdez's Airpods]# info 

[Desktop-packages] [Bug 1904368] Re: eclipse ide has huge padding and inconsistencies

[Frederik Feichtmeier]

** Changed in: yaru-theme (Ubuntu)
   Status: New => Invalid

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

Title:
  eclipse ide has huge padding and inconsistencies

Status in yaru-theme package in Ubuntu:
  Invalid

Bug description:
  Eclipse 4.6.3 has compact widgets and layout using Ambiance theme in
  ubuntu 20.04.1 LTS. However, when using default Yaru theme, the look
  and feel has huge padding and layout. GTK 3.20+ has this issue. Ubuntu
  16.04 has proper themeing.

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

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

[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

[Rolando Gorgs]

At Fosdem 21 conference it was announced that next summer Thunderbird 91
will be released, which again will include fundamental changes. My
impression is that this time many months have been wasted because of
unclear procedures and responsibilities - not because of unsolvable
technical problems. (I hope we will see Thunderbird 78 before version 91
is out... - just kidding)

@osomon: Thank you Olivier for taking care of this issue.
Would you please write a short post mortem after the successful backport, where 
the difficulties have been, what steps to take and what responsible persons to 
contact to solve such a situation in future? This will definitely not be the 
last major Thunderbird update that needs to be back ported to LTS.

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

Title:
  Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Bionic:
  Triaged
Status in thunderbird source package in Focal:
  Fix Committed
Status in thunderbird source package in Groovy:
  Fix Released

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

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

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

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

[Desktop-packages] [Bug 580933] Re: arping should return when there is nothing left to do

[Bug Watch Updater]

** Changed in: iputils
   Status: Unknown => Fix Released

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

Title:
  arping should return when there is nothing left to do

Status in Iputils:
  Fix Released
Status in iputils package in Ubuntu:
  Fix Released

Bug description:
  When using arping with a count and every probe has been answered
  promptly, arping waits until the next probe would be sent before
  printing the stats and returning. That is an unnecessary delay.

  In the function recv_pack in arping.c, we have

  290   if (quit_on_reply)
  291   finish();

  where it could be

  290   if(quit_on_reply || count == 1 && received == sent)
  291   finish();

  ProblemType: Bug
  Architecture: i386
  Dependencies:
   libgcc1 1:4.3.3-5ubuntu4
   gcc-4.3-base 4.3.3-5ubuntu4
   findutils 4.4.0-2ubuntu4
   libc6 2.9-4ubuntu6.1
  DistroRelease: Ubuntu 9.04
  Package: iputils-arping 3:20071127-1
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: iputils
  Uname: Linux 2.6.30-020630rc5-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/iputils/+bug/580933/+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 580933] Re: arping should return when there is nothing left to do

[Hendrik Lönngren]

** Bug watch added: Debian Bug tracker #686944
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686944

** Also affects: iputils via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686944
   Importance: Unknown
   Status: Unknown

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

Title:
  arping should return when there is nothing left to do

Status in Iputils:
  Unknown
Status in iputils package in Ubuntu:
  Fix Released

Bug description:
  When using arping with a count and every probe has been answered
  promptly, arping waits until the next probe would be sent before
  printing the stats and returning. That is an unnecessary delay.

  In the function recv_pack in arping.c, we have

  290   if (quit_on_reply)
  291   finish();

  where it could be

  290   if(quit_on_reply || count == 1 && received == sent)
  291   finish();

  ProblemType: Bug
  Architecture: i386
  Dependencies:
   libgcc1 1:4.3.3-5ubuntu4
   gcc-4.3-base 4.3.3-5ubuntu4
   findutils 4.4.0-2ubuntu4
   libc6 2.9-4ubuntu6.1
  DistroRelease: Ubuntu 9.04
  Package: iputils-arping 3:20071127-1
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: iputils
  Uname: Linux 2.6.30-020630rc5-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/iputils/+bug/580933/+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 580933] Re: arping should return when there is nothing left to do

[Hendrik Lönngren]

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

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

Title:
  arping should return when there is nothing left to do

Status in Iputils:
  Unknown
Status in iputils package in Ubuntu:
  Fix Released

Bug description:
  When using arping with a count and every probe has been answered
  promptly, arping waits until the next probe would be sent before
  printing the stats and returning. That is an unnecessary delay.

  In the function recv_pack in arping.c, we have

  290   if (quit_on_reply)
  291   finish();

  where it could be

  290   if(quit_on_reply || count == 1 && received == sent)
  291   finish();

  ProblemType: Bug
  Architecture: i386
  Dependencies:
   libgcc1 1:4.3.3-5ubuntu4
   gcc-4.3-base 4.3.3-5ubuntu4
   findutils 4.4.0-2ubuntu4
   libc6 2.9-4ubuntu6.1
  DistroRelease: Ubuntu 9.04
  Package: iputils-arping 3:20071127-1
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: iputils
  Uname: Linux 2.6.30-020630rc5-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/iputils/+bug/580933/+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 1914930] [NEW] gjs loose gnome-shell parent and become zombie process

[Hassan El Jacifi]

Public bug reported:

Multiple zombie gjs process.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gjs 1.66.1-1
ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Sun Feb  7 14:07:37 2021
InstallationDate: Installed on 2018-01-01 (1132 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
SourcePackage: gjs
UpgradeStatus: Upgraded to groovy on 2019-10-19 (476 days ago)

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


** Tags: amd64 apport-bug groovy

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

Title:
  gjs loose gnome-shell parent and become zombie process

Status in gjs package in Ubuntu:
  New

Bug description:
  Multiple zombie gjs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gjs 1.66.1-1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Feb  7 14:07:37 2021
  InstallationDate: Installed on 2018-01-01 (1132 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
  SourcePackage: gjs
  UpgradeStatus: Upgraded to groovy on 2019-10-19 (476 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1914930/+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 195982] Re: Shift key (and caps lock) stop working when using VMWare

[Ronny Ager-Wick]

Wow, I did not expect this bug from 2008 to resurface in 2021!

To quote myself in 2008:
> As I'm using the free version of vmware, I can live with it until:
> 1. They fix it
> 2. VirtualBox becomes stable enough to use

#2 happened many *many* years ago, so I can no longer test this issue,
that was never really resolved beyond the sort-of-workaround with
setxkbmap in over 12 years...

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

Title:
  Shift key (and caps lock) stop working when using VMWare

Status in Linux:
  Invalid
Status in linux package in Ubuntu:
  Won't Fix
Status in xkeyboard-config package in Ubuntu:
  Invalid
Status in Gentoo Linux:
  New

Bug description:
  [Problem]
  VMWare's keyboard mapping is imperfect, sometimes resulting in certain keys 
stopping functionality when running under VMWare, requiring the user to setup 
their configuration settings manually in VMWare.  For a detailed explanation 
see the following article:

  http://www.vmware.com/support/ws55/doc/ws_devices_keymap_linux_longer.html

  [Original Report]
  After a day or so of running the shift key mysteriously stops working as does 
the cap lock. In other words I cannot enter shifted characters of any kind. The 
keyboard is connected to a KVM and all other systems respond to it properly. In 
additional any VMWare sessions I have open respond correctly. So I have the 
condition where all non-vmware applications in Ubuntu Hardy (all updates 
applied as of 2008-02-26 at 12:43 UTC) fail to recognize the shift key BUT 
applications within an active (a paused/restarted session also works) VMWare 
sessions running DO recognize the key.

  When this condition occurs ALL applications (except those within a
  VMWare session) are also unstable and will usually crash within a few
  keystrokes.If I continue to operate in this mode. I cannot pinpoint
  what, if any, application triggers this. It has always happened while
  working within terminal/browser/vmware sessions and NOT when opening a
  new application. It could be related to the KVM switch, but none of my
  other systems (2 Mandriva, 1 Windows) are affected by this.

  This bug has been present on my system for a number of days across
  daily updates and reboots (if the update requested it) and I think
  since I installed Hardy Alpha 1.

  A work around: log off and back on. A reboot/restart does not appear
  to be needed.

  Error logs show some unusual activity.

  --- MARK 
  ...
  ... kernel ... rtc lost 7 interrupts ...
  --- MARK ---
  

  Plus some segfaults indicating which application crashed as I tried to
  type into it (mouse works fine).

  System: HP dv9743cl (which otherwise works lovely)
  Ubuntu: Hardy 8.04 (from lsb-release)

  
  TEST CASE:
  1. Click inside the VM and
 
  2. Hold any of the Ctrl, Alt and/or shift keys while releasing the 
keyboard/mouse to the host OS (which you obviously do when you press Crtl-Alt 
to revert back to windowed mode, as the cursor is then released from the VM). 

  WORKAROUND:
  After this happens to recover your keyboard execute 'setxkbmap' in a terminal

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/195982/+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 1777708] Re: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time

[Svenskmand]

Hi :)

I also have the R-Go Tools Split keyboard and is having the exact same
issue no Ubuntu 20.04. I also had the same issue on Ubuntu 18.04.

But I found a way to fix it. If I change the display server from
X11/Xorg to Wayland then the problem goes away! :D I just followed this
guide:

  https://linuxconfig.org/how-to-enable-disable-wayland-on-
ubuntu-20-04-desktop?fbclid
=IwAR1yAApu1CItCAnngvHbZgCta1WzY718qk8dqdRXJdVkclm-_xWbOFDGmAw

So my suspection is that this is a problem with the default display
server in 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/108

Title:
  Desktop briefly becomes unresponsive when typing on 2 keyboards at the
  same time

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

Bug description:
  I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates
  from the repos.

  If I connect 2 (or more) keyboards to my computer and type on both at
  the same time, the desktop briefly becomes unresponsive. More
  keypresses increase the time of unresponsiveness.

  E.g. when typing a full sentence in gedit or the terminal, only very
  few characters show up on the screen (I guess up until something is
  pressed on both keyboards at the same time), then everything freezes.
  Then after a while (some seconds), all the characters show up. And the
  desktop becomes responsive again.

  Symptoms: During the freeze, windows stop updating their content. If
  seconds are enabled on the clock at the top middle, these freeze too.
  But I'm still able to move the mouse pointer around during the freeze
  without any problems.

  The back story:

  I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and
  quickly noticed the issue. But initiallly I thought it was an issue
  with the keyboard, and the problem wasn't that bad. But as I've gotten
  more used to the keyboard since yesterday and started picking up a
  proper typing speed, things got worse.

  The keyboard is technically two separate cabled USB keyboards each
  with only about half of they keys of a normal keyboard (or at least
  that's very much my impression).

  After getting the suspicion that this was a software issue, not a
  hardware issue, I tried typing on my old Logitech keyboard (Unifying
  Receiver) along with one of the R-Go halves: Same issue. Then I tried
  each of the halves without the other (as in "single" keyboard typing):
  No issue. Then I connected another Logitech keyboard (separate UR),
  typed on both Logitechs: Same issue.

  Some further observations:

  1) Nothing of significance in my syslog.
  2) If I drop to a non-graphical shell, there's no problem. I suspect this 
issue is related to X.org or Gnome, but I'm in no position to say anything 
credible about that.
  3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS 
machine.

  Let me know if there are any logs I can provide or things I can run to
  produce useful debug output.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/108/+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 1914918] [NEW] The snap being updated in the background causes both old and new tabs to die to SIGTRAP

[Avamander]

Public bug reported:

The last few background updates of chromium have made some old tabs
suddenly crash with SIGTRAP and it also makes it impossible to open new
tabs, those die instantly with a SIGTRAP as well.

This is incredibly destructive to whatever might be the dying tabs'
unsaved state and there's no warning about it. Yet again a snap-related
change rolled out to users with absolutely amateur-tier testing.

Ubuntu: 20.04.2
Snap: 2.48+20.04
Chromium: 88.0.4324.150

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

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

Title:
  The snap being updated in the background causes both old and new tabs
  to die to SIGTRAP

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  The last few background updates of chromium have made some old tabs
  suddenly crash with SIGTRAP and it also makes it impossible to open
  new tabs, those die instantly with a SIGTRAP as well.

  This is incredibly destructive to whatever might be the dying tabs'
  unsaved state and there's no warning about it. Yet again a snap-
  related change rolled out to users with absolutely amateur-tier
  testing.

  Ubuntu: 20.04.2
  Snap: 2.48+20.04
  Chromium: 88.0.4324.150

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1914918/+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 1892276] Re: thumbnails stretched on desktop 20.04 after previous bug fix release

[GilgongoJones]

Confirm htd95's fileItem.js fixes this for me on newly upgraded Ubuntu
20.04.2.

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

Title:
  thumbnails stretched on desktop 20.04 after previous bug fix release

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Triaged

Bug description:
  I updated all packages from the update branch and in the last week or two the 
pdfs on my desktop are displayed incorrectly and stretched out. It appears that 
I did not have the bug prior to the fix, but have it now that I have updated to 
the new package version.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2017-07-03 (1147 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell-extension-desktop-icons 20.04.0-3~ubuntu20.04.1
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-28 (118 days ago)
  UserGroups: adbusers adm cdrom dialout dip lpadmin plugdev sambashare sudo 
tty uucp video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1892276/+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 1895896] Re: HP Officejet Pro 6830 can not be connected via USB

[hornetster]

Similar issue with Brother MFC-J890DW.

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

Title:
  HP Officejet Pro 6830 can not be connected via USB

Status in hplip package in Ubuntu:
  New

Bug description:
  After updating to Ubuntu 20.04. I was unable to print via my HP
  Officejet Pro 6830 printer via WLAN and via USB.

  I managed to get the printer running via WLAN by going to CUPS (In
  Browser: http://localhost:631), deleting the stalled printer jobs and
  deleting the printers via cups.

  Afterwards I added the printer connected via WLAN using the command-line tool 
hp-setup. This was successfull. 
  However, when adding the same printer with hp-setup connected via USB, the 
connection failed with the error message "Unable to communicate with the 
device. Please check the device and try again.".
  The device is connected to my PC via WLAN and USB. There is no problem.

  I had expected that the usb printer driver for my hp Officejet Pro
  6830 got installed and afterwards successfull printing is possible.

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

  apt-cache policy hplip
  hplip:
Installiert:   3.20.3+dfsg0-2
Installationskandidat: 3.20.3+dfsg0-2
Versionstabelle:
   *** 3.20.3+dfsg0-2 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  apt-cache policy cups
  cups:
Installiert:   2.3.1-9ubuntu1.1
Installationskandidat: 2.3.1-9ubuntu1.1
Versionstabelle:
   *** 2.3.1-9ubuntu1.1 500
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://de.archive.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: hplip 3.20.3+dfsg0-2
  ProcVersionSignature: Ubuntu 5.4.0-47.51-lowlatency 5.4.55
  Uname: Linux 5.4.0-47-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CupsErrorLog:
   E [16/Sep/2020:22:07:23 +0200] [Job 18] File \'\' not found
   W [16/Sep/2020:23:04:33 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Officejet_Pro_6830_TH5666228Z0611_-Gray..\' already exists
   W [16/Sep/2020:23:04:33 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Officejet_Pro_6830_TH5666228Z0611_-DeviceN..\' already exists
   E [16/Sep/2020:23:06:31 +0200] [Job 19] Der Druckauftrag wurde nicht 
angenommen.
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 16 23:12:23 2020
  InstallationDate: Installed on 2019-10-23 (329 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat:
   device for HP_Officejet_Pro_6830_7F02D1_: 
implicitclass://HP_Officejet_Pro_6830_7F02D1_/
   device for Officejet_Pro_6830: 
hp:/usb/Officejet_Pro_6830?serial=TH5666228Z0611
   device for Officejet_Pro_6830_fax: 
hpfax:/usb/Officejet_Pro_6830?serial=TH5666228Z0611
   device for Officejet_Pro_6830_TH5666228Z0611_: 
implicitclass://Officejet_Pro_6830_TH5666228Z0611_/
  MachineType: LENOVO 2349FS4
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Officejet_Pro_6830_fax.ppd', 
'/etc/cups/ppd/Officejet_Pro_6830_TH5666228Z0611_.ppd', 
'/etc/cups/ppd/Officejet_Pro_6830.ppd', 
'/etc/cups/ppd/HP_Officejet_Pro_6830_7F02D1_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Officejet_Pro_6830_fax.ppd: Permission denied
   grep: /etc/cups/ppd/Officejet_Pro_6830_TH5666228Z0611_.ppd: Permission denied
   grep: /etc/cups/ppd/Officejet_Pro_6830.ppd: Permission denied
   grep: /etc/cups/ppd/HP_Officejet_Pro_6830_7F02D1_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-lowlatency 
root=UUID=4e553931-2567-4bbd-a4d0-a2566cce0c66 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to focal on 2020-04-26 (143 days ago)
  dmi.bios.date: 03/08/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET93WW (2.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2349FS4
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET93WW(2.53):bd03/08/2013:svnLENOVO:pn2349FS4:pvrThinkPadT430:rvnLENOVO:rn2349FS4:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2349FS4
  dmi.product.sku: LENOVO_MT_2349
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

-- 

[Desktop-packages] [Bug 1881473] Re: printer communication error

[hornetster]

Yes, similar issue.
2x fresh installs of 20.04.1.

Using a Brother MFC-J890DW, and trying to connect USB. Keep getting 'several 
printers' automatically created, but generally don't work, and appear not to be 
USB.
Scanning is also hit and miss.
Have tried using automatically created printers, and also installing the 
Brother drivers. Sometimes works, (via network mostly), but after a reboot, 
broken again. Uninstall/reinstall.
Used to 'just work'. Last OS was an older version of Mint.

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

Title:
  printer communication error

Status in hplip package in Ubuntu:
  New

Bug description:
  Since updated to 20.04, I cannot print through USB (HP DeskJet 5570,
  but apparently according to some google research I am not the only one
  affected, and not only with HP).

  Until yesterday the error message looked like hplip found the printer,
  but could not communicate to it. After reinstalling hplip und cups,
  now hplip cannot even find the printer (xsane the same).

  Printer is usable as network printer, but that's not an acceptable
  solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: hplip 3.20.3+dfsg0-2
  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
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun May 31 15:12:08 2020
  Lpstat:
   device for DeskJet_5570_series_TH5A71Q1GX0674_: 
implicitclass://DeskJet_5570_series_TH5A71Q1GX0674_/
   device for HP_DeskJet_5570_series: 
dnssd://HP%20DeskJet%205570%20series%20%5B1D38FD%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-dc4a3e1d38fd
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_5570_series_TH5A71Q1GX0674_.ppd', 
'/etc/cups/ppd/HP_DeskJet_5570_series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_5570_series_TH5A71Q1GX0674_.ppd: Permission denied
   HP_DeskJet_5570_series: HP Deskjet 5570 Series, hpcups 3.20.3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=7ec84d5a-3d57-4d46-91e2-b4ef200eb5e4 ro persistent quiet splash 
vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to focal on 2020-04-25 (36 days ago)
  dmi.bios.date: 03/10/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3003
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88X-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3003:bd03/10/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88X-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  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
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2016-02-26T22:19:15

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1881473/+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 1913651] Re: /usr/bin/ubuntu-drivers:PermissionError:/usr/bin/ubuntu-drivers@480:__call__:main:invoke:invoke:invoke:new_func:invoke:autoinstall:command_install

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-drivers-common - 1:0.8.6.5

---
ubuntu-drivers-common (1:0.8.6.5) hirsute; urgency=medium

  * tests/test_ubuntu_drivers.py:
- Add testcase for list-oem --package-list.
  * UbuntuDrivers/detect.py:
- Fix the way we validate the nvidia modules metapackages
  (LP: #1914374).

 -- Alberto Milone   Wed, 03 Feb 2021
19:13:21 +0100

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  /usr/bin/ubuntu-drivers:PermissionError:/usr/bin/ubuntu-
  
drivers@480:__call__:main:invoke:invoke:invoke:new_func:invoke:autoinstall:command_install

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Groovy:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding ubuntu-drivers-common.  This problem was most recently seen
  with package version 1:0.8.6.3~0.20.10.1, the problem page at
  https://errors.ubuntu.com/problem/a5320fbf71298787ff2595cc2b8227783b068dae
  contains more details, including versions of packages affected,
  stacktrace or traceback, and individual crash reports.

  There is also this bucket:
  https://errors.ubuntu.com/problem/fb18ad88544e0c025b2c9ec591b91c080d23401d

  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/ubuntu-drivers-common/+bug/1913651/+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 1914051] Re: `ubuntu-drivers list-oem --package-list` is broken

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-drivers-common - 1:0.8.6.5

---
ubuntu-drivers-common (1:0.8.6.5) hirsute; urgency=medium

  * tests/test_ubuntu_drivers.py:
- Add testcase for list-oem --package-list.
  * UbuntuDrivers/detect.py:
- Fix the way we validate the nvidia modules metapackages
  (LP: #1914374).

 -- Alberto Milone   Wed, 03 Feb 2021
19:13:21 +0100

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

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

Title:
  `ubuntu-drivers list-oem --package-list` is broken

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Released

Bug description:
  This is the call Ubiquity is making to decide what OEM packages to
  install.

  With the current focal-updates version

  root@ubuntu-drivers-common-test:~# apt policy ubuntu-drivers-common
  ubuntu-drivers-common:
Installed: 1:0.8.6.3~0.20.04.2
Candidate: 1:0.8.6.3~0.20.04.2
Version table:
   *** 1:0.8.6.3~0.20.04.2 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:0.8.1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  root@ubuntu-drivers-common-test:~# ubuntu-drivers list-oem 
--package-list=/tmp/foo
  Usage: ubuntu-drivers list-oem [OPTIONS] [LIST_OEM]...
  Try "ubuntu-drivers list-oem -h" for help.

  Error: no such option: --package-list

  With the focal release version:

  root@ubuntu-drivers-common-test:~# ubuntu-drivers list-oem 
--package-list=/tmp/foo
  root@ubuntu-drivers-common-test:~#

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1914051/+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 1914374] Re: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-drivers-common - 1:0.8.6.5

---
ubuntu-drivers-common (1:0.8.6.5) hirsute; urgency=medium

  * tests/test_ubuntu_drivers.py:
- Add testcase for list-oem --package-list.
  * UbuntuDrivers/detect.py:
- Fix the way we validate the nvidia modules metapackages
  (LP: #1914374).

 -- Alberto Milone   Wed, 03 Feb 2021
19:13:21 +0100

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image

Status in OEM Priority Project:
  Fix Released
Status in ubiquity package in Ubuntu:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubiquity source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Released
Status in ubiquity source package in Groovy:
  Triaged
Status in ubuntu-drivers-common source package in Groovy:
  New

Bug description:
  I've installed the focal-desktop-amd64.iso image with SHA-256 sum
  b928163990d9e148605c230c5d3e7bc563bb67269d551f741abc804553f3477c from
  http://cdimage.ubuntu.com/focal/daily-live/20210202.1/ on the HP ZBook
  15 G7 laptop (CID 202009-28216).

  There are multiple issues:

  * The graphical desktop isn't launched. The screen remains black except for a 
cursor blinking erratically in the top left corner of the screen. If I hammer 
Control+Alt+F[12345] for a while, the graphical desktop starts eventually.
  * The screen resolution is 3840x2160 but there is no scaling, so everything 
is tiny.
  * The touchpad does not work.
  * WLAN does not work.
  * Ethernet does not work. I tried two dongles (a USB A as well as a USB C 
dongle).
  * No sound.

  $ cat /proc/version_signature
  Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18

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

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

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

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

[Phan Thanh Long]

** Changed in: linux (Ubuntu)
 Assignee: Phan Thanh Long (phanlong2811) => (unassigned)

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

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

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

Bug description:
  Update (based on #296)
  =

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

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

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

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

  Original bug report
  ===

  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron: