[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in a multi xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468950] Doesn't pair with Windows at all, doesn't even see it
https://bugs.kde.org/show_bug.cgi?id=468950 Nicolas Fella changed: What|Removed |Added Severity|critical|normal CC||nicolas.fe...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468954] New: Polish loop when hovering app icon in Task Manager in RTL (Right-to-Left environment)
https://bugs.kde.org/show_bug.cgi?id=468954 Bug ID: 468954 Summary: Polish loop when hovering app icon in Task Manager in RTL (Right-to-Left environment) Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: m...@ratijas.tk Target Milestone: 1.0 SUMMARY When hovering between Firefox which has one window and Sublime Text which has two, Plasma hanged with tons of these messages per second: file:///usr/local/kde/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:97:13: QML ListView: possible QQuickItem::polish() loop file:///usr/local/kde/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:97:13: QML ListView: ListView called polish() inside updatePolish() of ListView Happened in RTL mode, i.e. when running with this environment: LANGUAGE=ar:en_US LANG=ar_EG.UTF-8 LC_ALL= STEPS TO REPRODUCE 1. Run Plasma with some Arabic language 2. Hover over an icon of a running app with some windows However, I can not reproduce at will. Not sure what actually happened, and unfortunately I didn't get a stacktrace. OBSERVED RESULT Plasma hanged trying to get a ToolTip on screen. EXPECTED RESULT Should not hang ¯\_(ツ)_/¯ SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.2.12-arch1-1 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454385] Desktop icons disappear when focusing an app following unplugging an external/secondary screen
https://bugs.kde.org/show_bug.cgi?id=454385 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Version Fixed In||5.27.4 --- Comment #11 from Nate Graham --- Cuchac, your backtrace looks different. Can you submit a new bug report for it? Thanks! As for the original issue, this should have been fixed in Plasma 5.27. I can't reproduce it anymore the way I could in comment 5 and comment 7. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398883] valgrind incorrectly assumes ABI on PowerPC based on endianness
https://bugs.kde.org/show_bug.cgi?id=398883 --- Comment #9 from Carl Love --- I looked thru the patch. Nothing jumps out at me as being an issue. But, that doesn't guarantee anything given the assembly and all. I did try to apply the patch to test it but it doesn't apply. So, I would say, update the patch and lets test it on the supported BE and LE systems to make sure the patch doesn't break anything. Test it on the non-standard systems where you want to use it. As long as everything works fine, I wouldn't object to it. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 463739] Ephemeral Kalendar crash while switching between task lists
https://bugs.kde.org/show_bug.cgi?id=463739 Claudio Cambra changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/pim/ ||kalendar/commit/c1275c39582 ||e3d35af212b3c1977c7c971b36c ||0b --- Comment #6 from Claudio Cambra --- Git commit c1275c39582e3d35af212b3c1977c7c971b36c0b by Claudio Cambra, on behalf of Carl Schwan. Committed on 25/04/2023 at 15:30. Pushed by clau-cambra into branch 'master'. Fix checking if a non existing calendar Check again in 100ms to avoid a crash to avoid an occasional data race M +1-1src/models/multidayincidencemodel.cpp https://invent.kde.org/pim/kalendar/commit/c1275c39582e3d35af212b3c1977c7c971b36c0b -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468863] Plasma automatically switching from unoccupied desktops to occupied desktops
https://bugs.kde.org/show_bug.cgi?id=468863 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |REPORTED CC||natalie.clar...@kde.org Resolution|WAITINGFORINFO |--- --- Comment #3 from Nate Graham --- Ok, thanks for the info. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468889] way to force driverless printer to use drivers
https://bugs.kde.org/show_bug.cgi?id=468889 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO Summary|way to force printer to use |way to force driverless |drivers |printer to use drivers --- Comment #3 from Nate Graham --- But do you know that your driverless printer actually supports using drivers? Does this work? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390817] Persistent user confusion regarding pinned apps vs panel launchers
https://bugs.kde.org/show_bug.cgi?id=390817 Nate Graham changed: What|Removed |Added CC||enric...@hotmail.com --- Comment #11 from Nate Graham --- *** Bug 468892 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468892] Snap thunderbird issues when added to the panel
https://bugs.kde.org/show_bug.cgi?id=468892 Nate Graham changed: What|Removed |Added Resolution|NOT A BUG |DUPLICATE --- Comment #3 from Nate Graham --- Yep, this confuses a lot of people. See Bug 390817. *** This bug has been marked as a duplicate of bug 390817 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 461385] When trying to install an update including packages that want to prompt the user to agree to a EULA, the update fails silently
https://bugs.kde.org/show_bug.cgi?id=461385 --- Comment #37 from Nate Graham --- I see this in the logs: Transactions: 1 /13_aaadacec /13_aaadacecallow_cancel 1 /13_aaadacecpercentage -1 /13_aaadacecrole update-packages /13_aaadacecstatus setup /13_aaadacecstatus dep-resolve /13_aaadacecpercentage 0 /13_aaadacecpercentage 100 /13_aaadacecstatus update /13_aaadacecpercentage 0 /13_aaadacecstatus finished Transactions: [none] /13_aaadacecexit code: eula-required /13_aaadacecerror code: no-license-agreement, You've to agree/decline a license -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468892] Snap thunderbird issues when added to the panel
https://bugs.kde.org/show_bug.cgi?id=468892 Enrico changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #2 from Enrico --- (In reply to Nate Graham from comment #1) > Is the menu item you're clicking on actually named "Add to Panel", or does > it instead say, "Pin to Task Manager"? Hello, you are right... using "Pin" instead of "Add to panel" I get the expected behavior... sorry for the waste of time :-( TBH I didn't even noticed these 2 options that are pretty similar but have different behaviors -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468270] No contrast in account connection error message from Fedora live session
https://bugs.kde.org/show_bug.cgi?id=468270 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |REPORTED CC||k...@marcdeop.com, ||ngomp...@gmail.com Resolution|WAITINGFORINFO |--- Summary|No contrast in account |No contrast in account |connection error message|connection error message ||from Fedora live session --- Comment #4 from Nate Graham --- In that case this may be a Fedora bug with the default color scheme shown, or a caching issue on the Fedora live session. CCing some Fedora people. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 468953] New: Add product for discuss.kde.org
https://bugs.kde.org/show_bug.cgi?id=468953 Bug ID: 468953 Summary: Add product for discuss.kde.org Classification: Websites Product: bugs.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: product/component changes Assignee: sysad...@kde.org Reporter: john@pelago.org.uk CC: christo...@krop.fr Target Milestone: --- Please can you consider adding a bugzilla product for discuss.kde.org. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 463739] Ephemeral Kalendar crash while switching between task lists
https://bugs.kde.org/show_bug.cgi?id=463739 Carl Schwan changed: What|Removed |Added Latest Commit|https://invent.kde.org/pim/ |https://invent.kde.org/pim/ |kalendar/commit/c1275c39582 |kalendar/commit/a539c40f28d |e3d35af212b3c1977c7c971b36c |0f6658ff267725d638a03b5ddb9 |0b |ee --- Comment #7 from Carl Schwan --- Git commit a539c40f28d0f6658ff267725d638a03b5ddb9ee by Carl Schwan. Committed on 25/04/2023 at 15:39. Pushed by carlschwan into branch 'release/23.04'. Fix checking if a non existing calendar Check again in 100ms to avoid a crash to avoid an occasional data race (cherry picked from commit c1275c39582e3d35af212b3c1977c7c971b36c0b) M +1-1src/models/multidayincidencemodel.cpp https://invent.kde.org/pim/kalendar/commit/a539c40f28d0f6658ff267725d638a03b5ddb9ee -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468890] Spectacle consistently crashes in ViewerWindow::~ViewerWindow() when trying to take a screenshot from the main window
https://bugs.kde.org/show_bug.cgi?id=468890
Nate Graham changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Summary|Spectacle consistently |Spectacle consistently
|crashes when trying to take |crashes in
|a screenshot. |ViewerWindow::~ViewerWindow
||() when trying to take a
||screenshot from the main
||window
Status|NEEDSINFO |REPORTED
--- Comment #4 from Nate Graham ---
Pasting inline for searchability:
Application: Spectacle (spectacle), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 QObjectPrivate::Sender::receiverDeleted() (this=) at
kernel/qobject_p.h:219
#7 QObject::~QObject() (this=0x55fe2115bf88, this=) at
kernel/qobject.cpp:1026
#8 0x7f2a509b1b93 in QQuickMatrix4x4::~QQuickMatrix4x4() (this=, this=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquicktranslate.cpp:512
#9 QQuickPinchHandler::~QQuickPinchHandler() (this=0x55fe2115be80,
this=) at
../../include/QtQuick/5.15.9/QtQuick/private/../../../../../../qtdeclarative/src/quick/handlers/qquickpinchhandler_p.h:62
#10 QQuickPinchHandler::~QQuickPinchHandler() (this=0x55fe2115be80,
this=) at
../../include/QtQuick/5.15.9/QtQuick/private/../../../../../../qtdeclarative/src/quick/handlers/qquickpinchhandler_p.h:62
#11 0x7f2a50994d82 in QAccessibleQuickItem::role() const
(this=0x55fe204f68f0) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/accessible/qaccessiblequickitem.cpp:233
#12 0x7f2a3b74e929 in AtSpiAdaptor::pathForInterface(QAccessibleInterface*)
const [clone .constprop.0] (interface=0x55fe204f68f0, this=) at
../../../platformsupport/linuxaccessibility/atspiadaptor.cpp:1586
#13 0x7f2a3b73ad8e in
AtSpiAdaptor::notifyStateChange(QAccessibleInterface*, QString const&, int)
(this=this@entry=0x55fe20001290, interface=, state=..., value=0)
at ../../../platformsupport/linuxaccessibility/atspiadaptor.cpp:878
#14 0x7f2a3b73ba46 in AtSpiAdaptor::notify(QAccessibleEvent*)
(this=0x55fe20001290, event=) at
../../../platformsupport/linuxaccessibility/atspiadaptor.cpp:903
#15 0x7f2a508324bc in QQuickItemPrivate::setEffectiveVisibleRecur(bool)
(this=0x55fe211b0140, newEffectiveVisible=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickitem.cpp:6119
#16 0x7f2a50829ba3 in QQuickItem::setParentItem(QQuickItem*)
(this=0x55fe2115be80, parentItem=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickitem.cpp:2737
#17 0x7f2a5082a162 in QQuickItem::~QQuickItem() (this=0x55fe2115be80,
this=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickitem.cpp:2335
#18 0x7f2a0018632b in QQmlPrivate::QQmlElement::~QQmlElement()
(this=0x55fe2115be80, this=) at
/usr/include/qt/QtQml/qqmlprivate.h:144
#19 QQmlPrivate::QQmlElement::~QQmlElement() (this=0x55fe2115be80,
this=) at /usr/include/qt/QtQml/qqmlprivate.h:144
#20 0x7f2a508ba459 in QQuickView::~QQuickView() (this=0x55fe2014fda0,
this=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickview.cpp:209
#21 0x55fe1e3efca7 in SpectacleWindow::~SpectacleWindow() (this=, this=) at
/usr/src/debug/spectacle/spectacle-23.04.0/src/Gui/SpectacleWindow.cpp:105
#22 0x55fe1e3efd6c in ViewerWindow::~ViewerWindow() (this=0x55fe2014fda0,
this=) at
/usr/src/debug/spectacle/spectacle-23.04.0/src/Gui/ViewerWindow.cpp:43
#23 ViewerWindow::~ViewerWindow() (this=0x55fe2014fda0, this=)
at /usr/src/debug/spectacle/spectacle-23.04.0/src/Gui/ViewerWindow.cpp:43
#24 0x7f2a4f4b1aaa in QObject::event(QEvent*) (this=0x55fe2014fda0,
e=0x55fe20a2dcd0) at kernel/qobject.cpp:1334
#25 0x7f2a50d78b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55fe2014fda0, e=0x55fe20a2dcd0) at
kernel/qapplication.cpp:3640
#26 0x7f2a4f48e028 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55fe2014fda0, event=0x55fe20a2dcd0) at
kernel/qcoreapplication.cpp:1064
#27 0x7f2a4f48e093 in QCoreApplication::sendEvent(QObject*, QEvent*)
(receiver=, event=) at
kernel/qcoreapplication.cpp:1462
#28 0x7f2a4f48eb33 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x55fe1fc036a0) at
kernel/qcoreapplication.cpp:1821
#29 0x7f2a4f4d4f58 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x55fe1fd39080) at kernel/qeventdispatcher_glib.cpp:277
#30 0x7f2a4d10f53b in g_main_dispatch (context=0x7f2a34000ee0) at
../glib/glib/gmain.c:3460
#31 g_main_context_dispatch (context=0x7f2a34000ee0) at
../glib/glib/gmain.c:4200
#32 0x7f2a4d16c219 in g_main_context_iter
[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=462860 --- Comment #22 from Nate Graham --- Right, the "Version fixed in" field says "23.04.1" -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 468712] Setting Kirigami.FormData.buddyFor to a null item crashes the calling app
https://bugs.kde.org/show_bug.cgi?id=468712
Nate Graham changed:
What|Removed |Added
Status|NEEDSINFO |CONFIRMED
Component|Quick Settings |general
Summary|Configurações do sistema|Setting
|fecha iniesperado |Kirigami.FormData.buddyFor
||to a null item crashes the
||calling app
Ever confirmed|0 |1
Target Milestone|--- |Not decided
Product|systemsettings |frameworks-kirigami
Assignee|plasma-b...@kde.org |kdelibs-b...@kde.org
Resolution|BACKTRACE |---
CC||m...@ratijas.tk,
||notm...@gmail.com
Version|5.27.4 |5.105.0
--- Comment #3 from Nate Graham ---
Ok, so here's what appears to be happening. Your activities database has become
corrupted:
> kf.activitiesstats: [Error at ResultSetPrivate::initQuery]: QSqlError("11",
> "Não foi possível obter a linha", "database disk image is malformed")
This causes the grid of "Frequently used" pages to not be populated. Then when
we try to set the buddy for the label to the grid's first child item, it
crashes because there are no child items. Because that page is the thing that
gets shown when System Settings launches, it crashes on launch.
Looks like Kirigami.FormLayout doesn't handle the case of the object specified
by Kirigami.FormData.buddyFor being null. We could work around this in the
code for the Quick Settings page, but ideally it would be fixed in Kirigami so
that app-specific workarounds aren't ever required anywhere.
Armando, you should be able to fix this yourself by deleting your kactivities
database and letting it get re-created. Delete
`~/.local/share/kactivitymanagerd/resources/database*` on your system and then
System Settings shouldn't crash anymore.
Finally, if you can attach
~/.local/share/kactivitymanagerd/resources/errors.log, we may be able to see
what happened to the database.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 468952] plasmashell crashes after logging in and reconnecting display
https://bugs.kde.org/show_bug.cgi?id=468952 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468952] New: plasmashell crashes after logging in and reconnecting display
https://bugs.kde.org/show_bug.cgi?id=468952 Bug ID: 468952 Summary: plasmashell crashes after logging in and reconnecting display Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: waqar@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY My PC is basically a laptop with an external display. I left the screen locked for about an hour or so and then returned to my PC. Moved the mouse, screen turns on and I tried to type my password in the lockscreen which had no effect. Disconnected the external display => then typed in the password which worked => immediately reconnected the display cable => plasmashell crashed. I wasn't able to find a bug with a similar backtrace so opened this one. Core was generated by `/usr/bin/plasmashell --no-respawn'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f172b24a8b9 in QQuickWindowPrivate::queryPointerEventInstance(QQuickPointerDevice*, QEvent::Type) const () from /usr/lib/libQt5Quick.so.5 [Current thread is 1 (Thread 0x7f17248f2f80 (LWP 135607))] (gdb) bt #0 0x7f172b24a8b9 in QQuickWindowPrivate::queryPointerEventInstance(QQuickPointerDevice*, QEvent::Type) const () at /usr/lib/libQt5Quick.so.5 #1 0x7f172b24acd9 in QQuickWindow::mouseGrabberItem() const () at /usr/lib/libQt5Quick.so.5 #2 0x7f172b24e92f in QQuickWindowPrivate::removeGrabber(QQuickItem*, bool, bool) () at /usr/lib/libQt5Quick.so.5 #3 0x7f172b2319c5 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #4 0x7f172b2319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #5 0x7f172b2319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #6 0x7f172b2319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #7 0x7f172b2319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #8 0x7f172b2319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #9 0x7f172b2319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #10 0x7f172b2319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #11 0x7f172b2319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #12 0x7f172b231b39 in QQuickItemPrivate::setVisible(bool) () at /usr/lib/libQt5Quick.so.5 #13 0x7f172b23fd43 in QQuickItem::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib/libQt5Quick.so.5 #14 0x7f172bbe09ba in PlasmaQuick::AppletQuickItem::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib/libKF5PlasmaQuick.so.5 #15 0x7f17200b0b3a in () at /usr/lib/qt/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #16 0x7f17200bfb39 in () at /usr/lib/qt/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #17 0x7f172ac3c823 in () at /usr/lib/libQt5Qml.so.5 #18 0x7f172ab752f2 in QV4::QObjectWrapper::setProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*, QV4::Value const&) () at /usr/lib/libQt5Qml.so.5 #19 0x7f172ab75876 in QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, QV4::Value const&) () at /usr/lib/libQt5Qml.so.5 #20 0x7f172ab759d7 in QV4::QObjectWrapper::virtualPut(QV4::Managed*, QV4::PropertyKey, QV4::Value const&, QV4::Value*) () at /usr/lib/libQt5Qml.so.5 #21 0x7f172ab23a75 in QV4::Lookup::setterFallback(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value&, QV4::Value const&) () at /usr/lib/libQt5Qml.so.5 #22 0x7f172ab8eaff in () at /usr/lib/libQt5Qml.so.5 #23 0x7f172ab94804 in () at /usr/lib/libQt5Qml.so.5 #24 0x7f172ab36c36 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () at /usr/lib/libQt5Qml.so.5 #25 0x7f172ac971ad in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () at /usr/lib/libQt5Qml.so.5 #26 0x7f172ac537f1 in QQmlBoundSignalExpression::evaluate(void**) () at /usr/lib/libQt5Qml.so.5 #27 0x7f172ac5476c in () at /usr/lib/libQt5Qml.so.5 #28 0x7f172ac7647f in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /usr/lib/libQt5Qml.so.5 #29 0x7f17296be740 in () at /usr/lib/libQt5Core.so.5 #30 0x7f172ac31fcb in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () at /usr/lib/libQt5Qml.so.5 #31 0x7f172969ea0c in QMetaProperty::write(QObject*, QVariant const&) const () at /usr/lib/libQt5Core.so.5 #32 0x7f17296baf52 in QObject::setProperty(c
[okular] [Bug 468951] clicking on bubble, nothing happens
https://bugs.kde.org/show_bug.cgi?id=468951 --- Comment #1 from Philippe ROUBACH --- I can't attach the pdf see https://www.ratp.fr/ca-vaut-le-detour#2-attached-to-anchor?utm_medium=email&utm_source=email&utm_campaign=newsletter_avril_2_objl4_Newsletter_avril_2023&utm_content=carte_poi they are many links to pdf you can pick the first one or others. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468916] Plasma Panel Visually Freezes
https://bugs.kde.org/show_bug.cgi?id=468916 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Nate Graham --- Is this 100% reproducible for you by launching an app without moving the pointer off of it while it loads? Also could you get a backtrace of what plasmashell is doing when it's hung? 1. Run `gdb attach $(pidof plasmashell)` in a terminal window 2. If it says "--Type for more, q to quit, c to continue without paging--" at the bottom of the terminal window, press the "c" key. 3. When you see a prompt that says "(gdb)", type "bt" and press the enter key 4. If it says "--Type for more, q to quit, c to continue without paging--" at the bottom of the terminal window, press the "c" key. 5. Copy-and-paste the contents of the terminal window into a comment here -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468951] New: clicking on bubble, nothing happens
https://bugs.kde.org/show_bug.cgi?id=468951 Bug ID: 468951 Summary: clicking on bubble, nothing happens Classification: Applications Product: okular Version: 20.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: philippe.roub...@free.fr Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. open the pdf 2. click on the blue bubbles 3. OBSERVED RESULT nothing happens EXPECTED RESULT The right part of the document changes. Operating System: openSUSE Tumbleweed 20230422 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 KDE GEARS 22.12.3 -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 468942] Attached documents work in unexpected ways
https://bugs.kde.org/show_bug.cgi?id=468942 --- Comment #1 from Volker Krause --- >From which email program did you import that PDF? This seems to happen due to getting garbage file names from the Intent in that case, I yet have to investigate whether that's a problem on our side or on the sending side. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468937] SMS not working
https://bugs.kde.org/show_bug.cgi?id=468937 Simon Redman changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Simon Redman --- Hi Justin, Please share your Android app version. There was an issue with 1.24.0 which broke SMS, which was fixed with 1.24.1 a few days later. Thanks, Simon -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466675] Dragging files to Icons-Only Task Manager no longer works on X11
https://bugs.kde.org/show_bug.cgi?id=466675 Nate Graham changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #9 from Nate Graham --- phoenix.a...@yahoo.com, is it also fixed for you in Plasma 5.27.4? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468903] ProgressBar animation causes redraws even if invisible
https://bugs.kde.org/show_bug.cgi?id=468903 Nate Graham changed: What|Removed |Added Version|git-stable-Plasma/5.27 |5.27.4 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 438610] When a device connects, it is positioned too far down for a moment, causing it to overlap the separator line
https://bugs.kde.org/show_bug.cgi?id=438610 Nate Graham changed: What|Removed |Added Version Fixed In||5.27.5 -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 438610] When a device connects, it is positioned too far down for a moment, causing it to overlap the separator line
https://bugs.kde.org/show_bug.cgi?id=438610 Nate Graham changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/bluedevil/commit/6201245 |ma/bluedevil/commit/1956411 |c45b96fd6f06cca9e532cd7a184 |588dbed54acb672d89ca003d880 |f4c743 |6684c4 --- Comment #24 from Nate Graham --- Git commit 1956411588dbed54acb672d89ca003d8806684c4 by Nate Graham, on behalf of Harald Sitter. Committed on 25/04/2023 at 15:07. Pushed by ngraham into branch 'Plasma/5.27'. applet: introduce a brief animation for section height estimates section delegates changing height is a bit buggy. as a simple bandaid try to delay the height change a bit via a behavior. NOTE: this doesn't actually animate, it's purely there for the delay aspect huge hack but it gives the view a better chance of figuring out a layout that works from my testing QTBUG-29148 (cherry picked from commit 6201245c45b96fd6f06cca9e532cd7a184f4c743) M +4-0src/applet/package/contents/ui/FullRepresentation.qml https://invent.kde.org/plasma/bluedevil/commit/1956411588dbed54acb672d89ca003d8806684c4 -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 438610] When a device connects, it is positioned too far down for a moment, causing it to overlap the separator line
https://bugs.kde.org/show_bug.cgi?id=438610 Harald Sitter changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/bluedevil/commit/6201245 ||c45b96fd6f06cca9e532cd7a184 ||f4c743 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #23 from Harald Sitter --- Git commit 6201245c45b96fd6f06cca9e532cd7a184f4c743 by Harald Sitter. Committed on 25/04/2023 at 11:27. Pushed by ngraham into branch 'master'. applet: introduce a brief animation for section height estimates section delegates changing height is a bit buggy. as a simple bandaid try to delay the height change a bit via a behavior. NOTE: this doesn't actually animate, it's purely there for the delay aspect huge hack but it gives the view a better chance of figuring out a layout that works from my testing QTBUG-29148 M +4-0src/applet/package/contents/ui/FullRepresentation.qml https://invent.kde.org/plasma/bluedevil/commit/6201245c45b96fd6f06cca9e532cd7a184f4c743 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392008] Inconsistent behavior of "People" Tag
https://bugs.kde.org/show_bug.cgi?id=392008 --- Comment #13 from MarcP --- Hi Gilles, Kind of. It's not a bug per se, but a result of the way Digikam treats face regions and regular keywords. Face tags and regular tags are "merged" (shown as a single element) in Digikam if they have the same name. But not all picture managers also write a regular tag when a face is added, and this can lead to inconsistencies. So basically the problematic behavior here is that some face tags might end up outside "People" when importing pictures with new people in it. That will happen if: 1) The first picture that contained that name only contained it as a regular tag. 2) Subsequent pictures also (or only) contain that same name as a face tag. In that case Digikam will first place that tag outside the People hierarchy (because it wasn't a face tag at first), but then, when scanning more pictures, even if they contain face regions with that name, will continue to place them on the already created tag, outside the "People" hierarchy. It's a rather minor thing once your library has been curated in Digikam, but it can be a bit annoying when importing pictures edited in another picture manager. And I don't see an easy solution either. If digikam automatically realized that that new tag is indeed a face tag, it could move it inside "People", but that is a very dangerous move, because you don't know if the user had previously placed that tag somewhere else on purpose. Anyway, feel free to do what you want with this report. I still think I'd like to see regular tags and people tags being treated as independent things, but this is not how digikam has been working until now. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 468792] When uninstalling application label says Downloading
https://bugs.kde.org/show_bug.cgi?id=468792 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||n...@kde.org Ever confirmed|0 |1 --- Comment #1 from Nate Graham --- Can confirm. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 468949] Loses logins constantly
https://bugs.kde.org/show_bug.cgi?id=468949 --- Comment #3 from Joshua Goins --- Sounds pretty bad then, thanks for the info -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 468949] Loses logins constantly
https://bugs.kde.org/show_bug.cgi?id=468949 Joshua Goins changed: What|Removed |Added Assignee|unassigned-b...@kde.org |j...@redstrate.com -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 468814] New Toot button is replicated when viewing a Thread
https://bugs.kde.org/show_bug.cgi?id=468814 Joshua Goins changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 456233] "Invalid dates provided" for any/all inputs -> cannot create/edit events
https://bugs.kde.org/show_bug.cgi?id=456233 Matej Starc changed: What|Removed |Added CC||matej.st...@protonmail.com --- Comment #1 from Matej Starc --- I also can't create any events. Even if I fill every input with something. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 464869] Installing updates corrupts Grub 2 ( unbootable system)
https://bugs.kde.org/show_bug.cgi?id=464869 --- Comment #3 from Lassi Väätämöinen --- (In reply to Lassi Väätämöinen from comment #2) > This issue reproduces on nearly every time updates are installed. Especially > when Discover reports "System upgrades" to be available, and those get > installed. Now upgraded kernel to 5.19.0-41. The issue happens systematically, when there is a "system upgrade" that ends up into post-boot KDE Neon splash screen with "Installing updates XX%" During this upgrade the Grub gets corrupt. Every time. Not sure if these issues with Breeze Grub theme are related: https://www.reddit.com/r/kdeneon/comments/z0vf4h/kde_neon_update_replaced_grub_with_broken_version/ https://www.reddit.com/r/kde/comments/8nkzvs/neon_seems_hardwired_to_look_for_breeze_grub/ For what it's worth, I don't even seem to have the Breeze theme on my system (after running Boot Repair Disc, which is a must with KDE Neon...) $ cat /etc/default/grub.d/99_breeze-grub.cfg GRUB_THEME=/boot/grub/themes/breeze/theme.txt $ sudo ls /boot/grub/themes/breeze/theme.txt ls: cannot access '/boot/grub/themes/breeze/theme.txt': No such file or directory Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 5.19.0-41-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz Memory: 22,7 GiB of RAM Graphics Processor: SVGA3D; build: RELEASE; LLVM; Manufacturer: innotek GmbH Product Name: VirtualBox System Version: 1.2 -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 468920] Feature request: Allow copying and pasting of image data between Tokodon and other desktop applications
https://bugs.kde.org/show_bug.cgi?id=468920 Joshua Goins changed: What|Removed |Added Assignee|unassigned-b...@kde.org |j...@redstrate.com -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 468920] Feature request: Allow copying and pasting of image data between Tokodon and other desktop applications
https://bugs.kde.org/show_bug.cgi?id=468920 Joshua Goins changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Joshua Goins --- This should be easy enough, we merged some technical changes recently where I can easily add a right-click > copy menu for images. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 468795] failed to connect to server, connection refused, please check your settings
https://bugs.kde.org/show_bug.cgi?id=468795 --- Comment #2 from Joshua Goins --- Thanks for figuring it out! I'll look into making sure it's less easy to get stuck this way -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468892] Snap thunderbird issues when added to the panel
https://bugs.kde.org/show_bug.cgi?id=468892 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||n...@kde.org --- Comment #1 from Nate Graham --- Is the menu item you're clicking on actually named "Add to Panel", or does it instead say, "Pin to Task Manager"? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392562] Getting Started, Setting up - database, image storage locations
https://bugs.kde.org/show_bug.cgi?id=392562 --- Comment #3 from caulier.gil...@gmail.com --- @Henri digiKam 8.0.0 is out. This file still valid ? Best regards -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392008] Inconsistent behavior of "People" Tag
https://bugs.kde.org/show_bug.cgi?id=392008 --- Comment #12 from caulier.gil...@gmail.com --- @MarcP digiKam 8.0.0 is out. This file still valid ? Best regards -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468873] plasmashell always crashes on start with X11OutputOrderWatcher::refresh() when xrandr isn't available
https://bugs.kde.org/show_bug.cgi?id=468873 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Summary|plasmashell always crashes |plasmashell always crashes |on start|on start with ||X11OutputOrderWatcher::refr ||esh() when xrandr isn't ||available CC||n...@kde.org Resolution|--- |NOT A BUG --- Comment #2 from Nate Graham --- Aha, that does makes sense. Unfortunately we do not support Xinerama, sorry. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 468884] Can't open some self-made libaom avif photos anymore; sxiv opens them with no problem
https://bugs.kde.org/show_bug.cgi?id=468884 --- Comment #5 from Joshua Goins --- Interesting that your version of sxiv doesn't open it, sxiv on Arch (version 26-1) can open it -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467996] 5.27 reversed screen order for "Window to Next / Previous" Screen
https://bugs.kde.org/show_bug.cgi?id=467996 --- Comment #13 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/4024 -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 468949] Loses logins constantly
https://bugs.kde.org/show_bug.cgi?id=468949 --- Comment #2 from Liam Dawe --- We're talking probably less than an hour before it loses the logins. Since I keep closing and re-opening it (as it seems to not close to tray). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 391115] Very slow search, full text search (FTS) proposition for huge speedup.
https://bugs.kde.org/show_bug.cgi?id=391115 --- Comment #11 from caulier.gil...@gmail.com --- @Michał digiKam 8.0.0 is out. This file still valid ? Best regards Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 468949] Loses logins constantly
https://bugs.kde.org/show_bug.cgi?id=468949 --- Comment #1 from Joshua Goins --- Interesting, this should happen less for 23.04.0 but I haven't tested the flatpak version myself. I'll check up on it soon, how long is "closed for a while" - like a day? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448567] [Wayland] Text in Overview effect for desktops list and window titles is blocky on scaled displays
https://bugs.kde.org/show_bug.cgi?id=448567 --- Comment #14 from Nate Graham --- Thanks for following up, Connor! By any chance is https://bugs.kde.org/show_bug.cgi?id=451259 also fixed for you as of that commit? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468950] Doesn't pair with Windows at all, doesn't even see it
https://bugs.kde.org/show_bug.cgi?id=468950 --- Comment #1 from mailinglist...@gmail.com --- it did pair until recently, but cannot try older testflight builds because you do not make them available -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468950] New: Doesn't pair with Windows at all, doesn't even see it
https://bugs.kde.org/show_bug.cgi?id=468950 Bug ID: 468950 Summary: Doesn't pair with Windows at all, doesn't even see it Classification: Applications Product: kdeconnect Version: unspecified Platform: Other OS: iOS Status: REPORTED Severity: critical Priority: NOR Component: ios-application Assignee: lucas.w...@tuta.io Reporter: mailinglist...@gmail.com Target Milestone: --- SUMMARY Doesn't pair with Windows STEPS TO REPRODUCE 1. install app 2. refresh discovery, even try manual IP 3. doesn't see Windows OBSERVED RESULT no Windows EXPECTED RESULT Windows SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Please halt everything and focus on fixing pairing with Windows. Without this feature the app is effectively useless to me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467996] 5.27 reversed screen order for "Window to Next / Previous" Screen
https://bugs.kde.org/show_bug.cgi?id=467996 --- Comment #12 from Nate Graham --- We are getting off-topic regarding the original bug report. Let's keep the conversation on that topic please. Also let's try to avoid being bitter and spiteful, which makes developers *less* likely to do what you're asking, not more. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467996] 5.27 reversed screen order for "Window to Next / Previous" Screen
https://bugs.kde.org/show_bug.cgi?id=467996 --- Comment #11 from mdcclxv --- (In reply to Natalie Clarius from comment #10) > > Would it really be so hard to expose the display order number to the user? > > Yes. And for such a niche feature, where people use three or more screens > *and* do not want them ordered top to bottom/left to right *and* want to use > keyboard shortcuts to move between them *and* do not want to use the > directional shortcuts which are specifically for this purpose *and* would > bother finding, understanding and using such a setting, it is not worth it. Wow!! Three or more display is not niche at all nowadays, wake up to reality. I'm glad to see, again, an open minded attitude in the KDE dev world. You guys never disappoint. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467996] 5.27 reversed screen order for "Window to Next / Previous" Screen
https://bugs.kde.org/show_bug.cgi?id=467996 --- Comment #10 from Natalie Clarius --- > Would it really be so hard to expose the display order number to the user? Yes. And for such a niche feature, where people use three or more screens *and* do not want them ordered top to bottom/left to right *and* want to use keyboard shortcuts to move between them *and* do not want to use the directional shortcuts which are specifically for this purpose *and* would bother finding, understanding and using such a setting, it is not worth it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467996] 5.27 reversed screen order for "Window to Next / Previous" Screen
https://bugs.kde.org/show_bug.cgi?id=467996 --- Comment #9 from mdcclxv --- (In reply to Natalie Clarius from comment #8) > > I was also expecting that the "Screen Priorities" setting would do just > > that. So what's the purpose of that setting then? > > It is explained in the question mark on that setting. Problematic, but I don't want to steal the thread, so I'm giving up on this. > > The order of the screens for previous/next should work the same as the order > of virtual desktops, which there are analogous shortcuts for: top to bottom, > left to right. If you want more precise control, you can use the "to the > left/right/top/bottom" shortcuts instead. You do realize that it is waaay more comfortable to always press the same single key two or three times than deciding to press various keys depending on the desired outcome. Would it really be so hard to expose the display order number to the user? They already have that internally, so why not giving access to it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468904] External monitors connected to dGPU (NVIDIA) no longer working after upgrading to kde-plasma/plasma-meta-5.27.4
https://bugs.kde.org/show_bug.cgi?id=468904 Nate Graham changed: What|Removed |Added CC||k...@davidedmundson.co.uk Component|general |general Product|kde |plasmashell Target Milestone|--- |1.0 Assignee|unassigned-b...@kde.org |plasma-b...@kde.org Version|unspecified |5.27.4 --- Comment #5 from Nate Graham --- Sorry this happened. In Plasma 5.27 we implemented a new system for mapping Plasma desktops and panels to screens that is fundamentally more correct by design, and as a result much more robust. We also added code to migrate old settings to this new system. Unfortunately, due to the non-determinism baked into the old system, the migration code works better the simpler your arrangement of screens, desktops, and panels was. For complex arrangements, we've seen a few reports like this. The good news is that this shouldn't recur going forward due to the new system we have in Plasma 5.27. So hopefully this is the last time it should ever happen! -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 468824] Kubuntu Focus is not in the list of KDE patrons
https://bugs.kde.org/show_bug.cgi?id=468824 Phu H. Nguyen changed: What|Removed |Added Latest Commit|https://invent.kde.org/webs |https://invent.kde.org/webs |ites/ev-kde-org/commit/d612 |ites/ev-kde-org/commit/c5b6 |cede9f4b3296298331f6c26fc67 |65c1b841f9cdbbcd06e3f10fb4d |e659277b9 |5fc723bdb --- Comment #5 from Phu H. Nguyen --- Git commit c5b665c1b841f9cdbbcd06e3f10fb4d5fc723bdb by Phu Nguyen. Committed on 24/04/2023 at 09:39. Pushed by ngraham into branch 'master'. Add Enioka to the Supporters list It was only moved around on https://ev.kde.org/consultants/ but removed from https://ev.kde.org/supporting-members/ M +1-0supporting-members.md https://invent.kde.org/websites/ev-kde-org/commit/c5b665c1b841f9cdbbcd06e3f10fb4d5fc723bdb -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467741] Panel and panel widgets lack transparency
https://bugs.kde.org/show_bug.cgi?id=467741 Nate Graham changed: What|Removed |Added Target Milestone|--- |1.0 Component|Titlebar menu button/popup |Panel Product|kded-appmenu|plasmashell -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467996] 5.27 reversed screen order for "Window to Next / Previous" Screen
https://bugs.kde.org/show_bug.cgi?id=467996 --- Comment #8 from Natalie Clarius --- > I was also expecting that the "Screen Priorities" setting would do just > that. So what's the purpose of that setting then? It is explained in the question mark on that setting. The order of the screens for previous/next should work the same as the order of virtual desktops, which there are analogous shortcuts for: top to bottom, left to right. If you want more precise control, you can use the "to the left/right/top/bottom" shortcuts instead. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468948] I am using Teams client for Linux and after a while, plasmashell crashes after a notification window appears.
https://bugs.kde.org/show_bug.cgi?id=468948 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Bug Janitor Service --- Thank you for the bug report! However Plasma 5.24.7 is no longer eligible for support or maintenance from KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to a supported version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. If you need support for Plasma 5.24.7, please contact your distribution, who bears the responsibility of providing support for older releases that are no longer supported by KDE. If you can reproduce the issue after upgrading to a supported version, feel free to re-open this bug report. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468932] Segmentation fault when editing IPTC Copyright
https://bugs.kde.org/show_bug.cgi?id=468932 --- Comment #7 from caulier.gil...@gmail.com --- yes, you are right Maik. feel free to fix it in git, i'm busy in my office currently -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465712] After upgrade to 5.27, periodic visual glitches when monitors' refresh rates don't match
https://bugs.kde.org/show_bug.cgi?id=465712 --- Comment #19 from Liam Dawe --- I can confirm that as of now it does seem to work properly :) -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 468949] New: Loses logins constantly
https://bugs.kde.org/show_bug.cgi?id=468949 Bug ID: 468949 Summary: Loses logins constantly Classification: Applications Product: Tokodon Version: 23.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: liamd...@gmail.com CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- SUMMARY Trying out Tokodon in the latest release from Flathub, and it just seems after a while of closing it that all logins just vanish. It's making the app somewhat useless to have to constantly add the accounts back in. STEPS TO REPRODUCE 1. Test it on Fedora 38 with Flathub 2. Watch as accounts vanish after you close and leave it closed a while. SOFTWARE/OS VERSIONS Fedora 38 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459517] [master] Performance when working under filter layers is significantly worse (likely due to layer thumbnail generation)
https://bugs.kde.org/show_bug.cgi?id=459517 Dmitry Kazakov changed: What|Removed |Added Status|REOPENED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Dmitry Kazakov --- Mark as waiting for info -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459517] [master] Performance when working under filter layers is significantly worse (likely due to layer thumbnail generation)
https://bugs.kde.org/show_bug.cgi?id=459517 Dmitry Kazakov changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454385] Desktop icons disappear when focusing an app following unplugging an external/secondary screen
https://bugs.kde.org/show_bug.cgi?id=454385 --- Comment #10 from Cuchac --- Created attachment 158419 --> https://bugs.kde.org/attachment.cgi?id=158419&action=edit journal -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454385] Desktop icons disappear when focusing an app following unplugging an external/secondary screen
https://bugs.kde.org/show_bug.cgi?id=454385 --- Comment #9 from Cuchac --- Created attachment 158418 --> https://bugs.kde.org/attachment.cgi?id=158418&action=edit bt full with debug symbols -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454385] Desktop icons disappear when focusing an app following unplugging an external/secondary screen
https://bugs.kde.org/show_bug.cgi?id=454385 Cuchac changed: What|Removed |Added CC||cuc...@email.cz Platform|Other |Archlinux Version|5.24.90 |5.27.4 --- Comment #8 from Cuchac --- I still experience this issue. See attached "bt full" with debug symbols. It happens during when switching screens (docking station) or wake from sleep. Plasma 5.27.4 kded 5.105.0 Attached also journal from the crash. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465489] Selection Mode still gets triggered by Space, even after reassigning the shortcut
https://bugs.kde.org/show_bug.cgi?id=465489 Felix Ernst changed: What|Removed |Added Latest Commit||https://invent.kde.org/syst ||em/dolphin/commit/7b6a67e52 ||0c04f56b4b05fa26b252177398d ||f6df Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #12 from Felix Ernst --- Git commit 7b6a67e520c04f56b4b05fa26b252177398df6df by Felix Ernst, on behalf of Eugene Popov. Committed on 25/04/2023 at 13:05. Pushed by felixernst into branch 'master'. Fix activating the Selection Mode with a keyboard shortcut If a spacebar is used as a keyboard shortcut to activate the Selection Mode, then allow this shortcut to be triggered only if the view has a keyboard focus. M +14 -0src/dolphinmainwindow.cpp M +3-0src/dolphinmainwindow.h M +12 -4src/kitemviews/kitemlistcontroller.cpp M +5-0src/kitemviews/kitemlistcontroller.h M +5-5src/kitemviews/private/kitemlistkeyboardsearchmanager.cpp M +5-6src/kitemviews/private/kitemlistkeyboardsearchmanager.h M +5-0src/views/dolphinview.cpp M +11 -3src/views/dolphinview.h https://invent.kde.org/system/dolphin/commit/7b6a67e520c04f56b4b05fa26b252177398df6df -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 468605] auto-correction incorrectly changes dot to arrow in floating-point literals when using uniform initialization
https://bugs.kde.org/show_bug.cgi?id=468605 --- Comment #4 from Igor Kushnir --- Also take a look at related functions in include/clang-c/CXDiagnostic.h (or include/clang-c/Index.h). For example, I think clang_getDiagnosticSpelling() can potentially clarify the meaning of the single completion result libclang comes up with for "2->". -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 468605] auto-correction incorrectly changes dot to arrow in floating-point literals when using uniform initialization
https://bugs.kde.org/show_bug.cgi?id=468605 --- Comment #3 from Igor Kushnir --- (In reply to Alessandro Carinelli from comment #2) > Checking that m_results->Numresults is also different from 1 on line 984 > seems to fix the issue but I have no idea about what this variable > represents and I found no comments about it so I don't know if this breaks > anything else. Starting at the line 966 of the file plugins/clang/codecompletion/context.cpp, KDevelop takes a code fragment that leads up to and includes '.' (stored in the variable trimmedText); temporarily replaces this last dot with '->'; and then asks libclang to try and come up with possible completions after that arrow. If libclang finds a way to complete the arrow (NumResults [= the number of completion results] is positive), KDevelop assumes that the code with the arrow would compile given some more typing or completion after the arrow, decides that the dot should indeed be replaced with an arrow and does just that. So no, checking that m_results->Numresults is also different from 1 does not seem to be a good idea, at least not on the surface. You could check what is that strange completion result that libclang finds after "2." and see if this completion is something KDevelop should ignore here. You can start with debug-printing (via e.g. qCritical()) str.c_str(). The string is clearly not equal to "Parse Issue", but maybe it is something else, which should also be ignored. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468948] I am using Teams client for Linux and after a while, plasmashell crashes after a notification window appears.
https://bugs.kde.org/show_bug.cgi?id=468948 Yilmaz changed: What|Removed |Added CC||yilk...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459517] [master] Performance when working under filter layers is significantly worse (likely due to layer thumbnail generation)
https://bugs.kde.org/show_bug.cgi?id=459517 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com --- Comment #2 from Dmitry Kazakov --- Hi, tomtomtom! Could you please test the bug in the current master? I cannot reproduce the issue it seems. Could you make a video? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468948] New: I am using Teams client for Linux and after a while, plasmashell crashes after a notification window appears.
https://bugs.kde.org/show_bug.cgi?id=468948 Bug ID: 468948 Summary: I am using Teams client for Linux and after a while, plasmashell crashes after a notification window appears. Classification: Plasma Product: plasmashell Version: 5.24.7 Platform: Kubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: yilk...@gmail.com CC: k...@privat.broulik.de Target Milestone: 1.0 Created attachment 158417 --> https://bugs.kde.org/attachment.cgi?id=158417&action=edit Crash Report Application: plasmashell (5.24.7) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 5.15.0-70-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.2 LTS DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I am using Teams client for Linux and after a while, plasmashell crashes after a notification window appears. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted [KCrash Handler] #4 0x7f5947975195 in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x7f5934191994) at ./nptl/futex-internal.c:57 #5 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x7f5934191994) at ./nptl/futex-internal.c:87 #6 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7f5934191994, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #7 0x7f5947977ac1 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f5934191940, cond=0x7f5934191968) at ./nptl/pthread_cond_wait.c:503 #8 ___pthread_cond_wait (cond=0x7f5934191968, mutex=0x7f5934191940) at ./nptl/pthread_cond_wait.c:627 #9 0x7f5947e08ceb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f59499fc78a in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7f59499fdb0a in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7f59483e25a5 in QWindow::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #13 0x7f5948ce4713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f5947fefe3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f59483d76a1 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #16 0x7f59483aba2c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #17 0x7f5942f0cd6e in () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #18 0x7f59463ccd3b in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7f59464216c8 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7f59463ca3e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7f59480490b8 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f5947fee75b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f5947ff6cf4 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x56276d08fdce in () #25 0x7f594790dd90 in __libc_start_call_main (main=main@entry=0x56276d08ef70, argc=argc@entry=1, argv=argv@entry=0x7ffe52052f88) at ../sysdeps/nptl/libc_start_call_main.h:58 #26 0x7f594790de40 in __libc_start_main_impl (main=0x56276d08ef70, argc=1, argv=0x7ffe52052f88, init=, fini=, rtld_fini=, stack_end=0x7ffe52052f78) at ../csu/libc-start.c:392 #27 0x56276d08fef5 in () [Inferior 1 (process 5281) detached] Possible duplicates by query: bug 468272, bug 468243, bug 466976, bug 466395, bug 465663. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in a multi xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 --- Comment #15 from Andreas Sturmlechner --- (In reply to Andreas Sturmlechner from comment #7) > Please create an MR over at https://invent.kde.org/plasma/plasma-workspace > instead of attaching here, it will get much more attention. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458475] Performance highly degraded with filters
https://bugs.kde.org/show_bug.cgi?id=458475 Dmitry Kazakov changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit|785619b |https://invent.kde.org/grap ||hics/krita/commit/faee475b1 ||6081146c760aa2ff33aca48a03d ||26d5 Resolution|--- |FIXED --- Comment #12 from Dmitry Kazakov --- Git commit faee475b16081146c760aa2ff33aca48a03d26d5 by Dmitry Kazakov. Committed on 25/04/2023 at 12:48. Pushed by dkazakov into branch 'master'. Fix a huge slowdown with mesh transform added as a transform mask The Mesh Transform used to have very rough approximations for needRect and changeRect functions (basically, all touched patches were dragged into the changeRect). It caused each update thread to update the whole image, instead of its own part of it (which was slow). The patch introduces a better approximation of need/changeRects using a binary search in the param space followed by random rect sampling. M +1-0libs/global/CMakeLists.txt A +215 -0libs/global/KisBezierPatchParamSpaceUtils.h [License: GPL(v2.0+)] A +82 -0libs/global/KisBezierPatchParamToSourceSampler.h [License: GPL(v2.0+)] M +1-1libs/global/KisBezierUtils.h M +17 -0libs/global/KisCppQuirks.h A +80 -0libs/global/KisSampleRectIterator.cpp [License: GPL(v2.0+)] A +69 -0libs/global/KisSampleRectIterator.h [License: GPL(v2.0+)] M +12 -0libs/global/kis_algebra_2d.h M +170 -12 libs/image/KisBezierTransformMesh.cpp M +9-0libs/image/KisBezierTransformMesh.h M +0-1libs/image/kis_transform_mask.cpp M +192 -0libs/image/tests/kis_mesh_transform_worker_test.cpp M +8-0libs/image/tests/kis_mesh_transform_worker_test.h M +16 -0sdk/tests/testutil.h https://invent.kde.org/graphics/krita/commit/faee475b16081146c760aa2ff33aca48a03d26d5 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468630] .cbz files containing .webp or .tiff cannot be opened
https://bugs.kde.org/show_bug.cgi?id=468630 Sune Vuorela changed: What|Removed |Added CC||k...@pusling.com --- Comment #5 from Sune Vuorela --- (In reply to flampingog from comment #2) > Created attachment 158178 [details] > test .cbz file with one .webp image My okular opens it on linux. Do you have in your okular install the windows equivalent of /usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libqwebp.so ? it could be called plugins\imageformats\qwebp.dll -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 468947] New: VirtualBox VM memoryused not reported
https://bugs.kde.org/show_bug.cgi?id=468947 Bug ID: 468947 Summary: VirtualBox VM memoryused not reported Classification: Applications Product: plasma-systemmonitor Version: 5.27.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: meve...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Run a VM in Virtualbox (in my case Neon) 2. Look in plasma-system-monitor in the host, the process view for the VirtualBoxVM process OBSERVED RESULT Memory column empty for the VM process. EXPECTED RESULT some memory usage is reported for the VM SOFTWARE/OS VERSIONS Operating System: Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-40-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3800X 8-Core Processor Memory: 31.3 Gio of RAM -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 468605] auto-correction incorrectly changes dot to arrow in floating-point literals when using uniform initialization
https://bugs.kde.org/show_bug.cgi?id=468605 --- Comment #2 from Alessandro Carinelli --- The substitution in object happens at line 1000 in file plugins/clang/codecompletion/context.cpp, before that (line 984) the value of m_results->NumResults is checked to be different from 0. I noticed that in the case of this bug such value is always 1 while in other cases it is bigger. Checking that m_results->Numresults is also different from 1 on line 984 seems to fix the issue but I have no idea about what this variable represents and I found no comments about it so I don't know if this breaks anything else. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in a multi xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 Allistar changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in a multi xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 Allistar changed: What|Removed |Added Attachment #150133|0 |1 is obsolete|| --- Comment #14 from Allistar --- Created attachment 158416 --> https://bugs.kde.org/attachment.cgi?id=158416&action=edit Patch for 5.27.4.1 to filter monitors by serial number -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in a multi xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 --- Comment #13 from Allistar --- I have tried with 5.27.4.1 (the currently stable version on Gentoo) and the problem is still there. I have fixed this locally by modifying plasma-workspace/shell/screenpool.cpp by telling it to ignore two of my monitors by their serial number. I'll attach my patch file. The fundamental issue is the same and that's that the code identifies monitors by QScreen.name(). This is not unique. It's possible to have two monitors on the same system with the same name. The name is the xrandr output name. I have these monitors on my system: GPU 1: DVI-I-1, HDMI-0, DVI-D-0, HDMI-1 GPU 2: DVI-I-1, DVI-D-0 Note that there are two monitors that both have the name "DV!-I-1" and "DVI-D-0". The bug is primarily in ScreenPool::handleOutputOrderChanged and handleScreenAdded. The class "OutputOrderWatcher" also has a bug because it's using the screen name to identify the screen. My patch looks in plasmashellrc for a "[IgnoredScreens]" setting which is a list of the serial numbers to ignore. I've modified handleScreenAdded and handleOutputOrderChanged to skip over QScreens that have a matching serial number. A proper fix for this is to not assume the screen name is unique and instead have a method that returns something that is unique. I recommend the screen name prefixed with the DISPLAY number (e.g. ":0.0" or "0.1"). I have used serial number because that works for me but I don't think monitors will always provide a serial number. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 468440] Global Application shortcuts are slower than they could be
https://bugs.kde.org/show_bug.cgi?id=468440 Nicolas Fella changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|CONFIRMED |RESOLVED --- Comment #3 from Nicolas Fella --- ah, that explains a lot. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 468945] When open a playlist file (.m3u) outside of the program, the player opens without the contents of the playlist.
https://bugs.kde.org/show_bug.cgi?id=468945 george fb changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from george fb --- Already fixed. You can try it out by installing from kde remote https://userbase.kde.org/Tutorials/Flatpak#Nightly_KDE_Apps -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 468946] Kast does not start
https://bugs.kde.org/show_bug.cgi?id=468946 b...@mogwai.be changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from b...@mogwai.be --- Could you provide some more information? E.g. start up kasts from the command line, and then copy-paste the messages that will appear. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 468946] Kast does not start
https://bugs.kde.org/show_bug.cgi?id=468946 kev.metalw...@gmail.com changed: What|Removed |Added CC||kev.metalw...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 468946] New: Kast does not start
https://bugs.kde.org/show_bug.cgi?id=468946 Bug ID: 468946 Summary: Kast does not start Classification: Applications Product: kasts Version: 23.04.0 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: kev.metalw...@gmail.com Target Milestone: --- SUMMARY KAST FAILS TO START STEPS TO REPRODUCE 1. installed from Discover 2. ALT+ENTER and type kast 3. Enter OBSERVED RESULT the icon appears on the taskbar briefly and then disappears EXPECTED RESULT the application starts SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 5.19.0-40-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics Manufacturer: HP Product Name: HP Laptop 15-dy1xxx ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 357288] Setting "Screen Energy Saving" in "Energy Saving" config has no effect
https://bugs.kde.org/show_bug.cgi?id=357288 --- Comment #19 from mjay --- (In reply to mjay from comment #18) > (In reply to Al from comment #14) > > I am having similar issues here with the power saving not keeping the screen > > blanked. I can set it to blank the screen (in 1 minute for example), and it > > will blank all 3 monitors. They will go blank, even go into their power save > > mode for a second, but then everything comes right back on again. It does > > the same if I set a shortcut to blank the screen - goes off but then back on > > again in about 10 seconds or so. I am using an AMD X3900 X570 system, Radeon > > RX 5500XT video, 3 monitors (one of them is a different size than the other > > 2 FWIW) similar to a related report listed under bug 440350. Currently > > running the latest version of Fedora 35 KDE Plasma 5.23.4 Framework 5.89.0 > > kernel 5.15.12-200 and using X11 (Wayland does not work well here - maybe > > that is a clue). > > This sounds like a similar problem i had with Kscreen2. Kscreen2 would, note > that a > displayport connected monitor was powered down, then kscreen2, then moved > the windows > off that monitor and onto other monitors, tripping a event, powering them > back on again. EDIT: My problem, was not xscreen2, but rather my monitors in a hdmi/dp setup, with its input source detection, that was the culprit. not xscreen2, see https://gitlab.freedesktop.org/drm/amd/-/issues/1719 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 357288] Setting "Screen Energy Saving" in "Energy Saving" config has no effect
https://bugs.kde.org/show_bug.cgi?id=357288 mjay changed: What|Removed |Added CC||michaeljense...@hotmail.com --- Comment #18 from mjay --- (In reply to Al from comment #14) > I am having similar issues here with the power saving not keeping the screen > blanked. I can set it to blank the screen (in 1 minute for example), and it > will blank all 3 monitors. They will go blank, even go into their power save > mode for a second, but then everything comes right back on again. It does > the same if I set a shortcut to blank the screen - goes off but then back on > again in about 10 seconds or so. I am using an AMD X3900 X570 system, Radeon > RX 5500XT video, 3 monitors (one of them is a different size than the other > 2 FWIW) similar to a related report listed under bug 440350. Currently > running the latest version of Fedora 35 KDE Plasma 5.23.4 Framework 5.89.0 > kernel 5.15.12-200 and using X11 (Wayland does not work well here - maybe > that is a clue). This sounds like a similar problem i had with Kscreen2. Kscreen2 would, note that a displayport connected monitor was powered down, then kscreen2, then moved the windows off that monitor and onto other monitors, tripping a event, powering them back on again. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 357819] Korganizer doesn't send calendar events to Google account
https://bugs.kde.org/show_bug.cgi?id=357819 Salvatore changed: What|Removed |Added CC||sannythebes...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468932] Segmentation fault when editing IPTC Copyright
https://bugs.kde.org/show_bug.cgi?id=468932 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #6 from Maik Qualmann --- Gilles, I think this is the cause. It needs to be changed to QPlainTextEdit. The same in DTextEdit at this point. https://invent.kde.org/graphics/digikam/-/blob/master/core/libs/widgets/text/dplaintextedit.cpp#L217 Maik -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 448987] KDE Akonadi_indexing_agent crashes
https://bugs.kde.org/show_bug.cgi?id=448987 Carl Schwan changed: What|Removed |Added CC||c...@carlschwan.eu Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Carl Schwan --- This seems to be an issue in Wayland, since the report is more than a year old and a lot hapenned with Wayland lately. I'm closing this. Feel free to reopen if this happens again -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 451511] el bolquedor de pantalla se actuiva y escucho musoca en firefox
https://bugs.kde.org/show_bug.cgi?id=451511 Carl Schwan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME CC||c...@carlschwan.eu -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466559] Discover does not wait for the Polkit auth when updating Flatpaks and thus fails
https://bugs.kde.org/show_bug.cgi?id=466559 --- Comment #4 from Harald Sitter --- Ok -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 453457] akonadi_indexing service crashed
https://bugs.kde.org/show_bug.cgi?id=453457 --- Comment #2 from Carl Schwan --- *** Bug 459815 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 459815] Akonadi index crashes and closes kmail
https://bugs.kde.org/show_bug.cgi?id=459815 Carl Schwan changed: What|Removed |Added Status|REPORTED|RESOLVED CC||c...@carlschwan.eu Resolution|--- |DUPLICATE --- Comment #1 from Carl Schwan --- *** This bug has been marked as a duplicate of bug 453457 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 448750] SVGs corrupted on upgrade until SVG cache is cleared
https://bugs.kde.org/show_bug.cgi?id=448750 --- Comment #10 from Harald Sitter --- I'd be interested in someone uploading a set of broken cache files. It's exceptionally hard to guess what the problem might be without them. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466559] Discover does not wait for the Polkit auth when updating Flatpaks and thus fails
https://bugs.kde.org/show_bug.cgi?id=466559 --- Comment #3 from Ilya Bizyaev --- I wouldn't call it niche when it's the default in one of the major distros -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #44 from Vincent PINON --- > The error occurred several times again, and actually "kscreenlocker" line > doesn't appear every time in journalctl, whereas kwin_wayland failure is > always here. > It was still on 5.26.90 (latest available in Debian testing) ; I'm > installing 5.27.2 from Debian unstable, will see in the next days and let > you know... I forgot to report back: I still had the crash with plasma 5.27.2. It is always in kwin_wayland, so *not this bug*. Since then I reverted to X11 session to avoid this annoyance, so I don't track the problem anymore, sorry. -- You are receiving this mail because: You are watching all bug changes.
