date:20211109

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

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

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

Title:
  Gnome control center crashing when setting display positions

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

Bug description:
  From wake the order of the displays has changed and overlapping. The
  control center crashes when trying to move them back into the correct
  positions.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-control-center 1:3.38.5-1ubuntu1
  Uname: Linux 5.12.9-051209-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  6 18:38:43 2021
  InstallationDate: Installed on 2021-06-09 (27 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RebootRequiredPkgs: evolution-data-server
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1934836/+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 1942789] Re: On-demand and RTD3 need to be separated

2021-11-09 Thread jeremyszu

Hi Brian,

Let me think about your case, it's not a fresh installed system since
all nvidia drivers are backward compatible. Thus, user will get the
newer (e.g. 460 or 470) when installing the new stock ubuntu.

Since the Bug1942307, I will assume the user is staying at "nvidia" mode
if user didn't select the nvidia mode manually. (which means the
"/etc/prime-discrete" is "on" in the users you worry about)

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

Title:
  On-demand and RTD3 need to be separated

Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in nvidia-prime source package in Focal:
  Incomplete
Status in ubuntu-drivers-common source package in Focal:
  New
Status in nvidia-prime source package in Hirsute:
  New
Status in ubuntu-drivers-common source package in Hirsute:
  New

Bug description:
  RTD3 is a nvidia GPU feature to support runtime suspend.

  On-demand would be a X offloading feature.

  They are independent, according to discussion on
  https://github.com/tseliot/ubuntu-drivers-common/issues/55.

  Some parts need to be adjusted, e.g.

  ```
  # If we are dealing with NVIDIA PRIME, and runtimepm
  # is supported, enable it
  if (os.path.isfile('/run/nvidia_runtimepm_supported') and
  os.path.isfile('/usr/bin/prime-select')):
  print('Trying to select the on-demand PRIME profile')
  try:
  subprocess.call(['prime-select', 'on-demand'])
  except:
  pass

  # Create the override file for gpu-manager
  with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
  f.write('# File created by ubuntu-drivers\n')
  ```

  ---

  [Impact]

   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine

  [Test Plan]

   * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU 
driver. After the installation, reboot the system. Execute "prime-select query" 
should get "on-demand"
   * On non-laptop machine. Can set GPU mode to on-demand
   * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"

  [Where problems could occur]

   * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
   * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.

  [Other Info]

  X-HWE-Bug: Bug #1946434

  Changelogs:

  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium

    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)

    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
    RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
    is not available.
  - Don't check the current profile when setting
    a profile (LP: #1946476).
  - Catch BrokenPipeError.
  - Use bootvga detection when last_gfx_boot is
    not available.

  nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium

    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)

    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
    RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
    is not available.
  - Don't check the current profile when setting
    a profile (LP: #1946476).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942789/+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 1950393] Re: GDM session crashes on suspend on Ubuntu 21.10

Thanks for the bug report.

Your log shows evidence of bug 1949352 but that probably doesn't explain
"session crashes".

The most common GDM crash we are seeing in 21.10 is bug 1945061. But to
confirm exactly which crash you are experiencing here, please follow
these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

** Changed in: gdm3 (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/1950393

Title:
  GDM session crashes on suspend on Ubuntu 21.10

Status in gdm3 package in Ubuntu:
  Incomplete

Bug description:
  Since I started using kernel 5.13.0-20 (and 5.13.0-21) on Ubuntu
  21.10, my GDM session crashes when I try to put my laptop to standby.

  I've attached a relevant slice of the system journal that starts from
  the moment I pressed the power button, configured to trigger suspend,
  in my case.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 00:47:13 2021
  DistUpgraded: 2021-10-16 23:05:19,206 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 530 [17aa:380a]
 Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b]
  InstallationDate: Installed on 2020-03-17 (602 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 80RU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=0e855d19-79da-402d-9586-b7bfe9a9622a ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to impish on 2021-10-16 (24 days ago)
  dmi.bios.date: 08/09/2017
  dmi.bios.release: 1.61
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN61WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 700-15ISK
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN61WW:bd08/09/2017:br1.61:efr1.22:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:skuLENOVO_MT_80RU_BU_idea_FM_Lenovoideapad700-15ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80RU
  dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1950393/+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 1950355] Re: Intense screen flickering, vertical rainbow bars, display problems on Ubuntu 20.04, Lenovo X1 Carbon

At first this looks like a hardware fault to me. It looks like what
happens when I replace a laptop screen and it doesn't get a clean
electrical connection. The same can happen if it has received some bumps
and intermittently loses connections on some pins.

However there's a chance this is a kernel bug and your observation that
20.04.2 does not have a problem supports that theory...

Please:

1. Edit /etc/default/grub and change:

   GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

   to

   GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_psr=0"

2. Run:  sudo update-grub

3. Reboot.

Does that fix the problem?


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

** Changed in: linux-hwe-5.11 (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/1950355

Title:
  Intense screen flickering, vertical rainbow bars, display problems on
  Ubuntu 20.04, Lenovo X1 Carbon

Status in linux-hwe-5.11 package in Ubuntu:
  Incomplete

Bug description:
  (Initial post on ask ubuntu, copy pasted:
  https://askubuntu.com/questions/1359955/intense-screen-flickering-
  vertical-rainbow-bars-display-problems-on-ubuntu-20)

  Starting today (Aug 24) I observed intense screen flickering and
  tearing on my Ubuntu 20.04.3 on the Lenovo X1 Carbon. As far as I
  know, there were no shutdowns, updates, or changes. I observed this
  behavior once the machine started up from sleep. Throughout the day I
  have restarted (and powered down) the machine several times, but the
  problem persists.

  Here is a video example: https://photos.app.goo.gl/516nAe7AUUYnAHzd7

  Here is an image: https://i.stack.imgur.com/RgLvB.jpg

  This video was taken from a clean Ubuntu install USB, so I don't think
  it has to do with anything I've installed or updated in the past. The
  system does not have any other operating systems on it (its not dual
  booted).

  I'm using basic integrated graphics (Mesa Intel® UHD Graphics 620 (WHL
  GT2)). System has 16gb of RAM and a Intel® Core™ i7-8665U CPU @
  1.90GHz × 8 processor, so I don't think the issue is available
  processing power (although the integrated graphics could be bad).

  I'm already using Wayland.

  I tried everything in the following links: Ubuntu screen flickering
  https://www.reddit.com/r/Ubuntu/comments/g78o4e/screen_tearing_in_ubuntu_2004/

  The flickering is most noticeable in Chrome/Firefox (regardless of
  enabling/disabling hardware acceleration or setting any
  chrome://flags). However, I've also observed it with just editing Vim
  in terminal.

  EDIT: A month later, still experiencing this issue. This problem
  really seems to come and go -- it will go days without issue, and then
  have days again where it is constant. I've noticed it on all browsers.
  I've noticed that closing the webbrowser seems to resolve the issue
  most of the time. I've noticed that this is not an issue on any
  extended screens, just the main screen.

  ---

  Since the above post, I tried booting into a clean live disk running
  Ubuntu 20.04.2. This actually worked fine, and I did not observe any
  strange graphical effects. As per the reply on ask ubuntu, I decided
  to file this bug.

  ---

  Ubuntu release
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  9 13:16:35 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed
   virtualbox, 6.1.26, 5.11.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2021-03-15 (239 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20QDS3B800
  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.11.0-38-generic 
root=UUID=9213d3af-1e40-4621-9964-1212d1070372 ro quiet splash vt.handoff=7
  SourcePackage: xorg

[Desktop-packages] [Bug 1950328] Re: Idk

Please explain in more detail what kind of problem you are experiencing.

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

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

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

Title:
  Idk

Status in Ubuntu:
  Incomplete

Bug description:
  idk

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148
  Uname: Linux 5.4.0-90-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.82.00  Thu Oct 14 
10:24:40 UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Nov  9 15:16:26 2021
  DistUpgraded: 2021-11-09 13:33:35,359 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   8192cu, 1.11, 4.15.0-162-generic, x86_64: installed
   8192cu, 1.11, 5.4.0-90-generic, x86_64: installed
   nvidia, 470.82.00, 5.4.0-90-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:2560] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3a81]
  InstallationDate: Installed on 2021-10-15 (25 days ago)
  InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 
(20200806)
  MachineType: LENOVO 82JY
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-90-generic 
root=UUID=5064de25-8da0-4064-b74c-d45d2c8a30d4 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2021-11-09 (0 days ago)
  dmi.bios.date: 04/21/2021
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN36WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 5 17ACH6H
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN36WW:bd04/21/2021:svnLENOVO:pn82JY:pvrLegion517ACH6H:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegion517ACH6H:
  dmi.product.family: Legion 5 17ACH6H
  dmi.product.name: 82JY
  dmi.product.sku: LENOVO_MT_82JY_BU_idea_FM_Legion 5 17ACH6H
  dmi.product.version: Legion 5 17ACH6H
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Tue Nov  9 15:15:33 2021
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.11-1ubuntu1~20.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1950328/+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 1950316] Re: desktop UI unresponsive

Thanks for the bug report and for taking the time to make a video.

It appears the gnome-shell process is frozen (likely crashed). The mouse
cursor works still because it's managed by the Xorg process.

Next time the problem happens, please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

5. Also follow these instructions to check for recent crash reports:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Summary changed:

- desktop UI unresponsive
+ gnome-shell frozen but mouse still works

** 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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1950316

Title:
  gnome-shell frozen but mouse still works

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  mouse works
  keyboard doesn't

  video
  https://youtu.be/QWsrYBxu8hk

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  9 14:35:45 2021
  DistUpgraded: 2021-10-19 08:03:15,745 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: impish
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:84ca]
  InstallationDate: Installed on 2015-08-23 (2269 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=155c3c3c-daa6-414c-ac3d-0f8c492592c0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to impish on 2021-10-19 (21 days ago)
  dmi.bios.date: 07/21/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LX
  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.:bvr2501:bd07/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  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=1
  mtime.conffile..etc.default.apport: 2021-11-09T14:33:49.606944
  version.compiz: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1
  xserver.bootTime: Mon Aug 20 17:24:57 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1950316/+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 1813441] Re: Can no longer drag and drop files between desktop and applications

If you mean copy/paste (not drag and drop) then that is bug 1948008.

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

Title:
  Can no longer drag and drop files between desktop and applications

Status in gnome-shell-extension-desktop-icons:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Triaged
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Fix Released

Bug description:
  In releases before 19.04, you could drag and drop files from the
  desktop into applications.

  This no longer works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01-1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 26 21:47:14 2019
  InstallationDate: Installed on 2019-01-02 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+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 1948008] Re: Copying and pasting to/from Nautilus does not work

** Tags added: impish jammy

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

Title:
  Copying and pasting to/from Nautilus does not work

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Invalid
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  New
Status in gnome-shell source package in Focal:
  New
Status in gnome-shell-extension-desktop-icons source package in Focal:
  New
Status in gnome-shell-extension-desktop-icons-ng source package in Focal:
  Invalid
Status in gnome-shell source package in Hirsute:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Hirsute:
  Invalid
Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute:
  New
Status in gnome-shell source package in Impish:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Impish:
  Invalid
Status in gnome-shell-extension-desktop-icons-ng source package in Impish:
  New

Bug description:
  [Impact]

   * After upstream Nautilus has reverted the following commit [1]
  related to upstream bug [2] the desktop icons extension lost it's
  ability to copy to/from nautilus.

   * This is related to the fact that before there was some metadata
  passed along in the clipboard along with text data. This was causing
  issues with compatibility with some applications that were not
  expecting any metadata (MIME type in this case) was glued to the text
  clipboard contents. Hence, it was reverted upstream [3].

   * Fixing the root cause of this issue required changes to Nautilus
  [3], gnome-shell [4] and desktop-icons [5] [6]. Nautilus and gnome-
  shell parts are already implemented and present in Hirsute and Impish.

  
  [Test Plan]

   1) Make sure desktop-icons extension is enabled.
   2) Open nautilus window and copy any file from there by right-clicking and 
selecting "Copy" from the popup menu.
   3) Right-click on desktop and select "Paste" from the context menu.

  Expected result: selected file is copied to the desktop.
  Actual result: "Paste" item is disabled in the menu.

  [Where problems could occur]

   * Mixing a version of nautilus without commit [3] and fixed version
  of desktop-icons may still lead to a scenario when copying will not
  work.

   * Any extension/application copying to desktop using the smuggled-in-
  text clipboard behavior should be expected to stop working.

  [Other Info]

  [1] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/289
  [2] https://gitlab.gnome.org/GNOME/nautilus/-/issues/634
  [3] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/573
  [4] https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1321
  [5] 
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186
  [6] 
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948008/+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 1813441] Re: Can no longer drag and drop files between desktop and applications

This bug is already closed for 21.10 and I can confirm it definitely
works there. Please open a new bug if you have any problems with 21.10.

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

Title:
  Can no longer drag and drop files between desktop and applications

Status in gnome-shell-extension-desktop-icons:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Triaged
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Fix Released

Bug description:
  In releases before 19.04, you could drag and drop files from the
  desktop into applications.

  This no longer works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01-1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 26 21:47:14 2019
  InstallationDate: Installed on 2019-01-02 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+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 1923893] Re: After rescheduling an event, calendar alerts appear for the old time

** Package changed: gnome-shell (Ubuntu) => evolution-data-server
(Ubuntu)

** Also affects: evolution-data-server via
   https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/276
   Importance: Unknown
   Status: Unknown

** Changed in: evolution-data-server (Ubuntu)
   Status: New => Confirmed

** Changed in: evolution-data-server (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  After rescheduling an event, calendar alerts appear for the old time

Status in evolution-data-server:
  Unknown
Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  I use google calendar.  Events are created and updated via the
  browser. The calendar feed is configured through settings/online
  accounts. I can see upcoming events in the calendar drop down. The
  calendar and desktop are configured for the same timezone, and alerts
  normally appear simultaneously on my phone and desktop.

  I know sometimes stale calendar entries can be a factor, but I don't
  *think* that's an issue at this time (the change was made almost 24
  hours ago, I don't see the API limit errors I used to see in logs).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.2-1ubuntu1~20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 15:02:11 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-18 (666 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs:
   linux-image-5.8.0-49-generic
   linux-base
  RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (171 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1923893/+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 1947467] Re: GNOME 40 wayland-session exiting fullscreen doesn't restore original size & position

This will be fixed in gnome-shell 40.6 by:

commit aded2cd01b7af4d2bf355ed7cb129c6b869d84fb
Author: Florian Müllner 
Date:   Wed Nov 3 20:53:06 2021 +0100

Revert "layout: Exclude hidden actors from struts"

The change unvealed a series of mutter bugs that for most
users are worse than the issue that was fixed. So revert
the change on stable branches until the mutter side is
fixed.

This reverts commit cd1102ff30b134e45e9b5ab48318e6a4eae03416.



** Tags added: fixed-in-40.6 fixed-upstream

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

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

Title:
  GNOME 40 wayland-session exiting fullscreen doesn't restore original
  size & position

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

Bug description:
  Switching applications between normal and fullscreen got slower and also it 
won't remember position and size of the window on exiting fullscreen compared 
to gnome 3.x.
  I can also confirm this on a 20.04 installation with gnome 40 installed, that 
this is a degradation for gnome-shell 40 on wayland sessions. Xorg session is 
working fine.

  I've tested this with
  - firefox (F11 to enter/exit fullscreen)
  - YouTube videos
  - eog

  On going to fullscreen it often looses focus, and on exit the window
  just gets resized to the full monitor resolution.

  
  Rolling back my 20.04 machine to gnome 3.36 will make this work again under 
wayland.
  Considered that gnome 40 is the default for 21.10 and also wayland is the 
default, I hope this get's investigated and a fix is found before 20.04 is EOL.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 16 21:23:23 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-10-16 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1947467/+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 1938442] Re: Wrong permissions on ~/.hplip/.gnupg

2021-11-09 Thread Mathew Hodson

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

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

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

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

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

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

Title:
  Wrong permissions on ~/.hplip/.gnupg

Status in hplip package in Ubuntu:
  New
Status in hplip source package in Bionic:
  New
Status in hplip source package in Focal:
  New
Status in hplip source package in Hirsute:
  New
Status in hplip source package in Impish:
  New
Status in hplip source package in Jammy:
  New

Bug description:
  [Impact]
  * The directory ~/.hplip/.gnupg is readable by non-root users
  * This directory contains only public keys, but should still
have the permissions changed to 700 for privacy reasons

  [Test Case]
  * Install hplip and run `hp-plugin -i` 
  * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x
  * rm -rf ~/.hplip and install hplip from -proposed
  * run `hp-plugin -i` again
  * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx--

  [Regression Potential]
  * Because of file permissions becoming more restrictive,
it is possible that some other hplip binaries would
fail to read the .gnupg directory
  * To ensure this isn't the case, testing should be done
on different hplip use-cases to ensure they still
function properly

  [Original Description]
  Hi,

  we have a report in Fedora -
  https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey
  found out that ~/.hplip/.gnupg directory has permissions 755 instead
  of 700. Perms 700 prevent accessing the dir by other users, because
  the dir can contain private keys.

  However, .gnupg dir contains only a public key used in GPG
  verification of HP plugin, so the matter isn't that critical, but it
  is good to have it fixed.

  The patch is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+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 1943816] Re: "ubuntu-drivers install" needs to be used when installing nvidia-driver if enabling "third-party packages"

2021-11-09 Thread Mathew Hodson

** Also affects: ubiquity (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-drivers-common (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-drivers-common (Ubuntu Focal)
   Importance: Undecided => High

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

Title:
  "ubuntu-drivers install" needs to be used when installing nvidia-
  driver if enabling "third-party packages"

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

Bug description:
  ubiquity calls
  ```
  ubuntu-drivers install $FREEONLY $NOOEM --package-list 
/run/ubuntu-drivers.autoinstall
  ```
  to generate package list during live system but "ubuntu-drivers install" not 
only install packages but also create some config files for switching nvidia 
mode (e.g. on-demand) and change the runtime config as well (e.g. modify the 
iniramfs).

  Thus, not only package list needs to be referred but also the
  configuration.

  ---

  In ubuntu-drivers-common, which read the "/run/ubuntu-drivers.autoinstall" to 
install package. It also skipping the nvidia-mode changing (made by 
ubuntu-drivers install).
  ```
  $ cat ubiquity/target-config/31ubuntu_driver_packages
  #!/bin/sh
  set -e

  # install all packages that "ubuntu-drivers autoinstall" installed into the
  # live system. Ubiquity calls this with --package-list 
/run/ubuntu-drivers.autoinstall

  PKGLIST=/run/ubuntu-drivers.autoinstall
  [ -e $PKGLIST ] || exit 0

  for p in `cat $PKGLIST`; do
  apt-install $p
  done
  ```

  ---

  We need to use a same approach to make sure the nvidia mode is same on
  a same system (either all handing by ubuntu-drivers install or change
  the logic to maintainer script in each package).

  ---

  [Impact]

   * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on 
non-laptop machine
   * Patch make system not enable RTD3 unless it's a laptop
   * Install Ubuntu with "third-party packages" enabled, will not get same
 GPU configuration by running "ubuntu-drivers install"

  [Test Plan]

   * Install Ubuntu on machine with "third-party packages" enabled
   * On laptop with Nvidia RTD3 supported GPU. The configuration file 
'/run/nvidia_runtimepm_supported' will be created.
   * Execute "prime-select query" should get "on-demand"

  [Where problems could occur]

   * With non-laptop machine use RTD3 supported GPU may use more power

  [Other Info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1943816/+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 1949654] Re: Weird UI behavior when addprint off LAN using 21.10

I have done per requested.

What do you mean by "and share a link here"? Do you want me to visit
https://github.com/OpenPrinting/system-config-printer/issues , create
the same type of issue there and repaste the URL back here? Please
advise.

Also, FYI: doing this on 3x different 21.10 systems and all giving the
same never-ending-IP-output as displayed in the previously attached .png
(all systems on same LAN all pointing to same printer of course)

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

Title:
  Weird UI behavior when addprint off LAN using 21.10

Status in Ubuntu MATE:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  When using a fully patched 21.10 system and adding a LAN printer via
  it's IP, the response is very weird. See enclosed picture.

  PS: I believe this problem has been happening since AT LEAST 20.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-08-29 (437 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lpstat:
   device for _xeroxofficetq1_: ///dev/null
   device for C405: ///dev/null
   device for Xerox-CommonXCPT: socket://10.11.0.249:9100
  MachineType: System manufacturer System Product Name
  Package: system-config-printer 1.5.15-0ubuntu2
  PackageArchitecture: all
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox-CommonXCPT.ppd', '/etc/cups/ppd/C405.ppd', 
'/etc/cups/ppd/_xeroxofficetq1_.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Xerox-CommonXCPT.ppd: Permission denied
   grep: /etc/cups/ppd/C405.ppd: Permission denied
   grep: /etc/cups/ppd/_xeroxofficetq1_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1949654/+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 1949654] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1949654/+attachment/5539377/+files/ProcCpuinfo.txt

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

Title:
  Weird UI behavior when addprint off LAN using 21.10

Status in Ubuntu MATE:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  When using a fully patched 21.10 system and adding a LAN printer via
  it's IP, the response is very weird. See enclosed picture.

  PS: I believe this problem has been happening since AT LEAST 20.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-08-29 (437 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lpstat:
   device for _xeroxofficetq1_: ///dev/null
   device for C405: ///dev/null
   device for Xerox-CommonXCPT: socket://10.11.0.249:9100
  MachineType: System manufacturer System Product Name
  Package: system-config-printer 1.5.15-0ubuntu2
  PackageArchitecture: all
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox-CommonXCPT.ppd', '/etc/cups/ppd/C405.ppd', 
'/etc/cups/ppd/_xeroxofficetq1_.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Xerox-CommonXCPT.ppd: Permission denied
   grep: /etc/cups/ppd/C405.ppd: Permission denied
   grep: /etc/cups/ppd/_xeroxofficetq1_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1949654/+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 1949654] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1949654/+attachment/5539382/+files/UdevDb.txt

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

Title:
  Weird UI behavior when addprint off LAN using 21.10

Status in Ubuntu MATE:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  When using a fully patched 21.10 system and adding a LAN printer via
  it's IP, the response is very weird. See enclosed picture.

  PS: I believe this problem has been happening since AT LEAST 20.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-08-29 (437 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lpstat:
   device for _xeroxofficetq1_: ///dev/null
   device for C405: ///dev/null
   device for Xerox-CommonXCPT: socket://10.11.0.249:9100
  MachineType: System manufacturer System Product Name
  Package: system-config-printer 1.5.15-0ubuntu2
  PackageArchitecture: all
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox-CommonXCPT.ppd', '/etc/cups/ppd/C405.ppd', 
'/etc/cups/ppd/_xeroxofficetq1_.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Xerox-CommonXCPT.ppd: Permission denied
   grep: /etc/cups/ppd/C405.ppd: Permission denied
   grep: /etc/cups/ppd/_xeroxofficetq1_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1949654/+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 1949654] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1949654/+attachment/5539380/+files/ProcInterrupts.txt

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

Title:
  Weird UI behavior when addprint off LAN using 21.10

Status in Ubuntu MATE:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  When using a fully patched 21.10 system and adding a LAN printer via
  it's IP, the response is very weird. See enclosed picture.

  PS: I believe this problem has been happening since AT LEAST 20.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-08-29 (437 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lpstat:
   device for _xeroxofficetq1_: ///dev/null
   device for C405: ///dev/null
   device for Xerox-CommonXCPT: socket://10.11.0.249:9100
  MachineType: System manufacturer System Product Name
  Package: system-config-printer 1.5.15-0ubuntu2
  PackageArchitecture: all
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox-CommonXCPT.ppd', '/etc/cups/ppd/C405.ppd', 
'/etc/cups/ppd/_xeroxofficetq1_.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Xerox-CommonXCPT.ppd: Permission denied
   grep: /etc/cups/ppd/C405.ppd: Permission denied
   grep: /etc/cups/ppd/_xeroxofficetq1_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1949654/+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 1944216] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build

2021-11-09 Thread sdtrott

Is anyone ever going to come up with a fix for this? This has been going
on for a long time. The only way I can launch Linux now is by using the
5.8 kernel. Is it possible to remove the faulty 5.11 kernel so that I
can launch directly into 5.8?

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

Title:
  nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed
  to build

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

Bug description:
  Fails to boot upgrade Ubuntu 5.11.0-34, revert back to 5.8.0-63 on
  menu entry script in Grub and all works fine.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 340.108-0ubuntu5.20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.11.0-34-generic
  Date: Sun Sep 19 23:55:28 2021
  InstallationDate: Installed on 2021-02-28 (203 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageVersion: 340.108-0ubuntu5.20.04.2
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1944216/+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 1949654] acpidump.txt

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1949654/+attachment/5539383/+files/acpidump.txt

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

Title:
  Weird UI behavior when addprint off LAN using 21.10

Status in Ubuntu MATE:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  When using a fully patched 21.10 system and adding a LAN printer via
  it's IP, the response is very weird. See enclosed picture.

  PS: I believe this problem has been happening since AT LEAST 20.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-08-29 (437 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lpstat:
   device for _xeroxofficetq1_: ///dev/null
   device for C405: ///dev/null
   device for Xerox-CommonXCPT: socket://10.11.0.249:9100
  MachineType: System manufacturer System Product Name
  Package: system-config-printer 1.5.15-0ubuntu2
  PackageArchitecture: all
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox-CommonXCPT.ppd', '/etc/cups/ppd/C405.ppd', 
'/etc/cups/ppd/_xeroxofficetq1_.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Xerox-CommonXCPT.ppd: Permission denied
   grep: /etc/cups/ppd/C405.ppd: Permission denied
   grep: /etc/cups/ppd/_xeroxofficetq1_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1949654/+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 1949654] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1949654/+attachment/5539381/+files/ProcModules.txt

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

Title:
  Weird UI behavior when addprint off LAN using 21.10

Status in Ubuntu MATE:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  When using a fully patched 21.10 system and adding a LAN printer via
  it's IP, the response is very weird. See enclosed picture.

  PS: I believe this problem has been happening since AT LEAST 20.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-08-29 (437 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lpstat:
   device for _xeroxofficetq1_: ///dev/null
   device for C405: ///dev/null
   device for Xerox-CommonXCPT: socket://10.11.0.249:9100
  MachineType: System manufacturer System Product Name
  Package: system-config-printer 1.5.15-0ubuntu2
  PackageArchitecture: all
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox-CommonXCPT.ppd', '/etc/cups/ppd/C405.ppd', 
'/etc/cups/ppd/_xeroxofficetq1_.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Xerox-CommonXCPT.ppd: Permission denied
   grep: /etc/cups/ppd/C405.ppd: Permission denied
   grep: /etc/cups/ppd/_xeroxofficetq1_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1949654/+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 1949654] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1949654/+attachment/5539378/+files/ProcCpuinfoMinimal.txt

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

Title:
  Weird UI behavior when addprint off LAN using 21.10

Status in Ubuntu MATE:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  When using a fully patched 21.10 system and adding a LAN printer via
  it's IP, the response is very weird. See enclosed picture.

  PS: I believe this problem has been happening since AT LEAST 20.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-08-29 (437 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lpstat:
   device for _xeroxofficetq1_: ///dev/null
   device for C405: ///dev/null
   device for Xerox-CommonXCPT: socket://10.11.0.249:9100
  MachineType: System manufacturer System Product Name
  Package: system-config-printer 1.5.15-0ubuntu2
  PackageArchitecture: all
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox-CommonXCPT.ppd', '/etc/cups/ppd/C405.ppd', 
'/etc/cups/ppd/_xeroxofficetq1_.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Xerox-CommonXCPT.ppd: Permission denied
   grep: /etc/cups/ppd/C405.ppd: Permission denied
   grep: /etc/cups/ppd/_xeroxofficetq1_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1949654/+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 1949654] Lsusb-v.txt

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1949654/+attachment/5539375/+files/Lsusb-v.txt

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

Title:
  Weird UI behavior when addprint off LAN using 21.10

Status in Ubuntu MATE:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  When using a fully patched 21.10 system and adding a LAN printer via
  it's IP, the response is very weird. See enclosed picture.

  PS: I believe this problem has been happening since AT LEAST 20.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-08-29 (437 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lpstat:
   device for _xeroxofficetq1_: ///dev/null
   device for C405: ///dev/null
   device for Xerox-CommonXCPT: socket://10.11.0.249:9100
  MachineType: System manufacturer System Product Name
  Package: system-config-printer 1.5.15-0ubuntu2
  PackageArchitecture: all
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox-CommonXCPT.ppd', '/etc/cups/ppd/C405.ppd', 
'/etc/cups/ppd/_xeroxofficetq1_.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Xerox-CommonXCPT.ppd: Permission denied
   grep: /etc/cups/ppd/C405.ppd: Permission denied
   grep: /etc/cups/ppd/_xeroxofficetq1_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1949654/+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 1949654] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1949654/+attachment/5539379/+files/ProcEnviron.txt

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

Title:
  Weird UI behavior when addprint off LAN using 21.10

Status in Ubuntu MATE:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  When using a fully patched 21.10 system and adding a LAN printer via
  it's IP, the response is very weird. See enclosed picture.

  PS: I believe this problem has been happening since AT LEAST 20.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-08-29 (437 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lpstat:
   device for _xeroxofficetq1_: ///dev/null
   device for C405: ///dev/null
   device for Xerox-CommonXCPT: socket://10.11.0.249:9100
  MachineType: System manufacturer System Product Name
  Package: system-config-printer 1.5.15-0ubuntu2
  PackageArchitecture: all
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox-CommonXCPT.ppd', '/etc/cups/ppd/C405.ppd', 
'/etc/cups/ppd/_xeroxofficetq1_.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Xerox-CommonXCPT.ppd: Permission denied
   grep: /etc/cups/ppd/C405.ppd: Permission denied
   grep: /etc/cups/ppd/_xeroxofficetq1_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1949654/+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 1949654] PrintingPackages.txt

apport information

** Attachment added: "PrintingPackages.txt"
   
https://bugs.launchpad.net/bugs/1949654/+attachment/5539376/+files/PrintingPackages.txt

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

Title:
  Weird UI behavior when addprint off LAN using 21.10

Status in Ubuntu MATE:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  When using a fully patched 21.10 system and adding a LAN printer via
  it's IP, the response is very weird. See enclosed picture.

  PS: I believe this problem has been happening since AT LEAST 20.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-08-29 (437 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lpstat:
   device for _xeroxofficetq1_: ///dev/null
   device for C405: ///dev/null
   device for Xerox-CommonXCPT: socket://10.11.0.249:9100
  MachineType: System manufacturer System Product Name
  Package: system-config-printer 1.5.15-0ubuntu2
  PackageArchitecture: all
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox-CommonXCPT.ppd', '/etc/cups/ppd/C405.ppd', 
'/etc/cups/ppd/_xeroxofficetq1_.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Xerox-CommonXCPT.ppd: Permission denied
   grep: /etc/cups/ppd/C405.ppd: Permission denied
   grep: /etc/cups/ppd/_xeroxofficetq1_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1949654/+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 1949654] Lsusb-t.txt

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1949654/+attachment/5539374/+files/Lsusb-t.txt

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

Title:
  Weird UI behavior when addprint off LAN using 21.10

Status in Ubuntu MATE:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  When using a fully patched 21.10 system and adding a LAN printer via
  it's IP, the response is very weird. See enclosed picture.

  PS: I believe this problem has been happening since AT LEAST 20.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-08-29 (437 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lpstat:
   device for _xeroxofficetq1_: ///dev/null
   device for C405: ///dev/null
   device for Xerox-CommonXCPT: socket://10.11.0.249:9100
  MachineType: System manufacturer System Product Name
  Package: system-config-printer 1.5.15-0ubuntu2
  PackageArchitecture: all
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox-CommonXCPT.ppd', '/etc/cups/ppd/C405.ppd', 
'/etc/cups/ppd/_xeroxofficetq1_.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Xerox-CommonXCPT.ppd: Permission denied
   grep: /etc/cups/ppd/C405.ppd: Permission denied
   grep: /etc/cups/ppd/_xeroxofficetq1_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1949654/+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 1949654] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1949654/+attachment/5539373/+files/Lsusb.txt

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

Title:
  Weird UI behavior when addprint off LAN using 21.10

Status in Ubuntu MATE:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  When using a fully patched 21.10 system and adding a LAN printer via
  it's IP, the response is very weird. See enclosed picture.

  PS: I believe this problem has been happening since AT LEAST 20.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-08-29 (437 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lpstat:
   device for _xeroxofficetq1_: ///dev/null
   device for C405: ///dev/null
   device for Xerox-CommonXCPT: socket://10.11.0.249:9100
  MachineType: System manufacturer System Product Name
  Package: system-config-printer 1.5.15-0ubuntu2
  PackageArchitecture: all
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox-CommonXCPT.ppd', '/etc/cups/ppd/C405.ppd', 
'/etc/cups/ppd/_xeroxofficetq1_.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Xerox-CommonXCPT.ppd: Permission denied
   grep: /etc/cups/ppd/C405.ppd: Permission denied
   grep: /etc/cups/ppd/_xeroxofficetq1_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1949654/+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 1949654] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1949654/+attachment/5539371/+files/Lspci.txt

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

Title:
  Weird UI behavior when addprint off LAN using 21.10

Status in Ubuntu MATE:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  When using a fully patched 21.10 system and adding a LAN printer via
  it's IP, the response is very weird. See enclosed picture.

  PS: I believe this problem has been happening since AT LEAST 20.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-08-29 (437 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lpstat:
   device for _xeroxofficetq1_: ///dev/null
   device for C405: ///dev/null
   device for Xerox-CommonXCPT: socket://10.11.0.249:9100
  MachineType: System manufacturer System Product Name
  Package: system-config-printer 1.5.15-0ubuntu2
  PackageArchitecture: all
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox-CommonXCPT.ppd', '/etc/cups/ppd/C405.ppd', 
'/etc/cups/ppd/_xeroxofficetq1_.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Xerox-CommonXCPT.ppd: Permission denied
   grep: /etc/cups/ppd/C405.ppd: Permission denied
   grep: /etc/cups/ppd/_xeroxofficetq1_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1949654/+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 1949654] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1949654/+attachment/5539368/+files/CurrentDmesg.txt

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

Title:
  Weird UI behavior when addprint off LAN using 21.10

Status in Ubuntu MATE:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  When using a fully patched 21.10 system and adding a LAN printer via
  it's IP, the response is very weird. See enclosed picture.

  PS: I believe this problem has been happening since AT LEAST 20.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-08-29 (437 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lpstat:
   device for _xeroxofficetq1_: ///dev/null
   device for C405: ///dev/null
   device for Xerox-CommonXCPT: socket://10.11.0.249:9100
  MachineType: System manufacturer System Product Name
  Package: system-config-printer 1.5.15-0ubuntu2
  PackageArchitecture: all
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox-CommonXCPT.ppd', '/etc/cups/ppd/C405.ppd', 
'/etc/cups/ppd/_xeroxofficetq1_.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Xerox-CommonXCPT.ppd: Permission denied
   grep: /etc/cups/ppd/C405.ppd: Permission denied
   grep: /etc/cups/ppd/_xeroxofficetq1_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1949654/+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 1949654] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1949654/+attachment/5539369/+files/Dependencies.txt

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

Title:
  Weird UI behavior when addprint off LAN using 21.10

Status in Ubuntu MATE:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  When using a fully patched 21.10 system and adding a LAN printer via
  it's IP, the response is very weird. See enclosed picture.

  PS: I believe this problem has been happening since AT LEAST 20.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-08-29 (437 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lpstat:
   device for _xeroxofficetq1_: ///dev/null
   device for C405: ///dev/null
   device for Xerox-CommonXCPT: socket://10.11.0.249:9100
  MachineType: System manufacturer System Product Name
  Package: system-config-printer 1.5.15-0ubuntu2
  PackageArchitecture: all
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox-CommonXCPT.ppd', '/etc/cups/ppd/C405.ppd', 
'/etc/cups/ppd/_xeroxofficetq1_.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Xerox-CommonXCPT.ppd: Permission denied
   grep: /etc/cups/ppd/C405.ppd: Permission denied
   grep: /etc/cups/ppd/_xeroxofficetq1_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1949654/+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 1949654] Lspci-vt.txt

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1949654/+attachment/5539372/+files/Lspci-vt.txt

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

Title:
  Weird UI behavior when addprint off LAN using 21.10

Status in Ubuntu MATE:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  When using a fully patched 21.10 system and adding a LAN printer via
  it's IP, the response is very weird. See enclosed picture.

  PS: I believe this problem has been happening since AT LEAST 20.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-08-29 (437 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lpstat:
   device for _xeroxofficetq1_: ///dev/null
   device for C405: ///dev/null
   device for Xerox-CommonXCPT: socket://10.11.0.249:9100
  MachineType: System manufacturer System Product Name
  Package: system-config-printer 1.5.15-0ubuntu2
  PackageArchitecture: all
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox-CommonXCPT.ppd', '/etc/cups/ppd/C405.ppd', 
'/etc/cups/ppd/_xeroxofficetq1_.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Xerox-CommonXCPT.ppd: Permission denied
   grep: /etc/cups/ppd/C405.ppd: Permission denied
   grep: /etc/cups/ppd/_xeroxofficetq1_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1949654/+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 1949654] Locale.txt

apport information

** Attachment added: "Locale.txt"
   https://bugs.launchpad.net/bugs/1949654/+attachment/5539370/+files/Locale.txt

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

Title:
  Weird UI behavior when addprint off LAN using 21.10

Status in Ubuntu MATE:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  When using a fully patched 21.10 system and adding a LAN printer via
  it's IP, the response is very weird. See enclosed picture.

  PS: I believe this problem has been happening since AT LEAST 20.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-08-29 (437 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lpstat:
   device for _xeroxofficetq1_: ///dev/null
   device for C405: ///dev/null
   device for Xerox-CommonXCPT: socket://10.11.0.249:9100
  MachineType: System manufacturer System Product Name
  Package: system-config-printer 1.5.15-0ubuntu2
  PackageArchitecture: all
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox-CommonXCPT.ppd', '/etc/cups/ppd/C405.ppd', 
'/etc/cups/ppd/_xeroxofficetq1_.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Xerox-CommonXCPT.ppd: Permission denied
   grep: /etc/cups/ppd/C405.ppd: Permission denied
   grep: /etc/cups/ppd/_xeroxofficetq1_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1949654/+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 1949654] Re: Weird UI behavior when addprint off LAN using 21.10

apport information

** Tags added: apport-collected

** Description changed:

  When using a fully patched 21.10 system and adding a LAN printer via
  it's IP, the response is very weird. See enclosed picture.
  
  PS: I believe this problem has been happening since AT LEAST 20.04.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu71
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 21.10
+ InstallationDate: Installed on 2020-08-29 (437 days ago)
+ InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
+ Lpstat:
+  device for _xeroxofficetq1_: ///dev/null
+  device for C405: ///dev/null
+  device for Xerox-CommonXCPT: socket://10.11.0.249:9100
+ MachineType: System manufacturer System Product Name
+ Package: system-config-printer 1.5.15-0ubuntu2
+ PackageArchitecture: all
+ Papersize: letter
+ PpdFiles:
+  Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox-CommonXCPT.ppd', '/etc/cups/ppd/C405.ppd', 
'/etc/cups/ppd/_xeroxofficetq1_.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Xerox-CommonXCPT.ppd: Permission denied
+  grep: /etc/cups/ppd/C405.ppd: Permission denied
+  grep: /etc/cups/ppd/_xeroxofficetq1_.ppd: Permission denied
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
+ RebootRequiredPkgs: Error: path contained symlinks.
+ Tags:  impish
+ Uname: Linux 5.13.0-20-generic x86_64
+ UpgradeStatus: Upgraded to impish on 2021-10-14 (26 days ago)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/02/2020
+ dmi.bios.release: 5.17
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 5809
+ dmi.board.asset.tag: Default string
+ dmi.board.name: TUF X470-PLUS GAMING
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: Rev X.0x
+ dmi.chassis.asset.tag: Default string
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Default string
+ dmi.chassis.version: Default string
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: System Product Name
+ dmi.product.sku: SKU
+ dmi.product.version: System Version
+ dmi.sys.vendor: System manufacturer

** Attachment added: "CupsErrorLog.txt"
   
https://bugs.launchpad.net/bugs/1949654/+attachment/5539367/+files/CupsErrorLog.txt

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

Title:
  Weird UI behavior when addprint off LAN using 21.10

Status in Ubuntu MATE:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  When using a fully patched 21.10 system and adding a LAN printer via
  it's IP, the response is very weird. See enclosed picture.

  PS: I believe this problem has been happening since AT LEAST 20.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-08-29 (437 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lpstat:
   device for _xeroxofficetq1_: ///dev/null
   device for C405: ///dev/null
   device for Xerox-CommonXCPT: socket://10.11.0.249:9100
  MachineType: System manufacturer System Product Name
  Package: system-config-printer 1.5.15-0ubuntu2
  PackageArchitecture: all
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox-CommonXCPT.ppd', '/etc/cups/ppd/C405.ppd', 
'/etc/cups/ppd/_xeroxofficetq1_.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Xerox-CommonXCPT.ppd: Permission denied
   grep: /etc/cups/ppd/C405.ppd: Permission denied
   grep: /etc/cups/ppd/_xeroxofficetq1_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (26 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF X470-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string

[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.

2021-11-09 Thread Mathew Hodson

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

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

Title:
  Xwayland crash in gdm as screen off and touchscreen detach.

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  Fix Committed
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Hirsute:
  Fix Committed
Status in mutter source package in Impish:
  Fix Committed

Bug description:
  [Impact]

   * Gdm crashed and user need to be an expert to know how to work around,
     or need to reboot to fix.

   * OEM projects got certain SKU that can reliably reproduce this
  issue.

   * A merged patch in upstream fix the race condition.

  [Test Plan]

   * Use the SKU that can reliably reproduce this issue.
   * Do a cold boot, and wait for 5 mins. The monitor should turned-black
     but showing the Machine Vendor logo that was previously
     displayed by plymouth.
   * Try to dog-food the deb from the proposed channel and make sure
     all input events still properly propagate.

  [Where problems could occur]

   * If the patch is not properly working as expected, per the file this
     patch touch, the user desktop session could stop responding to
     mouse, keyboard, and touch screen input.

  [Other Info]

   * Can't think of any for now.

  

  This is a reproducible issue. Step to reproduce
  1. cold boot into gdm login screen.
  2. wait for 5 mins, and the screen will be turned off. (also observed that 
the touchscreen USB device drop of a USB bus on the target machine)

  Note: this bug seems to be timing sensitive. I got an OEM project
  machine that can reproduce this issue (reproducible on several
  machines with the same HW design). The machine is using ADL CPU, which
  needs a patched 5.14 kernel. So I can't reproduce this on impish. With
  the backported mutter, I verified an upstream patch seems to fix this
  issue.

  Expected result:
  The screen just turns black.

  Actual result:
  Saw Vendor boot logo on the monitor (previous draw by plymouth during booting)

  Analysis as it happens:
  1. Saw "LGDisplay Incell Touch" drop off the USB bus.
     Kernel message like: "usb 1-9: USB disconnect, device number 6"
     as the screen turned black.
  2. There is no switch on virtual tty.
  3. journal log from Xwayland "wl_display@1: error 0: invalid object 24"
  4. Xwayland and gnome-shell process both die as this happens.
  5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and
     gnome-shell stop there for 30 more seconds.
  6. backtrace as Xwayland crashed:

  ```
  #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6
  #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6
  #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351
  #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872
  #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at 
../../../../os/log.c:1010
  #5 0x56437429c8b0 in xwl_log_handler (format=, 
args=) at ../../../../../hw/xwayland/xwayland.c:1312
  #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error 
%d: %s\n") at ../src/wayland-util.c:404
  #7 0x7f447c3cb78b in display_handle_error (data=, 
display=0x56437639f000, object=0x56437639f000, code=0, message=)
  at ../src/wayland-client.c:911
  #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7
  #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7
  #10 0x7f447c3cf3a8 in wl_closure_invoke 
(closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=,
  target@entry=0x56437639f000, opcode=opcode@entry=0, data=) 
at ../src/connection.c:1018
  #11 0x7f447c3cbc48 in dispatch_event 
(display=display@entry=0x56437639f000, queue=) at 
../src/wayland-client.c:1445
  #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, 
display=0x56437639f000) at ../src/wayland-client.c:1584
  #13 wl_display_dispatch_queue_pending (display=0x56437639f000, 
queue=0x56437639f0d0) at ../src/wayland-client.c:1833
  #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896
  #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at 
../../../../../hw/xwayland/xwayland.c:957
  #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, 
timeout=) at ../../../../os/ospoll.c:657
  #17 0x5643743faa23 in WaitForSomething (are_ready=0) at 
../../../../os/WaitFor.c:208
  #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220
  #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, 
envp=) at ../../../../dix/main.c:276
  #20 0x7f447b8c90b3 in __libc_start_main () from 
/lib/x86_64-linux-gnu/libc.so.6
  #21 0x56437429c60e in _start

[Desktop-packages] [Bug 1950393] Re: GDM session crashes on suspend on Ubuntu 21.10

2021-11-09 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  GDM session crashes on suspend on Ubuntu 21.10

Status in xorg package in Ubuntu:
  New

Bug description:
  Since I started using kernel 5.13.0-20 (and 5.13.0-21) on Ubuntu
  21.10, my GDM session crashes when I try to put my laptop to standby.

  I've attached a relevant slice of the system journal that starts from
  the moment I pressed the power button, configured to trigger suspend,
  in my case.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 00:47:13 2021
  DistUpgraded: 2021-10-16 23:05:19,206 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 530 [17aa:380a]
 Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b]
  InstallationDate: Installed on 2020-03-17 (602 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 80RU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=0e855d19-79da-402d-9586-b7bfe9a9622a ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to impish on 2021-10-16 (24 days ago)
  dmi.bios.date: 08/09/2017
  dmi.bios.release: 1.61
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN61WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 700-15ISK
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN61WW:bd08/09/2017:br1.61:efr1.22:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:skuLENOVO_MT_80RU_BU_idea_FM_Lenovoideapad700-15ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80RU
  dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1950393/+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 1950393] [NEW] GDM session crashes on suspend on Ubuntu 21.10

You have been subscribed to a public bug:

Since I started using kernel 5.13.0-20 (and 5.13.0-21) on Ubuntu 21.10,
my GDM session crashes when I try to put my laptop to standby.

I've attached a relevant slice of the system journal that starts from
the moment I pressed the power button, configured to trigger suspend, in
my case.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 10 00:47:13 2021
DistUpgraded: 2021-10-16 23:05:19,206 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: impish
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 530 [17aa:380a]
   Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b]
InstallationDate: Installed on 2020-03-17 (602 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 80RU
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=0e855d19-79da-402d-9586-b7bfe9a9622a ro
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to impish on 2021-10-16 (24 days ago)
dmi.bios.date: 08/09/2017
dmi.bios.release: 1.61
dmi.bios.vendor: LENOVO
dmi.bios.version: E5CN61WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo ideapad 700-15ISK
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 700-15ISK
dmi.ec.firmware.release: 1.22
dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN61WW:bd08/09/2017:br1.61:efr1.22:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:skuLENOVO_MT_80RU_BU_idea_FM_Lenovoideapad700-15ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80RU
dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK
dmi.product.version: Lenovo ideapad 700-15ISK
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1

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


** Tags: amd64 apport-bug crash impish ubuntu
-- 
GDM session crashes on suspend on Ubuntu 21.10
https://bugs.launchpad.net/bugs/1950393
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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

[Desktop-packages] [Bug 1950396] [NEW] package thunderbird-locale-en 1:78.13.0+build1-0ubuntu0.20.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it

2021-11-09 Thread Pukar Bhandari

Public bug reported:

dpkg: error processing package thunderbird-locale-en (--configure):
 package is in a very bad inconsistent state; you should
 reinstall it before attempting configuration

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: thunderbird-locale-en 1:78.13.0+build1-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-40-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.21
AptOrdering:
 thunderbird:amd64: Install
 thunderbird-gnome-support:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  arpuuk 1567 F pulseaudio
 /dev/snd/controlC0:  arpuuk 1567 F pulseaudio
BuildID: 20210802223056
CasperMD5CheckResult: skip
Channel: Unavailable
Date: Tue Nov  9 16:15:23 2021
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
ForcedLayersAccel: False
InstallationDate: Installed on 2021-11-09 (0 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
IpRoute:
 default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp2s0 scope link metric 1000 
 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.25 metric 600
NoProfiles: True
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Title: package thunderbird-locale-en 1:78.13.0+build1-0ubuntu0.20.04.2 failed 
to install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/26/2020
dmi.bios.release: 1.31
dmi.bios.vendor: LENOVO
dmi.bios.version: R0WET63W (1.31 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20MVS0HX00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.31
dmi.modalias: 
dmi:bvnLENOVO:bvrR0WET63W(1.31):bd03/26/2020:br1.31:efr1.31:svnLENOVO:pn20MVS0HX00:pvrThinkPadA485:skuLENOVO_MT_20MV_BU_Think_FM_ThinkPadA485:rvnLENOVO:rn20MVS0HX00:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad A485
dmi.product.name: 20MVS0HX00
dmi.product.sku: LENOVO_MT_20MV_BU_Think_FM_ThinkPad A485
dmi.product.version: ThinkPad A485
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package focal

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

Title:
  package thunderbird-locale-en 1:78.13.0+build1-0ubuntu0.20.04.2 failed
  to install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in thunderbird package in Ubuntu:
  New

Bug description:
  dpkg: error processing package thunderbird-locale-en (--configure):
   package is in a very bad inconsistent state; you should
   reinstall it before attempting configuration

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: thunderbird-locale-en 1:78.13.0+build1-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-40-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.21
  AptOrdering:
   thunderbird:amd64: Install
   thunderbird-gnome-support:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  arpuuk 1567 F pulseaudio
   /dev/snd/controlC0:  arpuuk 1567 F pulseaudio
  BuildID: 20210802223056
  CasperMD5CheckResult: skip
  Channel: Unavailable
  Date: Tue Nov  9 16:15:23 2021
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-11-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.25 metric 600
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:

[Desktop-packages] [Bug 1813441] Re: Can no longer drag and drop files between desktop and applications

2021-11-09 Thread Tom

I confirm the bug is still present (and very annoying, making me lose a
lot of time) on Ubuntu 21.10.

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

Title:
  Can no longer drag and drop files between desktop and applications

Status in gnome-shell-extension-desktop-icons:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Triaged
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Fix Released

Bug description:
  In releases before 19.04, you could drag and drop files from the
  desktop into applications.

  This no longer works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01-1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 26 21:47:14 2019
  InstallationDate: Installed on 2019-01-02 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+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 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition

2021-11-09 Thread frigo

if the goal is to have a single snap making use of the kerberos ticket,
as a workaround you can put something like this in /etc/krb5.conf


[libdefaults]
default_ccache_name = 
DIR:/home/%{username}/snap/firefox/common/.cache/.k5_ccache


the default connections for the firefox snap prevent it to read hidden files 
under $HOME, so we help it a little. Seems to work so far

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

Title:
  [snap] kerberos GSSAPI no longer works after deb->snap transition

Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  I configure AuthServerWhitelist as documented:

  https://www.chromium.org/developers/design-documents/http-
  authentication

  and can see my whitelisted domains in chrome://policy/

  but websites that used to work with SPNEGO/GSSAPI/kerberos no longer
  work. I'm guessing the snap needs some sort of permission to use the
  kerberos ticket cache (or the plumbing to do so doesn't exist...).

  I can confirm that Chrome has the desired behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1849346/+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 1913570] Re: Firefox not opening file chooser dialog for importing certificates

François, this is a different (although related) issue: this bug report
was about firefox not even opening a file selection dialog to pick a
certificate file, which was resolved after installing xdg-desktop-
portal. The problem you're describing is that after selecting the
certificate file, firefox fails to actually import it. I can observe the
same problem, so that's definitely a bug. Would you mind filing an
upstream bug at
https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes|Firefox to track the
problem, making sure to include "snap" in the bug title, and marking it
as blocking https://bugzilla.mozilla.org/show_bug.cgi?id=1665641 ?

Thanks in advance!

** Bug watch added: Mozilla Bugzilla #1665641
   https://bugzilla.mozilla.org/show_bug.cgi?id=1665641

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

Title:
  Firefox not opening file chooser dialog for importing certificates

Status in firefox package in Ubuntu:
  Expired

Bug description:
  When installed as a snap, firefox won't open the file chooser dialog
  for importing a certificate authority. However, it is working when
  installed using apt.

  How to reproduce:
  1. Install firefox as snap
  2. Navigate to Preferences | Privacy & Security | Certificates | View 
Certificates
  3. Select Authorities
  4. Click Import ...
 -> A file selector dialog should open to import a certificate, but nothing 
happens.

  Environment:
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Thu Jan 28 11:43:55 2021
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-01-15 (12 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 
(20210115)
  ProcCpuinfoMinimal:
   processor: 3
   vendor_id: GenuineIntel
   cpu family   : 6
   model: 42
   model name   : Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
   stepping : 7
   microcode: 0x2f
   cpu MHz  : 3701.000
   cache size   : 8192 KB
   physical id  : 6
   siblings : 1
   core id  : 0
   cpu cores: 1
   apicid   : 6
   initial apicid   : 6
   fpu  : yes
   fpu_exception: yes
   cpuid level  : 13
   wp   : yes
   flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc 
arch_perfmon nopl xtopology tsc_reliable nonstop_tsc cpuid pni pclmulqdq ssse3 
cx16 pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx 
hypervisor lahf_lm pti ssbd ibrs ibpb stibp tsc_adjust arat md_clear flush_l1d 
arch_capabilities
   bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs itlb_multihit
   bogomips : 7402.00
   clflush size : 64
   cache_alignment  : 64
   address sizes: 43 bits physical, 48 bits virtual
   power management:
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=en_US
   LC_ADDRESS=de_DE.UTF-8
   LC_NAME=de_DE.UTF-8
   LC_MONETARY=de_DE.UTF-8
   LC_PAPER=de_DE.UTF-8
   LANG=en_US.UTF-8
   TERM=xterm-256color
   LC_IDENTIFICATION=de_DE.UTF-8
   LC_TELEPHONE=de_DE.UTF-8
   LC_MEASUREMENT=de_DE.UTF-8
   XDG_RUNTIME_DIR=
   LC_TIME=de_DE.UTF-8
   PATH=(custom, no user)
   LC_NUMERIC=de_DE.UTF-8
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Snap: firefox 84.0.2-1 (stable)
  Tags:  hirsute
  Uname: Linux 5.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True

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


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

Re: [Desktop-packages] [Bug 1949598] Re: Wrong resolution on second monitor after resume from suspend

2021-11-09 Thread Nicolás Abel Carbone

I cannot reproduce the bug on the stock kernel, but the whole resume from
suspend process doesn't work reliably on the stock kernel for my config.
So, I don't know if the bug is not present or if I don't see it because I
never get to that point.

I'll keep researching and see if I can reproduce the issue.

El mié, 3 de nov. de 2021 a la(s) 23:50, Daniel van Vugt (
1949...@bugs.launchpad.net) escribió:

> Thanks for the bug report.
>
> Does the same bug occur if you log into 'Ubuntu on Xorg'?
>
> Does the same bug occur if you run the Ubuntu kernel instead of the
> generic one you have installed?
>
>
> ** Changed in: gnome-shell (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1949598
>
> Title:
>   Wrong resolution on second monitor after resume from suspend
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949598/+subscriptions
>
>

--

Nicolás Abel Carbone

Doctor en Física -  Becario Posdoctoral

CIFICEN-CONICET-UNCPBA

Research Gate 

epsilon.h 

Bionirs 

*Mi horario de trabajo puede no coincidir con el suyo. Salvo que así lo
indique el mail, por favor no se sienta obligado a responder este mensaje
fuera de su horario de trabajo habitual.*

*My working hours may not be your working hours. Unless otherwise specified
in the mail, please do not feel obligated to reply outside of your normal
work schedule.*

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

Title:
  Wrong resolution on second monitor after resume from suspend

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 21.10 on wayland.

  I have two monitors connected to a AMD 5500xt, one via HDMI and
  another, the secondary, via DP, with an DP->VGA adaptor. This setup
  worked just fine on Ubuntu 21.04, also on wayland.

  After updating to 21.10, often (but not always) the secondary monitor
  wakes up showing a wrong, lower resolution. Instead of the normal
  1280x1024, it starts at 800x600. Despite this, in Gnome Settings the
  resolution is still reported as 1280x1024.

  I can solve this issue by changing the resolution in settings and
  reverting back to 1280x1024.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  Uname: Linux 5.13.0-051300-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  3 11:44:16 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-11-04 (364 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-03 (30 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949598/+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 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake

2021-11-09 Thread Igor V. Kovalenko

I believe there is no defined order in which audio devices are resuming,
which makes them appear to pulseaudio in random order. This is probably
causing pulseaudio module-switch-on-connect to flip user preference to
each appearing device in same (random) order. If you do not use this
function you can disable module-switch-on-connect or use it's blacklist
to prevent your preference flipping between devices.

Pulseaudio itself is not aware of suspend/resume function. I do not know
if there is any system callback that confirms that system completed
resume sequence and everything is back (including access rights to audio
devices) so fixing this issue in full will be not a trivial task.

With pulseaudio-15.0 update you can tell pulseaudio to always select specified 
profile when device appears. This also is not a complete solution, but you can 
either make sure your HDMI is always off or is always using the profile with 
your preferred port:
https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/15.0/#cardprofilescanbesettosticky
Pavucontrol 5.0 has easy button for this, or use pactl send-message as 
described in release notes.

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

Title:
  Pulseaudio breaks HDMI audio on sleep/wake

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs
  with pulseaudio after putting my system to sleep and then waking it
  up. these bugs aren't present on a fresh boot, only after resuming
  from sleep:

  - it forgets which sound output device it's set to, and always reverse to the 
motherboard's S/PDIF output.
  - I have two devices connected to my video card, one is a displayport 
monitor, and one is a home theater receiver via HDMI. it confuses the two, and 
randomly switches which device it thinks is capable of surround sound.
  - it sometimes refuses to switch to the correct audio device, and just resets 
any choice back to the internal S/PDIF, until the system is rebooted.

  as you can imagine, this a pretty frustrating state of affairs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.4
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa  3387 F pulseaudio
   /dev/snd/pcmC1D7p:   tessa  3387 F...m pulseaudio
   /dev/snd/controlC2:  tessa  3387 F pulseaudio
   /dev/snd/controlC0:  tessa  3387 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 22 18:38:42 2020
  InstallationDate: Installed on 2020-07-15 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: GRYPHON Z97
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+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 1942788] Autopkgtest regression report (ubuntu-drivers-common/1:0.9.0~0.21.04.2)

2021-11-09 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted ubuntu-drivers-common 
(1:0.9.0~0.21.04.2) for hirsute have finished running.
The following regressions have been reported in tests triggered by the package:

software-properties/0.99.10 (armhf)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#ubuntu-drivers-common

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

Thank you!

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

Title:
  Nvidia doesn't support RTD3 on non-laptops

Status in OEM Priority Project:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Incomplete
Status in ubuntu-drivers-common source package in Hirsute:
  Fix Committed

Bug description:
  According to Nvidia README, the RTD3 doesn't support on non-laptop
  machine.

  https://github.com/tseliot/ubuntu-drivers-common/issues/55

  We need to check chassis type before enabling RTD3.

  ---

  [Impact]

   * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on 
non-laptop machine
   * Patch make system not enable RTD3 unless it's a laptop

  [Test Plan]

   * Install Ubuntu on machine
   * Install GPU driver via 'ubuntu-drivers install'
   * On laptop with Nvidia RTD3 supported GPU. The configuration file 
'/run/nvidia_runtimepm_supported' will be created

  [Where problems could occur]

   * With non-laptop machine use RTD3 supported GPU may use more power

  [Other Info]

  X-HWE-Bug: Bug #1946440

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942788/+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 1913570] Re: Firefox not opening file chooser dialog for importing certificates

2021-11-09 Thread frigo

I hit this bug too with firefox 94.0.1-1 / Ubuntu 20.04.3 LTS (Focal
Fossa)

when trying to import my certificate from /etc/ssl/certs/toto.crt, that
has previously been installed with update-ca-certificates, "nothing
happens" as you describe

when opening the Browser Console, and repeating the action, I get an
error:

message: "Component returned failure code: 0x80520012
(NS_ERROR_FILE_NOT_FOUND) [nsIX509CertDB.importCertsFromFile]"

we can see what happens by looking in the snap:
snap run --shell firefox
cat /etc/ssl/certs/toto.crt
: No such file or directory

this is a symlink that points to a folder under /usr/local/share/ca-
certificates which is not accessible by the snap.

Fix it: copy the file under $HOME where it can be imported... hth

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

Title:
  Firefox not opening file chooser dialog for importing certificates

Status in firefox package in Ubuntu:
  Expired

Bug description:
  When installed as a snap, firefox won't open the file chooser dialog
  for importing a certificate authority. However, it is working when
  installed using apt.

  How to reproduce:
  1. Install firefox as snap
  2. Navigate to Preferences | Privacy & Security | Certificates | View 
Certificates
  3. Select Authorities
  4. Click Import ...
 -> A file selector dialog should open to import a certificate, but nothing 
happens.

  Environment:
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Thu Jan 28 11:43:55 2021
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-01-15 (12 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 
(20210115)
  ProcCpuinfoMinimal:
   processor: 3
   vendor_id: GenuineIntel
   cpu family   : 6
   model: 42
   model name   : Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
   stepping : 7
   microcode: 0x2f
   cpu MHz  : 3701.000
   cache size   : 8192 KB
   physical id  : 6
   siblings : 1
   core id  : 0
   cpu cores: 1
   apicid   : 6
   initial apicid   : 6
   fpu  : yes
   fpu_exception: yes
   cpuid level  : 13
   wp   : yes
   flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc 
arch_perfmon nopl xtopology tsc_reliable nonstop_tsc cpuid pni pclmulqdq ssse3 
cx16 pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx 
hypervisor lahf_lm pti ssbd ibrs ibpb stibp tsc_adjust arat md_clear flush_l1d 
arch_capabilities
   bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs itlb_multihit
   bogomips : 7402.00
   clflush size : 64
   cache_alignment  : 64
   address sizes: 43 bits physical, 48 bits virtual
   power management:
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=en_US
   LC_ADDRESS=de_DE.UTF-8
   LC_NAME=de_DE.UTF-8
   LC_MONETARY=de_DE.UTF-8
   LC_PAPER=de_DE.UTF-8
   LANG=en_US.UTF-8
   TERM=xterm-256color
   LC_IDENTIFICATION=de_DE.UTF-8
   LC_TELEPHONE=de_DE.UTF-8
   LC_MEASUREMENT=de_DE.UTF-8
   XDG_RUNTIME_DIR=
   LC_TIME=de_DE.UTF-8
   PATH=(custom, no user)
   LC_NUMERIC=de_DE.UTF-8
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Snap: firefox 84.0.2-1 (stable)
  Tags:  hirsute
  Uname: Linux 5.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1913570/+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 1947746] Re: [Snap] Ubuntu Firefox installed from snap cannot use Trezor U2F

2021-11-09 Thread Aditya Suseno

The solution from mcudev works for me.
I added this lines on 51-trezor.rules file and copied to /etc/udev/rules.d/ 
then restart my machine and voila it works!

Thanks mcudev and Olivier Tilloy!
You are the reasons I still using Firefox ️

** Attachment added: "Screenshot from 2021-11-10 02-23-39.png"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947746/+attachment/5539313/+files/Screenshot%20from%202021-11-10%2002-23-39.png

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

Title:
  [Snap] Ubuntu Firefox installed from snap cannot use Trezor U2F

Status in firefox package in Ubuntu:
  In Progress

Bug description:
  Trezor U2F security key doesn't work with firefox snap after updating
  to Ubuntu 21.10, but works with apt debian firefox package.

  Steps to reproduce:
  1) Insert Trezor U2F security key in USB port.
  2) Launch `run snap firefox` (it is the default on Ubuntu 21.10)
  3) Test https://demo.yubico.com/webauthn-technical/registration

  It works well on Ubuntu 21.04 and on traditional apt debian
  installation.

  
  $ snap list firefox
  Name Version  Rev  Tracking   Publisher  Notes
  firefox  93.0-1   631  latest/stable  mozilla✓   -

  
  $ snap connections firefox
  Interface PlugSlot
 Notes
  audio-playbackfirefox:audio-playback  :audio-playback 
 -
  audio-record  firefox:audio-record:audio-record   
 -
  avahi-observe firefox:avahi-observe   :avahi-observe  
 -
  browser-support   firefox:browser-sandbox :browser-support
 -
  camerafirefox:camera  :camera 
 -
  content[gnome-3-38-2004]  firefox:gnome-3-38-2004 
gnome-3-38-2004:gnome-3-38-2004  -
  content[gtk-3-themes] firefox:gtk-3-themes
gtk-common-themes:gtk-3-themes   -
  content[icon-themes]  firefox:icon-themes 
gtk-common-themes:icon-themes-
  content[sound-themes] firefox:sound-themes
gtk-common-themes:sound-themes   -
  cups-control  firefox:cups-control:cups-control   
 -
  dbus  -   firefox:dbus-daemon 
 -
  desktop   firefox:desktop :desktop
 -
  desktop-legacyfirefox:desktop-legacy  :desktop-legacy 
 -
  gsettings firefox:gsettings   :gsettings  
 -
  hardware-observe  firefox:hardware-observe:hardware-observe   
 -
  home  firefox:home:home   
 -
  joystick  firefox:joystick-   
 -
  mpris -   firefox:mpris   
 -
  network   firefox:network :network
 -
  network-observe   firefox:network-observe -   
 -
  openglfirefox:opengl  :opengl 
 -
  personal-filesfirefox:dot-mozilla-firefox :personal-files 
 -
  removable-media   firefox:removable-media :removable-media
 -
  screen-inhibit-controlfirefox:screen-inhibit-control  
:screen-inhibit-control  -
  system-files  firefox:etc-firefox-policies:system-files   
 -
  system-packages-doc   firefox:system-packages-doc 
:system-packages-doc -
  u2f-devices   firefox:u2f-devices :u2f-devices
 -
  unity7firefox:unity7  :unity7 
 -
  upower-observefirefox:upower-observe  :upower-observe 
 -
  wayland   firefox:wayland :wayland
 -
  x11   firefox:x11 :x11
 -

  
  $ cat /etc/os-release 
  PRETTY_NAME="Ubuntu 21.10"
  NAME="Ubuntu"
  VERSION_ID="21.10"
  VERSION="21.10 (Impish Indri)"
  VERSION_CODENAME=impish
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  UBUNTU_CODENAME=impish

  
  $ echo $XDG_SESSION_TYPE
  wayland

  
  $ uname -r
  5.13.0-19-generic

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1950355] [NEW] Intense screen flickering, vertical rainbow bars, display problems on Ubuntu 20.04, Lenovo X1 Carbon

2021-11-09 Thread Amol

Public bug reported:

(Initial post on ask ubuntu, copy pasted:
https://askubuntu.com/questions/1359955/intense-screen-flickering-
vertical-rainbow-bars-display-problems-on-ubuntu-20)

Starting today (Aug 24) I observed intense screen flickering and tearing
on my Ubuntu 20.04.3 on the Lenovo X1 Carbon. As far as I know, there
were no shutdowns, updates, or changes. I observed this behavior once
the machine started up from sleep. Throughout the day I have restarted
(and powered down) the machine several times, but the problem persists.

Here is a video example: https://photos.app.goo.gl/516nAe7AUUYnAHzd7

Here is an image: https://i.stack.imgur.com/RgLvB.jpg

This video was taken from a clean Ubuntu install USB, so I don't think
it has to do with anything I've installed or updated in the past. The
system does not have any other operating systems on it (its not dual
booted).

I'm using basic integrated graphics (Mesa Intel® UHD Graphics 620 (WHL
GT2)). System has 16gb of RAM and a Intel® Core™ i7-8665U CPU @ 1.90GHz
× 8 processor, so I don't think the issue is available processing power
(although the integrated graphics could be bad).

I'm already using Wayland.

I tried everything in the following links: Ubuntu screen flickering
https://www.reddit.com/r/Ubuntu/comments/g78o4e/screen_tearing_in_ubuntu_2004/

The flickering is most noticeable in Chrome/Firefox (regardless of
enabling/disabling hardware acceleration or setting any chrome://flags).
However, I've also observed it with just editing Vim in terminal.

EDIT: A month later, still experiencing this issue. This problem really
seems to come and go -- it will go days without issue, and then have
days again where it is constant. I've noticed it on all browsers. I've
noticed that closing the webbrowser seems to resolve the issue most of
the time. I've noticed that this is not an issue on any extended
screens, just the main screen.

---

Since the above post, I tried booting into a clean live disk running
Ubuntu 20.04.2. This actually worked fine, and I did not observe any
strange graphical effects. As per the reply on ask ubuntu, I decided to
file this bug.

---

Ubuntu release
Description:Ubuntu 20.04.3 LTS
Release:20.04

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

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  9 13:16:35 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed
 virtualbox, 6.1.26, 5.11.0-38-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
InstallationDate: Installed on 2021-03-15 (239 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: LENOVO 20QDS3B800
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.11.0-38-generic 
root=UUID=9213d3af-1e40-4621-9964-1212d1070372 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/24/2020
dmi.bios.release: 1.38
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET55W (1.38 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDS3B800
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.20
dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET55W(1.38):bd08/24/2020:br1.38:efr1.20:svnLENOVO:pn20QDS3B800:pvrThinkPadX1Carbon7th:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:rvnLENOVO:rn20QDS3B800:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDS3B800
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A

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

2021-11-09 Thread Gunnar Hjalmarsson

From the buildlog:

dpkg-source: info: applying desktopManager-Avoid-scheduling-multiple-
_layoutChil.patch

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

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

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

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

Bug description:
  [Impact]

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

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

  [Test Case]

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

  [Where problems could occur]

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

  [Other Info]

  See also bug 1898910

  ---

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

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

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


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

[Desktop-packages] [Bug 1917152] Re: File moved with Cut-Paste from a search filter still appears on original screen and if deleted disappears from new folder

2021-11-09 Thread ar barzh paour

same thing on Ubuntu 22.04

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

Title:
  File moved with Cut-Paste from a search filter still appears on
  original screen and if deleted disappears from new folder

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  Confirmed
Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  Affected version
  Nautilus 3.38 on Ubuntu 20.10 (but I also saw this bug some months and 
versions ago)

  I don't know if it's a specific Ubuntu bug or an upstream one, I reported it 
1.5 month ago on Gitlab Gnome without any answer nor review:
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/1723

  Resume: File moved with "Cut" from a window with an active search
  filter, and pasted in another folder on a second Nautilus window (not
  a subfolder), still appears on the first original screen (list is not
  automatically updated) - and if deleted from here, actually they
  disappear from the new folder !

  It can occur to loose important documents  - I often make direct
  shift-deletes, without recycler storage...

  Steps to reproduce
  I open a Nautilus window, go to a folder and make a search filter, for 
example 20 files appear on the window which name contains my search filter.

  If I select one of them, make Cut / Ctrl-X, open a new Nautilus
  window, go to another folder (which is not a subfolder of the first)
  and make Paste / Ctrl-V, it wells copy the file in the new folder.

  If I switch to the first Nautilus window with the original folder and
  search filter active, the moved file still appears on the list and I
  can open it. I think I've made an error (Ctrl-C instead of Ctrl-X) so
  I shift-delete it, it disappears from the list and only 19 files
  remain.

  Current behavior
  But… If I go to the second Nautilus window and the 2nd folder, the file has 
also disappeared from it ! File in the first window was "transformed" to a link 
instead of being removed, and suppressing it also deletes the file in its new 
folder - in my case, I lost several documents like this because of Shift-Delete 
and not trash use.

  Expected behavior
  After Cut - Paste, in the case of 2 Nautilus windows are opened, the file(s) 
moved from the first one should not be still visible in the search list, there 
should be an automatic refresh.

  If I do a Copy-Paste instead of a Cut-Paste, problem does not occur:
  delete only removes file in the fist original folder, not on the
  second. If I close the search filter, it's also OK, file(s) moved no
  more visible. And of course, if after Cut I stay in the same Nautilus
  window and go to another folder to paste, no problem: bug only occurs
  in case of a second window opened.

  Thanks in advance and best regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1917152/+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 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake

2021-11-09 Thread Alexey Gusev

the same problem on 21.10 
pulseaudio package 1:15.0+dfsg1-1ubuntu2

default output is reset in random order after resume from sleep.
Sometimes it stays as it was before suspend, but more often it just
changes to HDMI or dock output.

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

Title:
  Pulseaudio breaks HDMI audio on sleep/wake

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs
  with pulseaudio after putting my system to sleep and then waking it
  up. these bugs aren't present on a fresh boot, only after resuming
  from sleep:

  - it forgets which sound output device it's set to, and always reverse to the 
motherboard's S/PDIF output.
  - I have two devices connected to my video card, one is a displayport 
monitor, and one is a home theater receiver via HDMI. it confuses the two, and 
randomly switches which device it thinks is capable of surround sound.
  - it sometimes refuses to switch to the correct audio device, and just resets 
any choice back to the internal S/PDIF, until the system is rebooted.

  as you can imagine, this a pretty frustrating state of affairs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.4
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa  3387 F pulseaudio
   /dev/snd/pcmC1D7p:   tessa  3387 F...m pulseaudio
   /dev/snd/controlC2:  tessa  3387 F pulseaudio
   /dev/snd/controlC0:  tessa  3387 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 22 18:38:42 2020
  InstallationDate: Installed on 2020-07-15 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: GRYPHON Z97
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+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 1923893] Re: After rescheduling an event, calendar alerts appear for the old time

2021-11-09 Thread Kai Groner

This issue in evolution-data-server seems to describe the problem.

https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/276


** Bug watch added: gitlab.gnome.org/GNOME/evolution-data-server/-/issues #276
   https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/276

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

Title:
  After rescheduling an event, calendar alerts appear for the old time

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I use google calendar.  Events are created and updated via the
  browser. The calendar feed is configured through settings/online
  accounts. I can see upcoming events in the calendar drop down. The
  calendar and desktop are configured for the same timezone, and alerts
  normally appear simultaneously on my phone and desktop.

  I know sometimes stale calendar entries can be a factor, but I don't
  *think* that's an issue at this time (the change was made almost 24
  hours ago, I don't see the API limit errors I used to see in logs).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.2-1ubuntu1~20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 15:02:11 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-18 (666 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs:
   linux-image-5.8.0-49-generic
   linux-base
  RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (171 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1923893/+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 1885246] Re: Desktop freezes when moving window fast to other desktop

2021-11-09 Thread Guus Ellenkamp

More log available. The problem seems to occur when 'something else'
goes wrong, like some network error.

** Attachment added: "my-other-dmesg.log"

https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1885246/+attachment/5539283/+files/my-other-dmesg.log

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

Title:
Desktop freezes when moving window fast to other desktop

Status in lightdm package in Ubuntu:
New

Bug description:
For a long time sometimes my desktop freezes suddenly and it took me a
long time to find when. It turns out sometimes the desktop freezes
when I move a window fast from one desktop to another, normally I
would move it to the right.

OS is Ubuntu 18.04 and the issue occurs (as far as I remember) with
the Open Source drivers and the AMD drivers. When using some default
setting/driver the issue does not occur, but then screen updates are
very slow.

I am using an MSI H81M-P33 motherboard, processor i5-4460, AMD Radeon
HD 7700 Series (according to AMD driver). Monitor is AOC 1920x1080.

I tried many things, like different kernal versions and different
drivers. The currently installed AMD drivers don't work with the 5.3
kernel. I did not recently use something like kernel 5.0, so I don't
know if the issue is solved in later kernels.

I found some similar reports, but they all or mostly seem to relate to
laptops. While writing this report my desktop crashed again and I was
not moving a window, but just resizing it from the top down.

I can access the system through ssh and just changed the drivers from
AMD pro to AMD open source. Not sure what the effect is. More details
available if needed.

I would appreciate this would be solved, as it is pretty annoying to
restart my computer several times a day and sometimes losing work.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
Uname: Linux 4.15.0-108-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CurrentDesktop: LXDE
Date: Fri Jun 26 13:42:55 2020
InstallationDate: Installed on 2019-05-30 (392 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
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/1885246/+subscriptions

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

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

Hello Peter, or anyone else affected,

Accepted gnome-shell-extension-desktop-icons into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-
icons/20.04.0-3~ubuntu20.04.5 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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

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

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

Bug description:
  [Impact]

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

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

  [Test Case]

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

  [Where problems could occur]

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

  [Other Info]

  See also bug 1898910

  ---

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

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

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


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

[Desktop-packages] [Bug 1923893] Re: After rescheduling an event, calendar alerts appear for the old time

2021-11-09 Thread Kai Groner

This is still happening after upgrading to 21.10. The calendar reminder
I saw today and last night was canceled several weeks ago. When I looked
in the topbar calendar dropdown, the event did not appear there.

It's unclear to me if this is a gnome-shell issue or a gnome-calendar
issue or maybe something like evolution-data-server?

** Tags removed: hirsute
** Tags added: impish

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

Title:
  After rescheduling an event, calendar alerts appear for the old time

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I use google calendar.  Events are created and updated via the
  browser. The calendar feed is configured through settings/online
  accounts. I can see upcoming events in the calendar drop down. The
  calendar and desktop are configured for the same timezone, and alerts
  normally appear simultaneously on my phone and desktop.

  I know sometimes stale calendar entries can be a factor, but I don't
  *think* that's an issue at this time (the change was made almost 24
  hours ago, I don't see the API limit errors I used to see in logs).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.2-1ubuntu1~20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 14 15:02:11 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-18 (666 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs:
   linux-image-5.8.0-49-generic
   linux-base
  RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (171 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1923893/+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 1942789] Re: On-demand and RTD3 need to be separated

** Changed in: nvidia-prime (Ubuntu Focal)
   Status: New => Incomplete

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

Title:
  On-demand and RTD3 need to be separated

Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in nvidia-prime source package in Focal:
  Incomplete
Status in ubuntu-drivers-common source package in Focal:
  New
Status in nvidia-prime source package in Hirsute:
  New
Status in ubuntu-drivers-common source package in Hirsute:
  New

Bug description:
  RTD3 is a nvidia GPU feature to support runtime suspend.

  On-demand would be a X offloading feature.

  They are independent, according to discussion on
  https://github.com/tseliot/ubuntu-drivers-common/issues/55.

  Some parts need to be adjusted, e.g.

  ```
  # If we are dealing with NVIDIA PRIME, and runtimepm
  # is supported, enable it
  if (os.path.isfile('/run/nvidia_runtimepm_supported') and
  os.path.isfile('/usr/bin/prime-select')):
  print('Trying to select the on-demand PRIME profile')
  try:
  subprocess.call(['prime-select', 'on-demand'])
  except:
  pass

  # Create the override file for gpu-manager
  with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
  f.write('# File created by ubuntu-drivers\n')
  ```

  ---

  [Impact]

   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine

  [Test Plan]

   * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU 
driver. After the installation, reboot the system. Execute "prime-select query" 
should get "on-demand"
   * On non-laptop machine. Can set GPU mode to on-demand
   * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"

  [Where problems could occur]

   * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
   * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.

  [Other Info]

  X-HWE-Bug: Bug #1946434

  Changelogs:

  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium

    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)

    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
    RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
    is not available.
  - Don't check the current profile when setting
    a profile (LP: #1946476).
  - Catch BrokenPipeError.
  - Use bootvga detection when last_gfx_boot is
    not available.

  nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium

    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)

    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
    RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
    is not available.
  - Don't check the current profile when setting
    a profile (LP: #1946476).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942789/+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 1885246] Re: Desktop freezes when moving window fast to other desktop

2021-11-09 Thread Guus Ellenkamp

I am still having this problem with newer versions of all kinds of
things and even a new video card (of similar type).

Current video drivers etc.:

-Display-
Resolution  : 1920x1080 pixels
Vendor  : The X.Org Foundation
Version : 1.20.13
Current Display Name: :0
-Monitors-
Monitor 0   : 1920x1080 pixels
-OpenGL-
Vendor  : X.Org
Renderer: AMD JUNIPER (DRM 2.50.0 / 5.4.0-90-generic, LLVM 
13.0.0)
Version : 3.1 Mesa 22.0.0-devel (git-df92a13 2021-11-09 focal-oibaf-ppa)
Direct Rendering: Yes
-Extensions-
Composite
DAMAGE
DOUBLE-BUFFER
DPMS
DRI2
DRI3
GLX
Generic Event Extension
MIT-SCREEN-SAVER
MIT-SHM
Present
RANDR
RECORD
RENDER
SECURITY
SHAPE
SYNC
X-Resource
XC-MISC
XFIXES
XFree86-DGA
XFree86-VidModeExtension
XINERAMA
XInputExtension
XKEYBOARD
XTEST
XVideo
XVideo-MotionCompensation
default screen number:0

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

Title:
  Desktop freezes when moving window fast to other desktop

Status in lightdm package in Ubuntu:
  New

Bug description:
  For a long time sometimes my desktop freezes suddenly and it took me a
  long time to find when. It turns out sometimes the desktop freezes
  when I move a window fast from one desktop to another, normally I
  would move it to the right.

  OS is Ubuntu 18.04 and the issue occurs (as far as I remember) with
  the Open Source drivers and the AMD drivers. When using some default
  setting/driver the issue does not occur, but then screen updates are
  very slow.

  I am using an MSI H81M-P33 motherboard, processor i5-4460, AMD Radeon
  HD 7700 Series (according to AMD driver). Monitor is AOC 1920x1080.

  I tried many things, like different kernal versions and different
  drivers. The currently installed AMD drivers don't work with the 5.3
  kernel. I did not recently use something like kernel 5.0, so I don't
  know if the issue is solved in later kernels.

  I found some similar reports, but they all or mostly seem to relate to
  laptops. While writing this report my desktop crashed again and I was
  not moving a window, but just resizing it from the top down.

  I can access the system through ssh and just changed the drivers from
  AMD pro to AMD open source. Not sure what the effect is. More details
  available if needed.

  I would appreciate this would be solved, as it is pretty annoying to
  restart my computer several times a day and sometimes losing work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
  Uname: Linux 4.15.0-108-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Jun 26 13:42:55 2020
  InstallationDate: Installed on 2019-05-30 (392 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  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/1885246/+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 1942789] Re: On-demand and RTD3 need to be separated

I find the statement "focal does not have nvidia driver lower than 450"
in the bug description confusing.  I see the source package nvidia-
graphics-drivers-390 as being available in Focal.

https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390

Could somebody give some more information about how setting the GPU mode
to on-demand will work with this driver?

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

Title:
  On-demand and RTD3 need to be separated

Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in nvidia-prime source package in Focal:
  New
Status in ubuntu-drivers-common source package in Focal:
  New
Status in nvidia-prime source package in Hirsute:
  New
Status in ubuntu-drivers-common source package in Hirsute:
  New

Bug description:
  RTD3 is a nvidia GPU feature to support runtime suspend.

  On-demand would be a X offloading feature.

  They are independent, according to discussion on
  https://github.com/tseliot/ubuntu-drivers-common/issues/55.

  Some parts need to be adjusted, e.g.

  ```
  # If we are dealing with NVIDIA PRIME, and runtimepm
  # is supported, enable it
  if (os.path.isfile('/run/nvidia_runtimepm_supported') and
  os.path.isfile('/usr/bin/prime-select')):
  print('Trying to select the on-demand PRIME profile')
  try:
  subprocess.call(['prime-select', 'on-demand'])
  except:
  pass

  # Create the override file for gpu-manager
  with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
  f.write('# File created by ubuntu-drivers\n')
  ```

  ---

  [Impact]

   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine

  [Test Plan]

   * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU 
driver. After the installation, reboot the system. Execute "prime-select query" 
should get "on-demand"
   * On non-laptop machine. Can set GPU mode to on-demand
   * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"

  [Where problems could occur]

   * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
   * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.

  [Other Info]

  X-HWE-Bug: Bug #1946434

  Changelogs:

  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium

    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)

    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
    RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
    is not available.
  - Don't check the current profile when setting
    a profile (LP: #1946476).
  - Catch BrokenPipeError.
  - Use bootvga detection when last_gfx_boot is
    not available.

  nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium

    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)

    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
    RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
    is not available.
  - Don't check the current profile when setting
    a profile (LP: #1946476).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942789/+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 1942788] Re: Nvidia doesn't support RTD3 on non-laptops

Hello jeremyszu, or anyone else affected,

Accepted ubuntu-drivers-common into hirsute-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-drivers-
common/1:0.9.0~0.21.04.2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ubuntu-drivers-common (Ubuntu Hirsute)
   Status: Incomplete => Fix Committed

** Tags added: verification-needed verification-needed-hirsute

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

Title:
  Nvidia doesn't support RTD3 on non-laptops

Status in OEM Priority Project:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Incomplete
Status in ubuntu-drivers-common source package in Hirsute:
  Fix Committed

Bug description:
  According to Nvidia README, the RTD3 doesn't support on non-laptop
  machine.

  https://github.com/tseliot/ubuntu-drivers-common/issues/55

  We need to check chassis type before enabling RTD3.

  ---

  [Impact]

   * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on 
non-laptop machine
   * Patch make system not enable RTD3 unless it's a laptop

  [Test Plan]

   * Install Ubuntu on machine
   * Install GPU driver via 'ubuntu-drivers install'
   * On laptop with Nvidia RTD3 supported GPU. The configuration file 
'/run/nvidia_runtimepm_supported' will be created

  [Where problems could occur]

   * With non-laptop machine use RTD3 supported GPU may use more power

  [Other Info]

  X-HWE-Bug: Bug #1946440

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942788/+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 1931602] Re: [apparmor] Segfault in logs with apparmor enabled

Attaching a fix proposal for jammy.

** Patch added: "jammy.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931602/+attachment/5539262/+files/jammy.debdiff

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

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

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

** Changed in: firefox (Ubuntu Impish)
   Importance: Medium => Low

** Changed in: firefox (Ubuntu Hirsute)
   Importance: Medium => Low

** Changed in: firefox (Ubuntu Focal)
   Importance: Medium => Low

** Changed in: firefox (Ubuntu)
   Importance: Medium => Low

** Tags added: sts-sponsor-dgadomski

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

Title:
  [apparmor] Segfault in logs with apparmor enabled

Status in firefox package in Ubuntu:
  Confirmed
Status in firefox source package in Focal:
  Confirmed
Status in firefox source package in Hirsute:
  New
Status in firefox source package in Impish:
  New

Bug description:
  [Impact]

   * With apparmor enabled (and usr.bin.firefox in enforce mode) there
  is a crash happening every time right after launching Firefox.

  [Test Plan]

   * sudo aa-enforce /etc/apparmor.d/usr.bin.firefox

   * launch Firefox

   * See a similar segfault reported in the syslog:
  Jun 10 17:25:40 ubuntu kernel: [   86.775837] firefox[1765]: segfault at 0 ip 
7f724dd06384 sp 7fffa7aec450 error 6 in libxul.so[7f724a483000+53b2000]
  Jun 10 17:25:40 ubuntu kernel: [   86.775843] Code: 00 0f 1f 44 00 00 50 80 
3d f8 56 4c 04 00 74 02 58 c3 c6 05 ed 56 4c 04 01 48 8d 05 24 2c fa 02 48 8b 
0d 77 f0 3a 04 48 89 01  04 25 00 00 00 00 8d 01 00 00 e8 74 63 78 fc 66 2e 
0f 1f 84 00

  [Where problems could occur]

  The fix adds additional paths to firefox apparmor profile (e.g. affecting 
/sys/devices/pci* and RealtimeKit1). When using deb version of firefox the 
browser may chose a different code path to execute than before, so it may 
affect hw acceleration (the sysfs paths were used by libxul) and audio.
  Maybe rendering artifacts and audio sync issues in videos.

  [Other Info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931602/+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 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context

2021-11-09 Thread Jean-Baptiste Lallement

** Description changed:

  [Description]
  This is a request to backport this fix from mesa 21.1 to focal-updates which 
is affecting users of WSL:
  
  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87
  
  This cached stale pointer is causing various chromium applications
  (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is
  enabled in WSLg. We’re getting incredibly unlucky because a glx drawable
  is being freed and reallocated with exactly the same heap pointers
  during a resize, which is causing Mesa to think the new drawable is
  already fully initialized when binded to the context, but it is not true
  and only because the new drawable is matching the old stale pointer for
  the previously freed drawable… and as a result the context remain
  invalid and the app is unable to present.
  
  With the push of WDDMv3 drivers which expose vGPU in WSL, the number of
  users hitting this issue is increasing.
+ 
+ [Test Case]

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

Title:
  [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Triaged

Bug description:
  [Description]
  This is a request to backport this fix from mesa 21.1 to focal-updates which 
is affecting users of WSL:

  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87

  This cached stale pointer is causing various chromium applications
  (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU
  is enabled in WSLg. We’re getting incredibly unlucky because a glx
  drawable is being freed and reallocated with exactly the same heap
  pointers during a resize, which is causing Mesa to think the new
  drawable is already fully initialized when binded to the context, but
  it is not true and only because the new drawable is matching the old
  stale pointer for the previously freed drawable… and as a result the
  context remain invalid and the app is unable to present.

  With the push of WDDMv3 drivers which expose vGPU in WSL, the number
  of users hitting this issue is increasing.

  [Test Case]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+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 1949970] Re: attempt to dlopen nonexistent pam_kwallet.so spams log

** Changed in: lightdm (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

Title:
  attempt to dlopen nonexistent pam_kwallet.so spams log

Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Bionic:
  New
Status in lightdm source package in Focal:
  Fix Committed
Status in lightdm source package in Hirsute:
  Fix Committed
Status in lightdm source package in Impish:
  Fix Committed
Status in lightdm source package in Jammy:
  Fix Released

Bug description:
  [impact]

  lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as
  well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet
  which died around Trusty (https://launchpad.net/ubuntu/+source/pam-
  kwallet) while pam_kwallet5.so comes from kwallet-pam which provides
  only the newer '5' version, not the older unversioned library file.

  This results in repeated spam error messages in the system log
  complaining about failure to load pam_kwallet.so

  [test case]

  install/enable lightdm and check system log at boot for messages like:

  Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so

  [regression potential]

  any regression would likely cause problems during login and/or missing
  or extra log messages during pam authentication.

  [scope]

  this is needed in all releases

  [other info]

  https://github.com/canonical/lightdm/pull/216

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1949970/+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 1942789] Re: On-demand and RTD3 need to be separated

** Changed in: nvidia-prime (Ubuntu Focal)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-prime (Ubuntu Hirsute)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: ubuntu-drivers-common (Ubuntu Focal)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: ubuntu-drivers-common (Ubuntu Hirsute)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  On-demand and RTD3 need to be separated

Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in nvidia-prime source package in Focal:
  New
Status in ubuntu-drivers-common source package in Focal:
  New
Status in nvidia-prime source package in Hirsute:
  New
Status in ubuntu-drivers-common source package in Hirsute:
  New

Bug description:
  RTD3 is a nvidia GPU feature to support runtime suspend.

  On-demand would be a X offloading feature.

  They are independent, according to discussion on
  https://github.com/tseliot/ubuntu-drivers-common/issues/55.

  Some parts need to be adjusted, e.g.

  ```
  # If we are dealing with NVIDIA PRIME, and runtimepm
  # is supported, enable it
  if (os.path.isfile('/run/nvidia_runtimepm_supported') and
  os.path.isfile('/usr/bin/prime-select')):
  print('Trying to select the on-demand PRIME profile')
  try:
  subprocess.call(['prime-select', 'on-demand'])
  except:
  pass

  # Create the override file for gpu-manager
  with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
  f.write('# File created by ubuntu-drivers\n')
  ```

  ---

  [Impact]

   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine

  [Test Plan]

   * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU 
driver. After the installation, reboot the system. Execute "prime-select query" 
should get "on-demand"
   * On non-laptop machine. Can set GPU mode to on-demand
   * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"

  [Where problems could occur]

   * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
   * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.

  [Other Info]

  X-HWE-Bug: Bug #1946434

  Changelogs:

  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium

    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)

    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
    RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
    is not available.
  - Don't check the current profile when setting
    a profile (LP: #1946476).
  - Catch BrokenPipeError.
  - Use bootvga detection when last_gfx_boot is
    not available.

  nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium

    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)

    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
    RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
    is not available.
  - Don't check the current profile when setting
    a profile (LP: #1946476).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942789/+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 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context

** Changed in: mesa (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Triaged

Bug description:
  [Description]
  This is a request to backport this fix from mesa 21.1 to focal-updates which 
is affecting users of WSL:

  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87

  This cached stale pointer is causing various chromium applications
  (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU
  is enabled in WSLg. We’re getting incredibly unlucky because a glx
  drawable is being freed and reallocated with exactly the same heap
  pointers during a resize, which is causing Mesa to think the new
  drawable is already fully initialized when binded to the context, but
  it is not true and only because the new drawable is matching the old
  stale pointer for the previously freed drawable… and as a result the
  context remain invalid and the app is unable to present.

  With the push of WDDMv3 drivers which expose vGPU in WSL, the number
  of users hitting this issue is increasing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+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 1948008] Re: Copying and pasting to/from Nautilus does not work

** Changed in: gnome-shell (Ubuntu Focal)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

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

Title:
  Copying and pasting to/from Nautilus does not work

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Invalid
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  New
Status in gnome-shell source package in Focal:
  New
Status in gnome-shell-extension-desktop-icons source package in Focal:
  New
Status in gnome-shell-extension-desktop-icons-ng source package in Focal:
  Invalid
Status in gnome-shell source package in Hirsute:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Hirsute:
  Invalid
Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute:
  New
Status in gnome-shell source package in Impish:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Impish:
  Invalid
Status in gnome-shell-extension-desktop-icons-ng source package in Impish:
  New

Bug description:
  [Impact]

   * After upstream Nautilus has reverted the following commit [1]
  related to upstream bug [2] the desktop icons extension lost it's
  ability to copy to/from nautilus.

   * This is related to the fact that before there was some metadata
  passed along in the clipboard along with text data. This was causing
  issues with compatibility with some applications that were not
  expecting any metadata (MIME type in this case) was glued to the text
  clipboard contents. Hence, it was reverted upstream [3].

   * Fixing the root cause of this issue required changes to Nautilus
  [3], gnome-shell [4] and desktop-icons [5] [6]. Nautilus and gnome-
  shell parts are already implemented and present in Hirsute and Impish.

  
  [Test Plan]

   1) Make sure desktop-icons extension is enabled.
   2) Open nautilus window and copy any file from there by right-clicking and 
selecting "Copy" from the popup menu.
   3) Right-click on desktop and select "Paste" from the context menu.

  Expected result: selected file is copied to the desktop.
  Actual result: "Paste" item is disabled in the menu.

  [Where problems could occur]

   * Mixing a version of nautilus without commit [3] and fixed version
  of desktop-icons may still lead to a scenario when copying will not
  work.

   * Any extension/application copying to desktop using the smuggled-in-
  text clipboard behavior should be expected to stop working.

  [Other Info]

  [1] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/289
  [2] https://gitlab.gnome.org/GNOME/nautilus/-/issues/634
  [3] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/573
  [4] https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1321
  [5] 
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186
  [6] 
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948008/+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 1931602] Re: [apparmor] Segfault in logs with apparmor enabled

** Changed in: firefox (Ubuntu Hirsute)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

** Changed in: firefox (Ubuntu Impish)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

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

Title:
  [apparmor] Segfault in logs with apparmor enabled

Status in firefox package in Ubuntu:
  Confirmed
Status in firefox source package in Focal:
  Confirmed
Status in firefox source package in Hirsute:
  New
Status in firefox source package in Impish:
  New

Bug description:
  [Impact]

   * With apparmor enabled (and usr.bin.firefox in enforce mode) there
  is a crash happening every time right after launching Firefox.

  [Test Plan]

   * sudo aa-enforce /etc/apparmor.d/usr.bin.firefox

   * launch Firefox

   * See a similar segfault reported in the syslog:
  Jun 10 17:25:40 ubuntu kernel: [   86.775837] firefox[1765]: segfault at 0 ip 
7f724dd06384 sp 7fffa7aec450 error 6 in libxul.so[7f724a483000+53b2000]
  Jun 10 17:25:40 ubuntu kernel: [   86.775843] Code: 00 0f 1f 44 00 00 50 80 
3d f8 56 4c 04 00 74 02 58 c3 c6 05 ed 56 4c 04 01 48 8d 05 24 2c fa 02 48 8b 
0d 77 f0 3a 04 48 89 01  04 25 00 00 00 00 8d 01 00 00 e8 74 63 78 fc 66 2e 
0f 1f 84 00

  [Where problems could occur]

  The fix adds additional paths to firefox apparmor profile (e.g. affecting 
/sys/devices/pci* and RealtimeKit1). When using deb version of firefox the 
browser may chose a different code path to execute than before, so it may 
affect hw acceleration (the sysfs paths were used by libxul) and audio.
  Maybe rendering artifacts and audio sync issues in videos.

  [Other Info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931602/+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 1949291] Re: LibreOffice has started displaying a donation nag

Ubuntu is an opensource operating system and not a commercial product,
the banner is easy to dismis and the frequency isn't unreasonable, we
are not going to change that over upstream

** Changed in: libreoffice (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: libreoffice (Ubuntu)
   Status: New => Triaged

** Tags removed: rls-jj-incoming
** Tags added: rls-jj-notfixing

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

Title:
  LibreOffice has started displaying a donation nag

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

Bug description:
  I just opened up a spreadsheet (technically a CSV file, but who's
  counting), to discover LibreOffice displaying an eye-catching blue
  "Your donations support our worldwide community." banner just below
  the toolbars and about a toolbar and a half tall.

  This irritating nag is apparently supposed to display every 90 to 180
  days with no in-application means to disable it permanently, and
  there's apparently also a "Help us make LibreOffice even better!"
  banner that can appear too.

  According to this blog post...

  https://www.remembertheusers.com/2019/11/0580-libreoffice-nag-
  notices.html

  ...it is not responsive to configuration overrides within the user
  profile and the only apparent solution that doesn't require patching
  the source and rebuilding is to create a file containing the following
  markup in `$BASEDIR/share/registry`
  (`/usr/lib/libreoffice/share/registry` as installed by the Ubuntu
  package):

  
  http://www.w3.org/2001/XMLSchema; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xmlns:oor="http://openoffice.org/2001/registry;>

http://openoffice.org/2004/installation; oor:name="Setup" 
oor:package="org.openoffice">
  

  0


  0

  

  

  Regardless of how it's achieved, I think it's tasteless, irritating,
  and probably doesn't give a very good image to any office customers
  Ubuntu may have downstream for random employees to be receiving nag
  banners like that in IT-installed software.

  Please consider patching it out or otherwise ensuring it never
  triggers in distro-provided builds of LibreOffice.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun Oct 31 04:32:03 2021
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1949291/+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 1947420] Re: Buggish interface @ workstation panels previews when using dual portrait

2021-11-09 Thread bornagainpenguin

Adding myself to this as this also affects me.  At first I thought it
was just the way things were from now on, as an experiment in how the
workplace switcher worked. I did not realize it was a bug until I saw a
post about it in the Ubuntu-Mate forums.

I wonder how many others just shrugged and assumed this was working as
intended?

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

Title:
  Buggish interface @ workstation panels previews when using dual
  portrait

Status in MATE Desktop:
  New
Status in Ubuntu MATE:
  Confirmed
Status in libwnck3 package in Ubuntu:
  Confirmed
Status in mate-panel package in Ubuntu:
  Confirmed

Bug description:
  ...Freshly upgraded to 21.10 using the same OS that I used to open
  most of my previous video glitches ever...

  Using 2x monitor in portrait mode, the preview panel/widget(?) located
  at the bottom right side shows 2 things wrong:

  1. The "Workspace 1" preview is very elongated when compared to not only all 
of it's previous incarnations (from 14.04 to 21.10) but also has an 
inconsistent size when compared to it's neighbouring "Workspace 2". 
Expectation: both 1 and 2 should be sized identically.
  2. When hovering the mouse cursor on "Workspace 2" only it's left portion 
will highlight.
  Expectation: both monitors of "2" should highlight

  See enclosed picture.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mate-desktop/+bug/1947420/+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 1931602] Re: [apparmor] Segfault in logs with apparmor enabled

** Description changed:

  [Impact]
  
-  * With apparmor enabled (and usr.bin.firefox in enforce mode) there is
+  * With apparmor enabled (and usr.bin.firefox in enforce mode) there is
  a crash happening every time right after launching Firefox.
  
  [Test Plan]
  
-  * sudo aa-enforce /etc/apparmor.d/usr.bin.firefox
+  * sudo aa-enforce /etc/apparmor.d/usr.bin.firefox
  
-  * launch Firefox
+  * launch Firefox
  
-  * See a similar segfault reported in the syslog:
+  * See a similar segfault reported in the syslog:
  Jun 10 17:25:40 ubuntu kernel: [   86.775837] firefox[1765]: segfault at 0 ip 
7f724dd06384 sp 7fffa7aec450 error 6 in libxul.so[7f724a483000+53b2000]
  Jun 10 17:25:40 ubuntu kernel: [   86.775843] Code: 00 0f 1f 44 00 00 50 80 
3d f8 56 4c 04 00 74 02 58 c3 c6 05 ed 56 4c 04 01 48 8d 05 24 2c fa 02 48 8b 
0d 77 f0 3a 04 48 89 01  04 25 00 00 00 00 8d 01 00 00 e8 74 63 78 fc 66 2e 
0f 1f 84 00
  
  [Where problems could occur]
  
+ The fix adds additional paths to firefox apparmor profile (e.g. affecting 
/sys/devices/pci* and RealtimeKit1). When using deb version of firefox the 
browser may chose a different code path to execute than before, so it may 
affect hw acceleration (the sysfs paths were used by libxul) and audio.
+ Maybe rendering artifacts and audio sync issues in videos.
+ 
  [Other Info]

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

Title:
  [apparmor] Segfault in logs with apparmor enabled

Status in firefox package in Ubuntu:
  Confirmed
Status in firefox source package in Focal:
  Confirmed
Status in firefox source package in Hirsute:
  New
Status in firefox source package in Impish:
  New

Bug description:
  [Impact]

   * With apparmor enabled (and usr.bin.firefox in enforce mode) there
  is a crash happening every time right after launching Firefox.

  [Test Plan]

   * sudo aa-enforce /etc/apparmor.d/usr.bin.firefox

   * launch Firefox

   * See a similar segfault reported in the syslog:
  Jun 10 17:25:40 ubuntu kernel: [   86.775837] firefox[1765]: segfault at 0 ip 
7f724dd06384 sp 7fffa7aec450 error 6 in libxul.so[7f724a483000+53b2000]
  Jun 10 17:25:40 ubuntu kernel: [   86.775843] Code: 00 0f 1f 44 00 00 50 80 
3d f8 56 4c 04 00 74 02 58 c3 c6 05 ed 56 4c 04 01 48 8d 05 24 2c fa 02 48 8b 
0d 77 f0 3a 04 48 89 01  04 25 00 00 00 00 8d 01 00 00 e8 74 63 78 fc 66 2e 
0f 1f 84 00

  [Where problems could occur]

  The fix adds additional paths to firefox apparmor profile (e.g. affecting 
/sys/devices/pci* and RealtimeKit1). When using deb version of firefox the 
browser may chose a different code path to execute than before, so it may 
affect hw acceleration (the sysfs paths were used by libxul) and audio.
  Maybe rendering artifacts and audio sync issues in videos.

  [Other Info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931602/+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 1945774] Re: openssl: breaks ssl-cert installation: 8022CB35777F0000:error:1200007A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Fil

2021-11-09 Thread Lucas Kanashiro

According to the Debian bug, ssl-cert/1.1.1 contains the fix and it is
already available in jammy (release pocket), so I am marking this as fix
released.

** Changed in: ssl-cert (Ubuntu)
   Status: New => Fix Released

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

Title:
  openssl: breaks ssl-cert installation:
  8022CB35777F:error:127A:random number
  generator:RAND_write_file:Not a regular
  file:../crypto/rand/randfile.c:190:Filename=/dev/urandom

Status in hplip package in Ubuntu:
  New
Status in ssl-cert package in Ubuntu:
  Fix Released
Status in ssl-cert package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/990228:

  Package: openssl
  Version: 3.0.0~~alpha16-1
  Severity: serious
  User: debian...@lists.debian.org
  Usertags: piuparts

  Hi,

  during a test with piuparts I noticed your package causes other package
  to fail installation/upgrading.

  From the attached log (scroll to the bottom...):

  ...
Setting up openssl (3.0.0~~alpha16-1) ...
Setting up libbsd0:amd64 (0.11.3-1) ...
Setting up readline-common (8.1-2) ...
Setting up libxml2:amd64 (2.9.10+dfsg-6.7) ...
Setting up libgdbm6:amd64 (1.19-2) ...
Setting up postgresql-client-common (226) ...
Setting up libedit2:amd64 (3.1-20210522-1~exp1) ...
Setting up libreadline8:amd64 (8.1-2) ...
Setting up libldap-2.4-2:amd64 (2.4.57+dfsg-3) ...
Setting up libllvm11:amd64 (1:11.0.1-2) ...
Setting up ssl-cert (1.1.0+nmu1) ...
Could not create certificate. Openssl output was:
Generating a RSA private key

..+..+..+...+.+...+.+...+...+..+...+.+..+...+.+...+...+..+.+.+...+...+.+..++..+..+*.+*..+..++...+.+..+...++..+.++..++...++..+.+...+..+...+...+.+..+...+.++.+++.+..+.+.+..+..+.+...+.+.+.++.+.+.++++...+

..+.++...+...+...+..+..+.+...+.++...+.+..+..+..+*+...++..+...+..+...+..+.+..+*+..+...++..++..++.+..+...++.+.+..+.+.+..+.+..+..+..+.+++.++..+...+.+...+...+...+...+..++...+..+.+
Writing new private key to '/etc/ssl/private/ssl-cert-snakeoil.key'
-
Warning: No -copy_extensions given; ignoring any extensions in the request
Cannot write random bytes:
8022CB35777F:error:127A:random number generator:RAND_write_file:Not 
a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom
dpkg: error processing package ssl-cert (--configure):
 installed ssl-cert package post-installation script subprocess returned 
error exit status 1
dpkg: dependency problems prevent configuration of postgresql-common:
 postgresql-common depends on ssl-cert (>= 1.0.11); however:
  Package ssl-cert is not configured yet.
  ...

  Hmm, well, yes, /dev/urandom is not a regular file. It's a character
  device node.

  
  cheers,

  Andreas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1945774/+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 1945852] Re: [Dell Vostro 3500] sound strange noise - pulseaudio

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

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

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

Title:
  [Dell Vostro 3500] sound strange noise - pulseaudio

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The sound from the speakers and headphones is distorted when the
  system startup. Has some strange disturbance in sound. If I issue
  "pulseausio -k; pulseaudio --start" the sound is correct but when
  another startup problem is come back. Reinstalling pulseaudio and alsa
  does not help. Actually my pulseaudio version is
  1:13.99.1-1ubuntu3.11. I try under ubuntu 20.04.3 LTS and 21.04 but it
  is the same bug. Installing another newer kernel doesn't help either.
  The card is HDA Intel PCH, Cirrus Logic CS8409 / CS42L42 chip (Dell
  Vostro 3500).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bartek 3166 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  2 09:02:58 2021
  InstallationDate: Installed on 2021-10-02 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0GGCMJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3500:pvr:sku0A24:rvnDellInc.:rn0GGCMJ:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3500
  dmi.product.sku: 0A24
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1945852/+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 1931603] Re: [apparmor] Unable to show Downloads with apparmor enabled

** Also affects: firefox (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: firefox (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

Title:
  [apparmor] Unable to show Downloads with apparmor enabled

Status in firefox package in Ubuntu:
  New
Status in firefox source package in Focal:
  New
Status in firefox source package in Hirsute:
  New
Status in firefox source package in Impish:
  New

Bug description:
  Impact]

   * After a finished download (or opening the downloads list) it is
  impossible to "Open Containing Folder" for a downloaded file -
  pressing the button does nothing visible.

  [Test Plan]

   * sudo aa-enforce /etc/apparmor.d/usr.bin.firefox

   * launch Firefox

   * Download a file.

   * Go to downloads list.

   * Press the "Open Containing Folder" button next to the downloaded
  file on the list.

  [Where problems could occur]

  [Other Info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931603/+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 1931602] Re: [apparmor] Segfault in logs with apparmor enabled

** Also affects: firefox (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: firefox (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

Title:
  [apparmor] Segfault in logs with apparmor enabled

Status in firefox package in Ubuntu:
  Confirmed
Status in firefox source package in Focal:
  Confirmed
Status in firefox source package in Hirsute:
  New
Status in firefox source package in Impish:
  New

Bug description:
  [Impact]

   * With apparmor enabled (and usr.bin.firefox in enforce mode) there
  is a crash happening every time right after launching Firefox.

  [Test Plan]

   * sudo aa-enforce /etc/apparmor.d/usr.bin.firefox

   * launch Firefox

   * See a similar segfault reported in the syslog:
  Jun 10 17:25:40 ubuntu kernel: [   86.775837] firefox[1765]: segfault at 0 ip 
7f724dd06384 sp 7fffa7aec450 error 6 in libxul.so[7f724a483000+53b2000]
  Jun 10 17:25:40 ubuntu kernel: [   86.775843] Code: 00 0f 1f 44 00 00 50 80 
3d f8 56 4c 04 00 74 02 58 c3 c6 05 ed 56 4c 04 01 48 8d 05 24 2c fa 02 48 8b 
0d 77 f0 3a 04 48 89 01  04 25 00 00 00 00 8d 01 00 00 e8 74 63 78 fc 66 2e 
0f 1f 84 00

  [Where problems could occur]

  [Other Info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931602/+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 1945852] Re: [Dell Vostro 3500] sound strange noise - pulseaudio

2021-11-09 Thread Kamran Hossain

Can anyone tell me when it will be fixed? Or what is the alternative? It
is really annoying strange sound.

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

Title:
  [Dell Vostro 3500] sound strange noise - pulseaudio

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The sound from the speakers and headphones is distorted when the
  system startup. Has some strange disturbance in sound. If I issue
  "pulseausio -k; pulseaudio --start" the sound is correct but when
  another startup problem is come back. Reinstalling pulseaudio and alsa
  does not help. Actually my pulseaudio version is
  1:13.99.1-1ubuntu3.11. I try under ubuntu 20.04.3 LTS and 21.04 but it
  is the same bug. Installing another newer kernel doesn't help either.
  The card is HDA Intel PCH, Cirrus Logic CS8409 / CS42L42 chip (Dell
  Vostro 3500).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bartek 3166 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  2 09:02:58 2021
  InstallationDate: Installed on 2021-10-02 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0GGCMJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3500:pvr:sku0A24:rvnDellInc.:rn0GGCMJ:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3500
  dmi.product.sku: 0A24
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1945852/+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 1950330] [NEW] Grub doesn’t fully revert Zsys snapshots

2021-11-09 Thread Maurice Volaski

Public bug reported:

To reproduce this bug, take the following steps

Install Ubuntu 20.04.3 using a ZFS-based root.
Boot into it and get past the initial startup screens.

Install a package like htop to force the creation of a ZSys snapshot and
for additional confirmation in the user space, create a file on the
desktop.

You should see the file and htop should be able to run.

Reboot and hit escape to enter the grub screen. Choose the history menu
and choose the snapshot you just created. Then hit enter and then choose
the option to revert system and user data and then enter again.

Most of the time, this will work fine, but not absolutely *every* time.
Every so often, the system will hang after the last step (forcing you to
hard reboot), and the snapshots may or may not have been reverted.

One thing I noticed while doing this on a fresh install is that other
part of the system (the upgrade software) creates its own snapshots.
It's not clear if these have to be there to trip the system up into not
reverting. I think I reproduced once without them.

Note this is different from bug
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1949490, which
applies to ordinarily created snapshots.

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

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

Title:
  Grub doesn’t fully revert Zsys snapshots

Status in zsys package in Ubuntu:
  New

Bug description:
  To reproduce this bug, take the following steps

  Install Ubuntu 20.04.3 using a ZFS-based root.
  Boot into it and get past the initial startup screens.

  Install a package like htop to force the creation of a ZSys snapshot
  and for additional confirmation in the user space, create a file on
  the desktop.

  You should see the file and htop should be able to run.

  Reboot and hit escape to enter the grub screen. Choose the history
  menu and choose the snapshot you just created. Then hit enter and then
  choose the option to revert system and user data and then enter again.

  Most of the time, this will work fine, but not absolutely *every*
  time. Every so often, the system will hang after the last step
  (forcing you to hard reboot), and the snapshots may or may not have
  been reverted.

  One thing I noticed while doing this on a fresh install is that other
  part of the system (the upgrade software) creates its own snapshots.
  It's not clear if these have to be there to trip the system up into
  not reverting. I think I reproduced once without them.

  Note this is different from bug
  https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1949490, which
  applies to ordinarily created snapshots.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1950330/+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 1950328] [NEW] Idk

2021-11-09 Thread NasserAlqeifi

Public bug reported:

idk

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148
Uname: Linux 5.4.0-90-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.82.00  Thu Oct 14 10:24:40 
UTC 2021
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Nov  9 15:16:26 2021
DistUpgraded: 2021-11-09 13:33:35,359 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 8192cu, 1.11, 4.15.0-162-generic, x86_64: installed
 8192cu, 1.11, 5.4.0-90-generic, x86_64: installed
 nvidia, 470.82.00, 5.4.0-90-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation Device [10de:2560] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3a81]
InstallationDate: Installed on 2021-10-15 (25 days ago)
InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806)
MachineType: LENOVO 82JY
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-90-generic 
root=UUID=5064de25-8da0-4064-b74c-d45d2c8a30d4 ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2021-11-09 (0 days ago)
dmi.bios.date: 04/21/2021
dmi.bios.vendor: LENOVO
dmi.bios.version: GKCN36WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion 5 17ACH6H
dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN36WW:bd04/21/2021:svnLENOVO:pn82JY:pvrLegion517ACH6H:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegion517ACH6H:
dmi.product.family: Legion 5 17ACH6H
dmi.product.name: 82JY
dmi.product.sku: LENOVO_MT_82JY_BU_idea_FM_Legion 5 17ACH6H
dmi.product.version: Legion 5 17ACH6H
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.105-3~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Tue Nov  9 15:15:33 2021
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.20.11-1ubuntu1~20.04.2

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Idk

Status in xorg package in Ubuntu:
  New

Bug description:
  idk

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148
  Uname: Linux 5.4.0-90-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.82.00  Thu Oct 14 
10:24:40 UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Nov  9 15:16:26 2021
  DistUpgraded: 2021-11-09 13:33:35,359 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: focal
  DistroVariant:

[Desktop-packages] [Bug 1950092] Re: firefox: all bookmarks lost after snap upgrade to 701

2021-11-09 Thread Heinrich Schuchardt

What do mean you by "import existing profile from the deb"? This was an
update from snap to snap that failed.

I have deleted the old snap and changed profile.ini to point to my old
profile to solve my problem locally.

But you should still check why the snap to snap update fails.

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

Title:
  firefox: all bookmarks lost after snap upgrade to 701

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Today Firefox was updated to snap version 701. After that:

  * the toolbar settings are lost
  * all bookmarks are lost

  In my home directory I find:

  .mozilla/firefox/iw40rvsn.default-release-1
  .mozilla/firefox/yr14p2lb.default
  .mozilla/firefox/k2x43jhu.default-release
  .mozilla/firefox/53wtq3js.default-release-2

  Why would the snap create a new profile?

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1950092/+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 1860877] Re: No way to edit online account settings after creation

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

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Confirmed

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

Title:
  No way to edit online account settings after creation

Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  I set up a nextcloud account in the "online accounts" section of the ubuntu 
settings.
  https://help.ubuntu.com/stable/ubuntu-help/accounts.html.en

  However, there appears to be no way to edit the settings afterwards,
  for instance to change the password.

  Both in the settings and the documentation this option is completely
  missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1860877/+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 1950316] [NEW] desktop UI unresponsive

2021-11-09 Thread pleabargain

Public bug reported:

mouse works
keyboard doesn't

video
https://youtu.be/QWsrYBxu8hk

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  9 14:35:45 2021
DistUpgraded: 2021-10-19 08:03:15,745 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: impish
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:84ca]
InstallationDate: Installed on 2015-08-23 (2269 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=155c3c3c-daa6-414c-ac3d-0f8c492592c0 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to impish on 2021-10-19 (21 days ago)
dmi.bios.date: 07/21/2014
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-V LX
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.:bvr2501:bd07/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
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=1
mtime.conffile..etc.default.apport: 2021-11-09T14:33:49.606944
version.compiz: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1
version.libdrm2: libdrm2 2.4.107-8ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1
xserver.bootTime: Mon Aug 20 17:24:57 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: amd64 apport-bug impish 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/1950316

Title:
  desktop UI unresponsive

Status in xorg package in Ubuntu:
  New

Bug description:
  mouse works
  keyboard doesn't

  video
  https://youtu.be/QWsrYBxu8hk

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  9 14:35:45 2021
  DistUpgraded: 2021-10-19 08:03:15,745 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: impish
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:84ca]
  InstallationDate: Installed on 2015-08-23 (2269 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=155c3c3c-daa6-414c-ac3d-0f8c492592c0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to impish on 2021-10-19 (21 days ago)
  dmi.bios.date: 07/21/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.

[Desktop-packages] [Bug 1947746] Re: [Snap] Ubuntu Firefox installed from snap cannot use Trezor U2F

Thanks for the feedback mcudev, and sorry for not following up earlier
Aditya.

I've submitted https://github.com/snapcore/snapd/pull/11031, which
should enable Trezor keys for all snaps connecting to the u2f-devices
plug.

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

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

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

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

Title:
  [Snap] Ubuntu Firefox installed from snap cannot use Trezor U2F

Status in firefox package in Ubuntu:
  In Progress

Bug description:
  Trezor U2F security key doesn't work with firefox snap after updating
  to Ubuntu 21.10, but works with apt debian firefox package.

  Steps to reproduce:
  1) Insert Trezor U2F security key in USB port.
  2) Launch `run snap firefox` (it is the default on Ubuntu 21.10)
  3) Test https://demo.yubico.com/webauthn-technical/registration

  It works well on Ubuntu 21.04 and on traditional apt debian
  installation.

  
  $ snap list firefox
  Name Version  Rev  Tracking   Publisher  Notes
  firefox  93.0-1   631  latest/stable  mozilla✓   -

  
  $ snap connections firefox
  Interface PlugSlot
 Notes
  audio-playbackfirefox:audio-playback  :audio-playback 
 -
  audio-record  firefox:audio-record:audio-record   
 -
  avahi-observe firefox:avahi-observe   :avahi-observe  
 -
  browser-support   firefox:browser-sandbox :browser-support
 -
  camerafirefox:camera  :camera 
 -
  content[gnome-3-38-2004]  firefox:gnome-3-38-2004 
gnome-3-38-2004:gnome-3-38-2004  -
  content[gtk-3-themes] firefox:gtk-3-themes
gtk-common-themes:gtk-3-themes   -
  content[icon-themes]  firefox:icon-themes 
gtk-common-themes:icon-themes-
  content[sound-themes] firefox:sound-themes
gtk-common-themes:sound-themes   -
  cups-control  firefox:cups-control:cups-control   
 -
  dbus  -   firefox:dbus-daemon 
 -
  desktop   firefox:desktop :desktop
 -
  desktop-legacyfirefox:desktop-legacy  :desktop-legacy 
 -
  gsettings firefox:gsettings   :gsettings  
 -
  hardware-observe  firefox:hardware-observe:hardware-observe   
 -
  home  firefox:home:home   
 -
  joystick  firefox:joystick-   
 -
  mpris -   firefox:mpris   
 -
  network   firefox:network :network
 -
  network-observe   firefox:network-observe -   
 -
  openglfirefox:opengl  :opengl 
 -
  personal-filesfirefox:dot-mozilla-firefox :personal-files 
 -
  removable-media   firefox:removable-media :removable-media
 -
  screen-inhibit-controlfirefox:screen-inhibit-control  
:screen-inhibit-control  -
  system-files  firefox:etc-firefox-policies:system-files   
 -
  system-packages-doc   firefox:system-packages-doc 
:system-packages-doc -
  u2f-devices   firefox:u2f-devices :u2f-devices
 -
  unity7firefox:unity7  :unity7 
 -
  upower-observefirefox:upower-observe  :upower-observe 
 -
  wayland   firefox:wayland :wayland
 -
  x11   firefox:x11 :x11
 -

  
  $ cat /etc/os-release 
  PRETTY_NAME="Ubuntu 21.10"
  NAME="Ubuntu"
  VERSION_ID="21.10"
  VERSION="21.10 (Impish Indri)"
  VERSION_CODENAME=impish
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  UBUNTU_CODENAME=impish

  
  $ echo $XDG_SESSION_TYPE
  wayland

  
  $ uname -r
  5.13.0-19-generic

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1950092] Re: firefox: all bookmarks lost after snap upgrade to 701

When run for the first time, the snap should import existing profiles
from the deb.

Can you share the output of `snap connections firefox`?

Can you also run `rm -rf ~/snap/firefox/common/.mozilla` and then run
`snap run firefox` in a terminal and share the output here?

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

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

Title:
  firefox: all bookmarks lost after snap upgrade to 701

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Today Firefox was updated to snap version 701. After that:

  * the toolbar settings are lost
  * all bookmarks are lost

  In my home directory I find:

  .mozilla/firefox/iw40rvsn.default-release-1
  .mozilla/firefox/yr14p2lb.default
  .mozilla/firefox/k2x43jhu.default-release
  .mozilla/firefox/53wtq3js.default-release-2

  Why would the snap create a new profile?

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1950092/+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 1917152] Re: File moved with Cut-Paste from a search filter still appears on original screen and if deleted disappears from new folder

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

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

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

Title:
  File moved with Cut-Paste from a search filter still appears on
  original screen and if deleted disappears from new folder

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  Confirmed
Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  Affected version
  Nautilus 3.38 on Ubuntu 20.10 (but I also saw this bug some months and 
versions ago)

  I don't know if it's a specific Ubuntu bug or an upstream one, I reported it 
1.5 month ago on Gitlab Gnome without any answer nor review:
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/1723

  Resume: File moved with "Cut" from a window with an active search
  filter, and pasted in another folder on a second Nautilus window (not
  a subfolder), still appears on the first original screen (list is not
  automatically updated) - and if deleted from here, actually they
  disappear from the new folder !

  It can occur to loose important documents  - I often make direct
  shift-deletes, without recycler storage...

  Steps to reproduce
  I open a Nautilus window, go to a folder and make a search filter, for 
example 20 files appear on the window which name contains my search filter.

  If I select one of them, make Cut / Ctrl-X, open a new Nautilus
  window, go to another folder (which is not a subfolder of the first)
  and make Paste / Ctrl-V, it wells copy the file in the new folder.

  If I switch to the first Nautilus window with the original folder and
  search filter active, the moved file still appears on the list and I
  can open it. I think I've made an error (Ctrl-C instead of Ctrl-X) so
  I shift-delete it, it disappears from the list and only 19 files
  remain.

  Current behavior
  But… If I go to the second Nautilus window and the 2nd folder, the file has 
also disappeared from it ! File in the first window was "transformed" to a link 
instead of being removed, and suppressing it also deletes the file in its new 
folder - in my case, I lost several documents like this because of Shift-Delete 
and not trash use.

  Expected behavior
  After Cut - Paste, in the case of 2 Nautilus windows are opened, the file(s) 
moved from the first one should not be still visible in the search list, there 
should be an automatic refresh.

  If I do a Copy-Paste instead of a Cut-Paste, problem does not occur:
  delete only removes file in the fist original folder, not on the
  second. If I close the search filter, it's also OK, file(s) moved no
  more visible. And of course, if after Cut I stay in the same Nautilus
  window and go to another folder to paste, no problem: bug only occurs
  in case of a second window opened.

  Thanks in advance and best regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1917152/+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 1917152] Re: File moved with Cut-Paste from a search filter still appears on original screen and if deleted disappears from new folder

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

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

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

Title:
  File moved with Cut-Paste from a search filter still appears on
  original screen and if deleted disappears from new folder

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  Confirmed
Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  Affected version
  Nautilus 3.38 on Ubuntu 20.10 (but I also saw this bug some months and 
versions ago)

  I don't know if it's a specific Ubuntu bug or an upstream one, I reported it 
1.5 month ago on Gitlab Gnome without any answer nor review:
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/1723

  Resume: File moved with "Cut" from a window with an active search
  filter, and pasted in another folder on a second Nautilus window (not
  a subfolder), still appears on the first original screen (list is not
  automatically updated) - and if deleted from here, actually they
  disappear from the new folder !

  It can occur to loose important documents  - I often make direct
  shift-deletes, without recycler storage...

  Steps to reproduce
  I open a Nautilus window, go to a folder and make a search filter, for 
example 20 files appear on the window which name contains my search filter.

  If I select one of them, make Cut / Ctrl-X, open a new Nautilus
  window, go to another folder (which is not a subfolder of the first)
  and make Paste / Ctrl-V, it wells copy the file in the new folder.

  If I switch to the first Nautilus window with the original folder and
  search filter active, the moved file still appears on the list and I
  can open it. I think I've made an error (Ctrl-C instead of Ctrl-X) so
  I shift-delete it, it disappears from the list and only 19 files
  remain.

  Current behavior
  But… If I go to the second Nautilus window and the 2nd folder, the file has 
also disappeared from it ! File in the first window was "transformed" to a link 
instead of being removed, and suppressing it also deletes the file in its new 
folder - in my case, I lost several documents like this because of Shift-Delete 
and not trash use.

  Expected behavior
  After Cut - Paste, in the case of 2 Nautilus windows are opened, the file(s) 
moved from the first one should not be still visible in the search list, there 
should be an automatic refresh.

  If I do a Copy-Paste instead of a Cut-Paste, problem does not occur:
  delete only removes file in the fist original folder, not on the
  second. If I close the search filter, it's also OK, file(s) moved no
  more visible. And of course, if after Cut I stay in the same Nautilus
  window and go to another folder to paste, no problem: bug only occurs
  in case of a second window opened.

  Thanks in advance and best regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1917152/+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 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.

2021-11-09 Thread Yuan-Chen Cheng

I try to install impish and hirsute on the target machine, with the
kernel from focal (so that it support the new ADL GPU, and then the
monitor can be turned off so that the touchscreen will be detached,
that's the way we reproduce this issue in focal)

With that, with or without mutter from the proposed channel, I can't
reproduce this issue. (We do see the backlight turned off and the
touchscreen detached from kernel message.)

Given this is a timing-sensitive issue, I think as long as there is no
regression, then we can call that as verified done.

I've dog food those, and can't find regression so far. So I'll tag
verify done.

** Tags removed: verification-needed verification-needed-hirsute 
verification-needed-impish
** Tags added: verification-done verification-done-hirsute 
verification-done-impish

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

Title:
  Xwayland crash in gdm as screen off and touchscreen detach.

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  Fix Committed
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Hirsute:
  Fix Committed
Status in mutter source package in Impish:
  Fix Committed

Bug description:
  [Impact]

   * Gdm crashed and user need to be an expert to know how to work around,
     or need to reboot to fix.

   * OEM projects got certain SKU that can reliably reproduce this
  issue.

   * A merged patch in upstream fix the race condition.

  [Test Plan]

   * Use the SKU that can reliably reproduce this issue.
   * Do a cold boot, and wait for 5 mins. The monitor should turned-black
     but showing the Machine Vendor logo that was previously
     displayed by plymouth.
   * Try to dog-food the deb from the proposed channel and make sure
     all input events still properly propagate.

  [Where problems could occur]

   * If the patch is not properly working as expected, per the file this
     patch touch, the user desktop session could stop responding to
     mouse, keyboard, and touch screen input.

  [Other Info]

   * Can't think of any for now.

  

  This is a reproducible issue. Step to reproduce
  1. cold boot into gdm login screen.
  2. wait for 5 mins, and the screen will be turned off. (also observed that 
the touchscreen USB device drop of a USB bus on the target machine)

  Note: this bug seems to be timing sensitive. I got an OEM project
  machine that can reproduce this issue (reproducible on several
  machines with the same HW design). The machine is using ADL CPU, which
  needs a patched 5.14 kernel. So I can't reproduce this on impish. With
  the backported mutter, I verified an upstream patch seems to fix this
  issue.

  Expected result:
  The screen just turns black.

  Actual result:
  Saw Vendor boot logo on the monitor (previous draw by plymouth during booting)

  Analysis as it happens:
  1. Saw "LGDisplay Incell Touch" drop off the USB bus.
     Kernel message like: "usb 1-9: USB disconnect, device number 6"
     as the screen turned black.
  2. There is no switch on virtual tty.
  3. journal log from Xwayland "wl_display@1: error 0: invalid object 24"
  4. Xwayland and gnome-shell process both die as this happens.
  5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and
     gnome-shell stop there for 30 more seconds.
  6. backtrace as Xwayland crashed:

  ```
  #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6
  #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6
  #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351
  #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872
  #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at 
../../../../os/log.c:1010
  #5 0x56437429c8b0 in xwl_log_handler (format=, 
args=) at ../../../../../hw/xwayland/xwayland.c:1312
  #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error 
%d: %s\n") at ../src/wayland-util.c:404
  #7 0x7f447c3cb78b in display_handle_error (data=, 
display=0x56437639f000, object=0x56437639f000, code=0, message=)
  at ../src/wayland-client.c:911
  #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7
  #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7
  #10 0x7f447c3cf3a8 in wl_closure_invoke 
(closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=,
  target@entry=0x56437639f000, opcode=opcode@entry=0, data=) 
at ../src/connection.c:1018
  #11 0x7f447c3cbc48 in dispatch_event 
(display=display@entry=0x56437639f000, queue=) at 
../src/wayland-client.c:1445
  #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, 
display=0x56437639f000) at ../src/wayland-client.c:1584
  #13 wl_display_dispatch_queue_pending (display=0x56437639f000, 
queue=0x56437639f0d0) at

[Desktop-packages] [Bug 1917152] Re: File moved with Cut-Paste from a search filter still appears on original screen and if deleted disappears from new folder

2021-11-09 Thread nany

Hello,


I have the same issue in Ubuntu 20.04 (Nautilus 3.36.3), Ubuntu 21.10 (Nautilus 
40.2) and Ubuntu 22.04 (currently Nautilus 40.2 also).

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

Title:
  File moved with Cut-Paste from a search filter still appears on
  original screen and if deleted disappears from new folder

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  New
Status in tracker package in Ubuntu:
  New

Bug description:
  Affected version
  Nautilus 3.38 on Ubuntu 20.10 (but I also saw this bug some months and 
versions ago)

  I don't know if it's a specific Ubuntu bug or an upstream one, I reported it 
1.5 month ago on Gitlab Gnome without any answer nor review:
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/1723

  Resume: File moved with "Cut" from a window with an active search
  filter, and pasted in another folder on a second Nautilus window (not
  a subfolder), still appears on the first original screen (list is not
  automatically updated) - and if deleted from here, actually they
  disappear from the new folder !

  It can occur to loose important documents  - I often make direct
  shift-deletes, without recycler storage...

  Steps to reproduce
  I open a Nautilus window, go to a folder and make a search filter, for 
example 20 files appear on the window which name contains my search filter.

  If I select one of them, make Cut / Ctrl-X, open a new Nautilus
  window, go to another folder (which is not a subfolder of the first)
  and make Paste / Ctrl-V, it wells copy the file in the new folder.

  If I switch to the first Nautilus window with the original folder and
  search filter active, the moved file still appears on the list and I
  can open it. I think I've made an error (Ctrl-C instead of Ctrl-X) so
  I shift-delete it, it disappears from the list and only 19 files
  remain.

  Current behavior
  But… If I go to the second Nautilus window and the 2nd folder, the file has 
also disappeared from it ! File in the first window was "transformed" to a link 
instead of being removed, and suppressing it also deletes the file in its new 
folder - in my case, I lost several documents like this because of Shift-Delete 
and not trash use.

  Expected behavior
  After Cut - Paste, in the case of 2 Nautilus windows are opened, the file(s) 
moved from the first one should not be still visible in the search list, there 
should be an automatic refresh.

  If I do a Copy-Paste instead of a Cut-Paste, problem does not occur:
  delete only removes file in the fist original folder, not on the
  second. If I close the search filter, it's also OK, file(s) moved no
  more visible. And of course, if after Cut I stay in the same Nautilus
  window and go to another folder to paste, no problem: bug only occurs
  in case of a second window opened.

  Thanks in advance and best regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1917152/+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 1950040] Re: Wayland Screensharing broken in Ubuntu 21.10

Note that firefox 94.0 is now in the stable channel, so there is no need
to switch to the candidate channel to get the update.

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

Title:
  Wayland Screensharing broken in Ubuntu 21.10

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in pipewire package in Ubuntu:
  Invalid
Status in xdg-desktop-portal package in Ubuntu:
  Invalid

Bug description:
  Freshly installed Ubuntu 21.10, screen sharing does not work with any
  browser, tested the following options:

  - Firefox snap
  - Firefox deb
  - Chromium snap
  - Chromium flatpak

  Steps to reproduce:

  1. Go to 
https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/#7325517390736006
  2. Select to share the whole desktop in the xdg-desktop-portal
  3. Notice the orange screen share indicator in Gnome-Shell but actually 
nothing is shared in the browser.

  This should be handled high priority since this is a critical feature
  during the pandemic.

  Filed against ubuntu-meta since I don't know exactly which package to
  blame, whether it's pipewire, xdg-desktop portal or some problem
  directely with mutter / gnome-shell, please reassign accordingly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1950040/+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 1949605] Re: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS

Thanks Simon, I will comment here when there are packages ready for
wider testing. I have managed to successfully build thunderbird 91.3.0
for all supported architectures on hirsute, focal and bionic, but I want
to give it some basic testing before opening it up.

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

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

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

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

Title:
  Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS

Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Bionic:
  In Progress
Status in thunderbird source package in Focal:
  In Progress
Status in thunderbird source package in Hirsute:
  In Progress

Bug description:
  Similarly to bug #1895643, which was about upgrading thunderbird from
  68 to 78 in all supported Ubuntu releases, this bug is to track the
  update from thunderbird 78 to 91 in hirsute, focal and bionic.

  The rationale is that series 78 will soon be out of support (the last
  release, 78.14.0, was made public on September 7, 2021).

  Thunderbird follows the Firefox ESR release cycle, and the
  next/current series is 91 (already available in impish and jammy).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1949605/+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 1949605] Re: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS

2021-11-09 Thread Simon Iremonger

Both debian and ubuntu seem to have some sort of problem with Thunderbird not 
managing to build on all architectures, or so, in the latest versions in 
packages. databases.
I notice launchpad has built 91.3.0 packages for ubuntu jamil (presumably 
equivalent to debian sid or so)...
Do let us all know about any 'testing' packages ready to try out =).

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

Title:
  Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS

Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Bionic:
  Confirmed
Status in thunderbird source package in Focal:
  Confirmed
Status in thunderbird source package in Hirsute:
  Confirmed

Bug description:
  Similarly to bug #1895643, which was about upgrading thunderbird from
  68 to 78 in all supported Ubuntu releases, this bug is to track the
  update from thunderbird 78 to 91 in hirsute, focal and bionic.

  The rationale is that series 78 will soon be out of support (the last
  release, 78.14.0, was made public on September 7, 2021).

  Thunderbird follows the Firefox ESR release cycle, and the
  next/current series is 91 (already available in impish and jammy).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1949605/+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 1950040] Re: Wayland Screensharing broken in Ubuntu 21.10

Flatpaks are not part of Ubuntu so I'm not going to spend any time on
that.

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

Title:
  Wayland Screensharing broken in Ubuntu 21.10

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in pipewire package in Ubuntu:
  Invalid
Status in xdg-desktop-portal package in Ubuntu:
  Invalid

Bug description:
  Freshly installed Ubuntu 21.10, screen sharing does not work with any
  browser, tested the following options:

  - Firefox snap
  - Firefox deb
  - Chromium snap
  - Chromium flatpak

  Steps to reproduce:

  1. Go to 
https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/#7325517390736006
  2. Select to share the whole desktop in the xdg-desktop-portal
  3. Notice the orange screen share indicator in Gnome-Shell but actually 
nothing is shared in the browser.

  This should be handled high priority since this is a critical feature
  during the pandemic.

  Filed against ubuntu-meta since I don't know exactly which package to
  blame, whether it's pipewire, xdg-desktop portal or some problem
  directely with mutter / gnome-shell, please reassign accordingly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1950040/+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 1950040] Re: Wayland Screensharing broken in Ubuntu 21.10

2021-11-09 Thread Esokrates

Would you mind trying flatpaks? Those had working screensharing and do
not work anymore for me with 21.10.

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

Title:
  Wayland Screensharing broken in Ubuntu 21.10

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in pipewire package in Ubuntu:
  Invalid
Status in xdg-desktop-portal package in Ubuntu:
  Invalid

Bug description:
  Freshly installed Ubuntu 21.10, screen sharing does not work with any
  browser, tested the following options:

  - Firefox snap
  - Firefox deb
  - Chromium snap
  - Chromium flatpak

  Steps to reproduce:

  1. Go to 
https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/#7325517390736006
  2. Select to share the whole desktop in the xdg-desktop-portal
  3. Notice the orange screen share indicator in Gnome-Shell but actually 
nothing is shared in the browser.

  This should be handled high priority since this is a critical feature
  during the pandemic.

  Filed against ubuntu-meta since I don't know exactly which package to
  blame, whether it's pipewire, xdg-desktop portal or some problem
  directely with mutter / gnome-shell, please reassign accordingly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1950040/+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 1950040] Re: Wayland Screensharing broken in Ubuntu 21.10

If you had downgraded packages like in comment #2 then it's possible
"pipewire-media-session" might have been removed at the same time. But
that doesn't matter now. This appears to be a browser bug, fixed in
Firefox 94.

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

Title:
  Wayland Screensharing broken in Ubuntu 21.10

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in pipewire package in Ubuntu:
  Invalid
Status in xdg-desktop-portal package in Ubuntu:
  Invalid

Bug description:
  Freshly installed Ubuntu 21.10, screen sharing does not work with any
  browser, tested the following options:

  - Firefox snap
  - Firefox deb
  - Chromium snap
  - Chromium flatpak

  Steps to reproduce:

  1. Go to 
https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/#7325517390736006
  2. Select to share the whole desktop in the xdg-desktop-portal
  3. Notice the orange screen share indicator in Gnome-Shell but actually 
nothing is shared in the browser.

  This should be handled high priority since this is a critical feature
  during the pandemic.

  Filed against ubuntu-meta since I don't know exactly which package to
  blame, whether it's pipewire, xdg-desktop portal or some problem
  directely with mutter / gnome-shell, please reassign accordingly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1950040/+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 1950040] Re: Wayland Screensharing broken in Ubuntu 21.10