Bug#283764: X clients will not start. Fix found.
On Sat, Dec 18, 2004 at 08:37:34PM -0500, Branden Robinson wrote:
retitle 283764 xfree86-common: Xsession can barf if user has aliased ls to
force colors on
thanks
On Tue, Nov 30, 2004 at 11:14:40PM -0800, David Lawyer wrote:
Package: xfree86-common
Version: 4.3.0.dfsg.1.-1
Version *what*?
dpkg --status shows: Version: 4.3.0.dfsg.1-1
When I type startx at the console, x starts and quits. But if I type
startx at a dumb terminal on a serial port, x starts OK and goes to
the icewm (ice window manager which I have installed). So why can I
start X from a dumb terminal but not from the console?
It took me some time to determine why. The error is in the file
/etc/X11/Xsession. The run_parts() function has
for F in $(ls $1); do
it should be:
for F in $(command ls $1); do
This is because I have in my /etc/profile:
if [ $TERM = linux -o $TERM = xterm ]; then
if [ $TERM = linux ]; then
eval `dircolors`;
ls () { command ls --color $* ; }
fi
else
ls () { command ls -F $* ; }
.
So when I use a dumb terminal and $TERM = my-dumb-terminal (or whatever)
then ls() is defined differently. But at the console, ls() is made
to support colors and the run_parts() can't seem to cope with the
control codes which are embedded in the file names to create colors.
One word command fixes it.
What was frustrating was that there were no error messages.
Ah. Thanks for the analysis. This report brings to mind two rules, one of
which you should probably learn, and the other of which I should have
remembered:
1) Don't override the names of Unix commands, even in your interactive
shell environment. It promotes bad habits.
2) Never use ls when echo will suffice.
Thanks again.
--
G. Branden Robinson| I came, I saw, she conquered.
Debian GNU/Linux | The original Latin seems to have
[EMAIL PROTECTED] | been garbled.
http://people.debian.org/~branden/ | -- Robert Heinlein
David Lawyer
Re: ATI Radeon 9200 256MB PCI xfree86-4.3.0.1 - hang
Mr. Kolpackov, If you're still experiencing this problem, could you please file a bug against the xserver-xfree86 package using the reportbug command from the package of the same name? If you could include this message (with your quoted material below) as well as the /var/log/XFree86.0.log that you get when using the fglrx driver, that would be much appreciated. It sounds like the ati/radeon driver in XFree86 is simply misdetecting the amount of RAM on the display adapter. On Thu, Dec 02, 2004 at 04:36:01PM -0600, Boris Kolpackov wrote: Boris Kolpackov [EMAIL PROTECTED] writes: I am having problems with above-mentioned card. After startx the box just hangs (black screen) with the only way out is through power-down (C-A-Backspace doesn't work). There is no log in /var/log/XFree86.0.log. Here is some info: * Card is VisionTek eXtasy Radeon 9200 256MB PCI DVI/VGA/SV DeviceID is 5961 * XFree86-4.3.0.1 is from Debian unstable. I have disabled DRI (see config below). * I am running linux kernel 2.6.4. I have disabled AGP/Framebuffer. * Driver from ATI v3.14.6 (for 4.3.0) seem to work ok. * I tried various options for radeon driver (you can see them in config file below) without any difference. Meantime I continued poking the radeon driver. Since after the startx the box is totally wasted I decide to ssh from a remote box and run XFree86 -verbose. This way I at least could capture some output. The whole thing appeared to hang right after (--) Depth 24 pixmap format 32 bpp and just before (II) do I need RAC? No, I don't. So I started comparing output from ATI driver to the one from XFree's radeon. All important things seemed identical (like addresses of MMIO regs, V_BIOS segment, BIOS, Linear Framebuffer, etc) except the amount of memory the driver detected. ATI's driver reported 128MB (64bit DDR SDRAM) while radeon reported 256 (128bit DDR SDRAM). So I added VideoRam 131072 to the video card section of XF86Config-4. And everything just worked. Has anybody else experienced anything like this? hth, -boris Section Files FontPathunix/:7110# local font server # if the local font server has problems, we can fall back on these # FontPath /usr/lib/X11/fonts/Type1 # FontPath /usr/lib/X11/fonts/CID # FontPath /usr/lib/X11/fonts/Speedo # FontPath /usr/lib/X11/fonts/misc # FontPath /usr/lib/X11/fonts/cyrillic # FontPath /usr/lib/X11/fonts/100dpi # FontPath /usr/lib/X11/fonts/75dpi EndSection Section Module # LoadGLcore Loadbitmap Loaddbe Loadddc # Loaddri Loadextmod Loadfreetype # Loadglx Loadint10 Loadrecord Loadspeedo Loadtype1 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc104 Option XkbLayout ru Option XkbVariantphonetic Option XkbOptionsgrp:toggle EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/psaux #Option Device/dev/input/mice Option Protocol MouseManPlusPS/2 Option Emulate3Buttons false Option ZAxisMapping 4 5 EndSection Section Device Identifier Generic Video Card #Driver fglrx Driver radeon #ChipID 0x514D #ChipID 0x4966 #BusID PCI:5:14:0 #Option NoAccel true #Option ForcePCIMode true #Option BusType PCI EndSection Section Monitor Identifier Generic Monitor HorizSync 30-75 VertRefresh 50-85 Option DPMS EndSection Section Screen Identifier Default Screen Device Generic Video Card Monitor Generic Monitor DefaultDepth24 SubSection Display Depth 24 Modes 1600x1200 800x600 640x480 EndSubSection EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard InputDevice Configured Mouse EndSection Section DRI Mode0666 EndSection -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- G. Branden Robinson|Nixon was so crooked that he needed Debian GNU/Linux |servants to help
Processed: Re: Bug#284025: xserver-xfree86: SEGV in RADEONQueryConnectedDisplays
Processing commands for [EMAIL PROTECTED]: retitle 284025 xserver-xfree86: [ati/radeon] SEGV in RADEONQueryConnectedDisplays() Bug#284025: xserver-xfree86: SEGV in RADEONQueryConnectedDisplays Changed Bug title. # SEGVs are important. severity 284025 important Bug#284025: xserver-xfree86: [ati/radeon] SEGV in RADEONQueryConnectedDisplays() Severity set to `important'. tag 284025 + upstream patch Bug#284025: xserver-xfree86: [ati/radeon] SEGV in RADEONQueryConnectedDisplays() There were no tags set. Tags added: upstream, patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#284025: xserver-xfree86: SEGV in RADEONQueryConnectedDisplays
retitle 284025 xserver-xfree86: [ati/radeon] SEGV in
RADEONQueryConnectedDisplays()
# SEGVs are important.
severity 284025 important
tag 284025 + upstream patch
thanks
On Thu, Dec 02, 2004 at 05:04:18PM -0700, Bjorn Helgaas wrote:
[...]
The problem is pretty clear from the source. We call vbeDoEDID(),
which usually returns a pointer, but can return NULL for failure.
Then we dereference it without bothering to check for NULL:
[...]
Here's a patch:
--- xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c.orig
2004-11-30 13:59:17.314008332 -0700
+++ xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c
2004-11-30 14:00:14.328656071 -0700
@@ -1272,7 +1272,7 @@
for (i = 0; i 5; i++) {
pRADEONEnt-MonInfo1 = vbeDoEDID(pVbe, NULL);
}
- if (pRADEONEnt-MonInfo1-rawData[0x14] 0x80)
+ if (pRADEONEnt-MonInfo1
pRADEONEnt-MonInfo1-rawData[0x14] 0x80)
pRADEONEnt-MonType1 = MT_DFP;
else pRADEONEnt-MonType1 = MT_CRT;
}
Mr. Helgaas,
Thanks for this outstanding report. I wish all reports against
xserver-xfree86 came with a GDB session transcript and a patch. :)
I'll try to get this fix into the next release.
--
G. Branden Robinson| Mob rule isn't any prettier just
Debian GNU/Linux | because you call your mob a
[EMAIL PROTECTED] | government.
http://people.debian.org/~branden/ |
signature.asc
Description: Digital signature
Re: XKB on xserver
[Mr. van Grootheest, are you subscribed to debian-x? If so, I apologize for the private copy of this mail.] On Fri, Dec 03, 2004 at 09:11:55PM +0100, Jan Evert van Grootheest wrote: I've got a question that I hope someone here can answer. I have this machine 'joe' that is really only used as an x-terminal. So it's got almost no packages installed. The only X packages I installed are the xserver-xfree86 and its dependecies (xserver-common and xfree86-common). Since my wife is russian and I'm dutch, I really would like XKB support. But it appears that one really needs to install xbase-clients to get that. Some more about the setup... quark is the application server and runs gdm. It also supplies everything else. It is the main machine in the house. Its XKB support works just fine. Joe starts X from inittab using '-query quark'. And unless quark is used for W2k for kids games, it works just great! What I would like is to have XKB on joe without all the useless stuff that's being dragged in by xbase-clients. How do I do that? I don't think this is an unusual situation, is it? It is fairly uncommon. What you want to do is use xkbcomp on a machine that has xbase-clients installed to compile a keymap file corresponding to the desired configuration, and then transfer that .xkm file to the X terminal, where you can use the X server's -xkbmap option to load it. Please see xkbcomp(1x) and Xserver(1x) for more information. -- G. Branden Robinson|America is at that awkward stage. Debian GNU/Linux |It's too late to work within the [EMAIL PROTECTED] |system, but too early to shoot the http://people.debian.org/~branden/ |bastards. -- Claire Wolfe signature.asc Description: Digital signature
Processed: Re: Bug#229566: strace -tfo output
Processing commands for [EMAIL PROTECTED]: retitle 229566 xterm: fails to start with 'fatal pty error 23 (errno=22) on tty /dev/pts/3' Bug#229566: xterm fails to start with EINVAL Changed Bug title. tag 229566 - moreinfo Bug#229566: xterm: fails to start with 'fatal pty error 23 (errno=22) on tty /dev/pts/3' Tags were: help moreinfo Tags removed: moreinfo thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: Re: Bug#284111: xserver-xfree86: Doesn't scan PCI domains above 0000 on startup
Processing commands for [EMAIL PROTECTED]: close 284111 Bug#284111: xserver-xfree86: Doesn't scan PCI domains above on startup 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Ron Murray [EMAIL PROTECTED] severity 284111 normal Bug#284111: xserver-xfree86: Doesn't scan PCI domains above on startup Severity set to `normal'. merge 284111 279436 Bug#279436: xserver-xfree86: fix for bug #246782 breaks X server on machines with no PCI bus #0 Bug#284111: xserver-xfree86: Doesn't scan PCI domains above on startup Merged 279436 284111. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#284111: xserver-xfree86: Doesn't scan PCI domains above 0000 on startup
close 284111 severity 284111 normal merge 284111 279436 thanks On Fri, Dec 03, 2004 at 01:48:45PM -0500, Ron Murray wrote: Package: xserver-xfree86 Version: 4.3.0.dfsg.1-8rjmx3 Severity: important When I try to start X under a 2.6 kernel, the PCI scan never finds my video board. I strongly suspect that this is because it's on PCI domain 0001: the PCI scan code only appears to consider domain (see patch in bug #279436). Here's the output of 'lspci -v' on this machine: I do not understand why you knowingly filed a duplicate report. In any event, this bug was fixed in xfree86 4.3.0.dfsg.1-9. xfree86 (4.3.0.dfsg.1-9) unstable; urgency=high [...] * Apply patch from David Mosberger that replaces the fix for #225526 with one that works on systems that do not have a PCI bus numbered 0. Thanks, David! (Closes: #279436) [...] -- Fabio M. Di Nitto [EMAIL PROTECTED] Thu, 9 Dec 2004 17:14:45 +0100 Closing this duplicate, resolved report. -- G. Branden Robinson| Never attribute to human stupidity Debian GNU/Linux | that which can be adequately [EMAIL PROTECTED] | explained by GNU Libtool. http://people.debian.org/~branden/ | -- Scott James Remnant signature.asc Description: Digital signature
Bug#283929: followup
On Sat, Dec 18, 2004 at 09:11:34PM -0500, Branden Robinson wrote: Date: Sat, 18 Dec 2004 21:11:34 -0500 From: Branden Robinson [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Reply-To: Branden Robinson [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Bug#283929: xv application lock-ups trident driver [snip] Examining http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/hw/xfree86/CHANGELOG?rev=HEAD I see various fixes for the trident driver, which of them are incorporated in debian version? You can review the list of patches we have incorporated by looking at the source package. $ apt-get source xfree86 (Warning, this is a big download.) The file in question is: debian/patches/000_stolen_from_HEAD_trident_driver.diff I've downloaded debian's source of xfree86 and compiled it with fresh trident drivers from CVS, anyway problem persisted. Then I've tried knoppix on my hardware and it worked without any problems and lock-ups. The only major difference in knoppix's xserver config and mine was color depth. So I've changed default depth to 16bit and now it doesn't lock up my laptop. I've tried again depth of 24bits, but specified 1MB less memory to kernel on boot and it works fine. (i've tried this just a couple of minutes ago and cannot be so sure, but i think it will work without any problems). I'm running Debian on Acer's Travel Mate 354TE where video ram is borrowed from main ram, so I think video driver or kernel doesn't detect correctly video ram size and somehow corrupts kernel memory IMHO. Anyway here's info you have requested from /usr/share/bug/xserver-xfree86, but I think you can close the bug. Thank you for your time. [cut line] Contents of /var/lib/xfree86/X.roster: xserver-xfree86 xserver-xfree86-dbg /etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 20 2004-12-13 13:59 /etc/X11/X - /usr/bin/X11/XFree86 -rwxr-xr-x 1 root root 1745484 2004-09-28 15:09 /usr/bin/X11/XFree86 Contents of /var/lib/xfree86/XF86Config-4.roster: xserver-xfree86 xserver-xfree86-dbg VGA-compatible devices on PCI bus: :01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1 (rev 5d) /var/lib/xfree86/XF86Config-4.md5sum does not exist. XFree86 X server configuration file status: -rw-r--r-- 1 root root 3511 2004-12-20 10:16 /etc/X11/XF86Config-4 Contents of /etc/X11/XF86Config-4: # XF86Config-4 (XFree86 X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type man XF86Config-4 at the shell prompt.) # # This file is automatically updated on xserver-xfree86 package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xfree86 # package. # # If you have edited this file but would like it to be automatically updated # again, run the following commands as root: # # cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom # md5sum /etc/X11/XF86Config-4 /var/lib/xfree86/XF86Config-4.md5sum # dpkg-reconfigure xserver-xfree86 Section Files FontPathunix/:7100# local font server # if the local font server has problems, we can fall back on these FontPath/usr/lib/X11/fonts/misc FontPath/usr/lib/X11/fonts/cyrillic FontPath/usr/lib/X11/fonts/100dpi/:unscaled FontPath/usr/lib/X11/fonts/75dpi/:unscaled FontPath/usr/lib/X11/fonts/Type1 FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType FontPath/usr/lib/X11/fonts/Speedo FontPath/usr/lib/X11/fonts/100dpi FontPath/usr/lib/X11/fonts/75dpi EndSection Section Module LoadGLcore Loadbitmap Loaddbe Loadddc Loaddri Loadextmod Loadglx Loadrecord Loadspeedo Loadtype1 # Loadvbe Loadxtt EndSection Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc105 Option XkbLayout us,ro,ru Option XkbOptionsgrp:alt_shift_toggle Option XkbVariant EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/psaux Option Protocol PS/2 Option ZAxisMapping 4 5 EndSection Section InputDevice Identifier Generic Mouse
Bug#229566: strace -tfo output
retitle 229566 xterm: fails to start with 'fatal pty error 23 (errno=22) on tty
/dev/pts/3'
tag 229566 - moreinfo
thanks
On Thu, Dec 02, 2004 at 11:25:26PM -0800, Don Armstrong wrote:
http://rzlab.ucr.edu/debian/xterm/strace_tfo_output
has the strace tfo output generated with xterm 196.
Let me know if there's anything else I can get that would be of more
use.
Thomas,
After nearly a year, the strace you requested is available. :)
I'm attaching it to this message. It's only 1090 lines. :)
--
G. Branden Robinson| I am only good at complaining.
Debian GNU/Linux | You don't want me near your code.
[EMAIL PROTECTED] | -- Dan Jacobson
http://people.debian.org/~branden/ |
14092 23:17:55 execve(/usr/bin/X11/xterm, [xterm], [/* 22 vars */]) = 0
14092 23:17:55 uname({sys=Linux, node=xieana, ...}) = 0
14092 23:17:55 brk(0) = 0x10055000
14092 23:17:55 mmap(NULL, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x30016000
14092 23:17:55 access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
14092 23:17:55 open(/etc/ld.so.preload, O_RDONLY) = -1 ENOENT (No such file
or directory)
14092 23:17:55 open(/etc/ld.so.cache, O_RDONLY) = 5
14092 23:17:55 fstat64(5, {st_mode=S_IFREG|0644, st_size=41296, ...}) = 0
14092 23:17:55 mmap(NULL, 41296, PROT_READ, MAP_PRIVATE, 5, 0) = 0x30017000
14092 23:17:55 close(5) = 0
14092 23:17:55 access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
14092 23:17:55 open(/usr/lib/libXft.so.2, O_RDONLY) = 5
14092 23:17:55 read(5,
\177ELF\1\2\1\0\0\0\0\0\0\0\0\0\0\3\0\24\0\0\0\1\0\0J\224..., 512) = 512
14092 23:17:55 fstat64(5, {st_mode=S_IFREG|0644, st_size=74620, ...}) = 0
14092 23:17:55 mmap(0xffcd000, 141108, PROT_READ|PROT_EXEC, MAP_PRIVATE, 5, 0)
= 0xffcd000
14092 23:17:55 mprotect(0xffdf000, 67380, PROT_NONE) = 0
14092 23:17:55 mmap(0xffed000, 8192, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED, 5, 0x1) = 0xffed000
14092 23:17:55 mmap(0xffef000, 1844, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xffef000
14092 23:17:55 close(5) = 0
14092 23:17:55 access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
14092 23:17:55 open(/usr/lib/libfontconfig.so.1, O_RDONLY) = 5
14092 23:17:55 read(5,
\177ELF\1\2\1\0\0\0\0\0\0\0\0\0\0\3\0\24\0\0\0\1\0\0\262..., 512) = 512
14092 23:17:55 fstat64(5, {st_mode=S_IFREG|0644, st_size=180792, ...}) = 0
14092 23:17:55 mmap(0xff7f000, 251852, PROT_READ|PROT_EXEC, MAP_PRIVATE, 5, 0)
= 0xff7f000
14092 23:17:55 mprotect(0xffa9000, 79820, PROT_NONE) = 0
14092 23:17:55 mmap(0xffaf000, 49152, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED, 5, 0x2) = 0xffaf000
14092 23:17:55 mmap(0xffbb000, 6092, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xffbb000
14092 23:17:55 close(5) = 0
14092 23:17:55 access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
14092 23:17:55 open(/usr/lib/libfreetype.so.6, O_RDONLY) = 5
14092 23:17:55 read(5,
\177ELF\1\2\1\0\0\0\0\0\0\0\0\0\0\3\0\24\0\0\0\1\0\1L8..., 512) = 512
14092 23:17:55 fstat64(5, {st_mode=S_IFREG|0644, st_size=500664, ...}) = 0
14092 23:17:55 mmap(0xfee4000, 567184, PROT_READ|PROT_EXEC, MAP_PRIVATE, 5, 0)
= 0xfee4000
14092 23:17:55 mprotect(0xff57000, 96144, PROT_NONE) = 0
14092 23:17:55 mmap(0xff64000, 40960, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED, 5, 0x7) = 0xff64000
14092 23:17:55 mmap(0xff6e000, 1936, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xff6e000
14092 23:17:55 close(5) = 0
14092 23:17:55 access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
14092 23:17:55 open(/usr/lib/libexpat.so.1, O_RDONLY) = 5
14092 23:17:55 read(5,
\177ELF\1\2\1\0\0\0\0\0\0\0\0\0\0\3\0\24\0\0\0\1\0\0F\34..., 512) = 512
14092 23:17:55 fstat64(5, {st_mode=S_IFREG|0644, st_size=156064, ...}) = 0
14092 23:17:55 mmap(0xfe9e000, 220632, PROT_READ|PROT_EXEC, MAP_PRIVATE, 5, 0)
= 0xfe9e000
14092 23:17:55 mprotect(0xfec1000, 77272, PROT_NONE) = 0
14092 23:17:55 mmap(0xfece000, 24576, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED, 5, 0x2) = 0xfece000
14092 23:17:55 close(5) = 0
14092 23:17:55 access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
14092 23:17:55 open(/usr/lib/libXrender.so.1, O_RDONLY) = 5
14092 23:17:55 read(5,
\177ELF\1\2\1\0\0\0\0\0\0\0\0\0\0\3\0\24\0\0\0\1\0\0%\320..., 512) = 512
14092 23:17:55 fstat64(5, {st_mode=S_IFREG|0644, st_size=38348, ...}) = 0
14092 23:17:55 mmap(NULL, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x30022000
14092 23:17:55 mmap(0xfe74000, 103156, PROT_READ|PROT_EXEC, MAP_PRIVATE, 5, 0)
= 0xfe74000
14092 23:17:55 mprotect(0xfe7d000, 66292, PROT_NONE) = 0
14092 23:17:55 mmap(0xfe84000, 40960,
Processed: Re: Bug#284245: xserver-xfree86: memory leak when Xinerama/dualscreen enabled
Processing commands for [EMAIL PROTECTED]: retitle 284245 xserver-xfree86: [ati/radeon] X server leaks memory when Xinerama enabled on Radeon RV100 QY [Radeon 7000/VE] rev 0 Bug#284245: xserver-xfree86: memory leak when Xinerama/dualscreen enabled Changed Bug title. tag 284245 + upstream help Bug#284245: xserver-xfree86: [ati/radeon] X server leaks memory when Xinerama enabled on Radeon RV100 QY [Radeon 7000/VE] rev 0 There were no tags set. Tags added: upstream, help thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#236086: Norton AntiVirus detected a virus in a message you sent. The inf ected attachment was deleted.
Recipient of the infected attachment: Genialloyd - Servizio assicurativo on-line\Posta in arrivo Subject of the message: Mail Delivery (failure [EMAIL PROTECTED]) One or more attachments were deleted Attachment message.scr was Deleted for the following reasons: Virus [EMAIL PROTECTED] was found. application/ms-tnef
Bug#284245: xserver-xfree86: memory leak when Xinerama/dualscreen enabled
retitle 284245 xserver-xfree86: [ati/radeon] X server leaks memory when Xinerama enabled on Radeon RV100 QY [Radeon 7000/VE] rev 0 tag 284245 + upstream help thanks On Sat, Dec 04, 2004 at 01:29:59PM -0800, [EMAIL PROTECTED] wrote: Package: xserver-xfree86 Version: 4.3.0.dfsg.1-8 Severity: normal It is a severe memory leak when enabled Xinerama. Committed memory usage climbs to entire amount of physical+swap. Must kill X server and restart display manager to free memory. Quitting X session back to display manager frees memory not. [...] (--) PCI:*(1:0:0) ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] rev 0, Mem @ 0xd000/27, 0xdfef/16, I/O @ 0x8800/8, BIOS @ 0xdfec/17 I'm going to need help with this one, as I do not have a dual-head set of any kind to experiment with. I'd also be curious to know if people using drivers other than radeon are seeing this. -- G. Branden Robinson|The first thing the communists do Debian GNU/Linux |when they take over a country is to [EMAIL PROTECTED] |outlaw cockfighting. http://people.debian.org/~branden/ |-- Oklahoma State Senator John Monks signature.asc Description: Digital signature
Processed: Re: Bug#284306: xserver-common: Problem with Xwrapper : X: user not authorized to run the X server, aborting.
Processing commands for [EMAIL PROTECTED]: tag 284306 - patch Bug#284306: xserver-common: Problem with Xwrapper : X: user not authorized to run the X server, aborting. Tags were: patch Tags removed: patch tag 284306 + unreproducible Bug#284306: xserver-common: Problem with Xwrapper : X: user not authorized to run the X server, aborting. There were no tags set. Tags added: unreproducible thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: tagging 284025
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.5 # fixed in Debian X Strike Force XFree86 repository; to view, run svn diff -r 2101:2102 svn://necrotic.deadbeast.net/xfree86 tags 284025 + pending Bug#284025: xserver-xfree86: [ati/radeon] SEGV in RADEONQueryConnectedDisplays() Tags were: patch upstream 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)
/usr/lib/X11 symlink problems
Hello, I have quite an old install and my /usr/ was not large enough, so I copied it elsewhere and had /usr/lib/ be a symlink. It worked, but just the X packages where to be installed with some caution for some time. Now I cannot install it as xfree86-common complains. Yet I do believe it is correct, see for yourself: shekinah /usr/lib # ls -la X11 lrwxrwxrwx 1 root root 18 Dec 20 12:04 X11 - /usr/X11R6/lib/X11/ Obviously due to the (good or bad) decision to put /usr/lib/ elsewhere a relative link does not work for me. Any good ideas or clever thoughts? I will have to go through the postinst script for this time to get it installled fine, but that's a bad thing to do. Thanks, Alexander
Bug#286502: missing ] in /etc/init.d/xfs
Package: xfs
Version: 4.3.0.dfsg.1-9
Severity: normal
Tags: patch
hi,
there i a mistake in /etc/init.d/xfs:
sudo /etc/init.d/xfs restart
Stopping X font server: xfs.
Setting up X font server socket directory /tmp/.font-unix.../etc/init.d/xfs:
line 24: [: missing `]'
done.
Starting X font server: xfs.
i wrote a patch, it is in the attachment.
regards nico
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.9
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored:
LC_ALL set to [EMAIL PROTECTED])
Versions of packages xfs depends on:
ii libc6 2.3.2.ds1-19 GNU C Library: Shared libraries an
ii zlib1g 1:1.2.2-4compression library - runtime
-- no debconf information
--
Nico Golde - [EMAIL PROTECTED] | GPG: 1024D/73647CFF ,'`.
[EMAIL PROTECTED] | http://www.ngolde.de ( grml.org
VIM has two modes - the one in which it beeps`._,'
and the one in which it doesn't -- encrypted mail preferred
--- /etc/init.d/xfs 2004-12-20 15:07:57.0 +0100
+++ xfs.patch 2004-12-20 15:07:25.0 +0100
@@ -21,7 +21,7 @@
set_up_socket_dir () {
echo -n Setting up X font server socket directory $SOCKET_DIR...
- if [ -e $SOCKET_DIR ! [ -d $SOCKET_DIR ]; then
+ if [ -e $SOCKET_DIR ] ! [ -d $SOCKET_DIR ]; then
mv $SOCKET_DIR $SOCKET_DIR.$$
fi
mkdir -p $SOCKET_DIR
signature.asc
Description: Digital signature
Processed: Re: Bug#286502: missing ] in /etc/init.d/xfs
Processing commands for [EMAIL PROTECTED]: package xfs Ignoring bugs not assigned to: xfs close 286502 Bug#286502: missing ] in /etc/init.d/xfs 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Nico Golde [EMAIL PROTECTED] merge 286502 285133 Bug#285133: Typo in XFS startup script Bug#286502: missing ] in /etc/init.d/xfs Mismatch - only Bugs in same state can be merged: Values for `severity' don't match: #285133 has `serious'; #286502 has `normal' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#286502: missing ] in /etc/init.d/xfs
package xfs close 286502 merge 286502 285133 thanks On Monday, December 20, 2004 2:10 PM, Nico Golde [EMAIL PROTECTED] wrote: Package: xfs Version: 4.3.0.dfsg.1-9 Severity: normal Tags: patch hi, there i a mistake in /etc/init.d/xfs: In fact, your patch is exactly what was done in 4.3.0.dfsg.1-10, to close the previous report of this bug (#285133). Closing this report as the fixed packages are already in the archive. Regards, Adam
Processed: Fix severity and merge
Processing commands for [EMAIL PROTECTED]: package xfs Ignoring bugs not assigned to: xfs severity 286502 serious Bug#286502: missing ] in /etc/init.d/xfs Severity set to `serious'. merge 286502 285133 Bug#285133: Typo in XFS startup script Bug#286502: missing ] in /etc/init.d/xfs Bug#285154: typo in /etc/init.d/xfs prevents it from setting up X font server socket directory Bug#286043: xfs: init.d scrip has bad test[] paramiters. Merged 285133 285154 286043 286502. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#284111: xserver-xfree86: Doesn't scan PCI domains above 0000 on startup
Branden Robinson wrote:
close 284111
severity 284111 normal
merge 284111 279436
thanks
On Fri, Dec 03, 2004 at 01:48:45PM -0500, Ron Murray wrote:
Package: xserver-xfree86
Version: 4.3.0.dfsg.1-8rjmx3
Severity: important
When I try to start X under a 2.6 kernel, the PCI scan never finds my
video board. I strongly suspect that this is because it's on PCI
domain 0001: the PCI scan code only appears to consider domain
(see patch in bug #279436). Here's the output of 'lspci -v' on this
machine:
I do not understand why you knowingly filed a duplicate report.
In any event, this bug was fixed in xfree86 4.3.0.dfsg.1-9.
xfree86 (4.3.0.dfsg.1-9) unstable; urgency=high
[...]
* Apply patch from David Mosberger that replaces the fix for #225526 with
one that works on systems that do not have a PCI bus numbered 0. Thanks,
David! (Closes: #279436)
[...]
-- Fabio M. Di Nitto [EMAIL PROTECTED] Thu, 9 Dec 2004 17:14:45 +0100
Closing this duplicate, resolved report.
I don't think it really is a duplicate. The patch referred to in
#279436 only seems to consider PCI domain . Here's what I get when I
do 'ls /proc/bus/pci' on this machine (with a 2.6 kernel: 2.4 kernels
are quite different):
:80
:81
0001:00
devices
Now the way I read the patch in #279436 is that it hard-codes domain
:
+ /* with PCI domain #: */
+ {
+ /proc/bus/pci/:%02x/%02x.%1x, /* bus # 256 */
+ /proc/bus/pci/:%04x/%02x.%1x/* bus # = 256 */
Since my video board is on the 0001:00 bus, xserver never sees it.
It works with the fb device, but not with the glint driver for that
reason. And so I filed another bug report, since I don't think that the
solution to #279436 will fix the problem I have.
Of course, it's quite possible that I've read this wrong. In
particular, I'm still trying to grasp the whole PCI domain bit. But I do
not see any way that the above code can open anything with
/proc/bus/pci/0001: in it. If I'm wrong, then fair enough. Otherwise,
can we re-open this bug?
Thanks,
.Ron
**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager at postmaster at dor.state.ma.us.
**
xfree86_4.3.0.dfsg.1-10_mips.changes REJECTED
Rejected: libxpm-dev_4.3.0.dfsg.1-10_mips.deb: control file lists name as `libxpm-dev', which isn't in changes file. === If you don't understand why your files were rejected, or if the override file requires editing, reply to this email.
Take prescripiton medicine
Title: shearer noetherian eightfold degradation appointe Get all your prescriptions in one location! A whole range of tablets! Take a look! You name it! We have them all! Stop receiving promotional material now formate coproduct countrymen leapt nicosia seattle
Bug#286581: xlibs: Error in key definition for Dutch keyboards
Package: xlibs Version: 4.3.0.dfsg.1-8 Severity: normal Tags: l10n Yesterday I created a new keyboard layout for console-data for keyboards with a Dutch keymap (see #286401). Denis Barbier checked my layout against the one for X and noticed an inconsistency in de definition for keycode 86. It seems that bracketleft and bracketright are switched in the definition for X: 86 unshifted should be ] 86 shifted should be [ On Monday 20 December 2004 23:41, Denis Barbier wrote: On Mon, Dec 20, 2004 at 11:18:08PM +0100, Frans Pop wrote: On Monday 20 December 2004 22:58, Denis Barbier wrote: Your keymap looks good, and it seems that X keyboard definition switches brakcetleft and bracketright, can you please check so that this can also be fixed? ] is a normal keypress, [ is with shift (unlogical but true), so my definition is correct. See also: http://publib.boulder.ibm.com/iseries/v5r2/ic2924/index.htm?info/nls/rbagslayouts.htm I trust you, but please file a bugreport against xlibs so that other interested people may give comments. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-10.0412-2 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
X Strike Force XFree86 SVN property change: propchange - r2078 svn:log
Author: branden Revision: 2078 Property Name: svn:log New Property Value: Merge 4.3.0.dfsg.1-10 release bits and inaugurate 4.3.0.dfsg.1-11 development.
Processed: Re: Bug#285699: [sessreg] fails with error message from Xstartup; users cannot login with xdm
Processing commands for [EMAIL PROTECTED]: close 285699 Bug#285699: [sessreg] fails with error message from Xstartup; users cannot login with xdm 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Jeffrey W. Baker [EMAIL PROTECTED] reassign 285699 xdm Bug#285699: [sessreg] fails with error message from Xstartup; users cannot login with xdm Bug reassigned from package `xutils' to `xdm'. severity 285699 serious Bug#285699: [sessreg] fails with error message from Xstartup; users cannot login with xdm Severity set to `serious'. merge 285699 285150 Bug#285150: xdm: typo in /etc/X11/xdm/Xstartup prevents login Bug#285699: [sessreg] fails with error message from Xstartup; users cannot login with xdm Bug#285151: xdm: doesn't start xserver after updgrading to version 1.9 Bug#285782: xdm fails to login due to error in Xstartup Merged 285150 285151 285699 285782. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
X Strike Force XFree86 SVN commit: r2103 - trunk/debian
Author: branden Date: 2004-12-20 18:33:32 -0500 (Mon, 20 Dec 2004) New Revision: 2103 Modified: trunk/debian/TODO Log: Remove item that was fixed back in 4.3.0.dfsg.1-7. Modified: trunk/debian/TODO === --- trunk/debian/TODO 2004-12-20 09:25:59 UTC (rev 2102) +++ trunk/debian/TODO 2004-12-20 23:33:32 UTC (rev 2103) @@ -52,7 +52,6 @@ http://lists.debian.org/debian-x/2003/debian-x-200311/msg2.html * #253480: xdm: XDM fails if the user is over disk quota, but empty files can be created -* #261163: xlibs: KPDL mapping wrong in Polish layouts [patch available] * #255011: add macintosh/ca symbols file; awaiting keyboard photograph and test cycle with [EMAIL PROTECTED]
Bug#285699: [sessreg] fails with error message from Xstartup; users cannot login with xdm
close 285699
reassign 285699 xdm
severity 285699 serious
merge 285699 285150
thanks
On Tue, Dec 14, 2004 at 02:57:57PM -0800, Jeffrey W. Baker wrote:
After upgrade th 4.3.1.dfsg.1-9, nobody can login using xdm, although
normal invocation of startx works fine. The following message appears
in xdm.log:
sessreg: usage sessreg {-a -d} [-w wtmp-file] [-u utmp-file] [-L
lastlog-file]
[-t ttys-file] [-l line-name] [-h host-name]
[-s slot-number] [-x servers-file] user-name
I added a line to Xstartup to echo $DISPLAY and $USER to a file in /tmp,
and they seem reasonable (:0 and jwb, respectively).
I have worked around the problem by removing use-sessreg in in
xdm.options, but with this bug and the default config, nobody can
use xdm.
The bug was in xdm, and was fixed in xdm 4.3.0.dfsg.1-10. See
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=285150
for more information.
Closing and merging this duplicate resolved report.
[The following is a form letter.]
Hello,
You recently filed a duplicate bug report against a Debian package; that
is, the problem had already been reported.
While there is often nothing inherently wrong with doing so, the filing of
duplicate reports can cause Debian package maintainers to spend time
performing triage and maintenance operations on bug reports (e.g.,
instructing the Debian Bug Tracking System to merge the duplicates) that
could otherwise be spent resolving problems and doing other work on the
package.
One very good way to file bugs with the Debian Bug Tracking System is to
use the reportbug package and command of the same name. A very nice
feature of reportbug is that, if the machine where you run it has network
access to the World Wide Web, it can query the Debian Bug Tracking System
and show you existing reports. This reduces the chance that you'll file a
duplicate report, and offers you the option of adding follow-up information
to an existing bug report. This is especially valuable if you have unique
information to add to an existing report, because this way information
relevant to the problem is gathered together in one place as opposed to
being scattered among multiple, duplicate bug reports where some facts may
be overlooked by the package maintainers. The reportbug program also does
a lot of automatic information-gathering that helps package maintainers to
understand your system configuration, and also ensures that your message to
the Debian Bug Tracking System is well-formed so that it is processed
correctly by the automated tools that manage the reports. (If you've ever
gotten a bounce message from the Debian Bug Tracking System that tells
you your message couldn't be processed, you might appreciate this latter
feature.)
Therefore, I strongly urge you to give reportbug a try as your primary
bug reporting tool for the Debian System. (If you already do use
reportbug, please see below.)
One way to install reportbug is with apt-get; for
example:
# apt-get install reportbug
The reportbug command has a few different modes that cater to different
levels of user expertise. If this message has contained a lot of jargon
that is unfamiliar to you, you likely want to use reportbug's novice
mode; here's one way to do that.
$ reportbug --mode=novice
Please enter the name of the package in which you have found a problem,
or type 'other' to report a more general problem.
If you're more sophisticated, or if you are not using the released version
of Debian (stable), but instead Debian testing or unstable, you
should use reportbug's standard mode.
$ reportbug
Please enter the name of the package in which you have found a problem,
or type 'other' to report a more general problem.
The reportbug command is extensively documented in its usage message and
manual page. Commands to view these pieces of documentation are:
$ reportbug --help | more
$ man reportbug
(The output of the above commands has been omitted from this message.)
If you do use reportbug, but are so daunted by the large number of bugs
already filed against a package that you feel you cannot search for a
duplicate, please note that reportbug has a (f)ilter feature that enables
you to use a keyword search to limit the number of bugs reported. (If
you're feeling ambitious, the filter feature also accepts a regular
expression.) For example, if you'd like to report a SEGV (segfault), you
might filter based on the term SEGV. If you're having trouble upgrading
a package, you might filter based on upgrad (to catch both upgrade and
upgrading). Some package maintainers retitle bugs to contain keywords so
as to facilitate better filtering and convey more useful information, since
a bug report with a title of broken or the like is not very useful to
anyone.
We appreciate you taking the time to help package maintainers serve you
better by reducing the amount of time they need to spend coping with
duplicate bug reports.
Thanks for using
Processed: Bug#286581: xlibs: Error in key definition for Dutch keyboards
Processing commands for [EMAIL PROTECTED]: severity 286581 minor Bug#286581: xlibs: Error in key definition for Dutch keyboards Severity set to `minor'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
X Strike Force XFree86 SVN commit: r2104 - trunk/debian
Author: branden Date: 2004-12-20 19:08:45 -0500 (Mon, 20 Dec 2004) New Revision: 2104 Modified: trunk/debian/TODO Log: Remove item from TODO. More info is needed and the submitter is not being responsive, therefore it's anyone's guess when this tiem will be ready to move forward. Modified: trunk/debian/TODO === --- trunk/debian/TODO 2004-12-20 23:33:32 UTC (rev 2103) +++ trunk/debian/TODO 2004-12-21 00:08:45 UTC (rev 2104) @@ -52,8 +52,6 @@ http://lists.debian.org/debian-x/2003/debian-x-200311/msg2.html * #253480: xdm: XDM fails if the user is over disk quota, but empty files can be created -* #255011: add macintosh/ca symbols file; awaiting keyboard photograph and test - cycle with [EMAIL PROTECTED] Post 4.3.0-1
Processed: tagging 255011
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.5 # I need feedback to my message http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=255011msg=24 damn it! tags 255011 + moreinfo Bug#255011: xlibs: support for ca layout on macintosh model wanted Tags were: upstream Tags added: moreinfo End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#255011: #255011: xlibs: support for ca layout on macintosh wanted
re-sending the pic i made, but to the right place :). eric -- Cold pizza and cold coffee, second best thing to cold pizza and warm beer. keyboard_layout.png Description: PNG image signature.asc Description: Digital signature
Bug#255011: #255011: xlibs: support for ca layout on macintosh wanted
hi again,
i'd really like to have the right control and left command (win key)
be as right control and left win, but it seems that for some reason -
either with model of pc105 or macintosh, i get them bound to the same
key. other than that, the following configuration Work For Me. i can do
{}[] and | no problem.
Section InputDevice
Identifier Keyboard0
Driver keyboard
Option XkbRules xfree86
Option XkbModel pc105
Option XkbLayout ca
Option XkbOptions ctrl:nocaps lv3:rwin_switch
# -model pc105 -layout ca -option lv3:rwin_switch
EndSection
(though i haven't been able to get the caps lock to behave like a
control key yet :| ).
eric
--
We're not talking about the same thing, he said. For you the world is
weird because if you're not bored with it you're at odds with it. For me
the world is weird because it is stupendous, awesome, mysterious,
unfathomable; my interest has been to convince you that you must accept
responsibility for being here, in this marvelous world, in this marvelous
desert, in this marvelous time. I wanted to convince you that you must
learn to make every act count, since you are going to be here for only a
short while, in fact, too short for witnessing all the marvels of it.
-- Don Juan
signature.asc
Description: Digital signature
Re: ATI Radeon 9200 256MB PCI xfree86-4.3.0.1 - hang
On Mon, 2004-12-20 at 02:59 -0500, Branden Robinson wrote: It sounds like the ati/radeon driver in XFree86 is simply misdetecting the amount of RAM on the display adapter. No, but only the first 128 MB of video RAM are directly accessible. Unfortunately, the radeon driver doesn't know how to deal with this yet; until that's fixed, the amount of video RAM has to be limited to 128 MB using the VideoRam directive. -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
