Package: gq
Version: 1.0beta1-4
Severity: important

Hello,

after my latest system upgrade (sid) a few days ago, gq crashes very
frequently on random occasions, usually after clicking fast for some
10-20 times at most. Eg. login to a server (2 clicks), unfold the tree
some 2 or 3 levels deep, select an entry -> BOOM! It may take longer,
but adding a common entry (qmailLdapUser) alongside several others at
depth 3 in the tree took me two attempts because on the first, gq
crashed before I had finished the entry. And that's only some 10 simple
fields to enter. Formerly, I could work with gq for hours w/o any
problems. Now, I can't even read a whole tree without a crash.

This is the error message I get when running gq from the console:

$ gq  

Gdk-CRITICAL **: gdk_drawable_get_depth: assertion `GDK_IS_DRAWABLE (drawable)' 
failed
aborting...
Aborted

I realize that this may be a library problem instead, but I don't know
which.


Best,
--Toni++



-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27-2-686-smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages gq depends on:
ii  libatk1.0-0              1.11.4-1        The ATK accessibility toolkit
ii  libc6                    2.3.6-5         GNU C Library: Shared libraries an
ii  libglib2.0-0             2.10.1-2        The GLib library of C routines
ii  libgtk2.0-0              2.8.16-1        The GTK+ graphical user interface 
ii  libldap2                 2.1.30-13       OpenLDAP libraries
ii  libpango1.0-0            1.12.0-2        Layout and rendering of internatio
ii  libssl0.9.7              0.9.7i-1        SSL shared libraries
ii  libxml2                  2.6.23.dfsg.2-3 GNOME XML library
ii  zlib1g                   1:1.2.3-11      compression library - runtime

gq recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to