[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816191 Title: Printers partially recognizes network printer, but isn't able to even print a test page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1816191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816191 Title: Printers partially recognizes network printer, but isn't able to even print a test page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1816191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815307 Title: ipp printer isn't shown automatically - adding it errors with a CUPS internal error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1815307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816191 Title: Printers partially recognizes network printer, but isn't able to even print a test page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1816191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816191 Title: Printers partially recognizes network printer, but isn't able to even print a test page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1816191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815307 Title: ipp printer isn't shown automatically - adding it errors with a CUPS internal error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1815307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815307 Title: ipp printer isn't shown automatically - adding it errors with a CUPS internal error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1815307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815307 Title: ipp printer isn't shown automatically - adding it errors with a CUPS internal error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1815307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815307 Title: ipp printer isn't shown automatically - adding it errors with a CUPS internal error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1815307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765556 Title: nvidia-prime needs a reboot to switch between dGPU/hGPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765556 Title: nvidia-prime needs a reboot to switch between dGPU/hGPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767787 Title: prime-select doesn't switch to nvidia after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1767787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 752542] Re: ACPI DSDT info
bbswitch failed to load, dmesg says:
[127506.827564] bbswitch: version 0.8
[127506.827567] bbswitch: Found integrated VGA device :00:02.0:
\_SB_.PCI0.GFX0
[127506.827570] bbswitch: Found discrete VGA device :01:00.0:
\_SB_.PCI0.PEG0.PEGP
[127506.827577] bbswitch: failed to evaluate \_SB_.PCI0.PEG0.PEGP._DSM
{0xF8,0xD8,0x86,0xA4,0xDA,0x0B,0x1B,0x47,0xA7,0x2B,0x60,0x42,0xA6,0xB5,0xBE,0xE0}
0x100 0x0 {0x00,0x00,0x00,0x00}: AE_NOT_FOUND
[127506.827581] bbswitch: failed to evaluate \_SB_.PCI0.PEG0.PEGP._DSM
{0xA0,0xA0,0x95,0x9D,0x60,0x00,0x48,0x4D,0xB3,0x4D,0x7E,0x5F,0xEA,0x12,0x9F,0xD4}
0x102 0x0 {0x00,0x00,0x00,0x00}: AE_NOT_FOUND
[127506.827603] bbswitch: No suitable _DSM call found.
** Attachment added: "System_manufacturer-System_Product_Name.tar.gz"
https://bugs.launchpad.net/lpbugreporter/+bug/752542/+attachment/5140014/+files/System_manufacturer-System_Product_Name.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/752542
Title:
ACPI DSDT info
To manage notifications about this bug go to:
https://bugs.launchpad.net/bumblebee/+bug/752542/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765556 Title: nvidia-prime needs a reboot to switch between dGPU/hGPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737133] Re: package linux-image-4.13.0-19-generic 4.13.0-19.22 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
Yes, getting to TTY solved it for me as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737133 Title: package linux-image-4.13.0-19-generic 4.13.0-19.22 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737133] Re: package linux-image-4.13.0-19-generic 4.13.0-19.22 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
I've encountered the same problem, but your fix does not work for me. When trying to autoinstall the ubuntu-drivers I get: E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. But the dpkg command just hangs on: Setting up linux-image-4.13.0-19-generic (4.13.0-19.22) ... Running depmod. update-initramfs: deferring update (hook will be called later) The link /initrd.img is a dangling linkto /boot/initrd.img-4.13.0-19-generic vmlinuz(/boot/vmlinuz-4.13.0-19-generic ) points to /boot/vmlinuz-4.13.0-19-generic (/boot/vmlinuz-4.13.0-19-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.13.0-19-generic.postinst line 491. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.13.0-19-generic /boot/vmlinuz-4.13.0-19-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-19-generic /boot/vmlinuz-4.13.0-19-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737133 Title: package linux-image-4.13.0-19-generic 4.13.0-19.22 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703838 Title: Failure to automatically reconnect after drop - requiring manual reconnect, only successful after second try To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1703838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703838 Title: Failure to automatically reconnect after drop - requiring manual reconnect, only successful after second try To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1703838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703838 Title: Failure to automatically reconnect after drop - requiring manual reconnect, only successful after second try To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1703838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1159707] Re: Cinnamon panel / task bar becomes unresponsive to mouse
Using Linux-mint 17.3 32bit live-usb, shortly after sleep the menu, desktop and dialog boxes were not responsive to mouse clicks (neither left nor right). It happened after clicking on "show password" checkbox in the wifi password dialog. Other applications were working fine, and menu as well as dialog boxes were working through keyboard. Log-out and Log-in again fixed it for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1159707 Title: Cinnamon panel / task bar becomes unresponsive to mouse To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1159707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 414464] Re: controls fail to work in flash
Yeah, tried watching a youtube video with compiz disabled (like the above poster suggested), and the controls work for me. doesn't work when effects are on... -- controls fail to work in flash https://bugs.launchpad.net/bugs/414464 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 135619] ipython crashes on help modules (APT API not stable)
Public bug reported:
Binary package hint: ipython
after typing help
typing modules gets me the following output:
Please wait a moment while I gather a list of all available modules...
/usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not
stable yet
warnings.warn(apt API not stable yet, FutureWarning)
---
type 'exceptions.IOError' Traceback (most recent call last)
/home/fuk/ipython console in module()
/home/fuk/site.py in __call__(self, *args, **kwds)
349 def __call__(self, *args, **kwds):
350 import pydoc
-- 351 return pydoc.help(*args, **kwds)
352
353 def sethelper():
/home/fuk/pydoc.py in __call__(self, request)
1647 else:
1648 self.intro()
- 1649 self.interact()
1650 self.output.write('''
1651 You are now leaving help and returning to the Python interpreter.
/home/fuk/pydoc.py in interact(self)
1665 request = strip(replace(request, '', '', ', ''))
1666 if lower(request) in ('q', 'quit'): break
- 1667 self.help(request)
1668
1669 def getline(self, prompt):
/home/fuk/pydoc.py in help(self, request)
1681 elif request == 'keywords': self.listkeywords()
1682 elif request == 'topics': self.listtopics()
- 1683 elif request == 'modules': self.listmodules()
1684 elif request[:8] == 'modules ':
1685 self.listmodules(split(request)[1])
/home/fuk/pydoc.py in listmodules(self, key)
1802 if find(modname, '.') 0:
1803 modules[modname] = 1
- 1804 ModuleScanner().run(callback)
1805 self.list(modules.keys())
1806 self.output.write('''
/home/fuk/pydoc.py in run(self, callback, key, completer)
1853 callback(None, modname, desc)
1854
- 1855 for importer, modname, ispkg in pkgutil.walk_packages():
1856 if self.quit:
1857 break
/home/fuk/pkgutil.py in walk_packages(path, prefix, onerror)
123 path = [p for p in path if not seen(p)]
124
-- 125 for item in walk_packages(path, name+'.', onerror):
126 yield item
127
/home/fuk/pkgutil.py in walk_packages(path, prefix, onerror)
123 path = [p for p in path if not seen(p)]
124
-- 125 for item in walk_packages(path, name+'.', onerror):
126 yield item
127
/home/fuk/pkgutil.py in walk_packages(path, prefix, onerror)
108 if ispkg:
109 try:
-- 110 __import__(name)
111 except ImportError:
112 if onerror is not None:
/usr/lib/python2.5/site-packages/scipy/sandbox/gplt/__init__.py in module()
3 #
4
5 from info_gplt import __doc__
6
7 from interface import *
/usr/lib/python2.5/site-packages/scipy/sandbox/gplt/interface.py in module()
10 _active = _figure[-1]
11
--- 12 _intialize()
13
14 def _validate_active():
/usr/lib/python2.5/site-packages/scipy/sandbox/gplt/interface.py in _intialize()
7 def _intialize():
8 global _figure; global _active
9 _figure = [pyPlot.Plot()]
10 _active = _figure[-1]
11
/usr/lib/python2.5/site-packages/scipy/sandbox/gplt/pyPlot.py in __init__(self,
*cmd)
101 else:
102 self.g = plot_popen(helper + self.gnuplot + ' -persist 1
/dev/null 21', 'w')
-- 103 self._defaults()
104 time.sleep(.2) # put a pause here because in windows, wgnuplot
doesn't seem to get the first plot message
105 if (len(cmd) 0 and type(cmd[0]) != StringType):
/usr/lib/python2.5/site-packages/scipy/sandbox/gplt/pyPlot.py in _defaults(self)
695 cmd = cmd +'set grid;'
696 cmd = cmd +'show grid\n'
-- 697 self._send(cmd)
698 def _init_plot(self):
699 self.m_rmin = BIG
/usr/lib/python2.5/site-packages/scipy/sandbox/gplt/pyPlot.py in _send(self,
cmd)
818 if(len(cmd) 200):
819 self.g.write(cmd + '\n')
-- 820 self.g.flush()
821 else:
822 filename = tempfile.mktemp()
type 'exceptions.IOError': [Errno 32] Broken pipe
** Affects: ipython (Ubuntu)
Importance: Undecided
Status: New
--
ipython crashes on help modules (APT API not stable)
https://bugs.launchpad.net/bugs/135619
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 116290] Re: No choice of language for spell checking
I can confirm there's no choice for what dictionary the speller use. Tomboy uses GtkSpell for it's spell checking, and GtkSpell uses GNU Aspell. I have several languages installed for the Aspell dictionary, but there is no way to tell GtkSpell or Tomboy which dictionary i wish to use. It's not a bug though,, just lack of a *very* basic feature. There should be a way to use multiple languages in the spell checking mechanism. -- No choice of language for spell checking https://bugs.launchpad.net/bugs/116290 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 116290] Re: No choice of language for spell checking
oops (no way to edit posts?! i posted above the wrong spelling bug =P this is the correct page: http://bugzilla.gnome.org/show_bug.cgi?id=336484 please ignore my previous post. -- No choice of language for spell checking https://bugs.launchpad.net/bugs/116290 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 116290] Re: No choice of language for spell checking
I have also posted in here: http://bugzilla.gnome.org/show_bug.cgi?id=363357 (for the Tomboy team) -- No choice of language for spell checking https://bugs.launchpad.net/bugs/116290 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
