https://bugs.kde.org/show_bug.cgi?id=441673
--- Comment #13 from Manuel Geißer ---
I just installed the two packages. Works perfectly in Gwenview and Dolphin now
:)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=441312
--- Comment #12 from Manuel Geißer ---
Well, obviously I disagree very much.
> Without relatively big icons, the whole overview effect will become useless
> for me.
*With* icons it becomes useless. The purpose of an overview effect is to
q
https://bugs.kde.org/show_bug.cgi?id=441312
--- Comment #13 from Manuel Geißer ---
too difficult *to identify
pardon
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=441312
--- Comment #16 from Manuel Geißer ---
Oh, so to my bad luck this mis-feature got addded. And it seems it's not even
optional.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=441312
--- Comment #17 from Manuel Geißer ---
(In reply to Nate Graham from comment #14)
> Two things are clear:
>
> 1. People use this effect in different ways based on what's most comfortable
> for them; one size does not fit all.
>
https://bugs.kde.org/show_bug.cgi?id=441312
--- Comment #18 from Manuel Geißer ---
(In reply to Nate Graham from comment #14)
> 2. Thew more we argue, the less likely it is that we will agree on anything
> as we become more entrenched in our original positions.
I generally prefer good oppo
https://bugs.kde.org/show_bug.cgi?id=441312
--- Comment #20 from Manuel Geißer ---
> everyone thinks they're right
Some give meaningful reasons, others don't.
> I am trying to help you be effective here.
I care about correct and comprehensible decisions, not necessarily about
https://bugs.kde.org/show_bug.cgi?id=441312
--- Comment #21 from Manuel Geißer ---
Clarification to self about the Present Windows issues:
No one of ever wanted to fix them, it was all intentional. Surely devs as
capable as Nate, Vlad or David could have commented out the dimming and all the
https://bugs.kde.org/show_bug.cgi?id=441312
--- Comment #23 from Manuel Geißer ---
Okay, hiding my comments as spam - really?
Anyway, I think I have expressed my POV clearly and said everything that I
consider relevant. This conversations is now a waste of time. If you ever
happen to change your
https://bugs.kde.org/show_bug.cgi?id=441312
Manuel Geißer changed:
What|Removed |Added
CC|geisse...@gmail.com |
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=441312
--- Comment #24 from Manuel Geißer ---
Created attachment 141270
--> https://bugs.kde.org/attachment.cgi?id=141270&action=edit
Just in case anyone wants to enframe this conversation
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=441312
Manuel Geißer changed:
What|Removed |Added
CC||geisse...@gmail.com
--- Comment #26 from
https://bugs.kde.org/show_bug.cgi?id=441312
--- Comment #28 from Manuel Geißer ---
> I'd be quite interested in the scorcher Martin Keary alias Tantacrul would
> give
> you if he ever tested Present Windows or Overview...
Ah, I really can't wait for that scorcher... I nee
https://bugs.kde.org/show_bug.cgi?id=441312
Manuel Geißer changed:
What|Removed |Added
CC|geisse...@gmail.com |
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=441312
--- Comment #27 from Manuel Geißer ---
One thing I've learned now: Before judging a software project, look at how
developers act in its bug tracker. Then you will find out whether they are
friendly or unfriendly, competent or incompetent people
https://bugs.kde.org/show_bug.cgi?id=442012
Bug ID: 442012
Summary: [python3] Keywords-only enforcement using `*,` partly
breaks syntax highlighting
Product: frameworks-syntax-highlighting
Version: 5.85.0
Platform: Neon Pac
https://bugs.kde.org/show_bug.cgi?id=442012
Manuel Geißer changed:
What|Removed |Added
CC||geisse...@gmail.com
--- Comment #1 from Manuel
https://bugs.kde.org/show_bug.cgi?id=442012
--- Comment #2 from Manuel Geißer ---
At first I was a bit puzzled by this issue because stopping syntax highlighting
first gave me the impression that there was a fault in my code.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=439478
--- Comment #1 from Manuel Geißer ---
Created attachment 139967
--> https://bugs.kde.org/attachment.cgi?id=139967&action=edit
kcm_style transparent menu
Another screenshoot (kcmshell5 kcm_style)
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=439478
Manuel Geißer changed:
What|Removed |Added
CC||geisse...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=439477
Manuel Geißer changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=439477
--- Comment #5 from Manuel Geißer ---
I think this can't be the problem. The default browser is recognised properly,
as the cached file is opened in it. Was the description unclear?
--
You are receiving this mail because:
You are watching al
https://bugs.kde.org/show_bug.cgi?id=303438
--- Comment #58 from Manuel Geißer ---
> If we don't implement that, then the work is only half-finished
> and we will get bug reports about *that*.
It was designed to be optional. No one will bother to file a bug report.
I wonder whether i
https://bugs.kde.org/show_bug.cgi?id=439780
Bug ID: 439780
Summary: kio does not compile with libc++ due to the use of the
(obsolete and removed) std::mem_fun
Product: frameworks-kio
Version: 5.84.0
Platform: Gentoo Package
https://bugs.kde.org/show_bug.cgi?id=303438
--- Comment #60 from Manuel Geißer ---
Lol, we've repeatedly mentioned this before. It's in the issue description,
second sentence:
> I feel that enlarging the thumbnail under the mouse is a sufficient
> indication of focus
But if yo
https://bugs.kde.org/show_bug.cgi?id=439780
--- Comment #3 from Manuel Nickschas ---
Thanks, this fixes the issue for me! I wasn't completely sure if it can just be
replaced, thus I didn't offer a patch myself.
Kudos for the quick reaction!
--
You are receiving this mail becaus
https://bugs.kde.org/show_bug.cgi?id=303438
--- Comment #64 from Manuel Geißer ---
@hvm @Leonardo
Apparently there is a little misunderstanding. I don't mean to develop/maintain
a fork of Present Windows, I just intend(ed) to compile the version without
dimming locally (from the reject
https://bugs.kde.org/show_bug.cgi?id=439477
--- Comment #7 from Manuel Geißer ---
I think I did selected from the open-with dialog of the kcm, so the linked PR
is likely to fix the problem. Thanks in advance!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=439477
--- Comment #9 from Manuel Geißer ---
By the way, may I ask why the permanent cache ~/.cache/kioexec/krun/ exists at
all? Wouldn't regular tempfiles that are removed at the end of a session make
more sense?
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=439477
--- Comment #11 from Manuel Geißer ---
Yeah, I'll do that.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=439886
Bug ID: 439886
Summary: Remove `~/.cache/kioexec/krun/` and use regular
temporary files instead
Product: frameworks-kio
Version: 5.84.0
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=439477
--- Comment #12 from Manuel Geißer ---
https://bugs.kde.org/show_bug.cgi?id=439886
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=439886
Manuel Geißer changed:
What|Removed |Added
Platform|Other |Neon Packages
CC
https://bugs.kde.org/show_bug.cgi?id=439478
--- Comment #2 from Manuel Geißer ---
Created attachment 140110
--> https://bugs.kde.org/attachment.cgi?id=140110&action=edit
System Monitor
The new System Monitor is affected as well
--
You are receiving this mail because:
You are watch
https://bugs.kde.org/show_bug.cgi?id=439478
Manuel Geißer changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=439478
--- Comment #3 from Manuel Geißer ---
Would be really nice if something could be done about this. Transparent menus
is rather annoying ;)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=439938
Bug ID: 439938
Summary: System Monitor causes the system to overload and
freeze
Product: plasma-systemmonitor
Version: 5.22.3
Platform: Neon Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=439938
Manuel Geißer changed:
What|Removed |Added
CC||geisse...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=439938
Manuel Geißer changed:
What|Removed |Added
Status|RESOLVED|REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=439938
--- Comment #3 from Manuel Geißer ---
> We need some logs to prove what's actually at fault.
Which logs / files do you need?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=439938
--- Comment #4 from Manuel Geißer ---
> Manuel Geißer 2021-07-16 10:07:12 UTC
> David Edmundson 2021-07-16 10:17:08 UTC
>From looking at when you responded, you barely had enough time to try and
reproduce, so please don't claim yet
https://bugs.kde.org/show_bug.cgi?id=439938
--- Comment #5 from Manuel Geißer ---
Not sure whether this matters, but when I had the system monitor running it
lately did not display the graphs, animations, etc. I'd uploaded a screenshot
to Bug 439478 (https://bugsfiles.kde.org/attachment.c
https://bugs.kde.org/show_bug.cgi?id=439478
Manuel Geißer changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=439780
--- Comment #6 from Manuel Nickschas ---
(In reply to Ahmad Samir from comment #5)
> It seems I need to add -stdlib=libc++ to the compiler flags for clang to use
> libc++, I'll test that next :)
Yes, you either need to configure Clang to us
https://bugs.kde.org/show_bug.cgi?id=439938
Manuel Geißer changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=439938
--- Comment #8 from Manuel Geißer ---
Apparently this error message just meant I did not have qmlscene installed.
After installing the qmlscene package, I do see the graphs and there are no cpu
spikes.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=439938
--- Comment #9 from Manuel Geißer ---
I reinstalled the system monitor, but still don't see any graphs. Also, the
program terminates with a segfault on exit...
Here's a backtrace (probably useless due to missing symbols, but I can redo
it):
https://bugs.kde.org/show_bug.cgi?id=439938
--- Comment #10 from Manuel Geißer ---
Now I installed some symbols (namely plasma-systemmonitor-dbgsym and
qml-module-qtqml-dbgsym), and a segfault is not reproducable anymore after
installing the latter. Really strange.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=303438
--- Comment #71 from Manuel Geißer ---
Interesting. Thanks for sharing it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438875
--- Comment #3 from Manuel Geißer ---
PID: 1020 (plasmashell)
UID: 1000 (manuel)
GID: 1001 (manuel)
Signal: 11 (SEGV)
Timestamp: Thu 2021-07-29 11:22:52 CEST (16s ago)
Command Line: /usr/bin/plasmashell
https://bugs.kde.org/show_bug.cgi?id=438875
Manuel Geißer changed:
What|Removed |Added
Resolution|BACKTRACE |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=438875
--- Comment #4 from Manuel Geißer ---
Again, now with symbols and gdb backtrace:
PID: 1630 (plasmashell)
UID: 1000 (manuel)
GID: 1001 (manuel)
Signal: 11 (SEGV)
Timestamp: Thu 2021-07-29 11:27:50 CEST (19s
https://bugs.kde.org/show_bug.cgi?id=349519
--- Comment #139 from Manuel Geißer ---
Wow. I hadn't seen an issue with so many duplicates yet. Could anything be done
about it on the Plasma side?
I'm not sure whether Bug 438875 really is a duplicate of this issue, since it
affects on
https://bugs.kde.org/show_bug.cgi?id=438875
--- Comment #6 from Manuel Geißer ---
Are you sure about the duplicate? This issue is Wayland-only, and it seems Bug
349519 is not...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438875
--- Comment #8 from Manuel Geißer ---
I have never experienced any such condition under Plasma X11, so I think this
might deserve further investigation. At least 95% of my Plasma Wayland crashes
are caused by this issue. I wonder whether other users
https://bugs.kde.org/show_bug.cgi?id=438875
--- Comment #9 from Manuel Geißer ---
Also, the fact that the issue is easier to trigger when system workload is high
sounds suspicious to me. Possibly a race condition?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=433484
--- Comment #17 from Manuel Geißer ---
I finally uploaded the ScanTailor Advanced patch:
https://github.com/4lex4/scantailor-advanced/pull/179/files
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=439478
Manuel Geißer changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=439478
--- Comment #8 from Manuel Geißer ---
Just confirmed it does also reproduce with the default schemes.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=439478
--- Comment #9 from Manuel Geißer ---
I wonder whether my QtQuick install might be somewhat damaged in general,
because of the strange issues I had/have with the System Monitor (graphs not
visible, sometimes unusually high resource demand).
--
You
https://bugs.kde.org/show_bug.cgi?id=439478
--- Comment #11 from Manuel Geißer ---
> Please let us know what you discover after some further investigation.
What should I look for? I can't remember having done anything unusual that
could cause such problems...
The issues I had with PySi
https://bugs.kde.org/show_bug.cgi?id=435574
--- Comment #40 from Manuel Geißer ---
I took a look at Tracer. I installed it from source on Neon User, but it
doesn't really work, searching for outdated packages fails with a
NotImplementedError and showing specific packages with a FileNotFound
https://bugs.kde.org/show_bug.cgi?id=303438
--- Comment #73 from Manuel Geißer ---
I agree that dimming should be disabled (or at least there should be an option
added to do so) in the classical Present Windows, as it will yet take time
until the new QML replacement is ready for use. It would be
https://bugs.kde.org/show_bug.cgi?id=303438
--- Comment #76 from Manuel Geißer ---
> There is absolutely nothing constructive or helpful in this bug report.
> Closing.
No. This is completely wrong (and quite instuling towards the reporters). There
have been lots of constructive, reason
https://bugs.kde.org/show_bug.cgi?id=303438
--- Comment #77 from Manuel Geißer ---
In any case, closing this report and claming it were not a bug is wrong.
You need to acknowledge that too strongly dimmed windows clearly are a
usability issue, there can be no doubt whatsoever. Since this issue
https://bugs.kde.org/show_bug.cgi?id=303438
--- Comment #78 from Manuel Geißer ---
* Developer's -> Developers'
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=303438
--- Comment #79 from Manuel Geißer ---
Once the new QML Present Windows without dimming effect is merged, I would be
fine with closing the report, but as long as this is not the case, it should be
kept open.
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=436409
--- Comment #2 from Manuel Geißer ---
Now found out how to manually revert the lock:
go to /etc/apt/preferences.d/ and delete the problematic files (konsole and
konsole-kpart in my case)
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=438870
Bug ID: 438870
Summary: Opening files wrongly causes the previous opening task
to be performed
Product: frameworks-kio
Version: unspecified
Platform: Neon Packages
https://bugs.kde.org/show_bug.cgi?id=438870
Manuel Geißer changed:
What|Removed |Added
CC||geisse...@gmail.com
Version
https://bugs.kde.org/show_bug.cgi?id=438870
Manuel Geißer changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=431505
Manuel Geißer changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=438875
Bug ID: 438875
Summary: Toggling the application launcher sometimes crashes
Plasmashell on Wayland
Product: plasmashell
Version: master
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=438875
Manuel Geißer changed:
What|Removed |Added
CC||geisse...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=438875
Manuel Geißer changed:
What|Removed |Added
Keywords||wayland
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=438875
--- Comment #1 from Manuel Geißer ---
This bug is around since I use Plasma Wayland, so it's not a regression.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=424024
Manuel Geißer changed:
What|Removed |Added
Version|21.04.0 |21.04.2
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=424024
--- Comment #17 from Manuel Geißer ---
(In reply to David Edmundson from comment #13)
> Put a breakpoint on QPlatformWindow::QPlatormWindow
>
> it should occur once for the top level and again for menus, any others are
> your source o
https://bugs.kde.org/show_bug.cgi?id=431505
--- Comment #13 from Manuel Geißer ---
It was certainly intentional. If you read my previous comment you should know
why.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431505
Manuel Geißer changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=438905
Bug ID: 438905
Summary: Icons and texts on top of window previews are too
large
Product: kwin
Version: unspecified
Platform: Other
OS: Linux
Status: RE
https://bugs.kde.org/show_bug.cgi?id=438905
Manuel Geißer changed:
What|Removed |Added
CC||geisse...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=438905
Manuel Geißer changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=438905
--- Comment #1 from Manuel Geißer ---
As far as I can see, the problematic commit is 1a9b5259
https://invent.kde.org/plasma/kwin/-/commit/1a9b5259707ade9496256d35ae8ee1761989251e
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=438906
Bug ID: 438906
Summary: Don't darken panel in Present Windows effect (revert
64c72157 and a2ed8cb9)
Product: kwin
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=438906
Manuel Geißer changed:
What|Removed |Added
Version|unspecified |5.22.1
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=303438
Manuel Geißer changed:
What|Removed |Added
CC||geisse...@gmail.com
--- Comment #41 from
https://bugs.kde.org/show_bug.cgi?id=303438
--- Comment #42 from Manuel Geißer ---
:/
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438906
Manuel Geißer changed:
What|Removed |Added
CC||geisse...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=438906
Manuel Geißer changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=303438
--- Comment #43 from Manuel Geißer ---
I honestly don't get it: Since 9 years (!) users are arguing in a very clear
and understandable way that darkening the windows is not a good idea. Someone
sends a merge request to fix it. And what ha
https://bugs.kde.org/show_bug.cgi?id=303438
--- Comment #45 from Manuel Geißer ---
(In reply to Nate Graham from comment #44)
> The merge request will be merged once there is a highlight effect to replace
> the darkening effect. If we don't do that, we're just replacing one issu
https://bugs.kde.org/show_bug.cgi?id=303438
--- Comment #47 from Manuel Geißer ---
(In reply to Michael D from comment #46)
Yep, I concur.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438905
--- Comment #3 from Manuel Geißer ---
> This was an intentional change.
I know. But it was a bad one.
> We wanted to make the icons larger so that people who recognize windows on
> the basis of the parent app's icon (and there are suc
https://bugs.kde.org/show_bug.cgi?id=438906
--- Comment #2 from Manuel Geißer ---
> The desktop gets darkened too.
The desktop does not show application switchers. This is a completely different
thing; the comparison is inappropriate.
> The whole point is to reduce visual focus on ever
https://bugs.kde.org/show_bug.cgi?id=303438
--- Comment #48 from Manuel Geißer ---
> All the talk in the world won't change that, sorry.
Many good arguments supporting our point of view have been presented.
What's the point at continuing to ignore them? This would only demonst
https://bugs.kde.org/show_bug.cgi?id=303438
--- Comment #51 from Manuel Geißer ---
(In reply to Nate Graham from comment #49)
> I understand that you're upset, but insulting the people with the power do
> do what you're asking may not be the most effective technique. :)
Don&#
https://bugs.kde.org/show_bug.cgi?id=303438
--- Comment #53 from Manuel Geißer ---
> We made a very minor changes that were purely visuals and you opened 2 bug
> reports immediately
The sole purpose of the Present Windows effect is visuals. I opened bug reports
because I saw the appe
https://bugs.kde.org/show_bug.cgi?id=303438
--- Comment #54 from Manuel Geißer ---
> We know that this change *will* result in a usability issue, I know that I
> will
> get more feedback.
If something is a disimprovement, why not stick to the status quo?
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=303438
--- Comment #55 from Manuel Geißer ---
"We know that this change *will* result in a usability issue" <-> "If something
is not a direct improvement we stick to the status quo."
Contradiction in terms?
--
You are receiving
201 - 300 of 775 matches
Mail list logo
