Linux bluetooth development
 help / color / mirror / Atom feed
From: Max Krasnyansky <maxk@qualcomm.com>
To: David Woodhouse <dwmw2@infradead.org>, bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [PATCH] Check return code of pin helper.
Date: Mon, 28 Apr 2003 14:55:37 -0700	[thread overview]
Message-ID: <5.1.0.14.2.20030428145348.106adde0@unixmail.qualcomm.com> (raw)
In-Reply-To: <1051448314.2850.181.camel@imladris.demon.co.uk>

At 05:58 AM 4/27/2003, David Woodhouse wrote:
>On Sun, 2003-04-27 at 11:50, David Woodhouse wrote:
>> On Red Hat 9, the python interpreter segfaults when running bluepin if
>> hcid is started from the init script, but it all works fine if hcid was
>> started from a command prompt. This confuses me,
>
>This no longer confuses me. It's a fontconfig bug when there's no 'HOME'
>in the environment. Fixing the segfault in libfontconfig leaves bluepin
>still not working -- although setting $HOME to something bogus _does_
>work. I've worked around it in bluepin in the bluez-utils-2.3-4 package
>which should be in rawhide some time soon.

You said that bluepin still doesn't work even if you fix libfontconfig.
Do you know why ?

btw I want to replace Python bluepin script with a little gtk app in
later versions of bluez-utils.

Max



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2003-04-28 21:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-27 10:50 [Bluez-devel] [PATCH] Check return code of pin helper David Woodhouse
2003-04-27 12:58 ` David Woodhouse
2003-04-28 21:55   ` Max Krasnyansky [this message]
2003-04-29  6:47     ` David Woodhouse
2003-04-29 21:04     ` David Woodhouse

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=5.1.0.14.2.20030428145348.106adde0@unixmail.qualcomm.com \
    --to=maxk@qualcomm.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=dwmw2@infradead.org \
    /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