Description of problem: Osmo does not open a new message window in my email client (using Gmail IMAP accounts) Email client: Sylpheed Email accounts: 2 Gmail IMAP accounts PIM: Osmo Osmo: general preferences: Helpers: E-mail client: xdg-email %s (cannot be changed) Version-Release number of selected component (if applicable): Osmo 0.2.10 How reproducible: Always Steps to Reproduce: 1. I click on a contact email link in Osmo contact tab. 2. A window selection opens: choice a: access Gmail through the browser, choice b: Sylpheed (default email client on Fedora LXDE spin). 3. I select Sylpheed. Actual results: The Sylpheed main GUI opens only. It does not open a new message window with the address of my contact. Expected results: Clicking on a Osmo contact email address links should open a new message window in my default email client with my default IMAP account selected. Additional info: With my current configuration (default), Osmo can only open a new message window using the Gmail web browser interface. Using the web interface does not allow me to select what IMAP account to use (unless to log-off/in).
Created attachment 471967 [details] link to (window selection Added info; when I click on a contact's email address link, in Osmo, it opens a selection window in my web browser (see: attachment print-screen). The same selection window opens when I click a "link to:" link, on a web page. Forgive my ignorance, but it might actually not be a Osmo bug? It is more likely the xdg-email command missing some arguments to be effective with Sylpheed. In summary "LXDE Fedora Spin: FF & Osmo can not open 'a new email message window' in Sylpheed" (at least on my configuration -- 2 notebooks runing F13 LXDE, and F14 LXDE). Can somebody advise what type of bug report I should open? Thank you.
This is definitely an xdg-utils problem, reassigning. Can you please add the version of the package? There was an update that adds some features for LXDE, but I doubt it fixes sylpheed. BTW: (In reply to comment #0) > Osmo: general preferences: Helpers: E-mail client: xdg-email %s (cannot be > changed) You can change it if you hit return in the input field after changing it. Not very intuitive, I know, I have already complained to the author.
Christoph, it's xdg-utils-1.0.2, on F13 LXDE. In Osmo, I have changed 'xdg-email s%' for 'sylpheed s%' (thanks for the return key tip). Unfortunately, the result is the same. When I click a link in my contacts, it opens the Sylpeed main GUI (and not a new message with my contact email, and the email of my default account). You use LXDE too. How do you make osmo contacts work with sylpeed? Do I need to add something after the 'sylspheed s%' part?
By the looks of examining output from 'sylpheed --help', it seems different from most other email clients in that it requires the option --compose [address] It would be preferable for sylpheed to match the general convention used by most other email clients and accept: sylpheed [address] otherwise, we'll have to include more client-specific hacks within xdg-utils (which is obviously sub-optimal). Any chance of that?
pinging sylpheed maintainer(s) for comment
(In reply to comment #4) > By the looks of examining output from 'sylpheed --help', it seems different > from most other email clients in that it requires the option --compose > [address] IMHO this is pretty much standard, same for Thunderbird and Evolution. IMHO xdg-utils should probably use something like exo-open from Xfce, an enhanced version of the fdo desktop file specification: $ cat /usr/share/xfce4/helpers/sylpheed.desktop [Desktop Entry] Version=1.0 Icon=sylpheed Type=X-XFCE-Helper Name=Sylpheed Name[ast]=Sylpheed ...snipped... Name[zh_TW]=Sylpheed StartupNotify=true X-XFCE-Binaries=sylpheed; X-XFCE-Category=MailReader X-XFCE-Commands=%B; X-XFCE-CommandsWithParameter=/usr/lib64/xfce4/exo-1/exo-compose-mail-1 sylpheed %B "mailto:%s"; But I guess this is outside the scope of this bug.
exo-open sounds like something xdg-utils should definitely learn about, thanks!
(In reply to comment #4) > By the looks of examining output from 'sylpheed --help', it seems different > from most other email clients in that it requires the option --compose > [address] at last :) setting 'sylpheed --compose %s' in the osmo preferences address my issue. Thanks Rex for the pointer. this is a suggestion: since a default Fedora LXDE (13, 14) installation does not allow a lambda user (me) to create a email by clicking on the email address of his contacst in Osmo, could this issue + the simple command string to modify in the osmo prefs. be documented somewhere (wiki, installation note), until the situation evolves?
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.