spice-vdagent crashed with SIGSEGV

Bug #2015405 reported by zebul666
52
This bug affects 10 people
Affects Status Importance Assigned to Milestone
spice-vdagent (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Just launching an ubuntu 23.04 beta VM on libvirtd/qemu/KVM and this brings the reporting crash app as soon as loging into the desktop.

ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: spice-vdagent 0.22.1-3
ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
Uname: Linux 6.2.0-18-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 5 23:21:08 2023
ExecutablePath: /usr/bin/spice-vdagent
InstallationDate: Installed on 2023-03-31 (5 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329)
ProcCmdline: /usr/bin/spice-vdagent
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x559a23cd00e0: mov (%r15),%rdi
 PC (0x559a23cd00e0) ok
 source "(%r15)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: spice-vdagent
StacktraceTop:
 ()
 __libc_start_call_main (main=main@entry=0x559a23ccfe80, argc=argc@entry=1, argv=argv@entry=0x7ffce18a7c08) at ../sysdeps/nptl/libc_start_call_main.h:58
 __libc_start_main_impl (main=0x559a23ccfe80, argc=1, argv=0x7ffce18a7c08, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffce18a7bf8) at ../csu/libc-start.c:360
 ()
Title: spice-vdagent crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
separator:

Revision history for this message
zebul666 (zebul666) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1965173, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
zebul666 (zebul666) wrote :

Well, bug #1965173 has been deleted, so this bug is not a duplicate anymore, right ?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in spice-vdagent (Ubuntu):
status: New → Confirmed
Revision history for this message
Jane Atkinson (irihapeti) wrote :

This happened when trying out a daily Edubuntu install in a QEMU/KVM VM. Apart from the Apport message, nothing obvious happened.

tags: added: noble
Revision history for this message
Jane Atkinson (irihapeti) wrote :

I saw this again yesterday in a standard Ubuntu Noble install in QEMU/KVM. It's not a ISO install test; it's been updated regularly for a while. Again, other than the crash notice, nothing obvious happens.

Revision history for this message
nelsinchi (nelsinchi) wrote :

I recently installed Ubuntu 24.04 Noble Numbat (development branch), then I did `sudo apt update && sudo apt upgrade -y`, then I rebooted the VM. After that I got the error.

I installed this OS just for testing purposes via LXD VM.

Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.