Ubuntu
gnome-software package

gnome-software crashed with SIGSEGV in _IO_vfprintf_internal()

Bug #1719060 reported by joshiss
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-software (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

the error occurred while opening the

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-software 3.26.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 23 11:14:39 2017
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2016-03-07 (564 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba N/A
 gnome-software-plugin-snap 3.26.0-0ubuntu2
ProcCmdline: /usr/bin/gnome-software --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7f8c4e12b3e6 <__strlen_sse2+38>: movdqu (%rax),%xmm4
 PC (0x7f8c4e12b3e6) ok
 source "(%rax)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%xmm4" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-software
StacktraceTop:
 _IO_vfprintf_internal (s=s@entry=0x7ffff55e0300, format=<optimized out>, format@entry=0x5620d7a6d788 "Don't know how to handle ‘%s’", ap=ap@entry=0x7ffff55e0470) at vfprintf.c:1643
 __GI___vasprintf_chk (result_ptr=0x7ffff55e0450, flags=1, format=0x5620d7a6d788 "Don't know how to handle ‘%s’", args=0x7ffff55e0470) at vasprintf_chk.c:66
 g_vasprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_strdup_vprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_strdup_printf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-software crashed with SIGSEGV in _IO_vfprintf_internal()
UpgradeStatus: Upgraded to artful on 2017-09-14 (8 days ago)
UserGroups: adm lpadmin sambashare sudo

Revision history for this message
joshiss (joshiss) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _IO_vfprintf_internal (s=s@entry=0x7ffff55e0300, format=<optimized out>, format@entry=0x5620d7a6d788 "Don't know how to handle \342\200\230%s\342\200\231", ap=ap@entry=0x7ffff55e0470) at vfprintf.c:1643
 __GI___vasprintf_chk (result_ptr=result_ptr@entry=0x7ffff55e0450, flags=flags@entry=1, format=0x5620d7a6d788 "Don't know how to handle \342\200\230%s\342\200\231", format@entry=0x7ffff55e0450 "", args=0x7ffff55e0470) at vasprintf_chk.c:66
 vasprintf (__ap=<optimized out>, __fmt=<optimized out>, __ptr=0x7ffff55e0450) at /usr/include/x86_64-linux-gnu/bits/stdio2.h:210
 g_vasprintf (string=string@entry=0x7ffff55e0450, format=<optimized out>, args=args@entry=0x7ffff55e0470) at ../../../../glib/gprintf.c:316
 g_strdup_vprintf (format=<optimized out>, args=args@entry=0x7ffff55e0470) at ../../../../glib/gstrfuncs.c:514

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-software (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Sebastien Bacher (seb128)
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-software (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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