https://bugs.kde.org/show_bug.cgi?id=314638
--- Comment #5 from Yichao Yu ---
I'm just testing this and it seems that the artistic text tool has been
removed? If that is the case than this can be closed.
The current text tool has a popup window to edit the text and it interacts with
https://bugs.kde.org/show_bug.cgi?id=318450
--- Comment #3 from Yichao Yu ---
Yes, this is still an issue.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=430235
Bug ID: 430235
Summary: UI regression: Very difficult to configure per-event
notification
Product: systemsettings
Version: 5.20.4
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=427569
Yichao Yu changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=427569
--- Comment #4 from Yichao Yu ---
I've reduced the test case in the Qt bug report so I'm fairly sure it's a Qt
bug now.
https://bugreports.qt.io/browse/QTBUG-87345?focusedCommentId=530782&page=com.atlassian.jira.plugin.system.issue
https://bugs.kde.org/show_bug.cgi?id=427569
--- Comment #2 from Yichao Yu ---
Ref https://bugreports.qt.io/browse/QTBUG-87345
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=427569
--- Comment #1 from Yichao Yu ---
I'm still not sure what's changed but the issue seems to be caused by showing a
widget before a parent is set.
In `app/viewmainpage.cpp`, `mThumbnailBar` was created without a parent and may
be set
https://bugs.kde.org/show_bug.cgi?id=427569
Bug ID: 427569
Summary: Thumbnail view pops out as new window on Qt 5.15
Product: gwenview
Version: 20.08.2
Platform: Other
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=422554
--- Comment #4 from Yichao Yu ---
Have to say I don't really like the windows behavior you described though
having an aggressive warning would at least fix my initial confusion.
I think my bottom line is that there should be a way to se
https://bugs.kde.org/show_bug.cgi?id=422554
Bug ID: 422554
Summary: permission order in usershare_acl
Product: frameworks-kio
Version: 5.70.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=417310
--- Comment #2 from Yichao Yu ---
Note that there is a fix from a year ago waiting for review @
https://phabricator.kde.org/D20790.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411326
--- Comment #10 from Yichao Yu ---
Uninstalling or disabling is the workaround now. However it shouldn’t be the
permanent solution. There are so many different made application packages
(which is great on itself) and remembering what to install is next
https://bugs.kde.org/show_bug.cgi?id=411326
Yichao Yu changed:
What|Removed |Added
CC||yyc1...@gmail.com
--- Comment #7 from Yichao Yu
https://bugs.kde.org/show_bug.cgi?id=353216
--- Comment #40 from Yichao Yu ---
> Some times when I type out my comments they appear much too harsh than I
> intend them to be. This is something that I'm working on ;-). For this I
> apologize and would like to clear the slate on
https://bugs.kde.org/show_bug.cgi?id=353216
--- Comment #36 from Yichao Yu ---
> I give up. There are a number of people that would have helped you when I
> first mentioned this to you four years ago. It's a shame. I won't comment on
> this anymore.
Since you are mak
https://bugs.kde.org/show_bug.cgi?id=353216
--- Comment #34 from Yichao Yu ---
Err, assuming you are still talking about the kwin support (you changed how you
talked about it so I assumed you were talking about something else), I've
already mentioned above that I've given it my fair
https://bugs.kde.org/show_bug.cgi?id=353216
--- Comment #32 from Yichao Yu ---
I don't know what you meant by qtcurve-qt.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=322037
Yichao Yu changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=389109
--- Comment #3 from Yichao Yu ---
Oh, search function on bugzilla is so hard to use = = ...
Anyway, if anyone more familiar with QML wants to have a look see the debugging
I did at https://bugs.kde.org/show_bug.cgi?id=419866.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=419866
Bug ID: 419866
Summary: Desktop configure dialog does not close after clicking
"OK" when changing containment plugin type.
Product: plasmashell
Version: 5.18.4
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=362908
Yichao Yu changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=353216
--- Comment #30 from Yichao Yu ---
> Why didn't you finish the window decoration? You had over six years to finish
> it.
I'm not sure what you are trying to suggest by "six years".
If it was easy it would have happened a lon
https://bugs.kde.org/show_bug.cgi?id=353216
--- Comment #28 from Yichao Yu ---
As I said, pull requests are more than welcome.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=419436
Bug ID: 419436
Summary: Picture of the day (potd) background does not work in
greeter
Product: kscreenlocker
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=402412
Yichao Yu changed:
What|Removed |Added
CC||yyc1...@gmail.com
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=417077
Yichao Yu changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=417310
Bug ID: 417310
Summary: Incorrect resolution with HiDPI scaling on
Product: krdc
Version: 19.12
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=417077
--- Comment #1 from Yichao Yu ---
You need to be much more specific about what you are talking about. A few
points to consider.
1. QtCurve is a theme/style. While it is not completely unrelated to clicking,
it is not itself something that you click
https://bugs.kde.org/show_bug.cgi?id=408286
Yichao Yu changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/qtc
https://bugs.kde.org/show_bug.cgi?id=398021
--- Comment #3 from Yichao Yu ---
And if it's a generic issue rather than something that each users has to fix,
the component is likely framework-kconfig. Of course even in that case it could
still be caused by your local configuration (like i
https://bugs.kde.org/show_bug.cgi?id=398021
--- Comment #2 from Yichao Yu ---
QtCurve uses KConfig for saving the setting. I'll keep this open since that's
what was requested in the other issue but in the mean time I'm not sure what we
could do differently to fi
https://bugs.kde.org/show_bug.cgi?id=333601
--- Comment #4 from Yichao Yu ---
This was actually one of the first things I checked when switching to plasma 5
and it was working without this problem as far as I remember.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=327898
--- Comment #3 from Yichao Yu ---
Actually I can't reproduce this for the location but I can for the filename
box.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=327898
--- Comment #2 from Yichao Yu ---
I'm actually pretty confused by the version number scheme right now so I'm not
really sure which version I have. The kdialog package version is 17.12.1
installed from Feburary and kdialog --version gives me
https://bugs.kde.org/show_bug.cgi?id=387795
Yichao Yu changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/qtc
https://bugs.kde.org/show_bug.cgi?id=387795
Yichao Yu changed:
What|Removed |Added
Component|qt4 |qt5
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=387795
--- Comment #1 from Yichao Yu ---
It is not used in qt4 version.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=363753
Yichao Yu changed:
What|Removed |Added
CC||egorov_e...@bk.ru
--- Comment #72 from Yichao Yu
https://bugs.kde.org/show_bug.cgi?id=382182
Yichao Yu changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=380804
Yichao Yu changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=380804
--- Comment #1 from Yichao Yu ---
= = ... Too many numbers to change..
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=380519
Yichao Yu changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=363753
--- Comment #55 from Yichao Yu ---
Works for me so far. Haven't got a chance to figure out what's causing the
(absence of) mmap yet...
I assume you'll submit a pull request with this?
--
You are receiving this mail because:
You are w
https://bugs.kde.org/show_bug.cgi?id=363753
--- Comment #52 from Yichao Yu ---
Yes the latest version looks fine though I'd like to test it for some time.
> but if I understand the DBus protocol well enough they'd have to send exactly
> the "right" signals (one of t
https://bugs.kde.org/show_bug.cgi?id=363753
--- Comment #48 from Yichao Yu ---
> I cannot reproduce that - with my patch in place. If your reasoning is
> correct that patch should make me vulnerable to the crash.
Yes it'll make you vulnerable but it won't actually crash unl
https://bugs.kde.org/show_bug.cgi?id=363753
--- Comment #45 from Yichao Yu ---
> Maybe that has to do with the kind of signals we're connecting to but I don't
> understand how this could happen. I don't see how QtCurve could be unloaded
> without calling the Style dt
https://bugs.kde.org/show_bug.cgi?id=363753
--- Comment #43 from Yichao Yu ---
> fWhat callback are we talking about here?
The slots connected to the DBus signals.
> The function in which the crash occurs is called from the plugin dtor, not
> directly from the application.
Correct
https://bugs.kde.org/show_bug.cgi?id=363753
--- Comment #41 from Yichao Yu ---
> I maintain that the plugin shouldn't trigger callbacks if it cannot be sure
> that those callbacks are safe.
Sure, the plugin is not the one triggerring the callback, the applications is,
which makes t
https://bugs.kde.org/show_bug.cgi?id=363753
--- Comment #39 from Yichao Yu ---
(Sorry, not sure why I commented twice, definitely didn't refresh page and
not sure how to remove it.)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=363753
--- Comment #38 from Yichao Yu ---
> What is it that doesn't work in that approach?
What I've seen happens is
1. Plugin was unloaded
2. Callback triggers
3. Jumps to the plugin code section which is unmmapped.
4. Segfault
> Possi
https://bugs.kde.org/show_bug.cgi?id=363753
--- Comment #37 from Yichao Yu ---
> What is it that doesn't work in that approach?
What I've seen happens is
1. Plugin was unloaded
2. Callback triggers
3. Jumps to the plugin code section which is unmmapped.
4. Segfault
> Possi
https://bugs.kde.org/show_bug.cgi?id=363753
--- Comment #34 from Yichao Yu ---
FWIW, doing things just in the destructor doesn't work and that's exactly why I
need to do this complicated mess. Apparently some application doesn't desctruct
the Style before unloading the plugin
https://bugs.kde.org/show_bug.cgi?id=379175
Yichao Yu changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=363753
Yichao Yu changed:
What|Removed |Added
CC||luke-jr+kdeb...@utopios.org
--- Comment #27 from
https://bugs.kde.org/show_bug.cgi?id=377353
Yichao Yu changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=363753
--- Comment #26 from Yichao Yu ---
*** Bug 377353 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=378723
Yichao Yu changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=363753
Yichao Yu changed:
What|Removed |Added
CC||jodr...@live.com
--- Comment #25 from Yichao Yu
https://bugs.kde.org/show_bug.cgi?id=376155
--- Comment #8 from Yichao Yu ---
No, there's a slightly different behavior that I cannot fix even with my patch
so I didn't submitted it (the behavior might be new in 5.2). This time, instead
of simply untile (and doesn't move), it
https://bugs.kde.org/show_bug.cgi?id=376457
--- Comment #10 from Yichao Yu ---
I assume by that you mean https://phabricator.kde.org/D3602 ?
I didn't want to comment on a merged pull request so I opened a bug report.
I'll comment there instead.
--
You are receiving this mail becaus
https://bugs.kde.org/show_bug.cgi?id=376457
--- Comment #8 from Yichao Yu ---
Right, there are a lot of shortcuts that shouldn't be used with autorepeat, but
the change turns these ones from autorepeatable to not autorepeatable and
therefore one of the most important statements in the usab
https://bugs.kde.org/show_bug.cgi?id=376457
--- Comment #6 from Yichao Yu ---
Yet another acceptable solution would be to expose the new `switchWindow`
function in the KWin scripting interface (I thought it's possible to trigger
script with hotkey/add hotkey from a script?). I'
https://bugs.kde.org/show_bug.cgi?id=376457
Yichao Yu changed:
What|Removed |Added
Summary|Provide an option to|Revert wrapping in window
https://bugs.kde.org/show_bug.cgi?id=376457
--- Comment #5 from Yichao Yu ---
Also, although I'm not that familiar with how the auto testing is done on X11,
it seems that this should be a relatively easy thing to test for both options
and should not be strongly coupled to other optio
https://bugs.kde.org/show_bug.cgi?id=376457
Yichao Yu changed:
What|Removed |Added
Ever confirmed|0 |1
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=376457
--- Comment #2 from Yichao Yu ---
What's the usability feedback? I've seen
https://phabricator.kde.org/D3602#70700 but it doesn't seem to make sense for
me.
> Those who would not expect the wrap-around behavior would not expect any
https://bugs.kde.org/show_bug.cgi?id=362856
Yichao Yu changed:
What|Removed |Added
CC||yyc1...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=376155
--- Comment #4 from Yichao Yu ---
Does KWin support automatic testing on X now?
Also does that change look correct? The symptom AFAICT is definitely that
`m_quickTileMode` is changed from `0` to `1` (or the other way around, don't
remember)
https://bugs.kde.org/show_bug.cgi?id=376457
Bug ID: 376457
Summary: Provide an option to disable wrapping in window
swithing
Product: kwin
Version: 5.9.1
Platform: Other
OS: Linux
Status: UNCONFI
https://bugs.kde.org/show_bug.cgi?id=376155
--- Comment #2 from Yichao Yu ---
I suspect that this is caused by
```
commit 9934f5b57537feae54afd0c4366c90253638ada2
Author: Martin Gräßlin
Date: Fri Sep 16 14:27:50 2016 +0200
Properly implement maximize of ShellClient
Summary
https://bugs.kde.org/show_bug.cgi?id=376155
Yichao Yu changed:
What|Removed |Added
CC||yyc1...@gmail.com
--- Comment #1 from Yichao Yu
https://bugs.kde.org/show_bug.cgi?id=376340
--- Comment #6 from Yichao Yu ---
Is the master version ok? I cannot reproduce this somehow
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376164
--- Comment #1 from Yichao Yu ---
The stabilized API apparently has all the APIs used by most theme engines
removed so it's much harder to implement anything for GTK3 now. There was a
debate on the thread where they decide to deprecate the A
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #49 from Yichao Yu ---
By homogeneous I mean the setting is a single color.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #47 from Yichao Yu ---
> Is what you're asking in any way different from launching the QtCurve theme
> editor via `kcmshell5 style`, setting menu opacity to 50%, confirming they
> indeed become translucent (I had to detach t
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #45 from Yichao Yu ---
> Yichao, what do you think, can I commit this patch?
Using WA_TranslucentBackground for QMenu sounds safe. Be sure to check if
flipping the menu opacity setting to 100% after application started doesn't
reg
https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #29 from Yichao Yu ---
The usage is basically unsupported by Qt and is a hack from the very beginning
so unless Qt provide a proper way to do it this is always a bug of the style.
The only question is that what's a better way to ha
https://bugs.kde.org/show_bug.cgi?id=374568
--- Comment #23 from Yichao Yu ---
> I have nothing against your initial explicit cast to a QObject*, what about
> you Yichao?
Sounds good to me too.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374568
--- Comment #10 from Yichao Yu ---
I agree the code is likely UB. Still curious why it only crashes on your setup
and what code the compiler actually generate. When the method is protected,
would the following work?
```
struct HackedMenu: public
https://bugs.kde.org/show_bug.cgi?id=374568
--- Comment #4 from Yichao Yu ---
That patch looks correct.
IIRC that hack was probably needed since the method was protected. (maybe on
qt4? My internet connection is too terrible before Jan. 10 for me to do a
detail check)
Just curious, why would
https://bugs.kde.org/show_bug.cgi?id=363753
--- Comment #19 from Yichao Yu ---
> I use Qt 5.6.1 with the patch under review at
> https://codereview.qt-project.org/161056
Forgot to say that it's great to know the patch is working for you. What's
blocking the patch right now?
https://bugs.kde.org/show_bug.cgi?id=363753
--- Comment #17 from Yichao Yu ---
Not sure how to find the public link to the patch but it basically revert the
commit you link above. Th Qt bug is in 5.6+ IIRC, this is the Qt version that
starts to unload (unmap) the plugin file which cause segfault
https://bugs.kde.org/show_bug.cgi?id=363753
--- Comment #15 from Yichao Yu ---
It's wrong mainly in the sense that causes segfault in situation that doesn't
segfault, i.e. it causes segfault on my setup due to (I'm guessing) interaction
with other plugins. It is possibly the best
https://bugs.kde.org/show_bug.cgi?id=363753
Yichao Yu changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=362907
Yichao Yu changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=363753
Yichao Yu changed:
What|Removed |Added
CC||tehnic...@yandex.ru
--- Comment #9 from Yichao Yu
https://bugs.kde.org/show_bug.cgi?id=363753
Yichao Yu changed:
What|Removed |Added
CC||edisonalvari...@bol.com.br
--- Comment #8 from
https://bugs.kde.org/show_bug.cgi?id=366815
Yichao Yu changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=353216
--- Comment #10 from Yichao Yu ---
> Status please
The status is that I was told the API change should be sane and therefore
expecting relatively straightforward upgrade path and thought I could finish it
relatively quickly. However, I've ma
https://bugs.kde.org/show_bug.cgi?id=363753
--- Comment #5 from Yichao Yu ---
I don't thinkt he crash is OSX specific (fwiw I think this is a dup of
https://bugs.kde.org/show_bug.cgi?id=362907). I'm guessing this can be due to
other plugins here that uses dbus too which is why I smel
https://bugs.kde.org/show_bug.cgi?id=363753
--- Comment #3 from Yichao Yu ---
> not really sure what's the right solutions
As in not sure what action to take here. From the description in the qt review
you linked, it seems that this can be fixed properly on Qt side.
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=363753
--- Comment #2 from Yichao Yu ---
I guess that makes sense. OTOH, the commit that introduces this is due to the
observation that the dbus callbacks are being called **after** qtcurve is
`dlclose`d which segfault on the function call (after all the code
https://bugs.kde.org/show_bug.cgi?id=362907
--- Comment #1 from Yichao Yu ---
The commit fixes segfault on a Qt upgrade. I do have to workaround a number of
bugs so maybe it's fine to disable it on 5.5
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356978
Bug ID: 356978
Summary: Clicking any article cause all articles to be set to
read when only unread articles are shown.
Product: akregator
Version: GIT (master)
Platform: Other
94 matches
Mail list logo
