bluetoothd crashed with SIGSEGV in calloc()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: bluez
Very soon after booting and entering a Gnome session, doing nothing special yet.
ProblemType: Crash
Architecture: i386
DistroRelease: /usr/bin/
ExecutablePath: /usr/sbin/
Package: bluez 4.30-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/
ProcEnviron: PATH=(custom, no user)
Signal: 11
SourcePackage: bluez
StacktraceTop:
?? () from /lib/tls/
calloc () from /lib/tls/
dbus_malloc0 () from /lib/libdbus-1.so.3
?? () from /lib/libdbus-1.so.3
?? () from /lib/libdbus-1.so.3
Title: bluetoothd crashed with SIGSEGV in calloc()
Uname: Linux 2.6.28-8-generic i686
UserGroups: pulse pulse-access pulse-rt
Dominique Meeùs (dominiquem) wrote : | #1 |
- Dependencies.txt Edit (1.2 KiB, text/plain; charset="utf-8")
- Disassembly.txt Edit (515 bytes, text/plain; charset="utf-8")
- ProcMaps.txt Edit (3.7 KiB, text/plain; charset="utf-8")
- ProcStatus.txt Edit (718 bytes, text/plain; charset="utf-8")
- Registers.txt Edit (459 bytes, text/plain; charset="utf-8")
- Stacktrace.txt Edit (1.9 KiB, text/plain; charset="utf-8")
- ThreadStacktrace.txt Edit (1.9 KiB, text/plain; charset="utf-8")
Apport retracing service (apport) wrote : Symbolic stack trace | #2 |
Apport retracing service (apport) wrote : Symbolic threaded stack trace | #3 |
Changed in bluez: | |
importance: | Undecided → Medium |
Dominique Meeùs (dominiquem) wrote : | #4 |
Once more.
(A crash file was generated but I am not allowed to read it and, as a result ? the file I want to attach seems to be empty. Still I could read it as root and copy the contents here. Apport is not very user-friendly.)
ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Mar 3 19:53:02 2009
DistroRelease: /usr/bin/
ExecutablePath: /usr/sbin/
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/
ProcCwd: /
ProcEnviron: PATH=(custom, no user)
ProcMaps:
b7d36000-b7d3e000 r-xp 00000000 08:05 221802 /usr/lib/
b7d3e000-b7d3f000 r--p 00007000 08:05 221802 /usr/lib/
b7d3f000-b7d40000 rw-p 00008000 08:05 221802 /usr/lib/
b7d40000-b7d41000 r-xp 00000000 08:05 221799 /usr/lib/
b7d41000-b7d42000 r--p 00001000 08:05 221799 /usr/lib/
b7d42000-b7d43000 rw-p 00002000 08:05 221799 /usr/lib/
b7d43000-b7d47000 r-xp 00000000 08:05 221807 /usr/lib/
b7d47000-b7d48000 r--p 00003000 08:05 221807 /usr/lib/
b7d48000-b7d49000 rw-p 00004000 08:05 221807 /usr/lib/
b7d49000-b7d6a000 r-xp 00000000 08:05 221798 /usr/lib/
b7d6a000-b7d6b000 r--p 00020000 08:05 221798 /usr/lib/
b7d6b000-b7d6c000 rw-p 00021000 08:05 221798 /usr/lib/
b7d6c000-b7d6e000 rw-p b7d6c000 00:00 0
b7d6e000-b7d9e000 r-xp 00000000 08:01 37943 /lib/libpcre.
b7d9e000-b7d9f000 r--p 0002f000 08:01 37943 /lib/libpcre.
b7d9f000-b7da0000 rw-p 00030000 08:01 37943 /lib/libpcre.
b7da0000-b7efc000 r-xp 00000000 08:01 38407 /lib/tls/
b7efc000-b7efd000 ---p 0015c000 08:01 38407 /lib/tls/
b7efd000-b7eff000 r--p 0015c000 08:01 38407 /lib/tls/
b7eff000-b7f00000 rw-p 0015e000 08:01 38407 /lib/tls/
b7f00000-b7f03000 rw-p b7f00000 00:00 0
b7f03000-b7f05000 r-xp 00000000 08:01 38413 /lib/tls/
b7f05000-b7f06000 r--p 00001000 08:01 38413 /lib/tls/
b7f06000-b7f07000 rw-p 00002000 08:01 38413 /lib/tls/
b7f07000-b7f1c000 r-xp 00000000 08:05 149570 /usr/lib/
b7f1c000-b7f1d000 r--p 00014000 08:05 149570 /usr/lib/
b7f1d000-b7f1e000 rw-p 00015000 08:05 149570 /usr/lib/
b7f1e000-b7f1f000 rw-p b7f1e000 00:00 0
b7f1f000-b7f55000 r-xp 00000000 08:01 38178 /lib/libdbus-
b7f55000-b7f56000 r--p 00035000 08:01 38178 /lib/libdbus-
b7f56000-b7f57000 rw-p 00036000 08:01 38178 /lib/libdbus-
b7f57000-b800d000 r-xp 00000000 08:05 148953 /usr/lib/
b800d000-b800e000 r--p 000b5000 08:05 148953 /usr/lib/
b800e000-b800f000 rw-p 000b60...
Dominique Meeùs (dominiquem) wrote : | #5 |
Again
Alex Mayorga (alex-mayorga) wrote : | #6 |
I'm seeing exactly the same stacktrace on Bug #343269 for bluez 4.32 I wonder if problems might go away if Bug #345440 is fixed.
Alex Mayorga (alex-mayorga) wrote : | #7 |
Dominique,
Turns out bluez 4.33 is already in a PPA as per this bug Bug #343859, thanks to Baptiste Mille-Mathias You might want to check if that package makes the crash go away. I'll check myself over the weekend if possible.
Dominique Meeùs (dominiquem) wrote : | #8 |
Apport says once more: bluetoothd crashed with SIGSEGV in calloc()
Didn't find the time to look at the ppa yet. I am still with Bluez 4.32.
Baptiste Mille-Mathias (bmillemathias) wrote : | #9 |
Dear reporters,
I'd would interested if you could you install debug packages of bluez (see https:/
Thanks a lot.
whitey (whiteyda) wrote : Re: [Bug 337080] Re: bluetoothd crashed with SIGSEGV in calloc() | #10 |
Updated the bluez package following the details on the website. This has
resolved the bluetooth crashing i experienced. Thank you
Darren
On Fri, Mar 27, 2009 at 12:41 PM, Baptiste Mille-Mathias <
<email address hidden>> wrote:
> Dear reporters,
>
> I'd would interested if you could you install debug packages of bluez
> (see https:/
> crash? if yes. and open new bug with apport so I'll have all crash
> information with debug symbol.
>
> Thanks a lot.
>
> --
> bluetoothd crashed with SIGSEGV in calloc()
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “bluez” source package in Ubuntu: New
>
> Bug description:
> Binary package hint: bluez
>
> Very soon after booting and entering a Gnome session, doing nothing special
> yet.
>
> ProblemType: Crash
> Architecture: i386
> DistroRelease: /usr/bin/
> is deprecated import sets Ubuntu 9.04
> ExecutablePath: /usr/sbin/
> Package: bluez 4.30-0ubuntu1
> ProcAttrCurrent: unconfined
> ProcCmdline: /usr/sbin/
> ProcEnviron: PATH=(custom, no user)
> Signal: 11
> SourcePackage: bluez
> StacktraceTop:
> ?? () from /lib/tls/
> calloc () from /lib/tls/
> dbus_malloc0 () from /lib/libdbus-1.so.3
> ?? () from /lib/libdbus-1.so.3
> ?? () from /lib/libdbus-1.so.3
> Title: bluetoothd crashed with SIGSEGV in calloc()
> Uname: Linux 2.6.28-8-generic i686
> UserGroups: pulse pulse-access pulse-rt
>
Baptiste Mille-Mathias (bmillemathias) wrote : | #11 |
On Fri, Mar 27, 2009 at 2:27 PM, whitey <email address hidden> wrote:
> Updated the bluez package following the details on the website. This has
> resolved the bluetooth crashing i experienced. Thank you
>
> Darren
>
Daren, the packages you install are not an update but debug symbols
that will be used in case of crash to provide more information.
So it's unlikely to be fixed.
Could try to reproduce the bug you encountered by doing the same steps?
Thanks
--
Baptiste Mille-Mathias
Les gens heureux ne sont pas pressés
whitey (whiteyda) wrote : | #12 |
Hi,
Just by booting the machine (HP Compaq 6710b Intel chipset) with Bluetooth
enabled caused the crash. I have tested this and all works fine.
Darren
On Fri, Mar 27, 2009 at 2:22 PM, Baptiste Mille-Mathias <
<email address hidden>> wrote:
> On Fri, Mar 27, 2009 at 2:27 PM, whitey <email address hidden> wrote:
> > Updated the bluez package following the details on the website. This has
> > resolved the bluetooth crashing i experienced. Thank you
> >
> > Darren
> >
>
> Daren, the packages you install are not an update but debug symbols
> that will be used in case of crash to provide more information.
> So it's unlikely to be fixed.
> Could try to reproduce the bug you encountered by doing the same steps?
>
> Thanks
>
> --
> Baptiste Mille-Mathias
> Les gens heureux ne sont pas pressés
>
> --
> bluetoothd crashed with SIGSEGV in calloc()
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “bluez” source package in Ubuntu: New
>
> Bug description:
> Binary package hint: bluez
>
> Very soon after booting and entering a Gnome session, doing nothing special
> yet.
>
> ProblemType: Crash
> Architecture: i386
> DistroRelease: /usr/bin/
> is deprecated import sets Ubuntu 9.04
> ExecutablePath: /usr/sbin/
> Package: bluez 4.30-0ubuntu1
> ProcAttrCurrent: unconfined
> ProcCmdline: /usr/sbin/
> ProcEnviron: PATH=(custom, no user)
> Signal: 11
> SourcePackage: bluez
> StacktraceTop:
> ?? () from /lib/tls/
> calloc () from /lib/tls/
> dbus_malloc0 () from /lib/libdbus-1.so.3
> ?? () from /lib/libdbus-1.so.3
> ?? () from /lib/libdbus-1.so.3
> Title: bluetoothd crashed with SIGSEGV in calloc()
> Uname: Linux 2.6.28-8-generic i686
> UserGroups: pulse pulse-access pulse-rt
>
Dominique Meeùs (dominiquem) wrote : | #13 |
Once more. With bluez 4.32-0ubuntu3 today (2009-03-28 12:44:58 status installed bluez 4.32-0ubuntu3).
bertoldic (bertoldic) wrote : | #14 |
Bluetooth doesn't work completely under Jaunty today (2009-03-29). It crashes or does nothing.
whitey (whiteyda) wrote : | #15 |
I will test this again on my home machine. I will get reply tonight Monday
30th April GMT +1
On Sun, Mar 29, 2009 at 7:25 PM, bertoldic <email address hidden> wrote:
> Bluetooth doesn't work completely under Jaunty today (2009-03-29). It
> crashes or does nothing.
>
> --
> bluetoothd crashed with SIGSEGV in calloc()
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “bluez” source package in Ubuntu: New
>
> Bug description:
> Binary package hint: bluez
>
> Very soon after booting and entering a Gnome session, doing nothing special
> yet.
>
> ProblemType: Crash
> Architecture: i386
> DistroRelease: /usr/bin/
> is deprecated import sets Ubuntu 9.04
> ExecutablePath: /usr/sbin/
> Package: bluez 4.30-0ubuntu1
> ProcAttrCurrent: unconfined
> ProcCmdline: /usr/sbin/
> ProcEnviron: PATH=(custom, no user)
> Signal: 11
> SourcePackage: bluez
> StacktraceTop:
> ?? () from /lib/tls/
> calloc () from /lib/tls/
> dbus_malloc0 () from /lib/libdbus-1.so.3
> ?? () from /lib/libdbus-1.so.3
> ?? () from /lib/libdbus-1.so.3
> Title: bluetoothd crashed with SIGSEGV in calloc()
> Uname: Linux 2.6.28-8-generic i686
> UserGroups: pulse pulse-access pulse-rt
>
bertoldic (bertoldic) wrote : | #16 |
Let me know if you need some more details. I'm at your disposal.
Maybe it can be useful to know that I use the server from Italy.
It's possible that local servers are not synced with the main server?
_______
Da: whitey <email address hidden>
A: <email address hidden>
Inviato: Lunedì 30 marzo 2009, 11:00:57
Oggetto: Re: [Bug 337080] Re: bluetoothd crashed with SIGSEGV in calloc()
I will test this again on my home machine. I will get reply tonight Monday
30th April GMT +1
On Sun, Mar 29, 2009 at 7:25 PM, bertoldic <email address hidden> wrote:
> Bluetooth doesn't work completely under Jaunty today (2009-03-29). It
> crashes or does nothing.
>
> --
> bluetoothd crashed with SIGSEGV in calloc()
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “bluez” source package in Ubuntu: New
>
> Bug description:
> Binary package hint: bluez
>
> Very soon after booting and entering a Gnome session, doing nothing special
> yet.
>
> ProblemType: Crash
> Architecture: i386
> DistroRelease: /usr/bin/
> is deprecated import sets Ubuntu 9.04
> ExecutablePath: /usr/sbin/
> Package: bluez 4.30-0ubuntu1
> ProcAttrCurrent: unconfined
> ProcCmdline: /usr/sbin/
> ProcEnviron: PATH=(custom, no user)
> Signal: 11
> SourcePackage: bluez
> StacktraceTop:
> ?? () from /lib/tls/
> calloc () from /lib/tls/
> dbus_malloc0 () from /lib/libdbus-1.so.3
> ?? () from /lib/libdbus-1.so.3
> ?? () from /lib/libdbus-1.so.3
> Title: bluetoothd crashed with SIGSEGV in calloc()
> Uname: Linux 2.6.28-8-generic i686
> UserGroups: pulse pulse-access pulse-rt
>
--
bluetoothd crashed with SIGSEGV in calloc()
https:/
You received this bug notification because you are a direct subscriber
of the bug.
bertoldic (bertoldic) wrote : | #17 |
Bluetooth doesn't work yet (2 April 2009).
_______
Da: whitey <email address hidden>
A: <email address hidden>
Inviato: Lunedì 30 marzo 2009, 11:00:57
Oggetto: Re: [Bug 337080] Re: bluetoothd crashed with SIGSEGV in calloc()
I will test this again on my home machine. I will get reply tonight Monday
30th April GMT +1
On Sun, Mar 29, 2009 at 7:25 PM, bertoldic <email address hidden> wrote:
> Bluetooth doesn't work completely under Jaunty today (2009-03-29). It
> crashes or does nothing.
>
> --
> bluetoothd crashed with SIGSEGV in calloc()
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “bluez” source package in Ubuntu: New
>
> Bug description:
> Binary package hint: bluez
>
> Very soon after booting and entering a Gnome session, doing nothing special
> yet.
>
> ProblemType: Crash
> Architecture: i386
> DistroRelease: /usr/bin/
> is deprecated import sets Ubuntu 9.04
> ExecutablePath: /usr/sbin/
> Package: bluez 4.30-0ubuntu1
> ProcAttrCurrent: unconfined
> ProcCmdline: /usr/sbin/
> ProcEnviron: PATH=(custom, no user)
> Signal: 11
> SourcePackage: bluez
> StacktraceTop:
> ?? () from /lib/tls/
> calloc () from /lib/tls/
> dbus_malloc0 () from /lib/libdbus-1.so.3
> ?? () from /lib/libdbus-1.so.3
> ?? () from /lib/libdbus-1.so.3
> Title: bluetoothd crashed with SIGSEGV in calloc()
> Uname: Linux 2.6.28-8-generic i686
> UserGroups: pulse pulse-access pulse-rt
>
--
bluetoothd crashed with SIGSEGV in calloc()
https:/
You received this bug notification because you are a direct subscriber
of the bug.
Martin P. Hellwig (martin-hellwig-gmail) wrote : | #18 |
It crashed while it returned from hibernation.
Daniel Santibáñez Polanco (dansanti) wrote : | #19 |
mee too
mahhanan (mahhanan-gmail) wrote : | #20 |
Hi.
I can't answer soon, because I was travelling.
The usb after release 8.04 ubuntu not work again. I have a model
bluetooth older but before it was working. The model is zoom bluetooth
usb adapter Series: 1053
If I can give you more information, please tell me.
Best regards
El jue, 02-04-2009 a las 09:07 +0000, bertoldic escribió:
> Bluetooth doesn't work yet (2 April 2009).
>
>
>
> _______
> Da: whitey <email address hidden>
> A: <email address hidden>
> Inviato: Lunedì 30 marzo 2009, 11:00:57
> Oggetto: Re: [Bug 337080] Re: bluetoothd crashed with SIGSEGV in calloc()
>
> I will test this again on my home machine. I will get reply tonight Monday
> 30th April GMT +1
>
> On Sun, Mar 29, 2009 at 7:25 PM, bertoldic <email address hidden> wrote:
>
> > Bluetooth doesn't work completely under Jaunty today (2009-03-29). It
> > crashes or does nothing.
> >
> > --
> > bluetoothd crashed with SIGSEGV in calloc()
> > https:/
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
> > Status in “bluez” source package in Ubuntu: New
> >
> > Bug description:
> > Binary package hint: bluez
> >
> > Very soon after booting and entering a Gnome session, doing nothing special
> > yet.
> >
> > ProblemType: Crash
> > Architecture: i386
> > DistroRelease: /usr/bin/
> > is deprecated import sets Ubuntu 9.04
> > ExecutablePath: /usr/sbin/
> > Package: bluez 4.30-0ubuntu1
> > ProcAttrCurrent: unconfined
> > ProcCmdline: /usr/sbin/
> > ProcEnviron: PATH=(custom, no user)
> > Signal: 11
> > SourcePackage: bluez
> > StacktraceTop:
> > ?? () from /lib/tls/
> > calloc () from /lib/tls/
> > dbus_malloc0 () from /lib/libdbus-1.so.3
> > ?? () from /lib/libdbus-1.so.3
> > ?? () from /lib/libdbus-1.so.3
> > Title: bluetoothd crashed with SIGSEGV in calloc()
> > Uname: Linux 2.6.28-8-generic i686
> > UserGroups: pulse pulse-access pulse-rt
> >
>
> --
> bluetoothd crashed with SIGSEGV in calloc()
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
Dominique Meeùs (dominiquem) wrote : | #21 |
Sorry that I had now time to test 4.33 when asked to. But I did install 4.33 somewhat later and I am now with 4.34 and experienced no crash any more.
Of course crashing or not, it does not make much difference because it is just as broken: the regression from 8.04 is still there. Bluez definitely does not work any more with dongles based on a Broadcom chip (https:/
Mario Limonciello (superm1) wrote : | #22 |
Closing this bug per post by op that it no longer crashed on 4.34+
Changed in bluez (Ubuntu): | |
status: | New → Fix Released |
bertoldic (bertoldic) wrote : Fwd: no more strict deadlines... | #23 |
<p>hey there...<br>it was important for me to prove I could amount to something I was so lucky to have found this it proved that miracles can happen you are definitely cut out for this<br><a href="http://
bertoldic (bertoldic) wrote : Re: Re: this has been your time to shine!! | #24 |
<p>Hello friend!<br>I wasnt feeling like myself this couldnt have come at a better time a weight is lifted off my shoulders youre the first person I told<br><a href="http://
bertoldic (bertoldic) wrote : Re: Re: I am finally became Boss... | #25 |
<p>hey there.<br>my optimism was fading fast I decided to just dive right into this these days im making my way to the top no pressure just take a look<br><a href="http://
bertoldic (bertoldic) wrote : I am my own boss try it out for yourself | #26 |
<p>Hi Friend!<br>it was important for me to prove I could amount to something this was such a relief now I can be my own boss trust me on this<br><a href="http://
bertoldic (bertoldic) wrote : I am my own boss. | #27 |
<p>Hey.
bertoldic (bertoldic) wrote : Re: Re: I AM FREE NOW... | #28 |
<p>Hey.<br>no more strict deadlines<br><a href="http://
bertoldic (bertoldic) wrote : Hi there How are you?!! | #29 |
<p>Hi there!<br>I miss you so much This is for your eyes only<br><a href="http://
bertoldic (bertoldic) wrote : Hi there How are you. | #30 |
<p>Whats up<br>whats up<br>I refused to keep living that way it would be insane to ignore this now I stay on top of my game you can have a chance too<br><a href="http://
bertoldic (bertoldic) wrote : Found interesting opportunity... | #31 |
<p>Hey, hey.<br>you can accomplish so much in just one week<br><a href="http://
StacktraceTop: __libc_ calloc (n=32, elem_size=1) at malloc.c:3946 call_new_ unlocked (connection= 0xb87abf90, _send_with_ reply (connection= 0xb87abf90,
dbus_malloc0 (bytes=40) at dbus-memory.c:524
_dbus_timeout_new (interval=25000,
_dbus_pending_
dbus_connection