Skip to main content

Strange gdesklets problem

Crime scene from Fedora Extras reported on this
Fedora Forum post
.

I investigated the problem on the spec file and notice that "pyobirt >= 2.0.1". I am completely baffled what cause pyborbt to require == 2.0.1. I removed the ">=" for the update. I wonder what caused that glitch.

Here is the report:
$ gdesklets shell

You're running gDesklets for the first time.
gDesklets will start a requirements check now...

Checking requirements:
- sys ... found
- xml.parsers.expat ... found
- xml.sax ... found
- gtk ... found
- ORBit ... found
Version check failed.

ORBit python bindings (pyorbit) version == 2.0.1 are required.

Please make sure that the required software is installed.
Also try to avoid having multiple versions of a library/binding on your system.
gDesklets won't work if you don't have all necessary dependencies installed
on your system.

THE STARTUP WILL BE CANCELLED NOW

Comments

sdfasfdasfd said…
Found the answer myself in the end...

This works fine on FC5, maybe it'll help on other distros:

Open the file /usr/lib/gdesklets/gdesklets in a text editor (I used vi) and find the two lines where the dependency is checked:

( ("ORBit",), lambda m : m.__version__ == (2, 0, 1),
_("ORBit python bindings (pyorbit) version == 2.0.1 are required.")


then edit the entries to read:

( ("ORBit",), lambda m : m.__version__ >= (2, 0, 1),
_("ORBit python bindings (pyorbit) version >= 2.0.1 are required.")

Save the file and away you go

Hope this helps if you're having the same problem.
sdfasfdasfd said…
This comment has been removed by a blog administrator.
mark said…
This page was my first hit with google and it did the job perfectly. Thanks.

Popular posts from this blog

Running Sapphire Radeon RX 560 on Fedora 27 beta (follow up)

Following the previous blog and some investigation, it turned out the kernel package from Mystro256 COPR repository based on agd5f kernel branch (one of AMD developers) resolves the blank screen issue. That could trigger a problem for users having a new AMD graphic hardware so perhaps a warning should be written on the release. Perhaps having one of contributors be part of kernel team bringing these improvement until those patches arrive to the mainline kernel for a better user experience.

Past the issue, the desktop experience with Radeon RX 560 was tremendously improved compared to the retired GTX 460 v2. Gnome on Wayland on Fedora runs smooth showing how far the open source amdgpu driver went through compared to previous years. That was also the opportunity to run a vulkan based smoke test demo on RADV, which is a counterpart of glxgears.

Overall the card is excellent once missing software are installed.

Running Sapphire Pulse Radeon RX 560 4GB on Fedora 27 Beta

I bought a Sapphire PulseRadeon RX 560 4GB to replace the broken Nvidia GTX 460 v2 after a long years of service. It is then my first ever dedicated AMD based video-card for a desktop.

The boot sequence on Fedora 27 hit a problem: a plain blank screen suggesting the card is not yet supported. Looking at Phoronix website revealed one of possible requirement missed: LLVM 5.0 which is currently not available to Fedora repository save a failed built. I filed a bug report to address the issue. Hopefully that will land on time for the official release of Fedora 27.

Vulkan now fully functional on ASUS X550ZE

Running Fedora 28 Design Suite post beta shows a nice surprise: Vulkan with RADV is fully functional on both South Island (Hainan) and Sea Island (Kaveri) cards on ASUS X550ZE laptop. amdgpu driver is needed to enable the feat in combination of boot parameter (cik.amdgpu_support=1 cik.radeon_support=0 si.amdgpu_support=1 si.radeon_support=0)

Some minor issues need be to addressed like occasional glitches. Otherwise the performance is stable enough for dail use.