Comment 3 for bug 1444894

Revision history for this message
Ben Romer (bromer) wrote :

Same problem on Anjuta on 15.10.

Trying to open the UI file on a brand-new GTK C project causes:

GladeUI-Message: 20 missing displayable value for GtkWidget::AtkObject::accessible-role
GladeUI-Message: 1 missing displayable value for GtkButtonBox::layout-style
GladeUI-Message: 1 missing displayable value for GtkScrolledWindow::hscrollbar-policy
GladeUI-Message: 1 missing displayable value for GtkCellRendererAccel::accel-mode
GladeUI-Message: No displayable values for property GtkSourceView::background-pattern
GladeUI-Message: No displayable values for property VteTerminal::backspace-binding
GladeUI-Message: No displayable values for property VteTerminal::cursor-blink-mode
GladeUI-Message: No displayable values for property VteTerminal::cursor-shape
GladeUI-Message: No displayable values for property VteTerminal::delete-binding
GladeUI-Message: Glade needs artwork; a default icon will be used for the following classes:
 GtkApplicationWindow needs an icon named 'widget-gtk-applicationwindow'
 PeasGtkPluginManager needs an icon named 'widget-libpeas-gtk-pluginmanager'
 GtkSourceStyleSchemeChooserWidget needs an icon named 'widget-gtksourceview-gtksourcestyleschemechooserwidget'
 GtkSourceView needs an icon named 'widget-gtksourceview-gtksourceview'
 GtkSourceStyleSchemeChooserButton needs an icon named 'widget-gtksourceview-gtksourcestyleschemechooserbutton'
 PeasGtkPluginManagerView needs an icon named 'widget-libpeas-gtk-pluginmanagerview'

(anjuta:12538): Gdk-WARNING **: /build/gtk+3.0-pIzeMy/gtk+3.0-3.16.7/./gdk/x11/gdkwindow-x11.c:5540 drawable is not a native X11 window

(anjuta:12538): Gdk-ERROR **: The program 'anjuta' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 20600 error_code 3 request_code 20 (core protocol) 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 GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)