sudo bluetooth-sendto crashed with SIGSEGV in strcmp()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-bluetooth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-bluetooth
this is the terminal output:
xxxx@yyy:~$ sudo bluetooth-sendto filename.txt
** (bluetooth-
** (bluetooth-
** (bluetooth-
** (bluetooth-
Segmentation fault (Speicherabzug geschrieben)
File was not sent to motorola milestone (droid).
when repeating, segfault does not reoccur, but the rest is identical.
1)
Description: Ubuntu lucid (development branch)
Release: 10.04
2)
bluetooth:
Installiert: 4.51-0ubuntu2
Kandidat: 4.51-0ubuntu2
Versions-Tabelle:
*** 4.51-0ubuntu2 0
500 http://
100 /var/lib/
gnome-bluetooth:
Installiert: 2.29.3-0ubuntu1
Kandidat: 2.29.3-0ubuntu1
Versions-Tabelle:
*** 2.29.3-0ubuntu1 0
500 http://
100 /var/lib/
3)
expected: open dialog to choose receiver, then transfer file to receiver.
4)
instead: opened dialog to choose receiver, then bork.
ProblemType: Crash
Architecture: i386
Date: Tue Jan 12 22:44:35 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/
NonfreeKernelMo
Package: gnome-bluetooth 2.29.3-0ubuntu1
ProcAttrCurrent: unconfined (enforce)
ProcCmdline: bluetooth-sendto Maps-no-
ProcEnviron:
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0xfae11a <strcmp+10>: cmp (%edx),%al
PC (0x00fae11a) ok
source "(%edx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-bluetooth
StacktraceTop:
strcmp () from /lib/tls/
g_str_equal () from /lib/libglib-
?? ()
?? ()
?? () from /usr/lib/
Tags: lucid
Title: bluetooth-sendto crashed with SIGSEGV in strcmp()
Uname: Linux 2.6.32-10-generic i686
UserGroups:
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #456200, 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.