*** This bug is a duplicate of bug 1965173 ***
https://bugs.launchpad.net/bugs/1965173
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.
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/2013117/+attachment/5658390/+files/CoreDump.gz
** Attachment removed: "Disassembly.txt"
https://bugs.launchpad.net/bugs/2013117/+attachment/5658392/+files/Disassembly.txt
** Attachment removed: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/2013117/+attachment/5658395/+files/ProcMaps.txt
** Attachment removed: "ProcStatus.txt"
https://bugs.launchpad.net/bugs/2013117/+attachment/5658396/+files/ProcStatus.txt
** Attachment removed: "Registers.txt"
https://bugs.launchpad.net/bugs/2013117/+attachment/5658397/+files/Registers.txt
** Attachment removed: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/2013117/+attachment/5658398/+files/Stacktrace.txt
** Attachment removed: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/2013117/+attachment/5658399/+files/ThreadStacktrace.txt
** This bug has been marked a duplicate of private bug 1965173
** Tags removed: need-amd64-retrace
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to spice-vdagent in Ubuntu.
https://bugs.launchpad.net/bugs/2013117
Title:
spice-vdagent crashed with SIGSEGV in __libc_start_call_main()
Status in spice-vdagent package in Ubuntu:
New
Bug description:
I had just logged in following a reboot.
I created a terminal window.
In Terminal I did:
sudo snap refresh => up to date
then:
sudo apt update && sudo apt dist-upgrade => up to date.
I was sitting looking at the screen, not doing anything, when the
error popped up.
ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: spice-vdagent 0.22.1-3
ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
Uname: Linux 6.2.0-18-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 28 18:10:01 2023
ExecutablePath: /usr/bin/spice-vdagent
InstallationDate: Installed on 2023-03-23 (4 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230323)
ProcCmdline: /usr/bin/spice-vdagent
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=<set>
SegvAnalysis:
Segfault happened at: 0x55ac97b680e0: mov (%r15),%rdi
PC (0x55ac97b680e0) 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=0x55ac97b67e80, argc=argc@entry=1,
argv=argv@entry=0x7fffe4ddfbb8) at ../sysdeps/nptl/libc_start_call_main.h:58
__libc_start_main_impl (main=0x55ac97b67e80, argc=1, argv=0x7fffe4ddfbb8,
init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>,
stack_end=0x7fffe4ddfba8) at ../csu/libc-start.c:360
?? ()
Title: spice-vdagent crashed with SIGSEGV in __libc_start_call_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/2013117/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
