bluetooth-sendto crashed with SIGSEGV in g_path_is_absolute()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-bluetooth (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
The application gave this error while sending files to a Blackberry Q10 phone via Bluetooth.
NOTE, that there might be previously reported similar bugs but for older, unsupported versions of Ubuntu, hence I'm reporting this as a new issue.
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: gnome-bluetooth 3.8.2.1-0ubuntu12
ProcVersionSign
Uname: Linux 3.19.0-22-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Jul 8 10:43:25 2015
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2015-07-05 (2 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: bluetooth-sendto --device=
SegvAnalysis:
Segfault happened at: 0x7efbf6a45167 <g_path_
PC (0x7efbf6a45167) ok
source "$0x2f" ok
destination "(%rdi)" (0x000000d0) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-bluetooth
StacktraceTop:
g_path_is_absolute () from /lib/x86_
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? ()
Title: bluetooth-sendto crashed with SIGSEGV in g_path_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
| Patrik B. (inoki-deactivatedaccount) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #753079, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.