[Desktop-packages] [Bug 1816191] Re: Printers partially recognizes network printer, but isn't able to even print a test page
*** This bug is a duplicate of bug 1815307 *** https://bugs.launchpad.net/bugs/1815307 ** Description changed: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1816191 Title: Printers partially recognizes network printer, but isn't able to even print a test page Status in gnome-control-center package in Ubuntu: New Bug description: Printer is Canon iP7250, CUPS version is 2.2.10, Ubuntu 19.04 (2019-02-03 10:50). In Printers panel, I can see it being present without the need to add it - which is great. But I don't see it as an option to print to in GTK print dialogue, I can't select it as default printer from that Printers panel (that option is there in the dropdown menu when I click the cogwheel - but it doesn't seem to do anything - not even mark it as selected). Clicking on Printing options I get a blank window with Test Page button at the top - which doesn't seem to do anything. Sometimes clicking on Printer details (when it's a second time?) crashes the application. After the crash it's no longer visible, but Add new printer restores it - although it then says it searches for drivers and says it had failed adding the printer. When it doesn't crash, clicking on Printer details shows "Address: Canon iP7200 series._ipp._tcp.local:631 Driver: Canon iP7200 Series" Clicking in the screen on select from database, and selecting Canon Pixma iP7250 CUPS+Gutenprint Enables a normal Printing Options dialogue (i.e. not completely empty as before) - but the test page still doesn't print. It's says the printers state is stopped, and localhost:631 says the printer is pointing to file:///dev/null On 18.04 I can print to this printer fine after manually selecting this getenprint driver or using lp -d Canon_iP7200_series Without the need for any drivers installation, however, the Printers panel doesn't add it properly there either (in the automatic way). In this version of Ubuntu, even the lp -d Canon_iP7200_series command doesn't work (says lp: No such file or directory) Also driverless doesn't return anything (it says ipp://41182400.local:631/ipp/print on Ubuntu 18.04) And lpstat -e only occasionally reports seeing the printer (it works consistently on 18.04). Going to additional printer settings... and clicking on adding an ipp printer with the device URI ipp://41182400.local:631/ipp/print (which I know from 18.04 by typing driverless) and selecting the gutenprint driver for Canon Pixma iP7250 does work and prints the test page. But if I didn't know that URI (which I could not see using driverless on this vesion of Ubuntu) - I wouldn't have been able to add my printer. This is even a worse experience than in 18.04 - and the experience there was bad enough (as described in https://bugs.launchpad.net/ubuntu/+source/system-config- printer/+bug/1815307) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.30.2-4ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 15 20:38:48 2019 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1816191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816191] Re: Printers partially recognizes network printer, but isn't able to even print a test page
*** This bug is a duplicate of bug 1815307 *** https://bugs.launchpad.net/bugs/1815307 ** Description changed: Printer is Canon iP7250, CUPS version is 2.2.10, Ubuntu 19.04 (2019-02-03 10:50). In Printers panel, I can see it being present without the need to add it - which is great. But I don't see it as an option to print to in GTK print dialogue, I can't select it as default printer from that Printers panel (that option is there in the dropdown menu when I click the cogwheel - but it doesn't seem to do anything - not even mark it as selected). Clicking on Printing options I get a blank window with Test Page button at the top - which doesn't seem to do anything. Sometimes clicking on Printer details (when it's a second time?) crashes the application. After the crash it's no longer visible, but Add new printer restores it - although it then says it searches for drivers and says it had failed adding the printer. When it doesn't crash, clicking on Printer details shows "Address: Canon iP7200 series._ipp._tcp.local:631 Driver: Canon iP7200 Series" Clicking in the screen on select from database, and selecting Canon Pixma iP7250 CUPS+Gutenprint Enables a normal Printing Options dialogue (i.e. not completely empty as before) - but the test page still doesn't print. It's says the printers state is stopped, and localhost:631 says the printer is pointing to file:///dev/null On 18.04 I can print to this printer fine after manually selecting this getenprint driver or using lp -d Canon_iP7200_series Without the need for any drivers installation, however, the Printers panel doesn't add it properly there either (in the automatic way). In this version of Ubuntu, even the lp -d Canon_iP7200_series command doesn't work (says lp: No such file or directory) Also driverless doesn't return anything (it says ipp://41182400.local:631/ipp/print on Ubuntu 18.04) And lpstat -e only occasionally reports seeing the printer (it works consistently on 18.04). + Going to additional printer settings... and clicking on adding an ipp + printer with the device URI ipp://41182400.local:631/ipp/print + (which I know from 18.04 by typing driverless) and selecting the + gutenprint driver for Canon Pixma iP7250 does work and prints the test + page. + + But if I didn't know that URI (which I could not see using driverless on + this vesion of Ubuntu) - I wouldn't have been able to add my printer. + This is even a worse experience than in 18.04 - and the experience there + was bad enough (as described in + https://bugs.launchpad.net/ubuntu/+source/system-config- + printer/+bug/1815307) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.30.2-4ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 15 20:38:48 2019 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1816191 Title: Printers partially recognizes network printer, but isn't able to even print a test page Status in gnome-control-center package in Ubuntu: New Bug description: Printer is Canon iP7250, CUPS version is 2.2.10, Ubuntu 19.04 (2019-02-03 10:50). In Printers panel, I can see it being present without the need to add it - which is great. But I don't see it as an option to print to in GTK print dialogue, I can't select it as default printer from that Printers panel (that option is there in the dropdown menu when I click the cogwheel - but it doesn't seem to do anything - not even mark it as selected). Clicking on Printing options I get a blank window with Test Page button at the top - which doesn't seem to do anything. Sometimes clicking on Printer details (when it's a second time?) crashes the application. After the crash it's no longer visible, but Add new printer restores it - although it then says it searches for drivers and says it had failed adding the printer. When it doesn't crash, clicking on Printer details shows "Address: Canon iP7200 series._ipp._tcp.local:631 Driver: Canon iP7200 Series" Clicking in the screen on select from database, and selecting Canon Pixma iP7250 CUPS+Gutenprint Enables a normal Printing Options dialogue (i.e. not completely empty as before) - but the test page still doesn't print. It's says the printers state is
[Desktop-packages] [Bug 1815307] Re: ipp printer isn't shown automatically - adding it errors with a CUPS internal error
@till-kamppeter > The issues referenced in the previous comment are all fixed upstream now. If they were the cause for > your problem, your problem will be solved in Disco. I've just tested this using Disco, and it's even worse there - see my bug report: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1816191 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1815307 Title: ipp printer isn't shown automatically - adding it errors with a CUPS internal error Status in cups package in Ubuntu: Triaged Bug description: System: Ubuntu 18.04 system-config-printer version: 1.5.11-1ubuntu printer: Canon iP7250 I expect to be able to see the printer in the panel just as 'lpstat -l -e' or 'driverless' can see them, without the need to especially add a new printer. And if I do need to add it (don't see why that should be the case, but still), I expect that choosing the printer's name under network would result in adding the printer. What happened instead: Canon iP7250 isn't shown in the Printers panel, clicking on add and expanding the network options - it is shown, but when trying to add it (either driverless IPP, LPD via DNS-SD or IPP via DNS-SD) it gives an error about CUPS internal error. `$ lpstat -l -e` gives `Canon_iP7200_series network none ipp://Canon%20iP7200%20series._ipp._tcp.local/` So the system does see it, and `lp -d Canon_iP7200_series /etc/nsswitch.conf` does print (and for a minute the printer is shown in the Printers panel - but then disappears). I can add it by *not* clicking on the printer's name under Network, but rather, click on ipp printer and manually choose Canon -> iP7200 -> CUPS+Gutenprint driver (and not the recommended driverless option - which, if I choose results in that same cryptic error I get when trying to add the printer by clicking on it, as described above). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1815307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816191] Re: Printers partially recognizes network printer, but isn't able to even print a test page
** Description changed: Printer is Canon iP7250, CUPS version is 2.2.10, Ubuntu 19.04 (2019-02-03 10:50). In Printers panel, I can see it being present without the need to add it - which is great. But I don't see it as an option to print to in GTK print dialogue, I can't select it as default printer from that Printers panel (that option is there in the dropdown menu when I click the cogwheel - but it doesn't seem to do anything - not even mark it as selected). Clicking on Printing options I get a blank window with Test Page button at the top - which doesn't seem to do anything. Sometimes clicking on Printer details (when it's a second time?) crashes the application. After the crash it's no longer visible, but Add new printer restores it - although it then says it searches for drivers and says it had failed adding the printer. When it doesn't crash, clicking on Printer details shows "Address: Canon iP7200 series._ipp._tcp.local:631 Driver: Canon iP7200 Series" Clicking in the screen on select from database, and selecting Canon Pixma iP7250 CUPS+Gutenprint Enables a normal Printing Options dialogue (i.e. not completely empty as before) - but the test page still doesn't print. It's says the printers state is stopped, and localhost:631 says the printer is pointing to file:///dev/null On 18.04 I can print to this printer fine after manually selecting this getenprint driver or using lp -d Canon_iP7200_series - Without the need for any drivers installation, however, the Printers panel doesn't add it properly there either (in the automatic way). In this version of Ubuntu, even the + Without the need for any drivers installation, however, the Printers panel doesn't add it properly there either (in the automatic way). In this version of Ubuntu, even the lp -d Canon_iP7200_series command doesn't work (says lp: No such file or directory) + + Also driverless doesn't return anything (it says + ipp://41182400.local:631/ipp/print on Ubuntu 18.04) + + And lpstat -e only occasionally reports seeing the printer (it works + consistently on 18.04). + ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.30.2-4ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 15 20:38:48 2019 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANG=C.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANG=C.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1816191 Title: Printers partially recognizes network printer, but isn't able to even print a test page Status in gnome-control-center package in Ubuntu: New Bug description: Printer is Canon iP7250, CUPS version is 2.2.10, Ubuntu 19.04 (2019-02-03 10:50). In Printers panel, I can see it being present without the need to add it - which is great. But I don't see it as an option to print to in GTK print dialogue, I can't select it as default printer from that Printers panel (that option is there in the dropdown menu when I click the cogwheel - but it doesn't seem to do anything - not even mark it as selected). Clicking on Printing options I get a blank window with Test Page button at the top - which doesn't seem to do anything. Sometimes clicking on Printer details (when it's a second time?) crashes the application. After the crash it's no longer visible, but Add new printer restores it - although it then says it searches for drivers and says it had failed adding the printer. When it doesn't crash, clicking on Printer details shows "Address: Canon iP7200 series._ipp._tcp.local:631 Driver: Canon iP7200 Series" Clicking in the screen on select from database, and selecting Canon Pixma iP7250 CUPS+Gutenprint Enables a normal Printing Options dialogue (i.e. not completely empty as before) - but the test page still doesn't print. It's says the printers state is stopped, and localhost:631 says the printer is pointing to file:///dev/null On 18.04 I can print to this printer fine after manually selecting this getenprint driver or using lp -d Canon_iP7200_series Without the need for any drivers installation, however, the Printers panel doesn't add it properly there either (in the automatic way). In this version of Ubuntu, even the lp -d Canon_iP7200_series command doesn't work (says lp: No such file or
[Desktop-packages] [Bug 1816191] [NEW] Printers partially recognizes network printer, but isn't able to even print a test page
Public bug reported: Printer is Canon iP7250, CUPS version is 2.2.10, Ubuntu 19.04 (2019-02-03 10:50). In Printers panel, I can see it being present without the need to add it - which is great. But I don't see it as an option to print to in GTK print dialogue, I can't select it as default printer from that Printers panel (that option is there in the dropdown menu when I click the cogwheel - but it doesn't seem to do anything - not even mark it as selected). Clicking on Printing options I get a blank window with Test Page button at the top - which doesn't seem to do anything. Sometimes clicking on Printer details (when it's a second time?) crashes the application. After the crash it's no longer visible, but Add new printer restores it - although it then says it searches for drivers and says it had failed adding the printer. When it doesn't crash, clicking on Printer details shows "Address: Canon iP7200 series._ipp._tcp.local:631 Driver: Canon iP7200 Series" Clicking in the screen on select from database, and selecting Canon Pixma iP7250 CUPS+Gutenprint Enables a normal Printing Options dialogue (i.e. not completely empty as before) - but the test page still doesn't print. It's says the printers state is stopped, and localhost:631 says the printer is pointing to file:///dev/null On 18.04 I can print to this printer fine after manually selecting this getenprint driver or using lp -d Canon_iP7200_series Without the need for any drivers installation, however, the Printers panel doesn't add it properly there either (in the automatic way). In this version of Ubuntu, even the lp -d Canon_iP7200_series command doesn't work (says lp: No such file or directory) Also driverless doesn't return anything (it says ipp://41182400.local:631/ipp/print on Ubuntu 18.04) And lpstat -e only occasionally reports seeing the printer (it works consistently on 18.04). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.30.2-4ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 15 20:38:48 2019 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1816191 Title: Printers partially recognizes network printer, but isn't able to even print a test page Status in gnome-control-center package in Ubuntu: New Bug description: Printer is Canon iP7250, CUPS version is 2.2.10, Ubuntu 19.04 (2019-02-03 10:50). In Printers panel, I can see it being present without the need to add it - which is great. But I don't see it as an option to print to in GTK print dialogue, I can't select it as default printer from that Printers panel (that option is there in the dropdown menu when I click the cogwheel - but it doesn't seem to do anything - not even mark it as selected). Clicking on Printing options I get a blank window with Test Page button at the top - which doesn't seem to do anything. Sometimes clicking on Printer details (when it's a second time?) crashes the application. After the crash it's no longer visible, but Add new printer restores it - although it then says it searches for drivers and says it had failed adding the printer. When it doesn't crash, clicking on Printer details shows "Address: Canon iP7200 series._ipp._tcp.local:631 Driver: Canon iP7200 Series" Clicking in the screen on select from database, and selecting Canon Pixma iP7250 CUPS+Gutenprint Enables a normal Printing Options dialogue (i.e. not completely empty as before) - but the test page still doesn't print. It's says the printers state is stopped, and localhost:631 says the printer is pointing to file:///dev/null On 18.04 I can print to this printer fine after manually selecting this getenprint driver or using lp -d Canon_iP7200_series Without the need for any drivers installation, however, the Printers panel doesn't add it properly there either (in the automatic way). In this version of Ubuntu, even the lp -d Canon_iP7200_series command doesn't work (says lp: No such file or directory) Also driverless doesn't return anything (it says ipp://41182400.local:631/ipp/print on Ubuntu 18.04) And lpstat -e only occasionally reports seeing the printer (it works consistently on 18.04). ProblemType: Bug
[Desktop-packages] [Bug 1815307] Re: ipp printer isn't shown automatically - adding it errors with a CUPS internal error
Also added the ipptool results of the modified test given in https://github.com/OpenPrinting/cups-filters/issues/22 Seems to me that it is a similar issue. ** Attachment added: "ipp_attr2.txt" https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1815307/+attachment/5238085/+files/ipp_attr2.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1815307 Title: ipp printer isn't shown automatically - adding it errors with a CUPS internal error Status in system-config-printer package in Ubuntu: New Bug description: System: Ubuntu 18.04 system-config-printer version: 1.5.11-1ubuntu printer: Canon iP7250 I expect to be able to see the printer in the panel just as 'lpstat -l -e' or 'driverless' can see them, without the need to especially add a new printer. And if I do need to add it (don't see why that should be the case, but still), I expect that choosing the printer's name under network would result in adding the printer. What happened instead: Canon iP7250 isn't shown in the Printers panel, clicking on add and expanding the network options - it is shown, but when trying to add it (either driverless IPP, LPD via DNS-SD or IPP via DNS-SD) it gives an error about CUPS internal error. `$ lpstat -l -e` gives `Canon_iP7200_series network none ipp://Canon%20iP7200%20series._ipp._tcp.local/` So the system does see it, and `lp -d Canon_iP7200_series /etc/nsswitch.conf` does print (and for a minute the printer is shown in the Printers panel - but then disappears). I can add it by *not* clicking on the printer's name under Network, but rather, click on ipp printer and manually choose Canon -> iP7200 -> CUPS+Gutenprint driver (and not the recommended driverless option - which, if I choose results in that same cryptic error I get when trying to add the printer by clicking on it, as described above). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1815307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815307] Re: ipp printer isn't shown automatically - adding it errors with a CUPS internal error
Added the requested result of the ipptool query ** Attachment added: "ipp-attrs.txt" https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1815307/+attachment/5238018/+files/ipp-attrs.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1815307 Title: ipp printer isn't shown automatically - adding it errors with a CUPS internal error Status in system-config-printer package in Ubuntu: Incomplete Bug description: System: Ubuntu 18.04 system-config-printer version: 1.5.11-1ubuntu printer: Canon iP7250 I expect to be able to see the printer in the panel just as 'lpstat -l -e' or 'driverless' can see them, without the need to especially add a new printer. And if I do need to add it (don't see why that should be the case, but still), I expect that choosing the printer's name under network would result in adding the printer. What happened instead: Canon iP7250 isn't shown in the Printers panel, clicking on add and expanding the network options - it is shown, but when trying to add it (either driverless IPP, LPD via DNS-SD or IPP via DNS-SD) it gives an error about CUPS internal error. `$ lpstat -l -e` gives `Canon_iP7200_series network none ipp://Canon%20iP7200%20series._ipp._tcp.local/` So the system does see it, and `lp -d Canon_iP7200_series /etc/nsswitch.conf` does print (and for a minute the printer is shown in the Printers panel - but then disappears). I can add it by *not* clicking on the printer's name under Network, but rather, click on ipp printer and manually choose Canon -> iP7200 -> CUPS+Gutenprint driver (and not the recommended driverless option - which, if I choose results in that same cryptic error I get when trying to add the printer by clicking on it, as described above). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1815307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815307] Re: ipp printer isn't shown automatically - adding it errors with a CUPS internal error
** Description changed: System: Ubuntu 18.04 system-config-printer version: 1.5.11-1ubuntu printer: Canon iP7250 I expect to be able to see the printer in the panel just as 'lpstat -l -e' or 'driverless' can see them, without the need to especially add a new printer. And if I do need to add it (don't see why that should be the case, but still), I expect that choosing the printer's name under network would result in adding the printer. - What happened instead: Canon iP7250 isn't shown in the Printers panel, clicking on add and expanding the network options - it is shown, but when trying to add it (either driverless IPP, LPD via DNS-SD or IPP via DNS-SD) it gives an error about CUPS internal error. `$ lpstat -l -e` gives `Canon_iP7200_series network none ipp://Canon%20iP7200%20series._ipp._tcp.local/` So the system does see it, and `lp -d Canon_iP7200_series /etc/nsswitch.conf` does print (and for a minute the printer is shown in the Printers panel - but then disappears). I can add it by *not* clicking on the printer's name under Network, but rather, click on ipp printer and manually choose Canon -> iP7200 -> - CUPS+Gutenberg driver (and not the recommended driverless option - + CUPS+Gutenprint driver (and not the recommended driverless option - which, if I choose results in that same cryptic error I get when trying to add the printer by clicking on it, as described above). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1815307 Title: ipp printer isn't shown automatically - adding it errors with a CUPS internal error Status in system-config-printer package in Ubuntu: New Bug description: System: Ubuntu 18.04 system-config-printer version: 1.5.11-1ubuntu printer: Canon iP7250 I expect to be able to see the printer in the panel just as 'lpstat -l -e' or 'driverless' can see them, without the need to especially add a new printer. And if I do need to add it (don't see why that should be the case, but still), I expect that choosing the printer's name under network would result in adding the printer. What happened instead: Canon iP7250 isn't shown in the Printers panel, clicking on add and expanding the network options - it is shown, but when trying to add it (either driverless IPP, LPD via DNS-SD or IPP via DNS-SD) it gives an error about CUPS internal error. `$ lpstat -l -e` gives `Canon_iP7200_series network none ipp://Canon%20iP7200%20series._ipp._tcp.local/` So the system does see it, and `lp -d Canon_iP7200_series /etc/nsswitch.conf` does print (and for a minute the printer is shown in the Printers panel - but then disappears). I can add it by *not* clicking on the printer's name under Network, but rather, click on ipp printer and manually choose Canon -> iP7200 -> CUPS+Gutenprint driver (and not the recommended driverless option - which, if I choose results in that same cryptic error I get when trying to add the printer by clicking on it, as described above). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1815307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815307] [NEW] ipp printer isn't shown automatically - adding it errors with a CUPS internal error
Public bug reported: System: Ubuntu 18.04 system-config-printer version: 1.5.11-1ubuntu printer: Canon iP7250 I expect to be able to see the printer in the panel just as 'lpstat -l -e' or 'driverless' can see them, without the need to especially add a new printer. And if I do need to add it (don't see why that should be the case, but still), I expect that choosing the printer's name under network would result in adding the printer. What happened instead: Canon iP7250 isn't shown in the Printers panel, clicking on add and expanding the network options - it is shown, but when trying to add it (either driverless IPP, LPD via DNS-SD or IPP via DNS-SD) it gives an error about CUPS internal error. `$ lpstat -l -e` gives `Canon_iP7200_series network none ipp://Canon%20iP7200%20series._ipp._tcp.local/` So the system does see it, and `lp -d Canon_iP7200_series /etc/nsswitch.conf` does print (and for a minute the printer is shown in the Printers panel - but then disappears). I can add it by *not* clicking on the printer's name under Network, but rather, click on ipp printer and manually choose Canon -> iP7200 -> CUPS+Gutenberg driver (and not the recommended driverless option - which, if I choose results in that same cryptic error I get when trying to add the printer by clicking on it, as described above). ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1815307 Title: ipp printer isn't shown automatically - adding it errors with a CUPS internal error Status in system-config-printer package in Ubuntu: New Bug description: System: Ubuntu 18.04 system-config-printer version: 1.5.11-1ubuntu printer: Canon iP7250 I expect to be able to see the printer in the panel just as 'lpstat -l -e' or 'driverless' can see them, without the need to especially add a new printer. And if I do need to add it (don't see why that should be the case, but still), I expect that choosing the printer's name under network would result in adding the printer. What happened instead: Canon iP7250 isn't shown in the Printers panel, clicking on add and expanding the network options - it is shown, but when trying to add it (either driverless IPP, LPD via DNS-SD or IPP via DNS-SD) it gives an error about CUPS internal error. `$ lpstat -l -e` gives `Canon_iP7200_series network none ipp://Canon%20iP7200%20series._ipp._tcp.local/` So the system does see it, and `lp -d Canon_iP7200_series /etc/nsswitch.conf` does print (and for a minute the printer is shown in the Printers panel - but then disappears). I can add it by *not* clicking on the printer's name under Network, but rather, click on ipp printer and manually choose Canon -> iP7200 -> CUPS+Gutenberg driver (and not the recommended driverless option - which, if I choose results in that same cryptic error I get when trying to add the printer by clicking on it, as described above). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1815307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778011] Re: PRIME Power Saving mode draws too much power
Can we have an option to switch to the iGPU, but keep the nvidia card powered and its modules loaded so that it can be used for CUDA calculations? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: PRIME Power Saving mode draws too much power Status in nvidia-prime package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in nvidia-prime source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Bionic: In Progress Bug description: Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Solving the problem in systemd (LP: #1777099), and adding code in gpu- manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep, dramatically decreases power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765556] Re: nvidia-prime needs a reboot to switch between dGPU/hGPU
The prime-select replacement in https://github.com/matthieugras/Prime- Ubuntu-18.04 works without requiring a restart (simply kills and starts again the display manager). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765556 Title: nvidia-prime needs a reboot to switch between dGPU/hGPU Status in nvidia-prime package in Ubuntu: Confirmed Bug description: I previously used Ubuntu 16.04 and Nvidia 375 driver with a Nvidia Geforce 635M and Sandy Bridge i7. To switch between the 2 Optimus cards (Intel hybrid and Nvidia discrete), one had to go into nvidia- settings, switch, logoff, login back, and the change was applied. I now have a Nvidia Quadro M2000 and a Skylake Xeon which has some Sync/Mux feature (whatever does that mean) with the Nvidia 390 driver. First of all, installing nivida-prime doesn't install bbswitch-dkms. Then, once the GPU switch is made, it triggers update-initramfs, recompile the kernel modules, and one needs to reboot the system to get the GPU change. Even when we install bbswitch-dkms. So am I getting a wrong impression or is there something twisted here ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:20:01 2018 Dependencies: InstallationDate: Installed on 2018-04-08 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765556] Re: nvidia-prime needs a reboot to switch between dGPU/hGPU
Update regarding 17.10 - After switching from GDM to lightDM, logout and login are enough, no reboot required. With GDM, logout and sudo systemctl restart display-manager was also enough and didn't require a full reboot. This is for nvidia-prime 0.8.5, kernel 4.13.0-41-generic and 390.59-0ubuntu0~gpu17.10.1 - but for 0.8.8 on Bionic Beaver (also 390 drivers) a reboot was required even with lightDM instead of GDM, and restarting the display-manager wasn't enough as well.. So I'd say it's a regression in 0.8.8, wouldn't 0.8.5 work with the latest drivers and kernels? It could be a workaround for now to revert back to 0.8.5 for Bionic Beaver. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765556 Title: nvidia-prime needs a reboot to switch between dGPU/hGPU Status in nvidia-prime package in Ubuntu: Confirmed Bug description: I previously used Ubuntu 16.04 and Nvidia 375 driver with a Nvidia Geforce 635M and Sandy Bridge i7. To switch between the 2 Optimus cards (Intel hybrid and Nvidia discrete), one had to go into nvidia- settings, switch, logoff, login back, and the change was applied. I now have a Nvidia Quadro M2000 and a Skylake Xeon which has some Sync/Mux feature (whatever does that mean) with the Nvidia 390 driver. First of all, installing nivida-prime doesn't install bbswitch-dkms. Then, once the GPU switch is made, it triggers update-initramfs, recompile the kernel modules, and one needs to reboot the system to get the GPU change. Even when we install bbswitch-dkms. So am I getting a wrong impression or is there something twisted here ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:20:01 2018 Dependencies: InstallationDate: Installed on 2018-04-08 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767787] Re: prime-select doesn't switch to nvidia after reboot
Using prime indicator plus for switching, and lightDM instead of GDM behaves as it should. With GDM it require sudo systemctl restart display-manager - guess it's a GDM bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1767787 Title: prime-select doesn't switch to nvidia after reboot Status in nvidia-prime package in Ubuntu: New Bug description: After sudo prime-select nvidia, recreate new initramfs and reboot I still land on Gnome using Intel gfx card. I have color LED which provides me information about which card is used. When I check which mode is selected with sudo prime-select query I see nvidia but when I check which card is really used with glxheads I see Intel. For the true switch I need log off from Gnome, switch to virtual console and type two commands: sudo modprobe nvidia sudo systemctl restart display-manager.service After these two commands, I'm able to use Nvidia gfx card under Gnome. In my personal opinion, this solution with switching between cards through initramfs and reboot is a huge step back in the usability of Ubuntu. The previous solution with alternatives was much much better for end user. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.8 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Sun Apr 29 13:09:45 2018 Dependencies: InstallationDate: Installed on 2015-02-13 (1170 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-04-28 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1767787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765556] Re: nvidia-prime needs a reboot to switch between dGPU/hGPU
This also affects me on 17.10. would changing to 16.04 restore the expected behavior? I could wait 2 years for the next LTS, hopefully this issue would get solved by then. And until then I'd be able to switch without restarts. I wonder when, if ever, we'd get to not needing to logout\login to switch between the GPUs (like it currently is under Windows and MacOS). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765556 Title: nvidia-prime needs a reboot to switch between dGPU/hGPU Status in nvidia-prime package in Ubuntu: Confirmed Bug description: I previously used Ubuntu 16.04 and Nvidia 375 driver with a Nvidia Geforce 635M and Sandy Bridge i7. To switch between the 2 Optimus cards (Intel hybrid and Nvidia discrete), one had to go into nvidia- settings, switch, logoff, login back, and the change was applied. I now have a Nvidia Quadro M2000 and a Skylake Xeon which has some Sync/Mux feature (whatever does that mean) with the Nvidia 390 driver. First of all, installing nivida-prime doesn't install bbswitch-dkms. Then, once the GPU switch is made, it triggers update-initramfs, recompile the kernel modules, and one needs to reboot the system to get the GPU change. Even when we install bbswitch-dkms. So am I getting a wrong impression or is there something twisted here ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:20:01 2018 Dependencies: InstallationDate: Installed on 2018-04-08 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1703838] Re: Failure to automatically reconnect after drop - requiring manual reconnect, only successful after second try
I can induce a connection drop by changing the wireless channel on my router - this also produces a similar result (no auto reconnect) - it shows like it's trying for a minute or 2, and than shows the up/down arrows. Selecting the network manually connects immediately. Here's the NetworkManager log: https://pastebin.com/CB6d8NP4 Attached is the debug wpa_supplicant log starting from the disconnect ** Attachment added: "wpa_supplicant log (debug mode)" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1703838/+attachment/4914037/+files/wpa_sup%20failure%20to%20reconnect3%20debug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1703838 Title: Failure to automatically reconnect after drop - requiring manual reconnect, only successful after second try Status in network-manager package in Ubuntu: New Bug description: Using Ubuntu 17.04 (64 bit) Package version 1.4.4-1ubuntu3.1 This happened to me 3 times today: The connection drops and is not automatically restored, even though the network is visible in the nm-applet. Manually clicking on the network to connect, results in an animation of the nm-applet showing it's trying, but it gives up after a while and changes the icon to up\down arrows instead of the wifi sign. Clicking on it again, and selecting my network again, results in an almost instant reconnection, which implies that the computer should have known to do it automatically instead of requiring me to tell it to connect again (let alone twice). Here is the journal from a system startup: https://pastebin.com/hGrFEWiU And here is the journal from one such unsuccessful reconnect. I've added (*** comments ***) to mark where I've manually tried to reconnect (twice, second time successfully): https://pastebin.com/TAyt6McQ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1703838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1703838] Re: Failure to automatically reconnect after drop - requiring manual reconnect, only successful after second try
More system information: lspci -vn gives: 05:00.0 0280: 8086:24f3 (rev 3a) Subsystem: 8086:1010 Flags: bus master, fast devsel, latency 0, IRQ 142 Memory at df10 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-a7-a0-ff-ff-a3-07-c8 Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel driver in use: iwlwifi Kernel modules: iwlwifi Also attached wpa_supplicant log (although I set the log level to debug too late for this time). Notice that wpa_supplicant stops doing group rekeying about 15 minutes before the network disconnected (around 11:25), and all the messages from 13:57 and on are from the 2 reconnection attempts. It seems there was no automatic attempt at reconnection that reached wpa_supplicant. ** Attachment added: "wpa_supplicant log" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1703838/+attachment/4913485/+files/wpa_sup%20failure%20to%20reconnect2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1703838 Title: Failure to automatically reconnect after drop - requiring manual reconnect, only successful after second try Status in network-manager package in Ubuntu: New Bug description: Using Ubuntu 17.04 (64 bit) Package version 1.4.4-1ubuntu3.1 This happened to me 3 times today: The connection drops and is not automatically restored, even though the network is visible in the nm-applet. Manually clicking on the network to connect, results in an animation of the nm-applet showing it's trying, but it gives up after a while and changes the icon to up\down arrows instead of the wifi sign. Clicking on it again, and selecting my network again, results in an almost instant reconnection, which implies that the computer should have known to do it automatically instead of requiring me to tell it to connect again (let alone twice). Here is the journal from a system startup: https://pastebin.com/hGrFEWiU And here is the journal from one such unsuccessful reconnect. I've added (*** comments ***) to mark where I've manually tried to reconnect (twice, second time successfully): https://pastebin.com/TAyt6McQ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1703838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1703838] [NEW] Failure to automatically reconnect after drop - requiring manual reconnect, only successful after second try
Public bug reported: Using Ubuntu 17.04 (64 bit) Package version 1.4.4-1ubuntu3.1 This happened to me 3 times today: The connection drops and is not automatically restored, even though the network is visible in the nm-applet. Manually clicking on the network to connect, results in an animation of the nm-applet showing it's trying, but it gives up after a while and changes the icon to up\down arrows instead of the wifi sign. Clicking on it again, and selecting my network again, results in an almost instant reconnection, which implies that the computer should have known to do it automatically instead of requiring me to tell it to connect again (let alone twice). Here is the journal from a system startup: https://pastebin.com/hGrFEWiU And here is the journal from one such unsuccessful reconnect. I've added (*** comments ***) to mark where I've manually tried to reconnect (twice, second time successfully): https://pastebin.com/TAyt6McQ ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1703838 Title: Failure to automatically reconnect after drop - requiring manual reconnect, only successful after second try Status in network-manager package in Ubuntu: New Bug description: Using Ubuntu 17.04 (64 bit) Package version 1.4.4-1ubuntu3.1 This happened to me 3 times today: The connection drops and is not automatically restored, even though the network is visible in the nm-applet. Manually clicking on the network to connect, results in an animation of the nm-applet showing it's trying, but it gives up after a while and changes the icon to up\down arrows instead of the wifi sign. Clicking on it again, and selecting my network again, results in an almost instant reconnection, which implies that the computer should have known to do it automatically instead of requiring me to tell it to connect again (let alone twice). Here is the journal from a system startup: https://pastebin.com/hGrFEWiU And here is the journal from one such unsuccessful reconnect. I've added (*** comments ***) to mark where I've manually tried to reconnect (twice, second time successfully): https://pastebin.com/TAyt6McQ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1703838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
