retitle 648673 gconf2: Add NEWS entry logout and -in needed after upgrade quit
Am Montag, den 14.11.2011, 16:39 +0100 schrieb Vincent Lefevre: > On 2011-11-14 15:27:04 +0100, Josselin Mouette wrote: > > Have you tried logging out and in again? The upgrade cannot, > > unfortunately, be conducted in a way that lets new applications in a > > running session work correctly. > > The problem disappears after logging out and in again. I just confirmed this on my system too. > This is the kind of information that the user would like to know > (to avoid doing the upgrade at the wrong time and to know that these > kinds of errors are expected), possibly before upgrading. Perhaps > the NEWS file would be the right place (new entries are displayed by > apt-listchanges). If the machine has only one user (who is also the > admin), he should see it; otherwise the admin can warn his users. Josselin picked up that idea. Thank you! Thanks, Paul PS: Unfortunately I did not get all responses. To keep threading people could use `bts show --mbox 648673` from package `devscripts` to import the messages from the report and reply explicitly to a message their also ensuring correct threading.
signature.asc
Description: This is a digitally signed message part
