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
https://bugs.kde.org/show_bug.cgi?id=438313
--- Comment #48 from Manuel Geißer ---
Thanks! It now works correctly ;)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=425749
--- Comment #10 from Manuel Geißer ---
Update: PyQt5 got updated to 5.15 some time ago, and PySide2 toady. Many
thanks!!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=425749
--- Comment #11 from Manuel Geißer ---
Hmm, but unfortunately something went wrong. I just applied the update and now
PySide2 apparently is broken more or less compeletely. Some of my code directly
terminates with a segmentation fault, some does only
https://bugs.kde.org/show_bug.cgi?id=425749
--- Comment #12 from Manuel Geißer ---
In gdb:
Reading symbols from python3...
Reading symbols from
/usr/lib/debug/.build-id/9c/096cdc8214a805dca8d174fe072684b0f21645.debug...
(gdb) run
Starting program: /usr/bin/python3 pyside2_test.py
[Thread
https://bugs.kde.org/show_bug.cgi?id=425749
--- Comment #13 from Manuel Geißer ---
I tried to roll back, but apparently that's not easily possible.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=425749
--- Comment #15 from Manuel Geißer ---
(In reply to Jonathan Riddell from comment #14)
Thank you for looking into it. Yes, my system is fully up to date.
I can use the pyside2 binaries from PyPI for now, but anyway I'd like to know
the cause fo
https://bugs.kde.org/show_bug.cgi?id=425749
--- Comment #16 from Manuel Geißer ---
> I can run your example python app fine.
And you're sure you don't have the PyPI version of pyside2 installed?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=439477
Bug ID: 439477
Summary: Clicking on links in Qt/KDE apps causes the website to
be cached, rather than the link being forwarded to the
browser
Product: frameworks-kio
Ver
https://bugs.kde.org/show_bug.cgi?id=439477
--- Comment #1 from Manuel Geißer ---
Created attachment 139847
--> https://bugs.kde.org/attachment.cgi?id=139847&action=edit
Screenshot illustrating the problem
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=439477
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
CC||n...@kde.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=439478
Bug ID: 439478
Summary: Menu/tooltip background is transparent
Product: frameworks-kirigami
Version: 5.83.0
Platform: Neon Packages
OS: Linux
Status: REPORTED
Se
https://bugs.kde.org/show_bug.cgi?id=439480
Bug ID: 439480
Summary: Google accounts can't be added
Product: kmail2
Version: Git (master)
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: critica
https://bugs.kde.org/show_bug.cgi?id=439480
Manuel Geißer changed:
What|Removed |Added
CC||geisse...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=435690
--- Comment #25 from Manuel Geißer ---
So this means we can expect the bug to be already fixed in newer version of
Plasma?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=433071
--- Comment #4 from Manuel Geißer ---
This is still troubling me - I'd like to have the background wallpaper in Show
Desktop Grid back at some point, but I am not really enthusiastic about
switching to a new user account - I've done
https://bugs.kde.org/show_bug.cgi?id=433484
--- Comment #7 from Manuel Geißer ---
I filed another bug report with NodeGraphQt:
https://github.com/jchanvfx/NodeGraphQt/issues/207
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=436409
Bug ID: 436409
Summary: Locked packages cannot be unlocked
Product: muon
Version: 5.8.0
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: grave
https://bugs.kde.org/show_bug.cgi?id=436409
Manuel Geißer changed:
What|Removed |Added
CC||geisse...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=436412
Bug ID: 436412
Summary: Package dependency option cannot be changed
Product: muon
Version: 5.8.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: major
https://bugs.kde.org/show_bug.cgi?id=436412
--- Comment #1 from Manuel Geißer ---
Of course it is good to have a global option on whether to select optional
dependencies by default, but I think a per-package option/checkbox would be an
important complement.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=433071
--- Comment #5 from Manuel Geißer ---
Still missing my wallpaper...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=436412
Manuel Geißer changed:
What|Removed |Added
CC||geisse...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=436409
--- Comment #1 from Manuel Geißer ---
It would be important if at least someone could tell how to manually revert
locking a package (e. g. from command-line or via another package manager),
since this issue could potentially break system updates
https://bugs.kde.org/show_bug.cgi?id=436409
Manuel Geißer changed:
What|Removed |Added
CC||aleix...@kde.org
https://bugs.kde.org/show_bug.cgi?id=436409
Manuel Geißer changed:
What|Removed |Added
CC||sit...@kde.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=433071
--- Comment #6 from Manuel Geißer ---
Wallpaper, please come back :/
--
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|20.12.2 |21.04.0
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=424024
--- Comment #12 from Manuel Geißer ---
The problem persists in Lokalize 21.04.0
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=424024
--- Comment #14 from Manuel Geißer ---
typo Platorm
QPlatformWindow::QPlatformWindow would be correct
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=424024
--- Comment #15 from Manuel Geißer ---
It occurs fairly often in fact, about 45 breakpoints until the main window
turns up.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=424024
--- Comment #16 from Manuel Geißer ---
However, I'm not sure whether this is the right approach. This is not one of
the classical Qt/Wayland rendering issues; and no breakpoint happens when the
window doesn't repaint properly.
--
You are
https://bugs.kde.org/show_bug.cgi?id=390021
Manuel Geißer changed:
What|Removed |Added
CC||geisse...@gmail.com
--- Comment #7 from Manuel
https://bugs.kde.org/show_bug.cgi?id=436576
Bug ID: 436576
Summary: Line numbers panel becomes transparent for a short
moment when saving/reloading und Wayland
Product: kate
Version: 21.04.0
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=436576
Manuel Geißer changed:
What|Removed |Added
Keywords||wayland
CC
https://bugs.kde.org/show_bug.cgi?id=436576
--- Comment #1 from Manuel Geißer ---
I might have reported this in the wrong product/component, so feel free to move
the issue if you know a better place.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=433484
--- Comment #8 from Manuel Geißer ---
I think I have found the cause for Scantailor Advanced: It's the same as with
Gwenview and NodeGraphQt - the deprecated QGLWidget. I ran a recursive grep
across the source tree which found:
```
src
https://bugs.kde.org/show_bug.cgi?id=433484
--- Comment #10 from Manuel Geißer ---
I have created a simple patch for STA that appears to work for me (first time
ever that I write some c++). I'm not sure what to do about this format thing.
Is it still necessary for QOpenGLWidget? If so, h
https://bugs.kde.org/show_bug.cgi?id=433484
--- Comment #11 from Manuel Geißer ---
ScanTailor Advanced is unmaintained, so filing a bug is pointless, sadly. I'll
upload the patch to my personal STA repository soon.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=433484
--- Comment #12 from Manuel Geißer ---
What I find really confusing, ScanTailor Experimental by the original author
Joseph Artsimovich uses QGLWidget, too, but there it actually works on Wayland,
and it's way faster too. Not sure why.
See
https://bugs.kde.org/show_bug.cgi?id=433484
--- Comment #13 from Manuel Geißer ---
Oh, I just see Qt/OpenGL support behind an ifdef guard in STE:
```
#ifdef ENABLE_OPENGL
#include
#include
#endif
```
Probably I just built without it and the setting got silently ignored, that
would be a good
https://bugs.kde.org/show_bug.cgi?id=433484
--- Comment #14 from Manuel Geißer ---
* is behind
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=433071
--- Comment #7 from Manuel Geißer ---
wallpaper &>/dev/null
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=436576
Manuel Geißer changed:
What|Removed |Added
CC||cullm...@kde.org
https://bugs.kde.org/show_bug.cgi?id=435574
--- Comment #22 from Manuel Geißer ---
(In reply to Harald Sitter from comment #3)
> Can you outline heuristics for what requires a reboot and what does not?
Hmm, is there a list of which other packages depend on a package? Then a basic
heuristic wo
https://bugs.kde.org/show_bug.cgi?id=435574
--- Comment #23 from Manuel Geißer ---
A definitely more complex heuristic would be to somehow check whether any
binary provided by a package to be updated is currently in use. If it is not,
the update could be performed without reboot, but then it
201 - 300 of 427 matches
Mail list logo
