[Desktop-packages] [Bug 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume
@Daniel Lombraña González (teleyinex) #66 however, if I suspend the machine again and resume it, after few seconds it starts again to suspend without me doing anything, leaving the machine in an unusable state. Just try resuming again and again. For me this eventually works, but it sometimes takes 4-5 retries. -- 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/1184262 Title: [logind] stuck in PrepareForSleep, causing network and other services to not resume Status in “network-manager” package in Ubuntu: Confirmed Status in “systemd” package in Ubuntu: Incomplete Bug description: After a suspend/resume, network-manager claimed that wireless was not available and would not let me reconnect to the wireless here. 'iwlist wlan1 scan' would also not work; so thinking that it was a driver problem, I rebooted the system. When it came back up, nm- applet in lightdm claimed that networking was disabled, and the option to enable it was greyed out. It could also not be enabled by nmcli. I ended up stopping network-manager, bringing up the interface via /etc/network/interfaces, and logging in... at which point, restarting network-manager *did* let me enable networking from my logged-in session. So there are several problems here: - after a reboot, network-manager claimed networking was disabled. - nm-applet is not letting me enable networking from the lightdm session. - the networking was failing after a suspend/resume cycle, and could not be enabled even from inside the user session. The last issue probably *was* a kernel driver problem; but the first two issues are network-manager problems of some kind. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu8 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 21:38:31 2013 InstallationDate: Installed on 2010-09-24 (974 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) IpRoute: default via 192.168.1.1 dev wlan1 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.106 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago) WifiSyslog: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: ** (process:11977): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN not running unknownunknown unknown unknown unknownunknown unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+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
Re: [Desktop-packages] [Bug 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume
I'm getting this with GNOME classic. On Mon, Oct 28, 2013 at 4:19 PM, Evan Huus 1184...@bugs.launchpad.net wrote: Martin, I am seeing this regularly under Unity. Smells like a race condition to me. -- You received this bug notification because you are subscribed to a duplicate bug report (1234469). https://bugs.launchpad.net/bugs/1184262 Title: [logind] stuck in PrepareForSleep, causing network and other services to not resume Status in “network-manager” package in Ubuntu: Confirmed Status in “systemd” package in Ubuntu: Incomplete Bug description: After a suspend/resume, network-manager claimed that wireless was not available and would not let me reconnect to the wireless here. 'iwlist wlan1 scan' would also not work; so thinking that it was a driver problem, I rebooted the system. When it came back up, nm- applet in lightdm claimed that networking was disabled, and the option to enable it was greyed out. It could also not be enabled by nmcli. I ended up stopping network-manager, bringing up the interface via /etc/network/interfaces, and logging in... at which point, restarting network-manager *did* let me enable networking from my logged-in session. So there are several problems here: - after a reboot, network-manager claimed networking was disabled. - nm-applet is not letting me enable networking from the lightdm session. - the networking was failing after a suspend/resume cycle, and could not be enabled even from inside the user session. The last issue probably *was* a kernel driver problem; but the first two issues are network-manager problems of some kind. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu8 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 21:38:31 2013 InstallationDate: Installed on 2010-09-24 (974 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) IpRoute: default via 192.168.1.1 dev wlan1 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.106 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago) WifiSyslog: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: ** (process:11977): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN not running unknownunknown unknown unknown unknownunknown unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+subscriptions -- 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/1184262 Title: [logind] stuck in PrepareForSleep, causing network and other services to not resume Status in “network-manager” package in Ubuntu: Confirmed Status in “systemd” package in Ubuntu: Incomplete Bug description: After a suspend/resume, network-manager claimed that wireless was not available and would not let me reconnect to the wireless here. 'iwlist wlan1 scan' would also not work; so thinking that it was a driver problem, I rebooted the system. When it came back up, nm- applet in lightdm claimed that networking was disabled, and the option to enable it was greyed out. It could also not be enabled by nmcli. I ended up stopping network-manager, bringing up the interface via /etc/network/interfaces, and logging in... at which point, restarting network-manager *did* let me enable networking from my logged-in session. So there are several problems here: - after a reboot, network-manager claimed networking was disabled. - nm-applet is not letting me enable networking from the lightdm session. - the networking was failing after a suspend/resume cycle, and could not be enabled even from inside the user session. The last issue probably *was* a kernel driver problem; but the
[Desktop-packages] [Bug 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume
@Pablo180 (paultait22) #30: I'm already running 3.11.0-12-generic, so changing to that can't be the fix. @Julien Olivier (julo) #33: I also have this probably related problem, and so far I found no workaround for that, other than trying to resume again and again until it eventually works. I've already mentioned this in one of the duplicates (1234469), but I'll repeat the log I get from systemd-logind for a case in which the first 3 resumes failed, but the fourth one succeeded. Lid closed. Suspending... Failed to execute operation: Message did not receive a reply (timeout by message bus) Suspending... Failed to execute operation: Message did not receive a reply (timeout by message bus) Suspending... Failed to execute operation: Message did not receive a reply (timeout by message bus) Suspending... Lid opened. Operation finished. Other problems I encountered that seem also related: sometimes the computer fails to suspend and sometimes even fails to shutdown. Everything worked fine before this crappy Ubuntu upgrade. I'm on a Dell Latitude 6400. -- 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/1184262 Title: [logind] stuck in PrepareForSleep, causing network and other services to not resume Status in “network-manager” package in Ubuntu: Confirmed Status in “systemd” package in Ubuntu: Incomplete Bug description: After a suspend/resume, network-manager claimed that wireless was not available and would not let me reconnect to the wireless here. 'iwlist wlan1 scan' would also not work; so thinking that it was a driver problem, I rebooted the system. When it came back up, nm- applet in lightdm claimed that networking was disabled, and the option to enable it was greyed out. It could also not be enabled by nmcli. I ended up stopping network-manager, bringing up the interface via /etc/network/interfaces, and logging in... at which point, restarting network-manager *did* let me enable networking from my logged-in session. So there are several problems here: - after a reboot, network-manager claimed networking was disabled. - nm-applet is not letting me enable networking from the lightdm session. - the networking was failing after a suspend/resume cycle, and could not be enabled even from inside the user session. The last issue probably *was* a kernel driver problem; but the first two issues are network-manager problems of some kind. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu8 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 21:38:31 2013 InstallationDate: Installed on 2010-09-24 (974 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) IpRoute: default via 192.168.1.1 dev wlan1 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.106 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago) WifiSyslog: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: ** (process:11977): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN not running unknownunknown unknown unknown unknownunknown unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+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 107374] Re: adding new entries to alacarte has no effect
I'm having this problem on Ubuntu 13.10 and alacarte 3.10.0-1, both as normal user and as root. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/107374 Title: adding new entries to alacarte has no effect Status in “alacarte” package in Ubuntu: Confirmed Bug description: Binary package hint: alacarte I am unable to add items to a menu using the alacarte menu editor in feisty. $ dpkg -l | grep -i carte ii alacarte 0.11.3-0ubuntu2 easy menu editing $ uname -a Linux khermans-laptop 2.6.20-14-generic #2 SMP Mon Apr 2 16:32:46 UTC 2007 x86_64 GNU/Linux Go to applications - system tools - new item. Enter a name and a path to the app. No item will be added. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/107374/+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 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume
General question: since Ubuntu seems to not support reverting dist- upgrades, is there any collection of packages I can restore to their pre 13.10 working state to avoid this horrible problem? (If not I'll seriously consider switching distribution; this is just too much) -- 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/1184262 Title: [logind] stuck in PrepareForSleep, causing network and other services to not resume Status in “network-manager” package in Ubuntu: Confirmed Status in “systemd” package in Ubuntu: Incomplete Bug description: After a suspend/resume, network-manager claimed that wireless was not available and would not let me reconnect to the wireless here. 'iwlist wlan1 scan' would also not work; so thinking that it was a driver problem, I rebooted the system. When it came back up, nm- applet in lightdm claimed that networking was disabled, and the option to enable it was greyed out. It could also not be enabled by nmcli. I ended up stopping network-manager, bringing up the interface via /etc/network/interfaces, and logging in... at which point, restarting network-manager *did* let me enable networking from my logged-in session. So there are several problems here: - after a reboot, network-manager claimed networking was disabled. - nm-applet is not letting me enable networking from the lightdm session. - the networking was failing after a suspend/resume cycle, and could not be enabled even from inside the user session. The last issue probably *was* a kernel driver problem; but the first two issues are network-manager problems of some kind. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu8 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 21:38:31 2013 InstallationDate: Installed on 2010-09-24 (974 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) IpRoute: default via 192.168.1.1 dev wlan1 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.106 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago) WifiSyslog: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: ** (process:11977): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN not running unknownunknown unknown unknown unknownunknown unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+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 1234469] Re: Network does not come up after resuming from suspend.
*** This bug is a duplicate of bug 1184262 *** https://bugs.launchpad.net/bugs/1184262 I've tried suggested by pitti. After the first suspend and resume I get this: Lid closed. Suspending... Failed to send delayed message: Message did not receive a reply (timeout by message bus) Lid opened. Networking was disabled so I brought it back up with nmcli nm sleep false. Then I suspended again. After the second suspend trying to resume just led to another suspend I didn't ask for. Had to force another resume (power button) before the thing actually resumed: Lid closed. Suspending... Failed to execute operation: Message did not receive a reply (timeout by message bus) Suspending... Operation finished. Lid opened. Earlier today it happened to me that I couldn't resume at all because of this problem happening many times in a row. I would get to the login prompt but the machine would go back to sleep so fast that I wouldn't even have time to enter my password. I had to power off and restart the machine to take it out of that state. I'm on a Dell Latitude E6400. BTW. Should I stop commenting here and switch to #1184262 instead? -- 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/1234469 Title: Network does not come up after resuming from suspend. Status in “network-manager” package in Ubuntu: Confirmed Status in “systemd” package in Ubuntu: Confirmed Bug description: When my computer wakes up from being suspended, the wireless network connection doesn't come back up. I'm able to fix the problem by running nmcli nm sleep false, which causes the wireless card to reconnect. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu21 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Wed Oct 2 20:21:33 2013 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-08-09 (54 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IpRoute: default via 192.168.125.1 dev wlan0 proto static 192.168.125.0/24 dev wlan0 proto kernel scope link src 192.168.125.8 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: Upgraded to saucy on 2013-08-09 (54 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 199a6c07f-9a94-4c8e-82dd-0381befd6f90 802-3-ethernet1380753272 Wed 02 Oct 2013 05:34:32 PM CDTyes no /org/freedesktop/NetworkManager/Settings/1 9739 172c6f5c-b69c-40dd-ac1b-a279c84a17f8 802-11-wireless 1380763079 Wed 02 Oct 2013 08:17:59 PM CDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1234469/+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 596095] Re: /usr/lib/cups/filter/pstopdf failed for any PDF
I know this is an old one, but I'm getting the same error message (/usr/lib/cups/filter/pstopdf failed) with Ubuntu 13.10, CUPS 1.7rc1, and various TOSHIBA e-Studio printers with the recommended Foomatic/pxlmono and Foomatic/Postscript drivers. Was this bug ever fixed and this is a regression? -- 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/596095 Title: /usr/lib/cups/filter/pstopdf failed for any PDF Status in “cups” package in Ubuntu: Confirmed Bug description: Binary package hint: cups Seems like some of the last updates have broken my PDF printing. Printer is Samsung ML-2850D Foomatic/Postscript (recommended). A couple of weeks ago it certainly worked well, but now I get /usr/lib/cups/filter/pstopdf failed for any PDF file (downloaded or created by me with OOo or LaTeX). Printing directly from OOo works well. Please help, I can do any testing you suggest. I [19/Jun/2010:01:09:37 +0400] Listening to ::1:631 (IPv6) I [19/Jun/2010:01:09:37 +0400] Listening to 127.0.0.1:631 (IPv4) I [19/Jun/2010:01:09:37 +0400] Listening to /var/run/cups/cups.sock (Domain) I [19/Jun/2010:01:09:37 +0400] Remote access is disabled. D [19/Jun/2010:01:09:37 +0400] Added auto ServerAlias lightoze-tek I [19/Jun/2010:01:09:37 +0400] Loaded configuration file /etc/cups/cupsd.conf I [19/Jun/2010:01:09:37 +0400] Using default TempDir of /var/spool/cups/tmp... I [19/Jun/2010:01:09:37 +0400] Configured for up to 100 clients. I [19/Jun/2010:01:36:33 +0400] Listening to ::1:631 (IPv6) I [19/Jun/2010:01:36:33 +0400] Listening to 127.0.0.1:631 (IPv4) I [19/Jun/2010:01:36:33 +0400] Listening to /var/run/cups/cups.sock (Domain) I [19/Jun/2010:01:36:33 +0400] Remote access is disabled. D [19/Jun/2010:01:36:33 +0400] Added auto ServerAlias lightoze-tek I [19/Jun/2010:01:36:33 +0400] Loaded configuration file /etc/cups/cupsd.conf I [19/Jun/2010:01:36:33 +0400] Using default TempDir of /var/spool/cups/tmp... I [19/Jun/2010:01:36:33 +0400] Configured for up to 100 clients. I [19/Jun/2010:01:36:33 +0400] Allowing up to 100 client connections per host. I [19/Jun/2010:01:36:33 +0400] Using policy default as the default! I [19/Jun/2010:01:36:33 +0400] Full reload is required. I [19/Jun/2010:01:36:33 +0400] Loaded MIME database from /usr/share/cups/mime and /etc/cups: 37 types, 76 filters... D [19/Jun/2010:01:36:33 +0400] Loading printer LaserJet_2300... D [19/Jun/2010:01:36:33 +0400] load_ppd: Loading /var/cache/cups/LaserJet_2300.ipp... D [19/Jun/2010:01:36:33 +0400] cupsdRegisterPrinter(p=0x7f53a74fe1e0(LaserJet_2300)) D [19/Jun/2010:01:36:33 +0400] Loading printer ML-2850-Series... D [19/Jun/2010:01:36:33 +0400] load_ppd: Loading /var/cache/cups/ML-2850-Series.ipp... D [19/Jun/2010:01:36:33 +0400] cupsdRegisterPrinter(p=0x7f53a74f1fe0(ML-2850-Series)) D [19/Jun/2010:01:36:33 +0400] cupsdLoadRemoteCache: Not loading remote cache. I [19/Jun/2010:01:36:33 +0400] Loading job cache file /var/cache/cups/job.cache... D [19/Jun/2010:01:36:33 +0400] [Job 1] Loading from cache... .. D [19/Jun/2010:01:36:33 +0400] cupsdAddSubscription(mask=0, dest=(nil)(), job=(nil)(0), uri=(null)) I [19/Jun/2010:01:36:33 +0400] Full reload complete. I [19/Jun/2010:01:36:33 +0400] Cleaning out old temporary files in /var/spool/cups/tmp... D [19/Jun/2010:01:36:33 +0400] Removed temporary file /var/spool/cups/tmp/foomatic-hZhpP2... I [19/Jun/2010:01:36:33 +0400] Listening to ::1:631 on fd 6... I [19/Jun/2010:01:36:33 +0400] Listening to 127.0.0.1:631 on fd 7... I [19/Jun/2010:01:36:33 +0400] Listening to /var/run/cups/cups.sock on fd 8... I [19/Jun/2010:01:36:33 +0400] Resuming new connection processing... D [19/Jun/2010:01:36:33 +0400] Discarding unused server-started event... D [19/Jun/2010:01:36:34 +0400] Report: clients=0 D [19/Jun/2010:01:36:34 +0400] Report: jobs=117 D [19/Jun/2010:01:36:34 +0400] Report: jobs-active=0 D [19/Jun/2010:01:36:34 +0400] Report: printers=2 D [19/Jun/2010:01:36:34 +0400] Report: printers-implicit=0 D [19/Jun/2010:01:36:34 +0400] Report: stringpool-string-count=623 D [19/Jun/2010:01:36:34 +0400] Report: stringpool-alloc-bytes=6712 D [19/Jun/2010:01:36:34 +0400] Report: stringpool-total-bytes=12608 D [19/Jun/2010:01:37:01 +0400] cupsdAcceptClient: 11 from localhost (Domain) D [19/Jun/2010:01:37:01 +0400] cupsdReadClient: 11 POST / HTTP/1.1 D [19/Jun/2010:01:37:01 +0400] cupsdSetBusyState: Active clients D [19/Jun/2010:01:37:01 +0400] cupsdAuthorize: No authentication data provided. D [19/Jun/2010:01:37:01 +0400] cupsdReadClient: 11 1.1 CUPS-Get-Printers 1 D [19/Jun/2010:01:37:01 +0400] CUPS-Get-Printers D [19/Jun/2010:01:37:01 +0400] Returning IPP successful-ok for CUPS-Get-Printers (no URI) from localhost D [19/Jun/2010:01:37:01 +0400] cupsdSetBusyState: Not busy D
[Desktop-packages] [Bug 1116513] Re: /usr/lib/cups/filter/pdftops failed
What happened with this bug? I'm getting the same error message (/usr/lib/cups/filter/pstopdf failed) with Ubuntu 13.10, CUPS 1.7rc1, poppler 24.1 and various TOSHIBA e-Studio printers with the recommended Foomatic/pxlmono and Foomatic/Postscript drivers. I'm on a Dell Latitude E6400. Was this bug ever fixed and is my problem a regression? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1116513 Title: /usr/lib/cups/filter/pdftops failed Status in “poppler” package in Ubuntu: Triaged Bug description: ubuntu-bug /var/crash/_usr_bin_pdftops.7.crash won't load the crash report. Here is the copy of the beginning of the crash file. It appears that it caused by SIGFPE Floating Point exception. and the root cause is an uninitialized variable leading to a division by zero in poppler-tools. ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Tue Feb 5 11:39:24 2013 DistroRelease: Ubuntu 12.04 ExecutablePath: /usr/bin/pdftops ExecutableTimestamp: 1343381837 ProcCmdline: pdftops -level2 -origpagesizes -r 300 /tmp/00f4c511a5f16 - ProcCwd: / ProcEnviron: PATH=(custom, no user) LANG=en_CA.UTF-8 ProcMaps: ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cups 1.5.3-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35 Uname: Linux 3.2.0-37-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 CurrentDmesg: [ 44.042521] agpgart-intel :00:00.0: putting AGP V3 device into 8x mode [ 44.042564] nvidia :01:00.0: putting AGP V3 device into 8x mode [ 45.599391] init: plymouth-stop pre-start process (1257) terminated with status 1 [ 52.912013] eth0: no IPv6 routers present Date: Tue Feb 5 13:07:10 2013 InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1) Lpstat: device for hp_color_LaserJet_5550: hp:/net/hp_color_LaserJet_5550?zc=Electrical MachineType: Dell Computer Corporation Dimension 4600 MarkForUpload: True Papersize: letter PpdFiles: hp_color_LaserJet_5550: HP Color LaserJet 5550 v3010.107 Postscript (recommended) ProcEnviron: PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-37-generic root=UUID=adff9268-f105-4bd3-aeb2-11be7b02eb8e ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to precise on 2013-01-22 (13 days ago) dmi.bios.date: 07/21/2003 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A03 dmi.board.name: 02Y832 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA03:bd07/21/2003:svnDellComputerCorporation:pnDimension4600:pvr:rvnDellComputerCorp.:rn02Y832:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: Dimension 4600 dmi.sys.vendor: Dell Computer Corporation mtime.conffile..etc.cups.cupsd.conf: 2013-01-31T16:58:59.450493 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1116513/+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 1116513] Re: /usr/lib/cups/filter/pdftops failed
Correction: my problem is with /usr/lib/cups/filter/pdftops (typo in #6) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1116513 Title: /usr/lib/cups/filter/pdftops failed Status in “poppler” package in Ubuntu: Triaged Bug description: ubuntu-bug /var/crash/_usr_bin_pdftops.7.crash won't load the crash report. Here is the copy of the beginning of the crash file. It appears that it caused by SIGFPE Floating Point exception. and the root cause is an uninitialized variable leading to a division by zero in poppler-tools. ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Tue Feb 5 11:39:24 2013 DistroRelease: Ubuntu 12.04 ExecutablePath: /usr/bin/pdftops ExecutableTimestamp: 1343381837 ProcCmdline: pdftops -level2 -origpagesizes -r 300 /tmp/00f4c511a5f16 - ProcCwd: / ProcEnviron: PATH=(custom, no user) LANG=en_CA.UTF-8 ProcMaps: ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cups 1.5.3-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35 Uname: Linux 3.2.0-37-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 CurrentDmesg: [ 44.042521] agpgart-intel :00:00.0: putting AGP V3 device into 8x mode [ 44.042564] nvidia :01:00.0: putting AGP V3 device into 8x mode [ 45.599391] init: plymouth-stop pre-start process (1257) terminated with status 1 [ 52.912013] eth0: no IPv6 routers present Date: Tue Feb 5 13:07:10 2013 InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1) Lpstat: device for hp_color_LaserJet_5550: hp:/net/hp_color_LaserJet_5550?zc=Electrical MachineType: Dell Computer Corporation Dimension 4600 MarkForUpload: True Papersize: letter PpdFiles: hp_color_LaserJet_5550: HP Color LaserJet 5550 v3010.107 Postscript (recommended) ProcEnviron: PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-37-generic root=UUID=adff9268-f105-4bd3-aeb2-11be7b02eb8e ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to precise on 2013-01-22 (13 days ago) dmi.bios.date: 07/21/2003 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A03 dmi.board.name: 02Y832 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA03:bd07/21/2003:svnDellComputerCorporation:pnDimension4600:pvr:rvnDellComputerCorp.:rn02Y832:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: Dimension 4600 dmi.sys.vendor: Dell Computer Corporation mtime.conffile..etc.cups.cupsd.conf: 2013-01-31T16:58:59.450493 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1116513/+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 1116513] Re: /usr/lib/cups/filter/pdftops failed
Eventually I manged to make both my Toshiba printers work with a combination of the workarounds described here https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/978120 and changing to the autodetected drivers although they don't really match the precise model of the printer and other drivers are recommended for one of the priters. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1116513 Title: /usr/lib/cups/filter/pdftops failed Status in “poppler” package in Ubuntu: Triaged Bug description: ubuntu-bug /var/crash/_usr_bin_pdftops.7.crash won't load the crash report. Here is the copy of the beginning of the crash file. It appears that it caused by SIGFPE Floating Point exception. and the root cause is an uninitialized variable leading to a division by zero in poppler-tools. ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Tue Feb 5 11:39:24 2013 DistroRelease: Ubuntu 12.04 ExecutablePath: /usr/bin/pdftops ExecutableTimestamp: 1343381837 ProcCmdline: pdftops -level2 -origpagesizes -r 300 /tmp/00f4c511a5f16 - ProcCwd: / ProcEnviron: PATH=(custom, no user) LANG=en_CA.UTF-8 ProcMaps: ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cups 1.5.3-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35 Uname: Linux 3.2.0-37-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 CurrentDmesg: [ 44.042521] agpgart-intel :00:00.0: putting AGP V3 device into 8x mode [ 44.042564] nvidia :01:00.0: putting AGP V3 device into 8x mode [ 45.599391] init: plymouth-stop pre-start process (1257) terminated with status 1 [ 52.912013] eth0: no IPv6 routers present Date: Tue Feb 5 13:07:10 2013 InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1) Lpstat: device for hp_color_LaserJet_5550: hp:/net/hp_color_LaserJet_5550?zc=Electrical MachineType: Dell Computer Corporation Dimension 4600 MarkForUpload: True Papersize: letter PpdFiles: hp_color_LaserJet_5550: HP Color LaserJet 5550 v3010.107 Postscript (recommended) ProcEnviron: PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-37-generic root=UUID=adff9268-f105-4bd3-aeb2-11be7b02eb8e ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to precise on 2013-01-22 (13 days ago) dmi.bios.date: 07/21/2003 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A03 dmi.board.name: 02Y832 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA03:bd07/21/2003:svnDellComputerCorporation:pnDimension4600:pvr:rvnDellComputerCorp.:rn02Y832:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: Dimension 4600 dmi.sys.vendor: Dell Computer Corporation mtime.conffile..etc.cups.cupsd.conf: 2013-01-31T16:58:59.450493 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1116513/+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 1234469] Re: Network does not come up after resuming from suspend.
Updated to 13.10 just to run into this bug. It happens to me every time I close the lid (Suspend). Every single Ubuntu update has been a similar fiasco for me. I'm beyond disapointed. -- 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/1234469 Title: Network does not come up after resuming from suspend. Status in “network-manager” package in Ubuntu: Confirmed Status in “systemd” package in Ubuntu: Confirmed Bug description: When my computer wakes up from being suspended, the wireless network connection doesn't come back up. I'm able to fix the problem by running nmcli nm sleep false, which causes the wireless card to reconnect. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu21 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Wed Oct 2 20:21:33 2013 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-08-09 (54 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IpRoute: default via 192.168.125.1 dev wlan0 proto static 192.168.125.0/24 dev wlan0 proto kernel scope link src 192.168.125.8 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: Upgraded to saucy on 2013-08-09 (54 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 199a6c07f-9a94-4c8e-82dd-0381befd6f90 802-3-ethernet1380753272 Wed 02 Oct 2013 05:34:32 PM CDTyes no /org/freedesktop/NetworkManager/Settings/1 9739 172c6f5c-b69c-40dd-ac1b-a279c84a17f8 802-11-wireless 1380763079 Wed 02 Oct 2013 08:17:59 PM CDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1234469/+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 1075923] Re: nautilus hangs copying large directories from a samba share
Everything works well for me after updating to version 1.16.1-0ubuntu1.1 I could download 1.7GB of photos from my camera without any trouble. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1075923 Title: nautilus hangs copying large directories from a samba share Status in GVFS: Fix Released Status in “gvfs” package in Ubuntu: Fix Released Status in “gvfs” source package in Precise: In Progress Status in “gvfs” source package in Raring: Fix Committed Bug description: Impact: copies from/to samba share often end up hanging Test case: - visit a smb location in nautilus - copies data from/to it (some non trivial directories makes the issues easier to trigger) - the copy should complete without hanging Regression potentiel: Check that nautilus is still working correctly and than you don't have issues copying data from/to remote locations --- Problem === Copying files to and from samba shares (this includes Windows shares) is unreliable in Ubuntu 12.10 and Ubuntu 13.04 when using nautilus' integrated samba client (gvfs-smb): The copy randomly hangs after a few files or a few GB. Workaround == Until gvfs-smb is fixed, use the kernel samba client (cifs) that works reliably, is faster, but needs some terminal commands to get going: # sudo -s # mkdir /mnt/cifs # mount -t cifs -o user=YOUR_SAMBA_USER -o uid=YOUR_LINUX_USER //SAMBA_SERVER/SAMBA_SHARE /mnt/cifs It will ask for you password, you can then access the shared files at /mnt/cifs. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1075923/+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
