Summary: | command line not working, but works in terminal | ||
---|---|---|---|
Product: | [Applications] ktimer | Reporter: | Rodrigo <rodrigo1406> |
Component: | general | Assignee: | A. Spehr <zahl> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | alexander.lohnau, barafu, bertyfogs+kdebugs, buttasudicio, c.jason.kim, cat.alucardo, egorov, kde |
Priority: | NOR | ||
Version: | 20.04 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/utilities/ktimer/commit/0be87585e6f9584a904d9a60bd3d03f9a8375c21 | Version Fixed In: | 20.04.3 |
Description
Rodrigo
2014-03-24 04:07:25 UTC
(In reply to Rodrigo from comment #0) > I put as command line: > > rhythmbox /home/path/to/file/some_music.mp3 Are you sure you use absolute path? I can't reproduce it with absolute path, but with tilde it really don't work. There is a problem with tilde expansion, looks like it is expanded to ktimer binary directory instead of user home. There is still a bug with the usage of QProcess in KTimer. As an example, I'm trying to start "/usr/bin/kate" with the KTimer which doesn't work. Played around with the code in void KTimerJob::fire(), startDetached(d->command) did it's work as proc->setProgram(d->command); and proc->start(); does. I am not that familiar with QProcess to get the issues on changing method, so perhaps anyone will do :) Same problem here. Manjaro, kde frameworks 5.69.0. Command line "kdialog --msgbox Timeout!" does not show a message. [2020-04-26T13:25:02-0500] [ALPM] upgraded ktimer (19.12.3-1 -> 20.04.0-1) mpv --volume=45 --length=5 --no-video music.mp3 ~fails terminal-of-choice -e "command" ~fails terminal-of-choice ~works kcalc ~works vlc ~works vlc music.mp3 ~fails echo "#!/bin/bash mpv --volume=45 --length=5 --no-video music.mp3" > ktimer-executable-script chmod 744 ktimer-executable-script ./ktimer-executable-script ~works! I have 2 versions of 19.x working and 2 of 20.x failing. It seems any space causes it to fail. Curiously, calibre crashed a few days earlier and I left the terminal open it appears to have caught some stuff from ktimer. Ktimer was not happy with "#!/bin/bash; mpv --volume=45 --length=5 --no-video music.mp3" kdeinit5: Got EXEC_NEW '/usr/lib/qt/plugins/kf5/kio/man.so' from launcher. kdeinit5: preparing to launch '/usr/lib/qt/plugins/kf5/kio/man.so' log_kio_man: STARTING log_kio_man: QUrl("man:mpv --volume=45 --length=45 --no-video /home/#/music/1st") log_kio_man: QUrl("man:!mpv --volume=45 --length=45 --no-video /home/#/music/1st") log_kio_man: QUrl("man:!/mpv --volume=45 --length=45 --no-video /home/#/music/1st") log_kio_man: QUrl("man:!/bmpv --volume=45 --length=45 --no-video /home/#/music/1st") log_kio_man: QUrl("man:!/bimpv --volume=45 --length=45 --no-video /home/#/music/1st") log_kio_man: QUrl("man:!/binmpv --volume=45 --length=45 --no-video /home/#/music/1st") log_kio_man: QUrl("man:!/bin/mpv --volume=45 --length=45 --no-video /home/#/music/1st") log_kio_man: QUrl("man:!/bin/bmpv --volume=45 --length=45 --no-video /home/#/music/1st") log_kio_man: QUrl("man:!/bin/bampv --volume=45 --length=45 --no-video /home/#/music/1st") log_kio_man: QUrl("man:!/bin/basmpv --volume=45 --length=45 --no-video /home/#/music/1st") log_kio_man: QUrl("man:!/bin/bashmpv --volume=45 --length=45 --no-video /home/#/music/1st") log_kio_man: QUrl("man:!/bin/bash;mpv --volume=45 --length=45 --no-video /home/#/music/1st") log_kio_man: QUrl("man:!/bin/bash; mpv --volume=45 --length=45 --no-video /home/#/music/1st") log_kio_man: QUrl("man:!/bin/bash; mpv --volume=45 --length=5 --no-video /home/#/music/1st") log_kio_man: Done kdeinit5: PID 1507273 terminated. ^C Im just using 19.x A possibly relevant merge request was started @ https://invent.kde.org/utilities/ktimer/-/merge_requests/1 Git commit 0be87585e6f9584a904d9a60bd3d03f9a8375c21 by Laurent Montel, on behalf of Alexander Lohnau. Committed on 17/06/2020 at 20:38. Pushed by mlaurent into branch 'release/20.04'. Fix command lines with arguments M +1 -1 ktimer.cpp https://invent.kde.org/utilities/ktimer/commit/0be87585e6f9584a904d9a60bd3d03f9a8375c21 *** Bug 424349 has been marked as a duplicate of this bug. *** |