Bug#448467: xserver-xorg-video-intel: Thinkpad brightness keys don't work
On Sun, Dec 9, 2007 at 19:25:20 +0100, Marcus Better wrote: > Brice Goglin wrote: >> Can you try the latest upstream git of the driver ? > > That didn't go too well, X refused to start. Log attached. > > (II) LoadModule: "intel" > (II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so > (II) Module intel: vendor="X.Org Foundation" > compiled for 1.3.0, module version = 2.2.0 > Module class: X.Org Video Driver > ABI class: X.Org Video Driver, version 1.2 > (EE) module ABI major version (1) doesn't match the server's version (2) > (II) UnloadModule: "intel" > (II) Unloading /usr/lib/xorg/modules/drivers//intel_drv.so > (EE) Failed to load module "intel" (module requirement mismatch, 0) Looks like you built it against an old version of xserver-xorg-dev? Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: kmail: Cut and Paste buffer contents end up in message
Processing commands for [EMAIL PROTECTED]: > reassign 451332 xserver-xorg-input-mouse Bug#451332: kmail: Cut and Paste buffer contents end up in message Bug reassigned from package `kdelibs' to `xserver-xorg-input-mouse'. > forwarded 451332 https://bugs.freedesktop.org/show_bug.cgi?id=13144 Bug#451332: kmail: Cut and Paste buffer contents end up in message Forwarded-to-address changed from http://bugs.kde.org/show_bug.cgi?id=153677 to https://bugs.freedesktop.org/show_bug.cgi?id=13144. > tags 451332 +fixed-upstream Bug#451332: kmail: Cut and Paste buffer contents end up in message Tags were: fixed-upstream confirmed Tags added: fixed-upstream > thanks 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#451332: marked as done (kmail: Cut and Paste buffer contents end up in message)
Your message dated Mon, 10 Dec 2007 10:51:03 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#451332: kmail: Cut and Paste buffer contents end up in message 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) --- Begin Message --- Package: kmail Version: 4:3.5.8-1 Severity: normal For a month or two now, I have noticed that if the active window I have in my xserver is a kmail message, and I switch out of GUI to a text console and then back to the GUI, the contents of my cut and paste buffer end up being pasted in my email message. This gets to be annoying after a while. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.21 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kmail depends on: ii kdebase-kio-plugins 4:3.5.8.dfsg.1-1 core I/O slaves for KDE ii kdelibs4c2a 4:3.5.8.dfsg.1-3 core libraries and binaries for al ii kdepim-kio-plugins 4:3.5.8-1KDE pim I/O Slaves ii libart-2.0-22.3.19-3 Library of functions for 2D graphi ii libaudio2 1.9a-1 Network Audio System - shared libr ii libc6 2.6.1-6 GNU C Library: Shared libraries ii libfontconfig1 2.4.91-1 generic font configuration library ii libfreetype62.3.5-1+b1 FreeType 2 font engine, shared lib ii libgcc1 1:4.2.2-3GCC support library ii libice6 2:1.0.4-1X11 Inter-Client Exchange library ii libidn111.1-1GNU libidn library, implementation ii libjpeg62 6b-14The Independent JPEG Group's JPEG ii libkcal2b 4:3.5.8-1KDE calendaring library ii libkdepim1a 4:3.5.8-1KDE PIM library ii libkleopatra1 4:3.5.8-1KDE GnuPG interface libraries ii libkmime2 4:3.5.8-1KDE MIME interface library ii libkpimidentities1 4:3.5.8-1KDE PIM user identity information ii libksieve0 4:3.5.8-1KDE mail/news message filtering li ii libmimelib1c2a 4:3.5.8-1KDE mime library ii libpng12-0 1.2.15~beta5-3 PNG library - runtime ii libqt3-mt 3:3.3.7-9Qt GUI Library (Threaded runtime v ii libsm6 2:1.0.3-1+b1 X11 Session Management library ii libstdc++6 4.2.2-3 The GNU Standard C++ Library v3 ii libx11-62:1.0.3-7X11 client-side library ii libxcursor1 1:1.1.9-1X cursor management library ii libxext61:1.0.3-2X11 miscellaneous extension librar ii libxft2 2.1.12-2 FreeType-based font drawing librar ii libxi6 2:1.1.3-1X11 Input extension library ii libxinerama11:1.0.2-1X11 Xinerama extension library ii libxrandr2 2:1.2.2-1X11 RandR extension library ii libxrender1 1:0.9.4-1X Rendering Extension client libra ii libxt6 1:1.0.5-3X11 toolkit intrinsics library ii perl5.8.8-12 Larry Wall's Practical Extraction ii zlib1g 1:1.2.3.3.dfsg-7 compression library - runtime Versions of packages kmail recommends: ii procmail 3.22-16Versatile e-mail processor -- no debconf information --- End Message --- --- Begin Message --- Version: 1:1.2.3-2 On Mon, Dec 10, 2007 at 10:34:55 +0100, Sune Vuorela wrote: > reassign 451332 xserver-xorg-input-mouse > forwarded 451332 https://bugs.freedesktop.org/show_bug.cgi?id=13144 > tags 451332 +fixed-upstream > thanks > > Hi debian-x > > When switching to a text console and back to X, occasionally a middle-button > click is emmitted. According to upstream it is fixed in the mouse driver in > commit 6a03e8bd9699a33dabcdd2bbcf51a001ddfd5534 > > see https://bugs.freedesktop.org/show_bug.cgi?id=13144 for details. > Already fixed. Cheers, Julien --- End Message ---
Processed: Re: Bug#423606: k3dsurf: segfault also on i368 and intel graphics
Processing commands for [EMAIL PROTECTED]: > reassign 423606 libgl1-mesa-dri Bug#423606: segmentation fault of k3dsurf on start up Bug reassigned from package `k3dsurf' to `libgl1-mesa-dri'. > severity 423606 important Bug#423606: segmentation fault of k3dsurf on start up Severity set to `important' from `serious' > thanks 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: Re: Bug#455310: Blender crashes with Segmentation fault
Processing commands for [EMAIL PROTECTED]: > reassign 455310 libgl1-mesa-dri Bug#455310: Blender crashes with Segmentation fault Bug reassigned from package `blender' to `libgl1-mesa-dri'. > thanks 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#455512: build target cannot be run after interrupted
Package: compiz
Version: latest
Severity: important
Tags: patch
See attached patch.
-- System Information:
Debian Release: lenny/sid
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-amd64
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8)
--- compiz-0.5.2.old/debian/rules 2007-12-10 16:20:21.0 +0100
+++ compiz-0.5.2/debian/rules 2007-12-10 15:49:32.0 +0100
@@ -44,7 +44,7 @@
build-stamp:
dh_testdir
- mkdir obj-$(DEB_BUILD_GNU_TYPE)
+ mkdir -p obj-$(DEB_BUILD_GNU_TYPE)
chmod +x ./configure
cd obj-$(DEB_BUILD_GNU_TYPE) && \
../configure --prefix=/usr --sysconfdir=\$${prefix}/share $(confflags) \
Bug#455515: please remove libmetacity0 (>= 1:2.15.21) shlibs override
Package: compiz Version: latest Severity: normal Tags: patch The libmetacity0 (>= 1:2.15.21) override in shlibs.local is AFAICT not necessary. Unless I got something wrong (from changelogs and your comments) it's only there to workaround an incorrect abi bump, which is no longer an issue on sid but prevents a backport to etch. I've verified that the current sid package has a working compiz-gtk when recompiled on etch (with other fixes unrelated to this one). -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-amd64 Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8) --- compiz-0.6.3~git20071104.c9009efd/debian/shlibs.local 2007-12-10 16:57:55.0 +0100 +++ compiz-0.6.3~git20071104.c9009efd.new/debian/shlibs.local 2007-12-10 16:53:06.0 +0100 @@ -1,2 +1 @@ -libmetacity-private 0 libmetacity0 (>= 1:2.15.21) libdecoration 0 libdecoration0 (>= 0.5.0)
Bug#455516: allow building with older libfuse (to ease backporting)
Package: compiz Version: latest Severity: wishlist Tags: patch These two patches let compiz build with the libfuse version that shipped in etch. Attached is the debian-specific part. The rest is in upstream BTS: http://bugs.freedesktop.org/show_bug.cgi?id=13588 -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-amd64 Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8) diff -ur -x configure -x config.h.in compiz-0.6.3~git20071104.c9009efd/debian/control compiz-0.6.3~git20071104.c9009efd.new/debian/control --- compiz-0.6.3~git20071104.c9009efd/debian/control2007-12-10 16:57:55.0 +0100 +++ compiz-0.6.3~git20071104.c9009efd.new/debian/control2007-12-10 16:53:25.0 +0100 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Debian X Strike Force Uploaders: Thierry Reding <[EMAIL PROTECTED]>, David Nusinow <[EMAIL PROTECTED]>, Sean Finney <[EMAIL PROTECTED]> -Build-Depends: debhelper (>= 5), quilt (>= 0.40), libglib2.0-dev, libgconf2-dev, libpng12-dev | libpng-dev, libxcomposite-dev (>= 1:0.3-2), libxfixes-dev (>= 1:4.0.1), libxdamage-dev (>=1:1.0.3), libxrandr-dev (>= 2:1.1.0.2), libxrender-dev (>= 1:0.9.1), libice-dev (>= 1:1.0.1), libsm-dev (>= 1:1.0.1), libgl1-mesa-dev (>= 6.5.1) | libgl-dev, libcairo-dev, librsvg2-dev, libgnome-desktop-dev, libgnome-window-settings-dev, libdbus-glib-1-dev, libwnck-dev, libgtk2.0-dev, libpango1.0-dev, x11proto-gl-dev (>= 1.4.8-1), libxinerama-dev, libxml-parser-perl, libmetacity-dev, kdebase-dev, libdbus-qt-1-dev, libfuse-dev (>= 2.7.0), xsltproc +Build-Depends: debhelper (>= 5), quilt (>= 0.40), libglib2.0-dev, libgconf2-dev, libpng12-dev | libpng-dev, libxcomposite-dev (>= 1:0.3-2), libxfixes-dev (>= 1:4.0.1), libxdamage-dev (>=1:1.0.3), libxrandr-dev (>= 2:1.1.0.2), libxrender-dev (>= 1:0.9.1), libice-dev (>= 1:1.0.1), libsm-dev (>= 1:1.0.1), libgl1-mesa-dev (>= 6.5.1) | libgl-dev, libcairo-dev, librsvg2-dev, libgnome-desktop-dev, libgnome-window-settings-dev, libdbus-glib-1-dev, libwnck-dev, libgtk2.0-dev, libpango1.0-dev, x11proto-gl-dev (>= 1.4.8-1), libxinerama-dev, libxml-parser-perl, libmetacity-dev, kdebase-dev, libdbus-qt-1-dev, libfuse-dev, xsltproc Standards-Version: 3.7.2 Package: compiz
Bug#455310: Blender crashes with Segmentation fault
Hello again, thank you for the answers. I will follow this bug, and I'm willing to give any more information that is necessary. Some comments bellow. Cyril Brulebois escreveu: reassign 455310 libgl1-mesa-dri thanks On 11/05/2008, Ivan Marin wrote: Tried to do that: LIBGL_ALWAYS_INDIRECT=1 blender and my system rebooted. Whole system? Or only X? Anyway, that's a bug in mesa/X, not in blender, reassigning accordingly. The entire system, not just X. Ok, I will follow the bug report. I can try to install the sid drivers and see if the problem goes away, as soon as I have some free time (not until new year's eve). With mesa-dbg: […] Thanks, looks like the one I received for #423606 (with which XSF might want to merge this bugreport, but since I'm not sure, not merging). glxgears runs ok, also some screensavers. The hardware is a macbook. Did not try with other 3D software. Thanks for the info you provided. Cheers, Cheers, Ivan
Processed: Re: Bug#455310: Blender crashes with Segmentation fault
Processing commands for [EMAIL PROTECTED]: > forcemerge 439668 455310 Bug#439668: blender crash Bug#455310: Blender crashes with Segmentation fault Bug#446315: xserver-xorg-video-ati: crashes in R and Blender, and incomlete drawing of glut (opengl) wire objects Forcibly Merged 439668 446315 455310. > 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#455310: Blender crashes with Segmentation fault
forcemerge 439668 455310 thank you Ivan Marin wrote: Hello again, thank you for the answers. I will follow this bug, and I'm willing to give any more information that is necessary. Some comments bellow. Given the backtrace (with triangle_twoside), this is probably #439668 which has been forwarded upstream at https://bugs.freedesktop.org/show_bug.cgi?id=12164 I am merging these bugs. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#452268: patched xf86-video-intel-2.2.0/src/i830_3d.c (i830 render fix)
Jos van Wolput wrote: I attached here a patched version of i830_3d.c according to http://bugs.freedesktop.org/attachment.cgi?id=12993 Download xserver-xorg-video-intel_2.2.0.orig.tar.gz, unpack and replace /xf86-video-intel-2.2.0/src/i830_3d.c by the attached patched version, ./configure --prefix=/usr ./make ./sudo make install and the i830 render failure will be fixed (tested only on a 855GM chip)! Or use the i386 package available in http://people.debian.org/~bgoglin/intel-exa/ I already asked the submitters of various similar bugs to test it. Unfortunately, it doesn't seem to help on i965 (that's why I unmerged your bug from the other ones). Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#455539: please bring back the -core metapackage
Package: xorg Version: latest Severity: wishlist Tags: patch I just did some tests (setup a bare-bones sid system, and then installed a working gnome/gdm/x11 environment by hand), and found that it is possible to obtain a working gnome desktop by just installing the following X components (and their dependencies): xserver-xorg, xfonts-base (>= 1:1.0.0-1), xfonts-100dpi (>= 1:1.0.0-1), xfonts-75dpi (>= 1:1.0.0-1), xfonts-scalable (plus the dependencies dragged in by gdm and gnome-core, of course). This really calls for an easy way to install the server and associated fonts without having to type (and remember/figure out) the whole list. Please, could you bring back the -core metapackage we used to have, and set it up so that it serves this purpose? (i.e. install a basic X11 server without any clients) See attached patch. -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-amd64 Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8) diff -ur xorg-7.3+7/debian/control xorg-7.3+7.new/debian/control --- xorg-7.3+7/debian/control 2007-11-27 04:05:25.0 +0100 +++ xorg-7.3+7.new/debian/control 2007-12-10 19:33:09.0 +0100 @@ -108,11 +108,23 @@ (Xorg). It does not provide any drivers itself, and may be removed if you wish to only have certain drivers installed. +Package: xorg-core +Architecture: all +Depends: xserver-xorg, xfonts-base (>= 1:1.0.0-1), xfonts-100dpi (>= 1:1.0.0-1), xfonts-75dpi (>= 1:1.0.0-1), xfonts-scalable (>= 1:1.0.0-1) +Provides: x-window-system-core +Description: X.Org X Window System (server only) + This metapackage provides the components for a standalone + workstation running the X Window System. It provides an X server and + a set of fonts. It doesn't, however, provide any X clients. + . + Higher level metapackages, such as those for desktop environments, can + depend on this package and simplify their dependencies. + Package: xorg Architecture: all -Depends: xserver-xorg, libgl1-mesa-glx | libgl1, libglu1-mesa, xfonts-base (>= 1:1.0.0-1), xfonts-100dpi (>= 1:1.0.0-1), xfonts-75dpi (>= 1:1.0.0-1), xfonts-scalable (>= 1:1.0.0-1), x11-apps, x11-session-utils, x11-utils, x11-xfs-utils, x11-xkb-utils, x11-xserver-utils, xauth, xinit, xfonts-utils, xkb-data, xterm | x-terminal-emulator, sparc-utils | not+sparc +Depends: xorg-core, libgl1-mesa-glx | libgl1, libglu1-mesa, x11-apps, x11-session-utils, x11-utils, x11-xfs-utils, x11-xkb-utils, x11-xserver-utils, xauth, xinit, xfonts-utils, xkb-data, xterm | x-terminal-emulator, sparc-utils | not+sparc Recommends: xorg-docs -Provides: x-window-system, x-window-system-core +Provides: x-window-system Description: X.Org X Window System This metapackage provides the components for a standalone workstation running the X Window System. It provides the X libraries, an X
Bug#455310: Blender crashes with Segmentation fault
Should I repost all the backtraces there? Any more info needed? Thank you Ivan Brice Goglin escreveu: forcemerge 439668 455310 thank you Ivan Marin wrote: Hello again, thank you for the answers. I will follow this bug, and I'm willing to give any more information that is necessary. Some comments bellow. Given the backtrace (with triangle_twoside), this is probably #439668 which has been forwarded upstream at https://bugs.freedesktop.org/show_bug.cgi?id=12164 I am merging these bugs. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#452167: xserver-xorg-core: xserver crashes briefly after startup of window manager
Hi, Julien Cristau wrote: > > After some crashes, the following lines appeared repeatedly at the end > > of Xorg.0.log: > > > > tossed event which came in late > > mieqEnequeue: out-of-order valuator event; dropping. > > > These lines mean that the server is stuck, but the SIGIO signal handler > is still getting run. > > Which window manager are you using? Can you try to see where the X > server is hanging using gdb (from another machine)? I am using IceWM. I'll try to run gdb on the X server, but probably not before next weekend. Cheers, Wolf -- The Geek will inherit the Earth. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[bts-link] source package xserver-xorg-video-intel
# # bts-link upstream status pull for source package xserver-xorg-video-intel # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #426548 # * https://bugs.freedesktop.org/show_bug.cgi?id=11432 # * remote status changed: NEEDINFO -> NEW usertags 426548 - status-NEEDINFO usertags 426548 + status-NEW # remote status report for #439210 # * https://bugs.freedesktop.org/show_bug.cgi?id=13456 # * remote status changed: ASSIGNED -> RESOLVED # * remote resolution changed: (?) -> FIXED usertags 439210 - status-ASSIGNED usertags 439210 + status-RESOLVED resolution-FIXED thanks
Re: Analysis On Getting Rid Of xresprobe
On Sat, Dec 08, 2007 at 05:34:34PM -0500, David Nusinow wrote: > One issue is that sometimes the monitor will fail to do a proper > DDC on one occasion, but succeed on another. I saw this happening when I was doing some laptop/projector testing a few weeks ago. It seemed that sometimes it'd return EDID of one, and sometimes the other. It seemed to make a difference whether the projector was attached during X start or not. This opens a bigger question - how exactly does DDC handle multi-monitor situations? From what I could tell of xresprobe there's sort of a single-monitor assumption woven in there, but I couldn't tell how deeply that assumption goes. I looked at docs for the DDC call, but it wasn't very illuminating; my assembly-fu is not strong though, so I might have missed something obvious. > > I'm concerned about this because the way things are scaling, this is > > going to become a larger and larger sore spot for all of us. Maybe we > > need to start (threatening to?) deprecate extremely out of date drivers, > > or become more proactive at recruiting driver maintainers, or even just > > publish task lists for them? > > Yeah, pci-rework will be the first real breaking point for the drivers. > Previously they all worked fine with the server updates. I could see SuSE > or Redhat porting a bunch of the legacy drivers so as to not piss off their > customers, but we may not want to wait around that long. Porting over to > pci-rework isn't too terribly difficult[0], but it does need to be done if > these drivers are going to survive. Otherwise we'll have to simply EOL the > drivers and tell people to use old versions or buy new hardware :-\ > > [0] http://wiki.x.org/wiki/PciReworkHowto Thanks for the link. Of course, some of the companies picking Linux are doing so for cost reasons (particularly in the embedded and educational areas), and similar thinking also leads them to cheap low-end hardware options that often include graphics chips that require the less mainstream drivers. My thinking is that having TODO lists in our back pockets (in addition to EOLing the drivers) would help here - if the company has already proceeded too far and can no longer alter their hardware and OS version choices, that would communicate the NRE work they'd need to fund. Ideally, future companies will do research prior to settling on their graphics chip choice, and would be able to use the TODO and EOL info to assist in their selection criteria, and either select better maintained options, or budget/arrange for the maintenance work. Bryce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[bts-link] source package mesa
# # bts-link upstream status pull for source package mesa # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #455310 # * https://bugs.freedesktop.org/show_bug.cgi?id=12164 # * remote status changed: (?) -> REOPENED usertags 455310 + status-REOPENED thanks
Re: Analysis On Getting Rid Of xresprobe
On Mon, Dec 10, 2007 at 01:48:27PM -0800, Bryce Harrington wrote: > On Sat, Dec 08, 2007 at 05:34:34PM -0500, David Nusinow wrote: > > One issue is that sometimes the monitor will fail to do a proper > > DDC on one occasion, but succeed on another. > > I saw this happening when I was doing some laptop/projector testing a > few weeks ago. It seemed that sometimes it'd return EDID of one, and > sometimes the other. It seemed to make a difference whether the > projector was attached during X start or not. > > This opens a bigger question - how exactly does DDC handle multi-monitor > situations? From what I could tell of xresprobe there's sort of a > single-monitor assumption woven in there, but I couldn't tell how deeply > that assumption goes. I looked at docs for the DDC call, but it wasn't > very illuminating; my assembly-fu is not strong though, so I might have > missed something obvious. Yeah, I don't understand this well myself. I've only skimmed the surface of that code, but I should probably dive in to it soon to make sure I understand it. Ideally the drivers will be ported over to randr1.2 and the issue will be solved, but I'm not so optimistic on that one. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#455682: This bug probably is the same as: http://bugs.debian.org/455310
I generated the bug report with the `reportbug' tool indicating it as another instance of #455310 in the hope that the backtrace of another person might be helpful. But probably using `reportbug' and than indicating the original bug is not the right way to add information to a bug report already existing? - Sorry for generating unnecessary work! Thanks again, Dietrich -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Blender crashes with Segmentation fault ( http://bugs.debian.org/455310 )
Processing commands for [EMAIL PROTECTED]: > forcemerge 455310 455682 Bug#455310: Blender crashes with Segmentation fault Bug#455682: libgl1-mesa-dri: Same as in the original bug report: Blender crashes immediately after the window frame poppes up... Bug#439668: blender crash Bug#446315: xserver-xorg-video-ati: crashes in R and Blender, and incomlete drawing of glut (opengl) wire objects Forcibly Merged 439668 446315 455310 455682. > thanks 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]
