fails to capture with Unexpected short read from authority file

[anarcat]

This is a copy of the Debian bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764011

Shutter now fails to perform simple screenshots in Debian Jessie.

Here's an example of this problem:

```
anarcat@marcos:~$ shutter -s
defined(@array) is deprecated at /usr/bin/shutter line 3727.
        (Maybe you should just omit the defined()?)
defined(@array) is deprecated at /usr/bin/shutter line 3738.
        (Maybe you should just omit the defined()?)
WARNING: Gtk2::AppIndicator is missing --> there will be no icon showing up in the status bar when running Unity!

[... select zone, press enter]
Expecting 1645 bytes, got 47 at -1 at /usr/share/perl5/X11/Auth.pm line 39.
*** unhandled exception in callback:
*** Unexpected short read from authority file/home/anarcat/.Xauthority at /usr/share/perl5/X11/Protocol.pm line 2307.
*** ignoring at /usr/share/perl5/Shutter/Screenshot/Main.pm line 352.

[at this point i expected the usual popup with the captured image, but
instead shutter seems hanged. sending a signal (e.g. control-c on the
terminal) makes it resume its regular duties and the captured image
shows up normally]

^CGLib-CRITICAL **: Source ID 159 was not found when attempting to remove it at /usr/bin/shutter line 7247.
```

I marked this as "grave" because it makes shutter basically completely
unuseable unless someone knows about the commandline, which makes
shutter basically useless (i can think of a few other ways to make
screenshots from the commandline, the whole point of this software is
to have an intuitive pointy-clicky interface).

My .Xauthority file is readable:

anarcat@marcos:~$ file .Xauthority
.Xauthority: X11 Xauthority data

Interestingly, moving away my .shutter directory fixes the problem. so i
guess that's not something that deserves "grave" severity...

I have been able to isolate the problem to the "Include cursor when
taking a screenshot" setting. If it's on, I see the bug, if it's off, I
don't, regardless of the above versions.

Not sure what's going on - surely there's interaction with some other
component that has been upgraded, but I'm at a loss as to what happened
exactly...

[Michael Kogan (michael-kogan)]

This is reported against a very old Shutter version. I'd propose to report the bug upstream if it is still present: https://github.com/shutter-project/shutter/issues