[dolphin] [Bug 477298] Dolphin hangs when navigating to a directory with any JSON files in it

[Giuseppe]

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

Giuseppe  changed:

   What|Removed |Added

 CC||utenze@gmail.com

--- Comment #14 from Giuseppe  ---
The problem persists, even in a more updated PC with a different OS.

SUMMARY
Dolphin freezes, then crashes, when browsing the file system it enters a folder
that contains files with the extension .json

STEPS TO REPRODUCE
1. In a terminal, create in any subfolder of the home a empty file and rename
it with .json extension.
2. Open Dolphin and browse to the above folder. 

OBSERVED RESULT
Dolphin should freeze and you will have to kill it.

EXPECTED RESULT
Other file manager like Gnome "Files" enter normally in the folder

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 24.04
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Kernel Version: 6.8.0-31-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-2400 CPU @ 3.10GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 2000
Manufacturer: Hewlett-Packard
Product Name: HP Elite 7300 Series MT
System Version: 1.01

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

[systemsettings] [Bug 479729] New: Gui elements hidden by kcm title header

[Giuseppe Calà]

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

Bug ID: 479729
   Summary: Gui elements hidden by kcm title header
Classification: Applications
   Product: systemsettings
   Version: 5.92.0
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: gc...@mailbox.org
  Target Milestone: ---

Created attachment 164858
  --> https://bugs.kde.org/attachment.cgi?id=164858=edit
Image showing kcm_screenlocker partially visible

With kde/plasma 6 beta/rc there is a regression regarding kcm modules whose
content is not fully visible but top most elements are inaccessible since
rendered behind Kcm module's Title. Attached the screenlocker example.


STEPS TO REPRODUCE
1. Open a kcm module through kcmshell6 (f.i. `kcmshell6 kcm_screenlocker`)

OBSERVED RESULT

The module main area is partially hidden by title bar

EXPECTED RESULT
All gui elements should be visible and accessible

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.92.0
KDE Frameworks Version: 5.248.0
Qt Version: 6.7.0
Kernel Version: 6.6.10-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 4 × AMD A8-6500 APU with Radeon(tm) HD Graphics
Memory: 7.7 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2

ADDITIONAL INFORMATION

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

[kwin] [Bug 479402] New: On a 2560x1080p monitor, snapping a window to the edge and dragging the corner to the opposite edge only resizes the window to 75% of the screen width

[Giuseppe]

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

Bug ID: 479402
   Summary: On a 2560x1080p monitor,  snapping a window to the
edge and dragging the corner to the opposite edge only
resizes the window to 75% of the screen width
Classification: Plasma
   Product: kwin
   Version: 5.27.10
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Quick Tiling
  Assignee: kwin-bugs-n...@kde.org
  Reporter: giuseppepentangel...@gmail.com
  Target Milestone: ---

Created attachment 164675
  --> https://bugs.kde.org/attachment.cgi?id=164675=edit
It wont get dragged to the left more than this

EXPECTED BEHAVIOR
I expect that the window gets dragged till it occupies 100% of the screen width

I attach a screenshot of the problem

this problem is present on both wayland and x11 and it seems to cause
additional problems with windows not tiling properly anymore and not making
them resizable anymore

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

[systemsettings] [Bug 478962] New: Some system settings KCM modules aren't loaded

[Giuseppe Calà]

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

Bug ID: 478962
   Summary: Some system settings KCM modules aren't loaded
Classification: Applications
   Product: systemsettings
   Version: 5.91.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: gc...@mailbox.org
  Target Milestone: ---

Created attachment 164418
  --> https://bugs.kde.org/attachment.cgi?id=164418=edit
Image showing systemsettings's landing page opened from gui (left) and with
kcmshell6 (right)

SUMMARY
Some system settings KCM modules aren't loaded; there is an error loading a qml
file. For instance:
```
kf.kcmutils: Error loading QML file qrc:/kcm/kcm_landingpage/main.qml
kf.kcmutils: ""qrc:/kcm/kcm_landingpage/main.qml:18:1: Type KCM.SimpleKCM
unavailable
KCM.SimpleKCM {
^
kf.kcmutils: ""qrc:/qt/qml/org/kde/kcmutils/SimpleKCM.qml:33:1: Type
Kirigami.ScrollablePage unavailable
Kirigami.ScrollablePage {
^
kf.kcmutils: "   
"file:///usr/lib/qt6/qml/org/kde/kirigami/ScrollablePage.qml:68:1: Type
Kirigami.Page unavailable
Kirigami.Page {
^
kf.kcmutils: ""file:///usr/lib/qt6/qml/org/kde/kirigami/Page.qml:237:13:
Type Kirigami.PageRow unavailable
property Kirigami.PageRow row
^
kf.kcmutils: ""file:///usr/lib/qt6/qml/org/kde/kirigami/PageRow.qml:180:5:
Type OverlayDrawer unavailable
property OverlayDrawer leftSidebar
^
kf.kcmutils: "   
"file:///usr/lib/qt6/qml/org/kde/kirigami/OverlayDrawer.qml:22:1: Type
KT.OverlayDrawer unavailable
KT.OverlayDrawer {
^
kf.kcmutils: "   
"file:///usr/lib/qt6/qml/org/kde/kirigami/templates/OverlayDrawer.qml:120:56:
Cannot assign object of type "KTP.IconPropertiesGroup" to property of type
"IconPropertiesGroup_QMLTYPE_71*" as the former is neither the same as the
latter nor a sub-class of it.
property KTP.IconPropertiesGroup handleClosedIcon:
KTP.IconPropertiesGroup {
``` 
 The error disappears when launching the component from console through
kcmshell6 (on the right in image)

Not all modules show this behaviour: Proxy, connection preferences, font
manager are shown correctly.

STEPS TO REPRODUCE
1. Open systemsettings
2. 
3. 

OBSERVED RESULT

main widget on the right reports error loading a qml file

EXPECTED RESULT
show settings

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.91.0
KDE Frameworks Version: 5.247.0
Qt Version: 6.7.0
Kernel Version: 6.6.8-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 4 × AMD A8-6500 APU with Radeon(tm) HD Graphics
Memory: 7.7 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2

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

[kscreenlocker] [Bug 478090] [NVIDIA] locking 2nd time in a Wayland session results in black screen with cursor

[Giuseppe Calà]

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

Giuseppe Calà  changed:

   What|Removed |Added

 CC||gc...@mailbox.org

--- Comment #6 from Giuseppe Calà  ---
I confirm the bug. I usually use hibernate and after resume I got a black
screen with a mouse pointer that follows mouse movements.

Operating System: Arch Linux 
KDE Plasma Version: 5.91.0
KDE Frameworks Version: 5.247.0
Qt Version: 6.7.0
Kernel Version: 6.6.8-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 4 × AMD A8-6500 APU with Radeon(tm) HD Graphics
Memory: 7.7 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2

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

[frameworks-solid] [Bug 477915] Can't mount encrypted drives

[Giuseppe Calà]

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

Giuseppe Calà  changed:

   What|Removed |Added

 CC||gc...@mailbox.org

--- Comment #6 from Giuseppe Calà  ---
I confirm the bug. I'm also on Archlinux with [kde-unstable] enabled

Operating System: Arch Linux 
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
Kernel Version: 6.6.7-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 4 × AMD A8-6500 APU with Radeon(tm) HD Graphics
Memory: 7.7 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2

solid 5.246.0
udisks2 2.10.1
(kded5, solid5 not installed)

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

[clazy] [Bug 470993] New: Disable auto-unexpected-qstringbuilder on Qt >= 6.7

[Giuseppe D'Angelo]

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

Bug ID: 470993
   Summary: Disable auto-unexpected-qstringbuilder on Qt >= 6.7
Classification: Developer tools
   Product: clazy
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: dange...@gmail.com
CC: smart...@kde.org
  Target Milestone: ---

With the merge of https://codereview.qt-project.org/c/qt/qtbase/+/479775 in Qt
6.7, auto + QStringBuilder will be fine, so warning about it feels wrong. It
might also be interesting to tell users that they could fix the problem by
upgrading.

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

[clazy] [Bug 468419] New: Add a check that discourages isNull (in favor of isEmpty)

[Giuseppe D'Angelo]

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

Bug ID: 468419
   Summary: Add a check that discourages isNull (in favor of
isEmpty)
Classification: Developer tools
   Product: clazy
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: dange...@gmail.com
CC: smart...@kde.org
  Target Milestone: ---

Qt string-like classes feature two similar but different functions: isNull and
isEmpty. There are differences between the two, and the differences are subtle;
a null string is always empty but an empty string isn't necessarily null (e.g.
QString("") is empty but not null). Usage of isNull is almost always
questionable.

(One could also extend this to other classes, e.g. QRect, where the null vs.
empty semantics are very weird.)

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

[plasma-nm] [Bug 459592] Username/password fields missing in Openconnect's Fortinet protocol settings?

[Giuseppe Calà]

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

--- Comment #2 from Giuseppe Calà  ---
(In reply to Nicolas Fella from comment #1)
> Does creating a "Fortinet SSLVPN (fortisslvpn)" connection work as expected?
> Not sure why both "Fortinet SSLVPN (fortisslvpn)" and "Fortinet Compatible
> VPN (openconnect)" exist. I suspect it's the same kind of VPN but exposed
> via two different "backends"

"Fortinet SSLVPN (fortisslvpn)" partially works in the sense that I can receive
on my mail the OTP but the window in which I should write it up stays open for
a blink. I reported the bug here https://bugs.kde.org/show_bug.cgi?id=436158.

Thanks

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

[kontact] [Bug 464565] New: Kontact crashes on trying to append a notice to a mail message

[Giuseppe Vinci]

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

Bug ID: 464565
   Summary: Kontact crashes on trying to append a notice to a mail
message
Classification: Applications
   Product: kontact
   Version: 5.19.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: mail
  Assignee: kdepim-b...@kde.org
  Reporter: giuseppe.vi...@gmx.net
  Target Milestone: ---

SUMMARY
***
The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault

[KCrash Handler]
#4  0x7f972bfadb53 in free () from /lib64/libc.so.6
#5  0x7f972ddf66a1 in QDialog::exec (this=this@entry=0x7ffef984b840) at
dialogs/qdialog.cpp:613
#6  0x7f96a1016fac in KMail::MessageActions::annotateMessage
(this=0x55fb4bd707d0) at
/usr/src/debug/kmail-21.12.3-bp154.1.19.x86_64/src/messageactions.cpp:702
#7  0x7f972ca3d217 in QtPrivate::QSlotObjectBase::call (a=0x7ffef984b990,
r=0x55fb4bd707d0, this=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#8  doActivate (sender=0x55fb4bcf3430, signal_index=4,
argv=0x7ffef984b990) at kernel/qobject.cpp:3886
#9  0x7f972ca366c2 in QMetaObject::activate
(sender=sender@entry=0x55fb4bcf3430, m=m@entry=0x7f972e2e00a0
, local_signal_index=local_signal_index@entry=1,
argv=argv@entry=0x7ffef984b990) at kernel/qobject.cpp:3946
#10 0x7f972dbf4e12 in QAction::triggered (this=this@entry=0x55fb4bcf3430,
_t1=) at .moc/moc_qaction.cpp:376
#11 0x7f972dbf747c in QAction::activate (this=0x55fb4bcf3430,
event=) at kernel/qaction.cpp:1161
#12 0x7f972dd7343b in QMenuPrivate::activateCausedStack
(this=this@entry=0x55fb4c3e9290, causedStack=...,
action=action@entry=0x55fb4bcf3430, action_e=action_e@entry=QAction::Trigger,
self=self@entry=true) at widgets/qmenu.cpp:1384
#13 0x7f972dd7ac0b in QMenuPrivate::activateAction
(this=this@entry=0x55fb4c3e9290, action=action@entry=0x55fb4bcf3430,
action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at
widgets/qmenu.cpp:1461
#14 0x7f972dd7b93d in QMenu::mouseReleaseEvent (this=,
e=0x7ffef984c050) at widgets/qmenu.cpp:2966
#15 0x7f972dc3bb48 in QWidget::event (this=this@entry=0x55fb4c3d4ba0,
event=event@entry=0x7ffef984c050) at kernel/qwidget.cpp:9020
#16 0x7f972dd7dbdb in QMenu::event (this=0x55fb4c3d4ba0, e=0x7ffef984c050)
at widgets/qmenu.cpp:3088
#17 0x7f972dbfb3bc in QApplicationPrivate::notify_helper
(this=this@entry=0x55fb4b4cd3f0, receiver=receiver@entry=0x55fb4c3d4ba0,
e=e@entry=0x7ffef984c050) at kernel/qapplication.cpp:3632
#18 0x7f972dc02730 in QApplication::notify (this=,
receiver=0x55fb4c3d4ba0, e=0x7ffef984c050) at kernel/qapplication.cpp:3076
#19 0x7f972c9ffac3 in QCoreApplication::notifyInternal2
(receiver=0x55fb4c3d4ba0, event=0x7ffef984c050) at
kernel/qcoreapplication.cpp:1064
#20 0x7f972c9ffcae in QCoreApplication::sendSpontaneousEvent
(receiver=receiver@entry=0x55fb4c3d4ba0, event=event@entry=0x7ffef984c050) at
kernel/qcoreapplication.cpp:1474
#21 0x7f972dc0171f in QApplicationPrivate::sendMouseEvent
(receiver=0x55fb4c3d4ba0, event=event@entry=0x7ffef984c050, alienWidget=0x0,
nativeWidget=0x55fb4c3d4ba0, buttonDown=buttonDown@entry=0x7f972e317670
, lastMouseReceiver=..., spontaneous=true,
onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2614
#22 0x7f972dc56781 in QWidgetWindow::handleMouseEvent
(this=this@entry=0x55fb4ecf4710, event=event@entry=0x7ffef984c4b0) at
kernel/qwidgetwindow.cpp:580
#23 0x7f972dc5938d in QWidgetWindow::event (this=0x55fb4ecf4710,
event=0x7ffef984c4b0) at kernel/qwidgetwindow.cpp:300
#24 0x7f972dbfb3bc in QApplicationPrivate::notify_helper
(this=this@entry=0x55fb4b4cd3f0, receiver=receiver@entry=0x55fb4ecf4710,
e=e@entry=0x7ffef984c4b0) at kernel/qapplication.cpp:3632
#25 0x7f972dc021a0 in QApplication::notify (this=0x7ffef984da10,
receiver=0x55fb4ecf4710, e=0x7ffef984c4b0) at kernel/qapplication.cpp:3156
#26 0x7f972c9ffac3 in QCoreApplication::notifyInternal2
(receiver=0x55fb4ecf4710, event=0x7ffef984c4b0) at
kernel/qcoreapplication.cpp:1064
#27 0x7f972c9ffcae in QCoreApplication::sendSpontaneousEvent
(receiver=receiver@entry=0x55fb4ecf4710, event=event@entry=0x7ffef984c4b0) at
kernel/qcoreapplication.cpp:1474
#28 0x7f972d2a80cb in QGuiApplicationPrivate::processMouseEvent
(e=0x55fb4ed29c50) at kernel/qguiapplication.cpp:2282
#29 0x7f972d2a9675 in QGuiApplicationPrivate::processWindowSystemEvent
(e=e@entry=0x55fb4ed29c50) at kernel/qguiapplication.cpp:2002
#30 0x7f972d28144b in QWindowSystemInterface::sendWindowSystemEvents
(flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169
#31 0x7f9705471d0a in xcbSourceDispatch (source=) at
qxcbeventdispatcher.cpp:105
#32 0x7f971e2d87fb in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#33 0x7f971e2d8ba0 in ?? () from 

[kmail2] [Bug 463935] Crash on attempting to replay a message with an user template

[Giuseppe Vinci]

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

Giuseppe Vinci  changed:

   What|Removed |Added

 CC||giuseppe.vi...@gmx.net

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

[kmail2] [Bug 463935] New: Crash on attempting to replay a message with an user template

[Giuseppe Vinci]

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

Bug ID: 463935
   Summary: Crash on attempting to replay a message with an user
template
Classification: Applications
   Product: kmail2
   Version: 5.19.3
  Platform: OpenSUSE
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: commands and actions
  Assignee: kdepim-b...@kde.org
  Reporter: giuseppe.vi...@gmx.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
***
[KCrash Handler]
#4  KMReaderWin::htmlMail (this=0x0) at
/usr/src/debug/kmail-21.12.3-bp154.1.19.x86_64/src/kmreaderwin.cpp:398
#5  0x7fa093873b4d in KMMainWidget::slotCustomReplyAllToMsg
(this=0x55a5bce08cc0, tmpl=...) at
/usr/src/debug/kmail-21.12.3-bp154.1.19.x86_64/src/kmmainwidget.cpp:2094
#6  0x7fa093755b8f in KMMainWidget::qt_static_metacall (_o=,
_c=, _id=, _a=) at
/usr/src/debug/kmail-21.12.3-bp154.1.19.x86_64/build/src/kmailprivate_autogen/EWIEGA46WW/moc_kmmainwidget.cpp:663
#7  0x7fa123e6dfa9 in doActivate (sender=0x55a5bcf3e610,
signal_index=4, argv=0x7ffcf6c45410) at kernel/qobject.cpp:3898
#8  0x7fa123e67782 in QMetaObject::activate (sender=,
m=m@entry=0x7fa09244f5e0
,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffcf6c45410)
at kernel/qobject.cpp:3946
#9  0x7fa092213405 in
TemplateParser::CustomTemplatesMenu::replyAllTemplateSelected (this=, _t1=...) at
/usr/src/debug/messagelib-21.12.3-bp154.1.22.x86_64/build/templateparser/src/KF5TemplateParser_autogen/EWIEGA46WW/moc_customtemplatesmenu.cpp:187
#10 0x7fa123e6e1c7 in QtPrivate::QSlotObjectBase::call (a=0x7ffcf6c45530,
r=0x55a5bcf3e610, this=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#11 doActivate (sender=0x55a5bd06a1a0, signal_index=4,
argv=0x7ffcf6c45530) at kernel/qobject.cpp:3886
#12 0x7fa123e67782 in QMetaObject::activate
(sender=sender@entry=0x55a5bd06a1a0, m=m@entry=0x7fa1257110a0
, local_signal_index=local_signal_index@entry=1,
argv=argv@entry=0x7ffcf6c45530) at kernel/qobject.cpp:3946
#13 0x7fa125025e12 in QAction::triggered (this=this@entry=0x55a5bd06a1a0,
_t1=) at .moc/moc_qaction.cpp:376
#14 0x7fa12502847c in QAction::activate (this=0x55a5bd06a1a0,
event=) at kernel/qaction.cpp:1161
#15 0x7fa1251a443b in QMenuPrivate::activateCausedStack
(this=this@entry=0x55a5bd013b20, causedStack=...,
action=action@entry=0x55a5bd06a1a0, action_e=action_e@entry=QAction::Trigger,
self=self@entry=true) at widgets/qmenu.cpp:1384
#16 0x7fa1251abc0b in QMenuPrivate::activateAction
(this=this@entry=0x55a5bd013b20, action=action@entry=0x55a5bd06a1a0,
action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at
widgets/qmenu.cpp:1461
#17 0x7fa1251ac93d in QMenu::mouseReleaseEvent (this=,
e=0x7ffcf6c45bf0) at widgets/qmenu.cpp:2966
#18 0x7fa12506cb48 in QWidget::event (this=this@entry=0x55a5bd055f90,
event=event@entry=0x7ffcf6c45bf0) at kernel/qwidget.cpp:9020
#19 0x7fa1251aebdb in QMenu::event (this=0x55a5bd055f90, e=0x7ffcf6c45bf0)
at widgets/qmenu.cpp:3088
#20 0x7fa12502c3bc in QApplicationPrivate::notify_helper
(this=this@entry=0x55a5bc7e33f0, receiver=receiver@entry=0x55a5bd055f90,
e=e@entry=0x7ffcf6c45bf0) at kernel/qapplication.cpp:3632
#21 0x7fa125033730 in QApplication::notify (this=,
receiver=0x55a5bd055f90, e=0x7ffcf6c45bf0) at kernel/qapplication.cpp:3076
#22 0x7fa123e30c23 in QCoreApplication::notifyInternal2
(receiver=0x55a5bd055f90, event=0x7ffcf6c45bf0) at
kernel/qcoreapplication.cpp:1064
#23 0x7fa123e30e0e in QCoreApplication::sendSpontaneousEvent
(receiver=receiver@entry=0x55a5bd055f90, event=event@entry=0x7ffcf6c45bf0) at
kernel/qcoreapplication.cpp:1474
#24 0x7fa12503271f in QApplicationPrivate::sendMouseEvent
(receiver=0x55a5bd055f90, event=event@entry=0x7ffcf6c45bf0, alienWidget=0x0,
nativeWidget=0x55a5bd055f90, buttonDown=buttonDown@entry=0x7fa125748670
, lastMouseReceiver=..., spontaneous=true,
onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2614
#25 0x7fa125087781 in QWidgetWindow::handleMouseEvent
(this=this@entry=0x7fa0f4006c70, event=event@entry=0x7ffcf6c46050) at
kernel/qwidgetwindow.cpp:580
#26 0x7fa12508a38d in QWidgetWindow::event (this=0x7fa0f4006c70,
event=0x7ffcf6c46050) at kernel/qwidgetwindow.cpp:300
#27 0x7fa12502c3bc in QApplicationPrivate::notify_helper
(this=this@entry=0x55a5bc7e33f0, receiver=receiver@entry=0x7fa0f4006c70,
e=e@entry=0x7ffcf6c46050) at kernel/qapplication.cpp:3632
#28 0x7fa1250331a0 in QApplication::notify (this=0x7ffcf6c475b0,
receiver=0x7fa0f4006c70, e=0x7ffcf6c46050) at kernel/qapplication.cpp:3156
#29 0x7fa123e30c23 in QCoreApplication::notifyInternal2
(receiver=0x7fa0f4006c70, event=0x7ffcf6c46050) 

[kmymoney] [Bug 463708] CSV Import very slow

[Giuseppe Fuggiano]

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

--- Comment #12 from Giuseppe Fuggiano  ---
Hi Jack,

thank you for your suggestions.  Since there is no other solution, I think I
will end up preprocessing the CSV as you said.

Regards

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

[kmymoney] [Bug 463708] CSV Import very slow

[Giuseppe Fuggiano]

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

--- Comment #10 from Giuseppe Fuggiano  ---
Hi Jack, thanks for your suggestion.

I can indeed import it as Memo, as it really is.   But I also need to import it
as a Payee because I can't match the Memo field to determine the Payee (and
thus it's category) automatically, using the bank-provided information alone.  

As you can imagine, I can't / don't want to do that job manually each time I
import a CSV, even a small one.  Instead, I need something that can add all the
metadata automatically (including payees and categories).   If I could match
the Memo field and popupate the Payee and the Category fields, for example
using another kMyMoney feature with regular expressions, as done in the Payee
tab, it would be perfect.  Is that possible?  If not, do you have some other
suggestions? 

Remember: my bank-provided CSVs don't contain the Payee nor Category
information but only the Description field.  My banks don't give me that
information ready to import (and even if so, I would want to use my own
categories...).

Thank you.

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

[kmymoney] [Bug 463708] CSV Import very slow

[Giuseppe Fuggiano]

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

--- Comment #6 from Giuseppe Fuggiano  ---
No sorry you should import it as follows:

first column: date
second column: amount
third column: payee

I'm using the third column as payee because I don't have the payee specified in
my CSV exported from the bank. So I'll try to match the correct payee later
using the automated matching feature.

I've downloaded and installed kmymoney using the official Alpine Linux
repository.

Can you reproduce the bug now?

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

[kmymoney] [Bug 463708] CSV Import very slow

[Giuseppe Fuggiano]

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

--- Comment #5 from Giuseppe Fuggiano  ---
Hi, sorry for the few information provided. You imported my sample data as
expected. I'm using a "standard" setup, no network involved. My drive is
healthy. My PC is a DELL with 6 cores i7-8750H CPU @ 2.20GHz. 

I'm under Alpine Linux. I'm checking under another distro.

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

[kmymoney] [Bug 463708] CSV Import very slow

[Giuseppe Fuggiano]

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

--- Comment #2 from Giuseppe Fuggiano  ---
Created attachment 154945
  --> https://bugs.kde.org/attachment.cgi?id=154945=edit
test data

Use this data file to reproduce the bug. I've imported it to a new XML file. It
tool more that 10 minutes to finish.

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

[kmymoney] [Bug 463708] CSV Import very slow

[Giuseppe Fuggiano]

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

Giuseppe Fuggiano  changed:

   What|Removed |Added

   Platform|Flatpak |unspecified

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

[kmymoney] [Bug 463708] New: CSV Import very slow

[Giuseppe Fuggiano]

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

Bug ID: 463708
   Summary: CSV Import very slow
Classification: Applications
   Product: kmymoney
   Version: 5.1.3
  Platform: Flatpak
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: importer
  Assignee: kmymoney-de...@kde.org
  Reporter: giuseppe.fuggi...@gmail.com
  Target Milestone: ---

SUMMARY
When importing a simple and small CSV kmymoney takes 100% CPU and it's getting
really too much time (more than 15 minutes).


STEPS TO REPRODUCE
1. Import a CSV file with about 4k lines


OBSERVED RESULT
Too slow and 100% CPU used.

EXPECTED RESULT
Fast import.

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

ADDITIONAL INFORMATION

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

[kscreenlocker] [Bug 453741] kscreenlocker_greet crashes in ScreenLocker::UnlockApp::markViewsAsVisible()

[giuseppe]

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

giuseppe  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #17 from giuseppe  ---
(In reply to Nate Graham from comment #15)
> Can you reproduce it on Fedora 36?

Sorry, i must have missed the email somehow. After the stable release of Fedora
36 it didn't happen anymore, I've gone all summer without the bug. 
Now I'm on Steam OS since I changed my device but I assume the bug can be
marked as solved finally.

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

[kmail2] [Bug 338238] copied or moved mails are often not processed correctly (POP3)

[Giuseppe Vinci]

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

Giuseppe Vinci  changed:

   What|Removed |Added

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

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

[kmail2] [Bug 338238] copied or moved mails are often not processed correctly (POP3)

[Giuseppe Vinci]

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

--- Comment #9 from Giuseppe Vinci  ---
No, I can not reproduce the issue with my current software version, 5.14.2 on
OpenSuse Leap 15.3

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

[plasma-nm] [Bug 459592] New: Username/password fields missing in Openconnect's Fortinet protocol settings?

[Giuseppe Calà]

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

Bug ID: 459592
   Summary: Username/password fields missing in Openconnect's
Fortinet protocol settings?
Classification: Plasma
   Product: plasma-nm
   Version: 5.25.90
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: gc...@mailbox.org
CC: jgrul...@redhat.com
  Target Milestone: ---

Created attachment 152382
  --> https://bugs.kde.org/attachment.cgi?id=152382=edit
Openconnect settings page for Fortinet

SUMMARY
I'm unable to use the Fortinet's protocol provided by OpenConnect. I usually
connect to the job's vpn with username and password and a token sent by email
after login.

When configuring such VPN connection there is any field for username and
password so the plugin tries to use a certificate file that, in my case, is not
provided.

I can normally use openconnect from command line:

sudo openconnect --protocol=fortinet MY-GATEWAY --user MY-USERNAME 


STEPS TO REPRODUCE
1. Open Connections Manager Settings
2. Add a "VPN Compatible Fortinet (openconnect)"
3. Edit settings

OBSERVED RESULT
No imput fields for username and password

EXPECTED RESULT
Fields for username and password

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.25.90
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6

ADDITIONAL INFORMATION

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

[frameworks-kcalendarcore] [Bug 457964] Program kalendarac crash

[Giuseppe Della Bianca]

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

Giuseppe Della Bianca  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

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

[kdeconnect] [Bug 446522] Enabling playback multimedia controls on kdeconnect app can totally crash android

[Giuseppe Della Bianca]

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

Giuseppe Della Bianca  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

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

[kdeconnect] [Bug 446522] Enabling playback multimedia controls on kdeconnect app can totally crash android

[Giuseppe Della Bianca]

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

Giuseppe Della Bianca  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

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

[frameworks-kcalendarcore] [Bug 457964] Program kalendarac crash

[Giuseppe Della Bianca]

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

Giuseppe Della Bianca  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

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

[frameworks-kcalendarcore] [Bug 457964] Program kalendarac crash

[Giuseppe Della Bianca]

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

--- Comment #1 from Giuseppe Della Bianca  ---
(gdb) frame 1

QDateTime
KalendarAlarmClient::occurrenceForAlarm(const KCalendarCore::Incidence::Ptr
, const KCalendarCore::Alarm::Ptr , const QDateTime )
const
{
if (!incidence->recurs()) {
return {};
}

// recurring alarms not handled here for simplicity
if (alarm->repeatCount()) {
return {};
}

(gdb) print incidence
$1 = (const KCalendarCore::Incidence::Ptr &) @0x7fffc940: {value = 0x0, d =
0x0}

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

[frameworks-kcalendarcore] [Bug 457964] New: Program kalendarac crash

[Giuseppe Della Bianca]

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

Bug ID: 457964
   Summary: Program kalendarac crash
   Product: frameworks-kcalendarcore
   Version: 5.96.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: gius...@gmail.com
  Target Milestone: ---

Run kalendarac, crashes on 

(gdb) backtrace
#0  KCalendarCore::Incidence::recurs > (this=0x0) < at
/usr/src/debug/kf5-kcalendarcore-5.96.0-1.fc36.x86_64/src/incidence.cpp:605
#1  0x55560c5d in KalendarAlarmClient::occurrenceForAlarm
(this=0x7fffd200, from=..., alarm=..., incidence=...)
at
/usr/src/debug/kf5-akonadi-calendar-22.04.1-1.fc36.x86_64/reminder-daemon/kalendaralarmclient.cpp:281
#2  KalendarAlarmClient::checkAlarms (this=0x7fffd200)
at
/usr/src/debug/kf5-akonadi-calendar-22.04.1-1.fc36.x86_64/reminder-daemon/kalendaralarmclient.cpp:252
#3  0x76ff08c6 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#4  0x77c10106 in Akonadi::EntityTreeModel::collectionPopulated(long
long) () from /lib64/libKF5AkonadiCore.so.5
#5  0x77c20a82 in
Akonadi::EntityTreeModelPrivate::itemFetchJobDone(long long, KJob*) () from
/lib64/libKF5AkonadiCore.so.5
#6  0x76ff08c6 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#7  0x77a20d29 in KJob::result(KJob*, KJob::QPrivateSignal) () from
/lib64/libKF5CoreAddons.so.5
#8  0x77a2634b in KJob::finishJob(bool) () from
/lib64/libKF5CoreAddons.so.5
#9  0x76fe72c4 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#10 0x76fbd228 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#11 0x76fc0594 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#12 0x7700e467 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#13 0x748e3faf in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#14 0x749392c8 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#15 0x748e1940 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#16 0x7700df5a in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#17 0x76fbbc7a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#18 0x76fc3d42 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#19 0xcdeb in main (argc=, argv=)
at
/usr/src/debug/kf5-akonadi-calendar-22.04.1-1.fc36.x86_64/reminder-daemon/kalendaracmain.cpp:53

gdb frame 0

bool Incidence::recurs() const
{
Q_D(const Incidence);
if (d->mRecurrence) {
return d->mRecurrence->recurs();
} else {
return false;
}
}

(gdb) print d
Cannot access memory at address 0x18


Fedora Linux 36
KDE Plasma: 5.25.4
KDE Frameworks: 5.96.0
Qt: 5.15.5
X11
Kernel: 5.18.16-200.fc36.x86_64 (64 bit)

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

[korganizer] [Bug 324592] REQUEST: implementation of copying reminders

[Giuseppe Vinci]

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

--- Comment #9 from Giuseppe Vinci  ---
(In reply to gjditchfield from comment #8)
I have to thank, you and all them, which spend a lot of time to improve KDE
Apps

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

[korganizer] [Bug 324592] REQUEST: implementation of copying reminders

[Giuseppe Vinci]

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

--- Comment #7 from Giuseppe Vinci  ---
(In reply to gjditchfield from comment #6)

> Is this something like what you have in mind?
> 
> - Switch to the Reminders tab of the editor.
> - Right-click on an existing reminder.
> - Choose "Copy" from the pop-up menu.
> - Right-click on empty space in the reminder list (if there is any).
> - Choose "Paste" from the pop-up menu.
> - Click "Modify" to modify the new reminder.

In the version 4.4.10 it was a "Duplicate" button between the "New / Add" and
"Remove" ones in the Reminder tab
As I look at the current Reminder tab, I see, there is place enough for adding
another button in the same manner - maybe between "New" and "Modify". 
Reason for the button allocation:
The user add a complete new reminder (button "New") or duplicate an existent
one (button "Duplicate"). After that he/she maybe needs to edit some details in
the new added reminder (button "Modify").

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

[korganizer] [Bug 324592] REQUEST: implementation of copying reminders

[Giuseppe Vinci]

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

Giuseppe Vinci  changed:

   What|Removed |Added

 CC||giuseppe.vi...@gmx.net

--- Comment #5 from Giuseppe Vinci  ---
#gjditchfi...@acm.org

Which versions do you mind?
I am using now the 5.14.2, that is the newest one on OpenSuse Leap 15.3
with this KOrganizer version is not possible to copy a reminder, which you have
already set, to add another reminder. 
Please inform me, if you need more information, how this implementation should
/ could run (from user point of view!).

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

[plasmashell] [Bug 454007] Panel layout inverted on login

[giuseppe]

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

--- Comment #3 from giuseppe  ---
(In reply to Fushan Wen from comment #2)
> Please try the latest version. It should be fixed already. Unless there are
> other race conditions.

Confirm, fixed.

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

[plasmashell] [Bug 454007] New: panel result inverted

[giuseppe]

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

Bug ID: 454007
   Summary: panel result inverted
   Product: plasmashell
   Version: git-stable-Plasma/5.24
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: giuseppebelluzz...@gmail.com
  Target Milestone: 1.0

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

SUMMARY
The plasma panel appear to be inverted with start menu on the right and try
icon on the left

EXPECTED RESULT
start menu on the left and tray on the 

KDE neon unstable
Plasma 5.24.80
Frameworks: 5.94
Qt 5.15.3

ADDITIONAL INFORMATION
It works as expected, you can normally arrange the panel in the correct
position.
Was tested on live usb and also on Docker

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

[kscreenlocker] [Bug 453741] kscreenlocker_greet crashes in ScreenLocker::UnlockApp::markViewsAsVisible()

[giuseppe]

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

--- Comment #14 from giuseppe  ---
For what matters I could reproduce even on the live of F36, but maybe is Intel
(and Wayland) specific, so if we don't have a very similar hardware it might be
difficult to replicate.

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

[kscreenlocker] [Bug 453741] kscreenlocker_greet crashes in ScreenLocker::UnlockApp::markViewsAsVisible()

[giuseppe]

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

--- Comment #12 from giuseppe  ---
Then it might be Fedora related? It wasn't happening so consistently on F35. As
a workaround for now I'm using X11.

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

[kscreenlocker] [Bug 453741] Lock screen is broken

[giuseppe]

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

--- Comment #10 from giuseppe  ---
Created attachment 148804
  --> https://bugs.kde.org/attachment.cgi?id=148804=edit
coredumpctl after i run the command from bash instead of fish

I thought backtrace was the output when I tried to run the lock screen from
bash. Instead it should be the coredumpctl. This one seems longer of 40 lines
indeed.

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

[kscreenlocker] [Bug 453741] Lock screen is broken

[giuseppe]

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

--- Comment #9 from giuseppe  ---
Seens exact same, just this time i used bash as you suggested

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

[kscreenlocker] [Bug 453741] Lock screen is broken

[giuseppe]

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

--- Comment #7 from giuseppe  ---
/usr/libexec/kscreenlocker_greet --testing
Locked at 1652457928
file:///usr/share/plasma/look-and-feel/org.fedoraproject.fedora.desktop/contents/components/UserList.qml:42:9:
Unable to assign [undefined] to bool
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
file:///usr/share/plasma/look-and-feel/org.fedoraproject.fedora.desktop/contents/components/UserList.qml:42:9:
Unable to assign [undefined] to bool
qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Segmentation fault (core dumped)

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

[kscreenlocker] [Bug 453741] Lock screen is broken

[giuseppe]

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

--- Comment #5 from giuseppe  ---
Additional findings: I have a soundbar attached and powered by the monitor
itself. After I tried a couple of time the screen locker I noticed the soundbar
profile was set off by itself.

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

[kscreenlocker] [Bug 453741] Lock screen is broken

[giuseppe]

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

--- Comment #4 from giuseppe  ---
Created attachment 148801
  --> https://bugs.kde.org/attachment.cgi?id=148801=edit
coredumpctl gdb

this is the coredumpctl. 
About the other question, I just have fish set in use as konsole command, I
didn't do chsh to set it.

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

[kscreenlocker] [Bug 453741] Lock screen is broken

[giuseppe]

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

giuseppe  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED

--- Comment #2 from giuseppe  ---
(In reply to Nate Graham from comment #1)
> What happens if you run `/usr/libexec/kscreenlocker_greet --testing` ? Can
> you do so and paste the output in your terminal window?

It didn't crash this time. But after I turn off the monitor and on again it
didn't ask for my password.

Below the output:
Locked at 1652454987
file:///usr/share/plasma/look-and-feel/org.fedoraproject.fedora.desktop/contents/components/UserList.qml:42:9:
Unable to assign [undefined] to bool
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
file:///usr/share/plasma/look-and-feel/org.fedoraproject.fedora.desktop/contents/components/UserList.qml:42:9:
Unable to assign [undefined] to bool
qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
fish: Job 1, '/usr/libexec/kscreenlocker_gree…' terminated by signal SIGSEGV
(Address boundary error)

It seems the problem was the external monitor itself

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

[kscreenlocker] [Bug 453741] New: Lock screen is broken

[giuseppe]

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

Bug ID: 453741
   Summary: Lock screen is broken
   Product: kscreenlocker
   Version: 5.24.4
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: giuseppebelluzz...@gmail.com
CC: bhus...@gmail.com
  Target Milestone: ---

SUMMARY
Whenever I lock the screen, after my monitor is turned off or even if I turn it
off manually I get this error
"The lock screen is broken and unlocking is not possible anymore ... " with
instructions on how to manually unlock it.


STEPS TO REPRODUCE
1.  Lock the screen
2.  Turn off the monitor
3.  Turn on the monitor

OBSERVED RESULT
Black screen with the error mentioned above

EXPECTED RESULT
Be able to unlock the screen without using a TTY

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 36
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
Before the latest Fedora upgrade it happened just random, now it's constant.

I tried to follow the solution given here:  
https://forum.kde.org/viewtopic.php?f=309=174343=4cb37e2c4fdaed7c15c597e15ec942ca=15
  but it didn't work 

My setup consist of an external monitor used as main and only monitor, external
mouse and keyboard, the laptop is an Ideapad with intel i7 10th gen and Iris
Plus graphics

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

[kwin] [Bug 447705] Flickering in Wayland session when returning from standby

[giuseppe]

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

giuseppe  changed:

   What|Removed |Added

 CC||giuseppebelluzz...@gmail.co
   ||m

--- Comment #11 from giuseppe  ---
Similar problem here, but the flickering is just in the background, if i have a
window opened it isn't affected. It's sufficient to open a dialog menu or
application launcher to make it stop.
Intel core i7 1065g7 and Iris Plus graphics.
Plasma 5.24.2 
KDE Frameworks 5.91
Qt Version 5.15.2

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

[Haruna] [Bug 450493] Haruna flatpak extremely laggy

[giuseppe]

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

--- Comment #15 from giuseppe  ---
(In reply to george fb from comment #14)
Can confirm the beta is working as expected now. I wonder why this wasn't
reported earlier since I don't think it's an uncommon hardware/software setup

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

[Haruna] [Bug 450493] Haruna flatpak extremely laggy

[giuseppe]

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

--- Comment #12 from giuseppe  ---
I just tried with the beta version. So this one works, but the icon is missing
again, even after a reboot.

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

[Haruna] [Bug 450493] Haruna flatpak extremely laggy

[giuseppe]

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

--- Comment #11 from giuseppe  ---
(In reply to george fb from comment #10)
Commit: 660b69c738c735882e4e710f9dcf7d061df2afe85e3ef119706cfb659bbb888a
   Subject: Fix icon (00fdaa32)
  Date: 2021-12-13 04:36:43 +
Result: laggy and slow interface and video 

 Commit: f1fdadab1552454a078cb0f7ee80d8532c86eb8b44f3b1d64f791980e0403edd
   Subject: Update mpv and yt-dlp (b1629295)
  Date: 2021-11-22 14:26:01 +
Result: no icon, not opening

 Commit: d40f0869950b1f32de950ba47278865713cf6d97ed4ad8fbb1c1f6959e6ae89d
   Subject: Update Haruna to 0.7.3 (863e4f83)
  Date: 2021-11-03 19:25:24 +
Result: no icon, not opening

Commit: 2ab077fcc0b674ca764cf53e39439f418dcc16461dd8ea052c36f0704a87708a
   Subject: Update to 0.7.2 (09263d32)
  Date: 2021-09-29 07:48:21 +
Result: works fine

 Commit: a07e4e2d44123d18fd8d06b131cfecc29b5de959e2c4d3182d25b8ae6103836a
   Subject: Update to 0.7.1 (4b460b00)
  Date: 2021-09-16 16:39:25 +
Result: works fine

To be honest I remember it clearly working on my hardware and with Fedora after
the update that brought back the missing icon. It can actually be a problem
that it doesn't play nice with other flatpak runtimes?

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

[Haruna] [Bug 450493] Haruna flatpak extremely laggy

[giuseppe]

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

--- Comment #9 from giuseppe  ---
(In reply to george fb from comment #3)
Sorry I thought it was more common and not really hardware dependent. 

> (In reply to giuseppe from comment #0)
> 
> Have you used it before, other distro or package? Wayland or X11?
I used it a lot before without any problems. 
I've always used it in Wayland either in Manjaro and in Fedora, in Manjaro from
Aur and in Fedora Flatpak (current situation). Always worked until some weeks
before I posted the bug report. 
> What resolution is the file you are trying to play? What is your hardware
The file i try to play is an .mp4 at 512 x 384 but also other files. 
> CPU, GPU (if nvidia which drivers)?
CPU: intel core i7 1065g7 with integrated Iris Plus graphic
> It doesn't work to well on low end hardware
> https://bugs.kde.org/show_bug.cgi?id=442132
> 
> I'm also using the flatpak version and it works without problems.
I tried to delete haruna cache and config in ~/.var/app/org.kde.haruna also
tried to reinstall the Flatpak but nothing worked.
Even if I just open Haruna with no video the whole app is slow

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

[Haruna] [Bug 450493] New: Haruna flatpak extremely laggy

[giuseppe]

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

Bug ID: 450493
   Summary: Haruna flatpak extremely laggy
   Product: Haruna
   Version: 0.7.3
  Platform: Flatpak
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: generic
  Assignee: georgefb...@gmail.com
  Reporter: giuseppebelluzz...@gmail.com
  Target Milestone: ---

SUMMARY
Fresh Fedora 35 KDE install, Haruna from Flatpak stutter and is basically
unusable 


STEPS TO REPRODUCE
1. Install Haruna from Flatpak
2. Play any .mp4 file

OBSERVED RESULT
The whole application is laggy and the video played is so slow that is
impossible to watch

EXPECTED RESULT
Video plays normally and the whole app (i.e. settings or interacting with any
element) should work normally

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 35
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90
Qt Version: 5.15.2

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

[kdevelop] [Bug 449294] New: KDevelop Crash while selecting with the mouse a line

[giuseppe marco randazzo]

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

Bug ID: 449294
   Summary: KDevelop Crash while selecting with the mouse a line
   Product: kdevelop
   Version: 5.6.2
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: gmranda...@gmail.com
  Target Milestone: ---

Application: kdevelop (5.6.2)

Qt Version: 5.15.2
Frameworks Version: 5.88.0
Operating System: Linux 5.15.0-3-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux bookworm/sid
DrKonqi: 5.23.5 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
I was selecting a line of my code and it crashed. 
I was navigating using the scroll of my mouse, then I tried to select and
highlight some part of the code and booom, crash.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault

[KCrash Handler]
#4  0x7f5898765364 in QAccessible::queryAccessibleInterface(QObject*) () at
/lib/x86_64-linux-gnu/libQt5Gui.so.5
#5  0x7f5898765bdf in QAccessibleEvent::accessibleInterface() const () at
/lib/x86_64-linux-gnu/libQt5Gui.so.5
#6  0x7f589876610d in QAccessible::updateAccessibility(QAccessibleEvent*)
() at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#7  0x7f5896672ddd in KateViewInternal::cursorMoved() () at
/lib/x86_64-linux-gnu/libKF5TextEditor.so.5
#8  0x7f5896678967 in KateViewInternal::updateCursor(KTextEditor::Cursor
const&, bool, bool, bool) () at /lib/x86_64-linux-gnu/libKF5TextEditor.so.5
#9  0x7f589667be6e in KateViewInternal::placeCursor(QPoint const&, bool,
bool) () at /lib/x86_64-linux-gnu/libKF5TextEditor.so.5
#10 0x7f589667eef8 in KateViewInternal::mousePressEvent(QMouseEvent*) () at
/lib/x86_64-linux-gnu/libKF5TextEditor.so.5
#11 0x7f5898fcf4be in QWidget::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x7f5898f8d6bf in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x7f5898f951c4 in QApplication::notify(QObject*, QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x7f58982b3b1a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f5898f93cd3 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) ()
at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x7f5898fe858c in  () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x7f5898feb7f5 in  () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7f5898f8d6bf in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7f58982b3b1a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7f589879af77 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#21 0x7f58987711bc in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#22 0x7f588c74e57a in  () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#23 0x7f5894887cdb in g_main_context_dispatch () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7f5894887f88 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7f589488803f in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7f589830b154 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x7f58982b252b in
QEventLoop::exec(QFlags) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x7f58982ba800 in QCoreApplication::exec() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x560085dbb460 in  ()
#30 0x7f5897c547ed in __libc_start_main (main=0x560085db5c90, argc=1,
argv=0x7fff53d144a8, init=, fini=,
rtld_fini=, stack_end=0x7fff53d14498) at ../csu/libc-start.c:332
#31 0x560085dbc13a in _start ()
[Inferior 1 (process 3346) detached]

Possible duplicates by query: bug 448885, bug 446487, bug 423425, bug 399032,
bug 397159.

Reported using DrKonqi

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

[Discover] [Bug 448939] plasma-discover: segmentation fault (5.24 beta version)

[Giuseppe Calà]

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

Giuseppe Calà  changed:

   What|Removed |Added

 CC||gc...@mailbox.org
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Giuseppe Calà  ---
I confirm the fault with discover 5.23.90 packaged in [kde-unstable] in Arch
Linux

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

[kdevelop] [Bug 448885] New: Unespected crash of KDE while clicking on the "Projects" view

[giuseppe marco randazzo]

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

Bug ID: 448885
   Summary: Unespected crash of KDE while clicking on the
"Projects" view
   Product: kdevelop
   Version: 5.6.2
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: gmranda...@gmail.com
  Target Milestone: ---

Application: kdevelop (5.6.2)

Qt Version: 5.15.2
Frameworks Version: 5.88.0
Operating System: Linux 5.15.0-2-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux bookworm/sid
DrKonqi: 5.23.5 [KCrashBackend]

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

I was navigating with mouse my projects to see the different codes.
Then it crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault

[KCrash Handler]
#4  0x7f88f4e236bc in QAccessibleObject::object() const () at
/lib/x86_64-linux-gnu/libQt5Gui.so.5
#5  0x7f88f58980fa in QAccessibleWidget::isValid() const () at
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#6  0x7f88f4e1cbf4 in QAccessibleEvent::accessibleInterface() const () at
/lib/x86_64-linux-gnu/libQt5Gui.so.5
#7  0x7f88f4e1d10d in QAccessible::updateAccessibility(QAccessibleEvent*)
() at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#8  0x7f88f2d29ddd in KateViewInternal::cursorMoved() () at
/lib/x86_64-linux-gnu/libKF5TextEditor.so.5
#9  0x7f88f2d2f967 in KateViewInternal::updateCursor(KTextEditor::Cursor
const&, bool, bool, bool) () at /lib/x86_64-linux-gnu/libKF5TextEditor.so.5
#10 0x7f88f2d32e6e in KateViewInternal::placeCursor(QPoint const&, bool,
bool) () at /lib/x86_64-linux-gnu/libKF5TextEditor.so.5
#11 0x7f88f2d35ef8 in KateViewInternal::mousePressEvent(QMouseEvent*) () at
/lib/x86_64-linux-gnu/libKF5TextEditor.so.5
#12 0x7f88f56864be in QWidget::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x7f88f56446bf in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x7f88f564c1c4 in QApplication::notify(QObject*, QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7f88f496ab1a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7f88f564acd3 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) ()
at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x7f88f569f58c in  () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7f88f56a27f5 in  () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7f88f56446bf in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x7f88f496ab1a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7f88f4e51f77 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#22 0x7f88f4e281bc in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#23 0x7f88e8e1257a in  () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#24 0x7f88f0f3ecdb in g_main_context_dispatch () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7f88f0f3ef88 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7f88f0f3f03f in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7f88f49c2154 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x7f88f496952b in
QEventLoop::exec(QFlags) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x7f88f4971800 in QCoreApplication::exec() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x55e1d636b460 in  ()
#31 0x7f88f430b7ed in __libc_start_main (main=0x55e1d6365c90, argc=1,
argv=0x7ffc672ccd58, init=, fini=,
rtld_fini=, stack_end=0x7ffc672ccd48) at ../csu/libc-start.c:332
#32 0x55e1d636c13a in _start ()
[Inferior 1 (process 2528) detached]

The reporter indicates this bug may be a duplicate of or related to bug 446487.

Possible duplicates by query: bug 446487, bug 423425, bug 399032, bug 397159.

Reported using DrKonqi

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

[Haruna] [Bug 446259] Haruna icon missing (empty)

[giuseppe]

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

giuseppe  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |FIXED

--- Comment #3 from giuseppe  ---
(In reply to george fb from comment #2)
> Should work now without needing to manually change things.

I can confirm. Thank you.

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

[kdeconnect] [Bug 446522] New: Enabling playback multimedia controls on kdeconnect app can totally crash android

[Giuseppe Della Bianca]

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

Bug ID: 446522
   Summary: Enabling playback multimedia controls on kdeconnect
app can totally crash android
   Product: kdeconnect
   Version: 1.8
  Platform: Android
OS: Android 10.x
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: gius...@gmail.com
  Target Milestone: ---

In this condition

Fedora 35
Android 10
kdeconnect 1.18.1
Multimedia control of fedora enabled in kdeconnect, video in fedora playing,
playback controls displayed in android.

After a few minutes that the android screen has been turned off (I assume when
power saving is turned on) android totally crashes.

And it boots up in emergency mode, writing that the data seems corrupted and
therefore booting failed, and writing if you want to try again or return
android to factory conditions.

Trying again to reboot, android works properly.

In some cases, under the same conditions, restarting android, the android UI to
crash continuously.

Disabling fedora's media control in kdeconnect, the kdeconnect app works
correctly (and very well).

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

[Haruna] [Bug 446259] Haruna icon missing (empty)

[giuseppe]

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

giuseppe  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #1 from giuseppe  ---
I solved this little bug just by editing the
/var/lib/flatpak/app/org.kde.haruna/current/active/export/share/applications/org.kde.haruna.desktop
file and changing the icon line with
"/var/lib/flatpak/app/org.kde.haruna/current/active/files/share/icons/hicolor/scalable/apps/haruna.svg"

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

[Discover] [Bug 446392] New: unrelated search results

[giuseppe]

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

Bug ID: 446392
   Summary: unrelated search results
   Product: Discover
   Version: 5.23.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: PackageKit
  Assignee: lei...@leinir.dk
  Reporter: giuseppebelluzz...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
Often, when searching with Discover you won't get related search results. In
example if you search obs you will have a very long list of unrelated packages
(no obs studio isn't there), and after all the packages in the repo it will
list "obs studio" flatpak.
The issue is that the obs studio is found with a simple "dnf search" via
terminal (if you have rpm repositories enabled).


STEPS TO REPRODUCE
1. On Fedora, enable the rpm repositories and also the flathub repo
2. Open discover and search "obs"
3. In alternative to point 2. is possible to type in a terminal
"plasma-discover --backends flatpak-backend,packagekit-backend --search obs"

OBSERVED RESULT
In both cases you won't see obs studio among the first results. And only near
the end of the long list you have one obs studio but is flatpak.  

EXPECTED RESULT
obs studio as first result, and the ability to change the source from flatpak
to repo

SOFTWARE/OS VERSIONS
Fedora 35
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
If you search "obs studio" with discover or "obs\ studio" with the terminal
command written above, the results are more pertinent but still only the
flatpak is shown. 
Bonus: if you search obs studio in the terminal with "appstreamcli search obs
studio" it won't list obs studio as result but blender 
NOTE 
For convenience this was reported with obs studio, but I would expect this
behaviour to affect other packages as well

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

[Haruna] [Bug 446259] New: Haruna icon missing (empty)

[giuseppe]

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

Bug ID: 446259
   Summary: Haruna icon missing (empty)
   Product: Haruna
   Version: 0.7.3
  Platform: Flatpak
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: generic
  Assignee: georgefb...@gmail.com
  Reporter: giuseppebelluzz...@gmail.com
  Target Milestone: ---

SUMMARY

I'm on a fresh install of Fedora KDE, installed Haruna via Discover. It works
but it has no icon

STEPS TO REPRODUCE
1. Open Discover and enable Flathub from the settings
2. Search and install Haruna
3. Reboot
4. Open a video or just search Haruna in your menu

OBSERVED RESULT
Haruna is there but it has no icon

EXPECTED RESULT
Haruna is there with its nice H icon

SOFTWARE/OS VERSIONS 
 Fedora 35
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2

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

[dolphin] [Bug 387455] Column view in Dolphin

[Giuseppe Careri]

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

Giuseppe Careri  changed:

   What|Removed |Added

 CC||giuseppe.g...@gmail.com

--- Comment #6 from Giuseppe Careri  ---
Created attachment 141354
  --> https://bugs.kde.org/attachment.cgi?id=141354=edit
Screenshot of DOlphin's Show in Groups option

As of Dolphin 21.08.1, setting View Mode to Compact and enabling the "Show in
Groups" option divides the content of the folder into columns. (See attached
screenshot)
Maybe this could be a starting point for a miller-columns-style navigation
system?
I have not looked into the source code, I'm just throwing an idea :)

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

[kdeconnect] [Bug 438598] New: [wayland] shared clipboard not working

[giuseppe]

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

Bug ID: 438598
   Summary: [wayland] shared clipboard not working
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: giuseppebelluzz...@gmail.com
  Target Milestone: ---

SUMMARY
When using wayland the shared clipboard function doesn't work at all.

STEPS TO REPRODUCE
1. Be sure kdeconnect "shared clipboard" function already works well under X11
2. Start a new Wayland session
3. Copy some text on pc or on the mobile phone, or both.

OBSERVED RESULT
What is copied on the pc remain on the pc. What is copied on the mobile phone
remain on the mobile phone.
>Bonus: if you have two phones connected on the same pc, when you copy 
>something from phone A it will appear in the clipboard of phone B, but not on 
>pc.

EXPECTED RESULT
When copy something in the phone clipboard should be seen on pc clipboard and
vice versa.

SOFTWARE/OS VERSIONS
OS: Manjaro 21.0.6
KDE Plasma Version: 5.22.0
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2
---
Phone: Huawei P10; EMUI: 9.1.0; Android: 9

ADDITIONAL INFORMATION
It never worked under Wayland even with previous Plasma versions.
It works very well under X11.
(likely unrelated)For some reason the SMS function of KDE connect never worked
for me, even under X11.

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

[plasma-nm] [Bug 436158] New: Fortisslvpn plugin OTP dialog closes too quickly

[Giuseppe Calà]

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

Bug ID: 436158
   Summary: Fortisslvpn plugin OTP dialog closes too quickly
   Product: plasma-nm
   Version: 5.21.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: gc...@mailbox.org
  Target Milestone: ---

Created attachment 137898
  --> https://bugs.kde.org/attachment.cgi?id=137898=edit
fortisslvpn otp dialog

SUMMARY
I configured a FortiSSL Vpn in NetworkManager with One Time Password enabled in
advanced settings. The problem is that the dialog in which I should write the
token pops for less than a second (video included)

STEPS TO REPRODUCE
1. Configure FortiSSL VPN in NetworkManager with OTP authentication
2. Enable the new VPN from the applet

OBSERVED RESULT

The dialog for inserting the token auto-hides/closes suddenly.

EXPECTED RESULT

The dialog should wait for the token.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Archlinux, kernel 5.11.16-arch1-1
(available in About System)
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.81.0
Qt Version: 5.15.2

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

[frameworks-kiconthemes] [Bug 432293] telegram notification counter not working

[giuseppe]

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

--- Comment #5 from giuseppe  ---
(In reply to ariasuni from comment #4)
> I believe this is fixed by:
> https://invent.kde.org/frameworks/breeze-icons/-/merge_requests/81
> 
> This will be available in KDE Frameworks 5.79, which will be released this
> month:
> https://community.kde.org/Schedules/Frameworks
> 
> (I asked on the merge request if it couldn’t be backported to avoid this
> feature be broken for too long for people who won’t get KDE Frameworks 5.79
> soon)

Seems good, I will give a try in a live system as soon as the 5.79 comes out,
thank you. 
This should fix the monochrome icon problem and also give the possibility to
have a message counter on it.

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

[frameworks-kiconthemes] [Bug 432293] telegram notification counter not working

[giuseppe]

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

--- Comment #3 from giuseppe  ---
(In reply to Kai Uwe Broulik from comment #2)
> Ok, so the bug is probably that KIconEngine::name() always returns the input
> name whereas Qt does a check for whether the icon("foo-bar") is actually
> what it got. Since KIconEngine always returns "foo-bar" even if it did a
> fallback to "foo", Qt will always consider it existing. Now this I would say
> is a genuine bug in KIconEngine/KIconLoader.

I don't understand a lot of technical details but it seems to be at a dead end.

This problem came out after telegram changed its behaviour about monochrome
icons, now they only show a dot (as per request from many users with a
monochrome icon theme). It worked perfectly before for normal icons. 

I don't know if can be of interest but if I download the binary from
https://desktop.telegram.org/ it works as intended, even the beta version

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

[frameworks-kiconthemes] [Bug 432293] New: telegram notification counter not working

[giuseppe]

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

Bug ID: 432293
   Summary: telegram notification counter not working
   Product: frameworks-kiconthemes
   Version: 5.78.0
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: cf...@kde.org
  Reporter: giuseppebelluzz...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

PREMISE
I reported this bug on github
(https://github.com/telegramdesktop/tdesktop/issues/10264) and I was referred
to report it here since it seems to be a bug in KDE's kiconthemes framework

SUMMARY
The notification counter for telegram-desktop in the system tray is not
counting unread messages. 

STEPS TO REPRODUCE
1. Install telegram-desktop 2.5.7.
2. open telegram desktop and be sure notifications are enabled
3. receive some messages

OBSERVED RESULT
The icon tray doesn't show any red dot or any number of received messages


EXPECTED RESULT
The notification counter in system-tray should become red and show a number of
received messages


SOFTWARE/OS VERSIONS
Manjaro 20.2.1 + kernel 5.10.11
KDE Plasma Version: Plasma 5.20.5
KDE Frameworks Version: KDE 5.78.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

The bug is that QIcon::hasThemeIcon("telegram-attention-panel") returns true
even when only telegram icon is present in the icon theme.

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

[plasmashell] [Bug 432035] Panel: Blurred Icons and aliased text with very thin panels on a low DPI screen

[Giuseppe Calà]

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

--- Comment #11 from Giuseppe Calà  ---
!318 fixed the issue for me; both 20px and 22px height look fine

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

[kmail2] [Bug 432188] Kmail asks for for gpg passphrase when mail contains encrypted attachments

[Giuseppe Calà]

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

Giuseppe Calà  changed:

   What|Removed |Added

Summary|Kmail asks for for gpg  |Kmail asks for for gpg
   |password when mail contains |passphrase when mail
   |encrypted attachments   |contains encrypted
   ||attachments

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

[kmail2] [Bug 432188] New: Kmail asks for for gpg password when mail contains encrypted attachments

[Giuseppe Calà]

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

Bug ID: 432188
   Summary: Kmail asks for for gpg password when mail contains
encrypted attachments
   Product: kmail2
   Version: 5.16.1
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: gc...@mailbox.org
  Target Milestone: ---

SUMMARY
I own a server whose mysql database is dumped daily and once encrypted with my
public gpg key is sent to my mail; the mail itself _is not signed_. When in
kmail I click on that mail in the messages list, so not trying to open any
attachment, it asks for gpg passphrase. Very annoying...

This happens the first time I open kmail after a reboot and periodically (I
presume gpg-agent is responsibly for this).

STEPS TO REPRODUCE
1. Send a plain text email with a .asc file attached (encrypted with my own
public key)
2. Click on the mail in messages list

OBSERVED RESULT
A popup opens asking to decrypt the mail with gpg passphrase

EXPECTED RESULT
Just show the mail content

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.20
KDE Frameworks Version: 5.78
Qt Version: 5.15.2

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 432035] Panel: Blurred Icons and aliased text

[Giuseppe Calà]

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

--- Comment #6 from Giuseppe Calà  ---
Created attachment 135229
  --> https://bugs.kde.org/attachment.cgi?id=135229=edit
fonts settings

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

[plasmashell] [Bug 432035] Panel: Blurred Icons and aliased text

[Giuseppe Calà]

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

--- Comment #5 from Giuseppe Calà  ---
(In reply to Nate Graham from comment #2)
> Are you using a fractional scale factor? Does it only happen at 22px size?
> What about 20 or 24? Is this s regression from Plasma 5.20?

I'm not using any scale factor (1920x1080 resolution on a 24" monitor)

At 20px same problem, at 24px looks fine.

If of any help: I'm using "Noto Sans 10pt" as system font (image attached)

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

[plasmashell] [Bug 432035] New: Panel: Blurred Icons and aliased text

[Giuseppe Calà]

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

Bug ID: 432035
   Summary: Panel: Blurred Icons and aliased text
   Product: plasmashell
   Version: 5.20.90
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: gc...@mailbox.org
  Target Milestone: 1.0

Created attachment 135129
  --> https://bugs.kde.org/attachment.cgi?id=135129=edit
A panel with height set to 22px

Using a panel height of 22 px makes icons in systray blurry and global menu
text aliased


STEPS TO REPRODUCE
1. Clic dx on a panel and select Edit panel
2. Set an height of 22px
3. Confirm

OBSERVED RESULT
Blurry icons and aliased text

EXPECTED RESULT
sharp icons and text

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.20.90
KDE Frameworks Version: 5.78
Qt Version: 5.15.2

ADDITIONAL INFORMATION

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

[digikam] [Bug 253091] digiKam will not launch

[Giuseppe Vinci]

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

--- Comment #10 from Giuseppe Vinci  ---
This bug is already no more reproducible since long time on my environment.
I actually use the version 6.1.0; but why testing on beta versions?
I think, most of kde users does not work with betas. Or there are now only beta
testers among kde users? ;-)

Have a nice time!

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

[frameworks-kio] [Bug 389723] Plasma crashed

[Giuseppe Di Febbraro]

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

--- Comment #3 from Giuseppe Di Febbraro  ---
Reported cover one year ago. I don't use kdocker now. Thanx

Il ven 31 mag 2019 10:40 Méven Car  ha scritto:

> https://bugs.kde.org/show_bug.cgi?id=389723
>
> Méven Car  changed:
>
>What|Removed |Added
>
> 
>  Status|REPORTED|NEEDSINFO
>  CC||meve...@gmail.com
>  Resolution|--- |WORKSFORME
>
> --- Comment #2 from Méven Car  ---
> I couldn't reproduce with
>
> Operating System: Kubuntu 19.04
> KDE Plasma Version: 5.16.80
> KDE Frameworks Version: 5.59.0
> Qt Version: 5.12.2
> Kernel Version: 5.0.0-15-generic
>
> Does the issue still happen for you Giuseppe ?
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[clazy] [Bug 408038] New: Add a family of checks for "Qt value classes"

[Giuseppe D'Angelo]

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

Bug ID: 408038
   Summary: Add a family of checks for "Qt value classes"
   Product: clazy
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: dange...@gmail.com
CC: smart...@kde.org
  Target Milestone: ---

>From my experience at developing Qt itself (and Qt-based applications), here's
a suggestion for a family of checks.

We need to establish a definition for a "value class". In Qt: any class with a
public copy constructor. Move-only classes can also be considered value classes
but they're very rare in Qt.

The value classes that are interesting for us are either thin abstractions
(QRect, QPoint) or thick abstractions (QString, QFont). The main feat thick
abstractions in Qt are pimpled; thin abstractions have multiple non-pointer
data members right into the class itself. 

(RAII classes, another category of value classes, usually have
pointer/references data members. For more info, cf's Marc Mutz' talk at
MeetingC++. Runtime polymorphic classes shouldn't be copiable in the first
place, so they're not value classes for us.)


So, somehow, a thick abstraction is detectable due to the presence of just one
data member of type QSharedDataPointer / QExplictlySharedDataPointer etc. If
this proves to be hard, we can always have an attribute.


For any value class which is public API (not sure how to enforce that; file
name in which the declaratino appears?), check that:

* QVariant::fromValue(obj); compiles (implying either builtin support in
QVariant and/or Q_DECLARE_METATYPE exists)
* Q_DECLARE_TYPEINFO / QTypeInfo specialization exists for it. Thin classes are
usually primitive, and thick classes are usually movable.
* qDebug() << obj; compiles
* QDataStream ds; ds << obj; compiles
* qHash(obj); compiles (and possibly is noexcept)
* The class has a noexcept member swap 
* A noexcept swap(obj1, obj2) overload in the class' namespace exists
* std::hash{}(obj) compiles (and possibly is noexcept)
* The class is final


For thin abstractions also check that:

* The class itself is NOT exported; only individual, outofline members are
* The class follows the rule of 0
* Constructors are noexcept and constexpr
* Destruction is trivial (= the class is a literal type)
* Any function defined inline is also constexpr; 
* Any function defined inline is also noexcept -- this may give false
positives. In general it's impossible to check due to Lakos' rule; I'd warn
nonetheless and have users annotate with noexcept(false).


For thick abstractions also check that:

* The class is exported
* The class follows the rule of 5 (at the moment Qt cannot implement move
constructors, though; a resolution is coming)

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

[clazy] [Bug 408021] New: Warn if code contains the constant 0x9e3779b9 (hand-rolled boost::hash_combine)

[Giuseppe D'Angelo]

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

Bug ID: 408021
   Summary: Warn if code contains the constant 0x9e3779b9
(hand-rolled boost::hash_combine)
   Product: clazy
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: dange...@gmail.com
CC: smart...@kde.org
  Target Milestone: ---

Check if the code contains the constant "0x9e3779b9".

It's VERY likely someone is hand-rolling QtPrivate::QHashCombine /
boost::hash_combine. Suggest to use those instead.

E.g.
https://codereview.qt-project.org/c/qt/qtbase/+/263115/4/src/network/ssl/qsslerror.cpp#b367

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

[clazy] [Bug 408020] New: Suggest to use addRow instead of newRow+sprintf

[Giuseppe D'Angelo]

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

Bug ID: 408020
   Summary: Suggest to use addRow instead of newRow+sprintf
   Product: clazy
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: dange...@gmail.com
CC: smart...@kde.org
  Target Milestone: ---

Data-driven tests with QTest can use either newRow or addRow to add a new
testdata row. Each data row has a unique data-tag used in logs, testrunners
etc.

Sometimes this data-tag is generated procedurally:

  QTest::newRow(qPrintable(QString("Testing %1").arg(foo))) << foo;

However there's a better solution: QTest::addRow, which natively supports
printf syntax:

  QTest::addRow("Testing %d", foo) << foo;

The idea is that this check should see if newRow is being used with qPrintable
/ QString::asprintf / etc. and suggest addRow instead.

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

[plasma-pa] [Bug 398538] Simultaneous output volume control don't working as default anymore after some update

[Giuseppe Margarita]

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

Giuseppe Margarita  changed:

   What|Removed |Added

   Keywords||reproducible

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

[plasma-pa] [Bug 398538] Simultaneous output volume control don't working as default anymore after some update

[Giuseppe Margarita]

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

--- Comment #6 from Giuseppe Margarita  ---
STEPS TO REPRODUCE
1. You have a pulseaudio sink, let's call it "Stereo Internal Audio", linked to
your sound card and it's the default after a fresh install.
2. Make a new pulseaudio sink, i.e. using PulseEffects, and let's make it the
default sink.
3. Change the volume through keyboard key and PulseEffects default sink is
affected correctly.
4. Let's start a song or a video file and you make sure that the default
PulseEffects sink is used by the application.
5. Change the volume and you will see that PulseEffetcs sink IS NOT affected by
plasma-pa. Volume is changed on the sound card sink: Stereo Internal Audio. You
can also notice that nothing is changed in pulseaudio configuration:
PulseEffects is still the default sink.
6. Stop the reproduction, close the mediaplayer application and change the
volume again. PulseEffects is affected.

OBSERVED RESULT
plasma-pa does not respect the control on the default sink when an audio stream
is reproduced.

EXPECTED RESULT
plasma-pa should always change the volume on the default sink, or at least it
should let you choose the preferred sink to control even if it's not the
default in the pulseaudio config, just like it's done in kmix.

ADDITIONAL INFORMATION
kmix is another volume manager and it lets you choose one sink to control and
volume control always affects that sink even if it's not the default sink.
While the behavior in plasma-pa is clearly a bug because considering that: 

- It does not let you choose a preferred sink to control;
- It lets you switch the default pulseaudio sink changing the pulseaudio
configuration and the sink to be used by all applications

When you set a default sink different from the one associated to the sound card
and reproduce something, it won't control the volume on default sink.

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

[calligrawords] [Bug 310717] Nested lists

[Giuseppe Calà]

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

--- Comment #4 from Giuseppe Calà  ---
Created attachment 116478
  --> https://bugs.kde.org/attachment.cgi?id=116478=edit
sample file

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

[calligrawords] [Bug 310717] Nested lists

[Giuseppe Calà]

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

--- Comment #3 from Giuseppe Calà  ---
Things are slightly changed during these years, but not solved: there are
ordering and indentation errors and rendering errors when reopening the same
file:

here is a screenshot of a sample file, before closing it:

https://i.imgur.com/GKGZzHB.png

As you can see there is too much indentation for level 2 entries, and 4.X items
should start from 1 instead 3.

And here the same file after reopening it:

https://i.imgur.com/piTUX5n.png

All numbering is a mess.

I have attached the sample file.

I'm using Calligra 3.1.0 on Archlinux

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

[plasma-pa] [Bug 398538] Simultaneous output volume control don't working as default anymore after some update

[Giuseppe Margarita]

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

Giuseppe Margarita  changed:

   What|Removed |Added

 CC||giuseppemargar...@gmail.com

--- Comment #4 from Giuseppe Margarita  ---
Hello everyone, same issue reported here:
https://bugs.kde.org/show_bug.cgi?id=400789

The title here has a small mistake. plasma-pa is not changing the default sink,
it's only changing the volume on the first sink (usually the sink linked to the
audio card, i.e. HDMI or Internal Card). In my experience, it was changing
volume on the default sink when nothing was reproduced, but when I play
something, the behavior is the same reported here.

Anyway, you can work around this bug getting rid of plasma-pa and installing
Kmix. Configured in the right way, it can control only one sink chosen by the
user (even a sink not configured as the default). The only lack is that you
can't choose the default sink from the applet, but you can set it from command
line using pacmd set-default-sink.

In your case, set the simultaneous output as the default sink from pacmd and
choose from Kmix to control the simultaneous sink and everything will work.

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

[plasma-pa] [Bug 400789] plasma-pa does not change the volume on the default pulseaudio sink when audio is reproduced

[Giuseppe Margarita]

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

Giuseppe Margarita  changed:

   What|Removed |Added

   Keywords||reproducible

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

[plasma-pa] [Bug 400789] New: plasma-pa does not change the volume on the default pulseaudio sink when audio is reproduced

[Giuseppe Margarita]

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

Bug ID: 400789
   Summary: plasma-pa does not change the volume on the default
pulseaudio sink when audio is reproduced
   Product: plasma-pa
   Version: 5.14.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: applet
  Assignee: now...@gmail.com
  Reporter: giuseppemargar...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
When you change the default pulseudio sink from the one of your sound card to
another (maybe the equalizer or PulseEffetcs), pulseaudio won't control the
volume of the default sink when audio is playing.
It only controls the default sink when no audio is playing.

STEPS TO REPRODUCE
1. You have a pulseaudio sink, let's call it "Stereo Internal Audio", linked to
your sound card and it's the default after a fresh install.
2. Make a new pulseaudio sink, i.e. using PulseEffects, and let's make it the
default sink.
3. Change the volume through keyboard key and PulseEffects default sink is
affected correctly.
4. Let's start a song or a video file and you make sure that the default
PulseEffects sink is used by the application.
5. Change the volume and you will see that PulseEffetcs sink IS NOT affected by
plasma-pa. Volume is changed on the sound card sink: Stereo Internal Audio. You
can also notice that nothing is changed in pulseaudio configuration:
PulseEffects is still the default sink.
6. Stop the reproduction, close the mediaplayer application and change the
volume again. PulseEffects is affected.

OBSERVED RESULT
plasma-pa does not respect the control on the default sink when an audio stream
is reproduced.

EXPECTED RESULT
plasma-pa should always change the volume on the default sink, or at least it
should let you choose the preferred sink to control even if it's not the
default in the pulseaudio config, just like it's done in kmix.

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.14.3
KDE Frameworks Version: 5.51.0
Qt Version: 5.11.2

ADDITIONAL INFORMATION
kmix is another volume manager and it lets you choose one sink to control and
volume control always affects that sink even if it's not the default sink.
While the behavior in plasma-pa is clearly a bug because considering that: 

- It does not let you choose a preferred sink to control;
- It lets you switch the default pulseaudio sink changing the pulseaudio
configuration and the sink to be used by all applications

When you set a default sink different from the one associated to the sound card
and reproduce something, it won't control the volume on default sink.

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

[Heaptrack] [Bug 386923] heaptrack stalls forever in LineReader::getLine

[Giuseppe Bilotta]

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

--- Comment #13 from Giuseppe Bilotta <giuseppe.bilo...@gmail.com> ---
I'm afraid I'm still seeing the same segmentation fault with the Intel
proprietary platform, and only that one.

heaptrack/build [master] $ bin/heaptrack clinfo
heaptrack output will be written to
"/home/oblomov/src/heaptrack/build/heaptrack.clinfo.902.gz"
starting application, this might take some time...
Segmentation fault
heaptrack stats:
allocations:22117
leaked allocations: 13372
temporary allocations:  7908
Heaptrack finished! Now run the following to investigate the data:

  heaptrack --analyze
"/home/oblomov/src/heaptrack/build/heaptrack.clinfo.902.gz"


Running with -d doesn't provide much useful information, because the segfault
is inside the proprietary library:

Thread 1 "clinfo" received signal SIGSEGV, Segmentation fault.
0x757ebbc1 in ?? () from
/opt/intel/opencl-1.2-6.4.0.25/lib64/libintelocl.so
(gdb) bt
#0  0x757ebbc1 in ?? () from
/opt/intel/opencl-1.2-6.4.0.25/lib64/libintelocl.so
#1  0x757692fe in clGetPlatformInfo () from
/opt/intel/opencl-1.2-6.4.0.25/lib64/libintelocl.so
#2  0x779c36d4 in _malloc_clGetPlatformInfo
(plt_info_ptr=plt_info_ptr@entry=0x75768ef0 ,
pid=0x55789f00, cname=cname@entry=2308, sname=)
at ocl_icd_loader.c:298
#3  0x779c3fc4 in _find_and_check_platforms (num_icds=)
at ocl_icd_loader.c:498
#4  __initClIcd () at ocl_icd_loader.c:652
#5  _initClIcd_real () at ocl_icd_loader.c:702
#6  0x779c46ab in _initClIcd () at ocl_icd_loader.c:724
#7  clGetPlatformIDs (num_entries=0, platforms=0x0,
num_platforms=0x7fffe030) at ocl_icd_loader.c:846
#8  0x555640d5 in main (argc=1, argv=0x7fffe188) at
src/clinfo.c:3190

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

[Heaptrack] [Bug 386923] heaptrack stalls forever in LineReader::getLine

[Giuseppe Bilotta]

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

--- Comment #11 from Giuseppe Bilotta <giuseppe.bilo...@gmail.com> ---
I've double-checked against the other platforms, and this time the only one for
which I can reproduce the issue is the proprietary Intel one (in contrast to
the original report, for which I got the stall regardless).

I'm using Debian unstable. The OpenCL ICD dispatcher is ocl-icd-libopencl1
version 2.2.12-1, from the repositories. The Intel OpenCL runtime is version
16.1.1 (aka 6.4.0.25, apparently they have two versioning schemes).

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

[Heaptrack] [Bug 386923] heaptrack stalls forever in LineReader::getLine

[Giuseppe Bilotta]

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

--- Comment #9 from Giuseppe Bilotta <giuseppe.bilo...@gmail.com> ---
Ok, so now what I find is that running clinfo under heaptrack causes a
segfault. I can get some more information if I run `heaptrack -d clinfo`.
Sadly, the segmentation fault happens inside the proprietary Intel OpenCL
platform. I suspect that one of the LD preloads is interfering. The backtrace
is:



#0  0x7fffbb08abc1 in ?? () from
/opt/intel/opencl-1.2-6.4.0.25/lib64/libintelocl.so 
#1  0x7fffbb0082fe in clGetPlatformInfo () from
/opt/intel/opencl-1.2-6.4.0.25/lib64/libintelocl.so 
#2  0x779c26d4 in _malloc_clGetPlatformInfo
(plt_info_ptr=plt_info_ptr@entry=0x7fffbb007ef0 ,
pid=0x55ac0d80, cname=cname@entry=2308, sname=)  
at ocl_icd_loader.c:298
#3  0x779c2fc4 in _find_and_check_platforms (num_icds=)
at ocl_icd_loader.c:498 
#4  __initClIcd () at ocl_icd_loader.c:652  
#5  _initClIcd_real () at ocl_icd_loader.c:702
#6  0x779c36ab in _initClIcd () at ocl_icd_loader.c:724
#7  clGetPlatformIDs (num_entries=0, platforms=0x0,
num_platforms=0x5576ab58 ) at ocl_icd_loader.c:846   
#8  0x55561ffb in main (argc=1, argv=0x7fffe1b8) at
src/clinfo.c:2851

I'm not sure if it's easy to reproduce, but it's probably going to need the
Intel OpenCL ICD and the use of the open-source ocl-icd for libOpenCL.

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

[Heaptrack] [Bug 386923] heaptrack stalls forever in LineReader::getLine

[Giuseppe Bilotta]

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

--- Comment #8 from Giuseppe Bilotta <giuseppe.bilo...@gmail.com> ---
Sorry for not getting back at you earlier. I just tried with the current git
master, building on debian unstable with all dependencies, and I could not
replicate the deadlock either, neither with nor without the very verbose debug
option.

On the other side, I now get the following:

failed to parse line: t 7   
Segmentation fault

Looks like I'll have to investigate some more.

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

[plasmashell] [Bug 389723] New: Plasma crashed

[Giuseppe Di Febbraro]

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

Bug ID: 389723
   Summary: Plasma crashed
   Product: plasmashell
   Version: 5.11.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: am4deuz...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.11.3)

Qt Version: 5.9.1
Frameworks Version: 5.39.0
Operating System: Linux 4.13.0-32-generic x86_64
Distribution: Ubuntu 17.10

-- Information about the crash:
- What I was doing when the application crashed: opened kdocker, when appear
the cross to select the window to minimize, plasma is restarted

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2d2fbc2fc0 (LWP 2834))]

Thread 15 (Thread 0x7f2c54ff9700 (LWP 3165)):
#0  0x7f2d28a9a072 in futex_wait_cancelable (private=,
expected=0, futex_word=0x560d827afc54) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f2d28a9a072 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x560d827afc00, cond=0x560d827afc28) at pthread_cond_wait.c:502
#2  0x7f2d28a9a072 in __pthread_cond_wait (cond=0x560d827afc28,
mutex=0x560d827afc00) at pthread_cond_wait.c:655
#3  0x7f2d298ff6cb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f2c71a47ad5 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f2c71a4bba8 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f2c71a46c8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f2c71a4bc02 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f2c71a46c8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7f2c71a49a6b in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7f2d298fe29d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f2d28a937fc in start_thread (arg=0x7f2c54ff9700) at
pthread_create.c:465
#12 0x7f2d29200b5f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 14 (Thread 0x7f2c557fa700 (LWP 3164)):
#0  0x7f2d28a9a072 in futex_wait_cancelable (private=,
expected=0, futex_word=0x560d827afc54) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f2d28a9a072 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x560d827afc00, cond=0x560d827afc28) at pthread_cond_wait.c:502
#2  0x7f2d28a9a072 in __pthread_cond_wait (cond=0x560d827afc28,
mutex=0x560d827afc00) at pthread_cond_wait.c:655
#3  0x7f2d298ff6cb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f2c71a47ad5 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f2c71a4bba8 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f2c71a46c8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f2c71a4bc02 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f2c71a46c8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7f2c71a49a6b in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7f2d298fe29d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f2d28a937fc in start_thread (arg=0x7f2c557fa700) at
pthread_create.c:465
#12 0x7f2d29200b5f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 13 (Thread 0x7f2c55ffb700 (LWP 3163)):
#0  0x7f2d28a9a072 in futex_wait_cancelable (private=,
expected=0, futex_word=0x560d827afc54) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f2d28a9a072 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x560d827afc00, cond=0x560d827afc28) at pthread_cond_wait.c:502
#2  0x7f2d28a9a072 in __pthread_cond_wait (cond=0x560d827afc28,
mutex=0x560d827afc00) at pthread_cond_wait.c:655
#3  0x7f2d298ff6cb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f2c71a47ad5 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f2c71a4bba8 in  () at

[Heaptrack] [Bug 386923] heaptrack stalls forever in LineReader::getLine

[Giuseppe Bilotta]

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

--- Comment #6 from Giuseppe Bilotta <giuseppe.bilo...@gmail.com> ---
Thanks for the extensive tracking, Milian, I'll find sometime later today to
try the latest git master of heaptrack.

FWIW, I do have the Intel platform available, but I can reproduce the deadlock
by limiting the available platforms to just the Mesa one (using ocl-icd for
libOpenCL and setting OCL_ICD_VENDORS so that only Mesa is found), so I don't
thin Intel's TBB would be at fault in my case. Maybe Mesa does its own alloc
meddling? I'm using mesa 17.2.4-1+b1 packaged in Debian sid.

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

[Heaptrack] [Bug 386923] heaptrack stalls forever in LineReader::getLine

[Giuseppe Bilotta]

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

--- Comment #1 from Giuseppe Bilotta <giuseppe.bilo...@gmail.com> ---
Created attachment 108868
  --> https://bugs.kde.org/attachment.cgi?id=108868=edit
Thread stack on the debuggee (clinfo) after stalling

The backtrace I showed was only relevant to heaptrack itself. I'm attaching
here the output of a `thread apply all bt full` for clinfo after the stall is
achieved. It seems that mesa deadlocks somewhere, possibly due to the heaptrack
preload.

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

[Heaptrack] [Bug 386923] New: heaptrack stalls forever in LineReader::getLine

[Giuseppe Bilotta]

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

Bug ID: 386923
   Summary: heaptrack stalls forever in LineReader::getLine
   Product: Heaptrack
   Version: unspecified
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: m...@milianw.de
  Reporter: giuseppe.bilo...@gmail.com
  Target Milestone: ---

I tried running clinfo under heaptrack, and noticed that it stalls forever.

A backtrace on a stalled case gives:

#0  0x7faa3bbf76c0 in __read_nocancel () at
../sysdeps/unix/syscall-template.S:84
#1  0x7faa3c4855b7 in std::__basic_file::xsgetn(char*, long) () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#2  0x7faa3c4bed50 in std::basic_filebuf::underflow() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#3  0x7faa3c47d049 in std::basic_istream&
std::getline(std::basic_istream&,
std::__cxx11::basic_string&, char) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x55aa3a1be937 in std::getline (__str="R 5017", __is=...) at
/usr/include/c++/6/bits/basic_string.h:5382
#5  LineReader::getLine (in=..., this=0x7ffe0e404470) at
./src/util/linereader.h:45
#6  main () at ./src/interpret/heaptrack_interpret.cpp:360


With some experimenting, it seems that this happens if (and only if?) the Mesa
OpenCL ICD is available. Possible steps to reproduce, on Debian unstable:

* apt-get install ocl-icd-libopencl1 mesa-opencl-icd clinfo
* run heaptrack clinfo

This can be done also in a virtual machine, since it's not necessary for the
Mesa OpenCL ICD to actually expose any OpenCL devices (on my machine it has 0
devices, for example).

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

[phonon-backend-gstreamer] [Bug 381634] gstreamer causes many kde programs crash

[Giuseppe Della Bianca]

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

Giuseppe Della Bianca <b...@adria.it> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #3 from Giuseppe Della Bianca <b...@adria.it> ---
I have redone the update from fedora 23 to 26.
This time there were no gstreamer crashes.

Perhaps in the previous update had remained plasma or gstreamer old file or
library.

Sorry.

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

[Akonadi] [Bug 381636] Clicking Server->Start, the program crash

[Giuseppe Della Bianca]

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

--- Comment #6 from Giuseppe Della Bianca <b...@adria.it> ---
Connection::~Connection()
{
delete mLogFile;
if (mSocket) {
mSocket->disconnect(this);
>>>>mSocket->close();   <<<<<
delete mSocket;
}
}

mSocket is created by a thread and closed by another, this causes an assert
failed

Q_ASSERT_X(currentThread == thr || !thr,

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

[Akonadi] [Bug 381636] Clicking Server->Start, the program crash

[Giuseppe Della Bianca]

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

--- Comment #5 from Giuseppe Della Bianca <b...@adria.it> ---
My knowledge of Qt is less than zero.
I just noticed that QSocketNotifier object data contains abnormal or invalid
values.

The messages

'QSocketNotifier: Invalid socket 12 and type' Read ', disabling ...'

are the first symptom of a problem that is already done.

They seem to have problems using destroyed object, notifications that are still
active while their handler is being destroyed, or perhaps memory overwrite.

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

[Akonadi] [Bug 381636] Clicking Server->Start, the program crash

[Giuseppe Della Bianca]

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

--- Comment #3 from Giuseppe Della Bianca <b...@adria.it> ---
Created attachment 106316
  --> https://bugs.kde.org/attachment.cgi?id=106316=edit
output of akonadikonsole

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

[Akonadi] [Bug 381636] Clicking Server->Start, the program crash

[Giuseppe Della Bianca]

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

--- Comment #2 from Giuseppe Della Bianca <b...@adria.it> ---
Created attachment 106315
  --> https://bugs.kde.org/attachment.cgi?id=106315=edit
gud-akonadikonsole

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

[kio] [Bug 203977] several times is not possible the access data for libsmbclient

[Giuseppe Della Bianca]

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

Giuseppe Della Bianca <b...@adria.it> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

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

[kregexpeditor] [Bug 246607] Patch for fix several crash

[Giuseppe Della Bianca]

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

Giuseppe Della Bianca <b...@adria.it> changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

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

[Akonadi] [Bug 381636] New: Clicking Server->Start, the program crash

[Giuseppe Della Bianca]

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

Bug ID: 381636
   Summary: Clicking Server->Start, the program crash
   Product: Akonadi
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: akonadiconsole
  Assignee: kdepim-b...@kde.org
  Reporter: b...@adria.it
  Target Milestone: ---

Created attachment 106286
  --> https://bugs.kde.org/attachment.cgi?id=106286=edit
strace akonadiconsole

In a fedora 23 updated to 26

akonadiconsole 0.99
KDE Frameworks 5.35.0
Qt 5.7.1
Linux (x86_64) release 4.11.5-300.fc26.x86_64


Clicking Server-> Start, the program crash.

Maybe because of that

write(2, "QSocketNotifier: Socket notifier"..., 84QSocketNotifier: Socket
notifiers cannot be enabled or disabled from another thread

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

[kde] [Bug 381634] New: gstreamer causes many kde programs crash

[Giuseppe Della Bianca]

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

Bug ID: 381634
   Summary: gstreamer causes many kde programs crash
   Product: kde
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: b...@adria.it
  Target Milestone: ---

Created attachment 106283
  --> https://bugs.kde.org/attachment.cgi?id=106283=edit
KOrganizer alarm daemon

In a fedora 23 updated to 26.

An old gstreamer cache causes many kde programs crash (when a dialog box is
shown).

Clearing the gstreamer cache solves the problem.

I suggest inserting a cache invalidation/deletion/rebuild mechanism.

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

[okular] [Bug 362856] [Frameworks] Wrong render resolution, possibly caused by Plasma 5 "Scale Display"

[Giuseppe Ghibò]

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

Giuseppe Ghibò <gh...@mageia.org> changed:

   What|Removed |Added

 CC||gh...@mageia.org

--- Comment #27 from Giuseppe Ghibò <gh...@mageia.org> ---
I'm using the DPI forced to 282 but I get this problems too when using
QT_AUTO_SCREEN_SCALE_FACTOR=1 which I use as default; forcing
QT_AUTO_SCREEN_SCALE_FACTOR=0 before calling okular of course doesn't cause the
loss of resolution but in that case fonts menus and especially widgets (scroll
bars) aren't scaled properly.

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

[Akonadi] [Bug 378336] New: KMail resource crash

[Giuseppe Vinci]

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

Bug ID: 378336
   Summary: KMail resource crash
   Product: Akonadi
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Mixed Maildir resource
  Assignee: kdepim-b...@kde.org
  Reporter: giuseppe.vi...@gmx.net
CC: kram...@kde.org
  Target Milestone: ---

Application: akonadi_mixedmaildir_resource (4.14)
KDE Platform Version: 4.14.30
Qt Version: 4.8.5
Operating System: Linux 3.12.67-64-desktop x86_64
Distribution: "openSUSE 13.1 (Bottle) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I started manual the mixedmaildir resource named "saved-mails"
- Unusual behavior I noticed:
nothing
- Custom settings of the application:
a) I store most of recived mails in the mixedmaildir resource "saved-mails",
which is on another hard drive partition as /home
b) mail inbox is located in ~/.local/share/local-mail/ as Kmail standard

The crash can be reproduced every time.

-- Backtrace:
Application: saved-mails vom Typ KMail-Mailordner
(akonadi_mixedmaildir_resource), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x7f7c2ced24c9 in raise () from /lib64/libc.so.6
#7  0x7f7c2ced3958 in abort () from /lib64/libc.so.6
#8  0x7f7c2d7e1204 in qt_message_output (msgType=,
buf=) at global/qglobal.cpp:2323
#9  0x7f7c30d61352 in ~QDebug (this=0x7ffd72a7df70, __in_chrg=) at /usr/include/QtCore/qdebug.h:85
#10 KMIndexReader::readHeader (this=this@entry=0x7ffd72a7e300,
version=version@entry=0x7ffd72a7e00c) at
/usr/src/debug/kdepim-runtime-4.14.10/resources/mixedmaildir/kmindexreader/kmindexreader.cpp:251
#11 0x7f7c30d61a13 in KMIndexReader::readIndex
(this=this@entry=0x7ffd72a7e300) at
/usr/src/debug/kdepim-runtime-4.14.10/resources/mixedmaildir/kmindexreader/kmindexreader.cpp:323
#12 0x00426d9d in MaildirContext::readIndexData (this=0x2411940) at
/usr/src/debug/kdepim-runtime-4.14.10/resources/mixedmaildir/mixedmaildirstore.cpp:461
#13 0x00436159 in MixedMaildirStore::Private::visit (this=0x25528f0,
job=0x257f6f0) at
/usr/src/debug/kdepim-runtime-4.14.10/resources/mixedmaildir/mixedmaildirstore.cpp:1524
#14 0x00435e2b in MixedMaildirStore::processJob (this=,
job=0x257f6f0) at
/usr/src/debug/kdepim-runtime-4.14.10/resources/mixedmaildir/mixedmaildirstore.cpp:2311
#15 0x7f7c3092b940 in
Akonadi::FileStore::AbstractLocalStore::Private::processJobs (this=0x258b340,
jobs=...) at
/usr/src/debug/kdepim-runtime-4.14.10/resources/shared/filestore/abstractlocalstore.cpp:300
#16 0x7f7c2d8fed68 in QMetaObject::activate (sender=0x2555db0,
m=m@entry=0x7f7c30b45940
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd72a7e7f0)
at kernel/qobject.cpp:3556
#17 0x7f7c3093c362 in Akonadi::FileStore::AbstractJobSession::jobsReady
(this=, _t1=...) at
/usr/src/debug/kdepim-runtime-4.14.10/build/resources/shared/filestore/moc_session_p.cpp:98
#18 0x7f7c3093b43d in runNextJob (this=) at
/usr/src/debug/kdepim-runtime-4.14.10/resources/shared/filestore/sessionimpls.cpp:142
#19 Akonadi::FileStore::FiFoQueueJobSession::qt_static_metacall (_o=0x139e,
_c=5022, _id=6, _a=0x) at
/usr/src/debug/kdepim-runtime-4.14.10/build/resources/shared/filestore/moc_sessionimpls_p.cpp:49
#20 0x7f7c2d8fed68 in QMetaObject::activate (sender=0x2551b70, m=, local_signal_index=, argv=0x0) at kernel/qobject.cpp:3556
#21 0x7f7c2d902f31 in QObject::event (this=0x2551b70, e=) at
kernel/qobject.cpp:1165
#22 0x7f7c2e2f68ac in QApplicationPrivate::notify_helper
(this=this@entry=0x239c070, receiver=receiver@entry=0x2551b70,
e=e@entry=0x7ffd72a7ed60) at kernel/qapplication.cpp:4562
#23 0x7f7c2e2fce70 in QApplication::notify (this=this@entry=0x7ffd72a7f070,
receiver=receiver@entry=0x2551b70, e=e@entry=0x7ffd72a7ed60) at
kernel/qapplication.cpp:4348
#24 0x7f7c2f00d89a in KApplication::notify (this=0x7ffd72a7f070,
receiver=0x2551b70, event=0x7ffd72a7ed60) at
/usr/src/debug/kdelibs-4.14.30/kdeui/kernel/kapplication.cpp:311
#25 0x7f7c2d8eb0ad in QCoreApplication::notifyInternal
(this=0x7ffd72a7f070, receiver=0x2551b70, event=0x7ffd72a7ed60) at
kernel/qcoreapplication.cpp:949
#26 0x7f7c2d91a83c in sendEvent (event=, receiver=) at kernel/qcoreapplication.h:231
#27 QTimerInfoList::activateTimers (this=0x239c9d0) at
kernel/qeventdispatcher_unix.cpp:636
#28 0x7f7c2d917b21 in timerSourceDispatch (source=) at
kernel/qeventdispatcher_glib.cpp:186
#29 0x7f7c290c8316 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#30 0x7f7c290c8668 in ?? () from /usr/lib64/libglib-2.0.so.0
#31 0x7f7c290c870c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#32 0x7f7c2d917d55 in