From: Bastien Nocera <hadess@hadess.net>
To: Stanislav Brabec <sbrabec@suse.cz>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] bluez-gnome: Fix crash on pairing request of known rfcomm device
Date: Thu, 10 Sep 2009 16:21:44 +0100 [thread overview]
Message-ID: <1252596104.23937.1329.camel@localhost.localdomain> (raw)
In-Reply-To: <1252595415.3430.17.camel@hammer.suse.cz>
On Thu, 2009-09-10 at 17:10 +0200, Stanislav Brabec wrote:
> Attached patch fixes crash after access attempt to the device configured
> in rfcomm.conf, but not yet paired.
>
> How to reproduce:
>
> 1. Configure an unknown RFCOMM device that requires authentication in
> rfcomm.conf (e. g. mobile phone).
> 2. run pppd on /dev/rfcomm1
>
> Behavior:
> - Pairing request on mobile phone
> - Crash of bluetooth-applet on desktop
>
> The patch fixes only the crash, not the error completely (at least in
> version 1.8). Behavior after the fix:
> - Pairing request on mobile phone, then ask for PIN
> - No reaction on desktop
Fixed the same bug in gnome-bluetooth.
Cheers
prev parent reply other threads:[~2009-09-10 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 15:10 [PATCH] bluez-gnome: Fix crash on pairing request of known rfcomm device Stanislav Brabec
2009-09-10 15:21 ` Bastien Nocera [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1252596104.23937.1329.camel@localhost.localdomain \
--to=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sbrabec@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox