GNOME Bugzilla – Bug 716915
Fix EditingHostPage
Last modified: 2017-02-08 11:16:42 UTC
---- Reported by jim@yorba.org 2010-12-10 17:43:00 -0800 ---- Original Redmine bug id: 2951 Original URL: http://redmine.yorba.org/issues/2951 Searchable id: yorba-bug-2951 Original author: Jim Nelson Original description: We've often had to dive back in to the full-window page to fix various problems which have cropped up due to how EditingHostPage interacts with the other pages in the system. Often the bugs have to do with the page the user originated from (i.e. double-clicked on) going away or changing state out from under the full-window page. I've been thinking about how to redesign the operation of EditingHostPage that I believe will solve many of these problems, or at least minimize the fragility of the system. I'd like to attack this soon, as we seem to have to Band-Aid up this page at least once every release. --- Bug imported by chaz@yorba.org 2013-11-25 21:48 UTC --- This bug was previously known as _bug_ 2951 at http://redmine.yorba.org/show_bug.cgi?id=2951 Unknown Component Using default product and component set in Parameters Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one. Resolution set on an open status. Dropping resolution
Thanks for taking the time to report this. However, you are using a version that is too old and not supported anymore by GNOME developers. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes by GNOME developers for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME. Please feel free to reopen this bug report if the problem still occurs with a recent version of GNOME, or feel free to report this bug in the bug tracking system of your Linux distribution if your distribution still supports the version that you are using.