On Mon, Jan 16, 2012 at 11:44:43AM +0100, Antoine Jacoutot wrote:
> On Mon, Jan 16, 2012 at 09:46:47AM +1100, Brett wrote:
> > Hi,
> >
> > After updating to -current on 8th Jan, I noticed that whenever I mounted a
> > usb memory stick formatted as msdos, gvfsd-trash would get out of control
> >
On Mon, Jan 16, 2012 at 09:46:47AM +1100, Brett wrote:
> Hi,
>
> After updating to -current on 8th Jan, I noticed that whenever I mounted a
> usb memory stick formatted as msdos, gvfsd-trash would get out of control and
> chew up all available cpu (top shows it starting about 2% or something sma
On 01/15/12 23:46, Brett wrote:
> Hi,
>
> After updating to -current on 8th Jan, I noticed that whenever I mounted a
> usb memory stick formatted as msdos, gvfsd-trash would get out of control and
> chew up all available cpu (top shows it starting about 2% or something small
> then steadily cli
>
> >After updating to -current on 8th Jan, I noticed that whenever I mounted a
> >usb memory stick formatted as msdos, >gvfsd-trash would get out of control
> >and chew up all available cpu (top shows it starting about 2% or something
> >>small then steadily climbing). This would stop if I use
>After updating to -current on 8th Jan, I noticed that whenever I mounted a usb
>memory stick formatted as msdos, >gvfsd-trash would get out of control and
>chew up all available cpu (top shows it starting about 2% or something >small
>then steadily climbing). This would stop if I use top to ki
Hi,
After updating to -current on 8th Jan, I noticed that whenever I mounted a usb
memory stick formatted as msdos, gvfsd-trash would get out of control and chew
up all available cpu (top shows it starting about 2% or something small then
steadily climbing). This would stop if I use top to kill
