ALT Linux Sisyphus discussions
 help / color / mirror / Atom feed
* [sisyphus] gscan2pdf
@ 2007-11-06  8:02 Oleg Turkov
  2007-11-06 20:04 ` Oleg Turkov
  0 siblings, 1 reply; 2+ messages in thread
From: Oleg Turkov @ 2007-11-06  8:02 UTC (permalink / raw)
  To: ALT Linux Sisyphus discussions

Доброго времени суток.
А софтинка gscan2pdf только у меня падает после обновления?
При попытке открыть jpg получаем вот это:

strace gscan2pdf
...
write(2, "The program 'gscan2pdf' received"..., 590The program 'gscan2pdf' 
received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this connection)'.
  (Details: serial 5131 error_code 14 request_code 1 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
) = 590
exit_group(1)                           = ?
Process 5932 detached
perl: xcb_io.c:182: process_responses: Проверочное утверждение `((int) 
(((dpy->last_request_read)) - ((dpy->request))) <= 0)' не выполнено.

-- 
Turkov Oleg
turkov at univ.kiev.ua

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [sisyphus] gscan2pdf
  2007-11-06  8:02 [sisyphus] gscan2pdf Oleg Turkov
@ 2007-11-06 20:04 ` Oleg Turkov
  0 siblings, 0 replies; 2+ messages in thread
From: Oleg Turkov @ 2007-11-06 20:04 UTC (permalink / raw)
  To: ALT Linux Sisyphus discussions

В сообщении от 6 ноября 2007 Oleg Turkov написал(a):
> strace gscan2pdf
> ...
> write(2, "The program 'gscan2pdf' received"..., 590The program 'gscan2pdf'
> received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadIDChoice (invalid resource ID chosen for this
> connection)'. (Details: serial 5131 error_code 14 request_code 1 minor_code
> 0) (Note to programmers: normally, X errors are reported asynchronously;
> that is, you will receive the error a while after causing it.
>    To debug your program, run it with the --sync command line
>    option to change this behavior. You can then get a meaningful
>    backtrace from your debugger if you break on the gdk_x_error()
> function.) ) = 590
> exit_group(1)                           = ?
> Process 5932 detached
> perl: xcb_io.c:182: process_responses: Проверочное утверждение `((int)
> (((dpy->last_request_read)) - ((dpy->request))) <= 0)' не выполнено.

https://bugzilla.altlinux.org/show_bug.cgi?id=13340

Откатился на версию 0.9.16-alt2, работает. 

-- 
Turkov Oleg
turkov at univ.kiev.ua


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-11-06 20:04 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-11-06  8:02 [sisyphus] gscan2pdf Oleg Turkov
2007-11-06 20:04 ` Oleg Turkov

ALT Linux Sisyphus discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/sisyphus/0 sisyphus/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 sisyphus sisyphus/ http://lore.altlinux.org/sisyphus \
		sisyphus@altlinux.ru sisyphus@altlinux.org sisyphus@lists.altlinux.org sisyphus@lists.altlinux.ru sisyphus@lists.altlinux.com sisyphus@linuxteam.iplabs.ru sisyphus@list.linux-os.ru
	public-inbox-index sisyphus

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.sisyphus


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git