Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BD1F3D8B6 for ; Sat, 30 Jun 2012 20:22:52 +0000 (UTC) Received: (qmail 74882 invoked by uid 500); 30 Jun 2012 20:22:52 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 74817 invoked by uid 500); 30 Jun 2012 20:22:52 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 74808 invoked by uid 99); 30 Jun 2012 20:22:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 Jun 2012 20:22:52 +0000 X-ASF-Spam-Status: No, hits=1.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of hagar.delest@laposte.net does not designate 212.27.42.1 as permitted sender) Received: from [212.27.42.1] (HELO smtp1-g21.free.fr) (212.27.42.1) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 Jun 2012 20:22:44 +0000 Received: from [192.168.1.2] (unknown [83.153.184.98]) by smtp1-g21.free.fr (Postfix) with ESMTP id 2D8CE94013F for ; Sat, 30 Jun 2012 22:22:16 +0200 (CEST) Message-ID: <4FEF5FF7.9020307@laposte.net> Date: Sat, 30 Jun 2012 22:22:15 +0200 From: Hagar Delest User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120612 Thunderbird/14.0 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: [UPDATE SERVICE] proposal to activate the update service for OOo 3.2 and OOo 3.2.1 References: <4FEAD29A.9050300@googlemail.com> <4FEC239A.4000805@googlemail.com> <4FECB96E.90708@laposte.net> <4FECF896.3000106@cfl.rr.com> In-Reply-To: <4FECF896.3000106@cfl.rr.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Le ven. 29 juin 2012 02:36:38 CEST, TJ Frazier a �crit : > Is it really necessary to delete the whole User folder, or is it enough to delete the registrymodifications.xcu file in that folder? AFAIK, the user will lose only the "recent documents" entries for the item on the File menu, but other settings may vanish, too. The keyboard, toolbar, and autotext/autocorrect settings should be preserved. > > If deleting rm.xcu fixes the users' problems, we really should be asking them to attach a copy of the old one to a BZ issue, so somebody can see what's going wrong. > > /tj/ > It seems that deleting the rm.xcu file removes more than I first thought. For example a custom color palette (I usually overwrite the standard.soc by a custom one, with the same name) is reset to standard one. Rather odd. Indeed, you keep the toolbars and keyboard customization but you lose the macros: they are still in the basic folder but they are not referenced anymore in the rm.xcu so you don't see them! So in the end, I'm not sure that removing only the rm.xcu is a true good idea. It may leave bits of old files that could cause troubles later. Following my other topic about frequent crashes, I made some tests and noticed that removing the rm.xcu prevents the crashes (where they used to occur, but I've not checked if they would be back if I had continued with this new rm.xcu file). So rm.xcu may be the key point but it could be a problem with the way it is linked to the content of the profile (a broken reference to a file for example). In the past, there were several configuration files (history, main, ...). They have been merged into a single rm.xcu file. Less easy now to identify what is the part that is the culprit. I fear that uploading just the rm.xcu file would not be enough, especially if the problem is with a link with another part of the profile. Hagar