[Bug 615374] Re: Atop should have a /etc/default/atop file
+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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615374 Title: Atop should have a /etc/default/atop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atop/+bug/615374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 615374] Re: Atop should have a /etc/default/atop file
+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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615374 Title: Atop should have a /etc/default/atop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atop/+bug/615374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189063] Re: f-spot full crash upon startup
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. Disabling color management in f-spot seems preferable to disabling it system wide as suggested here by Jasper van der Neut ** Bug watch added: Red Hat Bugzilla #903022 https://bugzilla.redhat.com/show_bug.cgi?id=903022 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189063 Title: f-spot full crash upon startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/1189063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189063] Re: f-spot full crash upon startup
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 console. ~~~ [Info 04:23:02.657] Initializing Mono.Addins Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated. (f-spot:15551): GLib-GObject-WARNING **: Attempt to add property __gtksharp_8_FSpot_Widgets_CellRendererTextProgress::value after class was initialised (f-spot:15551): GLib-GObject-WARNING **: Attempt to add property __gtksharp_8_FSpot_Widgets_CellRendererTextProgress::text after class was initialised Object reference not set to an instance of an object System.NullReferenceException: Object reference not set to an instance of an object at FSpot.Widgets.PhotoImageView.LoadErrorImage (System.Exception e) [0x0] in :0 at FSpot.Widgets.PhotoImageView.HandlePhotoItemChanged (System.Object sender, FSpot.Core.BrowsablePointerChangedEventArgs args) [0x0] in :0 at (wrapper delegate-invoke) :invoke_void__this___object_BrowsablePointerChangedEventArgs (object,FSpot.Core.BrowsablePointerChangedEventArgs) at FSpot.Core.BrowsablePointer.SetIndex (Int32 value, IBrowsableItemChanges changes) [0x0] in :0 at FSpot.Core.BrowsablePointer.HandleCollectionChanged (IBrowsableCollection collection) [0x0] in :0 at (wrapper delegate-invoke) :invoke_void__this___IBrowsableCollection (FSpot.Core.IBrowsableCollection) at (wrapper delegate-invoke) :invoke_void__this___IBrowsableCollection (FSpot.Core.IBrowsableCollection) at FSpot.PhotoQuery.RequestReload () [0x0] in :0 at FSpot.QueryWidget.Close () [0x0] in :0 at FSpot.MainWindow.UpdateFindByTagMenu () [0x0] in :0 at FSpot.MainWindow..ctor (FSpot.Database.Db db) [0x0] in :0 at FSpot.App.get_Organizer () [0x0] in :0 at FSpot.App.HandleOrganize () [0x0] in :0 at FSpot.App.Organize () [0x0] in :0 at FSpot.Driver.Startup () [0x0] in :0 at Hyena.Gui.CleanRoomStartup.Startup (Hyena.Gui.StartupInvocationHandler startup) [0x0] in :0 (f-spot:15551): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping the last reference. ~~~ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189063 Title: f-spot full crash upon startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/1189063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189063] Re: f-spot full crash upon startup
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189063 Title: f-spot full crash upon startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/1189063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787802] Re: Update Manager hangs waiting for response to apt-listchanges hidden under Details
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 confirmed that setting APT_LISTCHANGES_FRONTEND=none in the environment on the comand line before running apt-listchanges correctly inhibits the display. I've also confirmed that the APT_LISTCHANGES_FRONTEND variable is not is not in the environement of the pager in the details panel. I found it interesting, and a little disturbing that I could get a root shell from the pager in this situation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787802 Title: Update Manager hangs waiting for response to apt-listchanges hidden under Details To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-listchanges/+bug/787802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
