On Thu, 2010-02-25 at 16:58 -0800, Dan Williams wrote:
> Hmm, doesn't ring a bell immediately. I pushed a fix for the driver
> thing and am doing another NM build for F11. I'll try to take a look at
> this after the new build goes through.
Even when using the latest build from koji [*], NetworkM
On Thu, 2010-02-25 at 21:38 -0300, Bernie Innocenti wrote:
> On Thu, 2010-02-25 at 14:11 -0300, Bernie Innocenti wrote:
> > Feb 25 17:01:30 xo-37-38-0f NetworkManager: *** START
> > **
> > Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 0:
> > Net
On Thu, 2010-02-25 at 14:11 -0300, Bernie Innocenti wrote:
> Feb 25 17:01:30 xo-37-38-0f NetworkManager: *** START
> **
> Feb 25 17:01:30 xo-37-38-0f NetworkManager: Frame 0:
> NetworkManager(nm_logging_backtrace+0x45) [0x8078da5]
> Feb 25 17:01:30
On Mon, 2010-02-22 at 12:08 -0300, Bernie Innocenti wrote:
> On Thu, 2010-02-18 at 09:55 -0800, Dan Williams wrote:
> > It'll probably take more investigation than I have time for this week,
> > so I'll just patch NM to accept the invalid driver name ('usb') as a
> > fallback. Which is the behavio
On Thu, 2010-02-18 at 09:55 -0800, Dan Williams wrote:
> It'll probably take more investigation than I have time for this week,
> so I'll just patch NM to accept the invalid driver name ('usb') as a
> fallback. Which is the behavior that 0.7.2 had anyway, so you can
> consider it a regression in 0
On Wed, 2010-02-17 at 22:44 -0300, Bernie Innocenti wrote:
> On Wed, 2010-02-17 at 11:08 -0800, Dan Williams wrote:
> > On Wed, 2010-02-17 at 10:20 -0300, Bernie Innocenti wrote:
> > > On Mon, 2010-02-15 at 16:15 -0800, Dan Williams wrote:
> > > > Not a known issue; but I'll try to reproduce on min
On Wed, 2010-02-17 at 11:08 -0800, Dan Williams wrote:
> On Wed, 2010-02-17 at 10:20 -0300, Bernie Innocenti wrote:
> > On Mon, 2010-02-15 at 16:15 -0800, Dan Williams wrote:
> > > Not a known issue; but I'll try to reproduce on mine. Unless Daniel
> > > gets there first of course.
> >
> > I retr
On Wed, 2010-02-17 at 10:20 -0300, Bernie Innocenti wrote:
> On Mon, 2010-02-15 at 16:15 -0800, Dan Williams wrote:
> > Not a known issue; but I'll try to reproduce on mine. Unless Daniel
> > gets there first of course.
>
> I retrieved the log:
I was able to reproduce the issue as well. The pro
On Mon, 2010-02-15 at 16:15 -0800, Dan Williams wrote:
> Not a known issue; but I'll try to reproduce on mine. Unless Daniel
> gets there first of course.
I retrieved the log:
Feb 17 13:12:29 xo-58-2d-7a kernel: [ 1395.246555] usb 2-4: reset high speed
USB device using ehci_hcd and address 11
F
On Mon, 2010-02-15 at 20:17 -0300, Bernie Innocenti wrote:
> We didn't collect the logs in the field, but in /var/log/messages we
> found an assertion failure from NM which was more or less like "driver !
> = NULL", just after logging something about the OLPC mesh device.
> Wireless wasn't working
We didn't collect the logs in the field, but in /var/log/messages we
found an assertion failure from NM which was more or less like "driver !
= NULL", just after logging something about the OLPC mesh device.
Wireless wasn't working at all afterwards.
The broken package is NetworkManager-0.7.2.995-
11 matches
Mail list logo
