anjuta crashs on glade openning a ui file in saucy

Bug #1250801 reported by Grizzly(Francis Smit)
46
This bug affects 10 people
Affects Status Importance Assigned to Milestone
anjuta (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

1). $ lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10

2). $ apt-cache policy anjuta
anjuta:
  Installed: 2:3.8.4-1
  Candidate: 2:3.8.4-1
  Version table:
 *** 2:3.8.4-1 0
        500 http://mirror.internode.on.net/pub/ubuntu/ubuntu/ saucy/universe i386 Packages
        100 /var/lib/dpkg/status

3). I expected to be able to open ui files with the Glade plugin

4). it segfaults with the following messages
grizzlysmit@rakbat:~/Projects$ anjuta --no-session&
[1] 16609
grizzlysmit@rakbat:~/Projects$
(anjuta:16609): Gtk-WARNING **: Scintilla 0x96ac908 is mapped but visible child GtkScrollbar 0x94a3c98 is not mapped

(anjuta:16609): Gtk-WARNING **: Scintilla 0x96ac908 is mapped but visible child GtkScrollbar 0x94a3b38 is not mapped

(anjuta:16609): Gtk-WARNING **: Scintilla 0x96ac908 is mapped but visible child GtkScrollbar 0x94a3c98 is not mapped

(anjuta:16609): Gtk-WARNING **: Scintilla 0x96ac908 is mapped but visible child GtkScrollbar 0x94a3b38 is not mapped
GladeUI-Message: No displayable values for property GtkEntry::input-purpose
GladeUI-Message: No displayable values for property GtkEntry::input-hints
GladeUI-Message: No displayable values for property GtkTextView::input-purpose
GladeUI-Message: No displayable values for property GtkTextView::input-hints
GladeUI-Message: 1 missing displayable value for GtkCellRendererAccel::accel-mode
GladeUI-Message: 1 missing displayable value for AnjutaVcsStatusTreeView::status-codes
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:
 AnjutaColumnTextView needs an icon named 'widget-anjuta-columntextview'
 GbfProjectView needs an icon named 'widget-anjuta-view'
 AnjutaPkgConfigChooser needs an icon named 'widget-anjuta-pkg_config_chooser'
 PeasGtkPluginManager needs an icon named 'widget-libpeas-gtk-pluginmanager'
 AnjutaPmChooserButton needs an icon named 'widget-anjuta-button'
 PeasGtkPluginManagerView needs an icon named 'widget-libpeas-gtk-pluginmanagerview'
 AnjutaTreeComboBox needs an icon named 'widget-anjuta-combo'
 AnjutaVcsStatusTreeView needs an icon named 'widget-anjuta-vcsstatus'
 AnjutaEnvironmentEditor needs an icon named 'widget-anjuta-environment_editor'
 AnjutaDropEntry needs an icon named 'widget-anjuta-dropentry'
 AnjutaEntry needs an icon named 'widget-anjuta-entry'
 GtkSourceView needs an icon named 'widget-gtksourceview-gtksourceview'
 AnjutaFileDropEntry needs an icon named 'widget-anjuta-filedropentry'
 AnjutaFileList needs an icon named 'widget-anjuta-filelist'

(anjuta:16609): Gdk-WARNING **: /build/buildd/gtk+3.0-3.8.4/./gdk/x11/gdkwindow-x11.c:5304 drawable is not a native X11 window

(anjuta:16609): 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 49638 error_code 3 request_code 20 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.)

[1]+ Trace/breakpoint trap (core dumped) anjuta --no-session

Tags: bot-comment
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1250801/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → anjuta (Ubuntu)
Revision history for this message
Grizzly(Francis Smit) (grizzly-smit) wrote :

Oh yeah this started right after I updated to Saucy from Raring I rebooted and tried to run Anjuta but it crashed

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in anjuta (Ubuntu):
status: New → Confirmed
Revision history for this message
Grizzly(Francis Smit) (grizzly-smit) wrote :

this bug still affects Trusty 14.04, the anjuta list suggest that: it could be caused by a version miss match between the version of glade in stalled and the one against which anjuta was compiled

Revision history for this message
Cladius J (cladius) wrote :

Hi,
running anjuta from terminal with sudo like this
sudo anjuta
in ubuntu 14.04 seems to solve this problem..

Revision history for this message
Grizzly(Francis Smit) (grizzly-smit) wrote :

yep running anjuta from a terminal
sudo anjuta
works for me too in 14.04

Revision history for this message
Paul Stimpson (dangerjunkie2002) wrote :

This workwround works for me too but it's obviously less than ideal from a security PoV to have to run random pieces of software with system prilileges.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.