date:20230402

[kate] [Bug 450419] 'Open Recent' listing is not shared across instances

2023-04-02 Thread jimbo

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

--- Comment #4 from jimbo  ---
I disagree that having recent files specific to the instance makes sense, I
would say it's counter-intuitive. However, it's probably too specific a feature
for the amount of work required.

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

[kate] [Bug 466531] Kate stops responding after pasting a very long line

2023-04-02 Thread Bug Janitor Service

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #7 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[kwin] [Bug 247353] [Tiling] KWin tiling with many windows can make the whole workspace unresponsive

2023-04-02 Thread Bug Janitor Service

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

--- Comment #5 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[kmymoney] [Bug 468108] New: ledger freeze on large account

2023-04-02 Thread Jonatan Cloutier

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

Bug ID: 468108
   Summary: ledger freeze on large account
Classification: Applications
   Product: kmymoney
   Version: git (master)
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: cloutier...@gmail.com
  Target Milestone: ---

Created attachment 157810
  --> https://bugs.kde.org/attachment.cgi?id=157810=edit
backtrace while freezed

SUMMARY
When trying to display any account ledger that has a large amount of
transaction (1k+) cpu goes to 100% and KMyMoney freeze and has to be killed.
Maybe I wasn't patient enough and it would have respond back, but more than a
few minutes would still make no sense.

Also, I'm guessing it related to the amount of transaction since it only happen
on a few of my larger account, but maybe some specific transaction that are
more likely to happen there or more reconciliation.

The culprit seems to be arround this:
#13 0x55b452bc in
SpecialLedgerItemFilterPrivate::filterAcceptsRow(QModelIndex const&,
QModelIndex const&, int) const (rowCount=977, source_parent=..., idx=...,
this=)
at /build/kmymoney/models/specialledgeritemfilter.cpp:288
#14 SpecialLedgerItemFilterPrivate::filterAcceptsRow(QModelIndex const&,
QModelIndex const&, int) const (this=, idx=,
source_parent=..., rowCount=)
at /build/kmymoney/models/specialledgeritemfilter.cpp:217

and caused by
https://github.com/KDE/kmymoney/commit/281c9759045f2a7929264accb58638ed250cf418
or later (did rollback to  f3b33e9 and it work, haven't try forward reproducing
the issue.

STEPS TO REPRODUCE
1. open ledger on any large account, either from the account page or the ledger
itself switching to another tab

OBSERVED RESULT
freeze

EXPECTED RESULT
display the ledger

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: (available in About System) 5.104.0
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 5.15.18
Built statically through the docker compose provided, but ran locally on my
arch

ADDITIONAL INFORMATION

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

[digikam] [Bug 468049] Digikam crash when image quality sorter used - terminate called after throwing an instance of 'cv::Exception'

2023-04-02 Thread bugzilla_noreply

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

--- Comment #6 from caulier.gil...@gmail.com ---
Petr,

Did you downloaded the DNN model file for the aesthetic detector?
(weights_inceptionv3_299.pb).
What's the contents from ~/.local/share/digikam/facesengine ?
Can you copy and paste the debug statement for the console when digikam start
(not the gdb trace) ? 
Did you use multi-core option from maintenance tool ?

Gilles Caulier

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

[frameworks-knewstuff] [Bug 468107] New: welcome screen "commodore 64" don't install

2023-04-02 Thread monono

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

Bug ID: 468107
   Summary: welcome screen "commodore 64" don't install
Classification: Frameworks and Libraries
   Product: frameworks-knewstuff
   Version: unspecified
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ad...@leinir.dk
  Reporter: gomorales.vic...@gmail.com
CC: alexander.loh...@gmx.de, kdelibs-b...@kde.org
  Target Milestone: ---

SUMMARY
welcome screen "commodore 64" don't install
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[kwin] [Bug 465937] Split does not reset to its original value once "adjacent quick-tiled windows" configuration ceases to exist

2023-04-02 Thread Prajna Sariputra

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

Prajna Sariputra  changed:

   What|Removed |Added

 CC||putr...@gmail.com

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

[plasma-systemmonitor] [Bug 468106] New: RAM and CPU usage do not reflect user experience and are not as useful

2023-04-02 Thread Dan Dascalescu

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

Bug ID: 468106
   Summary: RAM and CPU usage do not reflect user experience and
are not as useful
Classification: Applications
   Product: plasma-systemmonitor
   Version: 5.27.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: ddascalescu+...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
  Target Milestone: ---

Created attachment 157809
  --> https://bugs.kde.org/attachment.cgi?id=157809=edit
Screenshot

I ran into a state in which my new ThinkPad P1 Gen5's fan remained at max speed
for over an hour, even though System Monitor showed a total CPU utilization of
under 9% throughout this time. Running htop showed that `nvidia-powerd` was
roasting the CPU. "Show: All processes" was checked. Choosing "Show: System
Processes", `nvidia-powerd` was shown as taking up only 5% of the CPU.

Maybe this is technically correct if only one core was running at 100% and 5%
was an average across all core, but this isn't what interests the user. I was
using System Monitor to find out what was causing the fan to stay on, and a
process at 5% is easy to overlook and not suspect as the culprit. htop's output
was more useful.

In other instances (may post a screenshot later), the total memory of the
running apps from the Applications tab seemed to be under 4GB, yet my 16GB
system was thrashing the swap file. Whatever system components were using the
other ~12GB, should be shown, ideally with an option to kill them.

SOFTWARE/OS VERSIONS
Tuxedo OS 22.04 2
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8

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

[Akonadi] [Bug 456983] mysql.err.old grows too large (over 20 GB)

2023-04-02 Thread michele mazza

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

michele mazza  changed:

   What|Removed |Added

 CC||michele.ma...@gmail.com

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

[kdeconnect] [Bug 468105] Desktop displays deleted messages

2023-04-02 Thread bugzilla_noreply

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

--- Comment #2 from biscotty...@gmail.com ---
Created attachment 157808
  --> https://bugs.kde.org/attachment.cgi?id=157808=edit
Same conversation from the computer

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

[kdeconnect] [Bug 468105] Desktop displays deleted messages

2023-04-02 Thread bugzilla_noreply

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

--- Comment #1 from biscotty...@gmail.com ---
Created attachment 157807
  --> https://bugs.kde.org/attachment.cgi?id=157807=edit
>From the phone

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

[kdeconnect] [Bug 468105] New: Desktop displays deleted messages

2023-04-02 Thread bugzilla_noreply

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

Bug ID: 468105
Summary: Desktop displays deleted messages
Classification: Applications
Product: kdeconnect
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: messaging-application
Assignee: si...@ergotech.com
Reporter: biscotty...@gmail.com
Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

STEPS TO REPRODUCE
1. Connect android phone to computer
2. Install kpeoplevcard (I don't know why this isn't installed by default)
3.

OBSERVED RESULT

The desktop displays messages that have been deleted from my phone. In addition
there is at least one thread in which the content differs between the phone and
the computer.

EXPECTED RESULT

That all messages are correctly syncronized.

SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Fedora 37
(available in About System)
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
This is the first time I try to use KDE Connect on this computer. I had used it
with the same phone and an Ubuntu install but it was problematic so I didn't
keep using it. I do believe that the persistence of deleted messages was one of
my issues.

Thank you for all of your high-quality applications. After decades of trying
KDE intermittently I've found a home since I tried again a year ago. It's
finally the product I always wanted it to be. Activities are awesome!

1 2 3 >

1 - 100 of 221 matches

Mail list logo