[plasma-systemmonitor] [Bug 445917] CPU-Tctl and Tccd missing from filtered sensors

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=445917

Roman Lebedev  changed:

   What|Removed |Added

 CC||lebedev...@gmail.com

--- Comment #5 from Roman Lebedev  ---
Due to this "filtering", it is now simply impossible to monitor CPU temperature
on the AMD FX series or processors. Can that filtering please be ripped out?

-- 
You are receiving this mail because:
You are watching all bug changes.

[Elisa] [Bug 461299] elisa: irrtating stutters when playing audio

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=461299

--- Comment #9 from Roman Lebedev  ---
(In reply to Roman Lebedev from comment #8)
> (In reply to Roman Lebedev from comment #7)
> > (In reply to Nate Graham from comment #6)
> > > Sounds like a libvlc issue, perhaps.
> > 
> > You know what, why don't we just switch to libvlc backend?
> 
> Err. Of course, i meant libmpv.

https://invent.kde.org/multimedia/elisa/-/merge_requests/400
Testing welcomed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Elisa] [Bug 461299] elisa: irrtating stutters when playing audio

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=461299

--- Comment #8 from Roman Lebedev  ---
(In reply to Roman Lebedev from comment #7)
> (In reply to Nate Graham from comment #6)
> > Sounds like a libvlc issue, perhaps.
> 
> You know what, why don't we just switch to libvlc backend?

Err. Of course, i meant libmpv.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Elisa] [Bug 461299] elisa: irrtating stutters when playing audio

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=461299

--- Comment #7 from Roman Lebedev  ---
(In reply to Nate Graham from comment #6)
> Sounds like a libvlc issue, perhaps.

You know what, why don't we just switch to libvlc backend?

-- 
You are receiving this mail because:
You are watching all bug changes.

[Elisa] [Bug 461299] elisa: irrtating stutters when playing audio

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=461299

--- Comment #4 from Roman Lebedev  ---
(In reply to Aurélien COUDERC from comment #3)
> I’ve added the patch to the Debian package on top of 22.08.3 but it doesn’t
> solve the issue. It makes it less frequent but I still have occasional sound
> cuts on an otherwise idle modern machine.
> 
> I’ve not looked at the code but if the stutter is due to the playback
> directly waiting for the data to load from the disk, the correct solution is
> not to make the buffer bigger, it’s only going to make it less frequent.
> Also loading complete files in memory is not the solution either. I have a
> couple of albums that are a single FLAC file of a couple hundres of MBs and
> it seems overkill to load these entirely into memory.
> 
> If the issue is really the playback buffer becoming empty, the real fix
> would be to ensure the prefetch is done in the background so the playback
> never ends up waiting for the data to be there.
> 
> 
> Thanks for looking into this !

I have not analysed *all* the remaining issues i heard, but at least some of
them were artifacts in the audio itself.
Are you sure that is not the case for you?

-- 
You are receiving this mail because:
You are watching all bug changes.

[Elisa] [Bug 461299] elisa: irrtating stutters when playing audio

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=461299

--- Comment #1 from Roman Lebedev  ---
Posted minimal fix at
https://invent.kde.org/multimedia/elisa/-/merge_requests/397
I don't know if this fully solves the problem for me, but if it does not,
the next step would be forcing the kernel to prefetch the whole file...

-- 
You are receiving this mail because:
You are watching all bug changes.

[Elisa] [Bug 461300] elisa: It would be nice to have integrated EBU R 128 loudness normalization ability

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=461300

--- Comment #2 from Roman Lebedev  ---
(In reply to Nate Graham from comment #1)
> What's the difference between this and ReplayGain?

I'm not sure what the question is.

To reword my initial comment, i'm not interested in any solution,
be it ReplayGain or R128, that requires me to modify the files themselves.

Those two are essentially the same underlying algorithm i suppose,
with R128 being more recent/modern, an official standard,
and perhaps more accurate. I do believe R128 is taking over.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Elisa] [Bug 461300] elisa: It would be nice to have integrated EBU R 128 loudness normalization ability

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=461300

Roman Lebedev  changed:

   What|Removed |Added

 CC||lebedev...@gmail.com,
   ||n...@kde.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[Elisa] [Bug 461299] elisa: irrtating stutters when playing audio

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=461299

Roman Lebedev  changed:

   What|Removed |Added

 CC||lebedev...@gmail.com,
   ||n...@kde.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[Elisa] [Bug 461300] New: elisa: It would be nice to have integrated EBU R 128 loudness normalization ability

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=461300

Bug ID: 461300
   Summary: elisa: It would be nice to have integrated EBU R 128
loudness normalization ability
Classification: Applications
   Product: Elisa
   Version: 22.08.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: lebedev...@gmail.com
  Target Milestone: ---

While one could of course do that offline, it would of course modify the source
files,
which is not always desired, because it obviously changes the hash of the
file...

Is this conceptually reasonable to have?

-- 
You are receiving this mail because:
You are watching all bug changes.

[Elisa] [Bug 461299] New: elisa: irrtating stutters when playing audio

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=461299

Bug ID: 461299
   Summary: elisa: irrtating stutters when playing audio
Classification: Applications
   Product: Elisa
   Version: 22.08.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: lebedev...@gmail.com
  Target Milestone: ---

Sometimes, when playing local audio files, regardless of system's load level,
the audio playback momentairly stops and then resumes, it takes maybe less than
1s.

This is happening on fully performance tuned Pipewire setup,
and pwtop does not show any issues on pipewire side.

I highly suspect elisa is simply running out of the input to play,
and stutters when fetching next chunk from disk.

Does elisa already have some kind of precaching system?
Would it be acceptable to simply fully prefetch the whole file
before playing, or is the filesize a concern? Something smarter,
like ensuring that N next seconds are always avaliable could be nice, too.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kquickcharts] [Bug 457248] System monitor pie chart scaling error with non-zero manual data range

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=457248

--- Comment #9 from Roman Lebedev  ---
https://invent.kde.org/frameworks/kquickcharts/-/merge_requests/46
I haven't touched multi-item source handling, i don't really understand how
it's supposed to behave,
and i think it might not be handled correctly.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kquickcharts] [Bug 457248] System monitor pie charts is broken

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=457248

Roman Lebedev  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #7 from Roman Lebedev  ---
(In reply to Arjen Hiemstra from comment #2)
> (In reply to Roman Lebedev from comment #0)
> > 1. The coordinate system is wrong. Somehow "Start from angle = -180*"
> > results in starting from six-o-clock, which is -90* in reality:
> > https://upload.wikimedia.org/wikipedia/commons/9/9a/Degree-Radian_Conversion.
> > svg
> 
> Starting angle is arbitrary and there's no standard. In the case of the
> Quick Charts library, it follows what other chart libraries do: 0 is at the
> top, so -180 degrees is at the bottom.
> 
> > 2. There is some weird normalization bug. Even when the underlying data
> > reaches the specified data range max, the pie chart is still far from being
> > full.
> 
> Please show a code sample where this happens. If you're using automatic
> maximum, the data source may be providing a different maximum than what you
> expect.

I'm using pie chart in system monitor sensor, measuring cpu temperature.
Uploaded screenshots, let me know if that is not sufficient..

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kquickcharts] [Bug 457248] System monitor pie charts is broken

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=457248

--- Comment #6 from Roman Lebedev  ---
Created attachment 150974
  --> https://bugs.kde.org/attachment.cgi?id=150974=edit
chart under load

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kquickcharts] [Bug 457248] System monitor pie charts is broken

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=457248

--- Comment #5 from Roman Lebedev  ---
Created attachment 150973
  --> https://bugs.kde.org/attachment.cgi?id=150973=edit
idle chart

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kquickcharts] [Bug 457248] System monitor pie charts is broken

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=457248

--- Comment #4 from Roman Lebedev  ---
Created attachment 150972
  --> https://bugs.kde.org/attachment.cgi?id=150972=edit
sensors on system monitor

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kquickcharts] [Bug 457248] System monitor pie charts is broken

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=457248

--- Comment #3 from Roman Lebedev  ---
Created attachment 150971
  --> https://bugs.kde.org/attachment.cgi?id=150971=edit
pie chart settings in system monitor

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kquickcharts] [Bug 457248] New: System monitor pie charts is broken

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=457248

Bug ID: 457248
   Summary: System monitor pie charts is broken
   Product: frameworks-kquickcharts
   Version: 5.94.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ahiems...@heimr.nl
  Reporter: lebedev...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

1. The coordinate system is wrong. Somehow "Start from angle = -180*" results
in starting from six-o-clock, which is -90* in reality:
https://upload.wikimedia.org/wikipedia/commons/9/9a/Degree-Radian_Conversion.svg
2. There is some weird normalization bug. Even when the underlying data reaches
the specified data range max, the pie chart is still far from being full.

-- 
You are receiving this mail because:
You are watching all bug changes.

[ktorrent] [Bug 446475] File Download Order functionality has vanished

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=446475

Roman Lebedev  changed:

   What|Removed |Added

Version|21.11.90|21.12.3
 CC||lebedev...@gmail.com

--- Comment #2 from Roman Lebedev  ---
Same.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Elisa] [Bug 420895] Files view rooted at $HOME; cannot be used to browse alternative locations

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=420895

--- Comment #16 from Roman Lebedev  ---
I've posted https://invent.kde.org/multimedia/elisa/-/merge_requests/360
I don't know if there is some nicer solution that is planned,
but at least this makes elisa usable for me :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[Elisa] [Bug 420895] Files view rooted at $HOME; cannot be used to browse alternative locations

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=420895

Roman Lebedev  changed:

   What|Removed |Added

Version|19.12.3 |21.08.3
 CC||lebedev...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-ktexteditor] [Bug 365903] Search does not highlight search string occurrences that are part of a word

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=365903

Roman Lebedev  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |---
 Status|RESOLVED|REOPENED

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-ktexteditor] [Bug 365903] Search does not highlight search string occurrences that are part of a word

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=365903

--- Comment #6 from Roman Lebedev  ---
FWIW i can confirm this issue, i run into it constantly.
I think the behaviour that can be observed in QtCreator is much more
useful - selecting something (e.g. with a mouse) results in
all instances of the selected pattern being highlighted.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmix] [Bug 421495] Feature request: push-to-talk (PTT) for recording streams/microphones

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=421495

Roman Lebedev  changed:

   What|Removed |Added

 CC||lebedev...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 370640] kscreenlocker5 5.8.0-1 - got less usable with latest debian sid kf5 upgrades

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=370640

Roman Lebedev  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|NEEDSINFO   |REOPENED
 Resolution|WAITINGFORINFO  |---

--- Comment #13 from Roman Lebedev  ---
(In reply to Justin Zobel from comment #12)
> I've tried the lock/logout applet and I can flick my mouse to the bottom
> right of my screen and click it and I get the logout window.
> 
> Can you please test and confirm if this issue is still occurring or if this
> bug report can be marked as resolved.
This is still happening with debian sid
ii  libkscreenlocker5:amd64 5.19.5-3   
 amd64Secure lock screen
architecture

> I've set the bug status to "needsinfo" pending your response, please change
> back to "reported" or "resolved" when you respond, thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 370640] kscreenlocker5 5.8.0-1 - got less usable with latest debian sid kf5 upgrades

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=370640

--- Comment #11 from Roman Lebedev <lebedev...@gmail.com> ---
(In reply to Alexander Mentyu from comment #10)
> Could you please also try to change Compositor settings - disable or enable
> it - and try to reproduce the problem

Do have to re-login after changing the setting?
Without re-login, the issue remains after i enable the compositor.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 370640] kscreenlocker5 5.8.0-1 - got less usable with latest debian sid kf5 upgrades

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=370640

--- Comment #9 from Roman Lebedev <lebedev...@gmail.com> ---
Created attachment 46
  --> https://bugs.kde.org/attachment.cgi?id=46=edit
The Screen Edges params

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 370640] kscreenlocker5 5.8.0-1 - got less usable with latest debian sid kf5 upgrades

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=370640

--- Comment #7 from Roman Lebedev <lebedev...@gmail.com> ---
Still happens with current debian sid.
It's really pixel-perfect sensitivity problem.
It seems you need to point basically at the very edge of the screen. If you are
off by at least one pixel, it will get focus and will lock.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeplasma-addons] [Bug 389968] New: Timer widget: please add "count down to ${time}" support

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=389968

Bug ID: 389968
   Summary: Timer widget: please add "count down to ${time}"
support
   Product: kdeplasma-addons
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: timer
  Assignee: plasma-b...@kde.org
  Reporter: lebedev...@gmail.com
  Target Milestone: ---

Currently, you can only specify the time it should count down.
However there is a use-case to specify the target timestamp it should count
down *to*.

I.e. if i specify 00:15:00, it will count down 15 minutes.

But if i want to count down to today's 15:00pm, i need to calculate how many
hours/minutes/seconds that timestamp is from now, enter that, and start the
timer.

I'd prefer to be able to just specify the target time, and it can easily do the
calculations, much faster than i would :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[Heaptrack] [Bug 380860] Too long call line makes Summary page of heaptrack_gui unreadable

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=380860

--- Comment #2 from Roman Lebedev <lebedev...@gmail.com> ---
Yeah, i know, not ideal :D
This is how my integration test script for rawspeed library is being called..

-- 
You are receiving this mail because:
You are watching all bug changes.

[Heaptrack] [Bug 380860] New: Too long call line makes Summary page of heaptrack_gui unreadable

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=380860

Bug ID: 380860
   Summary: Too long call line makes Summary page of heaptrack_gui
unreadable
   Product: Heaptrack
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: m...@milianw.de
  Reporter: lebedev...@gmail.com
  Target Milestone: ---

Created attachment 105928
  --> https://bugs.kde.org/attachment.cgi?id=105928=edit
A screenshot of the Summary screen with the problem

I would guess that "debuggee:" field should either ellipsize, or be a
scrollable text-field, or the bottom part (with 5 scrolls) should be resizable.

*if* a solution is obvious, i guess i could implement the patch, since the
problem seems simple.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-ktexteditor] [Bug 365903] Search does not highlight search string occurrences that are part of a word

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=365903

Roman Lebedev <lebedev...@gmail.com> changed:

   What|Removed |Added

 CC||lebedev...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[ktorrent] [Bug 338930] Feature Request: Tracker Learning Database Loader

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=338930

Roman Lebedev <lebedev...@gmail.com> changed:

   What|Removed |Added

 CC||lebedev...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 373614] Crashes if Kdevelop is compilide against llvm 3.8 and mesa against 3.9

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=373614

Roman Lebedev <lebedev...@gmail.com> changed:

   What|Removed |Added

 CC||lebedev...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 372660] Kdenlive: please LOUDLY warn when there is proxy clips

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=372660

--- Comment #5 from Roman Lebedev <lebedev...@gmail.com> ---
(In reply to farid from comment #4)
> Hi Roman, 
> 
> Can you please test if it is fixed?

I can not test it, because i don't use appimages, and i don't think that
version is in debian testing yet.
Also, even if i would be able to test it, the issue is problematic to
reproduce.
So i guess feel free to close this, and if it happens with the version
containing the fix, i'll open/reopen issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 372660] Kdenlive: please LOUDLY warn when there is proxy clips

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=372660

--- Comment #2 from Roman Lebedev <lebedev...@gmail.com> ---
Hi Jean-Baptiste Mardelle.

I have not yet tried the recent-enough version with that commit, but looking at
the changes, i **think** it is not what i meant.
I do not want to see a warning simply when the toggle "Render using proxy
clips".

I want to see a warning when that toggle is DISABLED, but a proxy is enabled
for one of the clips (yellow "P" icon on the thumbnail in "Project Bin"(?)).
Because in such a case, for that particular clip, the proxy _WILL_ be used. No
matter the value of "Render using proxy clips" toggle.

I.e. that warning should be about the actual usage of proxy clips in the
render, not some settings.

Roman.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 372660] New: Kdenlive: please LOUDLY warn when there is proxy clips

[Roman Lebedev]

https://bugs.kde.org/show_bug.cgi?id=372660

Bug ID: 372660
   Summary: Kdenlive: please LOUDLY warn when there is proxy clips
   Product: kdenlive
   Version: 16.08.2
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: lebedev...@gmail.com
  Target Milestone: ---

When a proxy clip is enabled for one of the clips in the project, and setting
"use proxy clips for final export" is disabled, please LOUDLY warn that proxy
clip will be used. Ideally it should create a modal dialog "warning: proxy clip
will be used for render? Do render?"

Better, add a checkbox to NEVER use proxy clips for file renders.

This costs a lot of time. It has cost me more than 5 hours on more than three
separate occasions already :(

Roman.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369326] Kdevelop reliably crashes when Project -> Open Configuration

[Roman Lebedev via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369326

--- Comment #10 from Roman Lebedev <lebedev...@gmail.com> ---
Thank you!

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 370640] kscreenlocker5 5.8.0-1 - got less usable with latest debian sid kf5 upgrades

[Roman Lebedev via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370640

Roman Lebedev <lebedev...@gmail.com> changed:

   What|Removed |Added

 CC||lebedev...@gmail.com

--- Comment #2 from Roman Lebedev <lebedev...@gmail.com> ---
Created attachment 101556
  --> https://bugs.kde.org/attachment.cgi?id=101556=edit
A screenshot, the bottom sidepanel only

Or do you want the whole screen?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 370640] New: kscreenlocker5 5.8.0-1 - got less usable with latest debian sid kf5 upgrades

[Roman Lebedev via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=370640

Bug ID: 370640
   Summary: kscreenlocker5 5.8.0-1 -  got less usable with latest
debian sid kf5 upgrades
   Product: kscreenlocker
   Version: unspecified
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: lebedev...@gmail.com
CC: bhus...@gmail.com, mgraess...@kde.org

Hi.
Please don't get me wrong :)
I place screen locker button on panel, located at the bottom of the screen, at
the very right corner.
Previously, i was able to just move the mouse all the way to bottom-right
corner of the screen, left-click and the screenlocker would engage.
Now, it no longer works :(
If i move the mouse ll the way to bottom-right corner of the screen, the
screenlocker button no longer captures the focus.
Instead, i have to actually take care to place the mouse on top of screenlocker
button, and only then left-click...

Reproducible: Always

Steps to Reproduce:
1. add panel to the bottom of the screen
2. add screenlocker button to the very right edge/corner of the panel
3. move mouse all the way to bottom-right corner of the screen, left-click

Actual Results:  
screenlocker button does not capture the focus and does not lock the screen

Expected Results:  
screenlocker button should capture the focus and lock the screen
That is what it used to do before.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369326] Kdevelop reliably crashes when Project -> Open Configuration

[Roman Lebedev via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369326

--- Comment #7 from Roman Lebedev <lebedev...@gmail.com> ---
Because, at the time, i thought that since i only use cmake-based projects, i
do not need make plugin.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369326] Kdevelop reliably crashes when Project -> Open Configuration

[Roman Lebedev via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369326

--- Comment #5 from Roman Lebedev <lebedev...@gmail.com> ---
Yes, i did disable it by hand.
I think, i only disabled the 'make', not 'cmake' plugins.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369326] Kdevelop reliably crashes when Project -> Open Configuration

[Roman Lebedev via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369326

--- Comment #2 from Roman Lebedev <lebedev...@gmail.com> ---
Yes, it is.

>From https://bugs.kde.org/show_bug.cgi?id=369324#c1, which is the same issue as
this one as now know:
TLDR:
Can't load plugin "KDevCMakeBuilder" some of its required dependencies could
not be fulfilled: "org.kdevelop.IMakeBuilder"
Precedes crash

If i enable make and cmake plugins in kdevelop settings, the issue goes away.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369324] KDevelop5 crashes when i press Build

[Roman Lebedev via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369324

Roman Lebedev <lebedev...@gmail.com> changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=369326

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369326] Kdevelop reliably crashes when Project -> Open Configuration

[Roman Lebedev via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369326

Roman Lebedev <lebedev...@gmail.com> changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=369324

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 369324] KDevelop5 crashes when i press Build

[Roman Lebedev via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369324

--- Comment #1 from Roman Lebedev <lebedev...@gmail.com> ---
Additional information:

TLDR:
Can't load plugin "KDevCMakeBuilder" some of its required dependencies could
not be fulfilled: "org.kdevelop.IMakeBuilder"
Precedes crash

kdevplatform.serialization: version-hint not found, seems to be an old version
kdevplatform.serialization: "The data-repository at
/home/lebedevri/.cache/kdevduchain/kdevelop-{4610cd01-c18d-49fc-b307-32e906b07526}
has to be cleared."
Reusing existing ksycoca
Recreating ksycoca file
("/home/lebedevri/.cache/ksycoca5_en_9lP7GuKr0b+4rT+3m4RRdB8wUmw=", version
303)
modified: "kdevelopsessions.desktop"
modified: "plasma-applet-kdevelopsessions.desktop"
modified: "plasma-dataengine-kdevelopsessions.desktop"
modified: "kdevelopplugin.desktop"
modified: "text/x-kdevelop.xml"
modified: "packages/kdevelop.xml"
modified: "packages/kdevelopinternal.xml"
modified: "text/x-kdevelop-internal.xml"
Still in the time dict (i.e. deleted files) ("apps")
kf5.kservice.sycoca: Parse error in 
"/home/lebedevri/.config/menus/applications-merged/xdg-desktop-menu-dummy.menu"
, line  1 , col  1 :  "unexpected end of file"
Menu "applications-kmenuedit.menu" not found.
modified: "/home/lebedevri/kde/usr/share/applications/org.kde.kdevelop.desktop"
modified:
"/home/lebedevri/kde/usr/share/applications/org.kde.kdevelop_ps.desktop"
The desktop entry file 
"/home/lebedevri/.local/share/applications/ckan-handler.desktop"  has Type= "
Application"  instead of "Application" or "Service"
kf5.kservice.sycoca: Invalid Service : 
"/home/lebedevri/.local/share/applications/ckan-handler.desktop"
Saving
Not loading plugin named "KDevMakeBuilder" because it has been disabled!
Can't load plugin "KDevCMakeBuilder" some of its required dependencies could
not be fulfilled: "org.kdevelop.IMakeBuilder"
Can't load plugin "KDevQMakeBuilder" some of its required dependencies could
not be fulfilled: "org.kdevelop.IMakeBuilder"
Attempted to re-run an already running session.
couldn't create slave: "Unable to create io-slave:\nklauncher said: Unknown
protocol 'man'.\n"
Invalid return type in method "core"
Invalid return type in method "extensions"
KSambaShare: Could not find smb.conf!
Invalid return type in method "core"
Invalid return type in method "extensions"
Can't load plugin "KDevCMakeBuilder" some of its required dependencies could
not be fulfilled: "org.kdevelop.IMakeBuilder"
ASAN:DEADLYSIGNAL
=
==24876==ERROR: AddressSanitizer: SEGV on unknown address 0x0020 (pc
0x7f7a69ca2d9d bp 0x7ffe469fc220 sp 0x7ffe469fc210 T0)
#0 0x7f7a69ca2d9c in KDevelop::IPlugin::extensions() const
/home/lebedevri/kde/src/kdevplatform/interfaces/iplugin.cpp:137
#1 0x7f7a6ab71926 in KDevelop::IProjectBuilder*
KDevelop::IPlugin::extension()
(/home/lebedevri/kde/usr/lib/x86_64-linux-gnu/libKDevPlatformShell.so.10+0x150926)
#2 0x7f7a39739b2c in CMakeManager::builder() const
/home/lebedevri/kde/src/kdevelop/projectmanagers/cmake/cmakemanager.cpp:242
#3 0x7f7a615e6038 in
KDevelop::BuilderJobPrivate::addJob(KDevelop::BuilderJob::BuildType,
KDevelop::ProjectBaseItem*)
/home/lebedevri/kde/src/kdevplatform/project/builderjob.cpp:123
#4 0x7f7a615e68dc in
KDevelop::BuilderJob::addItems(KDevelop::BuilderJob::BuildType,
QList<KDevelop::ProjectBaseItem*> const&)
/home/lebedevri/kde/src/kdevplatform/project/builderjob.cpp:164
#5 0x7f7a4109ad89 in
ProjectManagerViewPlugin::runBuilderJob(KDevelop::BuilderJob::BuildType,
QList<KDevelop::ProjectBaseItem*>)
/home/lebedevri/kde/src/kdevplatform/plugins/projectmanagerview/projectmanagerviewplugin.cpp:397
#6 0x7f7a4109b081 in ProjectManagerViewPlugin::buildProjectItems()
/home/lebedevri/kde/src/kdevplatform/plugins/projectmanagerview/projectmanagerviewplugin.cpp:425
#7 0x7f7a410acd7b in QtPrivate::FunctorCall<QtPrivate::IndexesList<>,
QtPrivate::List<>, void, void (ProjectManagerViewPlugin::*)()>::call(void
(ProjectManagerViewPlugin::*)(), ProjectManagerViewPlugin*, void**)
(/home/lebedevri/kde/usr/lib/x86_64-linux-gnu/plugins/kdevplatform/26/kdevprojectmanagerview.so+0x33d7b)
#8 0x7f7a410ab9d7 in void QtPrivate::FunctionPointer::call<QtPrivate::List<>, void>(void
(ProjectManagerViewPlugin::*)(), ProjectManagerViewPlugin*, void**)
(/home/lebedevri/kde/usr/lib/x86_64-linux-gnu/plugins/kdevplatform/26/kdevprojectmanagerview.so+0x329d7)
#9 0x7f7a410a9647 in QtPrivate::QSlotObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*)
(/home/lebedevri/kde/usr

[kdevelop] [Bug 369326] New: Kdevelop reliably crashes when Project -> Open Configuration

[Roman Lebedev via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369326

Bug ID: 369326
   Summary: Kdevelop reliably crashes when Project -> Open
Configuration
   Product: kdevelop
   Version: 5.0.1
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: lebedev...@gmail.com

Application: kdevelop (5.0.1)

Qt Version: 5.6.1
Frameworks Version: 5.25.0
Operating System: Linux 4.7.0-1-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
- What I was doing when the application crashed:

I see no obivious pattern.
It worked fine yesterday.

Now, each time i press Project -> Open Configuration, kdevelop crashes.
This is cmake-based project.

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7b24e1e940 (LWP 31358))]

Thread 17 (Thread 0x7f7aef300700 (LWP 31482)):
#0  0x7f7b1e5be538 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f7b24ecfb76 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f7b24ecb2f2 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f7b24eced78 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f7b1e5b8464 in start_thread (arg=0x7f7aef300700) at
pthread_create.c:333
#5  0x7f7b247e197f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 16 (Thread 0x7f7af0ade700 (LWP 31480)):
#0  0x7f7b1d751009 in g_mutex_lock (mutex=mutex@entry=0x365fc70) at
././glib/gthread-posix.c:1336
#1  0x7f7b1d70b9bb in g_main_context_iterate (priority=,
n_fds=1, fds=0x35df960, timeout=, context=0x365fc70) at
././glib/gmain.c:4221
#2  0x7f7b1d70b9bb in g_main_context_iterate
(context=context@entry=0x365fc70, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3922
#3  0x7f7b1d70baec in g_main_context_iteration (context=0x365fc70,
may_block=1) at ././glib/gmain.c:3988
#4  0x7f7b250fc51b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f7b250a419a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f7b24ec9e53 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f7b24eced78 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f7b1e5b8464 in start_thread (arg=0x7f7af0ade700) at
pthread_create.c:333
#9  0x7f7b247e197f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 15 (Thread 0x7f7af1300700 (LWP 31414)):
#0  0x7f7b247dd0b9 in syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f7b24ec6a00 in QBasicMutex::lockInternal() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f7b24ec6b12 in QMutex::lock() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f7af9d90ec8 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) (file=, imports=..., session=...,
features=features@entry=KDevelop::TopDUContext::AllDeclarationsContextsAndUses,
includedFiles=..., index=0x1edf2c0, abortFunction=...) at
./languages/clang/duchain/clanghelpers.cpp:133
#4  0x7f7af9d90d00 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) (file=, imports=..., session=...,
features=features@entry=KDevelop::TopDUContext::AllDeclarationsContextsAndUses,
includedFiles=..., index=0x1edf2c0, abortFunction=...) at
./languages/clang/duchain/clanghelpers.cpp:121
#5  0x7f7af9d90d00 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) (file=, imports=..., session=...,
features=features@entry=KDevelop::TopDUContext::AllDeclarationsContextsAndUses,
includedFiles=..., index=0x1edf2c0, abortFunction=...) at
./languages/clang/duchain/clanghelpers.cpp:121
#6  0x7f7af9d90d00 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) (file=, imports=..., session=...,
features=features@entry=KDevelop::TopDUContext::AllDeclarationsContextsAndUses,
includedFiles=..., index=0x1edf2c0, abortFunction=...) at

[kdevelop] [Bug 369324] New: KDevelop5 crashes when i press Build

[Roman Lebedev via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369324

Bug ID: 369324
   Summary: KDevelop5 crashes when i press Build
   Product: kdevelop
   Version: 5.0.1
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: lebedev...@gmail.com

Application: kdevelop (5.0.1)

Qt Version: 5.6.1
Frameworks Version: 5.25.0
Operating System: Linux 4.7.0-1-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
- What I was doing when the application crashed:

Sometimes, when i press build button, kdevelop crashes.
CMake-based project is loaded (darktable).
I see no obivious pattern.

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0ed7bf6940 (LWP 9324))]

Thread 18 (Thread 0x7f0ea2090700 (LWP 9470)):
#0  0x7f0ed1396538 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f0ed7ca7b76 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f0ed7ca32f2 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f0ed7ca6d78 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f0ed1390464 in start_thread (arg=0x7f0ea2090700) at
pthread_create.c:333
#5  0x7f0ed75b997f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 17 (Thread 0x7f0ea38d7700 (LWP 9468)):
#0  0x7f0ed0529024 in g_mutex_unlock (mutex=0x2708e80) at
././glib/gthread-posix.c:1348
#1  0x7f0ed04e2ecc in g_main_context_prepare
(context=context@entry=0x2708e80, priority=priority@entry=0x7f0ea38d6b40) at
././glib/gmain.c:3497
#2  0x7f0ed04e38fb in g_main_context_iterate
(context=context@entry=0x2708e80, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3907
#3  0x7f0ed04e3aec in g_main_context_iteration (context=0x2708e80,
may_block=1) at ././glib/gmain.c:3988
#4  0x7f0ed7ed451b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0ed7e7c19a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f0ed7ca1e53 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f0ed7ca6d78 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f0ed1390464 in start_thread (arg=0x7f0ea38d7700) at
pthread_create.c:333
#9  0x7f0ed75b997f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 16 (Thread 0x7f0ea40d8700 (LWP 9384)):
#0  0x7f0ed139618f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0ed7ca7c3b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f0ecce14da0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7f0ecce18fc8 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7f0ecce13f1d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f0ecce19022 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f0ecce13f1d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f0ecce16de9 in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f0ed7ca6d78 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f0ed1390464 in start_thread (arg=0x7f0ea40d8700) at
pthread_create.c:333
#10 0x7f0ed75b997f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 15 (Thread 0x7f0ea48d9700 (LWP 9383)):
#0  0x7f0ed75b50b9 in syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f0ed7c9ea00 in QBasicMutex::lockInternal() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f0ed7c9eb12 in QMutex::lock() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f0eacb68ec8 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) () at
/usr/lib/x86_64-linux-gnu/libKDevClangPrivate.so.25
#4  0x7f0eacb68d00 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) () at

[kdevelop] [Bug 361958] outline dropdown widget jumps to function implementation in another file

[Roman Lebedev via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361958

--- Comment #5 from Roman Lebedev <lebedev...@gmail.com> ---
Created attachment 101248
  --> https://bugs.kde.org/attachment.cgi?id=101248=edit
Test case with multiple source files implementing same function

This testcase contains 2 source files, both of which implement the same symbol
- process().
They compile into separate modules, so this is absolutely valid case.
This is minimized from darktable's iop -
https://github.com/darktable-org/darktable/blob/master/src/iop/CMakeLists.txt

Try switching to this process() symbol.
Sometimes it switches to the currently selected source file, sometimes not.
It seems to depend on which file was opened first.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 361958] outline dropdown widget jumps to function implementation in another file

[Roman Lebedev via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361958

Roman Lebedev <lebedev...@gmail.com> changed:

   What|Removed |Added

 CC||lebedev...@gmail.com

--- Comment #4 from Roman Lebedev <lebedev...@gmail.com> ---
I'm also affected by this.
This is not a regression, at least not a recent one, it was like that for years
(at least 3)
I must say, it's quite inconvenient at the very least :)

-- 
You are receiving this mail because:
You are watching all bug changes.