Received: by 10.101.6.17 with SMTP id j17mr809511ani.55.1270992986340;
        Sun, 11 Apr 2010 06:36:26 -0700 (PDT)
Received: by 10.101.6.17 with SMTP id j17mr809510ani.55.1270992986280;
        Sun, 11 Apr 2010 06:36:26 -0700 (PDT)
Return-Path: <3V9DBSxAKADUTfUVjZkV-efiVgcpXffXcV....@codesite.bounces.google.com>
Received: from mail-gx0-f239.google.com (mail-gx0-f239.google.com [209.85.217.239])
        by gmr-mx.google.com with ESMTP id 11si281570gxk.13.2010.04.11.06.36.25;
        Sun, 11 Apr 2010 06:36:25 -0700 (PDT)
Received-SPF: pass (google.com: domain of 3V9DBSxAKADUTfUVjZkV-efiVgcpXffXcV....@codesite.bounces.google.com designates 209.85.217.239 as permitted sender) client-ip=209.85.217.239;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of 3V9DBSxAKADUTfUVjZkV-efiVgcpXffXcV....@codesite.bounces.google.com designates 209.85.217.239 as permitted sender) smtp.mail=3V9DBSxAKADUTfUVjZkV-efiVgcpXffXcV....@codesite.bounces.google.com; dkim=pass (test mode) header...@google.com
Received: by gxk17 with SMTP id 17so45642gxk.2
        for <xaos-devel@googlegroups.com>; Sun, 11 Apr 2010 06:36:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=beta;
        h=domainkey-signature:mime-version:x-generated-by
         :x-googlecode-project:x-googlecode-issue-id:received:message-id:date
         :subject:from:to:content-type;
        bh=wxtsSQJHrj4qn5ppNdrlbGmuQ7X6NRNn4y2RuxbhqXU=;
        b=i5ksyCDeoGNqpvfnGGw9FuTzGBOXX9MbbTHBLggN7Mge7NHUn913/xWZKmNSRJcbRb
         G7M8fa8A4JdSKUmCEsiw==
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=google.com; s=beta;
        h=mime-version:x-generated-by:x-googlecode-project
         :x-googlecode-issue-id:message-id:date:subject:from:to:content-type;
        b=xJ34pII9r39y7LuR6rmiVqygotNGCGRktMqymtzKdh9RCcMEjEde9Cql9zURrA+SjU
         7moDElBWMZomrRAW9YPg==
MIME-Version: 1.0
X-Generated-By: Google Code
X-GoogleCode-Project: gnuxaos
X-GoogleCode-Issue-Id: 48
Received: by 10.101.94.4 with SMTP id w4mr806522anl.53.1270992983136; Sun, 11 
	Apr 2010 06:36:23 -0700 (PDT)
Message-ID: <0-13201895609069124626-6080557357899609380-codesite-noreply=google....@googlecode.com>
Date: Sun, 11 Apr 2010 13:36:23 +0000
Subject: Issue 48 in gnuxaos: [PATCH] Crash when window manager forces XaoS to 
	a larger size then expected
From: codesite-nore...@google.com
To: xaos-devel@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 48 by ans...@43-1.org: [PATCH] Crash when window manager forces  
XaoS to a larger size then expected
http://code.google.com/p/gnuxaos/issues/detail?id=48

XaoS (3.2) would crash when the window manager forces XaoS to a larger
size then requested at startup.  This can happen when using a tiling
window manager such as awesome, ion3, ...

The attached patch has been introduced in Debian to solve this issue.
Please consider applying it in the next release (it should apply to the
3.5 sources).

See also http://bugs.debian.org/452284 for the original bug report.

Regards,
Ansgar


--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings