[SOLVED] 'libdlfaker.so' from LD_PRELOAD cannot be preloaded

pan64 · 10-07-2017, 09:21 AM

Sorry, I don't understand that. But anyway you can force set LD_PRELOAD if you wish and also you can check the config file of optirun.

TimewarpUK · 10-08-2017, 12:49 PM

Quote:

Originally Posted by pan64

Sorry, I don't understand that. But anyway you can force set LD_PRELOAD if you wish and also you can check the config file of optirun.

That's what I want to do. Can't seem to find any documentation on it though. Had a look at man too. Am I missing something?

TimewarpUK · 10-09-2017, 03:05 AM

This is my bumblebee.conf:

Code:

# Configuration file for Bumblebee. Values should **not** be put between quotes

## Server options. Any change made in this section will need a server restart
# to take effect.
[bumblebeed]
# The secondary Xorg server DISPLAY number
VirtualDisplay=:8
# Should the unused Xorg server be kept running? Set this to true if waiting
# for X to be ready is too long and don't need power management at all.
KeepUnusedXServer=false
# The name of the Bumbleblee server group name (GID name)
ServerGroup=bumblebee
# Card power state at exit. Set to false if the card shoud be ON when Bumblebee
# server exits.
TurnCardOffAtExit=false
# The default behavior of '-f' option on optirun. If set to "true", '-f' will
# be ignored.
NoEcoModeOverride=false
# The Driver used by Bumblebee server. If this value is not set (or empty),
# auto-detection is performed. The available drivers are nvidia and nouveau
# (See also the driver-specific sections below)
Driver=nvidia

## Client options. Will take effect on the next optirun executed.
[optirun]
# The method used for VirtualGL to transport frames between X servers.
# Possible values are proxy, jpeg, rgb, xv and yuv.
VGLTransport=proxy
# Should the program run under optirun even if Bumblebee server or nvidia card
# is not available?
AllowFallbackToIGC=false


# Driver-specific settings are grouped under [driver-NAME]. The sections are
# parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
# detection resolves to NAME).
# PMMethod: method to use for saving power by disabling the nvidia card, valid
# values are: auto - automatically detect which PM method to use
#         bbswitch - new in BB 3, recommended if available
#       switcheroo - vga_switcheroo method
#             none - disable PM completely
# https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods

## Section with nvidia driver specific options, only parsed if Driver=nvidia
[driver-nvidia]
# Module name to load, defaults to Driver if empty or unset
KernelDriver=nvidia
Module=nvidia
PMMethod=auto
# colon-separated path to the nvidia libraries
LibraryPath=/usr/lib64/nvidia-bumblebee:/usr/lib/nvidia-bumblebee:/usr/lib64:/usr/lib
# comma-separated path of the directory containing nvidia_drv.so and the
# default Xorg modules path
XorgModulePath=/usr/lib64/nvidia-bumblebee/xorg,/usr/lib64/xorg/modules
XorgConfFile=/etc/bumblebee/xorg.conf.nvidia

## Section with nouveau driver specific options, only parsed if Driver=nouveau
[driver-nouveau]
KernelDriver=nouveau
PMMethod=auto
XorgConfFile=/etc/bumblebee/xorg.conf.nouveau

I can't see where you can override LD_PRELOAD or set the 'libdlfaker.so' library path (except for NVIDIA libraries).

ondoho · 10-10-2017, 01:24 AM

"checking the config file" always consists of 2 parts:

1. reading the documentation for where the config files are stored, what their options and defaults are (maybe 'man bumblebee.conf'?)
2. opening the file(s) and checking them

TimewarpUK · 10-10-2017, 03:38 AM

Quote:

Originally Posted by ondoho

"checking the config file" always consists of 2 parts:

1. reading the documentation for where the config files are stored, what their options and defaults are (maybe 'man bumblebee.conf'?)
2. opening the file(s) and checking them

Already done ^.

It was man optirun but no info found.

The closest I found was

Code:

-l, --ldpath PATH
              libraries like libGL.so are searched in PATH (useful for the nvidia driver). By default, PATH is queried from the [sic]

That's all it says. I did try this from command line to no avail and there is a similar one in optirun.conf:

Code:

LibraryPath=

So I'll try that the next chance I get.

TimewarpUK · 10-21-2017, 02:56 PM

Colour me stumped.

I seem to be the only one with this problem on the internet

Not the first time...

Not found a way to unset it apart from .bashrc and had to write a bash script for Wireshark so it would unset the var before launching itself when called from the GUI. Don't like the solution but it'll have to do.

ondoho · 10-22-2017, 01:01 PM

Quote:

Originally Posted by TimewarpUK

I seem to be the only one with this problem on the internet

Not the first time...

if you experience that a lot, it means that
- either you have some really unique circumstances (which i don't see any indication of)
- or you need to work on your search skills

no disrespect.

TimewarpUK · 10-22-2017, 02:00 PM

Quote:

Originally Posted by ondoho

if you experience that a lot, it means that
- either you have some really unique circumstances (which i don't see any indication of)
- or you need to work on your search skills

no disrespect.

Yeh could be either.

When I've had problems I couldn't Google before it had been to something setup strange from the start that I much later discovered.

However, if you do suspect the latter and my Google Fu is weak, feel free to step in and help.

TimewarpUK · 10-22-2017, 04:27 PM

OK,

I've now managed to solve this by patching vglrun:

Code:

$ diff /usr/bin/vglrun~ /usr/bin/vglrun
235c235
< 	LD_PRELOAD=librrfaker.so
---
> 	LD_PRELOAD=/usr/lib64/VirtualGL/librrfaker.so
237c237
< 	LD_PRELOAD=librrfaker.so:$LD_PRELOAD
---
> 	LD_PRELOAD=/usr/lib64/VirtualGL/librrfaker.so:$LD_PRELOAD
240c240
< 	LD_PRELOAD=libdlfaker.so:$LD_PRELOAD
---
> 	LD_PRELOAD=/usr/lib64/VirtualGL/libdlfaker.so:$LD_PRELOAD
243c243
< 	LD_PRELOAD=libgefaker.so:$LD_PRELOAD
---
> 	LD_PRELOAD=/usr/lib64/VirtualGL/libgefaker.so:$LD_PRELOAD

The page at https://wiki.archlinux.org/index.php/VirtualGL helped but I'm still at a lost why I needed to patch a system file.

pan64 · 10-23-2017, 03:31 AM

that is great.
I think someone assumed something (an app) will be executed in /usr/lib64/VirtualGL and therefore librrfaker.so (without path) is sufficient.
Someone else invoked this app from another directory....

TimewarpUK · 10-23-2017, 04:03 AM

Quote:

Originally Posted by pan64

that is great.
I think someone assumed something (an app) will be executed in /usr/lib64/VirtualGL and therefore librrfaker.so (without path) is sufficient.
Someone else invoked this app from another directory....

Note sure why $LD_LIBRARY_PATH or LD cache isn't observed though, which should resolve it without path being specified.

pan64 · 10-23-2017, 04:12 AM

This is not really trivial, see for example here:
http://man7.org/linux/man-pages/man8/ld.so.8.html