From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26212 invoked by alias); 29 May 2007 19:22:15 -0000 Received: (qmail 26174 invoked by uid 48); 29 May 2007 19:22:06 -0000 Date: Tue, 29 May 2007 19:22:00 -0000 Message-ID: <20070529192206.26173.qmail@sourceware.org> From: "kris dot van dot hees at oracle dot com" To: frysk-bugzilla@sourceware.org In-Reply-To: <20070529185302.4562.kris.van.hees@oracle.com> References: <20070529185302.4562.kris.van.hees@oracle.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug general/4562] Editing a session name causes a new session to be created X-Bugzilla-Reason: AssignedTo Mailing-List: contact frysk-bugzilla-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: frysk-bugzilla-owner@sourceware.org X-SW-Source: 2007-q2/txt/msg00244.txt.bz2 List-Id: ------- Additional Comments From kris dot van dot hees at oracle dot com 2007-05-29 19:22 ------- Problem is that sessions are stored under their names, so when you change the name of the session using the edit functionality of the druid, and close the druid, it triggers a save of the current session, which causes it to get saved under the new name. The session manager acts as if the session was renamed, but in reality (in the underlying fs representation of sessions) a new one got created. So, when you start frysk again, it now finds both. When you chamge the name, the session under the new name ought to be automatically deleted at the time of saving the session under its new name. You can't really do it prior to the save of the new session information, because a crash or deliberate abort of frysk would leave you without even the old version of the session. -- http://sourceware.org/bugzilla/show_bug.cgi?id=4562 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.