On Wed, 1 Aug 2001, Benjamin Sher wrote:
> Dear friends:
>
> I had this problem before and somehow or other it solved itself.
>
> sher@localhost sher]$ rpm -q galeon
> galeon-0.11.3-1mdk
> [sher@localhost sher]$ rpm -q mozilla
> mozilla-0.9.2-7mdk
> [sher@localhost sher]$
>
> Galeon won't start either when I click on the Galeon desktop icon or when I
> type "galeon" as user in xterm. I even tried to start Galeon by adding
> "kstart" to the executable line: "kstart /usr/bin/galeon". Doesn't work. The
> "Galeon" icon appears for a while in the panel, the icon spins for a good
> while and then just disappears.
>
> I typed "top" in xterm and could see no reference to galeon or galeon-bin.
As the other post mentioned, you need to be using ps ax (or ps aux) for
that. Since there is no guarantee lingering galeon-bin processes will be
using the most CPU, you will not necessarily see it in top.
A problem I've had with galeon is that occasionally the
.galeon/history.xml file (in your home directory) will become corrupted,
which keeps it from loading. I tracked this down a while back by running
strace galeon and seeing what files it was opening before crash & burning.
So, try rm .galeon/history.xml
> I logged out of KDE and shut down the system, unplugged the power cable,
> reconnected it, rebooted, logged back into KDE, tried once again to launch
> Galeon. Again, same problem.
>
> I launched Konqueror as root, went to /usr/bin/ and clicked on "galeon". It
> brought up the Galeon welcome screen, followed by a request for creating a
> profile. So, Galeon seems to work as root. I decided not to proceed since I
> don't need or want a "root" account of Galeon.
Sounds more and more like the bookmarks.xml issue. galeon-bin would
definitely be stopped by a system shutdown. ;)
> This is very puzzling. Unfortunately, I have exhausted my "trial and error"
> options at this point.
Insight tends to better than trial and error. :) If you want to make
sense of strace at your own leisure, try doing small things like echo "hi"
at the command-line under strace eg.,
strace echo "hi"
Along with a bunch of other stuff, you can see things like:
open("/lib/libc.so.6", O_RDONLY) = 3
(opening up a shared library)
Result of 3 means the open succeeded and the process is reading from that
on descriptor 3, as opposed to:
open("/etc/ld.so.preload", O_RDONLY) = -1 ENOENT (No such file or
directory)
When it tried to open that file, there was an error ( -1 ENOENT)
Then, it writes to standard output (descriptor 1):
write(1, "hi\n", 3hi
)
The output is intermixed w/ standard error (which strace uses for
display), but this can be avoided (and you can get a copy of all the
system calls to look through) by doing:
strace echo hi 2> strace-output
Then, just open strace-output in an editor.
Also, there are manpages for all of those system calls in manual section
2. So, man 2 open will tell you what open() does. It's rather
C-programming oriented, but the DESCRIPTION and ERRORS sections should
give you the info you're after to see what a call is doing.
If you do this on galeon, and my guess is correct, you'll see something
bad happen shortly after reading history.xml ;)
>
> As a last resort, before sending this message, I uninstalled galeon (rpm -e
> galeon) and reinstalled it. Tried launching it again. Still won't start.
>
> Would very much appreciate your help.
>
> Thanks so much.
>
> Benjamin
Hope this helps!
-pete
> --
> Sher's Russian Web
> http://www.websher.net
> Benjamin and Anna Sher
> [EMAIL PROTECTED]
>
>
