Description of problem: I try to create a new glade-3 project: glade-3 dies, if first clicking on any icon in the Toplevels area, exept the Window icon (the first in the toplevels area). Version-Release number of selected component (if applicable): glade3-3.7.1-2.fc14.i686 How reproducible: Always Steps to Reproduce: 1.glade-3 2.Click on any icon in the Toplevel area (exept the "Window" icon) 3. Actual results: glade-3 dies withe the msg: ** GladeUI:ERROR:glade-project.c:4365:glade_project_model_get_path: assertion failed: (top != NULL) Aborted (core dumped) Expected results: glade-3 continues Additional info:
Same here. Here is the stack trace: (gdb) bt #0 __kernel_vsyscall () at arch/x86/vdso/vdso32/sysenter.S:49 #1 0x002cf501 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #2 0x002d0f6e in abort () at abort.c:92 #3 0x00553c84 in g_assertion_message (domain=0x995160 "GladeUI", file=0x99695a "glade-project.c", line=4365, func=0x997e87 "glade_project_model_get_path", message=<value optimized out>) at gtestutils.c:1358 #4 0x005541ee in g_assertion_message_expr (domain=0x995160 "GladeUI", file=0x99695a "glade-project.c", line=4365, func=0x997e87 "glade_project_model_get_path", expr= 0x996ac4 "top != NULL") at gtestutils.c:1369 #5 0x0093fa98 in glade_project_model_get_path (model=0xa60f668, iter=0xbfe1e2c0) at glade-project.c:4365 #6 0x02c69e56 in IA__gtk_tree_model_get_path (tree_model=0xa60f668, iter=0xbfe1e2c0) at gtktreemodel.c:1143 #7 0x009418d7 in glade_project_add_object (project=0xa60f668 [GladeProject], old_project=0xa60f668 [GladeProject], object=0xa6ffcf8 [GtkHButtonBox]) at glade-project.c:2730 #8 0x009417c1 in glade_project_add_object (project=0xa60f668 [GladeProject], old_project=0xa60f668 [GladeProject], object=0xa647318 [GtkVBox]) at glade-project.c:2707 #9 0x009417c1 in glade_project_add_object (project=0xa60f668 [GladeProject], old_project=0xa60f668 [GladeProject], object=0xa357418 [GtkDialog]) at glade-project.c:2707 #10 0x00980d47 in glade_command_add_execute (cmd=0xa6710f0 [GladeCommandAddRemove]) at glade-command.c:1392 #11 glade_command_add_remove_execute (cmd=0xa6710f0 [GladeCommandAddRemove]) at glade-command.c:1454 #12 0x00982415 in glade_command_add (widgets=0xa7735d0 = {...}, parent=0x0, placeholder=0x0, pasting=0) at glade-command.c:1084 #13 0x00983ecf in glade_command_create (adaptor=0xa3afed8 [GladeGtkDialogAdaptor], parent=0x0, placeholder=0x0, project=0xa60f668 [GladeProject]) at glade-command.c:1739 #14 0x0094de0c in glade_palette_create_root_widget (palette=0xa090b58 [GladePalette], adaptor=0xa3afed8 [GladeGtkDialogAdaptor]) at glade-palette.c:423 #15 0x0094e238 in glade_palette_toggled (palette=0xa090b58 [GladePalette]) at glade-palette.c:326 #16 0x00137bc4 in g_cclosure_marshal_VOID__VOID (closure=0xa1ac660, return_value=0x0, n_param_values=1, param_values=0xa69b620, invocation_hint=0xbfe1e6d0, marshal_data=0x94e1a0) at gmarshal.c:79 #17 0x0011a538 in g_type_class_meta_marshal (closure=0xa1ac660, return_value=0x0, n_param_values=1, param_values=0xa69b620, invocation_hint=0xbfe1e6d0, marshal_data=0x1a0) at gclosure.c:877 #18 0x0011bbe3 in g_closure_invoke (closure=0xa1ac660, return_value=0x0, n_param_values=1, param_values=0xa69b620, invocation_hint=0xbfe1e6d0) at gclosure.c:766 #19 0x0012def5 in signal_emit_unlocked_R (node=0xa06c7a0, detail=0, instance=0xa090b58, emission_return=0x0, instance_and_params=0xa69b620) at gsignal.c:3290 #20 0x0013724e in g_signal_emit_valist (instance=0xa090b58, signal_id=464, detail=0, var_args=0xbfe1e88c "\274\350\341\277h\352\025") at gsignal.c:2983 #21 0x00137403 in g_signal_emit (instance=0xa090b58, signal_id=464, detail=0) at gsignal.c:3040 #22 0x0094e0b8 in glade_palette_on_button_toggled (button=0xa38f0f0 [GtkToggleToolButton], palette=0xa090b58 [GladePalette]) at glade-palette.c:498 #23 0x00137bc4 in g_cclosure_marshal_VOID__VOID (closure=0xa1104f8, return_value=0x0, n_param_values=1, param_values=0xb1900f80, invocation_hint=0xbfe1ea20, marshal_data=0x0) at gmarshal.c:79 #24 0x0011bbe3 in g_closure_invoke (closure=0xa1104f8, return_value=0x0, n_param_values=1, param_values=0xb1900f80, invocation_hint=0xbfe1ea20) at gclosure.c:766 #25 0x0012e0f0 in signal_emit_unlocked_R (node=0xa2ed538, detail=0, instance=0xa38f0f0, emission_return=0x0, instance_and_params=0xb1900f80) at gsignal.c:3252 #26 0x0013724e in g_signal_emit_valist (instance=0xa38f0f0, signal_id=277, detail=0, var_args=0xbfe1ebdc "\rV\024") at gsignal.c:2983 #27 0x00137403 in g_signal_emit (instance=0xa38f0f0, signal_id=277, detail=0) at gsignal.c:3040 #28 0x02c4d11b in button_toggled (widget=0xa090f58 [GtkToggleButton], toggle_tool_button=0xa38f0f0 [GtkToggleToolButton]) at gtktoggletoolbutton.c:310 #29 0x00137bc4 in g_cclosure_marshal_VOID__VOID (closure=0xa10f8a0, return_value=0x0, n_param_values=1, param_values=0xa77d580, invocation_hint=0xbfe1ed50, marshal_data=0x0) at gmarshal.c:79 #30 0x0011bbe3 in g_closure_invoke (closure=0xa10f8a0, return_value=0x0, n_param_values=1, param_values=0xa77d580, invocation_hint=0xbfe1ed50) at gclosure.c:766 #31 0x0012e0f0 in signal_emit_unlocked_R (node=0xa223b20, detail=0, instance=0xa090f58, emission_return=0x0, instance_and_params=0xa77d580) at gsignal.c:3252 #32 0x0013724e in g_signal_emit_valist (instance=0xa090f58, signal_id=219, detail=0, var_args= 0xbfe1ef0c "\204j\353\002\204j\353\002X\017\t\nH\357\341\277z\312\304\002X\017\t\n8\320\033\n\313p\250\002\204j\353\002\200\342\017\n\270\215\"\nh\357\341\277h\352\025") at gsignal.c:2983 #33 0x00137403 in g_signal_emit (instance=0xa090f58, signal_id=219, detail=0) at gsignal.c:3040 #34 0x02c4ca1a in IA__gtk_toggle_button_toggled (toggle_button=0xa090f58 [GtkToggleButton]) at gtktogglebutton.c:365 #35 0x02c4ca7a in gtk_toggle_button_clicked (button=0xa090f58 [GtkToggleButton]) at gtktogglebutton.c:498 #36 0x00137bc4 in g_cclosure_marshal_VOID__VOID (closure=0xa207bd8, return_value=0x0, n_param_values=1, param_values=0xb1900f50, invocation_hint=0xbfe1f0d0, marshal_data= 0x2c4ca30) at gmarshal.c:79 #37 0x0011a538 in g_type_class_meta_marshal (closure=0xa207bd8, return_value=0x0, n_param_values=1, param_values=0xb1900f50, invocation_hint=0xbfe1f0d0, marshal_data=0x1a8) at gclosure.c:877 #38 0x0011bbe3 in g_closure_invoke (closure=0xa207bd8, return_value=0x0, n_param_values=1, param_values=0xb1900f50, invocation_hint=0xbfe1f0d0) at gclosure.c:766 #39 0x0012d86e in signal_emit_unlocked_R (node=0xa21cb68, detail=0, instance=0xa090f58, emission_return=0x0, instance_and_params=0xb1900f50) at gsignal.c:3182 #40 0x0013724e in g_signal_emit_valist (instance=0xa090f58, signal_id=208, detail=0, var_args=0xbfe1f28c "\rV\024") at gsignal.c:2983 #41 0x00137403 in g_signal_emit (instance=0xa090f58, signal_id=208, detail=0) at gsignal.c:3040 #42 0x02a916fa in IA__gtk_button_clicked (button=0xa090f58 [GtkToggleButton]) at gtkbutton.c:1128 #43 0x02c4c1c8 in gtk_toggle_button_released (button=0xa090f58 [GtkToggleButton]) at gtktogglebutton.c:485 #44 0x00137bc4 in g_cclosure_marshal_VOID__VOID (closure=0xa220a20, return_value=0x0, n_param_values=1, param_values=0xa77cb90, invocation_hint=0xbfe1f440, marshal_data=0x2c4c150) at gmarshal.c:79 #45 0x0011a538 in g_type_class_meta_marshal (closure=0xa220a20, return_value=0x0, n_param_values=1, param_values=0xa77cb90, invocation_hint=0xbfe1f440, marshal_data=0x1a4) at gclosure.c:877 #46 0x0011bbe3 in g_closure_invoke (closure=0xa220a20, return_value=0x0, n_param_values=1, param_values=0xa77cb90, invocation_hint=0xbfe1f440) at gclosure.c:766 #47 0x0012d86e in signal_emit_unlocked_R (node=0xa220a60, detail=0, instance=0xa090f58, emission_return=0x0, instance_and_params=0xa77cb90) at gsignal.c:3182 #48 0x0013724e in g_signal_emit_valist (instance=0xa090f58, signal_id=207, detail=0, var_args= 0xbfe1f5fc "\200\025\251\002\204j\353\002\304\367\341\277(\366\341\277d\026\251\002X\017\t\n\030\312\033\nX\366ῄj\353\002)\026\251\002\204j\353\002h\366\341\277\030'\266\002X\017\t\n8\317p\n") at gsignal.c:2983 #49 0x00137403 in g_signal_emit (instance=0xa090f58, signal_id=207, detail=0) at gsignal.c:3040 #50 0x02a9160a in gtk_button_released (button=0xa090f58 [GtkToggleButton]) at gtkbutton.c:1120 #51 0x02a91664 in gtk_button_button_release (widget=0xa090f58 [GtkToggleButton], event=0xa70cf38) at gtkbutton.c:1617 #52 0x02b62718 in _gtk_marshal_BOOLEAN__BOXED (closure=0xa0216c0, return_value=0xbfe1f7c4, n_param_values=2, param_values=0xa6e3db8, invocation_hint=0xbfe1f7b0, marshal_data= 0x2a91620) at gtkmarshalers.c:86 #53 0x0011a538 in g_type_class_meta_marshal (closure=0xa0216c0, return_value=0xbfe1f7c4, n_param_values=2, param_values=0xa6e3db8, invocation_hint=0xbfe1f7b0, marshal_data=0xb4) at gclosure.c:877 #54 0x0011bbe3 in g_closure_invoke (closure=0xa0216c0, return_value=0xbfe1f7c4, n_param_values=2, param_values=0xa6e3db8, invocation_hint=0xbfe1f7b0) at gclosure.c:766 #55 0x0012def5 in signal_emit_unlocked_R (node=0xa0217a8, detail=0, instance=0xa090f58, emission_return=0xbfe1f8fc, instance_and_params=0xa6e3db8) at gsignal.c:3290 #56 0x00136fcd in g_signal_emit_valist (instance=0xa090f58, signal_id=34, detail=0, var_args=0xbfe1f970 "\234\371\341\277X\324\001\n\002\371Ὶ(\313\002\204j\353\002") at gsignal.c:2993 #57 0x00137403 in g_signal_emit (instance=0xa090f58, signal_id=34, detail=0) at gsignal.c:3040 #58 0x02cb2b1e in gtk_widget_event_internal (widget=0xa090f58 [GtkToggleButton], event=0xa70cf38) at gtkwidget.c:4992 #59 0x02b60445 in IA__gtk_propagate_event (widget=0xa090f58 [GtkToggleButton], event=0xa70cf38) at gtkmain.c:2460 #60 0x02b60857 in IA__gtk_main_do_event (event=<value optimized out>) at gtkmain.c:1665 #61 0x0299638b in gdk_event_dispatch (source=0xa01cbc0, callback=0, user_data=0x0) at gdkevents-x11.c:2377 #62 0x0052c192 in g_main_dispatch (context=0xa01cc90) at gmain.c:2149 #63 g_main_context_dispatch (context=0xa01cc90) at gmain.c:2702 #64 0x0052c978 in g_main_context_iterate (context=0xa01cc90, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2780 #65 0x0052d04b in g_main_loop_run (loop=0xa6fe3f0) at gmain.c:2988 #66 0x02b5f499 in IA__gtk_main () at gtkmain.c:1237 #67 0x08055a87 in main (argc=1, argv=0xbfe1fd04) at main.c:186
Here is upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=619530
glade3 just cloned by git master ( 7070760c327ec2a7493d21bf0cf8ee0f4b568f59 ) works fine for me.
Upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=619530 resolved fixed.
Please add the upstream patch: http://git.gnome.org/browse/glade3/commit/?id=23b54570033436349238cdd8cbc0f97dd48ffe12
This bug makes glade unusable for me. I think this should be marked as a HIGH priority bug! Does anyone have plans to get this fixed any time soon?
(In reply to comment #6) > Does anyone have plans to get this fixed any time soon? It doesn't seem so
ping Huzaifa Will have a look if he does not pick it up in few days.
I think fix this would actually clean quite some of the glade-3 bugs: #643753 #639214 #609308 #611843 #615266 #615266 #626799 Less sure for: #639643 #643899
Ok I am taking it now.
Backporting the upstream patch does not make it go away. May be I need to push an update. Will test and see if something else needs to be done ..
Can someone confirm that it does not go away. You will need to manually download glade3 and glade3-libgladeui from: http://koji.fedoraproject.org/koji/buildinfo?buildID=209821 and install locally to try. Meanwhile I will check upstream. /rakesh
I have installed the packages mentioned in comment #12, and indeed the problem is still present in this version.
This would mean the best option is to put on an epoch as suggested in the bug: https://bugzilla.redhat.com/show_bug.cgi?id=649380
(In reply to comment #14) > This would mean the best option is to put on an epoch as suggested in the bug: > https://bugzilla.redhat.com/show_bug.cgi?id=649380 Yes, that is an option, which I wanted to avoid. Will check whether it does affect other packages as well.
*** Bug 649380 has been marked as a duplicate of this bug. ***
[rakesh@localhost SPECS]$ repoquery -q --whatrequires --alldeps glade3-libgladeui glade3-libgladeui-0:3.7.1-2.fc14.i686 glade3-libgladeui-0:3.7.1-2.fc14.x86_64 anjuta-1:2.31.90.0-1.fc14.i686 anjuta-1:2.31.90.0-1.fc14.x86_64 glade3-0:3.7.1-2.fc14.x86_64 glade3-libgladeui-devel-0:3.7.1-2.fc14.i686 glade3-libgladeui-devel-0:3.7.1-2.fc14.x86_64 gnome-media-devel-0:2.32.0-1.fc14.i686 gnome-media-devel-0:2.32.0-1.fc14.x86_64 gtkdatabox-glade-0:0.9.1.1-3.fc14.x86_64 libxfce4ui-devel-0:4.7.2-2.fc14.i686 libxfce4ui-devel-0:4.7.2-2.fc14.x86_64 libxfcegui4-devel-0:4.6.4-1.fc14.i686 libxfcegui4-devel-0:4.6.4-1.fc14.x86_64 libxfcegui4-devel-0:4.6.4-3.fc14.i686 libxfcegui4-devel-0:4.6.4-3.fc14.x86_64 I will build glade3 3.6.7 after adding epoch and ask for tag request for pushing to F14 from rel-eng. I will need to rebuild anjuta, gnome-media, gtkdatabox-glade and libxfcegui4.
https://fedorahosted.org/rel-eng/ticket/4307
*** Bug 637142 has been marked as a duplicate of this bug. ***
*** Bug 609308 has been marked as a duplicate of this bug. ***
*** Bug 639214 has been marked as a duplicate of this bug. ***
*** Bug 639643 has been marked as a duplicate of this bug. ***
*** Bug 643753 has been marked as a duplicate of this bug. ***
*** Bug 643899 has been marked as a duplicate of this bug. ***
*** Bug 662263 has been marked as a duplicate of this bug. ***
*** Bug 661991 has been marked as a duplicate of this bug. ***
*** Bug 659780 has been marked as a duplicate of this bug. ***
*** Bug 659435 has been marked as a duplicate of this bug. ***
*** Bug 657748 has been marked as a duplicate of this bug. ***
*** Bug 657639 has been marked as a duplicate of this bug. ***
*** Bug 657504 has been marked as a duplicate of this bug. ***
*** Bug 656065 has been marked as a duplicate of this bug. ***
*** Bug 655262 has been marked as a duplicate of this bug. ***
*** Bug 651841 has been marked as a duplicate of this bug. ***
*** Bug 649884 has been marked as a duplicate of this bug. ***
Package: glade3-3.7.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I try insert Frame icon (the 5th icon in section containers) in time of construction by Glade3 tutorial (2) - Constructing interface on http://tadeboro.blogspot.com/2009/09/glade3-tutorial-2-constructing.html 2. 3.
Since bug #649380 was closed as a duplicate of this, I will comment here :) This is from yesterday: 18:28 <tristan> yeah, I'm going to roll out a 3.7.2 by the end of the week from glade-3-8 branch 18:28 <tristan> hopefully with some of the worse bugs fixed Maybe it will work better without causing compatibility problems for people who have already upgraded their .glade files. Of course it won't be stable release, but since we're already on developer snapshots, maybe worth a try?
(In reply to comment #37) > Since bug #649380 was closed as a duplicate of this, I will comment here :) > > This is from yesterday: > > 18:28 <tristan> yeah, I'm going to roll out a 3.7.2 by the end of the week from > glade-3-8 branch > 18:28 <tristan> hopefully with some of the worse bugs fixed > > Maybe it will work better without causing compatibility problems for people who > have already upgraded their .glade files. > > Of course it won't be stable release, but since we're already on developer > snapshots, maybe worth a try? Yes, I noticed that. But we never know that that release will not also have something which breaks hell out, because it is a devel release. In other words I think we may get trapped into another issue of this kind because of this being odd numbered release. I am not a primary maintainer here but moving to odd numbered release was a mistake made earlier, even though that time we were in rawhide and never new about new scheduled stable release. We should revert back in my view for stable F14. For rawhide I will go with 3.7.2 once it is out.
(In reply to comment #38) > We should revert back in my view for stable F14. For rawhide I will go with > 3.7.2 once it is out. We have to be careful with this because if 3.8.0 is not planned by F15 then we're gonna end up in the same situation in F15 (ie: having the unstable version).
Not really sure which way to go... However glade is essentially useless for me and I kinda need it at the moment. Should I try to build the F13 version for F14, or the unstable version for F14?
so I built the f13 version for f14... works fine.
Package: glade3-3.7.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Add menu bar in vertical box 2.crash 3.
(In reply to comment #39) > (In reply to comment #38) > > We should revert back in my view for stable F14. For rawhide I will go with > > 3.7.2 once it is out. > > We have to be careful with this because if 3.8.0 is not planned by F15 then > we're gonna end up in the same situation in F15 (ie: having the unstable > version). Because mistake has already been done and F15 release cycle has some time still left. I will postphone reverting back on rawhide. May be a month more. I will anyway need to use epoch for rawhide to keep upgrade path working before F15 gets out (even before freeze).
Tagging has been done. Things to do: a) Epoch on rawhide, but don't revert back now.( to keep upgrade working). b) Build dependencies for fedora stable 14 c) Test them and push update to bodhi and keep it in update-testing for good time. (This will need everyone help - testing) d) And push once testing done, unless issues need to be fixed.
Umm glade3-3.6.7-1.fc14 had a mistake. Fixed and rebuild. Will have to request for retag, wait and then move on to build. http://koji.fedoraproject.org/koji/buildinfo?buildID=211766 /rakesh
(In reply to comment #44) > Tagging has been done. > > Things to do: > a) Epoch on rawhide, but don't revert back now.( to keep upgrade working). If you use epoch on rawhide while keeping 3.7.* you won't be able to revert to 3.6.* unless you increase the epoch. It is a solution but I am not sure whether this has other consequences or not.
(In reply to comment #46) > (In reply to comment #44) > > Tagging has been done. > > > > Things to do: > > a) Epoch on rawhide, but don't revert back now.( to keep upgrade working). > > If you use epoch on rawhide while keeping 3.7.* you won't be able to revert to > 3.6.* unless you increase the epoch. It is a solution but I am not sure whether > this has other consequences or not. Yes. I haven't pushed anything on rawhide. I will confirm with upstream about their schedule and then decide. Will inform here as well before moving on with that.
Package: glade3-3.7.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.happens at boot 2. 3.
(In reply to comment #39) > (In reply to comment #38) > > We should revert back in my view for stable F14. For rawhide I will go with > > 3.7.2 once it is out. > > We have to be careful with this because if 3.8.0 is not planned by F15 then > we're gonna end up in the same situation in F15 (ie: having the unstable > version). 3.8 and 3.10 will be available in time for F15 <jjardon> tristan|afk, Do you know the schelude for 3.10? Do you plan it for GNOME 3.0? <tristan|afk> I plan it for GTK+ 3.0 ... <tristan|afk> I'm trying to follow GTK+ 3.0 schedule, I'll /try/ <jjardon> oh, ok. GNOME 3 is scheluded for April, I think <tristan|afk> yeah should be good for april
Package: glade3-3.7.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.- 2. 3.
Package: glade3-3.7.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Create toplevel GtkWindow 2. Add 4-slot VBox 3. Add GtkMenuBar to the first slot of the VBox 4. Crash
Package: glade3-3.7.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Tried to undo an improperly removed vbox slot.
Package: glade3-3.7.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. using glade interface designer - click on Toplevels->Assistant 2. that's it. 3.
Package: glade3-3.7.1-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. run glade 2. create a window 3. try to place the "notebook" container on the window A crash occurs. Comment ----- The bug is reproducible
(In reply to comment #49) > (In reply to comment #39) > > (In reply to comment #38) > > > We should revert back in my view for stable F14. For rawhide I will go with > > > 3.7.2 once it is out. > > > > We have to be careful with this because if 3.8.0 is not planned by F15 then > > we're gonna end up in the same situation in F15 (ie: having the unstable > > version). > > 3.8 and 3.10 will be available in time for F15 > > <jjardon> tristan|afk, Do you know the schelude for 3.10? Do you plan it for > GNOME 3.0? > <tristan|afk> I plan it for GTK+ 3.0 > ... > <tristan|afk> I'm trying to follow GTK+ 3.0 schedule, I'll /try/ > <jjardon> oh, ok. GNOME 3 is scheluded for April, I think > <tristan|afk> yeah should be good for april Thanks for input. Holidays kept me away from computers. Now I am ready to push update to testing. I will add epoch to current build in rawhide and wait another month before deciding whether we want to revert back (in case stable release does not happen, with increment to epoch AGAIN) or we update to stable. /rakesh
libxfcegui4-4.6.4-4.fc14,libxfce4ui-4.7.2-3.fc14,gtkdatabox-0.9.1.1-4.fc14.2,gnome-media-2.32.0-2.fc14,anjuta-2.32.1.1-1.fc14,glade3-3.6.7-2.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/libxfcegui4-4.6.4-4.fc14,libxfce4ui-4.7.2-3.fc14,gtkdatabox-0.9.1.1-4.fc14.2,gnome-media-2.32.0-2.fc14,anjuta-2.32.1.1-1.fc14,glade3-3.6.7-2.fc14
libxfcegui4-4.6.4-4.fc14, libxfce4ui-4.7.2-3.fc14, gtkdatabox-0.9.1.1-4.fc14.2, gnome-media-2.32.0-2.fc14, anjuta-2.32.1.1-1.fc14, glade3-3.6.7-2.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update libxfcegui4 libxfce4ui gtkdatabox gnome-media anjuta glade3'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/libxfcegui4-4.6.4-4.fc14,libxfce4ui-4.7.2-3.fc14,gtkdatabox-0.9.1.1-4.fc14.2,gnome-media-2.32.0-2.fc14,anjuta-2.32.1.1-1.fc14,glade3-3.6.7-2.fc14
there are impossible for me to make su -c 'yum --enablerepo=updates-testing update libxfcegui4 libxfce4ui gtkdatabox gnome-media anjuta glade3' (it wrote, the packages are not installed) I had to change update to install. Before and after restart the computer, crashed glade in time to add the icon frame to the window of GTK-builder. It looks like the same, before su -c 'yum --enablerepo=updates-testing install libxfcegui4 libxfce4ui gtkdatabox gnome-media anjuta glade3'
(In reply to comment #58) > there are impossible for me to make su -c 'yum --enablerepo=updates-testing > update libxfcegui4 libxfce4ui gtkdatabox gnome-media anjuta glade3' > (it wrote, the packages are not installed) > I had to change update to install. Before and after restart the computer, > crashed glade in time to add the icon frame to the window of GTK-builder. It > looks like the same, before su -c 'yum --enablerepo=updates-testing install > libxfcegui4 libxfce4ui gtkdatabox gnome-media anjuta glade3' Thanks for looking into it, I will check if anything went wrong.
Package: glade3-3.7.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Create a window 2. Add a vertical box with 3 elements 3. Add an element to the vertical box making it a 4 elements VBox 4. Add a menu bar to the window 5; End of the story
(In reply to comment #58) > there are impossible for me to make su -c 'yum --enablerepo=updates-testing > update libxfcegui4 libxfce4ui gtkdatabox gnome-media anjuta glade3' > (it wrote, the packages are not installed) > I had to change update to install. Before and after restart the computer, > crashed glade in time to add the icon frame to the window of GTK-builder. It > looks like the same, before su -c 'yum --enablerepo=updates-testing install > libxfcegui4 libxfce4ui gtkdatabox gnome-media anjuta glade3' As you have already installed all packages. Try this now su -c 'yum --enablerepo=updates-testing update libxfcegui4 libxfce4ui gtkdatabox gnome-media anjuta glade3' It should pull following packages: libxfcegui4-4.6.4-4.fc14.x86_64 libxfce4ui-4.7.2-3.fc14.x86_64 gtkdatabox-0.9.1.1-4.fc14.2.x86_64 gnome-media-2.32.0-2.fc14.x86_64 anjuta-2.32.1.1-1.fc14.x86_64 glade3-3.6.7-2.fc14.x86_64 After running above command, you can cross check with: rpm -q libxfcegui4 libxfce4ui gtkdatabox gnome-media anjuta glade3 or you can watch the yum output. It worked for me, after waiting for some hours as my mirror took some time to refresh package set. May be earlier you tried it too soon. Try now. Regards, Rakesh Pandit
I had no installed packages gtkdatabox, anjuta. After install them (and ~40 dependencies) with yum install looks glade OK. Thanks.
(In reply to comment #62) > I had no installed packages gtkdatabox, anjuta. After install them (and ~40 > dependencies) with yum install looks glade OK. Thanks. Yes, then 'yum --enablerepo=updates-testing install libxfcegui4 libxfce4ui gtkdatabox gnome-media anjuta glade3' was appropriate. Thanks, As you are on it, can you give some karma over here as well: https://admin.fedoraproject.org/updates/libxfcegui4-4.6.4-4.fc14,libxfce4ui-4.7.2-3.fc14,gtkdatabox-0.9.1.1-4.fc14.2,gnome-media-2.32.0-2.fc14,anjuta-2.32.1.1-1.fc14,glade3-3.6.7-2.fc14 regards, rakesh pandit
Package: glade3-3.7.1-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Start Glade 2. Create a top-level window 3. Try to place a Menu container inside of window
Package: glade3-3.7.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Open an existing Glade file 2. Copy or cut a widget from Inspector 3. Paste the widget into another widget
Package: glade3-3.7.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Open an existing file 2. Go to Edit -> Preferences 3. Change "Object names are unique" from "within the project" to "inside toplevels"
libxfcegui4-4.6.4-4.fc14, libxfce4ui-4.7.2-3.fc14, gtkdatabox-0.9.1.1-4.fc14.2, gnome-media-2.32.0-2.fc14, anjuta-2.32.1.1-1.fc14, glade3-3.6.7-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.