| Summary: | HELP! The Ksnapshot stays doing thousands of snapshots without stop when, unintentionally, I make a combination of keys - that I still don't found out - and do not wants stop anymore! Do I have to reboot or halt the machine via Console (ctrl + alt + F1), | ||
|---|---|---|---|
| Product: | [Unmaintained] ksnapshot | Reporter: | Rosalvo <ropesogm> |
| Component: | general | Assignee: | Richard Moore <rich> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | andresbajotierra, metamorfozis, troygnichols |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
snapshot of ksnapshot TOTALLY FLIPPING OUT
.xsession-errors during ksnapshot flip-out |
||
|
Description
Rosalvo
2009-04-08 20:35:24 UTC
Created attachment 33308 [details]
snapshot of ksnapshot TOTALLY FLIPPING OUT
Attaching screenshot of the problem. Notice hundreds of instances of ksnapshot running at the bottom of the screen. This continued until the OS was essentially "locked up" and had to do a hard restart.
I am seeing the exact same problem described above. Pressing PrintScreen several times in rapid succession causes the "infinite looping" behavior. Before the system completely died I was able to actually get one of the ksnapshot instances to (eventually) take a snaphot. Created attachment 33691 [details]
.xsession-errors during ksnapshot flip-out
Here's a copy of my .xsession-errors during a ksnapshot flip-out. This line looks like it might be important:
krunner(11523): Failed to lock file "/var/tmp/kdecache-dkesh/kpc/kde-icon-cache.lock" , last result = 1
Maybe this is a common problem. Are you guys have ever the problem that one of your keys get's repeated infinitely? (not just printscreen). I have binded win + z buttons to amarok's next track global key. And i have often get this loop happens, exactly it starts to zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz to the current program which has the focus. I think it is occurs when the system load is a bit high (a peak is enough, like the not so lighty amarok's track change etc). So if the same occurs with printscreent, that can be hurt:) (anyways i'm on an eee 1000h and not yet get this problem, but zzzzzzz-ing is everyday problem) To solve this i think it's enough to add a setting option for maximum occurences, or hardcode it to 10. Merging with bug 166190. Thanks *** This bug has been marked as a duplicate of bug 166190 *** |