obex-data-server crashed with SIGSEGV

Bug #556491 reported by Jorge Sampaio
44
This bug affects 7 people
Affects Status Importance Assigned to Milestone
obex-data-server (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: obex-data-server

I was trying to transfer a file from my laptop (running 9.10) to my desktop (10.04 beta) using bluetooth connection

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: obex-data-server 0.4.5-1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Apr 6 21:05:25 2010
ExecutablePath: /usr/bin/obex-data-server
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
ProcCmdline: /usr/bin/obex-data-server --no-daemon
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_AU.utf8
SegvAnalysis:
 Segfault happened at: 0x41154f: repz cmpsb %es:(%rdi),%ds:(%rsi)
 PC (0x0041154f) ok
 source "%es:(%rdi)" (0x0041f263) ok
 destination "%ds:(%rsi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: obex-data-server
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/libopenobex.so.1
 ?? () from /usr/lib/libopenobex.so.1
 ?? () from /usr/lib/libopenobex.so.1
Title: obex-data-server crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Jorge Sampaio (jrgsampaio) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ods_obex_srv_get (obex_context=0x1e835d0,
 obex_event (handle=0x1e86230, object=0x1e880d0,
 obex_deliver_event (self=0x1e8a4b0,
 obex_server (self=0x1e86230, msg=0x1e82530,
 obex_data_indication (self=0x1e86230,

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in obex-data-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Baptiste Mille-Mathias (bmillemathias) wrote :

Hi Jorge

Is this bug is reproductible?

visibility: private → public
Revision history for this message
Jorge Sampaio (jrgsampaio) wrote : Re: [Bug 556491] Re: obex-data-server crashed with SIGSEGV

I don't know. The bluetooth in my notebook (a Toshiba T110) works
erratically in 9.10 (and even worse in 10.04), and since yesterday it is non
operative.

If I make it work, I will try to repeat the operation.

Cheers...

Jorge

On Thu, Apr 8, 2010 at 6:59 PM, Baptiste Mille-Mathias <
<email address hidden>> wrote:

> Hi Jorge
>
> Is this bug is reproductible?
>
> ** Visibility changed to: Public
>
> --
> obex-data-server crashed with SIGSEGV
> https://bugs.launchpad.net/bugs/556491
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “obex-data-server” package in Ubuntu: New
>
> Bug description:
> Binary package hint: obex-data-server
>
> I was trying to transfer a file from my laptop (running 9.10) to my desktop
> (10.04 beta) using bluetooth connection
>
> ProblemType: Crash
> DistroRelease: Ubuntu 10.04
> Package: obex-data-server 0.4.5-1
> ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
> Uname: Linux 2.6.32-19-generic x86_64
> NonfreeKernelModules: nvidia
> Architecture: amd64
> Date: Tue Apr 6 21:05:25 2010
> ExecutablePath: /usr/bin/obex-data-server
> InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
> ProcCmdline: /usr/bin/obex-data-server --no-daemon
> ProcEnviron:
> SHELL=/bin/bash
> LANG=en_AU.utf8
> SegvAnalysis:
> Segfault happened at: 0x41154f: repz cmpsb %es:(%rdi),%ds:(%rsi)
> PC (0x0041154f) ok
> source "%es:(%rdi)" (0x0041f263) ok
> destination "%ds:(%rsi)" (0x00000000) not located in a known VMA region
> (needed writable region)!
> SegvReason: writing NULL VMA
> Signal: 11
> SourcePackage: obex-data-server
> StacktraceTop:
> ?? ()
> ?? ()
> ?? () from /usr/lib/libopenobex.so.1
> ?? () from /usr/lib/libopenobex.so.1
> ?? () from /usr/lib/libopenobex.so.1
> Title: obex-data-server crashed with SIGSEGV
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>
> To unsubscribe from this bug, go to:
>
> https://bugs.launchpad.net/ubuntu/+source/obex-data-server/+bug/556491/+subscribe
>

Revision history for this message
Jorge Sampaio (jrgsampaio) wrote : Feliz Dia do Trabalho! !

Feliz Dia do Trabalho! !

Oi, eu estou disposto a dar-lhe uma grande surpresa:
<www.nokiaoo.com>. Eu comprei um Apple Mac livro há uma semana a
partir deste site. Agora, eu tenho recebido. Esta qualidade do produto
é muito bom. Eles também vendem celulares, TV, motores e assim por
diante. By the way, que vendem principalmente produtos novos e
originais e eles têm muitos bons comentários. Porque o próximo Dia do
Trabalho, por isso muitas empresas est?o promovendo os seus produtos.
nokiaoo site também tem pre?os muito competitivos. Se você precisa
estes produtos, você pode dar uma olhada. é uma boa chance de que você
n?o deve perder. Sauda??es!

Revision history for this message
Dave Ahlswede (mightyquinn) wrote :

I have this crash, completely reproducibly; every time, both on a 64bit desktop and a 32bit netbook connecting to each other, when i use blueman to "Browse device...", it will list the files. Then if i try to read or copy a file, obex-data-server crashes on the remote computer

Revision history for this message
Oded Arbel (oded-geek) wrote :

This happens to me when I try to access file browsing over bluetooth from my Android phone to my Ubuntu laptop running Maverick.

When I first try to connect I get a file listing but when I then try to do something (browse to another directory, copy a file) I get the crash and then I can no longer access the Ubuntu laptop.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in obex-data-server (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.