similar to: [Bug 55596] New: weston-launch causes graphical corruption / lockup

rsync -Ha --link-dest=/media/4tb/bak/panic-2012-01-01 /media/2tb/bak/panic-2012-02-01 /media/4tb/bak/ root at dancer:/media/4tb/bak# ls -l panic*/home/darxus/0000_latest.jpg -rw------- 15 darxus darxus 100772 1999-09-14 21:19 panic-2011-12-20/home/darxus/0000_latest.jpg -rw------- 15 darxus darxus 100772 1999-09-14 21:19 panic-2012-01-01/home/darxus/0000_latest.jpg -rw------- 1 darxus darxus

I'm watching my backup via rsync, throttled to a very low speed. Looks like downloading apache logs is taking the longest time (when I'm rsyncing over an old copy of the same data) because it's not noticing that, for example, www.chaosreigns.com-access.log.196.gz on the origin is the same file as www.chaosreigns.com-access.log.186.gz on the destination, so *everything* is getting

https://bugzilla.samba.org/show_bug.cgi?id=10233 Summary: rsync is spending a lot of time lstat64()'ing --exclude'd files Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org

I have legitimate ssh access to two remote machines. ssh directly from either machine to the other is blocked by firewalls which I cannot control. $ rsync -vae ssh user@host1:/tmp/dir user@host2:/tmp/ receiving file list ... done rsync: mkdir user@host2:/tmp: No such file or directory rsync error: error in file IO (code 11) at main.c(319) I would like this to copy host1:/tmp/dir into

Great job! I'm considering converting all my mp3 files to Vorbis format. Only examples/encoder_example is a bit too simplistic (of course, being an example), and the cmdline tools aren't ready. I encode my mp3 files at 96 kbit/s, because that's enough for me. Will Vorbis do well at this rate? Any quick hacks I can make to examples/encoder_example.c? Perhaps Vorbis is of interest

https://bugs.freedesktop.org/show_bug.cgi?id=48074 Bug #: 48074 Summary: 3D / OpenGL clients used with wayland always cause an immediate hang Classification: Unclassified Product: Mesa Version: 8.0 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium

I expect this is user error, but I thought I'd post in case anyone else is feeling a similar sense of losing their mind. I have a root cron job: 0 3 * * * rsync -Hva --stats --del ... / /media/2tb/bak/dancer-`date +\%F`/ "..." represents 4 --link-dest's and 22 --exclude's (including /media/). So last night, / should have been copied to

If I do ssh -i /home/darxus/.ssh/somekey user at host Where somekey is an rsa1 key, and host is only running ssh protocol 1, it fails to connect with "Permission denied (publickey).". 1) I think the specified v1 key should encourage ssh to try v1. 2) I think, if v2 fails, it should try v1. This works when I add the "-1" argument. -- "I don't want people who want

https://bugs.freedesktop.org/show_bug.cgi?id=56601 Priority: medium Bug ID: 56601 Assignee: nouveau at lists.freedesktop.org Summary: 9600m GT HDMI output no video or audio. Severity: normal Classification: Unclassified OS: Linux (All) Reporter: vekinn at gmail.com Hardware: x86-64 (AMD64)

https://bugs.freedesktop.org/show_bug.cgi?id=69488 Priority: medium Bug ID: 69488 Assignee: nouveau at lists.freedesktop.org Summary: GF108 (NVC1) GPU lockup QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: vekinn at gmail.com Hardware: Other

https://bugs.freedesktop.org/show_bug.cgi?id=75761 Pekka Paalanen <ppaalanen at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|wayland-bugs at lists.freedesk |nouveau at lists.freedesktop.o |top.org |rg QA Contact|

https://bugs.freedesktop.org/show_bug.cgi?id=75761 Pekka Paalanen <ppaalanen at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|NOTOURBUG |--- --- Comment #11 from Pekka Paalanen

https://bugs.freedesktop.org/show_bug.cgi?id=75761 Pekka Paalanen <ppaalanen at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEW --- Comment #12 from Pekka Paalanen <ppaalanen at gmail.com> --- Setting status to NEW, since this

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #13 from Lubosz Sarnecki <lubosz at gmail.com> --- My bisection process so far is pretty frustrating, since the majority of the commits between 3.12 and 3.13 do not boot. I get corrupted output before being able to login. The screen looks like so: http://i.imgur.com/C517qpP.jpg My current progress: # v3.12 good #

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #14 from Lubosz Sarnecki <lubosz at gmail.com> --- I am only bisecting the nouveau directory, like so: git bisect start v3.14 v3.10 -- drivers/gpu/drm/nouveau -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #15 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to comment #13) > My bisection process so far is pretty frustrating, > since the majority of the commits between 3.12 and 3.13 do not boot. > I get corrupted output before being able to login. What HW are you using? -- You are receiving this mail

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #16 from Lubosz Sarnecki <lubosz at gmail.com> --- Chipset: GF110 (NVC8) -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20140410/3e3ea7e7/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #17 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to comment #16) > Chipset: GF110 (NVC8) There are known issues with NVC8 that go away with blob pgraph fw, perhaps worth trying with that. (See bug #54437.) -- You are receiving this mail because: You are the assignee for the bug. -------------- next part

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #18 from Lubosz Sarnecki <lubosz at gmail.com> --- I was able to boot all commits with following boot option: nouveau.config=NvMSI=0 Thanks to xexaxo on the IRC for pointing out this option. f074d733866628973eca0ddb0c534ef4561da9e0 is the first bad commit commit f074d733866628973eca0ddb0c534ef4561da9e0 Author: Maarten

https://bugs.freedesktop.org/show_bug.cgi?id=75761 --- Comment #19 from Lubosz Sarnecki <lubosz at gmail.com> --- Reverting the patch on current Linux master (4a4389abdd9822fdf3cc2ac6ed87eb811fd43acc) fixes the issue for me. Apperently s->crtc needs to be hardcoded to -1 for the screen not to stay black when launching weston. -- You are receiving this mail because: You are the