date:20201103

** Tags added: nvidia-corruption

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

Title:
  [nvidia] Background image corrupted after standby or resume from
  suspend

Status in mutter package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix
Status in mutter source package in Focal:
  Confirmed
Status in nvidia-graphics-drivers-340 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-390 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-435 source package in Focal:
  Won't Fix

Bug description:
  Looks similar to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407

  When the computer goes to standby, the background image becomes
  corrupted.

  I am able to fix by "killall Xorg" , change the background image
  (settings > background) and restart.  Haven't tried login logout.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  9 10:58:35 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed
   nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c]
  InstallationDate: Installed on 2019-11-29 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTek Computer Inc. G60JX
  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.3.0-24-generic 
root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G60JX
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.family: PEGA Family
  dmi.product.name: G60JX
  dmi.product.sku: 0
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTek Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+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 1901585] Re: [nvidia] Ubuntu 20.04 LTS Desktop Screen blinking/flickering black and side menu bar turn upsidedown

This sounds like another Nvidia issue related to:

https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

which mentions "VT switches", so that can include user switching.

There is no workaround right now, other than to avoid the Nvidia driver,
or to avoid user switching and suspend/resume etc :(

** Tags added: nvidia-corruption

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

Title:
  [nvidia] Ubuntu 20.04 LTS Desktop Screen blinking/flickering black and
  side menu bar turn upsidedown

Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  New

Bug description:
  Sometimes after I change the used account to the not pirivleged user account 
and clik to side menu bar the (Xorg/Gnome) screen randomly start turn black and 
back to normal while i move the mouse, somtimes just stay black but if there is 
an opened window (used to be nautilus or FireFox) and is move over the mause 
cursor over its is start partially show the right content.
  Paralelly the side menu turn upside down randomly.

  I never experienced this with root account and find that if I lock the
  screen and relese it is used to solve the problem for a while.

  The problem raised after upgrade Ubuntu from 18.04 LTS to 20.04 LTS

  The computer is a desktop so there no accelerometer giroscope.
  The screen is a 4K montior with 3840×2160 resolution and work on 29,97 Hz
  The graphics card is an ASUS NVIDIA GeForce GTX 1060 6GB

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Ez egy könyvtár: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Ez egy könyvtár: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ez egy könyvtár: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .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  450.80.02  Wed Sep 23 
01:13:39 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 26 18:13:01 2020
  DistUpgraded: 2020-10-07 15:58:42,341 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Nem sikerült a gyermekfolyamat 
(„./xorg_fix_proprietary.py”) végrehajtása (Nincs ilyen fájl vagy könyvtár) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-51-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106 [GeForce GTX 1060 6GB] [1043:85ab]
  InstallationDate: Installed on 2017-01-03 (1391 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=74c33349-7cf3-4ced-8462-62ad4c43832d ro quiet splash 
crashkernel=512M-:192M vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-10-07 (19 days ago)
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3504
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/29/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx: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
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2:

[Desktop-packages] [Bug 1894627] Re: [nvidia] Web browser distorted after hibernation/power save when idle

** Tags added: nvidia-corruption

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

Title:
  [nvidia] Web browser distorted after hibernation/power save when idle

Status in chromium-browser package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Won't Fix

Bug description:
  https://bugs.chromium.org/p/chromium/issues/detail?id=791913

  ---

  my laptop goes to hibernation/power saver mode when my computer is idle.
  every time I bring my computer back up, the screen distorted. I have to close 
all my browsers. Sometimes, shut down the computer.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  N: Unable to locate package pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  7 03:33:23 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.100, 5.4.0-42-generic, x86_64: installed
   nvidia, 440.100, 5.4.0-45-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
     Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:8466]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Ti Mobile] 
[103c:8466]
  InstallationDate: Installed on 2020-06-23 (75 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Camera
   Bus 001 Device 003: ID 8087:0aaa Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP OMEN by HP Laptop
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=98265a4d-5439-415e-b43c-904265a8559a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.09
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8466
  dmi.board.vendor: HP
  dmi.board.version: 68.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.09:bd04/24/2019:svnHP:pnOMENbyHPLaptop:pvr:rvnHP:rn8466:rvr68.21:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop
  dmi.product.sku: 4CC49UA#ABA
  dmi.sys.vendor: HP
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-06-26T00:47:21.524860
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1896167] Re: Heavy screen tearing in Wayland sessions on Raspberry Pi 4-B

I've read a suggestion this is fixed in later kernels like 5.9. Need to
test.

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

Title:
  Heavy screen tearing in Wayland sessions on Raspberry Pi 4-B

Status in linux-raspi package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Heavy screen tearing in Wayland sessions on Raspberry Pi 4-B.

  That's after working around bug 1896164.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1896167/+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 1870886] Re: Window scales to 200% after screen unlocked, on desktop with external monitor

2020-11-03 Thread Kai-Heng Feng

Ok, appears to be fixed in Hirsute.

There's a brief period that the 2x sized window "wiggles" to the correct
size.

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

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

Title:
  Window scales to 200% after screen unlocked, on desktop with external
  monitor

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  System setup:
  - 4K screen with 200% scale factor.
  - System up to date with focal-proposed.

  
  Reproduce steps:
  1. Idle or suspend the system.
  2. Wake up the system and unlock the screen.
  3. Window 200% sized.

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

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

[Desktop-packages] [Bug 1896171] Re: Wayland 3D apps appear corrupt on Raspberry Pi 4B (v3d driver)

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1520
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1520

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1520
   Importance: Unknown
   Status: Unknown

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

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

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

Title:
  Wayland 3D apps appear corrupt on Raspberry Pi 4B (v3d driver)

Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Wayland 3D apps appear corrupt on Raspberry Pi 4B (v3d driver).

  Seen in glmark2-wayland, glmark2-es2-wayland, weston-simple-egl.

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

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

[Desktop-packages] [Bug 1902825] Re: High CPU usage just moving the mouse

Also I am reminded of an issue that was fixed upstream recently... Do
you find the high CPU only comes *after* the lock screen has been used?
Does it happen on a fresh boot when no lock screen has ever been used?

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

Title:
  High CPU usage just moving the mouse

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  high cpu usage just moving the mouse

  removed appindicator extension .. the cpu load is very high.


  running strace -c -p  while moving mouse

  % time seconds  usecs/call callserrors syscall
  -- --- --- - - 
   36.740.103852 103  1000 8 futex
   31.300.088469   8 10366  8750 recvmsg
   15.530.043901  11  3925   poll
   10.100.028550  10  2776   write
4.330.012232   7  1537   writev
1.600.004533   4   932   read
0.390.001092   3   337   getpid
0.000.01   0 2   getrusage
0.000.01   1 1   restart_syscall
0.000.00   0 4   mprotect
  -- --- --- - - 
  100.000.282631 20880  8758 total

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Wed Nov  4 10:49:20 2020
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902825/+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 1902825] Re: High CPU usage just moving the mouse

Please:

* Run 'top' to confirm which process is using the most CPU.

* After the problem happens again run:

  lsusb > lsusb.txt
  lspci -kv > lspci.txt
  journalctl -b0 > journal.txt
  gsettings list-recursively org.gnome.shell > shellsettings.txt
  xrandr --verbose > xrandr.txt

  and attach the resulting text files here.


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

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

Title:
  High CPU usage just moving the mouse

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  high cpu usage just moving the mouse

  removed appindicator extension .. the cpu load is very high.


  running strace -c -p  while moving mouse

  % time seconds  usecs/call callserrors syscall
  -- --- --- - - 
   36.740.103852 103  1000 8 futex
   31.300.088469   8 10366  8750 recvmsg
   15.530.043901  11  3925   poll
   10.100.028550  10  2776   write
4.330.012232   7  1537   writev
1.600.004533   4   932   read
0.390.001092   3   337   getpid
0.000.01   0 2   getrusage
0.000.01   1 1   restart_syscall
0.000.00   0 4   mprotect
  -- --- --- - - 
  100.000.282631 20880  8758 total

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Wed Nov  4 10:49:20 2020
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902825/+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 1902825] [NEW] High CPU usage just moving the mouse

2020-11-03 Thread rahul

Public bug reported:

high cpu usage just moving the mouse

removed appindicator extension .. the cpu load is very high.


running strace -c -p  while moving mouse

% time seconds  usecs/call callserrors syscall
-- --- --- - - 
 36.740.103852 103  1000 8 futex
 31.300.088469   8 10366  8750 recvmsg
 15.530.043901  11  3925   poll
 10.100.028550  10  2776   write
  4.330.012232   7  1537   writev
  1.600.004533   4   932   read
  0.390.001092   3   337   getpid
  0.000.01   0 2   getrusage
  0.000.01   1 1   restart_syscall
  0.000.00   0 4   mprotect
-- --- --- - - 
100.000.282631 20880  8758 total

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
Uname: Linux 5.8.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME-Classic:GNOME
Date: Wed Nov  4 10:49:20 2020
DisplayManager: gdm3
RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy

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

Title:
  High CPU usage just moving the mouse

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  high cpu usage just moving the mouse

  removed appindicator extension .. the cpu load is very high.


  running strace -c -p  while moving mouse

  % time seconds  usecs/call callserrors syscall
  -- --- --- - - 
   36.740.103852 103  1000 8 futex
   31.300.088469   8 10366  8750 recvmsg
   15.530.043901  11  3925   poll
   10.100.028550  10  2776   write
4.330.012232   7  1537   writev
1.600.004533   4   932   read
0.390.001092   3   337   getpid
0.000.01   0 2   getrusage
0.000.01   1 1   restart_syscall
0.000.00   0 4   mprotect
  -- --- --- - - 
  100.000.282631 20880  8758 total

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Wed Nov  4 10:49:20 2020
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902825/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

2020-11-03 Thread Hui Wang

@smurf,

What is generated after building? If it is *.deb file, just need to run
'sudo dpkg -i *.deb; reboot'

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1902783] Re: Super key is not working

Actually regarding comment #2, your setting:

  b'org.gnome.mutter' b'overlay-key' b"''"

shows the Super key is disabled and not expected to work. So that makes
this bug invalid. To get it back, run:

  gsettings set org.gnome.mutter overlay-key 'Super_L'


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

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

Title:
  Super key is not working

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Ubuntu supper key is not working

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Wed Nov  4 00:55:53 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-22 (104 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902783/+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 1898325] Re: Gnome calendar is not syncing with Google calendar online account.

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

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

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

Title:
  Gnome calendar is not syncing with Google calendar online account.

Status in gnome-calendar package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 20.10 groovy (beta).

  The Gnome calendar is not syncing with Google calendar online account.

  In Ubuntu 20.04 (focal) there is no such problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-calendar 3.38.0-1
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  3 02:34:16 2020
  InstallationDate: Installed on 2020-10-03 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1898325/+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 1835654] Re: Extracting a zip archieve creates a new unwanted folder

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

** Changed in: file-roller (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Extracting a zip archieve creates a new unwanted folder

Status in file-roller package in Ubuntu:
  Expired

Bug description:
  version of the package file-roller: 3.32.1-1 on Ubuntu 19.04

  If I right click on the .zip file and choose "extract here" from the context 
menu, then the archieve content is extracted into a newly created folder, with 
the same name as the zip file.
  The expected behavior would be extracting the content into the folder where 
the archieve is located.

  Note this does NOT occur for tar.xz archieves, which are correctly
  extracted into the current folder instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1835654/+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 1864244] Re: Text selection in address bar does not work as expected

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

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Text selection in address bar does not work as expected

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  In Nautilus, I can click "Ctrl+L" to open the address bar. At this
  point, the whole address will be selected, which is desirable.
  However, if I then press "Right" to place my cursor at the end of the
  current path, and then try to use "Shift+Ctrl+Left" to select word-by-
  word (e.g., to select and delete the final folder from the path), the
  whole path is again selected. It seems that the logic for preselecting
  the whole path upon opening the address bar seems to trigger in more
  circumstances than just upon opening, and this makes using Nautilus
  via keyboard slower and more frictive than necessary. (In general,
  text entry widgets that override the operating system's existing
  conventions always really annoy me, on desktop or mobile.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.4-0~ubuntu18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18
  Uname: Linux 4.15.0-76-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 21 15:44:24 2020
  InstallationDate: Installed on 2018-12-17 (431 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LC_CTYPE=en_US.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: dropbox 2018.11.28

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1864244/+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 1848559] Re: i couldn't access into settings and tweaks, when i clicked to them, it was setup and about 5 seconds later, they're disappeared

[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/1848559

Title:
  i couldn't access into settings and tweaks, when i clicked to them, it
  was setup and about 5 seconds later, they're disappeared

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

Bug description:
  because i installed icons from gnome-look, after i choose it,
  everything like tweaks,settings, folder home,... they couldn't open

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 18 00:51:32 2019
  InstallationDate: Installed on 2019-08-19 (59 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  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/1848559/+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 1894160] Re: package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-k

[Expired for nvidia-graphics-drivers-340 (Ubuntu) because there has been
no activity for 60 days.]

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

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade:
  intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está
  también en el paquete nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1

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

Bug description:
  No puedo instalar el driver de la tarjeta grafica nvidia ge force 210
  Soy nuevo en esto

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Sep  3 18:42:36 2020
  ErrorMessage: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', 
que está también en el paquete nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1
  InstallationDate: Installed on 2020-08-31 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: 
intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también 
en el paquete nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1
  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/1894160/+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 1898905] Autopkgtest regression report (sane-backends/1.0.31-2ubuntu0.20.10)

2020-11-03 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted sane-backends (1.0.31-2ubuntu0.20.10) 
for groovy have finished running.
The following regressions have been reported in tests triggered by the package:

gscan2pdf/2.8.2-1ubuntu2 (arm64, armhf)


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

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

[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 sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1898905

Title:
  Unfunctional plustek scanner in Ubuntu 20.10

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Groovy:
  Fix Committed
Status in sane-backends package in Debian:
  Unknown

Bug description:
  * Impact

  The plustek driver isn't working in 20.10

  * Test case

  Try doing a copy of a document on a plustek based device

  * Regression potential

  The locking option was disabled until 20.10, the locking code relies
  on a lock directory to exist in /var/lock but that location is not
  persitant which means the locking can't work. Debian has turned the
  option off again, we are going the same in the SRU because it's safer
  than trying to fix an option that never got properly tested. There is
  special verification to do, just check that plustek and other devices
  are working correctly.

  -

  There are multiple reports now of failing plustek backend in libsane
  1.0.31-2 as shipped in Ubuntu 20.10 and Debian dev

  My report:
  https://gitlab.com/sane-project/backends/-/issues/363

  Another report:
  https://gitlab.com/sane-project/backends/-/issues/360

  Debian bug report:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971584

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1898905/+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 1902810] Re: Video Flicker

Next time the problem starts happening please run:

  journalctl -b0 > journal.txt

and attach the resulting text file here.

Separately, please also try selecting 'Ubuntu on Wayland' from the login
screen, just before you enter your password.

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

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

** Summary changed:

- Video Flicker
+ [i915] Video Flicker

** Summary changed:

- [i915] Video Flicker
+ [i915] Dell Latitude 5285 video flicker when an external monitor is connected

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

Title:
  [i915] Dell Latitude 5285 video flicker when an external monitor is
  connected

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  The display on this Dell Latitude 5285 with detachable keyboard
  flickers when an external monitor is connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-7625.26~1603389471~20.04~f6b125f-generic 
5.8.14
  Uname: Linux 5.8.0-7625-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Tue Nov  3 18:38:42 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:07a4]
  InstallationDate: Installed on 2020-07-01 (125 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 022: ID 044e:1218 Alps Electric Co., Ltd Alps Touchpad
   Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5285
  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.8.0-7625-generic 
root=UUID=f22e0756-4530-44bf-8da3-d0ed47ef183a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2020
  dmi.bios.release: 1.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 32
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd07/24/2020:br1.10:svnDellInc.:pnLatitude5285:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct32:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5285
  dmi.product.sku: 07A4
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1902810/+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 1902783] Re: Super key is not working

If the above command does not fix the problem then next please try
uninstalling these extensions:

'extension-shortc...@shs-schubert.de', 'transparenttop...@peclu.net',
'openweather-extens...@jenslody.de', 'systemMonitor@gnome-shell-
extensions.gcampax.github.com', 'drawonyourscr...@abakkk.framagit.org',
'applications-overview-tooltip@RaphaelRochet', 'apt-update-
indica...@franglais125.gmail.com', 'caffe...@patapon.info',
'gsconn...@andyholmes.github.io', 'drop-down-termina...@bigbn.pro',
'places-m...@gnome-shell-extensions.gcampax.github.com', 'screenshot-
window-si...@gnome-shell-extensions.gcampax.github.com',
'windowsnaviga...@gnome-shell-extensions.gcampax.github.com', 'apps-menu
@gnome-shell-extensions.gcampax.github.com', 'pomod...@arun.codito.in',
'amdtool...@zerosubnet.com', 'radeon-dpm-control@s3rius', 'freon@Veske',
'auto-move-wind...@gnome-shell-extensions.gcampax.github.com', 'custom-
hot-corn...@janrunx.gmail.com', 'extensi...@abteil.org', 'drive-menu
@gnome-shell-extensions.gcampax.github.com', 'system-
moni...@paradoxxx.zero.gmail.com'

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

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

Title:
  Super key is not working

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu supper key is not working

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Wed Nov  4 00:55:53 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-22 (104 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902783/+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 1902783] Re: Super key is not working

It looks like you have lost your overlay key setting. Please try this to
restore it:

gsettings set org.gnome.mutter overlay-key 'Super_L'

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

Title:
  Super key is not working

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu supper key is not working

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Wed Nov  4 00:55:53 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-22 (104 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902783/+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 1902766] Re: Automatic suspend when idle not working in 20.10

Please also try removing or turning off any Bluetooth or wireless
peripherals you may have.

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

Title:
  Automatic suspend when idle not working in 20.10

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have my laptop configured to suspend automatically after 20 minutes
  of idle time when on battery power. See screenshot attached showing
  these settings.

  This worked fine in 20.04. It is not working in 20.10: the laptop is
  not suspending even after far more than 20 minutes of idle time.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  3 13:18:59 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-16 (444 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2020-10-26 (8 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2020-04-19T16:14:35.801558

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902766/+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 1902766] Re: Automatic suspend when idle not working in 20.10

Please also try waiting over 30 minutes, because I notice your idle-
delay is set to 10 minutes so maybe they are additive...

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

Title:
  Automatic suspend when idle not working in 20.10

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have my laptop configured to suspend automatically after 20 minutes
  of idle time when on battery power. See screenshot attached showing
  these settings.

  This worked fine in 20.04. It is not working in 20.10: the laptop is
  not suspending even after far more than 20 minutes of idle time.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  3 13:18:59 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-16 (444 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2020-10-26 (8 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2020-04-19T16:14:35.801558

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902766/+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 1902766] Re: Automatic suspend when idle not working in 20.10

Please try:

 * Uninstalling these extensions:

   'mprisindicatorbut...@jasonlg1979.github.io',
'bat...@martin.zurowietz.de', 'multi-volume@tigersoldier',
'd...@rastersoft.com'

   and then reboot.

 * Running these commands:

   gsettings get org.gnome.desktop.lockdown disable-lock-screen > lockscreen.txt
   systemd-inhibit --list --mode=block > inhibit.txt

   and attach the resulting text files here.

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

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

Title:
  Automatic suspend when idle not working in 20.10

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have my laptop configured to suspend automatically after 20 minutes
  of idle time when on battery power. See screenshot attached showing
  these settings.

  This worked fine in 20.04. It is not working in 20.10: the laptop is
  not suspending even after far more than 20 minutes of idle time.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  3 13:18:59 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-16 (444 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2020-10-26 (8 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2020-04-19T16:14:35.801558

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902766/+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 1902749] Re: Log in screen flashes on and off until I log in

Please try (in this order):

 * Selecting 'Ubuntu on Wayland' from the login screen before you enter
your password (the icon in the bottom right corner). Now does the
flashing also happen on the desktop?

 * The official Ubuntu kernel, which is version 5.4.

 * A slightly older kernel like 5.8.

 * Editing /etc/gdm3/custom.conf and uncomment:
 #WaylandEnable=false
   to:
 WaylandEnable=false


** Tags added: amdgpu hybrid nvidia

** Summary changed:

- Log in screen flashes on and off until I log in
+ [amdgpu] [nvidia] Log in screen flashes on and off until I log in

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

** Summary changed:

- [amdgpu] [nvidia] Log in screen flashes on and off until I log in
+ [amdgpu] Log in screen flashes on and off until I log in

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

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

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: New => Incomplete

** No longer affects: xserver-xorg-video-amdgpu (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/1902749

Title:
  [amdgpu] Log in screen flashes on and off until I log in

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Im on Ubuntu 20.04.1 with an AMD Ryzen 7 4800h CPU and a Nvidia GTX
  1650ti [Mobile] GPU using nvidia-driver-450

  Kernel is up to date (5.9.3)

  When my laptop boots, the log in screen flashes black and quickly back
  on until i log in. When i reach the desktop the flashing stops. Still,
  having the screen flickering on the log in screen is very annoying.

  As far as i can tell, the laptop doesn't have any further screen
  issues.

  Thanks in advance!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.9.3-050903-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.80.02  Wed Sep 23 
01:13:39 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Tue Nov  3 17:46:21 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU116M [GeForce GTX 1650 Ti Mobile] [10de:2192] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Tongfang Hongkong Limited Device [1d05:1101]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 
00 [VGA controller])
 Subsystem: Tongfang Hongkong Limited Renoir [1d05:1100]
  InstallationDate: Installed on 2020-10-27 (7 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Standard GK5NPFO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.9.3-050903-generic 
root=UUID=a7144690-52e4-4688-a61a-b208b0648077 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N.1.16PCS01
  dmi.board.asset.tag: Standard
  dmi.board.name: GK5NPFO
  dmi.board.vendor: TongFang
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: Standard
  dmi.chassis.version: Standard
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN.1.16PCS01:bd09/01/2020:br5.16:efr1.22:svnStandard:pnGK5NPFO:pvrStandard:rvnTongFang:rnGK5NPFO:rvrStandard:cvnStandard:ct10:cvrStandard:
  dmi.product.family: Standard
  dmi.product.name: GK5NPFO
  dmi.product.sku: 0001
  dmi.product.version: Standard
  dmi.sys.vendor: Standard
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  versio

[Desktop-packages] [Bug 1893300] Re: The status of cups still shows idle when the printer has been unplugged

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

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

Title:
  The status of cups still shows idle when the printer has been
  unplugged

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project focal series:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  [ Impact ]
  After printers (non-ippusb protocal) have been disconnected, the status of 
cups still shows "idle" instead of "disabled", so seems the disconnected 
procedure hasn't worked well.

  [ Test Case ]
  1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 
20.04 machine
  2. Wait for the status of cups became "Idle" (lpstat -p)
  3. Unplug the cable of the printer
  4. Check the status of cups again. (lpstat -p)

  [ Regression potential ]
  Low, the change just makes "strcmp" to "srtsrt" and has more checks on the 
existing of device path. 

  [Expected result]
  The status should show disabled.

  [Actual result]
  The status shows idle.

  [info]
  Target:
  HP LaserJet Pro203dw
  HP Officejet 100 Mobile Printer
  HP Officeject 200 Mobile Printer
  Brother HL-2250DN
  Samsung ML-331x

  Upstream Bug: https://github.com/OpenPrinting/system-config-
  printer/issues/182

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1893300

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893300/+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 1893300] Re: The status of cups still shows idle when the printer has been unplugged

** Tags added: verification-needed

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

Title:
  The status of cups still shows idle when the printer has been
  unplugged

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project focal series:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  [ Impact ]
  After printers (non-ippusb protocal) have been disconnected, the status of 
cups still shows "idle" instead of "disabled", so seems the disconnected 
procedure hasn't worked well.

  [ Test Case ]
  1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 
20.04 machine
  2. Wait for the status of cups became "Idle" (lpstat -p)
  3. Unplug the cable of the printer
  4. Check the status of cups again. (lpstat -p)

  [ Regression potential ]
  Low, the change just makes "strcmp" to "srtsrt" and has more checks on the 
existing of device path. 

  [Expected result]
  The status should show disabled.

  [Actual result]
  The status shows idle.

  [info]
  Target:
  HP LaserJet Pro203dw
  HP Officejet 100 Mobile Printer
  HP Officeject 200 Mobile Printer
  Brother HL-2250DN
  Samsung ML-331x

  Upstream Bug: https://github.com/OpenPrinting/system-config-
  printer/issues/182

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1893300

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893300/+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 1893300] Re: The status of cups still shows idle when the printer has been unplugged

And this is the package diff for focal

** Patch added: "system-config-printer-focal.diff"
   
https://bugs.launchpad.net/oem-priority/+bug/1893300/+attachment/5430871/+files/system-config-printer-focal.diff

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

Title:
  The status of cups still shows idle when the printer has been
  unplugged

Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project focal series:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  [ Impact ]
  After printers (non-ippusb protocal) have been disconnected, the status of 
cups still shows "idle" instead of "disabled", so seems the disconnected 
procedure hasn't worked well.

  [ Test Case ]
  1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 
20.04 machine
  2. Wait for the status of cups became "Idle" (lpstat -p)
  3. Unplug the cable of the printer
  4. Check the status of cups again. (lpstat -p)

  [ Regression potential ]
  Low, the change just makes "strcmp" to "srtsrt" and has more checks on the 
existing of device path. 

  [Expected result]
  The status should show disabled.

  [Actual result]
  The status shows idle.

  [info]
  Target:
  HP LaserJet Pro203dw
  HP Officejet 100 Mobile Printer
  HP Officeject 200 Mobile Printer
  Brother HL-2250DN
  Samsung ML-331x

  Upstream Bug: https://github.com/OpenPrinting/system-config-
  printer/issues/182

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1893300

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893300/+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 1893300] Re: The status of cups still shows idle when the printer has been unplugged

Here is the package diff for groovy

** Patch added: "system-config-printer-groovy.diff"
   
https://bugs.launchpad.net/oem-priority/+bug/1893300/+attachment/5430870/+files/system-config-printer-groovy.diff

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

Title:
  The status of cups still shows idle when the printer has been
  unplugged

Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project focal series:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  [ Impact ]
  After printers (non-ippusb protocal) have been disconnected, the status of 
cups still shows "idle" instead of "disabled", so seems the disconnected 
procedure hasn't worked well.

  [ Test Case ]
  1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 
20.04 machine
  2. Wait for the status of cups became "Idle" (lpstat -p)
  3. Unplug the cable of the printer
  4. Check the status of cups again. (lpstat -p)

  [ Regression potential ]
  Low, the change just makes "strcmp" to "srtsrt" and has more checks on the 
existing of device path. 

  [Expected result]
  The status should show disabled.

  [Actual result]
  The status shows idle.

  [info]
  Target:
  HP LaserJet Pro203dw
  HP Officejet 100 Mobile Printer
  HP Officeject 200 Mobile Printer
  Brother HL-2250DN
  Samsung ML-331x

  Upstream Bug: https://github.com/OpenPrinting/system-config-
  printer/issues/182

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1893300

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893300/+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 1868207] Re: Fractional scaling window sizes incorrect after resume from suspend

Thanks. I should have said "hear back"...

In that case this bug should be closed and anyone like krul still
experiencing issues, please open a new bug by running:

  ubuntu-bug mutter


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

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

Title:
  Fractional scaling window sizes incorrect after resume from suspend

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

Bug description:
  LP bug as requested at
  https://gitlab.gnome.org/GNOME/mutter/issues/1122

  From the summary there:

  With fractional scaling enabled, after resume from suspend, maximised
  & half tiled windows have been resized/scaled so they are too large
  for the screen, and as a result no longer fit on the screen.  Not sure
  if it also happens to windows that aren't in either of these states, I
  rarely have any. Further, most but not all windows are scaled like
  this. Epiphany and Terminal definitely are, maybe XWindows clients
  like Emacs aren't?

  Under 3.34, shell/mutter seemed to notice this and would visibly snap
  the window sizes back to what they should be. Under 3.36, that no
  longer seems to happen - the windows stay too big and I need to
  manually fix them.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.35.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 20 16:54:48 2020
  InstallationDate: Installed on 2018-08-13 (584 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to focal on 2020-03-07 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1868207/+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 1893300] Re: The status of cups still shows idle when the printer has been unplugged

** Description changed:

  [ Impact ]
  After printers (non-ippusb protocal) have been disconnected, the status of 
cups still shows "idle" instead of "disabled", so seems the disconnected 
procedure hasn't worked well.
  
  [ Test Case ]
  1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 
20.04 machine
  2. Wait for the status of cups became "Idle" (lpstat -p)
  3. Unplug the cable of the printer
  4. Check the status of cups again. (lpstat -p)
+ 
+ [ Regression potential ]
+ Low, the change just makes "strcmp" to "srtsrt" and has more checks on the 
existing of device path. 
  
  [Expected result]
  The status should show disabled.
  
  [Actual result]
  The status shows idle.
  
  [info]
  Target:
  HP LaserJet Pro203dw
  HP Officejet 100 Mobile Printer
  HP Officeject 200 Mobile Printer
  Brother HL-2250DN
  Samsung ML-331x
  
  Upstream Bug: https://github.com/OpenPrinting/system-config-
  printer/issues/182
  
  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1893300

** Also affects: oem-priority/focal
   Importance: Undecided
   Status: New

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

Title:
  The status of cups still shows idle when the printer has been
  unplugged

Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project focal series:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  [ Impact ]
  After printers (non-ippusb protocal) have been disconnected, the status of 
cups still shows "idle" instead of "disabled", so seems the disconnected 
procedure hasn't worked well.

  [ Test Case ]
  1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 
20.04 machine
  2. Wait for the status of cups became "Idle" (lpstat -p)
  3. Unplug the cable of the printer
  4. Check the status of cups again. (lpstat -p)

  [ Regression potential ]
  Low, the change just makes "strcmp" to "srtsrt" and has more checks on the 
existing of device path. 

  [Expected result]
  The status should show disabled.

  [Actual result]
  The status shows idle.

  [info]
  Target:
  HP LaserJet Pro203dw
  HP Officejet 100 Mobile Printer
  HP Officeject 200 Mobile Printer
  Brother HL-2250DN
  Samsung ML-331x

  Upstream Bug: https://github.com/OpenPrinting/system-config-
  printer/issues/182

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1893300

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893300/+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 1902721] Re: xrandr fails to set screen size while starting X11

I would like to find out if the missing mode problem originates from the
kernel. Please run:

  grep . /sys/class/drm/*/modes > drmmodes.txt

and attach the resulting text file here.


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

** Changed in: x11-xserver-utils (Ubuntu)
   Status: New => Incomplete

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

Title:
  xrandr fails to set screen size while starting X11

Status in x11-xserver-utils package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  while starting X11 xrandr executes commands:

  xrandr --newmode "3840x2160_30.00"  338.75  3840 4080 4488 5136  2160 2163 
2168 2200 -hsync +vsync
  xrandr --addmode DP-1 "3840x2160_30.00"
  xrandr --output DP-1 --mode "3840x2160_30.00"

  while newmode, addmode work, the third command fails with "xrandr: Configure 
crtc 0 failed".
  Looking at all video interfaces, the mode added to DP-1 is there. Now, from 
some remote shell:

  DISPLAY=:0.0 xrandr --output DP-1 --mode 3840x2160_30.00

  does not fail, but set graphics mode as desired. Trying to pause this to give 
it more time does not help. Does not work. It works as soon as i log in, set 
display to ":0.0" and then give the xrandr-command to use and set DP-1 to the 
desired mode.
  Removing all xrandr-commands does not help either: the display stays black.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: x11-common 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Tue Nov  3 14:52:24 2020
  Dependencies: lsb-base 11.1.0ubuntu2
  DistUpgraded: 2018-11-23 16:21:56,549 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1497]
  InstallationDate: Installed on 2014-01-31 (2468 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 
(20131016)
  MachineType: Hewlett-Packard HP Compaq 6200 Pro MT PC
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-52-generic 
root=UUID=de4af024-5d59-4f85-b5ca-11f17f085706 ro rootflags=subvol=@ 
consoleblank=0 video=DP-1:3840x2160M-32@30e
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2018-11-23 (710 days ago)
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 11/10/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J01 v02.15
  dmi.board.name: 1497
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.15:bd11/10/2011:svnHewlett-Packard:pnHPCompaq6200ProMTPC:pvr:rvnHewlett-Packard:rn1497:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq 6200 Pro MT PC
  dmi.product.sku: XL504AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/1902721/+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 1902721] Re: xrandr fails to set screen size while starting X11

In theory you should never need to use 'xrandr' at all...

I've decoded your monitor's EDID data and got:

EDID version: 1.3
Manufacturer: PHL Model 2290 Serial Number 174
Made in week 46 of 2016
Digital display
Maximum image size: 62 cm x 34 cm
Gamma: 2.20
DPMS levels: Off
RGB color display
First detailed timing is preferred timing
Color Characteristics
  Red:   0.6298, 0.3408
  Green: 0.3095, 0.6259
  Blue:  0.1562, 0.0605
  White: 0.3134, 0.3291
Established Timings I & II
720x40070.082 Hz   9:531.467 kHz  28.320 MHz (IBM)
640x48059.940 Hz   4:331.469 kHz  25.175 MHz (DMT)
640x48066.667 Hz   4:335.000 kHz  30.240 MHz (Apple)
640x48072.809 Hz   4:337.861 kHz  31.500 MHz (DMT)
640x48075.000 Hz   4:337.500 kHz  31.500 MHz (DMT)
800x60060.317 Hz   4:337.879 kHz  40.000 MHz (DMT)
800x60075.000 Hz   4:346.875 kHz  49.500 MHz (DMT)
   1024x76860.004 Hz   4:348.363 kHz  65.000 MHz (DMT)
   1024x76875.029 Hz   4:360.023 kHz  78.750 MHz (DMT)
   1280x1024   75.025 Hz   5:479.976 kHz 135.000 MHz (DMT)
Standard Timings
   1920x1080   60.000 Hz  16:967.500 kHz 148.500 MHz (DMT)
   1280x1024   60.020 Hz   5:463.981 kHz 108.000 MHz (DMT)
   1280x96060.000 Hz   4:360.000 kHz 108.000 MHz (DMT)
   1440x90074.984 Hz  16:10   70.635 kHz 136.750 MHz (DMT)
   1440x90059.887 Hz  16:10   55.935 kHz 106.500 MHz (DMT)
   1680x1050   59.954 Hz  16:10   65.290 kHz 146.250 MHz (DMT)
   1280x72060.000 Hz  16:945.000 kHz  74.250 MHz (DMT)
Detailed mode: Clock 533.250 MHz, 621 mm x 341 mm
   3840 3888 3920 4000 ( 48  32  80)
   2160 2163 2168  (  3   5  54)
   +hsync -vsync
   VertFreq: 59.997 Hz, HorFreq: 133.312 kHz
Detailed mode: Clock 262.750 MHz, 621 mm x 341 mm
   3840 3888 3920 4000 ( 48  32  80)
   2160 2163 2168 2191 (  3   5  23)
   +hsync -vsync
   VertFreq: 29.981 Hz, HorFreq: 65.688 kHz
Display Product Name: PHL 288P6L
Display Range Limits
  Monitor ranges (GTF): 23-80 Hz V, 30-99 kHz H, max dotclock 600 MHz
Has 1 extension block
Checksum: 0x4c



CTA-861 Extension Block Revision 3
Underscans PC formats by default
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
1 native detailed modes
47 bytes of CTA data blocks
  Video Data Block
 1920x1080   60.000 Hz  16:967.500 kHz 148.500 MHz (VIC  16, native)
 1280x72060.000 Hz  16:945.000 kHz  74.250 MHz (VIC   4)
  720x48059.940 Hz  16:931.469 kHz  27.000 MHz (VIC   3)
 1920x1080   50.000 Hz  16:956.250 kHz 148.500 MHz (VIC  31)
 1280x72050.000 Hz  16:937.500 kHz  74.250 MHz (VIC  19)
  640x48059.940 Hz   4:331.469 kHz  25.175 MHz (VIC   1)
  720x57650.000 Hz  16:931.250 kHz  27.000 MHz (VIC  18)
 3840x2160   24.000 Hz  16:954.000 kHz 297.000 MHz (VIC  93)
 3840x2160   25.000 Hz  16:956.250 kHz 297.000 MHz (VIC  94)
 3840x2160   30.000 Hz  16:967.500 kHz 297.000 MHz (VIC  95)
 3840x2160   50.000 Hz  16:9   112.500 kHz 594.000 MHz (VIC  96)
 3840x2160   60.000 Hz  16:9   135.000 kHz 594.000 MHz (VIC  97)
  Audio Data Block
Linear PCM, max channels 2
  Supported sample rates (kHz): 48 44.1 32
  Supported sample sizes (bits): 24 20 16
  Speaker Allocation Data Block
Speaker map:
  FL/FR - Front Left/Right
  Vendor-Specific Data Block, OUI 0x000c03 (HDMI)
Source physical address 1.4.0.0
DC_36bit
DC_30bit
DC_Y444
DVI_Dual
Maximum TMDS clock: 600 MHz
Extended HDMI video details:
  HDMI VICs:
 3840x2160   30.000 Hz  16:967.500 kHz 297.000 MHz (HDMI VIC 1)
 3840x2160   25.000 Hz  16:956.250 kHz 297.000 MHz (HDMI VIC 2)
 3840x2160   24.000 Hz  16:954.000 kHz 297.000 MHz (HDMI VIC 3)
  Vendor-Specific Data Block, OUI 0xc45dd8 (HDMI Forum)
Version: 1
Maximum TMDS Character Rate: 600 MHz
SCDC Present
Supports 12-bits/component Deep Color 4:2:0 Pixel Encoding
Supports 10-bits/component Deep Color 4:2:0 Pixel Encoding
  Extended tag: YCbCr 4:2:0 Capability Map Data Block
 3840x2160   50.000 Hz  16:9   112.500 kHz 594.000 MHz (VIC  96)
 3840x2160   60.000 Hz  16:9   135.000 kHz 594.000 MHz (VIC  97)
Detailed mode: Clock 74.250 MHz, 621 mm x 341 mm
   1280 1390 1430 1650 (110  40 220)
720  725  730  750 (  5   5  20)
   +hsync +vsync
   VertFreq: 60.000 Hz, HorFreq: 45.000 kHz
Detailed mode: Clock 27.000 MHz, 621 mm x 341 mm
720  736  798  858 ( 16  62  60)
480  489  495  525 (  9   6  30)
   -hsync -vsync
   VertFreq: 59.940 Hz, HorFreq: 31.469 kHz
Detailed mode: Clock 277.250 MHz, 621 mm x 341 mm
   1920 1968 2000 2080 ( 48  32  80)
   2160 2163 2173  (  3  10  49)
   +

[Desktop-packages] [Bug 1868207] Re: Fractional scaling window sizes incorrect after resume from suspend

2020-11-03 Thread Michael Gratton

Nothing extra to report - haven't seen it again.

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

Title:
  Fractional scaling window sizes incorrect after resume from suspend

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  LP bug as requested at
  https://gitlab.gnome.org/GNOME/mutter/issues/1122

  From the summary there:

  With fractional scaling enabled, after resume from suspend, maximised
  & half tiled windows have been resized/scaled so they are too large
  for the screen, and as a result no longer fit on the screen.  Not sure
  if it also happens to windows that aren't in either of these states, I
  rarely have any. Further, most but not all windows are scaled like
  this. Epiphany and Terminal definitely are, maybe XWindows clients
  like Emacs aren't?

  Under 3.34, shell/mutter seemed to notice this and would visibly snap
  the window sizes back to what they should be. Under 3.36, that no
  longer seems to happen - the windows stay too big and I need to
  manually fix them.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.35.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 20 16:54:48 2020
  InstallationDate: Installed on 2018-08-13 (584 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to focal on 2020-03-07 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1868207/+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 1902810] [NEW] Video Flicker

2020-11-03 Thread Dave Keeton

Public bug reported:

The display on this Dell Latitude 5285 with detachable keyboard flickers
when an external monitor is connected.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-7625.26~1603389471~20.04~f6b125f-generic 
5.8.14
Uname: Linux 5.8.0-7625-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Tue Nov  3 18:38:42 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 620 [1028:07a4]
InstallationDate: Installed on 2020-07-01 (125 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 022: ID 044e:1218 Alps Electric Co., Ltd Alps Touchpad
 Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 5285
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.8.0-7625-generic 
root=UUID=f22e0756-4530-44bf-8da3-d0ed47ef183a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2020
dmi.bios.release: 1.10
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.1
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 32
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd07/24/2020:br1.10:svnDellInc.:pnLatitude5285:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct32:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5285
dmi.product.sku: 07A4
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal third-party-packages ubuntu

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

Title:
  Video Flicker

Status in xorg package in Ubuntu:
  New

Bug description:
  The display on this Dell Latitude 5285 with detachable keyboard
  flickers when an external monitor is connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-7625.26~1603389471~20.04~f6b125f-generic 
5.8.14
  Uname: Linux 5.8.0-7625-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Tue Nov  3 18:38:42 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:07a4]
  InstallationDate: Installed on 2020-07-01 (125 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 022: ID 044e:1218 Alps Electric Co., Ltd Alps Touchpad
   Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5285
  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.8.0-7625-generic 
root=UUID=f22e0756-4530-44bf-8da3-d0ed47ef183a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date

[Desktop-packages] [Bug 1868207] Re: Fractional scaling window sizes incorrect after resume from suspend

Also Michael logged this bug from a Wayland session.

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

Title:
  Fractional scaling window sizes incorrect after resume from suspend

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  LP bug as requested at
  https://gitlab.gnome.org/GNOME/mutter/issues/1122

  From the summary there:

  With fractional scaling enabled, after resume from suspend, maximised
  & half tiled windows have been resized/scaled so they are too large
  for the screen, and as a result no longer fit on the screen.  Not sure
  if it also happens to windows that aren't in either of these states, I
  rarely have any. Further, most but not all windows are scaled like
  this. Epiphany and Terminal definitely are, maybe XWindows clients
  like Emacs aren't?

  Under 3.34, shell/mutter seemed to notice this and would visibly snap
  the window sizes back to what they should be. Under 3.36, that no
  longer seems to happen - the windows stay too big and I need to
  manually fix them.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.35.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 20 16:54:48 2020
  InstallationDate: Installed on 2018-08-13 (584 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to focal on 2020-03-07 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1868207/+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 1868207] Re: Fractional scaling window sizes incorrect after resume from suspend

Thanks krul, that confirms fractional scaling for you. I am still
curious to also here back from Michael Gratton.

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

Title:
  Fractional scaling window sizes incorrect after resume from suspend

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  LP bug as requested at
  https://gitlab.gnome.org/GNOME/mutter/issues/1122

  From the summary there:

  With fractional scaling enabled, after resume from suspend, maximised
  & half tiled windows have been resized/scaled so they are too large
  for the screen, and as a result no longer fit on the screen.  Not sure
  if it also happens to windows that aren't in either of these states, I
  rarely have any. Further, most but not all windows are scaled like
  this. Epiphany and Terminal definitely are, maybe XWindows clients
  like Emacs aren't?

  Under 3.34, shell/mutter seemed to notice this and would visibly snap
  the window sizes back to what they should be. Under 3.36, that no
  longer seems to happen - the windows stay too big and I need to
  manually fix them.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.35.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 20 16:54:48 2020
  InstallationDate: Installed on 2018-08-13 (584 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to focal on 2020-03-07 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1868207/+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 1902652] Re: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow

I think this should work in theory, but yeah it's not specific to a
machine type:

http://cdimage.ubuntu.com/releases/20.04.1/release/ubuntu-20.04.1-live-
server-arm64.iso

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

Title:
  [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow

Status in mesa package in Ubuntu:
  Incomplete
Status in xf86-video-armsoc package in Ubuntu:
  Incomplete

Bug description:
  3d rendering is very slow, also when surfing the internet, webpages
  take a while to render. Internet access is not the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 4.19.64+ aarch64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Nov  3 05:42:00 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   
  Lspci:
   
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ 
root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ noquiet 
splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
Identifier  "Allwinner sun4i DRM driver"
Driver  "armsoc"
Option  "DRI2"  "true"
   EndSection
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1902652/+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 1902652] Re: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow

Please run these commands:

  ls -l /dev/dri/* > dri.txt
  glxinfo > glx.txt

and attach the resulting text files here.

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

** Changed in: xf86-video-armsoc (Ubuntu)
   Status: New => Incomplete

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

Title:
  [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow

Status in mesa package in Ubuntu:
  Incomplete
Status in xf86-video-armsoc package in Ubuntu:
  Incomplete

Bug description:
  3d rendering is very slow, also when surfing the internet, webpages
  take a while to render. Internet access is not the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 4.19.64+ aarch64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Nov  3 05:42:00 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   
  Lspci:
   
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ 
root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ noquiet 
splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
Identifier  "Allwinner sun4i DRM driver"
Driver  "armsoc"
Option  "DRI2"  "true"
   EndSection
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1902652/+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 1878293] Re: xterm resize is wonky

** Also affects: xterm (Ubuntu Hirsute)
   Importance: Low
   Status: Invalid

** Also affects: mutter (Ubuntu Hirsute)
   Importance: Undecided
   Status: Fix Released

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

Title:
  xterm resize is wonky

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in xterm package in Ubuntu:
  Invalid
Status in mutter source package in Groovy:
  Fix Committed
Status in xterm source package in Groovy:
  Invalid
Status in mutter source package in Hirsute:
  Fix Released
Status in xterm source package in Hirsute:
  Invalid

Bug description:
  [ Impact ]

  When I try to resize an xterm window the same way,
  this happens instead: as the mouse is moved, the upper-right corner
  does move, but it doesn't track with the mouse pointer like it should.
  Meanwhile, the lower-left corner also moves (it should have remained anchored 
in its original x-y position on the screen).

  [ Test case ]

  - Start Xterm
  - Resize the window from its top/left corner
  - It should resize normally, and not act as shown in

https://gitlab.gnome.org/GNOME/mutter/uploads/3c19763b7748ce76b0ba2958cde7636b/Screencast_from_02-04-19_14_03_24.webm

  [ Regression potential ]

  Windows resizing might not work correctly

  ---

  % lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04 LTS
  Release:20.04
  Codename:   focal

  % wmctrl -m
  Name: GNOME Shell
  Class: N/A
  PID: N/A
  Window manager's "showing the desktop" mode: OFF

  Terms:
  window has four sides: top, bottom, left, and right
  when referring to corners, "upper" means "top", and "lower" means "bottom",
  so the four corners are upper-right, lower-right, lower-left, and  upper-left.
  wonky: works wrong, as detailed below ("cases that work wrong...")

  Description:

  I can resize a gnome-terminal window, everything works fine.
  (Grab it, using the mouse, by the upper-right corner (click-and-hold);
  the size changes as the mouse is moved, because the position
  of the upper-right corner follows the mouse.  (Only the upper-right corner 
moves.))
  But when I try to resize an xterm window the same way,
  this happens instead: as the mouse is moved, the upper-right corner
  does move, but it doesn't track with the mouse pointer like it should.
  Meanwhile, the lower-left corner also moves (it should have remained anchored 
in its original x-y position on the screen).

  Cases that work correctly:
  If the xterm window is grabbed by the lower-right corner and resized, this 
case works properly.
  If the xterm window is grabbed by the bottom edge and resized, this case 
works properly.
  If the xterm window is grabbed by the right edge and resized, this case works 
properly.

  Cases that work wrong ("wonky"):
  If the xterm window is grabbed by the left edge and resized, then the 
opposite (i.e. right) edge (incorrectly) migrates.
  If the xterm window is grabbed by the top edge and resized, then the opposite 
(i.e. bottom) edge (incorrectly) migrates.
  If the xterm window is grabbed by the upper-right corner and resized, then 
the window (incorrectly) migrates.
  If the xterm window is grabbed by the lower-left corner and resized, then the 
window (incorrectly) migrates.
  If the xterm window is grabbed by the upper-left corner and resized, then the 
window (incorrectly) migrates.

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: xterm 353-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue May 12 13:52:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GT 740] [10de:0fc8] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: PNY GK107 [GeForce GT 740] [196e:109a]
  InstallationDate: Installed on 2020-05-06 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=7f55a3c5-bff9-45ea-8979-583e4fbfec07 ro quiet splash 
vt.handoff=7SourcePack

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-11-03 Thread Mariano Ruiz

I have to rectify a little bit my affirmation above, everything I said
about the video issues is right, but the problem with the video lagging
and blinking and re-scalling specially when you move the cursor while
watching in full screen mode look like a GNOME problem, not a NVIDIA
proprietary driver problem, because after setting up the Nouveau open
source driver again, the same problem happens when watching video in
full screen, so better to setup the Nvidia driver with the workaround
than use the open source drive that does not enable all the acceleration
features your video hardware has.

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

Title:
  [nvidia] Screen scaling 125% gives 200%

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

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1899745] Re: [SRU] alsa-utils: let alsactl support _boot section defined in ucm

This bug was fixed in the package alsa-utils - 1.2.2-1ubuntu2

---
alsa-utils (1.2.2-1ubuntu2) focal; urgency=medium

  * d/p/0001-alsactl-init-iterate-through-all-cards-for-the-initi.patch
  * d/p/0002-alsactl-add-initial-support-for-UCM-init.patch
  * d/p/0003-alsactl-redirect-alsa-lib-errors.patch
  * d/p/0004-alsactl-add-D-argument-to-execute-also-the-UCM-defau.patch
  * d/p/0005-alsactl-use-the-right-priority-for-syslog-messages.patch
  * d/p/0006-alsactl-allow-to-compile-alsactl-without-UCM-support.patch
  * d/p/0007-alsactl-ucm-rename-_once-command-to-_boot-command.patch
  * d/p/0008-alsaucm-remove-custom-rules-alsactl-is-UCM-aware-now.patch
Make alsactl support _boot section defined in the ucm, then the
mixer values defined in the _boot section for Dell soundwire audio
machines could be executed at the first booting. (LP: #1899745)

 -- Hui Wang   Fri, 16 Oct 2020 17:50:30 +0200

** Changed in: alsa-utils (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] alsa-utils: let alsactl support _boot section defined in ucm

Status in HWE Next:
  New
Status in alsa-utils package in Ubuntu:
  Fix Released
Status in alsa-utils source package in Focal:
  Fix Released

Bug description:
  This patchset was backported from mainline alsa-utils 1.2.3, and
  groovy already integrated alsa-utils 1.2.3, there is no need to SRU
  this patchset to groovy, so only for focal.

  [Impact]
  We enabled 2 Dell soundwire audio machines, these machines depend on
  ucm to make the audio work, and in the ucm, the _boot section defined
  some amixers values for the 1st booting, these amixer values should
  be set to audio driver at the 1st booting, otherwise the whole audio
  doesn't work.

  [Fix]
  Backport some patches from mainline v1.2.3, these patches make the
  alsactl support _boot section in the ucm, then the systemd will call
  alsactl init after booting, the alsactl init will setting all amixers
  defined in the _boot section of ucm.

  [Test Case]
  On the Dell soundwire audio machines, After booting up, run 'amixer
  contents | less' to check all amixer values defined in the _boot
  section of ucm, all values read from driver are same as the ones in
  the ucm, test speaker/microphone/headset, all work well.

  [Regression Risk]
  This could introduce failure on runing 'alsactl init' for some machines,
  then the amixers will not be initialized correctly, users will experience
  all audio can't work like speaker doesn't output sound or microphone can't
  record sound. But this regression possibility is very low, since We have
  tested it both on soundwire machines and non-soundwire machines, all worked 
well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1899745/+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 1899745] Update Released

2020-11-03 Thread Chris Halse Rogers

The verification of the Stable Release Update for alsa-utils has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] alsa-utils: let alsactl support _boot section defined in ucm

Status in HWE Next:
  New
Status in alsa-utils package in Ubuntu:
  Fix Released
Status in alsa-utils source package in Focal:
  Fix Released

Bug description:
  This patchset was backported from mainline alsa-utils 1.2.3, and
  groovy already integrated alsa-utils 1.2.3, there is no need to SRU
  this patchset to groovy, so only for focal.

  [Impact]
  We enabled 2 Dell soundwire audio machines, these machines depend on
  ucm to make the audio work, and in the ucm, the _boot section defined
  some amixers values for the 1st booting, these amixer values should
  be set to audio driver at the 1st booting, otherwise the whole audio
  doesn't work.

  [Fix]
  Backport some patches from mainline v1.2.3, these patches make the
  alsactl support _boot section in the ucm, then the systemd will call
  alsactl init after booting, the alsactl init will setting all amixers
  defined in the _boot section of ucm.

  [Test Case]
  On the Dell soundwire audio machines, After booting up, run 'amixer
  contents | less' to check all amixer values defined in the _boot
  section of ucm, all values read from driver are same as the ones in
  the ucm, test speaker/microphone/headset, all work well.

  [Regression Risk]
  This could introduce failure on runing 'alsactl init' for some machines,
  then the amixers will not be initialized correctly, users will experience
  all audio can't work like speaker doesn't output sound or microphone can't
  record sound. But this regression possibility is very low, since We have
  tested it both on soundwire machines and non-soundwire machines, all worked 
well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1899745/+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 1900170] Re: apport hook looks for snap profile folder in the wrong place

This bug was fixed in the package chromium-browser -
1:85.0.4183.83-0ubuntu0.20.04.2

---
chromium-browser (1:85.0.4183.83-0ubuntu0.20.04.2) focal; urgency=medium

  [ Sébastien Bacher ]
  * debian/apport/chromium-browser.py:
- the profile is now installed in the common directory (LP: #1900170)

 -- Olivier Tilloy   Thu, 22 Oct 2020
18:07:20 +0200

** Changed in: chromium-browser (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  apport hook looks for snap profile folder in the wrong place

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Focal:
  Fix Released

Bug description:
  Since https://git.launchpad.net/~chromium-team/chromium-browser/+git
  /snap-from-source/commit/?id=d7e3b7f8, the default profile directory
  for the chromium snap was moved from $SNAP_USER_DATA to
  $SNAP_USER_COMMON (to mitigate the effects of bug #1616650).

  But the apport hook in the transitional deb package wasn't updated
  accordingly.

  [Impact]

  Bugs filed with `ubuntu-bug chromium-browser` have incomplete data
  attached. See e.g. the attachements to bug #1899356. There's a file
  called HookError_chromium_browser.txt with a python traceback because
  the profile directory wasn't found in the expected location.

  [Test Case]

  In focal, apt install chromium-browser, then run chromium at least
  once to ensure there is a profile directory (under
  $HOME/snap/chromium/common/chromium), then run `ubuntu-bug chromium-
  browser`. Observe that there isn't a FileNotFoundError traceback in
  the terminal for an unknown profile directory, and that the apport
  dialog with a summary of the information to be posted doesn't contain
  a "HookError_chromium_browser" entry.

  [Regression Potential]

  This affects only the apport hook for chromium-browser, the
  application itself shouldn't be affected. The hook should be verified
  to continue working by running the `ubuntu-bug chromium-browser`
  command and carefully inspecting the information that would be sent to
  launchpad.

  [Original description]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 16 18:40:02 2020
  InstallationDate: Installed on 2020-09-16 (29 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2020-11-03 Thread Chris Halse Rogers

The verification of the Stable Release Update for chromium-browser has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  apport hook looks for snap profile folder in the wrong place

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Focal:
  Fix Released

Bug description:
  Since https://git.launchpad.net/~chromium-team/chromium-browser/+git
  /snap-from-source/commit/?id=d7e3b7f8, the default profile directory
  for the chromium snap was moved from $SNAP_USER_DATA to
  $SNAP_USER_COMMON (to mitigate the effects of bug #1616650).

  But the apport hook in the transitional deb package wasn't updated
  accordingly.

  [Impact]

  Bugs filed with `ubuntu-bug chromium-browser` have incomplete data
  attached. See e.g. the attachements to bug #1899356. There's a file
  called HookError_chromium_browser.txt with a python traceback because
  the profile directory wasn't found in the expected location.

  [Test Case]

  In focal, apt install chromium-browser, then run chromium at least
  once to ensure there is a profile directory (under
  $HOME/snap/chromium/common/chromium), then run `ubuntu-bug chromium-
  browser`. Observe that there isn't a FileNotFoundError traceback in
  the terminal for an unknown profile directory, and that the apport
  dialog with a summary of the information to be posted doesn't contain
  a "HookError_chromium_browser" entry.

  [Regression Potential]

  This affects only the apport hook for chromium-browser, the
  application itself shouldn't be affected. The hook should be verified
  to continue working by running the `ubuntu-bug chromium-browser`
  command and carefully inspecting the information that would be sent to
  launchpad.

  [Original description]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 16 18:40:02 2020
  InstallationDate: Installed on 2020-09-16 (29 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900170/+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 1890365] Re: [snap] Web Serial fails to access local device

2020-11-03 Thread edward sternin

Made no difference.  Tried before or after launching the browser.

By the way, this bug is not there in edge.  Only Chromium.

On 10/30/20 12:27 PM, Olivier Tilloy wrote:
> Does the following help?
>
>  sudo snap connect chromium:raw-usb
>
> ** Changed in: chromium-browser (Ubuntu)
> Status: Expired => New
>
-- 
-
Edward Sternin, Physics Department, Brock U, St.Catharines, Ontario, L2S 3A1
   http://www.physics.brocku.ca/People/Faculty/Sternin/
voice: (905)688-5550x3414  FAX:(905)984-4857  email: edward.ster...@brocku.ca

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

Title:
  [snap] Web Serial fails to access local device

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  A javascript-based web page works fine when accessed through Chrome,
  fails to recognize that any devices exist when accessed from Chromium
  on the same Unubtu 20.04 platform.

  The code includes the following snippet:

  const requestOptions = {
  filters: [{ usbVendorId: 0x1881 }]
};
port = await navigator.serial.requestPort(requestOptions);
await port.open({ baudrate: 9600 });
writer = port.writable.getWriter();
reader = port.readable.getReader();

  Under Chrome 84.0.4147.105 (Official Build) (64-bit), ttyACM0 device
  is listed in the pop-up, is selectable, and can communicate.  Under
  Chromium 84.0.4147.105 (Official Build) snap (64-bit), the pop-up
  contains only "No compatible devices found" message.

  Experimental Web Features flag is enabled in both browsers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890365/+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 1901286] Re: gnome-disk-image-mounter fails after upgrade to 20.10

2020-11-03 Thread Tessa

Mapped file virtio-win-0.1.185.iso as /dev/loop0.

and then the ISO shows as mounted in nautilus. so I guess it's not a
problem with the ISO itself, but with whatever nautilus+gnome is doing
to try and mount it.

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

Title:
  gnome-disk-image-mounter fails after upgrade to 20.10

Status in gnome-disk-utility package in Ubuntu:
  Incomplete

Bug description:
  after upgrading to 20.10, mounting ISOs fails after a bit over 20s, with a 
GTK dialogue that reads:
  ```
  Error attaching disk image:
  GDBus.Error:org.freedesktop.UDisks2.Error.Fails: Error waiting for loop 
object after creating '/dev/loop5': Timed out waiting for object 
(udisks-error-quark, 0)
  ```

  note that the loop device named increases on every attempt, it doesn't
  appear to be freeing previously allocated devices.

  here's the only output when run from the shell:

  ```
  $ time gnome-disk-image-mounter some.iso 

  real  0m23.141s
  user  0m0.144s
  sys   0m0.019s

  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-disk-utility 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-lowlatency 5.8.14
  Uname: Linux 5.8.0-25-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 23 23:42:34 2020
  InstallationDate: Installed on 2020-07-15 (101 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gnome-disk-utility
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1901286/+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 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-11-03 Thread Mariano Ruiz

As @vsulimov mention, the solution from @nightwing666 works, in my case
in a ThinkPad X1 Gen 2, but the video scaling in full screen doesn't, it
makes any video you try to reproduce in full screen to blink, and if you
set the video again in not fullscreen mode the video is scaled x2, or it
makes the video player to crash. I tried with the default video player
from Ubuntu, with VLC Player and even with Firefox reproducing a video
from Youtube, in all the cases the result is the same: the video is
reproduced well as long you don't enable full screen video reproduction.
I tried with scalling at 125% and 150% and it failed in both cases.

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

Title:
[nvidia] Screen scaling 125% gives 200%

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

Bug description:
Procedure used:
1.
Fully updated system via apt update && apt upgrade

2.
Select the screen setup in gnome control center

3.
Click the "Fractional scaling" toggle

4.
Select 125% and click the green "use" button top right (it says "Anvend" in
dansih)

5.
Observe that the window has grown a lot, click the "use new settings" button

6.
The window tells me, I am at 200% scaling. The "200%" option is now
highlighted.

7.
Switch back to 100% and file this bug.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.16
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 4 09:42:34 2020
InstallationDate: Installed on 2018-01-14 (810 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=da_DK.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1902148] Re: [snap] launchers in app's dock menu do launch general LO

2020-11-03 Thread Heather Ellsworth

Yeah.. I was sure this would work because i tested my addition locally
in a little quick script. I reran the lp build and it failed in the same
way (good to know it's consistent). I did a local build last night and
ran out of memory becuase libreoffice is a beast so I'll try again on an
unused system to try and debug why it's failing..

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

Title:
  [snap] launchers in app's dock menu do launch general LO

Status in libreoffice package in Ubuntu:
  In Progress

Bug description:
  LO 7.0.2
  Ubuntu Focal

  1) right-click on LO icon in dock (white LO icon which does launch the home 
page with apps and recent docs)
  2) select e.g. Calc

  It does launch general LO (home page with apps and recent docs), not
  Calc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1902148/+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 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

This bug was fixed in the package systemd - 245.4-4ubuntu3.3

---
systemd (245.4-4ubuntu3.3) focal; urgency=medium

  [ Rafael David Tinoco ]
  * d/p/lp1861941-dont-generate-disk-byuuid-for-bcache-uuid.patch:
Reworded and reintroduced patch to fully explain delta is NOT a fix to
LP: #1861941 if the bcache-tools patch exists, but should be kept anyway
as the change makes sense for a better experience to end user.
(LP: #1861941)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f8f64b3b58a04a83b1c426818b9affc41e0bff6c

  [ Dan Streetman ]
  * d/p/lp1882596-man-fix-some-manvolnum.patch:
- fix some man section references (LP: #1882596)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3959ec95eff78d38ec4409807f151572afe83fe9
  * d/p/lp1895418-correct-resolved-conf-cache-default.patch:
- fix resolved.conf default Cache= value (LP: #1895418)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ebe274a2b01658ee39b372d7033c35209510b028
  * d/p/lp1897744-resolve-enable-RES_TRUSTAD-towards-the-127.0.0.53-st.patch:
- add resolv.conf 'trust-ad' option (LP: #1897744)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f6acc8c620b80adab7b048352d85e722b5ba8214
  * d/t/*:
- Update tests to fix false negatives (LP: #1892358)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=cee6c31a6caec7888270c9fa8757105ab950ed0c

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a1c1a2bb0ff27faf84fe94583631dfd0f1f4ed8f

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9417ce996766c133c2a33d4102ce1494f3166774

 -- Dan Streetman   Thu, 08 Oct 2020 16:14:56
-0400

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

** Changed in: systemd (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in build-essential package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid
Status in iputils package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Invalid
Status in ntpsec package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Invalid
Status in linux-meta source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in build-essential source package in Focal:
  Confirmed
Status in linux-meta source package in Focal:
  New
Status in qemu source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released
Status in util-linux source package in Focal:
  Confirmed

Bug description:
  [impact]

  autopkgtests are failing/flaky and prevent other packages from
  migrating to -updates

  [test case]

  check autopkgtest history

  [regression potential]

  in regard to the changed test cases, any regression would likely
  result in either an incorrectly passed test, or an incorrectly failed
  test.

  [scope]

  for systemd, this is needed for x, b, and f.

  tests in g appear to be mostly stable, but I've opened MR (linked from
  this bug) to update the tests there as well.

  i don't plan to update x, as it's reaching ESM in ~6 months, and
  backporting the test fixes is more work than just a simple code copy,
  since there are additional differences/changes needed in the older
  version of systemd (and python3). the failing/flaky tests in x have
  been like that forever, and people have just retried them; we can keep
  retrying them until x moves into ESM next year.

  [original description]

  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
    amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-an

[Desktop-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

This bug was fixed in the package systemd - 237-3ubuntu10.43

---
systemd (237-3ubuntu10.43) bionic; urgency=medium

  [ Guilherme G. Piccoli ]
  * d/p/lp1830746-bump-mlock-ulimit-to-64Mb.patch:
- Bump the memlock limit to match Focal and newer releases (LP: #1830746)
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=61adb797642f3dd2e5c14f7914c2949c665cefe8

  [ Victor Manuel Tapia King ]
  * d/p/lp1896614-core-Avoid-race-when-starting-dbus-services.patch:
- Fix race when starting dbus services (LP: #1896614)
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=373cb6ccd6978a7112bbfd7e5cf4f703a9f8448e

  [ Dan Streetman ]
  * d/t/*,
d/p/lp1892358/0001-test-increase-qemu-timeout-for-TEST-08-and-TEST-09.patch,
d/p/lp1892358/0002-test-increase-timeout-for-TEST-17-UDEV-WANTS.patch,
d/p/lp1892358/0003-test-increase-qemu-timeout-for-TEST-18-and-TEST-19.patch:
- Increase QEMU_TIMEOUT on 'upstream' autopkgtest tests
- Pull latest tests from newer releases to fix false negatives
- Blacklist flaky 'upstream' TEST-03
  (LP: #1892358)
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9fd8391c2499e163515b629a8ca5790898fc599d
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1756b3e1c3e625ed7162cff4909e7a29c315051
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=37f8d73516a84e85e4057d6a92204b4a174af718
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=229ed2076eb773efc548035262b8b8009bf89207
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f2d7b1f952667316cc07a4b3c5010e66ace07a90
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=659befe61bbfeb7afc9efa24458c9745412d7c6d

 -- Victor Manuel Tapia King   Wed, 07 Oct
2020 16:30:03 -0400

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in build-essential package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid
Status in iputils package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Invalid
Status in ntpsec package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Invalid
Status in linux-meta source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in build-essential source package in Focal:
  Confirmed
Status in linux-meta source package in Focal:
  New
Status in qemu source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released
Status in util-linux source package in Focal:
  Confirmed

Bug description:
  [impact]

  autopkgtests are failing/flaky and prevent other packages from
  migrating to -updates

  [test case]

  check autopkgtest history

  [regression potential]

  in regard to the changed test cases, any regression would likely
  result in either an incorrectly passed test, or an incorrectly failed
  test.

  [scope]

  for systemd, this is needed for x, b, and f.

  tests in g appear to be mostly stable, but I've opened MR (linked from
  this bug) to update the tests there as well.

  i don't plan to update x, as it's reaching ESM in ~6 months, and
  backporting the test fixes is more work than just a simple code copy,
  since there are additional differences/changes needed in the older
  version of systemd (and python3). the failing/flaky tests in x have
  been like that forever, and people have just retried them; we can keep
  retrying them until x moves into ESM next year.

  [original description]

  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
    amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services

[Desktop-packages] [Bug 1892358] Update Released

2020-11-03 Thread Chris Halse Rogers

The verification of the Stable Release Update for systemd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in build-essential package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid
Status in iputils package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Invalid
Status in ntpsec package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Invalid
Status in linux-meta source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in build-essential source package in Focal:
  Confirmed
Status in linux-meta source package in Focal:
  New
Status in qemu source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released
Status in util-linux source package in Focal:
  Confirmed

Bug description:
  [impact]

  autopkgtests are failing/flaky and prevent other packages from
  migrating to -updates

  [test case]

  check autopkgtest history

  [regression potential]

  in regard to the changed test cases, any regression would likely
  result in either an incorrectly passed test, or an incorrectly failed
  test.

  [scope]

  for systemd, this is needed for x, b, and f.

  tests in g appear to be mostly stable, but I've opened MR (linked from
  this bug) to update the tests there as well.

  i don't plan to update x, as it's reaching ESM in ~6 months, and
  backporting the test fixes is more work than just a simple code copy,
  since there are additional differences/changes needed in the older
  version of systemd (and python3). the failing/flaky tests in x have
  been like that forever, and people have just retried them; we can keep
  retrying them until x moves into ESM next year.

  [original description]

  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
    amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services  (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-smoke (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  logind (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  storage(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  upstream   (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFBFF.B.F.F..FFBF
  udev   (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  systemd-fsckd  (F 37% S  0% B 10% => P 50%/) 
BFFFB.FF...FB.F..B.
  root-unittests (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
    ppc64el
  tests-in-lxd   (F 25% S  0% B  0% => P 75%/) 
FFFFF.F.
  systemd-fsckd  (F 35% S  0% B  0% => P 65%/) 
FFF...FFFFF.F..F
  root-unittests (F  2% S  0% B  0% => P 97%/) 
..F.
    s390x
  tests-in-lxd   (F 52% S  0% B  0% => P 47%/) 
FFF.FFF.FF....F.
  timedated  (F  2% S  0% B  0% => P 97%/) 
...F
  upstream   (F 17% S  0% B  0% => P 82%/) 
.F..F.F.FFF...F.
  systemd-fsckd  (F 32% S  0% B

[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

2020-11-03 Thread Gunnar Hjalmarsson

@RussianNeuroMancer: This bug is closed, so please file a new bug if you
have found a new issue. OTOH, an issue with Linux 5.9 isn't reasonably
an Ubuntu bug yet. If you think there is a need to modify usb-modeswitch
to work with Linux 5.9, then I think it's best to start a new topic in
the upstream forum.

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

Title:
  usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

Status in usb-modeswitch package in Ubuntu:
  Fix Released

Bug description:
  Please refer to post of usb-modeswitch developer
  http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4&t=2827
  for complete issue description.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+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 1869881] Re: html file detected as unknown application/octet-stream

2020-11-03 Thread Matifou

Hi

I am still experiencing the problem! Creating a .whatever file, it opens
directly in gedit, using nautilus on a local drive. Doing exactly the
same using nautilus on a sftp, it will:

1) Complain file of unknown type
2) Clicking "select applications" will not suggest any default application, so 
need to click on View all Applications. Then selecting gedit will open once.
3) Not remember any choice, so every time I close gedit and try to reopen, 
problem 1) and 2)  occur.

When was the bug thought to be fixed? I have:

$nautilus --version: 
 GNOME nautilus 3.36.3
$apt list libglib2.0-bin 
 Listing... Done
 libglib2.0-bin/focal-updates,now 2.64.3-1~ubuntu20.04.1 amd64 
[installed,automatic]
 libglib2.0-bin/focal-updates 2.64.3-1~ubuntu20.04.1 i386

Thanks!

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

Title:
  html file detected as unknown application/octet-stream

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  On ubuntu 20.04, when I mount an sftp or ftp share with nautilus
  (1:3.36.1-1ubuntu1), html files are not detected. The properties
  dialog shows "Unknown (application/octet-stream)". Php, css and js
  files are right detected. It is a known bug?

  No problem with pcmanfm.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 31 14:59:58 2020
  InstallationDate: Installed on 2019-12-18 (103 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to focal on 2020-03-20 (10 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1869881/+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 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)

This bug was fixed in the package mutter - 3.38.1-2ubuntu1

---
mutter (3.38.1-2ubuntu1) groovy; urgency=medium

  * Merge with debian, including various upstream fixes. Remaining changes:
- debian/gbp.conf: update upstream branch to point to ubuntu/master
- debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  + X11: Add support for fractional scaling using Randr

mutter (3.38.1-2) unstable; urgency=medium

  * debian/patches: Wayland start Xwayland on public X11 sockets as well
(LP: #1897224)
  * debian/patches: Don't override window tile monitor (LP: #199)
  * debian/patches: Fix resizing issues (LP: #1878293)

 -- Marco Trevisan (Treviño)   Fri, 23 Oct 2020
12:43:24 +0200

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

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

Title:
  Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X
  display)

Status in Mutter:
  Unknown
Status in snapd:
  In Progress
Status in mutter package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Won't Fix
Status in mutter source package in Groovy:
  Fix Committed
Status in snapd source package in Groovy:
  Won't Fix
Status in mutter source package in Hirsute:
  Fix Released
Status in snapd source package in Hirsute:
  Won't Fix

Bug description:
  [Impact]

   * Users who select the Wayland session on Ubuntu 20.10 cannot run snap
     confined X11 applications, due to gnome-shell no longer listening on an
     abstract socket for connections.

   * The fix, which has been accepted into upstream's gnome-3-38 branch
     reverts the change removing the abstract socket, and fixes the bug that
     prompted it's removal:

 https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508

  [Test Case]

   * Start with a stock Ubuntu 20.10 desktop install.

   * At the GDM login screen, after selecting your user account use the gear
     icon to select the "Ubuntu on Wayland" session, and log in.

   * Ensure Chromium is installed by running "sudo snap install
  chromium".

   * Try to run "chromium" from the terminal.  Without the fix, it will fail
     with the error "Unable to open X display".  With the fix applied, it
     will launch as normal.

  [Regression Potential]

   * The patch modifies the logic gnome-shell uses to launch Xwayland.  So
     there is a potential that the change could break X11 application
     support on the Wayland session.

   * The default configuration for gnome-shell is to launch Xwayland on
     session start, so it should be immediately obvious if there are
     problems.

   * In addition to checking snapped X11 apps like Chromium, verify that a
     few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc).

  [Other Info]

   * Running "ss -xlp | grep Xwayland" should show that it is listening on
     both "/tmp/.X11-unix/X0" (the regular unix domain socket) and
     "@/tmp/.X11-unix/X0" (the abstract socket).

  ---
  I'm trying to run chromium installed via snap in Ubuntu 20.10 when running 
Ubuntu Wayland session. Unfortunately, chromium wouldn't start:

  > chromium
  [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to 
open X display.

  I am able to run Firefox just fine (assuming that Firefox still runs
  on xwayland) and also Intellij snap works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu47
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 25 09:45:16 2020
  InstallationDate: Installed on 2016-09-05 (1480 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Snap: chromium 85.0.4183.121 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897224/+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 1900009] Re: Window tiled to monitor where most of the window is in instead of where the mouse is.

This bug was fixed in the package mutter - 3.38.1-2ubuntu1

---
mutter (3.38.1-2ubuntu1) groovy; urgency=medium

  * Merge with debian, including various upstream fixes. Remaining changes:
- debian/gbp.conf: update upstream branch to point to ubuntu/master
- debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  + X11: Add support for fractional scaling using Randr

mutter (3.38.1-2) unstable; urgency=medium

  * debian/patches: Wayland start Xwayland on public X11 sockets as well
(LP: #1897224)
  * debian/patches: Don't override window tile monitor (LP: #199)
  * debian/patches: Fix resizing issues (LP: #1878293)

 -- Marco Trevisan (Treviño)   Fri, 23 Oct 2020
12:43:24 +0200

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

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

Title:
  Window tiled to monitor where most of the window is in instead of
  where the mouse is.

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Groovy:
  Invalid
Status in mutter source package in Groovy:
  Fix Committed

Bug description:
  Release: Ubuntu Groovy Gorilla (development branch) 20.10
  Package version: 3.38.1-1ubuntu1

  [ Impact ]

  When I tile windows using edge tiling, I want the window to tile on
  the same edge that I brought it to, however, if the window is mostly
  in monitor 1 when I try to tile it to the left (or right) edge of
  monitor 2, the window will tile to the left (or right) edge of monitor
  2.

  This happens on both my computer with an Nvidia GPU on x11 and my
  laptop using Intel integrated graphics on Wayland.

  [ Test case ]

  - In multi-monitor setup, grab a tile edge to the side where the other 
monitor is
  - The window should not be moved to the other monitor

  [ Regression potential ]

  Windows may be tiled to the wrong monitor once created

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/199/+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 1878293] Re: xterm resize is wonky

This bug was fixed in the package mutter - 3.38.1-2ubuntu1

---
mutter (3.38.1-2ubuntu1) groovy; urgency=medium

  * Merge with debian, including various upstream fixes. Remaining changes:
- debian/gbp.conf: update upstream branch to point to ubuntu/master
- debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  + X11: Add support for fractional scaling using Randr

mutter (3.38.1-2) unstable; urgency=medium

  * debian/patches: Wayland start Xwayland on public X11 sockets as well
(LP: #1897224)
  * debian/patches: Don't override window tile monitor (LP: #199)
  * debian/patches: Fix resizing issues (LP: #1878293)

 -- Marco Trevisan (Treviño)   Fri, 23 Oct 2020
12:43:24 +0200

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

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

Title:
  xterm resize is wonky

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in xterm package in Ubuntu:
  Invalid
Status in mutter source package in Groovy:
  Fix Committed
Status in xterm source package in Groovy:
  Invalid

Bug description:
  [ Impact ]

  When I try to resize an xterm window the same way,
  this happens instead: as the mouse is moved, the upper-right corner
  does move, but it doesn't track with the mouse pointer like it should.
  Meanwhile, the lower-left corner also moves (it should have remained anchored 
in its original x-y position on the screen).

  [ Test case ]

  - Start Xterm
  - Resize the window from its top/left corner
  - It should resize normally, and not act as shown in

https://gitlab.gnome.org/GNOME/mutter/uploads/3c19763b7748ce76b0ba2958cde7636b/Screencast_from_02-04-19_14_03_24.webm

  [ Regression potential ]

  Windows resizing might not work correctly

  ---

  % lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04 LTS
  Release:20.04
  Codename:   focal

  % wmctrl -m
  Name: GNOME Shell
  Class: N/A
  PID: N/A
  Window manager's "showing the desktop" mode: OFF

  Terms:
  window has four sides: top, bottom, left, and right
  when referring to corners, "upper" means "top", and "lower" means "bottom",
  so the four corners are upper-right, lower-right, lower-left, and  upper-left.
  wonky: works wrong, as detailed below ("cases that work wrong...")

  Description:

  I can resize a gnome-terminal window, everything works fine.
  (Grab it, using the mouse, by the upper-right corner (click-and-hold);
  the size changes as the mouse is moved, because the position
  of the upper-right corner follows the mouse.  (Only the upper-right corner 
moves.))
  But when I try to resize an xterm window the same way,
  this happens instead: as the mouse is moved, the upper-right corner
  does move, but it doesn't track with the mouse pointer like it should.
  Meanwhile, the lower-left corner also moves (it should have remained anchored 
in its original x-y position on the screen).

  Cases that work correctly:
  If the xterm window is grabbed by the lower-right corner and resized, this 
case works properly.
  If the xterm window is grabbed by the bottom edge and resized, this case 
works properly.
  If the xterm window is grabbed by the right edge and resized, this case works 
properly.

  Cases that work wrong ("wonky"):
  If the xterm window is grabbed by the left edge and resized, then the 
opposite (i.e. right) edge (incorrectly) migrates.
  If the xterm window is grabbed by the top edge and resized, then the opposite 
(i.e. bottom) edge (incorrectly) migrates.
  If the xterm window is grabbed by the upper-right corner and resized, then 
the window (incorrectly) migrates.
  If the xterm window is grabbed by the lower-left corner and resized, then the 
window (incorrectly) migrates.
  If the xterm window is grabbed by the upper-left corner and resized, then the 
window (incorrectly) migrates.

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: xterm 353-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue May 12 13:52:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant

[Desktop-packages] [Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

2020-11-03 Thread RussianNeuroMancer

*on Ubuntu 20.10 with Linux 5.8

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

Title:
  usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

Status in usb-modeswitch package in Ubuntu:
  Fix Released

Bug description:
  Please refer to post of usb-modeswitch developer
  http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4&t=2827
  for complete issue description.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+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 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

2020-11-03 Thread RussianNeuroMancer

Issue is no longer reproducible on Linux 5.8, although on 5.9 there is
regression: https://bugzilla.kernel.org/show_bug.cgi?id=209469

** Bug watch added: Linux Kernel Bug Tracker #209469
   https://bugzilla.kernel.org/show_bug.cgi?id=209469

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

Title:
  usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE

Status in usb-modeswitch package in Ubuntu:
  Fix Released

Bug description:
  Please refer to post of usb-modeswitch developer
  http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4&t=2827
  for complete issue description.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+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 1897965] Re: pulseaudio: Failed to load module "module-alsa-card" (No UCM verb is valid for hw:0)

2020-11-03 Thread Gannet

Sebastien Bacher (seb128), which exactly logs do you need? Maybe I could
upload them for you.

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

Title:
  pulseaudio: Failed to load module "module-alsa-card" (No UCM verb is
  valid for hw:0)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  No sound after login.

  $ LC_ALL=C systemctl --user status pulseaudio.service
  * pulseaudio.service - Sound Service
   Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Wed 2020-09-30 22:46:51 EEST; 8min ago
  TriggeredBy: * pulseaudio.socket
     Main PID: 1088 (pulseaudio)
   CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
   |-1088 /usr/bin/pulseaudio --daemonize=no --log-target=journal
   `-1126 /usr/libexec/pulse/gsettings-helper

  Sep 30 22:46:51 p5q3 systemd[1080]: Starting Sound Service...
  Sep 30 22:46:51 p5q3 pulseaudio[1088]: No UCM verb is valid for hw:0
  Sep 30 22:46:51 p5q3 systemd[1080]: Started Sound Service.
  Sep 30 22:46:52 p5q3 pulseaudio[1088]: Failed to load module 
"module-alsa-card" (argument: "device_id="1" name="pci-_01_00.1" 
card_name="alsa_card.pci-_01_00.1" namereg_fail=false tsched=yes 
fixed_laten>
  Sep 30 22:47:11 p5q3 pulseaudio[1088]: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': 
timed out (service_start_timeout=25000ms)

  Workaround found: 'pulseaudio -k' seems solves the problem, sound
  appears and working well, but some errors still present:

  $ LC_ALL=C systemctl --user status pulseaudio.service
  * pulseaudio.service - Sound Service
   Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Wed 2020-09-30 22:55:49 EEST; 7min ago
  TriggeredBy: * pulseaudio.socket
     Main PID: 12198 (pulseaudio)
   CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
   |-12198 /usr/bin/pulseaudio --daemonize=no --log-target=journal
   `-12212 /usr/libexec/pulse/gsettings-helper

  Sep 30 22:55:49 p5q3 systemd[1080]: Starting Sound Service...
  Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:1
  Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:0
  Sep 30 22:55:49 p5q3 systemd[1080]: Started Sound Service.
  Sep 30 22:56:14 p5q3 pulseaudio[12198]: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu11
  Uname: Linux 5.8.12-050812-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eugene 1088 F pulseaudio
    eugene 1092 F pipewire-media-
   /dev/snd/controlC1:  eugene 1092 F pipewire-media-
   /dev/snd/seq:eugene 1087 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Sep 30 22:50:58 2020
  InstallationDate: Installed on 2019-04-13 (536 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-09-06 (23 days ago)
  dmi.bios.date: 06/11/2010
  dmi.bios.release: 11.2
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd06/11/2010:br11.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1897965/+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 1896091] Re: [i915] Noise-like lines of graphics corruption when moving windows in Xorg sessions

2020-11-03 Thread Eric Mazoob

The problem goes away after the screen times out and I have to log back
in.

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

Title:
  [i915] Noise-like lines of graphics corruption when moving windows in
  Xorg sessions

Status in Mutter:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  I left my desktop (T480s thinkpad docked to ThinkVision P24h-10)
  unattended for a while, and then got the error message and now have
  funny lines on activity, e.g. red lines flashing on top of gnome-shell
  bar when switching windows, or white blocks/lines around typing text.

  This is the second or third time it happened, reboot fixes it until
  the error pops up again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-19-generic 5.8.0-19.20
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jak5052 F pulseaudio
   /dev/snd/controlC1:  jak5052 F pulseaudio
   /dev/snd/pcmC1D0p:   jak5052 F...m pulseaudio
   /dev/snd/controlC0:  jak5052 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Sep 17 19:14:11 2020
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (917 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-19-generic N/A
   linux-backports-modules-5.8.0-19-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2020
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET65W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:br1.42:efr1.20:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jak5052 F pulseaudio
   /dev/snd/controlC1:  jak5052 F pulseaudio
   /dev/snd/pcmC1D0p:   jak5052 F...m pulseaudio
   /dev/snd/controlC0:  jak5052 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (917 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-19-generic N/A
   linux-backports-modules-5.8.0-19-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 06/04/2020
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET65W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:br1.42:efr

[Desktop-packages] [Bug 1902446] Re: Not possible to see list of wifi networks

2020-11-03 Thread Vadim Peretokin

The usual gnome environment.

Not much in journalctl:

nov 03 22:59:57 volga audit[9670]: AVC apparmor="DENIED" operation="open" 
profile="snap.hiri.hiri" name="/home/vadi/.netrc" pid=9670 comm="hirimain" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
nov 03 22:59:57 volga kernel: audit: type=1400 audit(1604440797.544:5054): 
apparmor="DENIED" operation="open" profile="snap.hiri.hiri" 
name="/home/vadi/.netrc" pid=9670 comm="hirimain" requested_mask="r" denied_m>
nov 03 23:00:10 volga kernel: [UFW BLOCK] IN=wlp1s0 OUT= 
MAC=01:00:5e:00:00:01:08:26:97:d0:93:a0:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=55594 PROTO=2 
nov 03 23:00:42 volga kernel: [UFW BLOCK] IN=wlp1s0 OUT= 
MAC=01:00:5e:00:00:01:08:26:97:d0:93:a2:08:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=36 
TOS=0x00 PREC=0x00 TTL=1 ID=1 PROTO=2 
nov 03 23:00:43 volga kernel: [UFW BLOCK] IN=wlp1s0 OUT= 
MAC=01:00:5e:00:00:fb:92:d1:cf:19:a3:4c:08:00 SRC=192.168.1.226 DST=224.0.0.251 
LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
nov 03 23:00:50 volga audit[9649]: AVC apparmor="DENIED" operation="open" 
profile="snap.hiri.hiri" name="/home/vadi/.netrc" pid=9649 comm="BG" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
nov 03 23:00:50 volga kernel: audit: type=1400 audit(1604440850.353:5055): 
apparmor="DENIED" operation="open" profile="snap.hiri.hiri" 
name="/home/vadi/.netrc" pid=9649 comm="BG" requested_mask="r" denied_mask="r>
nov 03 23:00:50 volga audit[9649]: AVC apparmor="DENIED" operation="open" 
profile="snap.hiri.hiri" name="/home/vadi/.netrc" pid=9649 comm="BG" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
nov 03 23:00:50 volga kernel: audit: type=1400 audit(1604440850.577:5056): 
apparmor="DENIED" operation="open" profile="snap.hiri.hiri" 
name="/home/vadi/.netrc" pid=9649 comm="BG" requested_mask="r" denied_mask="r>
nov 03 23:00:50 volga audit[9649]: AVC apparmor="DENIED" operation="open" 
profile="snap.hiri.hiri" name="/home/vadi/.netrc" pid=9649 comm="BG" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
nov 03 23:00:50 volga kernel: audit: type=1400 audit(1604440850.701:5057): 
apparmor="DENIED" operation="open" profile="snap.hiri.hiri" 
name="/home/vadi/.netrc" pid=9649 comm="BG" requested_mask="r" denied_mask="r>
nov 03 23:00:51 volga audit[9649]: AVC apparmor="DENIED" operation="open" 
profile="snap.hiri.hiri" name="/home/vadi/.netrc" pid=9649 comm="Worker" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
nov 03 23:00:51 volga kernel: audit: type=1400 audit(1604440851.661:5058): 
apparmor="DENIED" operation="open" profile="snap.hiri.hiri" 
name="/home/vadi/.netrc" pid=9649 comm="Worker" requested_mask="r" denied_mas>
nov 03 23:01:11 volga kernel: [UFW BLOCK] IN=wlp1s0 OUT= 
MAC=01:00:5e:00:00:01:08:26:97:d0:93:a0:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=61275 PROTO=2 
nov 03 23:01:18 volga gnome-shell[3615]: 
../clutter/clutter/clutter-actor.c:10558: The clutter_actor_set_allocation() 
function can only be called from within the implementation of the 
ClutterActor::allocate() vir>
nov 03 23:01:21 volga systemd[2315]: Started Application launched by 
gsd-media-keys.
nov 03 23:01:21 volga systemd[2315]: Started VTE child process 69735 launched 
by x-terminal-emulator process 39586.
nov 03 23:01:21 volga systemd[2315]: 
gnome-launched-x-terminal-emulator-69726.scope: Succeeded.

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

Title:
  Not possible to see list of wifi networks

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Using the default 'light' theme, the network listing is impossible to
  read

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  1 19:41:38 2020
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-15 (1355 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

2020-11-03 Thread Brian Murray

Hello Leon, or anyone else affected,

Accepted network-manager into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.22.10-1ubuntu2.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-
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.

** Changed in: network-manager (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

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

Title:
  The network manager does not check the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  Invalid
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   In some cases, the wow is not configured and the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
  management of wake-on-LAN in NetworkManager).

   The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE 
bit.
   But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
   So, the management of wake-on-LAN still is done by NetworkManager.

   The killer 500s Wi-Fi does not want the network-manger to manager the
  wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set.
  (The driver will manager itself.) When the network-manager managers
  the wake-on-LAN, all of the Wi-Fi functions will be lost after the OS
  resumed from suspend.

  [Test Case]

   On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
   Step 1. Enter suspend (s2idle)
   Setp 2. Resume from suspend

   After resume from suspend, the Wi-Fi function still is normal.

   You can download the kernel and linux-firmware that backport the Qucalcomm's 
dirver fro focal from below link:
   https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633

  [Regression Potential]

   * This patch modifies the wake on lan parameters, please test that
  the corresponding feature still works fine with the different
  configuration values.

   1. Magic packet test:
    Set Wake on Wireless to off
    Send magic packet to the system
    Ensure it does not wake up

    Set Wake on Wirless to on
    Send magic packet to the system
    Ensure it does wake up

   2. Wi-Fi function test after resumed from suspend:
    After resume from suspend, the Wi-Fi should work normally.
    Scan APs.
    Connect to an AP.

  [Other Info]

   * platform: add the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE status
  check (!597) · Merge Requests · NetworkManager / NetworkManager ·
  GitLab -
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/597#note_588639

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1891632/+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 1902797] [NEW] zsys unable to save state since upgrade to 20.10

2020-11-03 Thread odror

Public bug reported:

Since the upgrade I did not have any state saved with zsys.

When typing

# /sbin/zsysctl  state save

I get the following error:
ERROR couldn't save state for user "root": user "root" doesn't exist 

Then I found out that the root pool was not mounted at boot.
I manually mounted it successfully. It did not fix the issue

#  lsb_release -rd
Description:Ubuntu 20.10
Release:20.10

# apt-cache policy zsys
zsys:
  Installed: 0.5.2
  Candidate: 0.5.2
  Version table:
 *** 0.5.2 500
500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zsys 0.5.2
ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
Uname: Linux 5.8.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset zfs zunicode zavl icp zcommon znvpair 
nvidia
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  3 13:47:04 2020
Grub.cfg: Error: [Errno 13] Permission denied: '/boot/grub/grub.cfg'
InstallationDate: Installed on 2020-03-15 (232 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/fish
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_mj0kfs@/vmlinuz-5.8.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_mj0kfs ro intel_iommu=on video=vesafb:off,efifb:off 
nvidia-drm.modeset=1 mitigations=off
RelatedPackageVersions:
 zfs-initramfs  0.8.4-1ubuntu11
 zfsutils-linux 0.8.4-1ubuntu11
SourcePackage: zsys
UpgradeStatus: Upgraded to groovy on 2020-10-23 (10 days ago)
ZFSListcache-bpool:
 bpool  /boot   off on  on  off on  off on  off 
-   none-   -   -   -   -   -   -   -
 bpool/BOOT noneoff on  on  off on  off on  
off -   none-   -   -   -   -   -   -   
-
 bpool/BOOT/ubuntu_mj0kfs   /boot   on  on  on  off on  
off on  off -   none-   -   -   -   -   
-   -   -

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


** Tags: amd64 apport-bug groovy

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

Title:
  zsys unable to save state since upgrade to 20.10

Status in zsys package in Ubuntu:
  New

Bug description:
  Since the upgrade I did not have any state saved with zsys.

  When typing

  # /sbin/zsysctl  state save

  I get the following error:
  ERROR couldn't save state for user "root": user "root" doesn't exist 

  Then I found out that the root pool was not mounted at boot.
  I manually mounted it successfully. It did not fix the issue

  #  lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  # apt-cache policy zsys
  zsys:
Installed: 0.5.2
Candidate: 0.5.2
Version table:
   *** 0.5.2 500
  500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: zsys 0.5.2
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset zfs zunicode zavl icp zcommon znvpair 
nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  3 13:47:04 2020
  Grub.cfg: Error: [Errno 13] Permission denied: '/boot/grub/grub.cfg'
  InstallationDate: Installed on 2020-03-15 (232 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/fish
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_mj0kfs@/vmlinuz-5.8.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_mj0kfs ro intel_iommu=on video=vesafb:off,efifb:off 
nvidia-drm.modeset=1 mitigations=off
  RelatedPackageVersions:
   zfs-initramfs  0.8.4-1ubuntu11
   zfsutils-linux 0.8.4-1ubuntu11
  SourcePackage: zsys
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (10 days ago)
  ZFSListcache-bpool:
   bpool/boot   off on  on  off on  off on  
off -   none-   -   -   -   -   -   -   
-
   bpool/BOOT   noneoff on  on  off on  off on  
off -   none-   -   -   -   -   -   -   
-
   bpool/BOOT/ubuntu_mj0kfs /boot   on  on  on  off on  
off on  off -   none-   -   -   -   -   
-   -   -

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

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

2020-11-03 Thread Joep Jaeger

I didn't upgrade to Ubuntu 20.10 at all Olivier, I'm still on Ubuntu
Mate 20.04.1. Maybe it came with an update? Thunderbird already was a
longer time just in English. But as far I know the problem started 27th
October, yes indeed.

Maybe also nice to know, when I didn't close the window displaying the
error, I got notification of  received new mails.

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

Title:
  thunderbird fails to open, xml parse error

Status in thunderbird package in Ubuntu:
  Confirmed

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

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

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

[Desktop-packages] [Bug 1902715] Re: Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

That's a valid question but if we knew what the issue was it would
probably be fixed. Did you try the workaround from the other bug to
switch to Default before going back to another value?

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

Title:
  Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

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

Bug description:
  I installed the Ubuntu version 20.04 LTS. I would like to change the
  alert sound. I followed these steps:

  1.Open the Activities overview and start typing Sound;
  2.Click on Sound to open the panel;
  3.In the Alert Sound section, select an alert sound.

  However, after choosing the preferred sound it does not change!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1902715/+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 1902715] Re: Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

2020-11-03 Thread Luiz Fernando Pinto de Oliveira

Thank you very much @Sebastien for the indication of the similar bug
(bug #1871320). The same problem is happening to me. How do I solve it?

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

Title:
  Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

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

Bug description:
  I installed the Ubuntu version 20.04 LTS. I would like to change the
  alert sound. I followed these steps:

  1.Open the Activities overview and start typing Sound;
  2.Click on Sound to open the panel;
  3.In the Alert Sound section, select an alert sound.

  However, after choosing the preferred sound it does not change!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1902715/+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 1902691] Re: package libreoffice-style-tango 1:6.4.6-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before

2020-11-03 Thread Banchory and District Men's Shed

Hi Heather,

I’ve never used or any aspect of LibreOffice, and I’d not previously heard
of Tango.  I think it was bundled with Ubuntu 20.04.  I’ll try the commands
you mention later this week.

Thank you for your prompt reply.

Best Regards,

Paul

On Tue, 3 Nov 2020 at 20:00, Heather Ellsworth <1902...@bugs.launchpad.net>
wrote:

> Thank you for reporting your bug to help make Ubuntu better!
>
> Can you tell me if you have this libreoffice-style-tango package installed?
> $ dpkg -l | grep libreoffice-style-tango
>
> If you do then I recommend uninstalling and reinstalling it.
> $ sudo apt-get remove --purge libreoffice-style-tango
> $ sudo apt install libreoffice-style-tango
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1902691
>
> Title:
>   package libreoffice-style-tango 1:6.4.6-0ubuntu0.20.04.1 failed to
>   install/upgrade: package is in a very bad inconsistent state; you
>   should  reinstall it before attempting configuration
>
> Status in libreoffice package in Ubuntu:
>   New
>
> Bug description:
>   This error occurred during an update
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 20.04
>   Package: libreoffice-style-tango 1:6.4.6-0ubuntu0.20.04.1
>   ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
>   Uname: Linux 5.4.0-52-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.10
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   Date: Tue Nov  3 11:26:18 2020
>   DpkgHistoryLog:
>Start-Date: 2020-11-03  11:25:47
>Commandline: aptdaemon role='role-commit-packages' sender=':1.81'
>Upgrade: gnome-control-center-data:amd64 (1:3.36.4-0ubuntu1,
> 1:3.36.4-0ubuntu2), gnome-control-center:amd64 (1:3.36.4-0ubuntu1,
> 1:3.36.4-0ubuntu2), libwbclient0:amd64 (2:4.11.6+dfsg-0ubuntu1.5,
> 2:4.11.6+dfsg-0ubuntu1.6), libgweather-3-16:amd64 (3.36.0-1,
> 3.36.1-1~ubuntu20.04.1), libgnome-bluetooth13:amd64 (3.34.1-1,
> 3.34.3-0ubuntu1), gnome-bluetooth:amd64 (3.34.1-1, 3.34.3-0ubuntu1),
> samba-libs:amd64 (2:4.11.6+dfsg-0ubuntu1.5, 2:4.11.6+dfsg-0ubuntu1.6),
> gir1.2-gweather-3.0:amd64 (3.36.0-1, 3.36.1-1~ubuntu20.04.1),
> gir1.2-gnomebluetooth-1.0:amd64 (3.34.1-1, 3.34.3-0ubuntu1),
> distro-info-data:amd64 (0.43ubuntu1.2, 0.43ubuntu1.4), libsmbclient:amd64
> (2:4.11.6+dfsg-0ubuntu1.5, 2:4.11.6+dfsg-0ubuntu1.6),
> gnome-control-center-faces:amd64 (1:3.36.4-0ubuntu1, 1:3.36.4-0ubuntu2),
> libgweather-common:amd64 (3.36.0-1, 3.36.1-1~ubuntu20.04.1), tzdata:amd64
> (2020a-0ubuntu0.20.04, 2020d-0ubuntu0.20.04)
>   DuplicateSignature:
>package:libreoffice-style-tango:1:6.4.6-0ubuntu0.20.04.1
>Setting up distro-info-data (0.43ubuntu1.4) ...
>dpkg: error processing package libreoffice-style-tango (--configure):
> package is in a very bad inconsistent state; you should
>   ErrorMessage: package is in a very bad inconsistent state; you should
> reinstall it before attempting configuration
>   InstallationDate: Installed on 2020-09-30 (33 days ago)
>   InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
> (20200731)
>   PackageArchitecture: all
>   Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal,
> 3.8.2-0ubuntu2
>   PythonDetails: N/A
>   RelatedPackageVersions:
>dpkg 1.19.7ubuntu3
>apt  2.0.2ubuntu0.1
>   SourcePackage: libreoffice
>   Title: package libreoffice-style-tango 1:6.4.6-0ubuntu0.20.04.1 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)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1902691/+subscriptions
>

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

Title:
  package libreoffice-style-tango 1:6.4.6-0ubuntu0.20.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libreoffice package in Ubuntu:
  New

Bug description:
  This error occurred during an update

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-style-tango 1:6.4.6-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Nov  3 11:26:18 2020
  DpkgHistoryLog:
   Start-Date: 2020-11-03  11:25:47
   Commandline: aptdaemon role='role-commit-packages' sender=':1.81'
   Upgrade: gnome-control-center-data:amd64 (1:3.36.4-0ubuntu1, 
1:3.36.4-0ubuntu2), gnome-control-center:amd64 (1:3.36.4-0ubuntu1, 
1:3.36.4-0ubuntu2), libwbclient0:amd64 (2:4.11.6+dfsg-0ubuntu1.5, 
2:4.11.6+dfsg-0ubuntu1.6), libgweather-3-16:amd64 (3.36.0-1, 
3.36.1-1~ubuntu20.04.1), libgnome-bluetooth13:amd64

[Desktop-packages] [Bug 1902715] Re: Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

sounds somewhat similar to bug #1871320

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

Title:
  Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

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

Bug description:
  I installed the Ubuntu version 20.04 LTS. I would like to change the
  alert sound. I followed these steps:

  1.Open the Activities overview and start typing Sound;
  2.Click on Sound to open the panel;
  3.In the Alert Sound section, select an alert sound.

  However, after choosing the preferred sound it does not change!

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

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

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

2020-11-03 Thread Olivier Tilloy

Thanks for the info Joep, and glad to know this worked around the
problem.

So in your case the the Dutch langpack was added to your profile
directory on the 27th of October, at 18:44 local time. Do you remember
when you upgraded to Ubuntu 20.10 ? Does this timestamp correspond to
the first time you launched thunderbird after upgrading, by any chance?

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

Title:
  thunderbird fails to open, xml parse error

Status in thunderbird package in Ubuntu:
  Confirmed

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

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

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

[Desktop-packages] [Bug 1902596] Re: VPN doesn't connect automatically

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 1902596

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

Could you also add the 'journalctl -b 0' log of a session showing the
issue?

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  VPN doesn't connect automatically

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I have set up my Network Connections manager to automatically connect
  to my VPN.  My VPN is saved with its credentials.  When I first log in
  (newly started, rebooted or woken from sleep/suspend), the VPN doesn't
  connect on its own.

  It sometimes doesn't connect at all, and sometimes it tells me that
  the VPN requires a password.  I haven't noticed a pattern.

  Description:  Ubuntu 20.10
  Release:  20.10

  network-manager:
Installed: 1.26.2-1ubuntu1
Candidate: 1.26.2-1ubuntu1
Version table:
   *** 1.26.2-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902596/+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 1902563] Re: Phone icon keeps flashing on random times on the dock mounting and unmounting the device

Weird, so the mount error stopped when disabling the option? Do you get
the issue if you enable the option again?

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Phone icon keeps flashing on random times on the dock mounting and
  unmounting the device

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

Bug description:
  Ubuntu desktop 20.04.1 all up to date @ 2/11/2020

  When plugging my BQ aquaris 4.5 over usb, the phone icon keeps flashing
  on random times on the dock mounting and unmounting the device

  probably a regression bug of:

  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865300

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  2 19:20:49 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-14 (233 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1902563/+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 1902787] [NEW] package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia

2020-11-03 Thread Juan Bernardo Albaitero Rosale P.

Public bug reported:

after updating from ubuntu 18.04 to 20.04 and trying to install nvidia
340 on the other drives i got the crash, now only have access to the
x.orgx server and not allowed to select any of the nvidia proprietary
drivers.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-340 (not installed)
ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Nov  3 12:14:58 2020
ErrorMessage: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que 
está también en el paquete nvidia-kernel-common-390 390.138-0ubuntu0.20.04.1
InstallationDate: Installed on 2020-10-30 (3 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-340 (not installed) failed to install/upgrade: intentando 
sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el 
paquete nvidia-kernel-common-390 390.138-0ubuntu0.20.04.1
UpgradeStatus: Upgraded to focal on 2020-11-03 (0 days ago)

** Affects: nvidia-graphics-drivers-340 (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 nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1902787

Title:
  package nvidia-340 (not installed) failed to install/upgrade:
  intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está
  también en el paquete nvidia-kernel-common-390
  390.138-0ubuntu0.20.04.1

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

Bug description:
  after updating from ubuntu 18.04 to 20.04 and trying to install nvidia
  340 on the other drives i got the crash, now only have access to the
  x.orgx server and not allowed to select any of the nvidia proprietary
  drivers.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Nov  3 12:14:58 2020
  ErrorMessage: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', 
que está también en el paquete nvidia-kernel-common-390 390.138-0ubuntu0.20.04.1
  InstallationDate: Installed on 2020-10-30 (3 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: 
intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también 
en el paquete nvidia-kernel-common-390 390.138-0ubuntu0.20.04.1
  UpgradeStatus: Upgraded to focal on 2020-11-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1902787/+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 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties

2020-11-03 Thread Michael Nazzareno Trimarchi

debdiff show the difference between the 18.04 ubuntu. In the 20.04 wpa
supplicant was bump to newer version so station attribute was added in
the right way

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

Title:
  Broken dbus GetAll message to wpa supplicant interface properties

Status in wpa package in Ubuntu:
  New

Bug description:
  dbus-send is able to read the properties of interface using GetAll. Those 
information include interface name, status, encryption method, etc. 
  The regression was introduced when someone try to have the Station attribute 
supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899262/+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 1902367] Re: Dock does not allow icons drag on free space

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Dock does not allow icons drag on free space

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

Bug description:
  Ubuntu desktop 20.04.1 up to date to latest @ 31/10/2020 with kernel
  5.4.0-52-generic

  The dock does not allow dragging new icons on the free space of the dock
  only allows to add in between 2 other icons or when the dock is full with 
icons it allows adding after the last one.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 31 14:40:09 2020
  InstallationDate: Installed on 2020-03-14 (230 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1902367/+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 1902001] Re: USB keyboard layout incorrect after unplugging and replugging

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

** This bug has been marked a duplicate of bug 1899509
   Mouse/touchpad settings not applied on hotplug/reconnect

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

Title:
  USB keyboard layout incorrect after unplugging and replugging

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-input-evdev package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel version: 5.4.0-52-generic (but problem began with 5.4.0-51-generic)
  Keyboard:   Bus 001 Device 018: ID 056e:1063 Elecom Co., Ltd ELECOM 
TK-FCP097

  Expected behaviour:
  USB keyboard layout remains the same when unplugging and replugging in same 
keyboard
  (This was the behaviour on 5.4.0-48-generic and earlier.)

  What happened instead:
  USB keyboard layout changes from:
  < _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us,jp,us,us", ",,intl,", 
"grp_led:scroll"

  to:
  > _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us,us", ",intl", 
"grp:alt_shift_toggle,grp_led:scroll"
  (output of xprop -root | grep XKB )

  The keyboard layout is reset to the correct layout after logging out
  and back in (or after suspend/resume); however, unplugging and
  replugging the keyboard in causes the same unexpected behaviour.

  Same problem occurs with a different USB keyboard: Bus 001 Device 019:
  ID 0d62:8070 Darfon Electronics Corp. ELECOM Wired Keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler 18578 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 29 16:35:31 2020
  InstallationDate: Installed on 2020-02-05 (266 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Latitude 5500
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=fa5c4fdb-0e37-4ef5-b109-3c129736f66c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-12 (170 days ago)
  dmi.bios.date: 07/06/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.1:bd07/06/2020:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902001/+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 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties

2020-11-03 Thread Michael Nazzareno Trimarchi

Are you using ubuntu 18.04? or are you using Focal Fossa?

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

Title:
  Broken dbus GetAll message to wpa supplicant interface properties

Status in wpa package in Ubuntu:
  New

Bug description:
  dbus-send is able to read the properties of interface using GetAll. Those 
information include interface name, status, encryption method, etc. 
  The regression was introduced when someone try to have the Station attribute 
supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899262/+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 1902446] Re: Not possible to see list of wifi networks

Thank you for your bug report. What desktop environement do you use? Could you 
add your 'journalctl -b 0' after getting the issue?
THe theme frame doesn't seem to be a 'light' one

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  Not possible to see list of wifi networks

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Using the default 'light' theme, the network listing is impossible to
  read

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  1 19:41:38 2020
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-15 (1355 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902446/+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 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Thank you for your bug report, could you report the issue upstream on
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues ?

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

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

Title:
  [Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After logging in, only a dummy device is available for audio playback
  (resulting in no audible playback). When running "pactl load-module
  module-detect" the sound card shows up, and playback works as
  expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio -k".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 28 17:21:02 2020
  InstallationDate: Installed on 2020-10-23 (4 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UDCTO1WW
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1901922/+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 1899435] Re: laptop (docked w/ lid closed) suspends after login

The bug was still incomplete because triagers are busy and no-one got to
review it again

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

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

Title:
  laptop (docked w/ lid closed) suspends after login

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

Bug description:
  I installed 20.04 on my Thinkpad T440p laptop (previously 18.04). As
  with 18.04 I boot up the laptop with it docked and with the lid
  closed, however with 20.04 something new happens right after user
  login ... the laptop goes into suspend and has to be woken up by
  pressing the power button on the dock. This behavior is new and did
  not happen with 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-settings-daemon 3.36.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 12 09:32:53 2020
  InstallationDate: Installed on 2020-09-22 (19 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1899435/+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 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties

Thanks, I tried d-feet earlier but it gives an accesserror, it works
using sudo though. The call on the interface seems successful here
though so I can't confirm the bug

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

Title:
  Broken dbus GetAll message to wpa supplicant interface properties

Status in wpa package in Ubuntu:
  New

Bug description:
  dbus-send is able to read the properties of interface using GetAll. Those 
information include interface name, status, encryption method, etc. 
  The regression was introduced when someone try to have the Station attribute 
supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899262/+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 1893300] Re: The status of cups still shows idle when the printer has been unplugged

** Changed in: system-config-printer (Ubuntu)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

** Changed in: system-config-printer (Ubuntu)
   Importance: Undecided => High

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

Title:
  The status of cups still shows idle when the printer has been
  unplugged

Status in OEM Priority Project:
  In Progress
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  [ Impact ]
  After printers (non-ippusb protocal) have been disconnected, the status of 
cups still shows "idle" instead of "disabled", so seems the disconnected 
procedure hasn't worked well.

  [ Test Case ]
  1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 
20.04 machine
  2. Wait for the status of cups became "Idle" (lpstat -p)
  3. Unplug the cable of the printer
  4. Check the status of cups again. (lpstat -p)

  [Expected result]
  The status should show disabled.

  [Actual result]
  The status shows idle.

  [info]
  Target:
  HP LaserJet Pro203dw
  HP Officejet 100 Mobile Printer
  HP Officeject 200 Mobile Printer
  Brother HL-2250DN
  Samsung ML-331x

  Upstream Bug: https://github.com/OpenPrinting/system-config-
  printer/issues/182

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1893300

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893300/+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 1902783] [NEW] Super key is not working

2020-11-03 Thread Umair Iqbal

Public bug reported:

Ubuntu supper key is not working

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME-Classic:GNOME
Date: Wed Nov  4 00:55:53 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-07-22 (104 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Super key is not working

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu supper key is not working

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Wed Nov  4 00:55:53 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-22 (104 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902783/+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 1883457] Re: Thumbnails for .xcf files only show in Gimp ( snap ) and nowhere else.

It's not a problem to be resolved in the different applications that are
loading thumbnails, snapd should resolve that usecase by making those
write to a location used by the system

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

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

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

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

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

Title:
  Thumbnails for .xcf files only show in Gimp ( snap ) and nowhere else.

Status in gimp package in Ubuntu:
  New
Status in gnome-xcf-thumbnailer package in Ubuntu:
  New
Status in gthumb package in Ubuntu:
  Invalid
Status in nautilus package in Ubuntu:
  Invalid
Status in nemo package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  New

Bug description:
  Hi,

  On Ubuntu ( Budgie ) 20.04 when using Gimp as a snap, you’ll see
  thumbnails for .xcf files only « inside » Gimp and nowhere else (
  Nemo, Nautilus, gThumb… )

  I did a messy workaround for .xcf thumbnails to appear anywhere
  expected : I put all of my user’s thumbnails into
  ~/snap/gimp/common/.cache/thumbnails/ and now ~/.cache/thumbnails/ is
  a symlink targeting the first.

  You’d agree it’s absolutely a bad idea to store all of an user’s
  thumbnails into a particular subfolder of a particular snap.

  How tell my session to look for thumbnails not only in
  ~/.cache/thumbnails/ but also in any thumbnails folder inside ~/snap/
  ?

  For references :
  ⋅ 
https://askubuntu.com/questions/1250031/gimp-snap-and-thumbnails-for-xcf-files
  ⋅ 
https://discourse.ubuntubudgie.org/t/gimp-as-a-snap-no-thumbnails-for-xcf-files-in-nemo-gthumb/3799
  ⋅ 
https://forum.snapcraft.io/t/gimp-and-thumbnails-for-xcf-files/18131/3?u=coeur-noir
  ⋅ https://forum.ubuntu-fr.org/viewtopic.php?id=2053949

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1883457/+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 1879580] Re: Screencast interface missing

The option to be enabled would require pipewire to be moved to main (the list 
of officially supported packaged), it's waiting for a security review at the 
moment
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533

The issue has been considered lower priority because pipewire is still
not considered stable nor tested enough to be default and most of Ubuntu
users are on x11 which doesn't need it.

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

Title:
  Screencast interface missing

Status in xdg-desktop-portal package in Ubuntu:
  Confirmed

Bug description:
  The `org.freedesktop.portal.ScreenCast` inferface is missing in the
  version shipped with Ubuntu 20.04.

  This interface is needed for OBS no work in non-X11 environments.

  Further reading:
  
https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus-org.freedesktop.portal.ScreenCast

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1879580/+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 1842886] Re: Yaru-dark shell menus and dialogs are not dark

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

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

Title:
  Yaru-dark shell menus and dialogs are not dark

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When you selected a dark application theme, the gnome-shell top bar
  menus used to also switch to match the theme (ie light text on a dark
  background) - eg see the screenshot showing the top-bar calendar at
  https://micheleg.github.io/dash-to-dock/news/2015/03/01/approaching-
  gnome-3.16.html).

  This is no longer the case - see attached screenshot for yark-dark.
  It's the same with adwaita-dark.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.33.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  5 16:01:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (65 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842886/+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 1667992] Re: ctrl-c sometimes causes wayland session to exit

Is anyone still, is anyone still seeing that issue in recent Ubuntu
versions? If so could you add your 'journalctl -b 0' log after seeing
the issue?

@Guilhem, what ubuntu version do you use? Do you get the issue if you
log out from the other session using the UI rather than the command you
described?

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

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

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

Title:
  ctrl-c sometimes causes wayland session to exit

Status in gnome-session package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.10; gnome-session 3.20.2-1ubuntu7; Gnome on Wayland.
  Ctrl-C should copy text; sometimes instead kills Gnome session.

  Sometimes, when I try to copy, I get logged out (presumably due to
  this combination being interpreted as SIGINT by Gnome).

  Unfortunately, I'm having trouble reliably reproducing this bug. It
  doesn't seem to happen if one copy has been done already (can't
  confirm though), however I can successfully copy immediately after
  logging in again. Even then, though, it doesn't always happen after
  first login, and many days it never happens at all.

  I don't even know if it happens when any application is focused
  (mostly because I only really use Chrome and the terminal in day-to-
  day operation), though I note that it's never happened when I've used
  that combination to interrupt another program under Gnome Terminal
  (not to say it can't happen though, I don't do that very often).

  Due to the difficulty in reproducing, I've yet to determine if it's
  even specifically a part of this package (though it seems a good place
  to start).

  I'll try remember to provide updates if I notice any other behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1667992/+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 1902691] Re: package libreoffice-style-tango 1:6.4.6-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at

2020-11-03 Thread Heather Ellsworth

Thank you for reporting your bug to help make Ubuntu better!

Can you tell me if you have this libreoffice-style-tango package installed?
$ dpkg -l | grep libreoffice-style-tango

If you do then I recommend uninstalling and reinstalling it.
$ sudo apt-get remove --purge libreoffice-style-tango
$ sudo apt install libreoffice-style-tango

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

Title:
  package libreoffice-style-tango 1:6.4.6-0ubuntu0.20.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libreoffice package in Ubuntu:
  New

Bug description:
  This error occurred during an update

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-style-tango 1:6.4.6-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Nov  3 11:26:18 2020
  DpkgHistoryLog:
   Start-Date: 2020-11-03  11:25:47
   Commandline: aptdaemon role='role-commit-packages' sender=':1.81'
   Upgrade: gnome-control-center-data:amd64 (1:3.36.4-0ubuntu1, 
1:3.36.4-0ubuntu2), gnome-control-center:amd64 (1:3.36.4-0ubuntu1, 
1:3.36.4-0ubuntu2), libwbclient0:amd64 (2:4.11.6+dfsg-0ubuntu1.5, 
2:4.11.6+dfsg-0ubuntu1.6), libgweather-3-16:amd64 (3.36.0-1, 
3.36.1-1~ubuntu20.04.1), libgnome-bluetooth13:amd64 (3.34.1-1, 
3.34.3-0ubuntu1), gnome-bluetooth:amd64 (3.34.1-1, 3.34.3-0ubuntu1), 
samba-libs:amd64 (2:4.11.6+dfsg-0ubuntu1.5, 2:4.11.6+dfsg-0ubuntu1.6), 
gir1.2-gweather-3.0:amd64 (3.36.0-1, 3.36.1-1~ubuntu20.04.1), 
gir1.2-gnomebluetooth-1.0:amd64 (3.34.1-1, 3.34.3-0ubuntu1), 
distro-info-data:amd64 (0.43ubuntu1.2, 0.43ubuntu1.4), libsmbclient:amd64 
(2:4.11.6+dfsg-0ubuntu1.5, 2:4.11.6+dfsg-0ubuntu1.6), 
gnome-control-center-faces:amd64 (1:3.36.4-0ubuntu1, 1:3.36.4-0ubuntu2), 
libgweather-common:amd64 (3.36.0-1, 3.36.1-1~ubuntu20.04.1), tzdata:amd64 
(2020a-0ubuntu0.20.04, 2020d-0ubuntu0.20.04)
  DuplicateSignature:
   package:libreoffice-style-tango:1:6.4.6-0ubuntu0.20.04.1
   Setting up distro-info-data (0.43ubuntu1.4) ...
   dpkg: error processing package libreoffice-style-tango (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2020-09-30 (33 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: libreoffice
  Title: package libreoffice-style-tango 1:6.4.6-0ubuntu0.20.04.1 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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1902691/+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 1897965] Re: pulseaudio: Failed to load module "module-alsa-card" (No UCM verb is valid for hw:0)

2020-11-03 Thread qwe

I don't have any 'pipewire' installed. Sound gradually fades away when
starting any sound (e.g. youtube). Headphones and built-in mic doesn't
work. Ubuntu 20.04.

> LC_ALL=C systemctl --user status pulseaudio.service
* pulseaudio.service - Sound Service
 Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Tue 2020-11-03 20:36:27 CET; 6min ago
TriggeredBy: * pulseaudio.socket
   Main PID: 23743 (pulseaudio)
 CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
 `-23743 /usr/bin/pulseaudio --daemonize=no --log-target=journal

Nov 03 20:36:26 acer systemd[1258]: Starting Sound Service...
Nov 03 20:36:26 acer pulseaudio[23743]: No UCM verb is valid for hw:0
Nov 03 20:36:27 acer systemd[1258]: Started Sound Service.

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

Title:
  pulseaudio: Failed to load module "module-alsa-card" (No UCM verb is
  valid for hw:0)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  No sound after login.

  $ LC_ALL=C systemctl --user status pulseaudio.service
  * pulseaudio.service - Sound Service
   Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Wed 2020-09-30 22:46:51 EEST; 8min ago
  TriggeredBy: * pulseaudio.socket
     Main PID: 1088 (pulseaudio)
   CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
   |-1088 /usr/bin/pulseaudio --daemonize=no --log-target=journal
   `-1126 /usr/libexec/pulse/gsettings-helper

  Sep 30 22:46:51 p5q3 systemd[1080]: Starting Sound Service...
  Sep 30 22:46:51 p5q3 pulseaudio[1088]: No UCM verb is valid for hw:0
  Sep 30 22:46:51 p5q3 systemd[1080]: Started Sound Service.
  Sep 30 22:46:52 p5q3 pulseaudio[1088]: Failed to load module 
"module-alsa-card" (argument: "device_id="1" name="pci-_01_00.1" 
card_name="alsa_card.pci-_01_00.1" namereg_fail=false tsched=yes 
fixed_laten>
  Sep 30 22:47:11 p5q3 pulseaudio[1088]: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': 
timed out (service_start_timeout=25000ms)

  Workaround found: 'pulseaudio -k' seems solves the problem, sound
  appears and working well, but some errors still present:

  $ LC_ALL=C systemctl --user status pulseaudio.service
  * pulseaudio.service - Sound Service
   Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Wed 2020-09-30 22:55:49 EEST; 7min ago
  TriggeredBy: * pulseaudio.socket
     Main PID: 12198 (pulseaudio)
   CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
   |-12198 /usr/bin/pulseaudio --daemonize=no --log-target=journal
   `-12212 /usr/libexec/pulse/gsettings-helper

  Sep 30 22:55:49 p5q3 systemd[1080]: Starting Sound Service...
  Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:1
  Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:0
  Sep 30 22:55:49 p5q3 systemd[1080]: Started Sound Service.
  Sep 30 22:56:14 p5q3 pulseaudio[12198]: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu11
  Uname: Linux 5.8.12-050812-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eugene 1088 F pulseaudio
    eugene 1092 F pipewire-media-
   /dev/snd/controlC1:  eugene 1092 F pipewire-media-
   /dev/snd/seq:eugene 1087 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Sep 30 22:50:58 2020
  InstallationDate: Installed on 2019-04-13 (536 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-09-06 (23 days ago)
  dmi.bios.date: 06/11/2010
  dmi.bios.release: 11.2
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsIn

[Desktop-packages] [Bug 1635803] Re: dragging file with middle mouse button doesn't show "Copy/Move/Link" context menu

** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #1512
   https://gitlab.gnome.org/GNOME/gtk/-/issues/1512

** Project changed: nautilus => gtk

** Changed in: gtk
   Importance: Medium => Unknown

** Changed in: gtk
   Status: Invalid => Unknown

** Changed in: gtk
 Remote watch: GNOME Bug Tracker #772797 => gitlab.gnome.org/GNOME/gtk/-/issues 
#1512

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

Title:
  dragging file with middle mouse button doesn't show "Copy/Move/Link"
  context menu

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  middle mouse a file, drag and drop it used to bring out a copy, move, etc 
dialog. This is now missing in 16.10.
  Can we please have this back, and an option to make the shortcut using 
rightclick + drag would be an improvement also.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct 22 19:14:18 2016
  InstallationDate: Installed on 2016-10-14 (8 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1635803/+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 1902715] Re: Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

2020-11-03 Thread Luiz Fernando Pinto de Oliveira

What desktop environment do you use?
R -> I am using the GNOME version 3.36.3 in Ubuntu 20.04. 

how do you test if it changed?
I use the terminal. I simply open the terminal and press the Tab key. And for 
example, I chose the "Sonar" alert sound, but I always hear the "Drip" sound.

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

Title:
  Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

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

Bug description:
  I installed the Ubuntu version 20.04 LTS. I would like to change the
  alert sound. I followed these steps:

  1.Open the Activities overview and start typing Sound;
  2.Click on Sound to open the panel;
  3.In the Alert Sound section, select an alert sound.

  However, after choosing the preferred sound it does not change!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1902715/+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 1902715] Re: Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

Thank you for your bug report. What desktop environment do you use? When
you say 'doesn't change', how do you test if it changed? do you mean
that the UI isn't showing the new one as selected? or that some sound is
not the one expected, if so could you give details on the sound and how
you get it played?

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

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

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

Title:
  Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

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

Bug description:
  I installed the Ubuntu version 20.04 LTS. I would like to change the
  alert sound. I followed these steps:

  1.Open the Activities overview and start typing Sound;
  2.Click on Sound to open the panel;
  3.In the Alert Sound section, select an alert sound.

  However, after choosing the preferred sound it does not change!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1902715/+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 1902715] Re: Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

2020-11-03 Thread Paul White

** Package changed: ubuntu => gnome-control-center (Ubuntu)

** Tags added: focal

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

Title:
  Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

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

Bug description:
  I installed the Ubuntu version 20.04 LTS. I would like to change the
  alert sound. I followed these steps:

  1.Open the Activities overview and start typing Sound;
  2.Click on Sound to open the panel;
  3.In the Alert Sound section, select an alert sound.

  However, after choosing the preferred sound it does not change!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1902715/+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 1898905] Re: Unfunctional plustek scanner in Ubuntu 20.10

2020-11-03 Thread Brian Murray

Hello mrvanes, or anyone else affected,

Accepted sane-backends into groovy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/sane-
backends/1.0.31-2ubuntu0.20.10 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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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: sane-backends (Ubuntu Groovy)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-groovy

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

Title:
  Unfunctional plustek scanner in Ubuntu 20.10

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Groovy:
  Fix Committed
Status in sane-backends package in Debian:
  Unknown

Bug description:
  * Impact

  The plustek driver isn't working in 20.10

  * Test case

  Try doing a copy of a document on a plustek based device

  * Regression potential

  The locking option was disabled until 20.10, the locking code relies
  on a lock directory to exist in /var/lock but that location is not
  persitant which means the locking can't work. Debian has turned the
  option off again, we are going the same in the SRU because it's safer
  than trying to fix an option that never got properly tested. There is
  special verification to do, just check that plustek and other devices
  are working correctly.

  -

  There are multiple reports now of failing plustek backend in libsane
  1.0.31-2 as shipped in Ubuntu 20.10 and Debian dev

  My report:
  https://gitlab.com/sane-project/backends/-/issues/363

  Another report:
  https://gitlab.com/sane-project/backends/-/issues/360

  Debian bug report:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971584

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1898905/+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 1902715] [NEW] Change alert sound ubuntu not working (Ubuntu 20.04 LTS)