Bug#391592: compiz-core: compiz crashes my X server
On Wed, Jun 06, 2007 at 09:19:19PM +0200, Brice Goglin wrote: Hi, Does this crash of the Xserver when running compiz still occurs nowadays? With latest compiz 0.5.0 and xserver-xorg-core 1.3 currently in unstable? With the compiz/xorg in etch, it works without crashing. So it seems the bug was meanwhile fixed. Thanks, --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#391592: compiz-core: compiz crashes my X server
Device Identifier radeon Driver radeon Option DRI on EndSection Section Monitor Identifier LCD monitor HorizSync 28-50 VertRefresh 43-75 Option DPMS EndSection Section Monitor Identifier Clone monitor HorizSync 28-50 VertRefresh 43-75 Option DPMS #Option BIOSHotkeys on # werkt niet Option MergedFB on Option MonitorLayout LVDS, CRT Option MetaModes 1400x1050 1280x1024 1024x768 800x600 640x480 #Option OverlayOnCRT2 true # werkt niet Option CRT2Hsync 50-75 Option CRT2VRefresh 50-82 EndSection Section Monitor Identifier Clone640 monitor HorizSync 28-50 VertRefresh 43-75 Option DPMS #Option BIOSHotkeys on # werkt niet Option MergedFB on Option MonitorLayout LVDS, CRT Option MetaModes 640x480 #Option OverlayOnCRT2 true # werkt niet Option CRT2Hsync 50-75 Option CRT2VRefresh 50-82 EndSection Section Monitor Identifier Xin800 monitor HorizSync 28-50 VertRefresh 43-75 Option DPMS Option MergedFB on Option MonitorLayout LVDS, CRT Option CRT2Position RightOf Option MetaModes 1400x1050-800x600 800x600 Option MergedNonRectangular true Option CRT2Hsync 50-75 Option CRT2VRefresh 50-82 EndSection Section Monitor Identifier Xin1024 monitor HorizSync 28-50 VertRefresh 43-75 Option DPMS Option MergedFB on Option MonitorLayout LVDS, CRT Option CRT2Position RightOf Option MetaModes 1400x1050-1024x768 1024x768 Option MergedNonRectangular true Option CRT2Hsync 50-75 Option CRT2VRefresh 50-82 EndSection Section Monitor Identifier Xin1400 monitor HorizSync 28-50 VertRefresh 43-75 Option DPMS Option MergedFB on Option MonitorLayout LVDS, CRT Option CRT2Position RightOf Option MetaModes 1400x1050-1400x1050 1400x1050 #Option MergedNonRectangular true # Not needed Option CRT2Hsync 50-75 Option CRT2VRefresh 50-82 EndSection Section Screen Identifier LCD Device radeon Monitor LCD monitor DefaultDepth24 SubSection Display Depth 24 Modes 1400x1050 EndSubSection EndSection Section Screen Identifier Clone Device radeon Monitor Clone monitor DefaultDepth24 SubSection Display Depth 24 Modes 1400x1050 1280x1024 1024x768 800x600 640x350 640x480 640x400 512x384 400x300 320x240 320x200 EndSubSection EndSection Section Screen Identifier Clone640 Device radeon Monitor Clone640 monitor DefaultDepth24 SubSection Display Depth 24 Modes 640x480 EndSubSection EndSection Section Screen Identifier Xin800 Device radeon Monitor Xin800 monitor DefaultDepth24 SubSection Display Virtual 2200 1050 Depth 24 Modes 1400x1050 800x600 EndSubSection EndSection Section Screen Identifier Xin1024 Device radeon Monitor Xin1024 monitor DefaultDepth24 SubSection Display Virtual 2424 1050 Depth 24 Modes 1400x1050 1024x768 EndSubSection EndSection Section Screen Identifier Xin1400 Device radeon Monitor Xin1400 monitor DefaultDepth24 SubSection Display Virtual 2800 1050 Depth 24 Modes 1400x1050 EndSubSection EndSection Section DRI Mode0666 EndSection Section ServerLayout Identifier Default Layout InputDevice Generic Keyboard InputDevice Configured Mouse Option AIGLX true #Screen LCD Clone Xin800 Xin1024 Xin1400 Screen LCD EndSection Section Extensions Option Composite enable EndSection -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#391592: compiz-core: compiz crashes my X server
On Sun, Oct 15, 2006 at 05:19:10PM +0200, Thierry Reding wrote: Yes, compiz-core should depend on xserver-xorg-core (= 2:1.1.1-9). Can you try that version and see if the problem persists? My system (Thinkpad T41 with radeon9000) locks up hard (not even sysrq works, only 4 seconds of power button). The only thing I see after compiz --replace is: libGL warning: 3D driver claims to not support visual 0x4b. However, I think by now this is not anymore the same bug as the original reporter reported. --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: xfree86_4.1.0-16woody4_alpha.changes REJECTED
(replying to my own mail at gun^Wflamethrower-point) On Mon, Oct 18, 2004 at 03:02:47PM +0200, Jeroen van Wolffelaar wrote: On Mon, Oct 18, 2004 at 07:44:29AM -0500, Branden Robinson wrote: Is there a FAQ somewhere that will tell me why I always get REJECTED mails from katie after submitting security-fixed packages to the Debian Security Team? I get one for each architecture. I seem to remember asking Debian Installer [EMAIL PROTECTED] before, but never getting an answer. The problem is that stable-security is a separate archive, and requires a sourceful upload. Give the '-sa' option to dpkg-buildpackage to overrule the heuristic that says only -1 and -0 packages need to have their source included. Branden Robinson told me that however he did prepare the upload, it was his understanding that the security team would not use it as-is, but rebuild it. They didn't, and due to Branden's assumption, he didn't think he needed to follow the guidelines specific to how exactly to dpkg-buildpackage the upload for security updates. Also see http://www.debian.org/doc/developers-reference/ch-pkgs#s-bug-security which says to simply mail updated packages to the security team, and to not normally upload them yourself. So it was the security team who uploaded Branden's packages as-is. Sorry for assuming wrong, but something like this is uncheckable as the signature was Branden's. A subsection of this section has also the answer to your question: | Unless the upstream source has been uploaded to security.debian.org | before (by a previous security update), build the upload with full | upstream source (dpkg-buildpackage -sa). If there has been a previous | upload to security.debian.org with the same upstream version, you may | upload without upstream source (dpkg-buildpackage -sd). This text is by the way incomplete. It should say If there has been a previous upload ... same upstream version _since the latest point release_, you may upload without upstream source. Or even better, just change it to 'always use -sa', as having multiple security updates for one package between the same point releases is rare, and even if so, the extra bandwidth used during upload is neglectible (and it can't hurt). --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl
Re: xfree86_4.1.0-16woody4_alpha.changes REJECTED
On Mon, Oct 18, 2004 at 07:44:29AM -0500, Branden Robinson wrote: Is there a FAQ somewhere that will tell me why I always get REJECTED mails from katie after submitting security-fixed packages to the Debian Security Team? I get one for each architecture. I seem to remember asking Debian Installer [EMAIL PROTECTED] before, but never getting an answer. The problem is that stable-security is a separate archive, and requires a sourceful upload. Give the '-sa' option to dpkg-buildpackage to overrule the heuristic that says only -1 and -0 packages need to have their source included. Also see http://www.debian.org/doc/developers-reference/ch-pkgs#s-bug-security which says to simply mail updated packages to the security team, and to not normally upload them yourself. A subsection of this section has also the answer to your question: | Unless the upstream source has been uploaded to security.debian.org | before (by a previous security update), build the upload with full | upstream source (dpkg-buildpackage -sa). If there has been a previous | upload to security.debian.org with the same upstream version, you may | upload without upstream source (dpkg-buildpackage -sd). --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl
