Public bug reported:

occurred while wiping free space

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: bleachbit 0.9.3-1
ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
Uname: Linux 3.8.0-15-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Mon Apr  1 02:08:58 2013
ExecutablePath: /usr/share/bleachbit/bleachbit.py
InstallationDate: Installed on 2013-02-12 (47 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: python /usr/bin/bleachbit
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 LANGUAGE=en_AU:en
 SHELL=/bin/bash
 TERM=unknown
SegvAnalysis:
 Segfault happened at: 0x7f0f0aa9548b:  rep movsq %ds:(%rsi),%es:(%rdi)
 PC (0x7f0f0aa9548b) ok
 source "%ds:(%rsi)" (0x02044000) not located in a known VMA region (needed 
readable region)!
 destination "%es:(%rdi)" (0x7f0f05a642dc) ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: bleachbit
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 _IO_default_xsputn () from /lib/x86_64-linux-gnu/libc.so.6
 _IO_file_xsputn () from /lib/x86_64-linux-gnu/libc.so.6
 fwrite () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
Title: bleachbit.py crashed with SIGSEGV in _IO_default_xsputn()
UpgradeStatus: Upgraded to raring on 2013-03-28 (3 days ago)
UserGroups:

** Affects: bleachbit (Ubuntu)
     Importance: Medium
         Status: New


** Tags: amd64 apport-crash raring

** 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/1162623

Title:
  bleachbit.py crashed with SIGSEGV in __GI__IO_default_xsputn()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bleachbit/+bug/1162623/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to