[Desktop-packages] [Bug 1849787] Re: The dock is shown in front of full screen windows since 19.10

2019-11-30 Thread Chris Guiver
my primary box; 20.04 (5.3.0-19)
dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

xscreensaver (glmatrix) was active (two displays) however the Ubuntu
DOCK was fully visible on my primary display.

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

Title:
  The dock is shown in front of full screen windows since 19.10

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

Bug description:
  See attached screenshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1849787/+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 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge

2019-11-30 Thread Till Kamppeter
Please attach both

/etc/cups/ppd/Brother_HL_L2375DW_series.ppd

and

/etc/cups/ppd/brother_hl_l2375dw_ser...@brw0c96e67e441e.local.ppd


** Changed in: cups (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Dell E310dw: Default driver doesn't work, driverless fails on sides
  =two-sided-long-edge

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Dell E310dw printer which worked well on 19.04 has problems in 19.10:

  First, I went through the CUPS web interface to add the printer. The
  interface gave me a choice of two entries with the same name plus one
  with "driverless" added. I chose the first entry (not driverless) and
  completed adding the printer. On the Printers page, the Dell was now
  listed. When I tried "Print Test Page", I got many pages each
  containing a single line of symbols.

  I deleted the printer in the web interface, intending to start again and 
choose the second option. But after I did Delete Printer, CUPS took me back to 
the Printers page which now listed:
  Dell_Printer_E310dw@DELL316BAA.local  Dell Printer E310dw, 
driverless, cups-filters 1.25.11

  So I clicked on that printer and tried Print Test Page, which worked.
  So then I tried a duplex print (which is really what I need this
  morning):

   lp -o sides=two-sided-long-edge -o collate=true -d
  Dell_Printer_E310dw@DELL316BAA.local filename.pdf

  It printed the PDF 2-sided, but with the sides flipped around the
  short edge, as if it was a landscape print. I tried the same command
  with sides=two-sided-short-edge and it flipped the same way. So sides
  is handling duplex but ignoring which edge is supposed to be used, and
  defaulting to landscape which I'd guess is less commonly what people
  want.

  This is all using what's built into Ubuntu. I haven't yet downloaded
  any extra drivers from Dell's site since Ubuntu claims to have a
  driver for the printer, and I'm pretty sure it was working in 19.04 (I
  may still have a working 19.04 to check that, if it would help).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Mon Nov 25 09:58:21 2019
  InstallationDate: Installed on 2019-10-10 (45 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  Lpstat:
   device for Brother_HL-3170CDW_series: 
dnssd://Brother%20HL-3170CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4251dee
   device for Dell_Printer_E310dw@DELL316BAA.local: 
implicitclass://Dell_Printer_E310dw%40DELL316BAA.local/
  MachineType: LENOVO 20QDCTO1WW
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd', 
'/etc/cups/ppd/Brother_HL-3170CDW_series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd: Permission denied
   grep: /etc/cups/ppd/Brother_HL-3170CDW_series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+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 1843733] Re: fftw3 ftbfs in eoan (armhf only)

2019-11-30 Thread Launchpad Bug Tracker
This bug was fixed in the package fftw3 - 3.3.8-2ubuntu1

---
fftw3 (3.3.8-2ubuntu1) focal; urgency=medium

  * debian/rules: Disable Neon for armhf single precision builds to avoid
crashes. It's unclear if this is an fftw3 internal bug in its code
generator (which fftw3 does by hand) or related to gcc changes in recent
years. But certainly disabling Neon avoids the crashes. (LP: #1843733)

 -- Daniel van Vugt   Sat, 30 Nov 2019
23:40:05 +0100

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

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

Title:
  fftw3 ftbfs in eoan (armhf only)

Status in FFTW:
  New
Status in fftw3 package in Ubuntu:
  Fix Released
Status in fftw3 source package in Eoan:
  In Progress

Bug description:
  fftw3 ftbfs in eoan (armhf only).

  https://launchpadlibrarian.net/441265031/buildlog_ubuntu-eoan-
  armhf.fftw3_3.3.8-2_BUILDING.txt.gz

  ( cd tests ; /usr/bin/make smallcheck )
  make[1]: Entering directory '/<>/tests'
  perl -w ./check.pl -r -c=1 -v `pwd`/bench
  Executing "/<>/tests/bench --verbose=1   --verify 
'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify 
'//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' 
--verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' 
--verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 
'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304'"
  ok7e10x12bv29 1.71318e-07 1.44516e-06 2.00887e-07
  ik7e10x12bv29 1.66737e-07 1.44901e-06 1.76717e-07
  Segmentation fault (core dumped)
  FAILED /<>/tests/bench:  --verify 'ok7e10x12bv29' --verify 
'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' 
--verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' 
--verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify 
'//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 
'ofc2304' --verify 'ifc2304'
  make[1]: *** [Makefile:723: smallcheck] Error 1
  make[1]: Leaving directory '/<>/tests'

To manage notifications about this bug go to:
https://bugs.launchpad.net/fftw3/+bug/1843733/+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 1854610] [NEW] No Japanese input possible after upgrade from 19.04 to 19.10

2019-11-30 Thread MrMister
Public bug reported:

Description:

After upgrading to xubuntu 19.10 my Japanese input did not work anymore. 

Regarding to this [https://askubuntu.com/questions/1182781/chinese-
input-methods-not-working-in-ubuntu-mate-19-10] website, there seems to
be the same problem with chinese input.

Workaround:
===
install ibus-gtk and ibus-gtk3.

`apt-cache show ibus-anthy` shows the following dependencies:
===
Depends: anthy (>= 1:0.3-6), ibus (>= 1.5), dconf-gsettings-backend | 
gsettings-backend, python3:any, libanthy1, libc6 (>= 2.4), libglib2.0-0 (>= 
2.37.3)

As ibus-gtk and ibus-gtk3 are not listed, I guess a/the solution would
be to add those to the dependency list.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ibus-anthy 1.5.10-2
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Dec  1 16:15:58 2019
SourcePackage: ibus-anthy
UpgradeStatus: Upgraded to eoan on 2019-12-01 (0 days ago)

** Affects: ibus-anthy (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

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

Title:
  No Japanese input possible after upgrade from 19.04 to 19.10

Status in ibus-anthy package in Ubuntu:
  New

Bug description:
  Description:
  
  After upgrading to xubuntu 19.10 my Japanese input did not work anymore. 

  Regarding to this [https://askubuntu.com/questions/1182781/chinese-
  input-methods-not-working-in-ubuntu-mate-19-10] website, there seems
  to be the same problem with chinese input.

  Workaround:
  ===
  install ibus-gtk and ibus-gtk3.

  `apt-cache show ibus-anthy` shows the following dependencies:
  ===
  Depends: anthy (>= 1:0.3-6), ibus (>= 1.5), dconf-gsettings-backend | 
gsettings-backend, python3:any, libanthy1, libc6 (>= 2.4), libglib2.0-0 (>= 
2.37.3)

  As ibus-gtk and ibus-gtk3 are not listed, I guess a/the solution would
  be to add those to the dependency list.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ibus-anthy 1.5.10-2
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Dec  1 16:15:58 2019
  SourcePackage: ibus-anthy
  UpgradeStatus: Upgraded to eoan on 2019-12-01 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-anthy/+bug/1854610/+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 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge

2019-11-30 Thread Alex Murray
** Attachment added: "error_log"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+attachment/5309038/+files/error_log

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

Title:
  Dell E310dw: Default driver doesn't work, driverless fails on sides
  =two-sided-long-edge

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Dell E310dw printer which worked well on 19.04 has problems in 19.10:

  First, I went through the CUPS web interface to add the printer. The
  interface gave me a choice of two entries with the same name plus one
  with "driverless" added. I chose the first entry (not driverless) and
  completed adding the printer. On the Printers page, the Dell was now
  listed. When I tried "Print Test Page", I got many pages each
  containing a single line of symbols.

  I deleted the printer in the web interface, intending to start again and 
choose the second option. But after I did Delete Printer, CUPS took me back to 
the Printers page which now listed:
  Dell_Printer_E310dw@DELL316BAA.local  Dell Printer E310dw, 
driverless, cups-filters 1.25.11

  So I clicked on that printer and tried Print Test Page, which worked.
  So then I tried a duplex print (which is really what I need this
  morning):

   lp -o sides=two-sided-long-edge -o collate=true -d
  Dell_Printer_E310dw@DELL316BAA.local filename.pdf

  It printed the PDF 2-sided, but with the sides flipped around the
  short edge, as if it was a landscape print. I tried the same command
  with sides=two-sided-short-edge and it flipped the same way. So sides
  is handling duplex but ignoring which edge is supposed to be used, and
  defaulting to landscape which I'd guess is less commonly what people
  want.

  This is all using what's built into Ubuntu. I haven't yet downloaded
  any extra drivers from Dell's site since Ubuntu claims to have a
  driver for the printer, and I'm pretty sure it was working in 19.04 (I
  may still have a working 19.04 to check that, if it would help).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Mon Nov 25 09:58:21 2019
  InstallationDate: Installed on 2019-10-10 (45 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  Lpstat:
   device for Brother_HL-3170CDW_series: 
dnssd://Brother%20HL-3170CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4251dee
   device for Dell_Printer_E310dw@DELL316BAA.local: 
implicitclass://Dell_Printer_E310dw%40DELL316BAA.local/
  MachineType: LENOVO 20QDCTO1WW
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd', 
'/etc/cups/ppd/Brother_HL-3170CDW_series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd: Permission denied
   grep: /etc/cups/ppd/Brother_HL-3170CDW_series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+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 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge

2019-11-30 Thread Alex Murray
** Attachment added: "attrs.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+attachment/5309039/+files/attrs.txt

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

Title:
  Dell E310dw: Default driver doesn't work, driverless fails on sides
  =two-sided-long-edge

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Dell E310dw printer which worked well on 19.04 has problems in 19.10:

  First, I went through the CUPS web interface to add the printer. The
  interface gave me a choice of two entries with the same name plus one
  with "driverless" added. I chose the first entry (not driverless) and
  completed adding the printer. On the Printers page, the Dell was now
  listed. When I tried "Print Test Page", I got many pages each
  containing a single line of symbols.

  I deleted the printer in the web interface, intending to start again and 
choose the second option. But after I did Delete Printer, CUPS took me back to 
the Printers page which now listed:
  Dell_Printer_E310dw@DELL316BAA.local  Dell Printer E310dw, 
driverless, cups-filters 1.25.11

  So I clicked on that printer and tried Print Test Page, which worked.
  So then I tried a duplex print (which is really what I need this
  morning):

   lp -o sides=two-sided-long-edge -o collate=true -d
  Dell_Printer_E310dw@DELL316BAA.local filename.pdf

  It printed the PDF 2-sided, but with the sides flipped around the
  short edge, as if it was a landscape print. I tried the same command
  with sides=two-sided-short-edge and it flipped the same way. So sides
  is handling duplex but ignoring which edge is supposed to be used, and
  defaulting to landscape which I'd guess is less commonly what people
  want.

  This is all using what's built into Ubuntu. I haven't yet downloaded
  any extra drivers from Dell's site since Ubuntu claims to have a
  driver for the printer, and I'm pretty sure it was working in 19.04 (I
  may still have a working 19.04 to check that, if it would help).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Mon Nov 25 09:58:21 2019
  InstallationDate: Installed on 2019-10-10 (45 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  Lpstat:
   device for Brother_HL-3170CDW_series: 
dnssd://Brother%20HL-3170CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4251dee
   device for Dell_Printer_E310dw@DELL316BAA.local: 
implicitclass://Dell_Printer_E310dw%40DELL316BAA.local/
  MachineType: LENOVO 20QDCTO1WW
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd', 
'/etc/cups/ppd/Brother_HL-3170CDW_series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd: Permission denied
   grep: /etc/cups/ppd/Brother_HL-3170CDW_series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+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 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge

2019-11-30 Thread Alex Murray
Let me know which of these PPDs to attach:

$ ls -la /etc/cups/ppd/Brother_HL_L2375DW_series*
-rw-r--r-- 1 root root 8499 Dec  1 17:14 
/etc/cups/ppd/brother_hl_l2375dw_ser...@brw0c96e67e441e.local.ppd
-rw-r- 1 root lp   8424 Dec  1 17:13 
/etc/cups/ppd/brother_hl_l2375dw_ser...@brw0c96e67e441e.local.ppd.O
-rw-r- 1 root lp   8615 Dec  1 17:13 
/etc/cups/ppd/Brother_HL_L2375DW_series.ppd
-rw-r--r-- 1 root root 8487 Dec  1 16:32 
/etc/cups/ppd/Brother_HL_L2375DW_series.ppd.O


** Changed in: cups (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Dell E310dw: Default driver doesn't work, driverless fails on sides
  =two-sided-long-edge

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Dell E310dw printer which worked well on 19.04 has problems in 19.10:

  First, I went through the CUPS web interface to add the printer. The
  interface gave me a choice of two entries with the same name plus one
  with "driverless" added. I chose the first entry (not driverless) and
  completed adding the printer. On the Printers page, the Dell was now
  listed. When I tried "Print Test Page", I got many pages each
  containing a single line of symbols.

  I deleted the printer in the web interface, intending to start again and 
choose the second option. But after I did Delete Printer, CUPS took me back to 
the Printers page which now listed:
  Dell_Printer_E310dw@DELL316BAA.local  Dell Printer E310dw, 
driverless, cups-filters 1.25.11

  So I clicked on that printer and tried Print Test Page, which worked.
  So then I tried a duplex print (which is really what I need this
  morning):

   lp -o sides=two-sided-long-edge -o collate=true -d
  Dell_Printer_E310dw@DELL316BAA.local filename.pdf

  It printed the PDF 2-sided, but with the sides flipped around the
  short edge, as if it was a landscape print. I tried the same command
  with sides=two-sided-short-edge and it flipped the same way. So sides
  is handling duplex but ignoring which edge is supposed to be used, and
  defaulting to landscape which I'd guess is less commonly what people
  want.

  This is all using what's built into Ubuntu. I haven't yet downloaded
  any extra drivers from Dell's site since Ubuntu claims to have a
  driver for the printer, and I'm pretty sure it was working in 19.04 (I
  may still have a working 19.04 to check that, if it would help).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Mon Nov 25 09:58:21 2019
  InstallationDate: Installed on 2019-10-10 (45 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  Lpstat:
   device for Brother_HL-3170CDW_series: 
dnssd://Brother%20HL-3170CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4251dee
   device for Dell_Printer_E310dw@DELL316BAA.local: 
implicitclass://Dell_Printer_E310dw%40DELL316BAA.local/
  MachineType: LENOVO 20QDCTO1WW
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd', 
'/etc/cups/ppd/Brother_HL-3170CDW_series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd: Permission denied
   grep: /etc/cups/ppd/Brother_HL-3170CDW_series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+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 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge

2019-11-30 Thread Alex Murray
I have the same problem with a Brother HL L2375-DW printer on Ubuntu
19.10.

This was auto-detected and added to the GNOME Printers as
'Brother_HL_L2375DW_series' - if I print double sided (long-edge) using
the then it prints the second page upside down (as though I had selected
short-edge) - but selecting short-edge also prints as short-edge.

However, I then went into 'Printer Details' via the gear menu for the
printer, and selected 'Select from Database...' and chose the  'Brother
HL-L2375DW series, driverless, cups-filters 1.25' driver. At this stage
a second instance of the printer appeared in GNOME Printers
('Brother_HL_L2375DW_series@BRW0C96E67E441E.local') - and printing to
this second instance seems to work correctly.

I am unsure how to know which PPD was used for the first auto-detected +
added instance but if you can help me to find out I will happily attach
the PPD here. See below for error_log, attrs.txt

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

Title:
  Dell E310dw: Default driver doesn't work, driverless fails on sides
  =two-sided-long-edge

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Dell E310dw printer which worked well on 19.04 has problems in 19.10:

  First, I went through the CUPS web interface to add the printer. The
  interface gave me a choice of two entries with the same name plus one
  with "driverless" added. I chose the first entry (not driverless) and
  completed adding the printer. On the Printers page, the Dell was now
  listed. When I tried "Print Test Page", I got many pages each
  containing a single line of symbols.

  I deleted the printer in the web interface, intending to start again and 
choose the second option. But after I did Delete Printer, CUPS took me back to 
the Printers page which now listed:
  Dell_Printer_E310dw@DELL316BAA.local  Dell Printer E310dw, 
driverless, cups-filters 1.25.11

  So I clicked on that printer and tried Print Test Page, which worked.
  So then I tried a duplex print (which is really what I need this
  morning):

   lp -o sides=two-sided-long-edge -o collate=true -d
  Dell_Printer_E310dw@DELL316BAA.local filename.pdf

  It printed the PDF 2-sided, but with the sides flipped around the
  short edge, as if it was a landscape print. I tried the same command
  with sides=two-sided-short-edge and it flipped the same way. So sides
  is handling duplex but ignoring which edge is supposed to be used, and
  defaulting to landscape which I'd guess is less commonly what people
  want.

  This is all using what's built into Ubuntu. I haven't yet downloaded
  any extra drivers from Dell's site since Ubuntu claims to have a
  driver for the printer, and I'm pretty sure it was working in 19.04 (I
  may still have a working 19.04 to check that, if it would help).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Mon Nov 25 09:58:21 2019
  InstallationDate: Installed on 2019-10-10 (45 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  Lpstat:
   device for Brother_HL-3170CDW_series: 
dnssd://Brother%20HL-3170CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4251dee
   device for Dell_Printer_E310dw@DELL316BAA.local: 
implicitclass://Dell_Printer_E310dw%40DELL316BAA.local/
  MachineType: LENOVO 20QDCTO1WW
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd', 
'/etc/cups/ppd/Brother_HL-3170CDW_series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd: Permission denied
   grep: /etc/cups/ppd/Brother_HL-3170CDW_series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

To manage 

[Desktop-packages] [Bug 1800043] Re: nautilus cannot write on nfs file share base dir

2019-11-30 Thread Bug Watch Updater
** Changed in: nautilus
   Status: New => Fix Released

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

Title:
  nautilus cannot write on nfs file share base dir

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  I installed Ubuntu 18.04LTS comming from 16.04LTS where I did not have this 
weird problem: If I mount a NFS share from a file server (i.e. Synology DS 418) 
Nautilus is not able to perform any write access to it (write, delete, make new 
directory,...). I can do all of this operations by using shell commands (touch, 
cp, mkdir...) in a terminal window. Also, nautilus can perform these actions if 
I start it with root privileges.
  Even stranger is the following: even though nautilus cannot write into the 
mounted shares it is able to write into its subfolders. This bug seems to 
affect others as well: 
https://askubuntu.com/questions/1000973/nautilus-cannot-write-into-1st-directory-of-a-nfs-share

  Ubuntu version: 18.04.1 LTS - amd64
  Nautilus version: 1:3.26.4-0~ubuntu18.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1800043/+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 1854608] [NEW] Screen Flickering during Boot up

2019-11-30 Thread sourabh
Public bug reported:

The Screen flickers during boot up and System runs very slow.

This is my GPU info.

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core
Processor Family Integrated Graphics Controller (rev 09)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-36-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec  1 11:07:19 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 5.0.0-32-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 5.0.0-36-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:3977]
InstallationDate: Installed on 2019-05-22 (192 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: LENOVO 20157
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-36-generic 
root=UUID=fb1d2555-5fe7-4a82-804c-8b91c22c2a1f ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/26/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 62CN34WW
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Emerald Lake 2
dmi.board.vendor: LENOVO
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnLENOVO:bvr62CN34WW:bd04/26/2012:svnLENOVO:pn20157:pvrLenovoG580:rvnLENOVO:rnEmeraldLake2:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
dmi.product.family: ChiefRiver System
dmi.product.name: 20157
dmi.product.sku: System SKUNumber
dmi.product.version: Lenovo G580
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic 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/1854608

Title:
  Screen Flickering during Boot up

Status in xorg package in Ubuntu:
  New

Bug description:
  The Screen flickers during boot up and System runs very slow.

  This is my GPU info.

  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
  Core Processor Family Integrated Graphics Controller (rev 09)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  1 11:07:19 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.0.0-32-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.0.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:3977]
  InstallationDate: Installed on 2019-05-22 (192 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 20157
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-36-generic 
root=UUID=fb1d2555-5fe7-4a82-804c-8b91c22c2a1f ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 62CN34WW
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Emerald Lake 2
  dmi.board.vendor: LENOVO
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 

[Desktop-packages] [Bug 1854589] Re: Windows move to different monitor when multiple monitors turned off and back on

2019-11-30 Thread Rich Wales
I don't think Compiz is relevant here.  My computer isn't running Compiz
— its display manager is GDM3 as best I can tell.  (ri...@richw.org, the
original reporter of this bug)

** Package changed: compiz (Ubuntu) => gdm3 (Ubuntu)

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

Title:
  Windows move to different monitor when multiple monitors turned off
  and back on

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10, gdm3 3.34.1-1ubuntu1, cinnamon 4.0.10-2, cinnamon-
  screensaver 4.0.3-1, nvidia-driver 435.21-0ubuntu2.

  I have a TV set connected to my computer as a second monitor (for
  displaying YouTube videos, etc.).

  When I turn off both my main monitor and the TV for the night, and
  turn them back on in the morning, I often find that the windows I had
  left open on the main monitor (email, browser, xterm, etc.) have moved
  from the main monitor to the TV and need to be moved back individually
  to the main monitor (via the "move to the other monitor" function on
  the taskbar icons).

  This doesn't always happen -- sometimes the windows show up on the
  main monitor where I left them the night before, and sometimes not.
  Maybe 50-50, one way or the other.

  The main monitor is configured (in the Display settings) as the
  primary monitor, and the taskbar panel remains on the main monitor --
  and when I wake up the screen saver to unlock it, the password
  dialogue always shows up on the main monitor -- but the windows may
  end up on either device after I've unlocked.

  It doesn't appear to make any difference what order I turn the monitor
  and the TV off/on.  In particular, I've conscientiously turned off the
  TV before locking the screen and turning off the monitor, and then
  turned on the monitor and unlocked the screen before turning the TV
  back on, but the windows frequently still end up on the TV instead of
  the main monitor.

  I would like to somehow flag the windows so that they will stay put on
  my main monitor when I turn things off at night and turn them back on
  in the morning -- or, even better, I would like the windows to remain
  associated with the same device and not move around on their own.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1854589/+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 1854589] [NEW] Windows move to different monitor when multiple monitors turned off and back on

2019-11-30 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Ubuntu 19.10, gdm3 3.34.1-1ubuntu1, cinnamon 4.0.10-2, cinnamon-
screensaver 4.0.3-1, nvidia-driver 435.21-0ubuntu2.

I have a TV set connected to my computer as a second monitor (for
displaying YouTube videos, etc.).

When I turn off both my main monitor and the TV for the night, and turn
them back on in the morning, I often find that the windows I had left
open on the main monitor (email, browser, xterm, etc.) have moved from
the main monitor to the TV and need to be moved back individually to the
main monitor (via the "move to the other monitor" function on the
taskbar icons).

This doesn't always happen -- sometimes the windows show up on the main
monitor where I left them the night before, and sometimes not.  Maybe
50-50, one way or the other.

The main monitor is configured (in the Display settings) as the primary
monitor, and the taskbar panel remains on the main monitor -- and when I
wake up the screen saver to unlock it, the password dialogue always
shows up on the main monitor -- but the windows may end up on either
device after I've unlocked.

It doesn't appear to make any difference what order I turn the monitor
and the TV off/on.  In particular, I've conscientiously turned off the
TV before locking the screen and turning off the monitor, and then
turned on the monitor and unlocked the screen before turning the TV back
on, but the windows frequently still end up on the TV instead of the
main monitor.

I would like to somehow flag the windows so that they will stay put on
my main monitor when I turn things off at night and turn them back on in
the morning -- or, even better, I would like the windows to remain
associated with the same device and not move around on their own.

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

-- 
Windows move to different monitor when multiple monitors turned off and back on
https://bugs.launchpad.net/bugs/1854589
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gdm3 in Ubuntu.

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


[Desktop-packages] [Bug 1754833] Re: Chromium complains that it's not the default browser when it is the default according to Gnome Settings

2019-11-30 Thread Gurjus Bhasin
Has this issue been fixed yet?

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

Title:
  Chromium complains that it's not the default browser when it is the
  default according to Gnome Settings

Status in Ubuntu Budgie:
  Confirmed
Status in xdg-utils package in Ubuntu:
  New

Bug description:
  (As seen in a daily build of Ubuntu Budgie 18.04 32bit downloaded
  earlier today)

  See attached screenshot.

  Thanks,
  Ken.
  ***

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1754833/+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 1002978] Re: [meta-bug] Inverted Internal microphone (phase inversion)

2019-11-30 Thread Bryan Cebuliak
On an Acer Aspire 5810TG running Ubuntu 18.04 with latest 5.3 kernel.
HDA Intel. ALC269 Analog. Pulseaudio was monitoring  minimal sound from
internal mic with both channels on, but ok  with either left or right
off. Audacity and Gnome Sound Recorder had no issues. Audacity showed
two phase inverted channels. Same issues  as  above  re  Skype and
Hangouts and same workarounds worked. External mono plug in mic - no
problem.

Same problem on same machine with Debian 10 Buster.

Tried remapping  the Pulseaudio stereo channels  to mono which allowed
even output through both speakers. For instructions see:

https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting
#No_microphone_on_Steam_or_Skype_with_enable-remixing_=_no

After this, Pulseaudio still has to  have one internal mic channel off
to function. However output is  now  through both  speakers instead of
one.

In Ubuntu, Audacity shows  two  channels with same phase. In Debian,
Audacity shows one mono channel. Same difference through the speakers.

I believe this is  still  a  bug as Pulseaudio cannot produce output
from with a phase inverted stereo internal mic as Audacity and Sound
recorder can.

Best regards,
Your bleeding user

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

Title:
  [meta-bug] Inverted Internal microphone (phase inversion)

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  This is a metabug for all machines that are having phase inverted
  internal microphones.

  If your internal mic is either completely silent (no signal), or you
  can possibly pick a very small sound, with much background noise, even
  though you have set gain to maximum, there is something you could try.

  Install the pavucontrol application, start it and go to the "Input Devices" 
tab. Unlock the channels (there is a keylock icon), then mute the right channel 
while keeping the left channel at the volume you want.
  If the internal mic is now working correctly, you have an inverted internal 
mic, so that your right channel cancels out the left one.

  (If you're not running PulseAudio, you can try doing the same through
  AlsaMixer instead (see https://wiki.ubuntu.com/Audio/Alsamixer ), try
  changing "Capture" level or "Internal Mic" or "Internal Mic Boost"
  using the Q,E,Z,C keys.)

  If so, please file a separate bug against the alsa-driver for your
  issue, make sure hardware info gets attached to it (either alsa-info
  as per https://wiki.ubuntu.com/Audio/AlsaInfo or the standard ones
  that follows when you do "ubuntu-bug alsa-driver" ), then write a
  comment in this bug, with your machine name and a pointer to the other
  bug.

  As time permits, I'll try to work on fixing them for the next Ubuntu release. 
Thanks!
   -- David Henningsson

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978/+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 1854603] [NEW] Greek (polytonic) keyboard layout not handling some accent marks

2019-11-30 Thread Jane Atkinson
Public bug reported:

I’m running Ubuntu 20.04 (GNOME shell desktop: gnome-shell
3.34.1+git20191024-1ubuntu1) in a QEMU/KVM vm.

I’m using a US keyboard which is set up to switch between English and
polytonic Greek.

This has been working satisfactorily in 18.04.

However, in 20.04, I’m noticing that I can’t add the breathing marks or
diaeresis to lower-case letters in polytonic Greek. When I try to type
the marks, they appear on the screen but disappear immediately once I
release the shift key.

I can add breathing marks and diaeresis to capital letters.

So far, I've seen this behaviour in LibreOffice, gedit and Firefox.

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

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

Title:
  Greek (polytonic) keyboard layout not handling some accent marks

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I’m running Ubuntu 20.04 (GNOME shell desktop: gnome-shell
  3.34.1+git20191024-1ubuntu1) in a QEMU/KVM vm.

  I’m using a US keyboard which is set up to switch between English and
  polytonic Greek.

  This has been working satisfactorily in 18.04.

  However, in 20.04, I’m noticing that I can’t add the breathing marks
  or diaeresis to lower-case letters in polytonic Greek. When I try to
  type the marks, they appear on the screen but disappear immediately
  once I release the shift key.

  I can add breathing marks and diaeresis to capital letters.

  So far, I've seen this behaviour in LibreOffice, gedit and Firefox.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1854603/+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 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

2019-11-30 Thread Doug Smythies
There is only one PLL (Phase Locked Loop) in the processor, all CPUs get
the resulting clock. When they go into deep idle states (deeper than C1,
at least for my processor) then they give up their vote into the PLL as
to what the frequency should be. Your single 100% task is dedicating the
CPU frequency for all, for when they are active.

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10HX.M034.20110426.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RF511/RF411/RF711
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 10HX
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 

[Desktop-packages] [Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop

2019-11-30 Thread Konstantin Hollerith
I'm using Ubuntu 18.04 since it came out, but are effected by this bug only 
since two weeks.
What I noticed: I have a couple of programs setup to start automatically (via 
gnome-session-properties). When I log in and get kicked out because of this 
bug, those programs where never started at all. On a normal Login they start 
fine.

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

Title:
  Unrecoverable failure in required component
  org.gnome.SettingsDaemon.Color.desktop

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

Bug description:
  I've had this happen a couple of times now since upgrading to 18.04:
  soon (perhaps within a minute) after logging in, Gnome session ends
  abruptly and I'm thrown back to the login screen. IIRC, in both
  instances this occurred on the first login after boot, so it does not
  reoccur on the subsequent re-login, and not on every login (very
  rarely in fact), and for now I have no better steps to reproduce this
  other than "boot, log in".

  Bug #1663839 (reported against 17.04) seems similar, as does bug
  #1731428 (reported against 17.10).

  journalctl output during the issue:

  Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: 
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to 
register before timeout
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.Color.desktop
  Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: 
CRITICAL: We failed, but the fail whale is dead. Sorry
  Apr 16 07:00:30 saegusa gnome-session-binary[4342]: CRITICAL: We failed, but 
the fail whale is dead. Sorry

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 17:07:14 2018
  InstallationDate: Installed on 2016-10-13 (550 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+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 1562219] Re: Unprivileged xinit wont start in unallocated vt

2019-11-30 Thread rebroad
Does install the suid-root wrapper allow for any user to run an X
server? This seems a little too open if so, as it seems better to allow
only either root, or the user logged into the console to run the server,
IMHO.

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

Title:
  Unprivileged xinit wont start in unallocated vt

Status in xinit package in Ubuntu:
  Confirmed

Bug description:
  If as an unprivileged user you launch xinit (or startx) to any vt
  (EVEN IF UNALLOCATED BY SYSTEMD) it will fail as described below. The
  only exception appears to be if the vt you attempt to launch X onto is
  already logged into by that user. For many this makes running X
  unprivileged unworkable.

  --

  When attempting to run xinit or startx after upgrading from 14.04 to
  16.04 it will not work.  There seems to be some sort of permission
  issue.  I have seen another person with this issue as well here:

  http://askubuntu.com/questions/749370/ubuntu-16-04-xf86openconsole-
  cannot-open-virtual-console-2?newreg=ba376d7a182d44608ed4675346b1ed74

  An example is when attempting to launch kodi, which worked prior to
  the upgrade:

  xinit /usr/bin/kodi --standalone -- -nocursor :0

  X.Org X Server 1.18.1
  Release Date: 2016-02-08
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.13.0-79-generic x86_64 Ubuntu
  Current Operating System: Linux hostname 4.4.0-15-generic #31-Ubuntu SMP Fri 
Mar 18 19:08:31 UTC 2016 x86_64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=6f2e8267-1240-4f7b-9889-42e65d74767e ro biosdevname=0 text
  Build Date: 11 March 2016  07:43:21AM
  xorg-server 2:1.18.1-1ubuntu4 (For technical support please see 
http://www.ubuntu.com/support)
  Current version of pixman: 0.33.6
  Before reporting problems, check http://wiki.x.org
  to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
  (++) from command line, (!!) notice, (II) informational,
  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/home/arch/.local/share/xorg/Xorg.0.log", Time: Fri Mar 25 
20:14:07 2016
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  (EE)
  Fatal server error:
  (EE) xf86OpenConsole: Cannot open virtual console 2 (Permission denied)
  (EE)
  (EE)
  Please consult the The X.Org Foundation support
   at http://wiki.x.org
   for help.
  (EE) Please also check the log file at 
"/home/arch/.local/share/xorg/Xorg.0.log" for additional information.
  (EE)
  (EE) Server terminated with error (1). Closing log file.
  xinit: giving up
  xinit: unable to connect to X server: Connection refused

  I have tried numerous workarounds including reinstalling xorg,
  removing all x-related files in my profile, and creating a new user.
  Unfortunately none of these worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xinit 1.3.4-3
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Mar 25 20:14:18 2016
  DistUpgraded: 2016-03-25 09:16:37,728 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: oem-audio-hda-daily, 0.201412181801~ubuntu14.04.1, 
3.13.0-83-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/xinit
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1849:0402]
  InstallationDate: Installed on 2014-12-14 (467 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=6f2e8267-1240-4f7b-9889-42e65d74767e ro biosdevname=0 text
  SourcePackage: xinit
  UpgradeStatus: Upgraded to xenial on 2016-03-25 (0 days ago)
  dmi.bios.date: 05/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.90
  dmi.board.name: H97M Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd05/18/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  

[Desktop-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

2019-11-30 Thread Davide Sangalli
@Doug Smythies: thanks for the reply.
I'm sampling every second.

Anyway, just to better understand.
When my system is idle all cores spend in C0 less than 10% of the time and the 
frequency of each core reported by i7z is different and below 2.2GHz. When I 
run a single core (and single thread) task, there is just core "0" which is 
100% of the time in C0 state (as it should) but I would have expected only such 
core to reach ~2.9GHz and the other to remain in below. Instead all cores goes 
to ~2.9GHz.
https://www.youtube.com/watch?v=HBKfkiOgIv4 (sorry for the oversimplified 
reference)

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10HX.M034.20110426.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 

[Desktop-packages] [Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm

2019-11-30 Thread Jason Jystad
Just ran into this issue on a fresh install of 19.10 with all updates
installed as of 2019/11/30. The lock icon in the menu is missing and the
keyboard shortcut is non-functional. The Screen Lock dialog in settings
is greyed out entirely.

chris-18's fix from earlier worked.

Setting org/gnome/desktop/lockdown/disable-lock-screen to disabled:
enabled the icon, the keyboard shortcut, and the Screen Lock dialog in
settings.

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

Title:
  Can't lock screen with keyboard shortcuts when using lightdm

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen.
  Additionally, if I wait a very long time the screen does not lock
  either.

  Switching from LightDM to GDM3 fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  6 09:17:35 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-01-22 (592 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  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/1715435/+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 1752091] Re: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed

2019-11-30 Thread A. Denton
Hello TJ, your gvfs-package build on
https://launchpad.net/~tj/+archive/ubuntu/bugfixes seems to have
resolved the problem for me! Therefore, a 1000 thanks! :-)

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

Title:
  gvfsd-metadata[1703]: g_udev_device_has_property: assertion
  'G_UDEV_IS_DEVICE (device)' failed

Status in gvfs:
  Fix Released
Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  I have no idea about the package to blame: gvfs/udev/kernel ?

  This is now logged:
  gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE 
(device)' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.35.91-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Feb 27 14:21:10 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1752091/+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 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

2019-11-30 Thread Doug Smythies
@Davide Sangalli: What you describe and show in your comment #80 is
correct and exactly what should happen. Your processor is spending an
extraordinary amount of time in C1 as opposed to deeper idle states. At
what sampling frequency do you run i7z? I would suggest once every 15
seconds or so, so that you don't wake up CPUs just to ask them status
stuff.

Everyone with this problem: If you don't bisect the kernel to isolate
the offending commit, as has been asked for a couple of times now, then
there will never be any progress for this bug report.

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10HX.M034.20110426.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RF511/RF411/RF711
  dmi.board.vendor: 

[Desktop-packages] [Bug 51554]

2019-11-30 Thread Vseerror
FYI, this reporter is gone - not responded to any bug reports. Perhaps
this can be closed?

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

Title:
  Unicode combining characters don't combine properly.

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: firefox

  Load this Unicode test page:

  http://www.cl.cam.ac.uk/~mgk25/ucs/examples/UTF-8-demo.txt

  Scroll down to "Combining characters". The accents will appear to the
  right of the characters they're meant to appear directly over.

  I'm running firefox 1.5.dfsg+1.5.0.4-0ubuntu6.06 on Ubuntu Dapper.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/51554/+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 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

2019-11-30 Thread Davide Sangalli
I also mention that, monitoring with i7z the clock of my CPU, when intel turbo 
is not working I get different freqs for each core
Core [core-id]  :Actual Freq (Mult.)  C0%   Halt(C1)%  C3 %   C6 %  
Temp  VCore
Core 1 [0]:   1126.19 (11.23x)  7.9993.9   1   1
40  0.6274
Core 2 [1]:   1239.87 (12.36x)   3.295.1   12.11
41  0.6208
Core 3 [2]:   1577.66 (15.73x)   3.795.4   1   1
38  0.6257
Core 4 [3]:   1316.89 (13.13x)  7.2381.9   112.8
39  0.6257
Core 5 [4]:   1572.58 (15.68x)  10.2  87   14.73
39  0.6257
Core 6 [5]:   1916.98 (19.11x)  8.0290.6   11.44
39  0.6266

However, as soon as I load 1 core to 100%, all goes at the maximum frequency 
(here I'm limiting the maximum and also the core is under-volted to keep the 
temperature stable.
Core [core-id]  :Actual Freq (Mult.)  C0%   Halt(C1)%  C3 %   C6 %  
Temp  VCore
Core 1 [0]:   2891.95 (28.83x)   100   0   0   0
52  0.8234
Core 2 [1]:   2891.77 (28.83x)  2.4192.2   1 3.6
47  0.8229
Core 3 [2]:   2891.72 (28.83x)  1.7394.4   12.37
44  0.8225
Core 4 [3]:   2891.81 (28.83x) 191.5   16.46
44  0.8230
Core 5 [4]:   2892.39 (28.83x) 196.9   11.37
44  0.8242
Core 6 [5]:   2891.94 (28.83x)2562.9   1 3.3
43  0.8243

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 

[Desktop-packages] [Bug 1444880] Re: xrandr report inverted gamma values

2019-11-30 Thread WinEunuchs2Unix
A bug report was filed in 2010, supposedly fixed in 2018 and patched in
2019 in `xrandr` version `1.5.1`. I tried compiling `1.5.1` in Ubuntu
but it didn't seem to have been fixed yet. Documented in this Ask Ubuntu
Q: [When will xrandr version 1.5.1 be available in
Ubuntu?](https://askubuntu.com/questions/1192154/when-will-xrandr-
version-1-5-1-be-available-in-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/1444880

Title:
  xrandr report inverted gamma values

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  $ xrandr --output VGA1  --gamma 1:1:1.7
  $ xrandr --verbose | grep -iE '(gamma|bright)'
  Gamma:  1.0:1.0:1.7
  Brightness: 1.0
  Gamma:  1.0:1.0:0.59
  Brightness: 1.0
  $ xrandr --output VGA1  --gamma 1:1:.6
  $ xrandr --verbose | grep -iE '(gamma|bright)'
  Gamma:  1.0:1.0:1.7
  Brightness: 1.0
  Gamma:  1.0:1.0:1.7
  Brightness: 1.0

  As you can see in output of commands above, "Gamma" values printed by
  xrandr --verbose are exactly the invert of the values set: 1/... Appart for value 1.0 which is correct.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444880/+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 1854583] [NEW] [ProLiant MicroServer Gen8, Nvidia GPU 81 HDMI/DP, Digital Out, HDMI] Sound is distorted

2019-11-30 Thread costinel
Public bug reported:

this works ok with latest 5.3.x kernel but not with 4.15 kernel
kernel 5.0.0 does not work ok with zfs so I can't confirm it is fixed or not in 
5.0.0

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base (not installed)
ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
Uname: Linux 4.15.0-70-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: LXDE
Date: Sat Nov 30 18:43:40 2019
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: GP108 High Definition Audio Controller - HDA NVidia
Symptom_Jack: Digital Out, HDMI
Symptom_Type: Digital clip or distortion, or "overdriven" sound
Title: [ProLiant MicroServer Gen8, Nvidia GPU 81 HDMI/DP, Digital Out, HDMI] 
Sound is distorted
UpgradeStatus: Upgraded to bionic on 2018-08-22 (465 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  [ProLiant MicroServer Gen8, Nvidia GPU 81 HDMI/DP, Digital Out, HDMI]
  Sound is distorted

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  this works ok with latest 5.3.x kernel but not with 4.15 kernel
  kernel 5.0.0 does not work ok with zfs so I can't confirm it is fixed or not 
in 5.0.0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Uname: Linux 4.15.0-70-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sat Nov 30 18:43:40 2019
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: GP108 High Definition Audio Controller - HDA NVidia
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [ProLiant MicroServer Gen8, Nvidia GPU 81 HDMI/DP, Digital Out, HDMI] 
Sound is distorted
  UpgradeStatus: Upgraded to bionic on 2018-08-22 (465 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1854583/+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

2019-11-30 Thread 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

2019-11-30 Thread 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

2019-11-30 Thread 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

2019-11-30 Thread 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

2019-11-30 Thread 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

2019-11-30 Thread 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

2019-11-30 Thread 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

2019-11-30 Thread 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

2019-11-30 Thread 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

2019-11-30 Thread 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

2019-11-30 Thread 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

2019-11-30 Thread 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

2019-11-30 Thread 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

2019-11-30 Thread 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

2019-11-30 Thread 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

2019-11-30 Thread 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

2019-11-30 Thread 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

2019-11-30 Thread 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 1457035] Re: gedit random paste highlighted text while scrolling

2019-11-30 Thread Norman Perelson
I still experience this bug. Using Pluma in Ubuntu Mate 19.10

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

Title:
  gedit random paste highlighted text while scrolling

Status in gedit package in Ubuntu:
  Confirmed

Bug description:
  my system:
  Ubuntu 14.04.2 LTS x64 (updated)
  Release:  14.04

  apt-cache policy gedit
  gedit:
    Installed: 3.10.4-0ubuntu4
    Candidate: 3.10.4-0ubuntu4
    Version table:
   *** 3.10.4-0ubuntu4 0
  500 http://it.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  reproducing bug:
  0) open a ~400 lines text file
  1) highlight some text (e.g. a single line in the middle)
  2) scroll till the bottom of the document (using the mouse wheel)
  3) scroll till the top
  4) Type Ctrl+C then Ctrl+F and finally Ctrl+V (or manually search for the 
same text in the document)

  you will notice that the highlighted text will be copy-pasted randomly
  in your document.

  if you can't reproduce the bug this way, try opening a 400 lines .py
  (python) text file (UTF-8 encoded) with python code inside it.

  EDIT:
  Bug confirmed with normal text files also (see comment #4)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1457035/+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] [NEW] Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

2019-11-30 Thread 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 1849637] Re: nouveau driver spams dmesg with SCHED_ERROR

2019-11-30 Thread Mathieu Tarral
** Also affects: xserver-xorg-video-nouveau (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  nouveau driver spams dmesg with SCHED_ERROR

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

Bug description:
  Hi,

  Since the upgrade from 19.04 to 19.10, the nouveau driver is continuously 
spamming dmesg output
  with

  nouveau :01:00.0: fifo: SCHED_ERROR 08 []

  
  -> lsb_release
  Description:  Ubuntu 19.10
  Release:  19.10

  -> hardware
  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Mobile)
  01:00.0 VGA compatible controller: NVIDIA Corporation TU106M [GeForce RTX 
2060 Mobile] (rev a1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nouveau-firmware/+bug/1849637/+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 1851918] Re: `hp-check -r` crashes with "AttributeError: module 'PIL.Image' has no attribute 'VERSION'"

2019-11-30 Thread Till Kamppeter
This is fixed in Debian's HPLIP package 3.19.8+dfsg0-2, so it is fixed
in Focal.

** Changed in: hplip (Ubuntu Focal)
   Status: Triaged => Fix Released

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

Title:
  `hp-check -r` crashes with "AttributeError: module 'PIL.Image' has no
  attribute 'VERSION'"

Status in HPLIP:
  Confirmed
Status in hplip package in Ubuntu:
  Fix Released
Status in pillow package in Ubuntu:
  Invalid
Status in python-imaging package in Ubuntu:
  Invalid
Status in hplip source package in Focal:
  Fix Released
Status in pillow source package in Focal:
  Invalid
Status in python-imaging source package in Focal:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install HPLIP on Ubuntu 19.10 with `sudo apt-get install hplip*`
  2. Run `hp-check -r`

  Expected results:
  * `hp-check -r` runs without errors

  Actual results:
  * `hp-check -r` shows many errors and crashes:

  $ hp-check -r
  Saving output in log file: /home/mate/hp-check.log

  HP Linux Imaging and Printing System (ver. 3.19.6)
  Dependency/Version Check Utility ver. 15.1

  Copyright (c) 2001-18 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Note: hp-check can be run in three modes:
  1. Compile-time check mode (-c or --compile): Use this mode before compiling 
the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper 
  dependencies are installed to successfully compile HPLIP. 
   
  2. Run-time check mode (-r or --run): Use this mode to determine if a distro 
supplied package (.deb, .rpm, etc) or an already built HPLIP supplied   
  tarball has the proper dependencies installed to successfully run.
   
  3. Both compile- and run-time check mode (-b or --both) (Default): This mode 
will check both of the above cases (both compile- and run-time  
  dependencies).
   

  Check types:  
   
  a. EXTERNALDEP - External Dependencies
   
  b. GENERALDEP - General Dependencies (required both at compile and run time)  
   
  c. COMPILEDEP - Compile time Dependencies 
   
  d. [All are run-time checks]  
   
  PYEXT SCANCONF QUEUES PERMISSION  
   

  Status Types:
  OK
  MISSING   - Missing Dependency or Permission or Plug-in
  INCOMPAT  - Incompatible dependency-version or Plugin-version

  warning: ubuntu-19.10 version is not supported. Using ubuntu-19.04
  versions dependencies to verify and install...

  ---
  | SYSTEM INFO |
  ---

   Kernel: 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 GNU/Linux
   Host: eoan
   Proc: 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 GNU/Linux
   Distribution: ubuntu 19.10
   Bitness: 64 bit

  
  ---
  | HPLIP CONFIGURATION |
  ---

  HPLIP-Version: HPLIP 3.19.6
  HPLIP-Home: /usr/share/hplip
  warning: HPLIP-Installation: Auto installation is not supported for ubuntu 
distro  19.10 version 

  Current contents of '/etc/hp/hplip.conf' file:
  # hplip.conf.  Generated from hplip.conf.in by configure.

  [hplip]
  version=3.19.6

  [dirs]
  home=/usr/share/hplip
  run=/var/run
  ppd=/usr/share/ppd/hplip/HP
  ppdbase=/usr/share/ppd/hplip
  doc=/usr/share/doc/hplip
  html=/usr/share/doc/hplip-doc
  icon=no
  cupsbackend=/usr/lib/cups/backend
  cupsfilter=/usr/lib/cups/filter
  drv=/usr/share/cups/drv
  bin=/usr/bin
  apparmor=/etc/apparmor.d
  # Following values are determined at configure time and cannot be changed.
  [configure]
  network-build=yes
  libusb01-build=no
  pp-build=no
  gui-build=yes
  scanner-build=yes
  fax-build=yes
  dbus-build=yes
  cups11-build=no
  doc-build=yes
  shadow-build=no
  hpijs-install=yes
  foomatic-drv-install=yes
  foomatic-ppd-install=no
  foomatic-rip-hplip-install=no
  hpcups-install=yes
  cups-drv-install=yes
  

[Desktop-packages] [Bug 1854565] [NEW] Mouse (not touchpad) right click acts as left click

2019-11-30 Thread Carlo Salinari
Public bug reported:

Ubuntu 18.04.3 LTS

(Please note this refers to an actual USB mouse on a Desktop system,
_not_ a Touchpad)

What happens:
Clicking the the right button of my mouse shows the context menu but then 
sometimes also acts as a left click.

Steps to reproduce:
- open a web page move the mouse pointer over a link
- click the right button (keep clicking the right button if the bug doesn't 
manifest immediately)
- at a certain (random) point, the link is followed as if a left click was 
issued

The bug is erratic but always reproducible (it is not always the _first_
right-click to be misinterpreted as a left one, but after a few tries it
always does).

What Should happen:
A right click should never be interpreted as a left one. This is a very basic 
UI interaction.

Extra information:
Tried different USB mice, it is not a hardware error.
Possibly related: the context menu sometimes appears very far from the actual 
position of the mouse cursor.

What I tried:
I tried disabling mouse click emulation via gnome-tweaks (see attachment). 
Nothing changed.

** Affects: gsettings-desktop-schemas (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Screenshot from 2019-11-30 12-02-18.png"
   
https://bugs.launchpad.net/bugs/1854565/+attachment/5308869/+files/Screenshot%20from%202019-11-30%2012-02-18.png

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

Title:
  Mouse (not touchpad) right click acts as left click

Status in gsettings-desktop-schemas package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04.3 LTS

  (Please note this refers to an actual USB mouse on a Desktop system,
  _not_ a Touchpad)

  What happens:
  Clicking the the right button of my mouse shows the context menu but then 
sometimes also acts as a left click.

  Steps to reproduce:
  - open a web page move the mouse pointer over a link
  - click the right button (keep clicking the right button if the bug doesn't 
manifest immediately)
  - at a certain (random) point, the link is followed as if a left click was 
issued

  The bug is erratic but always reproducible (it is not always the
  _first_ right-click to be misinterpreted as a left one, but after a
  few tries it always does).

  What Should happen:
  A right click should never be interpreted as a left one. This is a very basic 
UI interaction.

  Extra information:
  Tried different USB mice, it is not a hardware error.
  Possibly related: the context menu sometimes appears very far from the actual 
position of the mouse cursor.

  What I tried:
  I tried disabling mouse click emulation via gnome-tweaks (see attachment). 
Nothing changed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1854565/+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 1838154] Re: Something hinders XFCE performance. >:]

2019-11-30 Thread klfytklfyt
** Attachment added: "default configuration [less smooth, flickers, lags]"
   
https://bugs.launchpad.net/xorg-server/+bug/1838154/+attachment/5308868/+files/less%20smooth-2019-11-30_12.46.01.ogg

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

Title:
  Something hinders XFCE performance.  >:]

Status in wayland:
  New
Status in Xfce4 Desktop:
  New
Status in Xfwm4:
  New
Status in X.Org X server:
  New
Status in xorg package in Ubuntu:
  New
Status in xfwm4 package in Fedora:
  Unknown

Bug description:
  The following settings get rid of some kind of flickering
  or slow-down during typing and so on.

  1. Snapping settings: 1 (top) 1 (bottom) 0 (left) 2 (right)

  2. Send message trick lowers temperature.  :-)

  3. Avoid alt-tabbing.   >:]

  4. Rename Templates to "# Templates".

  __

  Additional info:

  two spaces bug  -  
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716
  https://bugzilla.redhat.com/show_bug.cgi?id=1754300#c2

  Templates bug  -  
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462
  https://bugzilla.redhat.com/show_bug.cgi?id=1729666

  :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/wayland/+bug/1838154/+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 1838154] Re: Something hinders XFCE performance. >:]

2019-11-30 Thread klfytklfyt
** Attachment added: "notice the smoothness difference [smooth]"
   
https://bugs.launchpad.net/xorg-server/+bug/1838154/+attachment/5308867/+files/smooth-2019-11-30_12.44.25.ogg

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

Title:
  Something hinders XFCE performance.  >:]

Status in wayland:
  New
Status in Xfce4 Desktop:
  New
Status in Xfwm4:
  New
Status in X.Org X server:
  New
Status in xorg package in Ubuntu:
  New
Status in xfwm4 package in Fedora:
  Unknown

Bug description:
  The following settings get rid of some kind of flickering
  or slow-down during typing and so on.

  1. Snapping settings: 1 (top) 1 (bottom) 0 (left) 2 (right)

  2. Send message trick lowers temperature.  :-)

  3. Avoid alt-tabbing.   >:]

  4. Rename Templates to "# Templates".

  __

  Additional info:

  two spaces bug  -  
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716
  https://bugzilla.redhat.com/show_bug.cgi?id=1754300#c2

  Templates bug  -  
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462
  https://bugzilla.redhat.com/show_bug.cgi?id=1729666

  :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/wayland/+bug/1838154/+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 1518021] Re: /usr/bin/Xorg:6:sna_dri2_event_free:sna_dri2_schedule_flip:sna_dri2_schedule_swap:DRI2SwapBuffers:ProcDRI2SwapBuffers

2019-11-30 Thread Bug Watch Updater
** Changed in: xserver-xorg-video-intel
   Status: Incomplete => Unknown

** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues 
#77
   https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues/77

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

Title:
  
/usr/bin/Xorg:6:sna_dri2_event_free:sna_dri2_schedule_flip:sna_dri2_schedule_swap:DRI2SwapBuffers:ProcDRI2SwapBuffers

Status in xf86-video-intel:
  Unknown
Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  This occurs on my shiny new Lenovo Thinkpad T540p.

  I have my laptop docked in a Lenovo UltraDock running two external
  1080p displays.

  When I'm logged in, if I un-dock the laptop I get booted back out to
  the login screen (i.e.- X crashes). This seems to happen about 90% of
  the time, so it's reasonably easy to reproduce.

  In order to try and reproduce this, I installed the X server -dbg
  packages. However, with the -dbg packages installed I can't seem to
  reproduce this  any more (possibly a race condition?).

  ---

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding xorg-server.  This problem was most recently seen with
  version 2:1.17.2-1ubuntu9, the problem page at
  https://errors.ubuntu.com/problem/e58accb723690ba7801e7f3fbc9bc637f08e8641
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1518021/+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 1518021]

2019-11-30 Thread Martin-peres-n
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues/77.

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

Title:
  
/usr/bin/Xorg:6:sna_dri2_event_free:sna_dri2_schedule_flip:sna_dri2_schedule_swap:DRI2SwapBuffers:ProcDRI2SwapBuffers

Status in xf86-video-intel:
  Unknown
Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  This occurs on my shiny new Lenovo Thinkpad T540p.

  I have my laptop docked in a Lenovo UltraDock running two external
  1080p displays.

  When I'm logged in, if I un-dock the laptop I get booted back out to
  the login screen (i.e.- X crashes). This seems to happen about 90% of
  the time, so it's reasonably easy to reproduce.

  In order to try and reproduce this, I installed the X server -dbg
  packages. However, with the -dbg packages installed I can't seem to
  reproduce this  any more (possibly a race condition?).

  ---

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding xorg-server.  This problem was most recently seen with
  version 2:1.17.2-1ubuntu9, the problem page at
  https://errors.ubuntu.com/problem/e58accb723690ba7801e7f3fbc9bc637f08e8641
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1518021/+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 1845046] Re: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected

2019-11-30 Thread jurosh
I sometimes trying to fix this for minutes, without any luck. But also
realized that when reconnecting there should be connected another
headphones, even if usb c one. Will be watching bwhaviour. Having issues
with Sone 1000xm3.

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

Title:
  Bluetooth headphones/speaker default to low quality headset mode and
  fails to switch to A2DP when selected

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Whenever I turn on my headphones theyll connect to my computer but im
  able to hear the input audio from my microphone and low quality output
  audio. I have to disconnect the headphones in the bluetooth devices
  and reconnect for it to fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  litleck1398 F pulseaudio
   /dev/snd/controlC0:  litleck1398 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 17:07:59 2019
  InstallationDate: Installed on 2019-09-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  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: WH-1000XM3
  Symptom_Type: High background noise, or volume is too low
  Title: [WH-1000XM3, playback] Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.19
  dmi.board.name: 01NYPT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware Aurora R5
  dmi.product.sku: 0729
  dmi.product.version: 1.0.19
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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 1854386] Re: Stuck on show applications overlay (can't close it)

2019-11-30 Thread Damian
** Description changed:

  Hello,
  
  I've upgraded my ubuntu 19.04 to 19.10 this morning and I came across
  this very annoying bug.
  
  Whenever I click on 'show applications' or press win key (shortcut), the
  menu with the applications show, but it's empty - you can search through
  it and it works fine (applications show, one can trigger application
  launch), but then after you select an application, the menu doesn't
  disappear at all.
  
  It doesn't go away when pressing any application on the dash panel, nor
  when clicking esc key, it only goes away after you click on the dash
  icon again, BUT...
  
  It doesn't really go away - it just becomes invisible, but still it
  overlaps all the items that are launched (with exception of dash panel,
  because it's not being overlapped), and you can't do anything on any
  launched application. Sometimes when you try to move some windows, you
  can see them getting transformed into a miniature, as if the system
  wanted to insert application into the suggestions on the 'show
  applications'.
  
  The only thing that worked for me was restarting my computer.
  
+ Here is a movie of this happening:
+ 
https://photos.google.com/share/AF1QipNA94MOXY4iH8rm01coSkZcH6ILYas9n2oXNs9Swxo16ijABFqz71VaRpO59tGpPg/photo/AF1QipOqVIZXLZW-Z_7zCIy8eeBGQgJQkPLY-OKfgy0Y?key=MTJBa2pRUl9VU2lmMXdEZGxYX3ZiSDRSTjJxWjdn
+ 
+ I couldn't record screen because apparently the hotkeys were also
+ intercepted and I couldn't save the video.
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15.3
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 28 18:00:54 2019
  InstallationDate: Installed on 2018-11-09 (383 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-11-27 (0 days ago)
  VarLogDistupgradeTermlog:

** Description changed:

  Hello,
  
  I've upgraded my ubuntu 19.04 to 19.10 this morning and I came across
  this very annoying bug.
  
  Whenever I click on 'show applications' or press win key (shortcut), the
  menu with the applications show, but it's empty - you can search through
  it and it works fine (applications show, one can trigger application
  launch), but then after you select an application, the menu doesn't
  disappear at all.
  
  It doesn't go away when pressing any application on the dash panel, nor
  when clicking esc key, it only goes away after you click on the dash
  icon again, BUT...
  
  It doesn't really go away - it just becomes invisible, but still it
  overlaps all the items that are launched (with exception of dash panel,
  because it's not being overlapped), and you can't do anything on any
  launched application. Sometimes when you try to move some windows, you
  can see them getting transformed into a miniature, as if the system
  wanted to insert application into the suggestions on the 'show
  applications'.
  
  The only thing that worked for me was restarting my computer.
  
  Here is a movie of this happening:
  
https://photos.google.com/share/AF1QipNA94MOXY4iH8rm01coSkZcH6ILYas9n2oXNs9Swxo16ijABFqz71VaRpO59tGpPg/photo/AF1QipOqVIZXLZW-Z_7zCIy8eeBGQgJQkPLY-OKfgy0Y?key=MTJBa2pRUl9VU2lmMXdEZGxYX3ZiSDRSTjJxWjdn
  
  I couldn't record screen because apparently the hotkeys were also
  intercepted and I couldn't save the video.
  
+ It makes programming right now super dangerous, as if you press the
+ 'win' button then it's basically 'adios'.
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15.3
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 28 18:00:54 2019
  InstallationDate: Installed on 2018-11-09 (383 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-11-27 (0 days ago)
  VarLogDistupgradeTermlog:

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

Title:
  Stuck on show applications overlay (can't close it)

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hello,

  I've upgraded my ubuntu 19.04 to 19.10 this morning and I came across
  this very annoying bug.

  Whenever I click on 'show applications' or press win key (shortcut),
  the 

[Desktop-packages] [Bug 1854561] Re: Show application renders computer unusable (invisible overlap)

2019-11-30 Thread Damian
Mistakenly created a duplicate of
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1854386

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

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

Title:
  Show application renders computer unusable (invisible overlap)

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Hello,

  I've upgraded my ubuntu 19.04 to 19.10 this morning and I came across
  this very annoying bug.

  Whenever I click on 'show applications' or press win key (shortcut),
  the menu with the applications show, but it's empty - you can search
  through it and it works fine (applications show, one can trigger
  application launch), but then after you select an application, the
  menu doesn't disappear at all.

  It doesn't go away when pressing any application on the dash panel,
  nor when clicking esc key, it only goes away after you click on the
  dash icon again, BUT...

  It doesn't really go away - it just becomes invisible, but still it
  overlaps all the items that are launched (with exception of dash
  panel, because it's not being overlapped), and you can't do anything
  on any launched application. Sometimes when you try to move some
  windows, you can see them getting transformed into a miniature, as if
  the system wanted to insert application into the suggestions on the
  'show applications'.

  The only thing that worked for me was restarting my computer.

  It seems like a similar issue to this: 
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1633
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/1686

  It don't know exactly which package this problem lies in, but it might
  be gnome-shell (you would know better). Might be that the problem is
  already solved, and just bumping the gnome package would solve it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1854561/+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 1854386] Re: Show application renders computer unusable (invisible overlap)

2019-11-30 Thread Damian
It seems like a similar issue to this: 
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1633
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1686

It don't know exactly which package this problem lies in, but it might
be gnome-shell (you would know better). Might be that the problem is
already solved, and just bumping the gnome package would solve it.

** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-shell
(Ubuntu)

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1633
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1633

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1686
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1686

** Summary changed:

- Show application renders computer unusable (invisible overlap)
+ Stuck on show applications overlay (can't close it)

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

Title:
  Stuck on show applications overlay (can't close it)

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hello,

  I've upgraded my ubuntu 19.04 to 19.10 this morning and I came across
  this very annoying bug.

  Whenever I click on 'show applications' or press win key (shortcut),
  the menu with the applications show, but it's empty - you can search
  through it and it works fine (applications show, one can trigger
  application launch), but then after you select an application, the
  menu doesn't disappear at all.

  It doesn't go away when pressing any application on the dash panel,
  nor when clicking esc key, it only goes away after you click on the
  dash icon again, BUT...

  It doesn't really go away - it just becomes invisible, but still it
  overlaps all the items that are launched (with exception of dash
  panel, because it's not being overlapped), and you can't do anything
  on any launched application. Sometimes when you try to move some
  windows, you can see them getting transformed into a miniature, as if
  the system wanted to insert application into the suggestions on the
  'show applications'.

  The only thing that worked for me was restarting my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15.3
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 28 18:00:54 2019
  InstallationDate: Installed on 2018-11-09 (383 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-11-27 (0 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1854386/+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 1854561] [NEW] Show application renders computer unusable (invisible overlap)

2019-11-30 Thread Damian
Public bug reported:

Hello,

I've upgraded my ubuntu 19.04 to 19.10 this morning and I came across
this very annoying bug.

Whenever I click on 'show applications' or press win key (shortcut), the
menu with the applications show, but it's empty - you can search through
it and it works fine (applications show, one can trigger application
launch), but then after you select an application, the menu doesn't
disappear at all.

It doesn't go away when pressing any application on the dash panel, nor
when clicking esc key, it only goes away after you click on the dash
icon again, BUT...

It doesn't really go away - it just becomes invisible, but still it
overlaps all the items that are launched (with exception of dash panel,
because it's not being overlapped), and you can't do anything on any
launched application. Sometimes when you try to move some windows, you
can see them getting transformed into a miniature, as if the system
wanted to insert application into the suggestions on the 'show
applications'.

The only thing that worked for me was restarting my computer.

It seems like a similar issue to this: 
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1633
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1686

It don't know exactly which package this problem lies in, but it might
be gnome-shell (you would know better). Might be that the problem is
already solved, and just bumping the gnome package would solve it.

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

** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-shell
(Ubuntu)

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

Title:
  Show application renders computer unusable (invisible overlap)

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Hello,

  I've upgraded my ubuntu 19.04 to 19.10 this morning and I came across
  this very annoying bug.

  Whenever I click on 'show applications' or press win key (shortcut),
  the menu with the applications show, but it's empty - you can search
  through it and it works fine (applications show, one can trigger
  application launch), but then after you select an application, the
  menu doesn't disappear at all.

  It doesn't go away when pressing any application on the dash panel,
  nor when clicking esc key, it only goes away after you click on the
  dash icon again, BUT...

  It doesn't really go away - it just becomes invisible, but still it
  overlaps all the items that are launched (with exception of dash
  panel, because it's not being overlapped), and you can't do anything
  on any launched application. Sometimes when you try to move some
  windows, you can see them getting transformed into a miniature, as if
  the system wanted to insert application into the suggestions on the
  'show applications'.

  The only thing that worked for me was restarting my computer.

  It seems like a similar issue to this: 
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1633
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/1686

  It don't know exactly which package this problem lies in, but it might
  be gnome-shell (you would know better). Might be that the problem is
  already solved, and just bumping the gnome package would solve it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1854561/+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 1854386] [NEW] Show application renders computer unusable (invisible overlap)

2019-11-30 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Hello,

I've upgraded my ubuntu 19.04 to 19.10 this morning and I came across
this very annoying bug.

Whenever I click on 'show applications' or press win key (shortcut), the
menu with the applications show, but it's empty - you can search through
it and it works fine (applications show, one can trigger application
launch), but then after you select an application, the menu doesn't
disappear at all.

It doesn't go away when pressing any application on the dash panel, nor
when clicking esc key, it only goes away after you click on the dash
icon again, BUT...

It doesn't really go away - it just becomes invisible, but still it
overlaps all the items that are launched (with exception of dash panel,
because it's not being overlapped), and you can't do anything on any
launched application. Sometimes when you try to move some windows, you
can see them getting transformed into a miniature, as if the system
wanted to insert application into the suggestions on the 'show
applications'.

The only thing that worked for me was restarting my computer.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubuntu-release-upgrader-core 1:19.10.15.3
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 28 18:00:54 2019
InstallationDate: Installed on 2018-11-09 (383 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to eoan on 2019-11-27 (0 days ago)
VarLogDistupgradeTermlog:

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


** Tags: amd64 apport-bug dist-upgrade eoan
-- 
Show application renders computer unusable (invisible overlap)
https://bugs.launchpad.net/bugs/1854386
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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


[Desktop-packages] [Bug 1854561] [NEW] Show application renders computer unusable (invisible overlap)

2019-11-30 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Hello,

I've upgraded my ubuntu 19.04 to 19.10 this morning and I came across
this very annoying bug.

Whenever I click on 'show applications' or press win key (shortcut), the
menu with the applications show, but it's empty - you can search through
it and it works fine (applications show, one can trigger application
launch), but then after you select an application, the menu doesn't
disappear at all.

It doesn't go away when pressing any application on the dash panel, nor
when clicking esc key, it only goes away after you click on the dash
icon again, BUT...

It doesn't really go away - it just becomes invisible, but still it
overlaps all the items that are launched (with exception of dash panel,
because it's not being overlapped), and you can't do anything on any
launched application. Sometimes when you try to move some windows, you
can see them getting transformed into a miniature, as if the system
wanted to insert application into the suggestions on the 'show
applications'.

The only thing that worked for me was restarting my computer.

It seems like a similar issue to this: 
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1633
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1686

It don't know exactly which package this problem lies in, but it might
be gnome-shell (you would know better). Might be that the problem is
already solved, and just bumping the gnome package would solve it.

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

-- 
Show application renders computer unusable (invisible overlap)
https://bugs.launchpad.net/bugs/1854561
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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


[Desktop-packages] [Bug 1852053] Re: Nautilus Crashes when opening search field and entering first character

2019-11-30 Thread Tom
The problem is back. But not frequent enough yet to let me catch it
properly, I did get after running 'nautilius -q":

Traceback (most recent call last):
  File 
"/home/tom/.local/share/nautilus-python/extensions/nautilus-gsconnect.py", line 
49, in 
localedir=LOCALE_DIR)
  File "/usr/lib/python2.7/gettext.py", line 560, in translation
raise IOError(ENOENT, 'No translation file found for domain', domain)
IOError: [Errno 2] No translation file found for domain: 
'org.gnome.Shell.Extensions.GSConnect'
Initializing nautilus-font-manager extension

I see "GSConnect" there and I do have this Gnome extension. I will
delete it when I can reproduce the error better.

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

Title:
  Nautilus Crashes when opening search field and entering first
  character

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Upgraded to 19.10 one week ago. Then all worked fine. Nothing major
  changed as far as I know. But now:

  - click in Dock on the file stack icon to open Nautilus
  - stay in Home or browse to any folder
  - click Ctrl-F to open search field at the top of window
  - enter any character as first character of search pattern
  - Nautilus immediately crashes and window disappears immediately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852053/+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