aMule Forum
English => en_Bugs => Topic started by: MareviQ on April 11, 2004, 09:32:42 PM
-
whaere do I get the 2.0 rc1 ??
becouse it worked like a charm, and when i installed rc2 it crashes at the startup (I have Fedora Core 1, used RPM packages provided by you guys for everything ....) wx, wxbase, the libcrypto thingy and amule)
what I get is this:
I start amule
a little window pops out saying that i started it for the first time, reset preferences to default, y;kno - the usual stuff
and then:
Initialising aMule
Loading preferences from /home/mareviq/.aMule/preferences.ini
OOPS! - Seems like aMule crashed
--== BACKTRACE FOLLOWS: ==--
- amule(_ZN9CamuleApp16OnFatalExceptionEv+0x3c) [0x824a5d8]
[1] /usr/lib/libwx_gtk-2.4.so.0(wxFatalSignalHandler+0x26)
[0x42339082]
[2] /lib/tls/libpthread.so.0 [0x41793f18]
[3] amule(_ZN9CamuleApp6OnInitEv+0xc5e) [0x8246f02]
[4] /usr/lib/libwx_gtk-2.4.so.0(_Z7wxEntryiPPc+0x1f9) [0x421d41d1]
[5] amule(main+0x17) [0x82461af]
[6] /lib/tls/libc.so.6(__libc_start_main+0xf0) [0x41514750]
[7] amule(_ZN17wxGenericTreeCtrlC2EP8wxWindowiRK7wxPointRK6wxSizelRK11wxValidatorRK8wxString+0xa9) [0x8120791]
can't even SEE the gui for a second. just the info window an then the whole thing crashes
....
doesn't look good....
and i DID download the FC1 version
...
btw. sorry if i did any typos, i'm using a screen like 5-6 inches wide and can't really see what i'm typing
-
one more thing:
the wretched thing will start nicely and all, IF RUN AS ROOT ......
someone tell me: SHOULDN'T IT BE THE OTHER WAY ROUND??!!
-
Is an error in .aMule configurations files probably. remove the directory except the Temp and Incoming and run aMule again.
It's a bad solution but is efective I think...
-
welll... that's broadly true ....
when I read yorr post I experimented for a while and it turned out I had to delete the .eMule file in the home directory .....
lost most of the settings anyway, but saved the serverlist at least :)
-
ok, now i've even located WHICH wxact line gave me all the trouble
after lots of testing it turned out to be the line saying where to put the downloaded files. (I don't use nor the default incoming nor the default temp directory .... have different partitions to handle the task)
when amule was told to put the files in /mnt/eva-01/downloads/done (which is on a fat32 partition) it crashed ....
(i have over 100 files there, but they're all hashed already ....)
note: it doesn't crash when pointed to a directory on a ext3 partition .....
looks like some fat32 (or vfat in general) handling code should be added
-
i have the same problem with aMule using a fat32 partition
amule
Initialising aMule
Loading preferences from /home/argo/.aMule/preferences.ini
OOPS! - Seems like aMule crashed
--== BACKTRACE FOLLOWS: ==--
- amule(_ZN9CamuleApp16OnFatalExceptionEv+0x40) [0x81fff50]
[1] /lib/tls/libpthread.so.0
[0x40f69218]
[2] [0xfb]
Aborted (core dumped)
does anyone know where to get the previous version? the latest stable version doesn't work too well for me :( ... :( ... ;( snif snif
-
well, i've made it work for me this way:
1) delete the .eMule file from home dir
2) remove the incoming and temp directories from .aMule if you aren't using them (like me)
3) make links pointing to the directories where you have incoming and temporary files in your .aMule dir
4) run aMule and if you get any message saying something like "impossible to set permissions for the file 'blahblah/anotherblah/thefileandmoreblah' (error 1: operation not permitted)" just ignore them (but if you find anything about this let me know please)
5) enjoy
the only thing you can't do this way is making backups of .part.met
-
That'll be surely an important walkaround for rc2, since there are lots of fat32 users under aMule :-)
Very much thanks. This post will surely have very much views while rc2 is the latest release ;-)
Again, thank you very much for this walkaround.
Lots of greetings!
-
you can get rc1 there
http://developer.berlios.de/project/showfiles.php?group_id=1296
-
Originally posted by k-teto
well, i've made it work for me this way:
1) delete the .eMule file from home dir
2) remove the incoming and temp directories from .aMule if you aren't using them (like me)
3) make links pointing to the directories where you have incoming and temporary files in your .aMule dir
4) run aMule and if you get any message saying something like "impossible to set permissions for the file 'blahblah/anotherblah/thefileandmoreblah' (error 1: operation not permitted)" just ignore them (but if you find anything about this let me know please)
5) enjoy
the only thing you can't do this way is making backups of .part.met
I had the permissions problem on a FAT32 partition when using previous versions of xmule/amule, but it was all solved just by mounting my FAT32 partition with the 'quiet' option. Just add it at the end of your /etc/fstab file on the line used to mount the FAT32 partition and that should solve it.
Regards.
-
That will help _a lot_. Not only to users, but also to devs, since that explains the bug :-)
Thanx a lot lot lot!
Will be fixed in rc3 most surely.
Greetings.
-
Hi, I treid adding the quiet option to my /etc/fstab ... the specific line which mounts my emule incoming and temp parent partition is as follows:
/dev/hda5 /mnt/win_d vfat umask=0,quiet,iocharset=iso8859-1,codepage=850 0 0
I am still getting the permissions error ....
am using amule 2 rc2 ..
mandrake 10 community ....
its works fine ... otherthan being unable to save the .met .part file stuff ....
any suggestion ?
thanking in advance ...
-
I haven't tried the quiet walkaround posted by skolnick, but I guess you might skip the permission warning by defining the user and group who "owns" the files in that filesystem and the mask for those files. Take a look at "man mount" and scroll down to "Mount options for fat". You should take a close look at umask= gid= and uid= .
I guess that'll do BUT, as I said, that's just a guess.
Regards!
-
hmmm. In addition:
> /dev/hda5 /mnt/win_d vfat umask=0,quiet,iocharset=iso8859-1,codepage=850 0 0
Set umask= to 660 or something like that. umask as a mount option desn't work in the same way as the "umask" command. When you use the "umask" command, you set the permission which you do NOT want to be set to newly created files (comonly set in /etc/profile), but when you use "umask" as an option in mount (commonly in /etc/fstab) you set the permission which you DO want the files in that filesystem to have.
I hope that helped.
Remeber to answer how it did ;-)
Regards!
-
Hi,
I'm unable to start aMule. I've tried the workaround posted on this thread and created sym links to the folders on the FAT32 partition but still no luck. The backtrace follows. Any thoughts on this?
[0] amule(_ZN9CamuleApp16OnFatalExceptionEv+0x3c) [0x824a0f4]
[1] /usr/lib/libwx_gtk-2.4.so.0(wxFatalSignalHandler+0x2d) [0x403c1c7d]
[2] /lib/tls/libpthread.so.0 [0x40a278f8]
[3] /usr/lib/libwx_gtk-2.4.so.0(_ZN8wxString10AssignCopyEjPKc+0x6d) [0x4036dced][4] /usr/lib/libwx_gtk-2.4.so.0(_ZN8wxStringaSEPKc+0x3e) [0x4036de4e]
[5] /usr/lib/libwx_gtk-2.4.so.0(_ZN12wxHtmlWindow4InitEv+0xd1) [0x403e5131]
[6] amule(_ZN10CServerWndC1EP8wxWindow+0x134) [0x821dfd0]
[7] amule(_ZN9CamuleDlgC1EP8wxWindow8wxString+0x287) [0x824b7d3]
[8] amule(_ZN9CamuleApp6OnInitEv+0xcf5) [0x8246961]
[9] /usr/lib/libwx_gtk-2.4.so.0(_Z7wxEntryiPPc+0x228) [0x4023f468]
[10] amule(main+0x17) [0x8245b77]
[11] /lib/tls/libc.so.6(__libc_start_main+0xe4) [0x42015704]
[12] amule(_ZN18wxBaseArrayPtrVoidD2Ev+0x31) [0x8122cf1]
Aborted
-
patch your amule to solve the fat32 problems plz -> http://www.amule.org/amule/thread.php?threadid=1683&boardid=8&sid=
-
Still won't start. :(
I've upgraded to aMule-2.0.0-rc2-2.i686-RH_9.0.rpm on RH9 and I get the same exact backtrace...
Any suggestions?
-=e0n=-
-
Maybe the rpm hasn't been updated :-/ No idea though.
Try compiling yourself, that way you'll surely have the fixed aMule v2-rc2 ;-)
Greetings.
-
Problem solved.
It was a wxBase, wxGTKdevel conflict.