usb-creator-gtk crashed with SIGSEGV in g_slist_length()

Bug #1162524 reported by Anmar Oueja
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
usb-creator (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Happens on any image I use.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: usb-creator-gtk 0.2.47
ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
Uname: Linux 3.8.0-15-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Sun Mar 31 12:28:25 2013
ExecutablePath: /usr/bin/usb-creator-gtk
InstallationDate: Installed on 2013-03-25 (5 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130325)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/bin/usb-creator-gtk
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f903e53f400 <g_slist_length+16>: mov 0x8(%rdi),%rdi
 PC (0x7f903e53f400) ok
 source "0x8(%rdi)" (0xa00000008) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: usb-creator
StacktraceTop:
 g_slist_length () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/python3/dist-packages/gi/_gi.cpython-33m-x86_64-linux-gnu.so
 PyEval_EvalFrameEx ()
 PyEval_EvalCodeEx ()
 PyEval_EvalFrameEx ()
Title: usb-creator-gtk crashed with SIGSEGV in g_slist_length()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Anmar Oueja (anmar) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_slist_length (list=0xa00000000, list@entry=0x26fb920) at /build/buildd/glib2.0-2.36.0/./glib/gslist.c:874
 _py_args_combine_and_check_length (py_kwargs=0x7f902c0effc8, py_args=0x7f9034051b90, arg_name_hash=0x0, arg_name_list=0x26fb920, function_name=0x1 <Address 0x1 out of bounds>) at ../../gi/pygi-invoke.c:169
 _invoke_state_init_from_callable_cache (kwargs=0x7f902c0effc8, py_args=<optimized out>, cache=0x26fb640, state=0x7f90254a56a0) at ../../gi/pygi-invoke.c:301
 pygi_callable_info_invoke (info=0x212d000, py_args=<optimized out>, kwargs=0x7f902c0effc8, cache=0x26fb640, function_ptr=0x0, user_data=0x0) at ../../gi/pygi-invoke.c:653
 ext_do_call (nk=0, na=0, flags=<optimized out>, pp_stack=0x7f90254a58b0, func=0x7f902c04d050) at ../Python/ceval.c:4374

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 usb-creator (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
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 usb-creator (Ubuntu):
status: New → Confirmed
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.