date:20201104

Thanks. It looks like your Firefox is configured to use client-side
decorations. That makes this a pure Firefox bug since it would be
responsible for rendering everything.

** No longer affects: xorg-server (Ubuntu)

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

Title:
  Scaling one monitor (to 1.5x in my case) can cause Firefox to lose
  window features (titlebar, buttons, bookmark bar)

Status in firefox package in Ubuntu:
  New

Bug description:
  One monitor is a 4K monitor scaled to 1.5x, the other is a normal
  1920x1080 monitor scaled to 1x.

  While Firefox is already open, after logging in with the lock screen,
  or modifying display settings, sometimes Firefox will lose the
  titlebar, address bar, buttons, and bookmark bar. The website being
  displayed will still show, however not all features are usable (right
  click menu, mouse icon doesn't change).

  Reproduction steps:

  - Change zoom level of one or more monitors to >1.0 but less than 2.0 (have 
not tested with non-fractional zooms)
  - Open Firefox and browse to any website
  - Lock screen or leave computer alone until the screen locks.
  - Login
  - Firefox may have lost the window chrome

  Workaround:

  - Open Display Settings
  - Change display settings or zoom level, then change back.

  Computer info:

  - Ubuntu 20.04.1
  - Fractional Scaling enabled
  - NVidia GeForce GTX 1080/PCIe/SSE2
  - Gnome 3.36.3
  - X11
  - Samsung LU32J590 4K (3840x2160) @ 1.5x
  - Dell E2416Hb 1920x1080 rotated portrait left, right of Samsung

  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.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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  435.21  Sun Aug 25 08:17:57 
CDT 2019
   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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 09:31:17 2020
  DistUpgraded: 2020-04-03 12:51:44,815 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6188]
  InstallationDate: Installed on 2018-04-28 (920 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  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-52-generic 
root=UUID=dfb5d6fd-4a4e-471d-bb00-77a6729533d8 ro quiet splash pci=nommconf 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-03 (214 days ago)
  dmi.bios.date: 04/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.80
  dmi.board.name: X99 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.80:bd04/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  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 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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:

[Desktop-packages] [Bug 1902921] Re: Scaling one monitor (to 1.5x in my case) can cause Firefox to lose window features (titlebar, buttons, bookmark bar)

Here's another image with the windows showing in alt-tab mode (whatever
that's called - pressed Super button once).

** Attachment added: "Screenshot_2020-11-04_22-54-59.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1902921/+attachment/5431403/+files/Screenshot_2020-11-04_22-54-59.png

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

Title:
  Scaling one monitor (to 1.5x in my case) can cause Firefox to lose
  window features (titlebar, buttons, bookmark bar)

Status in firefox package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  One monitor is a 4K monitor scaled to 1.5x, the other is a normal
  1920x1080 monitor scaled to 1x.

  While Firefox is already open, after logging in with the lock screen,
  or modifying display settings, sometimes Firefox will lose the
  titlebar, address bar, buttons, and bookmark bar. The website being
  displayed will still show, however not all features are usable (right
  click menu, mouse icon doesn't change).

  Reproduction steps:

  - Change zoom level of one or more monitors to >1.0 but less than 2.0 (have 
not tested with non-fractional zooms)
  - Open Firefox and browse to any website
  - Lock screen or leave computer alone until the screen locks.
  - Login
  - Firefox may have lost the window chrome

  Workaround:

  - Open Display Settings
  - Change display settings or zoom level, then change back.

  Computer info:

  - Ubuntu 20.04.1
  - Fractional Scaling enabled
  - NVidia GeForce GTX 1080/PCIe/SSE2
  - Gnome 3.36.3
  - X11
  - Samsung LU32J590 4K (3840x2160) @ 1.5x
  - Dell E2416Hb 1920x1080 rotated portrait left, right of Samsung

  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.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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  435.21  Sun Aug 25 08:17:57 
CDT 2019
   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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 09:31:17 2020
  DistUpgraded: 2020-04-03 12:51:44,815 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6188]
  InstallationDate: Installed on 2018-04-28 (920 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  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-52-generic 
root=UUID=dfb5d6fd-4a4e-471d-bb00-77a6729533d8 ro quiet splash pci=nommconf 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-03 (214 days ago)
  dmi.bios.date: 04/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.80
  dmi.board.name: X99 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.80:bd04/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  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 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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

[Desktop-packages] [Bug 1773502] Re: High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's Resources tab

** Also affects: gnome-system-monitor (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-system-monitor (Ubuntu)
   Status: New => Triaged

** Changed in: gnome-system-monitor (Ubuntu)
   Importance: Undecided => Low

** Tags added: groovy

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

Title:
  High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's
  Resources tab

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-system-monitor package in Ubuntu:
  Triaged

Bug description:
  gnome-shell or X.org using high cpu
  My fanless nettop use a Intel Celeron 847 CPU. On around 1 boot on 3, the CPU 
of one core is kept at 100 % by a process, this high CPU usage start few second 
after the boot. It seems related to the graphical system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 09:52:20 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2018-04-29 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2018-04-29 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 3.28.1-0ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1902921] Re: Scaling one monitor (to 1.5x in my case) can cause Firefox to lose window features (titlebar, buttons, bookmark bar)

@vanvugt Can you describe which parts of Firefox you can't tell are
missing? I can update the information if necessary.

Regarding which parts are missing here's a list:

- titlebar/tabs 
- minimize, maximize, close buttons
- Back/forward/refresh/home buttons, address bar, add-on buttons, settings 
hamburger menu
- Bookmark bar
- Scrollbar

Navigation with escape button works.

Mouse works.

Scrolling with mouse works.

Initial right-click of the mouse shows the context menu offset from the
mouse (showed up on Primary display instead of Secondary where the mouse
was clicked). Other right clicks of the mouse  show the context menu in
the correct place.

The dev console shows with all of the buttons and options present.

Other applications in windowed or fullscreen mode display on the monitor
in the correct resolution and with the window chrome.

** Attachment added: "Screenshot_2020-11-04_22-51-51.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1902921/+attachment/5431401/+files/Screenshot_2020-11-04_22-51-51.png

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

Title:
  Scaling one monitor (to 1.5x in my case) can cause Firefox to lose
  window features (titlebar, buttons, bookmark bar)

Status in firefox package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  One monitor is a 4K monitor scaled to 1.5x, the other is a normal
  1920x1080 monitor scaled to 1x.

  While Firefox is already open, after logging in with the lock screen,
  or modifying display settings, sometimes Firefox will lose the
  titlebar, address bar, buttons, and bookmark bar. The website being
  displayed will still show, however not all features are usable (right
  click menu, mouse icon doesn't change).

  Reproduction steps:

  - Change zoom level of one or more monitors to >1.0 but less than 2.0 (have 
not tested with non-fractional zooms)
  - Open Firefox and browse to any website
  - Lock screen or leave computer alone until the screen locks.
  - Login
  - Firefox may have lost the window chrome

  Workaround:

  - Open Display Settings
  - Change display settings or zoom level, then change back.

  Computer info:

  - Ubuntu 20.04.1
  - Fractional Scaling enabled
  - NVidia GeForce GTX 1080/PCIe/SSE2
  - Gnome 3.36.3
  - X11
  - Samsung LU32J590 4K (3840x2160) @ 1.5x
  - Dell E2416Hb 1920x1080 rotated portrait left, right of Samsung

  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.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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  435.21  Sun Aug 25 08:17:57 
CDT 2019
   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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 09:31:17 2020
  DistUpgraded: 2020-04-03 12:51:44,815 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6188]
  InstallationDate: Installed on 2018-04-28 (920 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  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-52-generic 
root=UUID=dfb5d6fd-4a4e-471d-bb00-77a6729533d8 ro quiet splash pci=nommconf 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-03 (214 days ago)
  dmi.bios.date: 04/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.80
  dmi.board.name: X99 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias:

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

That's just gnome-system-monitor and GTK-3 rendering inefficiently,
which is bug 1773502 ...

Does your problem happen if you don't have gnome-system-monitor running?

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

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

2020-11-04 Thread rahul

Yes ..

1. "Mouse " is touchpad on Logitech K400
2. no 'extensions' in the path

rahul@desktophp:~/.local/share/gnome-shell$ ls -al
total 12
drwx--  2 rahul rahul 4096 Nov  4 21:05 .
drwx-- 47 rahul rahul 4096 Nov  5 10:26 ..
-rw-r--r--  1 rahul rahul 1443 Nov  4 21:05 application_state
-rw-r--r--  1 rahul rahul0 Nov 11  2019 gnome-overrides-migrated

3. Attached is the screenshot in GNOME classic.. the CPU load do not change
with mouse / touchpad activity  but is at constant ~ 20 % with all 4 cores
loaded  without any activity!!

Regards /// Rahul

On Thu, 5 Nov 2020 at 07:31, Daniel van Vugt <1902...@bugs.launchpad.net>
wrote:

> Thanks.
>
> 1. When you say "mouse" do you mean the touchpad on the Logitech K400
> Plus?
>
> 2. Please look in ~/.local/share/gnome-shell and make sure you don't
> have an 'extensions' subdirectory in there.
>
> 3. Does the same problem occur in GNOME Shell, or only in GNOME Classic?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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
>


** Attachment added: "Screenshot from 2020-11-05 12-15-01.png"
   
https://bugs.launchpad.net/bugs/1902825/+attachment/5431399/+files/Screenshot%20from%202020-11-05%2012-15-01.png

-- 
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:

[Desktop-packages] [Bug 1902983] Re: The display is constantly flickering

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

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

Title:
  The display is constantly flickering

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  The display is running on intel graphics and it is constantly
  flickering when rendering gnome related programs

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 
5.8.0-7625.26~1603389471~20.04~f6b125f~dev-generic 5.8.14
  Uname: Linux 5.8.0-7625-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  455.28  Wed Sep 30 01:05:16 
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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Nov  5 09:45:30 2020
  DistUpgraded: 2020-08-06 15:02:44,138 DEBUG inhibit gnome-session idle
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 455.28, 5.8.0-7625-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
  InstallationDate: Installed on 2020-07-23 (104 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications 
   Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-7625-generic 
root=UUID=a1c36ce1-f1fe-444a-ace5-ef0166cc7adf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-08-06 (90 days ago)
  dmi.bios.date: 07/09/2020
  dmi.bios.release: 1.17
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.17.1
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.1:bd07/09/2020:br1.17:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  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 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/1902983/+subscriptions

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

[Desktop-packages] [Bug 1902580] Re: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot.

2020-11-04 Thread Jeff P

** Description changed:

  My Xubuntu 20.10 installation has no sound (Dummy Output) unless I
  reinstall pulseaudio after every reboot.
  
  pulseaudio does survive a suspend.  Just a hard reset or power cycle
  causes it to fail.
  
  How I re-install pulseaudio:
  
  sudo apt-get install --reinstall pulseaudio
  
  I have tried just killing the pulseaudio service, and letting it restart
  on it's own. It restarts, but no audio. Reinstalling seems to do the
  trick though.
+ 
+ 
+ Note: File samples are after reinstalling. (working state)
  
  Thank You,
  Jeff
  
  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: XFCE
  Date: Mon Nov  2 13:42:36 2020
  InstallationDate: Installed on 2020-11-02 (0 days ago)
  InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425IA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425IA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425IA_UM425IA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

Title:
  [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall
  pulseaudio after every reboot.

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  My Xubuntu 20.10 installation has no sound (Dummy Output) unless I
  reinstall pulseaudio after every reboot.

  pulseaudio does survive a suspend.  Just a hard reset or power cycle
  causes it to fail.

  How I re-install pulseaudio:

  sudo apt-get install --reinstall pulseaudio

  I have tried just killing the pulseaudio service, and letting it
  restart on it's own. It restarts, but no audio. Reinstalling seems to
  do the trick though.

  
  Note: File samples are after reinstalling. (working state)

  Thank You,
  Jeff

  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: XFCE
  Date: Mon Nov  2 13:42:36 2020
  InstallationDate: Installed on 2020-11-02 (0 days ago)
  InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425IA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425IA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425IA_UM425IA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)

This bug was fixed in the package apport - 2.20.11-0ubuntu51

---
apport (2.20.11-0ubuntu51) hirsute; urgency=medium

  * data/apport: Modify the check for whether or not a process is running in
the same namespace so that crashes from processes running protected in the
system.slice are considered as being from the same namespace. (LP: #1870060)
  * etc/apport/crashdb.conf: Enable Launchpad crash reports for 21.04.

 -- Brian Murray   Wed, 04 Nov 2020 13:40:41 -0800

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

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

Title:
  systemd ProtectSystem/mount namespace makes apport fail (impact most
  of our default system services)

Status in apport package in Ubuntu:
  Fix Released
Status in bluez package in Ubuntu:
  Invalid
Status in apport source package in Focal:
  Triaged
Status in bluez source package in Focal:
  Invalid
Status in apport source package in Groovy:
  Triaged
Status in bluez source package in Groovy:
  New

Bug description:
  [Impact]
  apport is not creating crash files for multiple system services that use 
ProtectSystem since Ubuntu 20.04 LTS.

  [Test Case]
  On an Ubuntu desktop system perform the following step
  1) sudo pkill -11 upowerd

  With the current version of apport there will not be a crash file for
  upowerd in /var/crash/. With the version of apport in -proposed there
  will be a crash file for upowerd in /var/crash/.

  [Regression Potential]
  In the event that the changes to /usr/share/apport/apport are bad then apport 
itself would crash thereby preventing us from getting any crash reports. So in 
addition to killing upowerd we should also test a regular application like 
xeyes.

  [Original Description]
  bluetoothd never leaves dumps/crash files when it crashes

  And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year

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

-- 
Mailing list: https://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 1902983] Re: The display is constantly flickering

2020-11-04 Thread Surya Siddharthan

Sorry for not adding sufficient information.
However the issue is fixed now.
I uninstalled and reinstalled my dgpu drivers and now everything is fine.
If you need more information please let me know. Please know that I cannot
record a video now as I don't have the issue anymore.

On Thu, Nov 5, 2020 at 10:45 AM Daniel van Vugt <1902...@bugs.launchpad.net>
wrote:

> This could be one of a number of different issues...
>
> Please:
>
> 1. Attach a video or photo of the problem.
>
> 2. Next time the problem starts happening open a Terminal window and
> run:
>
>journalctl -b0 > journal.txt
>
>and then attach the resulting text file here.
>
> ** Changed in: xorg-server (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1902983
>
> Title:
>   The display is constantly flickering
>
> Status in xorg-server package in Ubuntu:
>   Incomplete
>
> Bug description:
>   The display is running on intel graphics and it is constantly
>   flickering when rendering gnome related programs
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: xorg 1:7.7+19ubuntu14
>   ProcVersionSignature: Ubuntu
> 5.8.0-7625.26~1603389471~20.04~f6b125f~dev-generic 5.8.14
>   Uname: Linux 5.8.0-7625-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  455.28  Wed Sep 30
> 01:05:16 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
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg:
> read kernel buffer failed: Operation not permitted
>   Date: Thu Nov  5 09:45:30 2020
>   DistUpgraded: 2020-08-06 15:02:44,138 DEBUG inhibit gnome-session idle
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   DkmsStatus: nvidia, 455.28, 5.8.0-7625-generic, x86_64: installed
>   ExtraDebuggingInterest: Yes, including running git bisection searches
>   GraphicsCard:
>Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00
> [VGA controller])
>  Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c]
>  Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
>   InstallationDate: Installed on 2020-07-23 (104 days ago)
>   InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
> (20190805)
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd.
> Fingerprint Reader
>Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications
>Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: Dell Inc. XPS 15 9570
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-7625-generic
> root=UUID=a1c36ce1-f1fe-444a-ace5-ef0166cc7adf ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: Upgraded to focal on 2020-08-06 (90 days ago)
>   dmi.bios.date: 07/09/2020
>   dmi.bios.release: 1.17
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.17.1
>   dmi.board.name: 0D0T05
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr1.17.1:bd07/09/2020:br1.17:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
>   dmi.product.family: XPS
>   dmi.product.name: XPS 15 9570
>   dmi.product.sku: 087C
>   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 20.0.8-0ubuntu1~20.04.1
>   version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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
>

[Desktop-packages] [Bug 1902983] Re: The display is constantly flickering

This could be one of a number of different issues...

Please:

1. Attach a video or photo of the problem.

2. Next time the problem starts happening open a Terminal window and
run:

   journalctl -b0 > journal.txt

   and then attach the resulting text file here.

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

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

Title:
  The display is constantly flickering

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  The display is running on intel graphics and it is constantly
  flickering when rendering gnome related programs

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 
5.8.0-7625.26~1603389471~20.04~f6b125f~dev-generic 5.8.14
  Uname: Linux 5.8.0-7625-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  455.28  Wed Sep 30 01:05:16 
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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Nov  5 09:45:30 2020
  DistUpgraded: 2020-08-06 15:02:44,138 DEBUG inhibit gnome-session idle
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 455.28, 5.8.0-7625-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
  InstallationDate: Installed on 2020-07-23 (104 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications 
   Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-7625-generic 
root=UUID=a1c36ce1-f1fe-444a-ace5-ef0166cc7adf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-08-06 (90 days ago)
  dmi.bios.date: 07/09/2020
  dmi.bios.release: 1.17
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.17.1
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.1:bd07/09/2020:br1.17:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  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 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/1902983/+subscriptions

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

[Desktop-packages] [Bug 1902983] Re: The display is constantly flickering

2020-11-04 Thread Chris Guiver

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

Can you please be more specific, you mention GNOME related programs, but
which programs, when doing what etc?

It may also be helpful if you create a short video (via phone) of the
issue & provide a link to it if possible.

Unfortunately, we cannot work on this bug because your description
didn't include enough information. You may find it helpful to read "How
to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).


Thank you!

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

Title:
  The display is constantly flickering

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  The display is running on intel graphics and it is constantly
  flickering when rendering gnome related programs

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 
5.8.0-7625.26~1603389471~20.04~f6b125f~dev-generic 5.8.14
  Uname: Linux 5.8.0-7625-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  455.28  Wed Sep 30 01:05:16 
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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Nov  5 09:45:30 2020
  DistUpgraded: 2020-08-06 15:02:44,138 DEBUG inhibit gnome-session idle
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 455.28, 5.8.0-7625-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
  InstallationDate: Installed on 2020-07-23 (104 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications 
   Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-7625-generic 
root=UUID=a1c36ce1-f1fe-444a-ace5-ef0166cc7adf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-08-06 (90 days ago)
  dmi.bios.date: 07/09/2020
  dmi.bios.release: 1.17
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.17.1
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.1:bd07/09/2020:br1.17:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  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 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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

[Desktop-packages] [Bug 1897530] Re: The modesetting driver does not gracefully handle missing connectors on EnterVT

2020-11-04 Thread Timo Aaltonen

Kent, I've pushed this for an SRU, but need to know that if it actually
fixes the original bug, please pre-test the patched xserver from
ppa:canonical-x/x-staging

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

Title:
  The modesetting driver does not gracefully handle missing connectors
  on EnterVT

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg-server source package in Bionic:
  Invalid
Status in xorg-server-hwe-18.04 source package in Bionic:
  New
Status in xorg-server source package in Focal:
  New
Status in xorg-server-hwe-18.04 source package in Focal:
  Invalid

Bug description:
  [Impact]

  On a hybrid machine where NVIDIA is rendering the screen, if a display
  attached to a dock is removed while on suspend mode, on resume X
  crashes.

  [Test case]

  Test hot-unplug during suspend and resume, X shouldn't crash.

  [Regression potential]

  This replaces a patch we had with two commits that got merged upstream
  after a fairly extensive review process:

  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/

  And we ship it in groovy. If there were issues caused by it, they
  would be around hot-unplugging a dock while on suspend and such.

  --

  Expectation: on removal of external display during S3, after resume eDP 
rendering should still continue by Nvidia.
  Symptom description: Plug out DP cable when suspension, when resume, X will 
crash.

  1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but 
NV was rendering for eDP.
  2. After S3 entry dock was removed.
  3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails 
resume of TB3 devices and logs confirm that.
  4. X fails to enter VT due to Null meta mode.

  To address the explanation, X is not failing to enter the VT due to
  NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is
  failing to enter the VT. It’s expected that NVIDIA would have a NULL
  MetaMode, since there are no displays connected to it. Our driver is
  pretty robust to head state changes – even if we have to fall back to
  a NULL MetaMode, we will still enter the VT successfully.

  The logs clearly show that the failure is originating from the Intel
  (modesetting) driver, not the NVIDIA driver. The relevant path in X is
  driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes().
  In this function, the Intel driver tries to set a mode on each of the
  previously connected/enabled displays, and it tries to find the
  closest possible mode using xf86OutputFindClosestMode(). This is
  similar to our driver’s functionality, but unlike us, they don’t
  support a NULL fallback. If there are no modes supported on one of the
  displays, it simply fails, which causes X to terminate:

  DisplayModePtr mode = xf86OutputFindClosestMode(output,
  pScrn->currentMode);

  if (!mode)
  return FALSE;

  Since we removed one of the displays via the dock, it fails. It
  doesn’t matter if the internal panel is still available, Intel will
  fail if it can’t re-enable ANY of the previously connected displays.

  Technically the modesetting driver isn’t specifically an Intel driver,
  it’s a generic driver that can be used by any DRM device – it’s just
  that Intel has chosen to use the modesetting driver as their standard
  Linux X driver going forward.

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

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

[Desktop-packages] [Bug 1902983] Re: The display is constantly flickering

2020-11-04 Thread Chris Guiver

changed 'xorg' to 'xorg-server'

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

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

Title:
  The display is constantly flickering

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The display is running on intel graphics and it is constantly
  flickering when rendering gnome related programs

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 
5.8.0-7625.26~1603389471~20.04~f6b125f~dev-generic 5.8.14
  Uname: Linux 5.8.0-7625-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  455.28  Wed Sep 30 01:05:16 
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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Nov  5 09:45:30 2020
  DistUpgraded: 2020-08-06 15:02:44,138 DEBUG inhibit gnome-session idle
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 455.28, 5.8.0-7625-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
  InstallationDate: Installed on 2020-07-23 (104 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications 
   Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-7625-generic 
root=UUID=a1c36ce1-f1fe-444a-ace5-ef0166cc7adf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-08-06 (90 days ago)
  dmi.bios.date: 07/09/2020
  dmi.bios.release: 1.17
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.17.1
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.1:bd07/09/2020:br1.17:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  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 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/1902983/+subscriptions

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

[Desktop-packages] [Bug 1902983] [NEW] The display is constantly flickering

2020-11-04 Thread Surya Siddharthan

Public bug reported:

The display is running on intel graphics and it is constantly flickering
when rendering gnome related programs

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-7625.26~1603389471~20.04~f6b125f~dev-generic 
5.8.14
Uname: Linux 5.8.0-7625-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  455.28  Wed Sep 30 01:05:16 
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
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Thu Nov  5 09:45:30 2020
DistUpgraded: 2020-08-06 15:02:44,138 DEBUG inhibit gnome-session idle
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 455.28, 5.8.0-7625-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c]
   Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
InstallationDate: Installed on 2020-07-23 (104 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
 Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications 
 Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9570
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-7625-generic 
root=UUID=a1c36ce1-f1fe-444a-ace5-ef0166cc7adf ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-08-06 (90 days ago)
dmi.bios.date: 07/09/2020
dmi.bios.release: 1.17
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.17.1
dmi.board.name: 0D0T05
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.1:bd07/09/2020:br1.17:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9570
dmi.product.sku: 087C
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 20.0.8-0ubuntu1~20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/1902983

Title:
  The display is constantly flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  The display is running on intel graphics and it is constantly
  flickering when rendering gnome related programs

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 
5.8.0-7625.26~1603389471~20.04~f6b125f~dev-generic 5.8.14
  Uname: Linux 5.8.0-7625-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: ""

[Desktop-packages] [Bug 1899751] Re: pulseaudio - NO SOUND on DELL XPS L502X

Please try uninstalling 'pipewire' because it looks like that is
stealing audio interfaces from PulseAudio.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Incomplete

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

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

Title:
  pulseaudio - NO SOUND on DELL XPS L502X

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  enat@Dell-XPS-L502X:~$ pulseaudio
  E: [pulseaudio] pid.c: Daemon already running.
  E: [pulseaudio] main.c: Произошла ошибка при выполнении pa_pid_file_create().
  renat@Dell-XPS-L502X:~$ ubuntu-bug pulseaudio
  /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required 
(got type float).  Implicit conversion to integers using __int__ is deprecated, 
and may be removed in a future version of Python.
progress.setValue(value * 1000)
  renat@Dell-XPS-L502X:~$ 

  
  Still no Icon of the Speaker and no sound since update to beta...please fix 
it.
  Thx for a great job.

  Renat.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14
  Uname: Linux 5.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  renat   993 F pulseaudio
renat   996 F pipewire-media-
   /dev/snd/controlC1:  renat   996 F pipewire-media-
   /dev/snd/seq:renat   992 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 14 10:26:41 2020
  InstallationDate: Installed on 2019-07-01 (470 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-04 (9 days ago)
  dmi.bios.date: 09/07/2012
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0YR8NN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:br0.1:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.product.sku: System SKUNumber
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1899751] Re: pulseaudio - NO SOUND on DELL XPS L502X

(like bug 1902976)

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

Title:
  pulseaudio - NO SOUND on DELL XPS L502X

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  enat@Dell-XPS-L502X:~$ pulseaudio
  E: [pulseaudio] pid.c: Daemon already running.
  E: [pulseaudio] main.c: Произошла ошибка при выполнении pa_pid_file_create().
  renat@Dell-XPS-L502X:~$ ubuntu-bug pulseaudio
  /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required 
(got type float).  Implicit conversion to integers using __int__ is deprecated, 
and may be removed in a future version of Python.
progress.setValue(value * 1000)
  renat@Dell-XPS-L502X:~$ 

  
  Still no Icon of the Speaker and no sound since update to beta...please fix 
it.
  Thx for a great job.

  Renat.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14
  Uname: Linux 5.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  renat   993 F pulseaudio
renat   996 F pipewire-media-
   /dev/snd/controlC1:  renat   996 F pipewire-media-
   /dev/snd/seq:renat   992 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 14 10:26:41 2020
  InstallationDate: Installed on 2019-07-01 (470 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-04 (9 days ago)
  dmi.bios.date: 09/07/2012
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0YR8NN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:br0.1:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.product.sku: System SKUNumber
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1902976] Re: PulseAudio doesn't work when pipewire is installed

** Summary changed:

- [Acer Aspire E5-432] After boot pulseaudio needs to be restarted
+ PulseAudio doesn't work when pipewire is installed

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

** Package changed: pulseaudio (Ubuntu) => pipewire (Ubuntu)

** Summary changed:

- PulseAudio doesn't work when pipewire is installed
+ PulseAudio doesn't work when pipewire is installed (ie. KDE)

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

Title:
  PulseAudio doesn't work when pipewire is installed (ie. KDE)

Status in pipewire package in Ubuntu:
  New

Bug description:
  After an upgrade pulseaudio does not run properly after boot unless I
  restart the service with the command systemctl --user restart
  pulseaudio. Reinstalling the service with the comand apt-get install
  --reinstall pulseaudio also solves the issue.

  I am currently running Kubuntu 20.10 and the pulseaudio version is
  1:13.99.2-1ubuntu2.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ppedrotti   1572 F pipewire-media-
ppedrotti   5420 F pulseaudio
   /dev/snd/seq:ppedrotti   1567 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Nov  4 23:13:09 2020
  InstallationDate: Installed on 2020-10-17 (18 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (12 days ago)
  dmi.bios.date: 12/07/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Robin_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd12/07/2015:br0.0:efr1.7:svnAcer:pnAspireE5-432:pvrV1.10:rvnAcer:rnRobin_BA:rvrV1.10:cvnAcer:ct10:cvrV1.10:
  dmi.product.family: BSW
  dmi.product.name: Aspire E5-432
  dmi.product.sku: Aspire E5-432
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1902976] Re: [Acer Aspire E5-432] After boot pulseaudio needs to be restarted

2020-11-04 Thread Pablo Pedrotti

Uninstalling pipewire fixed the issue. Now both the speakers and the
microphone work properly.

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

Title:
  [Acer Aspire E5-432] After boot pulseaudio needs to be restarted

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After an upgrade pulseaudio does not run properly after boot unless I
  restart the service with the command systemctl --user restart
  pulseaudio. Reinstalling the service with the comand apt-get install
  --reinstall pulseaudio also solves the issue.

  I am currently running Kubuntu 20.10 and the pulseaudio version is
  1:13.99.2-1ubuntu2.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ppedrotti   1572 F pipewire-media-
ppedrotti   5420 F pulseaudio
   /dev/snd/seq:ppedrotti   1567 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Nov  4 23:13:09 2020
  InstallationDate: Installed on 2020-10-17 (18 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (12 days ago)
  dmi.bios.date: 12/07/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Robin_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd12/07/2015:br0.0:efr1.7:svnAcer:pnAspireE5-432:pvrV1.10:rvnAcer:rnRobin_BA:rvrV1.10:cvnAcer:ct10:cvrV1.10:
  dmi.product.family: BSW
  dmi.product.name: Aspire E5-432
  dmi.product.sku: Aspire E5-432
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1902829] Re: Missing "Mobile Broadband" menu item

^^^
Too late now :)

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

Title:
  Missing "Mobile Broadband" menu item

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Groovy:
  In Progress
Status in gnome-shell package in Debian:
  Unknown

Bug description:
  [Impact]

  gnome-shell does not show the "Mobile Broadband" menu item in Ubuntu
  20.10, which practically prevents net access for users who depend on
  mobile broadband. An upstream fix has recently been pushed.

  [Test case]

  * Install the binaries built by the gnome-shell source package from
  groovy-proposed

  * Reboot

  * Confirm with a USB dongle for mobile broadband that it's recognized
  in the system menu and allows you to connect.

  [Regression risk]

  The issue was triggered by a change to gjs, and the fix simply adds
  two property getters. Low regression risk.

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

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

[Desktop-packages] [Bug 1902829] Re: Missing "Mobile Broadband" menu item

This bug was fixed in the package gnome-shell - 3.38.1-1ubuntu2

---
gnome-shell (3.38.1-1ubuntu2) hirsute; urgency=medium

  * debian/patches/modemManager_Add-property-getters.patch:
- Cherry picked upstream commit to fix issue with missing "Mobile
  Broadband" item in the system menu (LP: #1902829).

 -- Gunnar Hjalmarsson   Wed, 04 Nov 2020 16:59:17
+0100

** Changed in: gnome-shell (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/1902829

Title:
  Missing "Mobile Broadband" menu item

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Groovy:
  In Progress
Status in gnome-shell package in Debian:
  Unknown

Bug description:
  [Impact]

  gnome-shell does not show the "Mobile Broadband" menu item in Ubuntu
  20.10, which practically prevents net access for users who depend on
  mobile broadband. An upstream fix has recently been pushed.

  [Test case]

  * Install the binaries built by the gnome-shell source package from
  groovy-proposed

  * Reboot

  * Confirm with a USB dongle for mobile broadband that it's recognized
  in the system menu and allows you to connect.

  [Regression risk]

  The issue was triggered by a change to gjs, and the fix simply adds
  two property getters. Low regression risk.

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

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

[Desktop-packages] [Bug 1902829] Re: Missing "Mobile Broadband" menu item

2020-11-04 Thread Gunnar Hjalmarsson

@Daniel: It's already in the queue. But yeah, if I had known about it...
I asked Marco before uploading, but he was probably not aware of that
one.

Would you suggest that we upload again with the fix of bug #1897765?

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

Title:
  Missing "Mobile Broadband" menu item

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell source package in Groovy:
  In Progress
Status in gnome-shell package in Debian:
  Unknown

Bug description:
  [Impact]

  gnome-shell does not show the "Mobile Broadband" menu item in Ubuntu
  20.10, which practically prevents net access for users who depend on
  mobile broadband. An upstream fix has recently been pushed.

  [Test case]

  * Install the binaries built by the gnome-shell source package from
  groovy-proposed

  * Reboot

  * Confirm with a USB dongle for mobile broadband that it's recognized
  in the system menu and allows you to connect.

  [Regression risk]

  The issue was triggered by a change to gjs, and the fix simply adds
  two property getters. Low regression risk.

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

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

[Desktop-packages] [Bug 1902976] Re: [Acer Aspire E5-432] After boot pulseaudio needs to be restarted

It looks like pipewire might have stolen some of the audio interfaces
from pulseaudio. Please try uninstalling pipewire.

** Summary changed:

- After boot pulseaudio needs to be restarted
+ [Acer Aspire E5-432] After boot pulseaudio needs to be restarted

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

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

Title:
  [Acer Aspire E5-432] After boot pulseaudio needs to be restarted

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After an upgrade pulseaudio does not run properly after boot unless I
  restart the service with the command systemctl --user restart
  pulseaudio. Reinstalling the service with the comand apt-get install
  --reinstall pulseaudio also solves the issue.

  I am currently running Kubuntu 20.10 and the pulseaudio version is
  1:13.99.2-1ubuntu2.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ppedrotti   1572 F pipewire-media-
ppedrotti   5420 F pulseaudio
   /dev/snd/seq:ppedrotti   1567 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Nov  4 23:13:09 2020
  InstallationDate: Installed on 2020-10-17 (18 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (12 days ago)
  dmi.bios.date: 12/07/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Robin_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd12/07/2015:br0.0:efr1.7:svnAcer:pnAspireE5-432:pvrV1.10:rvnAcer:rnRobin_BA:rvrV1.10:cvnAcer:ct10:cvrV1.10:
  dmi.product.family: BSW
  dmi.product.name: Aspire E5-432
  dmi.product.sku: Aspire E5-432
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1902976] [NEW] After boot pulseaudio needs to be restarted

2020-11-04 Thread Pablo Pedrotti

Public bug reported:

After an upgrade pulseaudio does not run properly after boot unless I
restart the service with the command systemctl --user restart
pulseaudio. Reinstalling the service with the comand apt-get install
--reinstall pulseaudio also solves the issue.

I am currently running Kubuntu 20.10 and the pulseaudio version is
1:13.99.2-1ubuntu2.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.2-1ubuntu2
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ppedrotti   1572 F pipewire-media-
  ppedrotti   5420 F pulseaudio
 /dev/snd/seq:ppedrotti   1567 F pipewire
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Wed Nov  4 23:13:09 2020
InstallationDate: Installed on 2020-10-17 (18 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to groovy on 2020-10-24 (12 days ago)
dmi.bios.date: 12/07/2015
dmi.bios.release: 0.0
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.10
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Robin_BA
dmi.board.vendor: Acer
dmi.board.version: V1.10
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.10
dmi.ec.firmware.release: 1.7
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd12/07/2015:br0.0:efr1.7:svnAcer:pnAspireE5-432:pvrV1.10:rvnAcer:rnRobin_BA:rvrV1.10:cvnAcer:ct10:cvrV1.10:
dmi.product.family: BSW
dmi.product.name: Aspire E5-432
dmi.product.sku: Aspire E5-432
dmi.product.version: V1.10
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug groovy

** Attachment added: "alsa-info.txt"
   
https://bugs.launchpad.net/bugs/1902976/+attachment/5431303/+files/alsa-info.txt

** Attachment removed: "alsa-info.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902976/+attachment/5431303/+files/alsa-info.txt

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

Title:
  After boot pulseaudio needs to be restarted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After an upgrade pulseaudio does not run properly after boot unless I
  restart the service with the command systemctl --user restart
  pulseaudio. Reinstalling the service with the comand apt-get install
  --reinstall pulseaudio also solves the issue.

  I am currently running Kubuntu 20.10 and the pulseaudio version is
  1:13.99.2-1ubuntu2.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ppedrotti   1572 F pipewire-media-
ppedrotti   5420 F pulseaudio
   /dev/snd/seq:ppedrotti   1567 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Nov  4 23:13:09 2020
  InstallationDate: Installed on 2020-10-17 (18 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (12 days ago)
  dmi.bios.date: 12/07/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Robin_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd12/07/2015:br0.0:efr1.7:svnAcer:pnAspireE5-432:pvrV1.10:rvnAcer:rnRobin_BA:rvrV1.10:cvnAcer:ct10:cvrV1.10:
  dmi.product.family: BSW
  dmi.product.name: Aspire E5-432
  dmi.product.sku: Aspire E5-432
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1725803] Re: Double-click to expand a super wide column (process name) ruins your day

2020-11-04 Thread user 76543456789

** Attachment removed: "process-name-column.zip"

https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1725803/+attachment/4983258/+files/process-name-column.zip

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

Title:
Double-click to expand a super wide column (process name) ruins your
day

Status in gnome-system-monitor package in Ubuntu:
New

Bug description:
Google Chrome has long process names. By long I mean hundreds and
hundreds of characters wide (see picture). Without knowing this I
unsuspectingly double-clicked the process name column edge in the
processes tab, and ended up with a column that stretched far, far to
the right. The only way to get back to normal was to scroll to the far
right and tediously grab the column and shrink it manually over and
over until it got back to normal.

Before doing that I tried double-clicking again to try and make it
shrink to its smallest size -- that didn't work. I generally tend to
expect the reverse operation to work when working with UI. Open-Close,
Expand-Collapse, Show-Hide, etc.

After doing that I -- unfortunately -- tried to disable the process
name column in the column context menu (right click). That made
everything worse. Another column took over the super wide column that
previously held process names, and pretty much every other existing
column seemingly disappeared from the table. After some head-
scratching I figured out that all other columns had collapsed into
zero width.

I tried restarting the application -- didn't work; it had saved my
column setup.

Adjusting some column widths went from a simple task to becoming a
real chore.

Expectations:
I expected to be able to collapse the column the same way I expanded it. I
also expected all other columns to keep their own sizes when disabling/hiding a
column. In hindsight I now also expect column expansion to have some kind of
sanity check.

Note:
I was positive that I had included the scroll bars in the screenshots, but
apparently they timed out and disappeared, so the pictures kind of fail to
illustrate the extent of the column width.

Description: Ubuntu 17.10
Release: 17.10

gnome-system-monitor:
Installed: 3.26.0-1
Candidate: 3.26.0-1
Version table:
*** 3.26.0-1 500
500 http://se.archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1902853] Re: Failure to create core GL context with llvmpipe when using GLX_ARB_context_flush_control

I would suggest reporting the issue upstream but they will ask you to
test a newer version first. So please try live booting Ubuntu 20.10 from
USB (which includes Mesa 20.2) and tell us if it has the same problem:

  https://ubuntu.com/download/desktop

If the problem persists then please open a bug upstream at
https://gitlab.freedesktop.org/groups/mesa/-/issues and then tell us the
new issue ID.

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

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

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

** Changed in: mesa (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/1902853

Title:
  Failure to create core GL context with llvmpipe when using
  GLX_ARB_context_flush_control

Status in libsdl2 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  When using llvmpipe on the non-HWE xorg version GL core context
  creation fails when using "GLX_ARB_context_flush_control" even though
  the driver reports that the extension is supported.

  Apologies if xorg is the wrong package here, this could be a libgl1
  -mesa-dri/glx bug instead, it's unclear to me where the fault lies in
  the graphics stack.

  xserver-common:
Installed: 2:1.19.6-1ubuntu4.7
Candidate: 2:1.19.6-1ubuntu4.7
  linux-generic:
Installed: 4.15.0.122.109
Candidate: 4.15.0.122.109

  Steps to reproduce on Ubuntu Server:
  1. Install Ubuntu 18.04 server edition in a VM, or other hardware without a 
physical graphics device
  2. Install the desktop with "sudo apt install ubuntu-desktop"
  3. Reboot
  4. Compile and run the attached file

  Steps to reproduce on Ubuntu Desktop:
  1. Install Ubuntu 18.04 desktop edition in a VM, or other hardware without a 
physical graphics device
  2. Remove the HWE packages with "apt remove *-hwe-18.04" and then "apt 
install xserver-xorg-core ubuntu-desktop xserver-xorg xserver-xorg-video-all 
xserver-xorg-input-all libgl1-mesa-dri libgl1-mesa-glx" to get things back to 
normal
  3. Reboot
  4. Compile and run the attached file

  Both examples produce:
  "Could not create GL context: BadValue (integer parameter out of range for 
operation)"

  For both cases, upgrading to (or staying on) the HWE stack allows
  creating the core 3.3 context successfully.

  
  Debugging:

  I've stepped all the way into libxcb for the context creation at
  src/glx.c:3258, with a call to
  "xcb_glx_create_context_attribs_arb_checked", but haven't managed to
  link this up to a received request in another process. The request is
  rejected with BadValue.

  BadVaue in this instance could mean one of two things according to GL spec:
  1. The GLX_RENDER_TYPE attribute is invalid
  2. An attribute or it's bitmask are not recognized.

  We can likely rule out 1 as GLX_RENDER_TYPE is correctly set to
  opengl. Option 2 allows looking at it at a higher level. SDL2 adds
  `GLX_CONTEXT_RELEASE_BEHAVIOUR_ARB=GLX_CONTEXT_RELEASE_BEHAVIOUR_FLUSH_ARB`
  to the attributes (at src/video/x11/SDL_x11opengl.c:720) by default
  when it detects the `GLX_ARB_context_flush_control` extension is
  present, which should be a no-op and the default setting. `glxinfo`
  and other gl functions all show that `GLX_ARB_context_flush_control`
  is present, but removing that usage from the attributes list (by
  removing lines 720 to 726 avoids the issue and we are given a valid GL
  context.

  Due to this, I think something in the graphics stack is rejecting the
  usage of GLX_ARB_context_flush_control, even though it's claiming to
  support it through other gl calls. The llvmpipe GL driver reports core
  support up to 3.3 as well, so this shouldn't be an issue. I also
  suspect it's simply something that's been fixed more recently, as
  installing the newer HWE versions of xorg (and the kernel) fixes the
  issue.

  
  I wouldn't expect to have to upgrade to the HWE stack to be able to get a 
working GL context this way, so I'm reporting this to check if it's a known 
issue or if there's a fix that can be made.

  The attached file depends on "libsdl2-dev" and can be compiled and run with:
  "g++ main.cpp -I/usr/include/SDL2 -lSDL2 -lGL && ./a.out"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 09:16:16 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]

[Desktop-packages] [Bug 1902899] Re: Color management is not quite good

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

This sounds like bug 938751. Please let us know if the workaround for
that doesn't fix your issue.

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

** This bug has been marked a duplicate of bug 938751
   Images are washed out or colors are skewed in some apps (particularly Image 
Viewer and Chrome)

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

Title:
  Color management is not quite good

Status in Ubuntu:
  New

Bug description:
  While attempting to work with software like Figma, Inskcape and Gimp I
  noticed that the screen I have doesn't show colors like in my iMac or
  in WIndows. When I plug the same display on my laptop running Ubuntu
  20.04 the colors just looks very opaque and desaturated. I looked on
  the web for a tool to fix this but it just doesn't exist. I think this
  could be a bug or a a problem with drivers. But theres no proprietary
  drivers for this machine. The open source Intel drivers are just
  terrible. I suggest Ubuntu developers include potentiometers to manage
  color saturation, contrast, brightness and temperature under the
  "Color" tab on Ubuntu settings pannel. When I go to the color section
  of the settings pannel it only allows me to chose a color profile but
  I can't even adjust color settings. I really wish Linux systems be
  more usable when it comes to work with graphic software in the future.

  My system info:

  Lenovo Ideapad s145
  Ubuntu 20.04.1 LTS
  Processor: Intel® Core™ i3-8130U CPU @ 2.20GHz × 4 
  Graphics: Mesa Intel® UHD Graphics 620 (KBL GT2)
  GNOME version: 3.36.3
  X11
  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)

  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
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 12:08:10 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: darling-mach, 0.1, 5.4.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:3fdf]
  InstallationDate: Installed on 2020-10-14 (21 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81XM
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=a08ea31a-d24d-4a85-b391-c1950060f906 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 10/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CSCN10WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvrCSCN10WW:bd10/12/2019:svnLENOVO:pn81XM:pvrLenovoIdeaPadS145-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IKB:
  dmi.product.family: IdeaPad S145-15IKB
  dmi.product.name: 81XM
  dmi.product.sku: LENOVO_MT_81XM_BU_idea_FM_IdeaPad S145-15IKB
  dmi.product.version: Lenovo IdeaPad S145-15IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103+git2011040630.5dea8f~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3~git2011040730.58e708~oibaf~f
  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 N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage

[Desktop-packages] [Bug 1902921] Re: Scaling one monitor (to 1.5x in my case) can cause Firefox to lose window features (titlebar, buttons, bookmark bar)

If the problem is just the window decorations then this is an Xwayland
bug (source package 'xorg-server').

But I can't tell right now if parts of Firefox itself are also missing.
And either way, the problem could be triggered by Firefox itself.

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

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

** Tags added: xrandr-scaling

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

Title:
  Scaling one monitor (to 1.5x in my case) can cause Firefox to lose
  window features (titlebar, buttons, bookmark bar)

Status in firefox package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  One monitor is a 4K monitor scaled to 1.5x, the other is a normal
  1920x1080 monitor scaled to 1x.

  While Firefox is already open, after logging in with the lock screen,
  or modifying display settings, sometimes Firefox will lose the
  titlebar, address bar, buttons, and bookmark bar. The website being
  displayed will still show, however not all features are usable (right
  click menu, mouse icon doesn't change).

  Reproduction steps:

  - Change zoom level of one or more monitors to >1.0 but less than 2.0 (have 
not tested with non-fractional zooms)
  - Open Firefox and browse to any website
  - Lock screen or leave computer alone until the screen locks.
  - Login
  - Firefox may have lost the window chrome

  Workaround:

  - Open Display Settings
  - Change display settings or zoom level, then change back.

  Computer info:

  - Ubuntu 20.04.1
  - Fractional Scaling enabled
  - NVidia GeForce GTX 1080/PCIe/SSE2
  - Gnome 3.36.3
  - X11
  - Samsung LU32J590 4K (3840x2160) @ 1.5x
  - Dell E2416Hb 1920x1080 rotated portrait left, right of Samsung

  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.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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  435.21  Sun Aug 25 08:17:57 
CDT 2019
   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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 09:31:17 2020
  DistUpgraded: 2020-04-03 12:51:44,815 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6188]
  InstallationDate: Installed on 2018-04-28 (920 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  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-52-generic 
root=UUID=dfb5d6fd-4a4e-471d-bb00-77a6729533d8 ro quiet splash pci=nommconf 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-03 (214 days ago)
  dmi.bios.date: 04/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.80
  dmi.board.name: X99 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.80:bd04/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  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 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4

[Desktop-packages] [Bug 1574243] Re: Unable to adjust screen backlight on login screen on Macbook Pro (early 2015)

2020-11-04 Thread user 76543456789

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574243/+attachment/4645251/+files/CurrentDmesg.txt

** Attachment removed: "XorgLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574243/+attachment/4645265/+files/XorgLog.txt

** Attachment removed: "XorgLogOld.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574243/+attachment/4645266/+files/XorgLogOld.txt

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

Title:
  Unable to adjust screen backlight on login screen on Macbook Pro
  (early 2015)

Status in xorg package in Ubuntu:
  New

Bug description:
  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu

  Fresh install of 16.04.

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

  Don't know. The guide to identify the package told me all login screen
  issues were "LightDM". ubuntu-bug told me that package was not
  installed.

  3) What you expected to happen

  To be able to adjust screen backlight brightness with the dedicated
  hardware buttons on the login screen, in order to be able log in. This
  works as expected whenever I'm logged in.

  4) What happened instead

  I had to log in from an almost black login screen with no backlight.

  I believe this bug was present in 15.10 as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Apr 24 13:58:00 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:162b] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Broadwell-U Integrated Graphics [106b:013f]
  InstallationDate: Installed on 2016-04-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=dd7fd213-44e3-45de-afe3-efd8c5825c1e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/11/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B16.1602111810
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B16.1602111810:bd02/11/2016:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Apr 24 02:40:40 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   41002 
   vendor APP
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Desktop-packages] [Bug 1902580] Re: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot.

Since every model of laptop has slightly different audio hardware, and
slightly different problems, we should open a separate bug for each
model. This bug is about the Asus ZenBook UX425IA.

For other machine types please open a new bug by running:

  ubuntu-bug pulseaudio

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

Title:
  [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall
  pulseaudio after every reboot.

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  My Xubuntu 20.10 installation has no sound (Dummy Output) unless I
  reinstall pulseaudio after every reboot.

  pulseaudio does survive a suspend.  Just a hard reset or power cycle
  causes it to fail.

  How I re-install pulseaudio:

  sudo apt-get install --reinstall pulseaudio

  I have tried just killing the pulseaudio service, and letting it
  restart on it's own. It restarts, but no audio. Reinstalling seems to
  do the trick though.

  Thank You,
  Jeff

  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: XFCE
  Date: Mon Nov  2 13:42:36 2020
  InstallationDate: Installed on 2020-11-02 (0 days ago)
  InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425IA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425IA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425IA_UM425IA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://launchpad.net/~desktop-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

Thanks.

1. When you say "mouse" do you mean the touchpad on the Logitech K400
Plus?

2. Please look in ~/.local/share/gnome-shell and make sure you don't
have an 'extensions' subdirectory in there.

3. Does the same problem occur in GNOME Shell, or only in GNOME Classic?

-- 
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 1902829] Re: Missing "Mobile Broadband" menu item

I suggest if you are patching gnome-shell then including the fix for bug
1897765 would also be helpful. But I was just going to wait for 3.38.2
instead.

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

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

Title:
  Missing "Mobile Broadband" menu item

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell source package in Groovy:
  In Progress
Status in gnome-shell package in Debian:
  Unknown

Bug description:
  [Impact]

  gnome-shell does not show the "Mobile Broadband" menu item in Ubuntu
  20.10, which practically prevents net access for users who depend on
  mobile broadband. An upstream fix has recently been pushed.

  [Test case]

  * Install the binaries built by the gnome-shell source package from
  groovy-proposed

  * Reboot

  * Confirm with a USB dongle for mobile broadband that it's recognized
  in the system menu and allows you to connect.

  [Regression risk]

  The issue was triggered by a change to gjs, and the fix simply adds
  two property getters. Low regression risk.

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

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

[Desktop-packages] [Bug 1902580] Re: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot.

2020-11-04 Thread Jay Jones

I lost audio as well and have to reinstall pulseaudio everytime I boot the 
computer to get it back-- otherwise you have Dummy Output only.  Everything 
worked fine until I updated this batch (from /var/log/apt/history.log):
Upgrade: netplan.io:amd64 (0.100-0ubuntu4~20.04.2, 0.100-0ubuntu4~20.04.3), 
libsystemd0:amd64 (245.4-4ubuntu3.2, 245.4-4ubuntu3.3), libasound2-data:amd64 
(1.2.2-2.1ubuntu2, 1.2.2-2.1ubuntu2.1), systemd-coredump:amd64 
(245.4-4ubuntu3.2, 245.4-4ubuntu3.3), udev:amd64 (245.4-4ubuntu3.2, 
245.4-4ubuntu3.3), alsa-utils:amd64 (1.2.2-1ubuntu1, 1.2.2-1ubuntu2), 
libudev1:amd64 (245.4-4ubuntu3.2, 245.4-4ubuntu3.3), systemd-timesyncd:amd64 
(245.4-4ubuntu3.2, 245.4-4ubuntu3.3), libnss-myhostname:amd64 
(245.4-4ubuntu3.2, 245.4-4ubuntu3.3), systemd-sysv:amd64 (245.4-4ubuntu3.2, 
245.4-4ubuntu3.3), chromium-codecs-ffmpeg-extra:amd64 
(1:85.0.4183.83-0ubuntu0.20.04.1, 1:85.0.4183.83-0ubuntu0.20.04.2), 
libpam-systemd:amd64 (245.4-4ubuntu3.2, 245.4-4ubuntu3.3), systemd:amd64 
(245.4-4ubuntu3.2, 245.4-4ubuntu3.3), libnss-systemd:amd64 (245.4-4ubuntu3.2, 
245.4-4ubuntu3.3), libasound2:amd64 (1.2.2-2.1ubuntu2, 1.2.2-2.1ubuntu2.1), 
libnetplan0:amd64 (0.100-0ubuntu4~20.04.2, 0.100-0ubuntu4~20.04.3), 
libatopology2:amd64 (1.2.2-2.1ubuntu2, 1.2.2-2.1ubuntu2.1)

Running 5.8.0-25 kernel on Renoir 4700U laptop (HP Envy x360 13)

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

Title:
  [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall
  pulseaudio after every reboot.

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  My Xubuntu 20.10 installation has no sound (Dummy Output) unless I
  reinstall pulseaudio after every reboot.

  pulseaudio does survive a suspend.  Just a hard reset or power cycle
  causes it to fail.

  How I re-install pulseaudio:

  sudo apt-get install --reinstall pulseaudio

  I have tried just killing the pulseaudio service, and letting it
  restart on it's own. It restarts, but no audio. Reinstalling seems to
  do the trick though.

  Thank You,
  Jeff

  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: XFCE
  Date: Mon Nov  2 13:42:36 2020
  InstallationDate: Installed on 2020-11-02 (0 days ago)
  InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425IA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425IA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425IA_UM425IA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1902094] Re: High Xorg and gnome-shell CPU usage while Sound Settings opened

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1181
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1181

** Also affects: gnome-control-center via
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1181
   Importance: Unknown
   Status: Unknown

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

Title:
  High Xorg and gnome-shell CPU usage while Sound Settings opened

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  Several days ago I found huge lags over all system on my Ubuntu
  20.04.1 LTS. Today I think found the problem, but not the reason. So
  when I open Settings -> Sound menu, the CPU usage comes to about 100%.
  If I close Settings window or go to other tab, it becomes OK. Nothing
  special in my sound configuration - monitor and notebook with built in
  audio and Bluetooth headset. Same worked just fine on Ubuntu 18.04
  LTS.

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-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] 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
  Date: Thu Oct 29 18:27:20 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-51-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0824]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0824]
  InstallationDate: Installed on 2020-09-12 (47 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. G5 5587
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=ef73abac-57c7-4134-90f3-1f52f41127a8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.0
  dmi.board.name: 03PVDF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd02/11/2019:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn03PVDF:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G5 5587
  dmi.product.sku: 0824
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/gnome-control-center/+bug/1902094/+subscriptions

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

[Desktop-packages] [Bug 1902969] [NEW] Thunder freezes UI when changing from title bars to CSD

2020-11-04 Thread motang

Public bug reported:

I noticed a bug. In Thunderbird (deb or snap) version open and right
click on the tab bar and choose customization and mess around with
showing title or not and close out of it the icon for TB is still in the
dock. If you click on the icon it locks up the UI.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: thunderbird 1:78.3.2+build1-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
Uname: Linux 5.8.0-26-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  mram   2160 F pulseaudio
 /dev/snd/controlC0:  mram   2160 F pulseaudio
BuildID: 20201006011220
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  4 18:55:14 2020
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:732
DefaultProfilePrefSources: prefs.js
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
InstallationDate: Installed on 2020-10-04 (31 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
IpRoute:
 default via 192.168.1.1 dev eno1 proto dhcp metric 100 
 169.254.0.0/16 dev eno1 scope link metric 1000 
 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.45 metric 100
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:732
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 - LastVersion=78.0/20200629202523 (Out of date)
 Profile0 (Default) - LastVersion=78.3.2/20201006011220
RunningIncompatibleAddons: False
SourcePackage: thunderbird
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2012
dmi.bios.release: 4.6
dmi.bios.vendor: Intel Corp.
dmi.bios.version: AGH6120H.86A.0015.2012.0926.1822
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH61AGL
dmi.board.vendor: Intel Corporation
dmi.board.version: G71256-202
dmi.chassis.type: 3
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: sabc1
dmi.modalias: 
dmi:bvnIntelCorp.:bvrAGH6120H.86A.0015.2012.0926.1822:bd09/26/2012:br4.6:svnSystem76,Inc.:pnSableComplete:pvrsabc1:rvnIntelCorporation:rnDH61AGL:rvrG71256-202:cvnSystem76,Inc.:ct3:cvrsabc1:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Sable Complete
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: sabc1
dmi.sys.vendor: System76, Inc.

** Affects: thunderbird (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 thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1902969

Title:
  Thunder freezes UI when changing from title bars to CSD

Status in thunderbird package in Ubuntu:
  New

Bug description:
  I noticed a bug. In Thunderbird (deb or snap) version open and right
  click on the tab bar and choose customization and mess around with
  showing title or not and close out of it the icon for TB is still in
  the dock. If you click on the icon it locks up the UI.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: thunderbird 1:78.3.2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mram   2160 F pulseaudio
   /dev/snd/controlC0:  mram   2160 F pulseaudio
  BuildID: 20201006011220
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 18:55:14 2020
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:732
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-10-04 (31 days ago)
  InstallationMedia:

[Desktop-packages] [Bug 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Yes we plan on it eventually (bug 1902485).

** Also affects: pulseaudio via
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1030
   Importance: Unknown
   Status: Unknown

-- 
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:
  Unknown
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/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 1887190] Re: [PATCH 4/4] pinctrl: amd: remove debounce filter setting in irq type setting

2020-11-04 Thread Coiby Xu

On Wed, Nov 04, 2020 at 10:42:38PM +0200, Andy Shevchenko wrote:
>On Wed, Nov 4, 2020 at 6:05 PM Coiby Xu  wrote:
>>
>> Debounce filter setting should be independent from irq type setting
>> because according to the ACPI specs, there are separate arguments for
>> specifying debounce timeout and irq type in GpioIo and GpioInt.
>>
>> This will fix broken touchpads for Lenovo Legion-5 AMD gaming laptops
>> including 15ARH05 (R7000) and R7000P whose BIOS set the debounce timeout
>> to 124.8ms which led to kernel receiving only ~7 HID reports per second.
>
>to the kernel

Thank you for correcting my grammar mistakes!

>
>> Cc: Hans de Goede 
>> Cc: Andy Shevchenko 
>> Cc: 1887...@bugs.launchpad.net
>> BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190
>
>> Message-Id: 
>> 
>
>Link: https://lore.kernel.org/...
>
>--
>With Best Regards,
>Andy Shevchenko

--
Best regards,
Coiby

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

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

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

Bug description:
  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware

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

2020-11-04 Thread Till Kamppeter

Uploaded fixed packages for focal and groovy, correcting version numbers
and message in debian/changelog.

Hugh, thanks for the debdiffs.

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

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

** Changed in: system-config-printer (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: system-config-printer (Ubuntu Groovy)
   Status: New => Fix Committed

-- 
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:
  Fix Released
Status in system-config-printer source package in Focal:
  Fix Committed
Status in system-config-printer source package in Groovy:
  Fix Committed

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

2020-11-04 Thread Till Kamppeter

Uploaded fixed package to Hirsute (1.5.12-0ubuntu4).

** Also affects: system-config-printer (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: system-config-printer (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: system-config-printer (Ubuntu)
   Status: New => Fix Released

-- 
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:
  Fix Released
Status in system-config-printer source package in Focal:
  New
Status in system-config-printer source package in Groovy:
  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 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)

2020-11-04 Thread Brian Murray

** Also affects: apport (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: bluez (Ubuntu Groovy)
   Importance: Undecided
   Status: New

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

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

** Changed in: apport (Ubuntu Focal)
   Status: Confirmed => Triaged

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

Title:
  systemd ProtectSystem/mount namespace makes apport fail (impact most
  of our default system services)

Status in apport package in Ubuntu:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in apport source package in Focal:
  Triaged
Status in bluez source package in Focal:
  Invalid
Status in apport source package in Groovy:
  Triaged
Status in bluez source package in Groovy:
  New

Bug description:
  [Impact]
  apport is not creating crash files for multiple system services that use 
ProtectSystem since Ubuntu 20.04 LTS.

  [Test Case]
  On an Ubuntu desktop system perform the following step
  1) sudo pkill -11 upowerd

  With the current version of apport there will not be a crash file for
  upowerd in /var/crash/. With the version of apport in -proposed there
  will be a crash file for upowerd in /var/crash/.

  [Regression Potential]
  In the event that the changes to /usr/share/apport/apport are bad then apport 
itself would crash thereby preventing us from getting any crash reports. So in 
addition to killing upowerd we should also test a regular application like 
xeyes.

  [Original Description]
  bluetoothd never leaves dumps/crash files when it crashes

  And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year

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

-- 
Mailing list: https://launchpad.net/~desktop-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-04 Thread Olivier Tilloy

Right, so the trigger for the bug appears to be upgrading from
thunderbird 68.x to 78.y, as Joep did by enabling the ubuntu-mozilla-
security PPA.

Note that that PPA is not recommended for general use, it is used for
preparing and testing updates. This doesn't invalidate this problem
though, which I haven't managed to reproduce in various testing
scenarios yet.

-- 
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 1902952] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1

2020-11-04 Thread Olivier Tilloy

Relevant excerpt from DpkgTerminalLog.txt:

error: cannot perform the following tasks:
- Download snap "chromium" (1376) from channel "stable" (read tcp 
10.115.1.203:55158->91.189.91.43:443: read: connection reset by peer)

This looks like a transient network failure. I suggest retrying:

sudo apt reinstall chromium-browser

Please let us know whether this works.

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

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

Title:
  package chromium-browser (not installed) failed to install/upgrade:
  new chromium-browser package pre-installation script subprocess
  returned error exit status 1

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  This is the third time.

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14
  Uname: Linux 5.8.0-1006-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu50
  AptOrdering:
   chromium-browser:arm64: Install
   chromium-browser-l10n:arm64: Install
   NULL: ConfigurePending
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Wed Nov  4 09:42:36 2020
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
  ImageMediaBuild: 20201022
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10
  SourcePackage: chromium-browser
  Title: package chromium-browser (not installed) failed to install/upgrade: 
new chromium-browser package pre-installation script subprocess returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1902952] [NEW] package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1

2020-11-04 Thread Robert

Public bug reported:

This is the third time.

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: chromium-browser (not installed)
ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14
Uname: Linux 5.8.0-1006-raspi aarch64
ApportVersion: 2.20.11-0ubuntu50
AptOrdering:
 chromium-browser:arm64: Install
 chromium-browser-l10n:arm64: Install
 NULL: ConfigurePending
Architecture: arm64
CasperMD5CheckResult: skip
Date: Wed Nov  4 09:42:36 2020
ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
ImageMediaBuild: 20201022
Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.5ubuntu2
 apt  2.1.10
SourcePackage: chromium-browser
Title: package chromium-browser (not installed) failed to install/upgrade: new 
chromium-browser package pre-installation script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package arm64 groovy

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

Title:
  package chromium-browser (not installed) failed to install/upgrade:
  new chromium-browser package pre-installation script subprocess
  returned error exit status 1

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  This is the third time.

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14
  Uname: Linux 5.8.0-1006-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu50
  AptOrdering:
   chromium-browser:arm64: Install
   chromium-browser-l10n:arm64: Install
   NULL: ConfigurePending
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Wed Nov  4 09:42:36 2020
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
  ImageMediaBuild: 20201022
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10
  SourcePackage: chromium-browser
  Title: package chromium-browser (not installed) failed to install/upgrade: 
new chromium-browser package pre-installation script subprocess returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1897185] Re: Laptop docked with lid closed, goes to sleep immediately on login

2020-11-04 Thread Tim Wetzel

This may also help:
I'm testing the fix for bug 1872159 (spinning logo hang on startup). It seems 
to be working.
So, since the rendering of the nVidia driver is superior to the x.org driver, I 
switched for the generic x.org back to nVidia's latest 450 version for the 
T570's GeForce 940MX. Well: on startup, the system exhibited this bug and went 
into suspend as soon as I put in the password. Immediately before suspending, 
the logs showed:
NVidia: access.
Using input driver 'libinput' for 'Video Bus'
and then suspended.
I then tried nVidia's 435 driver; same result (system suspended at login).
So I've gone back to the generic x.org driver for the discrete graphics again.
This is the same system where loading the Dropbox app on startup will also 
cause suspend.
Hope this helps.
Thanks.

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

Title:
  Laptop docked with lid closed, goes to sleep immediately on login

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04's software updater just applied quite a few updates
  affecting grub and nvidia. The modules should show in the report just
  submitted. Also, updates to initramfs had just installed a few days
  ago. Kudos in that these updates fixed two login/startup issues: I'd
  been affected by the compression change for initramfs and had started
  getting the spinning ubuntu circle on the logon splash screen,
  apparently due to an nvidia driver conflict. I'd turned the splash
  screen to nosplash, and have now been able to set it back to splash.
  Both of those issues now appear to be fixed.

  BUT now when I start Ubuntu with the T570 laptop docked, lid closed,
  external display and keyboard via the dock: as soon as I enter the
  login password and press enter, the system goes into suspend. If I
  then press the dock power button again, the system will resume and
  proceed normally.

  It seems that the new startup modules don't realize that the machine
  is docked; and/or that it erroneously now "detects" the closed lid as
  a change in lid state during startup, triggering suspend. Prior to
  today's updates, this was not an issue.

  I would appreciate seeing this corrected. Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.25
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 24 18:15:31 2020
  InstallationDate: Installed on 2020-06-22 (94 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

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

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

[Desktop-packages] [Bug 1902899] Re: Color management is not quite good

2020-11-04 Thread Flávio Vivório Salles

I uninstalled Oibaf graphics right now in order to perform extra
debugging if not too technical. And because I didn't notice any
improvements after installing Oibaf.

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

Title:
  Color management is not quite good

Status in xorg package in Ubuntu:
  New

Bug description:
  While attempting to work with software like Figma, Inskcape and Gimp I
  noticed that the screen I have doesn't show colors like in my iMac or
  in WIndows. When I plug the same display on my laptop running Ubuntu
  20.04 the colors just looks very opaque and desaturated. I looked on
  the web for a tool to fix this but it just doesn't exist. I think this
  could be a bug or a a problem with drivers. But theres no proprietary
  drivers for this machine. The open source Intel drivers are just
  terrible. I suggest Ubuntu developers include potentiometers to manage
  color saturation, contrast, brightness and temperature under the
  "Color" tab on Ubuntu settings pannel. When I go to the color section
  of the settings pannel it only allows me to chose a color profile but
  I can't even adjust color settings. I really wish Linux systems be
  more usable when it comes to work with graphic software in the future.

  My system info:

  Lenovo Ideapad s145
  Ubuntu 20.04.1 LTS
  Processor: Intel® Core™ i3-8130U CPU @ 2.20GHz × 4 
  Graphics: Mesa Intel® UHD Graphics 620 (KBL GT2)
  GNOME version: 3.36.3
  X11
  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)

  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
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 12:08:10 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: darling-mach, 0.1, 5.4.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:3fdf]
  InstallationDate: Installed on 2020-10-14 (21 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81XM
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=a08ea31a-d24d-4a85-b391-c1950060f906 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 10/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CSCN10WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvrCSCN10WW:bd10/12/2019:svnLENOVO:pn81XM:pvrLenovoIdeaPadS145-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IKB:
  dmi.product.family: IdeaPad S145-15IKB
  dmi.product.name: 81XM
  dmi.product.sku: LENOVO_MT_81XM_BU_idea_FM_IdeaPad S145-15IKB
  dmi.product.version: Lenovo IdeaPad S145-15IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103+git2011040630.5dea8f~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3~git2011040730.58e708~oibaf~f
  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 N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1887190] Re: [PATCH 4/4] pinctrl: amd: remove debounce filter setting in irq type setting

2020-11-04 Thread Andy Shevchenko

On Wed, Nov 4, 2020 at 6:05 PM Coiby Xu  wrote:
>
> Debounce filter setting should be independent from irq type setting
> because according to the ACPI specs, there are separate arguments for
> specifying debounce timeout and irq type in GpioIo and GpioInt.
>
> This will fix broken touchpads for Lenovo Legion-5 AMD gaming laptops
> including 15ARH05 (R7000) and R7000P whose BIOS set the debounce timeout
> to 124.8ms which led to kernel receiving only ~7 HID reports per second.

to the kernel

> Cc: Hans de Goede 
> Cc: Andy Shevchenko 
> Cc: 1887...@bugs.launchpad.net
> BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190

> Message-Id: 

Link: https://lore.kernel.org/...

-- 
With Best Regards,
Andy Shevchenko

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

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

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

Bug description:
  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO

[Desktop-packages] [Bug 1902911] Re: GNOME desktop does not suspend on lid close with HDMI TV connected

2020-11-04 Thread Andrei Borzenkov

> This most trivial (untested) patch

I now built package with this test and it correctly suspends with
external monitor connected.

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

Title:
  GNOME desktop does not suspend on lid close with HDMI TV connected

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

Bug description:
  Ubuntu 20.04 with all current updates, GNOME/Wayland desktop, Dell
  Latitude E5450 notebook.

  I have external TV connected via HDMI and I want notebook to suspend
  when I close lid even if TV is connected. This does not work. Even
  though logind is configured to suspend in this case:

  $ cat /etc/systemd/logind.conf.d/allow-suspend-with-hdmi.conf 
  [Login]
  HandleLidSwitchDocked=suspend
  $ 

  gnome-settings-daemon starts inhibitor as soon as it detects external
  monitor:

  WHO  UID  USER PID   COMMWHAT 
WHY 
MODE 
  bor  1001 bor  96600 gsd-power   
handle-lid-switchExternal monitor 
attached or configuration changed recently block

  so sytemd-logind does not initiate suspend, but there is also no code
  in gnome-settings-daemon itself to handle lid close (as it completely
  relies on systemd-logind today).

  Ubuntu package includes patch ubuntu-lid-close-suspend.patch that
  restores gsettings keys, but as there is no code to actually *use*
  these keys patch has no effect:

  $ gsettings list-recursively org.gnome.settings-daemon.plugins.power | grep 
-w lid
  org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend'
  org.gnome.settings-daemon.plugins.power 
lid-close-suspend-with-external-monitor true
  org.gnome.settings-daemon.plugins.power lid-close-battery-action 'suspend'
  $ 

  This most trivial (untested) patch to use this settings seems to be:

  diff --git a/plugins/power/gsd-power-manager.c 
b/plugins/power/gsd-power-manager.c
  index c7a16e8d..9b7a99b5 100644
  --- a/plugins/power/gsd-power-manager.c
  +++ b/plugins/power/gsd-power-manager.c
  @@ -1196,7 +1196,7 @@ upower_kbd_toggle (GsdPowerManager *manager,
   static gboolean
   suspend_on_lid_close (GsdPowerManager *manager)
   {
  -return !external_monitor_is_connected (manager->rr_screen);
  +return g_settings_get_boolean (manager->settings, 
"lid-close-suspend-with-external-monitor") || !external_monitor_is_connected 
(manager->rr_screen);
   }
   
   static gboolean

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-settings-daemon 3.36.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26~20.04.1-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 18:43:56 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2015-07-02 (1952 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to focal on 2020-10-03 (32 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-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-04 Thread Michael Nazzareno Trimarchi

Dear Sebastian, the problem that the station patch was backported
already but wrongly. I have just fixed in this package

This is coming from change log

wpa (2:2.6-15ubuntu1) bionic; urgency=low

  * Merge from Debian unstable.  Remaining changes:
- debian/patches/wpa_service_ignore-on-isolate.patch: add
  IgnoreOnIsolate=yes so that when switching "runlevels" in oem-config
  will not kill off wpa and cause wireless to be unavailable on first
  boot.
- debian/patches/session-ticket.patch: disable the TLS Session Ticket
  extension to fix auth with 802.1x PEAP on some hardware.
- debian/patches/android_hal_fw_path_change.patch: add a DBus method
  for requesting a firmware change when working with the Android HAL;
  this is used to set a device in P2P or AP mode; conditional to
  CONFIG_ANDROID_HAL being enabled.
- debian/config/wpasupplicant/linux: enable CONFIG_ANDROID_HAL.
- debian/control: Build-Depends on android-headers to get the required
  wifi headers for the HAL support.
- debian/patches/dbus-available-sta.patch: Make the list of connected
  stations available on DBus for hotspot mode; along with some of the
  station properties, such as rx/tx packets, bytes, capabilities, etc.

Up you have the patch that break the package. I just made it working
properly patch the package



  * Updated debian/patches/dbus-available-sta.patch for new getter API

-- 
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 1902921] Re: Scaling one monitor (to 1.5x in my case) can cause Firefox to lose window features (titlebar, buttons, bookmark bar)

** Description changed:

  One monitor is a 4K monitor scaled to 1.5x, the other is a normal
  1920x1080 monitor scaled to 1x.
  
- While Firefox is already open, after logging into the lock screen,
+ While Firefox is already open, after logging in with the lock screen,
  sometimes Firefox will lose the titlebar, address bar, buttons, and
  bookmark bar. The website being displayed will still show, however not
  all features are usable (right click menu, mouse icon doesn't change).
  
  Reproduction steps:
  
  - Change zoom level of one or more monitors to >1.0 but less than 2.0 (have 
not tested with non-fractional zooms)
  - Open Firefox and browse to any website
  - Lock screen or leave computer alone until the screen locks.
  - Login
  - Firefox may have lost the window chrome
  
  Workaround:
  
  - Open Display Settings
  - Change display settings or zoom level, then change back.
  
  Computer info:
  
  - Ubuntu 20.04.1
  - Fractional Scaling enabled
  - NVidia GeForce GTX 1080/PCIe/SSE2
  - Gnome 3.36.3
  - X11
  - Samsung LU32J590 4K (3840x2160) @ 1.5x
  - Dell E2416Hb 1920x1080 rotated portrait left, right of Samsung
  
  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.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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  435.21  Sun Aug 25 08:17:57 
CDT 2019
   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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 09:31:17 2020
  DistUpgraded: 2020-04-03 12:51:44,815 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6188]
  InstallationDate: Installed on 2018-04-28 (920 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  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-52-generic 
root=UUID=dfb5d6fd-4a4e-471d-bb00-77a6729533d8 ro quiet splash pci=nommconf 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-03 (214 days ago)
  dmi.bios.date: 04/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.80
  dmi.board.name: X99 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.80:bd04/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  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 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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

** Description changed:

  One monitor is a 4K monitor scaled to 1.5x, the other is a normal
  1920x1080 monitor scaled to 1x.
  
- While Firefox is already open, after logging in with the lock screen,
- sometimes Firefox will lose the titlebar, address bar, buttons, and
- bookmark bar. The website being displayed will still show, however not
- all features are usable (right click menu, mouse icon doesn't change).
+ While Firefox is already open, after logging in with the lock

[Desktop-packages] [Bug 1902832] Re: lftp support broken - exits with error_code -11 on Bionic

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

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

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

Title:
  lftp support broken - exits with error_code -11 on Bionic

Status in duplicity package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Confirmed
Status in duplicity source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Confirmed

Bug description:
  We are using duplicity 0.7.17 and Ubuntu 18.04 LTS.

  After upgrading these packages in Ubuntu:

  Upgrade: libc-bin:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: locales:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: multiarch-support:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: libc6-dev:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3), 
  Upgrade: libc6:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: libc-dev-bin:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)

  the duplicity/lftp support stopped working. It worked for years just
  fine before that.

  Basic error message is:

  Giving up after 5 attempts. BackendException: Error running 'lftp -c
  "source /tmp/duplicity-gVCsqa-tempdir/mkstemp-serY3Q-1; ( cd
  etc_backup/ && ls ) || ( mkdir -p etc_backup/ && cd etc_backup/ && ls
  )"': returned -11, with output:

  Error/debug output:

  Using archive dir: /root/.duplicity/etc_daily
  Using backup name: etc_daily
  GPG binary is gpg, version 2.2.4
  Import of duplicity.backends.acdclibackend Succeeded
  Import of duplicity.backends.azurebackend Succeeded
  Import of duplicity.backends.b2backend Succeeded
  Import of duplicity.backends.botobackend Succeeded
  Import of duplicity.backends.cfbackend Succeeded
  Import of duplicity.backends.dpbxbackend Failed: No module named dropbox
  Import of duplicity.backends.gdocsbackend Succeeded
  Import of duplicity.backends.giobackend Succeeded
  Import of duplicity.backends.hsibackend Succeeded
  Import of duplicity.backends.hubicbackend Succeeded
  Import of duplicity.backends.imapbackend Succeeded
  Import of duplicity.backends.lftpbackend Succeeded
  Import of duplicity.backends.localbackend Succeeded
  Import of duplicity.backends.mediafirebackend Succeeded
  Import of duplicity.backends.megabackend Succeeded
  Import of duplicity.backends.multibackend Succeeded
  Import of duplicity.backends.ncftpbackend Succeeded
  Import of duplicity.backends.onedrivebackend Succeeded
  Import of duplicity.backends.par2backend Succeeded
  Import of duplicity.backends.pydrivebackend Succeeded
  Import of duplicity.backends.rsyncbackend Succeeded
  Import of duplicity.backends.ssh_paramiko_backend Succeeded
  Import of duplicity.backends.ssh_pexpect_backend Succeeded
  Import of duplicity.backends.swiftbackend Succeeded
  Import of duplicity.backends.sxbackend Succeeded
  Import of duplicity.backends.tahoebackend Succeeded
  Import of duplicity.backends.webdavbackend Succeeded
  LFTP version is 4.8.1
  Using temporary directory /tmp/duplicity-_Mgype-tempdir
  Registering (mkstemp) temporary file 
/tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1
  SETTINGS:
  set ssl:verify-certificate true
  set ftp:ssl-allow false
  set http:use-propfind true
  set net:timeout 30
  set net:max-retries 5
  set ftp:passive-mode on
  debug
  open -u ',' 
ftp://hostname.your-storagebox.de

  Main action: remove-all-but-n-full
  Acquiring lockfile /root/.duplicity/etc_daily/lockfile
  

  duplicity 0.7.17 (February 26, 2018)
  Args: /usr/bin/duplicity remove-all-but-n-full 7 -v9 
--archive-dir=/root/.duplicity --force --name etc_daily --no-encryption 
ftp://@.your-storagebox.de/etc_full
  Linux  4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 
13:03:05 UTC 2020 x86_64 x86_64
  /usr/bin/python2 2.7.17 (default, Sep 30 2020, 13:38:04)
  [GCC 7.5.0]
  

  CMD: lftp -c "source /tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1; ( cd 
etc_full/ && ls ) || ( mkdir -p etc_full/ && cd etc_full/ && ls )"
  Reading results of 'lftp -c "source 
/tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1; ( cd etc_full/ && ls ) || ( 
mkdir -p etc_full/ && cd etc_full/ && ls )"'
  Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in 
inner_retry
  return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 578, in 
list
  return [tobytes(x) for x in self.backend._list()]
File "/usr/lib/python2.7/dist-packages/duplicity/backends/lftpbackend.py", 
line 181, in _list
  _, l, e = self.subprocess_popen(commandline)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 499, in 
subprocess_popen
  (logstr, result,

[Desktop-packages] [Bug 1902832] Re: lftp support broken - exits with error_code -11 on Bionic

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

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

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

Title:
  lftp support broken - exits with error_code -11 on Bionic

Status in duplicity package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Confirmed
Status in duplicity source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Confirmed

Bug description:
  We are using duplicity 0.7.17 and Ubuntu 18.04 LTS.

  After upgrading these packages in Ubuntu:

  Upgrade: libc-bin:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: locales:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: multiarch-support:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: libc6-dev:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3), 
  Upgrade: libc6:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: libc-dev-bin:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)

  the duplicity/lftp support stopped working. It worked for years just
  fine before that.

  Basic error message is:

  Giving up after 5 attempts. BackendException: Error running 'lftp -c
  "source /tmp/duplicity-gVCsqa-tempdir/mkstemp-serY3Q-1; ( cd
  etc_backup/ && ls ) || ( mkdir -p etc_backup/ && cd etc_backup/ && ls
  )"': returned -11, with output:

  Error/debug output:

  Using archive dir: /root/.duplicity/etc_daily
  Using backup name: etc_daily
  GPG binary is gpg, version 2.2.4
  Import of duplicity.backends.acdclibackend Succeeded
  Import of duplicity.backends.azurebackend Succeeded
  Import of duplicity.backends.b2backend Succeeded
  Import of duplicity.backends.botobackend Succeeded
  Import of duplicity.backends.cfbackend Succeeded
  Import of duplicity.backends.dpbxbackend Failed: No module named dropbox
  Import of duplicity.backends.gdocsbackend Succeeded
  Import of duplicity.backends.giobackend Succeeded
  Import of duplicity.backends.hsibackend Succeeded
  Import of duplicity.backends.hubicbackend Succeeded
  Import of duplicity.backends.imapbackend Succeeded
  Import of duplicity.backends.lftpbackend Succeeded
  Import of duplicity.backends.localbackend Succeeded
  Import of duplicity.backends.mediafirebackend Succeeded
  Import of duplicity.backends.megabackend Succeeded
  Import of duplicity.backends.multibackend Succeeded
  Import of duplicity.backends.ncftpbackend Succeeded
  Import of duplicity.backends.onedrivebackend Succeeded
  Import of duplicity.backends.par2backend Succeeded
  Import of duplicity.backends.pydrivebackend Succeeded
  Import of duplicity.backends.rsyncbackend Succeeded
  Import of duplicity.backends.ssh_paramiko_backend Succeeded
  Import of duplicity.backends.ssh_pexpect_backend Succeeded
  Import of duplicity.backends.swiftbackend Succeeded
  Import of duplicity.backends.sxbackend Succeeded
  Import of duplicity.backends.tahoebackend Succeeded
  Import of duplicity.backends.webdavbackend Succeeded
  LFTP version is 4.8.1
  Using temporary directory /tmp/duplicity-_Mgype-tempdir
  Registering (mkstemp) temporary file 
/tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1
  SETTINGS:
  set ssl:verify-certificate true
  set ftp:ssl-allow false
  set http:use-propfind true
  set net:timeout 30
  set net:max-retries 5
  set ftp:passive-mode on
  debug
  open -u ',' 
ftp://hostname.your-storagebox.de

  Main action: remove-all-but-n-full
  Acquiring lockfile /root/.duplicity/etc_daily/lockfile
  

  duplicity 0.7.17 (February 26, 2018)
  Args: /usr/bin/duplicity remove-all-but-n-full 7 -v9 
--archive-dir=/root/.duplicity --force --name etc_daily --no-encryption 
ftp://@.your-storagebox.de/etc_full
  Linux  4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 
13:03:05 UTC 2020 x86_64 x86_64
  /usr/bin/python2 2.7.17 (default, Sep 30 2020, 13:38:04)
  [GCC 7.5.0]
  

  CMD: lftp -c "source /tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1; ( cd 
etc_full/ && ls ) || ( mkdir -p etc_full/ && cd etc_full/ && ls )"
  Reading results of 'lftp -c "source 
/tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1; ( cd etc_full/ && ls ) || ( 
mkdir -p etc_full/ && cd etc_full/ && ls )"'
  Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in 
inner_retry
  return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 578, in 
list
  return [tobytes(x) for x in self.backend._list()]
File "/usr/lib/python2.7/dist-packages/duplicity/backends/lftpbackend.py", 
line 181, in _list
  _, l, e = self.subprocess_popen(commandline)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 499, in 
subprocess_popen
  (logstr, result, stdout

[Desktop-packages] [Bug 1902832] Re: lftp support broken - exits with error_code -11 on Bionic

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

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

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

Title:
  lftp support broken - exits with error_code -11 on Bionic

Status in duplicity package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Confirmed
Status in duplicity source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Confirmed

Bug description:
  We are using duplicity 0.7.17 and Ubuntu 18.04 LTS.

  After upgrading these packages in Ubuntu:

  Upgrade: libc-bin:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: locales:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: multiarch-support:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: libc6-dev:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3), 
  Upgrade: libc6:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: libc-dev-bin:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)

  the duplicity/lftp support stopped working. It worked for years just
  fine before that.

  Basic error message is:

  Giving up after 5 attempts. BackendException: Error running 'lftp -c
  "source /tmp/duplicity-gVCsqa-tempdir/mkstemp-serY3Q-1; ( cd
  etc_backup/ && ls ) || ( mkdir -p etc_backup/ && cd etc_backup/ && ls
  )"': returned -11, with output:

  Error/debug output:

  Using archive dir: /root/.duplicity/etc_daily
  Using backup name: etc_daily
  GPG binary is gpg, version 2.2.4
  Import of duplicity.backends.acdclibackend Succeeded
  Import of duplicity.backends.azurebackend Succeeded
  Import of duplicity.backends.b2backend Succeeded
  Import of duplicity.backends.botobackend Succeeded
  Import of duplicity.backends.cfbackend Succeeded
  Import of duplicity.backends.dpbxbackend Failed: No module named dropbox
  Import of duplicity.backends.gdocsbackend Succeeded
  Import of duplicity.backends.giobackend Succeeded
  Import of duplicity.backends.hsibackend Succeeded
  Import of duplicity.backends.hubicbackend Succeeded
  Import of duplicity.backends.imapbackend Succeeded
  Import of duplicity.backends.lftpbackend Succeeded
  Import of duplicity.backends.localbackend Succeeded
  Import of duplicity.backends.mediafirebackend Succeeded
  Import of duplicity.backends.megabackend Succeeded
  Import of duplicity.backends.multibackend Succeeded
  Import of duplicity.backends.ncftpbackend Succeeded
  Import of duplicity.backends.onedrivebackend Succeeded
  Import of duplicity.backends.par2backend Succeeded
  Import of duplicity.backends.pydrivebackend Succeeded
  Import of duplicity.backends.rsyncbackend Succeeded
  Import of duplicity.backends.ssh_paramiko_backend Succeeded
  Import of duplicity.backends.ssh_pexpect_backend Succeeded
  Import of duplicity.backends.swiftbackend Succeeded
  Import of duplicity.backends.sxbackend Succeeded
  Import of duplicity.backends.tahoebackend Succeeded
  Import of duplicity.backends.webdavbackend Succeeded
  LFTP version is 4.8.1
  Using temporary directory /tmp/duplicity-_Mgype-tempdir
  Registering (mkstemp) temporary file 
/tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1
  SETTINGS:
  set ssl:verify-certificate true
  set ftp:ssl-allow false
  set http:use-propfind true
  set net:timeout 30
  set net:max-retries 5
  set ftp:passive-mode on
  debug
  open -u ',' 
ftp://hostname.your-storagebox.de

  Main action: remove-all-but-n-full
  Acquiring lockfile /root/.duplicity/etc_daily/lockfile
  

  duplicity 0.7.17 (February 26, 2018)
  Args: /usr/bin/duplicity remove-all-but-n-full 7 -v9 
--archive-dir=/root/.duplicity --force --name etc_daily --no-encryption 
ftp://@.your-storagebox.de/etc_full
  Linux  4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 
13:03:05 UTC 2020 x86_64 x86_64
  /usr/bin/python2 2.7.17 (default, Sep 30 2020, 13:38:04)
  [GCC 7.5.0]
  

  CMD: lftp -c "source /tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1; ( cd 
etc_full/ && ls ) || ( mkdir -p etc_full/ && cd etc_full/ && ls )"
  Reading results of 'lftp -c "source 
/tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1; ( cd etc_full/ && ls ) || ( 
mkdir -p etc_full/ && cd etc_full/ && ls )"'
  Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in 
inner_retry
  return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 578, in 
list
  return [tobytes(x) for x in self.backend._list()]
File "/usr/lib/python2.7/dist-packages/duplicity/backends/lftpbackend.py", 
line 181, in _list
  _, l, e = self.subprocess_popen(commandline)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 499, in 
subprocess_popen
  (logstr, result, stdout +

[Desktop-packages] [Bug 1902832] Re: lftp support broken - exits with error_code -11 on Bionic

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

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

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

Title:
  lftp support broken - exits with error_code -11 on Bionic

Status in duplicity package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Confirmed
Status in duplicity source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Confirmed

Bug description:
  We are using duplicity 0.7.17 and Ubuntu 18.04 LTS.

  After upgrading these packages in Ubuntu:

  Upgrade: libc-bin:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: locales:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: multiarch-support:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: libc6-dev:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3), 
  Upgrade: libc6:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: libc-dev-bin:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)

  the duplicity/lftp support stopped working. It worked for years just
  fine before that.

  Basic error message is:

  Giving up after 5 attempts. BackendException: Error running 'lftp -c
  "source /tmp/duplicity-gVCsqa-tempdir/mkstemp-serY3Q-1; ( cd
  etc_backup/ && ls ) || ( mkdir -p etc_backup/ && cd etc_backup/ && ls
  )"': returned -11, with output:

  Error/debug output:

  Using archive dir: /root/.duplicity/etc_daily
  Using backup name: etc_daily
  GPG binary is gpg, version 2.2.4
  Import of duplicity.backends.acdclibackend Succeeded
  Import of duplicity.backends.azurebackend Succeeded
  Import of duplicity.backends.b2backend Succeeded
  Import of duplicity.backends.botobackend Succeeded
  Import of duplicity.backends.cfbackend Succeeded
  Import of duplicity.backends.dpbxbackend Failed: No module named dropbox
  Import of duplicity.backends.gdocsbackend Succeeded
  Import of duplicity.backends.giobackend Succeeded
  Import of duplicity.backends.hsibackend Succeeded
  Import of duplicity.backends.hubicbackend Succeeded
  Import of duplicity.backends.imapbackend Succeeded
  Import of duplicity.backends.lftpbackend Succeeded
  Import of duplicity.backends.localbackend Succeeded
  Import of duplicity.backends.mediafirebackend Succeeded
  Import of duplicity.backends.megabackend Succeeded
  Import of duplicity.backends.multibackend Succeeded
  Import of duplicity.backends.ncftpbackend Succeeded
  Import of duplicity.backends.onedrivebackend Succeeded
  Import of duplicity.backends.par2backend Succeeded
  Import of duplicity.backends.pydrivebackend Succeeded
  Import of duplicity.backends.rsyncbackend Succeeded
  Import of duplicity.backends.ssh_paramiko_backend Succeeded
  Import of duplicity.backends.ssh_pexpect_backend Succeeded
  Import of duplicity.backends.swiftbackend Succeeded
  Import of duplicity.backends.sxbackend Succeeded
  Import of duplicity.backends.tahoebackend Succeeded
  Import of duplicity.backends.webdavbackend Succeeded
  LFTP version is 4.8.1
  Using temporary directory /tmp/duplicity-_Mgype-tempdir
  Registering (mkstemp) temporary file 
/tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1
  SETTINGS:
  set ssl:verify-certificate true
  set ftp:ssl-allow false
  set http:use-propfind true
  set net:timeout 30
  set net:max-retries 5
  set ftp:passive-mode on
  debug
  open -u ',' 
ftp://hostname.your-storagebox.de

  Main action: remove-all-but-n-full
  Acquiring lockfile /root/.duplicity/etc_daily/lockfile
  

  duplicity 0.7.17 (February 26, 2018)
  Args: /usr/bin/duplicity remove-all-but-n-full 7 -v9 
--archive-dir=/root/.duplicity --force --name etc_daily --no-encryption 
ftp://@.your-storagebox.de/etc_full
  Linux  4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 
13:03:05 UTC 2020 x86_64 x86_64
  /usr/bin/python2 2.7.17 (default, Sep 30 2020, 13:38:04)
  [GCC 7.5.0]
  

  CMD: lftp -c "source /tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1; ( cd 
etc_full/ && ls ) || ( mkdir -p etc_full/ && cd etc_full/ && ls )"
  Reading results of 'lftp -c "source 
/tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1; ( cd etc_full/ && ls ) || ( 
mkdir -p etc_full/ && cd etc_full/ && ls )"'
  Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in 
inner_retry
  return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 578, in 
list
  return [tobytes(x) for x in self.backend._list()]
File "/usr/lib/python2.7/dist-packages/duplicity/backends/lftpbackend.py", 
line 181, in _list
  _, l, e = self.subprocess_popen(commandline)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 499, in 
subprocess_popen
  (logstr, result, stdout + '

[Desktop-packages] [Bug 1902832] Re: lftp support broken - exits with error_code -11 on Bionic

2020-11-04 Thread Wolfgang Karall-Ahlborn

When version 2.27-3ubuntu1.2 is installed (e.g. after the downgrade)
it's best to replace the above pinning file in #4 with

# cat

[Desktop-packages] [Bug 1902832] Re: lftp support broken - exits with error_code -11 on Bionic

2020-11-04 Thread Wolfgang Karall-Ahlborn

Hi,

attached a strace file of the lftp call when run with version
2.27-3ubuntu1.3:

# strace -f -o /tmp/lftp.strace lftp -c "source /scratch/duplicity-temp
/duplicity-RHpHVx-tempdir/mkstemp-jC4mJb-1; ( cd some-stage.example.org/
&& ls ) || ( mkdir -p some-stage.example.org/ && cd some-
stage.example.org/ && ls )"

dmesg shows:

[42084.466069] traps: lftp[8067] general protection ip:55792fb3a4b0
sp:7ffd77402a08 error:0 in lftp[55792fa2a000+14e000]


** Attachment added: "lftp.strace"
   
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1902832/+attachment/5431159/+files/lftp.strace

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

Title:
  lftp support broken - exits with error_code -11 on Bionic

Status in duplicity package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Confirmed
Status in duplicity source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Confirmed

Bug description:
  We are using duplicity 0.7.17 and Ubuntu 18.04 LTS.

  After upgrading these packages in Ubuntu:

  Upgrade: libc-bin:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: locales:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: multiarch-support:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: libc6-dev:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3), 
  Upgrade: libc6:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: libc-dev-bin:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)

  the duplicity/lftp support stopped working. It worked for years just
  fine before that.

  Basic error message is:

  Giving up after 5 attempts. BackendException: Error running 'lftp -c
  "source /tmp/duplicity-gVCsqa-tempdir/mkstemp-serY3Q-1; ( cd
  etc_backup/ && ls ) || ( mkdir -p etc_backup/ && cd etc_backup/ && ls
  )"': returned -11, with output:

  Error/debug output:

  Using archive dir: /root/.duplicity/etc_daily
  Using backup name: etc_daily
  GPG binary is gpg, version 2.2.4
  Import of duplicity.backends.acdclibackend Succeeded
  Import of duplicity.backends.azurebackend Succeeded
  Import of duplicity.backends.b2backend Succeeded
  Import of duplicity.backends.botobackend Succeeded
  Import of duplicity.backends.cfbackend Succeeded
  Import of duplicity.backends.dpbxbackend Failed: No module named dropbox
  Import of duplicity.backends.gdocsbackend Succeeded
  Import of duplicity.backends.giobackend Succeeded
  Import of duplicity.backends.hsibackend Succeeded
  Import of duplicity.backends.hubicbackend Succeeded
  Import of duplicity.backends.imapbackend Succeeded
  Import of duplicity.backends.lftpbackend Succeeded
  Import of duplicity.backends.localbackend Succeeded
  Import of duplicity.backends.mediafirebackend Succeeded
  Import of duplicity.backends.megabackend Succeeded
  Import of duplicity.backends.multibackend Succeeded
  Import of duplicity.backends.ncftpbackend Succeeded
  Import of duplicity.backends.onedrivebackend Succeeded
  Import of duplicity.backends.par2backend Succeeded
  Import of duplicity.backends.pydrivebackend Succeeded
  Import of duplicity.backends.rsyncbackend Succeeded
  Import of duplicity.backends.ssh_paramiko_backend Succeeded
  Import of duplicity.backends.ssh_pexpect_backend Succeeded
  Import of duplicity.backends.swiftbackend Succeeded
  Import of duplicity.backends.sxbackend Succeeded
  Import of duplicity.backends.tahoebackend Succeeded
  Import of duplicity.backends.webdavbackend Succeeded
  LFTP version is 4.8.1
  Using temporary directory /tmp/duplicity-_Mgype-tempdir
  Registering (mkstemp) temporary file 
/tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1
  SETTINGS:
  set ssl:verify-certificate true
  set ftp:ssl-allow false
  set http:use-propfind true
  set net:timeout 30
  set net:max-retries 5
  set ftp:passive-mode on
  debug
  open -u ',' 
ftp://hostname.your-storagebox.de

  Main action: remove-all-but-n-full
  Acquiring lockfile /root/.duplicity/etc_daily/lockfile
  

  duplicity 0.7.17 (February 26, 2018)
  Args: /usr/bin/duplicity remove-all-but-n-full 7 -v9 
--archive-dir=/root/.duplicity --force --name etc_daily --no-encryption 
ftp://@.your-storagebox.de/etc_full
  Linux  4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 
13:03:05 UTC 2020 x86_64 x86_64
  /usr/bin/python2 2.7.17 (default, Sep 30 2020, 13:38:04)
  [GCC 7.5.0]
  

  CMD: lftp -c "source /tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1; ( cd 
etc_full/ && ls ) || ( mkdir -p etc_full/ && cd etc_full/ && ls )"
  Reading results of 'lftp -c "source 
/tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1; ( cd etc_full/ && ls ) || ( 
mkdir -p etc_full/ && cd etc_full/ && ls )"'
  Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in

[Desktop-packages] [Bug 1902832] Re: lftp support broken - exits with error_code -11 on Bionic

2020-11-04 Thread Wolfgang Karall-Ahlborn

Hi,

this hit me as well on multiple bionic installs, downgraded via APT
pinning the old version as it's still in bionic-security

# cat < 
/etc/apt/preferences.d/20201104-force-libc6-version-to-unbreak-duplicity 
Package: libc6 libc-bin multiarch-support locales libc6-dev libc-dev-bin
Pin: version 2.27-3ubuntu1.2
Pin-Priority: 2000

EOF

and running apt dist-upgrade. After the downgrade, lftp worked again.

Cheers
Wolfgang

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

Title:
  lftp support broken - exits with error_code -11 on Bionic

Status in duplicity package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in duplicity source package in Bionic:
  New
Status in glibc source package in Bionic:
  New

Bug description:
  We are using duplicity 0.7.17 and Ubuntu 18.04 LTS.

  After upgrading these packages in Ubuntu:

  Upgrade: libc-bin:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: locales:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: multiarch-support:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: libc6-dev:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3), 
  Upgrade: libc6:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: libc-dev-bin:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)

  the duplicity/lftp support stopped working. It worked for years just
  fine before that.

  Basic error message is:

  Giving up after 5 attempts. BackendException: Error running 'lftp -c
  "source /tmp/duplicity-gVCsqa-tempdir/mkstemp-serY3Q-1; ( cd
  etc_backup/ && ls ) || ( mkdir -p etc_backup/ && cd etc_backup/ && ls
  )"': returned -11, with output:

  Error/debug output:

  Using archive dir: /root/.duplicity/etc_daily
  Using backup name: etc_daily
  GPG binary is gpg, version 2.2.4
  Import of duplicity.backends.acdclibackend Succeeded
  Import of duplicity.backends.azurebackend Succeeded
  Import of duplicity.backends.b2backend Succeeded
  Import of duplicity.backends.botobackend Succeeded
  Import of duplicity.backends.cfbackend Succeeded
  Import of duplicity.backends.dpbxbackend Failed: No module named dropbox
  Import of duplicity.backends.gdocsbackend Succeeded
  Import of duplicity.backends.giobackend Succeeded
  Import of duplicity.backends.hsibackend Succeeded
  Import of duplicity.backends.hubicbackend Succeeded
  Import of duplicity.backends.imapbackend Succeeded
  Import of duplicity.backends.lftpbackend Succeeded
  Import of duplicity.backends.localbackend Succeeded
  Import of duplicity.backends.mediafirebackend Succeeded
  Import of duplicity.backends.megabackend Succeeded
  Import of duplicity.backends.multibackend Succeeded
  Import of duplicity.backends.ncftpbackend Succeeded
  Import of duplicity.backends.onedrivebackend Succeeded
  Import of duplicity.backends.par2backend Succeeded
  Import of duplicity.backends.pydrivebackend Succeeded
  Import of duplicity.backends.rsyncbackend Succeeded
  Import of duplicity.backends.ssh_paramiko_backend Succeeded
  Import of duplicity.backends.ssh_pexpect_backend Succeeded
  Import of duplicity.backends.swiftbackend Succeeded
  Import of duplicity.backends.sxbackend Succeeded
  Import of duplicity.backends.tahoebackend Succeeded
  Import of duplicity.backends.webdavbackend Succeeded
  LFTP version is 4.8.1
  Using temporary directory /tmp/duplicity-_Mgype-tempdir
  Registering (mkstemp) temporary file 
/tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1
  SETTINGS:
  set ssl:verify-certificate true
  set ftp:ssl-allow false
  set http:use-propfind true
  set net:timeout 30
  set net:max-retries 5
  set ftp:passive-mode on
  debug
  open -u ',' 
ftp://hostname.your-storagebox.de

  Main action: remove-all-but-n-full
  Acquiring lockfile /root/.duplicity/etc_daily/lockfile
  

  duplicity 0.7.17 (February 26, 2018)
  Args: /usr/bin/duplicity remove-all-but-n-full 7 -v9 
--archive-dir=/root/.duplicity --force --name etc_daily --no-encryption 
ftp://@.your-storagebox.de/etc_full
  Linux  4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 
13:03:05 UTC 2020 x86_64 x86_64
  /usr/bin/python2 2.7.17 (default, Sep 30 2020, 13:38:04)
  [GCC 7.5.0]
  

  CMD: lftp -c "source /tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1; ( cd 
etc_full/ && ls ) || ( mkdir -p etc_full/ && cd etc_full/ && ls )"
  Reading results of 'lftp -c "source 
/tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1; ( cd etc_full/ && ls ) || ( 
mkdir -p etc_full/ && cd etc_full/ && ls )"'
  Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in 
inner_retry
  return fn(self, *args)
File "/usr/lib/python2.7/

[Desktop-packages] [Bug 1880405] Re: High CPU and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9

2020-11-04 Thread Steve Murphy

I hope this helps: I see these errors in my syslog:

Nov  4 10:43:32 parse2 gnome-shell[4026701]: JS ERROR: TypeError:
windowActor is
null#012_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28#012vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14

Nov  4 11:17:38 parse2 gnome-shell[4026701]: message repeated 34072
times: [ JS ERROR: TypeError: null has no
properties#012_onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9]

Nov  4 10:51:50 parse2 gnome-shell[11582]: 
[11584:11584:1104/105150.374036:ERROR:CONSOLE(1)] "[Shields]: Can't request 
shields panel data. Error: No tab url specified", source: 
chrome-extension://mnojpmjdmbbfme
jpflffifhffcmidifd/out/brave_extension_background.bundle.js (1)


Yet More Info:
While it was running slow, I did a gcore, and it showed a single active thread 
(90% CPU) in the garbage collector. That may have nothing to do with this, but 
who knows...


gnome-shell:  3.36.4
Ubuntu 20.04
Hardware: 64g memory, 1Tb NVME drive, Asus ROG Strix GeForce RTX 2060, 4 
Monitors
  Cores: 16  Threads: 32  AMD Ryzen 3950X
browser1 = brave tabs = 67
browser2 = firefox tabs= 64
various other windows Quake, rocketchat, Thunderbird, MATE terminal

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

Title:
  High CPU and journal flooded with: JS ERROR: TypeError: null has no
  properties
  _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9

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

Bug description:
  O.k. it is an old Lenovo thinkpad T410. However, in 18.04, 19.04 and 19.10 I 
did face these problems. The sometimes I have to wait 10 seconds to see if a 
window reacts or not. It is hard to use. 
Installiert:   3.36.1-5ubuntu2
Installationskandidat: 3.36.2-1ubuntu1~20.04.1
Versionstabelle:
   3.36.2-1ubuntu1~20.04.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   *** 3.36.1-5ubuntu2 100
  100 /var/lib/dpkg/status
   3.36.1-5ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Sun May 24 15:43:34 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-02-05 (109 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-05-08 (15 days ago)

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

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

[Desktop-packages] [Bug 1902921] Re: Scaling one monitor (to 1.5x in my case) can cause Firefox to lose window features (titlebar, buttons, bookmark bar)

I've attached an image of Netflix showing on the Dell monitor after I
changed the zoom level back to 1.5x for the Samsung monitor. The image
shows Firefox without the window border. Netflix was not in fullscreen
mode.

** Attachment added: "Netflix on Dell monitor without window features, not in 
fullscreen mode"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1902921/+attachment/5431155/+files/Screenshot_2020-11-04_09-55-18.png

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

Title:
  Scaling one monitor (to 1.5x in my case) can cause Firefox to lose
  window features (titlebar, buttons, bookmark bar)

Status in xorg package in Ubuntu:
  New

Bug description:
  One monitor is a 4K monitor scaled to 1.5x, the other is a normal
  1920x1080 monitor scaled to 1x.

  While Firefox is already open, after logging into the lock screen,
  sometimes Firefox will lose the titlebar, address bar, buttons, and
  bookmark bar. The website being displayed will still show, however not
  all features are usable (right click menu, mouse icon doesn't change).

  Reproduction steps:

  - Change zoom level of one or more monitors to >1.0 but less than 2.0 (have 
not tested with non-fractional zooms)
  - Open Firefox and browse to any website
  - Lock screen or leave computer alone until the screen locks.
  - Login
  - Firefox may have lost the window chrome

  Workaround:

  - Open Display Settings
  - Change display settings or zoom level, then change back.

  Computer info:

  - Ubuntu 20.04.1
  - Fractional Scaling enabled
  - NVidia GeForce GTX 1080/PCIe/SSE2
  - Gnome 3.36.3
  - X11
  - Samsung LU32J590 4K (3840x2160) @ 1.5x
  - Dell E2416Hb 1920x1080 rotated portrait left, right of Samsung

  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.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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  435.21  Sun Aug 25 08:17:57 
CDT 2019
   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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 09:31:17 2020
  DistUpgraded: 2020-04-03 12:51:44,815 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6188]
  InstallationDate: Installed on 2018-04-28 (920 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  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-52-generic 
root=UUID=dfb5d6fd-4a4e-471d-bb00-77a6729533d8 ro quiet splash pci=nommconf 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-03 (214 days ago)
  dmi.bios.date: 04/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.80
  dmi.board.name: X99 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.80:bd04/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  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 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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:

[Desktop-packages] [Bug 1902766] Re: Automatic suspend when idle not working in 20.10

2020-11-04 Thread Jonathan Kamens

Darn it, I tested this like three times before reporting it, but I can
no longer reproduce the issue. Sorry to bother you.


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

Title:
  Automatic suspend when idle not working in 20.10

Status in gnome-shell package in Ubuntu:
  Invalid

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 1902921] [NEW] Scaling one monitor (to 1.5x in my case) can cause Firefox to lose window features (titlebar, buttons, bookmark bar)

Public bug reported:

One monitor is a 4K monitor scaled to 1.5x, the other is a normal
1920x1080 monitor scaled to 1x.

While Firefox is already open, after logging into the lock screen,
sometimes Firefox will lose the titlebar, address bar, buttons, and
bookmark bar. The website being displayed will still show, however not
all features are usable (right click menu, mouse icon doesn't change).

Reproduction steps:

- Change zoom level of one or more monitors to >1.0 but less than 2.0 (have not 
tested with non-fractional zooms)
- Open Firefox and browse to any website
- Lock screen or leave computer alone until the screen locks.
- Login
- Firefox may have lost the window chrome

Workaround:

- Open Display Settings
- Change display settings or zoom level, then change back.

Computer info:

- Ubuntu 20.04.1
- Fractional Scaling enabled
- NVidia GeForce GTX 1080/PCIe/SSE2
- Gnome 3.36.3
- X11
- Samsung LU32J590 4K (3840x2160) @ 1.5x
- Dell E2416Hb 1920x1080 rotated portrait left, right of Samsung

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.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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  435.21  Sun Aug 25 08:17:57 
CDT 2019
 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
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  4 09:31:17 2020
DistUpgraded: 2020-04-03 12:51:44,815 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6188]
InstallationDate: Installed on 2018-04-28 (920 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
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-52-generic 
root=UUID=dfb5d6fd-4a4e-471d-bb00-77a6729533d8 ro quiet splash pci=nommconf 
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-03 (214 days ago)
dmi.bios.date: 04/06/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.80
dmi.board.name: X99 Extreme4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.80:bd04/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
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 20.0.8-0ubuntu1~20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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 possible-manual-nvidia-install ubuntu

** Description changed:

  One monitor is a 4K monitor scaled to 1.5x, the other is a normal
  1920x1080 monitor scaled to 1x.
  
  While Firefox is already open, after logging into the lock screen,
  sometimes Firefox will lose the titlebar, address bar, buttons, and
  bookmark bar. The website being displayed will still show, however not
  all features are usable (right click menu, mouse icon doesn't change).
  
  Reproduction steps:
  
  - Change zoom level of one or more monitors to >1.0 but less than 2.0 (have 
not tested with non-fractional zooms)
  - Open Firefox and browse to any website
  -

[Desktop-packages] [Bug 1902290] Re: Sync libraw 0.20.2-1 (main) from Debian unstable (main)

2020-11-04 Thread Hans Joachim Desserud

Right, that makes sense :)

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

Title:
  Sync libraw 0.20.2-1 (main) from Debian unstable (main)

Status in libraw package in Ubuntu:
  New

Bug description:
  Please sync libraw 0.20.2-1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* debian/tests/build:
  - Use the correct compiler for proposed autopkgtest cross-testing
support.
* debian/tests/build:
  - Use the correct compiler for proposed autopkgtest cross-testing
support.
* debian/tests/build:
  - Use the correct compiler for proposed autopkgtest cross-testing
support.

  The compiler changes in the autopkgtest for cross-testing has been
  included in the Debian package.

  
  Changelog entries since current hirsute version 0.19.5-1ubuntu1:

  libraw (0.20.2-1) unstable; urgency=medium

* New upstream release

   -- Matteo F. Vescovi   Mon, 19 Oct 2020 23:00:12
  +0200

  libraw (0.20.0-4) unstable; urgency=medium

* Upload to unstable
* debian/libraw20.symbols: drop duplicates and
  restrict to 64 bits

   -- Matteo F. Vescovi   Tue, 18 Aug 2020 15:45:30
  +0200

  libraw (0.20.0-3) experimental; urgency=medium

* debian/libraw20.symbols: drop MISSING and update others

   -- Matteo F. Vescovi   Tue, 04 Aug 2020 23:43:02
  +0200

  libraw (0.20.0-2) experimental; urgency=medium

* debian/libraw20.symbols: file updated

   -- Matteo F. Vescovi   Tue, 04 Aug 2020 21:11:25
  +0200

  libraw (0.20.0-1) experimental; urgency=medium

[ Matteo F. Vescovi ]
* New upstream release
  This release fixes CVE-2020-15503:
  | LibRaw before 0.20-RC1 lacks a thumbnail size range check.
  | This affects decoders/unpack_thumb.cpp,
  | postprocessing/mem_image.cpp, and utils/thumb_utils.cpp.
  | For example,
  | malloc(sizeof(libraw_processed_image_t)+T.tlength) occurs
  | without validating T.tlength.
* debian/: SONAME bump 19 -> 20
* debian/control:
  - debhelper bump 12 -> 13
  - S-V bump 4.4.0 -> 4.5.0 (no changes needed)
  - RRR set
* debian/tests/smoketest: path adapted
* debian/copyright: entries for unused files and licenses removed
* debian/rules: drop useless files installation
* debian/libraw20.symbols: missing and new symbols added

[ Sebastien Bacher ]
* debian/tests/build: use the correct compiler for
  autopkgtest cross-testing. (Closes: #954886)

   -- Matteo F. Vescovi   Thu, 30 Jul 2020 00:09:36
  +0200

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

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

[Desktop-packages] [Bug 1902915] [NEW] (Snap) Cannot add an attachment to the message

2020-11-04 Thread Alec B

Public bug reported:

When writing a new mail, I cannot add an attachment to the message.

Steps to reproduce.
1 - Click write
2 - Click attach

Expected: A file choose dialog should appear.
Actual : Nothing is shown.

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

$snap info thunderbird
name:  thunderbird
summary:   Mozilla Thunderbird email application
publisher: Canonical✓
store-url: https://snapcraft.io/thunderbird
contact:   https://launchpad.net/distros/ubuntu/+source/thunderbird
license:   unset
description: |
  Thunderbird is a free and open source email, newsfeed, chat, and calendaring 
client, that’s easy
  to set up and customize. One of the core principles of Thunderbird is the use 
and promotion of
  open standards - this focus is a rejection of our world of closed platforms 
and services that
  can’t communicate with each other. We want our users to have freedom and 
choice in how they
  communicate.
commands:
  - thunderbird
snap-id:  k1Ml1O9GzSO2QftV0ZlWSbUfQ78nN460
tracking: latest/stable
refresh-date: yesterday at 23:37 CET
channels:
  latest/stable:78.4.0 2020-11-03 (92) 69MB -
  latest/candidate: ↑   
  latest/beta:  ↑   
  latest/edge:  78.4.0 2020-11-03 (92) 69MB -
installed:  78.4.0(92) 69MB -

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

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

Title:
  (Snap) Cannot add an attachment to the message

Status in thunderbird package in Ubuntu:
  New

Bug description:
  When writing a new mail, I cannot add an attachment to the message.

  Steps to reproduce.
  1 - Click write
  2 - Click attach

  Expected: A file choose dialog should appear.
  Actual : Nothing is shown.

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

  $snap info thunderbird
  name:  thunderbird
  summary:   Mozilla Thunderbird email application
  publisher: Canonical✓
  store-url: https://snapcraft.io/thunderbird
  contact:   https://launchpad.net/distros/ubuntu/+source/thunderbird
  license:   unset
  description: |
Thunderbird is a free and open source email, newsfeed, chat, and 
calendaring client, that’s easy
to set up and customize. One of the core principles of Thunderbird is the 
use and promotion of
open standards - this focus is a rejection of our world of closed platforms 
and services that
can’t communicate with each other. We want our users to have freedom and 
choice in how they
communicate.
  commands:
- thunderbird
  snap-id:  k1Ml1O9GzSO2QftV0ZlWSbUfQ78nN460
  tracking: latest/stable
  refresh-date: yesterday at 23:37 CET
  channels:
latest/stable:78.4.0 2020-11-03 (92) 69MB -
latest/candidate: ↑   
latest/beta:  ↑   
latest/edge:  78.4.0 2020-11-03 (92) 69MB -
  installed:  78.4.0(92) 69MB -

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

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

[Desktop-packages] [Bug 1902911] [NEW] GNOME desktop does not suspend on lid close with HDMI TV connected

2020-11-04 Thread Andrei Borzenkov

Public bug reported:

Ubuntu 20.04 with all current updates, GNOME/Wayland desktop, Dell
Latitude E5450 notebook.

I have external TV connected via HDMI and I want notebook to suspend
when I close lid even if TV is connected. This does not work. Even
though logind is configured to suspend in this case:

$ cat /etc/systemd/logind.conf.d/allow-suspend-with-hdmi.conf 
[Login]
HandleLidSwitchDocked=suspend
$ 

gnome-settings-daemon starts inhibitor as soon as it detects external
monitor:

WHO  UID  USER PID   COMMWHAT   
  WHY   
  MODE 
bor  1001 bor  96600 gsd-power   handle-lid-switch  
  External monitor attached or 
configuration changed recently block

so sytemd-logind does not initiate suspend, but there is also no code in
gnome-settings-daemon itself to handle lid close (as it completely
relies on systemd-logind today).

Ubuntu package includes patch ubuntu-lid-close-suspend.patch that
restores gsettings keys, but as there is no code to actually *use* these
keys patch has no effect:

$ gsettings list-recursively org.gnome.settings-daemon.plugins.power | grep -w 
lid
org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend'
org.gnome.settings-daemon.plugins.power lid-close-suspend-with-external-monitor 
true
org.gnome.settings-daemon.plugins.power lid-close-battery-action 'suspend'
$ 

This most trivial (untested) patch to use this settings seems to be:

diff --git a/plugins/power/gsd-power-manager.c 
b/plugins/power/gsd-power-manager.c
index c7a16e8d..9b7a99b5 100644
--- a/plugins/power/gsd-power-manager.c
+++ b/plugins/power/gsd-power-manager.c
@@ -1196,7 +1196,7 @@ upower_kbd_toggle (GsdPowerManager *manager,
 static gboolean
 suspend_on_lid_close (GsdPowerManager *manager)
 {
-return !external_monitor_is_connected (manager->rr_screen);
+return g_settings_get_boolean (manager->settings, 
"lid-close-suspend-with-external-monitor") || !external_monitor_is_connected 
(manager->rr_screen);
 }
 
 static gboolean

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-settings-daemon 3.36.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-25.26~20.04.1-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  4 18:43:56 2020
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
InstallationDate: Installed on 2015-07-02 (1952 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-settings-daemon
UpgradeStatus: Upgraded to focal on 2020-10-03 (32 days ago)

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


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

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

Title:
  GNOME desktop does not suspend on lid close with HDMI TV connected

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

Bug description:
  Ubuntu 20.04 with all current updates, GNOME/Wayland desktop, Dell
  Latitude E5450 notebook.

  I have external TV connected via HDMI and I want notebook to suspend
  when I close lid even if TV is connected. This does not work. Even
  though logind is configured to suspend in this case:

  $ cat /etc/systemd/logind.conf.d/allow-suspend-with-hdmi.conf 
  [Login]
  HandleLidSwitchDocked=suspend
  $ 

  gnome-settings-daemon starts inhibitor as soon as it detects external
  monitor:

  WHO  UID  USER PID   COMMWHAT 
WHY 
MODE 
  bor  1001 bor  96600 gsd-power   
handle-lid-switchExternal monitor 
attached or configuration changed recently block

  so sytemd-logind does not initiate suspend, but there is also no code
  in gnome-settings-daemon itself to handle lid close (as it completely
  relies on systemd-logind today).

  Ubuntu package includes patch ubuntu-lid-close-suspend.patch that
  restores gsettings keys, but as there is no code to actually *use*
  these keys patch has no effect:

  $ gsettings list-recursively org.gnome.settings-daemon.plugins.power | grep 
-w lid
  org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend'
  org.gnome.settings-daemon.plugins.power

[Desktop-packages] [Bug 1902907] [NEW] Developer Options shows 'groovy-proposed' instead of 'hirsute-proposed' (software-properties-gtk on 21.04 Hirsute Hippo)

2020-11-04 Thread Rudra Saraswat

Public bug reported:

When testing Hirsute Hippo (21.04), I found that software-properties-gtk
shows 'groovy-proposed' instead of 'hirsute-proposed'. This is from a
live session in VirtualBox.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: software-properties-gtk 0.99.3
ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
Uname: Linux 5.8.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.455
CurrentDesktop: Unity:Unity7:ubuntu
Date: Wed Nov  4 16:16:14 2020
LiveMediaBuild: Ubuntu Unity 21.04
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (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 software-properties in Ubuntu.
https://bugs.launchpad.net/bugs/1902907

Title:
  Developer Options shows 'groovy-proposed' instead of 'hirsute-
  proposed' (software-properties-gtk on 21.04 Hirsute Hippo)

Status in software-properties package in Ubuntu:
  New

Bug description:
  When testing Hirsute Hippo (21.04), I found that software-properties-
  gtk shows 'groovy-proposed' instead of 'hirsute-proposed'. This is
  from a live session in VirtualBox.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: software-properties-gtk 0.99.3
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Nov  4 16:16:14 2020
  LiveMediaBuild: Ubuntu Unity 21.04
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1902829] Re: Missing "Mobile Broadband" menu item

2020-11-04 Thread Gunnar Hjalmarsson

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

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: gnome-shell (Ubuntu Groovy)
   Status: Triaged => In Progress

** Changed in: gnome-shell (Ubuntu Groovy)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  Missing "Mobile Broadband" menu item

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell source package in Groovy:
  In Progress
Status in gnome-shell package in Debian:
  Unknown

Bug description:
  [Impact]

  gnome-shell does not show the "Mobile Broadband" menu item in Ubuntu
  20.10, which practically prevents net access for users who depend on
  mobile broadband. An upstream fix has recently been pushed.

  [Test case]

  * Install the binaries built by the gnome-shell source package from
  groovy-proposed

  * Reboot

  * Confirm with a USB dongle for mobile broadband that it's recognized
  in the system menu and allows you to connect.

  [Regression risk]

  The issue was triggered by a change to gjs, and the fix simply adds
  two property getters. Low regression risk.

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

-- 
Mailing list: https://launchpad.net/~desktop-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

@Matifou, the issue you describe is a different one and probably not a
bug. The type detection on remote location rely on the filename usually
because to guess from the content it would have to start downloading the
files which could be slow or expensive.

-- 
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 1887190] [PATCH 4/4] pinctrl: amd: remove debounce filter setting in irq type setting

2020-11-04 Thread Coiby Xu

Debounce filter setting should be independent from irq type setting
because according to the ACPI specs, there are separate arguments for
specifying debounce timeout and irq type in GpioIo and GpioInt.

This will fix broken touchpads for Lenovo Legion-5 AMD gaming laptops
including 15ARH05 (R7000) and R7000P whose BIOS set the debounce timeout
to 124.8ms which led to kernel receiving only ~7 HID reports per second.

Cc: Hans de Goede 
Cc: Andy Shevchenko 
Cc: 1887...@bugs.launchpad.net
BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190
Message-Id: 
Signed-off-by: Coiby Xu 
---
 drivers/pinctrl/pinctrl-amd.c | 7 ---
 1 file changed, 7 deletions(-)

diff --git a/drivers/pinctrl/pinctrl-amd.c b/drivers/pinctrl/pinctrl-amd.c
index 524d55546b61..5a1d518b563e 100644
--- a/drivers/pinctrl/pinctrl-amd.c
+++ b/drivers/pinctrl/pinctrl-amd.c
@@ -468,7 +468,6 @@ static int amd_gpio_irq_set_type(struct irq_data *d, 
unsigned int type)
pin_reg &= ~BIT(LEVEL_TRIG_OFF);
pin_reg &= ~(ACTIVE_LEVEL_MASK << ACTIVE_LEVEL_OFF);
pin_reg |= ACTIVE_HIGH << ACTIVE_LEVEL_OFF;
-   pin_reg |= DB_TYPE_REMOVE_GLITCH << DB_CNTRL_OFF;
irq_set_handler_locked(d, handle_edge_irq);
break;

@@ -476,7 +475,6 @@ static int amd_gpio_irq_set_type(struct irq_data *d, 
unsigned int type)
pin_reg &= ~BIT(LEVEL_TRIG_OFF);
pin_reg &= ~(ACTIVE_LEVEL_MASK << ACTIVE_LEVEL_OFF);
pin_reg |= ACTIVE_LOW << ACTIVE_LEVEL_OFF;
-   pin_reg |= DB_TYPE_REMOVE_GLITCH << DB_CNTRL_OFF;
irq_set_handler_locked(d, handle_edge_irq);
break;

@@ -484,7 +482,6 @@ static int amd_gpio_irq_set_type(struct irq_data *d, 
unsigned int type)
pin_reg &= ~BIT(LEVEL_TRIG_OFF);
pin_reg &= ~(ACTIVE_LEVEL_MASK << ACTIVE_LEVEL_OFF);
pin_reg |= BOTH_EADGE << ACTIVE_LEVEL_OFF;
-   pin_reg |= DB_TYPE_REMOVE_GLITCH << DB_CNTRL_OFF;
irq_set_handler_locked(d, handle_edge_irq);
break;

@@ -492,8 +489,6 @@ static int amd_gpio_irq_set_type(struct irq_data *d, 
unsigned int type)
pin_reg |= LEVEL_TRIGGER << LEVEL_TRIG_OFF;
pin_reg &= ~(ACTIVE_LEVEL_MASK << ACTIVE_LEVEL_OFF);
pin_reg |= ACTIVE_HIGH << ACTIVE_LEVEL_OFF;
-   pin_reg &= ~(DB_CNTRl_MASK << DB_CNTRL_OFF);
-   pin_reg |= DB_TYPE_PRESERVE_LOW_GLITCH << DB_CNTRL_OFF;
irq_set_handler_locked(d, handle_level_irq);
break;

@@ -501,8 +496,6 @@ static int amd_gpio_irq_set_type(struct irq_data *d, 
unsigned int type)
pin_reg |= LEVEL_TRIGGER << LEVEL_TRIG_OFF;
pin_reg &= ~(ACTIVE_LEVEL_MASK << ACTIVE_LEVEL_OFF);
pin_reg |= ACTIVE_LOW << ACTIVE_LEVEL_OFF;
-   pin_reg &= ~(DB_CNTRl_MASK << DB_CNTRL_OFF);
-   pin_reg |= DB_TYPE_PRESERVE_HIGH_GLITCH << DB_CNTRL_OFF;
irq_set_handler_locked(d, handle_level_irq);
break;

--
2.28.0

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

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

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

Bug description:
  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons

[Desktop-packages] [Bug 1902898] Re: power-button action inconsistent between user session and greeter

2020-11-04 Thread Iain Lane

Issue here I think is that we use per-session overrides for the majority
of our Ubuntu customisations, and these don't apply to greeter sessions.

** Tags added: rls-hh-incoming

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

Title:
  power-button action inconsistent between user session and greeter

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Focal:
  Confirmed
Status in ubuntu-settings source package in Groovy:
  New
Status in ubuntu-settings source package in Hirsute:
  New

Bug description:
  When a user is logged in to the Ubuntu desktop, a power button event
  will cause the user to be prompted to choose if they'd like to proceed
  with a shutdown. However, if the system is sitting at a greeter
  screen, a power button event will instead attempt a suspend w/o
  prompting. This is due to a different set of defaults for the greeter
  and the user:

  For a logged-in desktop user, they
  see:

  $ gsettings get org.gnome.settings-daemon.plugins.power
  power-button-action 'interactive'

  But the gdm user sees:
  $ sudo machinectl shell gdm@ /bin/bash
  Connected to the local host. Press ^] three times within 1s to exit session.
  gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power 
power-button-action
  'suspend'

  Changing the gdm user's setting to "interactive" using gsettings
  causes the greeter to begin prompting, consistent with the logged in
  user experience.

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

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

[Desktop-packages] [Bug 1902094] Re: High Xorg and gnome-shell CPU usage while Sound Settings opened

Could you report it upstream on https://gitlab.gnome.org/GNOME/gnome-
control-center/-/issues ?

The issues seems to due to the level indicators which keep refreshing

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

Title:
  High Xorg and gnome-shell CPU usage while Sound Settings opened

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

Bug description:
  Several days ago I found huge lags over all system on my Ubuntu
  20.04.1 LTS. Today I think found the problem, but not the reason. So
  when I open Settings -> Sound menu, the CPU usage comes to about 100%.
  If I close Settings window or go to other tab, it becomes OK. Nothing
  special in my sound configuration - monitor and notebook with built in
  audio and Bluetooth headset. Same worked just fine on Ubuntu 18.04
  LTS.

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-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] 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
  Date: Thu Oct 29 18:27:20 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-51-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0824]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0824]
  InstallationDate: Installed on 2020-09-12 (47 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. G5 5587
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=ef73abac-57c7-4134-90f3-1f52f41127a8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.0
  dmi.board.name: 03PVDF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd02/11/2019:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn03PVDF:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G5 5587
  dmi.product.sku: 0824
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/gnome-control-center/+bug/1902094/+subscriptions

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

[Desktop-packages] [Bug 1902900] [NEW] Workspaces menu flashes when moving between workspace A and workspace B having B Firefox with a video in full screen on it

2020-11-04 Thread Antonio Mazzarino

Public bug reported:

As I said in the title the menu with the 3 workspaces flashes if you
switch from a normal workspace to a workspace that has a fullscreen
video in Firefox.

How to reproduce

* Open Firefox
* Open a video in full screen (I tested prime video and twitch)
* Press and keep pressed ctrl-alt and arrow to move between workspaces
* When you reach the video workspaces still keep pressed ctrl-alt

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 82.0+build2-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
NonfreeKernelModules: wl
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  sibilant   2096 F pulseaudio
BuildID: 20201014125134
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  4 16:28:48 2020
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:361
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
InstallationDate: Installed on 2020-11-03 (1 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
IpRoute:
 default via 192.168.1.254 dev wlp2s0 proto dhcp metric 600 
 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.92 metric 600
Profile0Extensions: extensions.sqlite corrupt or missing
Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile0Locales: extensions.sqlite corrupt or missing
Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:361
Profile0PrefSources: prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 (Default) - LastVersion=None/None (Out of date)
 Profile0 - LastVersion=82.0/20201014125134 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/12/2020
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 232.0.0.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-6F01561E16C75D06
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-6F01561E16C75D06
dmi.modalias: 
dmi:bvnAppleInc.:bvr232.0.0.0.0:bd04/12/2020:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro9,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug focal

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

Title:
  Workspaces menu flashes  when moving between workspace A and workspace
  B having B  Firefox with a video in full screen on it

Status in firefox package in Ubuntu:
  New

Bug description:
  As I said in the title the menu with the 3 workspaces flashes if you
  switch from a normal workspace to a workspace that has a fullscreen
  video in Firefox.

  How to reproduce

  * Open Firefox
  * Open a video in full screen (I tested prime video and twitch)
  * Press and keep pressed ctrl-alt and arrow to move between workspaces
  * When you reach the video workspaces still keep pressed ctrl-alt

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 82.0+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: wl
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sibilant   2096 F pulseaudio
  BuildID: 20201014125134
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  4 16:28:48 2020
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:361
  DefaultProfileThemes: extensions.sqlite corrupt

[Desktop-packages] [Bug 1902899] [NEW] Color management is not quite good

2020-11-04 Thread Flávio Vivório Salles

Public bug reported:

While attempting to work with software like Figma, Inskcape and Gimp I
noticed that the screen I have doesn't show colors like in my iMac or in
WIndows. When I plug the same display on my laptop running Ubuntu 20.04
the colors just looks very opaque and desaturated. I looked on the web
for a tool to fix this but it just doesn't exist. I think this could be
a bug or a a problem with drivers. But theres no proprietary drivers for
this machine. The open source Intel drivers are just terrible. I suggest
Ubuntu developers include potentiometers to manage color saturation,
contrast, brightness and temperature under the "Color" tab on Ubuntu
settings pannel. When I go to the color section of the settings pannel
it only allows me to chose a color profile but I can't even adjust color
settings. I really wish Linux systems be more usable when it comes to
work with graphic software in the future.

My system info:

Lenovo Ideapad s145
Ubuntu 20.04.1 LTS
Processor: Intel® Core™ i3-8130U CPU @ 2.20GHz × 4 
Graphics: Mesa Intel® UHD Graphics 620 (KBL GT2)
GNOME version: 3.36.3
X11
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)

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
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  4 12:08:10 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: darling-mach, 0.1, 5.4.0-52-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics 620 [17aa:3fdf]
InstallationDate: Installed on 2020-10-14 (21 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated Camera
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 81XM
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=a08ea31a-d24d-4a85-b391-c1950060f906 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
dmi.bios.date: 10/12/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: CSCN10WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad S145-15IKB
dmi.modalias: 
dmi:bvnLENOVO:bvrCSCN10WW:bd10/12/2019:svnLENOVO:pn81XM:pvrLenovoIdeaPadS145-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IKB:
dmi.product.family: IdeaPad S145-15IKB
dmi.product.name: 81XM
dmi.product.sku: LENOVO_MT_81XM_BU_idea_FM_IdeaPad S145-15IKB
dmi.product.version: Lenovo IdeaPad S145-15IKB
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.103+git2011040630.5dea8f~oibaf~f
version.libgl1-mesa-dri: libgl1-mesa-dri 20.3~git2011040730.58e708~oibaf~f
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 N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

** 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/1902899

Title:
  Color management is not quite good

Status in xorg package in Ubuntu:
  New

Bug description:
  While attempting to work with software like Figma, Inskcape and Gimp I
  noticed that the screen I have doesn't show colors like in my iMac or
  in WIndows. When I plug the same display on my laptop running Ubuntu
  20.04 the colors just looks very opaque and desaturated. I looked on
  the web for a tool to fix this but it just doesn't exist. I think this
  could be a bug or a a problem with drivers.

[Desktop-packages] [Bug 1902832] Re: lftp support broken - exits with error_code -11

2020-11-04 Thread Balint Reczey

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

** Summary changed:

- lftp support broken - exits with error_code -11
+ lftp support broken - exits with error_code -11 on Bionic

** Also affects: glibc (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: duplicity (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  lftp support broken - exits with error_code -11 on Bionic

Status in duplicity package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in duplicity source package in Bionic:
  New
Status in glibc source package in Bionic:
  New

Bug description:
  We are using duplicity 0.7.17 and Ubuntu 18.04 LTS.

  After upgrading these packages in Ubuntu:

  Upgrade: libc-bin:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: locales:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: multiarch-support:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: libc6-dev:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3), 
  Upgrade: libc6:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: libc-dev-bin:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)

  the duplicity/lftp support stopped working. It worked for years just
  fine before that.

  Basic error message is:

  Giving up after 5 attempts. BackendException: Error running 'lftp -c
  "source /tmp/duplicity-gVCsqa-tempdir/mkstemp-serY3Q-1; ( cd
  etc_backup/ && ls ) || ( mkdir -p etc_backup/ && cd etc_backup/ && ls
  )"': returned -11, with output:

  Error/debug output:

  Using archive dir: /root/.duplicity/etc_daily
  Using backup name: etc_daily
  GPG binary is gpg, version 2.2.4
  Import of duplicity.backends.acdclibackend Succeeded
  Import of duplicity.backends.azurebackend Succeeded
  Import of duplicity.backends.b2backend Succeeded
  Import of duplicity.backends.botobackend Succeeded
  Import of duplicity.backends.cfbackend Succeeded
  Import of duplicity.backends.dpbxbackend Failed: No module named dropbox
  Import of duplicity.backends.gdocsbackend Succeeded
  Import of duplicity.backends.giobackend Succeeded
  Import of duplicity.backends.hsibackend Succeeded
  Import of duplicity.backends.hubicbackend Succeeded
  Import of duplicity.backends.imapbackend Succeeded
  Import of duplicity.backends.lftpbackend Succeeded
  Import of duplicity.backends.localbackend Succeeded
  Import of duplicity.backends.mediafirebackend Succeeded
  Import of duplicity.backends.megabackend Succeeded
  Import of duplicity.backends.multibackend Succeeded
  Import of duplicity.backends.ncftpbackend Succeeded
  Import of duplicity.backends.onedrivebackend Succeeded
  Import of duplicity.backends.par2backend Succeeded
  Import of duplicity.backends.pydrivebackend Succeeded
  Import of duplicity.backends.rsyncbackend Succeeded
  Import of duplicity.backends.ssh_paramiko_backend Succeeded
  Import of duplicity.backends.ssh_pexpect_backend Succeeded
  Import of duplicity.backends.swiftbackend Succeeded
  Import of duplicity.backends.sxbackend Succeeded
  Import of duplicity.backends.tahoebackend Succeeded
  Import of duplicity.backends.webdavbackend Succeeded
  LFTP version is 4.8.1
  Using temporary directory /tmp/duplicity-_Mgype-tempdir
  Registering (mkstemp) temporary file 
/tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1
  SETTINGS:
  set ssl:verify-certificate true
  set ftp:ssl-allow false
  set http:use-propfind true
  set net:timeout 30
  set net:max-retries 5
  set ftp:passive-mode on
  debug
  open -u ',' 
ftp://hostname.your-storagebox.de

  Main action: remove-all-but-n-full
  Acquiring lockfile /root/.duplicity/etc_daily/lockfile
  

  duplicity 0.7.17 (February 26, 2018)
  Args: /usr/bin/duplicity remove-all-but-n-full 7 -v9 
--archive-dir=/root/.duplicity --force --name etc_daily --no-encryption 
ftp://@.your-storagebox.de/etc_full
  Linux  4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 
13:03:05 UTC 2020 x86_64 x86_64
  /usr/bin/python2 2.7.17 (default, Sep 30 2020, 13:38:04)
  [GCC 7.5.0]
  

  CMD: lftp -c "source /tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1; ( cd 
etc_full/ && ls ) || ( mkdir -p etc_full/ && cd etc_full/ && ls )"
  Reading results of 'lftp -c "source 
/tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1; ( cd etc_full/ && ls ) || ( 
mkdir -p etc_full/ && cd etc_full/ && ls )"'
  Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in 
inner_retry
  return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 578, in 
list
  return [tobytes(x) for x in self.backend._list()]
File

[Desktop-packages] [Bug 1902898] [NEW] power-button action inconsistent between user session and greeter

2020-11-04 Thread dann frazier

Public bug reported:

When a user is logged in to the Ubuntu desktop, a power button event
will cause the user to be prompted to choose if they'd like to proceed
with a shutdown. However, if the system is sitting at a greeter screen,
a power button event will instead attempt a suspend w/o prompting. This
is due to a different set of defaults for the greeter and the user:

For a logged-in desktop user, they
see:

$ gsettings get org.gnome.settings-daemon.plugins.power
power-button-action 'interactive'

But the gdm user sees:
$ sudo machinectl shell gdm@ /bin/bash
Connected to the local host. Press ^] three times within 1s to exit session.
gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power power-button-action
'suspend'

Changing the gdm user's setting to "interactive" using gsettings causes
the greeter to begin prompting, consistent with the logged in user
experience.

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

** Affects: ubuntu-settings (Ubuntu Focal)
 Importance: Undecided
 Status: Confirmed

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

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

** Also affects: ubuntu-settings (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-settings (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

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

** Changed in: ubuntu-settings (Ubuntu Focal)
   Status: New => Confirmed

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

Title:
  power-button action inconsistent between user session and greeter

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Focal:
  Confirmed
Status in ubuntu-settings source package in Groovy:
  New
Status in ubuntu-settings source package in Hirsute:
  New

Bug description:
  When a user is logged in to the Ubuntu desktop, a power button event
  will cause the user to be prompted to choose if they'd like to proceed
  with a shutdown. However, if the system is sitting at a greeter
  screen, a power button event will instead attempt a suspend w/o
  prompting. This is due to a different set of defaults for the greeter
  and the user:

  For a logged-in desktop user, they
  see:

  $ gsettings get org.gnome.settings-daemon.plugins.power
  power-button-action 'interactive'

  But the gdm user sees:
  $ sudo machinectl shell gdm@ /bin/bash
  Connected to the local host. Press ^] three times within 1s to exit session.
  gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power 
power-button-action
  'suspend'

  Changing the gdm user's setting to "interactive" using gsettings
  causes the greeter to begin prompting, consistent with the logged in
  user experience.

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

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

[Desktop-packages] [Bug 1902832] Re: lftp support broken - exits with error_code -11

Thanks for the comment, I'm tagging as regression-update and notified
the glibc SRU uploader.

To downgrade glibc the easier way would be to go on
https://launchpad.net/ubuntu/+source/glibc/2.27-3ubuntu1.2 and download
the deb files you mentioned at the start of the description in a new
directory and 'dpkg -i *.deb' those, it would still be useful to confirm
that it indeed fixes the issue

could you maybe describe how to set up an environment to be able to test
the issue (server, command line and arguments, etc)?

** Tags added: regression-update

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

Title:
  lftp support broken - exits with error_code -11 on Bionic

Status in duplicity package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in duplicity source package in Bionic:
  New
Status in glibc source package in Bionic:
  New

Bug description:
  We are using duplicity 0.7.17 and Ubuntu 18.04 LTS.

  After upgrading these packages in Ubuntu:

  Upgrade: libc-bin:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: locales:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: multiarch-support:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: libc6-dev:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3), 
  Upgrade: libc6:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: libc-dev-bin:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)

  the duplicity/lftp support stopped working. It worked for years just
  fine before that.

  Basic error message is:

  Giving up after 5 attempts. BackendException: Error running 'lftp -c
  "source /tmp/duplicity-gVCsqa-tempdir/mkstemp-serY3Q-1; ( cd
  etc_backup/ && ls ) || ( mkdir -p etc_backup/ && cd etc_backup/ && ls
  )"': returned -11, with output:

  Error/debug output:

  Using archive dir: /root/.duplicity/etc_daily
  Using backup name: etc_daily
  GPG binary is gpg, version 2.2.4
  Import of duplicity.backends.acdclibackend Succeeded
  Import of duplicity.backends.azurebackend Succeeded
  Import of duplicity.backends.b2backend Succeeded
  Import of duplicity.backends.botobackend Succeeded
  Import of duplicity.backends.cfbackend Succeeded
  Import of duplicity.backends.dpbxbackend Failed: No module named dropbox
  Import of duplicity.backends.gdocsbackend Succeeded
  Import of duplicity.backends.giobackend Succeeded
  Import of duplicity.backends.hsibackend Succeeded
  Import of duplicity.backends.hubicbackend Succeeded
  Import of duplicity.backends.imapbackend Succeeded
  Import of duplicity.backends.lftpbackend Succeeded
  Import of duplicity.backends.localbackend Succeeded
  Import of duplicity.backends.mediafirebackend Succeeded
  Import of duplicity.backends.megabackend Succeeded
  Import of duplicity.backends.multibackend Succeeded
  Import of duplicity.backends.ncftpbackend Succeeded
  Import of duplicity.backends.onedrivebackend Succeeded
  Import of duplicity.backends.par2backend Succeeded
  Import of duplicity.backends.pydrivebackend Succeeded
  Import of duplicity.backends.rsyncbackend Succeeded
  Import of duplicity.backends.ssh_paramiko_backend Succeeded
  Import of duplicity.backends.ssh_pexpect_backend Succeeded
  Import of duplicity.backends.swiftbackend Succeeded
  Import of duplicity.backends.sxbackend Succeeded
  Import of duplicity.backends.tahoebackend Succeeded
  Import of duplicity.backends.webdavbackend Succeeded
  LFTP version is 4.8.1
  Using temporary directory /tmp/duplicity-_Mgype-tempdir
  Registering (mkstemp) temporary file 
/tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1
  SETTINGS:
  set ssl:verify-certificate true
  set ftp:ssl-allow false
  set http:use-propfind true
  set net:timeout 30
  set net:max-retries 5
  set ftp:passive-mode on
  debug
  open -u ',' 
ftp://hostname.your-storagebox.de

  Main action: remove-all-but-n-full
  Acquiring lockfile /root/.duplicity/etc_daily/lockfile
  

  duplicity 0.7.17 (February 26, 2018)
  Args: /usr/bin/duplicity remove-all-but-n-full 7 -v9 
--archive-dir=/root/.duplicity --force --name etc_daily --no-encryption 
ftp://@.your-storagebox.de/etc_full
  Linux  4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 
13:03:05 UTC 2020 x86_64 x86_64
  /usr/bin/python2 2.7.17 (default, Sep 30 2020, 13:38:04)
  [GCC 7.5.0]
  

  CMD: lftp -c "source /tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1; ( cd 
etc_full/ && ls ) || ( mkdir -p etc_full/ && cd etc_full/ && ls )"
  Reading results of 'lftp -c "source 
/tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1; ( cd etc_full/ && ls ) || ( 
mkdir -p etc_full/ && cd etc_full/ && ls )"'
  Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in 
inner_retry
  return fn(self, *args)
File

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

2020-11-04 Thread rahul

Hello Daniel,

Here are the logs.

The top output is in gnome-shell file.

The Load goes up during mouse movement .. No lock screen on this system
!!

The behaviour is erratic, after fresh boot the load is very high initially
and GUI is very sluggish. it becomes usable after ~ 2 min. The load jumps
up and stays up randomly.

Regards /// Rahul

On Wed, 4 Nov 2020 at 12:30, Daniel van Vugt <1902...@bugs.launchpad.net>
wrote:

> 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 subscribed to the bug
> report.
> 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
>


** Attachment added: "xrandr.txt"
   https://bugs.launchpad.net/bugs/1902825/+attachment/5431040/+files/xrandr.txt

** Attachment added: "shellsettings.txt"
   
https://bugs.launchpad.net/bugs/1902825/+attachment/5431041/+files/shellsettings.txt

** Attachment added: "lspci.txt"
   https://bugs.launchpad.net/bugs/1902825/+attachment/5431042/+files/lspci.txt

** Attachment added: "lsusb.txt"
   https://bugs.launchpad.net/bugs/1902825/+attachment/5431043/+files/lsusb.txt

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/bugs/1902825/+attachment/5431044/+files/journal.txt

** Attachment added: "gnome-shell"
   
https://bugs.launchpad.net/bugs/1902825/+attachment/5431045/+files/gnome-shell

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

[Desktop-packages] [Bug 1897530] Re: The modesetting driver does not gracefully handle missing connectors on EnterVT

2020-11-04 Thread Timo Aaltonen

** Description changed:

+ [Impact]
+ 
+ On a hybrid machine where NVIDIA is rendering the screen, if a display
+ attached to a dock is removed while on suspend mode, on resume X
+ crashes.
+ 
+ [Test case]
+ 
+ Test hot-unplug during suspend and resume, X shouldn't crash.
+ 
+ 
+ [Regression potential]
+ This replaces a patch we had with two commits that got merged upstream after 
a fairly extensive review process:
+ 
+ https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/
+ 
+ And we ship it in groovy. If there were issues caused by it, they would
+ be around hot-unplugging a dock while on suspend and such.
+ 
+ 
+ --
+ 
  Expectation: on removal of external display during S3, after resume eDP 
rendering should still continue by Nvidia.
  Symptom description: Plug out DP cable when suspension, when resume, X will 
crash.
  
  1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but 
NV was rendering for eDP.
  2. After S3 entry dock was removed.
  3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails 
resume of TB3 devices and logs confirm that.
  4. X fails to enter VT due to Null meta mode.
  
- 
- To address the explanation, X is not failing to enter the VT due to NVIDIA’s 
NULL MetaMode. It’s the Intel (modesetting) driver that is failing to enter the 
VT. It’s expected that NVIDIA would have a NULL MetaMode, since there are no 
displays connected to it. Our driver is pretty robust to head state changes – 
even if we have to fall back to a NULL MetaMode, we will still enter the VT 
successfully.
+ To address the explanation, X is not failing to enter the VT due to
+ NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is
+ failing to enter the VT. It’s expected that NVIDIA would have a NULL
+ MetaMode, since there are no displays connected to it. Our driver is
+ pretty robust to head state changes – even if we have to fall back to a
+ NULL MetaMode, we will still enter the VT successfully.
  
  The logs clearly show that the failure is originating from the Intel
  (modesetting) driver, not the NVIDIA driver. The relevant path in X is
  driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes(). In
  this function, the Intel driver tries to set a mode on each of the
  previously connected/enabled displays, and it tries to find the closest
  possible mode using xf86OutputFindClosestMode(). This is similar to our
  driver’s functionality, but unlike us, they don’t support a NULL
  fallback. If there are no modes supported on one of the displays, it
  simply fails, which causes X to terminate:
  
  DisplayModePtr mode = xf86OutputFindClosestMode(output,
  pScrn->currentMode);
  
  if (!mode)
- return FALSE;
+ return FALSE;
  
  Since we removed one of the displays via the dock, it fails. It doesn’t
  matter if the internal panel is still available, Intel will fail if it
  can’t re-enable ANY of the previously connected displays.
  
  Technically the modesetting driver isn’t specifically an Intel driver,
  it’s a generic driver that can be used by any DRM device – it’s just
  that Intel has chosen to use the modesetting driver as their standard
  Linux X driver going forward.

** Description changed:

  [Impact]
  
  On a hybrid machine where NVIDIA is rendering the screen, if a display
  attached to a dock is removed while on suspend mode, on resume X
  crashes.
  
  [Test case]
  
  Test hot-unplug during suspend and resume, X shouldn't crash.
  
+ [Regression potential]
  
- [Regression potential]
- This replaces a patch we had with two commits that got merged upstream after 
a fairly extensive review process:
+ This replaces a patch we had with two commits that got merged upstream
+ after a fairly extensive review process:
  
  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/
  
  And we ship it in groovy. If there were issues caused by it, they would
  be around hot-unplugging a dock while on suspend and such.
- 
  
  --
  
  Expectation: on removal of external display during S3, after resume eDP 
rendering should still continue by Nvidia.
  Symptom description: Plug out DP cable when suspension, when resume, X will 
crash.
  
  1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but 
NV was rendering for eDP.
  2. After S3 entry dock was removed.
  3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails 
resume of TB3 devices and logs confirm that.
  4. X fails to enter VT due to Null meta mode.
  
  To address the explanation, X is not failing to enter the VT due to
  NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is
  failing to enter the VT. It’s expected that NVIDIA would have a NULL
  MetaMode, since there are no displays connected to it. Our driver is
  pretty robust to head state changes – even if we have to fall back to a
  NULL MetaMode, we will still enter the VT successfully.
  
  The logs clearly show that the failure is

[Desktop-packages] [Bug 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup

2020-11-04 Thread Ladislav Petrus

@seb128 , upstream (pulseaudio) asks whether it would be possible to
test an Ubuntu build of the pulseaudio 13.99.3 package by us.  Are you
able to provide a 13.99.3 pulseaudio packages for us to test?

-- 
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 1902290] Re: Sync libraw 0.20.2-1 (main) from Debian unstable (main)

2020-11-04 Thread Balint Reczey

This sync will start a transition. I'm deferring it a bit waiting for
the autopkgtest queues to become shorter.

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

Title:
  Sync libraw 0.20.2-1 (main) from Debian unstable (main)

Status in libraw package in Ubuntu:
  New

Bug description:
  Please sync libraw 0.20.2-1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* debian/tests/build:
  - Use the correct compiler for proposed autopkgtest cross-testing
support.
* debian/tests/build:
  - Use the correct compiler for proposed autopkgtest cross-testing
support.
* debian/tests/build:
  - Use the correct compiler for proposed autopkgtest cross-testing
support.

  The compiler changes in the autopkgtest for cross-testing has been
  included in the Debian package.

  
  Changelog entries since current hirsute version 0.19.5-1ubuntu1:

  libraw (0.20.2-1) unstable; urgency=medium

* New upstream release

   -- Matteo F. Vescovi   Mon, 19 Oct 2020 23:00:12
  +0200

  libraw (0.20.0-4) unstable; urgency=medium

* Upload to unstable
* debian/libraw20.symbols: drop duplicates and
  restrict to 64 bits

   -- Matteo F. Vescovi   Tue, 18 Aug 2020 15:45:30
  +0200

  libraw (0.20.0-3) experimental; urgency=medium

* debian/libraw20.symbols: drop MISSING and update others

   -- Matteo F. Vescovi   Tue, 04 Aug 2020 23:43:02
  +0200

  libraw (0.20.0-2) experimental; urgency=medium

* debian/libraw20.symbols: file updated

   -- Matteo F. Vescovi   Tue, 04 Aug 2020 21:11:25
  +0200

  libraw (0.20.0-1) experimental; urgency=medium

[ Matteo F. Vescovi ]
* New upstream release
  This release fixes CVE-2020-15503:
  | LibRaw before 0.20-RC1 lacks a thumbnail size range check.
  | This affects decoders/unpack_thumb.cpp,
  | postprocessing/mem_image.cpp, and utils/thumb_utils.cpp.
  | For example,
  | malloc(sizeof(libraw_processed_image_t)+T.tlength) occurs
  | without validating T.tlength.
* debian/: SONAME bump 19 -> 20
* debian/control:
  - debhelper bump 12 -> 13
  - S-V bump 4.4.0 -> 4.5.0 (no changes needed)
  - RRR set
* debian/tests/smoketest: path adapted
* debian/copyright: entries for unused files and licenses removed
* debian/rules: drop useless files installation
* debian/libraw20.symbols: missing and new symbols added

[ Sebastien Bacher ]
* debian/tests/build: use the correct compiler for
  autopkgtest cross-testing. (Closes: #954886)

   -- Matteo F. Vescovi   Thu, 30 Jul 2020 00:09:36
  +0200

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

-- 
Mailing list: https://launchpad.net/~desktop-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-04 Thread Joep Jaeger

apt policy thunderbird
thunderbird:
  Geïnstalleerd: 1:78.3.2+build1-0ubuntu0.20.04.1
  Kandidaat: 1:78.3.2+build1-0ubuntu0.20.04.1
  Versietabel:
 *** 1:78.3.2+build1-0ubuntu0.20.04.1 500
500 http://ppa.launchpad.net/ubuntu-mozilla-security/ppa/ubuntu 
focal/main amd64 Packages
100 /var/lib/dpkg/status
 1:68.10.0+build1-0ubuntu0.20.04.1 500
500 http://mirror.netcologne.de/ubuntu focal-updates/main amd64 Packages
500 http://mirror.netcologne.de/ubuntu focal-security/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
 1:68.7.0+build1-0ubuntu2 500
500 http://mirror.netcologne.de/ubuntu focal/main amd64 Packages

-- 
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 1726464] Re: Can't easily move the cursor between monitors when the dock is set to auto-hide

2020-11-04 Thread Carolina Sanchez

Hi Guys,

I use Ubuntu 20.04.1 and have a similar problem, in this case the mouse
just move the cursor between monitors through the top part and appears
in the second screen at the bottom of the screen. And viceversa from the
second monitor trough the bottom to the top of the first one. I tried
all the combinations for the Dock settings and nothing seems to fix the
bug. Do you have any other suggestion? Thanks, Carolina

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

Title:
  Can't easily move the cursor between monitors when the dock is set to
  auto-hide

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

Bug description:
  The sticky edge thing between monitors is very annoying as the cursor
  never ends up where it should when it's moved over to the other
  screen. It's annoying to the degree that I feel like I can not use
  multiple monitors with standard Ubuntu anymore.

  Unity had an option to disable this, please add one to Gnome as well.

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

-- 
Mailing list: https://launchpad.net/~desktop-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

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

-- 
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:
  New

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 1902538] Re: Every cycle python-apt breaks until updated for the new distro codename

2020-11-04 Thread Julian Andres Klode

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

Dupe of 1727470. FWIW, python-apt 2.1.15 does not hard code codenames
anymore, so won't have this issue.

** Changed in: python-apt (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: python-apt (Ubuntu)
   Status: Invalid => Fix Committed

** This bug has been marked a duplicate of bug 1727470
   [RFE] Automatically update the Ubuntu version strings in python-apt

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

Title:
  Every cycle python-apt breaks until updated for the new distro
  codename

Status in Ubuntu MATE:
  New
Status in python-apt package in Ubuntu:
  Fix Committed
Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  The problem is currently happening in hirsute (fixed with the python-
  apt in proposed, software-properties fails to start due a python-apt
  error

File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
605, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 91, in 
get_sources
  raise NoDistroTemplateException(
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/hirsute

  Could we try to handle the missing codename in a way that doesn't make
  python-apt users blow up every cycle until we play catching up?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1902538/+subscriptions

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

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

2020-11-04 Thread Von

@Coiby Xu (coiby)

> Will decreasing
polling_interval_active_us to 1ms fix the problem?
> $echo 1000 > /sys/module/i2c_hid/parameters/polling_interval_active_us 

Yes, I installed the latest version from Github, and decreasing
polling_interval_active_us seems to fix the problem.

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

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

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

Bug description:
  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias:

[Desktop-packages] [Bug 1902858] [NEW] 20.04 - Printer Change Driver window becomes unresponsive

2020-11-04 Thread ardour

Public bug reported:

User yetanotherbryan from Ubuntu Forums has reported on this since May
2020, and I've also experience this bug this week when I upgraded to
20.04.

Unable to Change Printer Driver in Ubuntu 20.04
(https://ubuntuforums.org/showthread.php?t=2444046)

I'm trying to get my printer setup on a fresh
install of 20.04. In setttings, when I add my
network printer (Samsung M287X), it is found
and installs a default driver. I am able to print
normally. I trying to swap out the printer driver
("Additional Printer Settings" > "Properties" >
"Make and Model -Change") to install alternative
drivers. This is necessary to enable some features
such as two sided printing. When I click "Change"
it attempts to search for drivers but comes
unresponsive. This is something that I have done
many times on previous versions of ubuntu. Anybody
have an idea of what is happening here?

Thanks,

Bryan

Included in this bug report is a screenshot of the bug itself.

** Affects: system-config-printer (Ubuntu)
Importance: Undecided
Status: New

** Attachment added: "Screenshot_2020-11-03_16-59-21.png"

https://bugs.launchpad.net/bugs/1902858/+attachment/5431007/+files/Screenshot_2020-11-03_16-59-21.png

** Description changed:

User yetanotherbryan from Ubuntu Forums has reported on this since May
2020, and I've also experience this bug this week when I upgraded to
20.04.

- Unable to Change Printer Driver in Ubuntu 20.04
- (https://ubuntuforums.org/showthread.php?t=2444046)
+ Unable to Change Printer Driver in Ubuntu 20.04
+ (https://ubuntuforums.org/showthread.php?t=2444046)
+
+ I'm trying to get my printer setup on a fresh
+ install of 20.04. In setttings, when I add my
+ network printer (Samsung M287X), it is found
+ and installs a default driver. I am able to print
+ normally. I trying to swap out the printer driver
+ ("Additional Printer Settings" > "Properties" >
+ "Make and Model -Change") to install alternative
+ drivers. This is necessary to enable some features
+ such as two sided printing. When I click "Change"
+ it attempts to search for drivers but comes
+ unresponsive. This is something that I have done
+ many times on previous versions of ubuntu. Anybody
+ have an idea of what is happening here?

- I'm trying to get my printer setup on a fresh install of 20.04. In
- setttings, when I add my network printer (Samsung M287X), it is found
- and installs a default driver. I am able to print normally. I trying
- to swap out the printer driver ("Additional Printer Settings" >
- "Properties" > "Make and Model -Change") to install alternative
- drivers. This is necessary to enable some features such as two sided
- printing. When I click "Change" it attempts to search for drivers but
- comes unresponsive. This is something that I have done many times on
- previous versions of ubuntu. Anybody have an idea of what is happening
- here?
-
- Thanks,
-
- Bryan
+ Thanks,
+
+ Bryan

Included in this bug report is a screenshot of the bug itself.

** Summary changed:

- Xubuntu 20.04 - Printer Change Driver Windows becomes unresponsive
+ 20.04 - Printer Change Driver Windows becomes unresponsive

** Summary changed:

- 20.04 - Printer Change Driver Windows becomes unresponsive
+ 20.04 - Printer Change Driver window becomes unresponsive

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

Title:
20.04 - Printer Change Driver window becomes unresponsive

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

Bug description:
User yetanotherbryan from Ubuntu Forums has reported on this since May
2020, and I've also experience this bug this week when I upgraded to
20.04.

Unable to Change Printer Driver in Ubuntu 20.04
(https://ubuntuforums.org/showthread.php?t=2444046)

Thanks,

Bryan

Included in this bug report is a screenshot of the bug itself.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1662244] Re: lightdm causes all greeters to fail to start

2020-11-04 Thread Alkis Georgopoulos

What torel proposed in https://bugs.launchpad.net/ubuntu/+source/unity-
greeter/+bug/1662244/comments/14 avoids the segfault:

* soft memlock 262144
* hard memlock 262144

Should all lightdm users manually put that in limits.conf, or should we
expect some update?

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

Title:
  lightdm causes all greeters to fail to start

Status in Light Display Manager:
  Invalid
Status in LightDM GTK+ Greeter:
  Invalid
Status in lightdm package in Ubuntu:
  Invalid
Status in unity-greeter package in Ubuntu:
  Invalid

Bug description:
  lightdm is failing to start. Best guess is because of unity-session-
  manager. This is from .xsession-errors.

  dbus-update-activation-environment: setting 
_=/usr/bin/dbus-update-activation-environment
  upstart: click-user-hooks main process (4028) terminated with status 1
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon respawning too fast, stopped
  upstart: indicator-application main process ended, respawning
  upstart: indicator-application main process ended, respawning
  upstart: indicator-application respawning too fast, stopped
  xbrlapi: window 0x03a00084 changed to NULL name
  xbrlapi: window 0x03a00084 changed to NULL name
  xbrlapi: window 0x03c00084 changed to NULL name
  xbrlapi: window 0x03c00084 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  upstart: dbus main process (4023) killed by TERM signal

  
  I've tried to move aside $HOME/.config/dconf/user and that didn't work. I've 
reverted kernel versions and that didn't work. I've moved aside $HOME/.cache 
and that didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Mon Feb  6 10:21:29 2017
  InstallationDate: Installed on 2015-07-20 (566 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to yakkety on 2016-12-14 (53 days ago)

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

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

[Desktop-packages] [Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]

2020-11-04 Thread Graeme Gregory

Bug exists in 20.10 too, I just triggered it. It happened after screen
lock/unlock cycle.

Like other restart got rid of it.

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

Title:
  undismissable, unclickable authentication dialog left on screen (top-
  left corner) after policykit authentication [pushModal: invocation of
  begin_modal failed]

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

Bug description:
  In disco, when policykit prompted me for a password in order for
  update-manager to dispatch instructions to aptdaemon to perform
  package updates, the password dialog remained on the screen after I
  clicked 'authenticate'.

  The window is not clickable, it appears not to even be a window -
  mouse presses are received by the window underneath.  The exception is
  that the 'cancel' button is active and receives mouse events - but
  clicking it does nothing.

  This may be a gnome-shell issue rather than policykit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: policykit-1 0.105-25
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 13:14:33 2019
  InstallationDate: Installed on 2010-09-24 (3125 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

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

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

[Desktop-packages] [Bug 1662244] Re: lightdm causes all greeters to fail to start

2020-11-04 Thread Alkis Georgopoulos

Hi, a recent systemd update in 18.04 makes slick-greeter segfault.
So all Ubuntu MATE 18.04 users now get black screens instead of lightdm.

It's related to memory limits so I'm cross-referencing it here:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746

This didn't help:

[LightDM]
lock-memory=false

Can I put something in /etc/security/limits.conf to see if it helps?

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

Title:
  lightdm causes all greeters to fail to start

Status in Light Display Manager:
  Invalid
Status in LightDM GTK+ Greeter:
  Invalid
Status in lightdm package in Ubuntu:
  Invalid
Status in unity-greeter package in Ubuntu:
  Invalid

Bug description:
  lightdm is failing to start. Best guess is because of unity-session-
  manager. This is from .xsession-errors.

  dbus-update-activation-environment: setting 
_=/usr/bin/dbus-update-activation-environment
  upstart: click-user-hooks main process (4028) terminated with status 1
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon respawning too fast, stopped
  upstart: indicator-application main process ended, respawning
  upstart: indicator-application main process ended, respawning
  upstart: indicator-application respawning too fast, stopped
  xbrlapi: window 0x03a00084 changed to NULL name
  xbrlapi: window 0x03a00084 changed to NULL name
  xbrlapi: window 0x03c00084 changed to NULL name
  xbrlapi: window 0x03c00084 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  upstart: dbus main process (4023) killed by TERM signal

  
  I've tried to move aside $HOME/.config/dconf/user and that didn't work. I've 
reverted kernel versions and that didn't work. I've moved aside $HOME/.cache 
and that didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Mon Feb  6 10:21:29 2017
  InstallationDate: Installed on 2015-07-20 (566 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to yakkety on 2016-12-14 (53 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-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

2020-11-04 Thread Johan Segerstedt

I have reported the issue upstream:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1030

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

-- 
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 1902538] Re: Ubuntu Mate 21.04 Software & Updates fails to run

The issue should be fixed with this update

https://launchpad.net/ubuntu/+source/python-apt/2.1.3ubuntu3

it does sound like we should do better than having software-properties
bail out every start of cycle until python-apt is updated, I'm going to
repurpose the bug for that issue

** Changed in: software-properties (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => High

** Changed in: python-apt (Ubuntu)
   Importance: Undecided => High

** Changed in: python-apt (Ubuntu)
   Status: New => Fix Committed

** Summary changed:

- Ubuntu Mate 21.04 Software & Updates fails to run
+ Every cycle python-apt breaks until updated for the new distro codename

** Description changed:

- When trying to open "Software & Updates" it shows in the dock, but fails
- to run. I realize that now I am unable to restore packages that were
- disabled during the install.
+ The problem is currently happening in hirsute (fixed with the python-apt
+ in proposed, software-properties fails to start due a python-apt error
+ 
+   File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
605, in reload_sourceslist
+ self.distro.get_sources(self.sourceslist)
+   File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 91, in 
get_sources
+ raise NoDistroTemplateException(
+ aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/hirsute
+ 
+ Could we try to handle the missing codename in a way that doesn't make
+ python-apt users blow up every cycle until we play catching up?

** Changed in: python-apt (Ubuntu)
   Status: Fix Committed => Confirmed

** Tags added: rls-hh-incoming

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

Title:
  Every cycle python-apt breaks until updated for the new distro
  codename

Status in Ubuntu MATE:
  New
Status in python-apt package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  The problem is currently happening in hirsute (fixed with the python-
  apt in proposed, software-properties fails to start due a python-apt
  error

File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
605, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 91, in 
get_sources
  raise NoDistroTemplateException(
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/hirsute

  Could we try to handle the missing codename in a way that doesn't make
  python-apt users blow up every cycle until we play catching up?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1902538/+subscriptions

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

[Desktop-packages] [Bug 1902832] Re: lftp support broken - exits with error_code -11

2020-11-04 Thread Carsten Schmitz

Yes, I am sure. I tested it on another server that did not do the
updates yet.

It must have been one of these packages because we do daily backups and
these were the only ones that were updated between the successful and
failed  run.

I tried downgrading but apt is not very smart and would remove too many
packages, and these are live systems so I did not dare to do it.

Please note that switching to ncftp was successful as a workaround, so
it something that only affects lftp.

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

Title:
  lftp support broken - exits with error_code -11

Status in duplicity package in Ubuntu:
  New

Bug description:
  We are using duplicity 0.7.17 and Ubuntu 18.04 LTS.

  After upgrading these packages in Ubuntu:

  Upgrade: libc-bin:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: locales:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: multiarch-support:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: libc6-dev:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3), 
  Upgrade: libc6:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: libc-dev-bin:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)

  the duplicity/lftp support stopped working. It worked for years just
  fine before that.

  Basic error message is:

  Giving up after 5 attempts. BackendException: Error running 'lftp -c
  "source /tmp/duplicity-gVCsqa-tempdir/mkstemp-serY3Q-1; ( cd
  etc_backup/ && ls ) || ( mkdir -p etc_backup/ && cd etc_backup/ && ls
  )"': returned -11, with output:

  Error/debug output:

  Using archive dir: /root/.duplicity/etc_daily
  Using backup name: etc_daily
  GPG binary is gpg, version 2.2.4
  Import of duplicity.backends.acdclibackend Succeeded
  Import of duplicity.backends.azurebackend Succeeded
  Import of duplicity.backends.b2backend Succeeded
  Import of duplicity.backends.botobackend Succeeded
  Import of duplicity.backends.cfbackend Succeeded
  Import of duplicity.backends.dpbxbackend Failed: No module named dropbox
  Import of duplicity.backends.gdocsbackend Succeeded
  Import of duplicity.backends.giobackend Succeeded
  Import of duplicity.backends.hsibackend Succeeded
  Import of duplicity.backends.hubicbackend Succeeded
  Import of duplicity.backends.imapbackend Succeeded
  Import of duplicity.backends.lftpbackend Succeeded
  Import of duplicity.backends.localbackend Succeeded
  Import of duplicity.backends.mediafirebackend Succeeded
  Import of duplicity.backends.megabackend Succeeded
  Import of duplicity.backends.multibackend Succeeded
  Import of duplicity.backends.ncftpbackend Succeeded
  Import of duplicity.backends.onedrivebackend Succeeded
  Import of duplicity.backends.par2backend Succeeded
  Import of duplicity.backends.pydrivebackend Succeeded
  Import of duplicity.backends.rsyncbackend Succeeded
  Import of duplicity.backends.ssh_paramiko_backend Succeeded
  Import of duplicity.backends.ssh_pexpect_backend Succeeded
  Import of duplicity.backends.swiftbackend Succeeded
  Import of duplicity.backends.sxbackend Succeeded
  Import of duplicity.backends.tahoebackend Succeeded
  Import of duplicity.backends.webdavbackend Succeeded
  LFTP version is 4.8.1
  Using temporary directory /tmp/duplicity-_Mgype-tempdir
  Registering (mkstemp) temporary file 
/tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1
  SETTINGS:
  set ssl:verify-certificate true
  set ftp:ssl-allow false
  set http:use-propfind true
  set net:timeout 30
  set net:max-retries 5
  set ftp:passive-mode on
  debug
  open -u ',' 
ftp://hostname.your-storagebox.de

  Main action: remove-all-but-n-full
  Acquiring lockfile /root/.duplicity/etc_daily/lockfile
  

  duplicity 0.7.17 (February 26, 2018)
  Args: /usr/bin/duplicity remove-all-but-n-full 7 -v9 
--archive-dir=/root/.duplicity --force --name etc_daily --no-encryption 
ftp://@.your-storagebox.de/etc_full
  Linux  4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 
13:03:05 UTC 2020 x86_64 x86_64
  /usr/bin/python2 2.7.17 (default, Sep 30 2020, 13:38:04)
  [GCC 7.5.0]
  

  CMD: lftp -c "source /tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1; ( cd 
etc_full/ && ls ) || ( mkdir -p etc_full/ && cd etc_full/ && ls )"
  Reading results of 'lftp -c "source 
/tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1; ( cd etc_full/ && ls ) || ( 
mkdir -p etc_full/ && cd etc_full/ && ls )"'
  Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in 
inner_retry
  return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 578, in 
list
  return [tobytes(x) for x in self.backend._list()]
File "/usr/lib/python2.7/dist-packages/duplicity/backends/lftpbackend.py", 
line 181, in _list
  _,

[Desktop-packages] [Bug 1902148] Re: [snap] launchers in app's dock menu do launch general LO

Which interpreter did you try in your local script? Doing

'#!/bin/sh
set -x
for app in base calc draw
do
App="${app^}"
sed -i \
-e 
"s#Icon=libreoffice7.0-$app#Icon=/usr/share/icons/gnome/256x256/apps/libreoffice7.0-$app.png#"
 \
-e "s#^Exec=libreoffice7.0 --\(.*\)#Exec=libreoffice.\1#g" \
-e 
"/^Name=$App$/{$!{N;s/^Name=$App\nExec=libreoffice$/Name=$App\nExec=libreoffice.$app/;ty;P;D;:y}}"
 \
/tmp/$app.desktop
done'

returns the same bad substitution error

-- 
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 1902832] Re: lftp support broken - exits with error_code -11

Thank you for your bug report. Are you sure it has with the glibc
update? Could you maybe try to downgrade back those packages to see it
if resolves the issue?

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

Title:
  lftp support broken - exits with error_code -11

Status in duplicity package in Ubuntu:
  New

Bug description:
  We are using duplicity 0.7.17 and Ubuntu 18.04 LTS.

  After upgrading these packages in Ubuntu:

  Upgrade: libc-bin:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: locales:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: multiarch-support:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: libc6-dev:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3), 
  Upgrade: libc6:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)
  Upgrade: libc-dev-bin:amd64 (2.27-3ubuntu1.2, 2.27-3ubuntu1.3)

  the duplicity/lftp support stopped working. It worked for years just
  fine before that.

  Basic error message is:

  Giving up after 5 attempts. BackendException: Error running 'lftp -c
  "source /tmp/duplicity-gVCsqa-tempdir/mkstemp-serY3Q-1; ( cd
  etc_backup/ && ls ) || ( mkdir -p etc_backup/ && cd etc_backup/ && ls
  )"': returned -11, with output:

  Error/debug output:

  Using archive dir: /root/.duplicity/etc_daily
  Using backup name: etc_daily
  GPG binary is gpg, version 2.2.4
  Import of duplicity.backends.acdclibackend Succeeded
  Import of duplicity.backends.azurebackend Succeeded
  Import of duplicity.backends.b2backend Succeeded
  Import of duplicity.backends.botobackend Succeeded
  Import of duplicity.backends.cfbackend Succeeded
  Import of duplicity.backends.dpbxbackend Failed: No module named dropbox
  Import of duplicity.backends.gdocsbackend Succeeded
  Import of duplicity.backends.giobackend Succeeded
  Import of duplicity.backends.hsibackend Succeeded
  Import of duplicity.backends.hubicbackend Succeeded
  Import of duplicity.backends.imapbackend Succeeded
  Import of duplicity.backends.lftpbackend Succeeded
  Import of duplicity.backends.localbackend Succeeded
  Import of duplicity.backends.mediafirebackend Succeeded
  Import of duplicity.backends.megabackend Succeeded
  Import of duplicity.backends.multibackend Succeeded
  Import of duplicity.backends.ncftpbackend Succeeded
  Import of duplicity.backends.onedrivebackend Succeeded
  Import of duplicity.backends.par2backend Succeeded
  Import of duplicity.backends.pydrivebackend Succeeded
  Import of duplicity.backends.rsyncbackend Succeeded
  Import of duplicity.backends.ssh_paramiko_backend Succeeded
  Import of duplicity.backends.ssh_pexpect_backend Succeeded
  Import of duplicity.backends.swiftbackend Succeeded
  Import of duplicity.backends.sxbackend Succeeded
  Import of duplicity.backends.tahoebackend Succeeded
  Import of duplicity.backends.webdavbackend Succeeded
  LFTP version is 4.8.1
  Using temporary directory /tmp/duplicity-_Mgype-tempdir
  Registering (mkstemp) temporary file 
/tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1
  SETTINGS:
  set ssl:verify-certificate true
  set ftp:ssl-allow false
  set http:use-propfind true
  set net:timeout 30
  set net:max-retries 5
  set ftp:passive-mode on
  debug
  open -u ',' 
ftp://hostname.your-storagebox.de

  Main action: remove-all-but-n-full
  Acquiring lockfile /root/.duplicity/etc_daily/lockfile
  

  duplicity 0.7.17 (February 26, 2018)
  Args: /usr/bin/duplicity remove-all-but-n-full 7 -v9 
--archive-dir=/root/.duplicity --force --name etc_daily --no-encryption 
ftp://@.your-storagebox.de/etc_full
  Linux  4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 
13:03:05 UTC 2020 x86_64 x86_64
  /usr/bin/python2 2.7.17 (default, Sep 30 2020, 13:38:04)
  [GCC 7.5.0]
  

  CMD: lftp -c "source /tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1; ( cd 
etc_full/ && ls ) || ( mkdir -p etc_full/ && cd etc_full/ && ls )"
  Reading results of 'lftp -c "source 
/tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1; ( cd etc_full/ && ls ) || ( 
mkdir -p etc_full/ && cd etc_full/ && ls )"'
  Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in 
inner_retry
  return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 578, in 
list
  return [tobytes(x) for x in self.backend._list()]
File "/usr/lib/python2.7/dist-packages/duplicity/backends/lftpbackend.py", 
line 181, in _list
  _, l, e = self.subprocess_popen(commandline)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 499, in 
subprocess_popen
  (logstr, result, stdout + '
  ' + stderr))
   BackendException: Error running 'lftp -c "source 
/tmp/duplicity-_Mgype-tempdir/mkstemp-55iPLR-1; ( cd etc_full/ && ls ) || ( 
mkdir

[Desktop-packages] [Bug 1901286] Re: gnome-disk-image-mounter fails after upgrade to 20.10

Hum, I though gdu would basically call to udisks. You could perhaps also
report the bug directly to the software writers on
https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues , they know
better the code and might have a better clue on guessing the issue

-- 
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 1902853] [NEW] Failure to create core GL context with llvmpipe when using GLX_ARB_context_flush_control

2020-11-04 Thread Marc

Public bug reported:

When using llvmpipe on the non-HWE xorg version GL core context creation
fails when using "GLX_ARB_context_flush_control" even though the driver
reports that the extension is supported.

Apologies if xorg is the wrong package here, this could be a libgl1
-mesa-dri/glx bug instead, it's unclear to me where the fault lies in
the graphics stack.

xserver-common:
  Installed: 2:1.19.6-1ubuntu4.7
  Candidate: 2:1.19.6-1ubuntu4.7
linux-generic:
  Installed: 4.15.0.122.109
  Candidate: 4.15.0.122.109

Steps to reproduce on Ubuntu Server:
1. Install Ubuntu 18.04 server edition in a VM, or other hardware without a 
physical graphics device
2. Install the desktop with "sudo apt install ubuntu-desktop"
3. Reboot
4. Compile and run the attached file

Steps to reproduce on Ubuntu Desktop:
1. Install Ubuntu 18.04 desktop edition in a VM, or other hardware without a 
physical graphics device
2. Remove the HWE packages with "apt remove *-hwe-18.04" and then "apt install 
xserver-xorg-core ubuntu-desktop xserver-xorg xserver-xorg-video-all 
xserver-xorg-input-all libgl1-mesa-dri libgl1-mesa-glx" to get things back to 
normal
3. Reboot
4. Compile and run the attached file

Both examples produce:
"Could not create GL context: BadValue (integer parameter out of range for 
operation)"

For both cases, upgrading to (or staying on) the HWE stack allows
creating the core 3.3 context successfully.


Debugging:

I've stepped all the way into libxcb for the context creation at
src/glx.c:3258, with a call to
"xcb_glx_create_context_attribs_arb_checked", but haven't managed to
link this up to a received request in another process. The request is
rejected with BadValue.

BadVaue in this instance could mean one of two things according to GL spec:
1. The GLX_RENDER_TYPE attribute is invalid
2. An attribute or it's bitmask are not recognized.

We can likely rule out 1 as GLX_RENDER_TYPE is correctly set to opengl.
Option 2 allows looking at it at a higher level. SDL2 adds
`GLX_CONTEXT_RELEASE_BEHAVIOUR_ARB=GLX_CONTEXT_RELEASE_BEHAVIOUR_FLUSH_ARB`
to the attributes (at src/video/x11/SDL_x11opengl.c:720) by default when
it detects the `GLX_ARB_context_flush_control` extension is present,
which should be a no-op and the default setting. `glxinfo` and other gl
functions all show that `GLX_ARB_context_flush_control` is present, but
removing that usage from the attributes list (by removing lines 720 to
726 avoids the issue and we are given a valid GL context.

Due to this, I think something in the graphics stack is rejecting the
usage of GLX_ARB_context_flush_control, even though it's claiming to
support it through other gl calls. The llvmpipe GL driver reports core
support up to 3.3 as well, so this shouldn't be an issue. I also suspect
it's simply something that's been fixed more recently, as installing the
newer HWE versions of xorg (and the kernel) fixes the issue.


I wouldn't expect to have to upgrade to the HWE stack to be able to get a 
working GL context this way, so I'm reporting this to check if it's a known 
issue or if there's a fix that can be made.

The attached file depends on "libsdl2-dev" and can be compiled and run with:
"g++ main.cpp -I/usr/include/SDL2 -lSDL2 -lGL && ./a.out"

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.18
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  4 09:16:16 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2020-11-03 (0 days ago)
InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
Lsusb:
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

[Desktop-packages] [Bug 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties

I'm using focal, the bug as tagged as incoming for series up to hirsute,
is it supposed to be mostly an issue for bionic? Maybe that station
attribute patch should be backported to bionic as a first step?

Could you give a more direct reference to that patch? Grepping for 'station' in 
debian/patches only returns
CVE-2019-16275.patch:connected station dropping its association.

It's still unclear to me what a real user facing scenario impact of the
issue would be. Would installing connman instead of network-manager and
trying to do some action

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-16275

-- 
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 1896091] Re: [i915] Noise-like lines of graphics corruption when moving windows in Xorg sessions