Bug 176150

Summary:	run command in konsole notifications has problems
Product:	[Applications] konsole	Reporter:	S. Umar <sait.a.umar>
Component:	general	Assignee:	Konsole Bugs <konsole-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	yoyo
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description S. Umar 2008-11-26 17:38:11 UTC

Version:            (using KDE 4.1.3)
Compiler:          gcc-4.3.0 
OS:                Linux
Installed from:    Fedora RPMs

I always had problems with konsole notifications working with
the KDE sound system (all other notifications are working).

Instead I run a command for some notifications such as:

play -q /usr/share/sounds/KDE_Beep_ShortBeep.wav

The command itself works fine if executed in the konsole, but
produces no sound from konsole notifications. If I examine
the .xsession-errors file I see the following:

/bin/sh: play%20-q%20/usr/share/sound /KDE_Beep_ShortBeep.wav: No such file or directory

(all in one line of course). So either blanks are replaced
by the %20 and the whole command looks continuous or
something else (I am using UTF-8 as default encoding).

I can trick it by putting the above command into a file
called "beep" in /usr/bin and just giving that as the command and it works.

Comment 1 Jozef Šiška 2009-02-06 15:13:31 UTC

I have the same problem with kopete notifications. It seems that the command in the "Run command" entry in notifications gets url-ified or something:

Using someting with spaces ( "xmessage test", without the quotes) gets:
/bin/sh: xmessage%20test: command not found

If there is a space at the end of the command it gets replaced with %20 even in the dialog. Also using / in the beginnig creates a file:// prefix:

bin/sh: file:///home/yoyo/bin/dumb_kopete_new_msg_notification: No such file or directory

( the command was "/home/yoyo/bin/dumb_kopete_new_msg_notification" )

This is with KDE compiled from svn r918146 (2009-01-29)

Comment 2 S. Umar 2009-02-06 15:24:24 UTC

Is it KDE 4.1 branch from SVN? or 4.2 branch? I have not tested it but I
think I saw commits in 4.2 branch that may have solved this problem.

Comment 3 Jozef Šiška 2009-02-06 16:25:49 UTC

Nevermind, I should have done more searching before...
It is bug 168968, the patch was merged yesterday, thanks for the pointer.

Comment 4 S. Umar 2009-02-06 18:07:42 UTC

Yes, that is the one. I updated from svn too.

Comment 5 Kurt Hindenburg 2010-06-02 15:19:14 UTC

Works here now  under KDE 4.4.x