Closed GoogleCodeExporter closed 9 years ago
Same issue with Server 2003....
Original comment by robinlen...@gmail.com
on 31 Oct 2009 at 6:51
I have same promblem. This's message "vboxTabWidget::invalidatePage: Current
item is
undefined}."
Os : ubuntu 9.10
Virtualbox : 3.0.10
Original comment by iamlittl...@gmail.com
on 1 Nov 2009 at 3:43
I also have same problem. This's message "vboxTabWidget::invalidatePage:
Current item is
undefined}."
OS: FreeBSD 7.2 amd64
Virtualbox: 3.0.6
Original comment by mario.lo...@gmail.com
on 8 Nov 2009 at 5:31
Same ISSUE here,
This's message "vboxTabWidget::invalidatePage: Current item is
undefined}."
Os : ubuntu 9.10
Virtualbox : 3.0.10
Original comment by gabrie...@gmail.com
on 16 Nov 2009 at 5:40
same on 8.04 ubuntu, can see the vmachines.
Original comment by peer...@gmail.com
on 16 Nov 2009 at 11:35
> What steps will reproduce the problem?
1. Checkout sources to /opt/vboxweb on Ubuntu 9.10 karmic kernel
2.6.31-14-generic x86_64
2. # python VBoxWebSvr.py
3. Reconfigure port in VBoxWeb.conf to 8666, and environment="production"
4. browse to: hostname:8666
>W hat is the expected output?
A userinterface allowing me to manage VM's
> What do you see instead?
Something that looks like a page for testing the widgets. None of the links
work,
except for the "create new VM" menu link. Screenshot attached.
Clickin on a tab or menu item results in:
vboxTabWidget::invalidatePage: Current item is undefined.
> What version of the product are you using? On what operating system?
VBox 3.0.10
Ubuntu 9.10 karmic 2.6.31 x86_64
Original comment by gralgrat...@gmail.com
on 18 Nov 2009 at 5:34
Attachments:
Additional:
I upgraded my VBox install to 3.0.12, the x86_64 deb package downloaded from
virtualbox.org, but still the same result.
Any suggestions as to what I may be missing?
Original comment by hoozeman...@gmail.com
on 19 Nov 2009 at 12:15
Install shockwave player pls on your browser to view the menu, check the
VBoxWeb.conf
file ,look for the lines "tools.gzip.mine_type"
Original comment by clydease...@gmail.com
on 23 Dec 2009 at 1:01
Shockwave re-installed and still having the same issue....
Original comment by robinlen...@gmail.com
on 31 Dec 2009 at 1:01
Had the same issue. I was running vboxweb as root, but my virtual machines was
running
as other user. Running vboxweb as this user solved my problem.
Original comment by kafa...@gmail.com
on 15 Jan 2010 at 10:49
[deleted comment]
the same issue: "vboxTabWidget::invalidatePage: Current item is undefined."
don't see VB machines
OS: Windows 2003 server
python 2.6
please advise
Original comment by dnepochi...@gmail.com
on 27 Mar 2010 at 5:28
Does anyone have a workaround on the mentioned issue?
Please help
Original comment by dnepochi...@gmail.com
on 28 Mar 2010 at 8:34
I'm getting this in VBoxWeb.log
File "/opt/vboxweb/vboxweb-read-only/cherrypy/_cpdispatch.py", line 25, in
__call__
return self.callable(*self.args, **self.kwargs)
File "VBoxWebSrv.py", line 407, in vboxGetUpdates
arrJSON.append(jsMachine(self.ctx, machine))
File "VBoxWebSrv.py", line 181, in __init__
self.HWVirtExEnabled =
machine.getHWVirtExProperty(ctx['global'].constants.HWVirtExPropertyType_Enabled
)
File "/usr/lib/virtualbox-ose/sdk/bindings/xpcom/python/xpcom/client/__init__.py",
line 384, in __getattr__
raise AttributeError, "XPCOM component '%s' has no attribute '%s'" %
(self._object_name_, attr)
AttributeError: XPCOM component '<unknown>' has no attribute
'getHWVirtExProperty'
VirtualBox-ose 3.0.12
Original comment by pandagr...@googlemail.com
on 28 Mar 2010 at 10:00
Same problem here.
When I click any of the buttons, I get the error:
vboxTabWidget::invalidatePage: Current item is undefined.
OS: Ubuntu 9.10 64 bit karmic
python 2.6.4
VirtualBox 3.1.6 r59338
Firefox v 3.5.9 / Chrome 5.0.342.9 beta
I've tried to run VBoxWeb both as root and with normal user permissions.
Original comment by egbert....@gmail.com
on 21 Apr 2010 at 5:53
use firefox
Original comment by msav...@gmail.com
on 28 Apr 2010 at 4:54
I use firefox and have this issue. I think this project is dead as this issue
is open
now for quite a long time.
Original comment by patrick....@gmail.com
on 28 Apr 2010 at 8:46
Try this:
in file www/static/js/VirtualBox_Main.js modify lines 657-659 to the following
state
(comment them):
// getDebugger: function()
// {
// return this.jsonObject.debugger;
// },
Original comment by Zer0C...@gmail.com
on 14 May 2010 at 12:14
This doesn't seem to make any difference
Original comment by patrick....@gmail.com
on 14 May 2010 at 2:09
Comment 18 by Zer0C88L, Yesterday (34 hours ago)
Try this:
in file www/static/js/VirtualBox_Main.js modify lines 657-659 to the following
state
(comment them):
// getDebugger: function()
// {
// return this.jsonObject.debugger;
// },
YES!!! :D
Original comment by icq33455...@gmail.com
on 15 May 2010 at 10:32
This does not make a difference to me either. Is anyone looking at this?
Original comment by pgmb...@googlemail.com
on 28 May 2010 at 12:57
RE #18: This works perfectly for me. Thank you!
Original comment by jason...@gmail.com
on 25 Jul 2010 at 9:39
Original comment by achim.ha...@gmail.com
on 26 Aug 2010 at 2:18
Original issue reported on code.google.com by
robinlen...@gmail.com
on 30 Oct 2009 at 7:10