On 3/18/08, Sjoerd Simons <[EMAIL PROTECTED]> wrote: > reassign 471317 network-manager > > On Tue, Mar 18, 2008 at 03:12:59AM +0100, Michael Biebl wrote: > > reassign 471317 libglib2.0-0 > > thanks > > > > Zitat von Neutron Soutmun <[EMAIL PROTECTED]>: > > > >> Confirm, downgrading the libglib to 2.14.6-1 and also 2.16.1-1 fix this > >> problem. > >> > > > > Thanks for the confirmation. Seems like > > 80_static-mutex-aliasing-warnings.patch breaks g_mutex_lock on amd64. > > Reassigning to libglib2.0-0. > > That patch can't break locking for NM. As Sebastien mentioned earlier, the > changes can only ever have effect when you compile against the new glib. We > need to debug this more on network-manager's side before starting to blame > glib. > > I've made some debs[0] which should fix the dbus errors we're seeing in the > NM > logs. Which may or may not fix this issue, but it definately fixes some > memory > corruption. (I couldn't test this because i don't have machines with kill > switches though...) > > So please everyone who can reproduce it, try these debs.. And if it still > fails > send in new NM logs :) > > Sjoerd > 0: http://beast.luon.net/~sjoerd/NM/
Sorry, I'm not sure, what's the actually problem. I only test, follow the others' comments that downgrading the libglib to prior version and it's work. Now I test your debs[0], the error message has gone and also fixes the problem :) Thanks (Sjoerd Simons <[EMAIL PROTECTED]>) for this patch, Best regards, Neutron Soutmun -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
