Starting Shutter freezes in 0.93.1
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Shutter |
New
|
Undecided
|
Unassigned | ||
Bug Description
Shutter has suddenly started giving me issues with an older version in 0.90.1 throwing this error when I try to start shutter from Terminal to see why it's not starting from the applet launcher or from the setup hotkeys for taking screenshots;
> defined(@array) is deprecated at /usr/bin/shutter line 3736.
> (Maybe you should just omit the defined()?)
> defined(@array) is deprecated at /usr/bin/shutter line 3747.
> (Maybe you should just omit the defined()?)
Shutter wouldn't function at all. So I updated to 0.93.1~
I tried to do a GDB Debug dump to see what it's failing on, but GDB says this when I try to run it;
> "/usr/bin/shutter": not in executable format: File format not recognised
I had already checked it and it is in an executable format, it reads as rwx-r-x-r-x, it has executable permissions. In the previous version when it decided it wont work anymore and throwing that above error I noticed I couldn't even kill the process for Shutter, it would just hang idle, didn't matter what kill signal I sent to the process. I tried seeing if the same happened in the 0.93.1 version, but it doesn't seem to happen, I can kill it normally with the killall command.
When the blank frozen empty window pops up and does nothing, I can click the X button or hit close from the context menu it'll just show me asking if I want to force close Shutter or wait because it's not responding.
just a FYI: I'm currently using Linux Mint 17.2, and the packages up till now I've been using for Shutter is from Trusty, but seems that no longer works for me, and that's the repo that Linux Mint uses by default for 17.2.
EDIT 1:** Just caught this error from Terminal
> (shutter:21118): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
| description: | updated |
