aMule Forum
English => Distro-Specific Packages => Packages for older versions => Topic started by: elfboi on January 05, 2006, 06:28:41 PM
-
I just ran my weekly apt-get update and apt-get upgrade, and now amule won't run anymore!
I get this line instead:
----
amule: error while loading shared libraries: libwx_gtk_xrc-2.6.so.0: cannot open shared object file: No such file or directory
----
This is my sources.list:
----
deb http://ftp.at.debian.org/debian/ sarge main contrib non-free
deb http://non-us.debian.org/debian-non-US sarge/non-US main contrib non-free
deb-src http://non-us.debian.org/debian-non-US sarge/non-US main contrib non-free
#
# Debian Security Updates
#
deb http://security.debian.org/ sarge/updates main contrib non-free
deb-src http://security.debian.org/ sarge/updates main contrib non-free
# non-free stuff
deb http://ftp://ftp.nerim.net/debian-marillat/ sarge main
# amule
deb http://amule-debian.dyndns.org/ debian/
----
What's wrong here? apt-get upgrade updated my libwxgtk2.6 and the other library that is used by the amule packages in amule-debian.dyndns.org, I don't recall the name of tha lib right now, and since then, amule has been broken. What can I do?
-
I just ran another apt-get update and got this error:
Konnte http://amule-debian.dyndns.org/debian/Packages.gz nicht holen 403 Forbidden
(Couldn't get http://amule-debian.dyndns.org/debian/Packages.gz 403 Forbidden)
Seems like there's something wrong with the repository...
-
i've the same problem...
in my /usr/lib i've libwx_gtk2u_xrc-2.6.so.0 against libwx_gtk_xrc-2.6.so.0 but i don't know what does it mean?!? ?(
-
Look in /var/cache/apt/archives/ for the file libwxbase2.6_2.6.2-1_i386.deb and install this again, it will replace the new version. amule will run fine after this, maybe until the next update :)
-
Thanks. I hope The Dude fixes the repository soon. I'm really looking forward to using aMule 2.1... with Kademlia, finally! I've been missing the Kad network ever since I switched from Windows to Linux...
Actually, I still use Windows on two of my machines (dual boot boxes, of course, one with Debian Sarge and Win98 SE, the other one with SuSE 10 and Win2k), but only for games and a few graphics related programs, like Poser and zBrush, and for some MIDI sequencing software. My third box is a modified XBox running Xebian 1.1.4 (Debian Sarge with some XBox-specific custom built packages and a special kernel), and that one is my web server, my living room media centre, and my aMule machine...
-
I installed the old version, but I still get this error:
amule: error while loading shared libraries: libwx_gtk_xrc-2.6.so.0: cannot open shared object file: No such file or directory
I think I also need to replace libwxgtk with the old version...
-
OK,replacing both libs with the old version works.
-
Ah, sorry, didn't check the forums earlier...
The background story is: I started upgrading my repository to amule 2.1.0 and switch wx to gtk2. After i was done with wx (and had it uploaded) my Debian machine broke down. AND I was told that my wx package is broken (which is correct). I've been on this the last few days (which is why I didn't have time for forums), the machine is up & running again and I investigate the wx problem right now. I took the repository offline so people don't bust their machines when trying to upgrade, I'll put it back online as soon as everything's resolved.
In addition to all this somebody who is very dear to me went through some very hard times lately which already kept me from sleeping two night this week, so my spare time is a little rare. Things are looking better now (I hope at least) and I'm starting to catch up with my repository & my sleep :)
-
Moved this thread to a little more appropriate forum.
As an update:
My Debian box is running again and I finally got wx to do as told (it was a very minor screwup with a symlink not being created that was needed). I even got amule to compile, added the amule-remote-gui package and everything worked beautifully. But when I tried running it all of the programs crash / segfault. Since it is 5 am here I#ll catch some sleep and investigate tomorrow ^^
-
Until thedude fixes its repository, if you want you can use the one of the Ubuntu debs for the 2.1.0.
I'm currently using it and it works fine.
-
Thanks Dude, for Your work on Sarge packages.
Which version is Your wxgtk package?
Is it patched against the unicode bug (http://forum.amule.org/thread.php?threadid=8415) ?
Offtopic, I'm just wondering where You sleep :D
Originally posted by thedude0001
...somebody...went through some very hard times lately which...kept me from sleeping...
-
It's 2.6.2, and thanks for reminding me of that patch, I definitely need to include that -.-
Originally posted by Arichy
Offtopic, I'm just wondering where You sleep :D
o.O It was not like "She kicked me out of my bed" but more like "She definitely needed me more than I needed my sleep" ^^
-
Originally posted by Mirko
Until thedude fixes its repository, if you want you can use the one of the Ubuntu debs for the 2.1.0.
I'm currently using it and it works fine.
How do you install those Ubuntu debs? I don't want any Ubuntu repositories in my /etc/apt/sources.list - so I guess I'll have to uninstall all the amule packages from The Dude, download all the Ubuntu debs, and install them by hand, using dpkg, which leads me to the following questions:
1. Which packages are needed? Which are optional?
2. In which order must they be installed?
-
Only one deb is needed.
I used the nodebug package from Wuischke: http://mitglied.lycos.de/wuischke.
-
As an workaround you can use my rep, too. I just finished the wx, so it is now the same as the ones on testing. Look in the amule-cvs section for the URL.
-
Ah, well. it was that stupid locale bug (completely forgot about it after it never hit me on my own box).
Good news: My repository is back online and seems to be working flawlessly, please report any problems here.
Bad news: I haven't slept all night (again) and won't be reading your problems before tomorrow (well, I might read them but I don't care any more today ^^ )
Changelog:
I added the (still experimental) remote gui amulegui in a package called amule-remote-gui. It's not complete, but useable for anybody who wants to play around with it.
-
Seems to work (at least amuled and amuleweb), great work. Thank you very much!
-
Nice to hear, you're welcome (and I hope the next upgrade runs a little more smoothly XD )
-
OK, 2.1.0 is up and running. It seeems to be less stable than 2.0.3, though. 2.0.3 crashed only once every two or three days, while 2.1.0 seems to be crashing at least once a day, no matter whether I use the monolithic or the daemon.
-
Repo and installation are working fine. Thank you!
But I also have one problem. After the update I could not login to the amule webserver anymore. It started fine but did not accept my password. Connecting with amulecmd worked as normal (although it sometimes reported an error: "Can not switch locales to de_DE").
I had to change the password for the webserver to be able to login again. After that, amulecmd didn't work anymore. It always tried to connect for a few seconds and then quit. While writing this, I've been able to connect with amulecmd again (I did not change anything!). I hope it works from now.
P.S.: I'm really missing the Kad-status in amuleweb. I can only tell from the logfile that kad is working. And I'm also missing the Up/Down status fields. I think they would both look really good when placed next to the "connection status" ;)
-
do you have a remote.conf file?
if not search the forum, this should fix teh password problems...
-
Yes I have one, but I think it isn't needed for amulecmd...
However, I found a much bigger problem meanwhile. When amule 2.1 is running, the internet connection is incredibly slow. In fact, it is unusable. I have to wait 2-3 minutes for google.com to load. Most other sites don't load at all. I had to shut amule down in order to come here.
With amule 2.0.3 I could even use skype when I set max upload to 9 (DSL 1000). If this problem cannot be solved, I have to go back to 2.0.3
any suggestions?
edit: there is another problem (not so bad as the first). amule often looses connection to the server and then it needs many retries to connect to an other server (can see this in the logfile). I've got only 13 servers in my met-file, the biggest ones, like razorback and donkey-server. They all worked fine with amule 2.0.3, it mostly reconnected only once a day...
-
Possibly (Kad enabled?) a router that can't deal with Kad. Once again: search forums, and please ask those questions in the general forum since they're not specific to my packages ^^
-
Sorry, I didn't mean to blame you !
I've just continued to write down the problems that occured after updating...
-
No offense taken, I just wanted to point out that the general help forum is the right place to post since I don't think that most devs will actually read these threads here ^^
-
Hello
I also updated from amuled 2.0.3 to 2.1 today and can not login per http.
I searched for what has changed and only found that ECUseTCPPort=1 is needed now in amule.conf. I added it, but it did not help.
So I started from scratch (rm amule.conf && rm remote.conf) and followed the wiki. Still it will not let me in. :(
I can't help myself here, because I don't get any error messages or something to work on the problem. Maybe someone could spare a minute to check my configs? :baby:
Here they are:
amule.conf (http://adrian.kicks-ass.net/stuff/amule.conf)
remote.conf (http://adrian.kicks-ass.net/stuff/remote.conf)
Thx for any help.
Adrian
-
Hi,
you have to specify a password in your amule.conf. Without it, you will never be able to login to amuleweb.
[WebServer]
Enabled=1
Password=xxx <--
I can't help myself here, because I don't get any error messages or something to work on the problem
I think that there is an error-message regarding the missing password. I had the same problem last time I installed amuled...
In your remote.conf you have to replace "123" with the ECPassword from your amule.conf (for the webserver being able to connect to amuled). The "AdminPassword" has to be the same like the one missing above.
Locale=
[EC]
Host=localhost
Port=4712
Password=123 <------
[Webserver]
Port=-1
Template=php-default
UseGzip=0
AllowGuest=0
AdminPassword=xxx <---------
GuestPassword=
-
One last word to my speed-problem:
I think I found the reason why it was so damn slow. It wasn't the enabled kad but the enabled "IPFilterAutoLoad". I don't know why the download of a 7MB file blocked the network for 3 hours, but since I've disabled it and rebooted, it behaves like it should. I hope that doesn't change again.
cu
-
Thanks for your replay,
I did what you suggestet, but still no connection ... ?(
I can't help myself here, because I don't get any error messages or something to work on the problem
I think that there is an error-message regarding the missing password. I had the same problem last time I installed amuled...
Where did you get this message? I start amuled not daemonized to see stdout, but nothing there. Mabye your remember a <2.0 version, because I could login on 2.0.3 without a password.
ADD: I just tried to use md5sums for the login passwords aswell. Nothing.
-
You always have to use md5 passwords...
I had that password problem with amule 2.0.3 (not CVS). I know that because I never used another version with sarge till yesterday. I don't know if this message still exists in 2.1, but I can remember that I wasn't able to even start amuleweb without a password. At least not automatically with amuled...
I suggest you open a new thread in the help forum (you can put a link to this one). I'm sure you will get some help pretty fast. And plz post your new .confs
good luck
-
Yuhoo, it works!
I was just typing the new post in amule help forum, and rereading the wiki. This time, I gave the notes section more attention removed the remote.conf, as "sugessted" in Note2. And there we go! (nice new frontend btw)
I still wonder about the no password for webserver thing, though. Im 100% sure, that I did not have to type a password on the loginscreen. Nor did I used a saved password by my browser. I know because I used to login from different PCs on our LAN.
Maybe I used the md5sum for space, which equals nothing.
echo -n | md5sum | cut -d ' ' -f 1
d41d8cd98f00b204e9800998ecf8427eBut this doesn't seem to work with 2.1 anymore.
I guess I will unzip my dd /dev/hda image and look for that config file. :D
Anyways, thanks for help and whising me good luck. <- That must have been it! ;)
-
You're welcome
And to confuse you just a little bit more: for me it works with exactly the same setup I recommended above. Even with the remote.conf (although I don't need it cause amuleweb is started automatically).
cu
-
Well, the fact that you could log into amuleweb without a password on 2.0.3 was a bug, not a feature. And as we try to do it with bugs it was killed ^^
-
Reminds me of that old MS joke: "It's a feature not a bug!" :)
But why must there be a password? My firewall doesn't allow any connections on port 4711, so its not insecure. On the other hand allowing a one letter password for internet connections is very insecure. (I'm asuming it works with only one letter, because my 4 letter password works, which is still quite insecure)
I'd say if amule wants to provide serious security it should allow only 6+ letter passwords, with numbers in it. (Don't know if this is even enough today. I am no crypto guy.)
But allow no passwords for people who don't need it.
To avoid out of the box, no password amule's out there waiting to get abused, one could add a NoPassword flag, which is by default disabled.
ADD:
Btw. In what file are amule's statistics stored? Mine are gone after the upgrade. Can I use a backup of an 2.0.3 file?
-
Well, that's a matter of opinion. The point was that amuleweb let the user login without password in it's default configuration. That should never happen as it is prone to cause some kind of desaster somewhere. We changed that behaviour so users need to set a password to be able to start amuleweb. Once the user is aware of that fact it can't be our responsibility to force n+ letter passwords on him with a cracklib check etc. THAT is a decision each user has to make for himself. We wanted to prevent *accidentially* running amuleweb without password.
amule stats are saven in ~/.aMule/amule.conf (along with all other configuration). It's safe to copy the statistics information into the new file after shutting down amule. It's also safe just to copy the whole file, though it will reset most of your preferences ^^
-
We wanted to prevent *accidentially* running amuleweb without password.
Sure I see your point.
But how about allowing NoPassword by flag or allowing the d41d8cd98f00b204e9800998ecf8427e md5sum. Is this hard to implement?
Do you have a bugtracking system so I can add this as a whislist? If this whish has any chances at all.
It would be quite nice in my environment.
-
We sure have a bugtracker at http://bugs.amule.org, you're welcome to add this wishlist item there. I don't think it should be too hard to implement, but then again I'm not much of a coder ^^