[kalarm] [Bug 366562] Kalarm starts in non-KDE desktop environments...
https://bugs.kde.org/show_bug.cgi?id=366562 David Jarvie <djar...@kde.org> changed: What|Removed |Added Version Fixed In||16.08.1 Latest Commit||cc2d8bb39417b186bfe40470eba ||921a64ef6c6c8 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from David Jarvie <djar...@kde.org> --- This is now fixed, for KDE Applications 16.08.1 release, so that KAlarm won't autostart on non-KDE desktops if it has never been run. Unfortunately, the KDE conditional autostart mechanism just isn't compatible with other desktops. Commit cc2d8bb39417b186bfe40470eba921a64ef6c6c8 in kdepim. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 366562] Kalarm starts in non-KDE desktop environments...
https://bugs.kde.org/show_bug.cgi?id=366562 David Jarvie <djar...@kde.org> changed: What|Removed |Added Component|kalarmd |general --- Comment #1 from David Jarvie <djar...@kde.org> --- KAlarm is designed to autostart at login once it has been run, to ensure that alarms are not missed. But it shouldn't start if it has never been used, or if the user has explicitly disabled start-at-login for it. What version of KAlarm are you using? What you report may well have been fixed in version 2.11.6 (KDE Applications 16.04.1). The fix prevents KAlarm autostarting in non-KDE desktops if KAlarm's start-at-login is disabled. See https://forum.kde.org/viewtopic.php?f=229=131410. Please see further explanation of autostart in non-KDE desktops at https://bugs.kde.org/show_bug.cgi?id=357653. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 360023] kalarm crashes on startup
https://bugs.kde.org/show_bug.cgi?id=360023 David Jarvie <djar...@kde.org> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #6 from David Jarvie <djar...@kde.org> --- I raised a bug report for Debian about requiring timezoned. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822061. Closing this bug as "Downstream" since it's a distro packaging issue. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 334557] KAlarm doesn't respect localization variables.
https://bugs.kde.org/show_bug.cgi?id=334557 David Jarvie <djar...@kde.org> changed: What|Removed |Added Version|unspecified |2.10.7-ak -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 180051] [KDE4] Need a way to have default printer settings
https://bugs.kde.org/show_bug.cgi?id=180051 David Jarvie <djar...@kde.org> changed: What|Removed |Added CC||djar...@kde.org --- Comment #104 from David Jarvie <djar...@kde.org> --- Created attachment 100374 --> https://bugs.kde.org/attachment.cgi?id=100374=edit Patch to initialise Qt printer dialog with CUPS settings There is a Qt code review, https://codereview.qt-project.org/#/c/32127/, with a patch for initialising the Qt printer dialog with all the CUPS settings, including default printer, duplex mode and greyscale/colour. This worked for me with Qt 4.8.6. I attach a patch file obtained from this code review. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 365257] Columns in main window do not resize properly to fit their contents
https://bugs.kde.org/show_bug.cgi?id=365257 David Jarvie <djar...@kde.org> changed: What|Removed |Added Summary|Columns in main window are |Columns in main window do |not resizeable |not resize properly to fit ||their contents --- Comment #1 from David Jarvie <djar...@kde.org> --- The original comment is incorrect - the columns were not manually resizeable in KDE 4 either. The time and repetition columns are supposed to resize to fit their contents. However this does not always work properly, so that when times are shown as am/pm, the whole text is not shown (e.g. "07/08/16 06:50 P..."). -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 365257] New: Columns in main window are not resizeable
https://bugs.kde.org/show_bug.cgi?id=365257 Bug ID: 365257 Summary: Columns in main window are not resizeable Product: kalarm Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: djar...@kde.org Reporter: djar...@kde.org They were resizeable in KDE 4, but not in KDE 5. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 359163] Emails fail with "Invalid 'From' email address." message.
https://bugs.kde.org/show_bug.cgi?id=359163 David Jarvie <djar...@kde.org> changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdep |http://commits.kde.org/kdep |im/99b6b56dc21716ad872d268d |im/1ff59b185cb90b8f0045c3fc |3902f5836aee588d|fa73e7f5ba6541a5 --- Comment #17 from David Jarvie <djar...@kde.org> --- Git commit 1ff59b185cb90b8f0045c3fcfa73e7f5ba6541a5 by David Jarvie. Committed on 11/06/2016 at 17:08. Pushed by djarvie into branch 'KDE/4.14'. Bug 359163: Use current email address preference setting If an email alarm was configured to use a KMail sender ID but the current email sender address preference setting is to use a hard coded email address, KAlarm still used the KMail sender ID, and furthermore email sending failed with an error message if the ID was no longer valid. This fix makes KAlarm use the current email sender address preference setting, so that an invalid sender ID only causes an error if the current setting is to use the KMail sender ID. M +4-4kalarm/kamail.cpp http://commits.kde.org/kdepim/1ff59b185cb90b8f0045c3fcfa73e7f5ba6541a5 -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 359163] Emails fail with "Invalid 'From' email address." message.
https://bugs.kde.org/show_bug.cgi?id=359163 David Jarvie <djar...@kde.org> changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im/99b6b56dc21716ad872d268d ||3902f5836aee588d --- Comment #16 from David Jarvie <djar...@kde.org> --- Git commit 99b6b56dc21716ad872d268d3902f5836aee588d by David Jarvie. Committed on 11/06/2016 at 16:44. Pushed by djarvie into branch 'Applications/16.04'. Bug 359163: Use current email address preference setting If an email alarm was configured to use a KMail sender ID but the current email sender address preference setting is to use a hard coded email address, KAlarm still used the KMail sender ID, and furthermore email sending failed with an error message if the ID was no longer valid. This fix makes KAlarm use the current email sender address preference setting, so that an invalid sender ID only causes an error if the current setting is to use the KMail sender ID. M +4-4kalarm/kamail.cpp http://commits.kde.org/kdepim/99b6b56dc21716ad872d268d3902f5836aee588d -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 359163] Emails fail with "Invalid 'From' email address." message.
https://bugs.kde.org/show_bug.cgi?id=359163 --- Comment #15 from David Jarvie <djar...@kde.org> --- I realise that KAlarm should always use the current configuration setting for email sender address, so if an email address is typed in the "From" email configuration setting, that should be used even if the alarm was originally set up to use a KMail identity. If things are done correctly, the error you have seen will only happen if "Use KMail identities" is selected in the settings dialog. Note that this bug was not related to whether or not 'sendmail' was selected. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 359163] Emails fail with "Invalid 'From' email address." message.
https://bugs.kde.org/show_bug.cgi?id=359163 --- Comment #14 from David Jarvie <djar...@kde.org> --- To avoid any doubt, can you please confirm a couple of details: 1) You said that it worked correctly in FC18. Does this mean Fedora 18 (which included KDE 4.9)? 2) Has the fault occurred with new email alarms created on your current OS? And were they created using the alarm edit dialog? (This is to be sure that the fault doesn't only happen for alarms previously created in FC18, and that the faulty alarms were not created via the command line or other non-dialog methods.) -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 362962] New: On first run, calendars are read-only, and calendar files are not created
https://bugs.kde.org/show_bug.cgi?id=362962 Bug ID: 362962 Summary: On first run, calendars are read-only, and calendar files are not created Product: kalarm Version: 2.11.4-5ak Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: djar...@kde.org Reporter: djar...@kde.org KDE Frameworks 5.21 Plasma Workspace 5.5 KDE Applications 16.04 Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 359163] Emails fail with "Invalid 'From' email address." message.
https://bugs.kde.org/show_bug.cgi?id=359163 David Jarvie <djar...@kde.org> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #13 from David Jarvie <djar...@kde.org> --- I tried setting up my config similar to your emailidentities, but I still didn't see the fault, until I edited my calendar.ics to include the property X-KDE-KALARM-FLAGS:EMAILID\;30593973 for my email alarm. This wasn't present in my calendar, but I noticed that it is present in the calendar you attached previously in all but one email alarm. After adding that property the fault occurred. I'll need to investigate why your alarms contain that property. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 362508] freeze
https://bugs.kde.org/show_bug.cgi?id=362508 --- Comment #7 from David Jarvie <djar...@kde.org> --- Do you have all plasma workspace packages installed? It only froze for me when I had a partial plasma installation. After installing plasma workspace completely, it no longer freezes, even when I run it by a new user. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 359163] Emails fail with "Invalid 'From' email address." message.
https://bugs.kde.org/show_bug.cgi?id=359163 --- Comment #11 from David Jarvie <djar...@kde.org> --- I've tried using sendmail on a Fedora 23 system, with both a Plasma 5 desktop and an XFCE desktop, but KAlarm reported sending the email successfully. Do you have any KDE email identities configured? The config file containing them is ~/.kde/share/config/emailidentities. They would normally be set up by configuring them in KMail. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 362631] KAlarm icon is indistinct and unrecognisable at smaller sizes
https://bugs.kde.org/show_bug.cgi?id=362631 --- Comment #6 from David Jarvie <djar...@kde.org> --- I tried out the 24x24 chronometer icons. The 'chronometer' icon doesn't look obviously connected to KAlarm at all, and it's also completely different from the other chronometer icons. The basic idea might work in the system tray, with the normal kalarm icon being the same as chronometer-start but with the arrow in the middle removed (i.e. an empty circle). Since the normal status of KAlarm is to have alarms enabled, I don't think it's appropriate to show the arrow in the 'kalarm' icon. I don't see a suitable icon for kalarm-disabled or kalarm-partdisabled. For me, the chronometer-pause icon doesn't convey a disabled meaning if the normal 'kalarm' icon doesn't have the arrow in the middle. Perhaps some other variations on the same basic idea might work for these two icons, though. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 336738] time zone is miscalculated by 1 hour or ignored
https://bugs.kde.org/show_bug.cgi?id=336738 --- Comment #20 from David Jarvie <djar...@kde.org> --- Git commit af320ed5599cb0737c0601e26126c39e64780de0 by David Jarvie. Committed on 05/05/2016 at 22:08. Pushed by djarvie into branch 'master'. Fix KDateTime::isValid() for ClockTime values Fix KDateTime::isValid() wrongly returning invalid for an instance which is specified in ClockTime, if the date/time is invalid in the local time zone. Bug was due to QDateTime::isValid() working differently in Qt4 and Qt5. REVIEW: 127629 M +16 -0autotests/kdatetimetest.cpp M +11 -1src/kdecore/kdatetime.cpp http://commits.kde.org/kdelibs4support/af320ed5599cb0737c0601e26126c39e64780de0 -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 362555] He froze for just open the kmenu and start kalarm
https://bugs.kde.org/show_bug.cgi?id=362555 David Jarvie <djar...@kde.org> changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Jarvie <djar...@kde.org> --- *** This bug has been marked as a duplicate of bug 362508 *** -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 362508] freeze
https://bugs.kde.org/show_bug.cgi?id=362508 --- Comment #6 from David Jarvie <djar...@kde.org> --- *** Bug 362555 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 362508] freeze
https://bugs.kde.org/show_bug.cgi?id=362508 David Jarvie <djar...@kde.org> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #5 from David Jarvie <djar...@kde.org> --- This happens on a compiled from sources version also. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 362631] KAlarm icon is indistinct and unrecognisable at smaller sizes
https://bugs.kde.org/show_bug.cgi?id=362631 --- Comment #4 from David Jarvie <djar...@kde.org> --- Note that the kalarm-disabled and kalarm-partdisabled icons provided by the KAlarm package are only used in the system tray, whereas the kalarm icon (also provided by the KAlarm package, as well as Breeze) is used both in the system tray and as a general purpose application icon. If systray icons are always supposed to be black and white, perhaps the kalarm-disabled icon, which currently is monochrome to distinguish it from the coloured 'kalarm' icon, should be provided by Breeze as the normal icon with a big diagonal line through it. Just an idea. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 362631] KAlarm icon is indistinct and unrecognisable at smaller sizes
https://bugs.kde.org/show_bug.cgi?id=362631 --- Comment #2 from David Jarvie <djar...@kde.org> --- Yes, the KAlarm icon is used in the system tray as well. Note that KAlarm uses three variations of its icon in the system tray to indicate its status, with the following icon names: - 'kalarm': the normal icon, indicating that all alarms are enabled. - 'kalarm-disabled': indicates that all alarms are currently disabled. In the icons shipped with KAlarm, this is simply a monochrome version of the 'kalarm' icon. - 'kalarm-partdisabled': indicates that some alarms are currently disabled. In the icons shipped with KAlarm, this is the 'kalarm' icon with a small 'x' in the bottom right corner. If you run KAlarm and disable alarms, you will see that the system tray icon changes from the Breeze icon to one of the icons shipped in the KAlarm package. When alarms are re-enabled, the icon changes back to the Breeze icon. You can see the icons packaged with KAlarm at https://quickgit.kde.org/?p=kdepim.git=tree=502b1ab43c82229a48e214abc7bd3969e7e2f8df=13334822110ee656602e0f449faad1bb6a26500f=kalarm%2Fsrc%2Fpixmaps -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 362631] New: KAlarm icon is indistinct and unrecognisable at smaller sizes
https://bugs.kde.org/show_bug.cgi?id=362631 Bug ID: 362631 Summary: KAlarm icon is indistinct and unrecognisable at smaller sizes Product: Breeze Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: djar...@kde.org CC: kain...@gmail.com The KAlarm icon looks like just a greenish blob at smaller sizes, and gives no clue visually as to what it represents. Having seen it in the system tray in two different distros, I couldn't make out what it was. Finally I looked at it in git and discovered that it has a digital time shown inside the green disc. Even at 48x48 this is not all that distinct, so it's not surprising that it doesn't work at smaller sizes. Could you please look into modifying it so that it is actually recognisable at sizes between 32x32 and 16x16. I doubt if text inside the disc is capable of working at small sizes, so as far as I can see, it really needs a redesign. I'm the KAlarm author. Frameworks version 5.22. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 362508] freeze
https://bugs.kde.org/show_bug.cgi?id=362508 --- Comment #2 from David Jarvie <djar...@kde.org> --- Please describe what you did which made this happen. (How did you start KAlarm?) Which versions of KAlarm and of KDE/KDE Frameworks are you using? -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 361936] Kalarm startup warning: Time zones are not accessible
https://bugs.kde.org/show_bug.cgi?id=361936 --- Comment #2 from David Jarvie <djar...@kde.org> --- This has been reported to Debian - see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822061. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 336738] time zone is miscalculated by 1 hour or ignored
https://bugs.kde.org/show_bug.cgi?id=336738 David Jarvie <djar...@kde.org> changed: What|Removed |Added CC||a...@polverini.org --- Comment #19 from David Jarvie <djar...@kde.org> --- *** Bug 362283 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 362283] One hour offset creating alarms on kalarm 15.12.3
https://bugs.kde.org/show_bug.cgi?id=362283 David Jarvie <djar...@kde.org> changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Jarvie <djar...@kde.org> --- *** This bug has been marked as a duplicate of bug 336738 *** -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 360023] kalarm crashes on startup
https://bugs.kde.org/show_bug.cgi?id=360023 --- Comment #5 from David Jarvie <djar...@kde.org> --- It turns out that kalarm 15.12 requires the KDE Frameworks 5 version of ktimezoned, which is provided by the plasma-workspace package (in Debian/Ubuntu - I'm not sure about Archlinux). If this isn't working on your system, it seems likely that it's some kind of packaging problem, since it works fine on a self-compiled system. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 361885] Kalarm crashes when closing main woindow
https://bugs.kde.org/show_bug.cgi?id=361885 David Jarvie <djar...@kde.org> changed: What|Removed |Added Product|kalarm |Breeze Component|general |general Assignee|djar...@kde.org |plasma-de...@kde.org --- Comment #1 from David Jarvie <djar...@kde.org> --- The crash is in the Breeze style code. Reassigning to Breeze. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 361936] Kalarm startup warning: Time zones are not accessible
https://bugs.kde.org/show_bug.cgi?id=361936 David Jarvie <djar...@kde.org> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from David Jarvie <djar...@kde.org> --- On Ubuntu or Debian, you need to install plasma-workspace package to fix this. The relevant file which is missing is /usr/lib/x86_64-linux-gnu/qt5/plugins/kded_ktimezoned.so (substitute your computer's architecture for 'x86_64-linux-gnu' if it doesn't have an AMD64 type processor). Clearly, there should be a package dependency for the KF5 version of kalarm on plasma-workspace (or alternatively the kded_ktimezoned.so file may need to be split out into another package). This is something that needs to be fixed by the Ubuntu packagers (and probably the Debian experimental packagers also). -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 361717] KAlarm Crashes on Creation (Add) of New *.ics Calander File
https://bugs.kde.org/show_bug.cgi?id=361717 David Jarvie <djar...@kde.org> changed: What|Removed |Added Version Fixed In||16.04 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im/37373504360a50f94ed73049 ||ddbdfe95f5e04a82 Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Jarvie <djar...@kde.org> --- Fixed for KDE Applications version 16.04 by commit http://commits.kde.org/kdepim/37373504360a50f94ed73049ddbdfe95f5e04a82 -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 361539] KAlarm Crashes on Creation (Add) of New *.ics Calander File
https://bugs.kde.org/show_bug.cgi?id=361539 David Jarvie <djar...@kde.org> changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||16.04 Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kdep ||im/37373504360a50f94ed73049 ||ddbdfe95f5e04a82 --- Comment #3 from David Jarvie <djar...@kde.org> --- This is probably fixed for KDE Applications version 16.04 by commit http://commits.kde.org/kdepim/37373504360a50f94ed73049ddbdfe95f5e04a82 If it happens again after updating to 16.04, please reopen. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 361543] KAlarm Automatically Creates New Calendar Named "akonadi_kalarm_resource_N+1" Every Time a New Calender is Created (Add)
https://bugs.kde.org/show_bug.cgi?id=361543 David Jarvie <djar...@kde.org> changed: What|Removed |Added Version Fixed In||16.04 -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 361543] KAlarm Automatically Creates New Calendar Named "akonadi_kalarm_resource_N+1" Every Time a New Calender is Created (Add)
https://bugs.kde.org/show_bug.cgi?id=361543 David Jarvie <djar...@kde.org> changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im/71c5ae4f4f24546e46179e1e ||233dda3da756152a --- Comment #3 from David Jarvie <djar...@kde.org> --- Git commit 71c5ae4f4f24546e46179e1e233dda3da756152a by David Jarvie. Committed on 13/04/2016 at 20:48. Pushed by djarvie into branch 'Applications/16.04'. Don't show spurious extra calendar after adding new calendar After adding a new calendar, the calendar list showed two entries for the new calendar, one labelled "akonadi_kalarm_resource_*" and with invalid details. M +2-1kalarm/Changelog M +2-0kalarm/collectionmodel.cpp http://commits.kde.org/kdepim/71c5ae4f4f24546e46179e1e233dda3da756152a -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 361543] KAlarm Automatically Creates New Calendar Named "akonadi_kalarm_resource_N+1" Every Time a New Calender is Created (Add)
https://bugs.kde.org/show_bug.cgi?id=361543 David Jarvie <djar...@kde.org> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from David Jarvie <djar...@kde.org> --- The calendar named "akonadi_kalarm_resource_*" is added to the calendars list as soon as the calendar configuration dialog is displayed. When one entry for the new calendar is deleted, the other also disappears from the list. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 361539] KAlarm Crashes on Creation (Add) of New *.ics Calander File
https://bugs.kde.org/show_bug.cgi?id=361539 --- Comment #1 from David Jarvie <djar...@kde.org> --- I can't reproduce this running under KDE frameworks 5,17.0. What version of KDE frameworks are you using? (Help -> About KAlarm -> Version will tell you the KDE frameworks version.) -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 336738] time zone is miscalculated by 1 hour or ignored
https://bugs.kde.org/show_bug.cgi?id=336738 David Jarvie <djar...@kde.org> changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kcal ||core/9800fca3b44300828a8b7d ||23ae962f01e47ac5ff Version Fixed In||16.04 Resolution|--- |FIXED --- Comment #18 from David Jarvie <djar...@kde.org> --- Git commit 9800fca3b44300828a8b7d23ae962f01e47ac5ff by David Jarvie. Committed on 11/04/2016 at 19:35. Pushed by djarvie into branch 'Applications/16.04'. Fix timesInInterval() when parsing VTIMEZONE RRULE components KDateTime::isValid() (KF5 <= 5.21) wrongly returns invalid for an instance which is specified in ClockTime, if the date/time is invalid in LocalTime, resulting in timesInInterval() returning no values when parsing a VTIMEZONE RRULE component in ICalTimeZones. This is a workaround for backwards compatibility with KF5 <= 5.21. Differential Revision: https://phabricator.kde.org/D1375 FIXED-IN: 16.04 M +2 -1 src/recurrencerule.cpp http://commits.kde.org/kcalcore/9800fca3b44300828a8b7d23ae962f01e47ac5ff -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 360674] Post-daylight savings time, kalarm records alarms 1 hour later than it should
https://bugs.kde.org/show_bug.cgi?id=360674 David Jarvie <djar...@kde.org> changed: What|Removed |Added Version Fixed In||16.04 Resolution|DUPLICATE |FIXED Latest Commit||http://commits.kde.org/kcal ||core/9800fca3b44300828a8b7d ||23ae962f01e47ac5ff --- Comment #7 from David Jarvie <djar...@kde.org> --- Git commit 9800fca3b44300828a8b7d23ae962f01e47ac5ff by David Jarvie. Committed on 11/04/2016 at 19:35. Pushed by djarvie into branch 'Applications/16.04'. Fix timesInInterval() when parsing VTIMEZONE RRULE components KDateTime::isValid() (KF5 <= 5.21) wrongly returns invalid for an instance which is specified in ClockTime, if the date/time is invalid in LocalTime, resulting in timesInInterval() returning no values when parsing a VTIMEZONE RRULE component in ICalTimeZones. This is a workaround for backwards compatibility with KF5 <= 5.21. Differential Revision: https://phabricator.kde.org/D1375 FIXED-IN: 16.04 M +2-1src/recurrencerule.cpp http://commits.kde.org/kcalcore/9800fca3b44300828a8b7d23ae962f01e47ac5ff -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 336738] time zone is miscalculated by 1 hour or ignored
https://bugs.kde.org/show_bug.cgi?id=336738 David Jarvie <djar...@kde.org> changed: What|Removed |Added CC||ha...@laging.de --- Comment #17 from David Jarvie <djar...@kde.org> --- *** Bug 361115 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 361115] daylight savings time is handled incorrectly
https://bugs.kde.org/show_bug.cgi?id=361115 David Jarvie <djar...@kde.org> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from David Jarvie <djar...@kde.org> --- *** This bug has been marked as a duplicate of bug 336738 *** -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 336738] time zone is miscalculated by 1 hour or ignored
https://bugs.kde.org/show_bug.cgi?id=336738 David Jarvie <djar...@kde.org> changed: What|Removed |Added Severity|normal |major -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 336738] time zone is miscalculated by 1 hour or ignored
https://bugs.kde.org/show_bug.cgi?id=336738 --- Comment #16 from David Jarvie <djar...@kde.org> --- *** Bug 360674 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 360674] Post-daylight savings time, kalarm records alarms 1 hour later than it should
https://bugs.kde.org/show_bug.cgi?id=360674 David Jarvie <djar...@kde.org> changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #6 from David Jarvie <djar...@kde.org> --- *** This bug has been marked as a duplicate of bug 336738 *** -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 336738] time zone is miscalculated by 1 hour or ignored
https://bugs.kde.org/show_bug.cgi?id=336738 David Jarvie <djar...@kde.org> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #15 from David Jarvie <djar...@kde.org> --- This is due to a bug in the KDE PIM libraries (in kcalcore). See https://phabricator.kde.org/D1375. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 360674] Post-daylight savings time, kalarm records alarms 1 hour later than it should
https://bugs.kde.org/show_bug.cgi?id=360674 David Jarvie <djar...@kde.org> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #5 from David Jarvie <djar...@kde.org> --- This is due to a bug in the KDE PIM libraries (in kcalcore). See https://phabricator.kde.org/D1375. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 356519] Clicking the kalarm icon to restore/minimize doesn't work
https://bugs.kde.org/show_bug.cgi?id=356519 David Jarvie <djar...@kde.org> changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from David Jarvie <djar...@kde.org> --- This has now been fixed. The fix is in KDE Frameworks, not in KAlarm. To get a working version, you need to install KDE Frameworks 5.21.0 or later. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 356519] Clicking the kalarm icon to restore/minimize doesn't work
https://bugs.kde.org/show_bug.cgi?id=356519 David Jarvie <djar...@kde.org> changed: What|Removed |Added Version Fixed In||KDE Frameworks 5.21.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 358589] Regression: Left click on system tray icon is not seen under XFCE (KDE 4.14 works)
https://bugs.kde.org/show_bug.cgi?id=358589 David Jarvie <djar...@kde.org> changed: What|Removed |Added Version Fixed In||5.21.0 --- Comment #14 from David Jarvie <djar...@kde.org> --- This has been fixed in KDE Frameworks 5.21. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 361115] daylight savings time is handled incorrectly
https://bugs.kde.org/show_bug.cgi?id=361115 David Jarvie <djar...@kde.org> changed: What|Removed |Added Component|kalarmd |general --- Comment #1 from David Jarvie <djar...@kde.org> --- Which version of KDE and KAlarm are you using? (Use menu option Help -> About KAlarm to find out.) Which time zone is configured as the default for KAlarm? Use menu option Settings -> Configure KAlarm, and then select the Time & Date tab to check. Do you use KAlarm's default time zone for your alarms? To verify this, open an alarm and if you're using the default, no time zone will be listed beside the Time Zone button. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 358589] Regression: Left click on system tray icon is not seen under XFCE (KDE 4.14 works)
https://bugs.kde.org/show_bug.cgi?id=358589 --- Comment #11 from David Jarvie <djar...@kde.org> --- On Wednesday 17 Feb 2016 23:54:51 you wrote: > https://bugs.kde.org/show_bug.cgi?id=358589 > > --- Comment #8 from Martin Klapetek <mklape...@kde.org> --- > Created attachment 97272 > --> https://bugs.kde.org/attachment.cgi?id=97272=edit > Patch > > Ok here's a patch. It should work against 5.17 too. > > Let me know if this does anything useful. I tested your patch, which worked successfully (see my comment in Bugzilla https://bugs.kde.org/show_bug.cgi?id=358589#c10). Can you commit it (presumably after a ReviewBoard review), so that things work for XFCE users? Thanks, -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 360023] kalarm crashes on startup
https://bugs.kde.org/show_bug.cgi?id=360023 --- Comment #3 from David Jarvie <djar...@kde.org> --- ktimezoned is implemented as a kded plugin in KDE Frameworks 5. It should presumably be possible to run it using the KF5 version of kcminit, but when I try that, it complains that it can't find ktimezoned.desktop. I don't know why that's missing. I suggest asking on the KDE forums or a KDE mailing list (perhaps kde-devel?). I can't guarantee that running the KF5 version of ktimezoned will fix the issue, but it needs to be checked out first, since the issue doesn't seem to exist when running under the Plasma 5 desktop. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 360134] Crash on wakeup, connecting to external monitor
https://bugs.kde.org/show_bug.cgi?id=360134 David Jarvie <djar...@kde.org> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from David Jarvie <djar...@kde.org> --- This looks like a Qt issue - the crash trace only refers to Qt code, with nothing to indicate that KDE is involved. If it isn't a Qt issue, then it's almost certainly a KDE Frameworks issue. Either way, there's nothing that links it specifically to KAlarm. Therefore I'm marking this as an upstream issue - please report it to Qt. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 360023] kalarm crashes on startup
https://bugs.kde.org/show_bug.cgi?id=360023 David Jarvie <djar...@kde.org> changed: What|Removed |Added Component|kalarmd |general --- Comment #1 from David Jarvie <djar...@kde.org> --- Using the plasma 5 desktop, I couldn't reproduce the crash. Unfortunately the crash trace has no useful information in it which would help to investigate the problem. You seem to be using the KDE 4 version of ktimezoned.desktop, and of kcminit, rather then the KF5 versions - I wonder why, when you're using the KF5 version of KAlarm. Which desktop are you using? -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 339375] kalarm process has high cpu consumption
https://bugs.kde.org/show_bug.cgi?id=339375 --- Comment #2 from David Jarvie <djar...@kde.org> --- Does this problem still exist? If so, try deleting all alarms which recur on an hourly or minutely frequency (so that only daily, weekly, monthly or annual recurrences are used). Does this reduce the CPU load? -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 336738] time zone is miscalculated by 1 hour or ignored
https://bugs.kde.org/show_bug.cgi?id=336738 --- Comment #13 from David Jarvie <djar...@kde.org> --- Please open a terminal window and type the following command, followed by : timedatectl Report what is displayed in the line beginning "Time zone:". -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 359163] Emails fail with "Invalid 'From' email address." message.
https://bugs.kde.org/show_bug.cgi?id=359163 --- Comment #9 from David Jarvie <djar...@kde.org> --- Sorry, I didn't notice that you attached calendar.ics in comment 4. This is puzzling - when I set my config to match yours, I don't see the fault occurring. Could you please help with some more information: 1) When you bring up the dialog to edit a new email alarm, does it show a 'From' field at the top (a combo box rather than an edit field), above the 'To' field? 2) Which version of Fedora are you running? If you are running a KDE desktop, is it KDE 4 or Plasma 5? -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed
https://bugs.kde.org/show_bug.cgi?id=358027 David Jarvie <djar...@kde.org> changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #15 from David Jarvie <djar...@kde.org> --- The reason for the bug appears to be that Debian testing contains a mixture of KDE Frameworks 5 (KF5), Plasma 5 desktop and KDE 4 applications (including KAlarm). The KF5/Plasma 5 combination doesn't correctly handle autostart of KDE 4 applications. Once Debian testing is updated to contain the KF5 version of KAlarm (in KDE Applications version 15.08 onwards), autostart should work correctly again. KAlarm's KDE 4 autostart configuration is held in ~/.kde/share/config/kalarmrc, whereas KF5 looks in ~/.config. However, even copying kalarmrc into ~/.config didn't make autostart work for me, so there may be some other incompatibility as well. I'm therefore closing this bug as "downstream", since the latest version of KAlarm (in KDE Applications 15.12) already works, and it's Debian which needs to be fixed by updating KAlarm. You could report this bug on the Debian bug system - I don't know whether or not Debian stretch is intended to be eventually released with KDE Applications 15.08 or later. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 359163] Emails fail with "Invalid 'From' email address." message.
https://bugs.kde.org/show_bug.cgi?id=359163 David Jarvie <djar...@kde.org> changed: What|Removed |Added Component|kalarmd |general -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 358589] Regression: Left click on system tray icon is not seen under XFCE (KDE 4.14 works)
https://bugs.kde.org/show_bug.cgi?id=358589 --- Comment #10 from David Jarvie <djar...@kde.org> --- Sorry, please ignore my last comment - I built the wrong branch. In fact, the patch does fix the issue - a left click on the system tray icon works correctly with the patch. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 358589] Regression: Left click on system tray icon is not seen under XFCE (KDE 4.14 works)
https://bugs.kde.org/show_bug.cgi?id=358589 --- Comment #9 from David Jarvie <djar...@kde.org> --- I tried the patch, but it doesn't make any difference to left clicks on the system tray icon. The signal activateRequested() is still not received by the application on left click. It is however received when Minimize/Restore are selected from the system tray icon context menu (the same as without the patch). -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 359163] Emails fail with "Invalid 'From' email address." message.
https://bugs.kde.org/show_bug.cgi?id=359163 --- Comment #3 from David Jarvie <djar...@kde.org> --- I tried out an email alarm with the email address configured in the same way as yours in the settings, but it was sent successfully. Could you please set up an email alarm and then attach your KAlarm configuration file (in ~/.kde/share/config/kalarmrc or ~/.config/kalarmrc or some similar directory), and also your calendar file (to find out its location, select menu View -> Show Calendars, and then right click on the active alarm calendar and select Show Details - the location is labelled "File:"). If you want to hide personal information in the calendar file, just replace it with other text before attaching the file. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 359163] Emails fail with "Invalid 'From' email address." message.
https://bugs.kde.org/show_bug.cgi?id=359163 --- Comment #1 from David Jarvie <djar...@kde.org> --- Which option is selected for your 'from' email address configured In KAlarm's settings dialog? (Use menu Settings -> Configure KAlarm -> Email.) -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 359296] No "Recurrence Rule" for Hourly/Minutely
https://bugs.kde.org/show_bug.cgi?id=359296 David Jarvie <djar...@kde.org> changed: What|Removed |Added Version Fixed In||15.12.2 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||6ee2c3baf980dd891a2717c69ab ||8c4172ff6ad77 --- Comment #1 from David Jarvie <djar...@kde.org> --- This has already been fixed on 1 February, in commit 6ee2c3baf980dd891a2717c69ab8c4172ff6ad77 (15.12 branch). -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed
https://bugs.kde.org/show_bug.cgi?id=358027 --- Comment #12 from David Jarvie <djar...@kde.org> --- 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 are watching all bug changes.
[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed
https://bugs.kde.org/show_bug.cgi?id=358027 --- Comment #14 from David Jarvie <djar...@kde.org> --- 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 receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed
https://bugs.kde.org/show_bug.cgi?id=358027 David Jarvie <djar...@kde.org> changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 --- Comment #11 from David Jarvie <djar...@kde.org> --- That would certainly explain why kalarm doesn't start. I'll need to think of how kalarmautostart's hangup can be investigated. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed
https://bugs.kde.org/show_bug.cgi?id=358027 --- Comment #9 from David Jarvie <djar...@kde.org> --- 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 AutoStart entry is set to true. I also run Debian, and it works on both wheezy and jessie. Can you check whether the autostart desktop file exists, and if so, whether it has executable permissions set. Also check kalarmrc to see that the AutoStart entry exists in the [General] section, and what its value is. Note that you can disable "start at login" in KAlarm so that it doesn't run at login, but as soon as you run it manually again, it enables "start at login" to ensure that it will always trigger alarms which the user may set up. The reasoning is that it's better to be safe and assume that the user intends to keep using it, and thereby ensure that alarms will trigger, rather than allowing the user to unintentionally not enable it and then wonder why alarms don't trigger. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed
https://bugs.kde.org/show_bug.cgi?id=358027 David Jarvie <djar...@kde.org> changed: What|Removed |Added Resolution|LATER |WAITINGFORINFO --- Comment #7 from David Jarvie <djar...@kde.org> --- Thanks. In order to let me diagnose the problem, can you please temporarily remove the startup script, and quit kalarm (using menu File -> Quit) before you next log out or shut down. After you log in after that, do as I asked in comment 4. You can then reinstate your startup script if you want. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 346060] KAlarm calculates deferred alarm time wrongly
https://bugs.kde.org/show_bug.cgi?id=346060 David Jarvie <djar...@kde.org> changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Version Fixed In||15.12.2 Latest Commit||fd5960c66c650ef42207e83b44e ||80e6e243474dd --- Comment #5 from David Jarvie <djar...@kde.org> --- Thanks for your detailed information. It turns out that the bug only occurs when the start-of-day setting is not midnight. Now fixed in 4.14 branch (commit a791b69599c3571ff2f4b1cc9033d8fb30f1bc33) - although bear in mind that there are unlikely to be any further official KDE 4.14 releases. Also fixed in 15.12 branch (commit fd5960c66c650ef42207e83b44e80e6e243474dd), for release 15.12.2. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 346060] KAlarm calculates deferred alarm time wrongly
https://bugs.kde.org/show_bug.cgi?id=346060 --- Comment #1 from David Jarvie <djar...@kde.org> --- I'm sorry this bug has been overlooked. If possible, can you provide more information on this: - You say that in KDE you have two time zones. How are these set? (In System Settings, you can only set one time zone, and that sets it for the system.) - What time zone is set in KAlarm (in the KAlarm menu, go to Settings -> Configure KAlarm -> Time & Date). - What do you mean by pressing OK in the main alarm window? Did you bring up the alarm edit dialog after deferring the alarm, edit it and click OK? - Can you please attach a copy of KAlarm's calendar (usually in ~/.kde/share/apps/kalarm/calendar.ics), after deferring the alarm. Please say what time is then shown for the alarm in KAlarm's main window. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 344902] kalarm uses gregorian calendar system for day number when adding reoccurring events in jalali calendar system
https://bugs.kde.org/show_bug.cgi?id=344902 David Jarvie <djar...@kde.org> changed: What|Removed |Added Severity|normal |wishlist --- Comment #5 from David Jarvie <djar...@kde.org> --- I'm changing the category of this bug to a wishlist item, since without either a change to the iCalendar specification, or changing KAlarm to not use iCalendar (which would be a very major change), it is not possible to implement Jalali recurrences. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 358625] klarm crashed when opening from systray
https://bugs.kde.org/show_bug.cgi?id=358625 David Jarvie <djar...@kde.org> changed: What|Removed |Added CC||kdelibs-b...@kde.org Assignee|djar...@kde.org |mklape...@kde.org Product|kalarm |frameworks-knotifications Component|general |general --- Comment #2 from David Jarvie <djar...@kde.org> --- This looks like a bug in KStatusNotifierItem, so reassigning to frameworks-knotifications. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 358625] kalarm crashed when opening from systray
https://bugs.kde.org/show_bug.cgi?id=358625 David Jarvie <djar...@kde.org> changed: What|Removed |Added Summary|klarm crashed when opening |kalarm crashed when opening |from systray|from systray CC||djar...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed
https://bugs.kde.org/show_bug.cgi?id=358027 David Jarvie <djar...@kde.org> changed: What|Removed |Added Resolution|--- |LATER Status|UNCONFIRMED |NEEDSINFO --- Comment #5 from David Jarvie <djar...@kde.org> --- Change status to NeedsInfo -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 358625] klarm crashed when opening from systray
https://bugs.kde.org/show_bug.cgi?id=358625 --- Comment #1 from David Jarvie <djar...@kde.org> --- Which desktop are you using? KDE Plasma, or what? -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 357018] Unable to specify value for reminder
https://bugs.kde.org/show_bug.cgi?id=357018 David Jarvie <djar...@kde.org> changed: What|Removed |Added Latest Commit|90adafe8dfd2894f90098df1f3d |a5c6b6dd5fb2b58676dcf182135 |9c04c5cb5b2dc |10a1778dbc6de --- Comment #4 from David Jarvie <djar...@kde.org> --- Fixed mistake in previous fix, in commit a5c6b6dd5fb2b58676dcf18213510a1778dbc6de (15.12 branch and master). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 358589] New: Regression: Left click on system tray icon is not seen under XFCE (KDE 4.14 works)
https://bugs.kde.org/show_bug.cgi?id=358589 Bug ID: 358589 Summary: Regression: Left click on system tray icon is not seen under XFCE (KDE 4.14 works) Product: frameworks-knotifications Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mklape...@kde.org Reporter: djar...@kde.org CC: kdelibs-b...@kde.org Using XFCE 4.10 desktop, a left click on a system tray icon is not seen for a KDE application (version 15.12) using frameworks 5.17. Running the same application (version 4.14) under the same XFCE login session, the left click works. See https://bugs.kde.org/show_bug.cgi?id=356519 for more details. I added debug output into KStatusNotifierItem, and verified that it does not emit the activateRequested() signal in frameworks 5.17, because the KStatusNotifierItem::activate() method never got called. It did emit the signal in KDE 4.14. I couldn't identify any differences in the KStatusNotifierItem class between 4.14 and 5.17 which might account for why it functions differently, so perhaps it's due to changes in some other class. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 358589] Regression: Left click on system tray icon is not seen under XFCE (KDE 4.14 works)
https://bugs.kde.org/show_bug.cgi?id=358589 David Jarvie <djar...@kde.org> changed: What|Removed |Added Platform|Other |Compiled Sources -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 356519] Clicking the kalarm icon to restore/minimize doesn't work
https://bugs.kde.org/show_bug.cgi?id=356519 --- Comment #6 from David Jarvie <djar...@kde.org> --- I've raised this as a bug against the KNotifications framework: https://bugs.kde.org/show_bug.cgi?id=358589. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 358217] Occasional crash on startup
https://bugs.kde.org/show_bug.cgi?id=358217 --- Comment #3 from David Jarvie <djar...@kde.org> --- I don't understand what can have given rise to the bug, but there is now an extra guard against using invalid data. Hence I can't be sure that it's fixed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 358589] Regression: Left click on system tray icon is not seen under XFCE (KDE 4.14 works)
https://bugs.kde.org/show_bug.cgi?id=358589 --- Comment #2 from David Jarvie <djar...@kde.org> --- Created attachment 96853 --> https://bugs.kde.org/attachment.cgi?id=96853=edit Bustle log for KAlarm version 14.4 I did personally test both versions of the application in the same XFCE session before reporting this bug. I can't run the two versions of the app at the same time, because it's a KUniqueApplication. Instead, I ran one version, started the Bustle recording, clicked a couple of times on the system tray icon, and then stopped the Bustle log. I then repeated this for the other version. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 358589] Regression: Left click on system tray icon is not seen under XFCE (KDE 4.14 works)
https://bugs.kde.org/show_bug.cgi?id=358589 --- Comment #3 from David Jarvie <djar...@kde.org> --- Created attachment 96854 --> https://bugs.kde.org/attachment.cgi?id=96854=edit Bustle log for KAlarm version 15.12 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 358589] Regression: Left click on system tray icon is not seen under XFCE (KDE 4.14 works)
https://bugs.kde.org/show_bug.cgi?id=358589 David Jarvie <djar...@kde.org> changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #4 from David Jarvie <djar...@kde.org> --- . -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 358589] Regression: Left click on system tray icon is not seen under XFCE (KDE 4.14 works)
https://bugs.kde.org/show_bug.cgi?id=358589 --- Comment #7 from David Jarvie <djar...@kde.org> --- I can test patches, as long as they can be applied to KF 5.17 (I'm not running master). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 358589] Regression: Left click on system tray icon is not seen under XFCE (KDE 4.14 works)
https://bugs.kde.org/show_bug.cgi?id=358589 David Jarvie <djar...@kde.org> changed: What|Removed |Added Blocks||356519 -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 356519] Clicking the kalarm icon to restore/minimize doesn't work
https://bugs.kde.org/show_bug.cgi?id=356519 David Jarvie <djar...@kde.org> changed: What|Removed |Added Depends on||358589 -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 358217] Occasional crash on startup
https://bugs.kde.org/show_bug.cgi?id=358217 --- Comment #5 from David Jarvie <djar...@kde.org> --- Preferably reopen this bug rather than a new one if you see the problem again. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 356519] Clicking the kalarm icon to restore/minimize doesn't work
https://bugs.kde.org/show_bug.cgi?id=356519 David Jarvie <djar...@kde.org> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #5 from David Jarvie <djar...@kde.org> --- Under XFCE, KStatusNotifierItem in the KNotifications framework library (version 5.17) doesn't see the mouse click on the system tray icon, and therefore doesn't pass the click to KAlarm, which therefore doesn't know to show/hide its main window. Version 4.14 of the same class does see the mouse click. The reason for KNotifications framework no longer seeing the click under XFCE needs investigation. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 356048] kalarm always crashes when changing alarms
https://bugs.kde.org/show_bug.cgi?id=356048 David Jarvie <djar...@kde.org> changed: What|Removed |Added Version Fixed In||15.12.2 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||6af5386719f01cc3a71f9486807 ||c66b1b3da26d1 --- Comment #2 from David Jarvie <djar...@kde.org> --- Thanks for the information on how to reproduce the crash. I suspect that one of the library classes doesn't handle destruction properly, and allows the contentsChanged() signal to be emitted when it shouldn't, but KAlarm now ignores the unwanted signal. Fixed in commit 6af5386719f01cc3a71f9486807c66b1b3da26d1 (15.12 branch and master). -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 358217] Occasional crash on startup
https://bugs.kde.org/show_bug.cgi?id=358217 David Jarvie <djar...@kde.org> changed: What|Removed |Added Latest Commit||4c8ecf34c1d9432b692d4ead41f ||c4b879aa51b4d Summary|corefile (sigfpe) |Occasional crash on startup |ksplashqml | Version Fixed In||15.12.2 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Jarvie <djar...@kde.org> --- This should be fixed now (I can't test because I can't reproduce the bug). Commit 4c8ecf34c1d9432b692d4ead41fc4b879aa51b4d (15.12 branch). -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 358027] Should start minimized or remember if last instance was open or closed
https://bugs.kde.org/show_bug.cgi?id=358027 --- Comment #1 from David Jarvie <djar...@kde.org> --- 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 window visible, or does it only appear in the system tray? -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 356519] Clicking the kalarm icon to restore/minimize doesn't work
https://bugs.kde.org/show_bug.cgi?id=356519 --- Comment #3 from David Jarvie <djar...@kde.org> --- Is it true that clicking on the system tray icon worked under XFCE for a KAlarm version earlier than 15.08? If so, what was the last version which worked? -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 356106] kalarm message windows are invisible for x-tile
https://bugs.kde.org/show_bug.cgi?id=356106 David Jarvie <djar...@kde.org> changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Jarvie <djar...@kde.org> --- KAlarm already has a mechanism to tile message windows - use the menu option View -> Spread Windows. I'm not familiar with x-tile, but it's possible that x-tile isn't able to handle windows which stay on top (which is the case for KAlarm message windows). KAlarm windows are designed to work in conjunction with both other applications' normal windows and with fullscreen windows. If x-tile can't handle the windows, that's really an x-tile problem, not a KAlarm one, since changing the window characteristics would almost certainly prevent them working properly in the normal case when x-tile is not being used. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 356519] Clicking the kalarm icon to restore/minimize doesn't work
https://bugs.kde.org/show_bug.cgi?id=356519 --- Comment #1 from David Jarvie <djar...@kde.org> --- Which desktop are you using? This worked for me when I tried it under a KDE4 desktop. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 357653] kalarm.autostart.desktop missing OnlyShowIn=KDE
https://bugs.kde.org/show_bug.cgi?id=357653 David Jarvie <djar...@kde.org> changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Jarvie <djar...@kde.org> --- kalarm.autostart.desktop is there to ensure that KAlarm starts when the user logs on. If it doesn't start, alarms won't be triggered. This applies whatever desktop is being used. So adding OnlyShowIn=KDE would stop KAlarm working except under the KDE desktop. Note that kalarm won't be started by kalarm.autostart.desktop if it has been configured not to autostart, using KAlarm's settings dialog. If you have special requirements and only want KAlarm to run under KDE, you would need to create a script to set the AutoStart entry in kalarmrc to the appropriate value depending on what desktop was being run, before kalarm.autostart.desktop was invoked at login. I'm marking this bug as invalid, since altering the file as you suggest would prevent KAlarm from working for most users. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 357018] Unable to specify value for reminder
https://bugs.kde.org/show_bug.cgi?id=357018 David Jarvie <djar...@kde.org> changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||15.12.2 Status|UNCONFIRMED |RESOLVED Latest Commit||90adafe8dfd2894f90098df1f3d ||9c04c5cb5b2dc --- Comment #2 from David Jarvie <djar...@kde.org> --- This was due to Qt5 being less tolerant of mistakes than Qt4 was. Fixed for 15.12.2 in commit 90adafe8dfd2894f90098df1f3d9c04c5cb5b2dc (15.12 branch and master), -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 357186] “ fatal error: phonon/backendcapabilities.h: No such file or directory” when building kdepim
https://bugs.kde.org/show_bug.cgi?id=357186 David Jarvie <djar...@kde.org> changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Jarvie <djar...@kde.org> --- This looks like a Mageia packaging problem. The phonon git repository still contains the file backendcapabilities.h, so there is no obvious reason why it shouldn't be present. I suggest you raise a bug report with Mageia. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 354417] crash on boot
https://bugs.kde.org/show_bug.cgi?id=354417 David Jarvie <djar...@kde.org> changed: What|Removed |Added CC||br...@gmcl.com --- Comment #6 from David Jarvie <djar...@kde.org> --- *** Bug 356787 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 356787] Akonadi crash soon after login
https://bugs.kde.org/show_bug.cgi?id=356787 David Jarvie <djar...@kde.org> changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Jarvie <djar...@kde.org> --- *** This bug has been marked as a duplicate of bug 354417 *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356940] kalarm crash on start up
https://bugs.kde.org/show_bug.cgi?id=356940 David Jarvie <djar...@kde.org> changed: What|Removed |Added Component|general |general Assignee|djar...@kde.org |plasma-de...@kde.org Product|kalarm |Breeze -- You are receiving this mail because: You are watching all bug changes.
