unsubscribe 5699415

From: "Tarun R Elankath" <tarun webkadai com>
To: <gnome-list gnome org>
Subject: unsubscribe 5699415
Date: Sun, 22 Oct 2000 01:00:25 +0530
----- Original Message -----
From: <gnome-list-request gnome org>
To: <gnome-list gnome org>
Sent: Saturday, October 21, 2000 9:31 PM
Subject: gnome-list digest, Vol 1 #336 - 18 msgs


> Send gnome-list mailing list submissions to
> gnome-list gnome org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mail.gnome.org/mailman/listinfo/gnome-list
> or, via email, send a message with subject or body 'help' to
> gnome-list-request gnome org
>
> You can reach the person managing the list at
> gnome-list-admin gnome org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of gnome-list digest..."
>
>
> Today's Topics:
>
>   1. Gnome Panel (Aristide Aragon)
>   2. Re: Performance on the Linux platform (Jason Stokes)
>   3. Re: Performance on the Linux platform (Ian Peters)
>   4. GNOME 1.2.2.1 impressions/bugs (Brent A. Nelson)
>   5. Re: Performance on the Linux platform (Ben FrantzDale)
>   6. gnome-libs build failure (Michael Myburgh)
>   7. Re: Gnome Panel (Ben FrantzDale)
>   8. Re: Performance on the Linux platform (Jason Stokes)
>   9. Re: gnome-libs build failure (Iain)
>   10. SegFault with Theme Selector (Chris Dempsey)
>   11. Re: Gnome Panel (Aristide Aragon)
>   12. theme selector problem... (gourdin)
>   13. Re: Performance on the Linux platform (Owen Taylor)
>   14. Re: RH7/CORBA compile queries (was RH7/gnome compile queries) (Bruce
W. Bigby)
>   15. Re: Performance on the Linux platform (Jason Stokes)
>   16. unsubscribe famous cc syau edu cn (famous)
>   17. Gnome 1.2.1 and 1.2.2 crashes all the time... (André Rabello dos
Anjos)
>   18. Re: Gnome 1.2.1 and 1.2.2 crashes all the time... (Ali Abdin)
>
> --__--__--
>
> Message: 1
> From: "Aristide Aragon" <aristide lionking org>
> To: <gnome-list gnome org>
> Subject: Gnome Panel
> Date: Fri, 20 Oct 2000 11:06:52 -0500
>
> Hello
> I'm new to this list, as I'm new to gnome. I used to use KDE and then
> moved to window maker. Windowmaker was fine, but all of a sudden it
> starting segfaulting.. So, I'm using gnome.
> A couple of days ago I had a problem, and I still can't fix it.
> I was trying ldescent, a Descent 1 port to Linux, and suddenly all
> applets dissapeared from my panel, and all my windows dissapeared.
> After trying alt+tab with no success I pressed control alt backspace,
> and then I discovered my windows were still alive, anyways it was too
> late nd X closed.
> Ever since my applets didn't appear back in my panel, and I can't add
> any applet to it. I don't get any error message or anything, they
> just don't show up.
> I tried renaming my ~/.gome and also created a new panel to try in
> that one, none worked.
> I also tried upgrading my gnome (that was about a month old) and that
> didn't work either, I can't add applets to the panel.
> I tried starting a panel from a console so if there were ny stderr
> messages I would see them, but I failed to even start a panel, even
> if I killed the old panel (because it restarts automatically).
> Does anybody know what's going on?
>
> Aristide
>
>
>
>
> --__--__--
>
> Message: 2
> Date: Sat, 21 Oct 2000 03:17:10 +1100
> From: Jason Stokes <jstok bluedog apana org au>
> To: Michael Thomas <michaelv cox-internet com>
> Cc: gnome-list gnome org
> Subject: Re: Performance on the Linux platform
>
> Michael Thomas wrote:
> >
> > Can anyone explain why gmc loads in approximately 1.5 seconds when
> > executed by right clicking on the desktop & selecting create new window
> > from the menu versus a full 7 .0 seconds. to load from  any other
> > method. (ex ample: Main Menu - File Manager)
>
> Right-clicking within the desktop and selecting create new window
> creates a new window managed by the current gmc process, whereas
> selecting "Main Menu -> File Manager" executes a new gmc process.  The
> overhead of starting a new gmc process is more than creating a new
> window within an existing gmc process.
>
> Anyone noticed that a gmc process never exits when you choose "exit"
> from the menu?  It just sticks around taking up memory and a process
> table entry forever. Bug?
>
>
> --__--__--
>
> Message: 3
> Date: Fri, 20 Oct 2000 12:47:54 -0400
> To: Jason Stokes <jstok bluedog apana org au>
> Cc: Michael Thomas <michaelv cox-internet com>, gnome-list gnome org
> Subject: Re: Performance on the Linux platform
> Michael Thomas <michaelv cox-internet com>, gnome-list gnome org
> From: Ian Peters <itp helixcode com>
>
> On Sat, Oct 21, 2000 at 03:17:10AM +1100, Jason Stokes wrote:
> >
> > Anyone noticed that a gmc process never exits when you choose "exit"
> > from the menu?  It just sticks around taking up memory and a process
> > table entry forever. Bug?
>
> No.  If you really want to make the gmc process die, you should go to
> Commands->Exit.  gmc is designed to stick around because it's intended
> to manage your desktop icons.  The "correct" way to run it is to have
> gmc started in your session, and then just create and destroy
> different views/windows, but always leave the process running.
>
> --
> Ian Peters
> itp helixcode com
>
>
> --__--__--
>
> Message: 4
> Date: Thu, 19 Oct 2000 16:35:10 -0400 (EDT)
> From: "Brent A. Nelson" <brent astro ufl edu>
> To: gnome-list gnome org
> Subject: GNOME 1.2.2.1 impressions/bugs
>
> I recently upgraded our GNOME environment from October GNOME (last year)
> to GNOME 1.2.2.1.  It seemed quite nice, but as I upgraded more and more
> people, I noticed certain issues...
>
> 1) The most immediate complaint was the colormap.  The new GNOME somehow
> manages to allocate the whole 8-bit color map, even with nothing but gmc,
> the panel, and a terminal on the screen! On the bright-side, I did get a
> number of converts to 24 bit color. ;-)  Does anyone have any insight into
> this issue? Unfortunately, 8-bit color is the "norm" in the sciences due
> to some reluctant old applications (although it is improving, some
> things still refuse to work on anything but 8-bit pseudocolor).
>
> 2) Once I upgraded people who use xfmail-- big trouble.  XFMail
> (especially when bringing up a window to compose a message) has a very
> high probability of killing off the tasklist applet.  I now have people
> constantly restarting tasklist throughout the day. Most distressing! :-(
>
> 3) The deskguide applet crashes occassionally.
>
> 4) So far, gdm 2.0beta4 (as distributed by Helix) seems to be better
> behaved than RedHat's 2.0beta2 RPMs have been, although not perfect.  With
> the old RPMs, given about 45 machines, gdm often would not restart
> properly when someone logged out, and I'd frequently have to restart gdm.
> With the newer gdm, I've still had to do this once, so it's still not
> reliable but it at least seems better.
>
> 5) I had sawfish die on one person, but in general, it does seem to be
> behaving much better than enlightenment did.  Shook my faith a little, but
> sawfish has been otherwise very well behaved (version 0.31.1).
>
> Overall, it looks like we'll at least survive this upgrade (most people
> seem quite happy with it, and it's much prettier), but does anyone at
> least have any idea how to fix the XFMail/tasklist issue? That one's
> really pretty nasty! I've sent off a message to the XFMail list, but I
> thought you guys should know, too, as tasklist really shouldn't die no
> matter what the apps on screen are doing.
>
> Many thanks for listening!
>
> Brent Nelson
> Sys. Manager
> Dept. of Astronomy
> University of Florida
>
>
>
> --__--__--
>
> Message: 5
> Subject: Re: Performance on the Linux platform
> From: Ben FrantzDale <bfrantzdale hmc edu>
> To: Michael Thomas <michaelv cox-internet com>
> Cc: gnome-list gnome org
> Date: 20 Oct 2000 02:43:48 +0500
>
> > Can anyone explain why gmc loads in approximately 1.5 seconds when
> > executed by right clicking on the desktop & selecting create new window
> > from the menu versus a full 7 .0 seconds. to load from  any other
> > method. (ex ample: Main Menu - File Manager)
> >
> > This has been experienced w/ three current version of RedHat on a
> > PentiumPro 180.
>
> I think what's happening is that ``file manager'' is loading up the gmc
> executable whereas double clicking on an icon just popps up a new view
> without loading the executable.
>
> --Ben
>
>
>
> --__--__--
>
> Message: 6
> Date: Fri, 20 Oct 2000 16:57:12 +0100 (BST)
> From: Michael Myburgh <Michael Myburgh ireland sun com>
> Reply-To: Michael Myburgh <Michael Myburgh ireland sun com>
> Subject: gnome-libs build failure
> To: gnome-list gnome org
>
>
> I've picked up the new gnome-libs module, which required
> me to pick up the gnome-common module in order to build.
> So I downloaded and installed gnome-common, but
> autogen.sh for gnome-libs still fails on the
> unrecognized identifier "PKG_CHECK_MODULES". Can anyone
> help me out here?
>
> Thanks
> Michael
>
>
>
> --__--__--
>
> Message: 7
> Subject: Re: Gnome Panel
> From: Ben FrantzDale <bfrantzdale thuban ac hmc edu>
> To: Aristide Aragon <aristide lionking org>
> Cc: gnome-list gnome org
> Date: 20 Oct 2000 19:35:54 +0500
>
> > Hello
> > I'm new to this list, as I'm new to gnome. I used to use KDE and then
> > moved to window maker. Windowmaker was fine, but all of a sudden it
> > starting segfaulting.. So, I'm using gnome.
> > A couple of days ago I had a problem, and I still can't fix it.
> > I was trying ldescent, a Descent 1 port to Linux, and suddenly all
> > applets dissapeared from my panel, and all my windows dissapeared.
> > After trying alt+tab with no success I pressed control alt backspace,
> > and then I discovered my windows were still alive, anyways it was too
> > late nd X closed.
> > Ever since my applets didn't appear back in my panel, and I can't add
> > any applet to it. I don't get any error message or anything, they
> > just don't show up.
> > I tried renaming my ~/.gome and also created a new panel to try in
> > that one, none worked.
> > I also tried upgrading my gnome (that was about a month old) and that
> > didn't work either, I can't add applets to the panel.
> > I tried starting a panel from a console so if there were ny stderr
> > messages I would see them, but I failed to even start a panel, even
> > if I killed the old panel (because it restarts automatically).
> > Does anybody know what's going on?
>
> Odd... I'm suprised that moving ~/.gnome/ didn't do anything... Though
> if you were using gnome when you did that it may have been recreated
> when you exited...
>
> I would try running some applets from a terminal and see if they give
> you any errors. Also, try loging out of X, going to a terminal
> (ctrl+alt+F1) and then moving ~/.gnome/.
>
> --Ben
>
>
>
> --__--__--
>
> Message: 8
> Date: Sat, 21 Oct 2000 04:52:44 +1100
> From: Jason Stokes <jstok bluedog apana org au>
> To: Ian Peters <itp helixcode com>
> Cc: Michael Thomas <michaelv cox-internet com>, gnome-list gnome org
> Subject: Re: Performance on the Linux platform
>
> Ian Peters wrote:
> >
> > On Sat, Oct 21, 2000 at 03:17:10AM +1100, Jason Stokes wrote:
> > >
> > > Anyone noticed that a gmc process never exits when you choose "exit"
> > > from the menu?  It just sticks around taking up memory and a process
> > > table entry forever. Bug?
> >
> > No.  If you really want to make the gmc process die, you should go to
> > Commands->Exit.  gmc is designed to stick around because it's intended
> > to manage your desktop icons.  The "correct" way to run it is to have
> > gmc started in your session, and then just create and destroy
> > different views/windows, but always leave the process running.
>
> Ok, if that's the case why is it possible to start a new instance of gmc
> via the footprint menu?  The user isn't going to be care about the
> different ways a new window can be created.  If you choose "Close
> Window" from the file menu, and the gmc process was only managing one
> window, it still runs but you've now lost any way to interact with it,
> and have to kill it with a signal, assuming the user understands such
> things.  This is not the ideal way for a GUI program to work.
>
>
> --__--__--
>
> Message: 9
> From: "Iain" <tigermilk btinternet com>
> To: "Michael Myburgh" <Michael Myburgh ireland sun com>,
> <gnome-list gnome org>
> Subject: Re: gnome-libs build failure
> Date: Fri, 20 Oct 2000 22:00:05 +0100
> charset="iso-8859-1"
>
> Looks like you picked up HEAD
> which you don't want to do.
>
> cvs -z3 checkout -r gnome-libs-1-0 gnome-libs
> >
> > I've picked up the new gnome-libs module, which required
> > me to pick up the gnome-common module in order to build.
> > So I downloaded and installed gnome-common, but
> > autogen.sh for gnome-libs still fails on the
> > unrecognized identifier "PKG_CHECK_MODULES". Can anyone
> > help me out here?
> >
> > Thanks
> > Michael
> >
> >
> > _______________________________________________
> > gnome-list mailing list
> > gnome-list gnome org
> > http://mail.gnome.org/mailman/listinfo/gnome-list
> >
>
>
>
> --__--__--
>
> Message: 10
> Date: Fri, 20 Oct 2000 14:48:54 -0700 (PDT)
> From: Chris Dempsey <chrisdempsey yahoo com>
> Subject: SegFault with Theme Selector
> To: gnome-list gnome org
>
> I am getting a recurring SegFault when choosing a
> theme in the Sawfish Theme Selector.  I realize this
> is slightly off-topic, but this list has a larger
> userbase...
>
> GeForce 2 GTS, FBSD 411-Stable, XFree86 4.0.1_2, Gnome
> 1.2, Sawfish 0.32.
>
> Themes are fun, please help me out!
>
> Chris Dempsey
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Messenger - Talk while you surf!  It's FREE.
> http://im.yahoo.com/
>
>
> --__--__--
>
> Message: 11
> From: "Aristide Aragon" <aristide lionking org>
> To: "Ben FrantzDale" <bfrantzdale thuban ac hmc edu>
> Cc: <gnome-list gnome org>
> Subject: Re: Gnome Panel
> Date: Fri, 20 Oct 2000 17:27:46 -0500
>
> I was out of X when I moved ~/.gnome
> I stted an applet from the console. I hadn't done this before because
> I didn't know the ame of any program that were an applet, but after
> reading this mail I thought of right clicking one and bingo!.
> I got the error:
> ** WARNING **: Cannot activate a panel object
>
> ** WARNING **: Cannot start CORBA
> and after that it sigfaulted.
>
> I'm quite surprised the gnome uses CORBA, that means running gnome
> remotely now means mor than just to change DISPLAY in the enviroment.
>
> What could be wrong?
>
> Aristied
>
> | > Hello
> | > I'm new to this list, as I'm new to gnome. I used to use KDE and
> then
> | > moved to window maker. Windowmaker was fine, but all of a sudden
> it
> | > starting segfaulting.. So, I'm using gnome.
> | > A couple of days ago I had a problem, and I still can't fix it.
> | > I was trying ldescent, a Descent 1 port to Linux, and suddenly
> all
> | > applets dissapeared from my panel, and all my windows
> dissapeared.
> | > After trying alt+tab with no success I pressed control alt
> backspace,
> | > and then I discovered my windows were still alive, anyways it was
> too
> | > late nd X closed.
> | > Ever since my applets didn't appear back in my panel, and I can't
> add
> | > any applet to it. I don't get any error message or anything, they
> | > just don't show up.
> | > I tried renaming my ~/.gome and also created a new panel to try
> in
> | > that one, none worked.
> | > I also tried upgrading my gnome (that was about a month old) and
> that
> | > didn't work either, I can't add applets to the panel.
> | > I tried starting a panel from a console so if there were ny
> stderr
> | > messages I would see them, but I failed to even start a panel,
> even
> | > if I killed the old panel (because it restarts automatically).
> | > Does anybody know what's going on?
> |
> | Odd... I'm suprised that moving ~/.gnome/ didn't do anything...
> Though
> | if you were using gnome when you did that it may have been
> recreated
> | when you exited...
> |
> | I would try running some applets from a terminal and see if they
> give
> | you any errors. Also, try loging out of X, going to a terminal
> | (ctrl+alt+F1) and then moving ~/.gnome/.
> |
> | --Ben
> |
> |
>
>
>
>
> --__--__--
>
> Message: 12
> From: gourdin <gourdin gcu-squad org>
> Date: Sat, 21 Oct 2000 00:28:13 +0200
> charset="iso-8859-1"
> To: gnome-list gnome org
> Subject: theme selector problem...
>
> Hi,
>
> When I try to use the theme selector in my gnome-control-center to install
a
> gtk theme, nothing happen.... the right array is empty (without any
> button...) did i miss anything ?
>
> Gourd|n
>
> PS : the other configuration options work perfectly...
>
>
> --__--__--
>
> Message: 13
> To: Jason Stokes <jstok bluedog apana org au>
> Cc: Ian Peters <itp helixcode com>,
> Michael Thomas <michaelv cox-internet com>, gnome-list gnome org
> Subject: Re: Performance on the Linux platform
> <39F07006 17ED58B2 bluedog apana org au> <20001020124754 B6385 flux>
> <39F0866C DD0DF9BD bluedog apana org au>
> From: Owen Taylor <otaylor redhat com>
> Date: 20 Oct 2000 17:50:23 -0400
>
>
> Jason Stokes <jstok bluedog apana org au> writes:
>
> > Ian Peters wrote:
> > >
> > > On Sat, Oct 21, 2000 at 03:17:10AM +1100, Jason Stokes wrote:
> > > >
> > > > Anyone noticed that a gmc process never exits when you choose "exit"
> > > > from the menu?  It just sticks around taking up memory and a process
> > > > table entry forever. Bug?
> > >
> > > No.  If you really want to make the gmc process die, you should go to
> > > Commands->Exit.  gmc is designed to stick around because it's intended
> > > to manage your desktop icons.  The "correct" way to run it is to have
> > > gmc started in your session, and then just create and destroy
> > > different views/windows, but always leave the process running.
> >
> > Ok, if that's the case why is it possible to start a new instance of gmc
> > via the footprint menu?  The user isn't going to be care about the
> > different ways a new window can be created.  If you choose "Close
> > Window" from the file menu, and the gmc process was only managing one
> > window, it still runs but you've now lost any way to interact with it,
> > and have to kill it with a signal, assuming the user understands such
> > things.  This is not the ideal way for a GUI program to work.
>
> When you use the foot menu, it doesn't create a new process -
> what happens is that when it launches GMC, GMC checks to see
> if there is a process already running, and if there is, tells
> that process to create a new window and exits.
>
> (This still takes longer than just creating a window from
> a menu, accounting for the original observation)
>
> There should never be a case where more than once GMC is
> running at a time.
>
>                                         Owen
>
>
> --__--__--
>
> Message: 14
> Date: Fri, 20 Oct 2000 21:17:20 -0400
> From: "Bruce W. Bigby" <bbigby rochester rr com>
> To: Iain <tigermilk btinternet com>
> Cc: dsh8290 rit edu, Joachim Backes <backes rhrk uni-kl de>,
> gnome-list <gnome-list gnome org>
> Subject: Re: RH7/CORBA compile queries (was RH7/gnome compile queries)
>
> Iain wrote:
> >
> > > (here's the line,  there are several of them and they all give the
same
> > error)
> > >
> > > #define ENCODER_DEC(typename) \
> > > void giop_encoder_##typename##(GIOPSendBuffer *send_buffer, \
> > >        const typename *mem)
> > >
> > >
> > > Could someone explain this C (preprocessor) feature to me?
> >
> > It's explained fully in the gcc info file under ## I think, but
basically,
> > it puts whatever is in typename into the define. So for
ENCODER_DEC(wibble)
> > it will expand to
> > void giop_encoder_wibble(GIOPSendBuffer *send_buffer, const wibble *mem)
> >
> > iain
> >
> > _______________________________________________
> > gnome-list mailing list
> > gnome-list gnome org
> > http://mail.gnome.org/mailman/listinfo/gnome-list
>
> Is this portable to non-GCC compiler environments???
> --
> Bruce W. Bigby
> http://home.rochester.rr.com/bigbyofrocny
> An elegant piece of software is one in which its design and
> its implementation are one and the same.
>
>
> --__--__--
>
> Message: 15
> Date: Sat, 21 Oct 2000 13:58:21 +1100
> From: Jason Stokes <jstok bluedog apana org au>
> To: Owen Taylor <otaylor redhat com>
> Cc: Ian Peters <itp helixcode com>,
> Michael Thomas <michaelv cox-internet com>, gnome-list gnome org
> Subject: Re: Performance on the Linux platform
> <39F07006 17ED58B2 bluedog apana org au> <20001020124754 B6385 flux>
> <39F0866C DD0DF9BD bluedog apana org au>
<ybeu2a7w5b4 fsf fresnel labs redhat com>
>
> Owen Taylor wrote:
> >
> > Jason Stokes <jstok bluedog apana org au> writes:
> > >
> > > Ok, if that's the case why is it possible to start a new instance of
gmc
> > > via the footprint menu?  The user isn't going to be care about the
> > > different ways a new window can be created.  If you choose "Close
> > > Window" from the file menu, and the gmc process was only managing one
> > > window, it still runs but you've now lost any way to interact with it,
> > > and have to kill it with a signal, assuming the user understands such
> > > things.  This is not the ideal way for a GUI program to work.
> >
> > When you use the foot menu, it doesn't create a new process -
> > what happens is that when it launches GMC, GMC checks to see
> > if there is a process already running, and if there is, tells
> > that process to create a new window and exits.
> >
> > (This still takes longer than just creating a window from
> > a menu, accounting for the original observation)
> >
> > There should never be a case where more than once GMC is
> > running at a time.
>
> I can personally vouch for the fact that when I select "File Manager"
> from the foot menu, it starts a new gmc process.  This may be an
> installation problem, since my gnome is built from CVS sources, but it's
> definitely the way it works.
>
>
> --__--__--
>
> Message: 16
> From: "famous" <famous cc syau edu cn>
> To: <gnome-list gnome org>
> Subject: unsubscribe famous cc syau edu cn
> Date: Sat, 21 Oct 2000 15:06:08 +0800
> boundary="----=_NextPart_000_001A_01C03B70.70FBCCE0"
>
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_001A_01C03B70.70FBCCE0
> Content-Type: text/plain;
> charset="gb2312"
> Content-Transfer-Encoding: quoted-printable
>
>
>
> ------=_NextPart_000_001A_01C03B70.70FBCCE0
> Content-Type: text/html;
> charset="gb2312"
> Content-Transfer-Encoding: quoted-printable
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
> <HTML>
> <HEAD>
>
> <META content=3Dtext/html;charset=3Dgb2312 http-equiv=3DContent-Type>
> <META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR>
> </HEAD>
> <BODY bgColor=3D#ffffff>
> <DIV>&nbsp;</DIV></BODY></HTML>
>
> ------=_NextPart_000_001A_01C03B70.70FBCCE0--
>
>
>
> --__--__--
>
> Message: 17
> Date: Fri, 20 Oct 2000 19:26:02 -0200
> From: André Rabello dos Anjos <Andre Rabello mail com>
> To: gnome-list gnome org
> Subject: Gnome 1.2.1 and 1.2.2 crashes all the time...
>
> Hi, is this the right place to ask for help?
>
> Well, my linux box has been running gnome since a while now. I have RH6.1
system but have done lots of upgrades since them. Initially it was robust
enough, but recently, after upgrading some things (which I don't exactly
recall now), gnome started crashing. It's really bad to loose some work and
have to recover every couple of hours and sometimes even minutes. That's how
long crashes are taking nowadays over here:-(
>
> Anyhow, is there a known bug that causes this bad behaviour? My
/var/log/messages just say this after a crash:
>
> Oct 20 18:59:10 aqui gnome-name-server[1205]: input condition is: 0x10,
exiting
>
> Which unfortunately, I don't know the meaning... Does anyone of you know?
Please, any light would be good, I would _really_ rate to have to change my
desktop. Gnome is really a major step on linux desktop'ing!
>
> I've tried chaning kernel versions, libraries and other stuff. I event
de-installed gnome-core 1.2.2 thinking it could be buggy, but the behaviour
repeats with version 1.2.1... Any clues?
>
> Cheers, Andre.
>
> --
> =======================================================
>                  Residencial Mailbox
>  André Rabello dos Anjos <Andre Rabello mail com>
>  Visit my homepage at: http://www.lps.ufrj.br/~rabello
> =======================================================
>
>
>
> --__--__--
>
> Message: 18
> Date: Sat, 21 Oct 2000 15:59:53 -0200
> From: Ali Abdin <aliabdin aucegypt edu>
> Subject: Re: Gnome 1.2.1 and 1.2.2 crashes all the time...
> To: =?iso-8859-1?Q?Andr=E9_Rabello_dos_Anjos?= <Andre Rabello mail com>
> Cc: gnome-list gnome org
> <Andre Rabello mail com>, gnome-list gnome org
>
> * André Rabello dos Anjos (Andre Rabello mail com) wrote at 15:57 on
21/10/00:
> > Hi, is this the right place to ask for help?
> >
> > Well, my linux box has been running gnome since a while now. I have
RH6.1 system but have done lots of upgrades since them. Initially it was
robust enough, but recently, after upgrading some things (which I don't
exactly recall now), gnome started crashing. It's really bad to loose some
work and have to recover every couple of hours and sometimes even minutes.
That's how long crashes are taking nowadays over here:-(
>
> Can you please state which INDIVIDUAL app is crashing? Once you determine
> which app is crashing, you can then usually figure out what the problem
is.
>
> > Anyhow, is there a known bug that causes this bad behaviour? My
/var/log/messages just say this after a crash:
> >
> > Oct 20 18:59:10 aqui gnome-name-server[1205]: input condition is: 0x10,
exiting
>
> This is nromal
>
> > Which unfortunately, I don't know the meaning... Does anyone of you
know? Please, any light would be good, I would _really_ rate to have to
change my desktop. Gnome is really a major step on linux desktop'ing!
>
> No - not unless you tell us EXACTLY what you are doing. Does all of 'X'
crash?
> if this is so, then it is an X bug, and not a GNOME bug
>
> > I've tried chaning kernel versions, libraries and other stuff. I event
de-installed gnome-core 1.2.2 thinking it could be buggy, but the behaviour
repeats with version 1.2.1... Any clues?
>
> Note: the latest stable gnome-libs version is 1.2.4
>
> >
> > Cheers, Andre.
> >
> > --
> > =======================================================
> >                  Residencial Mailbox
> >  André Rabello dos Anjos <Andre Rabello mail com>
> >  Visit my homepage at: http://www.lps.ufrj.br/~rabello
> > =======================================================
> >
> >
> > _______________________________________________
> > gnome-list mailing list
> > gnome-list gnome org
> > http://mail.gnome.org/mailman/listinfo/gnome-list
>
>
>
> --__--__--
>
> _______________________________________________
> gnome-list mailing list
> gnome-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-list
>
>
> End of gnome-list Digest_______________________________________________
> gnome-list mailing list
> gnome-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-list
>
[Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]