date:20201024

Turns out high CPU Usage and slow UI issue is unrelated, it was due to
CPU governor reset to powersave and always using min frequency.

But the issue with nouveau timeout and system lockup still stays I
guess. Unless it was triggered by low CPU frequency.

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

Title:
nouveau timeout and system lockup

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

Bug description:
After upgrading from 20.04 to 20.10 system is unusable anymore due to
GPU issues with nouveau. Same system worked fine on 20.04.

Switching to nvidia proprietary driver and Xorg fixes the issue.

Symptoms:

System starts just fine, but overall UI performance is bad, everything
seems slow and CPU usage seems too high even when idle. After a while
UI freezes completly. Sometimes it recovers after several minutes,
other times it doesn't and system freezes forever, requiring hard
reboot.

Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti. Intel Xeon
E3-1231 v3.

dmesg output attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+subscriptions

--
Mailing list: https://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 1894627] Re: [nvidia] Web browser distorted after hibernation/power save when idle

2020-10-24 Thread Kashad J Turner-Warren

Daniel, here are one more examples when I wake up my computer from sleep
mode. currently, I am using google chrome. it will gitch like this
until I close the browser.

On Fri, Oct 23, 2020 at 10:35 AM Olivier Tilloy <1894...@bugs.launchpad.net>
wrote:

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

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

2020-10-24 Thread Kashad J Turner-Warren

this is coming from my Gmail account.

On Sat, Oct 24, 2020 at 10:57 PM Kashad Turner-Warren 
wrote:

> Daniel, here are one more examples when I wake up my computer from sleep
> mode. currently, I am using google chrome. it will gitch like this
> until I close the browser.
>
> On Fri, Oct 23, 2020 at 10:35 AM Olivier Tilloy <
> 1894...@bugs.launchpad.net> wrote:
>
>> Not that I can tell.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1894627
>>
>> Title:
>>   [nvidia] Web browser distorted after hibernation/power save when idle
>>
>> Status in chromium-browser package in Ubuntu:
>>   New
>> Status in mutter package in Ubuntu:
>>   New
>>
>> Bug description:
>>   my laptop goes to hibernation/power saver mode when my computer is
>> idle.
>>   every time I bring my computer back up, the screen distorted. I have to
>> close all my browsers. Sometimes, shut down the computer.
>>
>>   Description:  Ubuntu 20.04.1 LTS
>>   Release:  20.04
>>   N: Unable to locate package pkgname
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 20.04
>>   Package: xorg 1:7.7+19ubuntu14
>>   ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
>>   Uname: Linux 5.4.0-45-generic x86_64
>>   NonfreeKernelModules: nvidia_modeset nvidia
>>   .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a
>> directory: '/proc/driver/nvidia/gpus/:01:00.0'
>>   .proc.driver.nvidia.registry: Binary: ""
>>   .proc.driver.nvidia.suspend: suspend hibernate resume
>>   .proc.driver.nvidia.suspend_depth: default modeset uvm
>>   .proc.driver.nvidia.version:
>>NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29
>> 08:45:51 UTC 2020
>>GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
>>   ApportVersion: 2.20.11-0ubuntu27.8
>>   Architecture: amd64
>>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>>   CasperMD5CheckResult: skip
>>   CompositorRunning: None
>>   CurrentDesktop: ubuntu:GNOME
>>   Date: Mon Sep  7 03:33:23 2020
>>   DistUpgraded: Fresh install
>>   DistroCodename: focal
>>   DistroVariant: ubuntu
>>   DkmsStatus:
>>nvidia, 440.100, 5.4.0-42-generic, x86_64: installed
>>nvidia, 440.100, 5.4.0-45-generic, x86_64: installed
>>   ExtraDebuggingInterest: Yes
>>   GraphicsCard:
>>Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00
>> [VGA controller])
>>  Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile)
>> [103c:8466]
>>NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c]
>> (rev a1) (prog-if 00 [VGA controller])
>>  Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Ti
>> Mobile] [103c:8466]
>>   InstallationDate: Installed on 2020-06-23 (75 days ago)
>>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
>> (20200423)
>>   Lsusb:
>>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>Bus 001 Device 002: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd
>> (Foxlink) HP Wide Vision HD Camera
>>Bus 001 Device 003: ID 8087:0aaa Intel Corp.
>>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>   MachineType: HP OMEN by HP Laptop
>>   ProcEnviron:
>>TERM=xterm-256color
>>PATH=(custom, no user)
>>XDG_RUNTIME_DIR=
>>LANG=en_US.UTF-8
>>SHELL=/bin/bash
>>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic
>> root=UUID=98265a4d-5439-415e-b43c-904265a8559a ro quiet splash vt.handoff=7
>>   SourcePackage: xorg
>>   Symptom: display
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>   dmi.bios.date: 04/24/2019
>>   dmi.bios.vendor: AMI
>>   dmi.bios.version: F.09
>>   dmi.board.asset.tag: Base Board Asset Tag
>>   dmi.board.name: 8466
>>   dmi.board.vendor: HP
>>   dmi.board.version: 68.21
>>   dmi.chassis.type: 10
>>   dmi.chassis.vendor: HP
>>   dmi.chassis.version: Chassis Version
>>   dmi.modalias:
>> dmi:bvnAMI:bvrF.09:bd04/24/2019:svnHP:pnOMENbyHPLaptop:pvr:rvnHP:rn8466:rvr68.21:cvnHP:ct10:cvrChassisVersion:
>>   dmi.product.family: 103C_5335KV HP OMEN
>>   dmi.product.name: OMEN by HP Laptop
>>   dmi.product.sku: 4CC49UA#ABA
>>   dmi.sys.vendor: HP
>>   modified.conffile..etc.default.apport:
>># set this to 0 to disable apport, or to 1 to enable it
>># you can temporarily override this with
>># sudo service apport start force_start=1
>>enabled=0
>>   mtime.conffile..etc.default.apport: 2020-06-26T00:47:21.524860
>>   version.compiz: compiz N/A
>>   version.libdrm2: libdrm2 2.4.101-2
>>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
>>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>>   version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
>>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.3
>>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
>>   version.xserver-xorg-

[Desktop-packages] [Bug 1901378] [NEW] hplip executables missing

2020-10-24 Thread Ryan Fugger

Public bug reported:

After fresh install of hplip and hplip-gui, executable symlinks
/usr/bin/hp* are broken.  /usr/share/hplip/*.py are not present, and in
fact, the /usr/share/hplip directory is missing completely.  The package
is completely broken.

Here is the output of the package installation:

$ sudo apt install hplip-gui 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  hplip
Suggested packages:
  hplip-doc
The following NEW packages will be installed:
  hplip hplip-gui
0 upgraded, 2 newly installed, 0 to remove and 9 not upgraded.
Need to get 223 kB of archives.
After this operation, 687 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://mirror.it.ubc.ca/ubuntu focal/main amd64 hplip amd64 
3.20.3+dfsg0-2 [204 kB]
Get:2 http://mirror.it.ubc.ca/ubuntu focal/universe amd64 hplip-gui all 
3.20.3+dfsg0-2 [19.1 kB]
Fetched 223 kB in 0s (573 kB/s)  
Selecting previously unselected package hplip.
(Reading database ... 228889 files and directories currently installed.)
Preparing to unpack .../hplip_3.20.3+dfsg0-2_amd64.deb ...
Unpacking hplip (3.20.3+dfsg0-2) ...
Selecting previously unselected package hplip-gui.
Preparing to unpack .../hplip-gui_3.20.3+dfsg0-2_all.deb ...
Unpacking hplip-gui (3.20.3+dfsg0-2) ...
Setting up hplip (3.20.3+dfsg0-2) ...
Creating/updating hplip user account...
Can't open /etc/hp/hplip.conf: No such file or directory.
Can't open /etc/hp/hplip.conf: No such file or directory.
Setting up hplip-gui (3.20.3+dfsg0-2) ...
Processing triggers for desktop-file-utils (0.24-1ubuntu3) ...
Processing triggers for mime-support (3.64ubuntu1) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for dbus (1.12.16-2ubuntu2.1) ...

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: hplip 3.20.3+dfsg0-2
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
CasperMD5CheckResult: skip
CupsErrorLog:
 
CurrentDesktop: GNOME
Date: Sat Oct 24 22:52:33 2020
InstallationDate: Installed on 2018-08-04 (813 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lpstat: device for HP_LaserJet_Professional_M1212nf_MFP: 
implicitclass://HP_LaserJet_Professional_M1212nf_MFP/
MachineType: LENOVO 20FMS7X200
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_Professional_M1212nf_MFP.ppd'] failed with exit code 
2: grep: /etc/cups/ppd/HP_LaserJet_Professional_M1212nf_MFP.ppd: Permission 
denied
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: hplip
UpgradeStatus: Upgraded to focal on 2020-08-17 (68 days ago)
dmi.bios.date: 05/07/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R06ET67W (1.41 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FMS7X200
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET67W(1.41):bd05/07/2019:svnLENOVO:pn20FMS7X200:pvrThinkPadT460:rvnLENOVO:rn20FMS7X200:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T460
dmi.product.name: 20FMS7X200
dmi.product.sku: LENOVO_MT_20FM_BU_Think_FM_ThinkPad T460
dmi.product.version: ThinkPad T460
dmi.sys.vendor: LENOVO

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

Title:
  hplip executables missing

Status in hplip package in Ubuntu:
  New

Bug description:
  After fresh install of hplip and hplip-gui, executable symlinks
  /usr/bin/hp* are broken.  /usr/share/hplip/*.py are not present, and
  in fact, the /usr/share/hplip directory is missing completely.  The
  package is completely broken.

  Here is the output of the package installation:

  $ sudo apt install hplip-gui 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
hplip
  Suggested packages:
hplip-doc
  The following NEW packages will be installed:
hplip hplip-gui
  0 upgraded, 2 newly installed, 0 to remove and 9 not upgraded.
  Need to get 223 kB of archives.
  After this operation, 687 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://mirror.it.ubc.ca/ubuntu focal/main amd64 hplip amd64 
3.20.3+dfsg0-2 [204 kB]
  Get:2 http://mirror.it.ubc.ca/ubuntu focal/universe amd64 hplip-gui all 
3.20.3+dfsg0-2 [19.1 kB]
  Fetched 223 kB in 0s (573 kB/s)

[Desktop-packages] [Bug 1901376] [NEW] xdmcp stopped working with groovy gdm3

2020-10-24 Thread Ryutaroh Matsumoto

Public bug reported:

On Ubuntu Focal

[xdmcp]
Enable=tue
ShowLocalGreeter=false

in /etc/gdm3/custom.conf enabled XDMCP.
But the same config. has no effect in Groovy.

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


** Tags: groovy

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

Title:
  xdmcp stopped working with groovy gdm3

Status in gdm3 package in Ubuntu:
  New

Bug description:
  On Ubuntu Focal

  [xdmcp]
  Enable=tue
  ShowLocalGreeter=false

  in /etc/gdm3/custom.conf enabled XDMCP.
  But the same config. has no effect in Groovy.

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

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

[Desktop-packages] [Bug 1901112] Re: Default gray wallpaper symbolic link is broken.

何を言っているのか良くはわからぬが
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1901367
に書いたとおり
/usr/share/gnome-background-properties/groovy-wallpapers.xml
には Gorilla Wallpaper Grey

/usr/share/backgrounds/Gorilla_Wallpaper_Grey_4096x2304.png
zoom
#00
#00
solid
という記述はなく、残念ながらあのHand Some Gorillaちゃんの壁紙は選べない
是非追加をして頂きたいものだ
Sorry, My Engrish is Poor Please Fix This Bug(Request?) 1901367
Thanks, Hand Some Gorilla :-)

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

Title:
Default gray wallpaper symbolic link is broken.

Status in ubuntu-wallpapers package in Ubuntu:
New

Bug description:
Default gray wallpaper symbolic link is broken. The link is still
linked to the name of the old one from Focal Fossa. It should be
linked to the new wallpaper. And considering that the old file does
not even exist in Groovy anymore, it will just set the wallpaper to a
black dark gray background.

Information:

1. Ubuntu 20.10 Groovy Gorilla amd64

2. ubuntu-wallpapers-groovy 20.10.2-0ubuntu1 or possibly ubuntu-
wallpapers 20.10.2-0ubuntu1

3. Gray wallpaper should work normally and should not have a broken
symbolic. It should set the actual wallpaper.

4. The symbolic link is broken and selecting the image for wallpaper
use in Control Center results in a blank dark gray background being
set.

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

[Desktop-packages] [Bug 1793124]

2020-10-24 Thread Lerouxethan32

(In reply to Ethan from comment #27)
> Made an account to say, I'd really like this bug solved / feature added

(dunno how to edit a comment).

And Calligra Sheets doesn't seem to have this problem

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

Title:
  [upstream] Scrolling on Calc leaves content invisible if cell is
  higher than screen

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

Bug description:
  I sometimes receive Calc documents where the content of an individual
  cell is split on so many lines that it fills up the whole screen and
  more. I can easily see the top part of these cells but scrolling to
  the bottom does not seem to work. Whether I try dragging the scrollbar
  or moving the screen with my laptop’s touchpad, Calc seems to skip the
  bottom part of the cell and jump directly to the following cell. See
  the attached screenshots of a document which has numbers 1 to 50 so
  that numbers 4 to 40 occupy one single cell (A4). In the first
  screenshot I see the top part of that cell (4 to 23) and in the next I
  have scrolled down the screen as little as possible, and now I see
  cell A5 (number 41) on the top. Everything in between is visually
  inaccessible whatever I try.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

Installed: 1:6.0.3-0ubuntu1
Candidate: 1:6.0.3-0ubuntu1
Version table:
   *** 1:6.0.3-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 18 11:16:17 2018
  InstallationDate: Installed on 2017-02-13 (582 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1793124/+subscriptions

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

[Desktop-packages] [Bug 1793124]

2020-10-24 Thread Lerouxethan32

Made an account to say, I'd really like this bug solved / feature added

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

Title:
  [upstream] Scrolling on Calc leaves content invisible if cell is
  higher than screen

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

Bug description:
  I sometimes receive Calc documents where the content of an individual
  cell is split on so many lines that it fills up the whole screen and
  more. I can easily see the top part of these cells but scrolling to
  the bottom does not seem to work. Whether I try dragging the scrollbar
  or moving the screen with my laptop’s touchpad, Calc seems to skip the
  bottom part of the cell and jump directly to the following cell. See
  the attached screenshots of a document which has numbers 1 to 50 so
  that numbers 4 to 40 occupy one single cell (A4). In the first
  screenshot I see the top part of that cell (4 to 23) and in the next I
  have scrolled down the screen as little as possible, and now I see
  cell A5 (number 41) on the top. Everything in between is visually
  inaccessible whatever I try.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

Installed: 1:6.0.3-0ubuntu1
Candidate: 1:6.0.3-0ubuntu1
Version table:
   *** 1:6.0.3-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 18 11:16:17 2018
  InstallationDate: Installed on 2017-02-13 (582 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1793124/+subscriptions

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

[Desktop-packages] [Bug 1892928] Re: Audio settings shows wrong application icons

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

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

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

Title:
  Audio settings shows wrong application icons

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

Bug description:
  The gnome sound settings show wrong icons
  https://pasteboard.co/Jo3btdG.png
  (here e.g. Chromium icon for Opera)

  In the program menu all icons are correct.

  (Ubuntu 20.04, Gnome 3.36.1)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_29_33_generic_69
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 25 22:34:35 2020
  InstallationDate: Installed on 2019-06-22 (430 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1901367] Re: ubuntu 20.10 background

ごめんなさい英語がよくわからなくて
でも1901353のバグもこれでfixするはずです

Sorry, My Engrish is poor I can't understand 1901353 bug report.
TOMO-ARE perhaps will be fixed by This way.
Thank you Handsome Gorilla :-)

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

Title:
  ubuntu 20.10 background

Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  about ubuntu 20.10 background
  /usr/share/backgrounds/contest/groovy.xml
  /usr/share/gnome-background-properties/groovy-wallpapers.xml
  wrong Filename "x:...Pierre Châte... -> o:...Pierre_Châte..."
  and please add "Gorilla Wallpaper Grey" to groovy-wallpapers.xml :-)

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

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

[Desktop-packages] [Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards

2020-10-24 Thread Bug Watch Updater

** Changed in: gnome-shell
   Status: New => 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/1738676

Title:
  With natural scrolling, horizontal sliders behave backwards

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  When natural-scrolling is enabled, controlling horizontal sliders is
  backwards and counter intuitive.

  The volume control in the top-bar "speaker" icon is backwards.

  You have to...
  - scroll DOWN, to INCREASE the volume
  - scroll UP, to DECREASE the volume

  Expected behavior:

  Enable natural-scrolling and
  - scroll UP, to INCREASE the volume
  - scroll DOWN, to DECREASE the volume
  - scroll UP, to INCREASE the screen brightness
  - scroll DOWN, to DECREASE the screen brightness

  Enable natural-scrolling, hover over a horizontal slider, and...
  - scroll UP, to move the slider to the RIGHT
  - scroll DOWN, to move the slider to the LEFT

  This happens for the OSD volume icon, and for the volume slider in the
  topbar menu.

  This also happens for screen brightness controls.

  This problem occurs for both mouse natural-scrolling and touchpad
  natural scrolling.

  Expected fix:

  When the pointer hovers over the speaker icon in the scroll actions on the 
speaker icon in the top bar should be reversed.
  When the user interacts with a horizontal slider, scrolling to the top should 
always move the slider to the right, and scrolling down should always move the 
slider to the left, even if natural-scrolling is enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec 17 19:23:30 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['r']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'spotify.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 
'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 
'gnome-system-monitor.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-12-10 (7 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.12.10 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1901353] Re: Ubuntu Default Greyscale Wallpaper Sym Link Broken

2020-10-24 Thread Chris Guiver

Possibly related to this bug report is
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1901367

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

Title:
  Ubuntu Default Greyscale Wallpaper Sym Link Broken

Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  The sym link still links to the nonexistent Focal greyscale wallpaper.

  How to reproduce:

  Try to set the wallpaper to the default greyscale in Settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-wallpapers 20.10.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 24 21:40:40 2020
  Dependencies: ubuntu-wallpapers-groovy 20.10.2-0ubuntu1
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-wallpapers
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1852172] Re: Battery history and statistics graphs markings are unreadable on a dark theme

2020-10-24 Thread Hiroshi Miura

We can see a changed color of legend labels with modification of fixed color 
values.
It should be get from theme color instead of fixed value.


>From ebe0b3a96deb7039c70843bece6b958bdf0b25f0 Mon Sep 17 00:00:00 2001
From: Hiroshi Miura 
Date: Sun, 25 Oct 2020 11:45:03 +0900
Subject: [PATCH] Change x/y label color

Signed-off-by: Hiroshi Miura 
---
 src/egg-graph-widget.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/egg-graph-widget.c b/src/egg-graph-widget.c
index 7c2fc9e..75783b9 100644
--- a/src/egg-graph-widget.c
+++ b/src/egg-graph-widget.c
@@ -491,7 +491,7 @@ egg_graph_widget_draw_labels (EggGraphWidget *graph, 
cairo_t *cr)
cairo_save (cr);
 
/* do x text */
-   cairo_set_source_rgb (cr, 0.2f, 0.2f, 0.2f);
+   cairo_set_source_rgb (cr, 0.5f, 0.5f, 0.5f);
for (i = 0; i < 11; i++) {
g_autofree gchar *text = NULL;
b = priv->box_x + ((gdouble) i * divwidth);
-- 
2.25.1

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

Title:
  Battery history and statistics graphs markings are unreadable on a
  dark theme

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

Bug description:
  1 - Use a dark theme using Gnome Tweaks.
  2 - Open Power Statistics
  3 - Click on Laptop battery -> History or Statistics tab.

  The markings on the X and Y axes are not readable since the text
  colour does not adapt to the dark theme.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-power-manager 3.32.0-1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 12 12:25:29 2019
  ExecutablePath: /usr/bin/gnome-power-statistics
  InstallationDate: Installed on 2019-10-19 (23 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   LANG=en_IN
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1901367] Re: ubuntu 20.10 background

2020-10-24 Thread Chris Guiver

Thank you for reporting this bug, and helping to make Ubuntu better.

This is likely a duplicate of https://bugs.launchpad.net/ubuntu/+source
/ubuntu-wallpapers/+bug/1901353

Can you please have a look at that bug report, and if I'm correct,
please mark this as a duplicate of 1901353

Thanks

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

Title:
  ubuntu 20.10 background

Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  about ubuntu 20.10 background
  /usr/share/backgrounds/contest/groovy.xml
  /usr/share/gnome-background-properties/groovy-wallpapers.xml
  wrong Filename "x:...Pierre Châte... -> o:...Pierre_Châte..."
  and please add "Gorilla Wallpaper Grey" to groovy-wallpapers.xml :-)

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

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

[Desktop-packages] [Bug 1901367] Re: ubuntu 20.10 background

UBUNTU 20.10 の本体はどうかわかりませんが
https://launchpad.net/ubuntu/+source/ubuntu-wallpapers
からDLした2020-10-23の
ubuntu-wallpapers-groovy_20.10.2-0ubuntu1_all.deb
をインストールしたところ
真っ黒な画面になる現象が起きました
これは
/usr/share/backgrounds/contest/groovy.xml
/usr/share/gnome-background-properties/groovy-wallpapers.xml
にファイル名のバグがありまして
Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg　が
Abstract_Painting_Photo_by_Pierre Châtel-Innocenti.jpg　と記述されている為で
スペースをアンダーバーに直すと正常になりました
ついでですが
昔は.pngのbackgroundsも"groovy-wallpapers.xml"に記載されており
選択肢に出てきていましたが　いつの間にか無くなってしまい寂しいです
Gorilla_Wallpaper_Grey_4096x2304.png
も"groovy-wallpapers.xml"に是非加えてあげて下さい
彼女はとてもハンサムなゴリラだと思います　(^^) _in_Japanese

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

Title:
  ubuntu 20.10 background

Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  about ubuntu 20.10 background
  /usr/share/backgrounds/contest/groovy.xml
  /usr/share/gnome-background-properties/groovy-wallpapers.xml
  wrong Filename "x:...Pierre Châte... -> o:...Pierre_Châte..."
  and please add "Gorilla Wallpaper Grey" to groovy-wallpapers.xml :-)

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

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

[Desktop-packages] [Bug 1901367] [NEW] ubuntu 20.10 background

Public bug reported:

about ubuntu 20.10 background
/usr/share/backgrounds/contest/groovy.xml
/usr/share/gnome-background-properties/groovy-wallpapers.xml
wrong Filename "x:...Pierre Châte... -> o:...Pierre_Châte..."
and please add "Gorilla Wallpaper Grey" to groovy-wallpapers.xml :-)

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

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

Title:
  ubuntu 20.10 background

Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  about ubuntu 20.10 background
  /usr/share/backgrounds/contest/groovy.xml
  /usr/share/gnome-background-properties/groovy-wallpapers.xml
  wrong Filename "x:...Pierre Châte... -> o:...Pierre_Châte..."
  and please add "Gorilla Wallpaper Grey" to groovy-wallpapers.xml :-)

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

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

[Desktop-packages] [Bug 1901351] Re: Bluetooth Mouse Natural Scrolling backwards on boot/sleep

2020-10-24 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  Bluetooth Mouse Natural Scrolling backwards on boot/sleep

Status in xorg package in Ubuntu:
  New

Bug description:
  Every time the Bluetooth mouse connects, the Natural Scrolling is
  ineffective.

  Settings shows it "Enabled" but it scrolls in the "not Natural"
  direction.

  Disabling and re-enabling the setting temporarily restores the
  direction, but it only lasts until the mouse reconnects.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 24 13:49:20 2020
  DistUpgraded: 2020-10-24 12:59:49,175 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:5036]
  MachineType: LENOVO 20BWS1D61J
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic 
root=UUID=09cc0657-0a94-4a6c-9043-2df6132cd821 ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (0 days ago)
  dmi.bios.date: 02/23/2019
  dmi.bios.release: 1.36
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET72WW (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS1D61J
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET72WW(1.36):bd02/23/2019:br1.36:efr1.4:svnLENOVO:pn20BWS1D61J:pvrThinkPadT450s:rvnLENOVO:rn20BWS1D61J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS1D61J
  dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1901350] Re: Touchpad stops working after sleep

2020-10-24 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  Touchpad stops working after sleep

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.04 and 20.10, the touchpad stops working after sleep.

  Restarting with rmmod psmouse and modprobe psmouse is not working
  anymore, the touchpad reloads but with the wrong settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 24 13:42:39 2020
  DistUpgraded: 2020-10-24 12:59:49,175 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:5036]
  MachineType: LENOVO 20BWS1D61J
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic 
root=UUID=09cc0657-0a94-4a6c-9043-2df6132cd821 ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (0 days ago)
  dmi.bios.date: 02/23/2019
  dmi.bios.release: 1.36
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET72WW (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS1D61J
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET72WW(1.36):bd02/23/2019:br1.36:efr1.4:svnLENOVO:pn20BWS1D61J:pvrThinkPadT450s:rvnLENOVO:rn20BWS1D61J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS1D61J
  dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1901350] [NEW] Touchpad stops working after sleep

You have been subscribed to a public bug:

On Ubuntu 20.04 and 20.10, the touchpad stops working after sleep.

Restarting with rmmod psmouse and modprobe psmouse is not working
anymore, the touchpad reloads but with the wrong settings.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 24 13:42:39 2020
DistUpgraded: 2020-10-24 12:59:49,175 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 5500 [17aa:5036]
MachineType: LENOVO 20BWS1D61J
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic 
root=UUID=09cc0657-0a94-4a6c-9043-2df6132cd821 ro
SourcePackage: xorg
UpgradeStatus: Upgraded to groovy on 2020-10-24 (0 days ago)
dmi.bios.date: 02/23/2019
dmi.bios.release: 1.36
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET72WW (1.36 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BWS1D61J
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.4
dmi.modalias: 
dmi:bvnLENOVO:bvrJBET72WW(1.36):bd02/23/2019:br1.36:efr1.4:svnLENOVO:pn20BWS1D61J:pvrThinkPadT450s:rvnLENOVO:rn20BWS1D61J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T450s
dmi.product.name: 20BWS1D61J
dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s
dmi.product.version: ThinkPad T450s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug groovy ubuntu
-- 
Touchpad stops working after sleep
https://bugs.launchpad.net/bugs/1901350
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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

[Desktop-packages] [Bug 1901351] [NEW] Bluetooth Mouse Natural Scrolling backwards on boot/sleep

You have been subscribed to a public bug:

Every time the Bluetooth mouse connects, the Natural Scrolling is
ineffective.

Settings shows it "Enabled" but it scrolls in the "not Natural"
direction.

Disabling and re-enabling the setting temporarily restores the
direction, but it only lasts until the mouse reconnects.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 24 13:49:20 2020
DistUpgraded: 2020-10-24 12:59:49,175 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 5500 [17aa:5036]
MachineType: LENOVO 20BWS1D61J
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic 
root=UUID=09cc0657-0a94-4a6c-9043-2df6132cd821 ro
SourcePackage: xorg
UpgradeStatus: Upgraded to groovy on 2020-10-24 (0 days ago)
dmi.bios.date: 02/23/2019
dmi.bios.release: 1.36
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET72WW (1.36 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BWS1D61J
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.4
dmi.modalias: 
dmi:bvnLENOVO:bvrJBET72WW(1.36):bd02/23/2019:br1.36:efr1.4:svnLENOVO:pn20BWS1D61J:pvrThinkPadT450s:rvnLENOVO:rn20BWS1D61J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T450s
dmi.product.name: 20BWS1D61J
dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s
dmi.product.version: ThinkPad T450s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug groovy ubuntu
-- 
Bluetooth Mouse Natural Scrolling backwards on boot/sleep
https://bugs.launchpad.net/bugs/1901351
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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

[Desktop-packages] [Bug 1901340] Re: Backup doesn't automatically start when drive is inserted

2020-10-24 Thread Michael Terry

Version 42.3 did fix an error with scheduled backups to encrypted
drives! I suspect that might be what you're hitting? Can you try the
snap and see if that fixes things? Might want to make a manual backup
first just to confirm everything is working.

snap install deja-dup --classic
sudo apt remove deja-dup

Maybe we should backport that patch to 20.04.

** Changed in: deja-dup (Ubuntu)
   Status: New => Incomplete

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

Title:
  Backup doesn't automatically start when drive is inserted

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  I have Deja Dup set up to automatically backup onto a removable drive
  encrypted with LUKS every day. Each morning I would get a notification
  saying that the backup will automatically start when the drive is
  connected. When I insert the drive, it is automatically unlocked since
  I have the password saved on the computer. But after waiting for
  around half an hour the backup doesn't seem to have started. When I
  open Deja Dup it says that the last backup was yesterday and the next
  backup is today. Clicking the Back Up Now button starts the backup.
  The drive is GPT partitioned with a single partition containing ext4
  inside LUKS.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: deja-dup 42.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 24 11:09:42 2020
  ExecutablePath: /usr/bin/deja-dup
  InstallationDate: Installed on 2020-10-20 (4 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (1 days ago)

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

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

[Desktop-packages] [Bug 1901358] [NEW] [System Settings] :Sound - 5.1 audio outputs are reported as Headphones

2020-10-24 Thread Gary Cameron

Public bug reported:

[System settings] Sound

ASUS ROG Zenith II Extreme Alpha TRX40 Motherboard

5.1 Audio outputs are only usable as stereo by selecting "Headphones USB
Audio", which means only the front right and left speaker work.

When I select "Speakers USB Audio" they do not work at all, neither as
stereo or 5.1 audio.

Ubuntu release 20.04

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

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

Title:
  [System Settings] :Sound - 5.1 audio outputs are reported as
  Headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  [System settings] Sound

  ASUS ROG Zenith II Extreme Alpha TRX40 Motherboard

  5.1 Audio outputs are only usable as stereo by selecting "Headphones
  USB Audio", which means only the front right and left speaker work.

  When I select "Speakers USB Audio" they do not work at all, neither as
  stereo or 5.1 audio.

  Ubuntu release 20.04

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

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

[Desktop-packages] [Bug 1647780] Re: [XPS 8900, Realtek ALC3861, Green Headphone Out, Front] No sound at all

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

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

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

Title:
  [XPS 8900, Realtek ALC3861, Green Headphone Out, Front] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound does not work for any line or headphone out.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  teshler8754 F pulseaudio
   /dev/snd/controlC0:  teshler8754 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec  6 10:59:00 2016
  InstallationDate: Installed on 2016-07-25 (133 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  teshler8754 F pulseaudio
   /dev/snd/controlC0:  teshler8754 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [XPS 8900, Realtek ALC3861, Green Headphone Out, Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0XJ8C4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd01/20/2016:svnDellInc.:pnXPS8900:pvr:rvnDellInc.:rn0XJ8C4:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: XPS 8900
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1901353] [NEW] Ubuntu Default Greyscale Wallpaper Sym Link Broken

2020-10-24 Thread NP Viroonc

Public bug reported:

The sym link still links to the nonexistent Focal greyscale wallpaper.

How to reproduce:

Try to set the wallpaper to the default greyscale in Settings.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubuntu-wallpapers 20.10.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CasperVersion: 1.455
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 24 21:40:40 2020
Dependencies: ubuntu-wallpapers-groovy 20.10.2-0ubuntu1
LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-wallpapers
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Ubuntu Default Greyscale Wallpaper Sym Link Broken

Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  The sym link still links to the nonexistent Focal greyscale wallpaper.

  How to reproduce:

  Try to set the wallpaper to the default greyscale in Settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-wallpapers 20.10.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 24 21:40:40 2020
  Dependencies: ubuntu-wallpapers-groovy 20.10.2-0ubuntu1
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-wallpapers
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1892643] Re: [SRU] Update libgweather to 3.36.1

2020-10-24 Thread Amr Ibrahim

I have libgweather 3.36.1-1~ubuntu20.04.1 installed for quite some time
now, the weather appears in gnome-shell without any problems, gnome-
weather shows the weather for four cities, three in Europe and one in
Africa, also without any problems.

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

** Patch removed: "libgweather_3.36.0-1_3.36.1-1~ubuntu20.04.1.diff"
   
https://bugs.launchpad.net/ubuntu/focal/+source/libgweather/+bug/1892643/+attachment/5417986/+files/libgweather_3.36.0-1_3.36.1-1~ubuntu20.04.1.diff

** Attachment removed: "libgweather_3.36.0-1_3.36.1-1~ubuntu20.04.1.diff.gz"
   
https://bugs.launchpad.net/ubuntu/focal/+source/libgweather/+bug/1892643/+attachment/5417988/+files/libgweather_3.36.0-1_3.36.1-1~ubuntu20.04.1.diff.gz

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

Title:
  [SRU] Update libgweather to 3.36.1

Status in libgweather:
  Unknown
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Focal:
  Fix Committed
Status in libgweather package in Debian:
  Unknown

Bug description:
  [Impact]

  libgweather 3.36.1 is a bug-fix release as part of GNOME 3.36.

  https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS

  This version works around the unavailability of the NOAA weather
  services by using very short-term forecasts as current weather
  conditions.

  Sometimes the current weather is not available because the NOAA
  weather servers aren't working correctly. Version 3.36.1 fixes the
  unavailability of current temperature in some locations.

  
  [Test case]

  Make sure that gnome-weather is still working properly and the weather
  in gnome-shell is shown when gnome-weather is installed.

  
  [Regression potential]

  The regression potential is low since the changes in version 3.36.1
  are small.

  
  [Other]

  libgweather 3.36.1 has been successfully built as a no-change backport
  from Groovy to Focal in my PPA and runs fine:

  
https://launchpad.net/~amribrahim1987/+archive/ubuntu/ppa/+packages?field.name_filter=libgweather&field.status_filter=published&field.series_filter=

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgweather-3-16 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 23 19:05:21 2020
  InstallationDate: Installed on 2020-04-26 (119 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libgweather
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1891649] Re: [snap] No separate icon/window tracking for app launchers

2020-10-24 Thread Cornelius

I have the same problem.

The workaround using "/snap/chromium/current/usr/lib/chromium-
browser/chrome" would link to the correct dash icon. But the app-
chromium uses the profile path ~/.config/chromium/Default in this case
instead ~/snap/chromium/common/chromium/Default. And when I open a link
in the app-chromium it opens a new window in the same profile and a new
dash icon (WM_CLASS chromium-browser instead of chromium). Hence this is
no useable workaround for me.

Parameter --profile-directory also does not work - seems like chromium
do not want to start a second process with the same profile.

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

Title:
  [snap] No separate icon/window tracking for app launchers

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I've created a custom chromium launcher for an internal website, starting 
chromium in --app mode.
  The launcher should get it's own Gnome dash icon.

  To match the created windows to the dash icon, I've taken the following 
measures:
  - include "StartupWMClass=myfoo" in the myfoo.desktop file
  - gave chromium the "--class=myfoo" parameter to make it set it's WM_CLASS to 
myfoo

  I've verified the WM_CLASS to be properly set to myfoo using xprop.
  However, this does not work when chromium is launched via snap.
  All windows get attributed to the chromium dash icon no matter what their 
WM_CLASS is.

  Bypassing snap and launching chromium via
  /snap/chromium/current/usr/lib/chromium-browser/chrome fixes the
  problem.

  Here are the full chromium exec lines:
  Broken:
  Exec=chromium --class=myfoo --no-first-run --app=https://internal.example.com/
  Working:
  Exec=/snap/chromium/current/usr/lib/chromium-browser/chrome --class=myfoo 
--no-first-run --app=https://internal.example.com/

  This is on a fully patched 20.04 system.

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

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

[Desktop-packages] [Bug 1901342] [NEW] Xorg freeze

2020-10-24 Thread Dan Ross

Public bug reported:

Description:Ubuntu 20.10
Release:20.10
5.8.0-25-generic #26-Ubuntu SMP Thu Oct 15 10:30:38 UTC 2020 x86_64 x86_64 
x86_64 GNU/Linux

After upgrading to Groovy Gorilla, my laptop hangs on the Ubuntu splash
screen after login. Workaround: Press CTRL+ALT+DEL then select recovery
mode for the 5.8 kernel, then select 'Resume'. Also, the screen
resolution seems to be lower than normal.

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

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 24 14:47:47 2020
DistUpgraded: Fresh install
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:015e]
   Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:015e]
InstallationDate: Installed on 2019-01-01 (662 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: Acer Aspire 6930
ProcEnviron:
 PATH=(custom, no username)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=1fca13f7-f9c9-45fe-8e1c-3c88c19237d4 ro recovery nomodeset 
dis_ucode_ldr
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/28/2009
dmi.bios.vendor: Acer
dmi.bios.version: v0.3238
dmi.board.name: Makalu
dmi.board.vendor: Acer
dmi.board.version: Not Applicable
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAcer:bvrv0.3238:bd07/28/2009:svnAcer:pnAspire6930:pvrNotApplicable:rvnAcer:rnMakalu:rvrNotApplicable:cvnAcer:ct1:cvrN/A:
dmi.product.name: Aspire 6930
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug freeze groovy 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/1901342

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.10
  Release:  20.10
  5.8.0-25-generic #26-Ubuntu SMP Thu Oct 15 10:30:38 UTC 2020 x86_64 x86_64 
x86_64 GNU/Linux

  After upgrading to Groovy Gorilla, my laptop hangs on the Ubuntu
  splash screen after login. Workaround: Press CTRL+ALT+DEL then select
  recovery mode for the 5.8 kernel, then select 'Resume'. Also, the
  screen resolution seems to be lower than normal.

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 24 14:47:47 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Contro

[Desktop-packages] [Bug 1901294] Re: nouveau timeout and system lockup

** Description changed:

After upgrading from 20.04 to 20.10 system is unusable anymore due to
GPU issues with nouveau. Same system worked fine on 20.04.

Switching to nvidia proprietary driver and Xorg fixes the issue.

Symptoms:

System starts just fine, but overall UI performance is bad, everything
seems slow and CPU usage seems too high even when idle. After a while UI
freezes completly. Sometimes it recovers after several minutes, other
times it doesn't and system freezes forever, requiring hard reboot.

- Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti.
+ Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti. Intel Xeon
+ E3-1231 v3.

dmesg output attached.

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

Title:
nouveau timeout and system lockup

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

Bug description:
After upgrading from 20.04 to 20.10 system is unusable anymore due to
GPU issues with nouveau. Same system worked fine on 20.04.

Switching to nvidia proprietary driver and Xorg fixes the issue.

Symptoms:

Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti. Intel Xeon
E3-1231 v3.

dmesg output attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+subscriptions

[Desktop-packages] [Bug 1901294] Re: nouveau timeout and system lockup

Tried 5.9.1 mainline kernel and got the same issue. The only difference
is Wayland recovered much faster (under 1 min). I didn't wait after
recovery to see if system will lockup completely and rebooted with
proprietary driver. Attaching dmesg output.

** Attachment added: "dmesg_5.9.1_mainline.log"

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+attachment/5426606/+files/dmesg_5.9.1_mainline.log

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

Title:
nouveau timeout and system lockup

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

Bug description:
After upgrading from 20.04 to 20.10 system is unusable anymore due to
GPU issues with nouveau. Same system worked fine on 20.04.

Switching to nvidia proprietary driver and Xorg fixes the issue.

Symptoms:

Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti.

dmesg output attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+subscriptions

[Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 and 5.6

2020-10-24 Thread Abdel Bolanos Martinez

Hi, I found the same issue with nvidia-340 on groovy (kernel 5.8).

Setting up nvidia-340 (340.108-0ubuntu5) ...
dpkg: error: version '-' has bad syntax: revision number is empty
dpkg: error: version '-' has bad syntax: revision number is empty
dpkg: error: version '-' has bad syntax: revision number is empty
dpkg: error: version '-' has bad syntax: revision number is empty
dpkg: error: version '-' has bad syntax: revision number is empty
update-initramfs: deferring update (trigger activated)
INFO:Enable nvidia-340
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
Adding system user `nvidia-persistenced' (UID 132) ...
Adding new group `nvidia-persistenced' (GID 141) ...
Adding new user `nvidia-persistenced' (UID 132) with group 
`nvidia-persistenced' ...
Not creating home directory `/'.
Loading new nvidia-340-340.108 DKMS files...
Building for 5.8.0-22-generic
Building for architecture x86_64
Building initial module for 5.8.0-22-generic
ERROR (dkms apport): kernel package linux-headers-5.8.0-22-generic is not 
supported
Error! Bad return status for module build on kernel: 5.8.0-22-generic (x86_64)
Consult /var/lib/dkms/nvidia-340/340.108/build/make.log for more information.
dpkg: error processing package nvidia-340 (--configure):
 installed nvidia-340 package post-installation script subprocess returned 
error exit status 10
Processing triggers for desktop-file-utils (0.24-1ubuntu4) ...
Processing triggers for mime-support (3.64ubuntu1) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
Processing triggers for libc-bin (2.32-0ubuntu3) ...
Processing triggers for man-db (2.9.3-2) ...
Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu2) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for initramfs-tools (0.137ubuntu12) ...
update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic
Errors were encountered while processing:
 nvidia-340

If you need my log file, please let me know.

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

Title:
  Nvidia 340.108 fails to install with kernels 5.5 and 5.6

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

Bug description:
  Hi developers,

  thanks for your great work on porting legacy drivers to Ubuntu.

  Anyway I have to complain in not seeing Nvidia 340.108 driver for
  kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4,
  because Nvidia 340.108 fails to install with kernels 5.5 and 5.6.

  Archlinux already has a driver for Kernel 5.6 via AUR
  (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has
  one for kernel 5.5.

  So, the question is: when will we see a new version in repositories?

  Bye and have a nice day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions

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

[Desktop-packages] [Bug 1901340] [NEW] Backup doesn't automatically start when drive is inserted

2020-10-24 Thread Alexander Zhang

Public bug reported:

I have Deja Dup set up to automatically backup onto a removable drive
encrypted with LUKS every day. Each morning I would get a notification
saying that the backup will automatically start when the drive is
connected. When I insert the drive, it is automatically unlocked since I
have the password saved on the computer. But after waiting for around
half an hour the backup doesn't seem to have started. When I open Deja
Dup it says that the last backup was yesterday and the next backup is
today. Clicking the Back Up Now button starts the backup. The drive is
GPT partitioned with a single partition containing ext4 inside LUKS.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: deja-dup 42.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 24 11:09:42 2020
ExecutablePath: /usr/bin/deja-dup
InstallationDate: Installed on 2020-10-20 (4 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, user)
 LANG=en_US.UTF-8
SourcePackage: deja-dup
UpgradeStatus: Upgraded to groovy on 2020-10-23 (1 days ago)

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

Title:
  Backup doesn't automatically start when drive is inserted

Status in deja-dup package in Ubuntu:
  New

Bug description:
  I have Deja Dup set up to automatically backup onto a removable drive
  encrypted with LUKS every day. Each morning I would get a notification
  saying that the backup will automatically start when the drive is
  connected. When I insert the drive, it is automatically unlocked since
  I have the password saved on the computer. But after waiting for
  around half an hour the backup doesn't seem to have started. When I
  open Deja Dup it says that the last backup was yesterday and the next
  backup is today. Clicking the Back Up Now button starts the backup.
  The drive is GPT partitioned with a single partition containing ext4
  inside LUKS.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: deja-dup 42.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 24 11:09:42 2020
  ExecutablePath: /usr/bin/deja-dup
  InstallationDate: Installed on 2020-10-20 (4 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (1 days ago)

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

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

[Desktop-packages] [Bug 1901187] Re: Keyboard layout switch problem

2020-10-24 Thread Ubuntu One

Same versions as OP.

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

Title:
  Keyboard layout switch problem

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

Bug description:
  Hello,

  I have a problem where keyboard layout change stops actually switching
  the keyboard input layout.

  Ubuntu version: 20.04.1 LTS

  Desktop environment: Gnome 3.36.3 (Ubuntu desktop)

  Steps to reproduce:
  1. Plug an external USB keyboard
  2. Log in to your ubuntu-desktop session
  3. Change layout => works properly
  4. Unplug USB keyboard and plug it again
  5. Change keyboard layout => Problem

  Expected behaviour:
  Changing keyboard layout through GUI to change keyboard layout from French to 
English.

  What happened instead:
  The GUI indicates that the layout changed. However when typing text into any 
window, the layout actually does not change.

  This problem also happens when the computer goes to sleep as it disconnects 
USB devices.
  Once the external USB keyboard is disconnected, the only way to get it to 
switch layout is by logging out and back in.

  If you could point me out to what logs would be useful and where to
  find them, I could provide you with more information.

  
  Note:
  It is worth noting that I am using an external USB keyboard on my laptop. 
Unplugging the keyboard fixes the problem once it happens. However re-plugging 
it causes the problem to instantly happen again.

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

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

[Desktop-packages] [Bug 1901187] Re: Keyboard layout switch problem

2020-10-24 Thread Ubuntu One

Suffered the same issue, with broken behaviour on external USB keyboard
but normal behaviour on laptop's internal keyboard. Workaround was to
remove the French keyboard layout and reinstall it. So far so good.

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

Title:
Keyboard layout switch problem

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

Bug description:
Hello,

I have a problem where keyboard layout change stops actually switching
the keyboard input layout.

Ubuntu version: 20.04.1 LTS

Desktop environment: Gnome 3.36.3 (Ubuntu desktop)

Steps to reproduce:
1. Plug an external USB keyboard
2. Log in to your ubuntu-desktop session
3. Change layout => works properly
4. Unplug USB keyboard and plug it again
5. Change keyboard layout => Problem

Expected behaviour:
Changing keyboard layout through GUI to change keyboard layout from French to
English.

What happened instead:
The GUI indicates that the layout changed. However when typing text into any
window, the layout actually does not change.

This problem also happens when the computer goes to sleep as it disconnects
USB devices.
Once the external USB keyboard is disconnected, the only way to get it to
switch layout is by logging out and back in.

If you could point me out to what logs would be useful and where to
find them, I could provide you with more information.

Note:
It is worth noting that I am using an external USB keyboard on my laptop.
Unplugging the keyboard fixes the problem once it happens. However re-plugging
it causes the problem to instantly happen again.

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

[Desktop-packages] [Bug 1901279] Re: map wacom drawing tablet to single monitor doesn't work

2020-10-24 Thread tylerecouture

Upon further investigation, this appears to be a problem with the
display output names names no longer being recognized when using some
nvidia drivers.  e.g VGA-1 HMDI-0 etc as provided by xrandr

For example:
$ xsetwacom --set "Wacom Intuos Pro S Pen stylus" MapToOutput DP-3
Unable to find an output 'DP-3'.

But I can set it using the coords or HEAD
$ xsetwacom --set "Wacom Intuos Pro S Pen stylus" MapToOutput 1920x1080+0+0

or

$ xsetwacom --set "Wacom Intuos Pro S Pen stylus" MapToOutput HEAD-0

reference: https://github.com/linuxwacom/xf86-input-wacom/wiki/Dual-and-
Multi-Monitor-Set-Up#nvidia-binary-driver

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

Title:
  map wacom drawing tablet to single monitor doesn't work

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

Bug description:
  When I try to map my wacom tablet to a single monitor, it doesn't do
  anything.  The tablet appears fine with the proper name in the tablet
  setting app, and it appears if I run xsetwacom --list

  Tried:

  Wacom Graphire3 4x5 (CTE-430)
  Wacom Intuos Pro S (PTH-460)

  
  Also same problem on Ubuntu 20.04 (and Nvidia RTX 2060) with Wacom Intuos Pro 
M (PTH-660)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.4-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 23 22:10:56 2020
  InstallationDate: Installed on 2019-07-03 (479 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-05-06 (170 days ago)

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

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

[Desktop-packages] [Bug 1901150] Re: No "Are you sure?" question when deleting something from Desktop

2020-10-24 Thread Adam Niedling

https://gitlab.gnome.org/World/ShellExtensions/desktop-
icons/-/issues/223

** Bug watch added: 
gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues #223
   https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues/223

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

Title:
  No "Are you sure?" question when deleting something from Desktop

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

Bug description:
  There isn't any "Are you sure?" question when deleting (del OR
  shift+del) something from Desktop.

  Was happening in 20.04 and now in 20.10 too.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell-extension-desktop-icons 20.04.0+git20200908-1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 23 10:08:44 2020
  InstallationDate: Installed on 2019-12-19 (308 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago)

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

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

[Desktop-packages] [Bug 1824260] Re: wrong kerning in SS-5 PDF form fields

2020-10-24 Thread xiota

Looking at `ss-5.pdf`, I saw the same rendering issue. The problem
appears to be associated with font substitution. In particular,
CourierStd is replaced with Ubuntu, which obviously won't render
properly.

![pdf-fonts](/uploads/aaa50e12cccb20910b8fa7c5d2d01b57/pdf-fonts.png)

I was able to correct the issue by installing the `fonts-urw-base35`
package and creating a file `~/.config/fontconfig/conf.d/10-pdf-
aliases.conf` with the following contents:






  CourierStd
  
  Nimbus Mono PS
  




This problem can likely be fixed by adding font substitution rules to
the appropriate font packages.

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

Title:
  wrong kerning in SS-5 PDF form fields

Status in Poppler:
  New
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  What I expected to happen:

  I am filling out the SS-5 Social Security Administration form (see
  attached). I entered "John Jacob Smith" into the "First", "Full Middle
  Name", and "Last" fields on page 5.

  What happened instead:

  I can enter the text without issue, but some of the letters are
  wrongly positioned, i.e. the kerning is wrong. For example, the letter
  "i" overlaps with the letter "m" in "Smith" (see attached image). It
  looks like the font in the fields might be displaying a variable width
  font when it is supposed to be a fixed-wdith font.

  Discussion:

  Since this bug is also present in xpdf and Okular (but not mupdf), I'm
  guessing this isn't a bug in Evince itself. However, I am reporting it
  here as a courtesy to other users (since Evince is the default PDF
  reader) and because I'm not sure which dependency is responsible. (I'm
  also not sure if it's a direct dependency problem or if it's something
  else like a font configuration issue.)

  Here is the output for pdffonts ss-5.pdf:

  name type  encoding emb 
sub uni object ID
   -  --- 
--- --- -
  IHPIKC+ArialMT   CID TrueType  Identity-H   yes 
yes yes824  0
  ArialMT  TrueType  WinAnsi  no  
no  no 826  0
  Arial-BoldMT TrueType  WinAnsi  no  
no  no 828  0
  CourierStd   Type 1WinAnsi  no  
no  no 145  0
  HelveticaType 1WinAnsi  no  
no  no 197  0
  MyriadPro-RegularType 1WinAnsi  no  
no  no 198  0
  ZapfDingbats Type 1ZapfDingbats no  
no  no 199  0

  I asked about this in an Ask Ubuntu question nearly a year ago, but
  received no response, so I am reporting a bug now instead:

  https://askubuntu.com/questions/1031235/wrong-letter-positioning-and-
  font-in-pdf-form

  Ubuntu version:

  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  evince version:

  $ apt-cache policy evince
  evince:
    Installed: 3.28.4-0ubuntu1
    Candidate: 3.28.4-0ubuntu1
    Version table:
   *** 3.28.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 10 21:27:11 2019
  InstallationDate: Installed on 2018-12-12 (119 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1901315] Re: Missing shortcuts for moving window to workspace right or left

2020-10-24 Thread Gunnar Hjalmarsson

Considering the fix of bug #1762952, Alt+Shift shouldn't be set
automatically in connection with a 20.04 -> 20.10 upgrade. Any chance
you can elaborate on which steps you took?

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

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

Title:
  Missing shortcuts for moving window to workspace right or left

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

Bug description:
  After upgrading to groovy, I can no longer move windows between
  workspaces to the right or left.  Both the "Move window one workspace
  right" and "Move window one workspace left" commands are missing from
  the list.  (See attached screenshot).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-lowlatency 5.8.14
  Uname: Linux 5.8.0-25-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 24 15:26:19 2020
  InstallationDate: Installed on 2018-08-25 (790 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-control-center
  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-control-center/+bug/1901315/+subscriptions

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

[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-10-24 Thread j.john.pease

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

had this issue in 20.04 switching to 20.10 has resolved the issue for me

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

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

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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

[Desktop-packages] [Bug 1901315] Re: Missing shortcuts for moving window to workspace right or left

2020-10-24 Thread Luis Arias

I was able to resolve the issue following the instructions here:

https://github.com/zakkak/workspace-
grid/issues/72#issuecomment-408428118

** Bug watch added: github.com/zakkak/workspace-grid/issues #72
   https://github.com/zakkak/workspace-grid/issues/72

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

Title:
  Missing shortcuts for moving window to workspace right or left

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

Bug description:
  After upgrading to groovy, I can no longer move windows between
  workspaces to the right or left.  Both the "Move window one workspace
  right" and "Move window one workspace left" commands are missing from
  the list.  (See attached screenshot).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-lowlatency 5.8.14
  Uname: Linux 5.8.0-25-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 24 15:26:19 2020
  InstallationDate: Installed on 2018-08-25 (790 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-control-center
  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-control-center/+bug/1901315/+subscriptions

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

[Desktop-packages] [Bug 1901318] [NEW] needs to depend on tcl (not just tcl8.6)

2020-10-24 Thread cmeerw

Public bug reported:

the package currently depends on tcl8.6, but
/usr/sbin/usb_modeswitch_dispatcher actually requires /usr/bin/tclsh
which isn't provided by tcl8.6, so it likely would need to depend on
something like tcl (= 8.6)

** Affects: usb-modeswitch (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  needs to depend on tcl (not just tcl8.6)

Status in usb-modeswitch package in Ubuntu:
  New

Bug description:
  the package currently depends on tcl8.6, but
  /usr/sbin/usb_modeswitch_dispatcher actually requires /usr/bin/tclsh
  which isn't provided by tcl8.6, so it likely would need to depend on
  something like tcl (= 8.6)

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

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

[Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 and 5.6

2020-10-24 Thread Ayush Kumar

Can verify the issue faced by sally (julesflwr). I too upgrade without
realizing the kernel incompatibility.

Butterfly (kelebek333),
Thanks a lot for your work, can you please add package of nvidia-340 for groovy 
too?
Again, thank you for your PPA repository!

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

Title:
  Nvidia 340.108 fails to install with kernels 5.5 and 5.6

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

Bug description:
  Hi developers,

  thanks for your great work on porting legacy drivers to Ubuntu.

  Anyway I have to complain in not seeing Nvidia 340.108 driver for
  kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4,
  because Nvidia 340.108 fails to install with kernels 5.5 and 5.6.

  Archlinux already has a driver for Kernel 5.6 via AUR
  (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has
  one for kernel 5.5.

  So, the question is: when will we see a new version in repositories?

  Bye and have a nice day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions

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

[Desktop-packages] [Bug 1901316] [NEW] [Z370 AORUS Gaming 7, Realtek ALC1220, Green Line Out, Rear] Playback problem. Center and subwoofer work, everything else has no sound.

2020-10-24 Thread Terry

Public bug reported:

When using the Ubuntu sound settings and doing a test, only the center
and subwoofer channels produce sound.  When playing any media that
relies on left/right channels, I don't hear anything.

Used alsamixer to unmute / increase volume to all desired channels with no 
change
Used PulseAudio volume control to load multiple different audio profiles with 
the same results.

Ubuntu Release: 
Description:Ubuntu 20.10
Release:20.10

alsa-base:
  Installed: 1.0.25+dfsg-0ubuntu5
  Candidate: 1.0.25+dfsg-0ubuntu5
  Version table:
 *** 1.0.25+dfsg-0ubuntu5 500
500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu groovy/main i386 Packages
100 /var/lib/dpkg/status

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

I also experienced the issue in the latest default kernel for Ubuntu, so
I downloaded one of the later stable ones:

Linux terry-pc 5.9.1-050901-generic #202010170731 SMP Sat Oct 17
07:42:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

When doing a speaker test, I get the following results:

speaker-test -c6

speaker-test 1.2.3

Playback device is default
Stream parameters are 48000Hz, S16_LE, 6 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 32 to 349525
Period size range from 10 to 116509
Using max buffer size 349524
Periods = 4
was set period_size = 87381
was set buffer_size = 349524
 0 - Front Left -- NO SOUND
 4 - Center -- WORKS CORRECTLY
 1 - Front Right -- NO SOUND
 3 - Rear Right -- NO SOUND
 2 - Rear Left -- NO SOUND
 5 - LFE -- WORKS CORRECTLY

I plugged headphones into the front jack, and the system detected and
switched the sound output device to the headphones.  However, I still
did not hear any sound when doing a test.

Lastly, this sound device works as expected under Windows 10, so I don't
believe that it is a hardware issue.

Thank you for your time.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 5.9.1-050901-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 24 09:12:25 2020
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Green Line Out, Rear
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Only some of outputs are working
Title: [Z370 AORUS Gaming 7, Realtek ALC1220, Green Line Out, Rear] Playback 
problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/28/2019
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F15a
dmi.board.asset.tag: Default string
dmi.board.name: Z370 AORUS Gaming 7
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF15a:bd11/28/2019:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ370AORUSGaming7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370AORUSGaming7:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Z370 AORUS Gaming 7
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
modified.conffile..etc.modprobe.d.alsa-base.conf: [deleted]

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


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

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

Title:
  [Z370 AORUS Gaming 7, Realtek ALC1220, Green Line Out, Rear] Playback
  problem.  Center and subwoofer work, everything else has no sound.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When using the Ubuntu sound settings and doing a test, only the center
  and subwoofer channels produce sound.  When playing any media that
  relies on left/right channels, I don't hear anything.

  Used alsamixer to unmute / increase volume to all desired channels with no 
change
  Used PulseAudio volume control to load multiple different audio profiles with 
the same results.

  Ubuntu Release: 
  Description:  Ubuntu 20.10
  Release:  20.10

  alsa-base:
Installed: 1.0.25+dfsg-0ubuntu5
Candidate: 1.0.25+dfsg-0ubuntu5
Version table:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://u

[Desktop-packages] [Bug 1901315] [NEW] Missing shortcuts for moving window to workspace right or left

2020-10-24 Thread Luis Arias

Public bug reported:

After upgrading to groovy, I can no longer move windows between
workspaces to the right or left.  Both the "Move window one workspace
right" and "Move window one workspace left" commands are missing from
the list.  (See attached screenshot).

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-control-center 1:3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-25.26-lowlatency 5.8.14
Uname: Linux 5.8.0-25-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 24 15:26:19 2020
InstallationDate: Installed on 2018-08-25 (790 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to groovy on 2020-10-24 (0 days ago)

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


** Tags: amd64 apport-bug groovy

** Attachment added: "Screenshot from 2020-10-24 15-23-48.png"
   
https://bugs.launchpad.net/bugs/1901315/+attachment/5426442/+files/Screenshot%20from%202020-10-24%2015-23-48.png

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

Title:
  Missing shortcuts for moving window to workspace right or left

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

Bug description:
  After upgrading to groovy, I can no longer move windows between
  workspaces to the right or left.  Both the "Move window one workspace
  right" and "Move window one workspace left" commands are missing from
  the list.  (See attached screenshot).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-lowlatency 5.8.14
  Uname: Linux 5.8.0-25-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 24 15:26:19 2020
  InstallationDate: Installed on 2018-08-25 (790 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-control-center
  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-control-center/+bug/1901315/+subscriptions

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

[Desktop-packages] [Bug 1885363] Re: [amdgpu] Screen flickers after waking up from suspend

2020-10-24 Thread Benjamin Altpeter

Just upgraded to Ubuntu 20.10. It seems like the issue is fixed with
that version, so this can be closed.

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

Title:
  [amdgpu] Screen flickers after waking up from suspend

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I upgraded my Ubuntu 20.04 system with a new graphics card a few days ago. 
Everything seems fine when running the system normally, however whenever I 
suspend the machine and then wake it back up, severe problems occur.
  The first time, the machine froze completely. Switching to a different TTY 
didn't work anymore and the keyboard LEDs didn't respond to caps and num lock 
anymore, so I had to force shutdown. The second time, it came back OK but the 
screen has been flickering heavily since. Restarting Gnome and unplugging and 
plugging monitors back in hasn't helped.

  Relevant specs:
  CPU: AMD® Ryzen 9 3900x 12-core processor × 24 
  GPU: AMD® Radeon rx 5600 xt (MSI RADEON RX 5600 XT MECH OC)
  Monitors: 1x Acer running at 3840x2160 60Hz, 2x Medion (showing up as 
"Messeltronik Dresden GmbH") both running at 1920x1080 60Hz.
  Gnome: 3.36.2
  X11
  Apt doesn't report any updates.

  The flickering is most pronounced on the Acer. On the Medions, it
  seems to only happen when something changes on the screen. I have
  tried to capture this on video: https://youtu.be/HWT1J76-x94

  
  This bug seem quite similar to this one 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874588). I can also stop 
the flickering by switching the Acer to 1080p but when switching back to 4k, 
the problem reappears.

  I hope that ubuntu-bug has included all the necessary details. Let me
  know if you need anything else.

  Thank you very much for your help!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  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: GNOME
  Date: Sat Jun 27 10:44:32 2020
  DistUpgraded: 2020-04-30 20:17:33,403 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.100, 5.4.0-37-generic, x86_64: installed
   nvidia, 440.100, 5.4.0-39-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev ca) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 
5600 OEM/5600 XT / 5700/5700 XT] [1462:381e]
  InstallationDate: Installed on 2019-03-26 (458 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-30 (57 days ago)
  dmi.bios.date: 04/08/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.60
  dmi.board.name: X570 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.:bvrP2.60:bd04/08/2020:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Extreme4: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.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all

2020-10-24 Thread Giuseppe Argentieri

I have the same model and same problem. Nothing to add apart from a
workaround which might be useful to address the problem, I hope.

1) I manually remove the module snd_rn_pci_acp3x.

Microphone stops working.

2) I restart pulseaudio with pulseaudio -k

Sound output starts working.

3) I manually reload snd_rn_pci_acp3x

Microphone detected and working again, without affecting the 'sink'
(output).


On a side note, but somehow related, the led light of the mic button (F4) is 
always on, whether the mic is muted or not.

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

Title:
  [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output 
didn't work anymore. 
  Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 
5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get 
the exact same problem (On 20.04 Livesystem it works) 
  An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device 
uses the wrong Kernel Module (Audio Input is working since it uses the correct 
kernel module and driver)

  
  07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device 
[1002:1637]
Subsystem: Lenovo Device [17aa:5081]
Kernel modules: snd_hda_intel
  --
  07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] 
Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01)
Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor 
[17aa:5081]
Kernel driver in use: snd_rn_pci_acp3x
Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x
  07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 10h-1fh) HD Audio Controller [1022:15e3]
Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller 
[17aa:5081]
Kernel modules: snd_hda_intel

  Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.8.16-050816-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  moritz 2175 F pulseaudio
   /dev/snd/pcmC1D0c:   moritz 2175 F...m pulseaudio
   /dev/snd/controlC0:  moritz 2175 F pulseaudio
   /dev/snd/pcmC0D0c:   moritz 2175 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri Oct 23 10:17:36 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed
  Symptom_Card: Webcam Vitade AF - USB 2.0 Camera
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  moritz 2175 F pulseaudio
   /dev/snd/pcmC1D0c:   moritz 2175 F...m pulseaudio
   /dev/snd/controlC0:  moritz 2175 F pulseaudio
   /dev/snd/pcmC0D0c:   moritz 2175 F...m pulseaudio
  Symptom_Type: No sound at all
  Title: [acp - acp, playback] No sound at all
  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: 20UD0013GE
  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:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UD0013GE
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T01:18:30.406924

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

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

[Desktop-packages] [Bug 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all

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

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

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

Title:
  [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output 
didn't work anymore. 
  Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 
5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get 
the exact same problem (On 20.04 Livesystem it works) 
  An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device 
uses the wrong Kernel Module (Audio Input is working since it uses the correct 
kernel module and driver)

  
  07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device 
[1002:1637]
Subsystem: Lenovo Device [17aa:5081]
Kernel modules: snd_hda_intel
  --
  07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] 
Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01)
Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor 
[17aa:5081]
Kernel driver in use: snd_rn_pci_acp3x
Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x
  07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 10h-1fh) HD Audio Controller [1022:15e3]
Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller 
[17aa:5081]
Kernel modules: snd_hda_intel

  Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.8.16-050816-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  moritz 2175 F pulseaudio
   /dev/snd/pcmC1D0c:   moritz 2175 F...m pulseaudio
   /dev/snd/controlC0:  moritz 2175 F pulseaudio
   /dev/snd/pcmC0D0c:   moritz 2175 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri Oct 23 10:17:36 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed
  Symptom_Card: Webcam Vitade AF - USB 2.0 Camera
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  moritz 2175 F pulseaudio
   /dev/snd/pcmC1D0c:   moritz 2175 F...m pulseaudio
   /dev/snd/controlC0:  moritz 2175 F pulseaudio
   /dev/snd/pcmC0D0c:   moritz 2175 F...m pulseaudio
  Symptom_Type: No sound at all
  Title: [acp - acp, playback] No sound at all
  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: 20UD0013GE
  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:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UD0013GE
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T01:18:30.406924

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

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

[Desktop-packages] [Bug 1901306] [NEW] Session Crash When CSGO Starts

2020-10-24 Thread Clayton Diggs

Public bug reported:

When launching CSGO via Steam (installed from the repositories via the
steam metapackage), the session begins hanging for a bit before a
fullscreen popup says "Something has gone wrong" and "the system could
not recover", a logout button, and I am sent back to GDM.

This does not happen under Wayland, BTW. But I was not sure whether to
report this as a GNOME Shell issue, a Mutter issue, or an X11/Xorg
issue.

GNOME Shell version:
gnome-shell:
  Installed: 3.38.1-1ubuntu1

System information:
System:Kernel: 5.8.0-25-generic x86_64 bits: 64 compiler: gcc v: 10.2.0 
Desktop: N/A
   Distro: Ubuntu 20.10 (Groovy Gorilla)
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x 
serial: 
   UEFI: American Megatrends v: 5407 date: 12/31/2019
CPU:   Info: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: 
Zen+ rev: 2
   L2 cache: 4096 KiB
   flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 108799
   Speed: 1376 MHz min/max: 1550/3400 MHz boost: disabled Core speeds 
(MHz): 1: 1377 2: 1377
   3: 1378 4: 1378 5: 1377 6: 1377 7: 1378 8: 1375 9: 1377 10: 1377 11: 
1376 12: 1377 13: 1376
   14: 1377 15: 1378 16: 1377
Graphics:  Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] 
vendor: XFX Pine
   driver: amdgpu v: kernel bus ID: 0c:00.0
   Display: x11 server: X.Org 1.20.9 driver: amdgpu,ati
   unloaded: fbdev,modesetting,radeon,vesa resolution: 3840x1080~144Hz
   OpenGL: renderer: AMD Radeon RX 5700 XT (NAVI10 DRM 3.38.0 
5.8.0-25-generic LLVM 11.0.0)
   v: 4.6 Mesa 20.2.1 direct render: Yes
Audio: Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / 
Z-Series]
   driver: snd_hda_intel v: kernel bus ID: 09:00.0
   Device-2: AMD Navi 10 HDMI Audio driver: snd_hda_intel v: kernel bus 
ID: 0c:00.1
   Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: 
snd_hda_intel v: kernel
   bus ID: 0e:00.3
   Device-4: Logitech HD Pro Webcam C920 type: USB driver: 
snd-usb-audio,uvcvideo
   bus ID: 1-1.3:4
   Device-5: C-Media Blue Snowball type: USB driver: 
hid-generic,snd-usb-audio,usbhid
   bus ID: 3-4:2
   Device-6: Kingston HyperX 7.1 Audio type: USB driver: 
hid-generic,snd-usb-audio,usbhid
   bus ID: 1-9:6
   Sound Server: ALSA v: k5.8.0-25-generic
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
vendor: ASUSTeK
   driver: r8169 v: kernel port: f000 bus ID: 04:00.0
   IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 
Drives:Local Storage: total: 6.60 TiB used: 625.28 GiB (9.3%)
   ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB size: 
232.89 GiB
   ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50 
size: 465.76 GiB
   temp: 28 C
   ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50 
size: 465.76 GiB
   temp: 25 C
   ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50 
size: 465.76 GiB
   temp: 26 C
   ID-5: /dev/sdd type: USB vendor: Western Digital model: WD easystore 
2624 size: 4.55 TiB
   ID-6: /dev/sde vendor: Western Digital model: WDS500G2B0A-00SM50 
size: 465.76 GiB
   temp: 26 C
Partition: ID-1: / size: 223.52 GiB used: 28.67 GiB (12.8%) fs: btrfs dev: 
/dev/nvme0n1p3
   ID-2: /boot size: 945.6 MiB used: 79.6 MiB (8.4%) fs: ext4 dev: 
/dev/nvme0n1p2
   ID-3: /home size: 223.52 GiB used: 28.67 GiB (12.8%) fs: btrfs dev: 
/dev/nvme0n1p3
Swap:  ID-1: swap-1 type: partition size: 7.46 GiB used: 4.0 MiB (0.1%) 
dev: /dev/nvme0n1p4
Sensors:   System Temperatures: cpu: 30.6 C mobo: N/A gpu: amdgpu temp: 48.0 C
   Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Info:  Processes: 442 Uptime: 1h 51m Memory: 31.36 GiB used: 2.55 GiB 
(8.1%) Init: systemd
   runlevel: 5 Compilers: gcc: N/A Packages: 1712 Shell: Bash v: 5.0.17 
inxi: 3.1.07

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 24 04:34:09 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-10-24 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy

** Description changed:

  When launching CS

[Desktop-packages] [Bug 1900812] Autopkgtest regression report (pulseaudio/1:13.99.2-1ubuntu2)

2020-10-24 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted pulseaudio (1:13.99.2-1ubuntu2) for 
groovy have finished running.
The following regressions have been reported in tests triggered by the package:

ffmpeg/unknown (armhf)


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

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

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

Thank you!

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

Title:
  pulseaudio crashed with SIGSEGV in
  pa_sink_move_streams_to_default_sink() from report_jack_state() from
  mixer_class_event() from hctl_elem_event_handler() from
  snd_hctl_elem_throw_event()

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  * Impact

  There is a segfault issue started with the recent update

  * Test case

  We don't have specific steps to trigger the issue so test for regression and 
verify that reports stop on
  https://errors.ubuntu.com/problem/31c6bfaf0ac65939a763307ca3d3a4f27f38e9f0

  * Regression potential

  The regression was created by a fix for gnome-control-center device
  selection issues, check that the settings still work correctly,
  allowing to change devices and showing the active one as selected

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

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

[Desktop-packages] [Bug 1901294] Re: nouveau timeout and system lockup

** Description changed:

After upgrading from 20.04 to 20.10 system is unusable anymore due to
GPU issues with nouveau. Same system worked fine on 20.04.

Switching to nvidia proprietary driver and Xorg fixes the issue.

Symptoms:

System starts just fine, but overall UI performance is bad, everything
seems slow and CPU usage seems too high even when idle. After a while UI
freezes completly. Sometimes it recovers after several minutes, other
- times it doesn't and system freezes forever, requiring hard revoot.
+ times it doesn't and system freezes forever, requiring hard reboot.

Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti.

dmesg output attached.

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

Title:
nouveau timeout and system lockup

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

Bug description:
After upgrading from 20.04 to 20.10 system is unusable anymore due to
GPU issues with nouveau. Same system worked fine on 20.04.

Switching to nvidia proprietary driver and Xorg fixes the issue.

Symptoms:

Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti.

dmesg output attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+subscriptions

[Desktop-packages] [Bug 1887502] Re: Desktop doesn't refresh (still shows files that have been deleted)

2020-10-24 Thread J-Paul BERARD

Issue ID #212

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

Title:
  Desktop doesn't refresh (still shows files that have been deleted)

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

Bug description:
  Ubuntu 20.04 wayland
  When I save different files (LibreOffice Writer and PDF) in the desktop 
folder, then delete them, the desktop doesn't refresh : the deleted files stay 
displayed on the desktop (the screen) (despite they don't appear anymore in 
Nautilus).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 14 11:27:06 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.6, 5.4.0-39-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] 
[1002:6739] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Barts PRO [Radeon HD 
6850] [174b:174b]
  InstallationDate: Installed on 2020-04-10 (94 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=042824eb-95be-471e-bdb4-d7adf594a94a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: 970 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.:bvrP2.80:bd08/05/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme4: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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1901296] [NEW] Display blinks black from time to time

2020-10-24 Thread Lyubomir

Public bug reported:

I have an issue since about a week or so, the display blinks black, like
it's turning off and on again. The black blink lasts for not more than a
second. I haven't managed to reproduce it in UEFI yet, so i believe it
might not be a hardware issue.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-52.57-lowlatency 5.4.65
Uname: Linux 5.4.0-52-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 24 12:29:59 2020
DistUpgraded: 2020-10-23 18:35:32,104 DEBUG /openCache(), new cache size 66443
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 450.80.02, 5.4.0-51-lowlatency, x86_64: installed
 nvidia, 450.80.02, 5.4.0-52-lowlatency, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:1193]
   Subsystem: Acer Incorporated [ALI] GP108M [GeForce MX150] [1025:119a]
InstallationDate: Installed on 2020-02-08 (258 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Acer Aspire A515-51G
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash 
resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality 
intel_iommu=on
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-10-23 (0 days ago)
dmi.bios.date: 01/03/2019
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.02
dmi.board.asset.tag: Type2 - Board Serial Number
dmi.board.name: Charmander_KL
dmi.board.vendor: KBL
dmi.board.version: V2.02
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.02
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
dmi.product.family: Aspire 5
dmi.product.name: Aspire A515-51G
dmi.product.sku: 
dmi.product.version: V2.02
dmi.sys.vendor: Acer
mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


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

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

Title:
  Display blinks black from time to time

Status in xorg package in Ubuntu:
  New

Bug description:
  I have an issue since about a week or so, the display blinks black,
  like it's turning off and on again. The black blink lasts for not more
  than a second. I haven't managed to reproduce it in UEFI yet, so i
  believe it might not be a hardware issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-lowlatency 5.4.65
  Uname: Linux 5.4.0-52-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 24 12:29:59 2020
  DistUpgraded: 2020-10-23 18:35:32,104 DEBUG /openCache(), new cache size 66443
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-51-lowlatency, x86_64: installed
   nvidia, 450.80.02, 5.4.0-52-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:1193]
 Subsystem: Acer Incorporated [ALI] GP108M [GeForce MX150] [1025:119a]
  InstallationDate: Installed on 2020-02-08 (258 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Acer Aspire A515-51G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash 
resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality 
intel_iommu=on
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-10-23 (0 days ago)
  dmi.bios.date:

[Desktop-packages] [Bug 1901294] Re: nouveau timeout and system lockup

** Description changed:

After upgrading from 20.04 to 20.10 system is unusable anymore due to
GPU issues with nouveau. Same system worked fine on 20.04.
+
+ Switching to nvidia proprietary driver and Xorg fixes the issue.

Symptoms:

System starts just fine, but overall UI performance is bad, everything
seems slow and CPU usage seems too high even when idle. After a while UI
freezes completly. Sometimes it recovers after several minutes, other
times it doesn't and system freezes forever, requiring hard revoot.

Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti.

dmesg output attached.

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

Title:
nouveau timeout and system lockup

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

Bug description:
After upgrading from 20.04 to 20.10 system is unusable anymore due to
GPU issues with nouveau. Same system worked fine on 20.04.

Switching to nvidia proprietary driver and Xorg fixes the issue.

Symptoms:

Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti.

dmesg output attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+subscriptions

[Desktop-packages] [Bug 1901294] [NEW] nouveau timeout and system lockup

Public bug reported:

After upgrading from 20.04 to 20.10 system is unusable anymore due to
GPU issues with nouveau. Same system worked fine on 20.04.

Symptoms:

System starts just fine, but overall UI performance is bad, everything
seems slow and CPU usage seems too high even when idle. After a while UI
freezes completly. Sometimes it recovers after several minutes, other
times it doesn't and system freezes forever, requiring hard revoot.

Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti.

dmesg output attached.

** Affects: xserver-xorg-video-nouveau (Ubuntu)
Importance: Undecided
Status: New

** Tags: groovy

** Attachment added: "dmesg.log"
https://bugs.launchpad.net/bugs/1901294/+attachment/5426351/+files/dmesg.log

** Tags added: groovy

** Description changed:

After upgrading from 20.04 to 20.10 system is unusable anymore due to
GPU issues with nouveau. Same system worked fine on 20.04.

Symptoms:

System starts just fine, but overall UI performance is bad, everything
seems slow and CPU usage seems too high even when idle. After a while UI
freezes completly. Sometimes it recovers after several minutes, other
- times it doesn't and system freezes completly.
+ times it doesn't and system freezes forever, requiring hard revoot.

Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti.

dmesg output attached.

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

Title:
nouveau timeout and system lockup

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

Bug description:
After upgrading from 20.04 to 20.10 system is unusable anymore due to
GPU issues with nouveau. Same system worked fine on 20.04.

Symptoms:

Setup: Ubuntu 20.10. nouveau. Wayland. nVidia GTX 1080 Ti.

dmesg output attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+subscriptions

[Desktop-packages] [Bug 1901293] [NEW] EPSON ET-2600 not detected by sane-find-scanner

2020-10-24 Thread Emersion

Public bug reported:

Used to work.

sane-find-scanner run by regular user doesn't work:

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

could not open USB device 0x1d6b/0x0003 at 002:001: Access denied (insufficient 
permissions)
could not open USB device 0x04b8/0x1122 at 001:010: Access denied (insufficient 
permissions)
could not open USB device 0x046d/0xc077 at 001:009: Access denied (insufficient 
permissions)
could not open USB device 0x1b1c/0x1b3d at 001:004: Access denied (insufficient 
permissions)
could not open USB device 0x046d/0xc31c at 001:003: Access denied (insufficient 
permissions)
could not open USB device 0x0930/0x6544 at 001:002: Access denied (insufficient 
permissions)
could not open USB device 0x1d6b/0x0002 at 001:001: Access denied (insufficient 
permissions)
  # No USB scanners found. If you expected something different, make sure that
  # you have loaded a kernel driver for your USB host controller and have setup
  # the USB system correctly. See man sane-usb for details.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.

  # You may want to run this program as root to find all devices. Once you
  # found the scanner devices, be sure to adjust access permissions as
  # necessary.

Works when run as root:

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
found USB scanner (vendor=0x04b8, product=0x1122) at libusb:001:010
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.

lsusb output:

Bus 001 Device 010: ID 04b8:1122 Seiko Epson Corp. ET-2600 Series

Tried adding this rule to /usr/lib/udev/rules.d/60-libsane.rules, but
this didn't help:

ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="1122",
ENV{libsane_matched}="yes"

However the rule does make it so uaccess is run:

$ sudo udevadm test $(udevadm info --query=path --name=/dev/bus/usb/001/010) 
2>&1
This program is for debugging only, it does not run any program
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.

Load module index
Parsed configuration file /usr/lib/systemd/network/99-default.link
Parsed configuration file /usr/lib/systemd/network/73-usb-net-by-mac.link
Created link configuration context.
Reading rules file: /usr/lib/udev/rules.d/39-usbmuxd.rules
Reading rules file: /usr/lib/udev/rules.d/40-usb-media-players.rules
Reading rules file: /usr/lib/udev/rules.d/40-usb_modeswitch.rules
Reading rules file: /usr/lib/udev/rules.d/40-vm-hotadd.rules
Reading rules file: /usr/lib/udev/rules.d/50-apport.rules
Reading rules file: /usr/lib/udev/rules.d/50-firmware.rules
Reading rules file: /usr/lib/udev/rules.d/50-udev-default.rules
Reading rules file: /usr/lib/udev/rules.d/55-dm.rules
Reading rules file: /usr/lib/udev/rules.d/55-ippusbxd.rules
Reading rules file: /usr/lib/udev/rules.d/56-hpmud.rules
Reading rules file: /usr/lib/udev/rules.d/60-autosuspend-chromiumos.rules
Reading rules file: /usr/lib/udev/rules.d/60-block.rules
Reading rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules
Reading rules file: /usr/lib/udev/rules.d/60-crda.rules
Reading rules file: /usr/lib/udev/rules.d/60-drm.rules
Reading rules file: /usr/lib/udev/rules.d/60-evdev.rules
Reading rules file: /usr/lib/udev/rules.d/60-fido-id.rules
Reading rules file: /usr/lib/udev/rules.d/60-input-id.rules
Reading rules file: /usr/lib/udev/rules.d/60-inputattach.rules
Reading rules file: /usr/lib/udev/rules.d/60-libfprint-2.rules
Reading rules file: /usr/lib/udev/rules.d/60-libgphoto2-6.rules
Reading rules file: /usr/lib/udev/rules.d/60-libsane.rules
Reading rules file: /usr/lib/udev/rules.d/60-pcmcia.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-input.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage-dm.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage.ru

[Desktop-packages] [Bug 1900334] Re: [snap] Mouse pointer theme and scaling not honoured for cursor themes not included in gtk-common-themes

2020-10-24 Thread Olivier Tilloy

As suggested in that snapcraft forum post, spotify would need to connect
to the gtk-common-themes interfaces to benefit from this fix.

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

Title:
  [snap] Mouse pointer theme and scaling not honoured for cursor themes
  not included in gtk-common-themes

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Since updating to the latest version, the mouse pointer/cursor in
  Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown
  on the desktop (or other non-snap applications).

  The symptom looks identical to that shown on this ticket:
  https://github.com/brave/browser-laptop/issues/9772

  See this gif: https://user-
  images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a-
  a1a32ff3af01.gif

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

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

[Desktop-packages] [Bug 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4

2020-10-24 Thread Daniel

** Package changed: bluez (Ubuntu) => pi-bluetooth (Ubuntu)

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

Title:
  Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on
  Raspberry Pi 4

Status in pi-bluetooth package in Ubuntu:
  New

Bug description:
  Raspberry pi 4 4Gb ram
  Ubuntu desktop 20.10 64 bit
  After reboot no Bluetooth devices connect, scanning Bluetooth devices works, 
results with same device name (duplicated and with not set up status).
  Sometimes after several reboots it works.
  If I use power off and cycle power then it works fine each time.

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

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

[Desktop-packages] [Bug 1901290] [NEW] Enchant-2 does not work properly with backends that want a NUL-terminated string

2020-10-24 Thread Timo Jyrinki

Public bug reported:

This shows up particularly with the inline checking feature of gspell in
eg gedit which is part of the default Ubuntu installation.

The issue is fixed in Enchant 2.2.12, and after that release reaches
Debian and Ubuntu hirsute, I hope a backport of this patch to https
://patch-diff.githubusercontent.com/raw/AbiWord/enchant/pull/260.patch
can be done to groovy and focal.

SRU paperwork to be added later, but in general all backends would be
good to test after the backport in various ways like gspell, sonnet,
libreoffice.

** Affects: enchant-2 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: enchant-2 (Debian)
 Importance: Unknown
 Status: Unknown

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

** Also affects: enchant-2 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969441
   Importance: Unknown
   Status: Unknown

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

Title:
  Enchant-2 does not work properly with backends that want a NUL-
  terminated string

Status in enchant-2 package in Ubuntu:
  New
Status in enchant-2 package in Debian:
  Unknown

Bug description:
  This shows up particularly with the inline checking feature of gspell
  in eg gedit which is part of the default Ubuntu installation.

  The issue is fixed in Enchant 2.2.12, and after that release reaches
  Debian and Ubuntu hirsute, I hope a backport of this patch to https
  ://patch-diff.githubusercontent.com/raw/AbiWord/enchant/pull/260.patch
  can be done to groovy and focal.

  SRU paperwork to be added later, but in general all backends would be
  good to test after the backport in various ways like gspell, sonnet,
  libreoffice.

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

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

[Desktop-packages] [Bug 1899437] Re: package libglib2.0-cil 2.12.40-3 failed to install/upgrade: installed libglib2.0-cil package post-installation script subprocess returned error exit status 1

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

** Changed in: gtk-sharp2 (Ubuntu)
   Status: New => Confirmed

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

Title:
  package libglib2.0-cil 2.12.40-3 failed to install/upgrade: installed
  libglib2.0-cil package post-installation script subprocess returned
  error exit status 1

Status in gtk-sharp2 package in Ubuntu:
  Confirmed

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-cil 2.12.40-3
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Oct 12 09:13:09 2020
  ErrorMessage: installed libglib2.0-cil package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-07-26 (809 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: gtk-sharp2
  Title: package libglib2.0-cil 2.12.40-3 failed to install/upgrade: installed 
libglib2.0-cil package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to focal on 2020-10-12 (0 days ago)

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

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

[Desktop-packages] [Bug 1901272] Re: Inconsistent Bluetooth behavior on reboot 20.10 on rpi4

2020-10-24 Thread Daniel

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

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

Title:
  Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on
  Raspberry Pi 4

Status in bluez package in Ubuntu:
  New

Bug description:
  Raspberry pi 4 4Gb ram
  Ubuntu desktop 20.10 64 bit
  After reboot no Bluetooth devices connect, scanning Bluetooth devices works, 
results with same device name (duplicated and with not set up status).
  Sometimes after several reboots it works.
  If I use power off and cycle power then it works fine each time.

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

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

[Desktop-packages] [Bug 1901272] [NEW] Inconsistent Bluetooth behavior on reboot 20.10 on rpi4