Bug#412449: X will only run at 640x480 with Radeon Mobility M6
On Sun, 2007-02-25 at 18:20 -0800, Daniel wrote:
Package: xserver-xorg
Version: 7.1.0-12
Since aptitude upgrading recently the Xorg server will only run at
640x480 mode.
[...]
(--) RADEON(0): MergedFB: Virtual width 640
(--) RADEON(0): MergedFB: Virtual height 480
Does this patch help?
--
Earthling Michel Dänzer | http://tungstengraphics.com
Libre software enthusiast | Debian, X and DRI developer
diff --git a/src/radeon_mergedfb.c b/src/radeon_mergedfb.c
index 820ba4b..a851f1c 100644
--- a/src/radeon_mergedfb.c
+++ b/src/radeon_mergedfb.c
@@ -581,8 +581,8 @@ RADEONRecalcDefaultVirtualSize(ScrnInfoPtr pScrn)
info-CRT1XOffs = info-CRT2XOffs = 0;
maxh -= (info-CRT1XOffs + info-CRT2XOffs);
}
- pScrn-virtualX = maxh;
- pScrn-displayWidth = maxh;
+ pScrn-virtualX = MAX(pScrn-virtualX, maxh);
+ pScrn-displayWidth = MAX(pScrn-displayWidth, maxh);
xf86DrvMsg(pScrn-scrnIndex, X_PROBED, str, width, maxh);
} else {
if(maxh pScrn-display-virtualX) {
@@ -592,7 +592,7 @@ RADEONRecalcDefaultVirtualSize(ScrnInfoPtr pScrn)
}
if(!(pScrn-display-virtualY)) {
-pScrn-virtualY = maxv;
+ pScrn-virtualY = MAX(pScrn-virtualY, maxv);
xf86DrvMsg(pScrn-scrnIndex, X_PROBED, str, height, maxv);
} else {
if(maxv pScrn-display-virtualY) {
Bug#367979: x-window-system-core is broken/missing fonts.alias file?
reassign 367979 xfonts-utils thank you Hi Rusty, Do you still have this fonts.alias problem with current Xorg/Etch? Note that fonts.alias files are not included in packages, they are generated by postinst script when a new package adds some fonts. This is why dpkg -S didn't find anything. But there have been some reports about the postinst script failing. It might be the reason why you didn't have a fonts.alias in the misc/ directory. By the way, x-window-system-core does not exists anymore. I am reassigning this bug to xfonts-utils which contains the script to generate fonts.alias. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Bug#367979: x-window-system-core is broken/missing fonts.alias file?
Processing commands for [EMAIL PROTECTED]: reassign 367979 xfonts-utils Bug#367979: x-window-system-core is broken/missing fonts.alias file? Bug reassigned from package `x-window-system-core' to `xfonts-utils'. 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#407055: Compiz breaks the X server if the other head doesn't have DRI
Hi, I have a similar setup and a similar need, but differently from the described scenario, compiz breaks my X server when I try to start it. I think the difference from my case to the other case reported here is that I don't have any support for DRI in the other head, instead of having a bad DRI. I'm attaching the log from the server just before the break, I think this can help. As this bug not only makes compiz unusable, but also affects another programs, I'll raise it's severity. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed (with 4 errors): Raising severity as this bug crashes the X server.
Processing commands for [EMAIL PROTECTED]: severity 407055 critical Bug#407055: compiz: manages only screen 0 of a multi screen display Severity set to `critical' from `normal' thanks. Unknown command or malformed arguments to command. As already stated before, this bug makes compiz to crash the X server, Unknown command or malformed arguments to command. so it affects other packages. Unknown command or malformed arguments to command. daniel Unknown command or malformed arguments to command. 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#407055: Compiz breaks the X server if the other head doesn't have DRI
Qui, 2007-03-01 às 12:46 +0100, Brice Goglin escreveu:
On 3/1/07, Daniel Ruoso [EMAIL PROTECTED] wrote:
I'm attaching the log from the server just before the break, I think
this can help. As this bug not only makes compiz unusable, but also
affects another programs, I'll raise it's severity.
Did you forget to attach?
Ops...
Here it goes now...
daniel
X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: UNKNOWN
Current Operating System: Linux cajazeiras 2.6.18-4-686 #1 SMP Wed Feb 21
16:06:54 UTC 2007 i686
Build Date: 01 March 2007
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: Thu Mar 1 10:41:09 2007
(==) Using config file: /etc/X11/xorg.conf
(WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found
(EE) AIGLX: Screen 1 is not DRI capable
xkb_keycodes { include xfree86+aliases(qwerty) };
xkb_types{ include complete };
xkb_compatibility{ include complete };
xkb_symbols { include pc(pc105)+pt };
xkb_geometry { include pc(pc104) };
The XKEYBOARD keymap compiler (xkbcomp) reports:
Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols
Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
(EE) xf86OpenSerial: Cannot open device /dev/wacom
No such file or directory.
Error opening /dev/wacom : No such file or directory
(EE) xf86OpenSerial: Cannot open device /dev/wacom
No such file or directory.
Error opening /dev/wacom : No such file or directory
(EE) xf86OpenSerial: Cannot open device /dev/wacom
No such file or directory.
Error opening /dev/wacom : No such file or directory
(EE) xf86OpenSerial: Cannot open device /dev/wacom
No such file or directory.
Error opening /dev/wacom : No such file or directory
(EE) xf86OpenSerial: Cannot open device /dev/wacom
No such file or directory.
Error opening /dev/wacom : No such file or directory
(EE) xf86OpenSerial: Cannot open device /dev/wacom
No such file or directory.
Error opening /dev/wacom : No such file or directory
Synaptics DeviceInit called
SynapticsCtrl called.
Synaptics DeviceOn called
Synaptics DeviceOff called
Synaptics DeviceOn called
Backtrace:
0: X(xf86SigHandler+0x84) [0x80c4354]
1: [0xb7fe2420]
2:
/usr/lib/xorg/modules/extensions/libGLcore.so(_mesa_initialize_context+0x53f)
[0x900b2aaf]
3: /usr/lib/xorg/modules/extensions/libGLcore.so(XMesaCreateContext+0x77)
[0x9020a287]
4: /usr/lib/xorg/modules/extensions/libGLcore.so [0x90206f44]
5: /usr/lib/xorg/modules/extensions/libglx.so(DoCreateContext+0x10f)
[0xb7cab17f]
6: /usr/lib/xorg/modules/extensions/libglx.so(__glXCreateContext+0x44)
[0xb7cab994]
7: /usr/lib/xorg/modules/extensions/libglx.so [0xb7cadf6a]
8: X(Dispatch+0x19b) [0x8086cab]
9: X(main+0x489) [0x806e699]
10: /lib/tls/libc.so.6(__libc_start_main+0xc8) [0xb7de3ea8]
11: X(FontFileCompleteXLFD+0xa9) [0x806d9d1]
Fatal server error:
Caught signal 11. Server aborting
Processed: Raising severity as this bug crashes the X server.
Processing commands for [EMAIL PROTECTED]: found 407055 0.3.6-1 Bug#407055: compiz: manages only screen 0 of a multi screen display Bug marked as found in version 0.3.6-1. 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#407055: Compiz breaks the X server if the other head doesn't have DRI
Qui, 2007-03-01 às 11:55 +, Daniel Ruoso escreveu: Qui, 2007-03-01 às 12:46 +0100, Brice Goglin escreveu: On 3/1/07, Daniel Ruoso [EMAIL PROTECTED] wrote: I'm attaching the log from the server just before the break, I think this can help. As this bug not only makes compiz unusable, but also affects another programs, I'll raise it's severity. Did you forget to attach? Ops... Here it goes now... daniel Well, the version in experimental also breaks, but it presents a different backtrace... Backtrace: 0: X(xf86SigHandler+0x84) [0x80c4354] 1: [0xe420] 2: /usr/lib/xorg/modules/extensions/libGLcore.so(_mesa_free+0x1d) [0xa780d21d] 3: /usr/lib/xorg/modules/extensions/libGLcore.so(XMesaDestroyVisual +0x1d) [0xa7910e2d] 4: /usr/lib/xorg/modules/extensions/libGLcore.so [0xa791031f] 5: /usr/lib/xorg/modules/extensions/libglx.so(__glXResetScreens+0x44) [0xb7c76b04] 6: /usr/lib/xorg/modules/extensions/libglx.so [0xb7c75d2c] 7: X(CloseDownExtensions+0x42) [0x8093f12] 8: X(main+0x4a3) [0x806e6b3] 9: /lib/tls/libc.so.6(__libc_start_main+0xc8) [0xb7db3ea8] 10: X(FontFileCompleteXLFD+0xa9) [0x806d9d1] daniel
Bug#407055: Compiz breaks the X server if the other head doesn't have DRI
Daniel Ruoso wrote: Well, the version in experimental also breaks, but it presents a different backtrace... Do you onyl have compiz in experimental? Or also some other X packages? Which xserver-xorg-core do you have? The following backtrace seems to end up in xserver-xorg-core, you could try this package in experimental too :) Backtrace: 0: X(xf86SigHandler+0x84) [0x80c4354] 1: [0xe420] 2: /usr/lib/xorg/modules/extensions/libGLcore.so(_mesa_free+0x1d) [0xa780d21d] 3: /usr/lib/xorg/modules/extensions/libGLcore.so(XMesaDestroyVisual +0x1d) [0xa7910e2d] 4: /usr/lib/xorg/modules/extensions/libGLcore.so [0xa791031f] 5: /usr/lib/xorg/modules/extensions/libglx.so(__glXResetScreens+0x44) [0xb7c76b04] 6: /usr/lib/xorg/modules/extensions/libglx.so [0xb7c75d2c] 7: X(CloseDownExtensions+0x42) [0x8093f12] 8: X(main+0x4a3) [0x806e6b3] 9: /lib/tls/libc.so.6(__libc_start_main+0xc8) [0xb7db3ea8] 10: X(FontFileCompleteXLFD+0xa9) [0x806d9d1] How did you get this backtrace? It does not look like a complete backtrace with debugging information that gdb could give. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407055: Compiz breaks the X server if the other head doesn't have DRI
Qui, 2007-03-01 às 14:21 +0100, Brice Goglin escreveu: Daniel Ruoso wrote: Well, the version in experimental also breaks, but it presents a different backtrace... Do you onyl have compiz in experimental? Or also some other X packages? Which xserver-xorg-core do you have? The following backtrace seems to end up in xserver-xorg-core, you could try this package in experimental too :) Only compiz-related packages. But, yes, I can try xserver-xorg-core from experimental... Any other package? Backtrace: 0: X(xf86SigHandler+0x84) [0x80c4354] 1: [0xe420] 2: /usr/lib/xorg/modules/extensions/libGLcore.so(_mesa_free+0x1d) [0xa780d21d] 3: /usr/lib/xorg/modules/extensions/libGLcore.so(XMesaDestroyVisual +0x1d) [0xa7910e2d] 4: /usr/lib/xorg/modules/extensions/libGLcore.so [0xa791031f] 5: /usr/lib/xorg/modules/extensions/libglx.so(__glXResetScreens+0x44) [0xb7c76b04] 6: /usr/lib/xorg/modules/extensions/libglx.so [0xb7c75d2c] 7: X(CloseDownExtensions+0x42) [0x8093f12] 8: X(main+0x4a3) [0x806e6b3] 9: /lib/tls/libc.so.6(__libc_start_main+0xc8) [0xb7db3ea8] 10: X(FontFileCompleteXLFD+0xa9) [0x806d9d1] How did you get this backtrace? It does not look like a complete backtrace with debugging information that gdb could give. This appears in my X log file. I'm not even sure of who prints it out, but as the X server breaks, I would think this is printed by the x server itself. I don't know, but maybe this unveils a xorg bug, more than a compiz bug. Daniel
Bug#407055: Compiz breaks the X server if the other head doesn't have DRI
Daniel Ruoso wrote: Qui, 2007-03-01 às 14:21 +0100, Brice Goglin escreveu: Daniel Ruoso wrote: Well, the version in experimental also breaks, but it presents a different backtrace... Do you onyl have compiz in experimental? Or also some other X packages? Which xserver-xorg-core do you have? The following backtrace seems to end up in xserver-xorg-core, you could try this package in experimental too :) Only compiz-related packages. But, yes, I can try xserver-xorg-core from experimental... Any other package? Looking at the dependencies, mesa could be upgraded too... Backtrace: 0: X(xf86SigHandler+0x84) [0x80c4354] 1: [0xe420] 2: /usr/lib/xorg/modules/extensions/libGLcore.so(_mesa_free+0x1d) [0xa780d21d] 3: /usr/lib/xorg/modules/extensions/libGLcore.so(XMesaDestroyVisual +0x1d) [0xa7910e2d] 4: /usr/lib/xorg/modules/extensions/libGLcore.so [0xa791031f] 5: /usr/lib/xorg/modules/extensions/libglx.so(__glXResetScreens+0x44) [0xb7c76b04] 6: /usr/lib/xorg/modules/extensions/libglx.so [0xb7c75d2c] 7: X(CloseDownExtensions+0x42) [0x8093f12] 8: X(main+0x4a3) [0x806e6b3] 9: /lib/tls/libc.so.6(__libc_start_main+0xc8) [0xb7db3ea8] 10: X(FontFileCompleteXLFD+0xa9) [0x806d9d1] How did you get this backtrace? It does not look like a complete backtrace with debugging information that gdb could give. This appears in my X log file. I'm not even sure of who prints it out, but as the X server breaks, I would think this is printed by the x server itself. I don't know, but maybe this unveils a xorg bug, more than a compiz bug. Could you ssh from another machine and attach gdb to X before starting compiz ? (with gdb -p $(pidof X)) If would be great to do this with a server recompiled for debugging. If you want to do so, see how to build at http://wiki.debian.org/HowToGetABacktrace (with hello=xserver-xorg-core). Brice
Bug#412737: avoiding circular dependenies
I have been trying to install xserver-xorg along with just the xserver-xorg-input-* and xserver-xorg-video-* packages required for my hardware. However, no matter what my actual selections were, apt-get always tried to pull in all the depenencies in xserver-xorg-input-all and xserver-xorg-video-all. So I tried to do it step by step. Some of the dependencies may be met without introducing circular dependencies, such as installing xbase-clients and xkb-data. But as soon as any of the xserver-xorg-* packages are involved, various circular dependencies cause apt-get to install many more packages than actually required or desired. I have read through #362313. I don't follow the argument that drivers should depend on the server, even if they would be of little use otherwise. This would be like having libraries depend on the programs that make use of them. Libraries installed but not used by other packages are orphaned and may be removed any time. Same with drivers for the xserver. Of couse, there must be drivers for the server to work, but which ones depends on the hardware. Recommends to take care of this were already mentioned in #362313. Circular dependencies between two packages make logically absolutely no sense. As any of such two packages may never be install without the other, they might as well be merged into a single package. This is not to say that xserver-xorg and xserver-xorg-core should be merged but that their circular dependencies should be removed. This still applies to xserver-xorg-core (2:1.2.0-4) from experimental. Any circular dependencies between two or more packages should be avoided wherever possible. In case of xserver-xorg* I don't see a reason why circular dependencies should be required. Here is my suggestion (dependencies of packages other than xserver-xorg-* are not included): xserver-xorg Depends: xserver-xorg-core, xserver-xorg-video-1.0, xserver-xorg-input, ... Recommends: xserver-xorg-video-all, xserver-xorg-input-all, ... xserver-xorg-core Depends: ... xserver-xorg-video-* Depends: (empty) Provides: xserver-xorg-video-1.0 xserver-xorg-input-* Depends: (empty) Provides: xserver-xorg-input None of xserver-xorg-video-* and xserver-xorg-input-* should depend on xserver-xorg. This provides a clean dependency hierarchy. Drivers required to provide a working xserver for most machines are pulled in via Recommends. At the same time this should allow individual drivers to be pulled in with apt-get to fulfill dependencies for a minimal install for existing hardware. Hope I haven't overlooked something important. Regards Andreas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407055: Compiz breaks the X server if the other head doesn't have DRI
severity 407055 important reassign 407055 xserver-xorg-core thanks On Thu, Mar 1, 2007 at 11:37:09 +, Daniel Ruoso wrote: Hi, I have a similar setup and a similar need, but differently from the described scenario, compiz breaks my X server when I try to start it. I think the difference from my case to the other case reported here is that I don't have any support for DRI in the other head, instead of having a bad DRI. I'm attaching the log from the server just before the break, I think this can help. As this bug not only makes compiz unusable, but also affects another programs, I'll raise it's severity. Crashes of the X server are usually bugs in the server, not the clients, and are usually of important severity. Please rebuild the server (from experimental) with debugging symbols, and get a backtrace from gdb (you'll need to use gdb from an ssh connection or similar). Thanks, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#407055: Compiz breaks the X server if the other head doesn't have DRI
Processing commands for [EMAIL PROTECTED]: severity 407055 important Bug#407055: compiz: manages only screen 0 of a multi screen display Severity set to `important' from `critical' reassign 407055 xserver-xorg-core Bug#407055: compiz: manages only screen 0 of a multi screen display Bug reassigned from package `compiz' to `xserver-xorg-core'. 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]
xserver-xorg-video-suncg6: Changes to 'debian-unstable'
debian/changelog |6 --
debian/control |2 +-
2 files changed, 5 insertions(+), 3 deletions(-)
New commits:
commit 096b9b9a9f417116931cb085edd9cbad41312b46
Author: Julien Cristau [EMAIL PROTECTED]
Date: Thu Mar 1 17:36:00 2007 +0100
Change Provides from xserver-xorg-video-1 to xserver-xorg-video-1.0.
diff --git a/debian/changelog b/debian/changelog
index 8f979ce..9b31f2b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,11 +1,13 @@
-xserver-xorg-video-suncg6 (1:1.1.0-3) UNRELEASED; urgency=low
+xserver-xorg-video-suncg6 (1:1.1.0-3) unstable; urgency=high
* Add link to xserver-xorg-core bug script, so that bugreports contain
the user's config and log files.
* Bump dependency on xserver-xorg-core to = 2:1.1.1-11, as previous
versions don't have the bug script.
+ * Provide xserver-xorg-video-1.0, like all other video drivers, instead of
+xserver-xorg-video-1.
- -- Julien Cristau [EMAIL PROTECTED] Tue, 7 Nov 2006 07:30:44 +0100
+ -- Julien Cristau [EMAIL PROTECTED] Thu, 1 Mar 2007 17:30:13 +0100
xserver-xorg-video-suncg6 (1:1.1.0-2) unstable; urgency=low
diff --git a/debian/control b/debian/control
index 3ee5242..3023967 100644
--- a/debian/control
+++ b/debian/control
@@ -9,7 +9,7 @@ Standards-Version: 3.7.2.0
Package: xserver-xorg-video-suncg6
Architecture: sparc
Depends: ${shlibs:Depends}, ${misc:Depends}, xserver-xorg-core (= 2:1.1.1-11)
-Provides: xserver-xorg-video-1
+Provides: xserver-xorg-video-1.0
Replaces: xserver-xorg ( 6.8.2-35)
Description: X.Org X server -- Sun CG6 display driver
This package provides the driver for Sun CG6 video devices.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#412962: xorg-common duplicates x11-common
Package: xorg-common Version: 6.8.2-10 Severity: normal xorg-common duplicates x11-common in /etc/X11/Xsession.d/ Either of packages needs to be removed (put in conflicts) Best regards Andrei Emeltchenko -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18 Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Versions of packages xorg-common depends on: ii debconf 1.5.11 Debian configuration management sy ii debianutils 2.17 Miscellaneous utilities specific t ii lsb-base 3.1-23 Linux Standard Base 3.1 init scrip xorg-common recommends no packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#412962: xorg-common duplicates x11-common
Processing commands for [EMAIL PROTECTED]: reassign 412962 xorg Bug#412962: xorg-common duplicates x11-common Warning: Unknown package 'xorg-common' Bug reassigned from package `xorg-common' to `xorg'. -- 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]
xserver-xorg-video-suncg6: Changes to 'refs/tags/xserver-xorg-video-suncg6-1_1.1.0-3'
Tag 'xserver-xorg-video-suncg6-1_1.1.0-3' created by Julien Cristau [EMAIL PROTECTED] at 2007-03-01 17:31 +0100 Tagging upload of xserver-xorg-video-suncg6 1:1.1.0-3 to unstable. Changes since 1_1.1.0-2: Branden Robinson: Set svn:keywords property to Id (keyword already present). Note probable out-of-dateness of maplink() function body. Add high-level documentation to XSFBS shell library, intended to reduce David Nusinow: Move xsfbs back to its rightful place Make us error out if we call patch and don't have quilt installed Fix the last commit and fix spelling error. Thanks Brice Goglin for the spelling catch. Fix for bug #371152. Thanks Joey Hess. Pull patches from ubuntu for ARCHITECTURE, LAPTOP, RECONFIGURE, FIRSTINST, and UPGRADE variables Move the files so they'll be put in debian/xsfbs automatically when pulled Merge branch 'xsfbs' into debian-unstable Julien Cristau: For each driver, add a symlink to xserver-xorg-core's bug script, so that each Change Provides from xserver-xorg-video-1 to xserver-xorg-video-1.0. --- debian/changelog | 11 debian/control |4 debian/xserver-xorg-video-suncg6.links |1 debian/xsfbs/xsfbs-autoreconf.mk | 150 + debian/xsfbs/xsfbs.mk | 359 + debian/xsfbs/xsfbs.sh | 907 + 6 files changed, 1430 insertions(+), 2 deletions(-) --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of xserver-xorg-video-suncg6_1.1.0-3_sparc.changes
xserver-xorg-video-suncg6_1.1.0-3_sparc.changes uploaded successfully to localhost along with the files: xserver-xorg-video-suncg6_1.1.0-3.dsc xserver-xorg-video-suncg6_1.1.0-3.diff.gz xserver-xorg-video-suncg6_1.1.0-3_sparc.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#412962: marked as done (xorg-common duplicates x11-common)
Your message dated Thu, 1 Mar 2007 18:29:33 +0100 with message-id [EMAIL PROTECTED] and subject line xorg-common duplicates x11-common 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: xorg-common Version: 6.8.2-10 Severity: normal xorg-common duplicates x11-common in /etc/X11/Xsession.d/ Either of packages needs to be removed (put in conflicts) Best regards Andrei Emeltchenko -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18 Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Versions of packages xorg-common depends on: ii debconf 1.5.11 Debian configuration management sy ii debianutils 2.17 Miscellaneous utilities specific t ii lsb-base 3.1-23 Linux Standard Base 3.1 init scrip xorg-common recommends no packages. ---End Message--- ---BeginMessage--- On Thu, Mar 1, 2007 at 11:53:49 +0200, Andrei Emeltchenko wrote: Package: xorg-common Version: 6.8.2-10 Severity: normal xorg-common duplicates x11-common in /etc/X11/Xsession.d/ Either of packages needs to be removed (put in conflicts) There is no such thing as a xorg-common package in Debian. Did you install this from ubuntu or some other external repository at some point? Closing this bug. Cheers, Julien ---End Message---
xserver-xorg-video-suncg6_1.1.0-3_sparc.changes ACCEPTED
Accepted: xserver-xorg-video-suncg6_1.1.0-3.diff.gz to pool/main/x/xserver-xorg-video-suncg6/xserver-xorg-video-suncg6_1.1.0-3.diff.gz xserver-xorg-video-suncg6_1.1.0-3.dsc to pool/main/x/xserver-xorg-video-suncg6/xserver-xorg-video-suncg6_1.1.0-3.dsc xserver-xorg-video-suncg6_1.1.0-3_sparc.deb to pool/main/x/xserver-xorg-video-suncg6/xserver-xorg-video-suncg6_1.1.0-3_sparc.deb Override entries for your package: xserver-xorg-video-suncg6_1.1.0-3.dsc - source x11 xserver-xorg-video-suncg6_1.1.0-3_sparc.deb - optional x11 Announcing to debian-devel-changes@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413009: xorg-server: [ia64] PCI domain mismatch - DRI unusable
Package: xorg-server Version: 2:1.1.1-19 Severity: normal Tags: patch Hi, ISTR this bug was filed already but since I can't find it anymore in the BTS, yet the bug is still there, I'm sending this bugreport. The attached hack comes from this bugreport: https://bugs.freedesktop.org/show_bug.cgi?id=7770 which explains at length what's going on. Basically, there's a PCI domain mismatch between X server and the kernel, leaving clients unable to use direct rendering, which this one-liner fixes. This bug has been there for quite a long time (at least since the 1.0.X releases) and is a real PITA. And yes, I'm using a desktop ia64 system :) HTH T-Bone Other relevant data: [EMAIL PROTECTED]:~$ glxinfo name of display: :0.0 libGL error: open DRM failed (Operation not permitted) libGL error: reverting to (slow) indirect rendering display: :0 screen: 0 direct rendering: No [EMAIL PROTECTED]:~$ ls -l /dev/dri/card0 crw-rw-rw- 1 root root 226, 0 2007-03-01 18:44 /dev/dri/card0 in /var/log/Xorg.0.log: [...] (II) Initializing built-in extension XEVIE drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 11, (OK) drmOpenByBusid: Searching for BusID pci:0001:00:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 11, (OK) drmOpenByBusid: drmOpenMinor returns 11 drmOpenByBusid: drmGetBusid reports pci::00:00.0 drmOpenDevice: node name is /dev/dri/card1 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -19 drmOpenDevice: node name is /dev/dri/card2 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -19 drmOpenDevice: node name is /dev/dri/card3 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -19 drmOpenDevice: node name is /dev/dri/card4 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -19 drmOpenDevice: node name is /dev/dri/card5 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -19 drmOpenDevice: node name is /dev/dri/card6 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -19 drmOpenDevice: node name is /dev/dri/card7 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -19 drmOpenDevice: node name is /dev/dri/card8 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -19 drmOpenDevice: node name is /dev/dri/card9 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -19 drmOpenDevice: node name is /dev/dri/card10 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -19 drmOpenDevice: node name is /dev/dri/card11 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -19 drmOpenDevice: node name is /dev/dri/card12 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -19 drmOpenDevice: node name is /dev/dri/card13 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -19 drmOpenDevice: node name is /dev/dri/card14 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -19 (EE) AIGLX error: drmOpen failed (Operation not permitted) (EE) AIGLX: reverting to software rendering -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: ia64 Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-mckinley Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) diff --git a/hw/xfree86/dri/dri.c b/hw/xfree86/dri/dri.c index 7b4d5bd..1715590 100644 --- a/hw/xfree86/dri/dri.c +++ b/hw/xfree86/dri/dri.c @@ -249,6 +249,8 @@ DRIScreenInit(ScreenPtr pScreen, DRIInfo return FALSE; } +pDRIPriv-pDriverInfo-busIdString = drmGetBusid(fd); +
Bug#410068: I can confirm the same bug.
My X also randomly crashes. I can be doing anything --- in the middle of an xemacs edit, and it crashes hard with a SIG 11 every few days. My Xorg.log.bak file from the most recent crash Backtrace: 0: X(xf86SigHandler+0x84) [0x80c4354] 1: [0xe420] 2: X(Dispatch+0x81) [0x8086b91] 3: X(main+0x489) [0x806e699] 4: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0x45aa7ea8] 5: X(FontFileCompleteXLFD+0xa9) [0x806d9d1] I do have one thing to add. This problem is new. My machine has been functioning unchanged with the same xorg configuration and hardware since october. I run a dual monitor setup with DRM disabled. All versions after: X Window System Version 7.1.1 Release Date: 12 May 2006 Build Date: 09 January 2007 crash. HOWEVER, I never once had a crash with X Window System Version 7.1.1 Release Date: 12 May 2006 Build Date: 07 July 2006 or any earlier version over the course of several months. I do know that the last non-crashing version of X was invoked on Jan 7th, and the next X restart on Jan 26th was the first version that ever crashed on me. I don't know exactly when I upgraded. I can't supply an xorg.log for the non-crashing version but I can show a full STDERR from X for both versions. I can supply the full logfile (should I attach?) and if my install contains symbols, I can run it under GDB. If you can help me find/install the appropriate packages, I can delta-search to find where exactly the crashes started. Scott /// log file exerpt for the crashing version /// X Window System Version 7.1.1 Release Date: 12 May 2006 X Protocol Version 11, Revision 0, Release 7.1.1 Build Operating System: UNKNOWN Current Operating System: Linux dragonlight 2.6.20 #1 Tue Feb 6 14:47:52 CST 2007 i686 Build Date: 09 January 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present (--) PCI:*(2:0:0) ATI Technologies Inc RV350 AS [Radeon 9550] rev 0, Mem @ 0xc000/27, 0xd200/16, I/O @ 0xa000/8 (--) PCI: (2:0:1) ATI Technologies Inc RV350 ? [Radeon 9550] (Secondary) rev 0, Mem @ 0xc800/27, 0xd201/16 (II) ATI: ATI driver (version 6.6.3) for chipsets: ati, ativga (II) Primary Device is: PCI 02:00:0 (WW) RADEON: No matching Device section for instance (BusID PCI:2:0:1) found (II) Setting vga for screen 0. (**) RADEON(0): RADEONPreInit (II) RADEON(0): MMIO registers at 0xd200: size 64KB (II) RADEON(0): PCI bus 2 card 0 func 0 (**) RADEON(0): Depth 24, (--) framebuffer bpp 32 (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) (==) RADEON(0): Default visual is TrueColor (**) RADEON(0): Option GARTSize 256 (**) RADEON(0): Option EnablePageFlip true (**) RADEON(0): Option FBTexPercent 20 (**) RADEON(0): Option AccelDFS true (**) RADEON(0): Option DDCMode true (**) RADEON(0): Option MergedFB true (**) RADEON(0): Option CRT2Position RightOf (**) RADEON(0): Option MergedDPI 100 100 (**) RADEON(0): Option SubPixelOrder RGB (**) RADEON(0): Option DynamicClocks true drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed [drm] failed to load kernel module radeon (EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM [dri] Disabling DRI. (II) RADEON(0): Generation 2 PCI interface, using max accessible memory (II) RADEON(0): Detected total video RAM=131072K, accessible=131072K (PCI BAR=131072K) (--) RADEON(0): Mapped VideoRAM: 131072 kByte (64 bit DDR SDRAM) (==) RADEON(0): Using XAA acceleration architecture -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#24706: xdm: full-force SAINT attack crashes xdm
Hi, About 9 years ago, you reported a bug to the Debian BTS regarding a SAINT attack crashing xdm. Did you reproduce this problem recently? With Xorg/Etch? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385463: This contains more options.
According to strings, /usr/bin/glxgears contains: -display -info -stereo -fullscreen -iacknowledgethatthistoolisnotabenchmark -printfps Also, the current git source of mesa only has these options in glxgears.c: -display -info -stereo -fullscreen The current version included in mesa-utils 6.3.2-1 (the one strings was run against) does not include a usage message, but later versions (e.g. the one from git) do. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#303689: marked as done (xdm: sets up signal handlers that call unsafe functions)
Your message dated Thu, 01 Mar 2007 21:10:30 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#303689: xdm: sets up signal handlers that call unsafe functions 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: xdm Severity: important /etc/logrotate.d/xdm manages to delete the /var/log/xdm.log currently in use, and never signals xdm to reopen its log file. Since xdm usually stays running for weeks at a time, and the log is 'rotated' daily, this means that most of the time xdm is writing to a deleted file. Which is less than helpful. That's the worst logrotate file I've seen in quite a while. -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | `. `' | `- -- | signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- The logrotate script has been fixed a while ago, closing. Brice ---End Message---
Bug#361924: xdm segfaults when restarting X
Hi, About a year ago, you reported (or replied to) a bug in the Debian BTS regarding a segfault of xdm when restarting X. Did any of you guys reproduce this problem recently? With Xorg/Etch? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#121442: xdm: crashes with pam_mkhomedir if directory doesn't already exist
About 5 years ago, you reported a bug to the Debian BTS regarding xdm crashing with pam_mkhomedir if the directory doesn't already exist. Did you reproduce this problem recently? With Xorg/Etch? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#74457: marked as done (xdm: login widget doesn't recognize AltGr key)
Your message dated Thu, 01 Mar 2007 21:44:05 +0100
with message-id [EMAIL PROTECTED]
and subject line Bug#74457: xdm: login widget doesn't recognize AltGr key
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: xdm
Version: 3.3.6-10
Severity: normal
somehow it is impossible to enter these chars in the login widget:
@[]{}\~|
I use XkbLayout de, XkbVariant nodeadkeys and therefore all those
chars must be input when holding down the AltGr key. For example @ is
generated by AltGr-q.
Uhm, yes, usually I do not put these chars in login names or passwords,
but my users do.
Is there a way to work around this problem?
Rainer
- System Information
Debian Release: 2.2
Architecture: i386
Kernel: Linux warp 2.2.13-warp.3.2 #1 SMP Sun Jan 2 11:20:28 CET 2000 i686
Versions of packages xdm depends on:
ii cpp 1:2.95.2-13 The GNU C preprocessor.
ii libc62.1.3-10GNU C Library: Shared libraries an
ii xbase-clients3.3.6-10miscellaneous X clients
ii xlib6g 3.3.6-10shared libraries required by X cli
-- Configuration Files:
/etc/X11/xdm/Xaccess changed [not included]
/etc/X11/xdm/Xservers changed [not included]
/etc/X11/xdm/xdm.options changed [not included]
---End Message---
---BeginMessage---
alt-gr seems to work ok now, closing this very old bug.
Brice
---End Message---
Bug#354713: xdm: sometimes hangs in malloc's futex
About a year ago, you reported a bug to the Debian BTS regarding xdm hanging in malloc's futex. Did you reproduce this problem recently? With Xorg/Etch? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#158983: xdm: Occasionally declares session dead, even for sessions on the local machine
About 4 years ago, you reported a bug to the Debian BTS regarding xdm declaring the session dead occasionaly. Did you reproduce this problem recently? With Xorg/Etch? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
xdm: Changes to 'debian-unstable'
debian/changelog |7 +++
debian/control |1 +
2 files changed, 8 insertions(+)
New commits:
commit dd2c9398e08e8539d82533207a5eddfffa4ea694
Author: Brice Goglin [EMAIL PROTECTED]
Date: Thu Mar 1 22:09:05 2007 +0100
* Restore Provides: x-display-manager which got lost during transition
to modular packages. (closes: #384686).
diff --git a/debian/changelog b/debian/changelog
index 7c0f6ec..690b0b3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+xdm (1:1.1.4-2) UNRELEASED; urgency=low
+
+ * Restore Provides: x-display-manager which got lost during transition
+to modular packages. (closes: #384686).
+
+ -- Brice Goglin [EMAIL PROTECTED] Thu, 1 Mar 2007 22:05:26 +0100
+
xdm (1:1.1.4-1) experimental; urgency=low
* New upstream release.
diff --git a/debian/control b/debian/control
index 023b0d8..91b65a0 100644
--- a/debian/control
+++ b/debian/control
@@ -10,6 +10,7 @@ Package: xdm
Architecture: any
Depends: ${shlibs:Depends}, debconf (= 1.2.9) | debconf-2.0, xbase-clients |
xmessage, cpp
Pre-Depends: x11-common (= 1:7.0.0)
+Provides: x-display-manager
Suggests: sessreg | xutils
Description: X display manager
xdm manages a collection of X servers, which may be on the local host or
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#167517: marked as done (xdm: $DISPLAY not passed to session reset scripts, contradicting manpage)
Your message dated Thu, 01 Mar 2007 22:30:35 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#167517: xdm: $DISPLAY not passed to session reset scripts, contradicting manpage 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: xdm Version: 4.2.1-4 Severity: normal Tags: upstream The xdm manpage says that all the same variables are passed to reset scripts as to the startup scripts. But that's wrong. DISPLAY is not passed to the reset script. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux apocalypse 2.4.18 #1 Fri May 3 19:03:16 EST 2002 i686 Locale: LANG=C, LC_CTYPE=C Versions of packages xdm depends on: ii cpp 2:2.95.4-17 The GNU C preprocessor. ii debconf 1.2.14 Debian configuration management sy ii libc62.3.1-3 GNU C Library: Shared libraries an ii libpam0g 0.76-7 Pluggable Authentication Modules l ii libxaw7 4.2.1-4 X Athena widget set library ii xbase-clients4.2.1-4 miscellaneous X clients ii xlibs4.2.1-4 X Window System client libraries -- debconf information: * xdm/default_servers_100dpi: * shared/default-x-display-manager: xdm * xdm/default_servers_nolisten_tcp: xdm/stop_running_server_with_children: true xdm/daemon_name: /usr/bin/X11/xdm * xdm/default_nolisten_udp: ---End Message--- ---BeginMessage--- DISPLAY seems to be passed correctly to the reset script with Etch. Closing. Brice ---End Message---
Bug#262712: xdm hangs at kde logout when using pam_ldap
About 2 years ago, you reported a bug to the Debian BTS regarding xdm hanging at kde logout when using pam_ldap. Did you reproduce this problem recently? With Xorg/Etch? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#354264: marked as done (xdm restarts while install/update)
Your message dated Thu, 01 Mar 2007 22:43:02 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#354264:xdm restarts while install/update 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: xdm Version: 6.9.0.dfsg.1-4 Severity: normal xdm restarts at his updates, which causes killing xserver with all aps it running, including xterm with apt-get, which installing the newer version of xdm =). In result, not all installing packages been properly configured, and system need run dpkg --configure -a. Before latest versions this poor behavior of xdm has not been spoted. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14ma-pre Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Versions of packages xdm depends on: ii cpp 4:4.0.2-2 The GNU C preprocessor (cpp) ii debconf [debconf-2.0] 1.4.70 Debian configuration management sy ii libc6 2.3.6-1GNU C Library: Shared libraries an ii libice6 6.9.0.dfsg.1-4 Inter-Client Exchange library ii libpam-modules0.79-3.1 Pluggable Authentication Modules f ii libpam-runtime0.79-3.1 Runtime support for the PAM librar ii libpam0g 0.79-3.1 Pluggable Authentication Modules l ii libselinux1 1.28-4 SELinux shared libraries ii libsm66.9.0.dfsg.1-4 X Window System Session Management ii libx11-6 6.9.0.dfsg.1-4 X Window System protocol client li ii libxau6 6.9.0.dfsg.1-4 X Authentication library ii libxaw8 6.9.0.dfsg.1-4 X Athena widget set library ii libxdmcp6 6.9.0.dfsg.1-4 X Display Manager Control Protocol ii libxext6 6.9.0.dfsg.1-4 X Window System miscellaneous exte ii libxinerama1 6.9.0.dfsg.1-4 X Window System multi-head display ii libxmu6 6.9.0.dfsg.1-4 X Window System miscellaneous util ii libxp66.9.0.dfsg.1-4 X Window System printing extension ii libxpm4 6.9.0.dfsg.1-4 X pixmap library ii libxt66.9.0.dfsg.1-4 X Toolkit Intrinsics ii xbase-clients 6.9.0.dfsg.1-4 miscellaneous X clients xdm recommends no packages. -- debconf information: * shared/default-x-display-manager: xdm xdm/stop_running_server_with_children: false xdm/daemon_name: /usr/bin/X11/xdm ---End Message--- ---BeginMessage--- Version: 1:1.0.5-2 I can't reproduce with Etch, closing. Brice ---End Message---
Bug#239651: marked as done (xdm: don't invoke non existent Xreset)
Your message dated Thu, 01 Mar 2007 22:45:19 +0100
with message-id [EMAIL PROTECTED]
and subject line Bug#239651: xdm: don't invoke non existent Xreset
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: xdm
Version: 4.3.0-7
Severity: normal
$ dlocate -L xdm|LC_ALL=C xargs zgrep Xreset
/etc/X11/xdm/xdm-config:DisplayManager*reset:
/usr/X11R6/lib/X11/xdm/Xreset
that file doesn't exist anymore !! so don't try to invoke it
/usr/X11R6/man/man1/xdm.1x.gz:or \fIXreset\fP.
mentioned several times in man page, but not mentioned that it is gone now
/usr/share/man/man5/xdm.options.5.gz:.I /etc/X11/xdm/Xreset
same
/usr/share/doc/xdm/changelog.Debian.gz: * Drop the
/etc/X11/xdm/{Xreset,Xsetup} conffiles.
yes, but also please do the above cleanups
---End Message---
---BeginMessage---
Version: 1:1.0.5-2
This file does not seem to be invoked anymore in Etch, closing.
Brice
---End Message---
Bug#118677: xdm: suboptimal handling of logins when /etc/nologin is present
severity 118677 wishlist retitle 118677 xdm: should display contents of /etc/nologin when present thank you Logging as root with /etc/nologin present in Etch works fine. the remaining part of the bug is a wishlist. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Bug#118677: xdm: suboptimal handling of logins when /etc/nologin is present
Processing commands for [EMAIL PROTECTED]: severity 118677 wishlist Bug#118677: xdm: suboptimal handling of logins when /etc/nologin is present Severity set to `wishlist' from `normal' retitle 118677 xdm: should display contents of /etc/nologin when present Bug#118677: xdm: suboptimal handling of logins when /etc/nologin is present Changed Bug title. 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#121442: marked as done (xdm: crashes with pam_mkhomedir if directory doesn't already exist)
Your message dated Thu, 01 Mar 2007 22:52:00 +0100 with message-id [EMAIL PROTECTED] and subject line submitter address invalid 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: xdm Version: 4.1.0-9 Severity: important Attempting to login through xdm with a LDAP/NSS background fails if the home directory doesn't exist and pam_mkhomedir.so is being used. User bob1 can login, $HOME was made by mkhomedir with ssh user bob2 cannot, $HOME doesn't exist Neither user is mentioned in /etc/passwd, data is retrieved over ldap. /etc/pam.d/xdm reads: authrequiredpam_nologin.so authrequiredpam_env.so authrequiredpam_ldap.so account requiredpam_ldap.so passwordrequiredpam_ldap.so session requiredpam_unix.so session requiredpam_mkhomedir.so skel=/etc/skel umask=0022 pam.d/ssh, which is successfully creates $HOME, reads: auth required pam_nologin.so auth required pam_ldap.so auth required pam_env.so # [1] accountrequired pam_ldap.so sessionrequired pam_unix.so sessionoptional pam_lastlog.so # [1] sessionoptional pam_motd.so # [1] sessionoptional pam_mail.so standard # [1] sessionrequired pam_limits.so sessionrequired pam_mkhomedir.so skel=/etc/skel/ umask=0022 password required pam_ldap.so The last of xdm.log reads: xdm error (pid 2424): Unknown session exit code 2816 from process 2480 X connection to :0.0 broken (explicit kill or server shutdown). This is up-to-date woody as of 2001-11-27, kernel 2.5.1-pre1 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed | Name VersionDescription +++-==-==-ii libc6 2.2.4-5GNU C Library: Shared libraries and Timezoneii xdm4.1.0-9X display manager ii libpam-modules 0.72-33Pluggable Authentication Modules for PAM ii libpam-runtime 0.72-33Runtime support for the PAM library ii libpam0g 0.72-33Pluggable Authentication Modules library ii libpam-ldap118-1 Pluggable Authentication Module allowing LDAii libnss-ldap172-1 NSS module for using LDAP as a naming servicii nscd 2.2.4-5GNU C Library: Name Service Cache Daemon Matthew -- GIT/CM/M d++(-) s++: a---? C UL$ P+++ L+++ E++ W-- N+ o? K++ w--- O-- M+ V? PS+++ PE(--) Y+++ PGP+++@ t+ 5-- X+(-) R tv- b++ DI D++ G++ e(*) h!++ r-- y- ---End Message--- ---BeginMessage--- Closing since the submitter's address is invalid. If anybody ever reproduces this problem, feel free to reopen. Brice ---End Message---
Bug#163935: marked as done (xdm: won't start at depth 8 because debian.xpm exhausts colormap)
Your message dated Thu, 01 Mar 2007 22:56:14 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#163935: xdm: won't start at depth 8 because debian.xpm exhausts colormap 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: xdm Version: 4.2.1-1 Thanks for 4.2!! Problem with starting xdm (it wouldn't). I've traced it down to the following: polya:~ $ sxpm /usr/X11R6/lib/X11/xdm/pixmaps/debian.xpm Read Xpm Error: Failed to parse or alloc some color. I'm on an 8-bit display, which probably has a lot to do with it. Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London website: http://www.maths.qmul.ac.uk/~jdg/ Debian GNU/Linux Developer, see: http://people.debian.org/~jdg/ Visit http://www.thehungersite.com/ to help feed the hungry ---End Message--- ---BeginMessage--- Closing since the bug was supposed to be fixed a while ago, and the submitter never said whether he could reproduce after the ping last year. Brice ---End Message---
Bug#113270: xdm: xdm login fails when password soon expires and warning is issued
Hi, About 5 years ago, you reported a bug to the Debian BTS regarding xdm logging failure when user passwd is expiring soon. Did you reproduce this problem recently? With Xorg/Etch? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#262712: marked as done (xdm hangs at kde logout when using pam_ldap)
Your message dated Thu, 01 Mar 2007 22:52:00 +0100 with message-id [EMAIL PROTECTED] and subject line submitter address invalid 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: xdm Version: 4.3.0.dfsg.1-4 Debian : testing (sarge) Kernel : 2.4.26-1-k7 Libc : 2.3.2-1 xdm hang after a kde logout when I'm using it with pam_ldap : /etc/pam.d/common-account : # # /etc/pam.d/common-account - authorization settings common to all servic= es # # This file is included from other service-specific PAM config files, # and should contain a list of the authorization modules that define # the central access policy for use on the system. The default is to # only deny service to users whose accounts are expired in /etc/shadow. # account sufficient pam_ldap.so account required pam_unix.so /etc/pam.d/common-auth : # # /etc/pam.d/common-auth - authentication settings common to all services # # This file is included from other service-specific PAM config files, # and should contain a list of the authentication modules that define # the central authentication scheme for use on the system # (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the # traditional Unix authentication mechanisms. # auth sufficient pam_ldap.so auth required pam_unix.so nullok_secure /etc/pam.d/common-password # # /etc/pam.d/common-password - password-related modules common to all services # # This file is included from other service-specific PAM config files, # and should contain a list of modules that define the services to be #used to change user passwords. The default is pam_unix # The nullok option allows users to change an empty password, else # empty passwords are treated as locked accounts. # # (Add `md5' after the module name to enable MD5 passwords) # # The obscure option replaces the old `OBSCURE_CHECKS_ENAB' option in # login.defs. Also the min and max options enforce the length of the # new password. password sufficient pam_ldap.so password required pam_unix.so nullok obscure min=3D4 max=3D8 md5 # Alternate strength checking for password. Note that this # requires the libpam-cracklib package to be installed. # You will need to comment out the password line above and # uncomment the next two in order to use this. # (Replaces the `OBSCURE_CHECKS_ENAB', `CRACKLIB_DICTPATH') # # password required pam_cracklib.so retry=3D3 minlen=3D6 difok=3D3 # password required pam_unix.so use_authtok nullok md5 /etc/pam.d/common-session # # /etc/pam.d/common-session - session-related modules common to all servi= ces # # This file is included from other service-specific PAM config files, # and should contain a list of modules that define tasks to be performed # at the start and end of sessions of *any* kind (both interactive and # non-interactive). The default is pam_unix. # session sufficient pam_ldap.so session required pam_unix.so To solve the problem, I've got to put this in /etc/X11/xdm/Xreset : /etc/init.d/xdm restart Best regards, Lionel Magallon ---End Message--- ---BeginMessage--- Closing since the submitter's address is invalid. If anybody ever reproduces this problem, feel free to reopen. Brice ---End Message---
Bug#24706: marked as done (xdm: full-force SAINT attack crashes xdm)
Your message dated Thu, 01 Mar 2007 22:52:00 +0100 with message-id [EMAIL PROTECTED] and subject line submitter address invalid 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: xbase Version: 3.3-4 Kernel 2.0.30 Debian 1.3.1 (libc.so.5.4.33) using package default xdm-config When hit with a full-force SAINT (ver 1.2.3) attack, xdm crashes, although X stays running just fine. So upon logout I had to go back to console, kill X and restart xdm on the two machines I checked with SAINT. SAINT does not report any problems with xdm or X -- Eric Fain DSP/Communications Lab (303)492-2759 [EMAIL PROTECTED] University of Colorado, Boulder CO ---End Message--- ---BeginMessage--- Closing since the submitter's address is invalid. If anybody ever reproduces this problem, feel free to reopen. Brice ---End Message---
Bug#13884: xdm: localhost appears in chooser when route is -net 127.0.0.0
Hi, About 9 years ago, you reported a bug to the Debian BTS regarding localhost appearing in chooser when route is -net 127.0.0.0. You didn't reply to Branden's ping 7 years ago. But you change the submitter's address later. So, did you reproduce this problem recently? With Xorg/Etch? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#327903: xdm server is not shown in chooser
Hi, About 1 year ago, you reported a bug to the Debian BTS regarding xdm not being shown in chooser. Did you reproduce this problem recently? With Xorg/Etch? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#37174: xdm: Unknown session exit code 2816 from process 483
Hi, About 8 years ago, you reported a bug to the Debian BTS regarding xdm exiting an unknown session exit code. Did you reproduce this problem recently? With Xorg/Etch? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#70100: marked as done (xdm: package upgrade left files in authdir, preventing further logins)
Your message dated Thu, 01 Mar 2007 23:05:51 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#70100: xdm: package upgrade left files in authdir, preventing further logins 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: xdm Version: 3.3.6-10 Severity: normal During a dist-upgrade from 2.1, xdm left a file in /var/lib/xdm/authdir/authfiles; this prevented further local logins via xdm. The file was not removed, even during booting, and had to be deleted manually in order to allow logins via xdm. -- System Information Debian Release: 2.2 Architecture: i386 Kernel: Linux moebius 2.2.15 #1 SMP Tue Aug 22 20:27:41 CEST 2000 i686 Versions of packages xdm depends on: ii cpp 1:2.95.2-13 The GNU C preprocessor. ii libc62.1.3-10GNU C Library: Shared libraries an ii xbase-clients3.3.6-10miscellaneous X clients ii xlib6g 3.3.6-10shared libraries required by X cli -- Configuration Files: /etc/X11/xdm/Xsetup_0 [Errno 13] Permission denied: '/etc/X11/xdm/Xsetup_0' ---End Message--- ---BeginMessage--- Closing as planned last year. Brice ---End Message---
Bug#37682: xdm: X -indirect users get wtmp entries written as logged onto 'console'
Hi, About 8 years ago, you reported a bug to the Debian BTS regarding X -indirect writing wtmp entry as if users were logged onto console. Did you reproduce this problem recently? With Xorg/Etch? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#139853: xdm: daemon fails to start when using lpp
Hi, About 5 years ago, you reported a bug to the Debian BTS regarding xdm not starting when using lpp. Did you reproduce this problem recently? With Xorg/Etch? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413054: Software Fallback with ctx-Line.SmoothFlag
Package: xserver-xorg-video-ati Version: 1:6.6.3-2 Severity: normal Tags: upstream Hi, it seems that the driver is not supporting something that causes it to turn off hardware acceleration. I assume this is an upstream issue, but I’d like it to be tracked here, if you don’t mind. I’m observing it with google earth: $ googleearth libGL warning: 3D driver claims to not support visual 0x4b *WARN_ONCE* File r300_render.c function r300Fallback line 428 Software fallback:ctx-Line.SmoothFlag *** ... I think it used to work around August with the versions in unstable, IIRC. If this is not the ati driver, but the mesa package, then please excuse my mis-filing and re-assign the bug. Greetings and thanks, Joachim PS: My hardware is: 01:00.0 VGA compatible controller: ATI Technologies Inc M10 NT [FireGL Mobility T2] (rev 80) glxinfo says: OpenGL renderer string: Mesa DRI R300 20060815 AGP 4x TCL OpenGL version string: 1.3 Mesa 6.5.1 -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.otto Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages xserver-xorg-video-ati depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii xserver-xorg-core 2:1.1.1-18 X.Org X server -- core server xserver-xorg-video-ati recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#101906: xdm: xdm crashes the X server in indirect mode
Hi, About 6 years ago, you reported a bug to the Debian BTS regarding xdm crashing the X server in indirect mode. Did you reproduce this problem recently? With Xorg/Etch? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#141089: marked as done (xdm: greeter changed to upstream defaults and logins don't work)
Your message dated Thu, 01 Mar 2007 23:14:39 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#141089: xdm: greeter changed to upstream defaults and logins don't work 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: xdm Version: 4.1.0-14 Severity: normal Hi, I just started to upgrade from 2.2r5 to testing (by pointing apt to testing and installing new ghostscript). After installation of gs, the new X including xdm, new libc etc. I logged out. I got a simple xdm login screen (in a different layout from the classical xdm screen I had before, but without the debian logo). Neither my personal account nor root was permitted to log in. I logged in via console and did a reboot, this time I got a xdm login screen looking like the screen I got the first time, but with debian logo and login worked fine. I think login should be possible through xdm without reboot, or the reboot should be offered by the installation process (M$ Windows-style, shudder...) Thank you for your work! Ciao Michael Below -- System Information Debian Release: 2.2 Kernel Version: Linux antithese.de 2.2.19 #1 Sun Sep 9 16:27:42 MEST 2001 i586 unknown Versions of the packages xdm depends on: ii cpp2.95.4-9 The GNU C preprocessor. ii debconf1.0.31 Debian configuration management system ii libc6 2.2.5-3GNU C Library: Shared libraries and Timezone ii libpam0g 0.72-9 Pluggable Authentication Modules library ii libxaw74.1.0-14 X Athena widget set library ii xbase-clients 4.1.0-14 miscellaneous X clients ii xlibs 4.1.0-14 X Window System client libraries --- Begin /etc/X11/xdm/Xservers (modified conffile) # # # # :0 local /usr/bin/X11/X vt7 -dpi 96 -deferglyphs 16 --- End /etc/X11/xdm/Xservers ---End Message--- ---BeginMessage--- Closing since there are very few chances the bug is still present, and we don't care about upgrade to woody anymore. Brice ---End Message---
Bug#187148: marked as done (xdm: only answers one XDMCP request and then shuts down socket)
Your message dated Thu, 01 Mar 2007 23:16:05 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#187148: xdm: only answers one XDMCP request and then shuts down socket 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: xdm Version: 4.2.1-6 Hi, after doing the lastest sid upgrade, my xdm doesn't work properly anymore. I have an Xserver with option -indirect to the host itself, where xdm provides a chooser, presenting the host itself and all other machines willing to serve. That worked well for several years. Now, the chooser still appears, but the login service is unavailable. Debugging showed that the xdm is (in contrast to older versions) willing to answer only one xdmcp request and then shuts down the xdmcp socket (i.e. binds the socket to the Xserver, so it doesn't accept other packets anymore). Since this first available request is already taken by the chooser query, all subsequent queries are dropped. Even when starting a new xdm without the Xserver, it answers only exactly one xdmcp request from other hosts. regards Hadmut ---End Message--- ---BeginMessage--- Closing since the submitter never replied to the ping about testing a new release. Brice ---End Message---
Bug#195279: marked as done (xdm: removes symlink to home directory on logout if uid of user is zero)
Your message dated Thu, 01 Mar 2007 23:19:59 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#195279: xdm: removes symlink to home directory on logout if uid of user is zero 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: xdm Version: 4.2.1-6 Severity: normal Possibly this only happens for root; at least, I can't reproduce it from a non-root user. I have an alternate root user whose home directory is pointed at by a symlink. When the X session ends, xdm replaces this symlink with an empty file. As far as I can tell from strace, some .Xauthority code gets very confused, using filenames like homedir-n instead of homedir/.Xauthority-n. (This works right *starting* the session.) Stracing the same for a non-root user doesn't show this confusion. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux khms.westfalen.de 2.4.19+kai.58 #1 Sam Sep 7 14:16:44 CEST 2002 i686 Locale: LANG=de_DE, LC_CTYPE=de_DE Versions of packages xdm depends on: ii cpp 3:3.2.3-1 The GNU C preprocessor. ii debconf 1.2.35 Debian configuration management sy ii libc6 2.3.1-16 GNU C Library: Shared libraries an ii libpam0g 0.76-9 Pluggable Authentication Modules l ii libxaw7 4.2.1-6X Athena widget set library ii xbase-clients 4.2.1-6miscellaneous X clients ii xlibs 4.2.1-6X Window System client libraries -- debconf information: shared/default-x-display-manager: xdm xdm/stop_running_server_with_children: false xdm/daemon_name: /usr/bin/X11/xdm ---End Message--- ---BeginMessage--- Closing since the submitter never replied to the ping about trying to reproduce with a new release. Brice ---End Message---
Bug#252326: marked as done (xdm: user cannot log in)
Your message dated Thu, 01 Mar 2007 23:20:30 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#252326: xdm: user cannot log in 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: xdm Version: 4.3.0.dfsg.1-1 Hello, i am not able to login local using xdm. With kdm everything works fine. I think there ist some problem verifying the passwort, because my /var/log/auth.log says: Jun 2 19:19:03 hermes : (pam_unix) authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=satura I have also completely purged and reinstalled the xdm Package but this did'nt solve the problem. mfg Andreas Messer -- gnuPG keyid: 0xE94F63B7 fingerprint: D189 D5E3 FF4B 7E24 E49D 7638 07C5 924C E94F 63B7 ---End Message--- ---BeginMessage--- Closing as planned a while ago since no reply to the ping. Brice ---End Message---
Bug#113542: marked as done (xdm: Xservers file uses wrong path to X binary)
Your message dated Thu, 01 Mar 2007 23:24:43 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#113542: xdm: Xservers file uses wrong path to X binary 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: xbase-clients Version: 4.1.0-5 (This may be a bug on xdm, either/or) /etc//X11/xinit/xserverrc:exec /usr/bin/X11/X -dpi 100 -nolisten tcp /etc//X11/xdm/Xservers::0 local /usr/X11R6/bin/X vt7 -dpi 100 -nolisten tcp Note the different paths to the same binary. ---End Message--- ---BeginMessage--- Looks ok in Etch, closing. Brice ---End Message---
Bug#325232: marked as done (xdm stop leaves xconsole running)
Your message dated Thu, 01 Mar 2007 23:31:49 +0100 with message-id [EMAIL PROTECTED] and subject line bug#325232: xdm stop leaves xconsole running 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: xdm Version: 6.8.2.dfsg.1-4 Severity: minor On a fresh sid installation, boot single user # invoke-rc.d xdm start # invoke-rc.d xdm stop # pstree shows a now useless xconsole process still running. ---End Message--- ---BeginMessage--- Looks ok in Etch, closing. Brice ---End Message---
Bug#113271: xdm: strange text in chooser
Hi, About 5 years ago, you reported (or replied to) a bug in the Debian BTS regarding a strange text being displayed in chooser on a remote display. Did any of you guys reproduce this problem recently? With Xorg/Etch? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413054: Software Fallback with ctx-Line.SmoothFlag
reassign 413054 libgl1-mesa-dri thanks On Thu, Mar 1, 2007 at 23:12:38 +0100, Joachim Breitner wrote: it seems that the driver is not supporting something that causes it to turn off hardware acceleration. I assume this is an upstream issue, but I’d like it to be tracked here, if you don’t mind. I’m observing it with google earth: $ googleearth libGL warning: 3D driver claims to not support visual 0x4b *WARN_ONCE* File r300_render.c function r300Fallback line 428 Software fallback:ctx-Line.SmoothFlag *** ... I think it used to work around August with the versions in unstable, IIRC. If this is not the ati driver, but the mesa package, then please excuse my mis-filing and re-assign the bug. The warning comes from the r300 dri driver, so I'm reassigning the bug there. Could you try the version of mesa in experimental? If it's not fixed in 6.5.2, would you mind filing the bug upstream at bugs.freedesktop.org? Thanks, Julien
Bug#113270: xdm: xdm login fails when password soon expires and warning is issued
Hi, On Thu, Mar 01, 2007 at 10:54:15PM +0100, Brice Goglin wrote: logging failure when user passwd is expiring soon. Did you reproduce this problem recently? With Xorg/Etch? If not, I will close this bug in No, I don't use X now, so I cannot say anything about this bug in context of the new system (Xorg). Feel free to close it. Regards, Lipo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#37682: marked as done (xdm: X -indirect users get wtmp entries written as logged onto 'console')
Your message dated Thu, 01 Mar 2007 23:43:59 +0100 with message-id [EMAIL PROTECTED] and subject line Undelivered Mail Returned to Sender 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: xdm Version: 3.3.2.3a-11 We have 3 machine. 1 server and 2 X terminal client. Clients uses X -indirect. usera:0 console Fri May 14 18:05 still logged in userb:0 console Fri May 14 13:09 - 18:05 (04:55) userb use client1, usera use server. userb NOT logged out at 18:05!!! -- System Information Debian Release: 2.1 Kernel Version: Linux backup 2.2.1 #1 Mon Feb 8 14:11:08 MET 1999 i586 unknown Versions of the packages xdm depends on: ii libc6 2.0.7.19981211 GNU C Library: shared libraries ii xlib6g 3.3.2.3a-11shared libraries required by X clients --- Begin /etc/X11/xdm/Xresources (modified conffile) ! /etc/X11/xdm/Xresources ! ! X resources used by xdm sessions xlogin*login.translations: #override\ CtrlKeyD: delete-character()\n\ KeyReturn: set-session-argument() finish-field() xlogin*borderWidth: 3 xlogin*greeting: xlogin*namePrompt: login:\ xlogin*fail: Login incorrect xlogin*greetColor: CadetBlue xlogin*failColor: red xlogin*Foreground: #ff xlogin*Background: #22 xlogin*greetColor: #ff xlogin.Login.foreground: #00 xlogin*geometry:450x200+100+400 xlogin*Foreground: black xlogin*Background: white XConsole.text.geometry: 480x130 XConsole.verbose: true XConsole*iconic:true XConsole*font: fixed Chooser*geometry: 700x300+300+200 Chooser*allowShellResize: false Chooser*viewport.forceBars: true Chooser*label.font: *-new century schoolbook-bold-i-normal-*-240-* Chooser*label.label:XDMCP Host Menu from CLIENTHOST Chooser*list.font: -*-*-medium-r-normal-*-*-230-*-*-c-*-iso8859-1 Chooser*Command.font: *-new century schoolbook-bold-r-normal-*-180-* Chooser*Foreground: #ff Chooser*Background: #00 --- End /etc/X11/xdm/Xresources --- Begin /etc/X11/xdm/Xresources_0 (modified conffile) ! /etc/X11/xdm/Xresources ! ! X resources used by xdm sessions xlogin*login.translations: #override\ CtrlKeyD: delete-character()\n\ KeyReturn: set-session-argument() finish-field() xlogin*borderWidth: 3 xlogin*greeting: xlogin*namePrompt: login:\ xlogin*fail: Login incorrect xlogin*greetColor: CadetBlue xlogin*failColor: red xlogin*Foreground: #ff xlogin*Background: #22 xlogin*greetColor: #ff xlogin.Login.foreground: #00 xlogin*geometry:450x200+100+400 xlogin*Foreground: black xlogin*Background: white XConsole.text.geometry: 480x130 XConsole.verbose: true XConsole*iconic:true XConsole*font: fixed Chooser*geometry: 700x300+300+200 Chooser*allowShellResize: false Chooser*viewport.forceBars: true Chooser*label.font: *-new century schoolbook-bold-i-normal-*-240-* Chooser*label.label:XDMCP Host Menu from CLIENTHOST Chooser*list.font: -*-*-medium-r-normal-*-*-230-*-*-c-*-iso8859-1 Chooser*Command.font: *-new century schoolbook-bold-r-normal-*-180-* Chooser*Foreground: #ff Chooser*Background: #00 --- End /etc/X11/xdm/Xresources_0 --- Begin /etc/X11/xdm/Xservers (modified conffile) # # # :0 local /usr/X11R6/bin/X --- End /etc/X11/xdm/Xservers --- Begin /etc/X11/xdm/Xsetup (modified conffile) #!/bin/sh # # /usr/X11R6/bin/freetemp /usr/X11R6/bin/xbanner -file /etc/X11/XBanner.ad --- End /etc/X11/xdm/Xsetup --- Begin /etc/X11/xdm/Xsetup_0 (modified conffile) #!/bin/sh # # if grep -qs ^run-xconsole /etc/X11/xdm/xdm.options; then # kill any running xconsole pid=$(cat /var/run/xconsole_0.pid 2/dev/null) if [ $pid ]; then kill $pid 2 /dev/null fi rm -f /var/run/xconsole_0.pid # start fresh xconsole and store its PID xconsole -geometry 480x130-0-0 -notify -verbose -fn fixed \ -exitOnFail -file /dev/xconsole echo $! /var/run/xconsole_0.pid fi /usr/X11R6/bin/freetemp /usr/X11R6/bin/xbanner -file /etc/X11/XBanner.ad --- End /etc/X11/xdm/Xsetup_0 --- Begin /etc/X11/xdm/Xstartup_0 (modified conffile) #!/bin/sh /usr/X11R6/bin/freetemp # # set -e if [ -x /etc/X11/xdm/Xstartup ]; then /etc/X11/xdm/Xstartup || exit $? fi exit 0 --- End /etc/X11/xdm/Xstartup_0 --- Begin /etc/X11/xdm/xdm-config (modified conffile) ! /etc/X11/xdm/xdm-config ! ! resources specific to xdm itself
Processed: bug 413009 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=7770
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.27 forwarded 413009 https://bugs.freedesktop.org/show_bug.cgi?id=7770 Bug#413009: xorg-server: [ia64] PCI domain mismatch - DRI unusable Noted your statement that Bug has been forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=7770. 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]
Processed: bug 67086 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=10145
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.27 forwarded 67086 https://bugs.freedesktop.org/show_bug.cgi?id=10145 Bug#67086: xdm: passes socket file descriptors to children Noted your statement that Bug has been forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=10145. 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#402537: xdm exits immediately after been launched
Eric, What's the status of your xdm exiting right after starting? Do you still reproduce with latest Xorg/Etch? Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#413054: Software Fallback with ctx-Line.SmoothFlag
Processing commands for [EMAIL PROTECTED]: reassign 413054 libgl1-mesa-dri Bug#413054: Software Fallback with ctx-Line.SmoothFlag Bug reassigned from package `xserver-xorg-video-ati' 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#139853: marked as done (xdm: daemon fails to start when using lpp)
Your message dated Thu, 01 Mar 2007 23:43:59 +0100 with message-id [EMAIL PROTECTED] and subject line Undelivered Mail Returned to Sender 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: kernel-patch-lpp Version: 0.4.0-2 Severity: normal I compiled the kernel, using the kernel-source-2.4.18 package, with the kernel-patch-lpp patch applied. I also applied the kernel-patch-preempt-2.4 patch, as well as the crypto patch from kerneli.org. As described in the README.Debian, I copied the contributed rc and rcS shell scripts into /etc/init.d after making backups. I use xdm to manage X sessions. Prior to using the LPP, xdm would start automatically after bootup. Subsequently, xdm will not start if LPP is used. That is, if the `append=console=/dev/tty2 CONSOLE=/dev/tty2' and `vga=0x301' lines are omitted (commented out) in /etc/lilo.conf, thereby disabling the graphical boot screen, then xdm /will/ start, even though I am still using the contributed rc and rcS scripts. However, if the graphical boot screen is enabled, using the /same/ rc and rcS scripts, xdm will /not/ start. It will start manually, however; if I login as root and run `/etc/init.d/xdm start' then xdm will start normally. -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux cherokee 2.4.18-k7 #1 Mon Mar 25 10:15:53 EST 2002 i686 Locale: LANG=C, LC_CTYPE= Versions of packages kernel-patch-lpp depends on: ii patch 2.5.4-10 Apply a diff file to an original ---End Message--- ---BeginMessage--- Closing since the submitter's address is invalid. If anybody ever reproduces this problem, feel free to reopen. Brice ---End Message---
Bug#139854: marked as done (xdm: daemon fails to start when using lpp)
Your message dated Thu, 01 Mar 2007 23:43:59 +0100 with message-id [EMAIL PROTECTED] and subject line Undelivered Mail Returned to Sender 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: kernel-patch-lpp Version: 0.4.0-2 Severity: normal I compiled the kernel, using the kernel-source-2.4.18 package, with the kernel-patch-lpp patch applied. I also applied the kernel-patch-preempt-2.4 patch, as well as the crypto patch from kerneli.org. As described in the README.Debian, I copied the contributed rc and rcS shell scripts into /etc/init.d after making backups. I use xdm to manage X sessions. Prior to using the LPP, xdm would start automatically after bootup. Subsequently, xdm will not start if LPP is used. That is, if the `append=console=/dev/tty2 CONSOLE=/dev/tty2' and `vga=0x301' lines are omitted (commented out) in /etc/lilo.conf, thereby disabling the graphical boot screen, then xdm /will/ start, even though I am still using the contributed rc and rcS scripts. However, if the graphical boot screen is enabled, using the /same/ rc and rcS scripts, xdm will /not/ start. It will start manually, however; if I login as root and run `/etc/init.d/xdm start' then xdm will start normally. -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux cherokee 2.4.18-k7 #1 Mon Mar 25 10:15:53 EST 2002 i686 Locale: LANG=C, LC_CTYPE= Versions of packages kernel-patch-lpp depends on: ii patch 2.5.4-10 Apply a diff file to an original -- |_|_ | _ _ |_ PGP public key: http://www.wilykit.com/wilykit.key |_) . |_)|(_|(_ |\ Never rub another man's rhubarb. -- Joker ---End Message--- ---BeginMessage--- Closing since the submitter's address is invalid. If anybody ever reproduces this problem, feel free to reopen. Brice ---End Message---
Bug#1985: xdm: forwards indirect requests from localhost with client IP of 127.0.0.1, which obviously won't come back
Hi, A very long time ago, you reported a bug to the Debian BTS regarding xdm not correctly forwarding indirect requests from localhost (using sender IP 127.0.0.1 instead of the actual one). Did you reproduce this problem recently? With Xorg/Etch? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#113271: xdm: strange text in chooser
Hi again, On Thu, Mar 01, 2007 at 11:38:39PM +0100, Brice Goglin wrote: regarding a strange text being displayed in chooser on a remote display. Did any of you guys reproduce this problem recently? With Xorg/Etch? If not, I will close this bug in the next weeks. Same answer as for Bug#113270: | No, I don't use X now, so I cannot say anything about this bug in | context of the new system (Xorg). Feel free to close it. Regards, Lipo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#13884: xdm: localhost appears in chooser when route is -net 127.0.0.0
Brice Goglin wrote: About 9 years ago, you reported a bug to the Debian BTS regarding localhost appearing in chooser when route is -net 127.0.0.0. You didn't reply to Branden's ping 7 years ago. But you change the submitter's address later. So, did you reproduce this problem recently? With Xorg/Etch? If not, I will close this bug in the next weeks. It's hard to say if this still happens, since current versions of the linux kernel do not allow creating such a routing table. -- see shy jo signature.asc Description: Digital signature
Bug#76337: xdm: can leave behind garbage files in current directory if interrupted while generating auth token
Hi, About 6 years ago, you reported a bug to the Debian BTS regarding xdm generating garbage files if interrupted while generating auth token. Did you reproduce this problem recently? With Xorg/Etch? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#76929: xdm: remote logins broken, corrupted XDMCP packets?
Hi, About 6 years ago, you reported a bug to the Debian BTS regarding corrupted XDMCP packets breaking remote login in xdm with a non-standard config. Did you reproduce this problem recently? With Xorg/Etch? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#382036: xdm restart with active pam_tally
Hi, Can you try to reproduce this bug with xdm 1:1.1.4-1 currently in experimental? If so, could you try to capture a backtrace of the crash with gdb? or at least get some info with strace? Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392832: XKB keymap fails to load when X started by xdm
Hi, Could you try to reproduce with xdm 1:1.1.4-1 currently in experimental? thanks. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#398289: marked as done (Copying address into in6_addr instead of in6_addr.sin6_addr in forward_respond().)
Your message dated Fri, 02 Mar 2007 00:12:57 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#398289: Copying address into in6_addr instead of in6_addr.sin6_addr in forward_respond(). 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: xdm Version: 1.0.5-1 Tags: upstream ipv6 In forward_respond(), when filling in6_addr structure, clientAddress.data is copied into sockaddr_in6 structure instead of its sin6_addr member. As a result, xdm fails to respond to ForwardQuery received over IPv6 connection. I submitted it to the X.Org's Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=8995. --- xdm-1.0.5.orig/xdmcp.c 2006-11-12 22:09:00.956646548 +0300 +++ xdm-1.0.5/xdmcp.c 2006-11-12 22:10:39.258790052 +0300 @@ -801,7 +801,7 @@ in6_addr.sin6_len = sizeof(in6_addr); #endif in6_addr.sin6_family = AF_INET6; - memmove(in6_addr,clientAddress.data,clientAddress.length); + memmove(in6_addr.sin6_addr,clientAddress.data,clientAddress.length); memmove((char *) in6_addr.sin6_port, clientPort.data, 2); client = (struct sockaddr *) in6_addr; clientlen = sizeof (in6_addr); -- Best regards, [EMAIL PROTECTED] My GPG key is Vickenty Fesunovhttp://kent.comintern.ru 0x546defd6 at pgp.mit.edu ---End Message--- ---BeginMessage--- Version: 1:1.1.4-1 The fix got applied upstream in 1.1.1. Closing with the experimental version. Brice ---End Message---
Bug#76337: xdm: can leave behind garbage files in current directory if interrupted while generating auth token
Brice Goglin wrote: About 6 years ago, you reported a bug to the Debian BTS regarding xdm generating garbage files if interrupted while generating auth token. Did you reproduce this problem recently? With Xorg/Etch? If not, I will close this bug in the next weeks. This would be difficult to reproduce as the bug that causes xdm to read too much from /dev/urandom has been fixed, so the window to reproduce it would be small. -- see shy jo signature.asc Description: Digital signature
Processed (with 1 errors): updating xdm bugs
Processing commands for [EMAIL PROTECTED]: severity 387205 wishlist Bug#387205: xdm password length limit Severity set to `wishlist' from `important' found 382037 1:1.1.4-1 Bug#382037: Missing programname and PID in syslog-log by PAM Bug marked as found in version 1:1.1.4-1. found 336220 1:1.1.4-1 Bug#336220: xdm: bogus /dev/mem access lead to trouble on arm platforms Bug marked as found in version 1:1.1.4-1. pending 384686 Unknown command or malformed arguments to command. forcemerge 256299 273771 Bug#256299: xdm: race condition in policy.c:Willing() Bug#273771: xdm: daemon can hang due to race condition in policy.c:Willing() when trying to run Xwilling sript Forcibly Merged 256299 273771. found 334461 1:1.1.4-1 Bug#334461: xdm: fails to stop on purge Bug marked as found in version 1:1.1.4-1. found 130706 1:1.1.4-1 Bug#130706: xdm: incorrect usage of PAM_RHOST Bug marked as found in version 1:1.1.4-1. severity 135692 wishlist Bug#135692: xdm: manpage should reference xdm.options manpage in SEE ALSO section Severity set to `wishlist' from `minor' forcemerge 135692 201858 Bug#135692: xdm: manpage should reference xdm.options manpage in SEE ALSO section Bug#201858: xdm: program manpage should mention config file manpages and vice-versa Forcibly Merged 135692 201858. severity 136988 wishlist Bug#136988: xdm: Undocumented resources *logoFileName, *logoPadding Severity set to `wishlist' from `minor' tags 140229 wontfix Bug#140229: xdm: /etc/init.d/xdm calls itself There were no tags set. Tags added: wontfix severity 376391 wishlist Bug#376391: xdm: xdm manpage refers to non-existent section 'Typical Usage' Severity set to `wishlist' from `minor' found 372114 1:1.1.4-1 Bug#372114: Pressing CTRL+ALT+Backspace causes xdm to delete pidfile Bug marked as found in version 1:1.1.4-1. found 95214 1:1.1.4-1 Bug#95214: xdm: uses XAUTHORITY variable for purposes other than those documented Bug marked as found in version 1:1.1.4-1. 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#402087: xdm: no home directory test for Xstartup
Hi Phil, It might be too late for my eyes to work fine, but I can't find the lines your talking about in /etc/X11/xdm/Xstartup (in 1:1.0.5-2). Does your proposal still apply with this version of xdm? Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#76929: marked as done (xdm: remote logins broken, corrupted XDMCP packets?)
Your message dated Fri, 02 Mar 2007 00:26:31 +0100
with message-id [EMAIL PROTECTED]
and subject line Undelivered Mail Returned to Sender
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: xdm
Version: 4.0.1-3
Severity: normal
I can't figure out what's going on here. Users use a Windows X Server
(Reflection) and login with xdm. Today, after seeing the login screen, the X
session ends, and here is the content of .xsession-errors:
(It has control chars, I don't know how will they reach there =) )
_X11TransSocketINETConnect: Can't get address for lÊÿ¿{ocalho,Êÿ¿¬
@tÊÿ¿ st
xrdb: Invalid argument
xrdb: Can't open display 'lÊÿ¿{ocalho,Êÿ¿¬
@tÊÿ¿ st:0.0'
_X11TransSocketINETConnect: Can't get address for lÊÿ¿{ocalho,Êÿ¿¬
@tÊÿ¿ st
xrdb: Invalid argument
xrdb: Can't open display 'lÊÿ¿{ocalho,Êÿ¿¬
@tÊÿ¿ st:0.0'
_X11TransSocketINETConnect: Can't get address for lÊÿ¿{ocalho,Êÿ¿¬
@tÊÿ¿ st
xrdb: Invalid argument
xrdb: Can't open display 'lÊÿ¿{ocalho,Êÿ¿¬
@tÊÿ¿ st:0.0'
_X11TransSocketINETConnect: Can't get address for lÊÿ¿{ocalho,Êÿ¿¬
@tÊÿ¿ st
xrdb: Invalid argument
xrdb: Can't open display 'lÊÿ¿{ocalho,Êÿ¿¬
@tÊÿ¿ st:0.0'
_X11TransSocketINETConnect: Can't get address for lÊÿ¿{ocalho,Êÿ¿¬
@tÊÿ¿ st
xrdb: Invalid argument
xrdb: Can't open display 'lÊÿ¿{ocalho,Êÿ¿¬
@tÊÿ¿ st:0.0'
_X11TransSocketINETConnect: Can't get address for lÊÿ¿{ocalho,Êÿ¿¬
@tÊÿ¿ st
xrdb: Invalid argument
xrdb: Can't open display 'lÊÿ¿{ocalho,Êÿ¿¬
@tÊÿ¿ st:0.0'
_X11TransSocketINETConnect: Can't get address for lÊÿ¿{ocalho,Êÿ¿¬
@tÊÿ¿ st
xrdb: Invalid argument
xrdb: Can't open display 'lÊÿ¿{ocalho,Êÿ¿¬
@tÊÿ¿ st:0.0'
_X11TransSocketINETConnect: Can't get address for lÊÿ¿{ocalho,Êÿ¿¬
@tÊÿ¿ st
xrdb: Invalid argument
xrdb: Can't open display 'lÊÿ¿{ocalho,Êÿ¿¬
@tÊÿ¿ st:0.0'
_X11TransSocketINETConnect: Can't get address for lÊÿ¿{ocalho,Êÿ¿¬
@tÊÿ¿ st
xmodmap: unable to open display 'lÊÿ¿{ocalho,Êÿ¿¬
@tÊÿ¿ st:0.0'
Bad option: MultiByte
_X11TransSocketINETConnect: Can't get address for lÊÿ¿{ocalho,Êÿ¿¬
@tÊÿ¿ st
icewm: Can't open display: lÊÿ¿{ocalho,Êÿ¿¬
@tÊÿ¿ st:0.0. X must be running and $DISPLAY set.
-- System Information
Debian Release: woody
Kernel Version: Linux mazinger 2.2.17 #1 Tue Oct 24 14:29:11 ART 2000 i686
unknown
Versions of the packages xdm depends on:
ii cpp2.95.2-17 The GNU C preprocessor.
ii libc6 2.1.97-1 GNU C Library: Shared libraries and Timezone
ii libpam0g 0.72-12Pluggable Authentication Modules library
ii libxaw74.0.1-1X Athena widget set library
ii xbase-clients 4.0.1-3miscellaneous X clients
ii xlibs 4.0.1-3X Window System client libraries
--- Begin /etc/X11/xdm/Xaccess (modified conffile)
* #any host can get a login window
* CHOOSER BROADCAST #any indirect host can get a chooser
--- End /etc/X11/xdm/Xaccess
--- Begin /etc/X11/xdm/Xservers (modified conffile)
--- End /etc/X11/xdm/Xservers
--- Begin /etc/X11/xdm/xdm-config (modified conffile)
! $XConsortium: xdm-conf.cpp /main/3 1996/01/15 15:17:26 gildea $
! $XFree86: xc/programs/xdm/config/xdm-conf.cpp,v 1.6 2000/01/31 19:33:43 dawes
Exp $
DisplayManager.errorLogFile:/var/log/xdm.log
DisplayManager.pidFile: /var/run/xdm.pid
DisplayManager.keyFile: /usr/X11R6/lib/X11/xdm/xdm-keys
DisplayManager.servers: /usr/X11R6/lib/X11/xdm/Xservers
DisplayManager.accessFile: /usr/X11R6/lib/X11/xdm/Xaccess
DisplayManager.authDir: /var/lib/xdm
DisplayManager.willing: su nobody -c /usr/X11R6/lib/X11/xdm/Xwilling
DisplayManager.randomFile: /dev/urandom
! All displays should use authorization.
! X terminals may not be configured that way, so they will require
! individualized resource settings.
DisplayManager*authorize: true
! Scripts to start the server, start the user session, and reset the server
DisplayManager*setup: /usr/X11R6/lib/X11/xdm/Xsetup
DisplayManager*startup: /usr/X11R6/lib/X11/xdm/Xstartup
DisplayManager*reset: /usr/X11R6/lib/X11/xdm/Xreset
!
DisplayManager*resources: /usr/X11R6/lib/X11/xdm/Xresources
DisplayManager*session: /usr/X11R6/lib/X11/xdm/Xsession
!
DisplayManager*userPath:
/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
DisplayManager*systemPath:
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11
Bug#405823: Still see the bug in xorg 1.2.0
Hello, Ariel wrote: I have a very strong suspicion that bugs #407036, #410768, #405823, and #402563 might all be the same bug as #406044 Bug reporters: Please try this patch: http://bugs.debian.org/cgi-bin/bugreport.cgi/xorg-server.nocrash.patch?bug=406044;msg=45;att=1 And report if it fixes the problem. (It fixed it for me, but I'm not the original reporter of 406044 so the two other reporters in 406044 please also try the patch.) Since some people might not know how to rebuild the X server with a patch, they could start by testing the xserver-xorg-core package from experimental (1.2.0-4 currently), which seems to contain the patch too. If their problem disappears, Ariel or somebody else will help them getting a patched 1.1.1 X server. I didn't try the patch, but I see bug #405823 even with 1.2.0-2 Regards Jiri Palecek
Processed: tagging 384686
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.27 tags 384686 + pending Bug#384686: xdm no longer provides x-display-manager? There were no tags set. Tags added: pending 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]
BTS cleaning status
Hi, After the recent discussion on debian-devel about BTS cleaning and so, I thought it might be a good time to report the status of my XSF BTS cleaning (maybe somebody wants to jump in and synchronize with me...). 1) old packages The original plan was to look at very old bugs. So I started with xserver-xfree86. I don't have exact numbers, but about 320 bugs got closed. I would say 60% because of ping timeout (about 4 weeks) or invalid address, 15% because the submitter didn't have the hardware anymore, and 25% because the problem was actually gone. While waiting for the submitters to reply to my pings, I started pinging other packages, from the old ones to the newers. Apart from a couple pings that are still pending, the following old xfree86 related packages are now bug-free: xfree86, xfree86-common, xserver-common, xlibmesa-dri, xlibmesa-gl, xlibmesa-glu, x-window-system, x-window-system-core. Once I will have reassigned most of the remaining xserver-xfree86 bugs (about 30) to xorg packages, we should be pretty close to have nothing =sarge-specific anymore. 2) wishlists There are still a lot of wishlists, especially against xserver-xfree86. Several are related to debconf, which is supposed to go away after Etch. I would be great if people with more knowledge than me could give a quick look at the others and tag some as wontfix. For most of these old wishlists, I miss some background to decide between wontfix or reassign to xorg :( 3) packages' status The following packages have been pingued and are waiting for the timeout to arrive: xserver-xfree86 xlibmesa-gl-dev xlibs xutils mesa-utils mesa libgl1-mesa-dev libgl1-mesa-dri libgl1-mesa-glx libglu1-mesa libosmesa4 libx11 libx11-6 libx11-data libx11-dev libxaw7 libxft2 xfonts-75dpi xfonts-base xfonts-cyrillic xfonts-encodings xfonts-scalable xfs xnest xutils-dev xvfb xdm The following (non-exhaustive list) packages are clean (I mean, no more obsolete or irrelevant bug, but possibly still some valid bugs): Most libs The mesa packages that are not listed above The following ones are almost clean, except some very simple bugs that are easy to fix (see below): twm libxft-dev xresprobe xcursor-themes xfonts-100dpi The following packages are still to do, I will start pinging them next week, doing the non-Xorg-related packages first: xkb-data xfonts-utils xbase-clients x11-common libdrm* libxvmc* xkeyboard-config xorg xserver-xorg xserver-xorg-core xserver-xorg-input-* xserver-xorg-video-* x11-proto* xorg-docs compiz* (I hope I didn't miss anything) Looking at the BTS of a package and searching for Done: Brice Goglin is usually a good way to know whether I worked on a package or not... 4) summary To summarize, within the last 2 months, I think about 500 bugs got closed. I expect to close more than 100 with the current pending pings. And hopefully 300 more with the packages that are still to-do. So we should be able to go under 1000 outstanding bugs then... About 20 bugs have been forwarded upstream. I could probably forward much more bugs, but I don't want upstream to hate me :) About 20 bugs are in my bookmarks, marked as trivial stuff to commit in git. I know how to commit simple stuff in git. But, I am still pretty afraid of creating an experimental branch or updating it with a new upstream release. So basically, I am waiting a little bit in case somebody does the branch update for me :) If there's something I should change in the way I am doing all this, please let me know. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413009: Comments
Not quite sure I understand the point of forwarding back to the 'source'... Which seems pretty stale at this point. I think it'd be nice to have this fixed for etch, especially given the triviality of the fix (which could even be #ifdef'd __ia64__ for non-contagiousness sake...) HTH T-Bone -- Thibaut VARENE http://www.parisc-linux.org/~varenet/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413009: Comments
On Fri, Mar 2, 2007 at 01:58:49 +0100, Thibaut VARENE wrote: Not quite sure I understand the point of forwarding back to the 'source'... Which seems pretty stale at this point. I think it'd be nice to have this fixed for etch, especially given the triviality of the fix (which could even be #ifdef'd __ia64__ for non-contagiousness sake...) The fix is referred to as a workaround, so I'd like to have Michel's opinion first on whether we should apply it for etch. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390913: SAVE_VBE_STATE and POST_VIDEO in /etc/default/acpi-support
Try turning SAVE_VBE_STATE and POST_VIDEO in /etc/default/acpi-support to false. This fixes the issue for me. See: http://thinkwiki.org/wiki/Problem_with_display_remaining_black_after_resume#Affected_Models Cheers, Brandon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#412599: xterm: boldMode does not work as described
On Tue, Feb 27, 2007 at 12:50:11AM +0100, Jörg Sommer wrote: Package: xterm Version: 224-1 Severity: normal Hi, the manual page of xterm says: Note that xterm has one bold font which you may set explicitly. It attempts to match a bold font for the other font selections (font1 through font6). If the normal and bold fonts are distinct, this resource [boldMode] has no effect. So I set boldFont and boldMode: % xrdb -query|grep -E '(XTerm.*ont|bold)' XTerm.*.boldFont: -misc-fixed-bold-*-*-*-18-*-*-*-*-*-iso10646-1 XTerm.*.font: -misc-fixed-medium-*-*-*-18-*-*-*-*-*-iso10646-1 XTerm.*.boldMode: false I need a little more information to see if I'm reconstructing this properly. Your locale appears to be de_DE.UTF-8, but the given resources are for XTerm rather than UXTerm. Are you starting xterm using the -u8 option, or using the utf8 or wideChars resource, then? btw - the .*. is really the same as * As you can see the font and boldFont entities are distinct, ergo the boldMode resource should get ignored. But it isn't so. I don't get bold characters. If I set the boldMode to true, I get ugly characters for font1 through font6. Well it could be distinct (even as specified) for a couple of different reasons, e.g., a) the pattern might not match a real font b) another resource could override one of the given patterns. For instance, I started with *font, but that was overridden by *VT100.font. But UXTerm*font worked. That was in my local app-defaults file (running with fvwm - none of that xrdb stuff to confuse). I see that by compiling xterm with tracing enabled (though it seems I should supply a shell script to do the queries, since this topic comes up regularly ;-) Bye, Jörg. -- System Information: Debian Release: unstable/experimental APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.20 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgp9EDvNmjf2p.pgp Description: PGP signature
Re: xorg-server: Changes to 'debian-experimental'
On Thu, Mar 01, 2007 at 08:09:54AM +0100, Michel Dänzer wrote: On Thu, 2007-03-01 at 05:10 +0100, David Nusinow wrote: commit 67f74f222d950e2e0739d0ba0363dab26e9b1229 Author: David Nusinow [EMAIL PROTECTED] Date: Wed Feb 28 23:07:07 2007 -0500 Set input and video abi versions to just 1 The major version number is all we really care about. The important information denoted by the minor version will be denoted with serverminver. diff --git a/debian/inputabiver b/debian/inputabiver index d3827e7..d00491f 100644 --- a/debian/inputabiver +++ b/debian/inputabiver @@ -1 +1 @@ -1.0 +1 The input major is still at 0 though, isn't it? grep 'XInput driver' /var/log/Xorg.0.log Yeah, thanks. I misread the source file a while back. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#303689: marked as done (xdm: sets up signal handlers that call unsafe functions)
package xdm reopen 303689 thanks DBTS The logrotate script has been fixed a while ago, closing. How about looking at the bug subject and the mail message, requesting cloning? This is not about logrotate at all... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
xorg-server: Changes to 'debian-experimental'
debian/inputabiver |2 +- 1 files changed, 1 insertion(+), 1 deletion(-) New commits: commit 8e3fca757d331c6abb259563e1d8e7210eaad274 Author: David Nusinow [EMAIL PROTECTED] Date: Thu Mar 1 21:02:12 2007 -0500 Input ABI version is currently 0.7, so set the package inputabiver to 0 Good catch from Michel Dänzer diff --git a/debian/inputabiver b/debian/inputabiver index d00491f..573541a 100644 --- a/debian/inputabiver +++ b/debian/inputabiver @@ -1 +1 @@ -1 +0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#303689: marked as done (xdm: sets up signal handlers that call unsafe functions)
Processing commands for [EMAIL PROTECTED]: package xdm Ignoring bugs not assigned to: xdm reopen 303689 Bug#303689: xdm: sets up signal handlers that call unsafe functions Bug reopened, originator not changed. 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]
Tum TV kanallari tek bir adreste! Ucretsiz! www.sihirli.tv
Processed: unmark wontfix to get patch review
Processing commands for [EMAIL PROTECTED]: tags 237877 - wontfix Bug#237877: xdm: please stop passing '-dpi 100' option to X server by default (also see #257266) Tags were: wontfix patch Tags removed: wontfix 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#237877: unmark wontfix to get patch review
tags 237877 - wontfix thanks As far as I can tell, bug 237877 got marked wontfix back before it had a patch available to change the dpi default to 100 and stop hardcoding it. It doesn't look like anyone reviewed the patch and either included it or stated why it doesn't work. I suspect the wontfix tag has perhaps helped it remain unnoticed. Thus, I've removed the wontfix tag to try to get patch review. Feel free to re-tag this wontfix, and remove the patch tag, if the most recent patch in this bug does not solve the problem. - Josh Triplett signature.asc Description: OpenPGP digital signature
Processing of xorg-server_1.2.0-5_i386.changes
xorg-server_1.2.0-5_i386.changes uploaded successfully to localhost along with the files: xorg-server_1.2.0-5.dsc xorg-server_1.2.0-5.diff.gz xserver-xorg-core_1.2.0-5_i386.deb xserver-xorg-dev_1.2.0-5_i386.deb xdmx_1.2.0-5_i386.deb xdmx-tools_1.2.0-5_i386.deb xnest_1.2.0-5_i386.deb xvfb_1.2.0-5_i386.deb xserver-xephyr_1.2.0-5_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of xserver-xorg-video-apm_1.1.1-5_i386.changes
xserver-xorg-video-apm_1.1.1-5_i386.changes uploaded successfully to localhost along with the files: xserver-xorg-video-apm_1.1.1-5.dsc xserver-xorg-video-apm_1.1.1-5.diff.gz xserver-xorg-video-apm_1.1.1-5_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of xserver-xorg-video-ark_0.6.0-5_i386.changes
xserver-xorg-video-ark_0.6.0-5_i386.changes uploaded successfully to localhost along with the files: xserver-xorg-video-ark_0.6.0-5.dsc xserver-xorg-video-ark_0.6.0-5.diff.gz xserver-xorg-video-ark_0.6.0-5_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of xserver-xorg-video-ati_6.6.3-4_i386.changes
xserver-xorg-video-ati_6.6.3-4_i386.changes uploaded successfully to localhost along with the files: xserver-xorg-video-ati_6.6.3-4.dsc xserver-xorg-video-ati_6.6.3-4.diff.gz xserver-xorg-video-ati_6.6.3-4_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of xserver-xorg-video-chips_1.1.1-6_i386.changes
xserver-xorg-video-chips_1.1.1-6_i386.changes uploaded successfully to localhost along with the files: xserver-xorg-video-chips_1.1.1-6.dsc xserver-xorg-video-chips_1.1.1-6.diff.gz xserver-xorg-video-chips_1.1.1-6_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of xserver-xorg-video-cirrus_1.1.0-5_i386.changes
xserver-xorg-video-cirrus_1.1.0-5_i386.changes uploaded successfully to localhost along with the files: xserver-xorg-video-cirrus_1.1.0-5.dsc xserver-xorg-video-cirrus_1.1.0-5.diff.gz xserver-xorg-video-cirrus_1.1.0-5_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of xserver-xorg-video-cyrix_1.1.0-6_i386.changes
xserver-xorg-video-cyrix_1.1.0-6_i386.changes uploaded successfully to localhost along with the files: xserver-xorg-video-cyrix_1.1.0-6.dsc xserver-xorg-video-cyrix_1.1.0-6.diff.gz xserver-xorg-video-cyrix_1.1.0-6_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
