kmail 'run command' notification doesn't work right

Bug #366403 reported by Robin Sheat on 2009-04-24
Affects Status Importance Assigned to Milestone
kdepim (Fedora)
Won't Fix
kdepim (Ubuntu)

Bug Description

Binary package hint: kmail

When given a command to run on new mail, kmail attempts to execute 'file:///path/to/command' rather than /path/to/command. This doesn't work.

Information in this bug: and the 'ln -s / file:' work-around also works.

Description of problem:
kmail does not execute a notification command because it modifies its name

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. configure: kmail: settings -> configure notifications ->
 (new mail arrived) -> run program ....
2. get a mail

Actual results:
program not invoked

Expected results:
the opposite

Additional info:
~/.xsession-errors reveals that kmail tries to execute the URL string 'file:///my/command' instead of the '/my/command'. That's why a workaround exists: creating a symlink /file: --> /

Ok, I can confirm it. The interesting thing is that it appends file:// only when full path is specified - otherwise it's working as expected.

Changed in kdepim (Fedora):
status: Unknown → In Progress

This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. 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 '10'.

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 10'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 10 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:

Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.

Changed in kdepim (Fedora):
status: In Progress → Won't Fix
Harald Sitter (apachelogger) wrote :

Hi Robin!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.


Changed in kdepim (Ubuntu):
status: New → Invalid
Changed in kdepim (Fedora):
importance: Unknown → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.