LibreOffice Manager (lomanager)

[AS]

The program 'gksu' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 841 error_code 3 request_code 2 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Timeline is critical here, the error is telling that the program gksu tried to access a "window" who's ID is actually unknown,
in turn this could be the result of a delayed mapping of the window, which is something that depend from the window manager.

http://www.rahul.net/kenton/40errs.html#Error3

Because of multiple DE install, I suspect JohnW is using a different window manager or a different window manager set up, that trigger the error, while the error itself probably is in gksu. Not easy to track it down.

JohnW,
Just for confirmation you could try something like that, from a non root user account:

Code:

gksu -l synaptic

this should trigger the same error as shown from lomanager...

[Just18]

I wonder why KDESU is not being used .......  a path problem?

This, run from a terminal should show if KDESU is being found or not .....

Code:

if [ -r /usr/lib/kde4/libexec/kdesu ]; then echo "KDESU found"; else echo "KDESU does not found"; fi

I get ....

[user@XPS ~]$ if [ -r /usr/lib/kde4/libexec/kdesu ]; then echo "KDESU found"; else echo "KDESU does not found"; fi
KDESU found

[pinoc]

I wonder why KDESU is not being used .......  a path problem?

This, run from a terminal should show if KDESU is being found or not .....

Code:

if [ -r /usr/lib/kde4/libexec/kdesu ]; then echo "KDESU found"; else echo "KDESU does not found"; fi

I get ....

[user@XPS ~]$ if [ -r /usr/lib/kde4/libexec/kdesu ]; then echo "KDESU found"; else echo "KDESU does not found"; fi
KDESU found

kdesu is found but then replaced by gksu. You can try to exchange the lines 123 and 125 and then run lomanager, it will then use kdesu instead. Maybe that helps.
-p.

[Just18]

I wonder why KDESU is not being used .......  a path problem?

This, run from a terminal should show if KDESU is being found or not .....

Code:

if [ -r /usr/lib/kde4/libexec/kdesu ]; then echo "KDESU found"; else echo "KDESU does not found"; fi

I get ....

[user@XPS ~]$ if [ -r /usr/lib/kde4/libexec/kdesu ]; then echo "KDESU found"; else echo "KDESU does not found"; fi
KDESU found

kdesu is found but then replaced by gksu. You can try to exchange the lines 123 and 125 and then run lomanager, it will then use kdesu instead. Maybe that helps.
-p.

Oops!   Yes see that now ......  even if KDESU is found it will not be used if GKSU is found.

Might be worth considering not checking for GKSU if KDESU is found ......

[pinoc]

can you please exchange the two lines as explained and see if lomanager works for you when using kdesu instead?
thanks,
-p.

[melodie]

Hi,
suggesting an idea, maybe for some time in the future ? ktsuss is desktop agnostic, and the latest available stable version (ktsuss-2) has been out for several weeks now... http://code.google.com/p/ktsuss

[JohnW_57]

JohnW,
Just for confirmation you could try something like that, from a non root user account:
Code:

gksu -l synaptic

this should trigger the same error as shown from lomanager...

It gives indeed the same error.

JohnW

[JohnW_57]

Solved!

The gksu problem happens when the QTCurve GTK2 theme is used!
Did change to an another GTK2 theme (for GTK2 apps) and that solved the issue.

So don't use QTCurve GTK2 theme for your GTK2 apps. (a bit buggy).

Gonna testing other GTK2 themes so get sure. 

[wimwillemsen@localhost ~]$ gksu -l synaptic  launches gksu and synaptic without the X Window System  error and lomamanager does working.


JohnW

[pinoc]

and how about kdesu synaptic in your KDE session ?

[JohnW_57]

[wimwillemsen@localhost ~]$ kdesu synaptic
kdesu(19283)/kdesu (kdelibs) KDESu::PtyProcess::exec: [ /root/rpmbuild/BUILD/kdelibs-4.6.5/kdesu/process.cpp : 293 ]  Running "/usr/bin/su"
kdesu(19283)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: [ /root/rpmbuild/BUILD/kdelibs-4.6.5/kdesu/su.cpp : 259 ]  Read line "Password: "

It launches the password manager to use synaptic (had no issue with kdesu).

The gksu issue was caused by the Qtcurve GTK2 theme and crashed lomanager (in the KDE session).
Changing another GTK2 theme solved it.

The kdesu question was from Just18. http://www.pclinuxos.com/forum/index.php/topic,59009.msg866661.html#msg866661

JohnW

[pinoc]

Hi JohnW,

The gksu problem happens when the QTCurve GTK2 theme is used!

now that we know what caused the problem, what I wanted to understand is this:

when using the QTCurve GTK2 theme in a KDE session:
gksu -l synaptic will crash but will kdesu synaptic work with the QTCurve GTK2 theme enabled? If so, then I can simply default to using kdesu when a KDE-session is detected, so lomanager will work independent of the "QTCurve GTK2 bug".

[JohnW_57]

kdesu synaptic had no problem with the qtcurve-gtk2 theme:

[wimwillemsen@localhost ~]$ kdesu synaptic
kdesu(10571)/kdesu (kdelibs) KDESu::PtyProcess::exec: [ /root/rpmbuild/BUILD/kdelibs-4.6.5/kdesu/process.cpp : 293 ]  Running "/usr/bin/su"
kdesu(10571)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: [ /root/rpmbuild/BUILD/kdelibs-4.6.5/kdesu/su.cpp : 259 ]  Read line "Password: "

(with the qtcurve-gtk2 theme)

JohnW

[pinoc]

kdesu synaptic had no problem with the qtcurve-gtk2 theme:

[wimwillemsen@localhost ~]$ kdesu synaptic
kdesu(10571)/kdesu (kdelibs) KDESu::PtyProcess::exec: [ /root/rpmbuild/BUILD/kdelibs-4.6.5/kdesu/process.cpp : 293 ]  Running "/usr/bin/su"
kdesu(10571)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: [ /root/rpmbuild/BUILD/kdelibs-4.6.5/kdesu/su.cpp : 259 ]  Read line "Password: "

(with the qtcurve-gtk2 theme)

JohnW

ok, thanks for testing. That is what I expected and just confirms that KDE is the best DE 
-p.

[menotu]

That is what I expected and just confirms that KDE is the best DE

+1   

[Archie]

That is what I expected and just confirms that KDE is the best DE

+1   

We're opening another heated debate but what the heck ...  +1