[Touch-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 Ubuntu Touch seeded 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/~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 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 Ubuntu Touch seeded 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/~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 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 Ubuntu Touch seeded 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/~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 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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
