* Dan Williams
>> [serial]
>> baud=115200
>
> I don't think we require the serial setting anymore? I could be wrong,
> but if we do, we should remove that requirement. ISTR doing that patch
> a few years ago.
Perhaps not. What I did to get that config was to boot up a F18-live
with GNOME, crea
On Sun, 2013-03-03 at 19:05 +0100, Tore Anderson wrote:
> * Dan Williams
>
> > You can always create the connections manually in the config files, and
> > we should add some pieces to the connection editor to support manual
> > creation/addition/deletion of Bluetooth connections.
>
> Thanks for c
* Dan Williams
> You can always create the connections manually in the config files, and
> we should add some pieces to the connection editor to support manual
> creation/addition/deletion of Bluetooth connections.
Thanks for confirming this. After some fiddling around, I managed to
find a config
On Sun, 2013-03-03 at 09:50 +0100, Tore Anderson wrote:
> I'm sorry to blow the dust off this old thread, but yesterday I ran into
> the exact same problem as Nick Peskett did, and Google eventually led me
> to this thread. Removing the check in questeion works, however, if
> possible I'd like to r
I'm sorry to blow the dust off this old thread, but yesterday I ran into
the exact same problem as Nick Peskett did, and Google eventually led me
to this thread. Removing the check in questeion works, however, if
possible I'd like to run the distro version of NM rather than a patched one.
* Dan Wi
On Tue, 2012-10-23 at 13:24 +0200, Aleksander Morgado wrote:
> On 23/10/12 12:15, Nick Peskett wrote:
> > If this is the case could memcmp(ip_iface, "rfcomm", 6) also be added to
> > the condition? This might allow generic unclaimed bluetooth modems to
> > still work.
>
> That memcmp() is quite eq
On 23/10/12 12:15, Nick Peskett wrote:
> If this is the case could memcmp(ip_iface, "rfcomm", 6) also be added to
> the condition? This might allow generic unclaimed bluetooth modems to
> still work.
That memcmp() is quite equivalent to just comparing the driver with
"bluetooth" as we did before.
On 23/10/2012 10:33, Aleksander Morgado wrote:
Currently when a modem device registered by Blueman is connected,
NetworkManager reports that there is no associated bluetooth device.
The if statement responsible for this ought to be reporting an error and
returning if the driver is named, but n
> Currently when a modem device registered by Blueman is connected,
> NetworkManager reports that there is no associated bluetooth device.
>
> The if statement responsible for this ought to be reporting an error and
> returning if the driver is named, but not named "bluetooth".
>
> Unfortunately
Currently when a modem device registered by Blueman is connected,
NetworkManager reports that there is no associated bluetooth device.
The if statement responsible for this ought to be reporting an error and
returning if the driver is named, but not named "bluetooth".
Unfortunately, the true
10 matches
Mail list logo
