qemulator crashes in managed mode
Bug #267005 reported by
jungle barricade cobra
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qemulator (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: qemulator
When a virtual machine(kvm or qemu) is started from qemulator, the default is to start it in managed mode, however when you try to start the management panel the qemulator python front end dies. The virtual machine keeps working correctly but qemulator is dead.
To post a comment you must log in.
System: Ubuntu 8.10 (GERMAN)
Same here. VM starts fine using qemulator, but any attemp to start the control monitor throughs an error on command line, control monitor never shows up and qemulator GUI dies:
loaded settings in controlmon xxx/Downloads/ ubuntu- 8.10-desktop- i386.iso' , '31667', '/dev/pts/1', 'default', '1'] ------- ------- ------- ------- xxx/Downloads/ ubuntu- 8.10-desktop- i386.iso' , '31667', '/dev/pts/1', 'default', '1'] Downloads/ ubuntu- 8.10-desktop- i386.iso qemulator .qemulator/ config qemulator/ qml_controlmon. py:172: GtkWarning: GtkSpinButton: setting an adjustment with non-zero page size is deprecated XML(self. gladefile, "dialog_ jobmonitor" , APP) python2. 5/threading. py", line 486, in __bootstrap_inner qemulator/ qml_controlmon. py", line 167, in run preload_ gui() qemulator/ qml_controlmon. py", line 202, in preload_gui filechooserbutt on_jobmon_ cdrom.add_ shortcut_ folder( self.settings[ "imagespath" ])
Opened monitor with job: ['Ubuntu', '/home/
------ Control monitor opened -------
job: ['Ubuntu', '/home/
jobimage: /home/xxx/
pid: 31667
pts: /dev/pts/1
runstat: 1
basedir: /usr
bindir: /usr/bin
libdir: /usr/lib/qemulator
sharedir: /usr/share/
configdir: /home/xxx/
detected qemu_version: 0.9.1
qemu 0.9.x detected, using 0.9 command set
/usr/lib/
self.wTree = gtk.glade.
Exception in thread Thread-9:
Traceback (most recent call last):
File "/usr/lib/
self.run()
File "/usr/lib/
self.
File "/usr/lib/
self.
GError: Das Lesezeichen file:///home/xxx existiert bereits