aMule Forum
English => en_Bugs => Topic started by: Guest on November 15, 2003, 06:03:54 PM
-
hello, just compiled amule 1.1.2 (MDK 9.1-KDE) and noticed that vhen movin my mouse after the screen saver was started (about one hour before), the amule windows remained blank, no way to even exit...
now I disabled the screen saver and seems that this problem doesn't happen anymore...
could the screen saver hang amule?
-
correction: the problem exist also when I switch to another desktop and back again to the original containig the amule windows...
-
sometimes amule hangs randomly when i don't look at him.
but it's not predictable... if you really manage to reproduce it i suppose developers can't do anything about that
-
less than a second after i pressed the submit button, this pc rebooted. nice.
i suppose it's an amule bug ;) (lol)
-
HAHA
I had problems with this site too - crashed konqi... not anymore, I have absolutely NO idea why...
whatever....
-
Original von superstoned
HAHA
I had problems with this site too - crashed konqi... not anymore, I have absolutely NO idea why...
whatever....
A question :
Your wxGTK is linked to GTK2 or GTK1 ??
Bye
Marcello
-
in case you didnt understand: konqeror ("konqi") is my webbrowser, and it crashed on this site (forum).
and I think my amule is compiled, linking wxwindows against gtk1, cuz its the standard deb I installed...
-
Hi,
in case you didnt understand: konqeror ("konqi") is my webbrowser, and it crashed on this site (forum).
and I think my amule is compiled, linking wxwindows against gtk1, cuz its the standard deb I installed...
Better than thinking, here is a way to be sure :
bigbob@bigbobwks1:~$ ldd /usr/lib/libwx_gtk-2.4.so.0.1.1
libgtk-1.2.so.0 => /usr/lib/libgtk-1.2.so.0 (0x40498000) <- OHHH GREAT !!! linked with GTK1 ...
libgdk-1.2.so.0 => /usr/lib/libgdk-1.2.so.0 (0x405b7000)
libgmodule-1.2.so.0 => /usr/lib/libgmodule-1.2.so.0 (0x405e8000)
libgthread-1.2.so.0 => /usr/lib/libgthread-1.2.so.0 (0x405eb000)
libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0 (0x405ee000)
libpthread.so.0 => /lib/libpthread.so.0 (0x4060f000)
libdl.so.2 => /lib/libdl.so.2 (0x40661000)
libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x40665000)
libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40673000)
libpng.so.3 => /usr/lib/libpng.so.3 (0x4073a000)
libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x40764000)
libtiff.so.3 => /usr/lib/libtiff.so.3 (0x40781000)
libz.so.1 => /usr/lib/libz.so.1 (0x407c2000)
libm.so.6 => /lib/libm.so.6 (0x407d0000)
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x407f3000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x408a6000)
libc.so.6 => /lib/libc.so.6 (0x408ae000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
Hope it help on your side to be sure ...
A++
-
update...
it seems neither the screensaver nor the doesktop switch...
simply, after a couple of hours amule gets stuck.
No CPU activity, no IO...
It seems to me that as time passes aMule reactions to events (button clicks) gets slower an slower... until aMule doesn't react at all...
Anyway my pc seems not overloaded by anything, an if I switch to other applications they behave as usual...
btw:
$ ldd /usr/lib/libwx_gtk-2.4.so.0.1.1
libgtk-1.2.so.0 => /usr/lib/libgtk-1.2.so.0 (0x404a7000) <- seems OK.. correct?
libgdk-1.2.so.0 => /usr/lib/libgdk-1.2.so.0 (0x405f3000)
libgmodule-1.2.so.0 => /usr/lib/libgmodule-1.2.so.0 (0x4062c000)
libgthread-1.2.so.0 => /usr/lib/libgthread-1.2.so.0 (0x4062f000)
libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0 (0x40633000)
libpthread.so.0 => /lib/libpthread.so.0 (0x4065b000)
libdl.so.2 => /lib/libdl.so.2 (0x406ad000)
libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x406b0000)
libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x406b8000)
libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x406c6000)
libpng12.so.0 => /usr/lib/libpng12.so.0 (0x407a6000)
libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x407cb000)
libtiff.so.3 => /usr/lib/libtiff.so.3 (0x407ec000)
libz.so.1 => /lib/libz.so.1 (0x40831000)
libm.so.6 => /lib/libm.so.6 (0x40840000)
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x40862000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x40915000)
libc.so.6 => /lib/libc.so.6 (0x4091e000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
hope it helps
-
huh...
it seems someone still experienced my same problem before...
http://amule.sourceforge.net/phpBB2/viewtopic.php?t=144
-
try not using the 'hide' option on the systray... just keep it minimized on some desktop. I have seen it crash a alot when hidden, but just once when not...