![]() |
Re: Can apps that disable dyntick be considered bugs?
Quote:
|
Re: Can apps that disable dyntick be considered bugs?
Just to answer that very last question, without going into ramifications at all: Yes, it's possible. There's a Unix signal for that: SIGSTOP. It suspends the application until you send SIGCONT.
|
Re: Can apps that disable dyntick be considered bugs?
Yes, it is possible. You can send SIGSTOP to the process and later resume it with SIGCONT.
This basically freezes the process. Code:
kill -STOP <pid> |
Re: Can apps that disable dyntick be considered bugs?
Quote:
|
Re: Can apps that disable dyntick be considered bugs?
Quote:
string "locked" signal sender=:1.6 -> dest=(null destination) path=/com/nokia/mce/signal; interface=com.nokia.mce.signal; member=tklock_mode_ind string "unlocked" Programs using libosso may already recieve those dbus events, if not, I guess monitoring for them manually would work too. |
Re: Can apps that disable dyntick be considered bugs?
Quote:
|
Re: Can apps that disable dyntick be considered bugs?
Quote:
|
Re: Can apps that disable dyntick be considered bugs?
Quote:
|
Re: Can apps that disable dyntick be considered bugs?
Quote:
Code:
$ browser(Although I just read xterm is one of the culprits...) |
Re: Can apps that disable dyntick be considered bugs?
People usually don't start browser from xterm :-) What you can do is to call something like
Code:
for p in `pidof browser` ; do kill -SIGSTOP $p ; done |
| All times are GMT. The time now is 16:39. |
vBulletin® Version 3.8.8