search for: ksnapshotting

http://bugs.freedesktop.org/show_bug.cgi?id=13750 Summary: Repetitively Taking Screenshots Causes the X Server to Hang Product: xorg Version: 7.2 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nVidia (open) AssignedTo: aplattner

On Fri, 2015-08-14 at 06:39 -0400, Bill Maltby (C4B) wrote: > On Fri, 2015-08-14 at 06:02 -0400, Bill Maltby (C4B) wrote: > > <snip> > Anyway, logging the user out and back in, the panel shows no checking > for updates. Ksnapshot selection for the other user still lagging and > jerky. CPU usage now bouncing 49%-53% with only this message composing > going on and the

On Thu, 2015-08-13 at 23:51 -0700, Gordon Messmer wrote: > On 08/13/2015 02:44 PM, Bill Maltby (C4B) wrote: > > Top shows > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > > 32160 root 20 0 259m 104m 22m R 76.5 1.3 559:07.79 Xorg > > 23391 hardtolo 20 0 6293m 215m 26m S 16.9 2.7 21:49.86 java > > Well, what's process

http://bugs.freedesktop.org/show_bug.cgi?id=25319 Summary: KSnapshot in allocation mode crashes X Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

On Fri, 2015-08-14 at 07:51 -0400, Bill Maltby (C4B) wrote: > <snip> > Ksnapshot region selection still lagging and jerky. > > So it would be easy to think some of this A.M.'s updates had a > beneficial effect in one regard, CPU, usage, but not in the clunky > behavior of region selection with Ksnapshot (could be a mouse driver > issue introduced with the 6.7

On Fri, 2015-08-14 at 06:02 -0400, Bill Maltby (C4B) wrote: > On Thu, 2015-08-13 at 23:51 -0700, Gordon Messmer wrote: > > On 08/13/2015 02:44 PM, Bill Maltby (C4B) wrote: > > > Top shows > > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > > > 32160 root 20 0 259m 104m 22m R 76.5 1.3 559:07.79 Xorg > > > 23391

http://bugs.freedesktop.org/show_bug.cgi?id=24820 Summary: [nv15] Vertical screen corruption in X when KMS is enabled Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo:

something strange is occurring on what is a new setup CentOS 5.2, KDE via NX When I am in Konsole and I press the 'up arrow' key, I get KSnapshot instead of repeating the last line. I looked at kcontrol and there doesn't seem to be any keybinding to cause that and it's irritating and I can't figure out how to shut it off...can someone toss me a bone here? Craig

Guys, Here is a little something to look at in the code. I have the following set: Run command 1: /opt/kde3/bin/ksnapshot <Super>Print Run command 2: /opt/kde3/bin/ksnapshot --current <Alt><Super><Sys_Req> The bug occurs when you choose 'Grab key combination' for <Alt><Super><Sys_Req>. When you enter the keystroke, the keystroke is clearly

Is it just me or does Xorg/Gnome seem slow and clunky to any other desktop users once the 6.7 upgrade is done? $ uname -a Linux CentOS501.homegroannetwork 2.6.32-573.1.1.el6.x86_64 #1 SMP Sat Jul 25 17:05:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/centos-release CentOS release 6.7 (Final) Top shows PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 32160 root

Hi, I'm working on a MEPIS (Debian-based Linux) computer, using the emacs/ESS package to do my R work. I've got some plots that I label interactively using the locate function. With the Windows GUI there is an option to take a snapshot of the graphics output, saving it as an image file. Is there a way to do this with emacs/ESS? Thanks, Tyler

Hi all, I would like to know if these troubles affect also other people, for example, I can no longer connect to Sipe (Lync) network by Pidgin since the Glibc has been updated and now I've just discovered that it was no longer possible to take screenshots with gnome-screenshot, I always receive an error message telling: "Unable to save the screenshot to disk: Value for PNG text

I just branched for 0.8, since Danny told me there was no reason not to. There are still some bugs to work out of course, but since development has been quiet lately, I figure it's time to branch so that we can: 1. Eventually get to the next stable release 2. Allow people to work more freely on master On my personal list of things I want to see working better before a 0.8 release, I have

> Nice to know I'm not the only one that tries to use system facilities > the way they were intended to work and has problems. Maybe if you touch > the bug report so they know I'm not the only one the folks will look and > elevate to RH bug just like they used to do? I was surprised that > "crash" didn't get any attention. While only vaguely related to this

What video card are you using? Xorg driver or proprietary binary thing? The next thing I'd do is boot the last kernel under which you saw "normal" performance. If booting the older kernel doesn't fix the problem, then the problem is probably the X11 server. At that point, I'd start using "yum downgrade" to revert individual components, and reboot until you