strace gkrellm2 -d F0 >log 2>&1 gettimeofday({1118092260, 533674}, NULL) = 0 poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN, revents=POLLIN}, {fd=8, events=POLLIN}], 3, 0) = 1 write(3, "F\4\5\0i\0`\0)\0`\0\0\0\0\0\5\0\6\0>\0\7\0g\0`\0i\0`\0"..., 792) = 792 read(3, "V\2\372:\33#\202\1\0\20\0\0\20\0\0\0\0\0\0\20\20\20\20"..., 32) = 32 read(3, gkrellm2: ath.c:184: _gcry_ath_mutex_lock: Assertion `*lock == ((ath_mutex_t) 0)' failed. gkrellm aborted: (?) gkrellm2: ath.c:184: _gcry_ath_mutex_lock: Assertion `*lock == ((ath_mutex_t) 0)' failed. ptrace: umoven: No such process 0xbfffef20, 32) = 32 trace: ptrace(PTRACE_SYSCALL, ...): No such process happens even when no plugin is loaded. Gkrellm crashes about every 10mn since today. Fortunately, I have a keybinding to start it, but am about to put it in a loop :)
I also am experiancing this problem. I originally thought it was due to a bad plugin, but after disabling them all this isn't the case.... ~ $ gkrellm2 -d 9 --- GKrellM 2.2.6 --- diskstats=1 partition_stats=0 sysfs_stats=0 gkrellm2: ath.c:184: _gcry_ath_mutex_lock: Assertion `*lock == ((ath_mutex_t) 0)' failed. gkrellm aborted: (?) Aborted
Yes, this is problem for me too. Came after an emerge -e system && emerge -e system && emerge -e world && emerge -e - world. Only package that is unstable now. Hate to do this emerge sequence again so soon... gkrellm2: ath.c:184: _gcry_ath_mutex_lock: Assertion `*lock == ((ath_mutex_t) 0)' failed. gkrellm aborted: (?) Aborted
i sync'd and upgraded yesterday and the problem fixed itself. don't be a coward, ~x86 everything ;-)
it is right that since about one month, I did not update gkrellm itself, but general updates of other parts of the system somehow fixed the bug. Everyone is ok to mark it invalid ? only mail me if no.
