virt-manager crashed with SIGSEGV in _pygi_argument_from_object()

Bug #1359815 reported by Cristian Aravena Romero
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
pygobject
Fix Released
Critical
virt-manager
Won't Fix
Undecided
pygobject (Ubuntu)
Fix Released
High
Martin Pitt

Bug Description

Double click in conection

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: virt-manager 1:1.0.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
Uname: Linux 3.16.0-9-generic x86_64
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Aug 21 11:07:33 2014
ExecutablePath: /usr/share/virt-manager/virt-manager
InstallationDate: Installed on 2014-04-27 (116 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python2 -tt /usr/share/virt-manager/virt-manager
SegvAnalysis:
 Segfault happened at: 0x7f1a2f269fb7: mov (%rax),%rax
 PC (0x7f1a2f269fb7) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: virt-manager
StacktraceTop:
 ?? () from /usr/lib/python2.7/dist-packages/gi/_gi.so
 ffi_closure_unix64_inner () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_closure_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_cell_renderer_get_preferred_width () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: virt-manager crashed with SIGSEGV in ffi_closure_unix64_inner()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _pygi_argument_from_object (object=0x3ddead0, type_info=0x0, transfer=(unknown: 1556257872)) at ../../gi/pygi-argument.c:955
 ffi_closure_unix64_inner (closure=0x7f1a30d08010, rvalue=0x7fff5cc29c50, reg_args=0x7fff5cc29ba0, argp=0x7fff5cc29c78 "") at ../src/x86/ffi64.c:670
 ffi_closure_unix64 () at ../src/x86/unix64.S:229
 gtk_cell_renderer_real_get_preferred_size (natural_size=<optimized out>, minimum_size=<optimized out>, orientation=<optimized out>, widget=<optimized out>, cell=<optimized out>) at /build/buildd/gtk+3.0-3.12.2/./gtk/gtkcellrenderer.c:1256
 gtk_cell_renderer_real_get_preferred_width (cell=0x3ec2600, widget=0x0, minimum_size=0x7fff5cc29dc8, natural_size=0x7fff5cc29dcc) at /build/buildd/gtk+3.0-3.12.2/./gtk/gtkcellrenderer.c:1295

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 virt-manager (Ubuntu):
importance: Undecided → Medium
summary: - virt-manager crashed with SIGSEGV in ffi_closure_unix64_inner()
+ virt-manager crashed with SIGSEGV in _pygi_argument_from_object()
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
In , Cristian (cristian-redhat-bugs) wrote :
Download full text (6.2 KiB)

Open bug in launchpad.net:
https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1359815

"Double click in conection"

#0 0x00007f1a2f269fb7 in _pygi_argument_from_object (object=0x3ddead0, type_info=0x0, transfer=(unknown: 1556257872)) at ../../gi/pygi-argument.c:955
        length = 34440432
        item_size = <optimized out>
        array = 0x0
        item_transfer = <optimized out>
        i = <optimized out>
        is_zero_terminated = 1556257248
        item_type_info = 0x3ddead0
        arg = {v_boolean = 7, v_int8 = 7 '\a', v_uint8 = 7 '\a', v_int16 = 7, v_uint16 = 7, v_int32 = 7, v_uint32 = 7, v_int64 = 7, v_uint64 = 7, v_float = 9.80908925e-45, v_double = 3.4584595208887258e-323, v_short = 7, v_ushort = 7, v_int = 7, v_uint = 7, v_long = 7, v_ulong = 7, v_ssize = 7, v_size = 7, v_string = 0x7 <error: Cannot access memory at address 0x7>, v_pointer = 0x7}
        type_tag = <optimized out>
        cleanup_data = 0x0
        __FUNCTION__ = "_pygi_argument_from_object"
#1 0x00007f1a2e8a98ef in ffi_closure_unix64_inner (closure=0x7f1a30d08010, rvalue=0x7fff5cc29c50, reg_args=0x7fff5cc29ba0, argp=0x7fff5cc29c78 "") at ../src/x86/ffi64.c:670
        cif = 0x20d8508
        avalue = 0x7fff5cc29a90
        arg_types = <optimized out>
        i = <optimized out>
        avn = <optimized out>
        gprcount = 6
        ssecount = <optimized out>
        ngpr = 1
        nsse = 0
        ret = 0
#2 0x00007f1a2e8a9c66 in ffi_closure_unix64 () at ../src/x86/unix64.S:229
No locals.
#3 0x00007f1a23c867c2 in gtk_cell_renderer_real_get_preferred_size (natural_size=<optimized out>, minimum_size=<optimized out>, orientation=<optimized out>, widget=<optimized out>, cell=<optimized out>) at /build/buildd/gtk+3.0-3.12.2/./gtk/gtkcellrenderer.c:1256
        min_req = {width = 35941184, height = 0}
#4 gtk_cell_renderer_real_get_preferred_width (cell=0x3ec2600, widget=0x0, minimum_size=0x7fff5cc29dc8, natural_size=0x7fff5cc29dcc) at /build/buildd/gtk+3.0-3.12.2/./gtk/gtkcellrenderer.c:1295
No locals.
#5 0x00007f1a23c87c35 in gtk_cell_renderer_get_preferred_width (cell=cell@entry=0x2246b40, widget=widget@entry=0x21c44a0, minimum_size=minimum_size@entry=0x7fff5cc29dc8, natural_size=natural_size@entry=0x7fff5cc29dcc) at /build/buildd/gtk+3.0-3.12.2/./gtk/gtkcellrenderer.c:1479
        klass = <optimized out>
        width = -1
        __FUNCTION__ = "gtk_cell_renderer_get_preferred_width"
#6 0x00007f1a23c80211 in gtk_cell_area_request_renderer (area=0x216b410, renderer=0x2246b40, orientation=GTK_ORIENTATION_HORIZONTAL, widget=0x21c44a0, for_size=-1, minimum_size=0x7fff5cc29dc8, natural_size=0x7fff5cc29dcc) at /build/buildd/gtk+3.0-3.12.2/./gtk/gtkcellarea.c:3584
        focus_line_width = 2
        __FUNCTION__ = "gtk_cell_area_request_renderer"
#7 0x00007f1a23c80d80 in compute_size (box=0x3ec2600, box@entry=0x216b410, orientation=orientation@entry=GTK_ORIENTATION_HORIZONTAL, context=0x3, context@entry=0x2252980, widget=0x3df6cd8, widget@entry=0x21c44a0, for_size=64974016, for_size@entry=-1, minimum_size=0x3df6cc0, minimum_size@entry=0x7fff5cc29e28, natural_size=0x0) at /build/buildd/gtk+3.0-3.12.2/./gtk/gtkcellareabox.c:1524
        info = ...

Read more...

Revision history for this message
Cole Robinson (crobinso) wrote :

If you are using latest pygobject, like 3.13.4 or later, you are probably hitting this:

https://bugzilla.gnome.org/show_bug.cgi?id=735090
https://bugzilla.redhat.com/show_bug.cgi?id=1130758

Revision history for this message
In , Cole (cole-redhat-bugs) wrote :

I commented on the original launchpad issue, pretty sure this is a pygobject bug that's now fixed upstream.

FWIW if a crash comes from pygi or gtk code it's usually not virt-manager's fault, since the bindings generally should protect us from crashes like that

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

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

Changed in virt-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Confirming, virt-manager didn't work today aynmore for me (when trying to connect).

Revision history for this message
gadLinux (gad-aguilardelgado) wrote :

Confirming, here with 14.10 utopic

Revision history for this message
Martin Pitt (pitti) wrote :
affects: virt-manager (Ubuntu) → pygobject (Ubuntu)
Changed in pygobject (Ubuntu):
importance: Medium → High
status: Confirmed → Triaged
Martin Pitt (pitti)
Changed in pygobject (Ubuntu):
status: Triaged → Fix Committed
assignee: nobody → Martin Pitt (pitti)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package pygobject - 3.13.90-0ubuntu2

---------------
pygobject (3.13.90-0ubuntu2) utopic; urgency=medium

  * Skip marshalling NULL output arguments in Python closures. Patch taken
    from upstream git. (LP: #1359815)
 -- Martin Pitt <email address hidden> Mon, 25 Aug 2014 08:13:46 +0200

Changed in pygobject (Ubuntu):
status: Fix Committed → Fix Released
Changed in pygobject:
importance: Unknown → Critical
status: Unknown → Fix Released
Changed in virt-manager:
importance: Unknown → Undecided
status: Unknown → Won't Fix
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.