Bug 615

what was used in steps if it's useful:

step 1 was inputted:
 - name: WindowsXP
 - selection: ISO
step 2 was inputted:
 - ISO selection: find some ISO not on the regular storages
 - OS Type: Windows
 - Version: XP
step 3:
 - RAM: 1024
 - CPU: 1
step 4:
 - select managed or other storage

then click browse

then press "New Volume"

if you strace virt-manager on what does it hang ?

CC: (none) => dmorganec

i was unsuccessfull to do an strace.

if i just ran "strace virt-manager" it just ended and had forked itself.

if i ran "strace -f virt-manager" it seemed to have some kind of issue with polkit, and i was unable with virt-manager to connect to the libvirtd.

i retried as root this time, instead of regular user which uses polkit, and i was able to actually do this...

so, is there some polkit access problem somewhere? i would think the issue is more related to that, but no conclusive evidence in either direction. either that, or the updates i installed had something to do with this.

if someone knows something to test, it might help.

Is this bug still there in Cauldron?

CC: (none) => lists.jjorge

i think someone told me that a newer version actually fixes this and that the newer version was released in the final... i have a mageia1 at work, with virt-manager, i'll test it there...

sorry, i just checked, it still has the bug in mageia final 1. (don't have a hardware cauldron to test) But this is easily reproducable, so i guess someone could doublecheck.

do we have a virt-manager maintainer?

(In reply to comment #6)
> sorry, i just checked, it still has the bug in mageia final 1. (don't have a
> hardware cauldron to test) But this is easily reproducable, so i guess someone
> could doublecheck.
> 
> do we have a virt-manager maintainer?

No, we don't

cc'ing Funda, Thierry and Jerôme, who touched this package. 

Hope one of them knows or can check whether or not this was fixed. 
Or have you now been able to test with Mga2Alpha1, AL13N?

setting version of this bug to "1"
If it is present in cauldron, too, that should go into a seperate bug report.

CC: (none) => fundawang, marja11, saispo, thierry.vignaud
Version: Cauldron => 1
Source RPM: virt-manager => virt-manager-0.8.7-1.mga1.i586.rpm

Still no virt-manager maintainer

ping myself to recheck for cauldron

This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

pretty sure mga2 has this issue too... i think i reproduced at work.

Hardware: i586 => All
Version: 1 => 2

Hmm, I haven't had this issue on either mga1 or 2 and have made a dozen or so vm's in the same fashion. I always create from within the "select or managed" dialog because I have several /data directories setup per architecture.

I just did basically the same steps as above, except setup a cauldron iso install at 512M, using a predefined "32bit" storage pool in /data/vmimages/32bit and then created the vm disk image with the "managed or other storage" dialog. No issues.

CC: (none) => stewbintn

this is specifically via that way only. if you create it normally, there is no issue.

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD

Actually this still happens

Version: 2 => Cauldron
Resolution: OLD => (none)
Status: RESOLVED => REOPENED

(In reply to Thierry Vignaud from comment #16)
> Actually this still happens

I assume if it didn't get fixed after over 4 years, it won't be fixed now, after almost 5 yrs, either.

There's no maintainer for virt-manager, so assigning to all packagers collectively

Assignee: bugsquad => pkg-bugs

Cannot reproduce. When choosing "select managed or other existing storage" and clicking "Forward" then I get an input error telling that a storage path needs to be provided, this is on mga5.

And if it still happens for you and you have a reproducer, better report that upstream so that it might eventually be fixed. Just keeping this report open forever won't help anyone.

CC: (none) => doktor5000

Looks fixed as of virt-manager-1.3.2-1.mga6

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED