Ric Tibbetts wrote: > Oscar wrote: > >>El jue, 17-01-2002 a las 06:51, Ric Tibbetts escribi�: >> >>>Salvatore Enrico Indiogine wrote: >>> >>>>Greetings! >>>> >>>>Each time I try to print an email from Evolution 1.0.1 the mail >>>>component crashes. >>>> >>>>Anyone else ran into this problem? >>>> >>>Bigger question: >>>How did you get it installed? I tried to update mine (I currently have >>>1.0 installed), and it failed on a dependancy to libgal19. I couldn't >>>find it on the Cooker site. >>> >>You must upgrade libgal19-0.19-2mdk.i586.rpm (It's in the cooker site). >>But I don't recommend it to you. Indeed, I installed the 1.0.1 version >>and the mail component crashes when I tried to print. >>Now I'm with 1.0 version and I'm happy (I only must type the password >>from time to time because the program does not remember it, but... it >>prints...) >>Saludos >>�scar. >> > > Thanks Oscar! > > <rant> > I have to comment, that your reply brings up my single largest complaint > about Linux installations: Inconsistancy. > I've been a Unix admin for a long time. Done a lot of server builds ( I > do enterprise server administration, not desktop ), with AIX, and HP-UX, > and never suffered this kind of inconsistancy. I realize that it's > harder to write for the PC environment, because of the huge variations > in hardware, but: > > As an example: > The first time I loaded 8.1 (on this box), I had problems with the > sound. I had to configure the sound card "every time I rebooted the > machine". Then, a week or so ago, I needed to re-load the box. Now the > sound card works just fine. Why? Why did it not work before, and it does > work now? I've had other similar inconsistancies, but they have slipped > my mind at the moment. > > Why am I bringing this up? > Well... > On my previous build, Evolution would not remember passwords (just as > you've described). But on THIS build, it does! What's different? > Nothing. It's just not consistant, and it should be. A box shouldn't > change behaviour dramatically, when you re-load the same OS, from the > same CDs. > > Just a personal sore point with Linux. I see a lot of it on these lists, > and soem of it I write off as operator differences. Very often the human > element gets involved in the install. Different people do the install, > and get different results. "Some" of that I can understand. But not to > the extent that I see it, and not on the same box, installed by the same > person... > One of my favorite inconsistancies is "Tuxracer". For "some" people, it > works just great, and for others it doesn't. And there seems to be no > rational explanation for why. For many of the folks for whom it doesn't > work, it has fired right up when run as root, but fails when run as a > normal user. (I'm one of those). Nobody seems to know why. > > Consistancy is not too much to ask for is it? > </rant> > > However, getting back to the topic at hand. > > I'm willing to risk the "upgrade" to 1.0.1 printing problem. Since my > password problem seems to have gone away, maybe the printing will work > to. :) It's worth a try. More likely, I'll get the printing problem, and > then loose my passwords when I go back down to 1.0 > > > > > ------------------------------------------------------------------------ > > Want to buy your Pack or Services from MandrakeSoft? > Go to http://www.mandrakestore.com >
Does Chromium work for you also? If it doesn't chances are you are missing a config file for openal in your home directory. Try this fix and let me know if it works: create file .openalrc and be sure to not forget the "."! touch .openalrc edit the file and input this one line: vi .openalrc (define native-use-select #f) and be sure to not forget the parenthesis! HTH altoine
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
