[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #155 from Rainer Klier --- hi, it really works! it is fixed! yesterday i installed KDE frameworks 5.27.2, and now the issue is gone! thank you so much. can anybody, in short words, describe, what the issue was about? it must have been something which was introduced in KDE frameworks 5.26. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872
--- Comment #22 from Jiri Slaby ---
(In reply to Jiri Slaby from comment #21)
> ep is corrupted:
> 1639if (QQmlEngine *qmlEngine = that->engine()->qmlEngine()) {
> 1640QQmlEnginePrivate *ep = QQmlEnginePrivate::get(qmlEngine);
> 1641if (ep && ep->propertyCapture) {
> 1642qDebug() << __func__ << ep << ep->propertyCapture;
> 1643ep->propertyCapture->captureProperty(that->object(), -1,
> role->index, /*doNotify=*/ false);
> 1644}
> 1645}
>
> This prints:
> virtualGet 0xb706dff0 0x8dc35e5b
...
> Many values/pointers are 0x8dc35e5b or -1879038348/0x90002674 or
> 0xc483ffe0/-997982240 or their combination. That is obviously bogus.
Ah, because it's not ep at that location -- 0xb706dff0 is code, not data:
> (gdb) x/24x 0xb706dff0
> 0xb706dff0 <_ZN20QQmlDelayedCallQueue11qt_metacastEPKc>:0x39e85356
> 0x81ffe0f8 0x1a1265c3 0x04ec8300
> 0xb706e000 <_ZN20QQmlDelayedCallQueue11qt_metacastEPKc+16>: 0x1424748b
> 0x4074f685 0x8d08ec83 0xed9c9483
> 0xb706e010 <_ZN20QQmlDelayedCallQueue11qt_metacastEPKc+32>: 0xe85650ff
> 0xffe076c8 0x8910c483 0x24448bc2
> 0xb706e020 <_ZN20QQmlDelayedCallQueue11qt_metacastEPKc+48>: 0x75d28510
> 0x04c4830b 0x8dc35e5b 0x90002674
> 0xb706e030 <_ZN20QQmlDelayedCallQueue11qt_metacastEPKc+64>: 0x5608ec83
> 0x5756e850 0xc483ffe0 0x04c48310
> 0xb706e040 <_ZN20QQmlDelayedCallQueue11qt_metacastEPKc+80>: 0x8dc35e5b
> 0x90002674 0xd9ebc031 0x0026748d
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 466597] Popup windows sometimes glitch desktop background as content when appearing
https://bugs.kde.org/show_bug.cgi?id=466597 --- Comment #4 from dsyrzm...@mozmail.com --- I tried wayland, and it indeed had issues, but i was able to start unity and rider to test their behaviour. There it's somewhat different; it doesn't flicker just sometimes and with the desktop glitching inside the window content, but instead every time a popup appears, only with a black background as content. It's a little less distracting because it's atleast a plain color instead of visual noise, but it's still there in a way. Although i would prefer that or better a neutral grey or even the theme's window color to the current behaviour. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872
--- Comment #21 from Jiri Slaby ---
(In reply to Hans Brage from comment #0)
> #7 0xb442e75c in QV4::ModelObject::virtualGet(QV4::Managed const*,
> QV4::PropertyKey, QV4::Value const*, bool*) (m=0xa15c0820, id=...,
> receiver=0xa15c0820, hasProperty=0x0) at
> /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/qmlmodels/
> qqmllistmodel.cpp:1639
ep is corrupted:
1639if (QQmlEngine *qmlEngine = that->engine()->qmlEngine()) {
1640QQmlEnginePrivate *ep = QQmlEnginePrivate::get(qmlEngine);
1641if (ep && ep->propertyCapture) {
1642qDebug() << __func__ << ep << ep->propertyCapture;
1643ep->propertyCapture->captureProperty(that->object(), -1,
role->index, /*doNotify=*/ false);
1644}
1645}
This prints:
virtualGet 0xb706dff0 0x8dc35e5b
So:
> (gdb) p *(QQmlEnginePrivate *)0xb706dff0
> $3 = { = { = { =
> {_vptr.QObjectData = 0x39e85356, q_ptr = 0x81ffe0f8, parent = 0x1a1265c3,
> children = {> = {}, {p = {
> static shared_null = {ref = {atomic = {_q_value =
> std::atomic = { -1 }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d
> = 0x4ec8300}, d = 0x4ec8300}}, isWidget = 1, blockSig = 1, wasDeleted = 0,
> isDeletingChildren = 1, sendChildEvents = 0, receiveChildEvents = 0,
> isWindow = 0, deleteLaterCalled = 1, unused = 1320052, postedEvents =
> 1081407109, metaObject = 0x8d08ec83}, extraData = 0xed9c9483,
> threadData = {> = {_q_value =
> std::atomic = { 0xe85650ff }}, }, connections
> = {> = {
> _q_value = std::atomic = {
> 0xffe076c8 }}, }, {currentChildBeingDeleted = 0x8910c483,
> declarativeData = 0x8910c483},
> sharedRefcount =
> {> = {_q_value =
> std::atomic = { 0x24448bc2 }}, data fields>}},
> mutex = { = { = {d_ptr = {_q_value =
> std::atomic = { 0x75d28510 }}}, }, fields>}, uiLanguage = {d = 0x4c4830b}},
> static baseModulesUninitialized = false, propertyCapture = 0x8dc35e5b,
> jsExpressionGuardPool = {d = 0x90002674}, rootContext = 0x5608ec83, profiler
> = 0x5756e850, outputWarningsToMsgLog = 224, cleanup = 0x4c48310,
> erroredBindings = 0x8dc35e5b, inProgressCreations = -1879038348,
> workerScriptEngine = 0xd9ebc031, baseUrl = {d = 0x26748d},
> activeObjectCreator = 0x53565755, networkAccessManager = 0xe0f7d7e8,
> networkAccessManagerFactory = 0x3c381ff, imageProviders = {{d = 0x83001a12,
> e = 0x83001a12}}, urlInterceptor = 0x748b0cec, scarceResourcesRefCount =
> 2089493540, importDatabase = {
> qmldirCache = { = {}, data = {buckets =
> 0xf6852024, numBuckets = -326927756, size = 1417907464, numBits = -4460},
> newedNodes = 0xe85650fd, nodePool = 0xffe07660},
> filePluginPath = {> = {> =
> {}, {p = {static shared_null = {ref = {atomic = {_q_value =
> std::atomic = { -1 }}}, alloc = 0, begin = 0, end = 0,
> array = {0x0}}, d = 0x8510c483}, d = 0x8510c483}}, fields>}, fileImportPath = {> =
> {> = {}, {p = {static
> shared_null = {ref = {
> atomic = {_q_value = std::atomic = { -1 }}}, alloc = 0,
> begin = 0, end = 0, array = {0x0}}, d = 0x833174c0}, d = 0x833174c0}}, data fields>}, qmlDirFilesForWhichPluginsHaveBeenLoaded = {
> q_hash = {{d = 0x838d08ec, e = 0x838d08ec}}}, initializedPlugins =
> {q_hash = {{d = 0xffeee270, e = 0xffeee270}}}, engine = 0x49e85650},
> typeLoader = {m_engine = 0x83ffe076, m_thread = 0xc08510c4,
> m_mutex = @0xec831774, m_profiler = {d = 0x94838d08}, m_networkReplies =
> {{d = 0x50ffeee2, e = 0x50ffeee2}}, m_typeCache = {{d = 0x7632e856, e =
> 0x7632e856}}, m_typeCacheTrimThreshold = -997982240,
> m_scriptCache = {{d = 0x75c08510, e = 0x75c08510}}, m_qmldirCache = {{d =
> 0x86f8d13, e = 0x86f8d13}}, m_importDirCache = {f = 0x890cc483, l =
> 0x5f5e5be8, hash = {{
> d = 0xb68dc35d , e =
> 0xb68dc35d }}, mx = 0, total =
> 1443425411},
> m_importQmlDirCache = { = {}, data =
> {buckets = 0x56bee857, numBuckets = -997982240, size = 214205200, numBits =
> -14967}, newedNodes = 0x5d5f5ee8, nodePool = 0x26b48dc3}},
> offlineStoragePath = {d = 0x0}, uniqueId = 3438013745, incubatorList =
> {__first = 0x26748d}, incubatorCount = 69485707, incubationController =
> 0x30440c7, static qml_debugging_enabled = false,
> networkAccessManagerMutex = { = {d_ptr = {_q_value =
> std::atomic = { 0xc300 }}}, },
> singletonInstances = {{d = 0x26748d, e = 0x26748d}}, cachedValueTypeInstances
> = {{
> d = 0x89565755, e = 0x89565755}}, m_compositeTypes = {{d = 0x25e853c6,
> e = 0x25e853c6}}, static s_designerMode = false, toDeleteInEngineThread =
> {_first = 0x81ffe0f7, _last = 0x1a1151c3, _flag = 0,
> _count = 376848768}}
Many values/pointers are 0x8dc35e5b or -1879038348/0x90002674 or
0xc483ffe0/-997982240 or their combination. That is obviously bogus.
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 466696] New: Dolphin "Open With -> Other Application..." does not work.
https://bugs.kde.org/show_bug.cgi?id=466696 Bug ID: 466696 Summary: Dolphin "Open With -> Other Application..." does not work. Classification: Applications Product: dolphin Version: 22.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bartos.p...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Opening any file from Dolphin using other than offered application does not work. STEPS TO REPRODUCE 1. Open context menu for any file 2. Select "Open With -> Other Application..." 3. Nothing happens OBSERVED RESULT When started from konsole, it prints message when trying to open application dialog: Couldn't get reply Error: "The name is not activatable" EXPECTED RESULT Dialog allowing to choose application to open file with should be displayed. Works ok in Krusader (2.8.0) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 37 KDE Plasma Version: 5.27.1 , 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 466673] Add ability to save highlighting and annotations in file
https://bugs.kde.org/show_bug.cgi?id=466673 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org --- Comment #7 from Ingo Klöcker --- (In reply to JDT from comment #6) > So, I'm puzzled. Why does the documentation still speak of the problem. I > checked and this page is in the current manual: > https://docs.kde.org/stable5/en/okular/okular/annotations.html I had a quick look and I don't see what you mean (but maybe I have missed it or someone has silently changed/removed it). Anyway. Yes, the page talks about an Okular-specific document archive that can be used for file formats that do not support annotations directly. But the page also reads > You can also save annotations directly into PDF files. > You can use File → Save to save it over the current file > or File → Save As... to save it to a new file. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 466695] New: Konsole crashes after monitors are turned off and on again
https://bugs.kde.org/show_bug.cgi?id=466695 Bug ID: 466695 Summary: Konsole crashes after monitors are turned off and on again Classification: Applications Product: konsole Version: 22.12.2 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: a...@haxalot.com Target Milestone: --- Application: konsole (22.12.2) (Compiled from sources) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.0.19-gentoo-dist x86_64 Windowing System: Wayland Distribution: "Gentoo Linux" DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: With a multi-monitor 2560x1440@120hz setup over DP on Wayland, turning the monitors off for the night leads to a guaranteed crash in Konsole when turning them back on again at morning. The crash can be reproduced every time. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault [KCrash Handler] #4 0x7fc87a994edf in Konsole::TerminalDisplay::bidiMap (this=, screenline=screenline@entry=0x7fc8509e9010, line=..., log2line=log2line@entry=0x7ffd15275570, line2log=line2log@entry=0x7ffd15276570, shapemap=shapemap@entry=0x7ffd15274d70, vis2line=0x7ffd15277570, shaped=@0x7ffd15274bc1: true, shape=true, bidi=true) at /var/tmp/portage/kde-apps/konsole-22.12.2/work/konsole-22.12.2/src/terminalDisplay/TerminalDisplay.cpp:3224 #5 0x7fc87a9a5cf4 in Konsole::TerminalPainter::drawContents (this=this@entry=0x5638771b71a0, image=0x7fc8509e9010, paint=..., rect=..., printerFriendly=printerFriendly@entry=false, imageSize=, bidiEnabled=, lineProperties=..., ulColorTable=) at /var/tmp/portage/kde-apps/konsole-22.12.2/work/konsole-22.12.2/src/terminalDisplay/TerminalPainter.cpp:280 #6 0x7fc87a993924 in Konsole::TerminalDisplay::paintEvent (this=0x5638770312f0, pe=) at /var/tmp/portage/kde-apps/konsole-22.12.2/work/konsole-22.12.2/src/terminalDisplay/TerminalDisplay.cpp:707 #7 0x7fc879fa7028 in QWidget::event (this=0x5638770312f0, event=0x7ffd152787e0) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qwidget.cpp:9045 #8 0x7fc879f6344e in QApplicationPrivate::notify_helper (this=, receiver=0x5638770312f0, e=0x7ffd152787e0) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qapplication.cpp:3640 #9 0x7fc879483ef8 in QCoreApplication::notifyInternal2 (receiver=0x5638770312f0, event=0x7ffd152787e0) at /var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/src/corelib/kernel/qcoreapplication.cpp:1064 #10 0x7fc879f9efc5 in QWidgetPrivate::sendPaintEvent (this=this@entry=0x563876f7ee60, toBePainted=...) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qwidget.cpp:5479 #11 0x7fc879f9f919 in QWidgetPrivate::drawWidget (this=0x563876f7ee60, pdev=, rgn=..., offset=..., flags=..., sharedPainter=, repaintManager=) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qwidget.cpp:5429 #12 0x7fc879fa0d71 in QWidgetPrivate::paintSiblingsRecursive (this=this@entry=0x5638771b7870, pdev=pdev@entry=0x563876722858, siblings=..., index=, rgn=..., offset=..., flags=..., sharedPainter=0x0, repaintManager=0x5638766d07a0) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qwidget.cpp:5610 #13 0x7fc879f9f570 in QWidgetPrivate::drawWidget (this=0x5638771b7870, pdev=, rgn=..., offset=..., flags=..., sharedPainter=, repaintManager=) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qwidget.cpp:5470 #14 0x7fc879fa0d71 in QWidgetPrivate::paintSiblingsRecursive (this=this@entry=0x5638764fa000, pdev=pdev@entry=0x563876722858, siblings=..., index=, rgn=..., offset=..., flags=..., sharedPainter=0x0, repaintManager=0x5638766d07a0) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qwidget.cpp:5610 #15 0x7fc879f9f570 in QWidgetPrivate::drawWidget (this=0x5638764fa000, pdev=, rgn=..., offset=..., flags=..., sharedPainter=, repaintManager=) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qwidget.cpp:5470 #16 0x7fc879fa0d71 in QWidgetPrivate::paintSiblingsRecursive (this=0x56387649b060, pdev=0x563876722858, siblings=..., index=, rgn=..., offset=..., flags=..., sharedPainter=0x0, repaintManager=0x5638766d07a0) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qwidget.cpp:5610 #17 0x7fc879fa0ba6 in QWidgetPrivate::paintSiblingsRecursive (this=this@entry=0x56387649b060, pdev=pdev@entry=0x563876722858, siblings=...,
[kwin] [Bug 465790] Resizing an Aurorae-decorated window leads to malformed decorations
https://bugs.kde.org/show_bug.cgi?id=465790 --- Comment #26 from punk.salt6...@fastmail.com --- (In reply to Nate Graham from comment #21) > I'm not able to reproduce those issues on Wayland with Plasma 5.27.2 and > 200% scaling using the Layan and Dexy decoration themes with an Intel iGPU. > > For people who can still reproduce the issue, can you be specific about what > scaling settings, window decoration themes, and GPU you're using? I'm on 100% scaling, using Dexy window decoration theme, with Amd 6900 xt gpu. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460728] 1920x1080 resolution setting defaults to interlaced 1080i mode on TV screen, not 1080p
https://bugs.kde.org/show_bug.cgi?id=460728 988a...@mail.ru changed: What|Removed |Added CC||988a...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466645] Auroroe window decorations causes "half-size" graphical corruption in window decorations
https://bugs.kde.org/show_bug.cgi?id=466645 --- Comment #6 from punk.salt6...@fastmail.com --- Also want to add that it never happens with Breeze so it's absolutely related to auroroe window decorations. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466463] Different scaling on HiDpi display for applications in 5.27.1
https://bugs.kde.org/show_bug.cgi?id=466463 --- Comment #18 from Michael Hamilton --- (In reply to Michal Hlavac from comment #4) > Thanks Luca, would be really great to have it in 5.27.2, anyway maybe a kind > of workaround for GTK3+ & java applications is to run: > > GDK_SCALE=2 program > > or echo "GDK_SCALE=2" >> ~/.profile > > this basically saves my work life. The easiest workaround is to use settings->Startup and Shutdown->Background Services and disable GNOME/GTK Settings Synchronisation Service - fixes KDE and other app's (as noted in https://bugs.kde.org/show_bug.cgi?id=466506). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466645] Auroroe window decorations causes "half-size" graphical corruption in window decorations
https://bugs.kde.org/show_bug.cgi?id=466645 --- Comment #5 from punk.salt6...@fastmail.com --- (In reply to Nate Graham from comment #4) > Looks like the same issue as in Bug 465790, which is marked as fixed. I > guess it's not actually fixed for all use cases. Re-opening. > > *** This bug has been marked as a duplicate of bug 465790 *** It's a tricky bug. I read the original bug report and it seems like it was simply appearing and easily spotted. Now it's kind of hiding and appears only in this scenario above... But it's still there. Thanks for reopening! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 466667] Segfault crash after using git push via git plugin
https://bugs.kde.org/show_bug.cgi?id=47 Waqar Ahmed changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/util ||ities/kate/commit/cd3f97c45 ||62ba95269b39b81a86b6212df07 ||ebe0 --- Comment #2 from Waqar Ahmed --- Git commit cd3f97c4562ba95269b39b81a86b6212df07ebe0 by Waqar Ahmed. Committed on 02/03/2023 at 06:51. Pushed by waqar into branch 'master'. Fix possible crash due to null tab button Not sure how it happens... but it did happen M +1-1apps/lib/kateoutputview.cpp https://invent.kde.org/utilities/kate/commit/cd3f97c4562ba95269b39b81a86b6212df07ebe0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465790] Resizing an Aurorae-decorated window leads to malformed decorations
https://bugs.kde.org/show_bug.cgi?id=465790 --- Comment #25 from kdeb...@thismymail.com --- (In reply to Nate Graham from comment #21) > I'm not able to reproduce those issues on Wayland with Plasma 5.27.2 and > 200% scaling using the Layan and Dexy decoration themes with an Intel iGPU. > > For people who can still reproduce the issue, can you be specific about what > scaling settings, window decoration themes, and GPU you're using? My Scaling is at 100%, my window decoration theme is "Sweet Mars" by "eliverlara". My Graphics chip is the "AMD Radeon RX Vega 7" which is integrated into the "AMD Ryzen 7 4700U" CPU. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466694] Doesn't check if distro logo has been upgraded
https://bugs.kde.org/show_bug.cgi?id=466694
--- Comment #1 from Alberto Salvia Novella ---
Work around: Remove:
${HOME}/.cache/icon-cache.kcache
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 466463] Different scaling on HiDpi display for applications in 5.27.1
https://bugs.kde.org/show_bug.cgi?id=466463 --- Comment #17 from painless roaster --- Version 5.27.2 did not solve the problem. :-( -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466694] New: Doesn't check if distro logo has been upgraded
https://bugs.kde.org/show_bug.cgi?id=466694 Bug ID: 466694 Summary: Doesn't check if distro logo has been upgraded Classification: Applications Product: systemsettings Version: 5.26.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: es204904...@gmail.com Target Milestone: --- If you update the distro logo file, specified at "/etc/os-release", [System Settings -> About this system] continues showing the old logo. Even after reboot, or after updating the icon cache. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 463225] Akonadi server crashed when switching user
https://bugs.kde.org/show_bug.cgi?id=463225 --- Comment #5 from bett...@gmail.com --- Created attachment 156908 --> https://bugs.kde.org/attachment.cgi?id=156908=edit New crash information added by DrKonqi akonadiserver (5.22.2 (22.12.2)) using Qt 5.15.8 Crashing on boot after a plasma upgrade -- Backtrace (Reduced): #4 0x56051757e29b in Akonadi::Server::AkonadiServer::connectionDisconnected() () #5 0x7f43732c8134 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #6 0x7f437329d4cb in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #7 0x7f43732a0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #8 0x7f43732eeb07 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 463225] Akonadi server crashed when switching user
https://bugs.kde.org/show_bug.cgi?id=463225 bett...@gmail.com changed: What|Removed |Added CC||bett...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466693] New: Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog.
https://bugs.kde.org/show_bug.cgi?id=466693 Bug ID: 466693 Summary: Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog. Classification: Applications Product: Discover Version: 5.27.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifier Assignee: plasma-b...@kde.org Reporter: a...@viatis.com CC: aleix...@kde.org, eli...@gmail.com, n...@kde.org Depends on: 419055 Target Milestone: --- +++ This bug was initially created as a clone of Bug #419055 +++ SUMMARY Even when the user sets a lower frequency of automatic updates (e.g. weekly) in the Software Sources dialog, Discover nevertheless checks for updates daily. This means that effectively the user has no control over automatic update frequency. STEPS TO REPRODUCE 1. In Discover, click on "Sources" -> "Software Sources". Provide the password if required. 2. In the "Software Sources" dialog that opens, click on "Updates". Make sure the "Check for updates" checkbox is checked, and choose a frequency other than "Daily" (e.g. "Weekly") in the corresponding dropdown. Click on "Close". OBSERVED RESULT Update notifications appear in the notifications area multiple times a week, presumably on every startup if updates are available. EXPECTED RESULT Update notifications appear at most once a week. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.2.1-arch1-1 (64-bit) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION SUMMARY Even when the user sets a lower frequency of automatic updates (e.g. weekly) in the Software Sources dialog, Discover nevertheless checks for updates daily. This means that effectively the user has no control over automatic update frequency. STEPS TO REPRODUCE 1. In Discover, click on "Sources" -> "Software Sources". Provide the password if required. 2. In the "Software Sources" dialog that opens, click on "Updates". Make sure the "Check for updates" checkbox is checked, and choose a frequency other than "Daily" (e.g. "Weekly") in the corresponding dropdown. Click on "Close". OBSERVED RESULT Update notifications appear in the notifications area multiple times a week. EXPECTED RESULT Update notifications appear at most once a week. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 19.10 (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION This is a follow up to bug 401810 (Phabricator patch D17375) and bug 337752. Unfortunately, it appears that the issue wasn't resolved (at least not on my system). My analysis shows that Discover's PackageKitNotifier attempts to check the frequency set in software-properties by running "apt-config dump" and looking for the "Apt::Periodic::Update-Package-Lists" property in its output. However, on my system the property name starts with uppercase "APT" rather than "Apt", and ends with a semicolon. Therefore PackageKitNotifier fails to find the correct property value, and falls back to the default of a daily check. Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=419055 [Bug 419055] Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419055] Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog.
https://bugs.kde.org/show_bug.cgi?id=419055 Alexandre changed: What|Removed |Added Blocks||466693 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=466693 [Bug 466693] Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 390797] Feature request: macOS-like titlebar proxy icon
https://bugs.kde.org/show_bug.cgi?id=390797 Mathieu Jobin changed: What|Removed |Added CC||opensou...@somekool.net --- Comment #8 from Mathieu Jobin --- I am also interested seeing this feature implemented. I wonder if the "client app" could not communicate to kwin that it has a file open. very much like showing the file need saving. I tried to find the API doc for this but I got lost... -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 466685] Touch position wrong on dual monitor set up on touchscreen laptop and always have to remap every log in or restart
https://bugs.kde.org/show_bug.cgi?id=466685 --- Comment #1 from fdana...@gmail.com --- Created attachment 156907 --> https://bugs.kde.org/attachment.cgi?id=156907=edit cursor and stylus didn't match the position -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 464231] KDE Connect for Mac OS no longer works after updating to latest version
https://bugs.kde.org/show_bug.cgi?id=464231 --- Comment #8 from ipcjs --- It looks like the stable version doesn't have the issue. it can be download from :https://binary-factory.kde.org/view/MacOS/job/kdeconnect-kde_Release_macos/lastStableBuild/ -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 364615] after mass rename, ctrl+z (undo) should revert ALL folders/files names
https://bugs.kde.org/show_bug.cgi?id=364615 Elvis Angelaccio changed: What|Removed |Added Latest Commit||https://cgit.kde.org/dolphi ||n.git/commit/?id=c5eb4e3116 ||1ccf422a2f2492fe998c5c9817b ||ea4 Version Fixed In||18.03.80 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 372862] Add .cpp syntax highlighting to .ino files
https://bugs.kde.org/show_bug.cgi?id=372862 Jonathan Poelen changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED URL||https://phabricator.kde.org ||/D5645 Latest Commit||https://cgit.kde.org/syntax ||-highlighting.git/commit/?i ||d=ba8ed1f28885484156a1fd280 ||2dafc3b2c12b1fc CC||jonathan.poe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 396243] wrong color scheme in the event dialog
https://bugs.kde.org/show_bug.cgi?id=396243 Christophe Marin changed: What|Removed |Added Latest Commit||https://cgit.kde.org/incide ||nceeditor.git/commit/?id=2c ||86217da538e02501cf76d953b4d ||2dee5c1cd51 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Christophe Marin --- Strange, my commit didn't close the bug. Anyway, done. I removed the hardcoded color=blue. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394455] New language kcm says "i18n_argument_missing" when I add a language
https://bugs.kde.org/show_bug.cgi?id=394455 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED CC||n...@kde.org Latest Commit||https://cgit.kde.org/plasma ||-desktop.git/commit/?id=150 ||f8877ee42f0d7f69c90549b4d8c ||ca578de4ea --- Comment #3 from Nate Graham --- Fixed with https://cgit.kde.org/plasma-desktop.git/commit/?id=150f8877ee42f0d7f69c90549b4d8cca578de4ea -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399992] Text ends in an ellipsis even though there's plenty of space below
https://bugs.kde.org/show_bug.cgi?id=32 Nate Graham changed: What|Removed |Added Version Fixed In||5.15.0 Latest Commit||https://cgit.kde.org/kwin.g ||it/commit/?id=e6c068010062e ||2ecddeee0e1d28ae84121d7fad1 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Nate Graham --- Fixed with https://phabricator.kde.org/D17982! --- Comment #4 from Nate Graham --- Fixed with https://phabricator.kde.org/D17982! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 315552] Allow save annotations directly to original pdf file
https://bugs.kde.org/show_bug.cgi?id=315552 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://cgit.kde.org/okular ||.git/commit/?id=3957683d765 ||1494a7bc48b26e6b113161e9a88 ||8c Latest Commit|https://cgit.kde.org/okular |3957683d7651494a7bc48b26e6b |.git/commit/?id=3957683d765 |113161e9a888c |1494a7bc48b26e6b113161e9a88 | |8c | 4aa7f...@opayq.com changed: What|Removed |Added CC||4aa7f...@opayq.com --- Comment #24 from Nate Graham --- Indeed it is! Fixed in https://cgit.kde.org/okular.git/commit/?id=3957683d7651494a7bc48b26e6b113161e9a888c --- Comment #25 from Nate Graham --- Indeed it is! Fixed in https://cgit.kde.org/okular.git/commit/?id=3957683d7651494a7bc48b26e6b113161e9a888c -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 358084] Renaming a profile actually duplicates it
https://bugs.kde.org/show_bug.cgi?id=358084 Nate Graham changed: What|Removed |Added Latest Commit||https://cgit.kde.org/konsol ||e.git/commit/?id=652e48cf6f ||db01b23163a0f1d5963def5295f ||0e9 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375921] present windows shows launchers (Kicker, Kickoff, Application Dashboard, SimpleMenu, etc)
https://bugs.kde.org/show_bug.cgi?id=375921 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||5.14 Resolution|--- |FIXED Latest Commit||https://cgit.kde.org/kwayla ||nd.git/commit/?id=10b00a219 ||e9fddd57431d6bdb6550cdba6ed ||73bf Patrick Silva changed: What|Removed |Added CC||z...@live.de --- Comment #34 from Nate Graham --- Fixed with https://cgit.kde.org/kwayland.git/commit/?id=10b00a219e9fddd57431d6bdb6550cdba6ed73bf --- Comment #35 from Scott Harvey --- Thanks, Nate. You beat me to the comment. --- Comment #36 from Patrick Silva --- *** Bug 395425 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 120400] Kdiff3 doesnt render utf-8 correctly
https://bugs.kde.org/show_bug.cgi?id=120400 michael changed: What|Removed |Added CC||reeves...@gmail.com Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED CC|reeves...@gmail.com | --- Comment #2 from michael --- Bug against unmaintained version. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466362] 10+ MB leak every second after new display added
https://bugs.kde.org/show_bug.cgi?id=466362 Nate Graham changed: What|Removed |Added Priority|NOR |VHI Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466362] 10+ MB leak every second after new display added
https://bugs.kde.org/show_bug.cgi?id=466362 Nate Graham changed: What|Removed |Added Component|generic-performance |Multi-screen support CC||aleix...@kde.org, ||notm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466362] 10+ MB leak every second after new display added
https://bugs.kde.org/show_bug.cgi?id=466362 Nate Graham changed: What|Removed |Added CC||kevin.david.h...@gmail.com --- Comment #14 from Nate Graham --- *** Bug 466634 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466634] When the desktop is running, even at idle, plasmashell will consume all of my 32GB of memory resulting in a system freeze.
https://bugs.kde.org/show_bug.cgi?id=466634 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #13 from Nate Graham --- *** This bug has been marked as a duplicate of bug 466362 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466634] When the desktop is running, even at idle, plasmashell will consume all of my 32GB of memory resulting in a system freeze.
https://bugs.kde.org/show_bug.cgi?id=466634 --- Comment #12 from Nate Graham --- Definitely not a fix, just a workaround that helps to confirm that this is Bug 466362. We'll see if we can get it fixed soon! -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 466692] New: Crash when saving existing events
https://bugs.kde.org/show_bug.cgi?id=466692 Bug ID: 466692 Summary: Crash when saving existing events Classification: Applications Product: kalendar Version: 22.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: chmc...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: kalendar (22.12.2) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.14-200.fc37.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 37 (Workstation Edition) DrKonqi: 5.27.1 [KCrashBackend] -- Information about the crash: I'm currently using Google calendar. When I save an existing event, Kalendar crashes every time. The crash can be reproduced every time. -- Backtrace: Application: Kalendar (kalendar), signal: Segmentation fault [KCrash Handler] #4 0x7fe4885a8b40 in QDateTime::operator=(QDateTime const&) () from /lib64/libQt5Core.so.5 #5 0x563165674338 in IncidenceOccurrenceModel::slotSourceDataChanged(QModelIndex const&, QModelIndex const&) () #6 0x7fe4886d0e96 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #7 0x7fe48864dcd0 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib64/libQt5Core.so.5 #8 0x7fe48867f778 in QSortFilterProxyModelPrivate::_q_sourceDataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib64/libQt5Core.so.5 #9 0x7fe4886d101f in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #10 0x7fe48864dcd0 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib64/libQt5Core.so.5 #11 0x7fe48867f778 in QSortFilterProxyModelPrivate::_q_sourceDataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib64/libQt5Core.so.5 #12 0x7fe4886d101f in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #13 0x7fe48864dcd0 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib64/libQt5Core.so.5 #14 0x7fe48867f778 in QSortFilterProxyModelPrivate::_q_sourceDataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib64/libQt5Core.so.5 #15 0x7fe4886d101f in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #16 0x7fe48864dcd0 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib64/libQt5Core.so.5 #17 0x7fe48ab13a2a in KSelectionProxyModelPrivate::sourceDataChanged(QModelIndex const&, QModelIndex const&) () from /lib64/libKF5ItemModels.so.5 #18 0x7fe4886d0e96 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #19 0x7fe48864dcd0 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib64/libQt5Core.so.5 #20 0x7fe48ae524ab in Akonadi::EntityTreeModelPrivate::dataChanged(QModelIndex const&, QModelIndex const&) () from /lib64/libKF5AkonadiCore.so.5 #21 0x7fe48ae5ba82 in Akonadi::EntityTreeModelPrivate::monitoredItemChanged(Akonadi::Item const&, QSet const&) () from /lib64/libKF5AkonadiCore.so.5 #22 0x7fe4886d101f in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #23 0x7fe48add38bb in Akonadi::Monitor::itemChanged(Akonadi::Item const&, QSet const&) () from /lib64/libKF5AkonadiCore.so.5 #24 0x7fe48adea526 in Akonadi::MonitorPrivate::emitItemsNotification(Akonadi::Protocol::ItemChangeNotification const&, QVector const&, Akonadi::Collection const&, Akonadi::Collection const&) () from /lib64/libKF5AkonadiCore.so.5 #25 0x7fe48ade28ca in Akonadi::MonitorPrivate::emitNotification(QSharedPointer const&) () from /lib64/libKF5AkonadiCore.so.5 #26 0x7fe48ade5c95 in Akonadi::MonitorPrivate::flushPipeline() () from /lib64/libKF5AkonadiCore.so.5 #27 0x7fe48ade5fed in Akonadi::MonitorPrivate::dataAvailable() () from /lib64/libKF5AkonadiCore.so.5 #28 0x7fe4886d0e96 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #29 0x7fe4886d101f in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #30 0x7fe48a6cf3d9 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib64/libKF5CoreAddons.so.5 #31 0x7fe48a6d4e3b in KJob::finishJob(bool) () from /lib64/libKF5CoreAddons.so.5 #32 0x7fe4886c8134 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #33 0x7fe4893aed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #34 0x7fe48869d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #35 0x7fe4886a0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int,
[kdeconnect] [Bug 463511] App crashes or closed while sending large files
https://bugs.kde.org/show_bug.cgi?id=463511 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|FIXED |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 450626] [translations] install.sh does not install translations properly
https://bugs.kde.org/show_bug.cgi?id=450626 --- Comment #17 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 461934] The KDE connect app crash when I try to transfer files
https://bugs.kde.org/show_bug.cgi?id=461934 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 457922] Can’t send picture from computer to iPhone using kde connect
https://bugs.kde.org/show_bug.cgi?id=457922 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466623] Unable to display screen if computer starts without HDMI cable connected (or without HDMI signal)
https://bugs.kde.org/show_bug.cgi?id=466623 --- Comment #3 from Chema --- Sorry, I forgot that Mate and Cinnamon are also based on GTK... So, I don't know the reason for the problem, all I know is that with GNOME (with Wayland), Xfce and Budgie it doesn't give any problem. As I said before, I think it's all about the detection of the HDMI. I've had to switch back to KDE with X11 to mitigate some of these issues. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 464231] KDE Connect for Mac OS no longer works after updating to latest version
https://bugs.kde.org/show_bug.cgi?id=464231 ipcjs changed: What|Removed |Added CC||gip...@gmail.com --- Comment #7 from ipcjs --- How can i download last available version? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459778] Screen occasionally freezes "EGL_BAD_SURFACE" errors when launching application while using the Klassy window decoration
https://bugs.kde.org/show_bug.cgi?id=459778 John changed: What|Removed |Added CC||ilikef...@waterisgone.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466691] Icons-only Task Manager - Sort Manual - Order of windows lost after x11vnc remote connection
https://bugs.kde.org/show_bug.cgi?id=466691 --- Comment #1 from Michael --- Clarifying on the Firefox Grouped. There was at least one new Firefox window that I hadn't sorted in since reloading the session. It was to the right of the ungrouped set of sorted Firefox windows. After this bug triggered again it is now all the way to the left of the still ungrouped but now 'together' (in sequence along the taskbar) Firefox windows. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466691] New: Icons-only Task Manager - Sort Manual - Order of windows lost after x11vnc remote connection
https://bugs.kde.org/show_bug.cgi?id=466691 Bug ID: 466691 Summary: Icons-only Task Manager - Sort Manual - Order of windows lost after x11vnc remote connection Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: mjevans1...@gmail.com Target Milestone: 1.0 Sort: Manual Order of windows lost after x11vnc remote connection STEPS TO REPRODUCE 1. Have multiple Firefox sessions, terminals, other programs, etc open. (Typical workspace?) 2. Icons-only Task Manager > Behavior > Sort: Manual 3. Carefully sort the windows into a user-desired manual order. 4. Remote connect with x11vnc 5. Sign back in at the physical terminal. 6. Windows are now no longer in the user specified order. Notably it looks roughly like the order of Firefox session windows is reversed (I have a lot of them), as well as combined together (they're not allowed to be grouped but now they are). A mix of windows that were after (to the right) as well as before (to the left) of Firefox's session windows are now all to the right, with only Dolphin to the left of Firefox's set of windows. Steam's set of windows (2) didn't get reversed, but they might not be a group candidate. Firefox's would be if grouping weren't banned for that program, and those windows appear to now be in reverse order. Overall all of the programs are now in a seemingly random order across the task bar (but still grouped left to right by program). I've had this issue for about a week and at least two different ArchLinux KDE updates have had the issue (I wanted to wait to see if it was fixed since it seemed likely a new update might resolve the issue). This was working 'recently' though I don't know what version of KDE Plasma workspace I was using on Arch Linux prior to the more recent updates. This regression may have been introduced somewhere between 5.26.x and 5.27.x. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466690] New: On top panel some types of app windows react wrong on restore from maximize
https://bugs.kde.org/show_bug.cgi?id=466690 Bug ID: 466690 Summary: On top panel some types of app windows react wrong on restore from maximize Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: szymondud...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. Login to Wayland Session 2. Move panel from bottom to top 3. Maximize app like : firefox, vscode, discord, timeshift, qtcreator by dragging to top or double click. 4. Pull down that window ( disconnect the maximized window from the panel ) 5. To restore original size of window, maximize again by double click or move by mouse to top of screen ( stick to panel ) OBSERVED RESULT On electron apps problem occur without exception and on others like Vala : Timeshift, or QT-6 : OBS, QTCreator, QBittorrent, GTK2 : gimp, Java : JetBrains, and Others : Krita. Occur also. on KDE apps, or when panel is not on top of screen, problem not appear. EXPECTED RESULT un-maximize must restore original window size. SOFTWARE/OS VERSIONS Linux : 6.1.x KDE Plasma Version: 5.26.5, 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.18.8 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466620] powerdevil continues to crash in KScreen::AbstractDpmsHelper::isSupported() when HDMI signal is lost
https://bugs.kde.org/show_bug.cgi?id=466620 Chema changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Chema --- coredumpctl backtrace: PID: 1984 (org_kde_powerde) UID: 1000 (rondo) GID: 1000 (rondo) Signal: 11 (SEGV) Timestamp: Tue 2023-02-28 23:05:34 CET (1 day 4h ago) Command Line: /usr/lib/org_kde_powerdevil Executable: /usr/lib/org_kde_powerdevil Control Group: /user.slice/user-1000.slice/user@1000.service/background.slice/plasma-powerdevil.service Unit: user@1000.service User Unit: plasma-powerdevil.service Slice: user-1000.slice Owner UID: 1000 (rondo) Boot ID: 1f36683284624ef78d6a3a1b6af2fda9 Machine ID: f894d2e603cd424bb9bcb2d128098414 Hostname: ComputerL Storage: /var/lib/systemd/coredump/core.org_kde_powerde.1000.1f36683284624ef78d6a3a1b6af2fda9.1984.167762193400.zst (present) Size on Disk: 1.2M Message: Process 1984 (org_kde_powerde) of user 1000 dumped core. Stack trace of thread 1984: #0 0x7fdffcd3a479 wl_proxy_marshal_array_flags (libwayland-client.so.0 + 0xa479) #1 0x7fdffcd3aafa wl_proxy_marshal_flags (libwayland-client.so.0 + 0xaafa) #2 0x7fdff429af5b n/a (libKF5ScreenDpms.so.8 + 0x6f5b) #3 0x7fdff429b960 n/a (libKF5ScreenDpms.so.8 + 0x7960) #4 0x7fdffc0bea71 n/a (libQt5Core.so.5 + 0x2bea71) #5 0x7fdff641daef _ZN15QtWaylandClient15QWaylandDisplay19addRegistryListenerEPFvPvP11wl_registryjRK7QStringjES1_ (libQt5WaylandClient.so.5 + 0x74aef) #6 0x7fdff643b760 _ZN23QWaylandClientExtension19addRegistryListenerEv (libQt5WaylandClient.so.5 + 0x92760) #7 0x7fdffc09d51e _ZNK11QMetaMethod6invokeEP7QObjectN2Qt14ConnectionTypeE22QGenericReturnArgument16QGenericArgumentS5_S5_S5_S5_S5_S5_S5_S5_S5_ (libQt5Core.so.5 + 0x29d51e) #8 0x7fdffc09df10 _ZN11QMetaObject12invokeMethodEP7QObjectPKcN2Qt14ConnectionTypeE22QGenericReturnArgument16QGenericArgumentS7_S7_S7_S7_S7_S7_S7_S7_S7_ (libQt5Core.so.5 + 0x29df10) #9 0x7fdff429ad8c n/a (libKF5ScreenDpms.so.8 + 0x6d8c) #10 0x7fdff429c928 _ZNK7KScreen4Dpms11isSupportedEv (libKF5ScreenDpms.so.8 + 0x8928) #11 0x7fdffcce4d70 _ZN10PowerDevil10ActionPool4initEPNS_4CoreE (libpowerdevilcore.so.2 + 0x12d70) #12 0x7fdffcceca9d _ZN10PowerDevil4Core14onBackendReadyEv (libpowerdevilcore.so.2 + 0x1aa9d) #13 0x7fdffc0bea71 n/a (libQt5Core.so.5 + 0x2bea71) #14 0x7fdff556735b _ZN23PowerDevilUPowerBackend18initWithBrightnessEb (powerdevilupowerbackend.so + 0x1135b) #15 0x7fdffc0bea71 n/a (libQt5Core.so.5 + 0x2bea71) #16 0x7fdff555e414 _ZN23PowerDevilUPowerBackend24brightnessSupportQueriedEb (powerdevilupowerbackend.so + 0x8414) #17 0x7fdffc0bea71 n/a (libQt5Core.so.5 + 0x2bea71) #18 0x7fdffcb6d43a _ZN4KJob6resultEPS_NS_14QPrivateSignalE (libKF5CoreAddons.so.5 + 0x5a43a) #19 0x7fdffcb7354c _ZN4KJob9finishJobEb (libKF5CoreAddons.so.5 + 0x6054c) #20 0x7fdffc0bea71 n/a (libQt5Core.so.5 + 0x2bea71) #21 0x7fdff557f785 n/a (kauth_helper_plugin.so + 0xa785) #22 0x7fdff557fe91 n/a (kauth_helper_plugin.so + 0xae91) #23 0x7fdffcaf445f n/a (libQt5DBus.so.5 + 0x6145f) #24 0x7fdffc0b1bb0 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2b1bb0) #25 0x7fdffc08df48 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x28df48) #26 0x7fdffc08ea53 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x28ea53) #27 0x7fdffc0d4e88 n/a (libQt5Core.so.5 + 0x2d4e88) #28 0x7fdffad1682b g_main_context_dispatch (libglib-2.0.so.0 + 0x5582b) #29 0x7fdffad6dcc9 n/a (libglib-2.0.so.0 + 0xaccc9) #30 0x7fdffad150e2 g_main_context_iteration (libglib-2.0.so.0 + 0x540e2) #31 0x7fdffc0d8c6c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d8c6c) #32 0x7fdffc0866ec _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2866ec) #33 0x7fdffc091219 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x291219) #34 0x563ded70c55b n/a (org_kde_powerdevil + 0x655b) #35 0x7fdffb83c790 n/a (libc.so.6 + 0x23790) #36
[KScreen] [Bug 466623] Unable to display screen if computer starts without HDMI cable connected (or without HDMI signal)
https://bugs.kde.org/show_bug.cgi?id=466623 Chema changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Chema --- As far as I can remember, since I started using KDE a couple of years ago, I don't really remember what version it was back then, I think it was 5.25 but I'm not sure, this problem has always happened, so I don't think be a regression error (at least, since I've been using it, obviously I can't know the previous versions). All I can say is that if I try other desktops, like GNOME or Xfce, this problem doesn't happen with them, it only happens with KDE. I don't know if it only happens to me, but from the beginning I think that KDE has a serious problem with the detection of HDMI on my computer: - If I boot the computer and it does not receive an HDMI signal while the system boots and the KDE login screen loads, there is no way for that session to recover the HDMI signal, the screen stays completely black. - If with the computer turned on I change the KVM switch to another computer, even if KDE only loses the HDMI signal for a couple of seconds, when returning to KDE the Powerdevil has crashed. - If I have a bi-directional EDID emulator connected to the HDMI output and I switch to another computer on the KVM switch and then come back to KDE, the session hangs with a black screen and there is no way to recover that session. I don't think it's a KDE-only problem, I think more of a QT problem, since Xfce and Gnome (based in GTK) don't have any of these problems, while Mate and Cinnamon do some (but not all) of them. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466634] When the desktop is running, even at idle, plasmashell will consume all of my 32GB of memory resulting in a system freeze.
https://bugs.kde.org/show_bug.cgi?id=466634 --- Comment #11 from kevin.david.h...@gmail.com --- It's been almost 3 hours. Still hovering in the 400Mb of memory range. So, is there a permanent fix, or do I need to start my machine with 1 monitor for the foreseeable future? On Wed, Mar 1, 2023 at 4:34 PM Kevin Hall wrote: > It rose to ~400Mb. I'll keep an eye on it and let you know if it climbs > over time. > > On Wed, Mar 1, 2023 at 4:24 PM Nate Graham > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=466634 >> >> --- Comment #9 from Nate Graham --- >> Thanks. And if you plug in the second screen, does the memory use >> immediately >> skyrocket? >> >> -- >> You are receiving this mail because: >> You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 466673] Add ability to save highlighting and annotations in file
https://bugs.kde.org/show_bug.cgi?id=466673 --- Comment #6 from JDT --- So, I'm puzzled. Why does the documentation still speak of the problem. I checked and this page is in the current manual: https://docs.kde.org/stable5/en/okular/okular/annotations.html Adobe reader is the reference implementation but it is not available on Linux and hasn't been for a while. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466665] Do not display flatpak permission settings in endeavourOS
https://bugs.kde.org/show_bug.cgi?id=45 --- Comment #5 from Sharath --- I forgot to mention thank you, thank you again anyway -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466635] Notifications still pop up on main screen when Do Not Disturb is checked on multi monitor setup
https://bugs.kde.org/show_bug.cgi?id=466635 --- Comment #7 from Nate Graham --- (In reply to voncloft from comment #6) > I have tried disabling on all 3 screens and it will still pop up on the > farthest left one. Sure but can you *remove* all of the Notifications widgets except for only one? I'm asking if the issue continues to happen when you only have a single Notifications widget. Not one per screen; only one on the whole system. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465818] Flatpak KCM doesn't create proper overrides because of translations
https://bugs.kde.org/show_bug.cgi?id=465818 --- Comment #6 from ratijas --- Git commit c108ef2b53918265d113d2d97721f88a3f9ed486 by ivan tkachenko. Committed on 02/03/2023 at 01:57. Pushed by ratijas into branch 'Plasma/5.27'. Fix inappropriately localized permission name "per-app-dev-shm" Which corresponds to FLATPAK_CONTEXT_FEATURE_PER_APP_DEV_SHM value from FlatpakContextFeatures enum in Flatpak internals. Amends 3d2a355aec552f49394975550aa36d3e3634302c. FIXED-IN: 5.27.3 (cherry picked from commit 7cf1da69d30cdd8efbb563070e0bdaf303ef118a) M +1-1flatpakpermission.cpp https://invent.kde.org/plasma/flatpak-kcm/commit/c108ef2b53918265d113d2d97721f88a3f9ed486 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465818] Flatpak KCM doesn't create proper overrides because of translations
https://bugs.kde.org/show_bug.cgi?id=465818 --- Comment #5 from ratijas --- Git commit 7cf1da69d30cdd8efbb563070e0bdaf303ef118a by ivan tkachenko. Committed on 02/03/2023 at 01:56. Pushed by ratijas into branch 'master'. Fix inappropriately localized permission name "per-app-dev-shm" Which corresponds to FLATPAK_CONTEXT_FEATURE_PER_APP_DEV_SHM value from FlatpakContextFeatures enum in Flatpak internals. Amends 3d2a355aec552f49394975550aa36d3e3634302c. FIXED-IN: 5.27.3 M +1-1flatpakpermission.cpp https://invent.kde.org/plasma/flatpak-kcm/commit/7cf1da69d30cdd8efbb563070e0bdaf303ef118a -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461367] xfreerdp /multimon Does Not Work with Legacy Scaling set to "Apply Scaling Themselves"
https://bugs.kde.org/show_bug.cgi?id=461367 --- Comment #7 from Stephen Ackerman --- Further testing with Debian Frameworks 5.103 + Plasma 5.27.0-1 (shows as 5.26.90 in System Settings? Looks like 5.27.2 is pending a release into Testing) revealed the following behavior: The off-by-one-pixel issue went away if I used 125% scaling instead of 130%, as inspired by Plasma X11 only allowing 6.25% scaling increments (eg, 125% / 131.25%). Could not get 131.25% to enter into Plasma Wayland's config menu. The rendering issue is still present. The expected behavior is one window stretched across both screens. The current behavior is whichever screen has the mouse renders correctly, while the other renders both "screens" side-by-side, centered vertically. Expected: +---+---+ | 1 | 2 | +---+---+ Actual: +-+---+ | 1 2 | 2 | +-+---+ That would be with the mouse on Screen 2, it switches around when the mouse is on screen 1. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466689] New: System Settings Crash After Applying Global Theme
https://bugs.kde.org/show_bug.cgi?id=466689 Bug ID: 466689 Summary: System Settings Crash After Applying Global Theme Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: z_mikow...@yahoo.com Target Milestone: --- Application: systemsettings (5.27.2) Qt Version: 5.15.3 Frameworks Version: 5.102.0 Operating System: Linux 5.19.0-32-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.2 LTS DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: Steps to Reproduce: 1. Open System Settings > Appearance > Global Theme 2. Select a different theme than the current (for this crash, I selected Breeze Dark IIRC) 3. In the "Apply Breeze Dark" dialog, check [x] Appearance settings and [x] Desktop and window layout 4. Click [ Apply ] button Expected Results: 1. Theme should be applied as selected. 2. System settings should not crash. Actual Results: 1. Theme is applied as selected (Good!) 2. System settings crashes (BAD) This behamatches closed bug 458405 which is marked as a duplicate of bug 446111. However, I have been able to reproduce, and the failure mode may vbe different. This is also on Plasma 5.27.2. Frequency: Estimated below 5%. While this crash occured once, I tried 20 additional times using the same system settings instance each time, and it occurred again on the 20th attempt. The detail listed is: Executable: systemsettings PID 50,622 Signal: Segmentation fault (11) Time 3/1/23 5:27 PM The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7fc7c2e7df00 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fc7c2e7de19 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fc7c2e7de19 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fc7c2e7de19 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7fc7c2e7ebde in QQuickWindowPrivate::deliverToPassiveGrabbers(QVector > const&, QQuickPointerEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7fc7c2e84ed5 in QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7fc7c2e8665f in QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7fc7c4f4d5a5 in QWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #12 0x7fc7c576c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7fc7c4ab9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fc7c39470ab in QQuickWidget::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5 #15 0x7fc7c57af4ee in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7fc7c576c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7fc7c5774364 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fc7c4ab9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7fc7c5772e47 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7fc7c57c8d40 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7fc7c57cbfd5 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7fc7c576c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7fc7c4ab9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7fc7c4f41307 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #25 0x7fc7c4f16a2c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #26 0x7fc7bf0f8d6e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #27 0x7fc7c3320d3b in g_main_context_dispatch () from
[okular] [Bug 466673] Add ability to save highlighting and annotations in file
https://bugs.kde.org/show_bug.cgi?id=466673 Luigi Toscano changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REOPENED|RESOLVED --- Comment #5 from Luigi Toscano --- If you want to complete the testing, please open the PDF with a different program (adobe reader is the reference implementation). If it still doesn't work, please reopen and attach a sample file. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 466673] Add ability to save highlighting and annotations in file
https://bugs.kde.org/show_bug.cgi?id=466673 Luigi Toscano changed: What|Removed |Added CC||luigi.tosc...@tiscali.it --- Comment #4 from Luigi Toscano --- (In reply to JDT from comment #2) > Albert, > > Okular's manual disagrees with you. Annotations are **not** saved in the pdf > file. See, for instances: > https://docs.kde.org/stable5/en/okular/okular/annotations.html > > Annotations and highlighting *used* to be stored in the PDF. There was an > intentional design decision made at some point. As one of the developer of the poppler libraries and one of the long standing contributor of Okular, I suspect that Albert knows how that part of Okular works. For the record, annotations are stored into the PDF. They used to be stored outside, but then both poppler and okular gained the needed bit to make sure the annotations were recorded back in the file, according the standard. > > If you'd like to learn more about the technical aspects, the information is > out there. For instance the information is stored in > ~/.kde/share/apps/okular/docdata If you refer to standard, please make sure to refer to updated ones. ~/.kde/share/apps/okular/docdata was the location used when Okular was based on Qt4, which hasn't been the case for the past 6 years (https://community.kde.org/Applications/16.12_Release_Notes). > https://unix.stackexchange.com/questions/71584/storing-okular-pdf-annotations-and-metadata-in-the-pdf-itself In fact the answers to this ^^ also states " This question is obsolete, as okular stores the annotations by default in the original PDF file (as of version 1.6.2, but I think the transition has happened earlier yet). " -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466555] Not all CalDev events appear in clock widget calendar
https://bugs.kde.org/show_bug.cgi?id=466555 --- Comment #1 from voncl...@gmail.com --- I created a patch to have 10 events fixed it myself: https://raw.githubusercontent.com/voncloft/Voncloft-OS/master/REPOS/plasma/plasma-workspace/event.patch -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466635] Notifications still pop up on main screen when Do Not Disturb is checked on multi monitor setup
https://bugs.kde.org/show_bug.cgi?id=466635 --- Comment #6 from voncl...@gmail.com --- (In reply to Nate Graham from comment #3) > Ok. If you remove all but one and then reboot, does that single > Notifications widget behave properly and suppress notifications on all > screens? I have tried disabling on all 3 screens and it will still pop up on the farthest left one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466635] Notifications still pop up on main screen when Do Not Disturb is checked on multi monitor setup
https://bugs.kde.org/show_bug.cgi?id=466635 --- Comment #5 from voncl...@gmail.com --- (In reply to Nate Graham from comment #4) > And are you on Wayland? > > Could be Bug 451090. no x11 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 465199] App freezes when I use animation docker
https://bugs.kde.org/show_bug.cgi?id=465199 --- Comment #8 from Redkitt3n14 --- Sorry I think I'll have to do it tomorrow, ain't gonna get time tonight On Wed, 1 Mar 2023, 15:37 Ash Hobba, wrote: > I will do that later today > > *From: *sh_zam > *Sent: *01 March 2023 06:31 > *To: *marmaladepla...@gmail.com > *Subject: *[krita] [Bug 465199] App freezes when I use animation docker > > > > https://bugs.kde.org/show_bug.cgi?id=465199 > > > > --- Comment #6 from sh_zam --- > > Odd, I can't reproduce it, it opens for me and the animation runs fine, > and I > > can change frames with much issues. Would it be possible for you to screen > > record the interaction with Krita? > > > > (The number of frames is quite large, and my device is weaker -- so maybe > we > > can rule out the possibility that this is due to weaker device :) ). > > > > -- > > You are receiving this mail because: > > You reported the bug. > > > -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 466673] Add ability to save highlighting and annotations in file
https://bugs.kde.org/show_bug.cgi?id=466673 --- Comment #3 from JDT --- I suspect the design decision is tied to either 1) adding the ability to read and mark up all sorts of documents or 2) imitate some PDF library programs that do the same thing (in order to make it easier to search annotations across an entire library) Whatever the design motivation, until there's a way to embed stuff back into the PDF, it effectively makes PDFs used with Okular into a Non Portable Document Format. Kind of an ironic decision when the source is open but it makes the format closed. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 441023] Tax report shows items that are not tax related
https://bugs.kde.org/show_bug.cgi?id=441023 --- Comment #5 from Jack --- Created attachment 156904 --> https://bugs.kde.org/attachment.cgi?id=156904=edit XML data file demonstrating the error of non-tax categories on tax report I'm attaching a relatively small (25K) xml data file which shows the problem. I have not been able to make one from scratch, so this is a modified reduced version of one I already had. Both the tax reports by category (this year and last year) show transactions listed without a category. None of those transactions has any split in the single category (OtherGroups) listed as tax related. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 462914] glitched horizontal lines in text selection @ 150% scale on X11
https://bugs.kde.org/show_bug.cgi?id=462914 nkwkel...@gmail.com changed: What|Removed |Added CC||nkwkel...@gmail.com --- Comment #8 from nkwkel...@gmail.com --- Which version will include the fix? I am still facing this bug on 22.12.2. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 466673] Add ability to save highlighting and annotations in file
https://bugs.kde.org/show_bug.cgi?id=466673 JDT changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #2 from JDT --- Albert, Okular's manual disagrees with you. Annotations are **not** saved in the pdf file. See, for instances: https://docs.kde.org/stable5/en/okular/okular/annotations.html Annotations and highlighting *used* to be stored in the PDF. There was an intentional design decision made at some point. If you'd like to learn more about the technical aspects, the information is out there. For instance the information is stored in ~/.kde/share/apps/okular/docdata https://unix.stackexchange.com/questions/395599/customize-the-folder-where-okular-saves-annotations https://unix.stackexchange.com/questions/71584/storing-okular-pdf-annotations-and-metadata-in-the-pdf-itself -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 458865] After an update to qt5-base the dolphin file picker dialog used in GTK applications via GTK_USE_PORTAL=1 ignores theming
https://bugs.kde.org/show_bug.cgi?id=458865 siloco...@gmail.com changed: What|Removed |Added CC||siloco...@gmail.com --- Comment #63 from siloco...@gmail.com --- (In reply to Demitrius Belai from comment #16) > I have a issue with Firefox do not follow the dark theme before upgrade > qt5-base (5.15.5+kde+r182-1 -> 5.15.5+kde+r184-1) on Arch Linux. I am pretty > sure it is related. > I have tried `systemctl --user restart > plasma-xdg-desktop-portal-kde.service` and it works. Works for me too. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427953] Unique instance and open in tabs ignored
https://bugs.kde.org/show_bug.cgi?id=427953 kewco...@gmail.com changed: What|Removed |Added CC||kewco...@gmail.com --- Comment #7 from kewco...@gmail.com --- Having the same issue. Have enabled: "Open new files in tabs" but the setting is being ignored -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466635] Notifications still pop up on main screen when Do Not Disturb is checked on multi monitor setup
https://bugs.kde.org/show_bug.cgi?id=466635 --- Comment #4 from Nate Graham --- And are you on Wayland? Could be Bug 451090. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466635] Notifications still pop up on main screen when Do Not Disturb is checked on multi monitor setup
https://bugs.kde.org/show_bug.cgi?id=466635 --- Comment #3 from Nate Graham --- Ok. If you remove all but one and then reboot, does that single Notifications widget behave properly and suppress notifications on all screens? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466635] Notifications still pop up on main screen when Do Not Disturb is checked on multi monitor setup
https://bugs.kde.org/show_bug.cgi?id=466635 --- Comment #2 from voncl...@gmail.com --- yes -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 459551] Oauth2 failure on connecting google groupware
https://bugs.kde.org/show_bug.cgi?id=459551 --- Comment #5 from Mike Benson --- (In reply to Enneamer from comment #3) > Is it because Oob workflow deprecation as suggested in the rclone page? Possibly, but I don't think it likely. The rclone bug referred to seems to me to be trying to do a silent sign in to Gdrive. Akonadi is kicking off a normal interactive Oauth authentication session, using the default browser (in my case, Firefox). I do have 2FA enabled on my Google Accounts. I have tried deleting the permissions assigned to the Akonadi google resource in my google account, and also tried creating an app password (which google will not let me use during the login). No success. My understanding is @dvratil has taken a sabbatical from KDE/Akonadi projects, so I'm not expecting any feedback from him. How do we approach debugging this? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466688] New: [wayland] With a display in the top center, moving the mouse cursor to the top of the screen on one of the side monitors causes the mouse cursor to teleport onto the top cent
https://bugs.kde.org/show_bug.cgi?id=466688 Bug ID: 466688 Summary: [wayland] With a display in the top center, moving the mouse cursor to the top of the screen on one of the side monitors causes the mouse cursor to teleport onto the top center screen Classification: Plasma Product: kwin Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: indecisiveautoma...@gmail.com Target Milestone: --- SUMMARY If you have a display layout with three screens on the bottom and one on the top in the top-center, moving the mouse cursor to the top of one of the left or right side displays causes the mouse cursor to teleport to the bottom of the top-center panel. This only happens if the cursor is approximately more than halfway across the screen in the direction of the top display. This can be reproduced if you move the cursor to the corner of the display opposite to the top-center display. If you're using a display to the left, move the cursor to the top left of the display and move the cursor across the top of the screen to the right. Once the cursor moves more than approximately halfway across, it will teleport to being in the bottom left corner of the top-center display. For a display to the right, the steps should be mirrored, moving the cursor to the left. This makes snapping windows maximised on these bottom displays a little bit harder as trying to maximise them without corner-tiling them can be a bit challenging. Without being careful, it can cause the window to corner-tile in the top display. This did not happen in the Plasma 5.27 beta or Plasma 5.27.0. It first started happening (at least for me) in Plasma 5.27.1, and is still present in Plasma 5.27.2. STEPS TO REPRODUCE (Assumes a display layout as described) 1. On one of the bottom side displays (to the left or right of the bottom center display), put cursor in top corner furthest from the top-center display 2. While keeping the cursor along the top of the display, move it in the direction the top center display (if the cursor was in the top-left corner, move it to the right while keeping it pressed against the top of the display) 3. Cursor will teleport to the corner of the top-center display. OBSERVED RESULT Cursor teleports to top-center display as described. EXPECTED RESULT Cursor should not teleport to the top-center display, and should behave as it did in Plasma 5.27.0 and below. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel 6.2.1 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION - Happens on scaled and non-scaled displays - Have only tried the Wayland session, have not tried X11 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 466668] Pdf viewer tool, wish
https://bugs.kde.org/show_bug.cgi?id=48 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|RESOLVED CC||aa...@kde.org Resolution|--- |INTENTIONAL --- Comment #1 from Albert Astals Cid --- The PDF specification doesn't have a "name" field for annotations, so we can't let you change the title because there's nowhere to store that new title you would use. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 466673] Add ability to save highlighting and annotations in file
https://bugs.kde.org/show_bug.cgi?id=466673 Albert Astals Cid changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- Annotations are saved in the pdf file. If they are not shown in the ipad app, that's an ipad app bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466660] KWin Big Icons TabBox jitters when notifications arrive
https://bugs.kde.org/show_bug.cgi?id=40 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/3732 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466634] When the desktop is running, even at idle, plasmashell will consume all of my 32GB of memory resulting in a system freeze.
https://bugs.kde.org/show_bug.cgi?id=466634 --- Comment #10 from kevin.david.h...@gmail.com --- It rose to ~400Mb. I'll keep an eye on it and let you know if it climbs over time. On Wed, Mar 1, 2023 at 4:24 PM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=466634 > > --- Comment #9 from Nate Graham --- > Thanks. And if you plug in the second screen, does the memory use > immediately > skyrocket? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466634] When the desktop is running, even at idle, plasmashell will consume all of my 32GB of memory resulting in a system freeze.
https://bugs.kde.org/show_bug.cgi?id=466634 --- Comment #9 from Nate Graham --- Thanks. And if you plug in the second screen, does the memory use immediately skyrocket? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466634] When the desktop is running, even at idle, plasmashell will consume all of my 32GB of memory resulting in a system freeze.
https://bugs.kde.org/show_bug.cgi?id=466634 --- Comment #8 from kevin.david.h...@gmail.com --- plasmashell got to about 23Gb in size and crashed/restarted. When it respawned, it grabbed ~390Mb of memory instead of the 2Gb that I was seeing earlier on startup. Still have the one monitor removed from desktop, running in single monitor since the last email. On Wed, Mar 1, 2023 at 2:45 PM Kevin Hall wrote: > Okay, I'll pull one monitor. plasmashell is currently sitting at 20.3Gb > memory usage as of this email. I'll report back in a couple of hours as to > the change or lack thereof. > > On Wed, Mar 1, 2023 at 2:43 PM Nate Graham > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=466634 >> >> --- Comment #6 from Nate Graham --- >> Unplugged would be better, since it's DisplayPort. >> >> Looks like your two screens report identical serial numbers. Despite thir, >> their EDID hash values do differ, so that's nice at least. >> >> Definitely curious to know if the issue goes away with only one screen >> plugged >> in. >> >> -- >> You are receiving this mail because: >> You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 463695] Unable to make screenshot on Wayland
https://bugs.kde.org/show_bug.cgi?id=463695 --- Comment #27 from drmacro --- Still just crashes on Ubuntu 22.04 Wayland -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 --- Comment #11 from Alej --- Confirm bug in plasma desktop 5.27.2 KDE Frameworks Versión 5.103.0 Qt versión 5.15.8 Kmail 5.22.2 (22.12.2) -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 466494] Is the KWallet is insecure?
https://bugs.kde.org/show_bug.cgi?id=466494 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #3 from Piotr Mierzwinski --- (In reply to Nicolas Fella from comment #1) > It's true that any program can request any password from a open wallet. > KWallet was never designed to prevent that, because it's somewhat impossible > to do. It would require that apps can be uniquely identified and can't > "impersonate" another app, which isn't possible in the traditional Linux > world. > > That doesn't mean KWallet is useless though. The primary thing it prevents > is storing passwords in plaintext on the disk so that they can't easily be > read if someone has physical access to your computer, e.g. by stealing your > laptop Yes, but If in my PC will appear malware/ malicious software then will be able to get the password. Am I right? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 Alej changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466687] New: Add shortcuts to allow moving of windows between tiling zones within a layout
https://bugs.kde.org/show_bug.cgi?id=466687 Bug ID: 466687 Summary: Add shortcuts to allow moving of windows between tiling zones within a layout Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Custom Tiling Assignee: kwin-bugs-n...@kde.org Reporter: thomaslukeduf...@hotmail.co.uk CC: notm...@gmail.com Target Milestone: --- SUMMARY In Windows using FancyZones, a combination of the Meta+Arrow keys allows a user to cycle the active window between each of the zones within a layout without having to use Shift+Drag. It's a little bonus feature that makes the custom tiling more useful and intuitive with how it integrates with quick snapping behaviors. It also would allow for some super quick layout management using only the keyboard! Simply adding keyboard shortcuts to cycle to the previous/next zone in a layout would work, though I know other solutions guess at the direction you want to move a window to decide which zone to tile it to, but that's a bit much for the scope of this feature imo. PS: I love the new tiling btw. I think it's what has kept me from cracking and moving back to Pop!OS and GNOME :^) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464727] Dolphin starts having graphical bugs after the "Choose Application" Portal opens (after double clicking on "Unknown" Type file.)
https://bugs.kde.org/show_bug.cgi?id=464727 --- Comment #3 from Andrej Halveland --- It's also 100% reproducible in Ark by right clicking on a text file (for example) and choosing "Open With...". This is on Plasma 5.27.2, KF 5.103.0, Qt 5.15.8. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466686] In Wayland screen goes blank after changing resolution and doesn't come back
https://bugs.kde.org/show_bug.cgi?id=466686 kevin changed: What|Removed |Added CC||pilo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466686] New: In Wayland screen goes blank after changing resolution and doesn't come back
https://bugs.kde.org/show_bug.cgi?id=466686 Bug ID: 466686 Summary: In Wayland screen goes blank after changing resolution and doesn't come back Classification: Applications Product: systemsettings Version: 5.27.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pilo...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Start a Wayland session 2. Choose display settings, change resolution and click apply 3. Screen goes blank and reboot is required OBSERVED RESULT Screen goes blank EXPECTED RESULT Resolution should change and return to settings window SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 466685] New: Touch position wrong on dual monitor set up on touchscreen laptop and always have to remap every log in or restart
https://bugs.kde.org/show_bug.cgi?id=466685 Bug ID: 466685 Summary: Touch position wrong on dual monitor set up on touchscreen laptop and always have to remap every log in or restart Classification: Plasma Product: wacomtablet Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jazzv...@gmail.com Reporter: fdana...@gmail.com Target Milestone: --- SUMMARY *** I use Lenovo ideapad flex 5 which is touchscreen laptop with stylus. I use dual monitor set up. Everytime I logged in I have to remap my touchscreen area. *** SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.27.2 (available in About System) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466684] New: Screen Corners/Touchscreen Gestures - Allow assignment of custom actions/shortcuts
https://bugs.kde.org/show_bug.cgi?id=466684 Bug ID: 466684 Summary: Screen Corners/Touchscreen Gestures - Allow assignment of custom actions/shortcuts Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: thomaslukeduf...@hotmail.co.uk Target Milestone: --- SUMMARY One of the things that limits the Screen corners settings is the limited options available to the user when choosing the behavior of screen corners. For example, I thought it would be cool to be able to change virtual desktops using the L/R corners. I was disappointed that there's only a predetermined list of actions I can select here, when this is available for other settings. It would add a lot of flexibility and perhaps unexpectedly powerful customization with (what I'd imagine is) relatively little effort. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466650] Multimonitor-setup: after login on X11, primary DisplayPort monitor loses signal but still counts as enabled and a part of the desktop
https://bugs.kde.org/show_bug.cgi?id=466650 Nate Graham changed: What|Removed |Added Summary|Multimonitor-setup: Primary |Multimonitor-setup: after |monitor disconnects after |login on X11, primary |login |DisplayPort monitor loses ||signal but still counts as ||enabled and a part of the ||desktop --- Comment #3 from Nate Graham --- Thanks. When it's in this state, can you paste the output of `kscreen-doctor -o`? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465790] Resizing an Aurorae-decorated window leads to malformed decorations
https://bugs.kde.org/show_bug.cgi?id=465790 Nate Graham changed: What|Removed |Added Summary|resizing a window leads to |Resizing an |malformed decoration under |Aurorae-decorated window |Aurorae |leads to malformed ||decorations -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452730] Shadows around Aurorae-decorated windows are not rendered proportionally (Scale-Factor 200%+, wayland, qt)
https://bugs.kde.org/show_bug.cgi?id=452730 Nate Graham changed: What|Removed |Added Summary|Shadows around Windows are |Shadows around |not rendered proportionally |Aurorae-decorated windows |(Scale-Factor 200%+,|are not rendered |wayland, qt)|proportionally ||(Scale-Factor 200%+, ||wayland, qt) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] Line glitches with 125% and 150% scale on Wayland with either Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 Bug Janitor Service changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466620] powerdevil continues to crash in KScreen::AbstractDpmsHelper::isSupported() when HDMI signal is lost
https://bugs.kde.org/show_bug.cgi?id=466620 Nate Graham changed: What|Removed |Added Summary|The bug I reported a few|powerdevil continues to |days ago with Powerdevil|crash in |continues to occur (power |KScreen::AbstractDpmsHelper |management options stop |::isSupported() when HDMI |working). |signal is lost -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466181] powerdevil crashes in KScreen::AbstractDpmsHelper::isSupported()
https://bugs.kde.org/show_bug.cgi?id=466181 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=466620 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466620] The bug I reported a few days ago with Powerdevil continues to occur (power management options stop working).
https://bugs.kde.org/show_bug.cgi?id=466620 Nate Graham changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO See Also||https://bugs.kde.org/show_b ||ug.cgi?id=466181 Severity|normal |crash --- Comment #4 from Nate Graham --- ...I was about to say: `coredumpctl` can help with this. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466620] The bug I reported a few days ago with Powerdevil continues to occur (power management options stop working).
https://bugs.kde.org/show_bug.cgi?id=466620 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #3 from Nate Graham --- The backtrace is virtually identical to the one in Bug 466181. But it's not *exactly* identical. It would help if you could get debug symbols for libkscreen and get a new backtrace. And also not a raw stack trace; an actual human-readable backtrace. `coredumpctl -- You are receiving this mail because: You are watching all bug changes.
