Mailinglist Archive: opensuse-factory (454 mails)

< Previous Next >
[opensuse-factory] Bug 1073996: xdpyinfo is using 100% of one cpu
* Patrick Shanahan <paka@xxxxxxxxxxxx> [12-22-17 08:10]:
* Patrick Shanahan <paka@xxxxxxxxxxxx> [12-21-17 15:24]:
* Jan Engelhardt <jengelh@xxxxxxx> [12-21-17 14:45]:

On Thursday 2017-12-21 15:46, Patrick Shanahan wrote:

I have a python backup instance runs at 3am every day, backintime:
def check_x_server():
return 0 == os.system( 'xdpyinfo >/dev/null 2>&1' )

for some reason the xdpyinfo instance persists.

So, does your script have DISPLAY set when it shouldn't?

backintime in ~/.local/share/backintime/cron_env shows:

so, I guess that would be "yes", but I don't know that it shouldn't ???
or, if in fact that does set $DISPLAY.

suggestions welcome, I know *nearly* nothing :)

fvogt suggested on irc that I run "gdb -p $(pidof xdpyinfo)" when the
xdpyinfo instance is present. output at:
+ thread apply all bt

also strace -p $(pidof xdpyinfo)

Bug 1073996
(paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri openSUSE Community Member facebook/ptilopteri
Registered Linux User #207535 @
Photos: paka @ IRCnet freenode
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >