Mergeant - Problem launching

Wondering if anyone else is using mergeant from within OpenSUSE 11.3/KDE4.4.4.

When I actually try to launch from CLI, this is the error that’s thrown which leads me to believe there is more of an issue than “just” trying to launch a GUI app from CLI. For one thing, running “locate” I cannot find the referenced document type definition (dtd) files anywhere on my machine.


I/O warning : failed to load external entity "/usr/share/libgda-3.0/dtd/libgda-dict.dtd"
** Message: Could not parse '/usr/share/libgda-3.0/dtd/libgda-dict.dtd': XML dictionaries validation will not be performed (some weird errors may occur)
I/O warning : failed to load external entity "/usr/share/libgda-3.0/dtd/libgda-array.dtd"
** Message: Could not parse '/usr/share/libgda-3.0/dtd/libgda-array.dtd': XML data import validation will not be performed (some weird errors may occur)
I/O warning : failed to load external entity "/usr/share/libgda-3.0/dtd/libgda-paramlist.dtd"
** Message: Could not parse '/usr/share/libgda-3.0/dtd/libgda-paramlist.dtd': XML data import validation will not be performed (some weird errors may occur)
I/O warning : failed to load external entity "/usr/share/libgda-3.0/dtd/libgda-server-operation.dtd"
** Message: Could not parse '/usr/share/libgda-3.0/dtd/libgda-server-operation.dtd': Validation for XML files for server operations will not be performed (some weird errors may occur)

(mergeant:14649): Gtk-CRITICAL **: gtk_list_store_get_value: assertion `VALID_ITER (iter, list_store)' failed

(mergeant:14649): GLib-GObject-WARNING **: gtype.c:4177: type id `0' is invalid

(mergeant:14649): GLib-GObject-WARNING **: can't peek value table for type `<invalid>' which is not currently referenced
Segmentation fault

Tony

On 02/03/2011 08:36 PM, tsu2 wrote:

> When I actually try to launch from CLI, this is the error that’s thrown
> which leads me to believe there is more of an issue than “just” trying
> to launch a GUI app from CLI. For one thing, running “locate” I cannot
> find the referenced document type definition (dtd) files anywhere on my
> machine.

launching GUI apps from the CLI should always work (if the app is ok,
of course)…

how did you install mergeant? were there any errors during that install…

are you running any factory software? were any factory repos enabled
when you installed mergeant?


DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11

There is a well documented issue launching GUI apps from the command line in KDE. Unfortunately there is no simple fix, when I researched this issue I saw different fixes for different apps, no two the same.

The mergeant I installed comes from the standard OpenSUSE 11.3 repositories, no factory repositories or apps were involved. I also updated mergeant, still no joy.

Just uninstalled/re-installed mergeant completely with same results(like missing XML files including the DTDs)

Tony

On 02/03/2011 11:36 PM, tsu2 wrote:

> There is a well documented issue launching GUI apps from the command
> line in KDE.

i’ve had no such problems and don’t remember any discussion in these
fora about such problems…would care to elaborate for my
enlightenment…or, just list a few URLs to the well documented
issue…thanks

> Unfortunately there is no simple fix, when I researched
> this issue I saw different fixes for different apps, no two the same.

so far every app i’ve launched from the cli which did not function
properly, did so because there was something wrong with the app or it
was installed improperly…which had nothing to do with how it was
launched…

> The mergeant I installed comes from the standard OpenSUSE 11.3
> repositories,

i didn’t ask where yours came from, but rather how you installed
it…and, i asked that for a reason, so i ask again, did you:

  • install with zypper from the command line

  • install with YaST from the command line

  • install with YaST2 (a GUI)

  • download the rpm file and run rpm against it

  • download the rpm and run YaST2 against it

  • some other way?

> no factory repositories or apps were involved. I also
> updated mergeant, still no joy.

were there update packages for the mergeant you installed??

> Just uninstalled/re-installed mergeant completely with same
> results(like missing XML files including the DTDs)

interesting, do you often find that that solves the problem??

did you try renaming ~/.mergeant and launching again…

and, why are you launching from the cli anyway? was it not added to
your menu system?

to better see what is going on i just installed mergeant and there is
now a new icon in my Menu > Applications > Office > Database named
“Database Administration - Mergeant Database Administration” which,
when left clicked pops up a “Connection opening:” dialog asking for a
data source and user name/password…

the same dialog pops up when typing mergeant into and Alt+F run command…

or, opening in a terminal and issuing that command also results in the
connect dialog, and the following output:


denver@linux:~> mergeant
I/O warning : failed to load external entity
"/usr/share/libgda-3.0/dtd/libgda-dict.dtd"
** Message: Could not parse
'/usr/share/libgda-3.0/dtd/libgda-dict.dtd': XML dictionaries
validation will not be performed (some weird errors may occur)
I/O warning : failed to load external entity
"/usr/share/libgda-3.0/dtd/libgda-array.dtd"
** Message: Could not parse
'/usr/share/libgda-3.0/dtd/libgda-array.dtd': XML data import
validation will not be performed (some weird errors may occur)
I/O warning : failed to load external entity
"/usr/share/libgda-3.0/dtd/libgda-paramlist.dtd"
** Message: Could not parse
'/usr/share/libgda-3.0/dtd/libgda-paramlist.dtd': XML data import
validation will not be performed (some weird errors may occur)
I/O warning : failed to load external entity
"/usr/share/libgda-3.0/dtd/libgda-server-operation.dtd"
** Message: Could not parse
'/usr/share/libgda-3.0/dtd/libgda-server-operation.dtd': Validation
for XML files for server operations will not be performed (some weird
errors may occur)
FAMOpen failed, FAMErrno=0

but, i can’t tell if any of that is a problem because i have no
database to point the Database Administrator at, do you?


DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11

Sorry, you’re right and I mis-spoke. all Apps including GUI apps which have been integrated into KDE will not have a problem launched from the CLI. However, it’s next to impossible to launch anything which hasn’t been “prepared” – Like a custom script or oftentimes app from source.

I was under the strong impression that it shouldn’t matter which method of YAST or zipper was used, they should all work the same reading and testing for package dependencies and use the same RPM database. If it makes any difference, I use the YAST GUI. Since I haven’t had any problems with YAST/zipper before, I think it’s more likely that the mergeant RPM package was faulty. Since you state below you were able to actually get to where you were prompted for a database, I wonder if I need to manually purge my RPM cache and force a new download.

I allowed Kupdate to look for update packages, but otherwise no. No updates were installed.

That’s interesting because as I noted when I clicked on the mergeant icon the app never launced for me, never prompted to connect to a database.

Can we doublecheck which version OpenSuSE and KDE you and I are running?

I’m running
OpenSuSE 11.3 (32bit)
KDE 4.4.4 release 3
mergeant version 0.67.79.2
Last changelog entry was Mon 09 Mar 2009 05:00:00 AM PDT

Thx,
Tony

On 02/04/2011 06:06 PM, tsu2 wrote:

> CLI. However, it’s next to impossible to launch anything which hasn’t
> been “prepared” – Like a custom script or oftentimes app from source.

sorry, i’ve never experienced that either…i’ve installed a lot from
script and never noticed any “next to impossible” to launch from
CLI…maybe you could mention one or two that you have compiled from
source which won’t run, please…

> I was under the strong impression that it shouldn’t matter which method
> of YAST or zipper was used, they should all work the same reading and
> testing for package dependencies and use the same RPM database. If it
> makes any difference

you had stated you thought the libs were not being found…and if
you install libs using the rpm command (which i thought maybe you had
done, and therefore i asked) they are not found until “ldconfig” has
been run as root (so that the new DB of libs are available)…that is
one of things done by YaST during an install

> I use the YAST GUI. Since I haven’t had any
> problems with YAST/zipper before, I think it’s more likely that the
> mergeant RPM package was faulty. Since you state below you were able to
> actually get to where you were prompted for a database, I wonder if I
> need to manually purge my RPM cache and force a new download.

at this point i must admit i have no idea what you need to do…

> That’s interesting because as I noted when I clicked on the mergeant
> icon the app never launced for me, never prompted to connect to a
> database.

did i ever suggest you use YaST to add a new user, then log in as that
user and see if mergeant would work?

> Can we doublecheck which version OpenSuSE and KDE you and I are
> running?
>
> I’m running
> OpenSuSE 11.3 (32bit)
> KDE 4.4.4 release 3
> mergeant version 0.67.79.2
> Last changelog entry was Mon 09 Mar 2009 05:00:00 AM PDT

except for the mergeant version (which is the same as yours) my
details are in my sig…i don’t know what “changelog entry” is or
where to find it…

by the way, i highly doubt the difference in our version of KDE would
have any impact on your problem…and, i do not recommend you move
to a newer version in an attempt to solve the problem…

oh, you might try turning off desktop effects (i never ever turn that
on)…


DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11

I’ll eat my shoes (well, maybe) if you can launch a GUI app from a CLI, like the following attempting to launch kwrite

SUSEBOX :/usr/share # kwrite
kwrite(4222): Session bus not found 

KCrash: Application 'kwrite' crashing...
sock_file=/root/.kde4/socket-XPHOME.MSHOME/kdeinit4__0
Warning: connect() failed: : No such file or directory
KCrash cannot reach kdeinit, launching directly.
drkonqi(4223): Session bus not found 

I haven’t noticed any lib errors, only missing DTD which would be different. DTD (Document Type Definition) is a schema document for XML, and XML can be used for many things, most commonly for configurations, data transfers, certain type of web pages, just about anything that requires a hierarchical structure. I don’t know how mergeant uses DTD/XML conceivably for anything including storing database connection info.

That’s interesting info that you say you are able to be prompted for connecting to a database but still get the same error from CLI, so it looks like the CLI error is not important.

The Changelog entry was found in the last tab in the mergeant RPM from within YAST, but I sort of doubt it should be different if the app version is the same.

Per your suggetion I logged into my machine and launched but with same result (app apparently hangs and doesn’t launch, timing out).

But interestingly I found a seg fault in /var/log/messages for further investigation

Feb  4 10:45:32 SUSEBOX kernel: [131976.256199] mergeant[3436]: segfault at 18 ip b7418635 sp bf8b8190 error 4 in libgtk-x11-2.0.so.0.2000.1[b71ec000+45b000]

The library does exist, so that’s not an issue.

I’ll consider turning off desktop effects, but since I haven’t experienced an issue related to that before I’m leaning towards that not being a likely factor

Thx,
Tony

Hi
So are you running the desktop session as root? Or have you used su to get to a root terminal? When running commands like that the norm is to use kdesu kwrite <path/filename> or browse to the file your wanting to edit.

Else you probably need to fiddle with the xhost command… before running su (hopefully su -)

On Fri, 04 Feb 2011 19:36:02 +0000, tsu2 wrote:

> I’ll eat my shoes (well, maybe) if you can launch a GUI app from a CLI,
> like the following attempting to launch kwrite

It can be done, that you can’t means there’s something not right with
your system.

Looks like dbus maybe isn’t running?

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

On 02/04/2011 08:36 PM, tsu2 wrote:
> I’ll eat my shoes (well, maybe) if you can launch a GUI app from a CLI,
> like the following attempting to launch kwrite
>
> Code:
> --------------------
> SUSEBOX :/usr/share # kwrite
> kwrite(4222): Session bus not found
>
> KCrash: Application ‘kwrite’ crashing…
> sock_file=/root/.kde4/socket-XPHOME.MSHOME/kdeinit4__0
> Warning: connect() failed: : No such file or directory
> KCrash cannot reach kdeinit, launching directly.
> drkonqi(4223): Session bus not found
> --------------------

as i tell you that your system is VERY sick (or as likely: you
procedures are very incorrect) i’ll let you look at the proof you
might not enjoy seeing, here:
http://www.imagebam.com/image/f17e39118159802 is an image with a still
open terminal (upper left) in which you can see the command ‘kwrite’
and the cursor on the next line down…because that terminal is in
use…supporting the OPEN and very usable KWrite (upper right)–on the
lower left you can see a portion of your note (as above)…i think it
would be ok if you boil your shoes a few hours to make them more
tender…and, you can select the sauce or gravy of your choice!! :wink:

now, as malcolm has already noted: you are trying to launch kwrite
asroot* which won’t work the way you tried to do it…

did you log into KDE as root? or, in what way did you become root in
that terminal??


DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11

Yes, I was launching as root and launching as non-root does launch the app without a problem. Interesting that Googling the dbus error never seems to have returned this “feature.” Now that I’m thinking about this, I wonder if this is caused because I don’t have an existing root KDE xdisplay running when invoking from a root terminal.

Yummy, shoes!

Tony

On 02/05/2011 05:06 PM, tsu2 wrote:
> Yes, I was launching as root and launching as non-root does launch the
> app without a problem. Interesting that Googling the dbus error never
> seems to have returned this “feature.” Now that I’m thinking about this,
> I wonder if this is caused because I don’t have an existing root KDE
> xdisplay running when invoking from a root terminal.

ok, here is the deal:

  • to launch any GUI app (say kwrite) with root powers, open a terminal
    (while signed into KDE as yourself, a simple user) and do NOT “su -”
    in the terminal to become root, and issue

kdesu kwrite

if you first switch user to root you can not launch kwrite, nor can
you “kdesu kwrite”…

but never never launch (say) “kdesu firefox” as root and browse the
net…just to big a risk…

and, if you are running gnome, instead of kdesu use gnomesu–note,
this is an “openSUSE thing”, i don’t know what Red Hat or others do
(and don’t care)…ubuntu uses (i think) sudo…like “sudo kwrite” but
i don’t know for sure…

and you should never log into KDE/Gnome/XFCE or any other *nix-like
graphical user interface desktop environment as root…

doing so 1) opens you up to several different security problems if you
(for example) browse the net, 2) too many too easy ways to damage your
system no matter how careful your actions (for example: well
documented cases of unintended change of ownership of ~/.ICEauthority
and ~/.Xauthority from user to root sometimes occurs), 3) and, anyway
logging into KDE/etc as root is never required to do any and all
administrative duties…

so, always log in as yourself, and “become root” by using a root
powered application (like YaST, File Manager Superuser Mode) or using
“su -”, sudo, kdesu, or gnomesu in a terminal to launch whatever tool
is needed (like Kwrite to edit a config file)…read more on all that
here:

http://en.opensuse.org/SDB:Login_as_root
http://tinyurl.com/ydbwssh
http://tinyurl.com/6ry6yd

additionally: after logging into KDE/Gnome/etc as root, if you
experience problems (for example, with uncommanded file ownership and
permissions changes) and if you can provide us with details of what
you were doing while you were logged in as root, that would help us
identify if there’s a bug that needs to be fixed…thanks for your help…

> Yummy, shoes!

i give you a pass on that, as long as you promise to not log into KDE
as root…in addition to the reasons listed above, also because it
can cause strange little problems to pop up (or not…like maybe it
could cause a mergeant ‘connect to’ dialog to NOT pop up on your
machine, but all it to on my machine, and now you know why i asked…


DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11