From: Bastien Nocera <hadess@hadess.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] bluez-gnome access volatile while adapter-changed
Date: Mon, 10 Mar 2008 23:29:20 +0000 [thread overview]
Message-ID: <1205191760.30595.1.camel@cookie.hadess.net> (raw)
In-Reply-To: <20080310143609.exuwdzs9gk4w48ss@wmlab.csie.ncu.edu.tw>
On Mon, 2008-03-10 at 14:36 +0800, Ming-I Hsieh wrote:
> Hi, all
>
> This is a patch for this bug. This bug adddress at
> bluetooth-device-select.c. While the dongle could be removed/inserted,
> the gnome-applet may crash due to access a 0x0 priv.
Good catch, but wrong fix, as we shouldn't even be listening to that
signal anymore. If you could please test the patch I uploaded at:
http://bugzilla.gnome.org/show_bug.cgi?id=519791#c4
I'll post it here for Marcel to apply if it fixes the problem for you.
Cheers
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-03-10 23:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 6:36 [Bluez-devel] [PATCH] bluez-gnome access volatile while adapter-changed Ming-I Hsieh
2008-03-10 23:29 ` Bastien Nocera [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-11 2:29 Ming-I Hsieh
2008-03-11 18:35 ` Bastien Nocera
2008-03-12 21:04 ` Marcel Holtmann
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=1205191760.30595.1.camel@cookie.hadess.net \
--to=hadess@hadess.net \
--cc=bluez-devel@lists.sourceforge.net \
/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