date:20200906

[Desktop-packages] [Bug 1855699] Re: Click pen icon on right side of path bar to enter custom path.

2020-09-06 Thread Clinton H

** Summary changed:

- Double click on path bar to enter custom path.
+ Click pen icon on right side of path bar to enter custom path.

** Description changed:

  1) Ubuntu 19.10
  2) 1:3.34.1-1ubuntu1
- 3) Double clicking on the path bar should allow a user to enter a custom path.
- 4) Unable to enter a custom path when double clicking on the path bar.
+ 3) Add a pen icon to the right side of the path bar. If a user clicks the pen 
icon, the path bar would become editable.
+ 4) Unable to enter a custom path.

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

Title:
  Click pen icon on right side of path bar to enter custom path.

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

Bug description:
  1) Ubuntu 19.10
  2) 1:3.34.1-1ubuntu1
  3) Add a pen icon to the right side of the path bar. If a user clicks the pen 
icon, the path bar would become editable.
  4) Unable to enter a custom path.

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

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

[Desktop-packages] [Bug 1183735] Re: By default, Onboard keyboard cannot be moved through the screen

2020-09-06 Thread Theodore R. Smith

For me, I have dual monitors and for the life of me could not get
Launchpad's Onboard keyboard to my main monitor. It was also stuck on
the top of the screen, making it a major hinderence.

Arch Linux, Gnome 3.36.

It's also the only GUI app I have ever encountered which does not
respond to the Alt + Space keyboard shortcut to display Gnome's window
menubar, which I normally use to show toolbars, etc.

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

Title:
  By default, Onboard keyboard cannot be moved through the screen

Status in One Hundred Papercuts:
  Invalid
Status in onboard package in Ubuntu:
  Invalid

Bug description:
  
  HOW TO REPRODUCE
  
  - With the default configuration, try to move Onboard through the screen.

  *
  BEHAVIOUR
  *
  - EXPECTED: The keyboard to be movable.
  - REAL: The keyboard cannot be moved.

  ***
  WORK-AROUND
  ***
  1. Click on the "Papercuts" button.
  2. Click on the "Preferences" button.
  3. Go to the "Window" tab.
  4. Mark the "Show the window's decoration" check-box.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: onboard 0.99.0~alpha1~tr1190-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
  Uname: Linux 3.8.0-21-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Fri May 24 11:34:00 2013
  InstallationDate: Installed on 2013-05-21 (2 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: onboard
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1890404] Re: prime-select needs reboot

2020-09-06 Thread Bapi Dey

How do you confirm that login-logout works before?

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

Title:
  prime-select needs reboot

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  in previous ubuntu versions (<18.4) it was posible to switch hybrid
  graphics with only logout/login, but not with 18.4+ including 20.4

  tried also with lightdm instead of gdm3, same result and more problems
  (not working fingerprint, tap2click and larger cursor)

  is it possible to select card by commandline (in grub) to avoid
  rebooting after switching?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nvidia-prime 0.8.14
  Uname: Linux 5.4.52-custom x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed Aug  5 10:23:56 2020
  Dependencies:
   
  InstallationDate: Installed on 2020-04-27 (99 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1890404] Re: prime-select needs reboot

2020-09-06 Thread frank

I only had this in 18.4 and 20.4,but had not tried older versions after
noticed it.but i remembered in any previous version reboot was not
needed.

I found a github-repo describing the difference,but had not tested it
because it is not designed to be working on 20.4.only tried lightdm,but
no difference.

https://github.com/matthieugras/Prime-Ubuntu-18.04

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

Title:
  prime-select needs reboot

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  in previous ubuntu versions (<18.4) it was posible to switch hybrid
  graphics with only logout/login, but not with 18.4+ including 20.4

  tried also with lightdm instead of gdm3, same result and more problems
  (not working fingerprint, tap2click and larger cursor)

  is it possible to select card by commandline (in grub) to avoid
  rebooting after switching?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nvidia-prime 0.8.14
  Uname: Linux 5.4.52-custom x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed Aug  5 10:23:56 2020
  Dependencies:
   
  InstallationDate: Installed on 2020-04-27 (99 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1894097] Re: Unable to switch from HSP to A2DP on BOSE blutoot headphones

2020-09-06 Thread Vonschutter

My apologies for the size of the log. This is the output for the last
boot and forward til today? I have compressed it to save space, but once
inflated its is 800 mb.

** Attachment added: "jounalctl log."

https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1894097/+attachment/5408063/+files/jounalctl.7z

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

Title:
Unable to switch from HSP to A2DP on BOSE blutoot headphones

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

Bug description:
I have a Bose NC 700 pair of headphones. The device works correctly
with Android and Windows (al be it more cumbersome and confusing in
Windows).

Device:
Firmware 1.5.1-9303+d287f23
GUID: 5c097385-cd87-d8dd-bab9-4c726a0ac560

I am available to test.

Problem 1: I am required to click on the "connect" toggle button for
the Bluetooth audio device about 20 - 30 times to make it connect.
This is also true for other speakers as for example JBL Bluetooth
speakers.

Problem 2: BOSE Headset/Gnome BT Audio configuration. I am unable to
switch between HSP/DSP mode to A2DP Sink. The device remains connected
as a communication device and not as an audio device. I remain stuck
with mono sound. Though the gnome control panel indicates that I have
indeed switched to A2DP Sink. However, when I click "test" I only get
the mono test and the sound is absolutely unusable. Because there is
a microphone on the headphones, Gnome control panel and the underlying
Bluetooth service refuse to change from HSP/DSP. Clearly this is not
by design.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.4-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 3 13:45:22 2020
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2020-08-04 (29 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
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/1894097/+subscriptions

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

[Desktop-packages] [Bug 1894432] [NEW] corrupted screen on Chrome when returning from sleep

2020-09-06 Thread david hoare

Public bug reported:

Problem just started happening within the last few days. No major system 
changes that I can think of other than some 'live-patches' being reported as 
updated...
Only appears to happen in Chrome (so maybe I should report it there?) as other 
application don't seem to display the same glitchiness.
Appears I have to stop all instances of chrome to clear it (or of course, 
restart the machine)
Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
 GCC version:
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: Sun Sep  6 08:41:51 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 440.100, 5.4.0-42-generic, x86_64: installed (WARNING! Diff between 
built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!)
 nvidia, 440.100, 5.4.0-45-generic, x86_64: installed (WARNING! Diff between 
built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!)
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. UHD Graphics [1043:150f]
   Subsystem: ASUSTeK Computer Inc. GP108BM [GeForce MX250] [1043:150f]
InstallationDate: Installed on 2020-06-17 (80 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 13d3:56cb IMC Networks USB2.0 HD IR UVC WebCam
 Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 004: ID 8087:0026 Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. ZenBook UX434FLC_UX434FL
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ac571274-cc68-46ff-b340-4ca15d7a7289 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/18/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX434FLC.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX434FLC
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX434FLC.303:bd12/18/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX434FLC_UX434FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX434FLC_UX434FL
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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

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


** Tags: amd64 apport-bug corruption focal ubuntu

** Attachment added: "example of corrupted screen display in chrome"
   
https://bugs.launchpad.net/bugs/1894432/+attachment/5408085/+files/graphics_glitch.png

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

Title:
  corrupted screen on Chrome when returning from sleep

Status in xorg package in Ubuntu:
  New

Bug description:
  Problem just started happening within the last few days. No major system 
changes that I can think of other than some 'live-patches' being reported as 
updated...
  Only appears to happen in Chrome (so maybe I should report it there?) as 
other application don't seem to di

[Desktop-packages] [Bug 1894433] [NEW] Use build flag "use_vaapi=true" for Chromium 86+

2020-09-06 Thread xalt7x

Public bug reported:

Upstream allowed to enable VAAPI through
chrome://flags/#disable-accelerated-video-decode
Commit URL:
https://chromium-review.googlesource.com/c/chromium/src/+/2208531

But Chromium still needs to be built with flag "use_vaapi=true"

Patch could be easily backported to version 85 but currently Chromium needs to 
be run with
--use-gl=desktop switch
(I have Bionic build on test PPA 
https://launchpad.net/~xalt7x/+archive/ubuntu/chromium-deb-vaapi-test-upstream)

Please use this build flag for Snap and Deb builds (16.04 , 18.04) so
people with Intel & AMD on X11 wouldn't need to rely 3rd-party PPAs for
Hardware acceleration.

Thanks!

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


** Tags: vaapi

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

Title:
  Use build flag "use_vaapi=true" for Chromium 86+

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Upstream allowed to enable VAAPI through
  chrome://flags/#disable-accelerated-video-decode
  Commit URL:
  https://chromium-review.googlesource.com/c/chromium/src/+/2208531

  But Chromium still needs to be built with flag "use_vaapi=true"

  Patch could be easily backported to version 85 but currently Chromium needs 
to be run with
  --use-gl=desktop switch
  (I have Bionic build on test PPA 
https://launchpad.net/~xalt7x/+archive/ubuntu/chromium-deb-vaapi-test-upstream)

  Please use this build flag for Snap and Deb builds (16.04 , 18.04) so
  people with Intel & AMD on X11 wouldn't need to rely 3rd-party PPAs
  for Hardware acceleration.

  Thanks!

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

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

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

2020-09-06 Thread stillnurs

Hey palls, it's Lenovo Legion Y540, and I just signed up here to suggest a 
solution for touchpad that helped for me. Since I have the similar touchpad 
types as here in the topic MSFT0001:01 04F3:309E .
I was wandering same as many of you for several days since installing Linux, 
(it's Manjaro btw, but anyways just try if you can, who knows, maybe it will 
work for you too)

So the solution for touchpad to get it working:

1/ sudo pacman -Rsn xf86-input-synaptics

2/ sudo pacman -Syu xf86-input-libinput

(create a new file if you don't have existing)
3/ /etc/X11/xorg.conf.d/30-touchpad.conf
Section "InputClass"
Identifier "MyTouchpad"
MatchIsTouchpad "on"
Driver "libinput"
Option "Tapping" "on"
EndSection

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

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

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

Bug description:
  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

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

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

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

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

2020-09-06 Thread stillnurs

update:

for the 3-step, you can edit xx-libinput.conf file if you have existing.

You will find a line which states the similar to these:

Section "InputClass"
Identifier "MyTouchpad"
MatchIsTouchpad "on"
Driver "libinput"
Option "Tapping" "on" #just add this OPTION line
EndSection

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

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

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

Bug description:
  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

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

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

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

Re: [Desktop-packages] [Bug 1887970] Re: Core dump

2020-09-06 Thread Spr Base

Helo Oliver

Could Chromium be changed back to DEB please? The snap seems slow
according to articles

https://personal.jatan.space/2020/09/05/ubuntu-snap-obsession-has-
snapped-me-off-of-it/

Thank you

On Thu, 30 Jul 2020 at 14:36, Olivier Tilloy <1887...@bugs.launchpad.net> wrote:
>
> The update to version 84 is in progress, but as I wrote earlier it's
> targetting 16.04 and 18.04 only. You may try to run the 18.04 packages
> on 20.04, but there's no guarantee it will run at all.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1887970
>
> Title:
>   Core dump
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   latest snap on Ubuntu LTS
>   ver : 84.0.4147.89
>   https://bugs.chromium.org/p/chromium/issues/detail?id=1106509#c2
>
>   Can you add debug symbols for libs? I'd be happy to provide a
>   backtrace.
>
>   note, I am running with GPU disabled!
>
>   There are various SIGTRAP, SIGSEGV core dumps I can easily reproduce
>
>   Run this 50  times
>
>   chromium-browser --no-sandbox --incognito --virtual-time-budget=5000
>   --disable-gpu --headless --print-to-pdf=a.pdf http://www.chimpazee.jp
>   >> log.log 2>&1
>
>   other sites easy to reproduce if you run it 50 times
>
>   Sri-Langka.com
>   newdress.it
>   cwalkerart.net
>
>
>   What went wrong?
>   Failed to open /dev/null
>   [0716/091926.883693:WARNING:gpu_process_host.cc(1233)] The GPU process has 
> crashed 1 time(s)
>   [0716/091926.889564:WARNING:gpu_process_host.cc(1233)] The GPU process has 
> crashed 2 time(s)
>   [0716/091926.893577:WARNING:gpu_process_host.cc(1233)] The GPU process has 
> crashed 3 time(s)
>   [0716/091926.894491:WARNING:gpu_process_host.cc(1233)] The GPU process has 
> crashed 4 time(s)
>   [0716/091926.908258:WARNING:gpu_process_host.cc(1233)] The GPU process has 
> crashed 5 time(s)
>   [0716/091926.910687:WARNING:gpu_process_host.cc(1233)] The GPU process has 
> crashed 6 time(s)
>   [0716/091926.910721:FATAL:gpu_data_manager_impl_private.cc(439)] GPU 
> process isn't usable. Goodbye.
>   Trace/breakpoint trap
>
>
>
>
>   other core dumps from this release
>
>   Chrome_IOThread_S5_1594714909.core
>   Chrome_IOThread_S5_1594716342.core
>   Chrome_IOThread_S5_1594716369.core
>   Chrome_IOThread_S5_1594716698.core
>   Chrome_IOThread_S5_1594719025.core
>   Chrome_IOThread_S5_1594719158.core
>   Chrome_IOThread_S5_1594719721.core
>   Chrome_IOThread_S5_1594720056.core
>   Chrome_IOThread_S5_1594720555.core
>   Chrome_IOThread_S5_1594720727.core
>   Chrome_IOThread_S5_1594723143.core
>   Chrome_IOThread_S5_1594723555.core
>   Chrome_IOThread_S5_1594724765.core
>   Chrome_IOThread_S5_1594726735.core
>   chrome_S5_1594713852.core
>   chrome_S5_1594714094.core
>   chrome_S5_1594715092.core
>   chrome_S5_1594715446.core
>   chrome_S5_1594716376.core
>   chrome_S5_1594717583.core
>   chrome_S5_1594718113.core
>   chrome_S5_1594719128.core
>   chrome_S5_1594719384.core
>   chrome_S5_1594721440.core
>   chrome_S5_1594721535.core
>   chrome_S5_1594722795.core
>   chrome_S5_1594722978.core
>   chrome_S5_1594723249.core
>   chrome_S5_1594724206.core
>   chrome_S5_1594724258.core
>   chrome_S5_1594724538.core
>   chrome_S5_1594724988.core
>   chrome_S5_1594725002.core
>   chrome_S5_1594726378.core
>   chrome_S6_1594713950.core
>   chrome_S6_1594714908.core
>   chrome_S6_1594716342.core
>   chrome_S6_1594716368.core
>   chrome_S6_1594716697.core
>   chrome_S6_1594717712.core
>   chrome_S6_1594719024.core
>   chrome_S6_1594719157.core
>   chrome_S6_1594719720.core
>   chrome_S6_1594720055.core
>   chrome_S6_1594720554.core
>   chrome_S6_1594720726.core
>   chrome_S6_1594720810.core
>   chrome_S6_1594721013.core
>   chrome_S6_1594722356.core
>   chrome_S6_1594723142.core
>   chrome_S6_1594723554.core
>   chrome_S6_1594724764.core
>   chrome_S6_1594726734.core
>   ThreadPoolForeg_S5_1594714202.core
>   ThreadPoolForeg_S5_1594714760.core
>   ThreadPoolForeg_S5_1594717626.core
>   ThreadPoolForeg_S5_1594720170.core
>   ThreadPoolForeg_S5_1594721977.core
>   ThreadPoolForeg_S5_1594724067.core
>   ThreadPoolForeg_S5_1594726574.core
>   ThreadPoolServi_S5_1594714496.core
>   ThreadPoolServi_S5_1594718153.core
>   ThreadPoolServi_S5_1594718433.core
>   ThreadPoolServi_S5_1594718656.core
>   ThreadPoolServi_S5_1594721429.core
>   ThreadPoolServi_S5_1594721635.core
>   ThreadPoolServi_S5_1594721840.core
>   ThreadPoolServi_S5_1594723905.core
>   ThreadPoolServi_S5_1594726588.core
>   ThreadPoolServi_S5_1594726621.core
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887970/+subscriptions

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

Title:
  Core dump

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  latest snap on Ub

[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card

2020-09-06 Thread mohammad hossein

I have this problem on kubuntu 18.04 and ubuntu,kubuntu 20.04
dell inspiron 5110n
nvidia gt525m 
nvidia driver-390

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

Title:
  prime-select intel is not powering off the nvidia card

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Right now, it seems that prime-select intel makes sure the nvidia driver is 
not loaded, as nvidia-settings reports.
  But my power consumption is > 20W.
  cat /proc/acpi/bbswitch reports the card is still on. 

  
  If bbswitch and powertop are reliable, then the nvidia card is still powered.
  This is a thinkpad w520 in Optimus mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-prime 0.8.7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 19:56:21 2018
  Dependencies:
   
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-12-14 (125 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago)

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

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

[Desktop-packages] [Bug 1894437] [NEW] Nautilus does not release memory

2020-09-06 Thread fcole90

Public bug reported:

I copied a large amount of files, viewed many thumbnails and done other
activities which may possibly require allocating more memory in the
system. I reached 6.6GB of memory. Then I closed all nautilus windows,
but the memory usage didn't lower.

I would have expected that after closing all nautilus windows it would
have reduced to normal levels, but it didn't. I don't think this is
normal.

Memory usage was checked on gnome-system-monitor.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
Uname: Linux 5.4.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Sun Sep  6 18:28:50 2020
InstallationDate: Installed on 2020-04-03 (155 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T09:26:46.106768
usr_lib_nautilus:

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

Title:
  Nautilus does not release memory

Status in nautilus package in Ubuntu:
  New

Bug description:
  I copied a large amount of files, viewed many thumbnails and done
  other activities which may possibly require allocating more memory in
  the system. I reached 6.6GB of memory. Then I closed all nautilus
  windows, but the memory usage didn't lower.

  I would have expected that after closing all nautilus windows it would
  have reduced to normal levels, but it didn't. I don't think this is
  normal.

  Memory usage was checked on gnome-system-monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Sep  6 18:28:50 2020
  InstallationDate: Installed on 2020-04-03 (155 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T09:26:46.106768
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1894433] Re: Use build flag "use_vaapi=true" for Chromium 86+

2020-09-06 Thread Launchpad Bug Tracker

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

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

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

Title:
  Use build flag "use_vaapi=true" for Chromium 86+

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Upstream allowed to enable VAAPI through
  chrome://flags/#disable-accelerated-video-decode
  Commit URL:
  https://chromium-review.googlesource.com/c/chromium/src/+/2208531

  But Chromium still needs to be built with flag "use_vaapi=true"

  Patch could be easily backported to version 85 but currently Chromium needs 
to be run with
  --use-gl=desktop switch
  (I have Bionic build on test PPA 
https://launchpad.net/~xalt7x/+archive/ubuntu/chromium-deb-vaapi-test-upstream)

  Please use this build flag for Snap and Deb builds (16.04 , 18.04) so
  people with Intel & AMD on X11 wouldn't need to rely 3rd-party PPAs
  for Hardware acceleration.

  Thanks!

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

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

[Desktop-packages] [Bug 1872180] Re: Network printer does not print: cups-browsed

2020-09-06 Thread Launchpad Bug Tracker

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

** Changed in: cups-filters (Ubuntu)
   Status: New => Confirmed

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

Title:
  Network printer does not print: cups-browsed

Status in cups-filters package in Ubuntu:
  Confirmed

Bug description:
  On a new installed Ubuntu 20.04 daily, network printer is found but when file 
sent to print, job is blocked on print queue. Looking at the setting of the 
printer found message that maybe cups-browsed is not running. 
  And, so found workaround to start it and prints finished successfully. 
  I don't know if there is a way to make it automatic and handled transparently 
for Ubuntu user?  

  Printer model HP DeskJet 3700

  Thank you, 
  Igor

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups-browsed 1.27.3-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 11 12:13:22 2020
  InstallationDate: Installed on 2020-04-01 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  Lpstat: device for HP_DeskJet_3700_series_6DEB51_: 
implicitclass://HP_DeskJet_3700_series_6DEB51_/
  MachineType: LENOVO 20QTCTO1WW
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_DeskJet_3700_series_6DEB51_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP_DeskJet_3700_series_6DEB51_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7
  SourcePackage: cups-filters
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET42W (1.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QTCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1 Gen 2
  dmi.product.name: 20QTCTO1WW
  dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2
  dmi.product.version: ThinkPad P1 Gen 2
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1894441] [NEW] nvidia 7050 glitch on Nouveau and Xubuntu 20.04

2020-09-06 Thread Michel-Ekimia

Public bug reported:

nvidia 7050 glitch on Nouveau and Xubuntu 20.04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-video-nouveau 1:1.0.16-1
ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
Uname: Linux 5.4.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Sun Sep  6 19:02:23 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation C73 [GeForce 7050 / nForce 610i] [10de:07e3] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: Packard Bell B.V. C73 [GeForce 7050 / nForce 610i] [1631:e038]
InstallationDate: Installed on 2020-09-06 (0 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 001 Device 002: ID 0846:4260 NetGear, Inc. WG111v3 54 Mbps Wireless 
[realtek RTL8187B]
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/8p, 12M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M
 |__ Port 3: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtl8187, 480M
MachineType: Packard Bell BV IMEDIA D9378 AIO
ProcEnviron:
 LANGUAGE=fr_FR
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=b807077b-46c6-4253-9a39-2be7f9e84214 ro quiet splash
SourcePackage: xserver-xorg-video-nouveau
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/08/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: PBDV10.P17
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MCP73VT-PM
dmi.board.vendor: Packard Bell BV
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Packard Bell BV
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrPBDV10.P17:bd04/08/2008:svnPackardBellBV:pnIMEDIAD9378AIO:pvrPB80139602:rvnPackardBellBV:rnMCP73VT-PM:rvr1.0:cvnPackardBellBV:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: IMEDIA D9378 AIO
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: PB80139602
dmi.sys.vendor: Packard Bell BV
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.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

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  nvidia 7050 glitch on Nouveau and Xubuntu 20.04

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

Bug description:
  nvidia 7050 glitch on Nouveau and Xubuntu 20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sun Sep  6 19:02:23 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C73 [GeForce 7050 / nForce 610i] [10de:07e3] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Packard Bell B.V. C73 [GeForce 7050 / nForce 610i] [1631:e038]
  InstallationDate: Installed on 2020-09-06 (0 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 001 Device 002: ID 0846:4260 NetGear, Inc. WG111v3 54 Mbps Wireless 
[realtek RTL8187B]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/8p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M
   |__ Port 3: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtl8187, 
480M
  MachineType: Packard Bell BV IMEDIA D9378 AIO
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=b807077b-46c6-4253-9a39-2be7f9e84214 ro quiet

[Desktop-packages] [Bug 112518] Re: Switch User freezes at blank screen

2020-09-06 Thread Sam Shiell

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

I have this exact bugg on Kubuntu 20.4 LTS.

It's not the same as #160264 as (like other people here) I get a black
screen, not a white one.

No response from any Fn+Fx keys, only fix is a hard boot.

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

Title:
  Switch User freezes at blank screen

Status in compiz package in Ubuntu:
  Invalid
Status in gdm package in Ubuntu:
  Invalid
Status in linux-restricted-modules-2.6.20 package in Ubuntu:
  Won't Fix
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  The system seems to freeze at a blank screen and is not responsive to
  any input after switching users then logging out.

  Steps to reproduce
  1. Login user A
  2. Switch user, Login user B
  3. Either log out user B or switch user again

  Then the screen is just frozen at a black screen and does not respond
  to any input.

  Distro Release: Feisty Fawn 7.04

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

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

[Desktop-packages] [Bug 1894449] [NEW] Screencast software doesn't work in Wayland mode

2020-09-06 Thread Lyubomir

Public bug reported:

I've tried Kazam, SimpleScreenRecorder and vokoscreenNG and none work.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55
Uname: Linux 5.4.0-45-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep  7 00:11:08 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-02-08 (211 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-04-20 (139 days ago)
mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742

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


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

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

Title:
  Screencast software doesn't work in Wayland mode

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I've tried Kazam, SimpleScreenRecorder and vokoscreenNG and none work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55
  Uname: Linux 5.4.0-45-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  7 00:11:08 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-02-08 (211 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-20 (139 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742

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

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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

2020-09-06 Thread sean

Most of us have tryed h264ify it dose not help the issue seem to be with
the build

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  News :

  - Candidate Chromium 83 Snap with vaapi enabled can be installed with
  :

  sudo snap install --channel=candidate/vaapi chromium

  Check that your vidéo is gpu decoded but checking "MojoVideoDecoder"
  in about:media-internals

  Widevine DRM streams will have DecryptingVideoDecoder

  Please report success/failure with

  - distro version
  - GPU Hardware used
  - Codec used

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

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

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

[Desktop-packages] [Bug 1894452] [NEW] shutdown delay because of cups

2020-09-06 Thread Cliff Carson

Public bug reported:

Both my desktop and laptop running 20.10 have a 90 second delay shutting
down (power off or restart).  Getting message;

A stop job is Running for Make remote CUPS printers available locally

After 90 seconds the shutdown continues to completion.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: cups 2.3.3-2ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Sun Sep  6 18:10:20 2020
InstallationDate: Installed on 2020-08-28 (9 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
KernLog:
 
Lpstat: device for ENVY_4500: hp:/net/ENVY_4500_series?ip=192.168.1.131
MachineType: CLEVO CO. W35_37ET
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/ENVY_4500.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/ENVY_4500.ppd: Permission denied
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: W35_37ET
dmi.board.vendor: CLEVO CO.
dmi.board.version: N/A
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 9
dmi.chassis.vendor: CLEVO CO.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: W35_37ET
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: N/A
dmi.sys.vendor: CLEVO CO.

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

Title:
  shutdown delay because of cups

Status in cups package in Ubuntu:
  New

Bug description:
  Both my desktop and laptop running 20.10 have a 90 second delay
  shutting down (power off or restart).  Getting message;

  A stop job is Running for Make remote CUPS printers available locally

  After 90 seconds the shutdown continues to completion.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: cups 2.3.3-2ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Sun Sep  6 18:10:20 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  KernLog:
   
  Lpstat: device for ENVY_4500: hp:/net/ENVY_4500_series?ip=192.168.1.131
  MachineType: CLEVO CO. W35_37ET
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/ENVY_4500.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/ENVY_4500.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

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

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

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

2020-09-06 Thread Murat Gokmen

Public bug reported:

Ubuntu 20.04 freezes randomly

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.capabilities.gpu0: Error: [Errno 21] Bir dizin: 
'/proc/driver/nvidia/capabilities/gpu0'
.proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Bir dizin: 
'/proc/driver/nvidia/capabilities/mig'
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Bir dizin: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.66  Wed Aug 12 19:42:48 
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] Erişim engellendi: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep  7 01:22:46 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 450.66, 5.4.0-45-generic, x86_64: installed
 virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed
 virtualbox, 6.1.10, 5.4.0-45-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
 NVIDIA Corporation GM107GL [Quadro K620] [10de:13bb] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: NVIDIA Corporation GM107GL [Quadro K620] [10de:1098]
InstallationDate: Installed on 2020-04-26 (133 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Dell Inc. Precision Tower 3620
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=tr_TR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=5abcce6c-0eb6-4ef4-bf1b-0a62c2924a2d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.15.0
dmi.board.name: 0MWYPT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.15.0:bd03/25/2020:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn0MWYPT:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.family: Precision
dmi.product.name: Precision Tower 3620
dmi.product.sku: 06B7
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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

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


** Tags: amd64 apport-bug focal freeze possible-manual-nvidia-install 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/1894454

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 freezes randomly

  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.capabilities.gpu0: Error: [Errno 21] Bir dizin: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Bir dizin: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Bir dizin: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.66  Wed Aug 12 19:42:48 
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] Erişim engellendi: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  7 01:22:46 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  Dist

[Desktop-packages] [Bug 1805077] Re: [ASUS X555YI] the audio pause and repeat for a very short of time randomly

2020-09-06 Thread Abdulrhman

I am a new Linux user, and I face the same problem in Ubuntu 20.04
A short (about a second or less) repeated sound occurs at random times, in the 
browser, in VLC or even the system sounds, and it's actually annoying.
I tried Fedora 32 but the same issue there but less likely to happens, and I 
tried OpenSUSE Leap 15.2 and it never happened.
My search led me to an Arch article explaining the situation:
"The newer implementation of the PulseAudio sound server uses timer-based audio 
scheduling instead of the traditional, interrupt-driven approach.
Timer-based scheduling may expose issues in some ALSA drivers. On the other 
hand, other drivers might be glitchy without it on, so check to see what works 
on your system."
See 
https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches,_skips_or_crackling
I tried the proposed solutions but it Don't work.

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

Title:
  [ASUS X555YI] the audio pause and repeat for a very short of time
  randomly

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  the audio pause and repeat for a very short of time randomly
  when I use web browser to play music and use smplayer play video this bug 
happens randomly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  widon 13716 F pulseaudio
   /dev/snd/controlC0:  widon 13716 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-24 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555YI.510
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555YI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555YI
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1805077] Re: [ASUS X555YI] the audio pause and repeat for a very short of time randomly

2020-09-06 Thread Launchpad Bug Tracker

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

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

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

Title:
  [ASUS X555YI] the audio pause and repeat for a very short of time
  randomly

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  the audio pause and repeat for a very short of time randomly
  when I use web browser to play music and use smplayer play video this bug 
happens randomly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  widon 13716 F pulseaudio
   /dev/snd/controlC0:  widon 13716 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-24 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555YI.510
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555YI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555YI
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

73 matches

Mail list logo