aMule Forum
English => aMule Help => Topic started by: youpla on November 15, 2009, 10:10:42 PM
-
Hello all,
I just compiled aMule 2.2.6 from source on a Mandriva 2009 system and I'm having a problem starting it.
Running it from the command line, I see this:
Initializing aMule 2.2.6 using wxGTK 2.8.9
Checking if there is an instance already running...
No other instances are running
And that's it, it does not do anything else. It does not consume any CPU, it does not terminate.
I've left it at that for 10 minutes with no change.
I did not have any such problem with aMule 2.2.5
What do you think I should try?
Thanks for your help
-
Hi youpla, long time no see!
Could you please try to rename the aMule configuration directory (mv ~/.aMule ~/.aMule.bak) and try to start aMule again afterwards?
-
Hi youpla, long time no see!
Yeah, I know, got hooked on a few other projects ::)
Could you please try to rename the aMule configuration directory (mv ~/.aMule ~/.aMule.bak) and try to start aMule again afterwards?
I just tried that, it did not change anything.
The test involved these steps:
aMule (To be sure it starts in 2.2.5)
su
aMule-2.2.5> make uninstall
aMule-2.2.6> make install
exit
mv ~/.aMule ~/.aMule.bak
aMule
And there it just does as before.
Where should I start looking?
-
Mh, ok, let's look for a sign of her passage:
Does aMule 2.2.6 create a new ~/.aMule directory after you moved the old one? And when you use the tool ed2k to add a link, will aMule react on changes to the file ~/.aMule/ED2KLinks ?
Could you also try to run aMule as root and see if a) the warning message appears and b) the window shows as another user?
-
It does create the ~/.aMule directory and even touches it if it is already there (the date changes)
ed2k says it added the link to the queue, but it does not start aMule and it does not make the "waiting" one react.
And running as root does not change anything, it does the same behavior.
Back to 2.2.5 for now, but I'll try any other thing you might suggest
-
I suspect your build environment. Did you change anything since building 2.2.5?
You could try to rebuild 2.2.5 in your current environment - maybe it hangs too.
-
Hum, bugger, you are right.
But I did not change anything specifically. Granted, I applied the updates required by the system, but do not remember seeing anything build related.
What can I try next?
-
Could you please compare the output of ldd amule for the working and non-working executables?
-
Hum, I went too fast in the previous steps and I do not actually have a working executable for aMule, whatever the version.
This is entirely my fault here, so I'm pretty much on my own here, I guess.
Just in case, this is on an x64 system and the output of ldd for the non working 2.2.6 is this:
linux-vdso.so.1 => (0x00007fffd7d89000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f6659994000)
libbfd-2.19.51.0.2.20090204.so => /usr/lib64/libbfd-2.19.51.0.2.20090204.so (0x00007f6659695000)
libz.so.1 => /lib64/libz.so.1 (0x00007f6659480000)
libcryptopp.so.6 => /usr/lib64/libcryptopp.so.6 (0x00007f6658d81000)
libupnp.so.3 => /usr/lib64/libupnp.so.3 (0x00007f6658b60000)
libthreadutil.so.2 => /usr/lib64/libthreadutil.so.2 (0x00007f665895b000)
libixml.so.2 => /usr/lib64/libixml.so.2 (0x00007f6658751000)
libwx_gtk2u_adv-2.8.so.0 => /usr/lib64/libwx_gtk2u_adv-2.8.so.0 (0x00007f6658469000)
libwx_gtk2u_core-2.8.so.0 => /usr/lib64/libwx_gtk2u_core-2.8.so.0 (0x00007f6657e3f000)
libwx_baseu_net-2.8.so.0 => /usr/lib64/libwx_baseu_net-2.8.so.0 (0x00007f6657c0d000)
libwx_baseu-2.8.so.0 => /usr/lib64/libwx_baseu-2.8.so.0 (0x00007f66578a9000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f66575a0000)
libm.so.6 => /lib64/libm.so.6 (0x00007f665731c000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f6657106000)
libc.so.6 => /lib64/libc.so.6 (0x00007f6656da4000)
/lib64/ld-linux-x86-64.so.2 (0x00007f6659bb0000)
libgtk-x11-2.0.so.0 => /usr/lib64/libgtk-x11-2.0.so.0 (0x00007f66567bb000)
libgdk-x11-2.0.so.0 => /usr/lib64/libgdk-x11-2.0.so.0 (0x00007f665651b000)
libgdk_pixbuf-2.0.so.0 => /usr/lib64/libgdk_pixbuf-2.0.so.0 (0x00007f6656300000)
libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007f66560bc000)
libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f6655df9000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f6655a80000)
libSDL-1.2.so.0 => /usr/lib64/libSDL-1.2.so.0 (0x00007f66557cb000)
libpango-1.0.so.0 => /usr/lib64/libpango-1.0.so.0 (0x00007f6655582000)
libgthread-2.0.so.0 => /usr/lib64/libgthread-2.0.so.0 (0x00007f665537d000)
libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x00007f665517b000)
libXxf86vm.so.1 => /usr/lib64/libXxf86vm.so.1 (0x00007f6654f76000)
libSM.so.6 => /usr/lib64/libSM.so.6 (0x00007f6654d6d000)
libpng12.so.0 => /usr/lib64/libpng12.so.0 (0x00007f6654b44000)
libjpeg.so.62 => /usr/lib64/libjpeg.so.62 (0x00007f6654921000)
libtiff.so.3 => /usr/lib64/libtiff.so.3 (0x00007f66546c5000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f66544c1000)
libpangocairo-1.0.so.0 => /usr/lib64/libpangocairo-1.0.so.0 (0x00007f66542b5000)
libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007f66540b0000)
libatk-1.0.so.0 => /usr/lib64/libatk-1.0.so.0 (0x00007f6653e90000)
libcairo.so.2 => /usr/lib64/libcairo.so.2 (0x00007f6653c19000)
libgio-2.0.so.0 => /usr/lib64/libgio-2.0.so.0 (0x00007f665399f000)
libpangoft2-1.0.so.0 => /usr/lib64/libpangoft2-1.0.so.0 (0x00007f6653772000)
libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007f6653541000)
libgmodule-2.0.so.0 => /usr/lib64/libgmodule-2.0.so.0 (0x00007f665333d000)
libXi.so.6 => /usr/lib64/libXi.so.6 (0x00007f6653133000)
libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x00007f6652f2a000)
libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00007f6652d20000)
libXcomposite.so.1 => /usr/lib64/libXcomposite.so.1 (0x00007f6652b1e000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007f665290c000)
libXdamage.so.1 => /usr/lib64/libXdamage.so.1 (0x00007f665270a000)
libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007f6652501000)
libpcre.so.0 => /lib64/libpcre.so.0 (0x00007f66522d1000)
libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f66520b5000)
libaudio.so.2 => /usr/lib64/libaudio.so.2 (0x00007f6651e9d000)
libdirectfb-1.2.so.0 => /usr/lib64/libdirectfb-1.2.so.0 (0x00007f6651c1b000)
libggi.so.2 => /usr/lib64/libggi.so.2 (0x00007f665197e000)
libaa.so.1 => /usr/lib64/libaa.so.1 (0x00007f6651761000)
librt.so.1 => /lib64/librt.so.1 (0x00007f6651558000)
libICE.so.6 => /usr/lib64/libICE.so.6 (0x00007f665133c000)
libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007f66510b6000)
libpixman-1.so.0 => /usr/lib64/libpixman-1.so.0 (0x00007f6650e70000)
libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x00007f6650b14000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f6650911000)
libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007f665070b000)
libXt.so.6 => /usr/lib64/libXt.so.6 (0x00007f66504a7000)
libfusion-1.2.so.0 => /usr/lib64/libfusion-1.2.so.0 (0x00007f665029d000)
libdirect-1.2.so.0 => /usr/lib64/libdirect-1.2.so.0 (0x00007f6650085000)
libncurses.so.5 => /lib64/libncurses.so.5 (0x00007f664fe33000)
libXxf86dga.so.1 => /usr/lib64/libXxf86dga.so.1 (0x00007f664fc2d000)
libgii.so.1 => /usr/lib64/libgii.so.1 (0x00007f664fa0d000)
libgg.so.1 => /usr/lib64/libgg.so.1 (0x00007f664f802000)
libslang.so.2 => /usr/lib64/libslang.so.2 (0x00007f664f4b0000)
-
Does aMule 2.2.x from the Mandriva repos work?
-
Well, thing is, it's not in any compiled form in the official Mandriva repos.
I did download the binary built by OldFrog for 2.2.5 but it does not even start because it cannot find an shared library. Actually, I should have known better because it was compiled for i586 when I have a x86_64 system.
I also tried downloading the source rpm mentioned on the same topic, but it does not compile even though urpmi said it's possible. It does not find xas.pl
I also tried the PLF source RPM mentioned on the same page, but urpmi gives me requirements that mean I would need to upgrade my entire system (going from 2009.1 to 2010.0).
It seems I'm stuck...
-
I went a bit further and edited amule.cpp to add new printf statements. This allowed me to discover that it's the call to ShowAlert that never returns inside Trigger_New_Version
So I went a bit further and removed the call to Trigger_New_Version to see if it would help.
And it actually does because I am now able to use aMule just like before.
It seems there is a problem with the ShowAlert call, but I'm not sure how to find more info about it.
-
It boils down to a wxMessageBox . If that doesn't work I'd expect you are bound to run into more problems.
I'm only a Windows user, but from what Linux threads I've been watching here the quickest way to get out of package trouble is to install the OS from scratch. It may well be that something breaks after many consecutive updates, packages added by hand, and so on. Full reinstall is much easier than on Windows actually, where you have to reinstall each app on its own, and usually lose its settings.
-
Well, I think I found what happens.
Basically, I noticed that when aMule starts, its main window does not show up but a taskbar button does. When I click on this button, it shows the main window.
So I tried running with the message box (as root for instance) and while amule stops apparently doing nothing, I minimized all windows to go back to the desktop. And sure enough, the message box is here showing and waiting for me to click on it.
But I did not notice it before because there is no taskbar button associated to it just like with the main window.
So the question really boils down to this:
Why doesn't it come up to the front of the screen and why isn't there a taskbar button when just the ShowAlert messages are displayed at the start?
-
Because there's no actual top level window created.
-
Why doesn't it come up to the front of the screen
Ha, and I always thought only Windows is that stupid. Welcome to the club. :)
There is no option "open message box in background" or such that we could use wrongly. It's just an annoying problem of the OS.
-
Well, I'm back with some news.
You mentioned that there must have been some updates that caused a problem, and you mentioned that it's an annoying problem of the OS.
There sure were some updates and I did not reboot after having applied them as I was not asked to by the system update.
But I tried rebooting the entire machine and the issue is now gone, the popup shows up in front and aMule main window shows in front as well.
In the end, there was no real bug and I thank you all for your help.
I at least hope this thread will help someone else facing the same problem in the future.