Looks to me like the following bug: http://bugzilla.gnome.org/show_bug.cgi?id=311410
Regards.
On Qua, 2006-06-28 at 02:26 +0200, abel deuring wrote:
> Hi all,
>
> I am fighting with a strange conflict between threading and the
> print dialog from gnomeprint.ui. The following script is stuck
> somewhere in the second constructor call:
>
> import gtk, gnomeprint, gnomeprint.ui
> gtk.threads_init()
> job = gnomeprint.Job(gnomeprint.config_default())
> dlg = gnomeprint.ui.Dialog(job, "Printer Setup", 0)
> dlg.run()
> dlg = gnomeprint.ui.Dialog(job, "Printer Setup", 0)
> dlg.run()
>
> Running the script from strace, I can see that the script is stuck
> waiting for a lock or mutex or so. The last lines from strace are:
>
> access("/bin/gnome-cups-add", X_OK) = -1 ENOENT (No such file or
> directory)
> access("/usr/games/gnome-cups-add", X_OK) = -1 ENOENT (No such file
> or directory)
> access("/opt/gnome/bin/gnome-cups-add", X_OK) = -1 ENOENT (No such
> file or directory)
> access("/opt/kde3/bin/gnome-cups-add", X_OK) = -1 ENOENT (No such
> file or directory)
> futex(0x815b0d8, FUTEX_WAIT, 2, NULL) = -1 EINTR (Interrupted
> system call)
> --- SIGTERM (Terminated) @ 0 (0) ---
> +++ killed by SIGTERM +++
>
> I am seeing this on a Suse 9.3 installation, which unfortunately
> does not have a very recent GTK version: 2.6.4; the PyGTK version is
> 2.5.3; I'm using gnome-python-extras-2.9.4 .
>
> Any ideas or suggestions?
>
> Abel
> _______________________________________________
> pygtk mailing list pygtk@daa.com.au
> http://www.daa.com.au/mailman/listinfo/pygtk
> Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
--
Gustavo J. A. M. Carneiro
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
The universe is always one step beyond logic.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
