[plasmashell] [Bug 491895] Plasmashell crashes after switching wireguard VPN connection on
https://bugs.kde.org/show_bug.cgi?id=491895 --- Comment #1 from Michał Goliński --- Created attachment 172748 --> https://bugs.kde.org/attachment.cgi?id=172748&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491895] New: Plasmashell crashes after switching wireguard VPN connection on
https://bugs.kde.org/show_bug.cgi?id=491895 Bug ID: 491895 Summary: Plasmashell crashes after switching wireguard VPN connection on Classification: Plasma Product: plasmashell Version: 6.1.4 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: ecthel...@o2.pl Target Milestone: 1.0 Application: plasmashell (6.1.4) Qt Version: 6.7.2 Frameworks Version: 6.5.0 Operating System: Linux 6.10.5-arch1-1 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.1.4 [CoredumpBackend] -- Information about the crash: After clicking connect on a typical wireguard VPN connection in networkmanager in systemtray, the plasmashell process crashes. This is an up-to-date Arch system, freshly after a reboot. The connection is established properly and plasmashell restarts automatically, so it's a minor nuisance only. Disconnecting runs normally, upon connecting I get the same behaviour (plasmashell crashing). The crash can be reproduced sometimes. -- Backtrace (Reduced): #6 0x71235df3c0af in VDMAbstractItemModelDataType::notify (this=, items=, index=0, count=24, roles=) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qmlmodels/qqmldmabstractitemmodeldata_p.h:136 #7 0x71235df488f3 in QQmlAdaptorModel::notify (this=0x5d6e48872480, items=..., index=0, count=24, roles=, this=, items=, index=, count=, roles=) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qmlmodels/qqmladaptormodel_p.h:127 #8 QQmlDelegateModel::_q_itemsChanged (this=, index=0, count=24, roles=...) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qmlmodels/qqmldelegatemodel.cpp:1462 #9 0x71235df527fd in QQmlDelegateModel::_q_layoutChanged (this=0x5d6e488bdd70, parents=, hint=) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qmlmodels/qqmldelegatemodel.cpp:2092 #10 0x71235df5c8c4 in QQmlDelegateModel::qt_metacall (this=0x5d6e488bdd70, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7ffe93a95300) at /usr/src/debug/qt6-declarative/build/src/qmlmodels/QmlModels_autogen/include/moc_qqmldelegatemodel_p.cpp:439 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 390131] Sorting of folders in folder tree
https://bugs.kde.org/show_bug.cgi?id=390131 Michał Goliński changed: What|Removed |Added Version|5.7.1 |5.21.3 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392167] Newlines in MIME parsing cause S/MIME signature to fail
https://bugs.kde.org/show_bug.cgi?id=392167 Michał Goliński changed: What|Removed |Added Version|5.7.2 |5.21.3 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392167] Newlines in MIME parsing cause S/MIME signature to fail
https://bugs.kde.org/show_bug.cgi?id=392167 Michał Goliński changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Michał Goliński --- Yes, seems to still be the case, exactly as before, saving the same message from inside kmail and from outlook webmail gives extra newlines between mime parts. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 460973] New: yakuake crashed when trying to select text from nvim
https://bugs.kde.org/show_bug.cgi?id=460973
Bug ID: 460973
Summary: yakuake crashed when trying to select text from nvim
Classification: Applications
Product: yakuake
Version: 22.08.2
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: h...@kde.org
Reporter: ecthel...@o2.pl
Target Milestone: ---
Application: yakuake (22.08.2)
Qt Version: 5.15.6
Frameworks Version: 5.99.0
Operating System: Linux 6.0.2-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.26.1 [KCrashBackend]
-- Information about the crash:
yakuake unexpectedly crashed on me, when I've tried to select text from nvim
(with Shift)
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Yakuake (yakuake), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7 0x7f53716a16b3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8 0x7f5371651958 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9 0x7f537163b53d in __GI_abort () at abort.c:79
#10 0x7f53718d2112 in std::__glibcxx_assert_fail
(file=file@entry=0x7f534c2e3570 "/usr/include/c++/12.2.0/bits/stl_vector.h",
line=line@entry=1123, function=function@entry=0x7f534c2e35a0 "std::vector<_Tp,
_Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp =
QVector; _Alloc =
std::allocator >; reference = QVector<"...,
condition=condition@entry=0x7f534c2e3911 "__n < this->size()") at
/usr/src/debug/gcc/libstdc++-v3/src/c++11/debug.cc:60
#11 0x7f534c20e690 in std::vector,
std::allocator > >::operator[] (this=, __n=) at /usr/include/c++/12.2.0/bits/stl_vector.h:1121
#12 std::vector,
std::allocator > >::operator[]
(this=0x7f535c018570, __n=965) at
/usr/include/c++/12.2.0/bits/stl_vector.h:1121
#13 Konsole::Screen::setSelectionEnd (this=0x7f535c018560, x=,
y=, trimTrailingWhitespace=false) at
/usr/src/debug/konsole-22.08.2/src/Screen.cpp:1555
#14 0x7f534c26a153 in Konsole::ScreenWindow::setSelectionEnd
(trimTrailingWhitespace=, line=, column=58,
this=0x55573f03bab0) at /usr/src/debug/konsole-22.08.2/src/ScreenWindow.cpp:145
#15 Konsole::TerminalDisplay::extendSelection (this=this@entry=0x55573ef8cf10,
position=...) at
/usr/src/debug/konsole-22.08.2/src/terminalDisplay/TerminalDisplay.cpp:1425
#16 0x7f534c26ed8a in Konsole::TerminalDisplay::mousePressEvent
(this=0x55573ef8cf10, ev=0x7ffc59617a70) at
/usr/src/debug/konsole-22.08.2/src/terminalDisplay/TerminalDisplay.cpp:1148
#17 0x7f5372baf45b in QWidget::event (this=0x55573ef8cf10,
event=0x7ffc59617a70) at kernel/qwidget.cpp:8656
#18 0x7f5372b78b1c in QApplicationPrivate::notify_helper
(this=this@entry=0x55573e737890, receiver=receiver@entry=0x55573ef8cf10,
e=e@entry=0x7ffc59617a70) at kernel/qapplication.cpp:3637
#19 0x7f5372b7e339 in QApplication::notify (this=,
receiver=, e=0x7ffc59617a70) at kernel/qapplication.cpp:3081
#20 0x7f5371e8cb88 in QCoreApplication::notifyInternal2
(receiver=0x55573ef8cf10, event=0x7ffc59617a70) at
kernel/qcoreapplication.cpp:1064
#21 0x7f5372b7c337 in QApplicationPrivate::sendMouseEvent
(receiver=0x55573ef8cf10, event=0x7ffc59617a70, alienWidget=,
nativeWidget=0x7ffc596182c0, buttonDown=, lastMouseReceiver=...,
spontaneous=true, onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2619
#22 0x7f5372bcd3b5 in QWidgetWindow::handleMouseEvent (this=0x55573f1a3a70,
event=0x7ffc59617dd0) at kernel/qwidgetwindow.cpp:683
#23 0x7f5372bcf15e in QWidgetWindow::event (this=0x55573f1a3a70,
event=0x7ffc59617dd0) at kernel/qwidgetwindow.cpp:300
#24 0x7f5372b78b1c in QApplicationPrivate::notify_helper (this=, receiver=0x55573f1a3a70, e=0x7ffc59617dd0) at
kernel/qapplication.cpp:3637
#25 0x7f5371e8cb88 in QCoreApplication::notifyInternal2
(receiver=0x55573f1a3a70, event=0x7ffc59617dd0) at
kernel/qcoreapplication.cpp:1064
#26 0x7f537233f13c in QGuiApplicationPrivate::processMouseEvent
(e=0x55573ef5daf0) at kernel/qguiapplication.cpp:2285
#27 0x7f5372328985 in QWindowSystemInterface::sendWindowSystemEvents
(flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169
#28 0x7f536c52e5f0 in xcbSourceDispatch (source=) at
/usr/src/debug/qtbase/src/plugins/platforms/xcb/qxcbeventdispatcher.cpp:105
#29 0x7f536ff1881b in g_main_dispatch (context=0x7f5364005010) at
../glib/glib/gmain.c:3444
#30 g_main_context_dispatch (context=0x7f5364005010) at
../glib/glib/gmain.c:4162
#31 0x7f536ff6eec9 in g_main_context_iterate.constprop.0
(context=0x7f5364005010, block=1, dispatch=1, self=) at
../glib/glib/gmain.c:4238
#32 0x7f536ff170d2 in g_main_context_iteration (context=0x7f5364005010,
may_block=1
[kio-extras] [Bug 451226] No thumbnail for EPUB3 files
https://bugs.kde.org/show_bug.cgi?id=451226 --- Comment #2 from Michał Goliński --- Gladly, but I have no idea where to start (e.g., how to get an account at invent.kde.org). -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 451226] New: No thumbnail for EPUB3 files
https://bugs.kde.org/show_bug.cgi?id=451226 Bug ID: 451226 Summary: No thumbnail for EPUB3 files Product: kio-extras Version: 21.12.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Thumbnails and previews Assignee: plasma-b...@kde.org Reporter: ecthel...@o2.pl Target Milestone: --- The thumbnailer for Epub 3.0 does not work properly. The file from IDPF (the spec creators) has no cover in Dolphin, even though one is in the file: https://github.com/IDPF/epub3-samples/releases/download/20170606/epub30-spec.epub STEPS TO REPRODUCE 1. Put the file into Dolphin 2. Enable previews OBSERVED RESULT Generic file icon EXPECTED RESULT Cover from the EPUB file itself. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I have done some debugging using the code from https://github.com/KDE/kio-extras/blob/master/thumbnail/ebookcreator.cpp It seems that coverHref is found properly here: https://github.com/KDE/kio-extras/blob/20f476fabfc3f5c50e514c075cea429f62f59652/thumbnail/ebookcreator.cpp#L157 But then the break on the next line skips the assignment itemHrefs[id] = href (this is ok, as we have already found the proper cover file). Nonetheless, in the end, it's the (now broken) itemHrefs map that is used as the source for final coverHref, not the coverHref variable that was meticulously found before: https://github.com/KDE/kio-extras/blob/20f476fabfc3f5c50e514c075cea429f62f59652/thumbnail/ebookcreator.cpp#L203 I suppose that line 203 should rather read: QByteArray encoded = coverHref.toUtf8(); -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445149] New: Allow audio device switching from the task icon
https://bugs.kde.org/show_bug.cgi?id=445149 Bug ID: 445149 Summary: Allow audio device switching from the task icon Product: plasmashell Version: 5.23.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: ecthel...@o2.pl CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Icons-Only Task Manager and the default Task Manager allow muting an audio playing application, but switching the audio device needs using the icon in dock. It would be great to be able to switch audio devices also from the icon (e.g., from the right-click menu). STEPS TO REPRODUCE 1. Use PipeWire 2. Run any program with audio stream. OBSERVED RESULT Audio can be muted/unmuted on task manager item level, audio device cannot be changed there. EXPECTED RESULT Switch audio device on icon level. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I don't think there was an option like that for PulseAudio in the past, but I am using PipeWire now. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392167] Newlines in MIME parsing cause S/MIME signature to fail
https://bugs.kde.org/show_bug.cgi?id=392167 --- Comment #2 from Michał Goliński --- Created attachment 111554 --> https://bugs.kde.org/attachment.cgi?id=111554&action=edit The same email when save from thunderbird Note that there is no blank line at line 2154 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392167] Newlines in MIME parsing cause S/MIME signature to fail
https://bugs.kde.org/show_bug.cgi?id=392167 Michał Goliński changed: What|Removed |Added CC||ecthel...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392167] Newlines in MIME parsing cause S/MIME signature to fail
https://bugs.kde.org/show_bug.cgi?id=392167 --- Comment #1 from Michał Goliński --- Created attachment 111553 --> https://bugs.kde.org/attachment.cgi?id=111553&action=edit A failing email saved form KMail. Note the spurious newline at line 2157. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392167] New: Newlines in MIME parsing cause S/MIME signature to fail
https://bugs.kde.org/show_bug.cgi?id=392167 Bug ID: 392167 Summary: Newlines in MIME parsing cause S/MIME signature to fail Product: kmail2 Version: 5.7.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-b...@kde.org Reporter: ecthel...@o2.pl Target Milestone: --- KMail mangles newlines in a multipart message. This causes siganture verification to fail. I believe this is caused by parts in multipart messages that do not end with a newline. The attached file shows the problem. It is a message that has the following structure: multipart/signed multipart/mixed multipart/related text/html image/jpeg image/jpeg image/jpeg image/jpeg image/jpeg image/jpeg image/jpeg image/jpeg image/jpeg image/jpeg >> application/pdf application/pkcs7-signature KMail adds a newline after the end boundary of multipart/related and before the boundary of multipart/mixed (in the marked place). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392167] Newlines in MIME parsing cause S/MIME signature to fail
https://bugs.kde.org/show_bug.cgi?id=392167 Michał Goliński changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=332973 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 332973] Kmail fails to recognize the digital signature of DHL, reason kmail fais on nested multipart html messages
https://bugs.kde.org/show_bug.cgi?id=332973 Michał Goliński changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=392167 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 390131] Sorting of folders in folder tree
https://bugs.kde.org/show_bug.cgi?id=390131 --- Comment #1 from Michał Goliński --- Created attachment 110479 --> https://bugs.kde.org/attachment.cgi?id=110479&action=edit Folders sorted by number of emails This is sorted by number of emails. Although the lowest level folders are sorted ok, folder containing other folders are not. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 390131] New: Sorting of folders in folder tree
https://bugs.kde.org/show_bug.cgi?id=390131 Bug ID: 390131 Summary: Sorting of folders in folder tree Product: kmail2 Version: 5.7.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: ecthel...@o2.pl Target Milestone: --- Created attachment 110478 --> https://bugs.kde.org/attachment.cgi?id=110478&action=edit Folders sorted by their size Ordering the list of folders gives really strange results. The attachemnt shows folders sorted according to their sizes. As you can see the list looks (mostly) as sorted lexicographically. But even this isn't exactly true. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 347323] Add support for changing cursor shape with extended DECSCUSR escape sequences
https://bugs.kde.org/show_bug.cgi?id=347323 Michał Goliński changed: What|Removed |Added CC||ecthel...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
