set version to cauldron, because package requests will usually be done for cauldron first and then be available in next stable release

Version: 1 => Cauldron
Source RPM: (none) => vice

*** Bug 3688 has been marked as a duplicate of this bug. ***

CC: (none) => chipo

still is not in cauldron :(

(In reply to comment #3)
> still is not in cauldron :(

It is now - please test. :)

CC: (none) => zen25000

Thank you !!! :)

@ Steve
@ Martin
@ Zombie Ryushu

Please give feedback about how the package works in cauldron (without feedback there is no chance it'll be packaged for 1, too)

CC: (none) => zombie_ryushu
Whiteboard: Mdv => Mdv, cauldron

⢠Instalation to Mageia 1 â no problems
⢠Icons in K-Menu â all
⢠installed CBM2 Emulator, CPLUS4 Emulator, C128 Emulator (read the note below), C64 Emulator, PET Emulator â all works

NOTE: when C128 Emulator is opened, looks like a bug, but is not. Pls read: http://vicekb.trikaliotis.net/00-007

(In reply to comment #7)
> ⢠Instalation to Mageia 1 â no problems
> ⢠Icons in K-Menu â all
> ⢠installed CBM2 Emulator, CPLUS4 Emulator, C128 Emulator (read the note
> below), C64 Emulator, PET Emulator â all works
> 
> NOTE: when C128 Emulator is opened, looks like a bug, but is not. Pls read:
> http://vicekb.trikaliotis.net/00-007

@ Martin

Thanks for the feedback, that sounds really good :)

@ Barry

Thanks for your work :)

Since cauldron vice already works in "1", assigning to you to get a vice package in 1/updates and reassign to QA

Hardware: i586 => All
Version: Cauldron => 1
Assignee: bugsquad => zen25000

(In reply to comment #8)
> 
> Since cauldron vice already works in "1", assigning to you to get a vice
> package in 1/updates and reassign to QA

vice-2.3.14-1.mga1 is now in Mga1 updates/testing

Assignee: zen25000 => qa-bugs

x86_64

Thanks Barry!

All the emulators start and tested with a couple of D64 disk images. It seems quite unstable but emulators like this do tend to be. This doesn't appear to be maintained any more upstream. Still managed to play Galaxian :D


Testing complete x86_64

I get ... 
Warning - Your machine is too slow for current settings!

but it does work.  At exit though, I get ...
Writing configuration file `/home/dave/.vice/vicerc'.

And a popup saying it cannot save settings.  This appears to be
because it's trying to write the file without having created
the directory ~/.vice

Can this be fixed easily, or should it be rported upstream
and the update validated?

CC: (none) => davidwhodgins

(In reply to comment #11)
> I get ... 
> Warning - Your machine is too slow for current settings!
> 

I tested in both Cauldron and Mga1 on different machines and did not see this - although I did not run it from a terminal.
 
> but it does work.  At exit though, I get ...
> Writing configuration file `/home/dave/.vice/vicerc'.
> 

Again I have not seen this either. I do have ~/.vice and if I rename it 
and then click "save settings" from e.g. the C64 menu, then a new one is created. I have only done some quick checking on this, but so far I don't see a case where that file is created automatically by any of the simulators, although it did get created at some time during my testing, and don't recall using the "save settings" button previously. 
My vicerc had only a VIC20 section in it, so I guess that module created the ~/.vice.

> And a popup saying it cannot save settings.  This appears to be
> because it's trying to write the file without having created
> the directory ~/.vice

Could you check whether in your case the creation of a ~/.vice for the current user does in fact fix the issue?
If so, I suppose we could touch /home/$USER/.vice in %post but I don't think it's policy to mess with user folders during installation, so I would not be happy about it. :/ 

I will keep trying to replicate the error as time allows.

BTW has anyone managed to get a large size C64 emulator screen? Mine are only around 1/9 screen size, but it may be an nvidia thing as I only have nvidia graphics. The VIC20 double size is OK.

I don't see the error message. Dave do you have it set to 'save on exit' in the settings menu?

I tried with that set and it created a dir and saved the vicerc without complaining.

There is one error message as it starts though..
Error - mouse_cursor_grab: bad params

Barry yes I managed a to use double size, nvidia here too. I had problems sometimes with this locking up the desktop and having to kill it from a tty though. I'm assuming that is just because it's a bit flaky, emulators do tend to be that way.

Now I can't seem to recreate the error writing the vicerc file.

It was with the xvic emulator, which I just had lock up for
about 2 minutes during which kde was unresponsive.  I was able
to use alt+ctrl+f1, and after switching back to kde, it started
responding again, and I was able to close it.

I'm inclined to approve the update, as it does work, but think
the package description should contain a warning that the
emulators may be very unstable at times, and shouldn't be
used on a production, or critical system.

Validating

Advisory
-------------
This update brings the Vice Commodore emulator which was present in Mandriva 2010.2 but missing from Mageia 1.

Please note that these have proved to be rather unstable in testing so use advisedly.
-------------

SRPM: vice-2.3.14-1.mga1.src.rpm

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

update pushed

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED