Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[wuischke]

Unfortunately I cannot say a lot about the problem. I does not work with wxGTK without debug (there's no change when loading a skin) and with debug enabled there were the backtraces as they are seen in the attachment.

I haven't figured out what is wrong, one skin was sometimes working, but not every time I tried to set it, none of the others.

Happened with Ubuntu 6.10, wxGTK 2.8.0 yesterday's CVS.

I did a fresh a install on a newly set up Arch Linux machine with wxGTK 2.8.0 and today's CVS and wasn't abled to enable any skins either.

Is there someone out there using skins with recent CVS without having problems?
What system do you use? (wx, amule-versions)

[phoenix]

Hi wuischke,

I am using Yopo's icons here with the latest CVS. The backtraces you posted imply that somehow aMule thinks it loaded the icon files, but in fact, it didn't. It would be nice if we could track this down. Can you post your icon file here? Also, post the section [SkinGUIOptions] of amule.conf. Are you using absolute paths in it?

[Yopo]

I recently also had very strange problems when loading the skins.

After changing some versions of a skin they began to fail while they worked fine before without being modified in the meantime ?(. Sometimes one or two icons and sometimes the whole skin.

With me it also happened with a fresh CVS.

But after fiddling around and in the meantime using absolute paths and ./ paths they work fine now . Although I think at first it also failed, so there is something strange going on...

[Yopo]

The backtraces you posted imply that somehow aMule thinks it loaded the icon files, but in fact, it didn't.

Hey, it seems you're on track with something here...

I heard in the other post that you and wuischke also had succes with the absolute paths  and ~/ and ./. But still strange that it failed before.

Do you have an idea why amule got confused?

[phoenix]

Yopo,

Please read my previous post. As I said before, there is no guaranty that it will work if you use relative paths. It may or may not work, it will depend upon the starting directory. So, repeating myself, yes, it sucks. But to solve the issue, there must be an agreement about relative to what these paths will be. I propose something like ~/.aMule/skins, but I am open to discussion.

Anyway, you should discuss. I am going on vacations tomorrow, and will only be back in february.

Cheers!

[Yopo]

OK, have a nice vacation, cya

[Yopo]

Ahh... started amule-cvs today again.....no skin anymore (only the default again). And this was while using the new version: 'amule-skin_yopo'. While it did work yesterday. I've now changed the paths to absolute paths again and the skin worked again. It only has the drawback that the user has to replace 'user' with his own username. Or do you think you can solve this with the plan you'll work on next week wuischke?

Do you also have a problem now with the new skin again? Because I'm thinking about replacing the attachment with a version with absolute paths specified, with a comment that 'user' in the paths has to be replaced by the username.

[wuischke]

You can replace /home/user/ by ~/ , this should be safe working. (I think...)

[Yopo]

At first I was using ./ which was working fine, untill it failed and the first thing I tried was changing the path to ~/ then, but this also failed. Untill I used /home/user/... and only untill then the skin started working again.

Now the strange thing is that after using the absolute path again, the ./ and ~/ paths also work again. So like  phoenix said, I think only the absolute paths will work 100% of the time.

You also had the problem until you used an absolute path again didn't you? Has this happened again in the meantime?