On Mon, Mar 01, 2010 at 10:58:57PM +0100, Nicola Mfb wrote:
> On Mon, Mar 1, 2010 at 10:19 PM, Ben Thompson wrote:
> [...]
> > I can reproduce this problem using NWA but I am not sure what is going
> > on at the D-Bus level. Maybe someone could help me (maybe Niko)?
>
> You may try to produce a w
On Mon, Mar 01, 2010 at 01:36:01PM +0300, Paul Fertser wrote:
> Ben Thompson writes:
> > On Sun, Feb 28, 2010 at 01:52:01PM +0200, Timo Juhani Lindfors wrote:
> >> Ben Thompson writes:
> >> > I will see if I can reliably reproduce the problem and submit a bug
> >> > report if there isn't one (whe
On Mon, Mar 1, 2010 at 10:19 PM, Ben Thompson wrote:
[...]
> I can reproduce this problem using NWA but I am not sure what is going
> on at the D-Bus level. Maybe someone could help me (maybe Niko)?
You may try to produce a wpa_supplicant.conf with the exact parameters
you see in nwa.conf, and st
On Mon, Mar 01, 2010 at 01:36:01PM +0300, Paul Fertser wrote:
> No, this backtrace of yours is entirely different. Please file a
> ticket preferrably with a way to reproduce it. Or at least be ready to
> test patches. I hope i can make the oops you report go away, but i
> need some way to test the
Ben Thompson writes:
> On Sun, Feb 28, 2010 at 01:52:01PM +0200, Timo Juhani Lindfors wrote:
>> Ben Thompson writes:
>> > I will see if I can reliably reproduce the problem and submit a bug
>> > report if there isn't one (where should I do this?).
>>
>> http://bugs.openmoko.org is the place for
On Sun, Feb 28, 2010 at 01:52:01PM +0200, Timo Juhani Lindfors wrote:
> Ben Thompson writes:
> > I will see if I can reliably reproduce the problem and submit a bug
> > report if there isn't one (where should I do this?).
>
> http://bugs.openmoko.org is the place for kernel bugs. Set the
> compon
Ben Thompson writes:
> I will see if I can reliably reproduce the problem and submit a bug
> report if there isn't one (where should I do this?).
http://bugs.openmoko.org is the place for kernel bugs. Set the
component to "System Software", an example bug:
http://docs.openmoko.org/trac/ticket/23
On Sat, Feb 27, 2010 at 09:54:16PM +0300, Paul Fertser wrote:
> Nicola Mfb writes:
> > On Fri, Feb 26, 2010 at 12:17 PM, Ben Thompson wrote:
> > [...]
> >> I think this is a different bug. It happens occasionally with me too,
> >> but it was also there with the old QT libs. Niko - are you aware o
Nicola Mfb writes:
> On Fri, Feb 26, 2010 at 12:17 PM, Ben Thompson wrote:
> [...]
>> I think this is a different bug. It happens occasionally with me too,
>> but it was also there with the old QT libs. Niko - are you aware of
>> this problem?
>
> If you are talking about complete system freeze i
On Fri, Feb 26, 2010 at 12:17 PM, Ben Thompson wrote:
[...]
> I think this is a different bug. It happens occasionally with me too,
> but it was also there with the old QT libs. Niko - are you aware of
> this problem?
If you are talking about complete system freeze it happens to mee too
sometimes
On Fri, Feb 26, 2010 at 11:39:39AM +0100, n...@el-hennig.de wrote:
>
>
> > Martin fixed qt builds (thanks again), and Ben just reported that NWA
> > works again after upgrading.
>
> It starts up, yes. But when I close nwa I have to reboot my FR as it does not
> react on any input by pressing th
> Martin fixed qt builds (thanks again), and Ben just reported that NWA
> works again after upgrading.
It starts up, yes. But when I close nwa I have to reboot my FR as it does not
react on any input by pressing the power button.
--
n...@el-hennig.de
Great News!!!
d
On Fri, Feb 26, 2010 at 12:25 AM, Nicola Mfb wrote:
> On Mon, Feb 15, 2010 at 3:34 PM, Davide Scaini wrote:
> > yes..
> > you have to use qt libs from noko repos dalle libqt* 4.4.3-r3 (while in
> shr
> > repos you find 4.6.0-r14.1.4).
> > It's a problem in cflgs when compiling q
On Mon, Feb 15, 2010 at 3:34 PM, Davide Scaini wrote:
> yes..
> you have to use qt libs from noko repos dalle libqt* 4.4.3-r3 (while in shr
> repos you find 4.6.0-r14.1.4).
> It's a problem in cflgs when compiling qts on shr... nicola (the developer
> of nwa) is aware of this, and shr guys I think
On 15 February 2010 14:22, Ben Thompson wrote:
> Hi
>
> I recently installed NWA on latest SHR-U and it fails to start up with
> the following error :-
>
> "Fatal Error: Cannot parse configuration file error occurred while
> parsing element on line 1, column 1"
[...]
> r...@om-gta02 /usr/share/nwa
Just to share my experience:
- i made i /etc/opkg folder with only arch.conf and noko-feed
- removed alla qt libs
- opkg update and installed nwa
-restored standard opkg folder and when i upgrade i upgrade all except qt
libs...
this is the "only" (?) way of having nwa working on shr atm. For me it
On Mon, Feb 15, 2010 at 03:34:28PM +0100, Davide Scaini wrote:
> yes..
> you have to use qt libs from noko repos dalle libqt* 4.4.3-r3 (while in shr
> repos you find 4.6.0-r14.1.4).
> It's a problem in cflgs when compiling qts on shr... nicola (the developer of
> nwa) is aware of this, and shr guys
yes..
you have to use qt libs from noko repos dalle libqt* 4.4.3-r3 (while in shr
repos you find 4.6.0-r14.1.4).
It's a problem in cflgs when compiling qts on shr... nicola (the developer
of nwa) is aware of this, and shr guys I think too...
d
On Mon, Feb 15, 2010 at 3:22 PM, Ben Thompson wrote:
Hi
I recently installed NWA on latest SHR-U and it fails to start up with
the following error :-
"Fatal Error: Cannot parse configuration file error occurred while
parsing element on line 1, column 1"
I checked that /usr/share/nwa/defaultconfiguration.xml exists and it
looks fine to me :-
r..
19 matches
Mail list logo