Summary: | gkrellm2: ath.c:184: _gcry_ath_mutex_lock: Assertion `*lock == ((ath_mutex_t) 0)' failed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | DEMAINE Benoît-Pierre, aka DoubleHP <dhp_gentoo> |
Component: | Current packages | Assignee: | Gentoo Dockapp Team <desktop-dock> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2005.0 | ||
Hardware: | All | ||
OS: | Other | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
DEMAINE Benoît-Pierre, aka DoubleHP
2005-06-06 14:45:15 UTC
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. |