aMule Forum
English => en_Bugs => Topic started by: KotCzarny on October 17, 2008, 11:57:03 PM
-
that is, when i do some searches then close tabs one by one, closing last one (ie. the only one showing at that moment) crashes my amule. clicking on 'clear' closes all tabs without crashing.
observed in: 2.1.3, 2.2.2
os info: linux, wxgtk2 2.8.5 (but also observed with 2.6.x)
-
IIRC this was a bug in wxGTK. Update to the latest one and see if it happens still.
Regards.
-
I have the latest version of Ubuntu that was released October 31, 2008, and I still receive this error. The latest version of Ubuntu upgrades all software to the latest available rendition of the package.
-
I still get it here and my aMule and wxGTK are self compiled.
-
I've posted a back tracke in the forum, that covers this topic. I face this problem for a long time, using ubuntu.
http://forum.amule.org/index.php?topic=16254.0
-
Weird, I guess the issue is exclusive to ubuntu, since I use fedora and have not seen this issue in a very long time.
Regards.
-
It seems only to plague gnome users, which speaks against an aMule bug
-
Hello
I'm new at linux anda I started tu use Kubuntu 8.10.
I also have this problem. When I close the search tab, amule closes....
At the Ubuntu forums, they don't say nothing... Here you say it's a Ubuntu problem...
If I install a older version, can the problem be fixed?? When is the new version 2.2.3 gonna be released? I have to try it.
Thank You
-
It's been a while since the last time I got it. I think it has been fixed, at least in trunk.
-
Hi
What do you mean with "trunk"??
Sorry, but I'm a newbie ;D ;D ;D
-
Trunk is the current developmental version, i.e. what is going to be aMule 2.3.0.
The tab problem is a problem with Ubuntu's wxwidgets 2.8.8. raveboy solved this problem by compiling wxwidgets 2.8.9, see http://www.amule.org/amule/index.php?topic=16254.msg85842#msg85842
-
It seems only to plague gnome users, which speaks against an aMule bug
It seems not, because i use gnome under fedora and I don't have the bug. I remember it was related to wxGTK, but you are right that the bug is not amule's.
Regards.
-
Well, I don't know if this matters, but my aMule binary was compiled long time ago, while using wxGTK 2.8.7, on fedora 9. Now it runs on Fedora 10 without the issue, and always ran on F9 without the issue. However, the funny part is that aMule still reports that it's running on wxGTK 2.8.7, even though I know for sure it's using the system's wxGTK which is 2.8.9. Should I report a bug on that?
Regards.
-
Was wx maybe linked statically when it was built ?
-
Was wx maybe linked statically when it was built ?
I don't think so, stu, because the binary file still asks for wx libraries, and file says the binary is dinamically linked:
[root@hades /]# ldd /usr/local/bin/amule
linux-gate.so.1 => (0x00130000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00133000)
libz.so.1 => /lib/libz.so.1 (0x00b64000)
libupnp.so.3 => /usr/lib/libupnp.so.3 (0x0014d000)
libthreadutil.so.2 => /usr/lib/libthreadutil.so.2 (0x00172000)
libixml.so.2 => /usr/lib/libixml.so.2 (0x00178000)
libwx_gtk2u_adv-2.8.so.0 => /usr/lib/libwx_gtk2u_adv-2.8.so.0 (0x00184000)
libwx_gtk2u_core-2.8.so.0 => /usr/lib/libwx_gtk2u_core-2.8.so.0 (0x00243000)
libwx_baseu_net-2.8.so.0 => /usr/lib/libwx_baseu_net-2.8.so.0 (0x005a2000)
libwx_baseu-2.8.so.0 => /usr/lib/libwx_baseu-2.8.so.0 (0x005cf000)
libGeoIP.so.1 => /usr/lib/libGeoIP.so.1 (0x00728000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x0578b000)
libm.so.6 => /lib/libm.so.6 (0x00751000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x05470000)
libc.so.6 => /lib/libc.so.6 (0x0077a000)
/lib/ld-linux.so.2 (0x00110000)
libdl.so.2 => /lib/libdl.so.2 (0x008ee000)
libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x02e74000)
libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x07645000)
libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x008f3000)
libgio-2.0.so.0 => /lib/libgio-2.0.so.0 (0x00910000)
libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x00b98000)
libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x00983000)
libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x00bc4000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x009a0000)
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00a33000)
libgobject-2.0.so.0 => /lib/libgobject-2.0.so.0 (0x00a62000)
libgmodule-2.0.so.0 => /lib/libgmodule-2.0.so.0 (0x00aa3000)
libgthread-2.0.so.0 => /lib/libgthread-2.0.so.0 (0x00aa7000)
librt.so.1 => /lib/librt.so.1 (0x00aac000)
libglib-2.0.so.0 => /lib/libglib-2.0.so.0 (0x00c0a000)
libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0x00ab6000)
libSM.so.6 => /usr/lib/libSM.so.6 (0x05729000)
libpng12.so.0 => /usr/lib/libpng12.so.0 (0x00ab9000)
libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x051dd000)
libtiff.so.3 => /usr/lib/libtiff.so.3 (0x045b5000)
libSDL-1.2.so.0 => /usr/lib/libSDL-1.2.so.0 (0x00ced000)
libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0x00ae1000)
libX11.so.6 => /usr/lib/libX11.so.6 (0x00d90000)
libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0x00aec000)
libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0x00aef000)
libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x00af2000)
libcairo.so.2 => /usr/lib/libcairo.so.2 (0x00e91000)
libXext.so.6 => /usr/lib/libXext.so.6 (0x00af7000)
libXrender.so.1 => /usr/lib/libXrender.so.1 (0x00b07000)
libXi.so.6 => /usr/lib/libXi.so.6 (0x00b10000)
libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0x00b19000)
libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0x00b20000)
libselinux.so.1 => /lib/libselinux.so.1 (0x00b7a000)
libexpat.so.1 => /lib/libexpat.so.1 (0x00b2a000)
libICE.so.6 => /usr/lib/libICE.so.6 (0x05565000)
libuuid.so.1 => /lib/libuuid.so.1 (0x053e5000)
libxcb-xlib.so.0 => /usr/lib/libxcb-xlib.so.0 (0x00b51000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00f09000)
libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0x00f25000)
libXau.so.6 => /usr/lib/libXau.so.6 (0x00b53000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00b56000)
[root@hades /]# file /usr/local/bin/amule
/usr/local/bin/amule: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, stripped
[root@hades /]#
however, I do not have the configure line used to build my binary anymore.
Regards.
-
ver += wxString::Format(wxT(" v%d.%d.%d"), wxMAJOR_VERSION, wxMINOR_VERSION, wxRELEASE_NUMBER );
Version is set at compile time. Don't know if you can also determine the runtime dll version.
I don't have a good feeling if the runtime lib doesn't match the version of the headers the program was compiled with btw. Linking the Unix builds statically might solve a lot of the crash problems plagueing us.
-
I didn't think it would solve this crash, but probably the one with Ubuntu/Crypto++.
-
I'm actually thinking about providing a static build for Linux. Not to replace distro packages (unless they are buggy), but to help people with distros which don't provide a current aMule version.
-
Static linking is not needed unless the dynamic linked libraries broke the ABI/API in the new version, in which case their numbering scheme should be changed and the application wouldn't find the original one and won't launch.
So no, we won't static link things by default. Wuischke is still allowed to provide a static build, of course.After all, xmule did when they were still active, so what could possibly go wrong? :P
-
FYI, I also got this bug and I posted a new backtrace (see backtraces subforum for my backtrace with some debug info)
However I cannot reproduce it reliably.
By the way, I think blaming Ubuntu for this bug is wrong, people using Fedora 10 also got it. I inspected the wx patches they ship and they couldn't cause this bug. I'm not so sure about the GTK+ patches they ship, I'm investigating this point.
It could be a GTK+, WX or aMule bug, but I'm almost 100% sure this bug is not Ubuntu specific.