Bug#694686: cron: sends non-MIME 8bit messages

brian m. carlson writes: > > cron sends 8-bit messages that are lacking a MIME-Version header. This > is in violation of RFC 5321 =C2=A7 2.3.1: It is impossible for cron to violate the SMTP specification, because cron doesn't use SMTP. In the simplest configuration, mail from cron can be deliver

Bug#629611: [PATCH] Fix ShmPutImage for XYBitmap

Julien Cristau writes: > > We can't call CopyArea in that case because the image has depth 1, which > might not match the target drawable, so we might overrun the shm > segment. Commit 11817a881cb93a89788105d1e575a468f2a8d27c apparently > fixed a similar bug for XYPixmap, but missed the bitmap ca

Bug#629611: xserver-xorg: reproducible X server segfault

I'm including here an updated version of the bug demonstration program. It now reliably segfaults every X server I can find. (That's not a lot of them since I haven't looked outside Debian stable.) It does the same basic operations as the previous test program in its bug-triggering mode, but allow

Bug#629611: xserver-xorg: reproducible X server segfault

Julien Cristau writes: > > On Sun, Oct 30, 2011 at 20:02:43 -0500, pac...@kosh.dhis.org wrote: > > > Disable "dri" > > Disable "dri2" > > Any particular reason you're doing this? Because I've read the security document[1]. There's a lot of scary stuff in there. [1] http://dri.sourcefor

Bug#629611: xserver-xorg: reproducible X server segfault

Julien Cristau writes: > > On Tue, Jun 7, 2011 at 23:56:08 -0500, Alan Curry wrote: > > > Xorg X server configuration file status: > > > > -rw--- 1 root root 3981 Feb 8 22:05 /etc/X11/xorg.conf > > > > Contents of /etc/X11/xorg.conf: > > ---

Bug#630944: dd can't seek and read in /proc/self/mem

=?iso-8859-1?Q?Jörg?= Sommer writes: > > pac...@kosh.dhis.org hat am Mon 27. Jun, 23:02 (-0500) geschrieben: > > =?iso-8859-1?Q?J=F6rg?= Sommer writes: > > > I don't know, why dd thinks something went wrong. llseek() and fstat64() > > > didn't return an error. Accessing the file with Ruby yields t

Bug#630944: dd can't seek and read in /proc/self/mem

=?iso-8859-1?Q?J=F6rg?= Sommer writes: > > Package: coreutils > Version: 8.5-1 > Severity: normal > > Hi, > > I wanted to extract the vdso segment, but dd can't work in > /proc/self/mem. The kernel restricts use of /proc/PID/mem to the process that is currently ptrace'ing (debugging) PID. dd ca

Bug#629611: xserver-xorg: reproducible X server segfault

Cyril Brulebois writes: > > thanks for the test case, even though I can't reproduce it. A full > backtrace might be nice: > http://pkg-xorg.alioth.debian.org/howto/use-gdb.html Here's what I got from that. (gdb) bt full #0 0x0fb028bc in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/lin

Bug#628511: iputils-ping: Ping unlawfully convert wrong or incomplete ip addresses

franchi writes: > > Package: iputils-ping > Version: 3:20100418-3 > Severity: minor > > My Default GW has IP 10.0.0.1 > The output of all both the commands: > > A) - ping 10.1 > > B) - ping 10.0.1 > > is "64 bytes from 10.0.0.1: icmp_req=1 ttl=64 time=0.853 ms". > These are valid IP address

Bug#610122: xjig: timer goes on after completing, finally causes beeps every 1s

Yann Dirson writes: > > FWIW - restricted the duration after which the beep occurs: > > - more than 11days 00:26:40 (15866min) > - less than 11days 17:50:22 (16910min) If you keep measuring, you'll end up at 11 days 13:46:40 (exactly 1 million seconds). The magic value 100 is used for an "in

Bug#605861: manpages-dev: return type of pclose possibly wrong

Daniel Reichelt writes: > > a) > when assigning > int i = pclose(pipeFD); > OR assigning > long i = pclose(pipeFD); > I get a compiler warning like this: > warning: assignment makes integer from pointer without a cast So pclose is apparently declared as returning a pointer. That's unusual. The m

Bug#602575: bash: Commands executed with $($prog) do not run properly

In article you write: >Package: bash >Version: 4.1-3 >Severity: normal > >Hi, > >if a program ist started with $($prog) the output is different from >or even $(). Example with find (excluding a directory from search): > [...] >$ echo $prog >find /test -type d ! -wholename "/test" >$ echo "$($prog

Bug#602508: csh: $? variable trigger error

Emiliano Visentin writes: > > Package: csh > Version: 20070713-1 > Severity: important > > In my cshell script I can't test the $? variable. In csh there isn't a $? variable. $?var is the syntax to query whether a variable named "var" exists. You're looking for $status -- Alan Curry -- To

Bug#595180: tcsh: ^W (werase) acts the same as ^U (kill)

Bjarni Ingi Gislason writes: > > Package: tcsh > Version: 6.14.00-7 > Severity: normal > > Output from "stty -a": [...] stty modes are relevant when you're entering text in the tty's canonical input mode, where there are only a few controls (erase, werase, kill). tcsh has its own command line

Bug#595161: libc6-dbg: zero documentation

mtctr r11 0x18cc : bctr 0x18d0 : nop 0x18d4 : nop 0x18d8 : nop 0x18dc : nop 0x18e0 : lis r12,4097 0x18e4 : addis r11,r11,-4096 0x100008e8 : lwz r0,2736(r12) (gdb) stepi 0x18b4 in printf () (gdb) 0x18b8 in printf () [...several more stepi's sn

Bug#590229: [coreutils] date reports illegal date jan 1st. 1982

Lars Boegild Thomsen writes: > > I am sure this one is upstream - and it's absolutely weird. This should > explain all: It's weird, and a FAQ. > > l...@ncpws04:~$ date --date=1981-12-31 >

Bug#590008: cpp-4.4: incorrect macro expansion when a macro call results in the same

Philip Ashmore writes: > > Package: cpp-4.4 > Version: 4.4.4-6 > Severity: normal > > Here's an example > > #define appendc(x) x##c > #define aXc(X) appendc(a##X) > #define abc appendc(abb) > > int aXc(b) = 0; // appendc(ab) -> abc -> appendc(abb) -> abbc > > int main(int a

Bug#584801: problem with German umlaut

Harald Dunkel writes: > > Is this a special xterm feature? "whois sensors.de" works much better > with -k8. Would you suggest to make -k8 the default? In a perfect world, it would be unnecessary since you wouldn't have anything written on your terminal that wasn't in the proper charset. In the r

Bug#481166: Reproduction of tiny menu in xterm; see attached png

Don Armstrong writes: > > See the attached png which shows the tiny menu in xterm. I'll dig up > some more useful debugging info. That looks familiar. Once, while experimenting with X resources, I added something like this: XTerm*Geometry: 80x30 which made the VT100 window 80x30 characters (int

Bug#584801: problem with German umlaut

Thomas Dickey writes: > > That file is all ascii, so probably not what you wanted to attach. > > ascii here, too. That must be some kind of mail system bug, closer to your end than the submitter. Viewing on http://bugs.debian.org/584801 I can see that the original message included this base64-enc

Bug#550428: 133668 looks similar

Looking through the old archives, I found another similar bug report, #133668, which was also closed without actually fixing the bug. People, this is simple: grep gethostbyaddr sysdeps/posix/getaddrinfo.c && echo STILL BUGGY DAMMIT -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.