Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't take screenshot while using Cinnamon w/ dual screen #670

Closed
dcelasun opened this issue May 3, 2012 · 22 comments
Closed

Can't take screenshot while using Cinnamon w/ dual screen #670

dcelasun opened this issue May 3, 2012 · 22 comments

Comments

@dcelasun
Copy link

dcelasun commented May 3, 2012

Just installed Cinnamon on Ubuntu 12.04 after a fresh install. I tried taking a screenshot with various panel plugins and standalone apps (deepin-scrot) without success. Everytime I try, cinnamon brings the wallpaper above all windows and hence takes the screenshot of the wallpaper, rendering the screenshot useless. I'm pretty sure this occurs only with dual screen setups.

@max0x7ba
Copy link

max0x7ba commented Jul 3, 2012

Same issue here on Fedora 17 and Cinnamon-1.4.1-0.3.fc17. I have two displays attached in clone mode.

@dalcde
Copy link
Contributor

dalcde commented Sep 15, 2012

There has been huge changes to the cinnamon screenshot functionality. Would you mind to test it again with the git version of Cinnamon?

@max0x7ba
Copy link

I'd love to. Do you have instructions somewhere how to build and install it? Is it autoreconf -i && ./configure && make && make install?

@dalcde
Copy link
Contributor

dalcde commented Sep 15, 2012

I guess you ./autogen.sh && make && make install.

I'm on Mint so I'm not sure if it would work properly.

@max0x7ba
Copy link

I managed to build Cinnamon from source (HEAD of master branch) and run it on Fedora 17.

Still, when I take a screenshot while in Cinnamon session the saved screenshot contains the background image from the login screen (which is different from my Cinnamon wallpaper). On the other hand, taking a screenshot from a Gnome Shell session works fine.

This is what I did to build and install Cinnamon from source on Fedora 17.

# 1. Install build dependencies using the version of Cinnamon from Fedora 17 repo.

$ cd ~/Downloads
$ yumdownloader --source cinnamon
$ sudo yum-builddep cinnamon-1.5.2-6.fc17.src.rpm

# 2. Get Cinnamon source.

$ cd ~/src
$ git clone git://github.com/linuxmint/Cinnamon.git
$ cd Cinnamon

# 3. Build and install. Extra define to suppress a build error.

$ ./autogen.sh CPPFLAGS='-Wno-error=deprecated-declarations -march=native'
$ make -j8
$ sudo make install

# 4. Cinnamon can't find gnome-session-check-accelerated. Fix it.

$ sudo mkdir -p /usr/lib/gnome-session/
$ cd /usr/lib/gnome-session/
$ sudo ln -s /usr/libexec/gnome-session-check-accelerated

# 5. Re-login and check that we now run the just built version.

$ ps -u max -fH
max      28370 28353  0 18:43 ?        00:00:00 gnome-session --session cinnamon
max      28489 28370  0 18:43 ?        00:00:00   /usr/bin/ssh-agent /bin/sh -c exec -l /bin/bash -c "gnome-session-cinnamon"
max      28526 28370  0 18:43 ?        00:00:00   /usr/libexec/gnome-settings-daemon
max      28553 28370  8 18:43 ?        00:00:38   /usr/local/bin/cinnamon
max      28724 28553  0 18:43 ?        00:00:03     emacs
max      28735 28724  0 18:43 pts/1    00:00:00       /bin/bash --noediting -i
max      28890 28735  0 18:50 pts/1    00:00:00         ps -u max -fH
max      28560 28370  0 18:43 ?        00:00:00   abrt-applet
max      28561 28370  0 18:43 ?        00:00:00   nm-applet
max      28562 28370  0 18:43 ?        00:00:00   /usr/libexec/tracker-store
max      28563 28370  0 18:43 ?        00:00:00   /usr/libexec/deja-dup/deja-dup-monitor
max      28564 28370  0 18:43 ?        00:00:00   nautilus -n
max      28568 28370  0 18:43 ?        00:00:00   zeitgeist-datahub
max      28574 28370  0 18:43 ?        00:00:01   /usr/libexec/tracker-miner-fs
max      28580 28370  0 18:43 ?        00:00:00   gnome-screensaver
max      28584 28370  0 18:43 ?        00:00:00   /usr/libexec/evolution/3.4/evolution-alarm-notify
[...]

$ cat ~/.xsession-errors
(imsettings-check:28457): GLib-WARNING **: (gerror.c:390):g_error_new_valist: runtime check failed: (domain != 0)

(imsettings-check:28481): GLib-WARNING **: (gerror.c:390):g_error_new_valist: runtime check failed: (domain != 0)
GNOME_KEYRING_CONTROL=/run/user/max/keyring-ZVqQQs
GNOME_KEYRING_CONTROL=/run/user/max/keyring-ZVqQQs
GNOME_KEYRING_CONTROL=/run/user/max/keyring-ZVqQQs
GPG_AGENT_INFO=/run/user/max/keyring-ZVqQQs/gpg:0:1
GNOME_KEYRING_CONTROL=/run/user/max/keyring-ZVqQQs
GPG_AGENT_INFO=/run/user/max/keyring-ZVqQQs/gpg:0:1
SSH_AUTH_SOCK=/run/user/max/keyring-ZVqQQs/ssh
Initializing tracker-store...
Tracker-Message: Setting up monitor for changes to config file:'/home/max/.config/tracker/tracker-store.cfg'
Tracker-Message: Setting up monitor for changes to config file:'/home/max/.config/tracker/tracker-store.cfg'
Starting log:
  File:'/home/max/.local/share/tracker/tracker-store.log'
Initializing tracker-miner-fs...
Tracker-Message: Setting up monitor for changes to config file:'/home/max/.config/tracker/tracker-miner-fs.cfg'
Starting log:
  File:'/home/max/.local/share/tracker/tracker-miner-fs.log'
Failed to play sound: File or data not found
** Message: applet now removed from the notification area

** (nautilus:28564): WARNING **: Can not determine workarea, guessing at layout

@mtwebster
Copy link
Member

I'm not reproducing this currently - dual screens screenshot looks fine, however I have a few changes implemented in my system regarding dual monitors, that might have had the side-effect of fixing this.

Keep an eye on: #1135

@max0x7ba
Copy link

@mtwebster I merged mtwebster/dual-monitor branch into my local copy of Cinnamon/master. That doesn't seem to fix the issue, taking screenshot is still broken on my machine.

I actually have two machines with Fedora 17 running Cinnamon: one with two screens in clone mode and another one with three screens in one big screen mode. Screenshot doesn't work on both of them.

@alagopus
Copy link

Both shutter and gnome-screenshot fail to capture the right image. It seems that it accesses the wrong overlay or buffer. Most prominent when coming back from locked screen, since it is almost all-dark then. When starting shutter, the captured image usually show the last dialog (plugin update) on top, even though it is long gone.

May be dependent on display adapter.

@digingbil
Copy link

Same issue here. ubuntu 12.04, cinnamon 1.6.1, Radeon 5750 HD, AMD Catalyst 12.8, dual monitor. Tested "Screenshot" and "Shutter" and both of them are giving me either wrong screenshot (a window ahich was opened earlier etc..) or an empty black picture (might be because my desktop bg is black and the ss utility is grabbing it).

@max0x7ba
Copy link

max0x7ba commented Nov 6, 2012

Another thread on this issue: http://forums.linuxmint.com/viewtopic.php?f=47&t=103522

@Perturbatio
Copy link

Just to add, I too am experiencing this. It seems to be capturing screens that are no longer displayed. i.e. I tried to take a screenshot of firefox with a particular page open and the screenshot was of a page I had closed several minutes earlier.

I don't know if it's related, but I have also noticed that the display flickers sometimes when loading or closing video player software (amongst other things). and I often see things appear briefly that have been on the display minutes or even hours ago.

If I use shutter to capture screenshots and choose the option to capture a selection, a perfect image of the screen from over 30 minutes ago is displayed in the overlay

Using a Radeon 5870 with the ATI Beta drivers 12.11

@dom96
Copy link

dom96 commented Jan 25, 2013

Same issue here. Radeon 7750 with Catalyst 13.1 on Arch Linux.

@robbrit
Copy link

robbrit commented Jan 29, 2013

Getting the same problem on Mint (Nadia) with Cinnamon v1.6.7. It not only captures the window at a wrong time, but often can't get the right workspace. It's with a Radeon 6670.

@z3r0z3r0
Copy link

z3r0z3r0 commented Feb 3, 2013

http://ati.cchtml.com/show_bug.cgi?id=648#c4 same bug affects gala as well (also mutter-based WM as muffin)
the issue is also discussed here > http://phoronix.com/forums/showthread.php?77250-AMD-Catalyst-13-2-Beta-Driver-For-Linux-Released/page4

@1sherbert1
Copy link

Screenshot success arrived after using Synaptic Package Manager to install amdcccle-updates which installation apparently deleted the older amdcccle. (= AMD Catalyst Control Centre, Linux Edition).

I am using Mint 13 Long Term Support with AMD Radeon 7750 card in a dual screen configuration. Cinnamon is now version 2.0.14+Maya.

All works good, eventually.

@anandrkris
Copy link

@dcelasun - Could you check the occurrence of this issue in the latest version (Cinnamon 2.2) and close the defect accordingly?

@dcelasun
Copy link
Author

dcelasun commented Aug 5, 2014

@anandrkris I've completely forgotten about this issue. Sadly, I no longer use Cinnamon so maybe someone else can verify it.

@mtwebster mtwebster reopened this Aug 5, 2014
@AlbertJP
Copy link
Contributor

AlbertJP commented Nov 9, 2014

@max0x7ba Does this problem still exist with a recent Cinnamon or updated AMD driver? Else I'll close the issue.

@1sherbert1
Copy link

No recent issue, thanks
SH
On 10/11/14 01:08, Albert Pool wrote:


  @max0x7ba Does this problem still
    exist with a recent Cinnamon or updated AMD driver? Else I'll
    close the issue.
  —
    Reply to this email directly or view
      it on GitHub.









-- 

Shane Herbert
Law West Law Office
49 Powderham Street
New Plymouth
+64 6 7599119

@Perturbatio
Copy link

Yep, working for me now too

@AlbertJP
Copy link
Contributor

AlbertJP commented Nov 9, 2014

Ok I'll close it, should anybody still have a problem feel free to open a new issue (when you've made sure that you are not running an outdated AMD driver) as this was an AMD driver problem.

@AlbertJP AlbertJP closed this as completed Nov 9, 2014
@1sherbert1
Copy link

I wish I could discern where responsibility for an issue lies . . 
Thanks Stephen. Appreciated, 
Shane H


On 10/11/14 11:21, Albert Pool wrote:


  Ok I'll close it, should anybody still have a problem feel free
    to open a new issue (when you've made sure that you are not
    running an outdated AMD driver) as this was an AMD driver
    problem.
  —
    Reply to this email directly or view
      it on GitHub.









-- 

Shane Herbert
Law West Law Office
49 Powderham Street
New Plymouth
+64 6 7599119

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests