[filelight] [Bug 438107] No way to go from 'concentric rings' view to Initial view.

2021-06-06 Thread hancerli
https://bugs.kde.org/show_bug.cgi?id=438107

hancerli  changed:

   What|Removed |Added

 CC||bhance...@gmail.com
   Keywords||junior-jobs

--- Comment #1 from hancerli  ---
As I stated in https://bugs.kde.org/show_bug.cgi?id=434532#c8 this one must be
evaluated by one of the maintainers. 

If that's a bug then I can take this on.

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

[filelight] [Bug 434532] "Up" button should be greyed out when in root or top directory

2021-06-06 Thread hancerli
https://bugs.kde.org/show_bug.cgi?id=434532

--- Comment #10 from hancerli  ---
Thanks!

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

[filelight] [Bug 435125] Total file size accumulates when refreshing

2021-05-26 Thread hancerli
https://bugs.kde.org/show_bug.cgi?id=435125

--- Comment #7 from hancerli  ---
then should it be closed?

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

[plasmashell] [Bug 436119] Possible memory leak

2021-05-17 Thread hancerli
https://bugs.kde.org/show_bug.cgi?id=436119

hancerli  changed:

   What|Removed |Added

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

--- Comment #4 from hancerli  ---
Here's the heaptrack analysis file. 
https://drive.google.com/file/d/1Ejj5GPR3iok-fsHCfKS_ncyu5GWreNXg/view?usp=sharing

Can't add ass attachment since it's 170mb. 

I'm fairly new to heaptrack and it'll take some time for me to start
understanding the content. So I decided to upload it asap if you'd like to
analyze it.

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

[filelight] [Bug 407177] Folder size differs from "du -h"

2021-05-17 Thread hancerli
https://bugs.kde.org/show_bug.cgi?id=407177

--- Comment #5 from hancerli  ---
Tried but cannot reproduce it. "du -hs" and filelight both report very similar
size info. There're minor differences which I assume caused by GiB - GB
difference.

Could it be related to a previous version?

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

[filelight] [Bug 407177] Folder size differs from "du -h"

2021-05-16 Thread hancerli
https://bugs.kde.org/show_bug.cgi?id=407177

--- Comment #4 from hancerli  ---
Thanks, I'll try that out.

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

[filelight] [Bug 407177] Folder size differs from "du -h"

2021-05-16 Thread hancerli
https://bugs.kde.org/show_bug.cgi?id=407177

hancerli  changed:

   What|Removed |Added

 CC||bhance...@gmail.com

--- Comment #2 from hancerli  ---
Hi there,

Thanks for reporting the bug.

I tested this one with more than 10 different folders (to see if somehow the
length of the folder name meddles with the size calculation) but couldn't see
that happening. Every time it worked correctly.

Can you still reproduce it? Or maybe it's been resolved?

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

[filelight] [Bug 435125] Total file size accumulates when refreshing

2021-05-16 Thread hancerli
https://bugs.kde.org/show_bug.cgi?id=435125

--- Comment #4 from hancerli  ---
I believe this one is still valid.

The total size increases only in the "refreshing" period. However, the size
information is shown correctly after the operation is done.

Is this the behavior you observe?

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

[filelight] [Bug 435125] Total file size accumulates when refreshing

2021-05-16 Thread hancerli
https://bugs.kde.org/show_bug.cgi?id=435125

--- Comment #3 from hancerli  ---
Created attachment 138488
  --> https://bugs.kde.org/attachment.cgi?id=138488&action=edit
main screen - total size shown properly

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

[filelight] [Bug 435125] Total file size accumulates when refreshing

2021-05-16 Thread hancerli
https://bugs.kde.org/show_bug.cgi?id=435125

hancerli  changed:

   What|Removed |Added

 CC||bhance...@gmail.com

--- Comment #2 from hancerli  ---
Created attachment 138487
  --> https://bugs.kde.org/attachment.cgi?id=138487&action=edit
refresh screen - total size miscalculated

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

[filelight] [Bug 434652] Filelight does not show Docker disk usage.

2021-05-16 Thread hancerli
https://bugs.kde.org/show_bug.cgi?id=434652

hancerli  changed:

   What|Removed |Added

 CC||bhance...@gmail.com

--- Comment #1 from hancerli  ---
Hi there,

Can you please elaborate a bit more on this one? I'm a bit lost between the
words and descriptions.

Also, a screenshot would be very useful indeed.

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

[plasmashell] [Bug 436119] Possible memory leak

2021-05-16 Thread hancerli
https://bugs.kde.org/show_bug.cgi?id=436119

--- Comment #3 from hancerli  ---
(In reply to David Edmundson from comment #1)
> >Is there any way to trace what consumes that much memory?
> 
> There is a tool called Heaptrack
> 
> That or just turning off applets individually till you nail it down.
> 
> I'm afraid there's not much we can do without some narrowing it down

Hi there,

Seems I skipped your response, somehow, sorry.

I just run the plasmashell with heaptrack and waiting for the memory usage to
rise up again, then I'll share the report. Should I switch the status back to
REPORTED?

Btw, thanks for the tip.

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

[filelight] [Bug 434532] "Up" button should be greyed out when in root or top directory

2021-05-05 Thread hancerli
https://bugs.kde.org/show_bug.cgi?id=434532

--- Comment #8 from hancerli  ---
(In reply to Mohammed Sameer from comment #6)
> Hi,
> I am not sure if this is correct, I think I have mistakenly reported that
> the bug is "Up" button is not greyed out when in root directory.
> But I think the "Up" button was meant for going back to "Initial
> view"(please see attached screenshot) & it is not working, because if we go
> to the "pie chart view", currently there is no way to go back to the
> "Initial view" other than reopening the filelight app.
> Could this be fixed here or submit a new bug report?

Hi Mohammed,
I'd like to work on this as well, but one of the maintainers should respond to
clarify if this is intentional or a design flaw.

IMHO, either way, it needs a new ticket.

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

[filelight] [Bug 434532] "Up" button should be greyed out when in root or top directory

2021-04-25 Thread hancerli
https://bugs.kde.org/show_bug.cgi?id=434532

hancerli  changed:

   What|Removed |Added

 CC||bhance...@gmail.com

--- Comment #2 from hancerli  ---
Anyone working on this one? Otherwise I can take it.

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

[plasmashell] [Bug 436119] New: Possible memory leak

2021-04-24 Thread hancerli
https://bugs.kde.org/show_bug.cgi?id=436119

Bug ID: 436119
   Summary: Possible memory leak
   Product: plasmashell
   Version: 5.21.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: generic-performance
  Assignee: plasma-b...@kde.org
  Reporter: bhance...@gmail.com
  Target Milestone: 1.0

SUMMARY
Hi there

I've been observing strange plasmashell behavior since it's installed. After
using it a couple of days (a couple of sleep-wakeup cycles) plasmashell starts
consuming a humongous amount of memory even though there are no
memory-intensive applications running in the background.

To lower the usage down, I have to either restart the plasmashell
(kquitapp5/kstart5) or reboot the device, otherwise, my total memory usage goes
up to %80-90, and swap is being used. Total usage reached around %88-%90 today
and lowered to %60 after restarting the plasmashell.

Is there any way to trace what consumes that much memory?

STEPS TO REPRODUCE
1. Start the KDE as usual
2. Use suspend instead of turning-off for a couple of days

OBSERVED RESULT
Memory usage of the plasmashell keeps increasing

EXPECTED RESULT
Memory usage of the plasmashell should stay same

SOFTWARE/OS VERSIONS
Windows: No
macOS: No
Linux/KDE Plasma: Yes 
(available in About System)
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.81.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

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

[dolphin] [Bug 431452] Maybe Dolphin should shows folder size/counter for empty folders too

2021-04-22 Thread hancerli
https://bugs.kde.org/show_bug.cgi?id=431452

hancerli  changed:

   What|Removed |Added

   Version Fixed In||21.04
  Latest Commit||https://invent.kde.org/syst
   ||em/dolphin/-/commit/acc42f9
   ||18925983e2e83501cd2bacc7952
   ||a55718

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

[dolphin] [Bug 431452] Maybe Dolphin should shows folder size/counter for empty folders too

2021-04-22 Thread hancerli
https://bugs.kde.org/show_bug.cgi?id=431452

hancerli  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from hancerli  ---
Sorry, I believe this commit has fixed the issue:

https://invent.kde.org/system/dolphin/-/commit/acc42f918925983e2e83501cd2bacc7952a55718

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

[dolphin] [Bug 431452] Maybe Dolphin should shows folder size/counter for empty folders too

2021-04-22 Thread hancerli
https://bugs.kde.org/show_bug.cgi?id=431452

--- Comment #2 from hancerli  ---
Created attachment 137805
  --> https://bugs.kde.org/attachment.cgi?id=137805&action=edit
Empty folder size is shown properly

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

[dolphin] [Bug 431452] Maybe Dolphin should shows folder size/counter for empty folders too

2021-04-22 Thread hancerli
https://bugs.kde.org/show_bug.cgi?id=431452

hancerli  changed:

   What|Removed |Added

 CC||bhance...@gmail.com

--- Comment #1 from hancerli  ---
Hi there,

Even though there's no reference in the codebase, this one seems resolved in
version 21.07.70

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