[filelight] [Bug 472271] Less an less effective

2023-07-14 Thread Mihai Sorin Dobrescu
https://bugs.kde.org/show_bug.cgi?id=472271

Mihai Sorin Dobrescu  changed:

   What|Removed |Added

 CC||msdobre...@gmail.com

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

[filelight] [Bug 472271] New: Less an less effective

2023-07-14 Thread Mihai Sorin Dobrescu
https://bugs.kde.org/show_bug.cgi?id=472271

Bug ID: 472271
   Summary: Less an less effective
Classification: Applications
   Product: filelight
   Version: 23.04.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: msdobre...@gmail.com
CC: martin.sandsm...@kde.org
  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
***

I used Filelight for years, I loved its simple infographic that presented the
largest dirs along with their size directly on the graphic.
Then, I was about to file a bug about it having no data on the graphic in some
cases, but was interrupted by upgrading to 23.04.2 and PAM! It showed a bloated
app!

While some may find useful the size panel, I don't. And cannot be disabled or
hidden.
>From a cool app with a simple look and yet comprehensive, it has become
something I - personally - won't use unless I have to.

Please bring back the feature of displaying the totals on the graphic, the
details on hover and a possibility to hide the left panel, the one with sizes!

SOFTWARE/OS VERSIONS
Operating System: MocaccinoOS 
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 6.1.38-mocaccino (64-bit)
Graphics Platform: X11
Processors: 16 × 11th Gen Intel® Core™ i7-11700K @ 3.60GHz
Memory: 61.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
Manufacturer: ASUS

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

[kdiff3] [Bug 472270] New: Crash when ignoring whitespace and diffing files with trailing whitespace

2023-07-14 Thread nyanpasu64
https://bugs.kde.org/show_bug.cgi?id=472270

Bug ID: 472270
   Summary: Crash when ignoring whitespace and diffing files with
trailing whitespace
Classification: Applications
   Product: kdiff3
   Version: 1.10.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: reeves...@gmail.com
  Reporter: nyanpas...@tuta.io
  Target Milestone: ---

Created attachment 160299
  --> https://bugs.kde.org/attachment.cgi?id=160299=edit
asan log of kdiff3 git d16aacc31841983a973faf2c1ce7989a7c72aee9

SUMMARY
When I diff files with whitespace at the end, while ignoring whitespace
differences, the app crashes.

STEPS TO REPRODUCE
1. Compile kdiff3 with asan enabled. Without it, the crashes only occur
randomly.
2. `kdiff3 file1 file2 file3` (sorry I cannot share the files)

OBSERVED RESULT
Segfault in 

EXPECTED RESULT
No segfault.

This bug actually consists of multiple interlocking related sources of
undefined behavior. The code was changed in
https://invent.kde.org/sdk/kdiff3/-/commit/f4b160a95e2079206dbf3bbd9de8e9546a499907#39f490613200d238a14dba98bf938d0cd0bb5b8e,
after your most recent 1.10.5 release. However it doesn't actually fix the
crash.

- Now you mark lines as different if they differ in length, even if they only
differ in whitespace and the loop body would mark them as identical. I think
this change should be reverted? IDK.
- That commit adds `if((p1 != p1End && p2 != p2End) && *p1 != *p2)` to avoid
dereferencing an out-of-bounds pointer. But your latest git commit still
crashes with asan enabled, because you check `isspace(p1->unicode()) && p1 !=
p1End`. If p1 points out of bounds, you dereference it *before* checking if
it's OOB.
- I'm not sure if .end() is technically valid to dereference because it's a
null terminator. QString adds null terminators on some but not all method
calls. I still think it's a bug to dereference .end().
- Even if you checked `p1 != p1End` before incrementing p1, the end-of-loop
condition executes `++p1, ++p2`, resulting in a "past-the-end" pointer which
isn't caught by `p1 != p1End` but is still invalid to dereference.
- This is invalid *even if a null terminator is present!*

I've patched all invalid derefs and increments at
https://invent.kde.org/nyanpasu/kdiff3/-/tree/fix-segfault. This version of the
program passes asan without errors. Even then, when closing the program, I get
an unrelated segfault even without asan. If I enable asan, I get a log where
apparently you're calling ~ProgressDialog() after main() exits:

==338259==ERROR: AddressSanitizer: SEGV on unknown address 0x4082 (pc
0x7f207a9025a0 bp 0x61906480 sp 0x7ffdf69c9540 T0)
==338259==The signal is caused by a READ memory access.
#0 0x7f207a9025a0 in QXcbConnection::removeWindowEventListener(unsigned
int) (/usr/lib/libQt5XcbQpa.so.5+0x385a0) (BuildId:
0d9bddd568990cb856de2d0fbc95719075f2bb11)
#1 0x7f207a91ede6 in QXcbWindow::destroy()
(/usr/lib/libQt5XcbQpa.so.5+0x54de6) (BuildId:
0d9bddd568990cb856de2d0fbc95719075f2bb11)
#2 0x7f207a91eee5 in QXcbWindow::~QXcbWindow()
(/usr/lib/libQt5XcbQpa.so.5+0x54ee5) (BuildId:
0d9bddd568990cb856de2d0fbc95719075f2bb11)
#3 0x7f207b68e0f5 
(/usr/lib/qt/plugins/xcbglintegrations/libqxcb-glx-integration.so+0x80f5)
(BuildId: 56d55ed2b339b27593c0687479bdc5caa4ca7928)
#4 0x7f2083155919 in QWindowPrivate::destroy()
(/usr/lib/libQt5Gui.so.5+0x155919) (BuildId:
acccfa0e6cf0112180781234f2b5087fd4cd0fc0)
#5 0x7f208399698b in QWidgetPrivate::deleteTLSysExtra()
(/usr/lib/libQt5Widgets.so.5+0x19698b) (BuildId:
b61c3153959c656fb8e955fe52184933b0a19c5f)
#6 0x7f20839b8a68 in QWidget::destroy(bool, bool)
(/usr/lib/libQt5Widgets.so.5+0x1b8a68) (BuildId:
b61c3153959c656fb8e955fe52184933b0a19c5f)
#7 0x7f208399ba42 in QWidget::~QWidget()
(/usr/lib/libQt5Widgets.so.5+0x19ba42) (BuildId:
b61c3153959c656fb8e955fe52184933b0a19c5f)
#8 0x55ecdbfdd225 in ProgressDialog::~ProgressDialog()
(/usr/bin/kdiff3+0x132a225) (BuildId: 44e4831ca1d69b2d07a18fdaada303168c6cc77b)
#9 0x55ecdc0e3f8e in void std::_Destroy(ProgressDialog*)
(/usr/bin/kdiff3+0x1430f8e) (BuildId: 44e4831ca1d69b2d07a18fdaada303168c6cc77b)
#10 0x55ecdc0e0574 in std::_Sp_counted_ptr_inplace, (__gnu_cxx::_Lock_policy)2>::_M_dispose()
(/usr/bin/kdiff3+0x142d574) (BuildId: 44e4831ca1d69b2d07a18fdaada303168c6cc77b)
#11 0x55ecdbfcdc3b in
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release()
/usr/include/c++/13.1.1/bits/shared_ptr_base.h:346
#12 0x55ecdbfd66e1 in
std::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count()
/usr/include/c++/13.1.1/bits/shared_ptr_base.h:1071
#13 0x55ecdc085f9d in std::__shared_ptr::~__shared_ptr()
/usr/include/c++/13.1.1/bits/shared_ptr_base.h:1524
#14 0x55ecdc08600b in std::shared_ptr::~shared_ptr()

[digikam] [Bug 472269] New: Unable to change/remove "Ignored" identity Face Tags and name as a person

2023-07-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=472269

Bug ID: 472269
   Summary: Unable to change/remove "Ignored" identity Face Tags
and name as a person
Classification: Applications
   Product: digikam
   Version: 8.1.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Faces-Workflow
  Assignee: digikam-bugs-n...@kde.org
  Reporter: richarda...@hotmail.com
  Target Milestone: ---

SUMMARY
There is functionality to remove a Face Tag identity by right clicking on the
photo. However it does not list the "Ignored" Face Tag so there appears to be
no way to remove it.
I have a number of photos where I now know the identity of the person and want
to remove the "Ignored" tag and replace with the correct identity Face Tag.

STEPS TO REPRODUCE
1. Tag a Face as "Ignored"
2. Right click on Photo and select "Remove Tag".

OBSERVED RESULT
"Ignored" tag is not listed.

EXPECTED RESULT
"Ignored" Tag listed with other Face tags

SOFTWARE/OS VERSIONS
Windows: 10

KDE Plasma Version: 
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Appologies I posted this as Bug 472174 but used the term "Unknown" instead of
"Ignored" for the Face tag identity. Maik Qualmann responded and closed that
correctly as I had misled you. 
Have now loaded the latest 8.1.0 and rechecked the issue as well as checking
the documentation at https://docs.digikam.org/en/main_window/people_view.html
but I believe the issue above still stands that you cannot remove an "Ignored"
tag, except possibly using "Remove All Tags" and then having to redo all the
tags on that photo.
Thanks, Richard

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

[krita] [Bug 472248] Jagged edges when rotating objects

2023-07-14 Thread Daniel
https://bugs.kde.org/show_bug.cgi?id=472248

--- Comment #4 from Daniel  ---
Ok, thank you!

Bug Janitor Service  schrieb am Sa., 15. Juli
2023, 05:45:

> https://bugs.kde.org/show_bug.cgi?id=472248
>
> Bug Janitor Service  changed:
>
>What|Removed |Added
>
> 
>  Resolution|WAITINGFORINFO  |---
>  Status|NEEDSINFO   |REPORTED
>
> --- Comment #3 from Bug Janitor Service  ---
> Thanks for your comment!
>
> Automatically switching the status of this bug to REPORTED so that the KDE
> team
> knows that the bug is ready to get confirmed.
>
> In the future you may also do this yourself when providing needed
> information.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[kmail2] [Bug 472268] Kmail crashed attempting to search "Find Action"

2023-07-14 Thread idoitprone
https://bugs.kde.org/show_bug.cgi?id=472268

--- Comment #2 from idoitprone  ---
```
   kc = { = { = { = {_vptr.QObject =
0x7fffec96e928 , static staticMetaObject = {d =
{superdata = {direct = 0x0}, stringdata = 0x7fffeeebc100
, data = 0x7fffeeebbfe0 ,
static_metacall = 0x7fffeed237e0 , relatedMetaObjects = 0x0, extradata = 0x0}},
d_ptr = {d = 0x56891bf0}, static staticQtMetaObject = {d = {superdata =
{direct = 0x0}, stringdata = 0x7fffeeebf0a0 , data =
0x7fffeeebc220 , static_metacall = 0x0, relatedMetaObjects =
0x0, extradata = 0x0}}},  = {_vptr.QPaintDevice = 0x7fffec96ead8
, painters = 0, reserved = 0x0}, static
staticMetaObject = {d = {superdata = {direct = 0x7fffeefbe840
}, stringdata = 0x7fffefd5aa20
, data = 0x7fffefd5a340 ,
static_metacall = 0x7fffef9e5530 , relatedMetaObjects = 0x0, extradata = 0x0}},
data = 0x56891d10}, static staticMetaObject = {d = {superdata = {direct =
0x7fffefebc2c0 }, stringdata = 0x7fffefd7f120
, data = 0x7fffefd7efc0 ,
static_metacall = 0x7fffefb31410 , relatedMetaObjects = 0x0, extradata = 0x0}}},
static staticMetaObject = {d = {superdata = {direct = 0x7fffefec7be0
}, stringdata = 0x7fffec9598e0
, data = 0x7fffec9588e0
, static_metacall = 0x7fffec933c60
,
relatedMetaObjects = 0x0, extradata = 0x0}}, d =
std::unique_ptr = {get() = 0x56b46ac0}}
actionCollections = std::vector of length 3, capacity 4 =
{0x55c2f6c0, 0x5607b740, 0x5607b740}
clients = {> = {},
{p = {static shared_null = {ref = {atomic = {_q_value = std::atomic = { -1
}}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x5609df50}, d =
0x5609df50}}
this = 
#46 QtPrivate::FunctorCall, QtPrivate::List<>, void,
KXmlGuiWindow::KXmlGuiWindow(QWidget*, Qt::WindowFlags):: >::call
(arg=, f=)
at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#47 QtPrivate::Functor, 0>::call, void> (arg=, f=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#48 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *)
(which=, this_=, r=,
a=, ret=) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#49 0x7fffeed257a2 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fffc1f0, r=0x55caf5f0, this=0x55c32b60) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
receiver = 0x55caf5f0
td = 
senderData = {previous = 0x0, receiver = 0x55caf5f0, sender =
0x55c32050, signal = 4}
c = 0x55aa3760
connections = {d = 0x55aa37c0}
list = 
inSenderThread = 
highestConnectionId = 5
signalVector = 
currentThreadId = 0x7fffe2c4d040
sp = 
signal_spy_set = 0x0
empty_argv = {0x0}
senderDeleted = false
#50 doActivate(QObject*, int, void**) (sender=0x55c32050,
signal_index=4, argv=0x7fffc1f0) at kernel/qobject.cpp:3925
receiver = 0x55caf5f0
td = 
senderData = {previous = 0x0, receiver = 0x55caf5f0, sender =
0x55c32050, signal = 4}
c = 0x55aa3760
connections = {d = 0x55aa37c0}
list = 
inSenderThread = 
highestConnectionId = 5
signalVector = 
currentThreadId = 0x7fffe2c4d040
sp = 
signal_spy_set = 0x0
empty_argv = {0x0}
senderDeleted = false
#51 0x7fffeed1e40f in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**)
(sender=sender@entry=0x55c32050, m=m@entry=0x7fffefebacc0
, local_signal_index=local_signal_index@entry=1,
argv=argv@entry=0x7fffc1f0) at kernel/qobject.cpp:3985
#52 0x7fffef99e8b2 in QAction::triggered(bool)
(this=this@entry=0x55c32050, _t1=) at
.moc/moc_qaction.cpp:376
_a = {0x0, 0x7fffc1ec}
#53 0x7fffef9a142f in QAction::activate(QAction::ActionEvent)
(this=0x55c32050, event=) at kernel/qaction.cpp:1161
d = 0x55a63820
#54 0x7fffefb25ef2 in
QMenuPrivate::activateCausedStack(QVector > const&, QAction*,
QAction::ActionEvent, bool)
(this=this@entry=0x56086790, causedStack=...,
action=action@entry=0x55c32050, action_e=action_e@entry=QAction::Trigger,
self=self@entry=true) at widgets/qmenu.cpp:1384
--Type  for more, q to quit, c to continue without paging--
guard = {block = @0x56086ad0, reset = false}
#55 0x7fffefb2dd23 in QMenuPrivate::activateAction(QAction*,
QAction::ActionEvent, bool) (this=0x56086790, action=0x55c32050,
action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1461
q = 0x56096220
inWhatsThisMode = false
causedStack = {d = 0x56ac6920}
#56 0x7fffef9e6d68 in QWidget::event(QEvent*) (this=0x56096220,
event=0x7fffc7e0) at kernel/qwidget.cpp:9045
d = 
#57 0x7fffef9a519e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0x555c3210, receiver=receiver@entry=0x56096220,
e=e@entry=0x7fffc7e0) at 

[kmail2] [Bug 472268] Kmail crashed attempting to search "Find Action"

2023-07-14 Thread idoitprone
https://bugs.kde.org/show_bug.cgi?id=472268

--- Comment #1 from idoitprone  ---
I attempted to run kmail in gdb


```

Thread 1 "kmail" received signal SIGSEGV, Segmentation fault.
QString::QString (other=..., this=0x7fffb200) at
../../include/QtCore/../../src/corelib/text/qstring.h:1094
1094{ Q_ASSERT( != this); d->ref.ref(); } 
Missing separate debuginfos, use: zypper install
librist4-debuginfo-0.2.7-1699.1.pm.10.x86_64
libxvidcore4-debuginfo-1.3.7-1699.1.pm.56.x86_64
(gdb) bt full
#0  QString::QString(QString const&) (other=..., this=0x7fffb200) at
../../include/QtCore/../../src/corelib/text/qstring.h:1094
d = 0x56be84e0
s = {d = 0x0}
#1  QAction::text() const (this=) at kernel/qaction.cpp:725
d = 0x56be84e0
s = {d = 0x0}
#2  0x7fffec938dd9 in KCommandBarModel::Item::displayName() const
(this=this@entry=0x56bcdd80) at
/usr/src/debug/kconfigwidgets-5.108.0/src/kcommandbarmodel_p.cpp:19
group = {d = 0x55f88010}
command = {d = 0x1e}
#3  0x7fffec93ad30 in KCommandBarModel::data(QModelIndex const&, int) const
(this=, index=, role=) at
/usr/src/debug/kconfigwidgets-5.108.0/src/kcommandbarmodel_p.cpp:126
entry = @0x56bcdd80: {groupName = {d = 0x55f88010}, action =
0x56b5d280, score = -1}
col = 
#4  0x7fffec93973c in QModelIndex::data(int) const (arole=0,
this=0x7fffb2b0) at /usr/include/qt5/QtCore/qabstractitemmodel.h:460
row = {d = 0x56bf8f50}
pos = 
index = {r = 177, c = 0, i = 0, m = 0x56b46b20}
accept = false
#5  CommandBarFilterModel::filterAcceptsRow(int, QModelIndex const&) const
(this=0x56b46b48, sourceRow=177, sourceParent=...) at
/usr/src/debug/kconfigwidgets-5.108.0/src/kcommandbar.cpp:82
row = {d = 0x56bf8f50}
pos = 
index = {r = 177, c = 0, i = 0, m = 0x56b46b20}
accept = false
#6  0x7fffeecbae96 in
QSortFilterProxyModelPrivate::create_mapping(QModelIndex const&) const
(this=this@entry=0x5600cde0, source_parent=...) at
itemmodels/qsortfilterproxymodel.cpp:506
i = 177
q = 
it = {i = }
m = 0x56be27e0
source_rows = 272
source_cols = 
#7  0x7fffeecbf60b in QSortFilterProxyModel::columnCount(QModelIndex
const&) const (this=, parent=...) at
itemmodels/qsortfilterproxymodel.cpp:2262
d = 0x5600cde0
source_parent = {r = -1, c = -1, i = 0, m = 0x0}
#8  0x7fffefc2bb7b in QHeaderViewPrivate::modelSectionCount() const
(this=0x5600ae60) at
../../include/QtWidgets/5.15.10/QtWidgets/private/../../../../../src/widgets/itemviews/qheaderview_p.h:236
d = 0x5600ae60
oldCount = 2
newCount = 

#9  QHeaderView::initializeSections() (this=0x56022840) at
itemviews/qheaderview.cpp:2249
d = 0x5600ae60
oldCount = 2
newCount = 
#10 0x7fffefc3094a in QHeaderView::reset() (this=0x56022840) at
itemviews/qheaderview.cpp:1794
d = 0x5600ae60
#11 0x7fffeed25743 in doActivate(QObject*, int, void**)
(sender=0x56b46b48, signal_index=21, argv=0x7fffb520) at
kernel/qobject.cpp:3937
method_relative = 
callFunction = 
methodIndex = 0
receiver = 0x56022840
td = 
senderData = {previous = 0x0, receiver = 0x56022840, sender =
0x56b46b48, signal = 21}
c = 0x56bc98c0
connections = {d = 0x5600c660}
list = 
inSenderThread = 
highestConnectionId = 65
signalVector = 
currentThreadId = 0x7fffe2c4d040
--Type  for more, q to quit, c to continue without paging--
sp = 
signal_spy_set = 0x0
empty_argv = {0x0}
senderDeleted = false
#12 0x7fffeed1e40f in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**)
(sender=, m=m@entry=0x7fffeefc5d40
,
local_signal_index=local_signal_index@entry=18, argv=argv@entry=0x7fffb520)
at kernel/qobject.cpp:3985
#13 0x7fffeec8678d in
QAbstractItemModel::modelReset(QAbstractItemModel::QPrivateSignal)
(this=, _t1=...) at .moc/moc_qabstractitemmodel.cpp:648
_a = {0x0, 0x7fffb51f}
#14 0x7fffeed257a2 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fffb620, r=0x56b46b48, this=0x5600d6e0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
receiver = 0x56b46b48
td = 
senderData = {previous = 0x0, receiver = 0x56b46b48, sender =
0x56b46af0, signal = 7}
c = 0x5600db20
connections = {d = 0x5600c4f0}
list = 
inSenderThread = 
highestConnectionId = 7
signalVector = 
currentThreadId = 0x7fffe2c4d040
sp = 
signal_spy_set = 0x0
empty_argv = {0x0}
senderDeleted = false
#15 doActivate(QObject*, int, void**) (sender=0x56b46af0,
signal_index=7, 

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[kmail2] [Bug 472268] Kmail crashed attempting to search "Find Action"

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=472268

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[plasma-mobile] [Bug 462530] Plasma mobile lockscreen does not have an alphanumeric virtual keyboard fallback

2023-07-14 Thread idoitprone
https://bugs.kde.org/show_bug.cgi?id=462530

--- Comment #7 from idoitprone  ---
(In reply to Devin Lin from comment #6)
> Have you been able to trigger the virtual keyboard at all? Like from within
> the shell. 
> 
> I wonder if KWin is disabling the virtual keyboard because it detects a
> hardware one.

Not once. I never was able to trigger it.

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

[kmail2] [Bug 472268] New: Kmail crashed attempting to search "Find Action"

2023-07-14 Thread idoitprone
https://bugs.kde.org/show_bug.cgi?id=472268

Bug ID: 472268
   Summary: Kmail crashed attempting to search "Find Action"
Classification: Applications
   Product: kmail2
   Version: 5.23.3
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Keywords: reproducible
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: monkeyboy...@yahoo.com
  Target Milestone: ---

Created attachment 160297
  --> https://bugs.kde.org/attachment.cgi?id=160297=edit
dr konqi crash log

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. Click Help
2. Click Find Action 
3. Type a char - Tested "k" and "l" 


OBSERVED RESULT
Kmail crashes and DrKonqi starts up.

EXPECTED RESULT
I do not know. I never used this feature before.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma:  openSUSE Tumbleweed 20230713 (x86_64)
(available in About System)
KDE Plasma Version: 5.27.6
KDE Frameworks Version:  5.108.0
Qt Version: 5.15.10
Application Verison: 5.23.3 (23.04.3)

zypper info kmail
Repository 'packman' is out-of-date. You can run 'zypper refresh' as root to
update it.
Loading repository data...
Reading installed packages...


Information for package kmail:
--
Repository : openSUSE-Tumbleweed-Oss
Name   : kmail
Version: 23.04.3-1.1
Arch   : x86_64
Vendor : openSUSE
Installed Size : 6.9 MiB
Installed  : Yes
Status : up-to-date
Source package : kmail-23.04.3-1.1.src
Upstream URL   : https://apps.kde.org/kmail2
Summary: Mail Client
Description: 
KMail is the KDE mail client.


ADDITIONAL INFORMATION

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[digikam] [Bug 472266] digikam face recognition ignores imported face tag data

2023-07-14 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=472266

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
When importing images with face regions, no face matrices are created for face
recognition, for performance reasons.
In this case you need to use the Maintenance tool (Extra menu) and in the face
detection section do the option "Clear training data and rebuild". Based on the
confirmed faces in the database, new face matrices are created for all.

Maik

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

[digikam] [Bug 472266] digikam face recognition ignores imported face tag data

2023-07-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=472266

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com
   Platform|Other   |Microsoft Windows

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

[kde] [Bug 472267] after last update scanner no more detected

2023-07-14 Thread Duns
https://bugs.kde.org/show_bug.cgi?id=472267

Duns  changed:

   What|Removed |Added

 CC||w...@culturanuova.net

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

[kde] [Bug 472267] New: after last update scanner no more detected

2023-07-14 Thread Duns
https://bugs.kde.org/show_bug.cgi?id=472267

Bug ID: 472267
   Summary: after last update scanner no more detected
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: w...@culturanuova.net
  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. turn on your HP scanner
2. open xsane

OBSERVED RESULT

No scanner device detected

EXPECTED RESULT

Scanner detected

SOFTWARE/OS VERSIONS

Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Kernel Version: 5.19.0-46-generic (64-bit)
Graphics Platform: X11
Processors: 2 × Intel® Core™ i3-7100 CPU @ 3.90GHz
Memory: 7,6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 630
Manufacturer: MSI
Product Name: MS-7A74
System Version: 1.0

ADDITIONAL INFORMATION

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

[krita] [Bug 472248] Jagged edges when rotating objects

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=472248

Bug Janitor Service  changed:

   What|Removed |Added

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

--- Comment #3 from Bug Janitor Service  ---
Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.

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

[krita] [Bug 472167] Animation play glitch !

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=472167

Bug Janitor Service  changed:

   What|Removed |Added

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

--- Comment #6 from Bug Janitor Service  ---
Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[kwalletmanager] [Bug 263174] Fingerprint support for kwallet

2023-07-14 Thread Hai Zaar
https://bugs.kde.org/show_bug.cgi?id=263174

Hai Zaar  changed:

   What|Removed |Added

 CC||haiz...@gmail.com

--- Comment #8 from Hai Zaar  ---
Are there any plans to work on it? 
If a developer lacks a fingerprint device I'll happy happy to ship them one.

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

[systemsettings] [Bug 472215] Add separate settings for Tap-and-drag left click and Tap-and-drag right click in Touchpad settings

2023-07-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=472215

kazk...@gmail.com changed:

   What|Removed |Added

 CC||kazk...@gmail.com

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

[krita] [Bug 469645] Krita keeps crashing on a specific piece of artwork

2023-07-14 Thread vanyossi
https://bugs.kde.org/show_bug.cgi?id=469645

vanyossi  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||ghe...@gmail.com
 Status|CONFIRMED   |NEEDSINFO

--- Comment #9 from vanyossi  ---
Please provide a detail step by step on how to reproduce the bug

What do you mean by "change it back to a kra file" after saving as png?, when I
"Save as..." "png" I do not have to "revert back" to a kra as the image was
never converted to a png, only a copy saved to that format. Without detail
steps or a screen record we cannot know the exact steps you are following to
make the bug appear.

Also please do not modify the bug status, that is for developers to determine

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[kdeconnect] [Bug 466617] kdeconnectd crashes when attempting to pair a device while playing MPRIS music without album art

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=466617

Bug Janitor Service  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|ASSIGNED

--- Comment #2 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/562

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

[kdeconnect] [Bug 466617] kdeconnectd crashes when attempting to pair a device while playing MPRIS music without album art

2023-07-14 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=466617

--- Comment #1 from Fushan Wen  ---
Created attachment 160296
  --> https://bugs.kde.org/attachment.cgi?id=160296=edit
New crash information added by DrKonqi

kdeconnectd (23.07.70) using Qt 5.15.10

When the current song changes, kdeconnect crashed.

-- Backtrace (Reduced):
#6  QString::QString(QString const&) (other=, this=this@entry=0x7ffd9d5d4f08) at
/usr/include/qt5/QtCore/qstring.h:1093
#7  Device::name() const (this=0x0) at
/mnt/data/home/qydw/Develop/KDE/Network/kdeconnect-kde/core/device.cpp:119
#8  0x7f4c9a00b12b in CompositeUploadJob::emitDescription(QString const&)
(this=this@entry=0x2092860, currentFileName=...) at
/mnt/data/home/qydw/Develop/KDE/Network/kdeconnect-kde/core/backends/lan/compositeuploadjob.cpp:287
#9  0x7f4c9a00bafc in CompositeUploadJob::startNextSubJob()
(this=0x2092860) at
/mnt/data/home/qydw/Develop/KDE/Network/kdeconnect-kde/core/backends/lan/compositeuploadjob.cpp:96
#10 0x7f4c981192b0 in QObject::event(QEvent*) (this=0x2092860,
e=0x7f4c8c057370) at kernel/qobject.cpp:1347

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

[kdeconnect] [Bug 466617] kdeconnectd crashes when attempting to pair a device while playing MPRIS music without album art

2023-07-14 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=466617

Fushan Wen  changed:

   What|Removed |Added

 CC||qydwhotm...@gmail.com

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

[krita] [Bug 469645] Krita keeps crashing on a specific piece of artwork

2023-07-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=469645

djdarius...@gmail.com changed:

   What|Removed |Added

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

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[digikam] [Bug 472266] New: digikam face recognition ignores imported face tag data

2023-07-14 Thread Justin
https://bugs.kde.org/show_bug.cgi?id=472266

Bug ID: 472266
   Summary: digikam face recognition ignores imported face tag
data
Classification: Applications
   Product: digikam
   Version: 8.1.0
  Platform: Other
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Faces-Recognition
  Assignee: digikam-bugs-n...@kde.org
  Reporter: jr.frees...@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.  Add new collection of images that have face data stored in xmp metadata.
xmp metadata was created by another program.
2.  digiKam recognizes xmp face data and creates people tags
3.  Under People -> WorkflowRun "Detect faces" followed by "Recognize
faces"

OBSERVED RESULT
digiKam does detect new faces that the former program missed or from fresh
images without face metadata. digiKam correctly does not duplicate any faces
detected by previous program and stored in xmp. digiKam displays newly detected
faces in the "Unknown" category. No newly detected faces are in the
"Unconfirmed" category. If I assign a People tag to a few of the same newly
detected faces, then digiKam will start making recommendations to the
"Unconfirmed" category. BUT, recommendations are only made for People tags
assigned inside digiKam and have an accuracy of less than 10%. Recommendations
are not made for any Person tag that was created when an image with xmp face
metadata. It appears that digiKam isn't able to correctly utilize faces tagged
by another program when performing the "Recognize faces" procedure. To confirm
this suspicion, I found a person who had never been tagged before. I assigned a
name to this person on ~10 faces. digiKam started making recommendations to the
"Unconfirmed" category for this person with better than 95% accuracy.

EXPECTED RESULT
I just reread the documentation about face recognition and saw the Note: "Face
recognition only works well with faces that have been automatically detected by
digiKam, not with manually drawn face rectangles or faces from other programs."
Based on this I'm guessing that face recognition is dependent upon the bounding
box and each method defines the bounding box uniquely. I don't recall ever
seeing an option to ignore face metadata when adding a new collection. What is
the proper way use face recognition in digikam with images tagged by other
programs? It would be helpful if the documentation contained a workaround in
addition to the cited note. Is there a simple way to delete existing face tag
data from a files xmp metadata and then redo the database?

Does the same problem exist if originally a person used the regular "Detect
faces" method and then after more images have been added to the collection, the
person enabled the "Use Yolo v3 detection model" option for face detection?

SOFTWARE/OS VERSIONS
Windows: 11 ver. 2009
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.

[frameworks-syntax-highlighting] [Bug 468394] r.xml syntax highlighting definitions miss specified integers (e.g., 3L)

2023-07-14 Thread Jonathan Poelen
https://bugs.kde.org/show_bug.cgi?id=468394

--- Comment #2 from Jonathan Poelen  ---
Created attachment 160295
  --> https://bugs.kde.org/attachment.cgi?id=160295=edit
current rendering and potential new rendering

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

[frameworks-syntax-highlighting] [Bug 468394] r.xml syntax highlighting definitions miss specified integers (e.g., 3L)

2023-07-14 Thread Jonathan Poelen
https://bugs.kde.org/show_bug.cgi?id=468394

Jonathan Poelen  changed:

   What|Removed |Added

 CC||jonathan.poe...@gmail.com

--- Comment #1 from Jonathan Poelen  ---
I tried with https://pandoc.org/try/ and the following code

```r
111
111L
111i
```

The last 2 lines are not in color. Except that this is not the behavior of
KSyntaxHighlighting, for which only L and i are in Normal.

As the syntax version is also 13, I have the impression that this is on the
side of skylighting (https://github.com/jgm/skylighting/), the library used by
pandoc. This library contains a tool for converting to html or displaying in
color on the console (ansi), so I think there will be the same problem as with
pandoc. But for the moment I can't confirm this, as I don't have haskell or
skylighting and can't install anything on my machine :/.

On the other hand, I'm thinking that only the suffix could be in a different
color, something like in the attached image (on the left the current behavior,
on the right what could be the new one).

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

[clazy] [Bug 472265] New: Evaluate Profile-Guided Optimization (PGO) on Clazy

2023-07-14 Thread Alexander Zaitsev
https://bugs.kde.org/show_bug.cgi?id=472265

Bug ID: 472265
   Summary: Evaluate Profile-Guided Optimization (PGO) on Clazy
Classification: Developer tools
   Product: clazy
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: zamazan...@tut.by
CC: smart...@kde.org
  Target Milestone: ---

Hi!

Recently I checked Profile-Guided Optimization (PGO) optimization on many kind
of software - the results are available here:
https://github.com/zamazan4ik/awesome-pgo/

One of the related to Clazy project result is optimizing LLVM-based projects:
https://github.com/llvm/llvm-project/issues/63486

I think the same approach should be applicable to Clazy as well since
Clang-based tooling like Clang, Clangd, Clang Tidy is improved by PGO according
to my tests. Would be great to see PGO-optimized Clazy in reality. Maybe some
kind of build option with PGO will be a good starting point.

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[plasmashell] [Bug 466193] Plasmashell sometimes tries to load before kactivitymanagerd has finished loading, and fails

2023-07-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=466193

--- Comment #17 from guimarcalsi...@gmail.com ---
Created attachment 160294
  --> https://bugs.kde.org/attachment.cgi?id=160294=edit
Known good boot

Known good boot - Shows the same message

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

[plasmashell] [Bug 466193] Plasmashell sometimes tries to load before kactivitymanagerd has finished loading, and fails

2023-07-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=466193

--- Comment #16 from guimarcalsi...@gmail.com ---
Created attachment 160293
  --> https://bugs.kde.org/attachment.cgi?id=160293=edit
Log when shell failed to load

PS: I deleted the last few lines where I switched TTYs and tried to kill
plasmashell with killall since that's probably not useful.

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

[plasmashell] [Bug 466193] Plasmashell sometimes tries to load before kactivitymanagerd has finished loading, and fails

2023-07-14 Thread Simon Vogl
https://bugs.kde.org/show_bug.cgi?id=466193

--- Comment #15 from Simon Vogl  ---
(In reply to guimarcalsilva from comment #14)
> I noticed BUG 466918 was marked as a duplicate of this, which is very
> similar to what's happening to me, however there they said it happens
> consistently, while in my case it happens intermittently. This week Plasma
> (5.27.6) failed to load twice after starting up the computer (I see the
> wallpaper and the mouse cursor, but the shell never loads). Restarting the
> computer fixes the issue and it happens seemingly randomly. I noticed my
> logs show the same message "Aborting shell load: The activity manager daemon
> (kactivitymanagerd) is not running.", however, I checked 3 other successful
> boots and they also show the same message twice, even though the shell loads
> succefully. I also don't have any problems with the panel disappearing.
> 
> I also tested my Plasma 6 VM and it shows the same message as well after a
> successful boot.
> 
> Can someone confirm the same message also appears after a successful boot?
> Maybe the issue is something else entirely.

I can confirm this, 100% identical behaviour on my system. Also appears after a
successful boot, and only very occasionally the shell actually fails to load.

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

[plasmashell] [Bug 466193] Plasmashell sometimes tries to load before kactivitymanagerd has finished loading, and fails

2023-07-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=466193

--- Comment #14 from guimarcalsi...@gmail.com ---
I noticed BUG 466918 was marked as a duplicate of this, which is very similar
to what's happening to me, however there they said it happens consistently,
while in my case it happens intermittently. This week Plasma (5.27.6) failed to
load twice after starting up the computer (I see the wallpaper and the mouse
cursor, but the shell never loads). Restarting the computer fixes the issue and
it happens seemingly randomly. I noticed my logs show the same message
"Aborting shell load: The activity manager daemon (kactivitymanagerd) is not
running.", however, I checked 3 other successful boots and they also show the
same message twice, even though the shell loads succefully. I also don't have
any problems with the panel disappearing.

I also tested my Plasma 6 VM and it shows the same message as well after a
successful boot.

Can someone confirm the same message also appears after a successful boot?
Maybe the issue is something else entirely.

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[kdeconnect] [Bug 472264] New: Inconsistency in README

2023-07-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=472264

Bug ID: 472264
   Summary: Inconsistency in README
Classification: Applications
   Product: kdeconnect
   Version: unspecified
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: windows-application
  Assignee: piyushaggarwal...@gmail.com
  Reporter: porretta.dan...@libero.it
  Target Milestone: ---

SUMMARY

In the README, there is written:

- in "How to install":

> Platforms other than Linux are not officially supported, as there has yet to 
> be an official release of KDE Connect for MacOS or Windows.

- in "Supported platforms":

> Computers running Windows, by installing from the Microsoft Store


OBSERVED RESULT

It is not clear if there is or there is not an official release of KDE Connect
for Windows.


EXPECTED RESULT

Have a clear statement in the README whether or not there is an official
release of KDE Connect for Windows.

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

[kwin] [Bug 472233] Debian-KDE, I get a black screen when my computer goes to sleep, and I can't wake it up.

2023-07-14 Thread Mathew A Coulliette
https://bugs.kde.org/show_bug.cgi?id=472233

--- Comment #7 from Mathew A Coulliette  
---
Created attachment 160292
  --> https://bugs.kde.org/attachment.cgi?id=160292=edit
VMware WorkStation Pro 17 version #s & info.

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

[kwin] [Bug 472233] Debian-KDE, I get a black screen when my computer goes to sleep, and I can't wake it up.

2023-07-14 Thread Mathew A Coulliette
https://bugs.kde.org/show_bug.cgi?id=472233

--- Comment #6 from Mathew A Coulliette  
---
I just want to declare something.  I use VMware Workstation 17 Pro to run
GNU/Linux.  I didn't declare this right away because I don't think that it is
the issue.  I have used VMware for years and never had a problem.  If you
understand how it works the OS doesn't know that it is in a Virtual Machine; it
thinks that it is running on actual hardware.  The Virtual Machine is very
complete; it even has BIOS!

VMware Workstation Pro Version Number:   17.0.2 build-21581411.

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

[dolphin] [Bug 463136] Copying files by dragging them doesn't work. Also dragging files to folders sometimes makes the whole editor freeze for some time.

2023-07-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=463136

ch...@jsr2a03.com changed:

   What|Removed |Added

 CC||ch...@jsr2a03.com

--- Comment #9 from ch...@jsr2a03.com ---
I saw this on gentoo after upgrading from 22.12.3 to 23.04.2.  Loading the fuse
module does indeed seem to fix it.  It seems this is required now, but I can't
really see a reason why.  In the past, I only would load fuse when I need to
use appimages.  I don't use snaps, flatpacks, etc.

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

[valgrind] [Bug 472263] New: iselVecExpr (amd64, subarch = amd64-cx16-lzcnt-rdtscp-sse3): can't reduce PermOrZero8x16(...)

2023-07-14 Thread Aaron Ucko
https://bugs.kde.org/show_bug.cgi?id=472263

Bug ID: 472263
   Summary: iselVecExpr (amd64, subarch =
amd64-cx16-lzcnt-rdtscp-sse3): can't reduce
PermOrZero8x16(...)
Classification: Developer tools
   Product: valgrind
   Version: 3.21.0
  Platform: RedHat Enterprise Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: vex
  Assignee: jsew...@acm.org
  Reporter: u...@ncbi.nlm.nih.gov
  Target Milestone: ---

Created attachment 160291
  --> https://bugs.kde.org/attachment.cgi?id=160291=edit
host and client stacktraces

SUMMARY
Valgrind can abort with errors along the lines of

iselVecExpr (amd64, subarch = amd64-cx16-lzcnt-rdtscp-sse3): can't reduce
PermOrZero8x16(t291,t102)
vex: the `impossible' happened:
   iselVecExpr_wrk
vex storage: T total 1856835088 bytes allocated
vex storage: P total 512 bytes allocated

(Full log tail attached.)

valgrind: the 'impossible' happened:
   LibVEX called failure_exit().


STEPS TO REPRODUCE (not so minimal, sorry; additionally requires Boost.Test
headers)
1. git clone https://github.com/ncbi/ncbi-vdb
2. cd ncbi_vdb
3. git checkout 3.0.6
4. mkdir Release
5. cd Release
6. cmake -DCMAKE_BUILD_TYPE=Release ..
7. make -s -j5
8. ln -s ../interfaces .
9. mkdir -p linux/x86_64/release
10. ln -s lib linux/x86_64/release/
11. cd ../..
12. git clone https://github.com/ncbi/ncbi-cxx-toolkit-public
13. cd ncbi-cxx-toolkit-public
14. ./cmake-configure --without-debug --with-dll
-DNCBI_ThirdParty_VDB=${PWD%/*}/ncbi-vdb/Release
15. cd CMake-*/build
16. make -s -j5 test_wgs_loader
17. valgrind --tool=memcheck
--suppressions=../../scripts/common/check/valgrind.supp ../bin/test_wgs_loader
--run_test=TestReplacedProtein1

OBSERVED RESULT

Valgrind terminates with the above report and the attached stack trace.

EXPECTED RESULT

Valgrind proceeds to completion.

SOFTWARE/OS VERSIONS
At minimum, Valgrind 3.20.0, 3.21.0, and revision cb684b50e.

ADDITIONAL INFORMATION
I built and tested everything on a CentOS 7 system using a third-party GCC
7.3.0 installation.   FWIW, the problem is new as of ncbi-vdb 3.0.6, even
though it occurs with no active VDB calls.

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[frameworks-syntax-highlighting] [Bug 426377] code folding with "null record" in Ada folds the rest of the file completely

2023-07-14 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=426377

Christoph Cullmann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/fram
   ||eworks/syntax-highlighting/
   ||-/commit/a22703c25934b7d1ff
   ||30e6b1dde47d94d1e2e19e
 Status|ASSIGNED|RESOLVED

--- Comment #7 from Christoph Cullmann  ---
Git commit a22703c25934b7d1ff30e6b1dde47d94d1e2e19e by Christoph Cullmann, on
behalf of Jonathan Poelen.
Committed on 14/07/2023 at 21:31.
Pushed by cullmann into branch 'master'.

ADA: fix folding on "null record" ; add digit separator, based numeral and
keywords

- fix folding on `null record`

```ada
type Car is record -- beginRegion=RecordRegion
  -- .
end record -- endRegion=RecordRegion
type Null_Record is null record;
-- Before~~ beginRegion=RecordRegion
-- After ~~ no region
```

- new highlight: Base, Exponent

```ada
   3#011201#e3
-- ^ Base
--   ^ Decimal
-- ^ Base
--  ^ Exponent

   3#0112401#e3
-- ^ Base
--   ^ Decimal
--   ^ Normal Text (4 is not valid in base 3)
```

A  +164  -0autotests/folding/test.adb.fold
A  +171  -0autotests/html/test.adb.dark.html
A  +171  -0autotests/html/test.adb.html
A  +164  -0autotests/input/test.adb
A  +164  -0autotests/reference/test.adb.ref
M  +167  -24   data/syntax/ada.xml

https://invent.kde.org/frameworks/syntax-highlighting/-/commit/a22703c25934b7d1ff30e6b1dde47d94d1e2e19e

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

[systemsettings] [Bug 471431] kded5 crash on system update

2023-07-14 Thread petrk
https://bugs.kde.org/show_bug.cgi?id=471431

--- Comment #2 from petrk  ---
After such crash there is a chance for my keymap to get reset to US. Special
characters are not working properly It can't be a coincidence and it's not
first time it happened. Here's output from localectl:
System Locale: LANG=pl_PL.UTF-8
VC Keymap: uk
   X11 Layout: gb
X11 Model: pl

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[digikam] [Bug 472253] Thumbnails of TIFF files show as low resolution with visible colour bands.

2023-07-14 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=472253

--- Comment #5 from Maik Qualmann  ---
A preview of digiKam-8.2.0 will be available here soon which will include the
change.

https://files.kde.org/digikam/

The date in the file name, it must be greater than 07/14/2023.

Maik

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

[digikam] [Bug 472253] Thumbnails of TIFF files show as low resolution with visible colour bands.

2023-07-14 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=472253

Maik Qualmann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/grap
   ||hics/digikam/-/commit/b4507
   ||1d7f6c763c4a987754d594afd09
   ||7447a057
 Status|REPORTED|RESOLVED
   Version Fixed In||8.2.0

--- Comment #4 from Maik Qualmann  ---
Git commit b45071d7f6c763c4a987754d594afd097447a057 by Maik Qualmann.
Committed on 14/07/2023 at 20:09.
Pushed by mqualmann into branch 'master'.

use default value again for compression of TIFF preview
QImage compression setting seems to differ between
Linux and Windows or different Qt versions.
FIXED-IN: 8.2.0

M  +9-1NEWS
M  +1-1core/libs/metadataengine/engine/metaengine_item.cpp

https://invent.kde.org/graphics/digikam/-/commit/b45071d7f6c763c4a987754d594afd097447a057

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

[digikam] [Bug 472253] Thumbnails of TIFF files show as low resolution with visible colour bands.

2023-07-14 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=472253

Maik Qualmann  changed:

   What|Removed |Added

Summary|Thumbnails of TIFF files|Thumbnails of TIFF files
   |show as low resolution with |show as low resolution with
   |visible colour bands.  Raw  |visible colour bands.
   |files are fine as are   |
   |jpegs.  |

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

[kdenlive] [Bug 472262] New: Rotoscoping and Rotoscoping (MASK) do not allow creating a shape

2023-07-14 Thread Anthony
https://bugs.kde.org/show_bug.cgi?id=472262

Bug ID: 472262
   Summary: Rotoscoping and Rotoscoping (MASK) do not allow
creating a shape
Classification: Applications
   Product: kdenlive
   Version: 23.04.3
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: j...@kdenlive.org
  Reporter: anthony.m.hoffm...@gmail.com
  Target Milestone: ---

When using the Rotoscoping or Rotscoping (MASK) effects the shape cannot be
created. 
***
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
***
The yellow instructions do not appear when in the effects mode. Clicking on the
image to create points acts as clicking the play/pause button. 

STEPS TO REPRODUCE
1. Apply the rotoscoping or rotoscoping (mask) effect to a video, image, title,
or color clip.
2. click on the video, image, title, or color clip to set up the effect.
3. Add a keyframe and click on the image in the image in the video display area
to add points for the rotoscope shape.

OBSERVED RESULT
The video begins to play. Click again the video pauses.

EXPECTED RESULT
A point is added for the rotoscoping shape

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Ubuntu 22.04.2 LTS
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION

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

[digikam] [Bug 472203] UI improvements

2023-07-14 Thread AB
https://bugs.kde.org/show_bug.cgi?id=472203

--- Comment #2 from AB  ---
Ok, I can stop participating and leave things as is, but I'm still asking are
things in this regard the way you want them to be? Of course I understand
limitations of resources.

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

[Ruqola] [Bug 472261] New: Tarball for tagged release 1.9.2 missing form download.kde.org

2023-07-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=472261

Bug ID: 472261
   Summary: Tarball for tagged release 1.9.2 missing form
download.kde.org
Classification: Applications
   Product: Ruqola
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mon...@kde.org
  Reporter: tu...@opensuse.org
  Target Milestone: ---

Version 1.9.2 has been tagged more than a week ago and is listed on
apps.kde.org/ruqola, yet the tarball is still missing from
https://download.kde.org/stable/ruqola/

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

[rkward] [Bug 469926] RKWard doesn't start anymore

2023-07-14 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=469926

Eric  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #4 from Eric  ---
(In reply to Eric from comment #3)
> Created attachment 160290 [details]
> strace output for rkward crash
> 
> This is the strace output for rkward when it crashes at start.

Not sure what happened to the rest of my comment, it disappeared after I added
the attachment.

I'm on Fedora 38. I built version 0.7.5 from the tarball, and also tried
building from git. In both cases it is crashing on startup with an error about
the R backend:

Connection closed unexpectedly. Last error was: QLocalSocket: Remote closed
The R backend will be shut down immediately. This means, you can not use any
more functions that rely on it.

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[rkward] [Bug 469926] RKWard doesn't start anymore

2023-07-14 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=469926

Eric  changed:

   What|Removed |Added

 CC||majzo...@umsl.edu

--- Comment #3 from Eric  ---
Created attachment 160290
  --> https://bugs.kde.org/attachment.cgi?id=160290=edit
strace output for rkward crash

This is the strace output for rkward when it crashes at start.

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

[systemsettings] [Bug 472260] New: There are no settings for changing and turning on/off transparency of taskbar and system menu.

2023-07-14 Thread Igor Mironchik
https://bugs.kde.org/show_bug.cgi?id=472260

Bug ID: 472260
   Summary: There are no settings for changing and turning on/off
transparency of taskbar and system menu.
Classification: Applications
   Product: systemsettings
   Version: 5.27.6
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: igor.mironc...@gmail.com
  Target Milestone: ---

SUMMARY

There are no settings for changing and turning on/off transparency of taskbar
and system menu.


OBSERVED RESULT

There are no settings for changing and turning on/off transparency of taskbar
and system menu.


EXPECTED RESULT

I'd like to see these settings in system settings dialog.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: KDE neon 5.27
(available in About System)
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10

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

[systemsettings] [Bug 471151] Paths are not entirely readable in Locations KCM

2023-07-14 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=471151

--- Comment #12 from Nate Graham  ---
Basically my "limited to a sane value to avoid overflowing the window" from the
first commit turned out to not be so sane after all! Hopefully the new value
should be much saner.

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

[systemsettings] [Bug 471151] Paths are not entirely readable in Locations KCM

2023-07-14 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=471151

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED
  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/plasma-desktop/-/commit/ |ma/plasma-desktop/-/commit/
   |d647242cf5a5884ce00f641d747 |2ead94b4841827348eb14227ca0
   |cec6497bd4d38   |1d4557b420a13

--- Comment #11 from Nate Graham  ---
Git commit 2ead94b4841827348eb14227ca01d4557b420a13 by Nate Graham.
Committed on 14/07/2023 at 18:41.
Pushed by ngraham into branch 'master'.

kcms/desktoppaths: refine text field width calculation

Instead of using a fairly crude upper width limit of half the page
width (which caused long text to get cut off with narrow windows),
make the calculation more real-world by actually seeing how much
horizontal space is available on the page in a varity of conditions:
wide and narrow view, and when the page is scrollable as well as not.

M  +19   -1kcms/desktoppaths/ui/main.qml

https://invent.kde.org/plasma/plasma-desktop/-/commit/2ead94b4841827348eb14227ca01d4557b420a13

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

[systemsettings] [Bug 471151] Paths are not entirely readable in Locations KCM

2023-07-14 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=471151

Nate Graham  changed:

   What|Removed |Added

 Status|REOPENED|ASSIGNED

--- Comment #10 from Nate Graham  ---
Aha, found the bug. It didn't actually have anything to do with the font at
all, but rather the text length relative to the page width.

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[plasmashell] [Bug 468180] Plasmashell crashed in QQuickTransition::prepare() after closing a notification

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=468180

Bug Janitor Service  changed:

   What|Removed |Added

   Priority|NOR |HI

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[krita] [Bug 472257] on brushes that changes opacity because of pressure the feature doesnt work anymore

2023-07-14 Thread Halla Rempt
https://bugs.kde.org/show_bug.cgi?id=472257

Halla Rempt  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 CC||ha...@valdyas.org
 Status|REPORTED|RESOLVED

--- Comment #1 from Halla Rempt  ---
Sorry, but your report is incomprehensible. Also, if you're really using 5.0.6,
please update to the latest version, 5.1.5.

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

[plasmashell] [Bug 470743] Next and Previous buttons of the Media Player applet don't work

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470743

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #9 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3072

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

[plasmashell] [Bug 471449] Mientras manipulaba una ventana con el navegador firefox el ordenador crasheo

2023-07-14 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=471449

Fushan Wen  changed:

   What|Removed |Added

 CC||qydwhotm...@gmail.com
 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #1 from Fushan Wen  ---


*** This bug has been marked as a duplicate of bug 468180 ***

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

[plasmashell] [Bug 468180] Plasmashell crashed in QQuickTransition::prepare() after closing a notification

2023-07-14 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=468180

Fushan Wen  changed:

   What|Removed |Added

 CC||oscarodrigue...@gmail.com

--- Comment #8 from Fushan Wen  ---
*** Bug 471449 has been marked as a duplicate of this bug. ***

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

[kalendar] [Bug 472259] New: The kalendar closed when changing the percentage of a task

2023-07-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=472259

Bug ID: 472259
   Summary: The kalendar closed when changing the percentage of a
task
Classification: Applications
   Product: kalendar
   Version: 22.12.3
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@kde.org
  Reporter: lfelipemo...@proton.me
CC: c...@carlschwan.eu
  Target Milestone: ---

Application: kalendar (22.12.3)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-10-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [KCrashBackend]

-- Information about the crash:
The kalendar closed when changing the percentage of a task synchronized to
nextcloud. 
The task was from last month not completed.

The crash can be reproduced every time.

-- Backtrace:
Application: Kalendar (kalendar), signal: Segmentation fault

[KCrash Handler]
#4  0x7f8626d96bd0 in QDateTime::operator=(QDateTime const&) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x5646b0ca7b56 in ?? ()
#6  0x7f8626ee8f4f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f8626e4bb1c in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f8626e867c5 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f8626ee8f7c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f8626e4bb1c in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f8626e867c5 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f8626ee8f7c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f8626e4bb1c in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f8626e867c5 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f8626ee8f7c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7f8626e4bb1c in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7f86291ed703 in ?? () from
/lib/x86_64-linux-gnu/libKF5ItemModels.so.5
#18 0x7f86291eef76 in ?? () from
/lib/x86_64-linux-gnu/libKF5ItemModels.so.5
#19 0x7f8626ee8f4f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7f8626e4bb1c in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7f862958714d in
Akonadi::EntityTreeModelPrivate::dataChanged(QModelIndex const&, QModelIndex
const&) () from /lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2
#22 0x7f862958fa19 in
Akonadi::EntityTreeModelPrivate::monitoredItemChanged(Akonadi::Item const&,
QSet const&) () from
/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2
#23 0x7f8626ee8f7c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7f86294de497 in Akonadi::Monitor::itemChanged(Akonadi::Item const&,
QSet const&) () from
/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2
#25 0x7f86294ef457 in
Akonadi::MonitorPrivate::emitItemsNotification(Akonadi::Protocol::ItemChangeNotification
const&, QVector const&, Akonadi::Collection const&,
Akonadi::Collection const&) () from
/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2
#26 0x7f86294f03dc in
Akonadi::MonitorPrivate::emitNotification(QSharedPointer
const&) () from /lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2
#27 0x7f86294edb19 in Akonadi::MonitorPrivate::flushPipeline() () from
/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2
#28 0x7f86294edf29 in Akonadi::MonitorPrivate::dataAvailable() () from
/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2
#29 0x7f8626ee8f4f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x7f8626ee8f7c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x7f86287a1775 in KJob::result(KJob*, KJob::QPrivateSignal) () from
/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#32 0x7f86287a2c5b in KJob::finishJob(bool) () from
/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#33 0x7f8626edd6f0 in QObject::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#34 0x7f8627b62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#35 0x7f8626eb16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#36 0x7f8626eb4681 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#37 0x7f8626f0a153 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#38 

[plasmashell] [Bug 468180] Plasmashell crashed in QQuickTransition::prepare() after closing a notification

2023-07-14 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=468180

Fushan Wen  changed:

   What|Removed |Added

 CC||franklindem...@linuxmail.or
   ||g

--- Comment #7 from Fushan Wen  ---
*** Bug 471948 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 471948] Plasmashell crashed after changing from the screen of a WINE-Program to the default Desktop screen

2023-07-14 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=471948

Fushan Wen  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||qydwhotm...@gmail.com
 Status|REPORTED|RESOLVED

--- Comment #1 from Fushan Wen  ---


*** This bug has been marked as a duplicate of bug 468180 ***

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

[plasmashell] [Bug 471209] Taskbar visually frozen, then crashed after taking screenshots

2023-07-14 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=471209

Fushan Wen  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||qydwhotm...@gmail.com
 Status|REPORTED|RESOLVED

--- Comment #2 from Fushan Wen  ---


*** This bug has been marked as a duplicate of bug 468180 ***

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

[plasmashell] [Bug 468180] Plasmashell crashed in QQuickTransition::prepare() after closing a notification

2023-07-14 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=468180

Fushan Wen  changed:

   What|Removed |Added

 CC||ve...@post.com

--- Comment #6 from Fushan Wen  ---
*** Bug 471209 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 472053] KDE Plasma Crash While Watching Video In Browser and Refreshing Desktop

2023-07-14 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=472053

Fushan Wen  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
  Latest Commit||https://invent.kde.org/qt/q
   ||t/qtdeclarative/-/commit/8a
   ||74155411d7a22bb8efa405fe59a
   ||681e47e6b45
 CC||qydwhotm...@gmail.com
 Resolution|--- |UPSTREAM
   Version Fixed In||Qt 6.6

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

[plasmashell] [Bug 472258] System Monitor Sensor doesn't display all GPU info

2023-07-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=472258

linuxquestions6969+...@gmail.com changed:

   What|Removed |Added

 CC||linuxquestions6969+kde@gmai
   ||l.com

--- Comment #1 from linuxquestions6969+...@gmail.com ---
Same problem here. 
nvidia-smi show correct data.

SOFTWARE/OS VERSIONS
OS: openSUSE Tumbleweed 
Kernel: 6.4.2-1-default (64-bit)
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
nvidia driver version: 535.54.03
GPU: nvidia RTX3070

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|crash   |wishlist

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

[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets

2023-07-14 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470114

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|wishlist|crash

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

[plasmashell] [Bug 472246] Plasma randomly crashes and restarts sometimes.

2023-07-14 Thread Mario Ebenhofer
https://bugs.kde.org/show_bug.cgi?id=472246

--- Comment #5 from Mario Ebenhofer  ---
I just read in Bug 414823 that this issue is fixed in QT6... So I can just
ignore it and when Plasma 6 releases (and I install it), that crashes will just
stop happening, right?

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

[plasmashell] [Bug 472246] Plasma randomly crashes and restarts sometimes.

2023-07-14 Thread Mario Ebenhofer
https://bugs.kde.org/show_bug.cgi?id=472246

--- Comment #4 from Mario Ebenhofer  ---
Created attachment 160289
  --> https://bugs.kde.org/attachment.cgi?id=160289=edit
Report of another crash, that happended when I was watching a youtube video in
Google Chrome and moved the mouse near the panel.

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

[plasmashell] [Bug 472246] Plasma randomly crashes and restarts sometimes.

2023-07-14 Thread Mario Ebenhofer
https://bugs.kde.org/show_bug.cgi?id=472246

--- Comment #3 from Mario Ebenhofer  ---
The crash just happened again, and like a few times before, it's saying that
the crash information is not useful. 
It says that some packages are missing, that should be installed...

The packages containing debug information for the following application and
libraries are missing:

/usr/bin/plasmashell
/lib/x86_64-linux-gnu/libQt5Core.so.5
/lib/x86_64-linux-gnu/libQt5Quick.so.5
/lib/x86_64-linux-gnu/libQt5Quick.so.5
/lib/x86_64-linux-gnu/libQt5Quick.so.5
/lib/x86_64-linux-gnu/libQt5Quick.so.5
/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so
/lib/x86_64-linux-gnu/libQt5Quick.so.5
/lib/x86_64-linux-gnu/libQt5Quick.so.5
/lib/x86_64-linux-gnu/libQt5Quick.so.5
/lib/x86_64-linux-gnu/libQt5Quick.so.5
/lib/x86_64-linux-gnu/libQt5Quick.so.5

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

[digikam] [Bug 472253] Thumbnails of TIFF files show as low resolution with visible colour bands. Raw files are fine as are jpegs.

2023-07-14 Thread IvorJ
https://bugs.kde.org/show_bug.cgi?id=472253

--- Comment #3 from IvorJ  ---
Maik

The TIFFs were created in Digikam.  The actual TIFFs are fine, it's the
preview that's the problem.

Ivor

On Fri, 14 Jul 2023 at 17:45, Maik Qualmann 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=472253
>
> Maik Qualmann  changed:
>
>What|Removed |Added
>
> 
>Platform|Other   |Microsoft Windows
>   Component|Albums-MainView |Thumbs-Image
>  CC||metzping...@gmail.com
>  OS|Other   |Microsoft Windows
>
> --- Comment #1 from Maik Qualmann  ---
> I cannot reproduce the problem with my TIFF files. What program were the
> TIFF
> files created with? They may contain a bad thumbnail/preview image in the
> metadata.
> Please download a sample image from a file hoster so we can investigate the
> problem.
>
> Maik
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[krita] [Bug 472167] Animation play glitch !

2023-07-14 Thread ahmett
https://bugs.kde.org/show_bug.cgi?id=472167

--- Comment #5 from ahmett  ---
Created attachment 160287
  --> https://bugs.kde.org/attachment.cgi?id=160287=edit
crash_lower  playback speed

Krita

 Version: 5.2.0-prealpha (git f49b676)
 Installation type: installer / portable package
 Hidpi: true

Qt

  Version (compiled): 5.15.7
  Version (loaded): 5.15.7

OS Information

  Build ABI: x86_64-little_endian-llp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: winnt
  Kernel Version: 10.0.19045
  Pretty Productname: Windows 10 Version 2009
  Product Type: windows
  Product Version: 10

Locale

  Languages: en_US, en_US
  C locale: C
  QLocale current: en
  QLocale system: tr
  QTextCodec for locale: UTF-8
  Process ACP: 65001 (UTF-8)
  System locale default ACP: 1254  (ANSI - Türkçe)

OpenGL Info

  Vendor:  "Google Inc. (NVIDIA)" 
  Renderer:  "ANGLE (NVIDIA, NVIDIA GeForce GTX 1060 6GB Direct3D11 vs_5_0
ps_5_0, D3D11-31.0.15.3168)" 
  Driver version:  "OpenGL ES 3.0.0 (ANGLE 2.1.0 git hash:
f2280c0c5f93+krita_qt5)" 
  Shading language:  "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0 git hash:
f2280c0c5f93+krita_qt5)" 
  Requested format:  QSurfaceFormat(version 3.0, options
QFlags(), depthBufferSize 24, redBufferSize 8,
greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8,
samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0,
colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::NoProfile) 
  Current format:  QSurfaceFormat(version 3.0, options
QFlags(), depthBufferSize 24, redBufferSize 8,
greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8,
samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0,
colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::NoProfile) 
  GL version: 3.0 
  Supports deprecated functions false 
  Is OpenGL ES: true 
  supportsBufferMapping: true 
  supportsBufferInvalidation: false 
  forceDisableTextureBuffers: true 
  Extensions: 
 GL_CHROMIUM_bind_generates_resource 
 GL_EXT_frag_depth 
 GL_ANGLE_depth_texture 
 GL_OES_texture_float_linear 
 GL_EXT_sRGB 
 GL_EXT_float_blend 
 GL_OES_packed_depth_stencil 
 GL_EXT_disjoint_timer_query 
 GL_OES_compressed_EAC_RG11_unsigned_texture 
 GL_NV_pack_subimage 
 GL_EXT_texture_format_BGRA 
 GL_ANGLE_request_extension 
 GL_EXT_occlusion_query_boolean 
 GL_EXT_texture_norm16 
 GL_EXT_instanced_arrays 
 GL_EXT_shader_texture_lod 
 GL_EXT_texture_rg 
 GL_OES_depth24 
 GL_EXT_draw_buffers 
 GL_EXT_robustness 
 GL_EXT_texture_compression_s3tc_srgb 
 GL_OES_mapbuffer 
 GL_OES_get_program_binary 
 GL_EXT_texture_compression_bptc 
 GL_ANGLE_texture_usage 
 GL_ANGLE_translated_shader_source 
 GL_EXT_multi_draw_indirect 
 GL_ANGLE_robust_client_memory 
 GL_CHROMIUM_copy_texture 
 GL_OES_texture_border_clamp 
 GL_OES_fbo_render_mipmap 
 GL_OES_texture_half_float 
 GL_ANGLE_base_vertex_base_instance_shader_builtin 
 GL_EXT_debug_marker 
 GL_OES_texture_npot 
 GL_NV_EGL_stream_consumer_external 
 GL_CHROMIUM_copy_compressed_texture 
 GL_EXT_blend_func_extended 
 GL_ANGLE_pack_reverse_row_order 
 GL_ANGLE_multi_draw 
 GL_EXT_draw_buffers_indexed 
 GL_EXT_texture_storage 
 GL_EXT_texture_compression_rgtc 
 GL_EXT_EGL_image_external_wrap_modes 
 GL_AMD_performance_monitor 
 GL_OES_EGL_image_external 
 GL_ANGLE_program_cache_control 
 GL_OES_compressed_ETC2_sRGB8_alpha8_texture 
 GL_EXT_draw_elements_base_vertex 
 GL_OVR_multiview2 
 GL_OES_EGL_image_external_essl3 
 GL_OES_vertex_array_object 
 GL_KHR_parallel_shader_compile 
 GL_EXT_texture_type_2_10_10_10_REV 
 GL_OES_compressed_ETC2_RGBA8_texture 
 GL_OES_compressed_EAC_R11_unsigned_texture 
 GL_ANGLE_texture_compression_dxt3 
 GL_CHROMIUM_sync_query 
 GL_EXT_unpack_subimage 
 GL_OES_draw_buffers_indexed 
 GL_ANGLE_texture_multisample 
 GL_EXT_read_format_bgra 
 GL_OES_element_index_uint 
 GL_EXT_texture_compression_dxt1 
 GL_WEBGL_video_texture 
 GL_ANGLE_multiview_multisample 
 GL_ANGLE_lossy_etc_decode 
 GL_EXT_texture_filter_anisotropic 
 GL_OES_texture_half_float_linear 
 GL_ANGLE_framebuffer_multisample 
 GL_CHROMIUM_lose_context 
 GL_NV_pixel_buffer_object 
 GL_OES_compressed_ETC2_sRGB8_texture 
 GL_OES_compressed_ETC2_punchthroughA_RGBA8_texture 
 GL_ANGLE_client_arrays 
 GL_OES_compressed_ETC2_punchthroughA_sRGB8_alpha_texture 
 GL_OES_EGL_image 
 GL_EXT_debug_label 
 GL_OES_texture_stencil8 
 GL_EXT_discard_framebuffer 
 GL_OES_draw_elements_base_vertex 
 GL_ANGLE_instanced_arrays 
 GL_OES_compressed_EAC_RG11_signed_texture 
 GL_EXT_color_buffer_float 
 GL_EXT_color_buffer_half_float 
 GL_ANGLE_framebuffer_blit 
 

[krita] [Bug 472167] Animation play glitch !

2023-07-14 Thread ahmett
https://bugs.kde.org/show_bug.cgi?id=472167

ahmett  changed:

   What|Removed |Added

 Attachment #160286|crash!! lower framerate |system info
description||

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

[krita] [Bug 472167] Animation play glitch !

2023-07-14 Thread ahmett
https://bugs.kde.org/show_bug.cgi?id=472167

--- Comment #3 from ahmett  ---
Comment on attachment 160286
  --> https://bugs.kde.org/attachment.cgi?id=160286
crash!! lower framerate

>Krita
>
> Version: 5.2.0-prealpha (git f49b676)
> Installation type: installer / portable package
> Hidpi: true
>
>Qt
>
>  Version (compiled): 5.15.7
>  Version (loaded): 5.15.7
>
>OS Information
>
>  Build ABI: x86_64-little_endian-llp64
>  Build CPU: x86_64
>  CPU: x86_64
>  Kernel Type: winnt
>  Kernel Version: 10.0.19045
>  Pretty Productname: Windows 10 Version 2009
>  Product Type: windows
>  Product Version: 10
>
>Locale
>
>  Languages: en_US, en_US
>  C locale: C
>  QLocale current: en
>  QLocale system: tr
>  QTextCodec for locale: UTF-8
>  Process ACP: 65001 (UTF-8)
>  System locale default ACP: 1254  (ANSI - Türkçe)
>
>OpenGL Info
> 
>  Vendor:  "Google Inc. (NVIDIA)" 
>  Renderer:  "ANGLE (NVIDIA, NVIDIA GeForce GTX 1060 6GB Direct3D11 vs_5_0 
> ps_5_0, D3D11-31.0.15.3168)" 
>  Driver version:  "OpenGL ES 3.0.0 (ANGLE 2.1.0 git hash: 
> f2280c0c5f93+krita_qt5)" 
>  Shading language:  "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0 git hash: 
> f2280c0c5f93+krita_qt5)" 
>  Requested format:  QSurfaceFormat(version 3.0, options 
> QFlags(), depthBufferSize 24, redBufferSize 8, 
> greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, 
> samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, 
> colorSpace QSurfaceFormat::DefaultColorSpace, profile  
> QSurfaceFormat::NoProfile) 
>  Current format:  QSurfaceFormat(version 3.0, options 
> QFlags(), depthBufferSize 24, redBufferSize 8, 
> greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, 
> samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, 
> colorSpace QSurfaceFormat::DefaultColorSpace, profile  
> QSurfaceFormat::NoProfile) 
>  GL version: 3.0 
>  Supports deprecated functions false 
>  Is OpenGL ES: true 
>  supportsBufferMapping: true 
>  supportsBufferInvalidation: false 
>  forceDisableTextureBuffers: true 
>  Extensions: 
> GL_CHROMIUM_bind_generates_resource 
> GL_EXT_frag_depth 
> GL_ANGLE_depth_texture 
> GL_OES_texture_float_linear 
> GL_EXT_sRGB 
> GL_EXT_float_blend 
> GL_OES_packed_depth_stencil 
> GL_EXT_disjoint_timer_query 
> GL_OES_compressed_EAC_RG11_unsigned_texture 
> GL_NV_pack_subimage 
> GL_EXT_texture_format_BGRA 
> GL_ANGLE_request_extension 
> GL_EXT_occlusion_query_boolean 
> GL_EXT_texture_norm16 
> GL_EXT_instanced_arrays 
> GL_EXT_shader_texture_lod 
> GL_EXT_texture_rg 
> GL_OES_depth24 
> GL_EXT_draw_buffers 
> GL_EXT_robustness 
> GL_EXT_texture_compression_s3tc_srgb 
> GL_OES_mapbuffer 
> GL_OES_get_program_binary 
> GL_EXT_texture_compression_bptc 
> GL_ANGLE_texture_usage 
> GL_ANGLE_translated_shader_source 
> GL_EXT_multi_draw_indirect 
> GL_ANGLE_robust_client_memory 
> GL_CHROMIUM_copy_texture 
> GL_OES_texture_border_clamp 
> GL_OES_fbo_render_mipmap 
> GL_OES_texture_half_float 
> GL_ANGLE_base_vertex_base_instance_shader_builtin 
> GL_EXT_debug_marker 
> GL_OES_texture_npot 
> GL_NV_EGL_stream_consumer_external 
> GL_CHROMIUM_copy_compressed_texture 
> GL_EXT_blend_func_extended 
> GL_ANGLE_pack_reverse_row_order 
> GL_ANGLE_multi_draw 
> GL_EXT_draw_buffers_indexed 
> GL_EXT_texture_storage 
> GL_EXT_texture_compression_rgtc 
> GL_EXT_EGL_image_external_wrap_modes 
> GL_AMD_performance_monitor 
> GL_OES_EGL_image_external 
> GL_ANGLE_program_cache_control 
> GL_OES_compressed_ETC2_sRGB8_alpha8_texture 
> GL_EXT_draw_elements_base_vertex 
> GL_OVR_multiview2 
> GL_OES_EGL_image_external_essl3 
> GL_OES_vertex_array_object 
> GL_KHR_parallel_shader_compile 
> GL_EXT_texture_type_2_10_10_10_REV 
> GL_OES_compressed_ETC2_RGBA8_texture 
> GL_OES_compressed_EAC_R11_unsigned_texture 
> GL_ANGLE_texture_compression_dxt3 
> GL_CHROMIUM_sync_query 
> GL_EXT_unpack_subimage 
> GL_OES_draw_buffers_indexed 
> GL_ANGLE_texture_multisample 
> GL_EXT_read_format_bgra 
> GL_OES_element_index_uint 
> GL_EXT_texture_compression_dxt1 
> GL_WEBGL_video_texture 
> GL_ANGLE_multiview_multisample 
> GL_ANGLE_lossy_etc_decode 
> GL_EXT_texture_filter_anisotropic 
> GL_OES_texture_half_float_linear 
> GL_ANGLE_framebuffer_multisample 
> GL_CHROMIUM_lose_context 
> GL_NV_pixel_buffer_object 
> GL_OES_compressed_ETC2_sRGB8_texture 
> GL_OES_compressed_ETC2_punchthroughA_RGBA8_texture 
> GL_ANGLE_client_arrays 
> GL_OES_compressed_ETC2_punchthroughA_sRGB8_alpha_texture 
> GL_OES_EGL_image 
> GL_EXT_debug_label 
> GL_OES_texture_stencil8 
> GL_EXT_discard_framebuffer 
> GL_OES_draw_elements_base_vertex 
> GL_ANGLE_instanced_arrays 
> 

[krita] [Bug 472167] Animation play glitch !

2023-07-14 Thread ahmett
https://bugs.kde.org/show_bug.cgi?id=472167

--- Comment #3 from ahmett  ---
Comment on attachment 160286
  --> https://bugs.kde.org/attachment.cgi?id=160286
crash!! lower framerate

>Krita
>
> Version: 5.2.0-prealpha (git f49b676)
> Installation type: installer / portable package
> Hidpi: true
>
>Qt
>
>  Version (compiled): 5.15.7
>  Version (loaded): 5.15.7
>
>OS Information
>
>  Build ABI: x86_64-little_endian-llp64
>  Build CPU: x86_64
>  CPU: x86_64
>  Kernel Type: winnt
>  Kernel Version: 10.0.19045
>  Pretty Productname: Windows 10 Version 2009
>  Product Type: windows
>  Product Version: 10
>
>Locale
>
>  Languages: en_US, en_US
>  C locale: C
>  QLocale current: en
>  QLocale system: tr
>  QTextCodec for locale: UTF-8
>  Process ACP: 65001 (UTF-8)
>  System locale default ACP: 1254  (ANSI - Türkçe)
>
>OpenGL Info
> 
>  Vendor:  "Google Inc. (NVIDIA)" 
>  Renderer:  "ANGLE (NVIDIA, NVIDIA GeForce GTX 1060 6GB Direct3D11 vs_5_0 
> ps_5_0, D3D11-31.0.15.3168)" 
>  Driver version:  "OpenGL ES 3.0.0 (ANGLE 2.1.0 git hash: 
> f2280c0c5f93+krita_qt5)" 
>  Shading language:  "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0 git hash: 
> f2280c0c5f93+krita_qt5)" 
>  Requested format:  QSurfaceFormat(version 3.0, options 
> QFlags(), depthBufferSize 24, redBufferSize 8, 
> greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, 
> samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, 
> colorSpace QSurfaceFormat::DefaultColorSpace, profile  
> QSurfaceFormat::NoProfile) 
>  Current format:  QSurfaceFormat(version 3.0, options 
> QFlags(), depthBufferSize 24, redBufferSize 8, 
> greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, 
> samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, 
> colorSpace QSurfaceFormat::DefaultColorSpace, profile  
> QSurfaceFormat::NoProfile) 
>  GL version: 3.0 
>  Supports deprecated functions false 
>  Is OpenGL ES: true 
>  supportsBufferMapping: true 
>  supportsBufferInvalidation: false 
>  forceDisableTextureBuffers: true 
>  Extensions: 
> GL_CHROMIUM_bind_generates_resource 
> GL_EXT_frag_depth 
> GL_ANGLE_depth_texture 
> GL_OES_texture_float_linear 
> GL_EXT_sRGB 
> GL_EXT_float_blend 
> GL_OES_packed_depth_stencil 
> GL_EXT_disjoint_timer_query 
> GL_OES_compressed_EAC_RG11_unsigned_texture 
> GL_NV_pack_subimage 
> GL_EXT_texture_format_BGRA 
> GL_ANGLE_request_extension 
> GL_EXT_occlusion_query_boolean 
> GL_EXT_texture_norm16 
> GL_EXT_instanced_arrays 
> GL_EXT_shader_texture_lod 
> GL_EXT_texture_rg 
> GL_OES_depth24 
> GL_EXT_draw_buffers 
> GL_EXT_robustness 
> GL_EXT_texture_compression_s3tc_srgb 
> GL_OES_mapbuffer 
> GL_OES_get_program_binary 
> GL_EXT_texture_compression_bptc 
> GL_ANGLE_texture_usage 
> GL_ANGLE_translated_shader_source 
> GL_EXT_multi_draw_indirect 
> GL_ANGLE_robust_client_memory 
> GL_CHROMIUM_copy_texture 
> GL_OES_texture_border_clamp 
> GL_OES_fbo_render_mipmap 
> GL_OES_texture_half_float 
> GL_ANGLE_base_vertex_base_instance_shader_builtin 
> GL_EXT_debug_marker 
> GL_OES_texture_npot 
> GL_NV_EGL_stream_consumer_external 
> GL_CHROMIUM_copy_compressed_texture 
> GL_EXT_blend_func_extended 
> GL_ANGLE_pack_reverse_row_order 
> GL_ANGLE_multi_draw 
> GL_EXT_draw_buffers_indexed 
> GL_EXT_texture_storage 
> GL_EXT_texture_compression_rgtc 
> GL_EXT_EGL_image_external_wrap_modes 
> GL_AMD_performance_monitor 
> GL_OES_EGL_image_external 
> GL_ANGLE_program_cache_control 
> GL_OES_compressed_ETC2_sRGB8_alpha8_texture 
> GL_EXT_draw_elements_base_vertex 
> GL_OVR_multiview2 
> GL_OES_EGL_image_external_essl3 
> GL_OES_vertex_array_object 
> GL_KHR_parallel_shader_compile 
> GL_EXT_texture_type_2_10_10_10_REV 
> GL_OES_compressed_ETC2_RGBA8_texture 
> GL_OES_compressed_EAC_R11_unsigned_texture 
> GL_ANGLE_texture_compression_dxt3 
> GL_CHROMIUM_sync_query 
> GL_EXT_unpack_subimage 
> GL_OES_draw_buffers_indexed 
> GL_ANGLE_texture_multisample 
> GL_EXT_read_format_bgra 
> GL_OES_element_index_uint 
> GL_EXT_texture_compression_dxt1 
> GL_WEBGL_video_texture 
> GL_ANGLE_multiview_multisample 
> GL_ANGLE_lossy_etc_decode 
> GL_EXT_texture_filter_anisotropic 
> GL_OES_texture_half_float_linear 
> GL_ANGLE_framebuffer_multisample 
> GL_CHROMIUM_lose_context 
> GL_NV_pixel_buffer_object 
> GL_OES_compressed_ETC2_sRGB8_texture 
> GL_OES_compressed_ETC2_punchthroughA_RGBA8_texture 
> GL_ANGLE_client_arrays 
> GL_OES_compressed_ETC2_punchthroughA_sRGB8_alpha_texture 
> GL_OES_EGL_image 
> GL_EXT_debug_label 
> GL_OES_texture_stencil8 
> GL_EXT_discard_framebuffer 
> GL_OES_draw_elements_base_vertex 
> GL_ANGLE_instanced_arrays 
> 

[plasmashell] [Bug 472258] System Monitor Sensor doesn't display all GPU info

2023-07-14 Thread Unknown
https://bugs.kde.org/show_bug.cgi?id=472258

]\/[ ]\/[ ]_ 1357  changed:

   What|Removed |Added

   Platform|Other   |Neon

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

[krita] [Bug 472167] Animation play glitch !

2023-07-14 Thread ahmett
https://bugs.kde.org/show_bug.cgi?id=472167

--- Comment #2 from ahmett  ---
Created attachment 160286
  --> https://bugs.kde.org/attachment.cgi?id=160286=edit
crash!! lower framerate

I noticed 2 more bugs.
1-There is a problem of not being able to play again. The timeline stops at the
last frame of the range.
2- When you reduce the playback speed to 50, the krita crashes.

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

[plasmashell] [Bug 472258] New: System Monitor Sensor doesn't display all GPU info

2023-07-14 Thread Unknown
https://bugs.kde.org/show_bug.cgi?id=472258

Bug ID: 472258
   Summary: System Monitor Sensor doesn't display all GPU info
Classification: Plasma
   Product: plasmashell
   Version: 5.27.6
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: System Monitor
  Assignee: plasma-b...@kde.org
  Reporter: mmarrerole...@gmail.com
CC: ahiems...@heimr.nl, notm...@gmail.com
  Target Milestone: 1.0

After update to Plasma 5.27.6, sensors for GPU stop working. Only works GPU
name; all other values like temp, usage, frequency... just display 0.


STEPS TO REPRODUCE
1. Add some sensor related to GPU on System Monitor applet.

OBSERVED RESULT
Value is 0.

EXPECTED RESULT
Real values.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10
Kernel Version: 6.3.1-060301-generic (64-bit)
Graphics Platform: X11
Processors: 12 × 12th Gen Intel® Core™ i5-12400
Memory: 31.1 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2
Manufacturer: ASUS

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

[Powerdevil] [Bug 469487] New OSD to swap between power profiles

2023-07-14 Thread Natalie Clarius
https://bugs.kde.org/show_bug.cgi?id=469487

Natalie Clarius  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/powerdevil/-/commit/fd29 |ma/powerdevil/-/commit/54a8
   |e77b5e6320ad072fbf38c508234 |05765d7f06f016b23fcab9703c6
   |38936a382   |3449b6c52

--- Comment #3 from Natalie Clarius  ---
Git commit 54a805765d7f06f016b23fcab9703c63449b6c52 by Natalie Clarius.
Committed on 11/07/2023 at 22:57.
Pushed by nclarius into branch 'power-profiles-osd'.

add interactive osd to switch power profiles
FIXED-IN: 6.0

M  +10   -0CMakeLists.txt
M  +19   -0daemon/powerdevilapp.cpp
M  +1-0daemon/powerdevilapp.h
A  +26   -0osd/CMakeLists.txt
A  +20   -0osd/main.cpp [License: GPL(v2.0+)]
A  +9-0osd/org.kde.powerdevil.powerProfileOsdService.xml
A  +86   -0osd/osd.cpp [License: GPL(v2.0+)]
A  +50   -0osd/osd.h [License: GPL(v2.0+)]
A  +27   -0osd/osdaction.cpp [License: GPL(v2.0+)]
A  +35   -0osd/osdaction.h [License: GPL(v2.0+)]
A  +86   -0osd/osdmanager.cpp [License: GPL(v2.0+)]
A  +41   -0osd/osdmanager.h [License: GPL(v2.0+)]
A  +12   -0osd/plasma-powerprofile-osd.service
A  +6-0osd/qml.qrc
A  +137  -0osd/qml/OsdSelector.qml [License: GPL(v2.0+)]

https://invent.kde.org/plasma/powerdevil/-/commit/54a805765d7f06f016b23fcab9703c63449b6c52

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

  1   2   3   >