Bug 691798 - anjuta window gets stuck when compiling
Summary: anjuta window gets stuck when compiling
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: anjuta
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Debarshi Ray
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-29 14:00 UTC by Lukas Bezdicka
Modified: 2011-03-29 14:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-29 14:18:04 UTC
Type: ---


Attachments (Terms of Use)

Description Lukas Bezdicka 2011-03-29 14:00:40 UTC
Description of problem:
when starting to build project anjuta window hangs

Version-Release number of selected component (if applicable):
# rpm -qa | grep anjuta
anjuta-devel-2.91.90.0-2.fc15.x86_64
anjuta-2.91.90.0-2.fc15.x86_64
anjuta-doc-2.91.90.0-2.fc15.noarch


How reproducible:
always
 
Actual results:
# strace -p 9650
Process 9650 attached - interrupt to quit
write(2, "\n(anjuta:9650): Gtk-WARNING **: "..., 128) = 128
write(2, "\n(anjuta:9650): Gtk-WARNING **: "..., 128) = 128
write(2, "\n(anjuta:9650): Gtk-WARNING **: "..., 128) = 128

Additional info:
# tail /home/social/.xsession-errors

(anjuta:9650): Gtk-WARNING **: gtkstylecontext.c:2519: widget class `AnjutaTabber' has no style property named `tab-curvature'

(anjuta:9650): Gtk-WARNING **: gtkstylecontext.c:2519: widget class `AnjutaTabber' has no style property named `tab-curvature'

(anjuta:9650): Gtk-WARNING **: gtkstylecontext.c:2519: widget class `AnjutaTabber' has no style property named `tab-curvature'

(anjuta:9650): Gtk-WARNING **: gtkstylecontext.c:2519: widget class `AnjutaTabber' has no style property named `tab-curvature'

(anjuta:9650): Gtk-WARNING **: gtkstylecontext.c:2519: widget class `AnjutaTabber' has no style property named `tab-curvature'

Comment 1 Johannes Schmid 2011-03-29 14:18:04 UTC
Thanks for reporting. This is already fixed upstream (should be in 2.91.92).


Note You need to log in before you can comment on or make changes to this bug.