search for: dhoworth

...o.c:452: _XRead: Assertion `dpy->xcb->reply_data != 0' failed. wine: Assertion failed at address 0xffffe410 (thread 0009), starting debugger... I googled and found hints that I need to use wine-tricks but when I tried, I see: Code: $ winetricks cc580 Executing sha1sum --status -c /home/dhoworth/winetrickscache/cc32inst.exe.sha1sum Executing wine /home/dhoworth/winetrickscache/cc32inst.exe /T:c:\winetrickstmp /c kscache/cc32inst.exe: xcb_io.c:452: _XRead: Assertion `dpy->xcb->reply_data != 0' failed. wine: Assertion failed at address 0xffffe410 (thread 000b), starting debugger......

Hi Dave, thanks for point that out. I didn't realise there was a detailed explanation of that field in the man page, I only saw the summary. Yes, that clearly explains how it's supposed to work. On 21 October 2016 at 01:46, Dave Howorth <dhoworth at mrc-lmb.cam.ac.uk> wrote: > On 2016-10-20 10:24, Samuel Williams wrote: >> >> Hello, >> >> I'm using Ruby's Shellwords module, which generates a string from an >> array, suitable for shell evaluation. >> >> Ruby's implementation prefers...

Hello, I'm using Ruby's Shellwords module, which generates a string from an array, suitable for shell evaluation. Ruby's implementation prefers escaping whitespace with a backslash rather than quotes. However, this appears to cause some kind of issue in Rsync when it computes argv from -e option. Here is an example command generated by some Ruby code: rsync --archive --stats -e

On 2016-10-10 17:24, Kip Warner wrote: > Note that I have temporarily disabled timeouts and added extra > verbosity. The transfer to the remote host via SSH works fine, up until > it gets to a 30+ GB file (a VM image). It gets about 90+ percent of the > way through, hangs, and then times out. I have a similar but different problem. I make a regular download from a site that always

On 2016-10-20 10:24, Samuel Williams wrote: > Hello, > > I'm using Ruby's Shellwords module, which generates a string from an > array, suitable for shell evaluation. > > Ruby's implementation prefers escaping whitespace with a backslash > rather than quotes. However, this appears to cause some kind of issue > in Rsync when it computes argv from -e option. The

I'm seeing an error that says there is a broken pipe, but the rsync command is local to one machine: /usr/bin/rsync -rltH --stats -D --delete --numeric-ids --whole-file /data/dir /backup/suse1/suse1-data-dir/ >/tmp/rsync-out 2>&1 The complete contents of the rsync-out file are: rsync: writefd_unbuffered failed to write 88 bytes [receiver]: Broken pipe (32) rsync error: error in

I use rsync to download a directory from a remote daemon. This has worked well for years but has recently started to give problems. The rsync transfer is run by a program called dirvish that is run as a cron job. The log looks like this: ACTION: rsync -vrltH --delete --stats -D --numeric-ids --exclude-from=/nfs/scop5/data/msd/sifts-mirror/2016-06-28/exclude