https://bugs.kde.org/show_bug.cgi?id=459995
Flossy Cat changed:
What|Removed |Added
CC||flossy-...@online.de
--- Comment #1 from Flossy
https://bugs.kde.org/show_bug.cgi?id=436388
Flossy Cat changed:
What|Removed |Added
CC||flossy-...@online.de
--- Comment #10 from Flossy
https://bugs.kde.org/show_bug.cgi?id=481069
--- Comment #31 from Flossy Cat ---
(In reply to Andreas Schneider from comment #30)
> As initially said that this is something for power users,
I'm the initial reporter of both this bug report and
https://bugs.kde.org/show_bug.cgi?id=481068
and
https://bugs.kde.org/show_bug.cgi?id=481069
--- Comment #29 from Flossy Cat ---
(In reply to Andreas Schneider from comment #28)
> You can pass it as command line options:
I know, but kindly read the rationale section in
https://bugs.kde.org/show_bug.cgi?id=481069#c26
to see why this additio
https://bugs.kde.org/show_bug.cgi?id=481069
--- Comment #27 from Flossy Cat ---
ERRATA
Ooops, forgot the ";" at line ends. Blush …
// code suggestion start
const std::string envPrefix = "KDE_NOTIFICATION_PARAMS_"; // name-space, your
choice
proc.setEnv(envPrefix + &qu
https://bugs.kde.org/show_bug.cgi?id=481069
--- Comment #26 from Flossy Cat ---
Thank you!
When you are at it, kindly consider the following improvement (sample code
below) (see also https://bugs.kde.org/show_bug.cgi?id=481068):
IMPROVEMENT
Add pre-filled environment variables
https://bugs.kde.org/show_bug.cgi?id=481069
--- Comment #20 from Flossy Cat ---
My comments #18 and #19 were classified as spam – can somebody enlighten me,
why?
And remove this classification because I am actually trying to achieve some
progress here.
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=481069
--- Comment #19 from Flossy Cat ---
(In reply to Nate Graham from comment #7)
> (In reply to Flossy Cat from comment #6)
> > …
> > How does KDE know which features are unused and how is removal decided?
> We largely have no ide
https://bugs.kde.org/show_bug.cgi?id=481069
--- Comment #18 from Flossy Cat ---
(In reply to Nate Graham from comment #13)
> I'm afraid I can't formally commit to that level of personal hand-holding as
> my time is split 500 ways and extremely limit these days. But I will be
> happy
https://bugs.kde.org/show_bug.cgi?id=483545
Bug ID: 483545
Summary: Kmail2 silently looses mails while displaying the
correct counts with the folders
Classification: Applications
Product: kmail2
Version: 5.22.3
https://bugs.kde.org/show_bug.cgi?id=481069
--- Comment #12 from Flossy Cat ---
(In reply to Nate Graham from comment #9)
> From the perspective of Bugzilla, this isn't a bug; the removal of the
> feature was intentional. The request being made here is to reconsider that
> removal
https://bugs.kde.org/show_bug.cgi?id=481166
Flossy Cat changed:
What|Removed |Added
Resolution|INTENTIONAL |FIXED
--- Comment #10 from Flossy Cat
https://bugs.kde.org/show_bug.cgi?id=481069
Flossy Cat changed:
What|Removed |Added
Keywords||regression, usability
--- Comment #8 from Flossy
https://bugs.kde.org/show_bug.cgi?id=481069
--- Comment #6 from Flossy Cat ---
(In reply to Nate Graham from comment #5)
> Got it, thanks. I can see how that would be useful for powerful custom
> workflows.
Glad to be of service.
Anyhow, my counterquestion was not rhetorical, but in earn
https://bugs.kde.org/show_bug.cgi?id=481069
--- Comment #4 from Flossy Cat ---
(In reply to Nate Graham from comment #3)
> How exactly was this feature found and
> configured? How did you set it all up? What was the UX like? Etc.
Get a system with
KDE Plasma Version: 5.27.9
KDE Fram
https://bugs.kde.org/show_bug.cgi?id=481069
--- Comment #2 from Flossy Cat ---
(In reply to Nate Graham from comment #1)
> Not being familiar with the functionality, can you take a few steps back and
> explain what it did,
It allowed to trigger a command execution when specific notific
https://bugs.kde.org/show_bug.cgi?id=481166
--- Comment #8 from Flossy Cat ---
(In reply to David Jarvie from comment #7)
> Many of your proposals go beyond the intended scope of KAlarm, and if
> implemented would expand its function from being a stand-alone personal
> alarm ap
https://bugs.kde.org/show_bug.cgi?id=481166
--- Comment #6 from Flossy Cat ---
(In reply to David Jarvie from comment #5)
> Yes, KAlarm is for both technical and non-technical users, but to serve the
> latter, it needs a simple interface. More advanced users can expand the
> range of
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #26 from Flossy Cat ---
(In reply to Bernhard E. Reiter from comment #25)
> …
> However it is most helpful to understand that there are many volunteers
> that work on KDE's software products. While the whole process may
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #24 from Flossy Cat ---
(In reply to Bernhard E. Reiter from comment #23)
> …
> It also maybe an option on OpenSuse to use one of the
> https://en.opensuse.org/SDB:KDE_repositories
> that is providing newer KDE Applicat
https://bugs.kde.org/show_bug.cgi?id=481166
--- Comment #4 from Flossy Cat ---
(In reply to David Jarvie from comment #3)
> As stated in its handbook, KAlarm is designed as a personal message, email
> and command scheduler. It is not designed for group use.
I do not intend group use
https://bugs.kde.org/show_bug.cgi?id=481166
--- Comment #2 from Flossy Cat ---
(In reply to David Jarvie from comment #1)
> By design, KAlarm stores all its alarms in VEVENT, and in order to provide
> all its functionality it uses quite a few custom properties in VEVENT and
> VALARM.
https://bugs.kde.org/show_bug.cgi?id=481053
--- Comment #7 from Flossy Cat ---
(In reply to David Jarvie from comment #6)
> The KDE 22.12 branch was effectively closed when 23.04 was created, so I
> wouldn't be willing to apply the fix to it.
When it is closed it is closed …
> I
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #21 from Flossy Cat ---
(In reply to David Faure from comment #20)
> Sorry for derailing the discussions about workarounds with a proper fix ;-)
> (see description in merge request)
Thank you – behavior looks good, judging from r
https://bugs.kde.org/show_bug.cgi?id=481166
Bug ID: 481166
Summary: When entering VTODOs into KALARM's ICAL calender they
are ignored
Classification: Applications
Product: kalarm
Version: 3.5.4.2
Platform: openSUSE
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #17 from Flossy Cat ---
(In reply to David Faure from comment #16)
> I'm working on a patch.
Nice – thank you.
Do you care to explain what kind of patch?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=481053
--- Comment #5 from Flossy Cat ---
(In reply to David Jarvie from comment #4)
> Versions already released by KDE cannot be modified other than by patching
> the source and rebuilding yourself (or by persuading OpenSUSE to issue a
> patche
https://bugs.kde.org/show_bug.cgi?id=481068
--- Comment #4 from Flossy Cat ---
(In reply to fanzhuyifan from comment #3)
> How about let's consolidate the discussion on resupporting this in 481069?
> (That's why I cc'ed 481069 when I closed this report.) We can always reopen
> if
https://bugs.kde.org/show_bug.cgi?id=481068
--- Comment #2 from Flossy Cat ---
My bug report demonstrates there is user request for this feature and the
decision is contended:
https://bugs.kde.org/show_bug.cgi?id=481069
These solitary declarations of unmaintenance show a lack of respect
https://bugs.kde.org/show_bug.cgi?id=481132
Bug ID: 481132
Summary: According documentation »kalarm« allows calendar
directories where each event is a single ICS file – in
practice it doesn't
Classification: Applications
https://bugs.kde.org/show_bug.cgi?id=481129
Bug ID: 481129
Summary: When adding an ICAL calendar file to korganizer the
resource first fails to work then duplicates in the
GUI …
Classification: Applications
Product:
https://bugs.kde.org/show_bug.cgi?id=481053
--- Comment #3 from Flossy Cat ---
(In reply to David Jarvie from comment #2)
> Now fixed for KAlarm version 3.6.4 in KDE Gear 23.08.5 (commit
> a05422923b625f9cf5f1d6f167e6a6d0b3e60b7f) and KAlarm version 3.7.0 in KDE
> Gear 24.0
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #15 from Flossy Cat ---
(In reply to Bernhard E. Reiter from comment #14)
> Two other potential "workarounds" for you (just for completion):
> * Stay on the elder version temporarily (to buy more time for a solution)
Alas
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #13 from Flossy Cat ---
(In reply to Bernhard E. Reiter from comment #10)
> I also find that the regression is a major one. (I've reported this in
> https://bugs.kde.org/show_bug.cgi?id=452264 among other significant
> usability
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #12 from Flossy Cat ---
(In reply to David Faure from comment #9)
> > Actually you should never have removed the original functionality
>
> "You"? Just because I have a @kde.org address does not mean I was part of
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #8 from Flossy Cat ---
(In reply to David Faure from comment #4)
> I was told this was because freedesktop.org notifications don't support
> custom widgets, only a few action buttons, for interoperability with other
> desktop env
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #7 from Flossy Cat ---
Comment on attachment 165676
--> https://bugs.kde.org/attachment.cgi?id=165676
Screenshot of a notifier popup
This screenshots serves as comparison to the information actually provided via
the "execute
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #6 from Flossy Cat ---
Created attachment 165676
--> https://bugs.kde.org/attachment.cgi?id=165676=edit
Screenshot of a notifier popup
This screenshot of a notifier popup serves for comparison with the information
provided to "
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #5 from Flossy Cat ---
VIA KNOTIFIER
(In reply to Flossy Cat from comment #2)
> Possible Workaround: »kalarm«
> ==
> …
> The burning question remains, how to call »kalarm« or create »kalarm«
>
https://bugs.kde.org/show_bug.cgi?id=481069
Bug ID: 481069
Summary: With framework version 6 the option to execute
commands as part of notifications seems gone
Classification: Frameworks and Libraries
Product: frameworks-knotifications
https://bugs.kde.org/show_bug.cgi?id=481068
Bug ID: 481068
Summary: The power to run a command upon a notification is
severely limited by lack of information
Classification: Frameworks and Libraries
Product: frameworks-knotifications
https://bugs.kde.org/show_bug.cgi?id=481063
--- Comment #1 from Flossy Cat ---
I forgot to mention: as a seasoned computer engineer I might help with changes
if brought up to speed …
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #3 from Flossy Cat ---
VIA KORGANIZER
(In reply to Flossy Cat from comment #2)
> Possible Workaround: »kalarm«
> ==
> …
> The burning question remains, how to call »kalarm« or create »kalarm«
>
https://bugs.kde.org/show_bug.cgi?id=481063
Bug ID: 481063
Summary: A reminder option to run a command would enable
valuable use-cases
Classification: Applications
Product: korganizer
Version: 5.22.3
Platform: openSUSE
https://bugs.kde.org/show_bug.cgi?id=481053
--- Comment #1 from Flossy Cat ---
I forgot to mention: as a seasoned computer engineer I might help with changes
if brought up to speed …
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=461233
Flossy Cat changed:
What|Removed |Added
CC||flossy-...@online.de
--- Comment #3 from Flossy
https://bugs.kde.org/show_bug.cgi?id=457046
--- Comment #3 from Flossy Cat ---
(In reply to geekiehiway from comment #0)
I experienced the same issue when upgrading within my distribution.
As neither here nor in the many duplicates I see any progress to a solution,
I've set up a discussion about
https://bugs.kde.org/show_bug.cgi?id=453299
Flossy Cat changed:
What|Removed |Added
CC||flossy-...@online.de
--- Comment #5 from Flossy
https://bugs.kde.org/show_bug.cgi?id=453298
Flossy Cat changed:
What|Removed |Added
CC||flossy-...@online.de
--- Comment #7 from Flossy
https://bugs.kde.org/show_bug.cgi?id=452264
Flossy Cat changed:
What|Removed |Added
CC||flossy-...@online.de
--- Comment #26 from Flossy
https://bugs.kde.org/show_bug.cgi?id=457046
Flossy Cat changed:
What|Removed |Added
CC||flossy-...@online.de
--- Comment #2 from Flossy
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #2 from Flossy Cat ---
Possible Workaround: »kalarm«
==
»kalarm« provides all the necessary functionality to set and postpone alarms
(and even some useful additional functionality).
The burning question remains
https://bugs.kde.org/show_bug.cgi?id=481053
Bug ID: 481053
Summary: kalarm CLI options wrongly transfered to
»--edit-new-display« and actual alarm
Classification: Applications
Product: kalarm
Version: 3.5.4.2
Platform:
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #1 from Flossy Cat ---
SEARCH FOR A WORKAROUND
Within this comment thread I suggest to collect the discussion about
workarounds.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=481024
Bug ID: 481024
Summary: The loss of user-defined snoozing for calendar and
todo reminders is a massive functional regression and
actually a hard show-stopper for my kontact usage
https://bugs.kde.org/show_bug.cgi?id=451825
--- Comment #5 from A weak little orange cat ---
(In reply to Nate Graham from comment #4)
> Thanks for the info.
>
> Are you on Wayland, or X11.
I am using X11 on plasma
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=451825
--- Comment #3 from A weak little orange cat ---
(In reply to A weak little orange cat from comment #2)
> (In reply to Nate Graham from comment #1)
> > Are you using multiple virtual desktops? If so, this is likely Bug 438552.
>
>
https://bugs.kde.org/show_bug.cgi?id=451825
--- Comment #2 from A weak little orange cat ---
(In reply to Nate Graham from comment #1)
> Are you using multiple virtual desktops? If so, this is likely Bug 438552.
No, Not using virtual desktops, But it does have a ghost window on the desk
https://bugs.kde.org/show_bug.cgi?id=451892
Bug ID: 451892
Summary: ark crashes when the URL contained in the text of the
compressed package is opened .
Product: ark
Version: 21.12.2
Platform: Fedora RPMs
dow is
not limited to kwrite, I have also encountered window problems with chrome and
edge.
STEPS TO REPRODUCE
1. after prolonged use.
OBSERVED RESULT
The window becomes transparent, freezes, and does not respond to any events.
EXPECTED RESULT
the same as above.
SOFTWARE/OS VERSIONS
➜ ~ cat /etc
https://bugs.kde.org/show_bug.cgi?id=451824
Bug ID: 451824
Summary: Terminal crashes while building rpm package
Product: konsole
Version: 21.12.2
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords:
https://bugs.kde.org/show_bug.cgi?id=449306
--- Comment #1 from Snowy Cat recieve Bugs ---
Created attachment 146262
--> https://bugs.kde.org/attachment.cgi?id=146262=edit
New crash information added by DrKonqi
plasmashell (5.23.5) using Qt 5.15.3
- What I was doing when the applicat
https://bugs.kde.org/show_bug.cgi?id=449306
Snowy Cat recieve Bugs changed:
What|Removed |Added
CC||yoshiazul2...@gmail.com
--
You
https://bugs.kde.org/show_bug.cgi?id=384029
cat <candrews...@gmail.com> changed:
What|Removed |Added
CC||candrews...@gmail.com
-
64 matches
Mail list logo
