{5} Assigned, Active Tickets by Owner (Full Description) (9 matches)

List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.

mike

Ticket Summary Component Milestone Type Severity Created
Description
#64 Q doesn't allow dots in PC names, but Minix from FreeOSZoo comes with two Q Control Q₂-0.9.1aX defect minor 10/05/07

When downloading Minix from FreeOSZoo through Q, you can't save the PC's configuration as it configured by default. (It still boots fine, however).

Steps to reproduce:

  1. Guest PC -> Download new Guest PC from free.oszoo.org
  2. Select Minix 3.1.1.
  3. Click Download.
  4. Press Cmd-E to edit the Minix 3.1.1 guest machine.
  5. Click "Update PC"

Results: The "Name" field is filled with the red text "Name with illegal characters (:./)". This occurs without making any changes to the PC configuration, and it can be confusing why the dialog doesn't close when clicking "Update PC" if you are on another tab because the error won't be visible.

Expected results:

  • Either Minix from FreeOSZoo shouldn't come with dots in the name, or Q should handle them.
  • Also, the "Name with illegal characters" error should be more prominent (popup?). It is invisible if you are on another tab.

By the way, great work on Q -- besides a few minor bugs, it works the best of all the other free emulators I've tried on OS X.


#65 Q doesn't correctly handle floppy disk images with spaces in their path name Q Control Q₂-0.9.1aX defect minor 10/05/07

Steps to reproduce:

  1. Edit any virtual machine.
  2. In the Hardware tab, go to Floppy -> Choose Imagefile...
  3. Choose a floppy image located in a folder with spaces somewhere in its pathname (create with Tools -> Create new Diskimage... if necessary).
  4. Boot the system.

Results:

Qemu unexpectedly quit

Error: invalid option -- '-'

and the system fails to start. Advanced -> QEMU Arguments is filled in with the pathname of the floppy after the spaces.

I'd guess this is happening because spaces aren't being quoted when Q calls qemu. I haven't looked at the source code, but maybe Q should shell out to qemu by passing arguments in an array? (Haven't checked if Q does that, but it seems that that may solve this problem).


#8 use shared memory Q Control Q₂-0.9.1aX enhancement normal 08/04/06

Use shared memory to display qemu video output.

This feature will "unify" Q Control and the Q Guests in one app.


#15 Q refuses to terminate if guest has crashed Q Control Q₂-0.9.1aX defect normal 08/30/07

When a guest has crashed Q does not recognize this and refuses to quit, saying a guest were still running.

As a workaround Q needs to be killed.


#27 Rework selection of architecture / machine selection editPC Q₂-0.9.1aX enhancement normal 08/31/07

Currently there is one list with combinations of architecture and emulated board/machine.

This list is incomplete for QEMU CVS and is potentially growing. Also, this selection has effects on the other options available.

Suggestion: Reorder controls hierarchically so that the architecture selection is on the top and influences the selection of machines (possibly retrieve options automatically via "-M ?" overriding known options). The combination of architecture and machine should then influence other available options.

Examples:

  • The Sparc32 SS-5 machine [renamed in post-0.9.0] does not allow more than 256 MB RAM. In any case, Q should catch such error messages of an exiting QEMU and display them in a sheet so that the user knows. Then, following this suggestion the Edit PC GUI could be made aware of this and limit the RAM size to numbers known valid (manually).
  • The default Sparc32 "-net nic" network device is not NE2000 but Lance (pcnet). Either label the current NE2000 option "Default" or name it correctly based on arch+machine to avoid confusion.
  • Disable or hide pcnet and Realtek for Sparc32 (not available).

Such differences between machines appear to be quite common, depending on implementation progress or real hardware.


#71 Leaks Mach ports Qemu Guest Window Q₂-0.9.1aX defect normal 01/10/08

Q v0.9.0d89 (and v0.9.0a89) running on Mac OS X 10.4.11. Guest is NetBSD 4.0, with no X11. If left running, the VSZ/RSS of process "i386-softmmu" continues to grow, as seen in the following:

bash$ while true; do vmmap 6616 | grep Mach | tail -1; sleep 10; done
Mach message            [   1464K]
Mach message            [   1628K]
Mach message            [   1792K]
Mach message            [   1956K]
Mach message            [   2116K]
Mach message            [   2280K]
Mach message            [   2444K]
Mach message            [   2608K]
Mach message            [   2772K]
Mach message            [   2936K]
Mach message            [   3100K]
Mach message            [   3264K]
Mach message            [   3428K]
Mach message            [   3592K]
Mach message            [   3756K]
Mach message            [   3920K]
Mach message            [   4084K]

This appears to amount to more than a gigabyte per day.

Drop me an email at stix@stix.id.au if you want any further info.


#21 Visual effects are applied to all screens Qemu Guest Window Q₂-0.9.1aX defect minor 08/31/07

When using multiple monitors, visual effects occur on all monitors, not only the "affected" monitor:

When on a secondary screen Q runs in fullscreen mode, Command+< results in spinning cubes on both screens. Instead, only the secondary screen should rotate in this case.

Same thing for fade-through-black for entering and leaving fullscreen mode.


#30 Q does not recognize every single-token parameter Q Control Q₂-0.9.1aX defect minor 09/01/07

Follow-up from #13 (andreasf):

But additionally, Q does not recognize every single-token parameter and tracking those is a tedious task. Instead, once initial fixes are in place, the argument parsing should be revisited to no longer rely on this string-explosion based on whitespace character, i.e. tokenizing quoted and unquoted strings, ignoring any combination of whitespace characters in between.


#20 Wrong menubar when switching to guest directly Q Control Q₂-0.9.1aX defect normal 08/31/07

When switching from a random Mac application to a Q guest window the menu bar stays as before, i.e. does not show the Q menu bar.

This is related to #8.


Note: See TracReports for help on using and creating reports.