From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <lakostis@anti-leasure.ru>
Date: Mon, 20 Jun 2005 18:26:15 +0400
From: "Konstantin A. Lepikhov" <lakostis@anti-leasure.ru>
To: ALT Linux Sisyphus discussion list <sisyphus@altlinux.ru>
Message-ID: <20050620142615.GB8994@lks.home>
Mail-Followup-To: ALT Linux Sisyphus discussion list <sisyphus@altlinux.ru>
References: <200506201003.48401.ru_classic@gts.lg.ua>
Mime-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <200506201003.48401.ru_classic@gts.lg.ua>
X-Operation-System: ALT Linux Sisyphus (20050611) 2.6.11-wks26-up-alt4
User-Agent: Mutt/1.5.8+cvs20050213i
X-Virus-Scanned: by amavisd-new at smtp.elektrostal.ru
Subject: [sisyphus] Re:
	=?koi8-r?b?8M/TzMUg0M/TzMXEzsXHzyDPws7P18zFzsnRINPUwcwg0MHE?=
	=?koi8-r?b?wdTY?= Firefox
X-BeenThere: sisyphus@altlinux.ru
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ALT Linux Sisyphus discussion list <sisyphus@altlinux.ru>
List-Id: ALT Linux Sisyphus discussion list <sisyphus.altlinux.ru>
List-Unsubscribe: <https://lists.altlinux.ru/mailman/listinfo/sisyphus>,
	<mailto:sisyphus-request@altlinux.ru?subject=unsubscribe>
List-Archive: <http://lists.altlinux.ru/pipermail/sisyphus>
List-Post: <mailto:sisyphus@altlinux.ru>
List-Help: <mailto:sisyphus-request@altlinux.ru?subject=help>
List-Subscribe: <https://lists.altlinux.ru/mailman/listinfo/sisyphus>,
	<mailto:sisyphus-request@altlinux.ru?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2005 14:35:55 -0000
Archived-At: <http://lore.altlinux.org/sisyphus/20050620142615.GB8994@lks.home/>
List-Archive: <http://lore.altlinux.org/sisyphus/>

Hi Alexander!

Monday 20, at 10:03:48 AM you wrote:

<skip>
> The error was 'BadShmSeg (invalid shared segment parameter)'.
>   (Details: serial 288 error_code 168 request_code 145 minor_code 2)
>   (Note to programmers: normally, X errors are reported asynchronously;
>    that is, you will receive the error a while after causing it.
>    To debug your program, run it with the --sync command line
>    option to change this behavior. You can then get a meaningful
>    backtrace from your debugger if you break on the gdk_x_error() 
> function.)
> 
> Кто-нибудь с таким столкнулся или это мне не повезло?
странно, у меня подобного не замечено. На днях будет обновление
FF/TB/mozilla, есть мысль, что поможет.

-- 
WBR, Konstantin	      chat with ==>ICQ: 109916175
     Lepikhov,	      speak  to ==>JID: lakostis@jabber.org
aka L.A. Kostis       write  to ==>mailto:lakostis@pisem.net.nospam

...The information is like the bank... 			  (c) EC8OR