Processed: Bug#452983: xserver-xorg: X server doesn't start per 'Modes' setting in xorg.conf
Processing commands for [EMAIL PROTECTED]: tags 452983 +wontfix Bug#452983: xserver-xorg: X server doesn't start per 'Modes' setting in xorg.conf There were no tags set. Tags added: wontfix thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452983: xserver-xorg: X server doesn't start per 'Modes' setting in xorg.conf
tags 452983 +wontfix thank you Modes is the old deprecated way to specificy modes. With RandR 1.2 drivers (you're using ati 6.7.196), the way to specify modes is ModeLine+PreferredMode in the Monitor section. Details in section III.5. of http://wiki.debian.org/XStrikeForce/HowToRandR12 I am marking this as wontfix for now. Note that Modes should still work for old-style drivers. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445553: Correction: xserver-xorg-video-sis: X crashes from various openGL programs with DRI
html /html Date: Sun, 25 Nov 2007 23:36:51 +0100 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Bug#445553: Correction: xserver-xorg-video-sis: X crashes from various openGL programs with DRI Matthew Gibson wrote: I finally managed to network and run ssh, and here is some of what I found. This is while running xscreensaver sundancer2. When my system was crashed, top displayed: Xorg was using about 45% of my cpu, and a normal amount of memory. Sundancer2 was using about 45% of my cpu, and a normal amount of memory sshd was using about .5% CPU mpd (music player deamon, which was playing music) was using about 4% of CPU top was using about 1% of CPU. I found that I couldn't kill either sundancer or Xorg unless I used the -s KILL signal. dmesg showed no additional messages when my computer was crashed, and no messages had been sent to Xorg.0.log I could still run stuff through ssh fine, just Xorg and the offending program were hung up. No output was made to the screen, and no keyboard input was received. (A But I could still kill programs and start (non-graphical) programs in ssh.) I could kill sundancer2, and then Xorg sat on 95 % of my processor, still accomplishing nothing. I then tried killing Xorg. It shutsdown, my screen flashed blank, and then top showed it started up again, under a new PID. Again, it sat on 95 % of my resources, and was still frozen. Is it better with xserver-xorg-video-sis 1:0.9.3-6 from unstable? (or at least the one from testing) Brice Hi, I appreciate that someones still working on this. I tried installing xserver-xorg-video-sis from unstable, but, as far as I remember, I had issues because I would have had to upgrade many more components of xserver-xorg in order to upgrade xserver-xorg-video-sis. And I have limited internet access (only sometimes, and I shouldn't download too much.) However, I am no longer using that computer, and I am now using one that has an nvidia driver. Thanks again for looking taking the time to look at it. Matthew _ R U Ready for Windows Live Messenger Beta 8.5? Try it today! http://entertainment.sympatico.msn.ca/WindowsLiveMessenger
Bug#445553: Correction: xserver-xorg-video-sis: X crashes from various openGL programs with DRI
Matthew Gibson wrote: Hi, I appreciate that someones still working on this. I tried installing xserver-xorg-video-sis from unstable, but, as far as I remember, I had issues because I would have had to upgrade many more components of xserver-xorg in order to upgrade xserver-xorg-video-sis. And I have limited internet access (only sometimes, and I shouldn't download too much.) However, I am no longer using that computer, and I am now using one that has an nvidia driver. Do you mean that you will never use it again and thus won't ever be able to test/debug anything regarding this bug report? If so, should I close the bug then? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#448845: dpkg-reconfigure xserver-xorg fails
On Tue, Nov 27, 2007 at 08:44:47AM +0100, Brice Goglin wrote: Do you still have this problem with latest xserver-xorg? (1:7.3+6 is in unstable, 1:7.3+7 just got uploaded there too). Problem still exists with 1:7.3+6 : dexconf: error: cannot generate configuration file; xserver-xorg/config/device/driver not set. Aborting. Reconfigure the X server with dpkg-reconfigure to correct this problem. Also, the dpkg-reconfigure xserver-xorg process fails to detect my monitor (A Samsung Syncmaster 710T). Or at least I presume that it fails to do so: after the attempt at autodetection I end up being asked to give the full monitor specs regardless. The Xserver detects the monitor just fine as far as I can see from the logs. Should I file a separate bug? Looks like not all of 1:7.3+7 has arrived yet. I'll try it when it becomes available. It may be relevant that this machine has been pretty much continually upgraded for the last six or seven years, mostly tracking unstable. It's not exactly a fresh install of Debian ;) Phil -- http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#448845: dpkg-reconfigure xserver-xorg fails
On Tue, Nov 27, 2007 at 09:48:54AM +, Philip Armstrong wrote: On Tue, Nov 27, 2007 at 08:44:47AM +0100, Brice Goglin wrote: Do you still have this problem with latest xserver-xorg? (1:7.3+6 is in unstable, 1:7.3+7 just got uploaded there too). Problem still exists with 1:7.3+6 : dexconf: error: cannot generate configuration file; xserver-xorg/config/device/driver not set. Aborting. Reconfigure the X server with dpkg-reconfigure to correct this problem. Also, the dpkg-reconfigure xserver-xorg process fails to detect my monitor (A Samsung Syncmaster 710T). Or at least I presume that it fails to do so: after the attempt at autodetection I end up being asked to give the full monitor specs regardless. The Xserver detects the monitor just fine as far as I can see from the logs. Should I file a separate bug? Looks like not all of 1:7.3+7 has arrived yet. I'll try it when it becomes available. OK, just done an update dragged in 1:7.3+7. Problem still exists. Just to test things, I tried removing the debconf config.dat cache file, so as to get all the defaults from the new package, but it didn't make any difference. Oh wait: I've found the problem! I didn't have discover installed (it was doing annoying things to my machine in the past) and this wasn't being picked up anywhere. Installing discover fixes the problem. Looks like the configuration needs to be aware of whether discover is installed or not, since it's currently a 'recommends' not a 'depends'. cheers, Phil -- http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443157: xserver-xorg-video-intel: Hard crashes when starting torus-trooper game
Hello, On Nov 25, 2007 11:05 PM, Brice Goglin [EMAIL PROTECTED] wrote: Sorry for the late reply, you seem to be experiencing a GPU lockup. It is very hard to debug. Can you reproduce this bug easily? Even with intel driver 2.2 which entered unstable recently? If so, please send the corresponding log, I will forward the bug upstream. I don't seem to have run across these problems recently, so it seems it has been fixed with the 2.2 version. However, I find that this version is extraordinary slow : when switching desks, to arrive, say, to an open iceweasel instance, most of the CPU is used by the X driver. It makes swicthind desk really jaggy and I'm pretty sure that wasn't the case a few weeks ago. It certainly does not happen on an other computer I use (with a NVIDIA card). I don't know what to think. Cheers, Vincent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
xorg: Changes to 'ubuntu'
debian/changelog| 64 debian/xserver-xorg.postinst.in | 22 ++--- debian/xserver-xorg.postrm.in | 35 - debian/xserver-xorg.preinst.in | 44 --- debian/xserver-xorg.prerm.in| 42 -- 5 files changed, 69 insertions(+), 138 deletions(-) New commits: commit 930d9ce4668ca6e04fb1fe14d9a213795e941a65 Author: Timo Aaltonen [EMAIL PROTECTED] Date: Tue Nov 27 13:43:12 2007 +0200 Prepare changelog for upload. diff --git a/debian/changelog b/debian/changelog index 3cfdfa2..59903f2 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,4 +1,4 @@ -xorg (1:7.3+7ubuntu1) UNRELEASED; urgency=low +xorg (1:7.3+7ubuntu1) hardy; urgency=low * Merge with Debian unstable, remaining changes: - apport/xorg-server.py, debian/x11-common.install: @@ -48,7 +48,7 @@ xorg (1:7.3+7ubuntu1) UNRELEASED; urgency=low 100% known in all combinations. + Skip video card autodetection if xforcevesa is set. - -- Timo Aaltonen [EMAIL PROTECTED] Mon, 19 Nov 2007 18:05:43 +0200 + -- Timo Aaltonen [EMAIL PROTECTED] Tue, 27 Nov 2007 11:53:49 +0200 xorg (1:7.3+7) unstable; urgency=low commit d2c1a9e5cbb37be2b8112fdb9be912de965691ce Author: David Nusinow [EMAIL PROTECTED] Date: Mon Nov 26 23:07:28 2007 -0500 Prepare changelog for upload diff --git a/debian/changelog b/debian/changelog index 3fb92bf..dfc3473 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,4 +1,4 @@ -xorg (1:7.3+7) UNRELEASED; urgency=low +xorg (1:7.3+7) unstable; urgency=low * Don't set driver-specific depths in xserver postinst + For newport, vga, savage, suncg6, and tdfx. These should all be handled @@ -8,7 +8,7 @@ xorg (1:7.3+7) UNRELEASED; urgency=low This situation was created if you had installed the previous package from scratch. Closes: #452897 - -- David Nusinow [EMAIL PROTECTED] Mon, 26 Nov 2007 22:06:02 -0500 + -- David Nusinow [EMAIL PROTECTED] Mon, 26 Nov 2007 23:07:19 -0500 xorg (1:7.3+6) unstable; urgency=low commit c2a1c75bec727d232b6dd8a81ff4ff247bd98f10 Author: David Nusinow [EMAIL PROTECTED] Date: Mon Nov 26 22:53:25 2007 -0500 + For newport, vga, savage, suncg6, and tdfx. These should all be handled * Get rid of old server symlink stuff that was left behind + Make sure we replace symlinks pointing to /bin/true in the postinst. This situation was created if you had installed the previous package from scratch. Closes: #452897 diff --git a/debian/changelog b/debian/changelog index ddfd561..3fb92bf 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,10 +1,14 @@ xorg (1:7.3+7) UNRELEASED; urgency=low * Don't set driver-specific depths in xserver postinst -+ For newport, vga, savage, suncg6, and tdfx. These should all be handled ++ For newport, vga, savage, suncg6, and tdfx. These should all be handled in the drivers themselves + * Get rid of old server symlink stuff that was left behind ++ Make sure we replace symlinks pointing to /bin/true in the postinst. + This situation was created if you had installed the previous package + from scratch. Closes: #452897 - -- David Nusinow [EMAIL PROTECTED] Sun, 25 Nov 2007 23:41:08 -0500 + -- David Nusinow [EMAIL PROTECTED] Mon, 26 Nov 2007 22:06:02 -0500 xorg (1:7.3+6) unstable; urgency=low diff --git a/debian/xserver-xorg.postinst.in b/debian/xserver-xorg.postinst.in index 91fd136..c0fb730 100644 --- a/debian/xserver-xorg.postinst.in +++ b/debian/xserver-xorg.postinst.in @@ -1644,6 +1644,10 @@ done # not exist. otherwise, assume that's the way the user wants it. if ! [ -e $SERVER_SYMLINK ]; then ln -s $THIS_SERVER $SERVER_SYMLINK +# recover from an old bug +elif [ `readlink $SERVER_SYMLINK` = /bin/true ]; then + rm -f $SERVER_SYMLINK + ln -s $THIS_SERVER $SERVER_SYMLINK fi # Don't touch the config on upgrades except to deal with known issues with old diff --git a/debian/xserver-xorg.postrm.in b/debian/xserver-xorg.postrm.in index b0a5378..0946d8a 100644 --- a/debian/xserver-xorg.postrm.in +++ b/debian/xserver-xorg.postrm.in @@ -28,40 +28,7 @@ THIS_SERVER=/usr/bin/Xorg # clean up non-conffile configuration files and related materials on purge if [ $1 = purge ]; then - # de-register this file as a handler of the X server symlink - if [ -e $SERVER_SYMLINK_ROSTER ]; then -# check existing roster file for our package name -if fgrep -qx $THIS_PACKAGE $SERVER_SYMLINK_ROSTER; then - # construct temporary roster file with our package name removed, ignoring - # failure - fgrep -vx $THIS_PACKAGE $SERVER_SYMLINK_ROSTER \ -$SERVER_SYMLINK_ROSTER.dpkg-tmp || true - # is there anything left? - if [ -s $SERVER_SYMLINK_ROSTER.dpkg-tmp ]; then -# yes, replace the roster file -mv $SERVER_SYMLINK_ROSTER.dpkg-tmp $SERVER_SYMLINK_ROSTER -
Bug#452983: xserver-xorg: X server doesn't start per 'Modes' setting in xorg.conf
On Tue, 27 Nov 2007 the mental interface of Brice Goglin told: tags 452983 +wontfix thank you Modes is the old deprecated way to specificy modes. With RandR 1.2 drivers (you're using ati 6.7.196), the way to specify modes is ModeLine+PreferredMode in the Monitor section. Details in section III.5. of http://wiki.debian.org/XStrikeForce/HowToRandR12 Thanks, fixed ;) I am marking this as wontfix for now. Bug closed. Sorry for the noise. Elimar -- .~. /V\ L I N U X /( )\ Phear the Penguin ^^-^^ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 453069 to xserver-xorg-core
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.11 reassign 453069 xserver-xorg-core Bug#453069: Xorg server crashes when compositing is enabled Bug reassigned from package `libxcomposite1' to `xserver-xorg-core'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452913: Xserver fails to start with a black screen
Brice Goglin wrote: Did any earlier xserver-xorg-core work? Which ones? You can use http://snapshot.debian.net/ to downgrade to 2:1.4-3 or 2:1.3.0 We need the config and log of this sony box, or we won't be able to do anything with this bug report. Can you log through ssh? If so, please send the output of /usr/share/bug/xserver-xorg/script 31 I cannot reproduce the bug anymore. I have kill xorg.conf, downgraded to testing, then upgraded back to unstable. Something was wrong with xorg.conf probably. Brice, thanks for pushing me this way, and sorry for noise. -- Sergey Yanovich -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452983: Bug#451929: gstreamer0.10-alsa: Jittering sound
reassign 451929 gstreamer0.10-alsa thanks On Tue, 27 Nov 2007 the mental interface of Daniel Franganillo told: 2007/11/26, Elimar Riesebieter [EMAIL PROTECTED]: On Mon, 26 Nov 2007 the mental interface of The alsa driver. Do you have different soundcards on the tested ones? Elimar Yes, different ones. But...why mplayer, xmms et al play music as the should whereas rhythmbox doesnt? Is that really related to an alsa driver bug? I didnt change kernel recently, and problems appeared when gstreamer updataed to 0.10.15 Thnaks. On Tue, 27 Nov 2007 the mental interface of Daniel Franganillo told: More info. Tested gstreamer0.10.15 in a gentoo box and it has glitches too. The machine is the same as mine. Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60) Thanks. Well, this seems to be a bug in gstreamer anyway. If music is playing well with mplayer, xmms and friends from the soundcard gstreamer produces glitches I think the gstreamer team has to find a solution then. Feel free to reassign the bug to rhythmbox... An ALSA tag will be tagged wontfix. Elimar -- The path to source is always uphill! -unknown- signature.asc Description: Digital signature
Bug#452913: Bug#437066: xserver-xorg-video-intel: refuses 1366x768 because detects 1024x768 panel size
Looks like my previous patch to bug #437066 was the real cause of bug
#452913.
The new patch (attached) copies values of bios_mode to fixed_mode,
instead of overwriting the latter.
--
Sergey Yanovich
diff --git a/src/i830_lvds.c b/src/i830_lvds.c
index a3a56f7..76e55f7 100644
--- a/src/i830_lvds.c
+++ b/src/i830_lvds.c
@@ -926,6 +926,16 @@ i830_lvds_init(ScrnInfoPtr pScrn)
bios_mode = i830_bios_get_panel_mode(pScrn, dev_priv-panel_wants_dither);
if (bios_mode != NULL) {
if (dev_priv-panel_fixed_mode != NULL) {
+ /* Fixup for a 1366x768 panel with the horizontal trimmed
+ * down to 1024 for text mode.
+ */
+ if (!xf86ModesEqual(dev_priv-panel_fixed_mode, bios_mode)
+ bios_mode-HDisplay == 1366)
+ {
+ memcpy(dev_priv-panel_fixed_mode-Clock,
+ bios_mode-Clock, sizeof(int)*12);
+ }
+
/* Fixup for a 1280x768 panel with the horizontal trimmed
* down to 1024 for text mode.
*/
Bug#453069: (no subject)
You'l probably find this core dump more useful (at least it has less question marks when I load it with kdbg). http://rapidshare.com/files/72669682/core.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#451243: xserver-xorg-video-intel: DRI/XGL hard lock / kernel oops: *ERROR* i915_wait_irq: EBUSY
Yair Mahalalel wrote: Package: xserver-xorg-video-intel Version: 2:2.1.99-1 Severity: important The problem is characterized by a hard freeze of the viedo system. X cannot be restarted without a reboot, keyboard is still responsive (Alt-Ctrl-Del reboots, PrtScn snow crashes the screen). Depending on (unrelated) kernel modules loaded, this might also be followed by a kernel oops and sometimes also system freeze, needing a cold restart. To reproduce the bug I run a recent SecondLife client. A few seconds of walking around is enough to trigger the freeze. When triggered the following line appears in the kernel log - [drm:i915_wait_irq] *ERROR* i915_wait_irq: EBUSY -- rec: 11828126 emitted: 11828128 I guess latest xserver-xorg-core and xserver-xorg-video-intel won't change anything here. It looks like a mesa problem to me, something like a GPU lockup. SecondLife uses OpenGL/DRI, right? Being easy to reproduce is a very good point here. Would you mind reporting this bug upstream at bugzilla.freedesktop.org product mesa component drivers/dri/i915 ? If you can't, I'll do it. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#453194: compiz-fusion-plugins-main: FTBFS: configure.ac:9: require Automake 1.9, but have 1.7.9
Package: compiz-fusion-plugins-main version: 0.6.0-3 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20071126 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. Relevant part: for f in po/Makefile.in.in; do \ cp -a $f $f.preserve; \ done ./autogen.sh autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --output=aclocal.m4t autoreconf: `aclocal.m4' is created autoreconf: configure.ac: tracing autoreconf: running: libtoolize --copy autoreconf: `aclocal.m4' is unchanged autoreconf: running: /usr/bin/autoconf autoreconf: running: /usr/bin/autoheader autoreconf: running: automake --add-missing --copy configure.ac: installing `./install-sh' configure.ac: installing `./mkinstalldirs' configure.ac: installing `./missing' configure.ac:9: require Automake 1.9, but have 1.7.9 autoreconf: automake failed with exit status: 1 make: *** [configure-stamp] Error 1 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 The full build log is available from: http://people.debian.org/~lucas/logs/2007/11/26 A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452894: Brightness is reduced when switching to a VT, using 3d games or switching resolution
Diego Escalante Urrelo wrote: Package: xserver-xorg-video-intel Version: 2:2.2.0-1 Severity: normal --- Please enter the report below this line. --- If I switch VTs, manually or automatically due GDM start or whatever, the screen brightness is reduced to 30%. You can reproduce this by openning zsnes, chromium or switching resolution/refresh on the screen resolution GNOME capplet. Also switching to contrl+alt+f1 or any other triggers the problem. Can you try running xrandr --output LVDS --set BACKLIGHT_CONTROL legacy and see it changes anything? What if you try combination, kernel or native instead? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442853: xserver-xorg-input-vmmouse: cursor does not move
Joerg Platte wrote: Am Sonntag, 25. November 2007 schrieben Sie: Hi Brice, Does this bug still occur with xserver-xorg-core 1.4.1 currently in unstable? Yes, otherwise I would have closed this bug. Ok. With xserver-xorg-input-vmmouse 12.4.3 as well, I guess? Could you send the corresponding Xorg.0.log so that I open a new report on the upstream bugzilla? (feel free to do it yourself if you want, of course :)) thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452894: Brightness is reduced when switching to a VT, using 3d games or switching resolution
On 11/27/07, Brice Goglin [EMAIL PROTECTED] wrote: Diego Escalante Urrelo wrote: Package: xserver-xorg-video-intel Version: 2:2.2.0-1 Severity: normal --- Please enter the report below this line. --- If I switch VTs, manually or automatically due GDM start or whatever, the screen brightness is reduced to 30%. You can reproduce this by openning zsnes, chromium or switching resolution/refresh on the screen resolution GNOME capplet. Also switching to contrl+alt+f1 or any other triggers the problem. Can you try running xrandr --output LVDS --set BACKLIGHT_CONTROL legacy and see it changes anything? What if you try combination, kernel or native instead? Ok I tried that, but nothing changed. Or I should say that I couldn't trigger the bug. Note that the missing thinkpad|ibm-acpi module seems to be the cause. I quickly tried your command but nothing seems to have changed, I tried running zsnes with each variation of the command but nothing happened. Shall I try without the module? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#453069: Xorg server crashes when compositing is enabled
Matthias Berndt wrote: Package: libxcomposite1 Version: 1:0.3.2-1+b1 Severity: important --- Please enter the report below this line. --- The Xorg server crashes under certain circumstances on my system when compositing is enabled, both with the nv driver and nvidias binary nvidia driver. To reproduce, I do the following on my system: 1. enable compositing for kwin (to do this, run kcmshell kwinoptions and enable Tranparency and drop shadows there). 2. start yakuake (a quake-style terminal emulator for KDE). 3. in a yakuake terminal, start mplayer with some audio file. 4. Open a new tab in yakuake (Ctrl-Alt-N). 5. hide yakuake (by pressing F12). Xorg now crashes. I've made a core dump, but it's 22MB and I don't know if debians bug tracking system can handle this. So I decided to upload it to rapidshare instead. http://rapidshare.com/files/72551477/core.html You should install xserver-xorg-core-dbg, switch to the nv driver (we can't do anything about nvidia), get a new core if needed, run gdb /usr/bin/Xorg core and then enter bt full. Send us the whole output of gdb. thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#453054: EXA doesn't work.
Matthias Berndt wrote: Package: xserver-xorg-video-nv Version: 1:2.1.6-1 Severity: normal --- Please enter the report below this line. --- In the nv man page, it says: Option AccelMethod string Choose acceleration architecture, either XAA or EXA. In my xorg.conf i have the line Option AccelMethod EXA and it doesn't work. From Xorg.0.log: (WW) NV(0): Option AccelMethod is not used So either the man page or something else is broken here. Please send your whole xorg.conf (reportbug should have done that for you actually). Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#448755: xserver-xorg: one display keeps turning off in xinerama (3-display) mode
Pallinger Péter wrote: Package: xserver-xorg Version: 1:7.1.0-19 Severity: normal I have a three-monitor setup with the following components: - ATI Radeon 7000 PCI - integrated Intel 845 chip - one 19 TFT @ 1240x1024 - two 15 TFTs @ 1024x768 - lspci|grep VGA output: 00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01) 01:02.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] The 19 TFT is connected to the DVI port of the radeon card, the other two are connected to the remaining DSUB connectors. The 19 TFT is on the left, the wto others are on its right, above each other. The 19 TFT keeps turning off sporadically (each 2-10 minutes) for about 2 seconds. The effect is the same as if the monitor changed video modes; but it does not (or to the same mode). The effect is produced in any video mode I have tried. In very rare cases (at most once a day), the display becomes distorted until the next 'switchoff' or manual resolution change, the whole screen being horizontally compressed into the right 4/5s of the screen. The other two displays work without any problem. Switching between applications on different monitors makes the effect appear more often (but sometimes it does not). I am using gnome, with automatic power management and screensaver turned off. A similar error is described in the mandrake/mandriva bugzilla, but I could not find an equivalent report for debian. http://qa.mandrivalinux.com/show_bug.cgi?id=6745 You seem to be using a very old Xorg (from Debian Etch). Things evolved a lot since then. So I should say can you upgrade to testing or unstable?. Unfortunately, multiple board support is broken in unstable and won't be fixed very soon. Still, one thing you could try is disabling the i810 config in your xorg.conf and see if the problem remains when only the 2 outputs of the radeon are used. If it doesn't help, the problem will likely be in the ati driver (which is getting very active development these days). Brice
Bug#451703: white screen of death under compiz
David wrote: Thank you very much to you all for the replies! You need the wobbly plugin. See http://bgoglin.livejournal.com/11253.html I read your instructions on this page (thank you), and I wonder: does anyone know the equivalent for KDE? IIRC, there's a KDE config backend coming with compiz-fusion. Alternatively: will it be straightforward in compiz-fusion? If so, I can wait. I didn't try the compizfusion configurator yet, I hope it will bring a sane config within a couple clicks. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442853: xserver-xorg-input-vmmouse: cursor does not move
Am Dienstag, 27. November 2007 schrieb Brice Goglin: Hi Brice, Ok. With xserver-xorg-input-vmmouse 12.4.3 as well, I guess? Could you Of course! I update each day to check if the bug has already been fixed. :) send the corresponding Xorg.0.log so that I open a new report on the upstream bugzilla? (feel free to do it yourself if you want, of course :)) OK, here it is. Why did they close the old bug without fixing the problem? Or are bugzilla bugs bound to a specific version and each new version needs a confirmation that the bug still exists by reporting it again? regards, Jörg X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.1~git20071119-1) Current Operating System: Linux ds37 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 Build Date: 20 November 2007 01:48:55AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Tue Nov 27 15:53:29 2007 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Generic Monitor (**) | |--Device Graphics Device (**) |--Input Device Generic Keyboard (**) |--Input Device Configured Mouse (==) Automatically adding devices (==) Automatically enabling devices (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/cyrillic, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType (==) RgbPath set to /etc/X11/rgb (==) ModulePath set to /usr/lib/xorg/modules (II) Open ACPI successful (/var/run/acpid.socket) (II) Loader magic: 0x81d7500 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 2.0 X.Org XInput driver : 2.0 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: pcidata (II) Loading /usr/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 1.4.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 2.0 (++) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,7190 card 15ad,1976 rev 01 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,7191 card , rev 01 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 8086,7110 card 15ad,1976 rev 08 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 8086,7111 card 15ad,1976 rev 01 class 01,01,8a hdr 00 (II) PCI: 00:07:2: chip 8086,7112 card 15ad,1976 rev 00 class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 8086,7113 card 15ad,1976 rev 08 class 06,80,00 hdr 80 (II) PCI: 00:0f:0: chip 15ad,0405 card 15ad,0405 rev 00 class 03,00,00 hdr 00 (II) PCI: 00:10:0: chip 104b,1040 card 104b,1040 rev 01 class 01,00,00 hdr 00 (II) PCI: 00:11:0: chip 1022,2000 card 1022,2000 rev 10 class 02,00,00 hdr 00 (II) PCI: 00:12:0: chip 1274,1371 card 1274,1371 rev 02 class 04,01,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x0080 (VGA_EN is cleared) (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:7:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(0:15:0) VMware Inc [VMware SVGA II] PCI Display Adapter rev 0, Mem @ 0xf000/27, 0xec00/23, I/O @ 0x1460/4 (II) Addressable bus resource ranges are [0] -1 0 0x - 0x (0x0) MX[B] [1] -1 0 0x - 0x (0x1) IX[B] (II) OS-reported resource ranges: [0] -1 0 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [1] -1 0 0x000f - 0x000f (0x1) MX[B] [2] -1 0 0x000c - 0x000e (0x3) MX[B] [3] -1 0 0x - 0x0009 (0xa) MX[B] [4] -1 0 0x - 0x (0x1) IX[B] [5] -1 0 0x - 0x00ff (0x100) IX[B] (II) PCI Memory resource overlap reduced 0xe800 from 0xebff to 0xe7ff (II) Active PCI resource ranges: [0] -1 0 0xec80 - 0xec80001f (0x20) MX[B] [1] -1 0 0xe800 - 0xe7ff (0x0) MX[B]O [2] -1 0 0xec00 - 0xec7f (0x80) MX[B](B) [3] -1 0 0xf000 - 0xf7ff (0x800) MX[B](B) [4] -1 0 0x1400 - 0x143f (0x40) IX[B] [5] -1 0 0x1080 - 0x10ff (0x80) IX[B] [6] -1 0 0x1440 - 0x145f (0x20) IX[B] [7] -1 0 0x1060 - 0x107f (0x20) IX[B] [8] -1 0 0x1050 -
Bug#452913: marked as done (Xserver fails to start with a black screen)
Your message dated Tue, 27 Nov 2007 22:13:49 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#452913: Xserver fails to start with a black screen has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: xserver-xorg-core Version: 2:1.4.1~git20071119 Severity: critical X fails on Sony VGN-TX770P with i915GM. Tried with both video-intel 2.1.1-5 and 2.2.0-1 versions. That box is unusable, bug reported from another one, so config/log are irrelevant and removed. ---End Message--- ---BeginMessage--- Ok, closing. Brice ---End Message---
Bug#451703: white screen of death under compiz
Thank you very much to you all for the replies! You need the wobbly plugin. See http://bgoglin.livejournal.com/11253.html I read your instructions on this page (thank you), and I wonder: does anyone know the equivalent for KDE? Alternatively: will it be straightforward in compiz-fusion? If so, I can wait. Thank you
Bug#453069: Xorg server crashes when compositing is enabled
You should install xserver-xorg-core-dbg,
I have that package installed
switch to the nv driver (we
can't do
anything about nvidia),
Both of the core dumps I've posted are from X with the nv driver.
get a new core if needed, run gdb
/usr/bin/Xorg core
and then enter bt full. Send us the whole output of gdb.
The stack trace is in the attachment. gdb also said:
warning: Can't read pathname for load map: Input/output error.
Failed to read a valid object file image from memory.
128 ../../../miext/cw/cw_render.c: No such file or directory.
Cannot access memory at address 0x8
Using host libthread_db library /lib/i686/cmov/libthread_db.so.1.
Core was generated by `X :1'.
Program terminated with signal 11, Segmentation fault.
#0 0xb6fe92d2 in cwGetBackingPicture (pPicture=0x854ac70, x_off=0xbfbe7440,
y_off=0xbfbe743c) at ../../../miext/cw/cw_render.c:128
in ../../../miext/cw/cw_render.c
#0 0xb6fe92d2 in cwGetBackingPicture (pPicture=0x854ac70, x_off=0xbfbe7440,
y_off=0xbfbe743c) at ../../../miext/cw/cw_render.c:128
pPixmap = (PixmapPtr) 0x0
#1 0xb6fe959d in cwGlyphs (op=3 '\003', pSrcPicture=0x85486e0,
pDstPicture=0x854ac70, maskFormat=0x8228968, xSrc=0, ySrc=0, nlists=1,
lists=0xbfbe7998,
glyphs=0xbfbe7598) at ../../../miext/cw/cw_render.c:296
ps = (PictureScreenPtr) 0x8228df0
pCwScreen = (cwScreenPtr) 0x8228378
src_picture_x_off = 0
src_picture_y_off = 0
pBackingSrcPicture = (PicturePtr) 0x85486e0
dst_picture_x_off = 139674304
dst_picture_y_off = value optimized out
pBackingDstPicture = value optimized out
#2 0x0816fa34 in damageGlyphs (op=65 'A', pSrc=0x85486e0, pDst=0x854ac70,
maskFormat=0x8228968, xSrc=value optimized out, ySrc=value optimized out,
nlist=1, list=0xbfbe7998, glyphs=0xbfbe7598) at
../../../miext/damage/damage.c:658
box = {x1 = -21392, y1 = 2132, x2 = 29912, y2 = -16450}
x1 = value optimized out
x = -1078037312
n = 0
y1 = value optimized out
x2 = 135622037
glyphsTmp = (GlyphPtr *) 0x8201308
y = -1078037272
glyph = value optimized out
y2 = 136319752
ps = (PictureScreenPtr) 0x8228df0
pScrPriv = (DamageScrPrivPtr) 0x82283d8
#3 0x081570fa in CompositeGlyphs (op=value optimized out, pSrc=0x85486e0,
pDst=0x854ac70, maskFormat=0x8228968, xSrc=0, ySrc=0, nlist=1,
lists=0xbfbe7998, glyphs=0xbfbe7598) at ../../render/picture.c:1785
ps = (PictureScreenPtr) 0x8228df0
#4 0x0815e988 in ProcRenderCompositeGlyphs (client=0x84b6930) at
../../render/render.c:1403
glyphSet = (GlyphSetPtr) 0x8548188
gs = 1
pFormat = (PictFormatPtr) 0x8228968
listsLocal = {{xOff = 85, yOff = 418, len = 3 '\003', format =
0x8228968}, {xOff = 0, yOff = 0, len = 64 '@', format = 0xbfbe79c8}, {xOff =
-5715,
yOff = -18478, len = 64 '@', format = 0x40}, {xOff = 5736, yOff = -18453,
len = 240 'ð', format = 0x852d838}, {xOff = 31320, yOff = -16450,
len = 76 'L', format = 0x852d7f0}, {xOff = 1160, yOff = 0, len = 4 '\004',
format = 0xbfbe79f8}, {xOff = -5715, yOff = -18478, len = 64 '@',
format = 0x40}, {xOff = 5736, yOff = -18453, len = 56 '8', format =
0x852d844}, {xOff = 31240, yOff = -16450, len = 144 '\220', format =
0x8245360}, {
xOff = 5736, yOff = -18453, len = 68 'D', format = 0xb7e8ee40}, {xOff =
4968, yOff = 2132, len = 144 '\220', format = 0x38}, {xOff = 24460,
yOff = 2077, len = 0 '\0', format = 0x0}, {xOff = 31304, yOff = -16450, len
= 68 'D', format = 0x8225708}, {xOff = -31896, yOff = 2081, len = 104 'h',
format = 0x81d5f8c}, {xOff = -10184, yOff = 2130, len = 140 '\214', format
= 0xb7f3acfb}, {xOff = 14943, yOff = -18674, len = 104 'h',
format = 0x852d7f0}, {xOff = 22280, yOff = 2082, len = 224 'à', format =
0x8225708}, {xOff = -31896, yOff = 2081, len = 112 'p', format = 0x846f570}, {
xOff = 22280, yOff = 2082, len = 104 'h', format = 0x846f570}, {xOff =
-2704, yOff = 2118, len = 112 'p', format = 0x852d7f0}, {xOff = 2716,
yOff = -18465, len = 151 '\227', format = 0x85342c0}, {xOff = 30096, yOff =
2082, len = 32 ' ', format = 0x82282c8}, {xOff = -31960, yOff = 2082,
len = 208 'Ð', format = 0xbfbe7b28}, {xOff = -2704, yOff = 2118, len = 1
'\001', format = 0x852d768}, {xOff = 31464, yOff = -16450, len = 0 '\0',
format = 0x823cf80}, {xOff = -1, yOff = -1, len = 0 '\0', format = 0x0},
{xOff = 17088, yOff = 2131, len = 144 '\220', format = 0xbfbe7b20}, {
xOff = -20355, yOff = -18673, len = 112 'p', format = 0xbfbe7c60}, {xOff =
1, yOff = 0, len = 32 ' ', format = 0xb70e410c}, {xOff = 0, yOff = 0,
len = 0 '\0', format = 0xbfbe7b28}, {xOff = -18852, yOff = -18690, len =
192 'À', format = 0x8227590}, {xOff = 31704, yOff = -16450, len = 92 '\\',
format = 0xbfbe7b28}, {xOff = 31544, yOff = -16450, len = 112 'p', format =
0x0}, {xOff = 1280, yOff = 1024, len = 144 '\220', format = 0x81d038c},
Bug#453069: Xorg server crashes when compositing is enabled
You should install xserver-xorg-core-dbg,
I have that package installed
switch to the nv driver (we
can't do
anything about nvidia),
Both of the core dumps I've posted are from X with the nv driver.
get a new core if needed, run gdb
/usr/bin/Xorg core
and then enter bt full. Send us the whole output of gdb.
The stack trace is in the attachment. gdb also said:
warning: Can't read pathname for load map: Input/output error.
Failed to read a valid object file image from memory.
128 ../../../miext/cw/cw_render.c: No such file or directory.
Cannot access memory at address 0x8
Using host libthread_db library /lib/i686/cmov/libthread_db.so.1.
Core was generated by `X :1'.
Program terminated with signal 11, Segmentation fault.
#0 0xb6fe92d2 in cwGetBackingPicture (pPicture=0x854ac70, x_off=0xbfbe7440,
y_off=0xbfbe743c) at ../../../miext/cw/cw_render.c:128
in ../../../miext/cw/cw_render.c
#0 0xb6fe92d2 in cwGetBackingPicture (pPicture=0x854ac70, x_off=0xbfbe7440,
y_off=0xbfbe743c) at ../../../miext/cw/cw_render.c:128
pPixmap = (PixmapPtr) 0x0
#1 0xb6fe959d in cwGlyphs (op=3 '\003', pSrcPicture=0x85486e0,
pDstPicture=0x854ac70, maskFormat=0x8228968, xSrc=0, ySrc=0, nlists=1,
lists=0xbfbe7998,
glyphs=0xbfbe7598) at ../../../miext/cw/cw_render.c:296
ps = (PictureScreenPtr) 0x8228df0
pCwScreen = (cwScreenPtr) 0x8228378
src_picture_x_off = 0
src_picture_y_off = 0
pBackingSrcPicture = (PicturePtr) 0x85486e0
dst_picture_x_off = 139674304
dst_picture_y_off = value optimized out
pBackingDstPicture = value optimized out
#2 0x0816fa34 in damageGlyphs (op=65 'A', pSrc=0x85486e0, pDst=0x854ac70,
maskFormat=0x8228968, xSrc=value optimized out, ySrc=value optimized out,
nlist=1, list=0xbfbe7998, glyphs=0xbfbe7598) at
../../../miext/damage/damage.c:658
box = {x1 = -21392, y1 = 2132, x2 = 29912, y2 = -16450}
x1 = value optimized out
x = -1078037312
n = 0
y1 = value optimized out
x2 = 135622037
glyphsTmp = (GlyphPtr *) 0x8201308
y = -1078037272
glyph = value optimized out
y2 = 136319752
ps = (PictureScreenPtr) 0x8228df0
pScrPriv = (DamageScrPrivPtr) 0x82283d8
#3 0x081570fa in CompositeGlyphs (op=value optimized out, pSrc=0x85486e0,
pDst=0x854ac70, maskFormat=0x8228968, xSrc=0, ySrc=0, nlist=1,
lists=0xbfbe7998, glyphs=0xbfbe7598) at ../../render/picture.c:1785
ps = (PictureScreenPtr) 0x8228df0
#4 0x0815e988 in ProcRenderCompositeGlyphs (client=0x84b6930) at
../../render/render.c:1403
glyphSet = (GlyphSetPtr) 0x8548188
gs = 1
pFormat = (PictFormatPtr) 0x8228968
listsLocal = {{xOff = 85, yOff = 418, len = 3 '\003', format =
0x8228968}, {xOff = 0, yOff = 0, len = 64 '@', format = 0xbfbe79c8}, {xOff =
-5715,
yOff = -18478, len = 64 '@', format = 0x40}, {xOff = 5736, yOff = -18453,
len = 240 'ð', format = 0x852d838}, {xOff = 31320, yOff = -16450,
len = 76 'L', format = 0x852d7f0}, {xOff = 1160, yOff = 0, len = 4 '\004',
format = 0xbfbe79f8}, {xOff = -5715, yOff = -18478, len = 64 '@',
format = 0x40}, {xOff = 5736, yOff = -18453, len = 56 '8', format =
0x852d844}, {xOff = 31240, yOff = -16450, len = 144 '\220', format =
0x8245360}, {
xOff = 5736, yOff = -18453, len = 68 'D', format = 0xb7e8ee40}, {xOff =
4968, yOff = 2132, len = 144 '\220', format = 0x38}, {xOff = 24460,
yOff = 2077, len = 0 '\0', format = 0x0}, {xOff = 31304, yOff = -16450, len
= 68 'D', format = 0x8225708}, {xOff = -31896, yOff = 2081, len = 104 'h',
format = 0x81d5f8c}, {xOff = -10184, yOff = 2130, len = 140 '\214', format
= 0xb7f3acfb}, {xOff = 14943, yOff = -18674, len = 104 'h',
format = 0x852d7f0}, {xOff = 22280, yOff = 2082, len = 224 'à', format =
0x8225708}, {xOff = -31896, yOff = 2081, len = 112 'p', format = 0x846f570}, {
xOff = 22280, yOff = 2082, len = 104 'h', format = 0x846f570}, {xOff =
-2704, yOff = 2118, len = 112 'p', format = 0x852d7f0}, {xOff = 2716,
yOff = -18465, len = 151 '\227', format = 0x85342c0}, {xOff = 30096, yOff =
2082, len = 32 ' ', format = 0x82282c8}, {xOff = -31960, yOff = 2082,
len = 208 'Ð', format = 0xbfbe7b28}, {xOff = -2704, yOff = 2118, len = 1
'\001', format = 0x852d768}, {xOff = 31464, yOff = -16450, len = 0 '\0',
format = 0x823cf80}, {xOff = -1, yOff = -1, len = 0 '\0', format = 0x0},
{xOff = 17088, yOff = 2131, len = 144 '\220', format = 0xbfbe7b20}, {
xOff = -20355, yOff = -18673, len = 112 'p', format = 0xbfbe7c60}, {xOff =
1, yOff = 0, len = 32 ' ', format = 0xb70e410c}, {xOff = 0, yOff = 0,
len = 0 '\0', format = 0xbfbe7b28}, {xOff = -18852, yOff = -18690, len =
192 'À', format = 0x8227590}, {xOff = 31704, yOff = -16450, len = 92 '\\',
format = 0xbfbe7b28}, {xOff = 31544, yOff = -16450, len = 112 'p', format =
0x0}, {xOff = 1280, yOff = 1024, len = 144 '\220', format = 0x81d038c},
Bug#453069: Xorg server crashes when compositing is enabled
forwarded 453069 https://bugs.freedesktop.org/show_bug.cgi?id=10617 thank you Matthias Berndt wrote: get a new core if needed, run gdb /usr/bin/Xorg core and then enter bt full. Send us the whole output of gdb. The stack trace is in the attachment. Thanks, that's already reported upstream at the URL above. I added a comment there, feel free to add more if you think it could help. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#453069: Xorg server crashes when compositing is enabled
Processing commands for [EMAIL PROTECTED]: forwarded 453069 https://bugs.freedesktop.org/show_bug.cgi?id=10617 Bug#453069: Xorg server crashes when compositing is enabled Noted your statement that Bug has been forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=10617. thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: forcibly merging 451570 452357
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.10 forcemerge 451570 452357 Bug#451570: xserver-xorg-video-intel: Lockup on startup with EXA if virtual screen exceeds 2048 Bug#452357: xserver-xorg-video-intel: 945GM always crashes within 10 seconds of login Forcibly Merged 451570 452357. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#453069: Xorg server crashes when compositing is enabled
You should install xserver-xorg-core-dbg,
I have that package installed
switch to the nv driver (we
can't do
anything about nvidia),
Both of the core dumps I've posted are from X with the nv driver.
get a new core if needed, run gdb
/usr/bin/Xorg core
and then enter bt full. Send us the whole output of gdb.
Here's the stack trace:
Using host libthread_db library /lib/i686/cmov/libthread_db.so.1.
Core was generated by `X :1'.
Program terminated with signal 11, Segmentation fault.
#0 0xb6fe92d2 in cwGetBackingPicture (pPicture=0x854ac70,
x_off=0xbfbe7440, y_off=0xbfbe743c) at ../../../miext/cw/cw_render.c:128
in ../../../miext/cw/cw_render.c
#0 0xb6fe92d2 in cwGetBackingPicture (pPicture=0x854ac70,
x_off=0xbfbe7440, y_off=0xbfbe743c) at ../../../miext/cw/cw_render.c:128
pPixmap = (PixmapPtr) 0x0
#1 0xb6fe959d in cwGlyphs (op=3 '\003', pSrcPicture=0x85486e0,
pDstPicture=0x854ac70, maskFormat=0x8228968, xSrc=0, ySrc=0, nlists=1,
lists=0xbfbe7998,
glyphs=0xbfbe7598) at ../../../miext/cw/cw_render.c:296
ps = (PictureScreenPtr) 0x8228df0
pCwScreen = (cwScreenPtr) 0x8228378
src_picture_x_off = 0
src_picture_y_off = 0
pBackingSrcPicture = (PicturePtr) 0x85486e0
dst_picture_x_off = 139674304
dst_picture_y_off = value optimized out
pBackingDstPicture = value optimized out
#2 0x0816fa34 in damageGlyphs (op=65 'A', pSrc=0x85486e0, pDst=0x854ac70,
maskFormat=0x8228968, xSrc=value optimized out, ySrc=value optimized
out,
nlist=1, list=0xbfbe7998, glyphs=0xbfbe7598)
at ../../../miext/damage/damage.c:658
box = {x1 = -21392, y1 = 2132, x2 = 29912, y2 = -16450}
x1 = value optimized out
x = -1078037312
n = 0
y1 = value optimized out
x2 = 135622037
glyphsTmp = (GlyphPtr *) 0x8201308
y = -1078037272
glyph = value optimized out
y2 = 136319752
ps = (PictureScreenPtr) 0x8228df0
pScrPriv = (DamageScrPrivPtr) 0x82283d8
#3 0x081570fa in CompositeGlyphs (op=value optimized out,
pSrc=0x85486e0, pDst=0x854ac70, maskFormat=0x8228968, xSrc=0, ySrc=0,
nlist=1,
lists=0xbfbe7998, glyphs=0xbfbe7598) at ../../render/picture.c:1785
ps = (PictureScreenPtr) 0x8228df0
#4 0x0815e988 in ProcRenderCompositeGlyphs (client=0x84b6930)
at ../../render/render.c:1403
glyphSet = (GlyphSetPtr) 0x8548188
gs = 1
pFormat = (PictFormatPtr) 0x8228968
listsLocal = {{xOff = 85, yOff = 418, len = 3 '\003', format =
0x8228968}, {xOff = 0, yOff = 0, len = 64 '@', format = 0xbfbe79c8},
{xOff = -5715,
yOff = -18478, len = 64 '@', format = 0x40}, {xOff = 5736, yOff
= -18453, len = 240 '�', format = 0x852d838}, {xOff = 31320, yOff
= -16450,
len = 76 'L', format = 0x852d7f0}, {xOff = 1160, yOff = 0, len =
4 '\004', format = 0xbfbe79f8}, {xOff = -5715, yOff = -18478, len =
64 '@',
format = 0x40}, {xOff = 5736, yOff = -18453, len = 56 '8', format =
0x852d844}, {xOff = 31240, yOff = -16450, len = 144 '\220', format =
0x8245360}, {
xOff = 5736, yOff = -18453, len = 68 'D', format = 0xb7e8ee40}, {xOff
= 4968, yOff = 2132, len = 144 '\220', format = 0x38}, {xOff = 24460,
yOff = 2077, len = 0 '\0', format = 0x0}, {xOff = 31304, yOff
= -16450, len = 68 'D', format = 0x8225708}, {xOff = -31896, yOff = 2081,
len = 104 'h',
format = 0x81d5f8c}, {xOff = -10184, yOff = 2130, len = 140 '\214',
format = 0xb7f3acfb}, {xOff = 14943, yOff = -18674, len = 104 'h',
format = 0x852d7f0}, {xOff = 22280, yOff = 2082, len = 224 '�', format
= 0x8225708}, {xOff = -31896, yOff = 2081, len = 112 'p', format =
0x846f570}, {
xOff = 22280, yOff = 2082, len = 104 'h', format = 0x846f570}, {xOff
= -2704, yOff = 2118, len = 112 'p', format = 0x852d7f0}, {xOff = 2716,
yOff = -18465, len = 151 '\227', format = 0x85342c0}, {xOff = 30096,
yOff = 2082, len = 32 ' ', format = 0x82282c8}, {xOff = -31960, yOff =
2082,
len = 208 '�', format = 0xbfbe7b28}, {xOff = -2704, yOff = 2118, len =
1 '\001', format = 0x852d768}, {xOff = 31464, yOff = -16450, len =
0 '\0',
format = 0x823cf80}, {xOff = -1, yOff = -1, len = 0 '\0', format =
0x0}, {xOff = 17088, yOff = 2131, len = 144 '\220', format = 0xbfbe7b20},
{
xOff = -20355, yOff = -18673, len = 112 'p', format = 0xbfbe7c60},
{xOff = 1, yOff = 0, len = 32 ' ', format = 0xb70e410c}, {xOff = 0, yOff
= 0,
len = 0 '\0', format = 0xbfbe7b28}, {xOff = -18852, yOff = -18690, len
= 192 '�', format = 0x8227590}, {xOff = 31704, yOff = -16450, len =
92 '\\',
format = 0xbfbe7b28}, {xOff = 31544, yOff = -16450, len = 112 'p',
format = 0x0}, {xOff = 1280, yOff = 1024, len = 144 '\220', format =
0x81d038c}, {
xOff = 30096, yOff = 2082, len = 192 '�', format = 0xbfbe7b18}, {xOff
= -1, yOff = -1, len = 255 '�', format = 0x62e07f}, {xOff = 22, yOff = 0,
len = 159 '\237', format = 0x81d5f8c}, {xOff = 30096, yOff = 2082, len
= 216
Bug#443059: marked as done (GDM and the keyboard freezes while trying to load xwindows)
Your message dated Tue, 27 Nov 2007 23:58:02 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#443059: GDM and the keyboard freezes while trying to load xwindows has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: xserver-xorg-video-ati Version: 1:6.6.193-3 When the system launches GDM after starting the computer, if the video driver is ati the screen goes black, like if there was no signal, and the keyboard doesnt respond. With the video driver vesa there is no problem. It happens since I upgraded xserver-xorg-video-ati (and many other xorg packages due to yesterdays upgrade). Running Linux 2.6.21-1-686 #1 and libc6 2.6.1-5. I have an ATI RADEON 7000 graphics card. -- Jorge González González [EMAIL PROTECTED] Weblog: http://aloriel.no-ip.org Fotolog: http://www.flickr.com/photos/aloriel ---End Message--- ---BeginMessage--- Jorge González González wrote: Jorge, Assuming this bug still occurs with 6.7.196-1 currently in experimental: About the freeze when using DRI, one thing you could try first: Reenable DRI and add Option BusType PCI to the Device section of xorg.conf. See if you still get a freeze on startup. Yeap, it works perfecly enabling DRI (Load DRI) and adding this option. Ok, it's probably caused by your AGP hardware not working perfectly. Switching to PCI mode causes the software to use the hardware a little bit slowly. I am closing this bug now. I mean that the screen is not centered, it also happens with Ubuntu, see the capture attached. But is just the GDM, when login into GNOME everything is fine. Maybe Gnome is switching to another mode right after startup and the CRT position needs to be modified accordingly. You can see the mode currently in use by running xrandr without argument. If you stop gdm, start X with startx /usr/bin/xterm, you should get the same mode than gdm does, save xrandr output into a file. Then start Gnome as usual and save the xrandr output as well. If the current mode in both xrandr outputs is different, then try to switch from one to the other with xrandr. Brice ---End Message---
Bug#448845: dpkg-reconfigure xserver-xorg fails
On Tue, Nov 27, 2007 at 10:14:14AM +, Philip Armstrong wrote: On Tue, Nov 27, 2007 at 09:48:54AM +, Philip Armstrong wrote: On Tue, Nov 27, 2007 at 08:44:47AM +0100, Brice Goglin wrote: Do you still have this problem with latest xserver-xorg? (1:7.3+6 is in unstable, 1:7.3+7 just got uploaded there too). Problem still exists with 1:7.3+6 : dexconf: error: cannot generate configuration file; xserver-xorg/config/device/driver not set. Aborting. Reconfigure the X server with dpkg-reconfigure to correct this problem. Also, the dpkg-reconfigure xserver-xorg process fails to detect my monitor (A Samsung Syncmaster 710T). Or at least I presume that it fails to do so: after the attempt at autodetection I end up being asked to give the full monitor specs regardless. The Xserver detects the monitor just fine as far as I can see from the logs. Should I file a separate bug? Looks like not all of 1:7.3+7 has arrived yet. I'll try it when it becomes available. OK, just done an update dragged in 1:7.3+7. Problem still exists. Just to test things, I tried removing the debconf config.dat cache file, so as to get all the defaults from the new package, but it didn't make any difference. Oh wait: I've found the problem! I didn't have discover installed (it was doing annoying things to my machine in the past) and this wasn't being picked up anywhere. Installing discover fixes the problem. Looks like the configuration needs to be aware of whether discover is installed or not, since it's currently a 'recommends' not a 'depends'. My main goal right now is getting rid of our reliance on discover in the postinst, so the fix for this bug will be to eventually remove all that code rather than a tighter dependency on discover. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#453054: EXA doesn't work.
Please send your whole xorg.conf (reportbug should have done that for you actually). Brice See attachment... It's quite a mess though. # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 1.0 ([EMAIL PROTECTED]) Wed Jun 13 18:39:30 PDT 2007 # /.../ # SaX generated X11 config file # Created on: 2007-01-13T03:24:40+0100. # # Version: 8.1 # Contact: Marcus Schaefer [EMAIL PROTECTED], 2005 # Contact: SaX-User list https://lists.berlios.de/mailman/listinfo/sax-users # # Automatically generated by [SaX2] (8.1) # PLEASE DO NOT EDIT THIS FILE! # Section ServerLayout Identifier Layout[all] Screen Screen[0] 0 0 InputDeviceKeyboard[0] CoreKeyboard InputDeviceMouse[1] CorePointer EndSection Section Files InputDevices /dev/gpmdata InputDevices /dev/input/mice FontPath/usr/share/fonts/misc:unscaled FontPath/usr/share/fonts/local FontPath/usr/share/fonts/75dpi:unscaled FontPath/usr/share/fonts/100dpi:unscaled FontPath/usr/share/fonts/Type1 FontPath/usr/share/fonts/URW FontPath/usr/share/fonts/Speedo FontPath/usr/share/fonts/PEX FontPath/usr/share/fonts/cyrillic FontPath/usr/share/fonts/latin2/misc:unscaled FontPath/usr/share/fonts/latin2/75dpi:unscaled FontPath/usr/share/fonts/latin2/100dpi:unscaled FontPath/usr/share/fonts/latin2/Type1 FontPath/usr/share/fonts/latin7/75dpi:unscaled FontPath/usr/share/fonts/baekmuk:unscaled FontPath/usr/share/fonts/japanese:unscaled FontPath/usr/share/fonts/kwintv FontPath/usr/share/fonts/truetype FontPath/usr/share/fonts/uni:unscaled FontPath/usr/share/fonts/CID FontPath/usr/share/fonts/ucs/misc:unscaled FontPath/usr/share/fonts/ucs/75dpi:unscaled FontPath/usr/share/fonts/ucs/100dpi:unscaled FontPath/usr/share/fonts/hellas/misc:unscaled FontPath/usr/share/fonts/hellas/75dpi:unscaled FontPath/usr/share/fonts/hellas/100dpi:unscaled FontPath/usr/share/fonts/hellas/Type1 FontPath/usr/share/fonts/misc/sgi:unscaled FontPath/usr/share/fonts/xtest FontPath/opt/kde3/share/fonts FontPathunix/:7100 EndSection Section Module Load dbe Load type1 Load freetype Load extmod Load glx Load v4l EndSection Section ServerFlags Option AllowMouseOpenFail on Option NoTrapSignals EndSection Section InputDevice Identifier Keyboard[0] Driver kbd Option InputFashion kbd Option Name Microsoft Natural Ergonomic Keyboard Option Protocol Standard Option XkbLayout de Option XkbModel microsoft Option XkbRules xfree86 Option XkbVariant nodeadkeys EndSection Section InputDevice # Driver evdev Identifier Mouse[1] Driver mouse Option Buttons 5 Option Device /dev/input/mice Option InputFashion Mouse Option Name Logitech;MX310 Option Protocol explorerps/2 # Option Protocol evdev Option Vendor Sysp Option ZAxisMapping 4 5 EndSection Section Modes Identifier Modes[0] ModeLine 1280x1024 138.5 1280 1368 1504 1728 1024 1025 1028 1069 ModeLine 1280x1024 128.9 1280 1368 1504 1728 1024 1025 1028 1066 ModeLine 1280x1024 119.4 1280 1368 1504 1728 1024 1025 1028 1063 ModeLine 1280x1024 108.9 1280 1360 1496 1712 1024 1025 1028 1060 ModeLine 1024x768 81.8 1024 1080 1192 1360 768 769 772 802 ModeLine 1024x768 76.2 1024 1080 1192 1360 768 769 772 800 ModeLine 1024x768 69.7 1024 1080 1184 1344 768 769 772 798 ModeLine 1024x768 64.1 1024 1080 1184 1344 768 769 772 795 ModeLine 800x600 48.9 800 840 920 1040 600 601 604 627 ModeLine 800x600 45.5 800 840 920 1040 600 601 604 625 ModeLine 800x600 42.1 800 840 920 1040 600 601 604 623 ModeLine 800x600 38.2 800 832 912 1024 600 601 604 622 EndSection Section Monitor Identifier Monitor[0] VendorName HIQ ModelName B90A UseModes Modes[0] DisplaySize 376301 HorizSync 30.0 - 81.0 VertRefresh 43.0 - 75.0 Option CalcAlgorithm XServerPool Option DPMS EndSection Section Device Identifier Device[0] Driver nvidia VendorName NVidia BoardName GeForce4 Ti 4200 Option RenderAccel on Option AccelMethod exa Option NvAGP 2 Option AGPFastWrite yes EndSection Section Screen Identifier Screen[0] Device Device[0]
Bug#407036: crashes while hibernating
I am not sure if it is exactly the issue reported but I think it might. In my case it seems that X is crashing BEFORE actually hibernating. I am deducing that it happened before since I found relevant crash information in /var/log/gdm/\:0.log.1 file with a timestamp when I left the work (after running s2disk). So here is a bit of information on the system (I will attach xorg.conf and relevant log file). ii xserver-xorg 1:7.3+7 the X.Org X server ii xserver-xorg-video-intel 2:2.2.0-1X.Org X server -- Intel i8xx, i9xx display driver amd64 let me know if you need any additional information or may be I should try to rebuild X with debugging symbols and no optimization to provide better handle on the source of the problem? -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.1~git20071119-1) Current Operating System: Linux len 2.6.23-1-amd64 #1 SMP Mon Nov 26 02:31:09 UTC 2007 x86_64 Build Date: 20 November 2007 02:55:16AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Tue Nov 27 15:49:36 2007 (==) Using config file: /etc/X11/xorg.conf (WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found (II) Module ddc already built-in (II) Module i2c already built-in (II) Module ramdac already built-in expected keysym, got XF86KbdLightOnOff: line 70 of pc expected keysym, got XF86KbdBrightnessDown: line 71 of pc expected keysym, got XF86KbdBrightnessUp: line 72 of pc expected keysym, got XF86KbdLightOnOff: line 70 of pc expected keysym, got XF86KbdBrightnessDown: line 71 of pc expected keysym, got XF86KbdBrightnessUp: line 72 of pc expected keysym, got XF86KbdLightOnOff: line 70 of pc expected keysym, got XF86KbdBrightnessDown: line 71 of pc expected keysym, got XF86KbdBrightnessUp: line 72 of pc expected keysym, got XF86KbdLightOnOff: line 70 of pc expected keysym, got XF86KbdBrightnessDown: line 71 of pc expected keysym, got XF86KbdBrightnessUp: line 72 of pc Backtrace: 0: /usr/bin/X(xf86SigHandler+0x6a) [0x47554a] 1: /lib/libc.so.6 [0x2b02fc0ea040] 2: /lib/libc.so.6(memcpy+0xe1) [0x2b02fc134d91] 3: /usr/lib/xorg/modules//libfb.so(fbBlt+0x9e4) [0x2b02fec5e5e4] 4: /usr/lib/xorg/modules//libfb.so(fbOddTile+0x14c) [0x2b02fec6a17c] 5: /usr/lib/xorg/modules//libfb.so(fbFillRegionTiled+0x1db) [0x2b02fec6a8fb] 6: /usr/lib/xorg/modules//libexa.so(ExaCheckPaintWindow+0x31) [0x2b02fee82831] 7: /usr/lib/xorg/modules//libexa.so(exaPaintWindow+0xb4) [0x2b02fee7d344] 8: /usr/bin/X [0x522cbf] 9: /usr/bin/X(compPaintWindowBackground+0x51) [0x4bd161] 10: /usr/bin/X(miWindowExposures+0xf8) [0x4d89f8] 11: /usr/lib/xorg/modules/extensions//libdri.so(DRIWindowExposures+0x97) [0x2b02fda35c67] 12: /usr/bin/X [0x49f5f1] 13: /usr/bin/X(miHandleValidateExposures+0x2b) [0x4ed5cb] 14: /usr/bin/X(UnmapWindow+0x1ff) [0x43aadf] 15: /usr/bin/X(ProcUnmapWindow+0x45) [0x44dbb5] 16: /usr/bin/X(Dispatch+0x2e2) [0x44e3d2] 17: /usr/bin/X(main+0x47c) [0x436bcc] 18: /lib/libc.so.6(__libc_start_main+0xf4) [0x2b02fc0d61c4] 19: /usr/bin/X(FontFileCompleteXLFD+0x261) [0x435f09] Fatal server error: Caught signal 11. Server aborting # (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the manual page. # (Type man at the shell prompt.) # # This file is automatically updated on package upgrades *only* # if it has not been modified since the last upgrade of the # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRules xorg Option XkbModel pc104 Option XkbLayout us Option XkbOptionsctrl:nocaps EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Protocol ExplorerPS/2 #Option ZAxisMapping 4 5 6 7 Option Device /dev/input/mice Option EmulateWheel on Option
Bug#453054: EXA doesn't work.
Matthias Berndt wrote: Please send your whole xorg.conf (reportbug should have done that for you actually). Brice See attachment... It's quite a mess though. Ok, the problem seems to be that EXA is only available for G80 boards (Geforce 8000 or so) from what I see in the changelog. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
