Bug 31142

Summary: spice-vdagent segfaults when installing from Mageia-9-alpha1-x86_64.iso
Product: Mageia Reporter: PC LX <mageia>
Component: InstallerAssignee: Mageia tools maintainers <mageiatools>
Status: NEW --- QA Contact:
Severity: normal    
Priority: Normal    
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: spice-vdagent-0.22.1-2.mga9.src.rpm CVE:
Status comment:
Attachments: Install report.
Screen shot 1
Screen shot 2

Description PC LX 2022-11-16 19:00:23 CET
Description of problem:

When installing from Mageia-9-alpha1-x86_64.iso (Sun Nov  6 06:48:26 PM CET 2022), the virtual console (CTRL+ALT+F2 or CTRL+ALT+F2) shows that spice-vdagent segfaults.

The installation was done in a QEMU/KVM virtual machine with guest agent channel enabled in the VM.



How reproducible:

The several times I checked it always happened.



Steps to Reproduce:
1. Boot a QEMU/KVM virtual machine, with guest agent channel enabled, from the Mageia-9-alpha1-x86_64.iso
2. Change to the virtual console (CTRL+ALT+F2 or CTRL+ALT+F3) and see the error message.
3. See error message.
Comment 1 Lewis Smith 2022-11-17 11:39:05 CET
Thank you for the report.
At what install stage does this happen?
Do you know whether it happens just on your VM setup? I am thinking that you can go a certain distance running the installer on the real hardware - up to disc partitioning - without it touching the disc. If the error occurs sooner, you could then compare real v VM installation.

And perhaps ask on qa-discuss whether ISO testers using VirtualBox see the same.

Are you able to attach the installation log? From a dated Wiki page:
"the reporter should provide the file /root/drakx/report.bug.xz as an attachment. An easy way for doing this is ask the reporter to switch to console 2 (by pressing "Ctrl-Alt-F2") during installation after the bug occurs, plug a USB key/stick and type
 bug /dev/sdxy       [adjusted to the output USB device/partition]"
and subsequently compress it with xz.

CC: (none) => lewyssmith
Source RPM: (none) => spice-vdagent-0.22.1-2.mga9.src.rpm

Comment 2 PC LX 2022-11-17 13:50:30 CET
Created attachment 13515 [details]
Install report.

Relevant line:

[   10.062115] spice-vdagent[699]: segfault at 0 ip 000000000040ae84 sp 00007ffe97e44ad0 error 4 in spice-vdagent[406000+c000]
Comment 3 PC LX 2022-11-17 15:49:09 CET
(In reply to Lewis Smith from comment #1)
> Thank you for the report.
> At what install stage does this happen?
> Do you know whether it happens just on your VM setup?

I can see it when choosing language. See attached screen shots.

> I am thinking that you
> can go a certain distance running the installer on the real hardware - up to
> disc partitioning - without it touching the disc. If the error occurs
> sooner, you could then compare real v VM installation.

Have only tested install on VMs but on host spice-vdagent should not run at all since it is only for VMs.

> And perhaps ask on qa-discuss whether ISO testers using VirtualBox see the
> same.

Will do.

> Are you able to attach the installation log? From a dated Wiki page:
> "the reporter should provide the file /root/drakx/report.bug.xz as an
> attachment. An easy way for doing this is ask the reporter to switch to
> console 2 (by pressing "Ctrl-Alt-F2") during installation after the bug
> occurs, plug a USB key/stick and type
>  bug /dev/sdxy       [adjusted to the output USB device/partition]"
> and subsequently compress it with xz.

In attachment.
Comment 4 PC LX 2022-11-17 15:50:17 CET
Created attachment 13516 [details]
Screen shot 1
Comment 5 PC LX 2022-11-17 15:50:33 CET
Created attachment 13517 [details]
Screen shot 2
Comment 6 Lewis Smith 2022-11-17 16:29:01 CET
Thank you for all those.
I take it that this does not stop the installation: I think you would have said so, and given it a high priority.

Assigning to the MageiaTools people for the Installer.

Assignee: bugsquad => mageiatools
CC: lewyssmith => (none)

Comment 7 PC LX 2022-11-18 02:58:41 CET
This issue removes copy&paste from the host, automatic resolution adjustment and a more seamless mouse handling but otherwise the installation is not stopped by this issue.