Solved

Clear looks Unable to locate theme engine in module_path

Posted on 2011-02-25
6
2,299 Views
Last Modified: 2012-06-27
./hype

(hype:2387): GLib-WARNING **: getpwuid_r(): failed due to unknown user id (1005)

(hype:2387): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",

(hype:2387): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",

(hype:2387): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",

(hype:2387): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",

(hype:2387): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",

(hype:2387): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",

(hype:2387): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",

(hype:2387): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",

(hype:2387): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",

(hype:2387): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",

(hype:2387): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",

(hype:2387): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",

(hype:2387): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",

(hype:2387): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",

(hype:2387): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",

(hype:2387): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",

(hype:2387): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",
Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory
Xlib:  extension "GLX" missing on display "vfx-lap-1:0.0".
Xlib:  extension "GLX" missing on display "vfx-lap-1:0.0".
*** glibc detected *** ./hype: free(): invalid pointer: 0x09f4bed0 ***
======= Backtrace: =========
/lib/libc.so.6[0x9a1b41]
/usr/lib/nvidia/tls/libnvidia-tls.so.260.19.29(+0xa20)[0xf742fa20]
./hype[0x83ce2fc]
./hype(_ZN8wxButton10SetDefaultEv+0x53)[0x83ce6fb]
./hype(_ZN17HypeMessageDialogC1EP8wxWindowRK8wxStringS4_S4_S4_S4_lb+0x66c)[0x81c6ee0]
./hype(_ZN9MainFrame11checkOpenGLEv+0x365)[0x81b41f9]
./hype(_ZN9MainFrameC1EP8wxWindowiRK8wxStringRK7wxPointRK6wxSizel+0x87)[0x81aac83]
./hype(_ZN7HypeApp6OnInitEv+0x220)[0x8195d60]
./hype(_ZN12wxAppConsole10CallOnInitEv+0xf)[0x8197c83]
./hype(_Z7wxEntryRiPPc+0x3e)[0x837cb02]
./hype(main+0x18)[0x8195a6c]
/lib/libc.so.6(__libc_start_main+0xe6)[0x949cc6]
./hype(gtk_widget_grab_focus+0x31)[0x8195961]
======= Memory map: ========
00101000-00235000 r-xp 00000000 08:01 1621766                            /usr/lib/libX11.so.6.3.0
00235000-00239000 rwxp 00133000 08:01 1621766                            /usr/lib/libX11.so.6.3.0
0023b000-00264000 r-xp 00000000 08:01 1621788                            /usr/lib/libpangoft2-1.0.so.0.2800.0
00264000-00265000 rwxp 00028000 08:01 1621788                            /usr/lib/libpangoft2-1.0.so.0.2800.0
00267000-00284000 r-xp 00000000 08:01 1621722                            /usr/lib/libxcb.so.1.1.0
00284000-00285000 rwxp 0001c000 08:01 1621722                            /usr/lib/libxcb.so.1.1.0
00540000-0055e000 r-xp 00000000 08:01 1622681                            /usr/lib/libgdk_pixbuf-2.0.so.0.2000.1
0055e000-0055f000 rwxp 0001d000 08:01 1622681                            /usr/lib/libgdk_pixbuf-2.0.so.0.2000.1
00561000-00588000 r-xp 00000000 08:01 1594151                            /usr/lib/libpng12.so.0.44.0
00588000-00589000 rwxp 00027000 08:01 1594151                            /usr/lib/libpng12.so.0.44.0
0058b000-00643000 r-xp 00000000 08:01 2101451                            /lib/libgio-2.0.so.0.2400.1
00643000-00645000 rwxp 000b8000 08:01 2101451                            /lib/libgio-2.0.so.0.2400.1
00647000-00659000 r-xp 00000000 08:01 2113707                            /lib/libz.so.1.2.3
00659000-0065a000 rwxp 00011000 08:01 2113707                            /lib/libz.so.1.2.3
0065c000-00671000 r-xp 00000000 08:01 2112292                            /lib/libresolv-2.12.2.so
00671000-00672000 r-xp 00014000 08:01 2112292                            /lib/libresolv-2.12.2.so
00672000-00673000 rwxp 00015000 08:01 2112292                            /lib/libresolv-2.12.2.so
00673000-00675000 rwxp 00000000 00:00 0
00677000-00694000 r-xp 00000000 08:01 2098877                            /lib/libselinux.so.1
00694000-00695000 r-xp 0001c000 08:01 2098877                            /lib/libselinux.so.1
00695000-00696000 rwxp 0001d000 08:01 2098877                            /lib/libselinux.so.1
00698000-00716000 r-xp 00000000 08:01 1622720                            /usr/lib/libcairo.so.2.10800.10
00716000-00718000 rwxp 0007e000 08:01 1622720                            /usr/lib/libcairo.so.2.10800.10
0071a000-0071c000 r-xp 00000000 08:01 1621780                            /usr/lib/libXcomposite.so.1.0.0
0071c000-0071d000 rwxp 00001000 08:01 1621780                            /usr/lib/libXcomposite.so.1.0.0
0071f000-0072d000 r-xp 00000000 08:01 1621786                            /usr/lib/libXi.so.6.1.0
0072d000-0072e000 rwxp 0000d000 08:01 1621786                            /usr/lib/libXi.so.6.1.0
00730000-007e3000 r-xp 00000000 08:01 1622488                            /usr/lib/libgdk-x11-2.0.so.0.2000.1
007e3000-007e6000 rwxp 000b2000 08:01 1622488                            /usr/lib/libgdk-x11-2.0.so.0.2000.1
007e8000-007ea000 r-xp 00000000 08:01 1621772                            /usr/lib/libXinerama.so.1.0.0
007ea000-007eb000 rwxp 00001000 08:01 1621772                            /usr/lib/libXinerama.so.1.0.0
007ed000-007f1000 r-xp 00000000 08:01 1622683                            /usr/lib/libXfixes.so.3.1.0
007f1000-007f2000 rwxp 00003000 08:01 1622683                            /usr/lib/libXfixes.so.3.1.0
007f4000-0085a000 r-xp 00000000 08:01 1580368                            /usr/lib/libpixman-1.so.0.18.0
0085a000-0085d000 rwxp 00066000 08:01 1580368                            /usr/lib/libpixman-1.so.0.18.0
0085f000-0086f000 r-xp 00000000 08:01 1622781                            /usr/lib/libXext.so.6.4.0
0086f000-00870000 rwxp 00010000 08:01 1622781                            /usr/lib/libXext.so.6.4.0
00872000-00879000 r-xp 00000000 08:01 1621782                            /usr/lib/libXrandr.so.2.2.0
00879000-0087a000 rwxp 00006000 08:01 1621782                            /usr/lib/libXrandr.so.2.2.0
0087c000-00887000 r-xp 00000000 08:01 1578712                            /usr/lib/libpangocairo-1.0.so.0.2800.0
00887000-00888000 rwxp 0000a000 08:01 1578712                            /usr/lib/libpangocairo-1.0.so.0.2800.0
0088a000-008a7000 r-xp 00000000 08:01 1622414                            /usr/lib/libatk-1.0.so.0.3009.1
008a7000-008a9000 rwxp 0001d000 08:01 1622414                            /usr/lib/libatk-1.0.so.0.3009.1
008ab000-008ad000 r-xp 00000000 08:01 1612501                            /usr/lib/libXdamage.so.1.1.0
008ad000-008ae000 rwxp 00001000 08:01 1612501                            /usr/lib/libXdamage.so.1.1.0
008b0000-008b9000 r-xp 00000000 08:01 1621776                            /usr/lib/libXcursor.so.1.0.2
008b9000-008ba000 rwxp 00008000 08:01 1621776                            /usr/lib/libXcursor.so.1.0.2
00911000-00920000 r-xp 00000000 08:01 2097233                            /lib/ld-2.12.2.so
00920000-00921000 -wxp 0000f000 08:01 2097233                            /lib/ld-2.12.2.so
00921000-0092f000 r-xp 00010000 08:01 2097233                            /lib/ld-2.12.2.so
0092f000-00930000 r-xp 0001d000 08:01 2097233                            /lib/ld-2.12.2.so
00930000-00931000 rwxp 0001e000 08:01 2097233                            /lib/ld-2.12.2.so
00933000-00ab7000 r-xp 00000000 08:01 2115011                            /lib/libc-2.12.2.so
00ab7000-00ab8000 ---p 00184000 08:01 2115011                            /lib/libc-2.12.2.so
00ab8000-00aba000 r-xp 00184000 08:01 2115011                            /lib/libc-2.12.2.so
00aba000-00abb000 rwxp 00186000 08:01 2115011                            /lib/libc-2.12.2.so
00abb000-00abe000 rwxp 00000000 00:00 0
00ac0000-00ac3000 r-xp 00000000 08:01 2101462                            /lib/libdl-2.12.2.so
00ac3000-00ac4000 r-xp 00002000 08:01 2101462                            /lib/libdl-2.12.2.so
00ac4000-00ac5000 rwxp 00003000 08:01 2101462                            /lib/libdl-2.12.2.so
00ac7000-00ade000 r-xp 00000000 08:01 2115012                            /lib/libpthread-2.12.2.so
00ade000-00adf000 r-xp 00016000 08:01 2115012                            /lib/libpthread-2.12.2.soAborted (core dumped)
0
Comment
Question by:aashee
  • 4
  • 2
6 Comments
 
LVL 35

Expert Comment

by:torimar
ID: 34979246
The program you are trying to install (Hype) requires hardware accelerated graphics:
http://www.visualappliance.com/products/hype/requirements.php

The program (Hype) also has not been updated, as it seems, since 2007, which means that it may not be compatible with Fedora 13, and that it certainly does not take into consideration what has been done with 3D acceleration in the last couple of versions of Fedora.

You will have to try, I guess, to install the proprietary drivers/kernel modules for your graphics chip, and then hope it will work after all.

If you have an Nvidia gfx card, here's the guide to follow:
http://forums.fedoraforum.org/showthread.php?t=204752

If ATI, then follow this guide:
http://forums.fedoraforum.org/showthread.php?t=155503
0
 

Author Comment

by:aashee
ID: 34980021
hi ,
maybe my drivers are already up to date ? how can i check that ?

what command to type ?
0
 
LVL 35

Expert Comment

by:torimar
ID: 34980433
This is not about 'updating' drivers. It is all about installing 3D-capable drivers that are not installed together with Fedora.
So unless you have gone through some manual installation as described in the two links I gave above, or like described in one of the following links:
http://www.linuxquestions.org/questions/fedora-35/fedora-12-nouveau-nvidia-driver-solution-771248/
http://www.fedorafaq.org/#radeon
http://www.fedorafaq.org/#nvidia

... you cannot yet have them. On top of that, this error line:
Xlib:  extension "GLX" missing on display "vfx-lap-1:0.0".

Open in new window

points to the fact that 3D support is not available.

To make things worse, starting with Fedora 11, an open-source driver called "Nouveau" (http://en.wikipedia.org/wiki/Nouveau_(graphics) ) has been added to Fedora which provides "experimental" 3D support.  It will most likely not work together with any application that requires genuine 3D support, and certainly not with a programme like Hype which was produced long before Nouveau got conceived.
Which means that this driver, if active, also needs to be disabled and blacklisted.

All this, the installation and the blacklisting, is described in the two links I gave in my first post. Make sure to follow those, not any other, because they are the 'official' install guides tested in a multitude of cases.
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
LVL 35

Expert Comment

by:torimar
ID: 34980462
ps:
The installation guide for Fedora 13 is always the second post in those two linked threads, like this one for Nvidia drivers: http://forums.fedoraforum.org/showpost.php?p=1114782&postcount=2
0
 

Author Comment

by:aashee
ID: 34981224
sorry ,maybe i am asking stupid question.
can i not check whether these are already there. maybe i don't need to do these changes.
we have very good graphics cards here and 3D softwares are installed and run in our environment. so i'm sure it must be active.

before screwing anything, how can i check whether these changes are already implemented ?
how can i check 3D compatible drivers are installed or not?

please update ?

0
 
LVL 35

Accepted Solution

by:
torimar earned 500 total points
ID: 34982202
On earlier versions of Fedora this could quickly be checked by running the commands:
$ glxinfo (see if it say 'Direct rendering: Yes')

and/or:
$ glxgears
(this will start a small 3D benchmarking application)

But as I tried to explain: nowadays there is also the Nouveau driver, and those commands above, if running fine, could also mean that Nouveau is installed and working, not the generic drivers for the gfx chip.

To check if those generic drivers are installed, use, for instance, the following commands
$ rpm -qa | grep nvidia  
(this is for Nvidia graphics)

or:
$ rpm -qa | grep catalyst
(this is for ATI graphics)

then see if it lists a "kmod-nvidia" or a "kmod-catalyst" module.


I understand your concern not to 'screw' anything, and if everything else is running fine,  I suggest you make it your main concern. My suggestions regarding the Gfx drivers are hypothetical - there is certainly a problem with the GLX module, but there is no guarantee that installing those drivers will actually make the program run, even if it definitely and undoubtedly requires hardware 3D support.

The program (Hype) is simply too old. Every year, two new versions of Fedora are released. If Hype was last updated in 2007, then it will still be reflecting Fedora 5 or 6. In case you really wish to know if it is worth the effort, I should think you had best contact the developers on www.visualappliance.com and ask whether their application will actually run on Fedora 13.
0

Featured Post

Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

rdate is a Linux command and the network time protocol for immediate date and time setup from another machine. The clocks are synchronized by entering rdate with the -s switch (command without switch just checks the time but does not set anything). …
I. Introduction There's an interesting discussion going on now in an Experts Exchange Group — Attachments with no extension (http://www.experts-exchange.com/discussions/210281/Attachments-with-no-extension.html). This reminded me of questions tha…
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.

867 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now