[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed

2020-08-17 Thread David Jarvie
https://bugs.kde.org/show_bug.cgi?id=358027 David Jarvie changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because:

[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed

2016-02-23 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358027 --- Comment #16 from tuk...@gmail.com --- As I said before I though this could be the case. Thank you for your help and sorry for the mix-ups again. I will forward this to Debian. -- You are receiving this mail because: You are watching all bug

[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed

2016-02-21 Thread David Jarvie via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358027 David Jarvie changed: What|Removed |Added Status|CONFIRMED |RESOLVED

[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed

2016-02-05 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358027 --- Comment #10 from tuk...@gmail.com --- All files are present and seem to be OK. I have found an issue though. if I run `kalarmautostart kalarm --tray` manually after closing my running instance of kalarm then nothing happens, the command just seems

[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed

2016-02-05 Thread David Jarvie via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358027 --- Comment #12 from David Jarvie --- I forgot to say that kalarmautostart is designed to hang for 30 seconds before starting kalarm. Please confirm whether it hangs for longer than that. -- You are receiving this mail because: You

[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed

2016-02-05 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358027 --- Comment #13 from tuk...@gmail.com --- It hangs for what is probably 30 seconds then exits with an error before terminating: kalarmautostart(14710) AutostartApp::slotAutostart: No command line kalarm is not open afterwards. -- You are receiving

[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed

2016-02-05 Thread David Jarvie via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358027 --- Comment #14 from David Jarvie --- It's definitely a bug getting that error message after typing 'kalarmautostart kalarm --tray'. I won't be able to investigate for a week or so, but I'll look at it after that. -- You are

[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed

2016-02-05 Thread David Jarvie via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358027 David Jarvie changed: What|Removed |Added Resolution|WAITINGFORINFO |---

[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed

2016-02-03 Thread David Jarvie via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358027 --- Comment #9 from David Jarvie --- The file /usr/share/autostart/kalarm.autostart.desktop should start KAlarm at login, provided that in KAlarm's config file (~/.kde/share/config/kalarmrc or ~/.config/kalarmrc or similar), the

[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed

2016-02-02 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358027 --- Comment #8 from tuk...@gmail.com --- The command you asked me to run shows no kalarm instances when I disable my startup script. I have verified that most of my KDE applications are running from my startup scripts - is it possible I am missing a KDE

[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed

2016-02-01 Thread David Jarvie via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358027 David Jarvie changed: What|Removed |Added Resolution|LATER |WAITINGFORINFO --- Comment #7

[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed

2016-02-01 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358027 --- Comment #6 from tuk...@gmail.com --- Hi David, the command you asked me to run only shows a running "kalarm" (no arguments). The reason for this is that I am using a startup script that runs kalarm like that from ~/.config/autostart-scripts/ . I am

[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed

2016-01-28 Thread David Jarvie via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358027 David Jarvie changed: What|Removed |Added Resolution|--- |LATER

[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed

2016-01-16 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358027 --- Comment #2 from tuk...@gmail.com --- kalarm --tray makes it initialize without the main window, as you would expect. I have closed kalarm and ran it both with and without --tray to make sure it was working properly. This is such a minor issue, as I

[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed

2016-01-16 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358027 --- Comment #3 from tuk...@gmail.com --- Typos made my last comment barely understandable so to clarify: --tray works fine but anyway it would be nicer to have kalarm behave more like the other apps I mention or offer a "open to tray" user setting.

[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed

2016-01-15 Thread David Jarvie via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358027 --- Comment #1 from David Jarvie --- Can you please quit KAlarm (using menu item File -> Quit when there are no alarm windows visible), and then start it using the following command: kalarm --tray Does this start KAlarm with the main