don't reopen closed bugs only because you have a similar issue
** Changed in: evince (Ubuntu)
Status: New = Fix Released
--
evince does not enable print
https://bugs.launchpad.net/bugs/66379
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
I see this bug in Gusty Gibbon Ubuntu 7.10
I can print from firefox, openoffice and gedit. But when I try to print
a pdf form evince, it does not show the Print button as enabled.
1. Open up the print dialog, my default printer is selected and the print
button is disabled.
2. Select the Print
I'm not sure if changing status to new is the correct thing to do so
appologies if this is not the correct procedure. I'm trying to reopen this bug
because I'm seeing it on 7.10 and the previous fix was done on 7.04.
thanks,
M
** Changed in: evince (Ubuntu)
Status: Fix Released = New
--
In addition to my previous 2 posts, I ran evince again except starting
inside a shell so that I could see the stdout/sdterr. I seen this
message when I opened up the print diloag for the first time:
** (evince:14375): WARNING **: File is empty
Maybe this doesn't mean anything relevant. However,
(Sorry for not consolidating my posts)
Here is my hosts file - note that locahost is 127.0.0.1 but my machine
name (mdevlin) is 127.0.1.1 - could this have something to do with it?
cat /etc/hosts
127.0.1.1 mdevlin
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost
...maybe Bug #145278 is related to this bug?
--
evince does not enable print
https://bugs.launchpad.net/bugs/66379
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Thank you Evince would not print PDFs at all. All other printing
okay. Your fix worked for me in Ubuntu 7.04. Thanks.
--
evince does not enable print
https://bugs.launchpad.net/bugs/66379
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
That should be fixed in gutsy, closing. Feel free to reopen if you still
get the issue with the new version though
** Changed in: evince (Ubuntu)
Status: Incomplete = Fix Released
--
evince does not enable print
https://bugs.launchpad.net/bugs/66379
You received this bug notification
** Changed in: evince (Ubuntu)
Assignee: Pascal De Vuyst = Ubuntu Desktop Bugs
--
evince does not enable print
https://bugs.launchpad.net/bugs/66379
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
The workaround did not solve the bug on my machine (running Feisty).
While
$ touch /etc/cups/ppd/prnSysadmin.ppd
does give me a URL that exists:
127.0.0.1:631/printers/prnSysadmin.ppd
.. when I select the printer in evince, the print button is still disabled and
the terminal outputs the
the new comment looks like bug #114701, would be interesting to know if
the gutsy GTK version fixes it
--
evince does not enable print
https://bugs.launchpad.net/bugs/66379
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for evince in
Yeah, printing works again here (the same configuration with the same
software does not work on Feisty). Same for evolution (bug #114701).
--
evince does not enable print
https://bugs.launchpad.net/bugs/66379
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
touch /etc/cups/ppd/x.ppd with each printers works for me
Feisty with personnal ppd
localhost 127.0.0.1
--
evince does not enable print
https://bugs.launchpad.net/bugs/66379
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for evince in
I have the same problem (can't print in evince - printing works fine
everywhere else). Printing in evince used to work fine in ubuntu Dapper.
It stopped working when upgrading to Edgy. I hoped Feisty would solve
the bug, but it is still there.
evince will show this message when selecting the
I did an strace on evince while trying to print.
The error ** (evince:24793): WARNING **: Error result: HTTP Error in GET
Success is obtained when trying to open:
http://localhost:631/printers/Queue.ppd
which gives a 404 Not Found error
http://localhost:631/printers/Queue exists: it shows my
http://localhost:631/printers/Queue.ppd exists if the queue is not raw.
If you have a raw queue, it does not have a PPD file and so it gives a
404 Not Found.
evince should also handle raw queues correctly and then only show
options which are suitable for raw queues.
In cas eo f a queue which is
http://bugzilla.gnome.org/show_bug.cgi?id=370685
Comment #4 from Johan Brannlund (reporter, points: 5)
2007-02-26 01:14 UTC
Pete McCormick figured out where the problem lies. In the function
cups_request_ppd_cb in modules/printbackends/cups/gtkprintbackendcups.c,
there's a check for a PPD
Please confirm if the following workaround solves your problem:
$ lpstat -v
device for x: ...
$ touch /etc/cups/ppd/x.ppd
Don't forget to replace the x by your printer name!
--
evince does not enable print
https://bugs.launchpad.net/bugs/66379
You received this bug notification because you are
For me the change of /etc/hosts seems not to work. I can print with
gedit, gimp openoffice ... but not with evince.
evince output:
** (evince:6517): WARNING **: Error result: HTTP Error in GET Success
My /etc/hosts look like this:
127.0.0.1 localhost
127.0.1.1 localhost homer
@Typhos
Looking at you printingbuginfo.txt I see you have no PPD (printer driver)
installed, I assume you have the Lexmark T520.
According to the Lexmark website this printer supports the following languages:
PostScript Level 3 and PCL6.
PostScript printers only need a printer specific PPD file
Here's /etc/hosts (also inline):
127.0.0.1 localhost
127.0.1.1 greenwich
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
**
Hello,
I was in the process of replaying with the requested information, when
I decided to try something.
I noticed that in my /etc/hosts file there was an entry that pointed
do 127.0.1.1 but none to 127.0.0.1, so I added it manually. making it look like
this:
Hello again
I also have this line order in /etc/hosts, and my printers are working.
Does this work for anyone else?
--
evince does not enable print
https://bugs.launchpad.net/bugs/66379
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact
The bug appears to be related to a change in Edgy where the hostname was
added to the /etc/hosts file as 127.0.1.1. There are many threads
(google 127.0.1.1) where this has caused performance problems. It looks
like cups is looking up your machine's IP address based on hostname,
finding the
This bug should be assigned to the package which generates the
/etc/hosts file. The /ect/hosts file itself does not belong to any
package:
[EMAIL PROTECTED]:/opt/lsb-buildenv-ia32/home/till/rpm/SPECS$ dpkg -S /etc/hosts
dpkg: /etc/hosts not found.
[EMAIL
I editing my printingbuginfo.txt to remove information about various
network printers I have installed. I hope this is not an issue.
Here is /etc/hosts (inline since it is relatively short), which displays the
127.0.1.1 issue:
127.0.0.1 localhost
127.0.1.1 imperium.cable.rcn.com
Well, here printing is enabled but there is no job generated.
Starting evince from console there is a message: (evince:16402): Gtk-WARNING
**: Unsupported unit
== System information ==
Release : Ubuntu 7.04 (feisty)
Architecture : i686
Kernel: 2.6.20-15-generic
Locale:
@Markus Kolb
This is a different issue that has been reported as bug #107425.
Please add further information about this issue in that bug report.
--
evince does not enable print
https://bugs.launchpad.net/bugs/66379
You received this bug notification because you are a member of Ubuntu
Desktop
I have found several Ubuntu machines that had /etc/host entries for the
hostname listed as 127.0.1.1 instead of 127.0.0.1. I don't know what
application made the bogus change, but this was the problem with
printing.
--
evince does not enable print
https://bugs.launchpad.net/bugs/66379
You
To track down this problem we need more information from people who have this
problem.
If you experience this problem on Feisty please attach the output of the
printingbug info script for some basic information about your printing setup.
The printingbug info script can be found here:
Unfortunately, it does now work here :-(.
--
evince does not enable print
https://bugs.launchpad.net/bugs/66379
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Hello again
Suddenly, everything (regarding this bug) is working as espected in
Feisty. The Print button is now enabled on all network printers, and it
prints just fine in epiphany, evince and other apps using GTK printing
API.
Can people confirm this? Do you see what I see?
Regards,
Henrik
The same I have in FC6:
http://forum.fedoraforum.org/forum/showthread.php?t=152619
--
evince does not enable print
https://bugs.launchpad.net/bugs/66379
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Moving milestone forward; this is probably post-feisty now unless a fix
appears soon.
** Changed in: evince (Ubuntu)
Target: ubuntu-7.04 = later
--
evince does not enable print
https://bugs.launchpad.net/bugs/66379
You received this bug notification because you are a member of Ubuntu
Hello
I have the same problem. Evince and Epiphany doesn't enable the print
button for most of the printers. It only appears on 1 out of 30 network
printers (the only one using an ip address in the iip address instead of
a host name. Dont know if that can have anything to do with it?)
Other
Hi all
Same probleme here, with no generic ppd files in cups.
Error message in /var/log/cups/access_log was:
localhost - - [09/Mar/2007:10:33:27 +0100] GET /ppd/colos.ppd HTTP/1.1 404 0
- -
where colos is my printer name.
So, under cups, i have to mention /manualy/ the ppd file instead of
I'm having the same problem on Ubuntu Feisty. I filed a bug against gnome-print
yesterday: http://bugzilla.gnome.org/show_bug.cgi?id=413002
I think it's the same problem.
--
evince does not enable print
https://launchpad.net/bugs/66379
--
desktop-bugs mailing list
Roman: gtk 2.10.9 used to be in blastwave.org/testing
it has been removed i dont know why
you probably will have to compile it by hand
or wait for the package to make it to unstable
or better, go to blastwave bug track and submit a bug for gtk2 to ask for the
upgrade
now this was off topic in
Philippe, with what options did you recompile evince?
I tried to do it, configure is ok, but gmake says Error :/
My options is:
./configure --prefix=/opt/evince --with-print=gnome
Also I went another way:
I've installed CSWcups and see my printer in evince's printers list.
But when i choose it,
Roman, i supose you have solaris if you installed CSWcups
i did that too
i did recompile evince with gnome print enable
althought with /opt/csw as prefix that's all
what gtk version do yhou have?
i have 2.10.9 it works ok
only thing, wiht gnomeprint enabled and cups, i cant change the paper
size
Philippe, i have gtk 2.10.1 from blactwave too and have a bug in the printing
backend as you say.
How did you upgrade gtk to 2.10.9 version? Did you recompile it from sources?
Roman
--
evince does not enable print
https://launchpad.net/bugs/66379
--
desktop-bugs mailing list
what is blastwave? Could people trying to get the GTK printing
problems fixed rather than rebuilding evince to use a deprecated API?
--
evince does not enable print
https://launchpad.net/bugs/66379
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
blastwave is a software distribution for Sun Solaris, so it is wildly
out of topic here ;-)
I suffer from the same problem. For me, my printers are broadcast by a
cups server over the network. I can reproduce it with the live CD
(changing Browsing to On in /etc/cups/cupsd.conf, wait for printers
blastwave is a packages system for solaris. (www.blastwave.org)
Solaris 10 include Java Desktop System - it's based on GNOME 2.6.1.
--
evince does not enable print
https://launchpad.net/bugs/66379
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Sorry for the confusion,
I thougth I was answering a post on blastwave/bug where I also posted
the bug about GTK
anyhow, the problem is the same, whether it be ubuntu or blastwave,
knowing evince prints with gnome backend doesnt confirm however the bug
is in gtk cups or evince
it could be
I use gnome 2.14 and evince 0.6.1 unfortunately i have no other
application compiled with gtk print backend
what version of Ubuntu do you use? GtkPrint is a new API from GTK 2.10
which has been shipped with GNOME 2.16 on edgy and not for dapper. On
edgy epiphany-browser uses GtkPrint as well and
** Changed in: evince (Ubuntu)
Importance: Undecided = High
Status: Needs Info = Confirmed
Target: None = ubuntu-7.04
--
evince does not enable print
https://launchpad.net/bugs/66379
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Sorry, i wasn't clear
i am not using ubuntu
i am using sparc/solaris/blastwave
however, googling the web only showed me this thread for the
evince/gtk/cups printing bug
so I post here abou it
(note that this is not ubuntu specific)
regards
--
evince does not enable print
I have the same in solaris. And nothing helps :(
Philippe, did you fix it?
--
evince does not enable print
https://launchpad.net/bugs/66379
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Ok so
gtk 2.10.9 from testing solves on bug and leads to another
i hanv't identified the last one
when printing
cups reports (see error logs in admin from localhost:631) bad request line ...
havnt found anything about that on the net
so I recompiled evince using --with-print=gnome
instead of
Philippe Leroux wrote:
Ok so
gtk 2.10.9 from testing solves on bug and leads to another
i hanv't identified the last one
when printing
cups reports (see error logs in admin from localhost:631) bad request line
...
havnt found anything about that on the net
so I recompiled evince using
Hi, I'm having the same problem
though on solaris using blastwave packages of gnome
firefox prints, gedit prints
but evince reports too many failed attemps
i click continue and then evince freezes...
googling only reports this thread
any tips on how to make it work?
i cant do much about the
Henry, thank you for the useful comment. Do other people having that
problem have a similar configuration problem? Do you use a firewall?
--
evince does not enable print
https://launchpad.net/bugs/66379
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I had this problem (or a very similar one). It was due to evince being
unable to connect to the cups server (connection refused). This was
apparent when I ran evince under strace.
The problem it seemed was due to an error in my hostname aliasing in the
networking configs. Initially, for some
I have the same problem with a cupsserver with several network printers.
None of the printers shows up in the dialog. All other programs work
just fine. (Gedit,firefox,evolution, openoffice,acroread) Only
Evince/Yelp and probably some others with the same printing dialog don't
seem to be working.
the dbus issue is probably different of the printing one. Does it get
fixed if you restart your session or reboot? For the printing, does
gnome-cups-manager works fine? Is cupsys running? Did you change your
configuration to limit the access to clients or something?
--
evince does not enable
Sebastien Bacher wrote:
the dbus issue is probably different of the printing one. Does it get
fixed if you restart your session or reboot? For the printing, does
gnome-cups-manager works fine? Is cupsys running? Did you change your
configuration to limit the access to clients or something?
Sebastien Bacher wrote:
it didn't make the dbus message stop? The printing error looks like
either a cups or gtk printing code issue
The dbus seems to get found, but the folling message is still there,
same result: printing buttons do not get enabled.
WARNING **: Error result: Too many
Le mercredi 18 octobre 2006 à 11:12 +, iroli a écrit :
Sebastien Bacher wrote:
the dbus issue is probably different of the printing one. Does it get
fixed if you restart your session or reboot? For the printing, does
gnome-cups-manager works fine? Is cupsys running? Did you change your
do you use GNOME as desktop? running GNOME applications outside of GNOME
can create issues when there is no dbus bus started
--
evince does not enable print
https://launchpad.net/bugs/66379
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Sebastien Bacher wrote:
do you use GNOME as desktop? running GNOME applications outside of GNOME
can create issues when there is no dbus bus started
yes its a default ubuntu installation using gnome.
--
evince does not enable print
https://launchpad.net/bugs/66379
--
desktop-bugs mailing
Thanks for your bug. evince uses GTK printing API. Do you have the same
issue with yelp or epiphany-browser? Do you have any message on the
command line if you run the application from it?
** Changed in: evince (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs
Status: Unconfirmed
$ evince test.pdf
** (evince:5588): WARNING **: Service registration failed.
** (evince:5588): WARNING **: Unable to determine the address of the
message bus (try 'man dbus-launch' and 'man dbus-daemon' for help)
(evince:5588): libgnomevfs-WARNING **: Failed to open session DBUS
connection:
63 matches
Mail list logo
