https://bugs.kde.org/show_bug.cgi?id=499913
--- Comment #30 from Tsu Jan ---
(In reply to Bug Janitor Service from comment #28)
> A possibly relevant merge request was started @
> https://invent.kde.org/plasma/kwin/-/merge_requests/7225
IMHO, a `for (;;)` loop is always dangerous,
https://bugs.kde.org/show_bug.cgi?id=499913
--- Comment #18 from Tsu Jan ---
(In reply to Jean-Francois Ostiguy from comment #17)
> Unfortunately https://bugs.kde.org/show_bug.cgi?id=500015#c5 is an
> improvement but not a solution.
It's definitely not a fix, but only a way of a
https://bugs.kde.org/show_bug.cgi?id=499913
--- Comment #14 from Tsu Jan ---
The change mentioned at https://bugs.kde.org/show_bug.cgi?id=500015#c5 worked
for me (with kwin_wayland). But the compilation of KWin took a long time and
made my CPU temperature reach 95°C; so, I won't do it
https://bugs.kde.org/show_bug.cgi?id=499913
--- Comment #12 from Tsu Jan ---
(In reply to TheFeelTrain from comment #11)
> I think this is the return of a bug I reported over a year ago:
> https://bugs.kde.org/show_bug.cgi?id=479786
>
> There may be some useful info in the pre
https://bugs.kde.org/show_bug.cgi?id=499913
Tsu Jan changed:
What|Removed |Added
CC||tsujan2...@gmail.com
--- Comment #10 from Tsu Jan
https://bugs.kde.org/show_bug.cgi?id=481977
Tsu Jan changed:
What|Removed |Added
CC||tsujan2...@gmail.com
--- Comment #26 from Tsu Jan
https://bugs.kde.org/show_bug.cgi?id=473170
--- Comment #3 from Tsu Jan ---
> Ahh of course, it's Bug 470925. It's fixed in Qt 6.6.
Thanks for the info! We needed it in LXQt.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=473170
Tsu Jan changed:
What|Removed |Added
CC||tsujan2...@gmail.com
--- Comment #1 from Tsu Jan
https://bugs.kde.org/show_bug.cgi?id=463951
Tsu Jan changed:
What|Removed |Added
CC||tsujan2...@gmail.com
--- Comment #2 from Tsu Jan
https://bugs.kde.org/show_bug.cgi?id=418891
--- Comment #7 from Tsu Jan ---
After a long search in Qt's code and finding no problem in it, I started to get
suspicious of the old dragging code of Breeze/Kvantum/QtCurve and, finally,
succeeded in replacing it with another code structure
https://bugs.kde.org/show_bug.cgi?id=418891
--- Comment #6 from Tsu Jan ---
Oh, I'd added a code comment to Kvantum: It started to happen with Qt5.11.
Before 5.11, the code worked fine everywhere: Breeze, Kvantum and QtCurve used
it with some variations (I think the original code came
https://bugs.kde.org/show_bug.cgi?id=418891
--- Comment #4 from Tsu Jan ---
It isn't related to resuming. You should put the mouse cursor over widgets that
have a hover effect (like toolbar buttons).
Actually, it isn't limited to Breeze; it happens with QtCurve too. It also
hap
https://bugs.kde.org/show_bug.cgi?id=418891
Tsu Jan changed:
What|Removed |Added
CC||tsujan2...@gmail.com
--- Comment #2 from Tsu Jan
https://bugs.kde.org/show_bug.cgi?id=427871
Tsu Jan changed:
What|Removed |Added
CC||tsujan2...@gmail.com
--- Comment #3 from Tsu Jan
https://bugs.kde.org/show_bug.cgi?id=346687
--- Comment #7 from Tsu Jan ---
Yes, this was a Qt issue. It was fixed a long time ago, after this old report.
The Zero-width_non-joiner character is OK.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #20 from Tsu Jan ---
> Is it scheduled for 5.16 series I hope?
That's my question too -- I'm just a kwin user. I only know that the patch
isn't applied to kwin 5.16.2.
--
You are receiving this mail because:
You ar
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #18 from Tsu Jan ---
> It's really annoying because
It's already fixed under X11. You could apply the patch or wait for it to come
to your distro.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #15 from Tsu Jan ---
OK, tested and saw the bug was present under Wayland too -- the patch had no
effect there.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408594
--- Comment #14 from Tsu Jan ---
Here, the patch fixed the issue. Thanks a lot!
I haven't tested KWin 5.16.1 under Wayland though.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408915
Bug ID: 408915
Summary: Blur effect: too much darkness with dark translucent
backgrounds
Product: kwin
Version: 5.16.0
Platform: Manjaro
OS: Linux
Stat
https://bugs.kde.org/show_bug.cgi?id=405781
Tsu Jan changed:
What|Removed |Added
CC||tsujan2...@gmail.com
--- Comment #5 from Tsu Jan
https://bugs.kde.org/show_bug.cgi?id=405801
Tsu Jan changed:
What|Removed |Added
CC||tsujan2...@gmail.com
--- Comment #3 from Tsu Jan
https://bugs.kde.org/show_bug.cgi?id=399680
--- Comment #8 from Tsu Jan ---
And I don't recommend an early creation of native handles at all -- it would
have bad side effects. Sorry, I didn't have time to read the KDE code.
--
You are receiving this mail because:
You are watchi
https://bugs.kde.org/show_bug.cgi?id=399680
--- Comment #7 from Tsu Jan ---
> Would you mind helping us Tsujan? Your Kvantum does this very well...
If this happens with Kvantum too, please report it to Kvantum's github page
(although I've never seen it).
I don't think I can b
https://bugs.kde.org/show_bug.cgi?id=402595
Tsu Jan changed:
What|Removed |Added
CC||tsujan2...@gmail.com
--- Comment #5 from Tsu Jan
https://bugs.kde.org/show_bug.cgi?id=382817
--- Comment #16 from Tsu Jan ---
For the sake of thoroughness, I should add that it wasn't a driver issue but
really a kwin problem, which is fixed in V5.13 somehow (the new blur effect may
have a role in that).
My reason is that no drive
https://bugs.kde.org/show_bug.cgi?id=382817
--- Comment #15 from Tsu Jan ---
> Marking as upstream as it looks quite a lot like a driver issue.
Most probably.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=382817
--- Comment #13 from Tsu Jan ---
Sorry, I meant DRI2 -- copy/paste typo.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=382817
--- Comment #12 from Tsu Jan ---
Switching to DDR2 (with modesetting) and choosing "OpenGl 2.0" as well as "Full
screen repaints" in System Settings had a considerable positive effect. DDR3
seems to have bugs, whether with modesetti
https://bugs.kde.org/show_bug.cgi?id=346687
--- Comment #5 from Tsu Jan ---
> could give some inspirations for a fix in Kate
Don't know about Kate's code but, for example, inside keyPressEvent(QKeyEvent
*event) this can be done for a text-edit:
if (event->key() == 0x200c)
{
https://bugs.kde.org/show_bug.cgi?id=346687
Tsu Jan changed:
What|Removed |Added
CC||tsujan2...@gmail.com
--- Comment #3 from Tsu Jan
https://bugs.kde.org/show_bug.cgi?id=377392
--- Comment #12 from Tsu Jan ---
A very different method. Anyhow, it's great that Dolphin has it :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=377392
--- Comment #10 from Tsu Jan ---
Thank you very much! Sorry that I wasn't able to do it!
IMHO, this is one the 2 "important" problems of Dolphin -- none of which is
very important -- the other one being the random 1-s delay at star
https://bugs.kde.org/show_bug.cgi?id=377392
--- Comment #8 from Tsu Jan ---
> are you willing to let me take over the patch?
Oh, that would be very kind of you! Yes, please! I haven't touched the patch
for a long time; it may need to be updated. As far as I remember, at that time,
some
https://bugs.kde.org/show_bug.cgi?id=377392
--- Comment #6 from Tsu Jan ---
This isn't about advertising: I know for sure that GitHub is very practical,
makes the contribution easy and doesn't waste anyone's time.
In comparison, I started to try phabricator with Enlightenmen
https://bugs.kde.org/show_bug.cgi?id=377392
--- Comment #4 from Tsu Jan ---
If only KDE was developed on GtiHub... Sorry, but the current situation doesn't
encourage any contribution. Believe me, KDE needs a lot of contribution.
--
You are receiving this mail because:
You are watching al
https://bugs.kde.org/show_bug.cgi?id=382817
--- Comment #11 from Tsu Jan ---
> What about switching to breeze window decoration?
I sometimes use breeze but there's no difference in this regard.
I tested with an older Intel-based Asus laptop and saw that the problem was so
mild tha
https://bugs.kde.org/show_bug.cgi?id=382817
--- Comment #9 from Tsu Jan ---
I tried the Intel Xorg driver again -- its bugs are fixed now -- but it had no
effect on this problem.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=382817
--- Comment #8 from Tsu Jan ---
Oh, I forgot to tell you about something that may contain a clue:
KWin effects (animation) may interfere with non-kwin ones too. For example, I
also use KWin under LXQt. LXQt's hiding panel has an animatio
https://bugs.kde.org/show_bug.cgi?id=382817
--- Comment #7 from Tsu Jan ---
> You could try switching to OpenGL 3
I had tried that before but got error messages in
`~/.local/share/sddm/xorg-session.log` (I don't remember them).
However, I tried it again a few minutes ago and saw
https://bugs.kde.org/show_bug.cgi?id=382817
--- Comment #5 from Tsu Jan ---
It's modesetting ("xf86-video-intel" was VERY buggy here and its use is
discouraged correctly, IMO). As for dri3, `LIBGL_DEBUG=verbose glxinfo | grep
libgl` gives:
...
libGL: pci id for fd 4: 8086:19
https://bugs.kde.org/show_bug.cgi?id=382817
--- Comment #3 from Tsu Jan ---
Another descriptive info, if it helps:
With kwin effects enabled, starting Dolphin (and some other apps that may have
a delay on starting -- although I think Dolphin's start delay is a bug)
sometimes creates an
https://bugs.kde.org/show_bug.cgi?id=382817
--- Comment #2 from Tsu Jan ---
KWin Support Information:
The following information should be used when requesting support on e.g.
http://forum.kde.org.
It provides information about the currently running instance, which options are
used,
what OpenGL
https://bugs.kde.org/show_bug.cgi?id=382817
Bug ID: 382817
Summary: Choppy and, generally, problematic KWin effects
Product: kwin
Version: 5.10.4
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: nor
https://bugs.kde.org/show_bug.cgi?id=373319
--- Comment #18 from Tsu Jan ---
@Martin
This time the patch works like a charm :) Thank you!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373319
--- Comment #16 from Tsu Jan ---
> unfortunately I can confirm that this theme still doesn't work.
Actually, any theme, with or without bottom border because even if there's a
bottom border, although the titlebar text and buttons
https://bugs.kde.org/show_bug.cgi?id=373319
--- Comment #14 from Tsu Jan ---
Created attachment 106653
--> https://bugs.kde.org/attachment.cgi?id=106653&action=edit
An Aurorae theme without border
Attached is an Aurorae theme without (bottom) border but with large shadow. If
I make
https://bugs.kde.org/show_bug.cgi?id=373319
--- Comment #12 from Tsu Jan ---
Created attachment 106652
--> https://bugs.kde.org/attachment.cgi?id=106652&action=edit
Problem with patch+Aurorae
I'm afraid the patch doesn't work well with Aurorae (although it works with
Pl
https://bugs.kde.org/show_bug.cgi?id=373319
--- Comment #10 from Tsu Jan ---
Happy to see there's an activity about this; just wanted to emphasize that the
issue isn't specific to Plastik and, theoretically, any fix should solve the
same problem in Aurorae too.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=373319
--- Comment #5 from Tsu Jan ---
This bug has been there for a long time. The problem is that Breeze's look is
so elementary and it doesn't support translucency or fine-tuning, so many KWin
users use Aurorae instead.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #133 from Tsu Jan ---
I'm not a KDE dev and I completely agree with Martin. It doesn't seem fair to
see KDE responsible for the behavior of a closed-source program like nvidia.
KDE devs did what the could (and I'm sure they
https://bugs.kde.org/show_bug.cgi?id=377411
--- Comment #5 from Tsu Jan ---
The problem of url's with double slashed is more fundamental than
https://git.reviewboard.kde.org/r/130001/. For example, Folder View creates
such url's easily. I think something basic in KDE's url handl
https://bugs.kde.org/show_bug.cgi?id=377392
--- Comment #2 from Tsu Jan ---
Added a patch here: https://git.reviewboard.kde.org/r/130002/diff/1/
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=377411
--- Comment #4 from Tsu Jan ---
Added the patch at https://git.reviewboard.kde.org/r/130001/
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=377411
--- Comment #3 from Tsu Jan ---
BTW, this is a just workaround; why that double slash, in the first place?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=377411
--- Comment #2 from Tsu Jan ---
There's no registration button at
https://phabricator.kde.org/differential/diff/create/ (for now?)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=377411
Bug ID: 377411
Summary: Created Items Are Not Selected In Parent Folder
Product: dolphin
Version: 16.12.0
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=377392
--- Comment #1 from Tsu Jan ---
Never mind! I found an easy way to add the feature in question; will attach a
patch after some tests.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=377392
Bug ID: 377392
Summary: Select Folder on Going up (Feature Request)
Product: dolphin
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity:
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #50 from Tsu Jan ---
Recently I started to prepare Kvantum for wayland and found something that
might be relevant to Qtcurve too:
Although setting WA_TranslucentBackground works fine on X11 (with some
precautions), it causes a lot of
https://bugs.kde.org/show_bug.cgi?id=373319
Tsu Jan changed:
What|Removed |Added
CC||tsujan2...@gmail.com
--- Comment #4 from Tsu Jan
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #44 from Tsu Jan ---
OK. I just wanted to share all facts that I found because, as I said earlier, I
owe them to this report.
I can't say what should be done in QtCurve (not my responsibility). So, I have
nothing to add anymore.
--
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #42 from Tsu Jan ---
> You said somewhere earlier on this ticket that menus don't need what
> addAlphaChannel does to be translucent
I said that on x11 and for MOST menus, not all.
> Windows should still be treated the sam
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #40 from Tsu Jan ---
@RJVB
My two cents: this may be good for menus on Mac but
(1) It's too much, IMO;
(2) The windows are made translucent in the old way. I assure you that the are
(random) problems with that. You may not use w
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #38 from Tsu Jan ---
I pushed the necessary changes to Kvantum. All apps seem happy with
translucency :) -- of course, except for those that should have opaque windows
(like many video players).
I'd like to add that THERE ARE som
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #37 from Tsu Jan ---
> Setting it [WA_TranslucentBackground] in addAlphaChannel() resolves the
> corner issue that made the patch useless on Mac.
If so, the solution should work there too. Good news for Mac!
--
You are receivin
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #34 from Tsu Jan ---
> Do you think you could try to get Kvantum to work on Mac?
I don't have Mac and changing a code blindly isn't a good practice at all.
However, any Mac PR that works fine and whose logic is understandable
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #31 from Tsu Jan ---
I forgot to say that I successfully tested this solution on two machines (one
very old and with nvidia, the other new and with Intel) and also on virtualbox,
with Qt-5.7.1 and Qt-5.5.x. All tests are done with Linux+x11
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #30 from Tsu Jan ---
@ Yichao Yu
I didn't work with QtCurve's code but, both practically and theoretically, I'm
sure that setting "WA_TranslucentBackground" before widget creation is the
safest solution. The code
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #28 from Tsu Jan ---
Much to my surprise, after playing with various codes, I found out that this is
really a QtCurve bug!
Let me summarize the problem and its new solution:
To make Qt windows translucent, we should set the surface format
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #27 from Tsu Jan ---
Although satisfied with the "ensurePolished" solution on x11, I reverted to the
freeze code (with Kvantum) under KDE to study the problem a little and found
that actually there was a way to close the me
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #25 from Tsu Jan ---
OK, I just wanted to know if the freeze was caused by a loop, in which case
you'd see a difference. Before using ensurePolished(), I didn't see a high CPU
usage either.
The freeze -- without ensurePolish
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #23 from Tsu Jan ---
I have a relatively new laptop with Intel and an old desktop computer with
nVidia. All menus are OK on both computers.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #22 from Tsu Jan ---
Any extra CPU usage under wayland or Mac?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #19 from Tsu Jan ---
Created attachment 103238
--> https://bugs.kde.org/attachment.cgi?id=103238&action=edit
x11 menus
All menus are OK on Linux (x11) now. Qt's behavior should be different in Mac.
--
You are receivi
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #18 from Tsu Jan ---
Strange! The whole point of ensurePolished() is to call `QStyle::polish()`
before creation of native windows. Here, on x11, it works not only with menus
but also with most top level widgets, although it's safe only
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #15 from Tsu Jan ---
Glad to know it works for QtCurve too! The developer(s) of QtCurve should be
informed about the whole problem and its solution.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #13 from Tsu Jan ---
OK, I may be wrong but I couldn't find any problem in kio. Of course, someone
knowledgeable about kio would know better.
I tested with Kvantum and found that ensurePolished() (only at
Style::styleHint()) is enoug
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #12 from Tsu Jan ---
I haven't found anything in kio yet but I'm pretty sure about this:
The freeze happens when a window handle is going to be created for those menus,
whether by setting WA_NativeWindow to `true` temporarily o
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #11 from Tsu Jan ---
> You'll also have to look in kdiroperator.cpp, that's where the context menu
> (for right-clicking on items in the file list) is defined.
Thanks! I will soon.
> I have rounded corners configured f
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #9 from Tsu Jan ---
@RJVB
Actually, I was lead to your report by google, while trying to know why
KFileDialog is an exception and which source file I should read. Your patch
says "kfilewidget.cpp". That will be a good start :)
-
https://bugs.kde.org/show_bug.cgi?id=374224
Tsu Jan changed:
What|Removed |Added
CC||tsujan2...@gmail.com
--- Comment #7 from Tsu Jan
https://bugs.kde.org/show_bug.cgi?id=371725
--- Comment #4 from Tsu Jan ---
I confirm that the issue is fixed by https://phabricator.kde.org/D3151. Thank
you very much!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=371725
--- Comment #2 from Tsu Jan ---
Still more info:
There is definitely a `QEvent::Leave` in QPlainTextEdit when the cursor reaches
the horizontal middle line -- I tested with a text editor of mine.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=371725
--- Comment #1 from Tsu Jan ---
More info:
As soon as I resize a left/right tiled window (of a text editor) just a little,
the problem disappears, even after I re-tile it. But when I close, open and
tile it again, the problem appears exactly on the
https://bugs.kde.org/show_bug.cgi?id=371725
Bug ID: 371725
Summary: Cursor Changes to Arrow on Text Editors
Product: kwin
Version: 5.8.2
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity:
https://bugs.kde.org/show_bug.cgi?id=351116
--- Comment #14 from Tsu Jan ---
@Martin Gräßlin
I understand your reasoning. It was why I said "Technical problems aside,...";
just wanted to show the problem from another perspective.
--
You are receiving this mail because:
You are wa
https://bugs.kde.org/show_bug.cgi?id=351116
Tsu Jan changed:
What|Removed |Added
CC||tsujan2...@gmail.com
--- Comment #12 from Tsu Jan
https://bugs.kde.org/show_bug.cgi?id=365014
--- Comment #40 from Tsu Jan ---
I confirm that this bug is fixed in Plasma-5.8.1. Thanks!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365014
--- Comment #38 from Tsu Jan ---
> There seem to be additional changes
OK! That's what I wanted to know. Thank you!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365014
--- Comment #36 from Tsu Jan ---
> I can confirm it works with master
So, other commits are also essential to fixing this bug? Which ones? I ask
because this bug, together with bug #360219, has made a painful experience out
of Plasma for months.
&
https://bugs.kde.org/show_bug.cgi?id=360219
Tsu Jan changed:
What|Removed |Added
CC||tsujan2...@gmail.com
--- Comment #31 from Tsu Jan
https://bugs.kde.org/show_bug.cgi?id=365014
Tsu Jan changed:
What|Removed |Added
CC||tsujan2...@gmail.com
--- Comment #34 from Tsu Jan
https://bugs.kde.org/show_bug.cgi?id=354482
--- Comment #9 from Tsu Jan ---
I'm almost sure that this bug is about
https://bugreports.qt.io/browse/QTBUG-49294
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #113 from Tsu Jan ---
Shouldn't the title be changed to "Black or corrupted screen on resume from
suspend with nVidia"? I had this issue with nVidia but never with Intel.
--
You are receiving this mail because:
You are w
https://bugs.kde.org/show_bug.cgi?id=361192
--- Comment #4 from Tsu Jan ---
You could close this report. See https://codereview.qt-project.org/#/c/159800/
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=361192
--- Comment #2 from Tsu Jan ---
Wrong address! Sorry, the bug is in qiconloader.cpp -> directoryMatchesSize().
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=361192
Tsu Jan changed:
What|Removed |Added
CC||tsujan2...@gmail.com
--- Comment #1 from Tsu Jan
https://bugs.kde.org/show_bug.cgi?id=250729
--- Comment #16 from Tsu Jan ---
@Wulf
I think this bug has never been fixed because it occurs once a year, being
related to daylight saving time.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=354482
--- Comment #5 from Tsu Jan ---
I forgot to confirm what Denis said: this is a Qt5 bug and not specific to Kate
or KDE. However, it is specific to Linux.
--
You are receiving this mail because:
You are watching all bug changes.
1 - 100 of 103 matches
Mail list logo
