From owner-freebsd-x11@FreeBSD.ORG Mon Dec 5 11:07:13 2011 Return-Path: Delivered-To: freebsd-x11@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C655106567A for ; Mon, 5 Dec 2011 11:07:13 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1A0F78FC12 for ; Mon, 5 Dec 2011 11:07:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pB5B7C1v081379 for ; Mon, 5 Dec 2011 11:07:12 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pB5B7Cf6081377 for freebsd-x11@FreeBSD.org; Mon, 5 Dec 2011 11:07:12 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 5 Dec 2011 11:07:12 GMT Message-Id: <201112051107.pB5B7Cf6081377@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-x11@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-x11@FreeBSD.org X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2011 11:07:13 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/162592 x11 [patch] update x11-drivers/xf86-video-ati to 6.14.3 o ports/161480 x11 [patch] x11/luit: don't depend on pty(4), use openpty( o ports/161021 x11 [patch] x11/xkeyboard-config: orphaned dirs when WITHO o ports/160968 x11 [patch] ports/x11/libXi broken manpages o ports/160963 x11 [patch] x11/bigreqsproto: disable specs p ports/160357 x11 x11/dri2proto port update o ports/160354 x11 x11-drivers/xf86-video-intel29 port update o ports/159792 x11 [patch] USB HID devices support for x11-drivers/xf86-i o ports/158529 x11 [patch] x11-servers/xorg-server: conditionalize --with o ports/158513 x11 Broken Xvideo in x11-drivers/xf86-video-intel drivers o ports/157282 x11 [MAINTAINER PATCH] net/xrdp: effective login name is n o ports/156949 x11 x11-drivers/xf86-video-ati 6.14.1 produce black blank f ports/156424 x11 8.2R xrandr & xf86-video-intel & xorg-server packages o ports/156405 x11 x11-drivers/xf86-video-ati driver: no hardware renderi o ports/156369 x11 x11-drivers/xf86-video-vmware: DPI value wrong calcula o ports/156368 x11 x11-drivers/xf86-video-vmware: pwcview does not work o ports/156042 x11 x11/xorg hang in combination with KWin-Tiling o ports/155696 x11 [patch] x11-servers/xorg-server: chase AIGLX altered d o ports/155683 x11 x11/xdm [patch] Enabling IPv6 support breaks IPv4 o ports/154651 x11 [PATCH] graphics/dri: make it possible to choose which f ports/154510 x11 [patch] x11/xorg: xorg servers have Motif-crippling bu o ports/154502 x11 x11/xdm authorization failure when used with E17 windo o ports/154449 x11 x11/xorg: missing manpage (7) Xsecurity o ports/154423 x11 x11-drivers/xf86-video-radeonhd: radeon xorg driver ca o ports/153593 x11 graphics/dri: clutter segfault, something to do with i o ports/153495 x11 x11-drivers/xf86-video-ati wavy line problem for lenov o ports/153358 x11 x11-drivers/xf86-video-intel: Intel driver freeze with o ports/152159 x11 [hang] xorg/x11: X11 freezes with Intel Mobile 965 and o ports/151596 x11 x11/xorg: wacom bamboo button 1 no longer works o ports/150633 x11 x11-servers/xorg-server: KVM switching causing X serve o ports/150155 x11 x11/xorg hangs after xrandr(1) usage o ports/149743 x11 x11/xorg: garbled window since Xorg-7.5 o ports/149636 x11 x11/xorg: buffer overflow in pci_device_freebsd_read_r o ports/148591 x11 information note for x11-drivers/xf86-input-synaptics o ports/148444 x11 [hang] x11-drivers/xf86-video-intel: intel driver free f ports/148340 x11 x11-drivers/xf86-video-neomagic: unresolved symbol xf8 o ports/147318 x11 [Patch]graphics/libdrm:Fix the PLIST when define WITHO o ports/147149 x11 x11/xorg: Xorg 7.5 hangs o ports/146460 x11 x11/xorg: crash after upgrade to v7.5 with radeon driv o ports/146321 x11 x11/libSM picks the wrong uuid.h o ports/146256 x11 x11/xorg does fails to start after upgrade from 7.4 to o ports/145649 x11 x11/xorg: X server crashes when starting opengl compos o ports/142069 x11 x11/xorg: After adding on a laptop Toshiba Sattelite L o ports/141660 x11 x11/xorg: X can't determine amount of video memory on o ports/139011 x11 [patch] Add options to support GLX TLS in x11-servers o ports/135276 x11 x11/xorg: GUI running first time only while using Free o ports/134132 x11 x11-servers/xorg-server: Intel i845 - xorg.conf with U o ports/131930 x11 [PATCH] x11-servers/xorg-server coredumps on exit o ports/131726 x11 x11-servers/xorg-server: xorg server messes with my eh s kern/130478 x11 [request] Port Linux kernel stub of nouveau to FreeBSD o ports/122830 x11 x11/xorg: Error in I830WaitLpRing() o ports/120947 x11 x11/xsm ignores system.xsm and .xsmstartup s ports/117907 x11 x11-servers/mga_hal broken on 7.0-BETA (GLIBC error) 53 problems total. From owner-freebsd-x11@FreeBSD.ORG Mon Dec 5 16:19:15 2011 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F09E106564A for ; Mon, 5 Dec 2011 16:19:15 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id C89798FC13 for ; Mon, 5 Dec 2011 16:19:14 +0000 (UTC) Received: by ywp17 with SMTP id 17so6322366ywp.13 for ; Mon, 05 Dec 2011 08:19:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=uzZkbKp1+l2xeP3r9ZOQiMUc2WBubAi/UnDRrCfE1bA=; b=Gll8G3sYoIH5eNTSh821mKeiE3evj+5K74I1B/ELxinWYvwyDFlihs1D3o4lFTbdG9 ZX0eEq3lS1r8qvUFw9RaWHvHvFcl4OhqCEl67MqMQ1GqM7tw7azoxElp3kQ8IUUlhC9D qb8pS4CSizJdqLblv9fddAqlKd/yHFuuSpuzE= MIME-Version: 1.0 Received: by 10.50.181.202 with SMTP id dy10mr9135538igc.14.1323101953364; Mon, 05 Dec 2011 08:19:13 -0800 (PST) Received: by 10.43.50.193 with HTTP; Mon, 5 Dec 2011 08:19:13 -0800 (PST) Date: Mon, 5 Dec 2011 11:19:13 -0500 Message-ID: From: Aryeh Friedman To: freebsd-x11@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: How to get x_window_t for a give window ID in libxcb X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2011 16:19:15 -0000 I am asking this here because I can not think of a better place (if there is let me know): Using the code at http://www.javakb.com/Uwe/Forum.aspx/java-programmer/21292/Getting-X11-window-idas a model I have made it so I can get the ID of any Java created window.... I also know how to set event masks and such... what I don't know is how to tie them together namely I need to find a lib/function that will give me back the x_window_t for that window and then allow me to modify the event mask From owner-freebsd-x11@FreeBSD.ORG Tue Dec 6 16:47:13 2011 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF6101065670 for ; Tue, 6 Dec 2011 16:47:13 +0000 (UTC) (envelope-from zeus@relay.ibs.dn.ua) Received: from relay.ibs.dn.ua (relay.ibs.dn.ua [91.216.196.25]) by mx1.freebsd.org (Postfix) with ESMTP id 46C718FC14 for ; Tue, 6 Dec 2011 16:47:12 +0000 (UTC) Received: from relay.ibs.dn.ua (localhost [127.0.0.1]) by relay.ibs.dn.ua with ESMTP id pB6GSpcA054612 for ; Tue, 6 Dec 2011 18:28:51 +0200 (EET) Received: (from zeus@localhost) by relay.ibs.dn.ua (8.14.4/8.14.4/Submit) id pB6GSo8Q054610 for freebsd-x11@freebsd.org; Tue, 6 Dec 2011 18:28:50 +0200 (EET) Date: Tue, 6 Dec 2011 18:28:50 +0200 From: Zeus V Panchenko To: freebsd-x11@freebsd.org Message-ID: <20111206162850.GB10565@relay.ibs.dn.ua> Mail-Followup-To: freebsd-x11@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 8.1-RELEASE X-Editor: GNU Emacs 23.2.1 X-Face: iVBORw0KGgoAAAANSUhEUgAAACoAAAAqBAMAAAA37dRoAAAAFVBMVEWjjoiZhHDWzcZuW1U wOT+RcGxziJxEN0lIAAABrklEQVQokV2STXLbMAyFQaraE3a5dzSTfR1IF7CQrM3QuECn9z9DH0 gxzgSyFvr88PBD0uJxoR6BE+e8LtRgohE5ZB50sODP/REbfUnte/z12+llCekLUSKenFIMke6Be WinE8H0RJHSN71rUQp64gFDmtDDhRk0zam3FzpNVFprhwPGaFo6oY9wDBJQ9Qz6EuKyROJjDGa+ uza4VOTa8iHlN58Yv5BF9+4BGl0LA5pUD5xKXg4aQlVZm0co3NKxCGxQpu3aC352Gv3DZONmwQd tkrlaylV3YSew7bWtwAZF/zi9jblmprPoL7ktzeFSxmarVNmWRi+Bmxg7Y7tbGtR8XZUxLTo86G thANsssetjp3POuBvMBRlw6jRa5pKN7yVlP+F2lyiZGSMf5hnSU6eAVupmtfjRcxy0momwpxDnz 06hwnOWvBnUdR8U2/KX7cq26u1Jy5xFZMPOVONRbRUrwey8Qar6cWgf12xSymQuVX0DfYd4R8kN Hg0qCtLeaYZcj8B90M2N0cEX1P0vKSxw7NLy/3X8Qeriusu66jNA37P4Mn5QRTG2hz4d9D/6E3a EX852nwAAAABJRU5ErkJggg== Subject: is Radeon HD 6300 supported? X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: zeus@ibs.dn.ua List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2011 16:47:14 -0000 Hi, may somebody answer, please, wheather Radeon HD 6300 based cards supported on FreeBSD? i'm thinking of Samsung 305U1Z-A01 notebook it is AMD dual core E450 APU based 11" notebook ubuntu 11.10 x86 (live cd) recognizes videocard but it mentions KMS in the log file ... so i'm wondering, may FreeBSD see the card ... -- Zeus V. Panchenko JID:zeus@gnu.org.ua GMT+2 (EET) From owner-freebsd-x11@FreeBSD.ORG Tue Dec 6 16:55:52 2011 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B373E1065670 for ; Tue, 6 Dec 2011 16:55:52 +0000 (UTC) (envelope-from akirchhoff135014@comcast.net) Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [76.96.62.64]) by mx1.freebsd.org (Postfix) with ESMTP id 787588FC15 for ; Tue, 6 Dec 2011 16:55:52 +0000 (UTC) Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta07.westchester.pa.mail.comcast.net with comcast id 5rD81i00N27AodY57svsrg; Tue, 06 Dec 2011 16:55:52 +0000 Received: from memory.visualtech.com ([50.78.52.49]) by omta19.westchester.pa.mail.comcast.net with comcast id 5svs1i00L13hoka3fsvsGh; Tue, 06 Dec 2011 16:55:52 +0000 Date: Tue, 6 Dec 2011 11:55:50 -0500 From: Adam K Kirchhoff To: zeus@ibs.dn.ua Message-ID: <20111206115550.65635e08@memory.visualtech.com> In-Reply-To: <20111206162850.GB10565@relay.ibs.dn.ua> References: <20111206162850.GB10565@relay.ibs.dn.ua> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.4; x86_64-slackware-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-x11@freebsd.org Subject: Re: is Radeon HD 6300 supported? X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2011 16:55:52 -0000 On Tue, 6 Dec 2011 18:28:50 +0200 Zeus V Panchenko wrote: > Hi, > > may somebody answer, please, wheather Radeon HD 6300 based cards > supported on FreeBSD? > > i'm thinking of Samsung 305U1Z-A01 notebook > > it is AMD dual core E450 APU based 11" notebook > > ubuntu 11.10 x86 (live cd) recognizes videocard but it mentions KMS in > the log file ... so i'm wondering, may FreeBSD see the card ... > > -- > Zeus V. Panchenko Only the vesa driver will work with that GPU on FreeBSD. There are a few HD6xxx GPUs that fall into the Everygreen code name, which are supported by xf86-video-ati without any 2D or 3D acceleration, but that particular one seems to be a Caicos chipset, which will not work with xf86-video-ati without KMS. Adam From owner-freebsd-x11@FreeBSD.ORG Fri Dec 9 19:35:06 2011 Return-Path: Delivered-To: x11@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D245510656DB for ; Fri, 9 Dec 2011 19:35:06 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from portsmonj.FreeBSD.org (portsmonj.freebsd.org [69.147.83.46]) by mx1.freebsd.org (Postfix) with ESMTP id C4B158FC21 for ; Fri, 9 Dec 2011 19:35:06 +0000 (UTC) Received: from portsmonj.freebsd.org (portsmonj.freebsd.org [69.147.83.46]) by portsmonj.FreeBSD.org (8.14.4/8.14.4) with ESMTP id pB78SgwI066372 for ; Wed, 7 Dec 2011 08:28:42 GMT (envelope-from linimon@FreeBSD.org) Date: Wed, 7 Dec 2011 08:28:42 GMT Message-Id: <201112070828.pB78SgwI066372@portsmonj.FreeBSD.org> From: linimon@FreeBSD.org To: x11@FreeBSD.org Cc: Subject: FreeBSD ports that you maintain which are currently marked broken X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: portmgr-feedback@FreeBSD.org List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2011 19:35:06 -0000 Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 7.x/8.x/9.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: x11-drivers/xf86-input-citron broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-drivers&portname=xf86-input-citron portname: x11-drivers/xf86-input-fpit broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-drivers&portname=xf86-input-fpit If these errors are ones that you are already aware of, please accept our apologies and ignore this message. On the other hand, if you no longer wish to maintain this port (or ports), please reply with a message stating that, and accept our thanks for your efforts in the past. Every effort has been made to make sure that these error reports really do correspond to a port that you maintain. However, due to the fact that this is an automated process, it may indeed generate false matches. If one of these errors fits that description, please forward this email to the author of this software, Mark Linimon , so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD.