From: David Woodhouse <dwmw2@infradead.org>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [PATCH] Check return code of pin helper.
Date: Tue, 29 Apr 2003 07:47:13 +0100 [thread overview]
Message-ID: <1051598832.2850.189.camel@imladris.demon.co.uk> (raw)
In-Reply-To: <5.1.0.14.2.20030428145348.106adde0@unixmail.qualcomm.com>
On Mon, 2003-04-28 at 22:55, Max Krasnyansky wrote:
> You said that bluepin still doesn't work even if you fix libfontconfig.
> Do you know why ?
Not really -- it's a fontconfig or pango bug. If $HOME is set to
"/somewhere/bogus" it works, if $HOME is NULL it doesn't.
Sounds like a failure to get a filename for a user config file is having
a more fatal effect than getting a potential filename but not being able
to open it, or something like that.
> btw I want to replace Python bluepin script with a little gtk app in
> later versions of bluez-utils.
OK.
--
dwmw2
-------------------------------------------------------
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
next prev parent reply other threads:[~2003-04-29 6:47 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
2003-04-29 6:47 ` David Woodhouse [this message]
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=1051598832.2850.189.camel@imladris.demon.co.uk \
--to=dwmw2@infradead.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=maxk@qualcomm.com \
/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;
as well as URLs for NNTP newsgroup(s).