wxWidgets

We should still have a fix for 2.6 (for a 2.6.4 release).
Reopening, though I vaguely recall there being another similar bug
report.
At one point I was dealing with this after amule devs asking me to take a
look on IRC, but I don't think I had a fix that didn't involve
restructuring GtkNotebook to not use an internal page indexing instead of
relying on gtk's.

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

This surely is a bug in wxWidgets and I also believe it has been fixed in
the upcoming 2.8 release.

hi vadz,

Yes, sorry if it was confusing but that's exactly what's happening:
GetSelection() is returning 3 even when there are only 3 pages. And no, I
haven't been able to test it with v2.8, sorry.

What I was also trying to comment is that using the same version
(v2.6.3.2) under Windows things work perfectly, so I think the bug is
related to GTK library and not wxWidgets itself.

Hope this clarifies

Unfortunately I don't quite understand the bug report as I don't
understand what does it mean that page D becomes index 2 (or 3) -- do you
mean GetSelection() still returns 3 even when there are only 3 pages left
or something else? In any case, I don't think it's the same bug as the
original report as the crash there was deep inside wxGTK and not related to
any "confusion" at the application level I think.

And, sorry to keep repeating it all the time, but are you testing with
2.8.0rc1 or not?

I think I reproduced the issue with some other project of mine. Here are
the steps in pseudo-code:

* Create a new wxNotebook
* Add page A to it. It becomes index 0 as returned by GetSelection()
* Add page B to it. It becomes index 1 as returned by GetSelection()
* Add page C to it. It becomes index 2 as returned by GetSelection()
* Add page D to it. It becomes index 3 as returned by GetSelection()

Then, if you delete page C (index 2), in older releases page D became
index 2, but in latest release it's still index 3. So programs that rely on
page indexes get confused, like aMule and some others.

I presume it's a GTK problem, though I've tested it using wxGTK

Hope this helps

i think we should do tests from older releases to the last, and when it
begins to crash, that's a problem in this release... that isnt corrected
yet

I can't compile amule with 2.8 RC1. Amule only work with 2.6

MuleGifCtrl.cpp:131: error: ‘class wxGIFDecoder’ has no member named
‘GetLogicalScreenWidth’
MuleGifCtrl.cpp:132: error: ‘class wxGIFDecoder’ has no member named
‘GetLogicalScreenHeight’
MuleGifCtrl.cpp:136: error: ‘class wxGIFDecoder’ has no member named
‘GetLeft’
MuleGifCtrl.cpp:136: error: ‘class wxGIFDecoder’ has no member named
‘GetTop’
make[2]: *** [libmuleappgui_a-MuleGifCtrl.o] Error 1
make[2]: se sale del directorio `/home/tasadar/amule-cvs/src'
make[1]: *** [install-recursive] Error 1
make[1]: se sale del directorio `/home/tasadar/amule-cvs/src'
make: *** [install-recursive] Error 1

Again, the important question is whether it still happens with 2.8.0rc1 --
does it?

In my amule, it crashes, when i close search tabs, when i close a private
message, when i close the comments window, in all of buttons that close any
menu

Logged In: YES
user_id=71618

The important question is if it still happens with current
cvs (soon to be released as 2.8.0). Can anyone please test this?

Logged In: YES
user_id=1433570

More information Mandriva:

http://qa.mandriva.com/show_bug.cgi?id=23691

Logged In: YES
user_id=1433570

I reproduce with Amaya in Ubuntu edgy. Error appear in
console when I close a Tab but amaya don't crash.

(amaya:13903): Gtk-CRITICAL **: gtk_widget_set_colormap:
assertion `!GTK_WIDGET_REALIZED (widget)' failed

(amaya:13903): Gtk-CRITICAL **: gtk_container_remove:
assertion `GTK_IS_TOOLBAR (container) || widget->parent ==
GTK_WIDGET (container)' failed

Logged In: YES
user_id=77100

I think this is a dup of a wxNotebook tab removal/closure
bug and it should be fixed already.

Logged In: YES
user_id=1632144

This bug is also forwarded to amule bug tracking system.
I think the main reason why this bug is forwarded here is
comments from JoseStefan:
"
I have installed aMule (dapper) in edgy for testing. aMule
(dapper) did not crash in dapper, so I though it was worth
testing.

As a result, aMule (dapper) will crash in edgy in just the
same way. I don't know how to provide in-depth crash
analysis so that is all I can offer for now. But this could
mean the bug lies on another package (like wxwidgets2.6)
"

Logged In: YES
user_id=71618

Unfortunately the 3 stack traces I looked at don't seem to
be that helpful -- all I can see is that it crashes in
wxNotebook dtor and this surely happens because the notebook
pointer itself (i.e. "this") is invalid and this means that
the bug is due to something which happens concurrently with
closing/destroying the notebook in aMule but I have no idea
what.

Why did boong write (in Ubuntu bugzilla) that it was wxGTK
bug, can we reproduce it somehow (without using aMule)?