Reginald Beardsley via openindiana-discuss writes:
> I do not find either of those.
>
> What is the full path for the files you cited?
[...]
> Can you check that library/desktop/libgksu and desktop/gksu are installed?
>
> Those are the most problematic candidates to be missing.
>
> -Till
Usually you see enough of the first part of the string. However, I also looked
for the open(2) of libgksu.so and neither caja nor mate-session nor any of
their children open it.
Reg
On Monday, June 21, 2021, 05:12:03 PM CDT, Udo Grabowski (IMK)
wrote:
On 21.06.21 22:17, Reginald
On 21.06.21 22:17, Reginald Beardsley via openindiana-discuss wrote:
FYI I wrapped both caja and mate-session with "truss -f -o". Neither output contains the
"Initializing gksu extensions" string. ...
Note that you usually don't see full strings in truss output,
those are printed usually as
I do not find either of those.
What is the full path for the files you cited?
/usr/bin/gksu and /usr/bin/gksudo are present. It turns out that both of those
are looking for libgksu2.so.0 which does not exist in my installation of
2021.04.30.
I did not get as many link libraries listed
Hi Everyone
Can you check that library/desktop/libgksu and desktop/gksu are installed?
Those are the most problematic candidates to be missing.
-Till
On 21.06.21 17:34, Gary Mills wrote:
On Mon, Jun 21, 2021 at 08:17:57PM +, Reginald Beardsley via
openindiana-discuss wrote:
At this
On Mon, Jun 21, 2021 at 08:17:57PM +, Reginald Beardsley via
openindiana-discuss wrote:
> At this point, the only means I can think of to find the source of
> the message is to run ldd(1) across all the executables and grep out
> anything that links libcaja-gksu.so.
dump -Lv ... | grep
FYI I wrapped both caja and mate-session with "truss -f -o". Neither output
contains the "Initializing gksu extensions" string. I have created OI issue
#13895 to provide a place for a subset of the truss output between consecutive
excve()s of caja. Total output before I could kill the
The problems I was having appear to have been caused by caja restarting. The
system stayed up with the mouse functional overnight. Before I disabled caja it
would lock up the cursor in an hour or less.
I'll wrap caja with a script that runs "truss -f -o" to find out why it is
failing and do
