https://bugs.kde.org/show_bug.cgi?id=384029
cat changed:
What|Removed |Added
CC||candrews...@gmail.com
--
You are receiving this mail
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=459995
Flossy Cat changed:
What|Removed |Added
CC||flossy-...@online.de
--- Comment #1 from Flossy
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=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 for
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 reo
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=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=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 #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 readi
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 …
>
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=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=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 Application
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 proces
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=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 appli
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=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 #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
Flossy Cat changed:
What|Removed |Added
Keywords||regression, usability
--- Comment #8 from Flossy
https://bugs.kde.org/show_bug.cgi?id=481166
Flossy Cat changed:
What|Removed |Added
Resolution|INTENTIONAL |FIXED
--- Comment #10 from Flossy Cat ---
(In
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
> remova
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
Platform
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
>
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 idea.
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 #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 with
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 #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 #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
a
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
Classifi
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=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 #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=457046
Flossy Cat changed:
What|Removed |Added
CC||flossy-...@online.de
--- Comment #2 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=453298
Flossy Cat changed:
What|Removed |Added
CC||flossy-...@online.de
--- Comment #7 from Flossy
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=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
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=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=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=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
--- 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=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=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=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=481024
--- Comment #6 from Flossy Cat ---
Created attachment 165676
--> https://bugs.kde.org/attachment.cgi?id=165676&action=edit
Screenshot of a notifier popup
This screenshot of a notifier popup serves for comparison with the information
prov
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 #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
> deskto
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 #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
> usab
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=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=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: korg
https://bugs.kde.org/show_bug.cgi?id=493233
Bug ID: 493233
Summary: Maximize a window cause it no longer update
framebuffer under Wayland
Classification: Plasma
Product: kwin
Version: 6.1.5
Platform: Gentoo Packages
https://bugs.kde.org/show_bug.cgi?id=481024
Flossy Cat changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=491636
--- Comment #4 from Flossy Cat ---
It does not work for all those people:
https://bbs.archlinux.org/viewtopic.php?id=281129
https://forum.manjaro.org/t/how-to-troubleshoot-broken-kde-plasma-window-manager/133533
https://forum.garudalinux.org/t/kwin
https://bugs.kde.org/show_bug.cgi?id=491636
--- Comment #6 from Flossy Cat ---
(In reply to Nate Graham from comment #5)
> I understand it's frustrating for your non-actionable bug report to be
> closed as RESOLVED WORKSFORME,
This is not about frustration, but about attitude.
I
https://bugs.kde.org/show_bug.cgi?id=483545
--- Comment #3 from Flossy Cat ---
(In reply to Bernhard E. Reiter from comment #2)
> Do you know which database akonadi is using for the cache? (Usually it would
> be postgresql, sqlite or mariadb.)
MariaDB 10.11.8-MariaDB source re
https://bugs.kde.org/show_bug.cgi?id=491119
Bug ID: 491119
Summary: Persisting loss of user-defined snoozing for calendar
and todo reminders is a massive functional regression
Classification: Applications
Product: korganizer
Vers
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #29 from Flossy Cat ---
The regression is unresolved Kontact Version: 5.24.5 (23.08.5), which is used
e.g. in OpenSUSE 15.6 and the corresponding SLE 15 (SUSE Linux Enterprise) as
part of the current long term support KDE version, which is
https://bugs.kde.org/show_bug.cgi?id=491130
Bug ID: 491130
Summary: Session management loses state between sessions
Classification: Plasma
Product: plasmashell
Version: 5.27.11
Platform: openSUSE
OS: Linux
Statu
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #31 from Flossy Cat ---
(In reply to David Faure from comment #30)
> It's fixed in 24.02, I'm not sure what else you're asking for. 23.08 is a
> year old, and time machines haven't been invented yet.
Very simple:
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #36 from Flossy Cat ---
Dear Bernhard,
thanking you for your soothing words – but …
(In reply to Bernhard E. Reiter from comment #32)
> Dear @Flossy Cat,
>
> > I personally are very sick of this kind of discussion, of
https://bugs.kde.org/show_bug.cgi?id=431382
Schrödingers Cat changed:
What|Removed |Added
CC||schroedingers...@disroot.or
https://bugs.kde.org/show_bug.cgi?id=390503
Schrödingers Cat changed:
What|Removed |Added
CC||schroedingers...@disroot.or
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #38 from Flossy Cat ---
(In reply to David Faure from comment #34)
> It is a bit contradictory to want to use a "stable LTS version" (which means
> no new features) and then ask for a new feature to be added to it. I know
&g
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #39 from Flossy Cat ---
(In reply to Martin Steigerwald from comment #33)
> I understand your frustrations, Flossy Cat. I truly do. KDEPIM has been a
> big trigger of frustrations for me as well.
Thanks for your quantum of solac
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #40 from Flossy Cat ---
Dear Bernhard,
(In reply to Bernhard E. Reiter from comment #32)
> … You were asking for alternatives, I know of Claws mail
> which has is a small but long term team behind it. …
Thanx for the hint. But Cl
https://bugs.kde.org/show_bug.cgi?id=491130
--- Comment #2 from Flossy Cat ---
(In reply to Kishore Gopalakrishnan from comment #1)
> I also seem to have a similar issue. When this happens again, can you check
> if you have messages like the following in your system logs?
>
> ```
&g
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #42 from Flossy Cat ---
Hi Bernhard,
(In reply to Bernhard E. Reiter from comment #37)
> …
> > F5: In both bug reports I offered my help and support for implementation
> > as a seasoned computer engineer if I'm poi
https://bugs.kde.org/show_bug.cgi?id=481024
--- Comment #44 from Flossy Cat ---
(In reply to Martin Steigerwald from comment #43)
> …
> 1) Researched yourself where a suitable place for offering help would be. It
> could be kde-pim mailing list. It could be their Matrix channel. It
https://bugs.kde.org/show_bug.cgi?id=483545
--- Comment #1 from Flossy Cat ---
Kmail loses e-mails on my productive system too.
Lost were mails in the "sent" folder – that is: recent e-mails according
current standards generated by Kmail itself.
There seems to be a very funda
https://bugs.kde.org/show_bug.cgi?id=491636
Bug ID: 491636
Summary: Kwin crashes out of the blue on an unloaded system
Classification: Plasma
Product: kwin
Version: 5.27.11
Platform: openSUSE
OS: Linux
Status: R
https://bugs.kde.org/show_bug.cgi?id=491636
--- Comment #2 from Flossy Cat ---
(In reply to Zamundaaa from comment #1)
> Please get a backtrace for the crash:
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_cras
https://bugs.kde.org/show_bug.cgi?id=493274
Rin Cat changed:
What|Removed |Added
CC||rin...@rincat.dev
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=493233
--- Comment #3 from Rin Cat ---
I've noticed a strange behavior. If I first occupy half of the window close to
the taskbar and then maximize it, this abnormal behavior does not occur.
However, if I first occupy the half far from the taskbar and
https://bugs.kde.org/show_bug.cgi?id=493233
--- Comment #4 from Rin Cat ---
Created attachment 173957
--> https://bugs.kde.org/attachment.cgi?id=173957&action=edit
Maximize from left to right
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=493919
--- Comment #8 from Flossy Cat ---
Created attachment 174281
--> https://bugs.kde.org/attachment.cgi?id=174281&action=edit
Screen shots documenting the solution path for the allegedly "LOST" game
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=493919
--- Comment #5 from Flossy Cat ---
Created attachment 174278
--> https://bugs.kde.org/attachment.cgi?id=174278&action=edit
Screen shots documenting the solution path for the allegedly "LOST" game
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=493919
--- Comment #9 from Flossy Cat ---
Created attachment 174282
--> https://bugs.kde.org/attachment.cgi?id=174282&action=edit
Screen shots documenting the solution path for the allegedly "LOST" game
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=493919
Bug ID: 493919
Summary: Solver falsely claims unsolvable and lost games
Classification: Applications
Product: kpat
Version: 23.08.5
Platform: Compiled Sources
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=493918
Flossy Cat changed:
What|Removed |Added
Blocks||493919
Referenced Bugs:
https://bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=493919
--- Comment #7 from Flossy Cat ---
Created attachment 174280
--> https://bugs.kde.org/attachment.cgi?id=174280&action=edit
Screen shots documenting the solution path for the allegedly "LOST" game
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=481069
--- Comment #39 from Flossy Cat ---
(In reply to Andreas Schneider from comment #38)
> The merge request has been closed :-(
>
> https://invent.kde.org/frameworks/knotifications/-/merge_requests/143
Thank you for the information – and thank
https://bugs.kde.org/show_bug.cgi?id=493919
--- Comment #3 from Flossy Cat ---
Created attachment 174275
--> https://bugs.kde.org/attachment.cgi?id=174275&action=edit
Screen shots documenting the solution path for the allegedly "unwinnable" game
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=493919
--- Comment #2 from Flossy Cat ---
Created attachment 174274
--> https://bugs.kde.org/attachment.cgi?id=174274&action=edit
Screen shots documenting the solution path for the allegedly "unwinnable" game
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=493919
--- Comment #6 from Flossy Cat ---
Created attachment 174279
--> https://bugs.kde.org/attachment.cgi?id=174279&action=edit
Screen shots documenting the solution path for the allegedly "LOST" game
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=493918
Bug ID: 493918
Summary: Suit of 2 under other cards not determinable
Classification: Applications
Product: kpat
Version: 23.08.5
Platform: Compiled Sources
OS: Linux
S
https://bugs.kde.org/show_bug.cgi?id=481069
--- Comment #48 from Flossy Cat ---
(In reply to Nate Graham from comment #45)
> I too am dissatisfied with the resolution here, but let me correct the
> record on one thing right now: bugs.kde.org is not violating the GDPR.
> There's a b
https://bugs.kde.org/show_bug.cgi?id=481069
--- Comment #44 from Flossy Cat ---
Farewell to everyone, who has tried to contribute to a good solution.
I did some bug-reporting on KDE the last months and essentially these bug
reports were either not acted upon or in a very unsatisfying manner
https://bugs.kde.org/show_bug.cgi?id=493919
--- Comment #1 from Flossy Cat ---
Created attachment 174273
--> https://bugs.kde.org/attachment.cgi?id=174273&action=edit
Screen shots documenting the solution path for the allegedly "unwinnable" game
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=493233
--- Comment #2 from Rin Cat ---
(In reply to Vlad Zahorodnii from comment #1)
> Please check kwin's logs `journalctl --user-unit --boot plasma-kwin_wayland`
I am using OpenRC, so I checked log in
`~/.local/share/sddm/wayland-session.log`.
https://bugs.kde.org/show_bug.cgi?id=493919
--- Comment #4 from Flossy Cat ---
Created attachment 174277
--> https://bugs.kde.org/attachment.cgi?id=174277&action=edit
Screen shots documenting the solution path for the allegedly "LOST" game
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=493233
Rin Cat changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
--- Comment #6 from Rin Cat ---
After a
https://bugs.kde.org/show_bug.cgi?id=500819
--- Comment #22 from Rin Cat ---
(In reply to samoht0 from comment #19)
> I'd guess, the driver rejecting is triggered here.
>
> https://github.com/KDE/kwin/commit/9dd70310eb016625313a0e81b6b49e98e64fff6a
>
> There might be ex
https://bugs.kde.org/show_bug.cgi?id=500819
Rin Cat changed:
What|Removed |Added
CC||rin...@rincat.dev
--- Comment #15 from Rin Cat
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&action=edit
New crash information added by DrKonqi
plasmashell (5.23.5) using Qt 5.15.3
- What I was doing w
1 - 100 of 107 matches
Mail list logo
