https://bugs.kde.org/show_bug.cgi?id=417108
--- Comment #10 from dolge...@informatik.uni-erlangen.de --- So for further evaluataion I ran 2 batch files: ################################################################# #!/bin/bash kalarm -c yellow -t 2020-03-10-15:00 --reminder 2D 'Test entry 1' kalarm -c yellow -t 2020-03-14-13:00 --reminder 2D 'Test entry 2' kalarm -c yellow -t 2020-03-18-16:00 --reminder 2D 'Test entry 3' kalarm -c yellow -t 2020-03-24-19:00 --reminder 2D 'Test entry 4' kalarm -c yellow -t 2020-03-30-21:00 --reminder 2D 'Test entry 5' kalarm ################################################################# and ################################################################# #!/bin/bash kalarm -c yellow -t 2020-03-10-15:00 --reminder 2D 'Test entry 1' & kalarm -c yellow -t 2020-03-14-13:00 --reminder 2D 'Test entry 2' & kalarm -c yellow -t 2020-03-18-16:00 --reminder 2D 'Test entry 3' & kalarm -c yellow -t 2020-03-24-19:00 --reminder 2D 'Test entry 4' & kalarm -c yellow -t 2020-03-30-21:00 --reminder 2D 'Test entry 5' & kalarm ################################################################# As you can see in the screen recordings attached above, the first one remained waiting while displaying the first imported entry. (This dialog was hiding somewhere in the background, you can easily overlook it.) Result: only the first entry was imported (The other two entries were already there before). The second script caused the first and last entry to be imported, the rest ignored. The expected (and previously familiar) behavior of n consecutive "kalarm -t" calls (without a final "&") would be the silent import of n events, as if they had been entered via the GUI. Am I wrong? Where to look for a crash trace? -- You are receiving this mail because: You are watching all bug changes.
