Comment 14 for bug 374397
Revision history for this message
| thomas richard (thomas-g-richard) wrote Re: [Bug 374397] Re: console-kit-daemon: glibgobject warning value location for gachararray passed as null | #14 |
guiliker a écrit :
> Hi,
>
> I found this on a google search and the description above very
> accurately describes what is happening to my newly upgraded to Jaunty
> box, what with the beeps and too quickly disappearing warning window.
> I'm just curious as to why this is still happening if a fix has been
> released through ubuntu repo's?
>
> This is an extract of syslog:
> Oct 27 02:53:36 ub-j console-
> Oct 27 02:53:36 ub-j last message repeated 8 times
> Oct 27 02:53:36 ub-j init: tty4 main process (2145) killed by TERM signal
> Oct 27 02:53:36 ub-j init: tty5 main process (2146) killed by TERM signal
> Oct 27 02:53:36 ub-j init: tty2 main process (2153) killed by TERM signal
> Oct 27 02:53:36 ub-j init: tty3 main process (2154) killed by TERM signal
> Oct 27 02:53:36 ub-j init: tty6 main process (2155) killed by TERM signal
> Oct 27 02:53:36 ub-j init: tty1 main process (3151) killed by TERM signal
> Oct 27 02:53:38 ub-j kernel: [ 6853.917246] mtrr: no MTRR for 40000000,10000000 found
> Oct 27 02:53:39 ub-j nm-system-settings: SCPlugin-Ifupdown: devices removed (udi: /org/freedeskto
> Oct 27 02:53:43 ub-j bluetoothd[2815]: bridge pan0 removed
> Oct 27 02:53:43 ub-j bluetoothd[2815]: Stopping SDP server
> Oct 27 02:53:43 ub-j bluetoothd[2815]: Exit
> Oct 27 02:53:43 ub-j exiting on signal 15
>
>
A very good question indeed !
I was wondering about it myself.
I can tell you that I don't have this bug anymore since my upgrade to
the beta version of karmic koala (though maybe it hasn't been solved for
all types of computers).
So all you have to do is wait for october the 29th and upgrade to Ubuntu
9.10 that day.