https://bugs.kde.org/show_bug.cgi?id=442643
--- Comment #4 from Aetf <7437...@gmail.com> ---
Can also confirm on my setup: 2 monitors with 2x scale factor. The left monitor
is primary.
Also, I don't think this is the same issue as Bug 443905. The problem in this
issue is that there's n
https://bugs.kde.org/show_bug.cgi?id=442643
Aetf <7437...@gmail.com> changed:
What|Removed |Added
CC||7437...@gmail.com
-
https://bugs.kde.org/show_bug.cgi?id=444990
Aetf <7437...@gmail.com> changed:
What|Removed |Added
CC||7437...@gmail.com
-
https://bugs.kde.org/show_bug.cgi?id=444990
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Attachment #143223|0 |1
is ob
https://bugs.kde.org/show_bug.cgi?id=444990
Bug ID: 444990
Summary: Shortcut conflicts when filename contains number
Product: okular
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=415683
Aetf <7437...@gmail.com> changed:
What|Removed |Added
CC||7437...@gmail.com
-
https://bugs.kde.org/show_bug.cgi?id=428760
Aetf <7437...@gmail.com> changed:
What|Removed |Added
CC||7437...@gmail.com
-
https://bugs.kde.org/show_bug.cgi?id=442064
Bug ID: 442064
Summary: the `powermanagement` data engine calling the
`UnInhibit` method with incorrect signature
Product: plasmashell
Version: master
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=404057
Aetf <7437...@gmail.com> changed:
What|Removed |Added
CC||7437...@gmail.com
-
https://bugs.kde.org/show_bug.cgi?id=299517
Aetf <7437...@gmail.com> changed:
What|Removed |Added
CC||7437...@gmail.com
-
https://bugs.kde.org/show_bug.cgi?id=427291
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Resolution|--- |FIXED
Status|RE
https://bugs.kde.org/show_bug.cgi?id=427291
Bug ID: 427291
Summary: Latte Dock crashes after the external display
disconnected
Product: lattedock
Version: 0.9.11
Platform: Archlinux Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=427291
--- Comment #1 from Aetf <7437...@gmail.com> ---
Created attachment 132091
--> https://bugs.kde.org/attachment.cgi?id=132091=edit
Crash log
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=323647
Aetf <7437...@gmail.com> changed:
What|Removed |Added
CC||7437...@gmail.com
-
https://bugs.kde.org/show_bug.cgi?id=406800
Aetf <7437...@gmail.com> changed:
What|Removed |Added
CC||7437...@gmail.com
-
https://bugs.kde.org/show_bug.cgi?id=424718
--- Comment #1 from Aetf <7437...@gmail.com> ---
Created attachment 130438
--> https://bugs.kde.org/attachment.cgi?id=130438=edit
If the window doesn't use window decoration, there is no red pixels visible
The same setting as in t
https://bugs.kde.org/show_bug.cgi?id=424718
Bug ID: 424718
Summary: Window decoration on maximized window is not large
enough to cover all underlaying pixels
Product: kwin
Version: 5.19.3
Platform: Archlinux Packages
https://bugs.kde.org/show_bug.cgi?id=417604
Aetf <7437...@gmail.com> changed:
What|Removed |Added
CC||7437...@gmail.com
-
https://bugs.kde.org/show_bug.cgi?id=414762
--- Comment #4 from Aetf <7437...@gmail.com> ---
My versions:
Qt 5.13.2
Plasma 5.17.3
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=414762
--- Comment #3 from Aetf <7437...@gmail.com> ---
Created attachment 124296
--> https://bugs.kde.org/attachment.cgi?id=124296=edit
The context menu location is as if the client area starts from (0, 0)
I can reproduce on Archlinux with t
https://bugs.kde.org/show_bug.cgi?id=414762
Aetf <7437...@gmail.com> changed:
What|Removed |Added
CC||7437...@gmail.com
-
https://bugs.kde.org/show_bug.cgi?id=405016
--- Comment #8 from Aetf <7437...@gmail.com> ---
(In reply to Michail Vourlakos from comment #7)
> Are you using Latte v0.8 or git version?
I'm using 0.8.8. But the bug was also there for the previous 0.8.7. But I'm not
sure which version ex
https://bugs.kde.org/show_bug.cgi?id=405016
Aetf <7437...@gmail.com> changed:
What|Removed |Added
CC||7437...@gmail.com
--- Comm
https://bugs.kde.org/show_bug.cgi?id=372116
Aetf <7437...@gmail.com> changed:
What|Removed |Added
CC||7437...@gmail.com
-
https://bugs.kde.org/show_bug.cgi?id=389448
--- Comment #12 from Aetf <7437...@gmail.com> ---
I've found a workaround. Adding/removing virtual desktops seems to force Qt to
recalculate the desktop size and makes Yakuake's sizing correct.
--
You are receiving this mail because:
You are wa
https://bugs.kde.org/show_bug.cgi?id=399731
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|INTEN
https://bugs.kde.org/show_bug.cgi?id=399731
Bug ID: 399731
Summary: Symlink layout file not supported
Product: latte-dock
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=391897
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CON
https://bugs.kde.org/show_bug.cgi?id=391897
--- Comment #3 from Aetf <7437...@gmail.com> ---
Hmm, you are right that the default build does include debug symbols. Not sure
why I didn't get it the first time.
Did you enable break on start in launch configurations? You can check the Frame
https://bugs.kde.org/show_bug.cgi?id=391897
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCON
https://bugs.kde.org/show_bug.cgi?id=389448
--- Comment #3 from Aetf <7437...@gmail.com> ---
Some investigation:
Given my resolution 3840x2160, It appears that Qt returns screen geometry as
1920x1080, which has been scaled down by QT_SCREEN_SCALE_FACTORS=2. Then in
KWindowSystem::workArea,
https://bugs.kde.org/show_bug.cgi?id=389448
--- Comment #2 from Aetf <7437...@gmail.com> ---
Another report of the same bug: https://bugs.kde.org/show_bug.cgi?id=388217
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389448
Aetf <7437...@gmail.com> changed:
What|Removed |Added
CC||7437...@gmail.com
--- Comm
https://bugs.kde.org/show_bug.cgi?id=384630
--- Comment #2 from Aetf <7437...@gmail.com> ---
I'm using the receipt from spack
(https://github.com/LLNL/spack/blob/develop/var/spack/repos/builtin/packages/valgrind/package.py).
And yes it was built with --enable-ubsan
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=384630
Aetf <7437...@gmail.com> changed:
What|Removed |Added
CC||7437...@gmail.com
-
https://bugs.kde.org/show_bug.cgi?id=384630
Bug ID: 384630
Summary: The 'impossible' happened
(__ubsan_handle_shift_out_of_bounds) as soon as
starting anything under valgrind
Product: valgrind
Version: 3.13.0
https://bugs.kde.org/show_bug.cgi?id=384368
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCON
https://bugs.kde.org/show_bug.cgi?id=384368
Bug ID: 384368
Summary: Support for gdb watchpoint option -location
Product: kdevelop
Version: unspecified
Platform: unspecified
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=340283
Aetf <7437...@gmail.com> changed:
What|Removed |Added
CC||7437...@gmail.com
-
https://bugs.kde.org/show_bug.cgi?id=372635
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Latest
https://bugs.kde.org/show_bug.cgi?id=372635
Aetf <7437...@gmail.com> changed:
What|Removed |Added
CC||7437...@gmail.com
-
https://bugs.kde.org/show_bug.cgi?id=376595
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Status|VERIFIED|CLOSED
--- Comment #27 fro
https://bugs.kde.org/show_bug.cgi?id=376595
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Resolution|WAITINGFORINFO |UPSTREAM
--- Comment #25 fro
https://bugs.kde.org/show_bug.cgi?id=376595
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Attachment #104135|0 |1
is ob
https://bugs.kde.org/show_bug.cgi?id=376595
--- Comment #22 from Aetf <7437...@gmail.com> ---
Okay I can reproduce your issue now. I guess the difference is that yours is
multi-threaded (several threads for qt internal stuff). And when gdb stopped,
it stopped at another thread differen
https://bugs.kde.org/show_bug.cgi?id=376595
--- Comment #18 from Aetf <7437...@gmail.com> ---
Created attachment 104154
--> https://bugs.kde.org/attachment.cgi?id=104154=edit
GDB outputs when watchpoint goes out of scope
Yes, kdevelop uses plain variable name when adding wat
https://bugs.kde.org/show_bug.cgi?id=376595
--- Comment #16 from Aetf <7437...@gmail.com> ---
Created attachment 104135
--> https://bugs.kde.org/attachment.cgi?id=104135=edit
Proposed patch
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376595
--- Comment #15 from Aetf <7437...@gmail.com> ---
Okay. So setting watch point itself seems normal in log. The crash actually
happens before the watch point was triggered.
gdb returned two replies for 35-exec-continue command:
35^running and 35
https://bugs.kde.org/show_bug.cgi?id=376595
--- Comment #12 from Aetf <7437...@gmail.com> ---
I see. Seems your Qt version doesn't support semicolon separated logging rules.
Instead, create a file named logging.conf with the following content:
[Rules]
kdevelop.debuggers.gdb.debu
https://bugs.kde.org/show_bug.cgi?id=376595
--- Comment #10 from Aetf <7437...@gmail.com> ---
Hmm actually I can't reproduce this. I tried with a structure member variable
and it works as intended.
>From the log output, kdevelop was complaining about gdb not returning required
da
https://bugs.kde.org/show_bug.cgi?id=360037
Aetf <7437...@gmail.com> changed:
What|Removed |Added
CC||7437...@gmail.com
-
https://bugs.kde.org/show_bug.cgi?id=376595
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Status|RESOLVED|VERIFIED
--- Comment #8 fro
https://bugs.kde.org/show_bug.cgi?id=374458
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CON
https://bugs.kde.org/show_bug.cgi?id=374458
--- Comment #9 from Aetf <7437...@gmail.com> ---
Francis could you try https://phabricator.kde.org/D4555 and see if it works for
you?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374458
--- Comment #8 from Aetf <7437...@gmail.com> ---
Oh I see. Didn't know much about git describe before. ;P
Now I can finally reproduce the crash. Launcher items are in fact not
draggable. But the crash happens when you click & hold the cursor,
https://bugs.kde.org/show_bug.cgi?id=374458
--- Comment #5 from Aetf <7437...@gmail.com> ---
Hmm, that's weird. I'm on Arch x86_64 too, with qt 5.8.0. And it works normally
with today's 5.1 branch HEAD:
kdevplatform: 3e2549d39
kdevelop: 2c1a1fd7f6
And in fact I can't find commit gd27
https://bugs.kde.org/show_bug.cgi?id=374458
--- Comment #3 from Aetf <7437...@gmail.com> ---
I just tested on the latest 5.1 branch. They are not draggable any more. IMO
that makes sense because launches are associated with one project and there's
no point to drag them around.
Francis, c
https://bugs.kde.org/show_bug.cgi?id=374894
--- Comment #6 from Aetf <7437...@gmail.com> ---
(In reply to Aetf from comment #5)
> + ed9e1726c, the first bad commit found by git bisect. I can reproduce the
> crash somethings
s/somethings/sometimes
I added some debug log to t
https://bugs.kde.org/show_bug.cgi?id=374894
--- Comment #5 from Aetf <7437...@gmail.com> ---
It's getting weirder. Mainly I tried on three commits (and a few others between
ed9e1726c and 7fa22b617, the results were similar).
+ 2b44ef9f6, the commit right before ed9e1726c. Crash
https://bugs.kde.org/show_bug.cgi?id=374894
--- Comment #3 from Aetf <7437...@gmail.com> ---
I did a bisect, seems ed9e1726c8c6c25b601da0893ecff8f9f9f47364 is the first bad
commit. Maybe related to the cache of ProjectItemDataProvider::itemCount?
Also, sometimes the crash was only triggere
https://bugs.kde.org/show_bug.cgi?id=374894
--- Comment #2 from Aetf <7437...@gmail.com> ---
I tried to revert 4f3e1fbbc, but it doesn't apply cleanly. There are still
compilation errors after solving a few conflicts. So I built the commit before
that (f00f30037), and tested. There's no
https://bugs.kde.org/show_bug.cgi?id=374894
Bug ID: 374894
Summary: KDevelop crashes when clicking on QuickOpen
Product: kdevelop
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=368603
--- Comment #22 from Aetf <7437...@gmail.com> ---
For a simplest session:
$ lldb-mi /path/to/executable
-break-insert main.cpp:30
-exec-run
There are also commands like -exec-continue, -exec-next. Reference:
https://sourceware.org/gdb/onlinedo
https://bugs.kde.org/show_bug.cgi?id=368603
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Resolution|--- |FIXED
Status|AS
https://bugs.kde.org/show_bug.cgi?id=368603
--- Comment #18 from Aetf <7437...@gmail.com> ---
I'm glad you found the reason. So the patch itself works for you now? If so,
I'm going to close this and push the change to master.
--
You are receiving this mail because:
You are watching a
https://bugs.kde.org/show_bug.cgi?id=368603
--- Comment #16 from Aetf <7437...@gmail.com> ---
Could you start KDevelop from the console and check the output when starting
the debug session on Linux? You can enable debug output from KDevelop by
launching it with the command
env QT_LOGGIN
https://bugs.kde.org/show_bug.cgi?id=368603
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Attachment #101058|0 |1
is ob
https://bugs.kde.org/show_bug.cgi?id=368603
--- Comment #13 from Aetf <7437...@gmail.com> ---
Sorry for the delay. I don't have enough time to do any actual coding due to my
course work for a few days.
That looks good to me. The reason I didn't add the check for OS X was I can't
find the m
https://bugs.kde.org/show_bug.cgi?id=368603
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Attachment #101057|0 |1
is ob
https://bugs.kde.org/show_bug.cgi?id=368603
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Assignee|unassigned-b...@kde.org |7437...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=368603
--- Comment #9 from Aetf <7437...@gmail.com> ---
Oops, it should be Bug 368603 in the description of the attachment.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368603
--- Comment #5 from Aetf <7437...@gmail.com> ---
Okay, that patch is required, otherwise lldb-mi doesn't produce correct spec
confirming output. That's why handleVersion is getting empty lists.
And the version output is quite different, is tha
https://bugs.kde.org/show_bug.cgi?id=368603
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDSINFO
Reso
https://bugs.kde.org/show_bug.cgi?id=357779
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Status|CONFIRMED |NEEDSINFO
Reso
https://bugs.kde.org/show_bug.cgi?id=368322
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Resolution|--- |FIXED
Status|AS
https://bugs.kde.org/show_bug.cgi?id=368322
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Assignee|kdevelop-bugs-n...@kde.org |7437...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=368162
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Resolution|--- |UPSTREAM
https://bugs.kde.org/show_bug.cgi?id=333759
Aetf <7437...@gmail.com> changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Reso
https://bugs.kde.org/show_bug.cgi?id=333759
--- Comment #8 from Aetf <7437...@gmail.com> ---
(In reply to Kevin Funk from comment #7)
I am still not quite convinced (see below) but maybe the removal deserves it
own patch. So, simpler fix submitted to Phabricator.
For the "cache/dupli
https://bugs.kde.org/show_bug.cgi?id=333759
--- Comment #5 from Aetf <7437...@gmail.com> ---
Posted on Phabricator now: https://phabricator.kde.org/D1351
Well, yes, it can be done by just make IVariableController::handleEvent
correctly updates m_active{Frame,Thread} even if
IVariableCont
https://bugs.kde.org/show_bug.cgi?id=333759
--- Comment #2 from Aetf <7437...@gmail.com> ---
Hi, I'm looking into this bug right now. It seems the bug still exists in the
latest version.
The exact steps to reproduce is as follow:
1. Debug some application
2. Pause the debugger
3. Co
https://bugs.kde.org/show_bug.cgi?id=333759
Aetf <7437...@gmail.com> changed:
What|Removed |Added
CC||7437...@gmail.com
--- Comm
82 matches
Mail list logo
