[Desktop-packages] [Bug 1020048] Re: after certain time printing to cups stops working
We run linux clients that connect to a central print server. I found this works: 1) Install cups server on the clients. 2) On clients turn on "Show printers shared by other systems" in web interface or in /etc/cups/cupsd.conf # Show shared printers on the local network. Browsing On BrowseOrder allow,deny BrowseAllow all BrowseLocalProtocols CUPS dnssd BrowseAddress @LOCAL BrowseAddress server:631 # *** NOTE I've added an entry that points directly to our main cups server - to speed up discovery. 3) On clients add a "BrowseAddress server:631" that points directly to your cups server. Change "server" to addres of your cups server. ( see above ) 4) On clients comment out all entries in /etc/cups/client.conf . This will force cups to use /var/run/cups/cups.sock on the client. Generally works because libreoffice doesn't communicate over TCP:631, rather directly to the local socket and the client<=>server communication is done via cupsd<=>cupsd: Client Libreoffice ... =>local-cups(with browsing on listening on /var/un/cups/cups.sock) ... =>server:631 browsing cups ... =>printer. It uses a bit more RAM on the client to run the cups server but RAM is not as much of an issue these days. USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 1071 0.0 0.2 11164 3816 ?Ss 10:45 0:00 /usr/sbin/cupsd -F -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1020048 Title: after certain time printing to cups stops working Status in LibreOffice Productivity Suite: New Status in “cups” package in Ubuntu: Fix Released Status in “libreoffice” package in Ubuntu: Confirmed Bug description: in our institution we are running only printers through a cups server. while freshly opened document prints well, after some time (few minutes) clicking "print file directly" and menu item "print" do not work any more. after close and open again, thing prints correctly. i have checked what exactly is going on in such cases and logs on the cups server don't show any submissions and/or errors so that the thing is obviously stopped at the level of libreoffice. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice 1:3.5.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Mon Jul 2 12:29:31 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash LC_PAPER=en_GB.UTF-8 SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1020048/+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 969489] Re: lightdm tries (and fails) to start too early?
With our particular setup of school labs. 2-3 out of 30 stations would always fail - the display manager would not start. On the kernel i turned removed: splash & quiet and noticed that the events proceeding starting lightdm were quite a bit shorter for the failed machines. When I turned on more debugging features, all the machines boot-up fine with no errors! So my hack/solution: * kernel boot options remove: splash quiet * kernel boot options add: verbose init=/sbin/init --verbose * /etc/default/rcS VERBOSE=yes My guess is that dumping the verbose text out to the screen creates just enough delay to fix the race condition. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? Status in Upstart: New Status in “lightdm” package in Ubuntu: Confirmed Bug description: Sometimes lightdm comes up fine. Other times it appears to fail. x-0.log shows it tried to load 'nv' (rather than 'nvidia' which is what actually exists). When I then log into console and 'start lightdm', it comes up fine (on :1). I've not had it come up ok today, so I don't know if, when it comes up fine, it starts on :0. No idea if the lightdm.conf needs a change to 'start on'clause, or if this is just a case of a bad shipped config file (for module 'nv'). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.1.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu1 Architecture: amd64 Date: Fri Mar 30 13:40:27 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120323) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+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 463059] Re: Process 'gs' begins taking 100% CPU and loading up vast amounts of RAM
Resolved this issue by lowering and creating custom DPI values. Default DPI from foomatic postcript PPDs is usually 600 DPI or 1200 DPI. Ghostscript `pdftops` and `gs` both take a long time converting high DPI values. The 600 DPI also creates a large postscript file which in turn are slow over the network as well as slow spooling on the printer itself. Printers have low RAM & small CPU. When I lowered DPI to 300 the print jobs were almost instantaneous. However the print quality was degraded. I modified the PPD files for dozen or so laser printers and found that 400DPI is identical to 600DPI in terms of print quality. With our printers I found the "sweet spot" to be 350DPI for print quality and maximum speed. To get custom "time/quality sweet spot" DPI values, you will need to edit your PPD file: cp /etc/cups/ppd/MYPRINTER.ppd $HOME/ Edit MYPRINTER.ppd 'Resolution' section and add 350 and 400 DPI. *DefaultResolution: 350x350dpi *Resolution 150x150dpi/150x150 DPI: "<>setpagedevice" *Resolution 300x300dpi/300x300 DPI: "<>setpagedevice" *Resolution 350x350dpi/350x350 DPI: "<>setpagedevice" *Resolution 400x400dpi/400x400 DPI: "<>setpagedevice" *Resolution 600x600dpi/600x600 DPI: "<>setpagedevice" You may want to update the ModelName, ShortNickName and NickName to indicate that this file has been modified. You can then either use the web interface to upload your custom ppd file or copy it to /usr/local/share/ppd/MYPRINTER.ppd Then restart cups service. Your custom PPD option will then appear in the pick-list when Modify Printer. Once the PPD is installed then go to the Default Options to set the DPI Resolution. You may want to test the timing/quality for 300, 350, 400, 600. I had 2 printers where 300DPI quality was just as good as the 600 DPI. If an end-user enjoys the long print delay so they can socialize at the printer - or enjoys burning CPU cycles imagining that their 1200dpi is actually "better quality", then all they have to do is increase the DPI setting on the print dialog before they send their job. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to foomatic-filters in Ubuntu. https://bugs.launchpad.net/bugs/463059 Title: Process 'gs' begins taking 100% CPU and loading up vast amounts of RAM Status in foomatic-filters package in Ubuntu: Fix Released Status in foomatic-filters source package in Karmic: Fix Released Bug description: Binary package hint: ghostscript My printer doesn't detect for some reason until I restart CUPS, so I ran: 'sudo /etc/init.d/cups restart'. Returned with [OK]. Then, process 'gs' (Ghostscript?) begins taking up all of my RAM (left me at 850/1000mb RAM used, 500/600mb swap used) and my CPU usage goes to 100%. Hard drive is chugging hard. I don't know why this is happening when I haven't even attempted to print yet. I'm not sure if this is a problem with my printer driver or Ghostscript (are they the same thing?). I have a Canon i860 printer plugged in via USB. I'm not sure which log files to add so I'll wait for some comments. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foomatic-filters/+bug/463059/+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 488710] Re: pdftops too slow with certain PDF files
Resolved this issue by lowering and creating custom DPI values. Default DPI from foomatic postcript PPDs is usually 600 DPI or 1200 DPI. Ghostscript `pdftops` and `gs` both take a long time converting high DPI values. The 600 DPI also creates a large postscript file which in turn are slow over the network as well as slow spooling on the printer itself. Printers have low RAM & small CPU. When I lowered DPI to 300 the print jobs were almost instantaneous. However the print quality was degraded. I modified the PPD files for dozen or so laser printers and found that 400DPI is identical to 600DPI in terms of print quality. With our printers I found the "sweet spot" to be 350DPI for print quality and maximum speed. To get custom "time/quality sweet spot" DPI values, you will need to edit your PPD file: cp /etc/cups/ppd/MYPRINTER.ppd $HOME/ Edit MYPRINTER.ppd 'Resolution' section and add 350 and 400 DPI. *DefaultResolution: 350x350dpi *Resolution 150x150dpi/150x150 DPI: "<>setpagedevice" *Resolution 300x300dpi/300x300 DPI: "<>setpagedevice" *Resolution 350x350dpi/350x350 DPI: "<>setpagedevice" *Resolution 400x400dpi/400x400 DPI: "<>setpagedevice" *Resolution 600x600dpi/600x600 DPI: "<>setpagedevice" You may want to update the ModelName, ShortNickName and NickName to indicate that this file has been modified. You can then either use the web interface to upload your custom ppd file or copy it to /usr/local/share/ppd/MYPRINTER.ppd Then restart cups service. Your custom PPD option will then appear in the pick-list when Modify Printer. Once the PPD is installed then go to the Default Options to set the DPI Resolution. You may want to test the timing/quality for 300, 350, 400, 600. I had 2 printers where 300DPI quality was just as good as the 600 DPI. If an end-user enjoys the long print delay so they can socialize at the printer - or enjoys burning CPU cycles imagining that their 1200dpi is actually "better quality", then all they have to do is increase the DPI setting on the print dialog before they send their job. -- 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/488710 Title: pdftops too slow with certain PDF files Status in poppler package in Ubuntu: Triaged Status in xpdf package in Ubuntu: Invalid Bug description: Binary package hint: cups The attached file won't print either from evince or lpr. Printing via xpdf causes xpdf to hang. A debug log is attached, the relevant job number is 593. Maybe relevant: in the document print status, the printer is shown as "Printer not connected?" However, other files print OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/488710/+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 848562] Re: gnome-shell lock screen does not display password prompt
Duplicate bug posted here: https://bugs.launchpad.net/linuxmint/+bug/1005545 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/848562 Title: gnome-shell lock screen does not display password prompt Status in GNOME Screensaver: Invalid Status in GNOME Shell: Fix Released Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: I have two monitors, the laptop screen and an external one connected via display port. When I do 'ctrl-alt-L' in gnome-shell to lock the screen, the laptop screen displays the screen background and the second monitor displays whatever was on it before locking the screen. When I press a key, no password prompt appears - the laptop continues to display the background. However, entering the password at this point unlocks the computer. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-shell 3.1.90.1-0ubuntu4 Uname: Linux 3.1.0-rc6-git-20110913.0846 x86_64 ApportVersion: 1.22.1-0ubuntu2 Architecture: amd64 Date: Tue Sep 13 11:42:07 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330) SourcePackage: gnome-shell UpgradeStatus: Upgraded to oneiric on 2011-09-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/848562/+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 289592] Re: Unknown media types in /usr/share/mime/packages/kde.xml
In package shared-mime-info there is update-mime-database.c and around
line 51 there is a hard-programmed list of mime types used to flag
invalid MIME types
/* This is the list of directories to scan when finding old type files to
* delete. It is also used to warn about invalid MIME types.
*/
const char *media_types[] = {
"text",
"application",
"image",
"audio",
"inode",
"video",
"message",
"model",
"multipart",
"x-content",
"x-epoc",
"x-scheme-handler",
};
in the get_type function around line 261 the program scans the hard-
coded list of mime types or it returns the error that everyone is
complaining about.
for (i = 0; i < G_N_ELEMENTS(media_types); i++)
{
if (strcmp(media_types[i], type->media) == 0)
return type;
}
g_warning("Unknown media type in type '%s'", name);
Dean M.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to shared-mime-info in Ubuntu.
https://bugs.launchpad.net/bugs/289592
Title:
Unknown media types in /usr/share/mime/packages/kde.xml
Status in shared-mime-info:
Confirmed
Status in kde4libs package in Ubuntu:
Invalid
Status in shared-mime-info package in Ubuntu:
Triaged
Status in kde4libs package in Debian:
New
Status in shared-mime-info package in Debian:
Confirmed
Bug description:
Here is the problem:
# update-mime-database /usr/share/mime
[...]
Unknown media type in type 'uri/mms'
Unknown media type in type 'uri/mmst'
Unknown media type in type 'uri/mmsu'
Unknown media type in type 'uri/pnm'
Unknown media type in type 'uri/rtspt'
Unknown media type in type 'uri/rtspu'
It seems to come from this file:
/usr/share/mime/packages/kde.xml
To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/289592/+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 289592] Re: Unknown media types in /usr/share/mime/packages/kde.xml
that `const char *media_types` either needs more added to it or a way to hook in an external file containing that list. Google search turns up some common "Unknown media type": all chemical uri interface map fonts vms zz-aplication -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/289592 Title: Unknown media types in /usr/share/mime/packages/kde.xml Status in shared-mime-info: Confirmed Status in kde4libs package in Ubuntu: Invalid Status in shared-mime-info package in Ubuntu: Triaged Status in kde4libs package in Debian: New Status in shared-mime-info package in Debian: Confirmed Bug description: Here is the problem: # update-mime-database /usr/share/mime [...] Unknown media type in type 'uri/mms' Unknown media type in type 'uri/mmst' Unknown media type in type 'uri/mmsu' Unknown media type in type 'uri/pnm' Unknown media type in type 'uri/rtspt' Unknown media type in type 'uri/rtspu' It seems to come from this file: /usr/share/mime/packages/kde.xml To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/289592/+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
