Summary: | Different gDesklets block each other | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | M Guzman <cloud1086> |
Component: | [OLD] GNOME | Assignee: | Mike Gardiner (RETIRED) <obz> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | High | ||
Version: | 1.4 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
M Guzman
2003-12-16 17:04:26 UTC
Hi there, I'm not sure with regards to the blocks not showing up, it's unlikely to be a portage problem, perhaps I can look at that some more. What I am sure about however, is they do in fact block each other, they both install the same sensors (see Sensors/CPU for example). I really want to move away from the desklet-{disk,network,cpu,memo}info as they arent being maintained individually by the author anymore. Instead, they are released together as a set of displays (psidisplays) and a set of sensors (psisensors). Have a look at qpkg -f /usr/share/gdesklets/Sensors/CPU/__init__.py, which should show the conflict. I'll look into the non-blocking blockingness of them :) with regards to your emerge -u world situation, but they do actually block each other for a reason. Thanks, Mike. closing. |