***** 0013-background-async.patch *****
PWD: /var/tmp/portage/gnome-base/gnome-shell-3.8.3-r1/work/gnome-shell-3.8.3

=======================================

PATCH COMMAND:  patch -p0 -g0 -E --no-backup-if-mismatch  < '/var/tmp/portage/gnome-base/gnome-shell-3.8.3-r1/work/gnome-shell-3.8.3-patches/0013-background-async.patch'

=======================================
can't find file to patch at input line 27
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|From: Lionel Landwerlin &lt;llandwerlin@gmail.com&gt;
|Date: Mon, 24 Jun 2013 18:13:05 +0000
|Subject: background: fix asynchronous management of background loading operations
|
|This fixes a blue background being drawn when switching the monitors
|configuration using hardware keys
|(clone/multimonitor/external/internal).
|
|The problem is that the shell gather all background loading requests
|under the same meta_background_load_file_async call using one
|GCancellable (the first one to come). So when the shell receives a
|batch of 12 or so XRandr events, it creates 12 new background managers
|which end up trying to load 12 times the same background picture. All
|of these requests are batched into the same
|meta_background_load_file_async using the first GCancellable received
|on the first request. Unfortunately, when the first request is
|cancelled by the following event indicating a new monitor setup, all
|of the background picture requests are dropped on the floor, and
|nothing gets loaded (hence the blue screen background).
|
|https://bugzilla.gnome.org/show_bug.cgi?id=703001
|---
|diff --git a/js/ui/background.js b/js/ui/background.js
|index 0e9c3aa..f2ffce8 100644
|--- a/js/ui/background.js
|+++ b/js/ui/background.js
--------------------------
No file to patch.  Skipping patch.
3 out of 3 hunks ignored

patch program exited with status 1
=======================================

PATCH COMMAND:  patch -p1 -g0 -E --no-backup-if-mismatch  < '/var/tmp/portage/gnome-base/gnome-shell-3.8.3-r1/work/gnome-shell-3.8.3-patches/0013-background-async.patch'

=======================================
patching file js/ui/background.js
Hunk #1 FAILED at 142.
Hunk #2 FAILED at 178.
2 out of 3 hunks FAILED -- saving rejects to file js/ui/background.js.rej

patch program exited with status 1
=======================================

PATCH COMMAND:  patch -p2 -g0 -E --no-backup-if-mismatch  < '/var/tmp/portage/gnome-base/gnome-shell-3.8.3-r1/work/gnome-shell-3.8.3-patches/0013-background-async.patch'

=======================================
can't find file to patch at input line 27
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|From: Lionel Landwerlin &lt;llandwerlin@gmail.com&gt;
|Date: Mon, 24 Jun 2013 18:13:05 +0000
|Subject: background: fix asynchronous management of background loading operations
|
|This fixes a blue background being drawn when switching the monitors
|configuration using hardware keys
|(clone/multimonitor/external/internal).
|
|The problem is that the shell gather all background loading requests
|under the same meta_background_load_file_async call using one
|GCancellable (the first one to come). So when the shell receives a
|batch of 12 or so XRandr events, it creates 12 new background managers
|which end up trying to load 12 times the same background picture. All
|of these requests are batched into the same
|meta_background_load_file_async using the first GCancellable received
|on the first request. Unfortunately, when the first request is
|cancelled by the following event indicating a new monitor setup, all
|of the background picture requests are dropped on the floor, and
|nothing gets loaded (hence the blue screen background).
|
|https://bugzilla.gnome.org/show_bug.cgi?id=703001
|---
|diff --git a/js/ui/background.js b/js/ui/background.js
|index 0e9c3aa..f2ffce8 100644
|--- a/js/ui/background.js
|+++ b/js/ui/background.js
--------------------------
No file to patch.  Skipping patch.
3 out of 3 hunks ignored

patch program exited with status 1
=======================================

PATCH COMMAND:  patch -p3 -g0 -E --no-backup-if-mismatch  < '/var/tmp/portage/gnome-base/gnome-shell-3.8.3-r1/work/gnome-shell-3.8.3-patches/0013-background-async.patch'

=======================================
can't find file to patch at input line 27
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|From: Lionel Landwerlin &lt;llandwerlin@gmail.com&gt;
|Date: Mon, 24 Jun 2013 18:13:05 +0000
|Subject: background: fix asynchronous management of background loading operations
|
|This fixes a blue background being drawn when switching the monitors
|configuration using hardware keys
|(clone/multimonitor/external/internal).
|
|The problem is that the shell gather all background loading requests
|under the same meta_background_load_file_async call using one
|GCancellable (the first one to come). So when the shell receives a
|batch of 12 or so XRandr events, it creates 12 new background managers
|which end up trying to load 12 times the same background picture. All
|of these requests are batched into the same
|meta_background_load_file_async using the first GCancellable received
|on the first request. Unfortunately, when the first request is
|cancelled by the following event indicating a new monitor setup, all
|of the background picture requests are dropped on the floor, and
|nothing gets loaded (hence the blue screen background).
|
|https://bugzilla.gnome.org/show_bug.cgi?id=703001
|---
|diff --git a/js/ui/background.js b/js/ui/background.js
|index 0e9c3aa..f2ffce8 100644
|--- a/js/ui/background.js
|+++ b/js/ui/background.js
--------------------------
No file to patch.  Skipping patch.
3 out of 3 hunks ignored

patch program exited with status 1
=======================================

PATCH COMMAND:  patch -p4 -g0 -E --no-backup-if-mismatch  < '/var/tmp/portage/gnome-base/gnome-shell-3.8.3-r1/work/gnome-shell-3.8.3-patches/0013-background-async.patch'

=======================================
can't find file to patch at input line 27
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|From: Lionel Landwerlin &lt;llandwerlin@gmail.com&gt;
|Date: Mon, 24 Jun 2013 18:13:05 +0000
|Subject: background: fix asynchronous management of background loading operations
|
|This fixes a blue background being drawn when switching the monitors
|configuration using hardware keys
|(clone/multimonitor/external/internal).
|
|The problem is that the shell gather all background loading requests
|under the same meta_background_load_file_async call using one
|GCancellable (the first one to come). So when the shell receives a
|batch of 12 or so XRandr events, it creates 12 new background managers
|which end up trying to load 12 times the same background picture. All
|of these requests are batched into the same
|meta_background_load_file_async using the first GCancellable received
|on the first request. Unfortunately, when the first request is
|cancelled by the following event indicating a new monitor setup, all
|of the background picture requests are dropped on the floor, and
|nothing gets loaded (hence the blue screen background).
|
|https://bugzilla.gnome.org/show_bug.cgi?id=703001
|---
|diff --git a/js/ui/background.js b/js/ui/background.js
|index 0e9c3aa..f2ffce8 100644
|--- a/js/ui/background.js
|+++ b/js/ui/background.js
--------------------------
No file to patch.  Skipping patch.
3 out of 3 hunks ignored

patch program exited with status 1
