Jacob Nevins
2013-08-05 22:30:35 UTC
I've also reproduced the crash with a build of the latest Freeciv
upstream code from this development branch (S2_3 r23154).
--
You received this bug notification because you are a member of
Debian/Ubuntu Games Team, which is subscribed to freeciv in Ubuntu.
https://bugs.launchpad.net/bugs/1208625
Title:
freeciv-gtk2 crashes under Unity when using menubar in cities report
Status in Freeciv Game:
New
Status in ?freeciv? package in Ubuntu:
New
Bug description:
(Filing against freeciv initially, but may turn out to be a bug in
appmenu-gtk or thereabouts.)
On Ubuntu 13.04 with Unity, running the supplied Freeciv (2.3.2-1),
using the menubar on the cities report (F4) -- not the individual city
dialog -- can cause the freeciv-gtk2 client to crash.
Originally noticed when changing production, but simply fiddling with the menubar will cause a crash sooner or later. Steps to reproduce:
1. Start new game
2. Found a city (select Settlers, press B)
3. Open cities report (F4) and select the new city
4. Repeatedly click on "Production" menu (bottom left), popping and unpopping it. Within about ten open/close cycles, the client crashes for me.
Friend reports that this did not used to happen with the same workflow
under Ubuntu 12.10 (which had the same version of Freeciv packaged) --
it seems to be new with 13.04.
There is some associated console spew:
Every time the Production menu is opened, we get three repeats of:
(freeciv-gtk2:2466): LIBDBUSMENU-GTK-CRITICAL **: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed
Additionally, at some point we get this when the Production menu is *closed*:
(freeciv-gtk2:2466): GLib-GObject-CRITICAL **: g_closure_unref: assertion `closure->ref_count > 0' failed
(freeciv-gtk2:2466): GLib-GObject-WARNING **: g_object_weak_unref: couldn't find weak ref 0x7fdbe02e4e40(0x9fd8058)
and if that is seen, the next time the Production menu is opened, the
client will crash.
I expect there are crash reports of this available on
errors.ubuntu.com, but I don't currently have access to that.
Backtraces I've seen have almost all frames in Gtk/dbusmenu/etc rather
than freeciv proper.
We've had trouble with Unity's menu-bar-stealing arrangements before
(bug #743265). Tellingly, I cannot reproduce the crash if I launch
Freeciv with "UBUNTU_MENUPROXY= freeciv-gtk2" (no crash in any of my
experiments, including 30 cycles).
As a result of the previous bug, this menu bar is decorated with the
property "ubuntu-local" to tell appmenu-gtk/dbusmenu/etc to keep their
hands off it. But the UBUNTU_MENUPROXY environment variable still
makes a difference, suggesting that it's not *completely* ignoring
this menubar. On the other hand, perhaps there's some bug in the way
we set up this menubar that appmenu is tickling -- it doesn't seem to
happen with any of the other "auxiliary" menubars (such as the Nations
report).
To manage notifications about this bug go to:
https://bugs.launchpad.net/freeciv/+bug/1208625/+subscriptions
upstream code from this development branch (S2_3 r23154).
--
You received this bug notification because you are a member of
Debian/Ubuntu Games Team, which is subscribed to freeciv in Ubuntu.
https://bugs.launchpad.net/bugs/1208625
Title:
freeciv-gtk2 crashes under Unity when using menubar in cities report
Status in Freeciv Game:
New
Status in ?freeciv? package in Ubuntu:
New
Bug description:
(Filing against freeciv initially, but may turn out to be a bug in
appmenu-gtk or thereabouts.)
On Ubuntu 13.04 with Unity, running the supplied Freeciv (2.3.2-1),
using the menubar on the cities report (F4) -- not the individual city
dialog -- can cause the freeciv-gtk2 client to crash.
Originally noticed when changing production, but simply fiddling with the menubar will cause a crash sooner or later. Steps to reproduce:
1. Start new game
2. Found a city (select Settlers, press B)
3. Open cities report (F4) and select the new city
4. Repeatedly click on "Production" menu (bottom left), popping and unpopping it. Within about ten open/close cycles, the client crashes for me.
Friend reports that this did not used to happen with the same workflow
under Ubuntu 12.10 (which had the same version of Freeciv packaged) --
it seems to be new with 13.04.
There is some associated console spew:
Every time the Production menu is opened, we get three repeats of:
(freeciv-gtk2:2466): LIBDBUSMENU-GTK-CRITICAL **: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed
Additionally, at some point we get this when the Production menu is *closed*:
(freeciv-gtk2:2466): GLib-GObject-CRITICAL **: g_closure_unref: assertion `closure->ref_count > 0' failed
(freeciv-gtk2:2466): GLib-GObject-WARNING **: g_object_weak_unref: couldn't find weak ref 0x7fdbe02e4e40(0x9fd8058)
and if that is seen, the next time the Production menu is opened, the
client will crash.
I expect there are crash reports of this available on
errors.ubuntu.com, but I don't currently have access to that.
Backtraces I've seen have almost all frames in Gtk/dbusmenu/etc rather
than freeciv proper.
We've had trouble with Unity's menu-bar-stealing arrangements before
(bug #743265). Tellingly, I cannot reproduce the crash if I launch
Freeciv with "UBUNTU_MENUPROXY= freeciv-gtk2" (no crash in any of my
experiments, including 30 cycles).
As a result of the previous bug, this menu bar is decorated with the
property "ubuntu-local" to tell appmenu-gtk/dbusmenu/etc to keep their
hands off it. But the UBUNTU_MENUPROXY environment variable still
makes a difference, suggesting that it's not *completely* ignoring
this menubar. On the other hand, perhaps there's some bug in the way
we set up this menubar that appmenu is tickling -- it doesn't seem to
happen with any of the other "auxiliary" menubars (such as the Nations
report).
To manage notifications about this bug go to:
https://bugs.launchpad.net/freeciv/+bug/1208625/+subscriptions