obex data server crash upon file transfer from computer to bluetooth device

[Hugues]

Binary package hint: obex-data-server

lsb_release -rd:
Description: Ubuntu karmic (development branch)
Release: 9.10

apt-cache policy obex-data-server:
obex-data-server:
  Installed: 0.4.4-2
  Candidate: 0.4.4-2
  Version table:
 *** 0.4.4-2 0
        500 http://ca.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status
Expected Behavior:
   File transfer to bluetooth device (LG RUMOUR PHONE)

What happened:
   2 possible behavior:
      1- obex data server crash (and the report tool leads me to this page ;))
      2- The file Transfer dialog with title: Sending files via bluetooth open and just stays there with no progress (left it there for 15 minutes)

I think this bug was not in the list I was presented though it may be related to: #222695 or #327200. I'm truly sorry if I entered a duplicate.

take care

ProblemType: Crash
Architecture: i386
Date: Tue Aug 4 16:16:05 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/obex-data-server
NonfreeKernelModules: nvidia wl
Package: obex-data-server 0.4.4-2
ProcCmdline: /usr/bin/obex-data-server --no-daemon
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_CA.UTF-8
ProcVersionSignature: Ubuntu 2.6.28-14.47-generic
SegvAnalysis:
 Segfault happened at: 0x805f64d <usb_close@plt+76013>: mov 0x20(%eax),%eax
 PC (0x0805f64d) ok
 source "0x20(%eax)" (0xaaaaaaca) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: obex-data-server
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_loop_run () from /usr/lib/libglib-2.0.so.0
Title: obex-data-server crashed with SIGSEGV in g_main_context_dispatch()
Uname: Linux 2.6.28-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:emit_disconnected (session=0x95b3240) at ods-session.c:179
g_idle_dispatch (source=0x95b04b8, callback=0xaaaaaaaa,
IA__g_main_context_dispatch (context=0x95ac508)
g_main_context_iterate (context=0x95ac508,
IA__g_main_loop_run (loop=0x95b0298)

[Baptiste Mille-Mathias (bmillemathias)]

Hello Hugues,

sorry for the late reply.
do you still have the same problem?

[Hugues (hugues-landry)]

Hi Baptiste,
   Thanks for your answer, Everything is working fine since karmic release :)

Thanks for all the good work you guys do on ubuntu, it's an amazing
distribution!

take care

Hugues

On Sun, Apr 4, 2010 at 6:37 AM, Baptiste Mille-Mathias
<email address hidden> wrote:
> Hello Hugues,
>
> sorry for the late reply.
> do you still have the same problem?
>
> --
> obex data server crash upon file transfer from computer to bluetooth device
> https://bugs.launchpad.net/bugs/409011
> 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
>
> lsb_release -rd:
> Description:    Ubuntu karmic (development branch)
> Release:        9.10
>
> apt-cache policy obex-data-server:
> obex-data-server:
>  Installed: 0.4.4-2
>  Candidate: 0.4.4-2
>  Version table:
>  *** 0.4.4-2 0
>        500 http://ca.archive.ubuntu.com karmic/main Packages
>        100 /var/lib/dpkg/status
> Expected Behavior:
>   File transfer to bluetooth device (LG RUMOUR PHONE)
>
> What happened:
>   2 possible behavior:
>      1- obex data server crash (and the report tool leads me to this page ;))
>      2- The file Transfer dialog with title: Sending files via bluetooth open and just stays there with no progress (left it there for 15 minutes)
>
> I think this bug was not in the list I was presented though it may be related to: #222695 or #327200. I'm truly sorry if I entered a duplicate.
>
> take care
>
> ProblemType: Crash
> Architecture: i386
> Date: Tue Aug  4 16:16:05 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/bin/obex-data-server
> NonfreeKernelModules: nvidia wl
> Package: obex-data-server 0.4.4-2
> ProcCmdline: /usr/bin/obex-data-server --no-daemon
> ProcEnviron:
>  SHELL=/bin/bash
>  LANG=en_CA.UTF-8
> ProcVersionSignature: Ubuntu 2.6.28-14.47-generic
> SegvAnalysis:
>  Segfault happened at: 0x805f64d <usb_close@plt+76013>: mov    0x20(%eax),%eax
>  PC (0x0805f64d) ok
>  source "0x20(%eax)" (0xaaaaaaca) not located in a known VMA region (needed readable region)!
>  destination "%eax" ok
> SegvReason: reading unknown VMA
> Signal: 11
> SourcePackage: obex-data-server
> StacktraceTop:
>  ?? ()
>  ?? () from /usr/lib/libglib-2.0.so.0
>  g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
>  ?? () from /usr/lib/libglib-2.0.so.0
>  g_main_loop_run () from /usr/lib/libglib-2.0.so.0
> Title: obex-data-server crashed with SIGSEGV in g_main_context_dispatch()
> Uname: Linux 2.6.28-14-generic i686
> 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/409011/+subscribe
>