[Desktop-packages] [Bug 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu

[Igor A Tarasov]

Do not remove PPTP. Just dont't use it for yourself. But I have no
choises.

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

Title:
  RM: Remove dangerously insecure MPPE PPTP from Ubuntu

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in network-manager-pptp package in Ubuntu:
  New
Status in pptp-linux package in Ubuntu:
  New
Status in pptpd package in Ubuntu:
  Fix Released

Bug description:
  Remove dangerously insecure MPPE PPTP from Ubuntu

  https://pptpclient.sourceforge.net/protocol-security.phtml

  It has been dead for over 20 years now.

  Current Windows versions natively support IPSec and L2TP as much
  better alternatives.

  https://learn.microsoft.com/en-us/windows/win32/fwp/ipsec-
  configuration#how-to-use-wfp-to-configure-ipsec-policies

  https://learn.microsoft.com/en-US/troubleshoot/windows-
  server/networking/configure-l2tp-ipsec-server-behind-nat-t-device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2041751/+subscriptions


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

[Desktop-packages] [Bug 1992306] Re: Default to a2dp ldac_hq codec for bluethooth headset and sound distorted

[Igor]

I have a similar problem here. After recent Ubuntu updates, I restarted
my computer. The audio on the WF-1000XM4 started stuttering.

Reinstalled Bluez and PulseAudio. In the PulseAudio GUI there is a tab
called Configuration. It constantly defaults codec LDAC (High Quality).
When I reset it manually to LDAC (Mobile Quality) the sound is ok. After
the next disconnect, the issue returns, and I solve it temporarily by
changing the codec again. "Lock card to this profile" icon does not
prevent it from resetting to LDAC (High Quality) again.

The issue does not involve a Bluetooth mouse, the problem is encountered
with and without connection to one.

ASUSTeK COMPUTER INC. ZenBook UX393EA_UX393EA

Ubuntu 22.04.2 LTS

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 13d3:56cb IMC Networks USB2.0 HD IR UVC WebCam
Bus 003 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.01
  bDeviceClass  224 Wireless
  bDeviceSubClass 1 Radio Frequency
  bDeviceProtocol 1 Bluetooth
  bMaxPacketSize064
  idVendor   0x8087 Intel Corp.
  idProduct  0x0026 AX201 Bluetooth
  bcdDevice0.02
  iManufacturer   0 
  iProduct0 
  iSerial 0 
  bNumConfigurations  1

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

Title:
  Default to a2dp ldac_hq codec for bluethooth headset and sound
  distorted

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I had some trouble getting my bluetooth headphones to work and I
  believe the culprit is the default codec that pulseaudio chooses. It
  appears to work ok when having no other Bluetooth devices connected,
  but when connecting a bluetooth mouse the audio gets distorted and
  begins to stutter. The offending codec is ldac_hq. I did some
  investigating today and found out you can change the codec in
  pavucontrol. Selecting ldac_sq seems to work without any issue.

  I don't know what the problem with ldac_hq is, maybe bandwidth? Wasn't
  able to find any obvious problems in the logs, even when enabling
  debugging in bluez.

  While investigating this I noticed others having the same issue, and
  it was difficult to find a way to change the codec, so maybe ldac_hq
  shouldn't be chosen as default?

  Headphones: Sony WF-1000XM
  Mouse: Logitech M590
  Computer: 
https://www.asus.com/Laptops/For-Home/Zenbook/Zenbook-S-UX391/techspec/

  $ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 27c6:5201 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
  Bus 001 Device 002: ID 13d3:56b9 IMC Networks USB2.0 HD UVC WebCam
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  description: Bluetooth wireless interface
 product: Bluetooth wireless interface
 vendor: Intel Corp.
 physical id: 8
 bus info: usb@1:8
 version: 0.10
 capabilities: bluetooth usb-2.00
 configuration: driver=btusb maxpower=100mA speed=12Mbit/s

  Ubuntu 22.04.1 LTS
  pulseaudio: 1:15.99.1+dfsg1-1ubuntu1
  bluez: 5.64-0ubuntu1
  pavucontrol: 5.0-2

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


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

[Desktop-packages] [Bug 1980831] Re: GUI freezes randomly, mouse still moving, nothing else works

[Igor Kobzev]

Have you tried just pressing the Super ('Windows') key to get into the
Activities overview? I've had this bug ever since I started using Gnome:
in Ubuntu 20.04, in PopOS, in Manjaro, in Fedora. The Super key trick
works every time. It'd still be nice to fix the underlying issue,
though.

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

Title:
  GUI freezes randomly, mouse still moving, nothing else works

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When working normally, random freezes happen. Everything freezes,
  except the mouse cursor.

  I tried from keyboard to: switch to another window, start a terminal,
  run a command to restart gnome, enabled ctrl+alt+backspace and tried
  it to restart X windows, ctrl+alt+delete, switch to another session
  with ctrl+alt+F1-F9 - nothing works.

  If I'm listening to something, the sound goes on for a while;
  sometimes it stops by itself, other times it keeps going.

  The only way to recover that I've found is to stop the laptop from the
  power button.

  For a while I thought it was due to firefox; I installed the deb
  version and then switched to chrome - same behavior.

  It didn't happen when I was playing Hollow Knight in Steam, or when
  I've used the terminal and nothing else.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  6 14:27:36 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-06-16 (19 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1875369] Re: recording device won't change

[Igor V. Kovalenko]

This is a believed to be an application issue
https://webcompat.com/issues/53808

** Bug watch added: webcompat.com/issues #53808
   https://webcompat.com/issues/53808

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

Title:
  recording device won't change

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  installed from lubuntu .iso
  fully updated as of yesterday
  fresh boot this morning

  some of these details are most likely irrelevant, but it's what i do to keep 
things simple:
  ignore graphical login screen, change to VT2
  startx /usr/bin/xterm

  in the xterm:
  /opt/firefox/firefox&  #(nightly)
  openbox&
  pavucontrol-qt&
  pavucontrol&#results are the same regardless which of the pavucontrols is 
invoked

  in firefox:
  voice.google.com
  start a call

  in either of the pavucontrols:
  try to change the recording device:
  the menu opens, select the desired device, but it just doesn't change.
  doesn't matter which of the two pavucontrols was invoked

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Apr 27 07:49:12 2020
  InstallationDate: Installed on 2020-03-15 (42 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314)
  ProcEnviron:
   LC_TIME=en_DK.utf8
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/20/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ETA2WW (2.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C6008SUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C6008SUS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6008SUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Edge E540
  dmi.product.name: 20C6008SUS
  dmi.product.sku: LENOVO_MT_20C6_BU_Think_FM_ThinkPad Edge E540
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO

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


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

[Desktop-packages] [Bug 1969304] [NEW] can't switch to Wayland

[IGOR GOROKHIVSKYI]

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

Public bug reported:

I downloaded the next updates, then restarted the computer to install.
The installation crashed, after which I rebooted the computer again.
When logging in, there was no longer a menu to switch from X server to
wayland

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 17 17:25:41 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-03-24 (23 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  can't switch to Wayland

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I downloaded the next updates, then restarted the computer to install.
  The installation crashed, after which I rebooted the computer again.
  When logging in, there was no longer a menu to switch from X server to
  wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 17 17:25:41 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-24 (23 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1960307] Re: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices

[Igor V. Kovalenko]

Changing codec via gnome-control-center would probably need a feature
request to gnome-control-center to support new functionality in
>=pulseaudio-15.0

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

Title:
  No gstreamer dependency causes high-fidelity codecs to be missing for
  Bluetooth devices

Status in PulseAudio:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Confirmed
Status in gstreamer1.0 package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After the announcements of PulseAudio 15 and Gstreamer 1.20, which
  both advertised LDAC and AptX (HD) support, I expected that jammy
  (22.04) would support those codecs.

  Though in reality it seems that something is missing, gstreamer
  reports that those codecs are supported but "pactl [...] list-codec"
  only lists sbc (and variants).

  Checking here https://packages.ubuntu.com/jammy/pulseaudio-module-
  bluetooth it seems that PulseAudio is not built with gstreamer
  support, is that the current blocker?

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


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

[Desktop-packages] [Bug 1960307] Re: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices

[Igor V. Kovalenko]

Whether your headset cannot be switched from HFP to A2DP is a separate
issue anyway. You can try pairing and trusting the device again, also
please check if you have pipewire audio enabled which could seldom take
over bluetooth a2dp, and see if bluetoothd log has anything related.

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

Title:
  No gstreamer dependency causes high-fidelity codecs to be missing for
  Bluetooth devices

Status in PulseAudio:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Confirmed
Status in gstreamer1.0 package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After the announcements of PulseAudio 15 and Gstreamer 1.20, which
  both advertised LDAC and AptX (HD) support, I expected that jammy
  (22.04) would support those codecs.

  Though in reality it seems that something is missing, gstreamer
  reports that those codecs are supported but "pactl [...] list-codec"
  only lists sbc (and variants).

  Checking here https://packages.ubuntu.com/jammy/pulseaudio-module-
  bluetooth it seems that PulseAudio is not built with gstreamer
  support, is that the current blocker?

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


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

[Desktop-packages] [Bug 1960307] Re: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices

[Igor V. Kovalenko]

It's in the 15.0 release notes,
https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/15.0/#supportforldacandaptxbluetoothcodecsplussbcxqsbcwithhigher-
qualityparameters

  pactl send-message /card/bluez_card.XX_XX_XX_XX_XX_XX/bluez list-
codecs

You should also be able to find codec selection in pavucontrol
'Configuration' tab if pavucontrol is built correctly.

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

Title:
  No gstreamer dependency causes high-fidelity codecs to be missing for
  Bluetooth devices

Status in PulseAudio:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Confirmed
Status in gstreamer1.0 package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After the announcements of PulseAudio 15 and Gstreamer 1.20, which
  both advertised LDAC and AptX (HD) support, I expected that jammy
  (22.04) would support those codecs.

  Though in reality it seems that something is missing, gstreamer
  reports that those codecs are supported but "pactl [...] list-codec"
  only lists sbc (and variants).

  Checking here https://packages.ubuntu.com/jammy/pulseaudio-module-
  bluetooth it seems that PulseAudio is not built with gstreamer
  support, is that the current blocker?

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


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

[Desktop-packages] [Bug 1964579] Re: Pulseaudio fails to detect /enable Intel SST sound card

[Igor V. Kovalenko]

Almost positive this is due to pipewire audio part is running, see alsa
info:

PipeWire:
  Installed - Yes (/usr/bin/pipewire)
  Running - Yes

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

Title:
  Pulseaudio fails to detect /enable Intel SST sound card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Testing Live session and also full install  Ubuntu Mate Jammy daily
  ISO 11-03-2022

  The machine tested - AEROFARA Aero2 Pro, N5105,8GB,Ethernet
  GB,WiFi,Bluetooth 4.0,128GB SSD,Intel UHD Graphics

  The audio card is not detected - entering sound preferences settings -
  "output" only shows

  dummy output stereo - under "hardware" is no entry available

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: pass
  CasperVersion: 1.467
  CurrentDesktop: MATE
  Date: Fri Mar 11 09:25:31 2022
  LiveMediaBuild: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220311)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_Jack: Digital Out, HDMI
  Title: [AERO 2 Pro, Intel Jasperlake HDMI, Digital Out, HDMI] Pulseaudio 
fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: JB1006
  dmi.board.asset.tag: Default string
  dmi.board.name: AERO 2 Pro
  dmi.board.vendor: Shenzhen Wangang Technology Co., Ltd
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 0.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrJB1006:bd12/13/2021:br5.19:efr0.7:svnShenzhenWangangTechnologyCo.,Ltd:pnAERO2Pro:pvrDefaultstring:rvnShenzhenWangangTechnologyCo.,Ltd:rnAERO2Pro:rvrDefaultstring:cvnDefaultstring:ct35:cvrDefaultstring:skuAERO2Pro:
  dmi.product.family: Windows 10 Pro
  dmi.product.name: AERO 2 Pro
  dmi.product.sku: AERO 2 Pro
  dmi.product.version: Default string
  dmi.sys.vendor: Shenzhen Wangang Technology Co., Ltd

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


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

[Desktop-packages] [Bug 1962019] [NEW] [850XBD, Realtek ALC256, Black Headphone Out, Right] Background noise or low volume

[Igor Pontes Tresolavy]

Public bug reported:

Laptop's (Samsung Odyssey) speaker works fine, but headphone presents
incredibly low volume and buzzing/crackling noise only when sound is
being played

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ipontes3olavy   1497 F pulseaudio
 /dev/snd/pcmC0D0p:   ipontes3olavy   1497 F...m pulseaudio
 /dev/snd/controlC1:  ipontes3olavy   1497 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 23 12:37:47 2022
InstallationDate: Installed on 2022-02-22 (0 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Right
Symptom_Type: High background noise, or volume is too low
Title: [850XBD, Realtek ALC256, Black Headphone Out, Right] Background noise or 
low volume
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/19/2021
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P03AHZ.009.210719.JJ
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP850XBD-XG2BR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGLA185A0K-C01-G001-S0001+10.0.18362
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP03AHZ.009.210719.JJ:bd07/19/2021:br5.13:svnSAMSUNGELECTRONICSCO.,LTD.:pn850XBD:pvrP03AHZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP850XBD-XG2BR:rvrSGLA185A0K-C01-G001-S0001+10.0.18362:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PAHZ:
dmi.product.family: Odyssey Series
dmi.product.name: 850XBD
dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHZ
dmi.product.version: P03AHZ
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

Title:
  [850XBD, Realtek ALC256, Black Headphone Out, Right] Background noise
  or low volume

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Laptop's (Samsung Odyssey) speaker works fine, but headphone presents
  incredibly low volume and buzzing/crackling noise only when sound is
  being played

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ipontes3olavy   1497 F pulseaudio
   /dev/snd/pcmC0D0p:   ipontes3olavy   1497 F...m pulseaudio
   /dev/snd/controlC1:  ipontes3olavy   1497 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 23 12:37:47 2022
  InstallationDate: Installed on 2022-02-22 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_Type: High background noise, or volume is too low
  Title: [850XBD, Realtek ALC256, Black Headphone Out, Right] Background noise 
or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P03AHZ.009.210719.JJ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP850XBD-XG2BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLA185A0K-C01-G001-S0001+10.0.18362
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP03AHZ.009.210719.JJ:bd07/19/2021:br5.13:svnSAMSUNGELECTRONICSCO.,LTD.:pn850XBD:pvrP03AHZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP850XBD-XG2BR:rvrSGLA185A0K-C01-G001-S0001+10.0.18362:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PAHZ:
  dmi.product.family: Odyssey Series
  dmi.product.name: 850XBD
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHZ
  dmi.product.version: P03AHZ
  

[Desktop-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot

[Igor V. Kovalenko]

Corrado, this is still not ideal - while it appears to work at the
moment, having two audio servers with their own idea of volumes would
probably cause trouble going on.

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

Title:
  In Jammy sound level reset after reboot

Status in alsa-utils package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After reboot sound level is reset ignoring the level set in previous
  session.

  I manually set the sound output level 
  at next boot the sound is set at a different level (about 70%)

  Expected: the sound level is persistent across power off/on

  What happens : sound level is set at a different level (about 70%)

  Note: this problem does not occur on different partitions of same PC
  running Ubuntu 20.04 or 21.10

  corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p3-jj-1130:~$ inxi -Fx
  System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 
compiler: gcc v: 11.2.0
 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 

 Mobo: Dell model: 0C1PF2 v: A00 serial:  UEFI: 
Dell v: 1.5.0 date: 12/17/2019
  Battery:   ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) 
volts: 11.3 min: 11.4
 model: SWD-ATL3.618 DELL WJPC403 status: Discharging
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 cache:
 L2: 6 MiB
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046
 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 
710 3: 706 4: 714 5: 966 6: 712
 7: 724 8: 821
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus-ID: 00:02.0
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus-ID: 1-6:3
 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell 
driver: loaded: i915
 note: n/a (using device driver) resolution: 1920x1080~60Hz
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
21.2.2 direct render: Yes
  Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel
 bus-ID: 00:1f.3
 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes
 Sound Server-2: PulseAudio v: 15.0 running: yes
 Sound Server-3: PipeWire v: 0.3.40 running: yes
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000
 bus-ID: 01:00.0
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci
 v: kernel bus-ID: 02:00.0
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9
  Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 
1-10:4
 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: 
enabled,running rfk-block: hardware: no
 software: yes address: D8:12:65:B8:21:BA
  Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%)
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB temp: 24.9 C
 ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 
GiB
  Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: 
/dev/nvme0n1p3
 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  Alert: No swap data was found.
  Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A
 Fan Speeds (RPM): cpu: 0
  Info:  Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) 
Init: systemd runlevel: 5 Compilers:
 gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07
  corrado@corrado-p3-jj-1130:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-11-30 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  Package: gnome-control-center 1:41.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Tags:  wayland-session jammy
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade 

[Desktop-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot

[Igor V. Kovalenko]

OK that matches what we have observed elsewhere. In theory there is an
audio device reservation protocol which is obeyed by both pulseaudio and
pipewire, but in practice it looks like at least some versions of
pipewire media server component do not obey the protocol in full (i.e.
are still using control device) I cannot think of any other reason why
both pulseaudio and pipewire are using the same control device.

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

Title:
  In Jammy sound level reset after reboot

Status in alsa-utils package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After reboot sound level is reset ignoring the level set in previous
  session.

  I manually set the sound output level 
  at next boot the sound is set at a different level (about 70%)

  Expected: the sound level is persistent across power off/on

  What happens : sound level is set at a different level (about 70%)

  Note: this problem does not occur on different partitions of same PC
  running Ubuntu 20.04 or 21.10

  corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p3-jj-1130:~$ inxi -Fx
  System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 
compiler: gcc v: 11.2.0
 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 

 Mobo: Dell model: 0C1PF2 v: A00 serial:  UEFI: 
Dell v: 1.5.0 date: 12/17/2019
  Battery:   ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) 
volts: 11.3 min: 11.4
 model: SWD-ATL3.618 DELL WJPC403 status: Discharging
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 cache:
 L2: 6 MiB
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046
 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 
710 3: 706 4: 714 5: 966 6: 712
 7: 724 8: 821
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus-ID: 00:02.0
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus-ID: 1-6:3
 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell 
driver: loaded: i915
 note: n/a (using device driver) resolution: 1920x1080~60Hz
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
21.2.2 direct render: Yes
  Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel
 bus-ID: 00:1f.3
 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes
 Sound Server-2: PulseAudio v: 15.0 running: yes
 Sound Server-3: PipeWire v: 0.3.40 running: yes
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000
 bus-ID: 01:00.0
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci
 v: kernel bus-ID: 02:00.0
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9
  Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 
1-10:4
 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: 
enabled,running rfk-block: hardware: no
 software: yes address: D8:12:65:B8:21:BA
  Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%)
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB temp: 24.9 C
 ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 
GiB
  Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: 
/dev/nvme0n1p3
 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  Alert: No swap data was found.
  Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A
 Fan Speeds (RPM): cpu: 0
  Info:  Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) 
Init: systemd runlevel: 5 Compilers:
 gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07
  corrado@corrado-p3-jj-1130:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-11-30 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 

[Desktop-packages] [Bug 1961477] [NEW] software-properties-gtk not running

[Igor Golov]

Public bug reported:

When I try to run the program from Ubuntu nothing happens. An error
occurs when trying to run the program from the console. Attempts to roll
back the version were unsuccessful.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: software-properties-gtk 0.99.9.8
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 19 15:33:18 2022
InstallationDate: Installed on 2022-01-10 (39 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  software-properties-gtk not running

Status in software-properties package in Ubuntu:
  New

Bug description:
  When I try to run the program from Ubuntu nothing happens. An error
  occurs when trying to run the program from the console. Attempts to
  roll back the version were unsuccessful.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.99.9.8
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 19 15:33:18 2022
  InstallationDate: Installed on 2022-01-10 (39 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot

[Igor V. Kovalenko]

Please have a look which apps are using audio devices: 'lsof /dev/snd/*

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

Title:
  In Jammy sound level reset after reboot

Status in alsa-utils package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After reboot sound level is reset ignoring the level set in previous
  session.

  I manually set the sound output level 
  at next boot the sound is set at a different level (about 70%)

  Expected: the sound level is persistent across power off/on

  What happens : sound level is set at a different level (about 70%)

  Note: this problem does not occur on different partitions of same PC
  running Ubuntu 20.04 or 21.10

  corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p3-jj-1130:~$ inxi -Fx
  System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 
compiler: gcc v: 11.2.0
 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 

 Mobo: Dell model: 0C1PF2 v: A00 serial:  UEFI: 
Dell v: 1.5.0 date: 12/17/2019
  Battery:   ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) 
volts: 11.3 min: 11.4
 model: SWD-ATL3.618 DELL WJPC403 status: Discharging
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 cache:
 L2: 6 MiB
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046
 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 
710 3: 706 4: 714 5: 966 6: 712
 7: 724 8: 821
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus-ID: 00:02.0
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus-ID: 1-6:3
 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell 
driver: loaded: i915
 note: n/a (using device driver) resolution: 1920x1080~60Hz
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
21.2.2 direct render: Yes
  Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel
 bus-ID: 00:1f.3
 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes
 Sound Server-2: PulseAudio v: 15.0 running: yes
 Sound Server-3: PipeWire v: 0.3.40 running: yes
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000
 bus-ID: 01:00.0
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci
 v: kernel bus-ID: 02:00.0
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9
  Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 
1-10:4
 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: 
enabled,running rfk-block: hardware: no
 software: yes address: D8:12:65:B8:21:BA
  Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%)
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB temp: 24.9 C
 ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 
GiB
  Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: 
/dev/nvme0n1p3
 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  Alert: No swap data was found.
  Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A
 Fan Speeds (RPM): cpu: 0
  Info:  Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) 
Init: systemd runlevel: 5 Compilers:
 gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07
  corrado@corrado-p3-jj-1130:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-11-30 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  Package: gnome-control-center 1:41.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Tags:  wayland-session jammy
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare 

[Desktop-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot

[Igor V. Kovalenko]

Sebastien, if distribution is intended to provide pipewire function for
video only, there is no need to install audio parts. At very least
'with-pulse' 'with-jack' and other files directly or transitively
enabling 'with-audio' pipewire parts should not be installed so pipewire
media session daemon does not get hold of hardware controls.

Alternatively, if distribution is intended to provide pulseaudio
interface via pipewire, that should be properly switching pulseaudio
activation socket to pipewire-pulse, and/or disabling or uninstalling
pulseaudio daemon and maybe disabling pulseaudio autospawn in
client.conf

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

Title:
  In Jammy sound level reset after reboot

Status in alsa-utils package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After reboot sound level is reset ignoring the level set in previous
  session.

  I manually set the sound output level 
  at next boot the sound is set at a different level (about 70%)

  Expected: the sound level is persistent across power off/on

  What happens : sound level is set at a different level (about 70%)

  Note: this problem does not occur on different partitions of same PC
  running Ubuntu 20.04 or 21.10

  corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p3-jj-1130:~$ inxi -Fx
  System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 
compiler: gcc v: 11.2.0
 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 

 Mobo: Dell model: 0C1PF2 v: A00 serial:  UEFI: 
Dell v: 1.5.0 date: 12/17/2019
  Battery:   ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) 
volts: 11.3 min: 11.4
 model: SWD-ATL3.618 DELL WJPC403 status: Discharging
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 cache:
 L2: 6 MiB
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046
 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 
710 3: 706 4: 714 5: 966 6: 712
 7: 724 8: 821
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus-ID: 00:02.0
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus-ID: 1-6:3
 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell 
driver: loaded: i915
 note: n/a (using device driver) resolution: 1920x1080~60Hz
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
21.2.2 direct render: Yes
  Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel
 bus-ID: 00:1f.3
 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes
 Sound Server-2: PulseAudio v: 15.0 running: yes
 Sound Server-3: PipeWire v: 0.3.40 running: yes
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000
 bus-ID: 01:00.0
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci
 v: kernel bus-ID: 02:00.0
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9
  Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 
1-10:4
 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: 
enabled,running rfk-block: hardware: no
 software: yes address: D8:12:65:B8:21:BA
  Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%)
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB temp: 24.9 C
 ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 
GiB
  Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: 
/dev/nvme0n1p3
 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  Alert: No swap data was found.
  Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A
 Fan Speeds (RPM): cpu: 0
  Info:  Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) 
Init: systemd runlevel: 5 Compilers:
 gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07
  corrado@corrado-p3-jj-1130:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  

[Desktop-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot

[Igor V. Kovalenko]

Do you have both pulseaudio and pipewire audio enabled simultaneously?
At least system log suggests pipewire with session manager is also being
activated, this could cause issues if both attempt to restore volumes
for some reason.

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

Title:
  In Jammy sound level reset after reboot

Status in alsa-utils package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After reboot sound level is reset ignoring the level set in previous
  session.

  I manually set the sound output level 
  at next boot the sound is set at a different level (about 70%)

  Expected: the sound level is persistent across power off/on

  What happens : sound level is set at a different level (about 70%)

  Note: this problem does not occur on different partitions of same PC
  running Ubuntu 20.04 or 21.10

  corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p3-jj-1130:~$ inxi -Fx
  System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 
compiler: gcc v: 11.2.0
 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 

 Mobo: Dell model: 0C1PF2 v: A00 serial:  UEFI: 
Dell v: 1.5.0 date: 12/17/2019
  Battery:   ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) 
volts: 11.3 min: 11.4
 model: SWD-ATL3.618 DELL WJPC403 status: Discharging
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 cache:
 L2: 6 MiB
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046
 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 
710 3: 706 4: 714 5: 966 6: 712
 7: 724 8: 821
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus-ID: 00:02.0
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus-ID: 1-6:3
 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell 
driver: loaded: i915
 note: n/a (using device driver) resolution: 1920x1080~60Hz
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
21.2.2 direct render: Yes
  Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel
 bus-ID: 00:1f.3
 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes
 Sound Server-2: PulseAudio v: 15.0 running: yes
 Sound Server-3: PipeWire v: 0.3.40 running: yes
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000
 bus-ID: 01:00.0
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci
 v: kernel bus-ID: 02:00.0
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9
  Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 
1-10:4
 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: 
enabled,running rfk-block: hardware: no
 software: yes address: D8:12:65:B8:21:BA
  Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%)
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB temp: 24.9 C
 ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 
GiB
  Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: 
/dev/nvme0n1p3
 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  Alert: No swap data was found.
  Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A
 Fan Speeds (RPM): cpu: 0
  Info:  Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) 
Init: systemd runlevel: 5 Compilers:
 gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07
  corrado@corrado-p3-jj-1130:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-11-30 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  Package: gnome-control-center 1:41.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Tags:  wayland-session jammy
  

[Desktop-packages] [Bug 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake

[Igor V. Kovalenko]

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

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

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

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

Title:
  Pulseaudio breaks HDMI audio on sleep/wake

Status in pulseaudio package in Ubuntu:
  Confirmed

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

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

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

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

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


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

[Desktop-packages] [Bug 1941962] Re: pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from pa_x11_wrapper_unref()

[Igor V. Kovalenko]

Just a heads-up, fix for libx11 issue 139 is now merged upstream
https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/84

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

Title:
  pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from
  pa_x11_wrapper_unref()

Status in X.Org X server:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/52094416ad4b4132ebf639ec8530fed1fdbac584

  crash

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  Uname: Linux 5.13.13-xanmod1-cacule x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anasc  1719 F pulseaudio
   /dev/snd/pcmC0D0p:   anasc  1719 F...m pulseaudio
  CasperMD5CheckResult: pass
  Date: Sat Aug 28 21:00:59 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-08-26 (2 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210824)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  SegvAnalysis:
   Segfault happened at: 0x7fbcc9d6a8a4 :  mov%edx,0x4(%rax)
   PC (0x7fbcc9d6a8a4) ok
   source "%edx" ok
   destination "0x4(%rax)" (0x0004) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   XFreeGC () from /lib/x86_64-linux-gnu/libX11.so.6
   XCloseDisplay () from /lib/x86_64-linux-gnu/libX11.so.6
   pa_x11_wrapper_unref () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-15.0.so
   module_x11_publish_LTX_pa__done () from 
/usr/lib/pulse-15.0+dfsg1/modules/module-x11-publish.so
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-15.0.so
  Title: pulseaudio crashed with SIGSEGV in XFreeGC()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 02/05/2021
  dmi.bios.release: 15.14
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 86E2
  dmi.board.vendor: HP
  dmi.board.version: 95.36
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.36
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd02/05/2021:br15.14:efr95.36:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:sku5SU52EA#BH4:rvnHP:rn86E2:rvr95.36:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cs3xxx
  dmi.product.sku: 5SU52EA#BH4
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  separator:

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


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

[Desktop-packages] [Bug 1945235] Re: pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put() from transport_put() from hfp_rfcomm_handle()

[Igor V. Kovalenko]

This could be a problem in pulseaudio native backend, provoked by
numerous reconnections between bluez and headset.

If verbose log from pulseaudio daemon can be collected for this crash, I
think it is worth to file an issue in pulseaudio tracker here
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/ with
verbose log attached.

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

Title:
  pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put() from
  transport_put() from hfp_rfcomm_handle()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/3f255341dbcb4f57cf88d6fc2bed25ae18a760fe

  ---

  have headphones bluetooth
  bluetooth connect and disconnect if i turn off sound

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  duncan20876 F pulseaudio
   /dev/snd/controlC0:  duncan20876 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Mon Sep 27 21:06:47 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-09-13 (14 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_bluetooth_transport_put () at 
/usr/lib/pulse-15.0+dfsg1/modules/libbluez5-util.so
   () at /usr/lib/pulse-15.0+dfsg1/modules/libbluez5-util.so
   pa_mainloop_dispatch () at /lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_iterate () at /lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_run () at /lib/x86_64-linux-gnu/libpulse.so.0
  Title: pulseaudio crashed with SIGABRT in pa_bluetooth_transport_put()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 07/21/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  separator:

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


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

[Desktop-packages] [Bug 1941977] Re: PC streams music over low-quality HFP/SCO connection, instead of A2DP/AVDTP

[Igor V. Kovalenko]

Hi Brian, would you mind filing an issue on bluez tracker for this
analysis here https://github.com/bluez/bluez/issues

To me it looks valid, but still running this through bluez maintainers
is a good idea.

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

Title:
  PC streams music over low-quality HFP/SCO connection, instead of
  A2DP/AVDTP

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This issue was first discovered when I got this headset 2 years back:
  https://www.amazon.co.uk/gp/product/B01C2QCPYI.

  STEPS
  * Enable Bluetooth on the PC
  * Have music or some video playing on the PC
  * Power on the (already-paired) headset. It automatically connects to the PC.

  EXPECTED RESULT
  The PC's audio should now be streamed to the headset, over high-quality A2DP

  ACTUAL RESULT
  The PC's audio gets streamed over the low-quality HFP/SCO connection instead. 

  Stopping and resuming the stream changes nothing. I have to manually
  open Blueman and right-click on the device and select "High-quality
  A2DP profile", for it to switch to the expected high-quality A2DP
  transport.

  HCI snoop logs and verbose bluetoothd-syslogs taken in both headset-
  initiated and PC-initiated connections are attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3.3 [modified: 
lib/systemd/system/bluetooth.service]
  ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114
  Uname: Linux 5.4.0-74-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 29 03:49:08 2021
  InstallationDate: Installed on 2019-06-08 (812 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9380
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic 
root=UUID=93dae559-0f0d-4e36-9318-ee7154840a9f ro 
resume=UUID=01c18f00-e0eb-4891-9bf1-3110416d9b39 quiet splash 
mem_sleep_default=deep vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/14/2020:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 9C:B6:D0:99:1D:20  ACL MTU: 1024:8  SCO MTU: 50:8
UP RUNNING PSCAN 
RX bytes:3313120 acl:776 sco:26275 events:305102 errors:0
TX bytes:255208317 acl:298108 sco:22053 commands:6779 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-04-27T23:21:52.866445

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


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

[Desktop-packages] [Bug 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()

[Igor V. Kovalenko]

I cannot reproduce this yet. Could someone who can please collect
pulseaudio daemon verbose log for this crash?

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

Title:
  pulseaudio crashed with SIGSEGV in _IceTransClose()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e

  ---

  Installing Xubuntu Impish daily ISO 04092021

  After install I rebooted - applied updates and then rebooted again-

  the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() )
  occurred after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kx  847 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Sat Sep  4 16:43:45 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-09-04 (0 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6
   _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6
   IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6
   SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6
   ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so
  Title: pulseaudio crashed with SIGSEGV in _IceTransClose()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 12/23/2020
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN51WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V14-IIL
  dmi.ec.firmware.release: 1.51
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL:
  dmi.product.family: V14-IIL
  dmi.product.name: 82C4
  dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL
  dmi.product.version: Lenovo V14-IIL
  dmi.sys.vendor: LENOVO
  separator:

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


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

[Desktop-packages] [Bug 1941962] Re: pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from pa_x11_wrapper_unref()

[Igor V. Kovalenko]

I believe this crash is caused by this libx11 issue
https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/139


** Bug watch added: gitlab.freedesktop.org/xorg/lib/libx11/-/issues #139
   https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/139

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

Title:
  pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from
  pa_x11_wrapper_unref()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/52094416ad4b4132ebf639ec8530fed1fdbac584

  crash

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  Uname: Linux 5.13.13-xanmod1-cacule x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anasc  1719 F pulseaudio
   /dev/snd/pcmC0D0p:   anasc  1719 F...m pulseaudio
  CasperMD5CheckResult: pass
  Date: Sat Aug 28 21:00:59 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-08-26 (2 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210824)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  SegvAnalysis:
   Segfault happened at: 0x7fbcc9d6a8a4 :  mov%edx,0x4(%rax)
   PC (0x7fbcc9d6a8a4) ok
   source "%edx" ok
   destination "0x4(%rax)" (0x0004) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   XFreeGC () from /lib/x86_64-linux-gnu/libX11.so.6
   XCloseDisplay () from /lib/x86_64-linux-gnu/libX11.so.6
   pa_x11_wrapper_unref () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-15.0.so
   module_x11_publish_LTX_pa__done () from 
/usr/lib/pulse-15.0+dfsg1/modules/module-x11-publish.so
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-15.0.so
  Title: pulseaudio crashed with SIGSEGV in XFreeGC()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 02/05/2021
  dmi.bios.release: 15.14
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 86E2
  dmi.board.vendor: HP
  dmi.board.version: 95.36
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.36
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd02/05/2021:br15.14:efr95.36:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:sku5SU52EA#BH4:rvnHP:rn86E2:rvr95.36:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cs3xxx
  dmi.product.sku: 5SU52EA#BH4
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  separator:

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


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

[Desktop-packages] [Bug 1931547] Re: DisplayLink displays are black after Mesa update

[Igor Lopez]

I might be affected by this and am willing to test if it solves my problem.
What happened was that about maybe two weeks ago the DisplayPorts from my DELL 
D6000 Dock stopped working (but works when connecting a Windows Laptop)
Where do I find instructions on testing?

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

Title:
  DisplayLink displays are black after Mesa update

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Please incorporate xorg-server fix for issue:
  https://gitlab.freedesktop.org/xorg/xserver/-/issues/1183

  It was already merged in to xserver master and xserver-1.20-branch branches.
  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/681
  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/683

  This is reported by our users reports on Ubuntu 20.10  with Xserver-1.20.9
  and on Ubuntu 21.04 with XServer-1.20.11

  
  If it is required i am willing to help with anything.

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

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

[Desktop-packages] [Bug 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

[Igor Voldiner]

As a side note: headset mic was brought to life (tested for "headset-
mode" model) on the 0x19 pin (as detected/configured by default)  with
specifically selecting "Not Present" for jack detection (in Advanced
override tab).

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

Title:
  [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Running the command alsamixer allows me to manually increase the sound levels 
for the headset, and sound plays properly through them. This requires me to 
disable the auto-mute feature.
  I haven't rebooted my system yet to see if this is permanent.
  But the UI doesn't show the heaphones at all and only sends sound through the 
main speakers of the laptop.

  ➜  ~ lspci -nnk | grep -i -A7 audio
  00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

  ➜  ~ cat /proc/asound/card0/codec* | grep Codec 
  Codec: Realtek ALC256
  Codec: Intel Kabylake HDMI

  Using for example pavucontrol allows me to select the headphone, which are 
marked as unplugged, and I can play audio through them as long as I keep the 
application open.
  If I reboot or close pavucontrol, everything is back to the original state 
and only the speakers work.

  Additional Information:

  ➜  ~ lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  What I expect to happen:

  When I plug in my headphones, Ubuntu and the UI should see them and
  automatically redirect all sound through them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   olivar 8320 F...m pulseaudio
   /dev/snd/controlC0:  olivar 8320 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec  6 13:02:14 2018
  InstallationDate: Installed on 2018-11-21 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 01.01
  dmi.board.name: DANA_MB
  dmi.board.vendor: Razer
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr:
  dmi.product.family: 1A582001 Razer Blade
  dmi.product.name: Blade
  dmi.product.version: 1.04
  dmi.sys.vendor: Razer

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

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

[Desktop-packages] [Bug 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

[Igor Voldiner]

I found a work-around that allows detection of headphones to work correctly.
by changing model name of the codec to "headset-mode" from "headset-mic" in 
/etc/modprobe.d/alsa-base.conf

However this did not solve the problem with headset mic, which is not
working (tried all pins available from hdajackretask) for any of two of
above specified model names.

Alsa-info output: http://alsa-
project.org/db/?f=5066c1fc285a210c75e5ef61712c35c2cce9efca

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

Title:
  [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Running the command alsamixer allows me to manually increase the sound levels 
for the headset, and sound plays properly through them. This requires me to 
disable the auto-mute feature.
  I haven't rebooted my system yet to see if this is permanent.
  But the UI doesn't show the heaphones at all and only sends sound through the 
main speakers of the laptop.

  ➜  ~ lspci -nnk | grep -i -A7 audio
  00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

  ➜  ~ cat /proc/asound/card0/codec* | grep Codec 
  Codec: Realtek ALC256
  Codec: Intel Kabylake HDMI

  Using for example pavucontrol allows me to select the headphone, which are 
marked as unplugged, and I can play audio through them as long as I keep the 
application open.
  If I reboot or close pavucontrol, everything is back to the original state 
and only the speakers work.

  Additional Information:

  ➜  ~ lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  What I expect to happen:

  When I plug in my headphones, Ubuntu and the UI should see them and
  automatically redirect all sound through them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   olivar 8320 F...m pulseaudio
   /dev/snd/controlC0:  olivar 8320 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec  6 13:02:14 2018
  InstallationDate: Installed on 2018-11-21 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 01.01
  dmi.board.name: DANA_MB
  dmi.board.vendor: Razer
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr:
  dmi.product.family: 1A582001 Razer Blade
  dmi.product.name: Blade
  dmi.product.version: 1.04
  dmi.sys.vendor: Razer

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

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

[Desktop-packages] [Bug 1916358] [NEW] #789859

[Cemirtan Igor Grigore]

Public bug reported:

sudo rm /etc/apt/sources.list.d/some-ppa.list
rm: невозможно удалить '/etc/apt/sources.list.d/some-ppa.list': Нет такого 
файла или каталога

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  #789859

Status in software-properties package in Ubuntu:
  New

Bug description:
  sudo rm /etc/apt/sources.list.d/some-ppa.list
  rm: невозможно удалить '/etc/apt/sources.list.d/some-ppa.list': Нет такого 
файла или каталога

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

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

[Desktop-packages] [Bug 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell

[Igor Hipólito Vieira]

I'm also having the same issue whenever I try to drag and drop something
from the desktop. Is there any kind of log I can provide to help fix the
issue?

Here's some info from neofetch:

```
Laptop: Dell Latitude 5400
OS: Ubuntu 20.10 x86_64
Kernel: 5.8.0-29-generic
Shell: zsh 5.8
DE: GNOME 3.38.1
WM: Mutter
WM Theme: Adwaita
Theme: Yaru-dark [GTK2/3]
Icons: Yaru [GTK2/3]
Terminal: x-terminal-emul
CPU: Intel i7-8665U (8) @ 4.800GHz
GPU: Intel UHD Graphics 620
RAM: 15823MiB
```

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

Title:
  [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-
  shell

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

Bug description:
  [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-
  shell in Ubuntu 20.10 (beta).

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

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

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

[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

[Igor]

I meant HFP profile.

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  In Progress
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

[Igor]

@pesso82

There is your problem. Those headphones do not support HSP 1.6 profile,
only 1.5.

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  In Progress
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

[Igor]

@gdi2k

What we have in the Linux now is HFP with 8kHz encoding. All other
platforms such as Windows, Android, Chromium, etc, supports HFP with
16kHZ encoding which is much much better quality. Sure, it's not like
A2DP, but quality is very much acceptable to speak with someone.

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  In Progress
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

[Igor]

@dennis9771

Just get yourself Bluetooth audio card and save yourself a trouble, this
will never be fixed. And you will not be able to use A2DP for
conversation even if fixed. The goal of the fix is to add HFP 1.6 with
mSBC 16kHz audio encoding so you have better quality during
conversation.

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  In Progress
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1896842] Re: simple-scan cannot scan a page using EPSON V39 scanner

[Igor Shabalov]

Thank you for the update, yes, version 3.36.6 works, I confirm.

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

Title:
  simple-scan cannot scan a page using EPSON V39 scanner

Status in Simple Scan:
  Unknown
Status in simple-scan package in Ubuntu:
  Fix Committed

Bug description:
  ishabalov@black:~$ simple-scan --debug
  [+0.00s] DEBUG: simple-scan.vala:1720: Starting simple-scan 3.36.3, PID=38292
  [+0.00s] DEBUG: unsetenv() is not thread-safe and should not be used after 
threads are created
  [+0.01s] DEBUG: _g_io_module_get_default: Found default implementation dconf 
(DConfSettingsBackend) for ‘gsettings-backend’
  [+0.09s] DEBUG: app-window.vala:1906: Loading state from 
/home/ishabalov/.cache/simple-scan/state
  [+0.09s] DEBUG: app-window.vala:1885: Restoring window to 1351x672 pixels
  [+0.17s] DEBUG: scanner.vala:1539: sane_init () -> SANE_STATUS_GOOD
  [+0.17s] DEBUG: scanner.vala:1545: SANE version 1.0.29
  [+0.17s] DEBUG: scanner.vala:1606: Requesting redetection of scan devices
  [+0.17s] DEBUG: scanner.vala:828: Processing request
  [+0.56s] DEBUG: app-window.vala:1981: Saving state to 
/home/ishabalov/.cache/simple-scan/state
  [+8.42s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
  [+8.42s] DEBUG: scanner.vala:353: Device: 
name="imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0"
 vendor="EPSON" model="Epson_Perfection_V39" type=""
  [+8.72s] DEBUG: app-window.vala:1981: Saving state to 
/home/ishabalov/.cache/simple-scan/state
  [+9.90s] DEBUG: simple-scan.vala:1536: Requesting scan at 300 dpi from device 
'imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0'
  [+9.90s] DEBUG: scanner.vala:1674: Scanner.scan 
("imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0",
 dpi=300, scan_mode=ScanMode.COLOR, depth=8, type=single, paper_width=0, 
paper_height=0, brightness=26, contrast=46, delay=3000ms)
  [+9.90s] DEBUG: scanner.vala:828: Processing request
  [+10.17s] DEBUG: scanner.vala:889: sane_open 
("imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0")
 -> SANE_STATUS_GOOD
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (0)
  [+10.17s] DEBUG: scanner.vala:760: Option 0: type=int size=4 
cap=soft-detect,advanced
  [+10.17s] DEBUG: scanner.vala:763:   Description: 
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (1)
  [+10.17s] DEBUG: scanner.vala:760: Option 1: name='device-02-general' 
title='General' type=group size=0 cap=inactive
  [+10.17s] DEBUG: scanner.vala:763:   Description: Basic options.
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (2)
  [+10.17s] DEBUG: scanner.vala:760: Option 2: name='source' title='Document 
Source' type=string size=15 values=["Document Table"] cap=soft-detect
  [+10.17s] DEBUG: scanner.vala:763:   Description: Document Source
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (3)
  [+10.17s] DEBUG: scanner.vala:760: Option 3: name='enable-resampling' 
title='Enable Resampling' type=bool size=4 cap=soft-detect,inactive,advanced
  [+10.17s] DEBUG: scanner.vala:763:   Description: This option provides the 
user with a wider range of supported resolutions.  Resolutions not supported by 
the hardware will be achieved through image processing methods.
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (4)
  [+10.17s] DEBUG: scanner.vala:760: Option 4: name='resolution' 
title='Resolution' type=int size=4 unit=dpi min=50, max=4800, quant=0 
cap=soft-select,soft-detect
  [+10.17s] DEBUG: scanner.vala:763:   Description: Resolution
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (5)
  [+10.17s] DEBUG: scanner.vala:760: Option 5: name='scan-area' title='Scan 
Area' type=string size=19 values=["Executive/Portrait", "ISO/A4/Portrait", 
"ISO/A5/Portrait", "ISO/A5/Landscape", "ISO/A6/Portrait", "ISO/A6/Landscape", 
"JIS/B5/Portrait", "JIS/B6/Portrait", "JIS/B6/Landscape", "Letter/Portrait", 
"Manual", "Maximum"] cap=soft-select,soft-detect
  [+10.17s] DEBUG: scanner.vala:763:   Description: Scan Area
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (6)
  [+10.17s] DEBUG: scanner.vala:760: Option 6: name='mode' title='Image Type' 
type=string size=11 values=["Monochrome", "Grayscale", "Color"] 
cap=soft-select,soft-detect,emulated
  [+10.17s] DEBUG: scanner.vala:763:   Description: Image Type
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (7)
  [+10.17s] DEBUG: scanner.vala:760: Option 7: name='device-03-geometry' 
title='Geometry' type=group size=0 cap=inactive
  [+10.17s] DEBUG: scanner.vala:763:   Description: Scan area and image size 
related options.
  [+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (8)
  [+10.17s] DEBUG: scanner.vala:760: Option 8: name='br-x' 

[Desktop-packages] [Bug 1896842] [NEW] simple-scan cannot scan a page using EPSON V39 scanner

[Igor Shabalov]

Public bug reported:

ishabalov@black:~$ simple-scan --debug
[+0.00s] DEBUG: simple-scan.vala:1720: Starting simple-scan 3.36.3, PID=38292
[+0.00s] DEBUG: unsetenv() is not thread-safe and should not be used after 
threads are created
[+0.01s] DEBUG: _g_io_module_get_default: Found default implementation dconf 
(DConfSettingsBackend) for ‘gsettings-backend’
[+0.09s] DEBUG: app-window.vala:1906: Loading state from 
/home/ishabalov/.cache/simple-scan/state
[+0.09s] DEBUG: app-window.vala:1885: Restoring window to 1351x672 pixels
[+0.17s] DEBUG: scanner.vala:1539: sane_init () -> SANE_STATUS_GOOD
[+0.17s] DEBUG: scanner.vala:1545: SANE version 1.0.29
[+0.17s] DEBUG: scanner.vala:1606: Requesting redetection of scan devices
[+0.17s] DEBUG: scanner.vala:828: Processing request
[+0.56s] DEBUG: app-window.vala:1981: Saving state to 
/home/ishabalov/.cache/simple-scan/state
[+8.42s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
[+8.42s] DEBUG: scanner.vala:353: Device: 
name="imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0"
 vendor="EPSON" model="Epson_Perfection_V39" type=""
[+8.72s] DEBUG: app-window.vala:1981: Saving state to 
/home/ishabalov/.cache/simple-scan/state
[+9.90s] DEBUG: simple-scan.vala:1536: Requesting scan at 300 dpi from device 
'imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0'
[+9.90s] DEBUG: scanner.vala:1674: Scanner.scan 
("imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0",
 dpi=300, scan_mode=ScanMode.COLOR, depth=8, type=single, paper_width=0, 
paper_height=0, brightness=26, contrast=46, delay=3000ms)
[+9.90s] DEBUG: scanner.vala:828: Processing request
[+10.17s] DEBUG: scanner.vala:889: sane_open 
("imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0")
 -> SANE_STATUS_GOOD
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (0)
[+10.17s] DEBUG: scanner.vala:760: Option 0: type=int size=4 
cap=soft-detect,advanced
[+10.17s] DEBUG: scanner.vala:763:   Description: 
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (1)
[+10.17s] DEBUG: scanner.vala:760: Option 1: name='device-02-general' 
title='General' type=group size=0 cap=inactive
[+10.17s] DEBUG: scanner.vala:763:   Description: Basic options.
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (2)
[+10.17s] DEBUG: scanner.vala:760: Option 2: name='source' title='Document 
Source' type=string size=15 values=["Document Table"] cap=soft-detect
[+10.17s] DEBUG: scanner.vala:763:   Description: Document Source
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (3)
[+10.17s] DEBUG: scanner.vala:760: Option 3: name='enable-resampling' 
title='Enable Resampling' type=bool size=4 cap=soft-detect,inactive,advanced
[+10.17s] DEBUG: scanner.vala:763:   Description: This option provides the user 
with a wider range of supported resolutions.  Resolutions not supported by the 
hardware will be achieved through image processing methods.
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (4)
[+10.17s] DEBUG: scanner.vala:760: Option 4: name='resolution' 
title='Resolution' type=int size=4 unit=dpi min=50, max=4800, quant=0 
cap=soft-select,soft-detect
[+10.17s] DEBUG: scanner.vala:763:   Description: Resolution
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (5)
[+10.17s] DEBUG: scanner.vala:760: Option 5: name='scan-area' title='Scan Area' 
type=string size=19 values=["Executive/Portrait", "ISO/A4/Portrait", 
"ISO/A5/Portrait", "ISO/A5/Landscape", "ISO/A6/Portrait", "ISO/A6/Landscape", 
"JIS/B5/Portrait", "JIS/B6/Portrait", "JIS/B6/Landscape", "Letter/Portrait", 
"Manual", "Maximum"] cap=soft-select,soft-detect
[+10.17s] DEBUG: scanner.vala:763:   Description: Scan Area
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (6)
[+10.17s] DEBUG: scanner.vala:760: Option 6: name='mode' title='Image Type' 
type=string size=11 values=["Monochrome", "Grayscale", "Color"] 
cap=soft-select,soft-detect,emulated
[+10.17s] DEBUG: scanner.vala:763:   Description: Image Type
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (7)
[+10.17s] DEBUG: scanner.vala:760: Option 7: name='device-03-geometry' 
title='Geometry' type=group size=0 cap=inactive
[+10.17s] DEBUG: scanner.vala:763:   Description: Scan area and image size 
related options.
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (8)
[+10.17s] DEBUG: scanner.vala:760: Option 8: name='br-x' title='Bottom Right X' 
type=fixed size=4 unit=mm min=2.539993, max=218.439987, quant=0 
cap=soft-select,soft-detect
[+10.17s] DEBUG: scanner.vala:763:   Description: Bottom Right X
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (9)
[+10.17s] DEBUG: scanner.vala:760: Option 9: name='br-y' title='Bottom Right Y' 
type=fixed size=4 unit=mm min=2.539993, max=299.719986, quant=0 
cap=soft-select,soft-detect
[+10.17s] DEBUG: scanner.vala:763:   Description: Bottom Right 

[Desktop-packages] [Bug 1879024] Re: Error message : "Failed to scan - unable to connect to scanner" when using simple-scan

[Igor Shabalov]

Have exactly same error with Brother MFS-L8900CDW
Upgraded from 18.04.5 - was working well before upgrade.

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

Title:
  Error message : "Failed to scan - unable to connect to scanner" when
  using simple-scan

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  1) System and program information:
  I am using Ubuntu 20.04 LTS and am trying to use the brother printer/scanner 
combo MFC-J5910DW in order to scan documents with simple-scan:
   
  simple-scan:
   Installed: 3.36.0-0ubuntu1
Candidate: 3.36.0-0ubuntu1
Version table:
   *** 3.36.0-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  2) Description of what I did and what happened:
  I downloaded and installed the newest scanner driver deb-packages (2 of them) 
from the official brother web-page and installed them using

  $ sudo apt-get install ./'sannerdirverfilename'.deb

  and there was no error message. So I also installed simple-scan from
  the Ubuntu repository using:

  $ sudo apt-get install simple-scan

  This also worked just fine. But when I now try to use simple-scan, it
  doesn't work. I call the program from the terminal command line:

  $ simple scan

  and it opens an interactive window, searches for a scanner and finds
  the brother scanner. But when I then hit the 'scan' button, I get the
  error message

  "Failed to scan - unable to connect to scanner"

  3) Error Log for simple-scan:
  So I used simple-scan with the debug option, and here is the log-file:

  $ simple-scan --debug
  [+0,00s] DEBUG: simple-scan.vala:638: Starting simple-scan 3.36.0, PID=7992
  [+0,00s] DEBUG: unsetenv() is not thread-safe and should not be used after 
threads are created
  [+0,02s] DEBUG: _g_io_module_get_default: Found default implementation dconf 
(DConfSettingsBackend) for ‘gsettings-backend’
  [+0,06s] DEBUG: app-window.vala:1908: Loading state from 
/home/barbara/.cache/simple-scan/state
  [+0,06s] DEBUG: app-window.vala:1887: Restoring window to 600x400 pixels
  [+0,33s] DEBUG: app-window.vala:1983: Saving state to 
/home/barbara/.cache/simple-scan/state
  [+6,00s] DEBUG: scanner.vala:1541: sane_init () -> SANE_STATUS_GOOD
  [+6,00s] DEBUG: scanner.vala:1547: SANE version 1.0.29
  [+6,00s] DEBUG: scanner.vala:1608: Requesting redetection of scan devices
  [+6,00s] DEBUG: scanner.vala:828: Processing request
  [+6,15s] DEBUG: app-window.vala:1983: Saving state to 
/home/barbara/.cache/simple-scan/state
  [+14,91s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
  [+14,91s] DEBUG: scanner.vala:353: Device: name="brother4:bus2;dev2" 
vendor="Brother" model="MFC-J5910DW" type="USB scanner"
  [+15,02s] DEBUG: app-window.vala:1983: Saving state to 
/home/barbara/.cache/simple-scan/state
  [+41,02s] DEBUG: simple-scan.vala:455: Requesting scan at 150 dpi from device 
'brother4:bus2;dev2'
  [+41,02s] DEBUG: scanner.vala:1676: Scanner.scan ("brother4:bus2;dev2", 
dpi=150, scan_mode=ScanMode.GRAY, depth=2, type=single, paper_width=0, 
paper_height=0, brightness=0, contrast=0, delay=3000ms)
  [+41,02s] DEBUG: scanner.vala:828: Processing request
  [+41,02s] DEBUG: scanner.vala:889: sane_open ("brother4:bus2;dev2") -> 
SANE_STATUS_IO_ERROR
  [+41,02s] WARNING: scanner.vala:893: Unable to open device: Error during 
device I/O
  [+41,43s] DEBUG: app-window.vala:1983: Saving state to 
/home/barbara/.cache/simple-scan/state
  [+56,27s] DEBUG: app-window.vala:1983: Saving state to 
/home/barbara/.cache/simple-scan/state
  [+100,09s] DEBUG: autosave-manager.vala:201: Deleting autosave records
  [+100,09s] DEBUG: scanner.vala:1704: Stopping scan thread
  [+100,09s] DEBUG: scanner.vala:828: Processing request
  [+100,09s] DEBUG: scanner.vala:1715: sane_exit ()

  I have no idea why sane cannot open the I/O device.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: simple-scan 3.36.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 16 07:54:46 2020
  InstallationDate: Installed on 2020-04-24 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Latitude E5450
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=2bb62112-1254-42cd-ba84-e3f2edc0d4b2 ro quiet splash vt.handoff=7
  SimpleScanLog:
   
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0DCPV1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell 

Re: [Desktop-packages] [Bug 1871573] Re: [Lenovo ThinkPad P1 Gen 2] HDMI port can't be found

[Igor]

Hi Thierry,

>From memory I did set "on demand" mode and it worked correctly.

Now it is a strange situation, kernel 5.4.0-28 is the latest that boots
correctly in my setup if only built in screen (on later versions, it hangs
shortly after Linux boot started, Lenovo sign still there and progress
circle not shown anymore)
Latest kernels boots correctly if there is external screen plugged by HDMI
(so, maybe "hung" from 1st case it is just that still somehow expects
external screen...)

Regards,
Igor


čet, 18. lip 2020. u 13:45 Thierry Bossy <1871...@bugs.launchpad.net>
napisao je:

> Hi,
>
> I have a very similar problem and noticed the following:
> My external display is working with Nvidia "Performance Mode" only. In
> "On-demand" mode, I have a black screen that it is not detected in Ubuntu
> system settings, although it is detected by Nvidia X Server Settings.
> As if we needed a parameter in On-demand to force HDMI interface to start
> with Nvidia card and not Intel.
>
> Any hints about this?
>
> @Igor, are you sure that you are in "On Demand" mode? I realized that it
> automatically switches to "Performance Mode" when we change the driver.
>
> Thanks,
> Thierry
> ---
> My config:
> - Lenovo Thinkpad P1 Gen2 with Nvidia Quadro T2000
> - Secure Boot Disabled
> - Nvidia driver 440 activated
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1871573
>
> Title:
>   [Lenovo ThinkPad P1 Gen 2] HDMI port can't be found
>
> Status in nvidia-prime package in Ubuntu:
>   Won't Fix
>
> Bug description:
>   Hi,
>
>   I know that you have certified version 18.04 and that 20.04 is not out
> yet.
>   So this is more heads up.
>
>   I am testing Ubuntu 20.04 on new Lenovo P1 2nd gen.
>   Currently HDMI does not work.
>
>   How do I know that problem is not in cable or monitor ?
>   If I boot to windows, HDMI port works as expected.
>
>   Thank you,
>   Igor RACIC
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: xorg 1:7.7+19ubuntu14
>   ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
>   Uname: Linux 5.4.0-21-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu24
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Apr  8 10:00:57 2020
>   DistUpgraded: Fresh install
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   DkmsStatus:
>acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
>nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
>   GraphicsCard:
>Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00
> [VGA controller])
>  Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f]
>   InstallationDate: Installed on 2020-04-01 (6 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
>   MachineType: LENOVO 20QTCTO1WW
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic
> root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   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
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.100-4
>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
>   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+git20190815-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to

Re: [Desktop-packages] [Bug 1882923] Re: Ubuntu 20.04, login screen, unable to click with trackpad

[Igor]

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

Hi Daniel,

Thank you reply.

When login using default login manager, once you are logged in, it works as
intended.

On the other hand, if you login with i3 window manager, this problem is
still there, tap to click does not work.
Is it question for i3 team?

Thank you,
Igor


On Wed, Jun 10, 2020, 13:40 Daniel van Vugt <1882...@bugs.launchpad.net>
wrote:

> *** This bug is a duplicate of bug 1711538 ***
> https://bugs.launchpad.net/bugs/1711538
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. This particular bug has already been reported and is a
> duplicate of bug 1711538, so it is being marked as such. Please look at
> the other bug report to see if there is any missing information that you
> can provide, or to see if there is a workaround for the bug.
> Additionally, any further discussion regarding the bug should occur in
> the other report. Feel free to continue to report any other bugs you may
> find.
>
>
> ** This bug has been marked a duplicate of bug 1711538
>Tap-to-click does not work on the GDM login screen
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1882923
>
> Title:
>   Ubuntu 20.04, login screen, unable to click with trackpad
>
> Status in xorg package in Ubuntu:
>   New
>
> Bug description:
>   Hi,
>
>   In login screen, mouse works but clicking is possible only with click
> button.
>   Click on trackpad does not work.
>   Once entered Ubuntu session, click on trackpad works.
>   But if used i3wm (sudo apt install i3 + choosing i3 in right below
> button on login ) - problem persists even after login (mouse clicks
> possible only with mouse buttons)
>
>   Thank you,
>   Igor
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: xorg 1:7.7+19ubuntu14
>   ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
>   Uname: Linux 5.4.0-28-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.2
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: skip
>   CompositorRunning: None
>   CurrentDesktop: i3
>   Date: Wed Jun 10 12:18:15 2020
>   DistUpgraded: Fresh install
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   GraphicsCard:
>Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00
> [VGA controller])
>  Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f]
>NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1)
> (prog-if 00 [VGA controller])
>  Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:229f]
>   InstallationDate: Installed on 2020-04-01 (69 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
>   MachineType: LENOVO 20QTCTO1WW
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic
> root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   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
>   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/xorg/+bug/1882923/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to

[Desktop-packages] [Bug 1882923] [NEW] Ubuntu 20.04, login screen, unable to click with trackpad

[Igor]

Public bug reported:

Hi,

In login screen, mouse works but clicking is possible only with click button. 
Click on trackpad does not work. 
Once entered Ubuntu session, click on trackpad works. 
But if used i3wm (sudo apt install i3 + choosing i3 in right below button on 
login ) - problem persists even after login (mouse clicks possible only with 
mouse buttons)

Thank you, 
Igor

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: i3
Date: Wed Jun 10 12:18:15 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f]
 NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:229f]
InstallationDate: Installed on 2020-04-01 (69 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
MachineType: LENOVO 20QTCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7
SourcePackage: xorg
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
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

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Ubuntu 20.04, login screen, unable to click with trackpad

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  In login screen, mouse works but clicking is possible only with click button. 
  Click on trackpad does not work. 
  Once entered Ubuntu session, click on trackpad works. 
  But if used i3wm (sudo apt install i3 + choosing i3 in right below button on 
login ) - problem persists even after login (mouse clicks possible only with 
mouse buttons)

  Thank you, 
  Igor

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: i3
  Date: Wed Jun 10 12:18:15 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f]
   NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:229f]
  InstallationDate: Installed on 2020-04-01 (69 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  MachineType: LENOVO 20QTCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  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.ver

[Desktop-packages] [Bug 1874247] Re: Don't work wired connection regression focal

[Igor Zubarev]

Currently works ok. It seems it was Beta bug.

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

Title:
  Don't work wired connection regression focal

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After upgrade to focal I can't connect to wired network. It was ok in
  19.10 before

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 15:44:52 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.254 dev wlp7s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp7s0 scope link metric 1000 
   192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.67 metric 600
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1877129] Re: jackd won't run in realtime

[Igor Sakulin]

Please see attached systemd log

** Attachment added: "jrn"
   
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1877129/+attachment/5367437/+files/jrn

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

Title:
  jackd won't run in realtime

Status in jackd2 package in Ubuntu:
  Incomplete

Bug description:
  Was using jackd2 for ages, never had this issue. The usual limits.conf
  tweaks are present. Jackd won't run in realtime even as root. It's
  very easy to reproduce in Focal.

  Before upgrade, was working:
  Ubuntu 18.04.4 LTS
  uname -r
  kernel 5.3.0-51-generic
  jackd --version
  jackdmp version 1.9.12 tmpdir /dev/shm protocol 8

  After upgrade:
  Ubuntu 20.04 LTS
  uname -r
  5.4.0-29-generic
  jackd --version
  jackdmp version 1.9.12 tmpdir /dev/shm protocol 8

  
  Simple test:
  jackd -R -d dummy -r192000 -p2048

  jackdmp 1.9.12
  Copyright 2001-2005 Paul Davis and others.
  Copyright 2004-2016 Grame.
  Copyright 2016-2017 Filipe Coelho.
  jackdmp comes with ABSOLUTELY NO WARRANTY
  This is free software, and you are welcome to redistribute it
  under certain conditions; see the file COPYING for details
  Cannot create RT messagebuffer thread: Operation not permitted (1)
  Retrying messagebuffer thread without RT scheduling
  Messagebuffer not realtime; consider enabling RT scheduling for user
  no message buffer overruns
  Cannot create RT messagebuffer thread: Operation not permitted (1)
  Retrying messagebuffer thread without RT scheduling
  Messagebuffer not realtime; consider enabling RT scheduling for user
  no message buffer overruns
  Cannot create RT messagebuffer thread: Operation not permitted (1)
  Retrying messagebuffer thread without RT scheduling
  Messagebuffer not realtime; consider enabling RT scheduling for user
  no message buffer overruns
  JACK server starting in realtime mode with priority 10
  self-connect-mode is "Don't restrict self connect requests"
  Cannot use real-time scheduling (RR/10)(1: Operation not permitted)
  AcquireSelfRealTime error

  I'm guessing that it's not jack itself (package ver. seems to be the
  same as bionic, without new feats), smth is missing in the kernel
  config. I would try RT kernel, but it usually does not boot at all
  thanks to Nvidia blob on that system.

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

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

[Desktop-packages] [Bug 1877129] [NEW] jackd won't run in realtime

[Igor Sakulin]

Public bug reported:

Was using jackd2 for ages, never had this issue. The usual limits.conf
tweaks are present. Jackd won't run in realtime even as root. It's very
easy to reproduce in Focal.

Before upgrade, was working:
Ubuntu 18.04.4 LTS
uname -r
kernel 5.3.0-51-generic
jackd --version
jackdmp version 1.9.12 tmpdir /dev/shm protocol 8

After upgrade:
Ubuntu 20.04 LTS
uname -r
5.4.0-29-generic
jackd --version
jackdmp version 1.9.12 tmpdir /dev/shm protocol 8


Simple test:
jackd -R -d dummy -r192000 -p2048

jackdmp 1.9.12
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2017 Filipe Coelho.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
Cannot use real-time scheduling (RR/10)(1: Operation not permitted)
AcquireSelfRealTime error

I'm guessing that it's not jack itself (package ver. seems to be the
same as bionic, without new feats), smth is missing in the kernel
config. I would try RT kernel, but it usually does not boot at all
thanks to Nvidia blob on that system.

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

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

Title:
  jackd won't run in realtime

Status in jackd2 package in Ubuntu:
  New

Bug description:
  Was using jackd2 for ages, never had this issue. The usual limits.conf
  tweaks are present. Jackd won't run in realtime even as root. It's
  very easy to reproduce in Focal.

  Before upgrade, was working:
  Ubuntu 18.04.4 LTS
  uname -r
  kernel 5.3.0-51-generic
  jackd --version
  jackdmp version 1.9.12 tmpdir /dev/shm protocol 8

  After upgrade:
  Ubuntu 20.04 LTS
  uname -r
  5.4.0-29-generic
  jackd --version
  jackdmp version 1.9.12 tmpdir /dev/shm protocol 8

  
  Simple test:
  jackd -R -d dummy -r192000 -p2048

  jackdmp 1.9.12
  Copyright 2001-2005 Paul Davis and others.
  Copyright 2004-2016 Grame.
  Copyright 2016-2017 Filipe Coelho.
  jackdmp comes with ABSOLUTELY NO WARRANTY
  This is free software, and you are welcome to redistribute it
  under certain conditions; see the file COPYING for details
  Cannot create RT messagebuffer thread: Operation not permitted (1)
  Retrying messagebuffer thread without RT scheduling
  Messagebuffer not realtime; consider enabling RT scheduling for user
  no message buffer overruns
  Cannot create RT messagebuffer thread: Operation not permitted (1)
  Retrying messagebuffer thread without RT scheduling
  Messagebuffer not realtime; consider enabling RT scheduling for user
  no message buffer overruns
  Cannot create RT messagebuffer thread: Operation not permitted (1)
  Retrying messagebuffer thread without RT scheduling
  Messagebuffer not realtime; consider enabling RT scheduling for user
  no message buffer overruns
  JACK server starting in realtime mode with priority 10
  self-connect-mode is "Don't restrict self connect requests"
  Cannot use real-time scheduling (RR/10)(1: Operation not permitted)
  AcquireSelfRealTime error

  I'm guessing that it's not jack itself (package ver. seems to be the
  same as bionic, without new feats), smth is missing in the kernel
  config. I would try RT kernel, but it usually does not boot at all
  thanks to Nvidia blob on that system.

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

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

[Desktop-packages] [Bug 1875622] [NEW] Ubuntu 20.04 Dark mode isn't making the GNOME menus dark

[Igor Zubarev]

Public bug reported:

Ubuntu 20.04 dark mode is not making the top bar menus dark.
Also the grant permission dialog is not dark too.

Where are a lot of guides how to fix it. Users have to install different tweaks 
etc.
But is it going to be fixed in 20.04?

See https://www.omgubuntu.co.uk/2020/04/enable-full-dark-mode-in-ubuntu-20-04
https://askubuntu.com/questions/1231169/ubuntu-20-04-dark-mode-isnt-making-the-gnome-menus-dark
https://itsfoss.com/dark-mode-ubuntu/
http://ubuntuhandbook.org/index.php/2020/04/dark-gnome-shell-menus-ubuntu-20-04/

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 28 14:00:14 2020
DisplayManager: gdm3
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "DarkThemeMenu.png"
   
https://bugs.launchpad.net/bugs/1875622/+attachment/5362380/+files/DarkThemeMenu.png

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

Title:
  Ubuntu 20.04 Dark mode isn't making the GNOME menus dark

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 dark mode is not making the top bar menus dark.
  Also the grant permission dialog is not dark too.

  Where are a lot of guides how to fix it. Users have to install different 
tweaks etc.
  But is it going to be fixed in 20.04?

  See https://www.omgubuntu.co.uk/2020/04/enable-full-dark-mode-in-ubuntu-20-04
  
https://askubuntu.com/questions/1231169/ubuntu-20-04-dark-mode-isnt-making-the-gnome-menus-dark
  https://itsfoss.com/dark-mode-ubuntu/
  
http://ubuntuhandbook.org/index.php/2020/04/dark-gnome-shell-menus-ubuntu-20-04/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 14:00:14 2020
  DisplayManager: gdm3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1875622] Re: Ubuntu 20.04 Dark mode isn't making the GNOME menus dark

[Igor Zubarev]

Grant permission dialog

** Attachment added: "GrantPermission.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1875622/+attachment/5362386/+files/GrantPermission.png

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

Title:
  Ubuntu 20.04 Dark mode isn't making the GNOME menus dark

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 dark mode is not making the top bar menus dark.
  Also the grant permission dialog is not dark too.

  Where are a lot of guides how to fix it. Users have to install different 
tweaks etc.
  But is it going to be fixed in 20.04?

  See https://www.omgubuntu.co.uk/2020/04/enable-full-dark-mode-in-ubuntu-20-04
  
https://askubuntu.com/questions/1231169/ubuntu-20-04-dark-mode-isnt-making-the-gnome-menus-dark
  https://itsfoss.com/dark-mode-ubuntu/
  
http://ubuntuhandbook.org/index.php/2020/04/dark-gnome-shell-menus-ubuntu-20-04/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 14:00:14 2020
  DisplayManager: gdm3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1874247] [NEW] Don't work wired connection regression focal

[Igor Zubarev]

Public bug reported:

After upgrade to focal I can't connect to wired network. It was ok in
19.10 before

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 22 15:44:52 2020
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 192.168.1.254 dev wlp7s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp7s0 scope link metric 1000 
 192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.67 metric 600
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

Title:
  Don't work wired connection regression focal

Status in network-manager package in Ubuntu:
  New

Bug description:
  After upgrade to focal I can't connect to wired network. It was ok in
  19.10 before

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 15:44:52 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.254 dev wlp7s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp7s0 scope link metric 1000 
   192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.67 metric 600
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1873622] [NEW] Gnome shell 3.36 leaks, eats more memory than 3.34

[Igor Zubarev]

Public bug reported:

Before Beta release and in 3.34 my gnome-shell used 177 MB of memory in
maximum load, currently it begins from 190 MB to 500 MB without reducing
after stop of heavy applications. It seems some plugins or gnome-shell
still are memory hog

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
Uname: Linux 5.4.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 19 08:47:37 2020
DisplayManager: gdm3
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Gnome shell 3.36 leaks, eats more memory than 3.34

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Before Beta release and in 3.34 my gnome-shell used 177 MB of memory
  in maximum load, currently it begins from 190 MB to 500 MB without
  reducing after stop of heavy applications. It seems some plugins or
  gnome-shell still are memory hog

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 19 08:47:37 2020
  DisplayManager: gdm3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1873346] [NEW] Gnome Files icon bug focal

[Igor Zubarev]

Public bug reported:

Gnome Files icon is showing on the light background in gnome-shell, but
all other icons on transparent background. See attached screen

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
Uname: Linux 5.4.0-24-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 16 22:48:17 2020
DisplayManager: gdm3
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Снимок экрана от 2020-04-16 22-46-58.png"
   
https://bugs.launchpad.net/bugs/1873346/+attachment/5355726/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202020-04-16%2022-46-58.png

** Description changed:

- Gnome Files icon is showing on the light background, but all other icons
- on transparent background. See attached screen
+ Gnome Files icon is showing on the light background in gnome-shell, but
+ all other icons on transparent background. See attached screen
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 16 22:48:17 2020
  DisplayManager: gdm3
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=ru_RU.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=ru_RU.UTF-8
+  SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Gnome Files icon bug focal

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Gnome Files icon is showing on the light background in gnome-shell,
  but all other icons on transparent background. See attached screen

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 16 22:48:17 2020
  DisplayManager: gdm3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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] [NEW] Network printer does not print: cups-browsed

[Igor]

Public bug reported:

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

** Affects: cups-filters (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 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:
  New

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/~d

[Desktop-packages] [Bug 1871212] [NEW] Authentication window doesn't use the same theme as gnome-shell

[Igor Zubarev]

Public bug reported:

Authentication window doesn't use the same theme as gnome-shell.

I use dark theme in gnome-shell, but authentication window use light
theme. The problem occurred in Gnome Control Center when I unlocked user
settings. Also the same problem with theming when I created live usb
disk in usb disk creator

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.0-2ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  6 22:16:30 2020
DisplayManager: gdm3
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Снимок экрана от 2020-04-06 22-10-02.png"
   
https://bugs.launchpad.net/bugs/1871212/+attachment/5348033/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202020-04-06%2022-10-02.png

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

Title:
  Authentication window doesn't use the same theme as gnome-shell

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Authentication window doesn't use the same theme as gnome-shell.

  I use dark theme in gnome-shell, but authentication window use light
  theme. The problem occurred in Gnome Control Center when I unlocked
  user settings. Also the same problem with theming when I created live
  usb disk in usb disk creator

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  6 22:16:30 2020
  DisplayManager: gdm3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1870628] Re: Authentication required window after startup

[Igor Zubarev]

Yes, you are right I have two GPUs. GeForce GT 735M supporting Prime and
Intel graphics

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

Title:
  Authentication required window after startup

Status in gnome-keyring package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After I setup auto logging without password in Gnome Control Center I
  got Authentication required window every start of Ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-keyring 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 00:41:50 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1870628] Re: Authentication required window after startup

[Igor Zubarev]

Daniel, I don't know. I use Nvidia 440.64 driver and it works. Also I
disabled animations. May be this is a reason.

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

Title:
  Authentication required window after startup

Status in gnome-keyring package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After I setup auto logging without password in Gnome Control Center I
  got Authentication required window every start of Ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-keyring 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 00:41:50 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1870628] Re: Authentication required window after startup

[Igor Zubarev]

Sebastian, I added file system.journal
If you need I can send you text output 'journalctl -b 0'

** Attachment added: "system.journal"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1870628/+attachment/5347589/+files/system.journal

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

Title:
  Authentication required window after startup

Status in gnome-keyring package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After I setup auto logging without password in Gnome Control Center I
  got Authentication required window every start of Ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-keyring 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 00:41:50 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1870628] Re: Authentication required window after startup

[Igor Zubarev]

Sebastian,

I added the photo from mobile because printscreen didn't work.

** Attachment added: "IMG_20200406_113549.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1870628/+attachment/5347585/+files/IMG_20200406_113549.jpg

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

Title:
  Authentication required window after startup

Status in gnome-keyring package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After I setup auto logging without password in Gnome Control Center I
  got Authentication required window every start of Ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-keyring 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 00:41:50 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1870628] [NEW] Authentication required window after startup

[Igor Zubarev]

Public bug reported:

After I setup auto logging without password in Gnome Control Center I
got Authentication required window every start of Ubuntu

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-keyring 3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  4 00:41:50 2020
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-keyring
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Authentication required window after startup

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  After I setup auto logging without password in Gnome Control Center I
  got Authentication required window every start of Ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-keyring 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 00:41:50 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1870490] [NEW] Don't work deleting files and folders from desktop by press Delete

[Igor Zubarev]

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

Public bug reported:

When I press button Delete for deletion selected folder or file on
desktop nothing happens. Upgraded to 20.04 from 19.10.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell-extension-desktop-icons 19.10.2+git20200223-1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset wl nvidia
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  3 10:23:18 2020
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell-extension-desktop-icons
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Description changed:

  When I press button Delete for deletion selected folder or file on
- desktop nothing happens
+ desktop nothing happens. Upgraded to 20.04 from 19.10.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-desktop-icons 19.10.2+git20200223-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset wl nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 10:23:18 2020
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=ru_RU.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=ru_RU.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Don't work deleting files and folders from desktop by press Delete

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

Bug description:
  When I press button Delete for deletion selected folder or file on
  desktop nothing happens. Upgraded to 20.04 from 19.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-desktop-icons 19.10.2+git20200223-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset wl nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 10:23:18 2020
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1868360] Re: No superuser access window after upgrade to 20.04

[Igor Zubarev]

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

It seems it's a problem of Software and Updates, because I tried to
install apps in Gnome Software, run synaptic etc and it was ok with
password window.

So i think you can mark it as a duplicate of bug #1727908.

** This bug has been marked a duplicate of bug 1727908
   Software & Updates application does not permit changes on the "Other 
Software" tab

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

Title:
  No superuser access window after upgrade to 20.04

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

Bug description:
  After I upgraded to Ubuntu 20.04 I couldn't change settings which
  required superuser access. For example program sources, users etc. If
  I try to change I get no modal window with superuser password.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 21 09:37:05 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: Upgraded to focal on 2020-03-12 (8 days ago)

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

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

[Desktop-packages] [Bug 1868360] Re: No superuser access window after upgrade to 20.04

[Igor Zubarev]

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

I marked as a duplicate of  bug #1727908.

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

Title:
  No superuser access window after upgrade to 20.04

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

Bug description:
  After I upgraded to Ubuntu 20.04 I couldn't change settings which
  required superuser access. For example program sources, users etc. If
  I try to change I get no modal window with superuser password.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 21 09:37:05 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: Upgraded to focal on 2020-03-12 (8 days ago)

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

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

[Desktop-packages] [Bug 1868360] Re: No superuser access window after upgrade to 20.04

[Igor Zubarev]

Very strange. It doesn't work in Software and Updates when I push checkboxes in 
Other software.
But works in Control Center-> Users when click Unlock.

Also I remember that before last update it worked also in Software and
Updates

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

Title:
  No superuser access window after upgrade to 20.04

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

Bug description:
  After I upgraded to Ubuntu 20.04 I couldn't change settings which
  required superuser access. For example program sources, users etc. If
  I try to change I get no modal window with superuser password.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 21 09:37:05 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: Upgraded to focal on 2020-03-12 (8 days ago)

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

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

[Desktop-packages] [Bug 1868529] Re: Stretched picture or pdf preview icon on desktop

[Igor Zubarev]

** Description changed:

  After upgrade to 20.04 desktop previews of pictures and documents became
- stretched. See attach pic
+ stretched. The regular previews in Nautilus have normal sizes. See
+ attach pic
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-desktop-icons 19.10.2+git20200223-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 23 11:44:13 2020
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=ru_RU.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=ru_RU.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  After upgrade to 20.04 desktop previews of pictures and documents became
  stretched. The regular previews in Nautilus have normal sizes. See
- attach pic
+ attached pic
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-desktop-icons 19.10.2+git20200223-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 23 11:44:13 2020
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Stretched picture or pdf preview icon on desktop

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

Bug description:
  After upgrade to 20.04 desktop previews of pictures and documents
  became stretched. The regular previews in Nautilus have normal sizes.
  See attached pic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-desktop-icons 19.10.2+git20200223-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 23 11:44:13 2020
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1868529] Re: Stretched picture or pdf preview icon on desktop

[Igor Zubarev]

** Attachment added: "Снимок экрана от 2020-03-23 11-43-59.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1868529/+attachment/5340361/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202020-03-23%2011-43-59.png

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

Title:
  Stretched picture or pdf preview icon on desktop

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

Bug description:
  After upgrade to 20.04 desktop previews of pictures and documents
  became stretched. See attach pic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-desktop-icons 19.10.2+git20200223-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 23 11:44:13 2020
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1868529] [NEW] Stretched picture or pdf preview icon on desktop

[Igor Zubarev]

Public bug reported:

After upgrade to 20.04 desktop previews of pictures and documents became
stretched. See attach pic

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell-extension-desktop-icons 19.10.2+git20200223-1
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 23 11:44:13 2020
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell-extension-desktop-icons
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Stretched picture or pdf preview icon on desktop

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

Bug description:
  After upgrade to 20.04 desktop previews of pictures and documents
  became stretched. See attach pic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-desktop-icons 19.10.2+git20200223-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 23 11:44:13 2020
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1868360] Re: No superuser access window after upgrade to 20.04

[Igor Zubarev]

Yes. Here is output:

$ gnome-control-center user-accounts

(gnome-control-center:5010): Gtk-WARNING **: 09:47:51.316: Error
acquiring permission: Failed to acquire permission for action-id
org.gnome.controlcenter.user-accounts.administration

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

Title:
  No superuser access window after upgrade to 20.04

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

Bug description:
  After I upgraded to Ubuntu 20.04 I couldn't change settings which
  required superuser access. For example program sources, users etc. If
  I try to change I get no modal window with superuser password.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 21 09:37:05 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: Upgraded to focal on 2020-03-12 (8 days ago)

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

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

[Desktop-packages] [Bug 1868360] Re: No superuser access window after upgrade to 20.04

[Igor Zubarev]

** Attachment added: "system.journal"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1868360/+attachment/5339877/+files/system.journal

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

Title:
  No superuser access window after upgrade to 20.04

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

Bug description:
  After I upgraded to Ubuntu 20.04 I couldn't change settings which
  required superuser access. For example program sources, users etc. If
  I try to change I get no modal window with superuser password.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 21 09:37:05 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: Upgraded to focal on 2020-03-12 (8 days ago)

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

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

[Desktop-packages] [Bug 1868360] Re: No superuser access window after upgrade to 20.04

[Igor Zubarev]

** Attachment removed: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1868360/+attachment/5339876/+files/journal.txt

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

Title:
  No superuser access window after upgrade to 20.04

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

Bug description:
  After I upgraded to Ubuntu 20.04 I couldn't change settings which
  required superuser access. For example program sources, users etc. If
  I try to change I get no modal window with superuser password.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 21 09:37:05 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: Upgraded to focal on 2020-03-12 (8 days ago)

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

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

[Desktop-packages] [Bug 1868360] Re: No superuser access window after upgrade to 20.04

[Igor Zubarev]

Also see attached output after I type 'journalctl -b 0'


** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1868360/+attachment/5339876/+files/journal.txt

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

Title:
  No superuser access window after upgrade to 20.04

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

Bug description:
  After I upgraded to Ubuntu 20.04 I couldn't change settings which
  required superuser access. For example program sources, users etc. If
  I try to change I get no modal window with superuser password.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 21 09:37:05 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: Upgraded to focal on 2020-03-12 (8 days ago)

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

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

[Desktop-packages] [Bug 1868360] Re: No superuser access window after upgrade to 20.04

[Igor Zubarev]

Firstly, when I go to Control Center-> Users and click Unlock I see
background dark window and after that temporary see Gnome Ubuntu initial
login screen and it disappears.

I expected to see authorization dialog but nothing happened.
Also I found new gnome-shell crash report in var/crash/
See attached file  

** Attachment added: "_usr_bin_gnome-shell.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1868360/+attachment/5339875/+files/_usr_bin_gnome-shell.1000.crash

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

Title:
  No superuser access window after upgrade to 20.04

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

Bug description:
  After I upgraded to Ubuntu 20.04 I couldn't change settings which
  required superuser access. For example program sources, users etc. If
  I try to change I get no modal window with superuser password.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 21 09:37:05 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: Upgraded to focal on 2020-03-12 (8 days ago)

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

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

[Desktop-packages] [Bug 1868360] [NEW] No superuser access window after upgrade to 20.04

[Igor Zubarev]

Public bug reported:

After I upgraded to Ubuntu 20.04 I couldn't change settings which
required superuser access. For example program sources, users etc. If I
try to change I get no modal window with superuser password.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-screensaver (not installed)
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 21 09:37:05 2020
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-screensaver
Symptom: security
Title: Screen locking issue
UpgradeStatus: Upgraded to focal on 2020-03-12 (8 days ago)

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

Title:
  No superuser access window after upgrade to 20.04

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  After I upgraded to Ubuntu 20.04 I couldn't change settings which
  required superuser access. For example program sources, users etc. If
  I try to change I get no modal window with superuser password.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 21 09:37:05 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: Upgraded to focal on 2020-03-12 (8 days ago)

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

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

[Desktop-packages] [Bug 1867352] [NEW] Xorg freeze after boot if use xorg.conf generated by nvidia-xconfig

[Igor Zubarev]

Public bug reported:

Hello!

I have constant X crash if use xorg.conf generated by nvidia-xconfig.
Currently my xorg.conf is absent. Only if I have an empty conf file or it is 
absent I can start X.
The problem exists in 19.10 and 20.04 development version

Also I have strange messages if I run nvidia-xconfig:
$ sudo nvidia-xconfig

WARNING: Unable to locate/open X configuration file.

Package xorg-server was not found in the pkg-config search path.
Perhaps you should add the directory containing `xorg-server.pc'
to the PKG_CONFIG_PATH environment variable
No package 'xorg-server' found
New X configuration file written to '/etc/X11/xorg.conf'


Here is my xorg.conf generated by nvidia:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 440.64

Section "ServerLayout"
Identifier "Layout0"
Screen  0  "Screen0"
InputDevice"Keyboard0" "CoreKeyboard"
InputDevice"Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName  "Unknown"
Option "DPMS"
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor"Monitor0"
DefaultDepth24
SubSection "Display"
Depth   24
EndSubSection
EndSection

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:  gcc version 9.2.1 20200304 (Ubuntu 9.2.1-31ubuntu1)
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 13 16:44:45 2020
DistUpgraded: 2020-03-13 00:50:36,699 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed
 nvidia, 440.64, 5.4.0-14-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: I don't know
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation 3rd Gen Core processor Graphics Controller 
[104d:90b7]
   Subsystem: Sony Corporation GK208M [GeForce GT 735M] [104d:90b7]
MachineType: Sony Corporation SVF15A1S9RB
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=81c8a442-a191-4c83-b415-ee0f1f2b0b81 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-03-12 (0 days ago)
dmi.bios.date: 07/19/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R0250DA
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0250DA:bd07/19/2016:svnSonyCorporation:pnSVF15A1S9RB:pvrC10H9CDB:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: VAIO
dmi.product.name: SVF15A1S9RB
dmi.product.sku: 54581586
dmi.product.version: C10H9CDB
dmi.sys.vendor: Sony Corporation
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1

[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

[Igor Maric]

This is a huge issue in business environment. I can't understand that we
don't have this in 2020 when all other platform has it and even now its
importance is a wishlist? Come on! It's impossible to have a
conversation using Bluetooth, audio is unusable.

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

[Igor Voldiner]

Having the same issue on the same machine and would be extremely happy
if there is any help or advances in this regard.

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

Title:
  [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Running the command alsamixer allows me to manually increase the sound levels 
for the headset, and sound plays properly through them. This requires me to 
disable the auto-mute feature.
  I haven't rebooted my system yet to see if this is permanent.
  But the UI doesn't show the heaphones at all and only sends sound through the 
main speakers of the laptop.

  ➜  ~ lspci -nnk | grep -i -A7 audio
  00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

  ➜  ~ cat /proc/asound/card0/codec* | grep Codec 
  Codec: Realtek ALC256
  Codec: Intel Kabylake HDMI

  Using for example pavucontrol allows me to select the headphone, which are 
marked as unplugged, and I can play audio through them as long as I keep the 
application open.
  If I reboot or close pavucontrol, everything is back to the original state 
and only the speakers work.

  Additional Information:

  ➜  ~ lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  What I expect to happen:

  When I plug in my headphones, Ubuntu and the UI should see them and
  automatically redirect all sound through them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   olivar 8320 F...m pulseaudio
   /dev/snd/controlC0:  olivar 8320 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec  6 13:02:14 2018
  InstallationDate: Installed on 2018-11-21 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 01.01
  dmi.board.name: DANA_MB
  dmi.board.vendor: Razer
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr:
  dmi.product.family: 1A582001 Razer Blade
  dmi.product.name: Blade
  dmi.product.version: 1.04
  dmi.sys.vendor: Razer

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

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

[Desktop-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

[Igor Grkavac]

Hey guys,

I also experienced this problem, but after increasing swap memory from
2GB to 8GB, I didn't reproduce the issue for 1 month straight.

Hope this helps,

Igor D. Grkavac.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in xserver-xorg-video-intel source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Triaged
Status in xserver-xorg-video-intel source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Triaged
Status in xserver-xorg-video-intel source package in Disco:
  Invalid

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1854578] xserver.devices.txt

[igor tokarev]

apport information

** Attachment added: "xserver.devices.txt"
   
https://bugs.launchpad.net/bugs/1854578/+attachment/5308928/+files/xserver.devices.txt

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

Title:
  Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

Status in xorg package in Ubuntu:
  New

Bug description:
  The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
  move the brightness bar in that window, but actual screen brightness
  does not change. Also, the touchpad does not work at all, however a
  few times it did work after a reboot without any recognisable change
  in the driver or system settings.

  Ubuntu driver does not load after Ubuntu upgrade (now upgraded to
  19.10) and only starts to work (giving required screen resolution)
  only after installing lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov 30 18:09:10 2019
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-30 (0 days ago)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VM.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VM
  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.:bvrG752VM.308:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Nov 30 17:38:28 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for pci::01:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release 

[Desktop-packages] [Bug 1854578] ProcCpuinfoMinimal.txt

[igor tokarev]

apport information

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

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

Title:
  Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

Status in xorg package in Ubuntu:
  New

Bug description:
  The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
  move the brightness bar in that window, but actual screen brightness
  does not change. Also, the touchpad does not work at all, however a
  few times it did work after a reboot without any recognisable change
  in the driver or system settings.

  Ubuntu driver does not load after Ubuntu upgrade (now upgraded to
  19.10) and only starts to work (giving required screen resolution)
  only after installing lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov 30 18:09:10 2019
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-30 (0 days ago)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VM.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VM
  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.:bvrG752VM.308:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Nov 30 17:38:28 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for pci::01:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - 

[Desktop-packages] [Bug 1854578] XorgLogOld.txt

[igor tokarev]

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1854578/+attachment/5308925/+files/XorgLogOld.txt

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

Title:
  Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

Status in xorg package in Ubuntu:
  New

Bug description:
  The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
  move the brightness bar in that window, but actual screen brightness
  does not change. Also, the touchpad does not work at all, however a
  few times it did work after a reboot without any recognisable change
  in the driver or system settings.

  Ubuntu driver does not load after Ubuntu upgrade (now upgraded to
  19.10) and only starts to work (giving required screen resolution)
  only after installing lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov 30 18:09:10 2019
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-30 (0 days ago)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VM.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VM
  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.:bvrG752VM.308:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Nov 30 17:38:28 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for pci::01:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 

[Desktop-packages] [Bug 1854578] ProcCpuinfo.txt

[igor tokarev]

apport information

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

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

Title:
  Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

Status in xorg package in Ubuntu:
  New

Bug description:
  The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
  move the brightness bar in that window, but actual screen brightness
  does not change. Also, the touchpad does not work at all, however a
  few times it did work after a reboot without any recognisable change
  in the driver or system settings.

  Ubuntu driver does not load after Ubuntu upgrade (now upgraded to
  19.10) and only starts to work (giving required screen resolution)
  only after installing lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov 30 18:09:10 2019
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-30 (0 days ago)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VM.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VM
  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.:bvrG752VM.308:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Nov 30 17:38:28 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for pci::01:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 

[Desktop-packages] [Bug 1854578] Xrandr.txt

[igor tokarev]

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1854578/+attachment/5308926/+files/Xrandr.txt

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

Title:
  Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

Status in xorg package in Ubuntu:
  New

Bug description:
  The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
  move the brightness bar in that window, but actual screen brightness
  does not change. Also, the touchpad does not work at all, however a
  few times it did work after a reboot without any recognisable change
  in the driver or system settings.

  Ubuntu driver does not load after Ubuntu upgrade (now upgraded to
  19.10) and only starts to work (giving required screen resolution)
  only after installing lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov 30 18:09:10 2019
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-30 (0 days ago)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VM.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VM
  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.:bvrG752VM.308:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Nov 30 17:38:28 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for pci::01:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  

[Desktop-packages] [Bug 1854578] UdevDb.txt

[igor tokarev]

apport information

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

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

Title:
  Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

Status in xorg package in Ubuntu:
  New

Bug description:
  The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
  move the brightness bar in that window, but actual screen brightness
  does not change. Also, the touchpad does not work at all, however a
  few times it did work after a reboot without any recognisable change
  in the driver or system settings.

  Ubuntu driver does not load after Ubuntu upgrade (now upgraded to
  19.10) and only starts to work (giving required screen resolution)
  only after installing lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov 30 18:09:10 2019
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-30 (0 days ago)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VM.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VM
  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.:bvrG752VM.308:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Nov 30 17:38:28 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for pci::01:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  

[Desktop-packages] [Bug 1854578] UnitySupportTest.txt

[igor tokarev]

apport information

** Attachment added: "UnitySupportTest.txt"
   
https://bugs.launchpad.net/bugs/1854578/+attachment/5308923/+files/UnitySupportTest.txt

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

Title:
  Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

Status in xorg package in Ubuntu:
  New

Bug description:
  The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
  move the brightness bar in that window, but actual screen brightness
  does not change. Also, the touchpad does not work at all, however a
  few times it did work after a reboot without any recognisable change
  in the driver or system settings.

  Ubuntu driver does not load after Ubuntu upgrade (now upgraded to
  19.10) and only starts to work (giving required screen resolution)
  only after installing lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov 30 18:09:10 2019
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-30 (0 days ago)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VM.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VM
  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.:bvrG752VM.308:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Nov 30 17:38:28 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for pci::01:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release 

[Desktop-packages] [Bug 1854578] xdpyinfo.txt

[igor tokarev]

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1854578/+attachment/5308927/+files/xdpyinfo.txt

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

Title:
  Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

Status in xorg package in Ubuntu:
  New

Bug description:
  The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
  move the brightness bar in that window, but actual screen brightness
  does not change. Also, the touchpad does not work at all, however a
  few times it did work after a reboot without any recognisable change
  in the driver or system settings.

  Ubuntu driver does not load after Ubuntu upgrade (now upgraded to
  19.10) and only starts to work (giving required screen resolution)
  only after installing lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov 30 18:09:10 2019
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-30 (0 days ago)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VM.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VM
  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.:bvrG752VM.308:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Nov 30 17:38:28 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for pci::01:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
 

[Desktop-packages] [Bug 1854578] XorgLog.txt

[igor tokarev]

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1854578/+attachment/5308924/+files/XorgLog.txt

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

Title:
  Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

Status in xorg package in Ubuntu:
  New

Bug description:
  The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
  move the brightness bar in that window, but actual screen brightness
  does not change. Also, the touchpad does not work at all, however a
  few times it did work after a reboot without any recognisable change
  in the driver or system settings.

  Ubuntu driver does not load after Ubuntu upgrade (now upgraded to
  19.10) and only starts to work (giving required screen resolution)
  only after installing lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov 30 18:09:10 2019
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-30 (0 days ago)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VM.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VM
  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.:bvrG752VM.308:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Nov 30 17:38:28 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for pci::01:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  

[Desktop-packages] [Bug 1854578] ProcModules.txt

[igor tokarev]

apport information

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

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

Title:
  Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

Status in xorg package in Ubuntu:
  New

Bug description:
  The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
  move the brightness bar in that window, but actual screen brightness
  does not change. Also, the touchpad does not work at all, however a
  few times it did work after a reboot without any recognisable change
  in the driver or system settings.

  Ubuntu driver does not load after Ubuntu upgrade (now upgraded to
  19.10) and only starts to work (giving required screen resolution)
  only after installing lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov 30 18:09:10 2019
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-30 (0 days ago)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VM.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VM
  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.:bvrG752VM.308:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Nov 30 17:38:28 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for pci::01:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 

[Desktop-packages] [Bug 1854578] ProcEnviron.txt

[igor tokarev]

apport information

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

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

Title:
  Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

Status in xorg package in Ubuntu:
  New

Bug description:
  The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
  move the brightness bar in that window, but actual screen brightness
  does not change. Also, the touchpad does not work at all, however a
  few times it did work after a reboot without any recognisable change
  in the driver or system settings.

  Ubuntu driver does not load after Ubuntu upgrade (now upgraded to
  19.10) and only starts to work (giving required screen resolution)
  only after installing lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov 30 18:09:10 2019
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-30 (0 days ago)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VM.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VM
  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.:bvrG752VM.308:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Nov 30 17:38:28 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for pci::01:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 

[Desktop-packages] [Bug 1854578] ProcInterrupts.txt

[igor tokarev]

apport information

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

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

Title:
  Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

Status in xorg package in Ubuntu:
  New

Bug description:
  The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
  move the brightness bar in that window, but actual screen brightness
  does not change. Also, the touchpad does not work at all, however a
  few times it did work after a reboot without any recognisable change
  in the driver or system settings.

  Ubuntu driver does not load after Ubuntu upgrade (now upgraded to
  19.10) and only starts to work (giving required screen resolution)
  only after installing lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov 30 18:09:10 2019
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-30 (0 days ago)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VM.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VM
  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.:bvrG752VM.308:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Nov 30 17:38:28 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for pci::01:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 

[Desktop-packages] [Bug 1854578] DpkgLog.txt

[igor tokarev]

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1854578/+attachment/5308914/+files/DpkgLog.txt

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

Title:
  Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

Status in xorg package in Ubuntu:
  New

Bug description:
  The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
  move the brightness bar in that window, but actual screen brightness
  does not change. Also, the touchpad does not work at all, however a
  few times it did work after a reboot without any recognisable change
  in the driver or system settings.

  Ubuntu driver does not load after Ubuntu upgrade (now upgraded to
  19.10) and only starts to work (giving required screen resolution)
  only after installing lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov 30 18:09:10 2019
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-30 (0 days ago)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VM.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VM
  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.:bvrG752VM.308:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Nov 30 17:38:28 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for pci::01:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  

[Desktop-packages] [Bug 1854578] CurrentDmesg.txt

[igor tokarev]

apport information

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

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

Title:
  Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

Status in xorg package in Ubuntu:
  New

Bug description:
  The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
  move the brightness bar in that window, but actual screen brightness
  does not change. Also, the touchpad does not work at all, however a
  few times it did work after a reboot without any recognisable change
  in the driver or system settings.

  Ubuntu driver does not load after Ubuntu upgrade (now upgraded to
  19.10) and only starts to work (giving required screen resolution)
  only after installing lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov 30 18:09:10 2019
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-30 (0 days ago)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VM.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VM
  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.:bvrG752VM.308:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Nov 30 17:38:28 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for pci::01:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 

[Desktop-packages] [Bug 1854578] Lspci.txt

[igor tokarev]

apport information

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

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

Title:
  Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

Status in xorg package in Ubuntu:
  New

Bug description:
  The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
  move the brightness bar in that window, but actual screen brightness
  does not change. Also, the touchpad does not work at all, however a
  few times it did work after a reboot without any recognisable change
  in the driver or system settings.

  Ubuntu driver does not load after Ubuntu upgrade (now upgraded to
  19.10) and only starts to work (giving required screen resolution)
  only after installing lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov 30 18:09:10 2019
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-30 (0 days ago)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VM.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VM
  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.:bvrG752VM.308:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Nov 30 17:38:28 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for pci::01:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  

[Desktop-packages] [Bug 1854578] Dependencies.txt

[igor tokarev]

apport information

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

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

Title:
  Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

Status in xorg package in Ubuntu:
  New

Bug description:
  The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
  move the brightness bar in that window, but actual screen brightness
  does not change. Also, the touchpad does not work at all, however a
  few times it did work after a reboot without any recognisable change
  in the driver or system settings.

  Ubuntu driver does not load after Ubuntu upgrade (now upgraded to
  19.10) and only starts to work (giving required screen resolution)
  only after installing lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov 30 18:09:10 2019
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-30 (0 days ago)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VM.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VM
  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.:bvrG752VM.308:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Nov 30 17:38:28 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for pci::01:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 

[Desktop-packages] [Bug 1854578] Lsusb.txt

[igor tokarev]

apport information

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

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

Title:
  Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

Status in xorg package in Ubuntu:
  New

Bug description:
  The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
  move the brightness bar in that window, but actual screen brightness
  does not change. Also, the touchpad does not work at all, however a
  few times it did work after a reboot without any recognisable change
  in the driver or system settings.

  Ubuntu driver does not load after Ubuntu upgrade (now upgraded to
  19.10) and only starts to work (giving required screen resolution)
  only after installing lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov 30 18:09:10 2019
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-30 (0 days ago)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VM.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VM
  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.:bvrG752VM.308:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Nov 30 17:38:28 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for pci::01:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  

[Desktop-packages] [Bug 1854578] Re: Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

[igor tokarev]

apport information

** Tags added: apport-collected

** Description changed:

  The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
  move the brightness bar in that window, but actual screen brightness
  does not change. Also, the touchpad does not work at all, however a few
  times it did work after a reboot without any recognisable change in the
  driver or system settings.
  
  Ubuntu driver does not load after Ubuntu upgrade (now upgraded to 19.10)
  and only starts to work (giving required screen resolution) only after
  installing lightdm.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov 30 18:09:10 2019
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-30 (0 days ago)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VM.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VM
  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.:bvrG752VM.308:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Nov 30 17:38:28 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for pci::01:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
+ --- 
+ ProblemType: Bug
+ .tmp.unity_support_test.1:
+  
+ ApportVersion: 2.20.11-0ubuntu8.2
+ Architecture: amd64
+ CompositorRunning: None
+ DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
+ DistroCodename: eoan
+ DistroRelease: Ubuntu 19.10
+ DistroVariant: ubuntu
+ DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
+ ExtraDebuggingInterest: Yes, if not too technical
+ GraphicsCard:
+  NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
+Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
+ InstallationDate: Installed on 2017-03-08 (996 days ago)
+ InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ MachineType: ASUSTeK COMPUTER INC. G752VM
+ Package: xorg 1:7.7+19ubuntu12
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
+ ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
+ Tags: third-party-packages eoan 

[Desktop-packages] [Bug 1854578] [NEW] Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

[igor tokarev]

*** This bug is a security vulnerability ***

Public security bug reported:

The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
move the brightness bar in that window, but actual screen brightness
does not change. Also, the touchpad does not work at all, however a few
times it did work after a reboot without any recognisable change in the
driver or system settings.

Ubuntu driver does not load after Ubuntu upgrade (now upgraded to 19.10)
and only starts to work (giving required screen resolution) only after
installing lightdm.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CompositorRunning: None
Date: Sat Nov 30 18:09:10 2019
DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
InstallationDate: Installed on 2017-03-08 (996 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: ASUSTeK COMPUTER INC. G752VM
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to eoan on 2019-11-30 (0 days ago)
dmi.bios.date: 04/24/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VM.308
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VM
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.:bvrG752VM.308:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G752VM
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Sat Nov 30 17:38:28 2019
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 [drm] Failed to open DRM device for pci::01:00.0: -19
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.20.5+git20191008-0ubuntu1

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


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

** Information type changed from Public to Public Security

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

Title:
  Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

Status in xorg package in Ubuntu:
  New

Bug description:
  The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
  move the brightness bar in that window, but actual screen brightness
  does not change. Also, the touchpad does not work at all, however a
  few times it did work after a reboot without any recognisable change
  in the driver or system settings.

  Ubuntu driver does not load after Ubuntu upgrade (now upgraded to
  19.10) and only starts to work (giving required screen resolution)
  only after installing lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov 30 18:09:10 2019
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py 

[Desktop-packages] [Bug 874535] Re: Volume Slider Jumps, due to rapidly changing hardware jack sense state

[Igor Tverdovskiy]

UPDATE:
even after disconnection of the front audio panel, the issue still happens once 
in a blue moon:
Left pulseaudio in debug mode for several days after fix:

$ tail -f /tmp/pulseaudio.log | grep is.now

(3284.252|  96.036) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(3285.280|   1.006) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(4430.108| 136.098) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(4431.133|   1.003) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(65064.220|  35.638) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(65065.244|   1.023) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(163655.996|  23.995) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(163657.020|   1.023) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(166826.748|   0.027) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(166827.772|   0.712) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(170071.580|   2.337) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(170072.605|   0.483) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(170196.156|  63.020) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(170197.180|   1.022) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(173292.956| 110.638) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(173293.980|   1.023) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(405426.784|  13.234) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(405427.804|   0.998) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(501250.208|  28.079) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(501251.228|   1.018) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(508205.532|   1.475) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(508206.556|   1.022) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(576198.464|  60.134) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(576199.484|   1.018) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(577215.964|   3.252) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(577216.992|   0.726) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(577250.780|  26.097) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(577251.804|   1.022) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(577291.740|   0.147) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(577292.764|   0.515) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(577495.964|  54.201) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(577496.988|   1.023) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(578591.196| 137.355) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(578592.220|   1.022) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(589797.436|   1.779) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(589798.460|   1.022) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(589802.556|   4.095) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(589803.580|   1.022) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(593142.972| 274.353) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(593143.996|   1.002) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(593435.804| 267.849) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(593436.832|   1.005) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(594411.680|  25.302) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(594412.700|   1.001) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
(594960.540|  37.896) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
(594961.564|   1.002) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now 

[Desktop-packages] [Bug 1798790] Re: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it)

[Igor Yakushin]

I have Dell 7530 with Nvidia Quadro P3200 (nvidia driver 418.74),
running Ubuntu 18.04 (with all the latest updates) and I observe the
same thing: with power cable it boots fine and without it gets stuck on
"bpfilter started".

WaylandEnable=false
was already uncommented in /etc/gdm3/custom.conf.

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

Title:
  Ubuntu login screen never appears when using the Nvidia driver (and
  setting WaylandEnable=false fixes it)

Status in gdm:
  Fix Released
Status in gdm3 package in Ubuntu:
  In Progress
Status in gnome-session package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Invalid
Status in gdm3 source package in Eoan:
  In Progress
Status in gnome-session source package in Eoan:
  In Progress
Status in gnome-shell source package in Eoan:
  In Progress
Status in mutter source package in Eoan:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/gdm/issues/483
  formerly https://gitlab.gnome.org/GNOME/gdm/issues/435

  ---

  The boot process hangs with the last message being "started bpfilter".
  There is unusual Network activity during that time. The light of the
  WiFi adapter is blinking a lot.

  I am not sure the problem is with the gdm3 package. As a matter of
  fact, I would remove it and let someone more experienced to set it.
  I'm afraid I might break something, though.

  The specific steps or actions you took that caused you to encounter the 
problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers
  installed.

  The behavior you expected: I expected Ubuntu 18.10 to boot normally.

  The behavior you actually encountered: The computer gets stuck in a
  command-like environment with the last message being "started
  bpfilter". You can't type any commands.

  I have found that uninstalling the Nvidia proprietary drivers by going
  into recovery mode fixes the issue.

  Booting with the earlier kernel doesn't fix the issue. Installing the
  earlier v.340 driver also doesn't fix the issue.

  This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in-
  boot-after-starting-gnome-display-manager-on-intel-graphic) seems
  relevant. This is where I found the "solution".

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

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

[Desktop-packages] [Bug 874535] Re: Volume Slider Jumps, due to rapidly changing hardware jack sense state

[Igor Tverdovskiy]

Hi,

The same on Kubuntu 18.04

Tried kernels:
uname -r
4.20.17-042017-generic

uname -r
5.1.6-050106-generic

Hardware:
Base Board Information
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: AB350M-D3H-CF

Realtek® ALC887 codec

Headphones are connected on the backward.

Log according to 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/874535/comments/33:
tail -f /tmp/pulseaudio.log | grep is.now
( 241.947|   0.019) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
( 269.853|  27.904) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
( 269.874|   0.019) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
( 274.694|   4.818) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
( 274.716|   0.018) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
( 276.145|   1.427) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
( 276.166|   0.019) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged
( 276.251|   0.083) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now plugged in
( 276.272|   0.019) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 
Jack' is now unplugged


In fact I don't have jack in 'Front Headphone Jack', my jack is plugged in 
'Line Out Jack':
manual testing by plug/unplug
(1692.464|  35.788) D: [pulseaudio] module-alsa-card.c: Jack 'Line Out Jack' is 
now unplugged
(1693.627|   1.148) D: [pulseaudio] module-alsa-card.c: Jack 'Line Out Jack' is 
now plugged in

1) Fix did not help:
> Then edit /etc/modprobe.d/alsa-base.conf and add this line:
> options snd-hda-intel jackpoll_ms=250
However this fix (or maybe together with the second fix) made sound 
interruptions to appear more rarely (e.g. once in a minute instead of once in 
several seconds). 
Tried jackpoll_ms=250,250 and jackpoll_ms=1000,1000

2) Fix did not help either:
Commenting out the following in the
/usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf

#[Jack Front Headphone]
#required-any = any

#[Jack Headphone]
#required-any = any

3) Fix did not help:
ALSA level: start alsamixer in a terminal and change "Automute mode" to 
"disabled"
On my system I basically don't have 'Automute mode' option

4) The only solution helped is to physically disconnect front panel
audio connector on the motherboard. Only then those sound cracking and
popping disappeared completely.

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

Title:
  Volume Slider Jumps, due to rapidly changing hardware jack sense state

Status in alsa-driver package in Ubuntu:
  Triaged

Bug description:
  In Oneiric Release,  The volume slider randomly jump down a notch or
  two for fraction of  a second, even when there is no audio playing on
  the system.  If mute is selected, the menu will quickly flip out of
  mute mode and back again.  This change actually affects the audio
  output, resulting in pops correlated with the volume changes.

  nVidia GF106 Audio Controller
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC892 Analog [ALC892 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jfrorie9959 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfb9f8000 irq 54'
 Mixer name : 'Realtek ALC892'
 Components : 'HDA:10ec0892,1462522c,00100302'
 Controls  : 35
 Simple ctrls  : 20
  Card2.Amixer.info:
   Card hw:2 'Generic'/'HD-Audio Generic at 0xfbcf8000 irq 55'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 4
 Simple ctrls  : 1
  Card2.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  DistroRelease: Ubuntu 11.10
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  Package: pulseaudio 1:1.0-0ubuntu3.1
  PackageArchitecture: amd64
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-14-generic x86_64
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (82 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 11/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.0
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: X58A-GD45 (MS-7522)
  

[Desktop-packages] [Bug 1819048] [NEW] PCI/internal sound card not detected

[Igor]

Public bug reported:

No sound, i.e. sound card not properly detected
can't really say much about that - tried to google
for intel corporation device 2284 and there are postings about
a working driver which i couldn't track down

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-165.215-generic 3.13.11-ckt39
Uname: Linux 3.13.0-165-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Thu Mar  7 20:37:39 2019
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
InstallationDate: Installed on 2018-01-21 (410 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 4.2.0
dmi.board.name: 0M08DC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr4.2.0:bd10/27/2017:svnDellInc.:pnInspiron15-3552:pvr4.2.0:rvnDellInc.:rn0M08DC:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 15-3552
dmi.product.version: 4.2.0
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug trusty

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound, i.e. sound card not properly detected
  can't really say much about that - tried to google
  for intel corporation device 2284 and there are postings about
  a working driver which i couldn't track down

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-165.215-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-165-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Thu Mar  7 20:37:39 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2018-01-21 (410 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 4.2.0
  dmi.board.name: 0M08DC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr4.2.0:bd10/27/2017:svnDellInc.:pnInspiron15-3552:pvr4.2.0:rvnDellInc.:rn0M08DC:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 15-3552
  dmi.product.version: 4.2.0
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1815874] [NEW] [snap] Libreoffice contextual groups menu text cropping

[Igor Ljubuncic]

Public bug reported:

LibreOffice 6.0.2 shows truncated/cropped text on some options in the
contextual grouped menu (notebook bar). See attached. Notice words like
Italic, Underlined, Left, etc.

This with 96dpi on 1920x1080p resolution, Enabled anti-aliasing with
rgba/slight hinting in Plasma on Kubuntu 18.04 with the Breeze theme,
and Sifr icon theme in LibreOffice.

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


** Tags: libreoffice notebookbar snap

** Attachment added: "lo-cropped-text-contextual-groups.png"
   
https://bugs.launchpad.net/bugs/1815874/+attachment/5238561/+files/lo-cropped-text-contextual-groups.png

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

Title:
  [snap] Libreoffice contextual groups menu text cropping

Status in libreoffice package in Ubuntu:
  New

Bug description:
  LibreOffice 6.0.2 shows truncated/cropped text on some options in the
  contextual grouped menu (notebook bar). See attached. Notice words
  like Italic, Underlined, Left, etc.

  This with 96dpi on 1920x1080p resolution, Enabled anti-aliasing with
  rgba/slight hinting in Plasma on Kubuntu 18.04 with the Breeze theme,
  and Sifr icon theme in LibreOffice.

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

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

[Desktop-packages] [Bug 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts

[Telmenko Igor Valerievish]

Why does it not in default settings?

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts

Status in gnome-control-center:
  Unknown
Status in X.Org X server:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  This is a bug about shortcuts mapped to combinations which include
  each other.

  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press  (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)

  The expected behavior is to fire shortcuts on the release (not on
  press) of the special keys (ctrl,shift,alt, etc) which is also how
  Windows behave. This is a serious problem for bilingual layouts,
  typically using Alt+Shift or Ctrl+Shift for keyboard layout change.

  For users being affected by this problem, the easiest solution for now is to 
add this PPA in your repositories:
  https://launchpad.net/~oded-geek/+archive/xorg-patches

  Practical summary of this bug for ubuntu developers (since reading 120 
comments is impractical for most):
  This problem is a really old (since 2004) issue of the xkb part of xorg; the 
main discussion was made upstream in freedesktop-bugs #865. There has been a 
patch from Ilya Murav'jov for upstream (#55), and attached here (#61).
  Upstream xorg has refused to apply the patch, mainly because it "explicitly 
contradicts the (xkb) spec"  (#84, #91).
  This patch has been reported to work for many people without any problems, 
and there is also a PPA by Oded Arbel (#95) where he maintains a patched 
version of the ubuntu xorg.
  The proper resolution of this bug would be to apply this patch to the 
upstream xorg, or at minimum to the official ubuntu xorg package.

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

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

[Desktop-packages] [Bug 1801699] [NEW] Gnome Software Snap Store sign in action is ambiguous

[Igor Ljubuncic]

Public bug reported:

In Ubuntu 18.10, Gnome Software has the option to sign in to Snap Store.

This option is ambiguous as it may lead users to believe they need to
sign in to interact with snaps.

The sign in should either lead to clearly defined activity (e.g.
download, account sync, etc) or not be shown.

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


** Tags: gnome gnome-software in sign snap software

** Attachment added: "gnome-software.png"
   
https://bugs.launchpad.net/bugs/1801699/+attachment/5209273/+files/gnome-software.png

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

Title:
  Gnome Software Snap Store sign in action is ambiguous

Status in gnome-software package in Ubuntu:
  New

Bug description:
  In Ubuntu 18.10, Gnome Software has the option to sign in to Snap
  Store.

  This option is ambiguous as it may lead users to believe they need to
  sign in to interact with snaps.

  The sign in should either lead to clearly defined activity (e.g.
  download, account sync, etc) or not be shown.

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

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

[Desktop-packages] [Bug 1725779] Re: Gnome network manager cannot find authentication binary

[Igor Shuvalov]

It's very strange, but I've just execute apt update && apt upgrade, reboot. And 
now vpnc works fine!
My issue solved

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

Title:
  Gnome network manager cannot find authentication binary

Status in network-manager-pptp package in Ubuntu:
  Confirmed
Status in network-manager-ssh package in Ubuntu:
  Confirmed
Status in network-manager-vpnc package in Ubuntu:
  Confirmed

Bug description:
  From logs:

  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7424] audit: 
op="connection-activate" uuid="71868b90-3a57-4fee-9933-bf7c9b22d44d" 
name="Library" pid=2510 uid=1000 result="success"
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7473] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Started the VPN service, PID 6934
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7518] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Saw the service appear; activating connection
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V NetworkManager[5935]:  [1508608443.7698] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Failed to request VPN secrets #3: No agents were available for t
  his request.
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7708] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 VPN plugin: state changed: stopped (6)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-pptp-gnome 1.2.4-4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct 21 14:07:06 2017
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-pptp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1725779] Re: Gnome network manager cannot find authentication binary

[Igor Shuvalov]

I have clean installed 18.04 and openvpn works well. But only problem
with cisco vpn. It's not connection with Ubuntu panel. But it works with
nm-applet

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

Title:
  Gnome network manager cannot find authentication binary

Status in network-manager-pptp package in Ubuntu:
  Confirmed
Status in network-manager-ssh package in Ubuntu:
  Confirmed
Status in network-manager-vpnc package in Ubuntu:
  Confirmed

Bug description:
  From logs:

  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7424] audit: 
op="connection-activate" uuid="71868b90-3a57-4fee-9933-bf7c9b22d44d" 
name="Library" pid=2510 uid=1000 result="success"
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7473] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Started the VPN service, PID 6934
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7518] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Saw the service appear; activating connection
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V NetworkManager[5935]:  [1508608443.7698] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Failed to request VPN secrets #3: No agents were available for t
  his request.
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7708] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 VPN plugin: state changed: stopped (6)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-pptp-gnome 1.2.4-4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct 21 14:07:06 2017
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-pptp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1725779] Re: Gnome network manager cannot find authentication binary

[Igor Shuvalov]

network-manager-vpnc
network-manager-vpnc-gnome

Are installed

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

Title:
  Gnome network manager cannot find authentication binary

Status in network-manager-pptp package in Ubuntu:
  Confirmed
Status in network-manager-ssh package in Ubuntu:
  Confirmed
Status in network-manager-vpnc package in Ubuntu:
  Confirmed

Bug description:
  From logs:

  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7424] audit: 
op="connection-activate" uuid="71868b90-3a57-4fee-9933-bf7c9b22d44d" 
name="Library" pid=2510 uid=1000 result="success"
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7473] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Started the VPN service, PID 6934
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7518] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Saw the service appear; activating connection
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V NetworkManager[5935]:  [1508608443.7698] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Failed to request VPN secrets #3: No agents were available for t
  his request.
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7708] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 VPN plugin: state changed: stopped (6)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-pptp-gnome 1.2.4-4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct 21 14:07:06 2017
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-pptp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1725779] Re: Gnome network manager cannot find authentication binary

[Igor Shuvalov]

I'm not sure it's network-manager bug.
OpenVPN works fine, but vpnc is broken.
But in the same time it's working ok using nm-applet, so I think it's gnome bug

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

Title:
  Gnome network manager cannot find authentication binary

Status in network-manager-pptp package in Ubuntu:
  Confirmed
Status in network-manager-ssh package in Ubuntu:
  Confirmed
Status in network-manager-vpnc package in Ubuntu:
  Confirmed

Bug description:
  From logs:

  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7424] audit: 
op="connection-activate" uuid="71868b90-3a57-4fee-9933-bf7c9b22d44d" 
name="Library" pid=2510 uid=1000 result="success"
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7473] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Started the VPN service, PID 6934
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7518] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Saw the service appear; activating connection
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V NetworkManager[5935]:  [1508608443.7698] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Failed to request VPN secrets #3: No agents were available for t
  his request.
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7708] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 VPN plugin: state changed: stopped (6)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-pptp-gnome 1.2.4-4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct 21 14:07:06 2017
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-pptp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1772066] Re: Ubuntu 18.04 Network-Manager-OpenVPN won't connected, worked in 17.10, 17.04

[Igor Shuvalov]

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

** This bug has been marked a duplicate of bug 1725779
   Gnome network manager cannot find authentication binary

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

Title:
  Ubuntu 18.04 Network-Manager-OpenVPN won't connected, worked in 17.10,
  17.04

Status in network-manager-openvpn package in Ubuntu:
  Confirmed

Bug description:
  Under Kubuntu 18.04 and Ubuntu 18.04 (both installed multiboot on a
  Thinkpad X230T), OpenVPN won't connect to a host that worked under
  Kubuntu 17.10 and 17.04.  This host continues to be accessible under
  Deepin Linux.

  Here is a log from today's attempt on Kubuntu 18.04.

  -- begin paste --

  $ grep VPN /var/log/syslog
  May 18 12:19:28 mycomputer systemd[1]: Stopped OpenVPN service.
  May 18 12:20:02 mycomputer systemd[1]: Starting OpenVPN service...
  May 18 12:20:02 mycomputer systemd[1]: Started OpenVPN service.
  May 18 12:22:19 mycomputer NetworkManager[819]:   [1526660539.0028] 
vpn-connection[0x55b11e5a01a0,d5e7329e-1444-4c96-a4b6-12d4d9e3130b,"UTORvpn",0]:
 Started the VPN service, PID 3113
  May 18 12:22:19 mycomputer NetworkManager[819]:   [1526660539.2667] 
vpn-connection[0x55b11e5a01a0,d5e7329e-1444-4c96-a4b6-12d4d9e3130b,"UTORvpn",0]:
 VPN plugin: state changed: starting (3)
  May 18 12:22:19 mycomputer nm-openvpn[3116]: OpenVPN 2.4.4 
x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] 
[AEAD] built on Feb 10 2018
  May 18 12:22:19 mycomputer NetworkManager[819]:   [1526660539.5365] 
vpn-connection[0x55b11e5a01a0,d5e7329e-1444-4c96-a4b6-12d4d9e3130b,"UTORvpn",0]:
 VPN plugin: failed: connect-failed (1)
  May 18 12:22:19 mycomputer NetworkManager[819]:   [1526660539.5365] 
vpn-connection[0x55b11e5a01a0,d5e7329e-1444-4c96-a4b6-12d4d9e3130b,"UTORvpn",0]:
 VPN plugin: failed: connect-failed (1)
  May 18 12:22:19 mycomputer NetworkManager[819]:   [1526660539.5370] 
vpn-connection[0x55b11e5a01a0,d5e7329e-1444-4c96-a4b6-12d4d9e3130b,"UTORvpn",0]:
 VPN plugin: state changed: stopping (5)
  May 18 12:22:19 mycomputer NetworkManager[819]:   [1526660539.5381] 
vpn-connection[0x55b11e5a01a0,d5e7329e-1444-4c96-a4b6-12d4d9e3130b,"UTORvpn",0]:
 VPN plugin: state changed: stopped (6)
  May 18 12:22:19 mycomputer NetworkManager[819]:   [1526660539.5396] 
vpn-connection[0x55b11e5a01a0,d5e7329e-1444-4c96-a4b6-12d4d9e3130b,"UTORvpn",0]:
 VPN service disappeared

  -- end paste --

  Just in case it's not included from the ubuntu-bug network-manager-
  openvpn

  -- begin paste --

  $ lsb_release -rd
  Description:Ubuntu 18.04 LTS
  Release:18.04

  $ apt-cache policy network-manager-openvpn
  network-manager-openvpn:
Installed: 1.8.2-1
Candidate: 1.8.2-1
Version table:
   *** 1.8.2-1 500
  500 http://ca.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  -- end paste --

  And here's the results of an attempt on Ubuntu 18.04 a few days ago.

  -- begin paste --

  daviding@mycomputer:~$ grep VPN /var/log/syslog
  May 16 13:09:38 mycomputer NetworkManager[935]:   [1526490578.0785] 
keyfile: add connection /etc/NetworkManager/system-connections/UTorVPN 
(0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6,"UTorVPN")
  May 16 13:09:38 mycomputer NetworkManager[935]:   [1526490578.0794] 
audit: op="connection-add" uuid="0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6" 
name="UTorVPN" pid=3635 uid=1000 result="success"
  May 16 13:11:11 mycomputer gnome-shell[2018]: VPN plugin at 
/usr/lib/NetworkManager/nm-openvpn-auth-dialog is not executable
  May 16 13:11:11 mycomputer gnome-shell[2018]: Invalid VPN service type 
(cannot find authentication binary)
  May 16 13:11:42 mycomputer NetworkManager[935]:   [1526490702.3080] 
audit: op="connection-activate" uuid="0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6" 
name="UTorVPN" pid=3635 uid=1000 result="success"
  May 16 13:11:42 mycomputer NetworkManager[935]:   [1526490702.3167] 
vpn-connection[0x561cde5941c0,0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6,"UTorVPN",0]:
 Started the VPN service, PID 5807
  May 16 13:11:42 mycomputer NetworkManager[935]:   [1526490702.3231] 
vpn-connection[0x561cde5941c0,0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6,"UTorVPN",0]:
 Saw the service appear; activating connection
  May 16 13:11:42 mycomputer NetworkManager[935]:  [1526490702.3286] 
vpn-connection[0x561cde5941c0,0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6,"UTorVPN",0]:
 plugin NeedSecrets request #1 failed: Invalid connection type.
  May 16 13:11:42 mycomputer NetworkManager[935]:   [1526490702.3361] 
vpn-connection[0x561cde5941c0,0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6,"UTorVPN",0]:
 VPN service disappeared
  May 16 13:11:43 mycomputer NetworkManager[935]:   [1526490703.3431] 
audit: op="connection-activate"H uuid="0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6" 
name="UTorVPN" pid=3635