Running conky with the -d (daemonize) option causes conky to hang without displaying anything, after which it must be killed with SIGKILL. The console output is normal: Conky: forked to background, pid is 10661 Conky: desktop window (106) is root window Conky: drawing to desktop window Conky: drawing to double buffer Running with own_window set to 'yes' causes a tiny, empty window to appear. Reproducible: Always
What happens when you run Conky without forking it? If it crashes, can you provide a backtrace?
Sorry, I should have tested it more thoroughly before - it only hangs when using the -d option and if the $acpitemp function is used. It works fine without the -d option. I tried attaching gdb to the process after it froze, and this is the backtrace: #0 0x00007f9ab56e0a7a in ?? () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.3/libgomp.so.1 #1 0x00007f9ab56dfcab in ?? () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.3/libgomp.so.1 #2 0x000000000042047a in update_stat () #3 0x0000000000407160 in update_stuff () #4 0x000000000041a075 in update_text () #5 0x000000000041b695 in main ()
Try disabling the openmp use flag for Conky.
(In reply to comment #3) > Try disabling the openmp use flag for Conky. That fixes it.
Fixed in >=conky-1.7.1.1-r2 by disabling the openmp flag (Upstream rcommendation).