[Touch-packages] [Bug 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge
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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843733] Re: fftw3 ftbfs in eoan (armhf only)
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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge
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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge
** 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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge
** 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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge
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 Ubuntu
Touch seeded 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
[Touch-packages] [Bug 1854608] [NEW] Screen Flickering during Boot up
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 Ubuntu Touch seeded 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.cha
[Touch-packages] [Bug 1854588] Re: Clicking 'Install' on gdebi-gtk makes it vanish ONLY when .deb opened from Chrome/Firefox
The following workaround doesn't remove anything and allows the wrapper to survive updates: sudo -i printf '#!/bin/sh\n\n/usr/share/gdebi/gdebi-gtk "$@"\n' > /usr/local/bin/gdebi-gtk chmod +x /usr/local/bin/gdebi-gtk exit -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1854588 Title: Clicking 'Install' on gdebi-gtk makes it vanish ONLY when .deb opened from Chrome/Firefox Status in Ubuntu MATE: New Status in gdebi package in Ubuntu: New Bug description: Before anyone says this bug already exists... it doesn't (at least as far as I can see). It's just that a lot of similar bugs do/did exist where people have also experienced the same symptoms (of gdebi-gtk vanishing upon clicking 'Install'). So yes this is the same symptoms, but it must be a different cause as the circumstances are different and doesn't have the same resolution. The meat of it... Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or with Chrome if you installed that) go to any site that offers a .deb package and either... a) choose to open it directly from the browser (rather than saving it to 'Downloads' folder) b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that file from within the browser itself. You should find that gdebi-gtk appears but vanishes the moment you click 'Install' without a prompt for a password, an explanation or the package actually getting installed. This bug has existed since the beginning of Ubuntu 18.04 however it's been largely confused with other similar bugs. I've had it on half a dozen machines and confirmed it exists with IRC users on #ubuntu-mate of freenode. However with *this* bug (compared to others) gdebi-gtk works perfectly fine if you run it from the terminal or just double click the .deb package from your file manager. It's the kind of bug which if you're a hardened desktop Linux user, you'd just work around it... But if you're a novice and you can't get a simple thing like Teamviewer installed (which is a .deb, and a thing I might ask someone to do over the phone to try to help them) you likely get fed up and re-install Windows :S Any input on this would be brilliant as I can't seem to get any logs/output. ~lantizia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1854588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845741] Re: package libpam-runtime 1.1.8-3.6ubuntu2 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le
[Expired for pam (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pam (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1845741 Title: package libpam-runtime 1.1.8-3.6ubuntu2 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. Status in pam package in Ubuntu: Expired Bug description: je ne peux telecharger aucune application toujours il me notifie qu'il au probléme ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpam-runtime 1.1.8-3.6ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: libpam-runtime:amd64: Configure cups-browsed:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Sep 28 00:43:19 2019 DpkgTerminalLog: dpkg: erreur de traitement du paquet libpam-runtime (--configure) : le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. InstallationDate: Installed on 2018-05-12 (503 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] Aucun fichier ou dossier de ce type: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.3ubuntu0.1 SourcePackage: pam Title: package libpam-runtime 1.1.8-3.6ubuntu2 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1845741/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1002978] Re: [meta-bug] Inverted Internal microphone (phase inversion)
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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764172] Re: Unable to change hostname specified during Bionic server installation
** Summary changed: - Unable to change hostname + Unable to change hostname specified during Bionic server installation ** Also affects: subiquity (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Unable to change hostname specified during Bionic server installation + Unable to change hostname from the one specified during Bionic server installation -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hostname in Ubuntu. https://bugs.launchpad.net/bugs/1764172 Title: Unable to change hostname from the one specified during Bionic server installation Status in hostname package in Ubuntu: Confirmed Status in subiquity package in Ubuntu: New Bug description: In Bionic Beta 2 I am not able on a host or in a guest VM to change the hostname of a Bionic Beta 2 installation by changing /etc/hostname. The name in the file can be changed but it always reverts to the hostname configured during installation. In the following thread on the topic it is suggested to remove a number of cloud packages. When doing this in a VM install I could change the hostname again via /etc/hostname. https://ubuntuforums.org/showthread.php?t=2389098&page=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hostname/+bug/1764172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764172] Re: Unable to change hostname
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: hostname (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hostname in Ubuntu. https://bugs.launchpad.net/bugs/1764172 Title: Unable to change hostname from the one specified during Bionic server installation Status in hostname package in Ubuntu: Confirmed Status in subiquity package in Ubuntu: New Bug description: In Bionic Beta 2 I am not able on a host or in a guest VM to change the hostname of a Bionic Beta 2 installation by changing /etc/hostname. The name in the file can be changed but it always reverts to the hostname configured during installation. In the following thread on the topic it is suggested to remove a number of cloud packages. When doing this in a VM install I could change the hostname again via /etc/hostname. https://ubuntuforums.org/showthread.php?t=2389098&page=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hostname/+bug/1764172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
Launchpad has imported 1 comments from the remote bug at https://sourceware.org/bugzilla/show_bug.cgi?id=25237. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2019-11-30T23:38:36+00:00 Balint Reczey wrote: Created attachment 12095 Patch adjusting offset to stay in the file This itself was tolerated for long time, but WSL's ELF loader crashes due to the offset and it seems to be easy to fix. Reply at: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1843479/comments/7 ** Changed in: binutils Status: Unknown => New ** Changed in: binutils Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in binutils: New Status in binutils package in Ubuntu: In Progress Status in gzip package in Ubuntu: In Progress Bug description: Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1843479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 90085] Re: When /tmp is mounted noexec, preconfigure fails
@jblainemitre indeed - but presumably one can pick any directory? I'm assuming there's no particular requirement that the selected dir is world-writeable like /tmp and /var/tmp (or at least there doesn't seem to be in my setup?) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/90085 Title: When /tmp is mounted noexec, preconfigure fails Status in debconf package in Ubuntu: Triaged Status in debconf package in Debian: Confirmed Bug description: Binary package hint: mysql-server /tmp mounted noexec, this ensues: Preconfiguring packages ... Can't exec "/tmp/mysql-server-5.0.config.89611": Permission denied at /usr/share/perl/5.8/IPC/Open3.pm line 168. open2: exec of /tmp/mysql-server-5.0.config.89611 configure failed at /usr/share/perl5/Debconf/ConfModule.pm line 57 mysql-server-5.0 failed to preconfigure, with exit status 2 ace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/90085/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854595] Re: package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: openssl (Ubuntu) Importance: Undecided => Low ** Changed in: openssl (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1854595 Title: package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1 Status in openssl package in Ubuntu: Invalid Bug description: I was doing a partial upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Sat Nov 30 19:02:39 2019 ErrorMessage: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-06-13 (1631 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: openssl Title: package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1854595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
** Bug watch added: Sourceware.org Bugzilla #25237 https://sourceware.org/bugzilla/show_bug.cgi?id=25237 ** Also affects: binutils via https://sourceware.org/bugzilla/show_bug.cgi?id=25237 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in binutils: Unknown Status in binutils package in Ubuntu: In Progress Status in gzip package in Ubuntu: In Progress Bug description: Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1843479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854595] Re: package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1854595 Title: package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1 Status in openssl package in Ubuntu: New Bug description: I was doing a partial upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Sat Nov 30 19:02:39 2019 ErrorMessage: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-06-13 (1631 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: openssl Title: package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1854595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854595] [NEW] package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error ex
Public bug reported: I was doing a partial upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Sat Nov 30 19:02:39 2019 ErrorMessage: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-06-13 (1631 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: openssl Title: package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1854595 Title: package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1 Status in openssl package in Ubuntu: New Bug description: I was doing a partial upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Sat Nov 30 19:02:39 2019 ErrorMessage: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-06-13 (1631 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: openssl Title: package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1854595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 940030] Re: rsyslog stops working after logrotate until restarted
Has been hit by this bug on two of my servers apparently (both 18.04.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/940030 Title: rsyslog stops working after logrotate until restarted Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Bionic: Fix Released Bug description: This could otherwise be titled, rsyslog reload does not create log files; only restart does. This is happening on a number of machines I work on. It's happening on 10.04 and 11.04. It might be similar to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/407862 But in my case after the restart there is no /var/log/syslog being created, nor auth.log, kern.log, etc. The files are rotated, rsyslog is reloaded, and none of the log files are created and nothing is being logged. This has been plaguing my systems since moving from syslog-ng, which I may return to as it seems it was actually production ready. Without manually restarting those files don't exist so here's what I did on an 11.04 system: logrotate --force --verbose /etc/logrotate.conf gives: rotating pattern: /var/log/syslog forced from command line (7 rotations) empty log files are not rotated, old logs are removed considering log /var/log/syslog log /var/log/syslog does not exist -- skipping not running postrotate script, since no logs were rotated rotating pattern: /var/log/mail.info /var/log/mail.warn /var/log/mail.err /var/log/mail.log /var/log/daemon.log /var/log/kern.log /var/log/auth.log /var/log/user.log /var/log/lpr.log /var/log/cron.log /var/log/debug /var/log/messages forced from command line (4 rotations) empty log files are not rotated, old logs are removed considering log /var/log/mail.info log /var/log/mail.info does not exist -- skipping considering log /var/log/mail.warn log /var/log/mail.warn does not exist -- skipping considering log /var/log/mail.err log does not need rotating considering log /var/log/mail.log log does not need rotating considering log /var/log/daemon.log log /var/log/daemon.log does not exist -- skipping considering log /var/log/kern.log log /var/log/kern.log does not exist -- skipping considering log /var/log/auth.log log /var/log/auth.log does not exist -- skipping considering log /var/log/user.log log /var/log/user.log does not exist -- skipping considering log /var/log/lpr.log log /var/log/lpr.log does not exist -- skipping considering log /var/log/cron.log log /var/log/cron.log does not exist -- skipping considering log /var/log/debug log /var/log/debug does not exist -- skipping considering log /var/log/messages log /var/log/messages does not exist -- skipping not running postrotate script, since no logs were rotated Then /sbin/reload rsyslog logger -i testing At this point there is no /var/log/syslog Then: /sbin/restart rsyslog And voila there is a /var/log/syslog beginning with: Feb 23 19:24:48 somehost kernel: imklog 4.6.4, log source = /proc/kmsg started. Feb 23 19:24:48 somehost rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="2299" x-info="http://www.rsyslog.com";] (re)start Feb 23 19:24:48 somehost rsyslogd: rsyslogd's groupid changed to 114 Feb 23 19:24:48 somehost rsyslogd: rsyslogd's userid changed to 108 Then to recreate: logrotate --force --verbose /etc/logrotate.conf rotating pattern: /var/log/syslog forced from command line (7 rotations) empty log files are not rotated, old logs are removed considering log /var/log/syslog log needs rotating rotating log /var/log/syslog, log->rotateCount is 7 dateext suffix '-20120223' glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]' compressing log with: /bin/gzip renaming /var/log/syslog to /var/log/syslog-20120223 running postrotate script removing old log /var/log/syslog-20111219.gz rotating pattern: /var/log/mail.info /var/log/mail.warn /var/log/mail.err /var/log/mail.log /var/log/daemon.log /var/log/kern.log /var/log/auth.log /var/log/user.log /var/log/lpr.log /var/log/cron.log /var/log/debug /var/log/messages forced from command line (4 rotations) empty log files are not rotated, old logs are removed considering log /var/log/mail.info log /var/log/mail.info does not exist -- skipping considering log /var/log/mail.warn log /var/log/mail.warn does not exist -- skipping considering log /var/log/mail.err log does not need rotating considering log /var/log/mail.log log does not need rotating considering log /var/log/daemon.log log /var/log/daemon.log does not exist -- skipping considering log /var/log/kern.log log needs rotating considering log /var/log/auth.log log needs rotating considering log /var/l
[Touch-packages] [Bug 1727470] Re: [RFE] Automatically update the Ubuntu version strings in python-apt
Any chance this could be improved? It is really frustrating that we have to manually translate this string every time before a new Ubuntu release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1727470 Title: [RFE] Automatically update the Ubuntu version strings in python-apt Status in Ubuntu Translations: Triaged Status in python-apt package in Ubuntu: Triaged Bug description: Every time there is a new Ubuntu release, some strings need to be manually translated although the only thing that is changing is the Ubuntu version and code name. Please, consider updating these strings automatically based on a translated template. It would help many translators. These strings are: Ubuntu xx.yy 'Code Name' Cdrom with Ubuntu xx.yy 'Code Name' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1727470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
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 Ubuntu Touch seeded packages, which is subscribed to lightdm 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854588] Re: Clicking 'Install' on gdebi-gtk makes it vanish ONLY when .deb opened from Chrome/Firefox
Goes back further than Ubuntu 18.04 then... https://stackoverflow.com/questions/49214954/gdebi-refusing-to-render- service-to-dead-parents ** Also affects: gdebi (Ubuntu) Importance: Undecided Status: New ** Description changed: Before anyone says this bug already exists... it doesn't (at least as far as I can see). It's just that a lot of similar bugs do/did exist where people have also experienced the same symptoms (of gdebi-gtk vanishing upon clicking 'Install'). So yes this is the same symptoms, but it must be a different cause as the circumstances are different and doesn't have the same resolution. The meat of it... - Basically on a fresh install of Ubuntu 18.04.3 amd64... with Firefox (or with Chrome if you installed that) go to any site that offers a .deb package and either... + Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or with Chrome if you installed that) go to any site that offers a .deb package and either... a) choose to open it directly from the browser (rather than saving it to 'Downloads' folder) b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that file from within the browser itself. You should find that gdebi-gtk appears but vanishes the moment you click 'Install' without a prompt for a password, an explanation or the package actually getting installed. This bug has existed since the beginning of Ubuntu 18.04 however it's been largely confused with other similar bugs. I've had it on half a dozen machines and confirmed it exists with IRC users on #ubuntu-mate of freenode. However with *this* bug (compared to others) gdebi-gtk works perfectly fine if you run it from the terminal or just double click the .deb package from your file manager. It's the kind of bug which if you're a hardened desktop Linux user, you'd just work around it... But if you're a novice and you can't get a simple thing like Teamviewer installed (which is a .deb, and a thing I might ask someone to do over the phone to try to help them) you likely get fed up and re-install Windows :S Any input on this would be brilliant as I can't seem to get any logs/output. ~lantizia -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1854588 Title: Clicking 'Install' on gdebi-gtk makes it vanish ONLY when .deb opened from Chrome/Firefox Status in Ubuntu MATE: New Status in gdebi package in Ubuntu: New Bug description: Before anyone says this bug already exists... it doesn't (at least as far as I can see). It's just that a lot of similar bugs do/did exist where people have also experienced the same symptoms (of gdebi-gtk vanishing upon clicking 'Install'). So yes this is the same symptoms, but it must be a different cause as the circumstances are different and doesn't have the same resolution. The meat of it... Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or with Chrome if you installed that) go to any site that offers a .deb package and either... a) choose to open it directly from the browser (rather than saving it to 'Downloads' folder) b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that file from within the browser itself. You should find that gdebi-gtk appears but vanishes the moment you click 'Install' without a prompt for a password, an explanation or the package actually getting installed. This bug has existed since the beginning of Ubuntu 18.04 however it's been largely confused with other similar bugs. I've had it on half a dozen machines and confirmed it exists with IRC users on #ubuntu-mate of freenode. However with *this* bug (compared to others) gdebi-gtk works perfectly fine if you run it from the terminal or just double click the .deb package from your file manager. It's the kind of bug which if you're a hardened desktop Linux user, you'd just work around it... But if you're a novice and you can't get a simple thing like Teamviewer installed (which is a .deb, and a thing I might ask someone to do over the phone to try to help them) you likely get fed up and re-install Windows :S Any input on this would be brilliant as I can't seem to get any logs/output. ~lantizia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1854588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444880] Re: xrandr report inverted gamma values
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&A: [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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854583] [NEW] [ProLiant MicroServer Gen8, Nvidia GPU 81 HDMI/DP, Digital Out, HDMI] Sound is distorted
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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854582] [NEW] systemd-timesyncd.service not starting
Public bug reported: Kubuntu -19.10 (though I believe the problem also exists on prior versions) Time synchronization not working: -- greenman@Crynfyd19.10 /lib/systemd/system$ timedatectl status Local time: Sat 2019-11-30 08:21:57 PST Universal time: Sat 2019-11-30 16:21:57 UTC RTC time: Sat 2019-11-30 16:21:57 Time zone: America/Los_Angeles (PST, -0800) System clock synchronized: no NTP service: inactive RTC in local TZ: no greenman@Crynfyd19.10 /lib/systemd/system$ sudo systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-timesyncd.service.d └─disable-with-time-daemon.conf Active: inactive (dead) since Sat 2019-11-30 08:21:28 PST; 2min 0s ago Condition: start condition failed at Sat 2019-11-30 08:23:15 PST; 12s ago └─ ConditionFileIsExecutable=!/usr/sbin/VBoxService was not met Docs: man:systemd-timesyncd.service(8) Main PID: 813 (code=exited, status=0/SUCCESS) Status: "Shutting down..." Nov 30 07:29:50 Crynfyd systemd[1]: Starting Network Time Synchronization... Nov 30 07:29:51 Crynfyd systemd[1]: Started Network Time Synchronization. Nov 30 07:30:21 Crynfyd systemd-timesyncd[813]: Synchronized to time server for the first time 91.189. Nov 30 08:21:28 Crynfyd systemd[1]: Stopping Network Time Synchronization... Nov 30 08:21:28 Crynfyd systemd[1]: systemd-timesyncd.service: Succeeded. Nov 30 08:21:28 Crynfyd systemd[1]: Stopped Network Time Synchronization. Nov 30 08:23:15 Crynfyd systemd[1]: Condition check resulted in Network Time Synchronization being ski -- The problem has to do with the file /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf; -- greenman@Crynfyd19.10 /lib/systemd/system/systemd-timesyncd.service.d$ cat disable-with-time-daemon.conf [Unit] # don't run timesyncd if we have another NTP daemon installed ConditionFileIsExecutable=!/usr/sbin/ntpd ConditionFileIsExecutable=!/usr/sbin/openntpd ConditionFileIsExecutable=!/usr/sbin/chronyd ConditionFileIsExecutable=!/usr/sbin/VBoxService -- I do have virtualbox installed, but not running, so VBoxService is not running. This means that although the binary is there, it is not providing time sync services, so the system is not time syncing. If I remove the line "ConditionFileIsExecutable=!/usr/sbin/VBoxService" from the file and restart, all is well: -- greenman@Crynfyd19.10 /lib/systemd/system/systemd-timesyncd.service.d$ sudo systemctl daemon-reload greenman@Crynfyd19.10 /lib/systemd/system/systemd-timesyncd.service.d$ sudo systemctl restart systemd-timesyncd.service greenman@Crynfyd19.10 /lib/systemd/system/systemd-timesyncd.service.d$ timedatectl status Local time: Sat 2019-11-30 08:29:43 PST Universal time: Sat 2019-11-30 16:29:43 UTC RTC time: Sat 2019-11-30 16:29:43 Time zone: America/Los_Angeles (PST, -0800) System clock synchronized: yes NTP service: active RTC in local TZ: no -- So instead of testing just for the existence of the binary, which is resulting in no time sync service, what it probably should do is check for a running process, and allow the service to start if no other time syncing service is running. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1854582 Title: systemd-timesyncd.service not starting Status in systemd package in Ubuntu: New Bug description: Kubuntu -19.10 (though I believe the problem also exists on prior versions) Time synchronization not working: -- greenman@Crynfyd19.10 /lib/systemd/system$ timedatectl status Local time: Sat 2019-11-30 08:21:57 PST Universal time: Sat 2019-11-30 16:21:57 UTC RTC time: Sat 2019-11-30 16:21:57 Time zone: America/Los_Angeles (PST, -0800) System clock synchronized: no NTP service: inactive RTC in local TZ: no greenman@Crynfyd19.10 /lib/systemd/system$ sudo systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-timesyncd.service.d └─disable-with-time-daemon.conf Active: inactive (dead) since Sat 2019-11-30 08:21:28 PST; 2min 0s ago Condition: start condition failed at Sat 2019-11-30 08:23:15 PST; 12s ago └─ ConditionFileIsExecutable=!/usr/sbin/VBoxServi
[Touch-packages] [Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
While this is a bug in WSL's ELF loader I located to problem in binutil's strip and after the fix passed my testing I'll send it upstream and also SRU it to Eoan to let us rebuild affected packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in binutils package in Ubuntu: In Progress Status in gzip package in Ubuntu: In Progress Bug description: Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1843479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854581] [NEW] Bluetooth disconnect on 16.04
Public bug reported: Bluetooth disconnect randomly and is out of order since I restart the computer. Stop and restart BT service doesn't change the issue. This happen on Asus M70V computer. sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since sam. 2019-11-30 16:57:58 CET; 2s ago Docs: man:bluetoothd(8) Main PID: 21551 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─21551 /usr/lib/bluetooth/bluetoothd bluetoothd[21551]: Not enough free handles to register service bluetoothd[21551]: Not enough free handles to register service bluetoothd[21551]: Current Time Service could not be registered bluetoothd[21551]: gatt-time-server: Input/output error (5) bluetoothd[21551]: Not enough free handles to register service bluetoothd[21551]: Not enough free handles to register service bluetoothd[21551]: Sap driver initialization failed. bluetoothd[21551]: sap-server: Operation not permitted (1) bluetoothd[21551]: Endpoint registered: sender=:1.153 path=/MediaEndpoint/A2DPSource nov. 30 16:57:58 happy-buntu bluetoothd[21551]: Endpoint registered: sender=:1.153 path=/MediaEndpoint/A2DPSink Thanks for help ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.4.0-169.198-generic 4.4.197 Uname: Linux 4.4.0-169-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Nov 30 17:00:50 2019 InstallationDate: Installed on 2018-04-16 (593 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK Computer Inc. M70Vn ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-169-generic root=UUID=d3601bac-5eb3-4f24-a402-9211b2c74282 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M70Vn 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.:bvr206:bd12/21/2009:svnASUSTeKComputerInc.:pnM70Vn:pvr1.0:rvnASUSTeKComputerInc.:rnM70Vn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M70Vn dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 00:22:43:C5:84:05 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:5002654 acl:731390 sco:0 events:294427 errors:0 TX bytes:507962830 acl:587355 sco:0 commands:258 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1854581 Title: Bluetooth disconnect on 16.04 Status in bluez package in Ubuntu: New Bug description: Bluetooth disconnect randomly and is out of order since I restart the computer. Stop and restart BT service doesn't change the issue. This happen on Asus M70V computer. sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since sam. 2019-11-30 16:57:58 CET; 2s ago Docs: man:bluetoothd(8) Main PID: 21551 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─21551 /usr/lib/bluetooth/bluetoothd bluetoothd[21551]: Not enough free handles to register service bluetoothd[21551]: Not enough free handles to register service bluetoothd[21551]: Current Time Service could not be registered bluetoothd[21551]: gatt-time-server: Input/output error (5) bluetoothd[21551]: Not enough free handles to register service bluetoothd[21551]: Not enough free handles to register service bluetoothd[21551]: Sap driver initialization failed. bluetoothd[21551]: sap-server: Operation not permitted (1) bluetoothd[21551]: Endpoint registered: sender=:1.153 path=/MediaEndpoint/A2DPSource nov. 30 16:57:58 happy-buntu bluetoothd[21551]: Endpoint registered: sender=:1.153 path=/MediaEndpoint/A2DPSink Thanks for help ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.4.0-169.198-generic 4.4.197 Uname: Linux 4.4.0-169-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Nov 30 17:00:50 2019 InstallationDate: Installed on 2018-04-16 (593 day
[Touch-packages] [Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
** Also affects: binutils (Ubuntu) Importance: Undecided Status: New ** Changed in: binutils (Ubuntu) Status: New => In Progress ** Changed in: binutils (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) ** Changed in: gzip (Ubuntu) Status: Invalid => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in binutils package in Ubuntu: In Progress Status in gzip package in Ubuntu: In Progress Bug description: Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1843479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854578] UnitySupportTest.txt
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 Ubuntu Touch seeded 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" -
[Touch-packages] [Bug 1854578] UdevDb.txt
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 Ubuntu Touch seeded 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 (2016
[Touch-packages] [Bug 1854578] xdpyinfo.txt
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 Ubuntu Touch seeded 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
[Touch-packages] [Bug 1854578] xserver.devices.txt
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 Ubuntu Touch seeded 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" - R
[Touch-packages] [Bug 1854578] Xrandr.txt
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 Ubuntu Touch seeded 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 (2016
[Touch-packages] [Bug 1854578] XorgLog.txt
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 Ubuntu Touch seeded 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 (2
[Touch-packages] [Bug 1854578] XorgLogOld.txt
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 Ubuntu Touch seeded 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 amd
[Touch-packages] [Bug 1854578] ProcInterrupts.txt
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 Ubuntu Touch seeded 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" - Rel
[Touch-packages] [Bug 1854578] ProcEnviron.txt
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 Ubuntu Touch seeded 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 a
[Touch-packages] [Bug 1854578] ProcCpuinfoMinimal.txt
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 Ubuntu Touch seeded 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 Xeru
[Touch-packages] [Bug 1854578] ProcModules.txt
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 Ubuntu Touch seeded 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 a
[Touch-packages] [Bug 1854578] ProcCpuinfo.txt
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 Ubuntu Touch seeded 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 a
[Touch-packages] [Bug 1854578] Dependencies.txt
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 Ubuntu Touch seeded 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
[Touch-packages] [Bug 1854578] DpkgLog.txt
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 Ubuntu Touch seeded 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 (2
[Touch-packages] [Bug 1854578] Lsusb.txt
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 Ubuntu Touch seeded 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 (201607
[Touch-packages] [Bug 1854578] Lspci.txt
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 Ubuntu Touch seeded 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 (201607
[Touch-packages] [Bug 1854578] CurrentDmesg.txt
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 Ubuntu Touch seeded 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
[Touch-packages] [Bug 1854578] Re: Nvidia driver on ASUS G752VM screen brigtness and touchpad not working
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 ubuntu
[Touch-packages] [Bug 1854578] [NEW] Nvidia driver on ASUS G752VM screen brigtness and touchpad not working
*** 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 Ubuntu Touch seeded 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_propr
[Touch-packages] [Bug 1854565] [NEW] Mouse (not touchpad) right click acts as left click
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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838154] Re: Something hinders XFCE performance. >:]
** 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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838154] Re: Something hinders XFCE performance. >:]
** 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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys
I just upgraded from 16.04 to 18.04 and I'm seeing the same/similar issue. I have the same messages in the log, and I have an encrypted home folder. When I *first* try to log in after a reboot, I get bounced back to the login screen. It then logs in on the second attempt (so far - but this makes me nervous). None of the fixes above have worked for me so far. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1718658 Title: ecryptfs-mount-private fails to initialize ecryptfs keys Status in ecryptfs-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: ecryptfs-mount-private fails to mount the ecryptfs after the 1st reboot after creating the ecryptfs by ecryptfs-setup-private. After the unsucessful attempt dmesg contains: [ 1265.695388] Could not find key with description: [] [ 1265.695393] process_request_key_err: No key [ 1265.695394] Could not find valid key in user session keyring for sig specified in mount option: [] [ 1265.695395] One or more global auth toks could not properly register; rc = [-2] [ 1265.695396] Error parsing options; rc = [-2] Note: The correct key ID has been replaced in the "". I also accidentally found an workaround - just running ecrytpfs- manager and then the ecryptfs-mount-private (it does not ask for password for the second time and mounts the ecryptfs correctly): host:~$ ecryptfs-manager eCryptfs key management menu --- 1. Add passphrase key to keyring 2. Add public key to keyring 3. Generate new public/private keypair 4. Exit Make selection: 4 host:~$ ls Private/ Access-Your-Private-Data.desktop README.txt host:~$ ecryptfs-mount-private host:~$ ls Private/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845046] Re: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected
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 Ubuntu Touch seeded packages, which is subscribed to bluez 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854557] Re: Sync opencv 4.1.2+dfsg-5 (universe) from Debian unstable (main)
** Changed in: opencv (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1854557 Title: Sync opencv 4.1.2+dfsg-5 (universe) from Debian unstable (main) Status in opencv package in Ubuntu: New Bug description: Please sync opencv 4.1.2+dfsg-5 (universe) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Move from libgdcm2-dev to libgdcm-dev. * No-change rebuild against libgdcm3.0 * Rebuild against new libproj15. The Debian package has changed to libgdcm-dev too. Changelog entries since current focal version 4.1.2+dfsg-4ubuntu3: opencv (4.1.2+dfsg-5) unstable; urgency=medium [ Bas Couwenberg ] * Replace libgdbm2-dev with libgdbm-dev, and libvtkgdcm2-dev with libvtkgdcm-dev. (closes: #944341) [ Mo Zhou ] * Add AVX512_COMMON to amd64 dispatch list, and VFPV3,NEON to arm64 list. * Exclude gdcm development packages from B-D on non-release architectures. [ Gianfranco Costamagna ] * Remove builddir-static to save some space (Closes: #943706) -- Mo Zhou Sun, 24 Nov 2019 16:08:26 +0800 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1854557/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854557] [NEW] Sync opencv 4.1.2+dfsg-5 (universe) from Debian unstable (main)
Public bug reported: Please sync opencv 4.1.2+dfsg-5 (universe) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Move from libgdcm2-dev to libgdcm-dev. * No-change rebuild against libgdcm3.0 * Rebuild against new libproj15. The Debian package has changed to libgdcm-dev too. Changelog entries since current focal version 4.1.2+dfsg-4ubuntu3: opencv (4.1.2+dfsg-5) unstable; urgency=medium [ Bas Couwenberg ] * Replace libgdbm2-dev with libgdbm-dev, and libvtkgdcm2-dev with libvtkgdcm-dev. (closes: #944341) [ Mo Zhou ] * Add AVX512_COMMON to amd64 dispatch list, and VFPV3,NEON to arm64 list. * Exclude gdcm development packages from B-D on non-release architectures. [ Gianfranco Costamagna ] * Remove builddir-static to save some space (Closes: #943706) -- Mo Zhou Sun, 24 Nov 2019 16:08:26 +0800 ** Affects: opencv (Ubuntu) Importance: Undecided Status: New ** Tags: focal upgrade-software-version ** Tags added: focal upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1854557 Title: Sync opencv 4.1.2+dfsg-5 (universe) from Debian unstable (main) Status in opencv package in Ubuntu: New Bug description: Please sync opencv 4.1.2+dfsg-5 (universe) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Move from libgdcm2-dev to libgdcm-dev. * No-change rebuild against libgdcm3.0 * Rebuild against new libproj15. The Debian package has changed to libgdcm-dev too. Changelog entries since current focal version 4.1.2+dfsg-4ubuntu3: opencv (4.1.2+dfsg-5) unstable; urgency=medium [ Bas Couwenberg ] * Replace libgdbm2-dev with libgdbm-dev, and libvtkgdcm2-dev with libvtkgdcm-dev. (closes: #944341) [ Mo Zhou ] * Add AVX512_COMMON to amd64 dispatch list, and VFPV3,NEON to arm64 list. * Exclude gdcm development packages from B-D on non-release architectures. [ Gianfranco Costamagna ] * Remove builddir-static to save some space (Closes: #943706) -- Mo Zhou Sun, 24 Nov 2019 16:08:26 +0800 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1854557/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
