aMule Forum
English => aMule Help => Topic started by: hplus on February 27, 2006, 04:44:04 PM
-
Hello everybody,
i cannot login the web control interface when i connect from outside my network.
I have the login page, but after login, the 3 frames (header,main,footer) display the login page again...)
There is no problem from inside the network... what should i do?
Another problem, when i try the remote gui, from a windows OS, same version 2.10, i can connect , but there is only some information that are displayed, and the transfer panel is empty, and no search is possible.
thanks
Franky
-
You should clean cookies and disable firefox "accelerator" extensions.
Remote gui will have a problem to work over slow networks.
-
I'll try to clean my cookies.. i'll check this as soon as i am back home.
About the network speed, i am on a 80Kilobytes/sec line, its really enough!
You can send the entire bitmap of the gui over such a line... So i don't think this is the problem.
Maybe there a problem to connect from a window amulegui client to a linux amuled server?
did somebody tried?
thanks
-
Maybe there a problem to connect from a window amulegui client to a linux amuled server
Many tried and it's reported functional. I personly found win amulegui to be quite unstable. Do you have any errors printed on console and/or log(s) ?
i am on a 80Kilobytes/sec line, its really enough
Don't jump to conclusion before checking the facts. 640kbps line is not "really enough" - regular ethernet LAN have 100Mbps. Do you share this line with other application(s) or it's fully dedicated to amulegui while it's running ?
You can send the entire bitmap of the gui over such a line
Try to run X (or Windows remote desktop) over this line - and you will quickly understand that this is far from true.
-
Here are the logs
amulegui --verbose
(amulegui:5980): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer
(amulegui:5980): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(amulegui:5980): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `'
(amulegui:5980): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(amulegui:5980): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)'
(amulegui:5980): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(amulegui:5980): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)'
(amulegui:5980): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Connecting...
Going to event loop...
Remote GUI EC event handler
LOG: Succeeded! Connection established to aMule 2.1.0
Usage: aMule [-v] [-h] [-geometry ]
-v, --version Displays the current version number.
-h, --help Displays this information.
-geometry: Sets the geometry of the app.
uses the same format as standard X11 apps:
[=][{xX}][{+-}{+-}]
Unknown long option 'verbose'
LOG:
LOG: - This is aMule 2.1.0 using wxGTK2 v2.6.1 (Unicoded) based on eMule.
LOG: Running on Linux 2.6.12-12mdksmp i686
LOG: - Visit http://www.amule.org to check if a new version is available.
LOG:
(amulegui:5980): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer
(amulegui:5980): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Shutting down aMule...
aMule dialog destroyed
(amulegui:5980): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)'
(amulegui:5980): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
I tried from a linux machine this time, and there is the same problem.
the servers show up in the server tab, but transfer is empty and search is not functionnal...
-
Ok,
even on the localhost its the same problem,
the amuled doesn't complain about any connection problem with the gui...
Looks like the amulegui doesn't work for me on the v2.1....
By the way, cleaning the cookies solved my first problem. thanks,
-
(amulegui:5980): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer
(amulegui:5980): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(amulegui:5980): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `'
(amulegui:5980): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(amulegui:5980): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)'
(amulegui:5980): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(amulegui:5980): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)'
(amulegui:5980): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Looks like something in wx-gtk fucked up.
-
Maybe...
These messages don't appear when i switch between the tabs in the gui, in fact nothing shows up in the log when i interact with the gui.. These meassage are created when the gui is first displayed and when i close it. So i think its just some signals between the wx widget that causes the messages at building and destruction time of the gui.
Of course if there is some problem in the signals, slots can be unlinked and it can explain why
nothing shows up in some tabs. But how come i have the exact same behavior on 3 different machine: two different version of mandrake (2005 & 2006) and on a Windows Xp..
That makes me think there is a bug in the amulegui v2.1 source code.
regards
-
That makes me think there is a bug in the amulegui v2.1 source code.
Or in wx code. Or combination of wx and gtk you have.