Public bug reported:

Error when this program creating z bootable disk. I'm haven't more
details, only things from bug report.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: usb-creator-gtk 0.2.48
ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
Uname: Linux 3.11.0-7-generic i686
ApportVersion: 2.12.1-0ubuntu4
Architecture: i386
Date: Wed Sep 18 10:10:17 2013
ExecutablePath: /usr/bin/usb-creator-gtk
InstallationDate: Installed on 2013-09-17 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130917)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/bin/usb-creator-gtk
SegvAnalysis:
 Segfault happened at: 0xb6ee30f4:      movl   $0xffffffff,0x4(%eax)
 PC (0xb6ee30f4) ok
 source "$0xffffffff" ok
 destination "0x4(%eax)" (0x00000004) not located in a known VMA region (needed 
writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: usb-creator
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
Title: usb-creator-gtk crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: usb-creator (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-crash i386 need-i386-retrace saucy

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1226980

Title:
  usb-creator-gtk crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1226980/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to