From owner-freebsd-ports@FreeBSD.ORG Sat Jan 10 20:56:05 2009 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B088E1065672 for ; Sat, 10 Jan 2009 20:56:05 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157]) by mx1.freebsd.org (Postfix) with ESMTP id 3C3678FC16 for ; Sat, 10 Jan 2009 20:56:04 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so3375190fgb.35 for ; Sat, 10 Jan 2009 12:56:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=Ivn3B+Fq2pjdgnffI86AkhUMsueDqqIlGhLge2xHgfI=; b=Fo7XYUSJcemevdzEiSInMWpuDlOCVw3i58IuRWtNYrSUaiuYThPM3X9OIFI7igmpBp ULT/Hx1SfY4WR7K/eYmwAC4Ms2tWfgPc3bCmz5QJ1gOmSseCkbD5uzj7Rhgn+GNkIwwO ApDUrdK0wWoTmXQKKuZkLoru3hjgZyVRQKfuk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=AmFhnE+dB9T6UdTE5EGQoTldrqEPSA8ensihbiyCLULCTSOdfqlpr+dlMiEZvbOSUP 5lhrAFrleawLh8vGs43SF0J+X5XS5ZsjCcGH5jLcik/ziRbSxblqiQ56BfigrejXsOiv kCzfd0yVQ6s1C8dcbp4mfHdr/woAYPLPqhCE0= Received: by 10.86.84.5 with SMTP id h5mr15667519fgb.59.1231620964134; Sat, 10 Jan 2009 12:56:04 -0800 (PST) Received: by 10.86.23.16 with HTTP; Sat, 10 Jan 2009 12:56:04 -0800 (PST) Message-ID: <3f1fd1ea0901101256y126c7c69rea04e3222ffa8363@mail.gmail.com> Date: Sat, 10 Jan 2009 21:56:04 +0100 From: "Michal Varga" To: "Doug Barton" In-Reply-To: <4968FE90.6040807@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3f1fd1ea0901101039j69b09b18s44650cbe3bbca45b@mail.gmail.com> <4968FE90.6040807@FreeBSD.org> Cc: ports@freebsd.org Subject: Re: gnome-session 2.24 (upstream) mess X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jan 2009 20:56:06 -0000 On Sat, Jan 10, 2009 at 9:01 PM, Doug Barton wrote: > Michal Varga wrote: >> Hello guys, >> I noticed that Gnome 2.24 was commited today along with gnome-session >> 2.24, so I need to ask - how did FreeBSD Gnome team decide to deal >> with the recent session management ... > > FYI we don't use that kind of language on our lists. > > In any case it seems something like this should be in the pkg-message > so that users are aware. > > Doug > You're right, I apologize for the somewhat improper language, It's been just stuck in my head since I've been debugging this behaviour for a friend and came across the whole issue, then immediately started tearing my hair out (obviously, I'm a heavy session user too). The whole situation made quite a number of people angry, and not just because of missing "my windows won't pop back when i relog". With this, uhm, politely said, regression (at least on Ubuntu where I've been pointed to to check it), fully gnome-aware applications now simply crash when you log out of Gnome (take with a grain of salt - I didn't check if they are actually sig-terminated, or if they shut themselves semi-correctly when X server terminates, or anything deeper). But the outcome is that the next time you log back and restart your applications manually, you get a nice show of "It seems that Galeon crashed last time, It seems that Evolution crashed last time, poink, poink, poink..". Or if you have an application with unsaved changes or crunching some data, it is not able to prevent logout and it's closed (with a hammer) too. The whole situation makes one want to cry, some online discussions about it are a pretty nice evidence of that. Still you are right, I'll watch my language next time and prevent any similar slips. (And, Jeremy - I'm sorry I didn't take part in testing this particular release from MarcusCom, I've been doing it for years and somewhat grew too lazy over time.. At least you can be sure you will definitely have one tester back for 2.26 :) m.