From: Stefan Seyfried <seife@suse.de>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluez3.30 audio/serial plugin issue
Date: Sat, 12 Apr 2008 12:13:26 +0200 [thread overview]
Message-ID: <48008B46.3080601@suse.de> (raw)
In-Reply-To: <E673024B-BC5B-44C7-806D-38CA69FD680E@holtmann.org>
Marcel Holtmann wrote:
> it seems the solution to this is to use --enable-glib. For some reason =
> our eglib plugin loader doesn't work always. I never saw this problem =
> and still can't reproduce it.
If you want to debug it, i could e.g. provide you with a qemu image of
openSUSE FACTORY where it is reproducible.
OTOH, if eglib is going away anyway, maybe there are more important things =
to
debug ;-)
-- =
Stefan Seyfried
R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg | "Well, surrounding them's out."
This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG N=FCrnberg)
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference =
Don't miss this year's exciting event. There's still time to save $100. =
Use priority code J8TL2D2. =
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/java=
one
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-04-12 10:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 8:33 [Bluez-users] bluez3.30 audio/serial plugin issue dong yan
2008-04-11 8:44 ` Marcel Holtmann
2008-04-12 10:13 ` Stefan Seyfried [this message]
2008-04-12 20:02 ` Marcel Holtmann
2008-04-15 18:07 ` Stefan Seyfried
2008-04-15 3:26 ` dong yan
-- strict thread matches above, loose matches on Subject: below --
2008-04-14 11:13 Jimmi
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=48008B46.3080601@suse.de \
--to=seife@suse.de \
--cc=bluez-users@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