xrandr broken dependency in >=13.37

FeyFre · 03-05-2013, 06:25 AM

Hi

A few minutes ago I decided to inspect my system(13.37) and found broken dependency in xranrd package.
Except of xranrd binary executable itself it contains another executable xkeystone. I really do not know its purpose and functions, but since it still there I can make conclusion it required by smb. But it seems to be written on Nickle programming language, whose interpreter is absent on system. Double checked install disk, and ftp sources - no such package found in both 13.37, 14.0 and -current trees. On SlackBuild.org it absent also.
So I downloaded latest sources, quickly crafted SlackBuild, built and installed it. Now it tries to run, but it emits a ton of nickle related errors.
Saw similar bug-reports for other distros, but some of them was closed with WON'T FIX resolution, so I not digged in.

Since malfunction of xkeystone does not hurts me personally, but can do it to smb. other, it is my ought to report it(probably I first who noticed it here) to PV and/or community to be sure such inconsistency(AFAIK, S. known to be pretty polished out of box) will be solved in future.

ponce · 03-05-2013, 06:33 AM

In my humble opinion, this is not a Slackware-specific problem: if upstream distributes non-working stuff (this is what I seem to understand from the various bug reports), basically they should remove/fix it theirself.

Package maintainers cannot do also upstream's work, I think usually nobody got time for that, especially if you maintain a whole distribution alone (like Pat is doing).

allend · 03-05-2013, 07:31 AM

Interesting timing. A Debian developer is also querying xkeystone. http://www.mail-archive.com/debian-b...sg1104445.html

fskmh · 03-05-2013, 12:17 PM

Ditto for Arch:

Quote:

Description:

Trying to run the new program xkeystone, which made xorg-xrandr depend on nickle results in fatal execution errors.

I decided to give it a whirl and made a SlackBuild for nickle (which I cannot attach).

On trying to run xkeystone I got the same errors as the Arch guys.

Code:

Cannot autoload from file "nichrome.5c", giving up.
Cannot autoload from file "nichrome-box.5c", giving up.
Cannot autoload from file "nichrome-label.5c", giving up.
Cannot autoload from file "nichrome-button.5c", giving up.
/usr/bin/xkeystone:30: non-existant namespace Nichrome

I think Nichrome is another FFI binding written by the same dev that wrote xkeystone and cairo-5c, but I can't find it.

The bottom line is that the Arch and Debian guys seem inclined to drop xkeystone from xrandr.