+1
I'd also be very happy to provide a patch for this. It's only a few
lines.
My concern is with adjusting the frequency of polling in daemon mode.
There's not many other settings of interest for daemon mode.
I agree that /etc/default/atop is the right spot for this.
--
You received this bug
+1
I'd also be very happy to provide a patch for this. It's only a few
lines.
My concern is with adjusting the frequency of polling in daemon mode.
There's not many other settings of interest for daemon mode.
I agree that /etc/default/atop is the right spot for this.
--
You received this bug
See also https://bugzilla.redhat.com/show_bug.cgi?id=903022 which looks
to be the same bug.
Salient points are that it's fixed upstream, and there's a patch there
for f-spot which disables the loading of cms profiles, intended as an
interim measure till Stephen Shaw works out a release for the fix
uninstalling colord as in #6 doesn't seem to work for me. I'm not
entirely clear whether this is a new bug though.
I renamed .config/f-spot, and then ran f-spot and got the following.
f-spot is able to get as far as putting the error in a dialog this time,
though the text below is from the consol
Stephen, can we have an update on this? It seems to me that if we don't
have a fix, then we should roll back to a working version if that's
possible? Or is this about interaction with other components which have
changed?
--
You received this bug notification because you are a member of Ubuntu
B
I'm amazed that this bug has persisted so long. apt-listchanges is a useful
add-on, but if it breaks major functionality (ie update-manager) and there's no
energy to fix it, then apt-listchanges should be removed from the repositories.
I'm affected by this bug. I'm running oneiric.
I've confi
