Re: [Evolution] Error: Cannot create the specified folder: Genericerror...
On Fri, 2002-11-08 at 22:21, Jeffrey Stedfast wrote: > On Fri, 2002-11-08 at 22:58, Andrew Bertola wrote: > > I am getting an error when trying to create a new mbox "folder" via > > remote IMAP. Is this a known issue? > > you probably tried to use a forbidden char in the folder name or > something. > > (iirc, generic error means it didn't even make it to the mailer before > it decided it wasn't going to do it) Thinking about this again, I was able to create the exact same mbox in mutt, then I went back to evo and successfully subscribed to that mbox. -- +-- T h e C o o p . n e t --+ | Drew Bertola Hosting - Colocation Tel: 408-738-8337 | | TheCoop.net Programming - Administration Mob: 408-887-0426 | | [EMAIL PROTECTED]Open Source Specialistshttp://thecoop.net | +---+ ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
Re: [Evolution] Error: Cannot create the specified folder: Genericerror...
On Fri, 2002-11-08 at 22:21, Jeffrey Stedfast wrote: > On Fri, 2002-11-08 at 22:58, Andrew Bertola wrote: > > I am getting an error when trying to create a new mbox "folder" via > > remote IMAP. Is this a known issue? > > you probably tried to use a forbidden char in the folder name or > something. > > (iirc, generic error means it didn't even make it to the mailer before > it decided it wasn't going to do it) Is there a list of illegal characters floating around, or is that an IMAP thing? -- +-- T h e C o o p . n e t --+ | Drew Bertola Hosting - Colocation Tel: 408-738-8337 | | TheCoop.net Programming - Administration Mob: 408-887-0426 | | [EMAIL PROTECTED]Open Source Specialistshttp://thecoop.net | +---+ ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
Re: [Evolution] Error: Cannot create the specified folder: Genericerror...
On Fri, 2002-11-08 at 22:58, Andrew Bertola wrote: > I am getting an error when trying to create a new mbox "folder" via > remote IMAP. Is this a known issue? you probably tried to use a forbidden char in the folder name or something. (iirc, generic error means it didn't even make it to the mailer before it decided it wasn't going to do it) Jeff -- Jeffrey Stedfast Evolution Hacker - Ximian, Inc. [EMAIL PROTECTED] - www.ximian.com ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
Re: [Evolution] reading / writing mail with Japanese fonts(iso-2022-jp)...
On Sat, 2002-11-09 at 00:23, Andrew Bertola wrote: > On Thu, 2002-11-07 at 22:33, Thomas O'Dowd wrote: > > As for kinput2 not working. It works for me but of course it gets > > displayed as when I convert something. Andrew, why are you killing > > kinput2 all the time. I start it once as lots of my apps use it. You > > might want to check that you have XMODIFIERS set. Something like... > > > > LANG=en_US LC_CTYPE=ja_JP LC_MESSAGES=en_US XMODIFIERS="@im=kinput2" > > evolution. > > No joy on RH 8.0. Maybe I have to take it up with them. It seems that > 1.0.8 worked w/ 7.3, but not with 8.0. I installed support for both > en_US and ja_JP. > > Then again, mutt works great with iso-2022-jp and kinput2 (at least > inside gnome-terminal w/ emacs -nw as editor). > > So, what's the difference in language support infrastructure? No idea, I'm still using RH 7.1 and Gnome 1.4. No time to upgrade yet. Does Japanese input work within a normal kterm? Try starting a kterm and then echoing some kanji to the terminal. echo 'INPUTKANJIHERE'. If kinput works then it should also work with evolution. I don't use emacs but I think it has a slightly different way of handling things and talks directly to the canna servers. Make sure that XMODIFIERS is set. Also, how did you start kinput2? I use "kinput2 -canna". That still won't solve the display problems in evolution though. Larry, any further ideas on that? Cheers, Tom. -- Thomas O'Dowd, CEO, Nooper.com - Mobile Services Inc., Tokyo, Japan i-mode & FOMA consulting, development, testing: http://nooper.co.jp/ ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
[Evolution] Error: Cannot create the specified folder: Generic error...
I am getting an error when trying to create a new mbox "folder" via remote IMAP. Is this a known issue? -- +-- T h e C o o p . n e t --+ | Drew Bertola Hosting - Colocation Tel: 408-738-8337 | | TheCoop.net Programming - Administration Mob: 408-887-0426 | | [EMAIL PROTECTED]Open Source Specialistshttp://thecoop.net | +---+ ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
Re: [Evolution] Upcoming Evo. 1.2 distribution support
On Thu, 2002-11-07 at 00:39, Greg Macek wrote: > I would like to know what the official stance will be on supported > distributions for the upcoming Evolution 1.2. I noticed that after > 1.2beta2, a 1.2RC1 release was not made for SuSE 7.3, the distro I > happen to be running on my home computer. I was testing it out on my > personal machine so I didn't have to interrupt my daily workflow with > any possible problems. > > Regardless, I am now left with a 1.2Beta2 running on there with no > upgrade path available to me right now. I'm not exactly sure why > development abruptly stopped for SuSE 7.3 during this, but it leaves me > hanging. Will there be a final 1.2 for 7.3? If not, why? Was there going > to be any official statements made as to distribution support? > > I read in the knowledge base that as of 9/11/02 about dropping support > for older distros over time. Perhaps with the recent release of SuSE 8.1 > you've decided to drop support for 7.3. Some warning or announcement > would be nice though. I run 7.3 pro on my work notebook and use > Evolution 1.0.8 exclusively for email. I was looking forward to moving > to 1.2 soon, but now I'm not so sure I'll be able. Please let me know > what the future holds for Evolution. Thanks. > > Pardon my rant. Just needed to write :-) > > - Greg The release notes for 1.2RC1 list supported distributions, including some for which support is planned in the near future, e.g. SuSE 8.1. As for some of the platforms for which 1.2RC1 will not be available... well, it's a beta, and the word "beta" implies certain caveats. We're not reducing our level of support for SuSE; we're just shifting it to a more recent set of versions. If you're willing to upgrade, you may want to consider that Evolution 1.2 will be available for SuSE 8.1 before Ximian Desktop will, so if you want both Evolution 1.2 and Ximian Desktop for SuSE, then you're pretty much limited to SuSE 8.1. If you're not willing to upgrade, and bugs in 1.2Beta2 make it worse than 1.0.8, you can downgrade to 1.0.8. -- Mark Gordon <[EMAIL PROTECTED]> ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
Re: [Evolution] Font display problems redux
On Sat, 2002-11-09 at 02:21, Larry Underhill wrote: > I have recently had the joy of switching my wife's computer over to > linux. I too am running Redhat 8.0 on that machine with 1.0.8 > Evolution and I'm using the MS webfonts as well. I have the same exact > problem as described by Cliff. As others have said on this list, I have the MS web fonts installed and do not experience any of the problems you or others have posted. It does seem that everyone who has posted with this problem is using RH 8.0 - at least that's my recollection - so perhaps this is a RH 8.0 specific issue? Perhaps posting to a Red Hat list might be more help? Best, Darren -- == D. D. Brierton[EMAIL PROTECTED] www.dzr-web.com Trying is the first step towards failure (Homer Simpson) == ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
Re: [Evolution] Debugging LDAP queries?
Hmm, the only server I can find that generates ADMIN_LIMIT_EXCEEDED (error 11) is netscape directory server - it's generated when the "look through limit" is exceeded while building a list of candidate matches. here's the blurb from the documentation: Look Through Limit in Entries Description Specifies the maximum number of entries that ns-slapd will check when seeking candidate entries in response for a search request. If this limit is reached, ns-slapd returns any entries it has located that match the search request, as well as an exceeded size limit error. For a general discussion of the searching algorithm, refer to "The Searching Algorithm". >From the above it sounds like it's similar to the search size limit, only it's used at the start of the search as opposed to the end. Regardless, it sounds like there's too many possible candidates (probably due to the complexity of the query, or just the number of ORs in the query.) and the first n candidates (where n = look through limit) don't match the query. If you have the ldapsearch command locally, try this: $ ldapsearch -h -x -b -s '(|(displayName=had*)(mail=had*)(|(cn=had*)(sn=had*))(fileAs=had*))' dn and see if that works. If you have access to the server's slapd.conf file (or the directory admin's ear) see if you can find out what the lookthroughlimit is set to. at present there's not much we can do as far as simplifying that query. The really yucky fileAs/sn part is caused by the ldap backend, and is expanded from queries on the fileAs attribute (since on entries with fileAs we want to use that, but on entries without it we want to use sn), and we might be able to just replace that big mess with (fileAs=had*) in certain instances (where sn is already in the query.) Chris On Fri, 2002-11-08 at 08:49, Bob Haddleton wrote: On Thu, 2002-11-07 at 17:59, Chris Toshok wrote: > If you do killev, then run wombat from a terminal and watch it's output > you'll see the query that's sent to the ldap server (as well as the > result code the server sends back.) Here's what I got: wombat-Message: Starting wombat Wombat up and running wombat-pas-Message: libldap vendor/version: OpenLDAP 2.00.11 wombat-pas-Message: extensions present: wombat-pas-Message: X_OPENLDAP wombat-pas-Message: X_OPENLDAP_V2_REFERRALS wombat-pas-Message: TLS not available (ldap_error 0x5c) wombat-pas-Message: supported server control: 2.16.840.1.113730.3.4.2 wombat-pas-Message: supported server control: 2.16.840.1.113730.3.4.3 wombat-pas-Message: supported server control: 2.16.840.1.113730.3.4.4 wombat-pas-Message: supported server control: 2.16.840.1.113730.3.4.5 wombat-pas-Message: supported server control: 1.2.840.113556.1.4.473 wombat-pas-Message: supported server control: 2.16.840.1.113730.3.4.9 wombat-pas-Message: supported server control: 2.16.840.1.113730.3.4.12 wombat-pas-Message: supported SASL mechanism: EXTERNAL searching server using filter: (| (displayName=had*) (mail=had*) (|(cn=had*)(sn=had*)) (|(fileAs=had*)(&(!(fileAs=*))(sn=had*))) ) wombat-pas-WARNING **: search returned 11 Every query that is attempted returns "11". Anything else I can look at? Thanks! -- Bob Haddleton [EMAIL PROTECTED] ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
Re: [Evolution] Font display problems redux
I have recently had the joy of switching my wife's computer over to linux. I too am running Redhat 8.0 on that machine with 1.0.8 Evolution and I'm using the MS webfonts as well. I have the same exact problem as described by Cliff. I have observed the following: 1. HTML adverts from say, Amazon will not display text. If I toggle the 'load images' selection, then I get the images to load in the html email, but still no text. 2. Random messages from friends do not display the text in the email. If I hit 'reply' then I I can view the text. The only somewhat consistent thing that I have found is: a) the MUA from the offending sender is Outlook Express (5/6) b) the sender is sending me a new mail -- not replying or forwarding. However, this is not 100%... more like 90%. I have a pretty stock install of Redhat 8.0 on this machine. I chose the 'workstation' option during the install process and I am running GNOME rather than KDE. If I can provide more relevant info, I'll be happy to. I've managed to get my spouse to run RH 8.0, but somehow I can't convince her that mutt is really cool and that writing your own perl scripts to query the ldap server is fun ;) If I get this fixed, she will be real happy. Cheers, Larry Underhill "He is a very tainted fellow and full of wickedness." On Wed, Nov 06, 2002 at 03:21:40PM -0800, Cliff Wells wrote: > On Wed, 2002-11-06 at 15:09, Steven Tryon wrote: > > I could see it in the preview pane, but it was blank in a > > print/preview. I've seen (or, perhaps, not seen) a couple of other > > messages like these. > > My problem is the opposite: I can see it in print preview (or if I > choose to reply/forward the message) but not in the message pane. > > > -- > Cliff Wells, Software Engineer > Logiplex Corporation (www.logiplex.net) > (503) 978-6726 x308 (800) 735-0555 x308 > > > ___ > evolution maillist - [EMAIL PROTECTED] > http://lists.ximian.com/mailman/listinfo/evolution -- ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
Re: [Evolution] Cannot add/edit entries of LDAP Addressbook
Raphael and I have been bouncing mail back and forth privately on this, but I figured I'd respond to the list with the solution I just found. The trouble is that evolution only queries the RootDSE when it opens the connection, and some ldap servers are configured such that you need to be authenticated to read anything, including attributes of the RootDSE (like the subschema's dn). For instance, in the comments of my openldap 2.0.25 slapd.conf here is the following acl: #access to * # by self write # by users read # by anonymous auth If this acl is used alone, you'll find yourself unable to create/edit contacts. A fix for this would be to query the root dse again after we've authenticated. The only trouble with this setup is that it makes querying the authentication capabilities (sasl mechs) of the server impossible before we've authenticated. Anyway, I'm filing a bug about the RootDSE-query-after-auth thing, but in the meantime if you find that all your contact editor fields are greyed out even after you authenticate, make sure you ldap server has the following two ACL's listed: access to dn="" by * read access to dn="cn=Subschema" by * read Chris On Fri, 2002-11-08 at 03:17, Raphael Vallazza wrote: > Hi! > > I have a problem with my LDAP addressbook. I connot add nor edit > entries, because the fields are greyed out. The strange thing is that if > i click on the "Full Name" button of the Contact Editor i can enter the > name of the person, and then i can even save it! The other fields remain > grayed out. The permissions of the LDAP server are ok, because i can use > any other ldap client to modify/add/delete entries in that > organizational unit. > > This problem was already reported on bugzilla: > http://bugzilla.ximian.com/show_bug.cgi?id=25540 > http://bugzilla.ximian.com/show_bug.cgi?id=28820 > > but has never been solved. > > Does anyone know how to solve or workaround the problem? > > Regards > Raphael > > > ___ > evolution maillist - [EMAIL PROTECTED] > http://lists.ximian.com/mailman/listinfo/evolution ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
Re: [Evolution] JPEGs from a Mac OS X
fre, 2002-11-08 kl. 21:42 skrev Gregory Alan Kedrovsky: > > Seems to me it's a coding config problem. Does anyone know what might be > > the problem? He says he can send the same pic to his WinTel machine (via > > Juno, another dial-up he has) and it comes through fine in WinDoze. > Tell him he'll be doing you a real favor by sending it as a .zip file > (do Macs have zip?) gzip -d or gunzip it. > Really?? Is that the best answer to the problem?? You sound like you've > bumped into this one before. And, there's no other fix for it? Is there > a reason it happens? To be honest, I've no idea. But what he's sending you will be 7-bit encoded one way or the other. The best bet is base64 that's gone wrong somewhere - you hinted at the same yourself. And yes, I have something to do with anti-virus and anti-spam shit and how to deal with those things in smtp mail, even base64 coded and suchlike. You never know, it might work. > Tell him that, come the spring, you'll mow the lawn for him. > I told him. But, I bet he doesn't hold his breath. We live just about 1 > hemisphere apart. :-) 'Spect he'll pay the plane ticket :c) Best, Tony -- Tony Earnshaw So mangt eit ord kunde vori usagt. e-post: [EMAIL PROTECTED] www:http://www.billy.demon.nl ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
Re: [Evolution] JPEGs from a Mac OS X
On Fri, 2002-11-08 at 12:19, Gregory Alan Kedrovsky wrote: > My Evolution 1.0.8 won't receive a binary file (jpeg picture) sent from > a Mac OS X (using UUEncoding?). > You did a uudecode right? Ah the good old times when mail was run via uucp. Read something about the history of the Internet, there you will find uuencode and uudecode. Hope this helps, Ronald > My Dad just made the switch from a WinTel machine to a blowtorch of a > Mac (it's really sweet). He's still climbing the learning curve, so > we've hit a hitch we can't get over. He attaches a jpeg picture (he's a > huge railfan, likes trains) to an e-mail and sends it to me. > > It comes in and I can't do ANYthing with it. I see the attachment. I > cannot view it in The GIMP, Electric Eyes... nothing. I save it to disk, > and it saves, but when I try to pull it up, I get "Unknown." But, it's a > standard JPEG. > > Seems to me it's a coding config problem. Does anyone know what might be > the problem? He says he can send the same pic to his WinTel machine (via > Juno, another dial-up he has) and it comes through fine in WinDoze. > > Thanks! > -Greg ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
Re: [Evolution] JPEGs from a Mac OS X
> Seems to me it's a coding config problem. Does anyone know what might be > the problem? He says he can send the same pic to his WinTel machine (via > Juno, another dial-up he has) and it comes through fine in WinDoze. Tell him he'll be doing you a real favor by sending it as a .zip file (do Macs have zip?) gzip -d or gunzip it. Really?? Is that the best answer to the problem?? You sound like you've bumped into this one before. And, there's no other fix for it? Is there a reason it happens? Tell him that, come the spring, you'll mow the lawn for him. I told him. But, I bet he doesn't hold his breath. We live just about 1 hemisphere apart. :-) THANKS! -Greg -- My Penguin wears a Red Hat. http://www.greg-and-sue.com/screenshot.jpg - e-mail: [EMAIL PROTECTED] - e-mail (alt): [EMAIL PROTECTED] - church site: www.iglesia-del-este.com - personal site: www.greg-and-sue.com ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
Re: [Evolution] JPEGs from a Mac OS X
fre, 2002-11-08 kl. 20:19 skrev Gregory Alan Kedrovsky: > Seems to me it's a coding config problem. Does anyone know what might be > the problem? He says he can send the same pic to his WinTel machine (via > Juno, another dial-up he has) and it comes through fine in WinDoze. Tell him he'll be doing you a real favor by sending it as a .zip file (do Macs have zip?) gzip -d or gunzip it. Tell him that, come the spring, you'll mow the lawn for him. Best, Tony -- Tony Earnshaw So mangt eit ord kunde vori usagt. e-post: [EMAIL PROTECTED] www:http://www.billy.demon.nl ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
Re: [Evolution] SuSE 8.1 Support when?
Paul - Sorry about any confusion, yes the Evo release notes say "soon" for SuSE 8.1 and due to some unrelated issues, the Release Candidate 1 was not pushed for SuSE 8.1. We will release the final version of Evolution 1.2 for SuSE 8.1. Thanks, -Christine On Fri, 2002-11-08 at 06:39, Paul Hands wrote: Hi, The XImian web site says that support for SuSE 8.1 will be announced "soon". Has anyone a clearer idea of when "soon" is? I fully expect the usual, humorous (well, almost) answers, but I'm hoping for a date. The reason i ask is that I'm using the 1.2RC1 client of both evo and connector on SuSE 8.1, and they seem to work, but because of a libpng version issue, I get a lot of error messages :- libpng warning: Application was compiled with png.h from libpng-1.0.12 libpng warning: Application is running with png.c from libpng-1.2.4 and if I try the help:about evolution menu pick, the whole thing dies with an assertion :- evolution-shell-ERROR **: file e-shell-about-box.c: line 270 (impl_realize): assertion failed: (background_pixbuf != NULL) I thought I'd download the source and try compiling it, but I can't get configure to work - it keeps complaining about GTK not being installed, or having been moved. Neither of these things is true, so I'm just about to give up on compilation as an option, hence the subject question. Paul
[Evolution] JPEGs from a Mac OS X
My Evolution 1.0.8 won't receive a binary file (jpeg picture) sent from a Mac OS X (using UUEncoding?). My Dad just made the switch from a WinTel machine to a blowtorch of a Mac (it's really sweet). He's still climbing the learning curve, so we've hit a hitch we can't get over. He attaches a jpeg picture (he's a huge railfan, likes trains) to an e-mail and sends it to me. It comes in and I can't do ANYthing with it. I see the attachment. I cannot view it in The GIMP, Electric Eyes... nothing. I save it to disk, and it saves, but when I try to pull it up, I get "Unknown." But, it's a standard JPEG. Seems to me it's a coding config problem. Does anyone know what might be the problem? He says he can send the same pic to his WinTel machine (via Juno, another dial-up he has) and it comes through fine in WinDoze. Thanks! -Greg -- My Penguin wears a Red Hat. http://www.greg-and-sue.com/screenshot.jpg - e-mail: [EMAIL PROTECTED] - e-mail (alt): [EMAIL PROTECTED] - church site: www.iglesia-del-este.com - personal site: www.greg-and-sue.com ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
Re: [Evolution] Debugging LDAP queries?
On Thu, 2002-11-07 at 17:59, Chris Toshok wrote: > If you do killev, then run wombat from a terminal and watch it's output > you'll see the query that's sent to the ldap server (as well as the > result code the server sends back.) Here's what I got: wombat-Message: Starting wombat Wombat up and running wombat-pas-Message: libldap vendor/version: OpenLDAP 2.00.11 wombat-pas-Message: extensions present: wombat-pas-Message: X_OPENLDAP wombat-pas-Message: X_OPENLDAP_V2_REFERRALS wombat-pas-Message: TLS not available (ldap_error 0x5c) wombat-pas-Message: supported server control: 2.16.840.1.113730.3.4.2 wombat-pas-Message: supported server control: 2.16.840.1.113730.3.4.3 wombat-pas-Message: supported server control: 2.16.840.1.113730.3.4.4 wombat-pas-Message: supported server control: 2.16.840.1.113730.3.4.5 wombat-pas-Message: supported server control: 1.2.840.113556.1.4.473 wombat-pas-Message: supported server control: 2.16.840.1.113730.3.4.9 wombat-pas-Message: supported server control: 2.16.840.1.113730.3.4.12 wombat-pas-Message: supported SASL mechanism: EXTERNAL searching server using filter: (| (displayName=had*) (mail=had*) (|(cn=had*)(sn=had*)) (|(fileAs=had*)(&(!(fileAs=*))(sn=had*))) ) wombat-pas-WARNING **: search returned 11 Every query that is attempted returns "11". Anything else I can look at? Thanks! -- Bob Haddleton [EMAIL PROTECTED] ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
Re: [Evolution] reading / writing mail with Japanese fonts(iso-2022-jp)...
On Thu, 2002-11-07 at 22:33, Thomas O'Dowd wrote: > As for kinput2 not working. It works for me but of course it gets > displayed as when I convert something. Andrew, why are you killing > kinput2 all the time. I start it once as lots of my apps use it. You > might want to check that you have XMODIFIERS set. Something like... > > LANG=en_US LC_CTYPE=ja_JP LC_MESSAGES=en_US XMODIFIERS="@im=kinput2" > evolution. No joy on RH 8.0. Maybe I have to take it up with them. It seems that 1.0.8 worked w/ 7.3, but not with 8.0. I installed support for both en_US and ja_JP. Then again, mutt works great with iso-2022-jp and kinput2 (at least inside gnome-terminal w/ emacs -nw as editor). So, what's the difference in language support infrastructure? -- +-- T h e C o o p . n e t --+ | Drew Bertola Hosting - Colocation Tel: 408-738-8337 | | TheCoop.net Programming - Administration Mob: 408-887-0426 | | [EMAIL PROTECTED]Open Source Specialistshttp://thecoop.net | +---+ ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
[Evolution] is red-carpet broken or is it really that quiet
I subscribe to the evo dev snapshot (among other channels) which usually means a new version most days ... however, there hasn't been anything to update in more than a week ... Is it really that quiet out there or has something broken? ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
[Evolution] strange behaviour in vFolder editor
Hi, Does anybody else notice this? When I open the vFolder editor the rules are listed in the order they were created, which often doesn't match the order of the vFolders in the Folder list. (This is probably not strange behaviour but could they be listed in the same order?) So when I try to move the filters so they are in the same order the move up and move down buttons behave very strange: the first time the move up button is pressed the selected filter is moved one position up, like it should. But the second time the filter is moved *down* instead of up! The only way to move a filter more than 1 position up is by moving the filter directly above it down until the filter is in the desired position... Should I file this as a bug? (And the first part as a feature request?) Regards -- # Mertens Bram "M8ram" <[EMAIL PROTECTED]> Linux User #249103 # # Red Hat Linux 7.3 KDE 3.0.0-10 kernel 2.4.18-3 i686 128MB RAM # ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
Re: [Evolution] Cannot add/edit entries of LDAP Addressbook
On Fri, 2002-11-08 at 03:17, Raphael Vallazza wrote: > Hi! > > I have a problem with my LDAP addressbook. I connot add nor edit > entries, because the fields are greyed out. The strange thing is that if > i click on the "Full Name" button of the Contact Editor i can enter the > name of the person, and then i can even save it! The other fields remain > grayed out. The permissions of the LDAP server are ok, because i can use > any other ldap client to modify/add/delete entries in that > organizational unit. > > This problem was already reported on bugzilla: > http://bugzilla.ximian.com/show_bug.cgi?id=25540 > http://bugzilla.ximian.com/show_bug.cgi?id=28820 > > but has never been solved. > > Does anyone know how to solve or workaround the problem? which version of evolution are you running? (the versions in the bugs above are 1.0.5 and 1.0.8 respectively). evolution queries the ldap server when it opens the connection (and also after you authenticate if the open-time query failed) for schema information. It bases the editable fields on what your server has - if you aren't loading schemas that define 'top', 'person', 'organizationalPerson', 'inetOrgPerson', and 'calEntry' 'evolutionPerson', fields the fields will be greyed out. The fact that the fields are editable in the full name dialog while being uneditable in the main dialog a bug. Chris ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
[Evolution] SuSE 8.1 Support when?
Hi, The XImian web site says that support for SuSE 8.1 will be announced "soon". Has anyone a clearer idea of when "soon" is? I fully expect the usual, humorous (well, almost) answers, but I'm hoping for a date. The reason i ask is that I'm using the 1.2RC1 client of both evo and connector on SuSE 8.1, and they seem to work, but because of a libpng version issue, I get a lot of error messages :- libpng warning: Application was compiled with png.h from libpng-1.0.12 libpng warning: Application is running with png.c from libpng-1.2.4 and if I try the help:about evolution menu pick, the whole thing dies with an assertion :- evolution-shell-ERROR **: file e-shell-about-box.c: line 270 (impl_realize): assertion failed: (background_pixbuf != NULL) I thought I'd download the source and try compiling it, but I can't get configure to work - it keeps complaining about GTK not being installed, or having been moved. Neither of these things is true, so I'm just about to give up on compilation as an option, hence the subject question. Paul
[Evolution] Cannot add/edit entries of LDAP Addressbook
Hi! I have a problem with my LDAP addressbook. I connot add nor edit entries, because the fields are greyed out. The strange thing is that if i click on the "Full Name" button of the Contact Editor i can enter the name of the person, and then i can even save it! The other fields remain grayed out. The permissions of the LDAP server are ok, because i can use any other ldap client to modify/add/delete entries in that organizational unit. This problem was already reported on bugzilla: http://bugzilla.ximian.com/show_bug.cgi?id=25540 http://bugzilla.ximian.com/show_bug.cgi?id=28820 but has never been solved. Does anyone know how to solve or workaround the problem? Regards Raphael ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
Re: [Evolution] red-carpet on Solaris just stopped working... newdistributions.xml file at fault?
I'm not sure if it's really a bug. I looked at the source and best I
can figure out it crashed because when it called the distribution file
parser it didn't get back a single response (I'm not sure how it handled
getting a double response as I didn't run a debugger on it) and didn't
check that it had a proper response before it went on to use it. It's a
bug to assume you get a correct response from a routine that should
return correct responses, or for the routine to only expect one entry
per OS in that XML file? Both seem fine assumptions to me, since you
have control of both... Maybe a little better error handling would be
good, but if you always checked everything we'd all run out of disk
space very fast =O{ I imagine though that a bit of careful dicking with
the distributions.xml file and some DNS poisoning to get someone's
red-carpet to read your file rather than the official one, on top of
red-carpet always being run as root could be a problem though... Maybe
it should be seen as a security issue?
Mark.
On Tue, 2002-11-05 at 17:18, Benjamin Kahn wrote:
> Mark,
> Ah. Interesting. That sounds like a bug. Can you file it in
> http://bugzilla.ximian.com/ ? Also, we have Solaris support back up
> now. Sorry for the problem.
>
> On Tue, 2002-11-05 at 11:14, Mark R. Bowyer wrote:
> > Sorry - I should of mentioned that. With my fake uname library in
> > place, I do indeed get that dialogue box. But to try to catch a truss
> > or some better idea of why it thought I was now wrong, I was running it
> > by hand without the wrapper script to get that crash...
> >
> > Sorry I left this out.
> >
> > Mark.
> >
> > On Tue, 2002-11-05 at 16:09, Benjamin Kahn wrote:
> > > Mark,
> > > Thanks for the report. You're right. Something is wonky for Solaris
> > > 8. We'll have this fixed in a few hours.
> > >
> > > (On a real Solaris 8 box, you should have gotten a dialog box telling
> > > you that the distribution wasn't supported instead of the crash.) It'll
> > > be back being supported some time today.
> > >
> > > On Tue, 2002-11-05 at 08:22, Mark R. Bowyer wrote:
> > > > Hi,
> > > >
> > > > I'm getting the following error from red-carpet as of this morning:
> > > >
> > > > :
> > > > [cddb90]: Reading from the cache:
> > > > file:///var/cache/redcarpet/red-carpet.ximian.com:80/distributions.xml
> > > >
> > > >
> > > > libredcarpet-ERROR **: file rc-distro.c: line 733
> > > > (rc_distro_get_status): assertion failed: (system_distro)
> > > > aborting...
> > > > Abort (core dumped)
> > > >
> > > > A bit of research shows that the distributions.xml file (when ungzipped)
> > > > has two blocks at the top for Solaris 7 and 8, both marked
> > > > "internal", and then Solaris 7 and 8 both turn up again lower
> > > > down as retired and supported respectively, and 9 shown as
> > > > presupported. In all cases the same uname commands and responses are
> > > > shown for the block.
> > > >
> > > > As far as I can make out, no other OS shows the same version twice with
> > > > different statii (Latin was never my strong point ;O) and the
> > > > distributions file was updated last night... Can I surmise that these
> > > > "internal" blocks were left in by mistake, and are causing this problem,
> > > > or do I suddenly have a compatibility problem here?
> > > >
> > > > I should point out I'm actually running on a new Solaris 10 alpha build,
> > > > and am using a LD_PRELOADed uname-fixing library to get red-carpet to
> > > > work on it. Not supported, but worked nicely thank you up until now ;O)
> > --
> > o omailto:Moredhel@;earthling.net
> > /v\ark R. Bowyer http://www.bowyer.screaming.net[EMAIL PROTECTED]
> > `-' --
> > /"\
> > \ / ASCII Ribbon Campaign fingerprint = 7924 9E9E 7B91 225E B065
> > X Against HTML Mail 1024D/19BC72F6 39D0 551D ABE6 1514 0DC1
> > / \
> >
> >
--
o omailto:Moredhel@;earthling.net
/v\ark R. Bowyer http://www.bowyer.screaming.net[EMAIL PROTECTED]
`-' --
/"\
\ / ASCII Ribbon Campaign fingerprint = 7924 9E9E 7B91 225E B065
X Against HTML Mail 1024D/19BC72F6 39D0 551D ABE6 1514 0DC1
/ \
signature.asc
Description: This is a digitally signed message part
Re: [Evolution] reading / writing mail with Japanese fonts(iso-2022-jp)...
On Fri, 2002-11-08 at 15:39, Larry Ewing wrote: > On Fri, 2002-11-08 at 00:33, Thomas O'Dowd wrote: > > Hi Larry > > > > Could you suggest a font that works for Japanese? I tried everything on > > my system at this stage as far as I can tell. I managed to get Japanese > > to display using a font called efont but then normal ascii doesn't > > display. I have lots of other Japanese fonts installed but nothing else > > would display Japanese properly with 1.1.90 or earlier betas. This all > > used to work with 1.0.8 with the normal Helvetica/Courier combination > > specified in html viewer fonts. > > What is the xlfd of the font you were using before, and in particular > what encoding did you choose? What locale are you using? Presume you are talking about the xlfd name of the efont that I mentioned above that displayed only Japanese but no ascii. -efont-fixed-medium-r-normal-*-12-*-*-*-c-*-iso10646-1 There was no actual encoding choices on that font except for the default which was as above. my normal setting uses -adobe-courier-medium-r-normal-*-12-*-*-*-m-*-iso8859-1 as for locale stuff I didn't do anything special. I started evolution like below. LANG=en_US LC_CTYPE=ja_JP.eucjp LC_MESSAGES=en_US XMODIFIERS="@im=kinput2" evolution I also tried using ja_JP.utf8 but on starting I got the following message Gdk-WARNING **: locale not supported by Xlib, locale set to C and no Japanese was displayed at all. Currently I can see subjects/names in the message list summary pane but not in the preview pane or message window. Cheers, Tom. -- Thomas O'Dowd, CEO, Nooper.com - Mobile Services Inc., Tokyo, Japan i-mode & FOMA consulting, development, testing: http://nooper.co.jp/ ___ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
