[kwin] [Bug 489849] Overview doesn't show open windows on mirrored display
https://bugs.kde.org/show_bug.cgi?id=489849 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de --- Comment #1 from Leszek Lesner --- Can confirm. First I thought the Desktop is broken. But it appears windows are only shown per screen. Other effects that should stack windows or show them behave the same like (CTRL+F10) for example. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459389] Copy and paste do not work in Wayland when using some text editors in konsole and some applications
https://bugs.kde.org/show_bug.cgi?id=459389 --- Comment #25 from Leszek Lesner --- I narrowed down the issue for me to XWayland clients (apps running in XWayland) suffering from this issue. Restarting XWayland helps there or copying something in a XWayland client to clipboard again to make it able to paste again. For now I fixed my browsers by starting them in Wayland mode (Vivaldi, Chromium & Firefox) and that fixes the issue for me. Maybe others can check if thats the case for them too. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 412722] KOrganizer does not show some events from EWS resource
https://bugs.kde.org/show_bug.cgi?id=412722 --- Comment #20 from Leszek Lesner --- Maybe the other blockedStatusList for declined atendees is blocking it. Try removing that as well and see if it fixes it for you. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 412722] KOrganizer does not show some events from EWS resource
https://bugs.kde.org/show_bug.cgi?id=412722 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de --- Comment #17 from Leszek Lesner --- This patch applying to akonadi-calendar fixes it for me. Why those blocked things cannot be configured is a mystery to me. diff --git a/src/etmcalendar.cpp b/src/etmcalendar.cpp index f662541616cba2651c742038b43f405404802d21..af973fc6ee7f5c6e2a2d278ad44a5fa1612b57ab 100644 --- a/src/etmcalendar.cpp +++ b/src/etmcalendar.cpp @@ -154,7 +154,6 @@ void ETMCalendarPrivate::setupFilteredETM() mCalFilterPartStatusProxyModel = new CalFilterPartStatusProxyModel(this); mCalFilterPartStatusProxyModel->setFilterVirtual(false); QList blockedStatusList; -blockedStatusList << KCalendarCore::Attendee::NeedsAction; blockedStatusList << KCalendarCore::Attendee::Declined; mCalFilterPartStatusProxyModel->setDynamicSortFilter(true); mCalFilterPartStatusProxyModel->setBlockedStatusList(blockedStatusList); -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459389] Copy and paste do not work in Wayland when using some text editors in konsole and some applications
https://bugs.kde.org/show_bug.cgi?id=459389 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de --- Comment #23 from Leszek Lesner --- I think this is still an issue. I tried copying stuff from konsole to chromium or vivaldi. Both should run in wayland and its not always working. Sometimes I have to multiple times copy from konsole for it to even appear in klipper. Maybe it has something to do with tmux running on the terminal but I use the right click copy function or CTRL+Shift+C which should use Konsole's copy process. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 435721] Select appointments from Office 365 not showing in Korganizer
https://bugs.kde.org/show_bug.cgi?id=435721 Leszek Lesner changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from Leszek Lesner --- Its fixed with this commit for me: https://invent.kde.org/pim/akonadi-calendar/-/commit/34d2a59be84708fe4df3b30af4649c2d63d4dcda?merge_request_iid=46 Turns out its another issue altogether. See: https://bugs.kde.org/show_bug.cgi?id=436812 I am setting it as resolved as it seems to be merged already. I compiled akonadi-calendar for my Kubuntu 22.10 + PPA system with the patch linked from above and everything shows up nicely again in Korganizer. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 435721] Select appointments from Office 365 not showing in Korganizer
https://bugs.kde.org/show_bug.cgi?id=435721 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de --- Comment #4 from Leszek Lesner --- I can confirm this. Additionally even if I use davmail reoccuring events do not appear for me. Though same settings with thunderbird mail they appear. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 448460] discover 5.23.90 crashes with segfault on startup
https://bugs.kde.org/show_bug.cgi?id=448460 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de --- Comment #20 from Leszek Lesner --- (In reply to espidev from comment #18) > Strange, I cannot reproduce this, both on my desktop and on my Pinephone. > > Perhaps everyone can try this MR to see if it fixes things? The stacktrace > makes no sense to me... > > https://invent.kde.org/plasma/discover/-/merge_requests/228 This fixes it for me too -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422275] Kwin crashes when using hot corner to switch virtual desktops
https://bugs.kde.org/show_bug.cgi?id=422275
--- Comment #3 from Leszek Lesner ---
Still experiencing this issue occasionally on KWin master.
Here is the Backtrace:
--- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#5 0x7fd190c814ad in KWin::EffectWindow::isOnAllDesktops() const
(this=0x0) at /home/leszek/kde/src/kwin/src/libkwineffects/kwineffects.cpp:815
#6 0x562403cea32f in
KWin::DesktopGridEffect::desktopList(KWin::EffectWindow const*) const
(this=0x562405d909c0, w=0x0) at
/home/leszek/kde/src/kwin/src/effects/desktopgrid/desktopgrid.cpp:1449
#7 0x562403ce2c84 in
KWin::DesktopGridEffect::slotWindowClosed(KWin::EffectWindow*)
(this=0x562405d909c0, w=0x7fd184020ea0) at
/home/leszek/kde/src/kwin/src/effects/desktopgrid/desktopgrid.cpp:448
#8 0x562403cf7914 in QtPrivate::FunctorCall,
QtPrivate::List, void, void
(KWin::DesktopGridEffect::*)(KWin::EffectWindow*)>::call(void
(KWin::DesktopGridEffect::*)(KWin::EffectWindow*), KWin::DesktopGridEffect*,
void**) (f=(void (KWin::DesktopGridEffect::*)(class KWin::DesktopGridEffect *
const, class KWin::EffectWindow *)) 0x562403ce2b9c
,
o=0x562405d909c0, arg=0x7ffdaa5360a0) at
/home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:152
#9 0x562403cf6622 in QtPrivate::FunctionPointer::call,
void>(void (KWin::DesktopGridEffect::*)(KWin::EffectWindow*),
KWin::DesktopGridEffect*, void**) (f=(void (KWin::DesktopGridEffect::*)(class
KWin::DesktopGridEffect * const, class KWin::EffectWindow *)) 0x562403ce2b9c
,
o=0x562405d909c0, arg=0x7ffdaa5360a0) at
/home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:185
#10 0x562403cf468b in QtPrivate::QSlotObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1,
this_=0x562405db8f30, r=0x562405d909c0, a=0x7ffdaa5360a0, ret=0x0) at
/home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:418
#11 0x7fd18f5de853 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffdaa5360a0, r=0x562405d909c0, this=0x562405db8f30) at
../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/kernel/qobjectdefs_impl.h:398
#12 doActivate(QObject*, int, void**) (sender=0x5624053f0b60,
signal_index=12, argv=0x7ffdaa5360a0) at
/home/leszek/kde/src/Qt5/qtbase/src/corelib/kernel/qobject.cpp:3886
#13 0x7fd190c666cb in
KWin::EffectsHandler::windowClosed(KWin::EffectWindow*) (this=0x5624053f0b60,
_t1=0x7fd184020ea0) at
/home/leszek/kde/build/kwin/src/libkwineffects/kwineffects_autogen/EWIEGA46WW/moc_kwineffects.cpp:1631
#14 0x7fd19138642f in
KWin::EffectsHandlerImpl::slotWindowClosed(KWin::Toplevel*, KWin::Deleted*)
(this=0x5624053f0b60, c=0x56240639f3b0, d=0x5624063557e0) at
/home/leszek/kde/src/kwin/src/effects.cpp:560
#15 0x7fd19139d7ce in QtPrivate::FunctorCall,
QtPrivate::List, void, void
(KWin::EffectsHandlerImpl::*)(KWin::Toplevel*, KWin::Deleted*)>::call(void
(KWin::EffectsHandlerImpl::*)(KWin::Toplevel*, KWin::Deleted*),
KWin::EffectsHandlerImpl*, void**) (f=(void (KWin::EffectsHandlerImpl::*)(class
KWin::EffectsHandlerImpl * const, class KWin::Toplevel *, class KWin::Deleted
*)) 0x7fd1913863e0 , o=0x5624053f0b60, arg=0x7ffdaa5362b0) at
/home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:152
#16 0x7fd19139c830 in QtPrivate::FunctionPointer::call,
void>(void (KWin::EffectsHandlerImpl::*)(KWin::Toplevel*, KWin::Deleted*),
KWin::EffectsHandlerImpl*, void**) (f=(void (KWin::EffectsHandlerImpl::*)(class
KWin::EffectsHandlerImpl * const, class KWin::Toplevel *, class KWin::Deleted
*)) 0x7fd1913863e0 , o=0x5624053f0b60, arg=0x7ffdaa5362b0) at
/home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:185
#17 0x7fd19139ab51 in QtPrivate::QSlotObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1,
this_=0x562406039f30, r=0x5624053f0b60, a=0x7ffdaa5362b0, ret=0x0) at
/home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:418
#18 0x7fd18f5de853 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffdaa5362b0, r=0x5624053f0b60, this=0x562406039f30) at
../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/kernel/qobjectdefs_impl.h:398
#19 doActivate(QObject*, int, void**) (sender=0x56240639f3b0,
signal_index=10, argv=0x7ffdaa5362b0) at
/home/leszek/kde/src/Qt5/qtbase/src/corelib/kernel/qobject.cpp:3886
#20 0x7fd1912e001f in KWin::Toplevel::windowClosed(KWin::Toplevel*,
KWin::Deleted*) (this=0x56240639f3b0, _t1=0x56240639f3b0, _t2=0x5624063557e0)
at /home/leszek/kde/build/kwin/src/kwin_autogen/EWIEGA46WW/moc_toplevel.cpp:809
#21 0x7fd191526055 in KWin::X11Client::releaseWindow(bool)
(this=0x56240639f3b0, on_shutdown=false) at
/home/leszek/kde/src/kwin/src/x11client.cpp:269
#22 0x7fd1913a1a78 in
KWin::X11Client::unmapNotifyEvent(xcb_unmap_notify_event_t*)
(this=0x56240639f3b0, e=0x7fd18402b710) at
/home/leszek/kde/src/kwin/src/events.cpp:549
#23 0x7fd1913a1314 in KWin::X11C
[kwin] [Bug 439152] New: Kwin 5.22.2 cannot be compiled against Mesa 18.3 anymore
https://bugs.kde.org/show_bug.cgi?id=439152 Bug ID: 439152 Summary: Kwin 5.22.2 cannot be compiled against Mesa 18.3 anymore Product: kwin Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: leszek.les...@web.de Target Milestone: --- SUMMARY Before commit https://invent.kde.org/plasma/kwin/-/commit/7a48ec6e66f080e8d53fbd63ffcfecd40ecf628c#7a9874a60b0fcdb7da55e6a4fa50bf28a6bc8cf2_154_157 it was possible to be compiled against Mesa 18.3. After the commit it is not possible anymore as the line mention above returns undefined. STEPS TO REPRODUCE 1. Compile Kwin with Mesa 18.3 OBSERVED RESULT 'gbm_format_name_desc' undefined EXPECTED RESULT compiles fine SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.22.2 (available in About System) KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83 Qt Version: 5.15.3 ADDITIONAL INFORMATION Reverting commit https://invent.kde.org/plasma/kwin/-/commit/7a48ec6e66f080e8d53fbd63ffcfecd40ecf628c#7a9874a60b0fcdb7da55e6a4fa50bf28a6bc8cf2 fixes the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435132] Wayland session restarts while dragging windows or alt-tab switching, then several clients crash
https://bugs.kde.org/show_bug.cgi?id=435132 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de --- Comment #6 from Leszek Lesner --- I also had the issue and got the tip to remove "KWinQpaPlugin.so" from the lib folder if it is still there. After that Wayland session runs rock solid again for me. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 403391] crash of akonadi_imap_resource
https://bugs.kde.org/show_bug.cgi?id=403391 --- Comment #28 from Leszek Lesner --- I found a fix for my web.de imap crash. See my comment and patch here. You can try to apply it to your setup and see if it fixes the imap crashes for you too https://bugs.kde.org/show_bug.cgi?id=433117#c1 -- You are receiving this mail because: You are watching all bug changes.
[kimap] [Bug 433117] Kimap crashes constantly on Web.de imap account after a few weeks
https://bugs.kde.org/show_bug.cgi?id=433117 --- Comment #1 from Leszek Lesner --- Created attachment 137793 --> https://bugs.kde.org/attachment.cgi?id=137793&action=edit Patch to fix imapset Q_ASSERT I think I found a fix now. After adding this patch where I adjust the assert I don't get any web.de imap crash anymore. All the other imap accounts run fine after the change aswell. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 403391] crash of akonadi_imap_resource
https://bugs.kde.org/show_bug.cgi?id=403391 --- Comment #27 from Leszek Lesner --- Created attachment 137377 --> https://bugs.kde.org/attachment.cgi?id=137377&action=edit New crash information added by DrKonqi akonadi_imap_resource (5.17.40 (21.07.40)) using Qt 5.15.2 - What I was doing when the application crashed: Again another crash after a few days of Web.de usage. It seems that it does not support a certain Imap feature or so that leads to the crash as I can get new mails if shortly after crash and it auto restarts I hit abort in akonadiconsole for this Imap Ressource. It shows then newly missed unread messages normally and works until I try to restart the imap ressource again. -- Backtrace (Reduced): #5 0x7efe5db5f7bb in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #6 0x7efe5db4a535 in __GI_abort () at abort.c:79 #7 0x7efe5e09fa05 in qt_message_fatal (context=..., message=...) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/global/qlogging.cpp:1914 #8 0x7efe5e09fa05 in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7fff555c09a0, msg=msg@entry=0x7efe5e370ea0 "ASSERT: \"%s\" in file %s, line %d") at /home/leszek/kde/src/Qt5/qtbase/src/corelib/global/qlogging.cpp:893 #9 0x7efe5e09ef23 in qt_assert(char const*, char const*, int) (assertion=, file=, line=) at ../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/global/qlogging.h:90 -- You are receiving this mail because: You are watching all bug changes.
[kimap] [Bug 433117] New: Kimap crashes constantly on Web.de imap account after a few weeks
https://bugs.kde.org/show_bug.cgi?id=433117 Bug ID: 433117 Summary: Kimap crashes constantly on Web.de imap account after a few weeks Product: kimap Version: git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: leszek.les...@web.de Target Milestone: --- SUMMARY My KImap crashes after a few weeks of usage. If I remove my account and readd it it starts working for a few weeks again OBSERVED RESULT Crash EXPECTED RESULT Don't crash SOFTWARE/OS VERSIONS KDE Plasma Version: master KDE Frameworks Version: 5.80 Qt Version: 5.15.2 ADDITIONAL INFORMATION Thats the debug output by dr.konqui Application: WEB.DE Freemail (leszek.lesner) (akonadi_imap_resource), signal: Aborted Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fc8f5612980 (LWP 841011))] [KCrash Handler] #5 0x7fc8fb22c7bb in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #6 0x7fc8fb217535 in __GI_abort () at abort.c:79 #7 0x7fc8fb76ca05 in qt_message_fatal (context=..., message=...) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/global/qlogging.cpp:1914 #8 0x7fc8fb76ca05 in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffd15428460, msg=msg@entry=0x7fc8fba3dea0 "ASSERT: \"%s\" in file %s, line %d") at /home/leszek/kde/src/Qt5/qtbase/src/corelib/global/qlogging.cpp:893 #9 0x7fc8fb76bf23 in qt_assert(char const*, char const*, int) (assertion=, file=, line=) at ../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/global/qlogging.h:90 #10 0x7fc8fe323c65 in KIMAP::ImapSet::add(QVector const&) (this=0x7ffd15428568, values=...) at /home/leszek/kde/src/kimap/src/imapset.cpp:240 #11 0x7fc8fe323b60 in KIMAP::ImapSet::add(long long) (this=0x7ffd15428568, value=-1) at /home/leszek/kde/src/kimap/src/imapset.cpp:231 #12 0x561ab193015f in ChangeItemsFlagsTask::prepareJob(KIMAP::Session*) (this=0x561ab1dff190, session=0x561ab1e1efa0) at /home/leszek/kde/src/kdepim-runtime/resources/imap/changeitemsflagstask.cpp:75 #13 0x561ab1930394 in ChangeItemsFlagsTask::triggerAppendFlagsJob(KIMAP::Session*) (this=0x561ab1dff190, session=0x561ab1e1efa0) at /home/leszek/kde/src/kdepim-runtime/resources/imap/changeitemsflagstask.cpp:97 #14 0x561ab192feb4 in ChangeItemsFlagsTask::onSelectDone(KJob*) (this=0x561ab1dff190, job=0x561ab1da4ad0) at /home/leszek/kde/src/kdepim-runtime/resources/imap/changeitemsflagstask.cpp:56 #15 0x561ab19312b2 in QtPrivate::FunctorCall, QtPrivate::List, void, void (ChangeItemsFlagsTask::*)(KJob*)>::call(void (ChangeItemsFlagsTask::*)(KJob*), ChangeItemsFlagsTask*, void**) (f=(void (ChangeItemsFlagsTask::*)(class ChangeItemsFlagsTask * const, class KJob *)) 0x561ab192fc10 , o=0x561ab1dff190, arg=0x7ffd154288e0) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:152 #16 0x561ab1931232 in QtPrivate::FunctionPointer::call, void>(void (ChangeItemsFlagsTask::*)(KJob*), ChangeItemsFlagsTask*, void**) (f=(void (ChangeItemsFlagsTask::*)(class ChangeItemsFlagsTask * const, class KJob *)) 0x561ab192fc10 , o=0x561ab1dff190, arg=0x7ffd154288e0) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:185 #17 0x561ab193119c in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x561ab1d5e1c0, r=0x561ab1dff190, a=0x7ffd154288e0, ret=0x0) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:418 #18 0x7fc8fb99b66c in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffd154288e0, r=0x561ab1dff190, this=0x561ab1d5e1c0) at ../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/kernel/qobjectdefs_impl.h:398 #19 0x7fc8fb99b66c in doActivate(QObject*, int, void**) (sender=0x561ab1da4ad0, signal_index=6, argv=0x7ffd154288e0) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/kernel/qobject.cpp:3886 #20 0x7fc8fd0aa6f2 in KJob::result(KJob*, KJob::QPrivateSignal) (this=0x561ab1da4ad0, _t1=0x561ab1da4ad0, _t2=...) at /home/leszek/kde/build/kcoreaddons/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:576 #21 0x7fc8fd0a8657 in KJob::finishJob(bool) (this=0x561ab1da4ad0, emitResult=true) at /home/leszek/kde/src/kcoreaddons/src/lib/jobs/kjob.cpp:92 #22 0x7fc8fd0a8da6 in KJob::emitResult() (this=0x561ab1da4ad0) at /home/leszek/kde/src/kcoreaddons/src/lib/jobs/kjob.cpp:296 #23 0x7fc8fe32cae1 in KIMAP::Job::handleErrorReplies(KIMAP::Response const&) (this=0x561ab1da4ad0, response=...) at /home/leszek/kde/src/kimap/src/job.cpp:72 #24 0x7fc8fe34226b in KIMAP::SelectJob::handleResponse(KIMAP::Response const&) (this=0x561ab1da4ad0, response=...) at /home/leszek/kde/src/kimap/src/selectjob.cpp:222 #25 0x7fc8fe345173 in KIMAP::SessionPrivate::responseReceived(KIMAP::Response const&) (this=0x561ab1e1efc0, response=..
[konsole] [Bug 433043] Cannot be compiled with gcc-8.3 anymore
https://bugs.kde.org/show_bug.cgi?id=433043 Leszek Lesner changed: What|Removed |Added Version|unspecified |master -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 433043] New: Cannot be compiled with gcc-8.3 anymore
https://bugs.kde.org/show_bug.cgi?id=433043 Bug ID: 433043 Summary: Cannot be compiled with gcc-8.3 anymore Product: konsole Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: leszek.les...@web.de Target Milestone: --- SUMMARY Compiling fails because of for_each_n is not supported in gcc-8.3 STEPS TO REPRODUCE 1. Try compiling with gcc-8 OBSERVED RESULT Compile fails: https://dpaste.org/ovGQ EXPECTED RESULT Compile succeeds SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian Stable (available in About System) KDE Plasma Version: master KDE Frameworks Version: 5.80 Qt Version: 5.12.5 ADDITIONAL INFORMATION The commit responsible is: https://invent.kde.org/utilities/konsole/-/commit/e4a0c20821aa3fc18bae842df7352629465f5b1b -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 432991] New: Does not compile with gcc 8.3 due to fs being experimental
https://bugs.kde.org/show_bug.cgi?id=432991
Bug ID: 432991
Summary: Does not compile with gcc 8.3 due to fs being
experimental
Product: ksysguard
Version: 5.21.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: libksysguard
Assignee: ksysguard-b...@kde.org
Reporter: leszek.les...@web.de
CC: plasma-b...@kde.org
Target Milestone: ---
SUMMARY
Linking fails when trying to compile with gcc-8.3 as the filesystem extension
is experimental.
STEPS TO REPRODUCE
1. Try compiling with gcc-8.3
OBSERVED RESULT
Linking failure with processcore
EXPECTED RESULT
Links fine
SOFTWARE/OS VERSIONS
Linux: Debian GNU/Linux 10
(available in About System)
KDE Plasma Version: 5.21.80
KDE Frameworks Version: 5.80
Qt Version: 5.12.2
ADDITIONAL INFORMATION
Adding the filesystem target manually to the CMakeLists.txt of processcore
like /usr/lib/gcc/x86_64-linux-gnu/8/libstdc++fs.a fixes the issue
processcore/CMakeLists.txt looks like this then
target_link_libraries(processcore
PUBLIC
Qt::Core
KSysGuard::Formatter
PRIVATE
KF5::I18n
KF5::AuthCore
KF5::CoreAddons
KF5::Service
${ZLIB_LIBRARIES}
+ /usr/lib/gcc/x86_64-linux-gnu/8/libstdc++fs.a
)
See linking error here: https://pastebin.com/6BZ5vdHv
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 403391] crash of akonadi_imap_resource
https://bugs.kde.org/show_bug.cgi?id=403391 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de --- Comment #26 from Leszek Lesner --- I can confirm for my WEB.DE account that suddenly crashes the imap_resource Application: Web.de(2) (akonadi_imap_resource), signal: Aborted Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fdf8a1ee980 (LWP 5236))] [KCrash Handler] #5 0x7fdf8fe077bb in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #6 0x7fdf8fdf2535 in __GI_abort () at abort.c:79 #7 0x7fdf90347a05 in qt_message_fatal (context=..., message=...) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/global/qlogging.cpp:1914 #8 0x7fdf90347a05 in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7fff89de6550, msg=msg@entry=0x7fdf90618ea0 "ASSERT: \"%s\" in file %s, line %d") at /home/leszek/kde/src/Qt5/qtbase/src/corelib/global/qlogging.cpp:893 #9 0x7fdf90346f23 in qt_assert(char const*, char const*, int) (assertion=, file=, line=) at ../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/global/qlogging.h:90 #10 0x7fdf92ef6c65 in KIMAP::ImapSet::add(QVector const&) (this=0x7fff89de6658, values=...) at /home/leszek/kde/src/kimap/src/imapset.cpp:240 #11 0x7fdf92ef6b60 in KIMAP::ImapSet::add(long long) (this=0x7fff89de6658, value=-1) at /home/leszek/kde/src/kimap/src/imapset.cpp:231 #12 0x56001f77315f in ChangeItemsFlagsTask::prepareJob(KIMAP::Session*) (this=0x7fdf6c03e400, session=0x560021298050) at /home/leszek/kde/src/kdepim-runtime/resources/imap/changeitemsflagstask.cpp:75 #13 0x56001f773394 in ChangeItemsFlagsTask::triggerAppendFlagsJob(KIMAP::Session*) (this=0x7fdf6c03e400, session=0x560021298050) at /home/leszek/kde/src/kdepim-runtime/resources/imap/changeitemsflagstask.cpp:97 #14 0x56001f772eb4 in ChangeItemsFlagsTask::onSelectDone(KJob*) (this=0x7fdf6c03e400, job=0x560021299dc0) at /home/leszek/kde/src/kdepim-runtime/resources/imap/changeitemsflagstask.cpp:56 #15 0x56001f7742b2 in QtPrivate::FunctorCall, QtPrivate::List, void, void (ChangeItemsFlagsTask::*)(KJob*)>::call(void (ChangeItemsFlagsTask::*)(KJob*), ChangeItemsFlagsTask*, void**) (f=(void (ChangeItemsFlagsTask::*)(class ChangeItemsFlagsTask * const, class KJob *)) 0x56001f772c10 , o=0x7fdf6c03e400, arg=0x7fff89de69d0) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:152 #16 0x56001f774232 in QtPrivate::FunctionPointer::call, void>(void (ChangeItemsFlagsTask::*)(KJob*), ChangeItemsFlagsTask*, void**) (f=(void (ChangeItemsFlagsTask::*)(class ChangeItemsFlagsTask * const, class KJob *)) 0x56001f772c10 , o=0x7fdf6c03e400, arg=0x7fff89de69d0) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:185 #17 0x56001f77419c in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x5600211e2e70, r=0x7fdf6c03e400, a=0x7fff89de69d0, ret=0x0) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:418 #18 0x7fdf9057666c in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fff89de69d0, r=0x7fdf6c03e400, this=0x5600211e2e70) at ../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/kernel/qobjectdefs_impl.h:398 #19 0x7fdf9057666c in doActivate(QObject*, int, void**) (sender=0x560021299dc0, signal_index=6, argv=0x7fff89de69d0) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/kernel/qobject.cpp:3886 #20 0x7fdf91c8153e in KJob::result(KJob*, KJob::QPrivateSignal) (this=0x560021299dc0, _t1=0x560021299dc0, _t2=...) at /home/leszek/kde/build/kcoreaddons/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:576 #21 0x7fdf91c7f4a3 in KJob::finishJob(bool) (this=0x560021299dc0, emitResult=true) at /home/leszek/kde/src/kcoreaddons/src/lib/jobs/kjob.cpp:92 #22 0x7fdf91c7fbf2 in KJob::emitResult() (this=0x560021299dc0) at /home/leszek/kde/src/kcoreaddons/src/lib/jobs/kjob.cpp:296 #23 0x7fdf92effae1 in KIMAP::Job::handleErrorReplies(KIMAP::Response const&) (this=0x560021299dc0, response=...) at /home/leszek/kde/src/kimap/src/job.cpp:72 #24 0x7fdf92f1526b in KIMAP::SelectJob::handleResponse(KIMAP::Response const&) (this=0x560021299dc0, response=...) at /home/leszek/kde/src/kimap/src/selectjob.cpp:222 #25 0x7fdf92f18173 in KIMAP::SessionPrivate::responseReceived(KIMAP::Response const&) (this=0x560021298070, response=...) at /home/leszek/kde/src/kimap/src/session.cpp:288 #26 0x7fdf92f1ce5e in QtPrivate::FunctorCall, QtPrivate::List, void, void (KIMAP::SessionPrivate::*)(KIMAP::Response const&)>::call(void (KIMAP::SessionPrivate::*)(KIMAP::Response const&), KIMAP::SessionPrivate*, void**) (f=(void (KIMAP::SessionPrivate::*)(class KIMAP::SessionPrivate * const, const struct KIMAP::Response &)) 0x7fdf92f178f8 , o
[gwenview] [Bug 432075] Zoom 100% and back to Fit window broken since spin box commit
https://bugs.kde.org/show_bug.cgi?id=432075 --- Comment #5 from Leszek Lesner --- This seems to fix it for me aswell. Thank you for the quick fix. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 432075] New: Zoom 100% and back to Fit window broken since spin box commit
https://bugs.kde.org/show_bug.cgi?id=432075 Bug ID: 432075 Summary: Zoom 100% and back to Fit window broken since spin box commit Product: gwenview Version: Git (add output of "git log -1 --oneline" to description) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: leszek.les...@web.de Target Milestone: --- SUMMARY Middle clicking or pressing F key to zoom 100% into an image works not when invoking the first time. Only second time. Zoom to fit window shows the same behavior and only works when invoked a second time. Also keys for navigation are not working when zoom to fit window is only invoked once as the image is not fully zoomed out to fit the window. STEPS TO REPRODUCE 1. Open Photo that is bigger than window (and have default fit to window set) 2. Press F or middle mouse click to zoom into image 3. Press again to zoom fit into window OBSERVED RESULT You need to multiple times press F / middle mouse click for the zoom to work. Fit to window zoom out does not really zoom out completely which makes left and right arrow keys not work anymore to switch to the next / previous image. EXPECTED RESULT It should work on first invoke of F / middle mouse click SOFTWARE/OS VERSIONS Linux/KDE Plasma: git master (5.21.80) (available in About System) KDE Plasma Version: 5.21.80 (git master 24.01.2021) KDE Frameworks Version: 5.79 (git master 24.01.2021) Qt Version: 5.15.2 ADDITIONAL INFORMATION The following commit is causing the issue: https://invent.kde.org/graphics/gwenview/-/commit/2cdaca95c1303c69466917398ef6e47b0f3de920 Reverting it fixes the issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kservice] [Bug 429593] KBuildSycoca loop causes hangs
https://bugs.kde.org/show_bug.cgi?id=429593 Leszek Lesner changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||leszek.les...@web.de Ever confirmed|0 |1 --- Comment #10 from Leszek Lesner --- Can confirm -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 429602] New: Crashes on starting ASSERT: "!subDocIds.isEmpty()" message
https://bugs.kde.org/show_bug.cgi?id=429602 Bug ID: 429602 Summary: Crashes on starting ASSERT: "!subDocIds.isEmpty()" message Product: frameworks-baloo Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: stefan.bru...@rwth-aachen.de Reporter: leszek.les...@web.de Target Milestone: --- SUMMARY Baloo crashes on start for me (version from master 25.11.2020) STEPS TO REPRODUCE 1. Start baloo OBSERVED RESULT baloo_file crashes EXPECTED RESULT it runs fine SOFTWARE/OS VERSIONS Linux/KDE Plasma: master (available in About System) KDE Plasma Version: master KDE Frameworks Version: master Qt Version: 5.15.2 ADDITIONAL INFORMATION Application: baloo_file (baloo_file), signal: Aborted Content of s_kcrashErrorMessage: (null) [KCrash Handler] #5 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #6 0x7fbaa1ed0535 in __GI_abort () at abort.c:79 #7 0x7fbaa249fa05 in qt_message_fatal (context=..., message=...) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/global/qlogging.cpp:1914 #8 QMessageLogger::fatal (this=this@entry=0x7fba9c86b6f0, msg=msg@entry=0x7fbaa2770ea0 "ASSERT: \"%s\" in file %s, line %d") at /home/leszek/kde/src/Qt5/qtbase/src/corelib/global/qlogging.cpp:893 #9 0x7fbaa249ef23 in qt_assert (assertion=, file=, line=) at ../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/global/qlogging.h:90 #10 0x7fbaa2aef7c5 in Baloo::IdTreeDB::put (this=0x7fba9c86b810, docId=859899, subDocIds=...) at /home/leszek/kde/src/baloo/src/engine/idtreedb.cpp:50 #11 0x7fbaa2ae8f35 in Baloo::DocumentUrlDB::updateUrl (this=0x7fba9c86b8e0, id=55169099730322179, parentId=55169099730322179, url=...) at /home/leszek/kde/src/baloo/src/engine/documenturldb.cpp:119 #12 0x7fbaa2b08ba4 in Baloo::WriteTransaction::replaceDocument (this=0x7f7a900122e0, doc=..., operations=...) at /home/leszek/kde/src/baloo/src/engine/writetransaction.cpp:248 #13 0x7fbaa2b01f6c in Baloo::Transaction::replaceDocument (this=0x7fba9c86ba60, doc=..., operations=...) at /home/leszek/kde/src/baloo/src/engine/transaction.cpp:261 #14 0x5624b1ef4176 in Baloo::UnindexedFileIndexer::run (this=0x5624b30131e0) at /home/leszek/kde/src/baloo/src/file/unindexedfileindexer.cpp:55 #15 0x7fbaa24db931 in QThreadPoolThread::run (this=0x5624b38f3c80) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/thread/qthreadpool.cpp:100 #16 0x7fbaa24d875d in QThreadPrivate::start (arg=0x5624b38f3c80) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/thread/qthread_unix.cpp:329 #17 0x7fbaa0b4efa3 in start_thread (arg=) at pthread_create.c:486 #18 0x7fbaa1fa74cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 #1 0x7fba9e81b136 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fba9e81b25c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbaa26ef36b in QEventDispatcherGlib::processEvents (this=0x7fba98000b20, flags=...) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:425 #4 0x7fbaa269a853 in QEventLoop::exec (this=this@entry=0x7fba9d411d10, flags=..., flags@entry=...) at ../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/global/qflags.h:141 #5 0x7fbaa24d75b6 in QThread::exec (this=this@entry=0x7fbaa2bbad80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/global/qflags.h:121 #6 0x7fbaa2b3e4e5 in QDBusConnectionManager::run (this=0x7fbaa2bbad80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at /home/leszek/kde/src/Qt5/qtbase/src/dbus/qdbusconnection.cpp:179 #7 0x7fbaa24d875d in QThreadPrivate::start (arg=0x7fbaa2bbad80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/thread/qthread_unix.cpp:329 #8 0x7fbaa0b4efa3 in start_thread (arg=) at pthread_create.c:486 #9 0x7fbaa1fa74cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 #1 0x7fba9e81b136 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fba9e81b25c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbaa26ef36b in QEventDispatcherGlib::processEvents (this=0x5624b2f7f890, flags=...) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:425 #4 0x7fbaa269a853 in QEventLoop::exec (this=this@entry=0x7ffedda11790, flags=..., flags@entry=...) at ../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/global/qflags.h:141 #5 0x7fbaa26a26cc in QCoreApplication::exec () at ../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/global/qflags.h:121 #6 0x5624b1edfb3f in main (argc=1, argv=0x7ffedda11bd8) at /home
[kmail2] [Bug 429327] New: KMail crashes when trying to open settings (latest KF5)
https://bugs.kde.org/show_bug.cgi?id=429327 Bug ID: 429327 Summary: KMail crashes when trying to open settings (latest KF5) Product: kmail2 Version: 5.15.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: leszek.les...@web.de Target Milestone: --- SUMMARY KMail crashes when opening settings with latest git master KF5 STEPS TO REPRODUCE 1. Click on settings 2. Click on configure kmail OBSERVED RESULT KMail crashes. EXPECTED RESULT Settings open SOFTWARE/OS VERSIONS Linux/KDE Plasma: master (available in About System) KDE Plasma Version: master KDE Frameworks Version: master Qt Version: 5.15.2 ADDITIONAL INFORMATION Application: KMail (kmail), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [KCrash Handler] #5 0x7f259ba6ccbe in KPluginFactory::d_func (this=0x0) at /home/leszek/kde/src/kcoreaddons/src/lib/plugin/kpluginfactory.h:375 #6 0x7f259ba6b902 in KPluginFactory::setMetaData (this=0x0, metaData=...) at /home/leszek/kde/src/kcoreaddons/src/lib/plugin/kpluginfactory.cpp:46 #7 0x7f259ba6ef2c in KPluginLoader::factory (this=0x7ffde3c3b0c0) at /home/leszek/kde/src/kcoreaddons/src/lib/plugin/kpluginloader.cpp:113 #8 0x7f2597ecc396 in KService::createInstance (this=0x56445ee339e0, parentWidget=0x0, parent=0x56445ee39430, args=..., error=0x7ffde3c3b248) at /opt/plasma5/include/KF5/KService/kservice.h:541 #9 0x7f2597ecbabe in KService::createInstance (this=0x56445ee339e0, parent=0x56445ee39430, args=..., error=0x7ffde3c3b248) at /opt/plasma5/include/KF5/KService/kservice.h:520 #10 0x7f2597eca2be in KCModuleLoader::loadModule (mod=..., report=KCModuleLoader::Inline, parent=0x56445ee39430, args=...) at /home/leszek/kde/src/kcmutils/src/kcmoduleloader.cpp:108 #11 0x7f2597ed91c4 in KCModuleProxyPrivate::loadModule (this=0x56445ee39670) at /home/leszek/kde/src/kcmutils/src/kcmoduleproxy.cpp:81 #12 0x7f2597ed8d44 in KCModuleProxy::realModule (this=0x56445ee39430) at /home/leszek/kde/src/kcmutils/src/kcmoduleproxy.cpp:54 #13 0x7f2597ed5f1f in KCMultiDialog::addModule (this=0x56445ed96dd0, moduleInfo=..., parentItem=0x0, args=...) at /home/leszek/kde/src/kcmutils/src/kcmultidialog.cpp:482 #14 0x7f2597ed5ad3 in KCMultiDialog::addModule (this=0x56445ed96dd0, path=..., args=...) at /home/leszek/kde/src/kcmutils/src/kcmultidialog.cpp:446 #15 0x7f25a50b8b65 in ConfigureDialog::ConfigureDialog (this=0x56445ed96dd0, parent=0x0, modal=false) at /home/leszek/kde/src/kmail/src/configuredialog/configuredialog.cpp:41 #16 0x7f25a4ff1983 in KMKernel::slotShowConfigurationDialog (this=0x7ffde3c3cb90) at /home/leszek/kde/src/kmail/src/kmkernel.cpp:1241 #17 0x7f25a4fde623 in QtPrivate::FunctorCall, QtPrivate::List<>, void, void (KMKernel::*)()>::call(void (KMKernel::*)(), KMKernel*, void**) (f=(void (KMKernel::*)(class KMKernel * const)) 0x7f25a4ff18fe , o=0x7ffde3c3cb90, arg=0x7ffde3c3bdf0) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:152 #18 0x7f25a4fddfd6 in QtPrivate::FunctionPointer::call, void>(void (KMKernel::*)(), KMKernel*, void**) (f=(void (KMKernel::*)(class KMKernel * const)) 0x7f25a4ff18fe , o=0x7ffde3c3cb90, arg=0x7ffde3c3bdf0) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:185 #19 0x7f25a4fdd1d6 in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x564456621680, r=0x7ffde3c3cb90, a=0x7ffde3c3bdf0, ret=0x0) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:418 #20 0x7f259a63d66c in QtPrivate::QSlotObjectBase::call (a=0x7ffde3c3bdf0, r=0x7ffde3c3cb90, this=0x564456621680) at ../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/kernel/qobjectdefs_impl.h:398 #21 doActivate (sender=0x56445660bdc0, signal_index=4, argv=0x7ffde3c3bdf0) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/kernel/qobject.cpp:3886 #22 0x7f259a637982 in QMetaObject::activate (sender=sender@entry=0x56445660bdc0, m=m@entry=0x7f259b7e7180 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffde3c3bdf0) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/kernel/qobject.cpp:3946 #23 0x7f259b322242 in QAction::triggered (this=this@entry=0x56445660bdc0, _t1=) at .moc/moc_qaction.cpp:376 #24 0x7f259b324626 in QAction::activate (this=0x56445660bdc0, event=) at /home/leszek/kde/src/Qt5/qtbase/src/widgets/kernel/qaction.cpp:1161 #25 0x7f259b48fe2c in QMenuPrivate::activateCausedStack (this=this@entry=0x564456789230, causedStack=..., action=action@entry=0x56445660bdc0, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at /home/leszek/kde/src/Qt5/qtbase/src/widgets/widgets/qmenu.cpp:1384 #26 0x7f259b496e80 in QMenuPrivate::activateAction (this=this@entry=0x564456789230, action=action@entry=0x5
[Discover] [Bug 429225] New: discover cannot be compiled against older appstream (bump required version)
https://bugs.kde.org/show_bug.cgi?id=429225 Bug ID: 429225 Summary: discover cannot be compiled against older appstream (bump required version) Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: leszek.les...@web.de CC: aleix...@kde.org Target Milestone: --- SUMMARY Dependency for Appstream is too low. Does not compile with 0.12.5 STEPS TO REPRODUCE 1. Try compiling discover with appstream 0.12.5 OBSERVED RESULT error: 'class AppStream::Pool' has no member named 'lastError' EXPECTED RESULT Compile fine SOFTWARE/OS VERSIONS Linux/KDE Plasma: master (available in About System) KDE Plasma Version: master KDE Frameworks Version: master Qt Version: 5.15.2 ADDITIONAL INFORMATION Changing the requirement to 0.12.8 would be advises. This seems to be the lowest version it compiles correctly without above error. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428374] Dolphin crashes when typing in filter bar in specific folder
https://bugs.kde.org/show_bug.cgi?id=428374 --- Comment #15 from Leszek Lesner --- Can still confirm that typing to quickly in filter bar sometimes crashes dolphin. Here my backtrace: Application: Dolphin (dolphin), signal: Aborted Content of s_kcrashErrorMessage: (null) [KCrash Handler] #5 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #6 0x7faa07387535 in __GI_abort () at abort.c:79 #7 0x7faa0793fa05 in qt_message_fatal (context=..., message=...) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/global/qlogging.cpp:1914 #8 QMessageLogger::fatal (this=this@entry=0x7ffdfc211140, msg=msg@entry=0x7faa07c10ea0 "ASSERT: \"%s\" in file %s, line %d") at /home/leszek/kde/src/Qt5/qtbase/src/corelib/global/qlogging.cpp:893 #9 0x7faa0793ef23 in qt_assert (assertion=, file=, line=) at ../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/global/qlogging.h:90 #10 0x7faa0a2c032c in KItemListView::slotItemsRemoved (this=0x5595aebfc950, itemRanges=...) at /home/leszek/kde/src/dolphin/src/kitemviews/kitemlistview.cpp:1199 #11 0x7faa0a274eaf in KFileItemListView::slotItemsRemoved (this=0x5595aebfc950, itemRanges=...) at /home/leszek/kde/src/dolphin/src/kitemviews/kfileitemlistview.cpp:339 #12 0x7faa0a2cf3d6 in QtPrivate::FunctorCall, QtPrivate::List, void, void (KItemListView::*)(KItemRangeList const&)>::call (f=&virtual table offset 536, o=0x5595aebfc950, arg=0x7ffdfc211450) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:152 #13 0x7faa0a2ce6c2 in QtPrivate::FunctionPointer::call, void> (f=&virtual table offset 536, o=0x5595aebfc950, arg=0x7ffdfc211450) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:185 #14 0x7faa0a2cd633 in QtPrivate::QSlotObject, void>::impl (which=1, this_=0x5595aec0ff30, r=0x5595aebfc950, a=0x7ffdfc211450, ret=0x0) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:418 #15 0x7faa07b6e66c in QtPrivate::QSlotObjectBase::call (a=0x7ffdfc211450, r=0x5595aebfc950, this=0x5595aec0ff30) at ../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/kernel/qobjectdefs_impl.h:398 #16 doActivate (sender=0x5595aec7e050, signal_index=4, argv=0x7ffdfc211450) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/kernel/qobject.cpp:3886 #17 0x7faa0a265e8b in KItemModelBase::itemsRemoved (this=0x5595aec7e050, _t1=...) at /home/leszek/kde/build/dolphin/src/dolphinprivate_autogen/Z3MQH7AOBD/moc_kitemmodelbase.cpp:253 #18 0x7faa0a27f6fa in KFileItemModel::removeItems (this=0x5595aec7e050, itemRanges=..., behavior=KFileItemModel::KeepItemData) at /home/leszek/kde/src/dolphin/src/kitemviews/kfileitemmodel.cpp:1319 #19 0x7faa0a27d126 in KFileItemModel::applyFilters (this=0x5595aec7e050) at /home/leszek/kde/src/dolphin/src/kitemviews/kfileitemmodel.cpp:706 #20 0x7faa0a27cec4 in KFileItemModel::setNameFilter (this=0x5595aec7e050, nameFilter=...) at /home/leszek/kde/src/dolphin/src/kitemviews/kfileitemmodel.cpp:660 #21 0x7faa0a30ccff in DolphinView::setNameFilter (this=0x5595ae781cb0, nameFilter=...) at /home/leszek/kde/src/dolphin/src/views/dolphinview.cpp:484 #22 0x7faa0a44eb78 in DolphinViewContainer::setNameFilter (this=0x5595aec3a4e0, nameFilter=...) at /home/leszek/kde/src/dolphin/src/dolphinviewcontainer.cpp:667 #23 0x7faa0a452969 in QtPrivate::FunctorCall, QtPrivate::List, void, void (DolphinViewContainer::*)(QString const&)>::call (f=(void (DolphinViewContainer::*)(class DolphinViewContainer * const, const class QString &)) 0x7faa0a44eb3c , o=0x5595aec3a4e0, arg=0x7ffdfc2117d0) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:152 #24 0x7faa0a45248a in QtPrivate::FunctionPointer::call, void> (f=(void (DolphinViewContainer::*)(class DolphinViewContainer * const, const class QString &)) 0x7faa0a44eb3c , o=0x5595aec3a4e0, arg=0x7ffdfc2117d0) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:185 #25 0x7faa0a451a43 in QtPrivate::QSlotObject, void>::impl (which=1, this_=0x5595aebc4320, r=0x5595aec3a4e0, a=0x7ffdfc2117d0, ret=0x0) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:418 #26 0x7faa07b6e66c in QtPrivate::QSlotObjectBase::call (a=0x7ffdfc2117d0, r=0x5595aec3a4e0, this=0x5595aebc4320) at ../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/kernel/qobjectdefs_impl.h:398 #27 doActivate (sender=0x5595aeb984a0, signal_index=7, argv=0x7ffdfc2117d0) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/kernel/qobject.cpp:3886 #28 0x7faa0a4b255b in FilterBar::filterChanged (this=0x5595aeb984a0, _t1=...) at /home/leszek/kde/build/dolphin/src/dolphinstatic_autogen/A7DZ2KMSNA/moc_filterbar.cpp:174 #29 0x7faa0a45f33b in QtPrivate::FunctorCall, QtPrivate::List, void, void (FilterBar::*)(QString const&)>::call (f=(void (FilterBar::*)(class FilterBar * const, const class QString &)) 0x7faa0a4b250c , o=0x5595aeb984a0, arg=0x7ffdfc211980) at /home/leszek/kde/qt5/include/QtCore/qobjectd
[plasmashell] [Bug 428241] plasmashell crashes when notification closes
https://bugs.kde.org/show_bug.cgi?id=428241 Leszek Lesner changed: What|Removed |Added Resolution|--- |UPSTREAM Status|CONFIRMED |RESOLVED --- Comment #15 from Leszek Lesner --- Tested the linked patch for Qt 5.15 (https://codereview.qt-project.org/c/qt/qtdeclarative/+/319750) Only applying this to my 5.15.2 base and rerun my kdeconnect ping test showed this really fixed the issue. So it is an upstream issue apparently that has been fixed and hopefully will land in 5.15.2 before the release. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428374] Dolphin crashes when typing in filter bar in specific folder
https://bugs.kde.org/show_bug.cgi?id=428374 --- Comment #8 from Leszek Lesner --- Yes. Master build of dolphin and it is the version running -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428374] Dolphin crashes when typing in filter bar in specific folder
https://bugs.kde.org/show_bug.cgi?id=428374 --- Comment #6 from Leszek Lesner --- Used the filter function in my plasma master installation path plasmoids folder to search for "sys" as soon as I type in the y it crashes -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428374] Dolphin crashes when typing in filter bar in specific folder
https://bugs.kde.org/show_bug.cgi?id=428374 --- Comment #4 from Leszek Lesner --- I searched a bit more and found the commit that breaks it for me: https://invent.kde.org/system/dolphin/-/commit/a24327cd50ef17b953ecb908d260b73460158107 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428241] plasmashell crashes when notification closes
https://bugs.kde.org/show_bug.cgi?id=428241 --- Comment #9 from Leszek Lesner --- I can constantly reproduce it by using kdeconnect and sending a ping message from my phone to laptop. If I don't touch the message after the timeout of the message ran out it crashes plasma. If I touch the message and halt the timer with my mouse and then let it run again by hovering over something else. I don't see the issue. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428374] Dolphin crashes when typing in filter bar in specific folder
https://bugs.kde.org/show_bug.cgi?id=428374 Leszek Lesner changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #3 from Leszek Lesner --- Apparently not really fixed. Had it fixed for the other it failed before but now I have this issue again in a completely different folder. Here is the debug output: Application: Dolphin (dolphin), signal: Aborted Content of s_kcrashErrorMessage: (null) [KCrash Handler] #5 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #6 0x7fd0fb694535 in __GI_abort () at abort.c:79 #7 0x7fd0fbc4ca05 in qt_message_fatal (context=..., message=...) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/global/qlogging.cpp:1914 #8 QMessageLogger::fatal (this=this@entry=0x7ffc16e66e80, msg=msg@entry=0x7fd0fbf1dea0 "ASSERT: \"%s\" in file %s, line %d") at /home/leszek/kde/src/Qt5/qtbase/src/corelib/global/qlogging.cpp:893 #9 0x7fd0fbc4bf23 in qt_assert (assertion=, file=, line=) at ../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/global/qlogging.h:90 #10 0x7fd0fe5ccdd2 in KItemListView::slotItemsRemoved (this=0x55cdc6621d80, itemRanges=...) at /home/leszek/kde/src/dolphin/src/kitemviews/kitemlistview.cpp:1199 #11 0x7fd0fe581bcb in KFileItemListView::slotItemsRemoved (this=0x55cdc6621d80, itemRanges=...) at /home/leszek/kde/src/dolphin/src/kitemviews/kfileitemlistview.cpp:309 #12 0x7fd0fe5dbe7e in QtPrivate::FunctorCall, QtPrivate::List, void, void (KItemListView::*)(KItemRangeList const&)>::call (f=&virtual table offset 536, o=0x55cdc6621d80, arg=0x7ffc16e67190) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:152 #13 0x7fd0fe5db16a in QtPrivate::FunctionPointer::call, void> (f=&virtual table offset 536, o=0x55cdc6621d80, arg=0x7ffc16e67190) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:185 #14 0x7fd0fe5da0db in QtPrivate::QSlotObject, void>::impl (which=1, this_=0x55cdc661d770, r=0x55cdc6621d80, a=0x7ffc16e67190, ret=0x0) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:418 #15 0x7fd0fbe7b66c in QtPrivate::QSlotObjectBase::call (a=0x7ffc16e67190, r=0x55cdc6621d80, this=0x55cdc661d770) at ../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/kernel/qobjectdefs_impl.h:398 #16 doActivate (sender=0x55cdc65a8870, signal_index=4, argv=0x7ffc16e67190) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/kernel/qobject.cpp:3886 #17 0x7fd0fe572e0b in KItemModelBase::itemsRemoved (this=0x55cdc65a8870, _t1=...) at /home/leszek/kde/build/dolphin/src/dolphinprivate_autogen/Z3MQH7AOBD/moc_kitemmodelbase.cpp:253 #18 0x7fd0fe58c3e4 in KFileItemModel::removeItems (this=0x55cdc65a8870, itemRanges=..., behavior=KFileItemModel::KeepItemData) at /home/leszek/kde/src/dolphin/src/kitemviews/kfileitemmodel.cpp:1317 #19 0x7fd0fe589e10 in KFileItemModel::applyFilters (this=0x55cdc65a8870) at /home/leszek/kde/src/dolphin/src/kitemviews/kfileitemmodel.cpp:704 #20 0x7fd0fe589bae in KFileItemModel::setNameFilter (this=0x55cdc65a8870, nameFilter=...) at /home/leszek/kde/src/dolphin/src/kitemviews/kfileitemmodel.cpp:658 #21 0x7fd0fe61961d in DolphinView::setNameFilter (this=0x55cdc62267d0, nameFilter=...) at /home/leszek/kde/src/dolphin/src/views/dolphinview.cpp:484 #22 0x7fd0fe75831c in DolphinViewContainer::setNameFilter (this=0x55cdc6577200, nameFilter=...) at /home/leszek/kde/src/dolphin/src/dolphinviewcontainer.cpp:667 #23 0x7fd0fe75c10d in QtPrivate::FunctorCall, QtPrivate::List, void, void (DolphinViewContainer::*)(QString const&)>::call (f=(void (DolphinViewContainer::*)(class DolphinViewContainer * const, const class QString &)) 0x7fd0fe7582e0 , o=0x55cdc6577200, arg=0x7ffc16e67510) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:152 #24 0x7fd0fe75bc2e in QtPrivate::FunctionPointer::call, void> (f=(void (DolphinViewContainer::*)(class DolphinViewContainer * const, const class QString &)) 0x7fd0fe7582e0 , o=0x55cdc6577200, arg=0x7ffc16e67510) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:185 #25 0x7fd0fe75b1e7 in QtPrivate::QSlotObject, void>::impl (which=1, this_=0x55cdc6692950, r=0x55cdc6577200, a=0x7ffc16e67510, ret=0x0) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:418 #26 0x7fd0fbe7b66c in QtPrivate::QSlotObjectBase::call (a=0x7ffc16e67510, r=0x55cdc6577200, this=0x55cdc6692950) at ../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/kernel/qobjectdefs_impl.h:398 #27 doActivate (sender=0x55cdc65aca60, signal_index=7, argv=0x7ffc16e67510) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/kernel/qobject.cpp:3886 #28 0x7fd0fe7b8d09 in FilterBar::filterChanged (this=0x55cdc65aca60, _t1=...) at /home
[dolphin] [Bug 428374] Dolphin crashes when typing in filter bar in specific folder
https://bugs.kde.org/show_bug.cgi?id=428374 Leszek Lesner changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Leszek Lesner --- You are right. After your notice I did a fresh recompile of dolphin and it seems not to crash. Thanks for taking the time to look into it. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428374] New: Dolphin crashes when typing in filter bar in specific folder
https://bugs.kde.org/show_bug.cgi?id=428374 Bug ID: 428374 Summary: Dolphin crashes when typing in filter bar in specific folder Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bars: filter Assignee: dolphin-bugs-n...@kde.org Reporter: leszek.les...@web.de CC: kfm-de...@kde.org Target Milestone: --- SUMMARY As soon as I type in a letter in the filter bar in one specific folder it crashes dolphin STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: master (available in About System) KDE Plasma Version: master KDE Frameworks Version: master Qt Version: 5.15.2 ADDITIONAL INFORMATION Application: Dolphin (dolphin), signal: Aborted Content of s_kcrashErrorMessage: (null) [KCrash Handler] #5 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #6 0x7f6eff7e6535 in __GI_abort () at abort.c:79 #7 0x7f6effd9ea05 in qt_message_fatal (context=..., message=...) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/global/qlogging.cpp:1914 #8 QMessageLogger::fatal (this=this@entry=0x7ffd2195d9d0, msg=msg@entry=0x7f6f0006fea0 "ASSERT: \"%s\" in file %s, line %d") at /home/leszek/kde/src/Qt5/qtbase/src/corelib/global/qlogging.cpp:893 #9 0x7f6effd9df23 in qt_assert (assertion=, file=, line=) at ../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/global/qlogging.h:90 #10 0x7f6f0271edd2 in KItemListView::slotItemsRemoved (this=0x55a2f6f73770, itemRanges=...) at /home/leszek/kde/src/dolphin/src/kitemviews/kitemlistview.cpp:1199 #11 0x7f6f026d3bcb in KFileItemListView::slotItemsRemoved (this=0x55a2f6f73770, itemRanges=...) at /home/leszek/kde/src/dolphin/src/kitemviews/kfileitemlistview.cpp:309 #12 0x7f6f0272de7e in QtPrivate::FunctorCall, QtPrivate::List, void, void (KItemListView::*)(KItemRangeList const&)>::call (f=&virtual table offset 536, o=0x55a2f6f73770, arg=0x7ffd2195dce0) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:152 #13 0x7f6f0272d16a in QtPrivate::FunctionPointer::call, void> (f=&virtual table offset 536, o=0x55a2f6f73770, arg=0x7ffd2195dce0) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:185 #14 0x7f6f0272c0db in QtPrivate::QSlotObject, void>::impl (which=1, this_=0x55a2f6f75860, r=0x55a2f6f73770, a=0x7ffd2195dce0, ret=0x0) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:418 #15 0x7f6efffcd66c in QtPrivate::QSlotObjectBase::call (a=0x7ffd2195dce0, r=0x55a2f6f73770, this=0x55a2f6f75860) at ../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/kernel/qobjectdefs_impl.h:398 #16 doActivate (sender=0x55a2f6ec3e70, signal_index=4, argv=0x7ffd2195dce0) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/kernel/qobject.cpp:3886 #17 0x7f6f026c4e0b in KItemModelBase::itemsRemoved (this=0x55a2f6ec3e70, _t1=...) at /home/leszek/kde/build/dolphin/src/dolphinprivate_autogen/Z3MQH7AOBD/moc_kitemmodelbase.cpp:253 #18 0x7f6f026de3e4 in KFileItemModel::removeItems (this=0x55a2f6ec3e70, itemRanges=..., behavior=KFileItemModel::KeepItemData) at /home/leszek/kde/src/dolphin/src/kitemviews/kfileitemmodel.cpp:1317 #19 0x7f6f026dbe10 in KFileItemModel::applyFilters (this=0x55a2f6ec3e70) at /home/leszek/kde/src/dolphin/src/kitemviews/kfileitemmodel.cpp:704 #20 0x7f6f026dbbae in KFileItemModel::setNameFilter (this=0x55a2f6ec3e70, nameFilter=...) at /home/leszek/kde/src/dolphin/src/kitemviews/kfileitemmodel.cpp:658 #21 0x7f6f0276b61d in DolphinView::setNameFilter (this=0x55a2f6f77fe0, nameFilter=...) at /home/leszek/kde/src/dolphin/src/views/dolphinview.cpp:484 #22 0x7f6f028aa31c in DolphinViewContainer::setNameFilter (this=0x55a2f6fc6c80, nameFilter=...) at /home/leszek/kde/src/dolphin/src/dolphinviewcontainer.cpp:667 #23 0x7f6f028ae10d in QtPrivate::FunctorCall, QtPrivate::List, void, void (DolphinViewContainer::*)(QString const&)>::call (f=(void (DolphinViewContainer::*)(class DolphinViewContainer * const, const class QString &)) 0x7f6f028aa2e0 , o=0x55a2f6fc6c80, arg=0x7ffd2195e060) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:152 #24 0x7f6f028adc2e in QtPrivate::FunctionPointer::call, void> (f=(void (DolphinViewContainer::*)(class DolphinViewContainer * const, const class QString &)) 0x7f6f028aa2e0 , o=0x55a2f6fc6c80, arg=0x7ffd2195e060) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:185 #25 0x7f6f028ad1e7 in QtPrivate::QSlotObject, void>::impl (which=1, this_=0x55a2f6b7ad90, r=0x55a2f6fc6c80, a=0x7ffd2195e060, ret=0x0) at /home/leszek/kde/qt5/include/QtCore/qobjectdefs_impl.h:418 #26 0x7f6efffcd66c in QtPrivate::QSlotObjectBase::call (a=0x7ffd2195e060, r=0x55a2f6fc6c80, this=0x55a2f6b7ad90) at ../../include/QtCore/../../../../../src/Qt5/qtbase/src/corelib/kernel/qobjectd
[plasmashell] [Bug 428241] plasmashell crashes when notification closes
https://bugs.kde.org/show_bug.cgi?id=428241 Leszek Lesner changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||leszek.les...@web.de --- Comment #5 from Leszek Lesner --- I can confirm the issue. Here is my log: https://pastebin.com/xLqT1jeM -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428039] New: Holding a key does not repeat it like it should [Wayland][kwin][kwayland-server]
https://bugs.kde.org/show_bug.cgi?id=428039 Bug ID: 428039 Summary: Holding a key does not repeat it like it should [Wayland][kwin][kwayland-server] Product: kwin Version: git master Platform: Netrunner OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: leszek.les...@web.de Target Milestone: --- SUMMARY Keyboard repeat is broken. Holding a key does not repeat it like it should. STEPS TO REPRODUCE 1. Open a wayland session 2. open a terminal 3. press and hold a key OBSERVED RESULT Only one key press is recorded and printed in the terminal EXPECTED RESULT as long as I hold it should repeat the key SOFTWARE/OS VERSIONS Linux/KDE Plasma: master (available in About System) KDE Plasma Version: master KDE Frameworks Version: master Qt Version: 5.15.2 ADDITIONAL INFORMATION It has to do with these changes: https://invent.kde.org/plasma/kwayland-server/-/commit/8a6d17f2cbfadee783d1664ec7e59e521075cfd5 https://invent.kde.org/plasma/kwin/-/commit/5e037570fe90d9883e887bb8f0e78d5bef8ec2f6 Reverting those two fixes the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427841] New: Crash when dragging and dropping files from Wayland to XWayland client
https://bugs.kde.org/show_bug.cgi?id=427841 Bug ID: 427841 Summary: Crash when dragging and dropping files from Wayland to XWayland client Product: kwin Version: git master Platform: Netrunner OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: leszek.les...@web.de Target Milestone: --- SUMMARY Crash when starting to drag a file from dolphin to kdenlive STEPS TO REPRODUCE 1. Try dragging a file from dolphin to kdenlive 2. First attempt fails (appears to trigger a drag in kdenlive itself instead [of clips already there]) 3. Try dragging the file again from dolphin (only drag and moving the mouse) OBSERVED RESULT Kwin_Wayland crashes and I land on the login page EXPECTED RESULT Drag and Drop should work SOFTWARE/OS VERSIONS Linux/KDE Plasma: master (available in About System) KDE Plasma Version: master KDE Frameworks Version: master Qt Version: 5.15.2 ADDITIONAL INFORMATION Seems to me the first drag is the issue that confuses xwayland and wayland completely and leads to the crash as sometimes dragging and dropping works fine on the first try. Only when kdenlive gets into drag mode and thinking I am dragging some clip from it it freaks out. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412924] [kwin_wayland] High CPU usage with Qt 5.14 and mouse cursor artifacts
https://bugs.kde.org/show_bug.cgi?id=412924 --- Comment #18 from Leszek Lesner --- Looks like a memory leak to me. The process gradually uses more CPU and more and more memory on my system. So 120 fps at the beginning of a session and the more RAM it uses the slower the framerate gets. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412924] [kwin_wayland] High CPU usage with Qt 5.14 and mouse cursor artifacts
https://bugs.kde.org/show_bug.cgi?id=412924 Leszek Lesner changed: What|Removed |Added Version|5.19.90 |git master -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412924] [kwin_wayland] High CPU usage with Qt 5.14 and mouse cursor artifacts
https://bugs.kde.org/show_bug.cgi?id=412924 Leszek Lesner changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||leszek.les...@web.de --- Comment #17 from Leszek Lesner --- Can confirm relatively high CPU usage (showing 6% instead of nothing in systemmonitor. Also framerate breaks down from 120 frames to under 100 with sometimes even under 50 fps which is clearly visible mostly when using the virtual desktop overview with 4 virtual desktops showing side by side. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425041] Wayland session crashes when I try to resize Konsole dragging its upper right corner
https://bugs.kde.org/show_bug.cgi?id=425041 Leszek Lesner changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||leszek.les...@web.de Ever confirmed|0 |1 --- Comment #7 from Leszek Lesner --- I can confirm this with dolphin when maximized and trying to resize after unmaximizing (which did not change its size btw). Also Gwenview suffers. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427472] New: Kicker sysactions show favorites
https://bugs.kde.org/show_bug.cgi?id=427472 Bug ID: 427472 Summary: Kicker sysactions show favorites Product: plasmashell Version: master Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: leszek.les...@web.de CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 132229 --> https://bugs.kde.org/attachment.cgi?id=132229&action=edit Screenshot example with kicker SUMMARY Instead of sysactions I get favorites in the sysaction area STEPS TO REPRODUCE 1. Open Kicker 2. Look at sysactions OBSERVED RESULT Instead of sysactions I get favorites EXPECTED RESULT It should show sysactions SOFTWARE/OS VERSIONS Linux/KDE Plasma: master git (09 Oct 2020) KDE Frameworks Version: 5.75 Qt Version: 5.15.1 ADDITIONAL INFORMATION Reverting this commit fixes the issue: https://invent.kde.org/plasma/plasma-workspace/-/commit/fcdbbda3965d73900c415071ad882f550994fdc2 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 427236] New: KMail crashes after closing e-mail window
https://bugs.kde.org/show_bug.cgi?id=427236 Bug ID: 427236 Summary: KMail crashes after closing e-mail window Product: kmail2 Version: Git (master) Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: leszek.les...@web.de Target Milestone: --- Created attachment 132065 --> https://bugs.kde.org/attachment.cgi?id=132065&action=edit Debug output kmail SUMMARY Opening up a e-mail in a new window crashes KMail when closing this window. STEPS TO REPRODUCE 1. Double click on a e-mail 2. Wait until the e-mail loads in a new window 3. Close the window via close button or File->Close OBSERVED RESULT KMail crashes. EXPECTED RESULT E-Mail window closes only. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Git Master (2nd October 2020) (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.15.1 (Git branch with 2nd October 2020 commits) ADDITIONAL INFORMATION See attached debug output Might be related to https://bugs.kde.org/show_bug.cgi?id=403359 though its reported so long ago and I only have this issue since a few days (updating more or less regularly from git master) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426072] kwin_wayland crashes when I hover over task manager after dragging an entry from it to kickoff
https://bugs.kde.org/show_bug.cgi?id=426072 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de --- Comment #2 from Leszek Lesner --- Similiar crash when dragging a file ontop the taskswitcher and then pressing ALT+Tab to switch as it does not do automatic raising of windows that are associated with the windiw list you drag the file onto. Application: Plasma (plasmashell), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [KCrash Handler] #5 0x in () #6 0x7fd9ba7ad0b9 in DeclarativeMimeData::DeclarativeMimeData(QMimeData const*) (this=0x55ed13745840, copy=0x55ed0a37de80) at /home/leszek/kde/src/kdeclarative/src/qmlcontrols/draganddrop/DeclarativeMimeData.cpp:39 #7 0x7fd9ba7ac4cb in DeclarativeDragDropEvent::mimeData() (this=0x7ffd73381480) at /home/leszek/kde/src/kdeclarative/src/qmlcontrols/draganddrop/DeclarativeDragDropEvent.cpp:52 #8 0x7fd9ba7a2a79 in DeclarativeDragDropEvent::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x7ffd73381480, _c=QMetaObject::ReadProperty, _id=4, _a=0x7ffd7337f550) at /home/leszek/kde/build/kdeclarative/src/qmlcontrols/draganddrop/draganddropplugin_autogen/EWIEGA46WW/moc_DeclarativeDragDropEvent.cpp:121 #9 0x7fd9d0c182a9 in QQmlPropertyData::readProperty(QObject*, void*) const (property=0x7ffd7337f530, target=, this=0x55ed224798f8) at ../../include/QtQml/5.15.1/QtQml/private/../../../../../../../../src/Qt5/qtdeclarative/src/qml/qml/qqmlpropertydata_p.h:357 #10 0x7fd9d0c182a9 in loadProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData const&) (v4=0x55ed00cbfa10, object=0x7ffd73381480, property=...) at /home/leszek/kde/src/Qt5/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:138 #11 0x7fd9d0c37344 in QV4::Moth::VME::interpret(QV4::CppStackFrame*, QV4::ExecutionEngine*, char const*) (frame=0x7ffd7337f740, engine=0x55ed00cbfa10, code=0x7fd9ac5794a2 ":\004:\005\030\b\022<\030\v\246\006\b\001\v\030\b\006b\bL\005\246\a\006") at /home/leszek/kde/src/Qt5/qtdeclarative/src/qml/jsruntime/qv4vme_moth.cpp:638 #12 0x7fd9d0c3c657 in QV4::Moth::VME::exec(QV4::CppStackFrame*, QV4::ExecutionEngine*) (frame=frame@entry=0x7ffd7337f740, engine=engine@entry=0x55ed00cbfa10) at /home/leszek/kde/src/Qt5/qtdeclarative/src/qml/jsruntime/qv4vme_moth.cpp:463 #13 0x7fd9d0bcf412 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) (this=this@entry=0x55ed04b939e0, thisObject=, argv=argv@entry=0x7fd9c81db508, argc=, context=) at /home/leszek/kde/src/Qt5/qtdeclarative/src/qml/jsruntime/qv4function.cpp:69 #14 0x7fd9d0d556a7 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) (this=this@entry=0x55ed04b94ec0, callData=callData@entry=0x7fd9c81db4d8, isUndefined=isUndefined@entry=0x0) at ../../include/QtQml/5.15.1/QtQml/private/../../../../../../../../src/Qt5/qtdeclarative/src/qml/jsruntime/qv4value_p.h:343 #15 0x7fd9d0d00217 in QQmlBoundSignalExpression::evaluate(void**) (this=, a=0x7ffd73381450) at ../../include/QtQml/5.15.1/QtQml/private/../../../../../../../../src/Qt5/qtdeclarative/src/qml/jsruntime/qv4jscall_p.h:95 #16 0x7fd9d0d0162b in QQmlBoundSignal_callback(QQmlNotifierEndpoint*, void**) (e=0x55ed04b93900, a=0x7ffd73381450) at ../../include/QtQml/5.15.1/QtQml/private/../../../../../../../../src/Qt5/qtdeclarative/src/qml/qml/qqmlboundsignalexpressionpointer_p.h:69 #17 0x7fd9d0d357b3 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) (endpoint=, a=a@entry=0x7ffd73381450) at /home/leszek/kde/src/Qt5/qtdeclarative/src/qml/qml/qqmlnotifier.cpp:104 #18 0x7fd9d0ce253c in QQmlData::signalEmitted(QAbstractDeclarativeData*, QObject*, int, void**) (object=0x55ed04b93c10, index=, a=0x7ffd73381450) at /home/leszek/kde/src/Qt5/qtdeclarative/src/qml/qml/qqmlengine.cpp:834 #19 0x7fd9cefd104f in doActivate(QObject*, int, void**) (sender=0x55ed04b93c10, signal_index=30, argv=0x7ffd73381450) at /home/leszek/kde/src/Qt5/qtbase/src/corelib/kernel/qobject_p.h:110 #20 0x7fd9ba7a3343 in DeclarativeDropArea::dragEnter(DeclarativeDragDropEvent*) (this=0x55ed04b93c10, _t1=0x7ffd73381480) at /home/leszek/kde/build/kdeclarative/src/qmlcontrols/draganddrop/draganddropplugin_autogen/EWIEGA46WW/moc_DeclarativeDropArea.cpp:268 #21 0x7fd9ba7ac89f in DeclarativeDropArea::dragEnterEvent(QDragEnterEvent*) (this=0x55ed04b93c10, event=0x7ffd73381800) at /home/leszek/kde/src/kdeclarative/src/qmlcontrols/draganddrop/DeclarativeDropArea.cpp:46 #22 0x7fd9d13697e8 in QQuickItem::event(QEvent*) (this=0x55ed04b93c10, ev=0x7ffd73381800) at /home/leszek/kde/src/Qt5/qtdeclarative/src/quick/items/qquickitem.cpp:8128 #23 0x7fd9cfeb311e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x55ed008e8e20, receiver=receiver@entry=0x55ed04
[kwin] [Bug 426072] kwin_wayland crashes when I hover over task manager after dragging an entry from it to kickoff
https://bugs.kde.org/show_bug.cgi?id=426072 Leszek Lesner changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 422232] Failed to receive file on Desktop from Android
https://bugs.kde.org/show_bug.cgi?id=422232 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Leszek Lesner --- Can confirm this with several 4k video clips from my smartphone to laptop. KDE Plasma master (27th August 2020) KF 5.73 Qt 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424754] Plasma fails to paste text copied from apps running on Xwayland (tested Firefox and Chromium)
https://bugs.kde.org/show_bug.cgi?id=424754 --- Comment #4 from Leszek Lesner --- (In reply to Leszek Lesner from comment #3) > No not fixed yet. I still have empty entries in klipper and still stuff not > copied on Ctrl+C in XWayland apps. Figured out if you disable "Prevent empty keyboard" it seems to work!? Ctrl+C works directly in XWayland apps like Chromium/Firefox and co -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424754] Plasma fails to paste text copied from apps running on Xwayland (tested Firefox and Chromium)
https://bugs.kde.org/show_bug.cgi?id=424754 --- Comment #3 from Leszek Lesner --- No not fixed yet. I still have empty entries in klipper and still stuff not copied on Ctrl+C in XWayland apps. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424731] New: [Wayland] Clipboard Ctrl+C not working right click copy working XWayland
https://bugs.kde.org/show_bug.cgi?id=424731 Bug ID: 424731 Summary: [Wayland] Clipboard Ctrl+C not working right click copy working XWayland Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: leszek.les...@web.de Target Milestone: 1.0 Created attachment 130453 --> https://bugs.kde.org/attachment.cgi?id=130453&action=edit Empty string appears in klipper after first usage of Ctrl+C SUMMARY STEPS TO REPRODUCE 1. Open Chromium or other XWayland app 2. Mark text 3. Hit Ctrl+C OBSERVED RESULT empty string copied in klipper EXPECTED RESULT marked text copied in klipper SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian stable (10) (available in About System) KDE Plasma Version: Plasma 5.19.80 (Current git master: 2020-07-28) KDE Frameworks Version: 5.73.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION right click in Xwayland client and hit copy works as expected. Only Ctrl+C seems to copy nothing (or an empty string) Hitting Ctrl+C a second time on the same or another XWayland client copies the string like it should and kipper shows the empty string copied before. (It is not listed there on first Ctrl+C press) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424709] Plasma crashes when I try to clean the clipboard on Wayland session of neon unstable
https://bugs.kde.org/show_bug.cgi?id=424709 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de --- Comment #1 from Leszek Lesner --- I can confirm this issue with self compiled plasma aswell -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422275] New: Kwin crashes when using hot corner to switch virtual desktops
https://bugs.kde.org/show_bug.cgi?id=422275 Bug ID: 422275 Summary: Kwin crashes when using hot corner to switch virtual desktops Product: kwin Version: 5.18.90 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: leszek.les...@web.de Target Milestone: --- Application: kwin_x11 (5.18.90) (Compiled from sources) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.6.15-050615-generic x86_64 Windowing system: X11 Distribution: Neptune 6 -- Information about the crash: - What I was doing when the application crashed: I tried switching the desktop via hot corner desktop overview effect and using a hot corner The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Content of s_kcrashErrorMessage: (null) [KCrash Handler] #5 0x7f756b12e7bb in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #6 0x7f756b119535 in __GI_abort () at abort.c:79 #7 0x7f756b7c6945 in () at /home/leszek/kde/qt5/lib/libQt5Core.so.5 #8 0x7f756b7c5e63 in qt_assert_x(char const*, char const*, char const*, int) () at /home/leszek/kde/qt5/lib/libQt5Core.so.5 #9 0x7f756f0fd765 in KWin::EffectsHandlerImpl::windowToDesktops(KWin::EffectWindow*, QVector const&) (this=0x55c71a818bb0, w=0x55c71a856b60, desktopIds=...) at /home/leszek/kde/src/kwin/effects.cpp:939 #10 0x7f756ed8d25f in KWin::DesktopGridEffect::windowInputMouseEvent(QEvent*) (this=0x55c71a892530, e=0x7ffcb3aca9a0) at /home/leszek/kde/src/kwin/effects/desktopgrid/desktopgrid.cpp:550 #11 0x7f756f0fe64a in KWin::EffectsHandlerImpl::checkInputWindowEvent(QMouseEvent*) (this=0x55c71a818bb0, e=0x7ffcb3aca9a0) at /home/leszek/kde/src/kwin/effects.cpp:1299 #12 0x7f7564684f77 in KWin::EffectsMouseInterceptionX11Filter::event(xcb_generic_event_t*) (this=0x55c71b1fb630, event=0x7f756001f970) at /home/leszek/kde/src/kwin/plugins/platforms/x11/standalone/effects_mouse_interception_x11_filter.cpp:101 #13 0x7f756f116e48 in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) (this=0x55c71a444160, e=0x7f756001f970) at /home/leszek/kde/src/kwin/events.cpp:240 #14 0x7f756f179a7e in KWin::XcbEventFilter::nativeEventFilter(QByteArray const&, void*, long*) (this=0x55c71a3d68d0, eventType=..., message=0x7f756001f970, result=0x7ffcb3acad98) at /home/leszek/kde/src/kwin/main.cpp:412 #15 0x7f756b9b8dff in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) () at /home/leszek/kde/qt5/lib/libQt5Core.so.5 #16 0x7f7565800f90 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () at /home/leszek/kde/qt5/plugins/platforms/../../lib/libQt5XcbQpa.so.5 #17 0x7f7565801c96 in QXcbConnection::processXcbEvents(QFlags) () at /home/leszek/kde/qt5/plugins/platforms/../../lib/libQt5XcbQpa.so.5 #18 0x7f756582928c in () at /home/leszek/kde/qt5/plugins/platforms/../../lib/libQt5XcbQpa.so.5 #19 0x7f756b9ba38b in QEventLoop::exec(QFlags) () at /home/leszek/kde/qt5/lib/libQt5Core.so.5 #20 0x7f756b9c213e in QCoreApplication::exec() () at /home/leszek/kde/qt5/lib/libQt5Core.so.5 #21 0x55c71851c947 in main(int, char**) (argc=3, argv=0x7ffcb3acb1e8) at /home/leszek/kde/src/kwin/main_x11.cpp:479 [Inferior 1 (process 23957) detached] The reporter indicates this bug may be a duplicate of or related to bug 47. Possible duplicates by query: bug 421576, bug 420414, bug 419798, bug 418804, bug 418803. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422035] New: Icons align right on move align left
https://bugs.kde.org/show_bug.cgi?id=422035 Bug ID: 422035 Summary: Icons align right on move align left Product: plasmashell Version: 5.18.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: leszek.les...@web.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Align Icons as columns to the right and set sorting manually 2. Move an icon to a new column or row (with now other icon) OBSERVED RESULT Icons suddenly align left but mirrored. EXPECTED RESULT Icon should just move according to set alignment SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 10 stable KDE Plasma Version: 5.18.90 KDE Frameworks Version: 5.70 Qt Version: 5.14.2 ADDITIONAL INFORMATION When trying to mark desktop icons for selection they suddenly jump to the right alignment again. See video here that shows the issue: https://youtu.be/5LrviqEU1rM -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419080] Window doesn't have correct size when using themes with Aurorae theme engine
https://bugs.kde.org/show_bug.cgi?id=419080 --- Comment #5 from Leszek Lesner --- Created attachment 128620 --> https://bugs.kde.org/attachment.cgi?id=128620&action=edit Broken aurorae Theme maximized -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419080] Window doesn't have correct size when using themes with Aurorae theme engine
https://bugs.kde.org/show_bug.cgi?id=419080 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de --- Comment #4 from Leszek Lesner --- Can confirm with Kwin 5.18.90 aswell. Every aurorae theme looks like some pixels are missing maximized. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 408054] Wikipedia Applet shows nothing
https://bugs.kde.org/show_bug.cgi?id=408054 Leszek Lesner changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||leszek.les...@web.de --- Comment #2 from Leszek Lesner --- This bug has been fixed long ago in 2.9.0 upstream release. See: https://cgit.kde.org/amarok.git/commit/?id=8c15258b28870b6d9990b24f87ce913e2049bac8 and the release announcement for Amarok 2.9.0: https://amarok.kde.org/en/node/888 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377762] Flickering desktop on wayland
https://bugs.kde.org/show_bug.cgi?id=377762 Leszek Lesner changed: What|Removed |Added Ever confirmed|0 |1 CC||leszek.les...@web.de Status|REPORTED|CONFIRMED --- Comment #6 from Leszek Lesner --- Can confirm on Plasma 5.14.3 and nouveau KF: 5.52 Qt: 5.11.2 Graphics: Card: NVIDIA GT218M [NVS 3100M] Display Server: wayland (X.Org 1.19.6 ) drivers: nouveau (unloaded: modesetting,fbdev,vesa) Resolution: 1280x800@59.99hz OpenGL: renderer: NVA8 version: 3.3 Mesa 18.0.5 https://youtu.be/ufb7KWG28Y0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385920] [Wayland] With "resolution dependent" size, cursor is huge when hovering over Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=385920 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de --- Comment #21 from Leszek Lesner --- Tested with 5.14.3 still an issue there. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 400799] New: [Wayland] no fullscreen
https://bugs.kde.org/show_bug.cgi?id=400799 Bug ID: 400799 Summary: [Wayland] no fullscreen Product: gwenview Version: 18.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: leszek.les...@web.de Target Milestone: --- Double clicking or pressing the fullscreen button does only change the UI in Gwenview to the fullscreen one but does not go to fullscreen itself on Wayland. STEPS TO REPRODUCE 1. Start Plasma Wayland 2. Open an Image 3. Press fullscreen button SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 related: https://bugs.kde.org/show_bug.cgi?id=366764 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397793] Powermanagement settings are not saved when xdg config dirs overwrite default settings
https://bugs.kde.org/show_bug.cgi?id=397793 Leszek Lesner changed: What|Removed |Added Summary|Powermanagement settings|Powermanagement settings |are not saved. |are not saved when xdg ||config dirs overwrite ||default settings -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397793] Powermanagement settings are not saved.
https://bugs.kde.org/show_bug.cgi?id=397793 Leszek Lesner changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|DOWNSTREAM |--- --- Comment #3 from Leszek Lesner --- Powermanagement should still be able to save settings even though xdg config dirs overwrites its default settings. So it is not a downstream bug. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 388593] Krunner spellcheck plugin does not work (Could not find a dictionary)
https://bugs.kde.org/show_bug.cgi?id=388593 --- Comment #4 from Leszek Lesner --- Added bug here for the spellchecking kcm: https://bugs.kde.org/show_bug.cgi?id=398247 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 391243] New web shortcuts take effect only after user restarts sessions
https://bugs.kde.org/show_bug.cgi?id=391243 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 398247] New: Spellchecking KCM should give more info on what "backend" is missing
https://bugs.kde.org/show_bug.cgi?id=398247 Bug ID: 398247 Summary: Spellchecking KCM should give more info on what "backend" is missing Product: systemsettings Version: 5.12.6 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_language Assignee: h...@kde.org Reporter: leszek.les...@web.de Target Milestone: --- Instead of just telling the user "backend" is missing it should give more detailed information like "Please install a dictionary like hunspell/aspell/myspell and make sure to have sonnet plugins installed". The latter is often forgotten by distros and most people are unable to make spellchecking work as only a part knows about aspell/hunspell/myspell and even a smaller part knows about sonnet-plugins. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 388593] Krunner spellcheck plugin does not work (Could not find a dictionary)
https://bugs.kde.org/show_bug.cgi?id=388593 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de --- Comment #3 from Leszek Lesner --- You need to have the sonnet-plugins package installed and the hunspell or aspell language packs aswell as configure the correct language in systemsettings for it to work. I'll create a new bug for spellchecking kcm to list this as hints somehow. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 398245] Dictionary runner should inform user on what is necessary to install to make it work
https://bugs.kde.org/show_bug.cgi?id=398245 --- Comment #1 from Leszek Lesner --- To make it more clear. It should list it in the Info panel for the plugin or when using the keyword and it isn't working -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 398245] New: Dictionary runner should inform user on what is necessary to install to make it work
https://bugs.kde.org/show_bug.cgi?id=398245 Bug ID: 398245 Summary: Dictionary runner should inform user on what is necessary to install to make it work Product: krunner Version: 5.12.6 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: leszek.les...@web.de Target Milestone: --- Sadly I fail to make the dictionary krunner plugin working for me. It should list what it needs to run successfully. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 398244] New: Spellchecker runner plugin configure button should allow opening kcm to configure spellchecking
https://bugs.kde.org/show_bug.cgi?id=398244 Bug ID: 398244 Summary: Spellchecker runner plugin configure button should allow opening kcm to configure spellchecking Product: krunner Version: 5.12.6 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: spellchecker Assignee: k...@privat.broulik.de Reporter: leszek.les...@web.de Target Milestone: --- The spellchecker runner plugin should not only allow setting the keyword to use but also allow opening up the kcm that allows configuring the spellcheck. (like setting the language and such) -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 398242] New: Webshortcuts runner missing configure button
https://bugs.kde.org/show_bug.cgi?id=398242 Bug ID: 398242 Summary: Webshortcuts runner missing configure button Product: krunner Version: 5.12.6 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: webshortcuts Assignee: ro...@kde.org Reporter: leszek.les...@web.de Target Milestone: --- It is not clear for every user on how to configure the webshortcuts krunner plugin. It would make sense to add a button that calls the kcm. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397793] Powermanagement settings are not saved.
https://bugs.kde.org/show_bug.cgi?id=397793 --- Comment #1 from Leszek Lesner --- Seems to be a bad combination of a default settings file shipped with the distribution as default in a xdg data dir folder. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397793] New: Powermanagement settings are not saved.
https://bugs.kde.org/show_bug.cgi?id=397793 Bug ID: 397793 Summary: Powermanagement settings are not saved. Product: plasmashell Version: 5.13.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Battery Monitor Assignee: k...@privat.broulik.de Reporter: leszek.les...@web.de CC: plasma-b...@kde.org Target Milestone: 1.0 Opening up the settings of the battery and powermanagement widget and unticking boxes for display timeout or others and hitting apply and reopening the settings shows them checked again. Changing the values only and hitting apply saves the settings and reopening shows the right settings. The config file seems to be written correctly. Though when unchecking the settings it removes all previously stored values. So it will initialize with default values on reopening. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396792] Grouping of tasks ignores "only show tasks from current desktop"
https://bugs.kde.org/show_bug.cgi?id=396792 --- Comment #1 from Leszek Lesner --- Created attachment 114083 --> https://bugs.kde.org/attachment.cgi?id=114083&action=edit Settings for the taskmanager that causes the issue I attached an image with the settings I set for the task manager. Also noticed that checking "Keep launchers separate" seems to create the expected behavior. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396792] New: Grouping of tasks ignores "only show tasks from current desktop"
https://bugs.kde.org/show_bug.cgi?id=396792 Bug ID: 396792 Summary: Grouping of tasks ignores "only show tasks from current desktop" Product: plasmashell Version: 5.12.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: leszek.les...@web.de CC: plasma-b...@kde.org Target Milestone: 1.0 Grouping of tasks in the panel seems to be always active and ignoring "only show tasks from current desktop". To reproduce: 1. Activate "only show tasks from current desktop" + manual sorting of tasks and leave grouping of tasks turned on "by application name". 2. Go to a clean virtual desktop and open konsole 3. Go to another clean virtual desktop and open a bunch of application windows (see how the tasks open right next to the previous application) 4. Try opening up a new konsole window on that virtual desktop and see how its tasks is shown far left at position 1 of the tasklist How it should behave: In step 4. it should create the new konsole task like all the other apps right to the last opened one (or if another konsole task is opened right next to it to follow the grouping on that particular virtual desktop) -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 395739] SFTP hangs after restarting remote device
https://bugs.kde.org/show_bug.cgi?id=395739 --- Comment #2 from Leszek Lesner --- Dolphin is actually not frozen. It keeps working It is just looping around on refresh and sftp.so (so kio_sftp) is hanging. So every kio sftp attempt is waiting in an infinite loop -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 395739] New: SFTP hangs after restarting remote device
https://bugs.kde.org/show_bug.cgi?id=395739 Bug ID: 395739 Summary: SFTP hangs after restarting remote device Product: kio-extras Version: 18.04.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: SFTP Assignee: plasma-b...@kde.org Reporter: leszek.les...@web.de Target Milestone: --- Created attachment 113506 --> https://bugs.kde.org/attachment.cgi?id=113506&action=edit Error log SFTP connected to my smartwatch. Edit watchface save. Everything works. Restart Smartwatch and try to refresh view or reconnect via sftp to it and dolphin hangs at a loading view. Killing sftp.so and I get instant access to my smartwatch again. See attached log of kio_sftp -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393670] Dolphin not using previous configuration (dolphinui.rc version number needs update)
https://bugs.kde.org/show_bug.cgi?id=393670 --- Comment #6 from Leszek Lesner --- It is a distribution specific configuration file. So if a distro ships a configured toolbar you need to manually update the file or the distro needs to update that file everytime a new dolphin version comes out. -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 393950] New: Text is cut off in dolphin side panel tags (not able to click "change..." as not visible)
https://bugs.kde.org/show_bug.cgi?id=393950 Bug ID: 393950 Summary: Text is cut off in dolphin side panel tags (not able to click "change..." as not visible) Product: QtCurve Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: qt5 Assignee: yyc1...@gmail.com Reporter: leszek.les...@web.de CC: h...@kde.org Target Milestone: --- With QtCurve 1.8 and Dolphin 18.04 (+ baloo-widgets 18.04) when adding a tag for a file in dolphins side panel I don't get the "Change" option anymore. It is just not visible. When changing the Theme from QtCurve to Breeze the "Change..." link becomes visible and I am able to click it. The same goes for the properties window for the file. See original error report by one of our users: https://www.zevenos.com/forum/showthread.php?tid=22140 (Bug 2) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393670] Dolphin not using previous configuration (dolphinui.rc version number needs update)
https://bugs.kde.org/show_bug.cgi?id=393670 --- Comment #3 from Leszek Lesner --- Upgraded from 17.08 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393670] Dolphin not using previous configuration (dolphinui.rc version number needs update)
https://bugs.kde.org/show_bug.cgi?id=393670 Leszek Lesner changed: What|Removed |Added Summary|Dolphin not using previous |Dolphin not using previous |configuration |configuration (dolphinui.rc ||version number needs ||update) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393670] Dolphin not using previous configuration
https://bugs.kde.org/show_bug.cgi?id=393670 --- Comment #1 from Leszek Lesner --- Turns out the dolphinui.rc version number needs an update. Maybe it should perform that automatically. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393670] New: Dolphin not using previous configuration
https://bugs.kde.org/show_bug.cgi?id=393670 Bug ID: 393670 Summary: Dolphin not using previous configuration Product: dolphin Version: 18.04.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: leszek.les...@web.de CC: elvis.angelac...@kde.org Target Milestone: --- After upgrading to Dolphin 18.04 it resets all previous configuration of panels like custom launchers and such. That should not happen. It should take what was previously configured and use it. -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 393462] QtCurve freezes open/save dialog when right clicked (context menu opened)
https://bugs.kde.org/show_bug.cgi?id=393462 Leszek Lesner changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Leszek Lesner --- It is actually a duplicate of #374224 and this patch works flawlessly: https://bugsfiles.kde.org/attachment.cgi?id=103308 *** This bug has been marked as a duplicate of bug 374224 *** -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 374224] KFileDialog Options drop-down menu grabs keyboard and mouse with QtCurve style
https://bugs.kde.org/show_bug.cgi?id=374224 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de --- Comment #56 from Leszek Lesner --- *** Bug 393462 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 393462] QtCurve freezes open/save dialog when right clicked (context menu opened)
https://bugs.kde.org/show_bug.cgi?id=393462 --- Comment #2 from Leszek Lesner --- @Dr. Chaptatin yes tested in on newer Qt version and there it does not happen. However it happens with 1.8 on Qt 5.7.1 (Debian Stable) -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 393462] New: QtCurve freezes open/save dialog when right clicked (context menu opened)
https://bugs.kde.org/show_bug.cgi?id=393462 Bug ID: 393462 Summary: QtCurve freezes open/save dialog when right clicked (context menu opened) Product: QtCurve Version: git Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: qt5 Assignee: yyc1...@gmail.com Reporter: leszek.les...@web.de CC: h...@kde.org Target Milestone: --- When in a file open/save dialog and you want to change the icon view via right click or sorting or click the menu button top right to open the contextmenu it shows the contextmenu and then freezes everything. The menu cannot be closed anymore nor can an item be clicked on. So to reproduce. Set QtCurve Widget Theme in systemsettings. Open Kate -> File Open -> right click I tried it on older versions available on ubuntu / kde neon / debian / neptune Version 1.8 and the newest git version show the same behavior. -- You are receiving this mail because: You are watching all bug changes.
[kfind] [Bug 393343] New: 18.04 needs Qt 5.9 at least to be able to build
https://bugs.kde.org/show_bug.cgi?id=393343 Bug ID: 393343 Summary: 18.04 needs Qt 5.9 at least to be able to build Product: kfind Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: leszek.les...@web.de Target Milestone: --- Kfind is using QFileDialog which uses "selectedMimeTypeFilter" method which is only available from Qt 5.9 on. So CMakeLists needs a change minimum version required from 5.6.0 to 5.9.0 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338571] Performance Regression: Folder synchronisation in Akonadi 16.08 (actually in any release, starting with KDE 4.14) very slow, compared to kMail from KDE 4.13.x
https://bugs.kde.org/show_bug.cgi?id=338571 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 391472] Plasmoid cannot be translated
https://bugs.kde.org/show_bug.cgi?id=391472 --- Comment #3 from Leszek Lesner --- Created this now: https://phabricator.kde.org/D11482 -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 391472] Plasmoid cannot be translated
https://bugs.kde.org/show_bug.cgi?id=391472 --- Comment #2 from Leszek Lesner --- (In reply to Leszek Lesner from comment #1) > So all it needs is this to fix it? > Ignore the code as the formatting is broken. Here is a full diff: https://dpaste.de/of7i -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 391472] Plasmoid cannot be translated
https://bugs.kde.org/show_bug.cgi?id=391472 Leszek Lesner changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 391472] Plasmoid cannot be translated
https://bugs.kde.org/show_bug.cgi?id=391472 --- Comment #1 from Leszek Lesner --- So all it needs is this to fix it? diff --git a/Messages.sh b/Messages.sh index db8982f..8f4817c 100644 --- a/Messages.sh +++ b/Messages.sh @@ -1,4 +1,4 @@ #! /usr/bin/env bash $EXTRACTRC `find . -name \*.rc -o -name \*.ui -o -name \*.kcfg` >> rc.cpp -$XGETTEXT `find . -name \*.js -o -name \*.qml -o -name \*.cpp` -o $podir/plasmavault-kde +$XGETTEXT `find . -name \*.js -o -name \*.qml -o -name \*.cpp` -o $podir/plasma_applet_o rm -f rc.cpp -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 391472] Plasmoid cannot be translated
https://bugs.kde.org/show_bug.cgi?id=391472 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 321201] Fade Desktop effect takes place while fullscreen effect (desktop grid) is active
https://bugs.kde.org/show_bug.cgi?id=321201 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de --- Comment #7 from Leszek Lesner --- This problem reoccured for at least KWin 5.10 (had 5.8.7 before where the problem did not happen [not tested kwin 5.9]). See example video: https://www.youtube.com/watch?v=L7UbJHe0p6c -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377970] [Wayland] Notifications are often misplaced
https://bugs.kde.org/show_bug.cgi?id=377970 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 373791] Crash on exit
https://bugs.kde.org/show_bug.cgi?id=373791 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de --- Comment #5 from Leszek Lesner --- The crash is actually happening in the melt framework and taking kdenlive down aswell. This commit (6 months old already) in melt fixes the issue: https://github.com/mltframework/mlt/commit/a3188e301b5a9a1f25dbb98a510e366363348e64 We added the fix to our mlt packages in Neptune since then and don't suffer from kdenlive crashing any longer. As no new melt version (e.g. 6.4.2) was released I suggest all distros should patch melt in the meantime until it is fixed. (or someone from kdenlive can poke the melt guys to do a new bugfix release so distros can pick up the fix amongst others) Status should be set to confirmed btw. or something indicating that it is an upstream issue within melt. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378032] Remember history of notifications like on KDE4
https://bugs.kde.org/show_bug.cgi?id=378032 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 380118] Plymouth KCM DBUS Backend error
https://bugs.kde.org/show_bug.cgi?id=380118 --- Comment #1 from Leszek Lesner --- Proposed patch now available here: https://phabricator.kde.org/D5943 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 379403] plymouth-kcm uses presence of update-alternatives to detect Ubuntu
https://bugs.kde.org/show_bug.cgi?id=379403 Leszek Lesner changed: What|Removed |Added CC||leszek.les...@web.de --- Comment #1 from Leszek Lesner --- Yeah that detection is a bit poor. I guess OpenSUSE does not use update-alternatives for setting a default.plymouth. As I had a nother issue on ubuntu/debian with update-alternatives I added this patch that checks with update-alternatives --list default.plymouth if the plymouth theme is already registered with alternatives system or not. I think this could be used (if it fails on opensuse as it should if there is no default.plymouth) to skip the rest of the stuff. https://phabricator.kde.org/D5942 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 380118] Plymouth KCM DBUS Backend error
https://bugs.kde.org/show_bug.cgi?id=380118 Leszek Lesner changed: What|Removed |Added CC||notm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 380118] New: Plymouth KCM DBUS Backend error
https://bugs.kde.org/show_bug.cgi?id=380118 Bug ID: 380118 Summary: Plymouth KCM DBUS Backend error Product: kde Version: Git Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: leszek.les...@web.de Target Milestone: --- When applying a new theme It shows a DBus backend error after 25-30 seconds. The reason for this is that the Kauth call to the helper uses the default timeout. However helper itself has a timeout of 60seconds for the update-initramfs -u command. We need to set a timeout for the Kauth action to at least 60seconds aswell then. Though in general having a UI frozen for 60 seconds is a bit odd aswell. So it needs a progressbar or at least a Hint that shows it is working (Like a big overlay fading in ontop of the kcm showing a label "Working ... ") -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 380113] Plymouth KCM update-alternatives not able to set available themes
https://bugs.kde.org/show_bug.cgi?id=380113 Leszek Lesner changed: What|Removed |Added CC||notm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
