[kwin] [Bug 484015] SDDM Wayland does not go into monitor powersave timeout with no user logged in
https://bugs.kde.org/show_bug.cgi?id=484015 Jonathan Isom changed: What|Removed |Added CC||jei...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485257] Snapd Backend crashes in SnapBackend::populateJobsWithFilter() with Plasma 6 Discover
https://bugs.kde.org/show_bug.cgi?id=485257 Jonathan L Hanmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #3 from Jonathan L Hanmann --- After a lot of trial and error I found that it was indeed due to my snapd-glib-qt. Since I'm building on Ubuntu Noble (beta obviously I guess) the existing package is built against Qt 6.42 probably. This caused the symbol problem which I tried to work around by changing the QStringList to a QList which appeared to work. Although it built ok it caused the runtime crash somehow. I don't understand that exact mechanism. My solution was to build Qt 6.7.0 packages for my system. That took several days to figure out all by itself. I then rebuilt Snapd-Glib against Qt 6.7.0 using. When I installed that and then rebuilt Discover, voila!, it now appears to start and work ok. I will close this if I am allowed to since it was my own problem which I've now resolved. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485257] Snapd Backend crashes in SnapBackend::populateJobsWithFilter() with Plasma 6 Discover
https://bugs.kde.org/show_bug.cgi?id=485257 --- Comment #2 from Jonathan L Hanmann --- Created attachment 168718 --> https://bugs.kde.org/attachment.cgi?id=168718=edit valgrind output log Added valgrind output log from failure -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485796] New: OEM install does not work
https://bugs.kde.org/show_bug.cgi?id=485796 Bug ID: 485796 Summary: OEM install does not work Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: j...@jriddell.org CC: j...@jriddell.org, neon-b...@kde.org Target Milestone: --- OEM install does not work since at last Plasma 6 but maybe before I've updated the oem-prepare/prepare-user/calamares-oem-prepare2 script to use kwriteconfig6 and remove use of plasmapkg which set the theme, however it'll still need a theme set somehow However it doesn't start SDDM on reboot unless you change the oem-config.target to want multi-user.target instead of basic.target. I don't know what's wrong with basic.target. If in doubt blame Wayland? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482341] Error when open Discover: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg)
https://bugs.kde.org/show_bug.cgi?id=482341 Jonathan Riddell changed: What|Removed |Added Resolution|FIXED |--- Latest Commit|https://invent.kde.org/neon | |/neon/keyring/-/commit/b4d2 | |826747c47dabfc64fae50917f21 | |37786cbb6 | Status|RESOLVED|REPORTED --- Comment #3 from Jonathan Riddell --- Issue is at https://invent.kde.org/teams/neon/-/issues/133 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482341] Error when open Discover: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg)
https://bugs.kde.org/show_bug.cgi?id=482341 Jonathan Riddell changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/neon ||/neon/keyring/-/commit/b4d2 ||826747c47dabfc64fae50917f21 ||37786cbb6 Resolution|--- |FIXED --- Comment #2 from Jonathan Riddell --- Git commit b4d2826747c47dabfc64fae50917f2137786cbb6 by Jonathan Riddell. Committed on 17/04/2024 at 14:46. Pushed by jriddell into branch 'Neon/unstable'. remove obsolete code, remove use of deprecated apt-key, install neon keyring into /etc/apt/trusted.gpg.d/ M +6-18 debian/postinst https://invent.kde.org/neon/neon/keyring/-/commit/b4d2826747c47dabfc64fae50917f2137786cbb6 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485402] Calamares does not load on Neon User ISO 20240411-1555
https://bugs.kde.org/show_bug.cgi?id=485402 Jonathan Riddell changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Jonathan Riddell --- sorry, should work on new one -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485381] KDE Partition Manager Will Not Start (Crashes??)
https://bugs.kde.org/show_bug.cgi?id=485381 Jonathan Riddell changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483332] Unable to run KDE Neon live
https://bugs.kde.org/show_bug.cgi?id=483332 --- Comment #5 from Jonathan Riddell --- it might be the switch to wayland by default, e.g. on virtualbox is now needs "3D Accelation" enabled, also EFI -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485381] KDE Partition Manager Will Not Start (Crashes??)
https://bugs.kde.org/show_bug.cgi?id=485381 --- Comment #1 from Jonathan Riddell --- Fixed in the building repo, will be deployed along with kde gear 24.02.2 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485381] KDE Partition Manager Will Not Start (Crashes??)
https://bugs.kde.org/show_bug.cgi?id=485381 Jonathan Riddell changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483092] libkf5runner-dev is missing most files
https://bugs.kde.org/show_bug.cgi?id=483092 Jonathan Riddell changed: What|Removed |Added Resolution|--- |NOT A BUG Status|CONFIRMED |RESOLVED --- Comment #4 from Jonathan Riddell --- As we now ship Plasma 6 we no longer ship KRunner for KF5 and KF5 plugins will no longer build. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481988] Updating to neon 6.0 broke plasma (broken dependencies for plasma-desktop)
https://bugs.kde.org/show_bug.cgi?id=481988 Jonathan Riddell changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 453224] Nothing happens when I click on 'Next' button
https://bugs.kde.org/show_bug.cgi?id=453224 Jonathan Riddell changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 451228] Itinerary does not start
https://bugs.kde.org/show_bug.cgi?id=451228 Jonathan Riddell changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #6 from Jonathan Riddell --- should be fixed with current updates, let me know if it's still an issue -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 380298] No calculator app in default Neon install
https://bugs.kde.org/show_bug.cgi?id=380298 Jonathan Riddell changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |NOT A BUG --- Comment #4 from Jonathan Riddell --- We deliberately don't install any apps except file manager and web browser by default, it's up to the users to decide what to install -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485257] Snapd Backend crashes in SnapBackend::populateJobsWithFilter() with Plasma 6 Discover
https://bugs.kde.org/show_bug.cgi?id=485257
--- Comment #1 from Jonathan L Hanmann ---
Below is the patch I made to libsnapd-qt-2-1 (version 1.64-0ubuntu5 from the
Ubuntu Noble source package. This enabled me to build discover but I don't know
enough to determine if my change could be part of the problem so I thought to
be thorough on this.
Index: snapd-glib-1.64/snapd-qt/auth-data.cpp
===
--- snapd-glib-1.64.orig/snapd-qt/auth-data.cpp
+++ snapd-glib-1.64/snapd-qt/auth-data.cpp
@@ -15,7 +15,7 @@ QSnapdAuthData::QSnapdAuthData (void *sn
QSnapdAuthData::QSnapdAuthData (QObject *parent) : QSnapdWrappedObject
(snapd_auth_data_new ("", NULL), g_object_unref, parent) {}
-QSnapdAuthData::QSnapdAuthData (const QString& macaroon, const QStringList&
discharges, QObject *parent) : QSnapdWrappedObject (NULL, g_object_unref,
parent)
+QSnapdAuthData::QSnapdAuthData (const QString& macaroon, const QList&
discharges, QObject *parent) : QSnapdWrappedObject (NULL, g_object_unref,
parent)
{
g_auto(GStrv) strv = g_new (gchar *, discharges.size () + 1);
int i;
Index: snapd-glib-1.64/snapd-qt/Snapd/auth-data.h
===
--- snapd-glib-1.64.orig/snapd-qt/Snapd/auth-data.h
+++ snapd-glib-1.64/snapd-qt/Snapd/auth-data.h
@@ -22,7 +22,7 @@ class Q_DECL_EXPORT QSnapdAuthData : pub
public:
explicit QSnapdAuthData (void *snapd_object, QObject* parent = 0);
-explicit QSnapdAuthData (const QString& macaroon, const QStringList&
discharges, QObject* parent = 0);
+explicit QSnapdAuthData (const QString& macaroon, const QList&
discharges, QObject* parent = 0);
explicit QSnapdAuthData (QObject* parent = 0);
QString macaroon () const;
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 485257] New: Snapd Backend Crash with Plasma 6 Discover
https://bugs.kde.org/show_bug.cgi?id=485257
Bug ID: 485257
Summary: Snapd Backend Crash with Plasma 6 Discover
Classification: Applications
Product: Discover
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: discover
Assignee: plasma-b...@kde.org
Reporter: jhanm...@ca.rr.com
CC: aleix...@kde.org
Target Milestone: ---
Application: plasma-discover (6.0.80)
(Compiled from sources)
Qt Version: 6.6.3
Frameworks Version: 6.1.0
Operating System: Linux 6.1.43-vpanthor-rk35xx aarch64
Windowing System: Wayland
Distribution: Armbian-unofficial 24.5.0-trunk noble
DrKonqi: 6.0.80 [KCrashBackend]
-- Information about the crash:
No special preconditions prior to running Discover to instigate the crash.
Whether I run via the menu or via command line the same crash occurs. If I
manually specify all other backends other then the Snapd backend Discover will
successfully start. I can use the snap command line utility. I've installed
Chromium via the snap command line utility and Chromium is fully functional so
it isn't that snapd isn't alive or functional.
In order to build Discover I had to modify the system libsnap-qt due to
QSnapAuth using QStringList in the system library for the second constructor
argument whereas the Discover Snapd backend appears to use QList. This
causes a linker error. This is the only change I made to libsnapd-qt in order
to build Discover.
This will likely appear in the crash information but to offer some clear
visibility into my environment. I am running Ubuntu Noble on a Radxa Rock-5b.
This is an aarch64 machine. I had to do custom builds of Mesa (OpenGL/OpenGLES
libraries) and QT 6.6.3 to build and run Plasma 6. I built Qt 6.6.3 using
kdesrc-build. Qt and Plasma 6 are installed only locally for my user and not as
system binaries.
The crash can be reproduced every time.
-- Backtrace:
Application: Discover (plasma-discover), signal: Bus error
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6 0xb0114c80 in __aarch64_ldadd4_acq_rel () at
/home/jon/kde/qt/lib/libQt6Core.so.6
#7 0xaff31684 in std::__atomic_base::fetch_add
(__m=std::memory_order_acq_rel, __i=1, this=) at
/usr/include/c++/13/bits/atomic_base.h:635
#8 QAtomicOps::ref (_q_value=) at
/home/jon/kde/src/qtbase/src/corelib/thread/qatomic_cxx11.h:258
#9 QBasicAtomicInteger::ref (this=) at
/home/jon/kde/src/qtbase/src/corelib/thread/qbasicatomic.h:49
#10 QThreadData::ref (this=) at
/home/jon/kde/src/qtbase/src/corelib/thread/qthread.cpp:99
#11 0xafe71538 in QObjectPrivate::connectImpl
(sender=sender@entry=0xc4eb7cd0, signal_index=11,
receiver=receiver@entry=0xc4ebc6b0, slot=slot@entry=0x7fffe1d8,
slotObjRaw=slotObjRaw@entry=0x680013d0, type=type@entry=0,
types=types@entry=0x0, senderMetaObject=senderMetaObject@entry=0x9818fb10
) at
/home/jon/kde/src/qtbase/src/corelib/kernel/qobject.cpp:5189
#12 0xafe71c40 in QObject::connectImpl
(sender=sender@entry=0xc4eb7cd0, signal=signal@entry=0x7fffe1e8,
receiver=receiver@entry=0xc4ebc6b0, slot=slot@entry=0x7fffe1d8,
slotObjRaw=0x680013d0, type=type@entry=Qt::AutoConnection,
types=types@entry=0x0, senderMetaObject=,
senderMetaObject@entry=0x9818fb10 ) at
/home/jon/kde/src/qtbase/src/corelib/kernel/qobject.cpp:5119
#13 0x9816ca38 in QObject::connect (type=Qt::AutoConnection, slot=@0x7fffe1d8: (void
(QSnapdRequest::*)(class QSnapdRequest * const)) 0x98101300
, context=0xc4ebc6b0, signal=(void
(SnapBackend::*)(class SnapBackend * const)) 0x981699e4
, sender=0xc4eb7cd0) at
/home/jon/kde/qt/include/QtCore/qobject.h:240
#14
SnapBackend::populateJobsWithFilter(QList
const&, std::function
const&)>&)::{lambda()#1}::operator()() const (__closure=) at
/home/jon/kde/src/discover/libdiscover/backends/SnapBackend/SnapBackend.cpp:182
#15 std::__invoke_impl(QList
const&, std::function
const&)>&)::{lambda()#1}&>(std::__invoke_other,
SnapBackend::populateJobsWithFilter(QList
const&, std::function
const&)>&)::{lambda()#1}&) (__f=) at
/usr/include/c++/13/bits/invoke.h:61
#16
std::__invoke(QList
const&, std::function
const&)>&)::{lambda()#1}&>(SnapBackend::populateJobsWithFilter(QList
const&, std::function
const&)>&)::{lambda()#1}&) (__fn=) at
/usr/include/c++/13/bits/invoke.h:96
#17
std::invoke(QList
const&, std::function
const&)>&)::{lambda()#1}&>(SnapBackend::populateJobsWithFilter(QList
const&, std::function
const&)>&)::{lambda()#1}&) (__fn=) at
/usr/include/c++/13/functional:113
#18
QtConcurrent::StoredFunctionCall(QList
const&, std::function
const&)>&)::{lambda()#1}>::runFunctor()::{lambda(SnapBackend::populateJobsWithFilter(QList
const&, std::function
[Discover] [Bug 473332] Discover crashes in KNSCore::ResultsStream::fetch when searching
https://bugs.kde.org/show_bug.cgi?id=473332 --- Comment #19 from Jonathan Isom --- (In reply to Waleed Hamra from comment #18) > Is this crash still happening to other reporters? > > I had a bug marked as a duplicate of this and for me, in 6.0.3 of Discover, > my initial reproducible crashes are no longer happening. I tested a week or 2 ago and it was crashing then. I just did a little test and it didn't crash now. Definitely an improvement. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 484859] haruna: Update to version 1.0.2 with Qt6 and KF6
https://bugs.kde.org/show_bug.cgi?id=484859 --- Comment #4 from Jonathan Riddell --- mm it doesn't work with our version of ffmpeg and I'm not too keen to update that as it's a big backport task that might break other things, it might need to wait for us to move to newer Ubuntu -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 484859] haruna: Update to version 1.0.2 with Qt6 and KF6
https://bugs.kde.org/show_bug.cgi?id=484859 --- Comment #2 from Jonathan Riddell --- Build failure is: 14:06:34 [ 61%] Building CXX object src/CMakeFiles/haruna.dir/framedecoder.cpp.o 14:06:37 /workspace/build/src/framedecoder.cpp: In member function ‘void FrameDecoder::seek(int)’: 14:06:37 /workspace/build/src/framedecoder.cpp:210:46: error: ‘AV_FRAME_FLAG_KEY’ was not declared in this scope; did you mean ‘AV_PKT_FLAG_KEY’? some video library dependency is the wrong version maybe -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 484859] haruna: Update to version 1.0.2 with Qt6 and KF6
https://bugs.kde.org/show_bug.cgi?id=484859 Jonathan Riddell changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Jonathan Riddell --- it needs the build fixed -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 484940] libkcolorpicker-qt6-0 failed to install in updates
https://bugs.kde.org/show_bug.cgi?id=484940 Jonathan Riddell changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/neon ||/backports-jammy/kcolorpick ||er/-/commit/d329fb071b4e989 ||8019f151ecdc85730db186efe Resolution|--- |FIXED --- Comment #8 from Jonathan Riddell --- Git commit d329fb071b4e9898019f151ecdc85730db186efe by Jonathan Riddell. Committed on 03/04/2024 at 14:22. Pushed by jriddell into branch 'Neon/release'. conflict libkcolorpicker0 M +7-11 debian/control https://invent.kde.org/neon/backports-jammy/kcolorpicker/-/commit/d329fb071b4e9898019f151ecdc85730db186efe -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 484940] libkcolorpicker-qt6-0 failed to install in updates
https://bugs.kde.org/show_bug.cgi?id=484940 --- Comment #1 from Jonathan Riddell --- Ug sorry about that, libkcolorpicker0 comes from Ubuntu so we should add a breaks/replaces but the archives are busy building Qt 6.7 so that won't be published until that's done. To work around run apt remove libkcolorpicker0 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483717] Bluetooth does not work, ever since Plasma 6.0 release.
https://bugs.kde.org/show_bug.cgi?id=483717 Jonathan Riddell changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 484442] gwenview fails to open
https://bugs.kde.org/show_bug.cgi?id=484442 --- Comment #2 from Jonathan Riddell --- Please paste output of apt-cache policy libkimageannotator-qt6-0 and of ls -l /usr/lib/x86_64-linux-gnu/libkImageAnnotator-Qt6.so* and of apt-cache policy gwenview -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 470794] Packaged version of PlasmaTube depends on outdated and broken version of yt-dlp
https://bugs.kde.org/show_bug.cgi?id=470794 --- Comment #2 from Jonathan Riddell --- There's a general KDE issue here too, why does it not specify the version of yt-dlp needed at build time etc.. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 484287] kdescr-build missing some dependencies
https://bugs.kde.org/show_bug.cgi?id=484287 --- Comment #4 from Jonathan L Hanmann --- Apologies 5 should be libgtk-3-dev not gtk-3-dev Also required were: 8. libibus-1.0-dev 9. libscim-dev 10. xserver-xorg-input-libinput-dev 11. xserver-xorg-input-evdev-dev 12. xserver-xorg-dev -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 484287] kdescr-build missing some dependencies
https://bugs.kde.org/show_bug.cgi?id=484287 --- Comment #3 from Jonathan L Hanmann --- 5. Python3 module chai. I had to do a user install with pip and an override option. 6. gtk-3-dev 7. libpython3.12-dev -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483759] Add ability to put a window in a portion of a tiling layout zone by placement Top/Bottom 25%
https://bugs.kde.org/show_bug.cgi?id=483759 --- Comment #2 from Jonathan Isom --- (In reply to Nick from comment #1) > Hi - I'm a little unclear about this request. Would it be possible to > provide a little more detail so the feature request is really clear? Thanks, > Nick If looking at the default tiling layout, 3 zones in a 1x3 layout, currently when moving a window into one of the zones the window will fill that zone. My suggestion is that if a window is dragged to either the upper 25% or lower 25% of a zone it would fill only that half, creating 2 sub-zones each. With the 3 zones in the default it would effectively allow 6 windows, 3 top and 3 bottom in a 2x3 layout, to be tiled onscreen without having to subdivide the zones in the template editor ahead of time. This would add additional flexibility to the tiling system and apply only temporarily until the window(s) are moved out. Currently if I wanted to do this I'd have to go to the tiling layout editor, split the zone vertically, use the layout for ever how long that is, then undo the split when I am done. Hope that is clearer. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 484287] kdescr-build missing some dependencies
https://bugs.kde.org/show_bug.cgi?id=484287 --- Comment #2 from Jonathan L Hanmann --- 4. ruby-sass -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 484287] kdescr-build missing some dependencies
https://bugs.kde.org/show_bug.cgi?id=484287 --- Comment #1 from Jonathan L Hanmann --- Apologies. libdisplay-info should be libdisplay-info-dev. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 484287] New: kdescr-build missing some dependencies
https://bugs.kde.org/show_bug.cgi?id=484287 Bug ID: 484287 Summary: kdescr-build missing some dependencies Classification: Developer tools Product: kdesrc-build Version: Git Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mp...@kde.org Reporter: jhanm...@ca.rr.com Target Milestone: --- SUMMARY kdesrc-build --initial-setup and --install-distro-packages did not install all necessary dependencies on my build system. I had to install the following additional packages manually. 1. libxcb-xinput-dev 2. libdisplay-info 3. xdotool STEPS TO REPRODUCE 1. Installed kdesrc-build from git. 2. Ran kdesrc-build --initial-setup 3. Ran kdesrc-build --install-distro-packages 4. Ran kdesrc-build workspace OBSERVED RESULT kdesrc-build failed on several components until the listed packages were installed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux kernel version 6.8.1 (Linux rock-5b-1 6.8.1-edge-rockchip-rk3588 #2 SMP PREEMPT Fri Mar 15 18:19:29 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux) KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.80 Qt Version: 6.6.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483956] neon-ubuntu-advantage-tools : Breaks: ubuntu-advantage-tools but 31.2~22.04 is to be installed
https://bugs.kde.org/show_bug.cgi?id=483956 --- Comment #5 from Jonathan Riddell --- now deployed -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483956] neon-ubuntu-advantage-tools : Breaks: ubuntu-advantage-tools but 31.2~22.04 is to be installed
https://bugs.kde.org/show_bug.cgi?id=483956 --- Comment #4 from Jonathan Riddell --- update-manager-core added a versioned depends on ubuntu-advantage-tools so our newly introduced neon-ubuntu-advantage-tools no longer works. I'm testing a fix to be deployed shortly -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483980] Neon Arm64 ISO file needed, thanks
https://bugs.kde.org/show_bug.cgi?id=483980 Jonathan Riddell changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Jonathan Riddell --- This would be nice to have yes. More a feature than a bug of course. What's your use case? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] With NVIDIA GPU on X11, unable to interact with windows sometimes; instead interacts with Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=478556 Jonathan Lopes changed: What|Removed |Added CC||joniwe...@gmail.com --- Comment #11 from Jonathan Lopes --- I'm running Plasma 6 on Wayland and have the exact same problem with all IntelliJ IDEs. The problem happens whenever I have an XWayland application behind the IDE. My current “workaround” is to bring a native Wayland window to the foreground before switching to the IDE so I never have an XWayland application below it. To illustrate it better (I hope bugzilla does not break the formatting), imagine that I opened Dolphin maximized, then opened IntelliJ IDEA: > | Dolphin | > | | IntelliJ | > | | | > | | | > |--| | >|--| IntelliJ is on top of Dolphin, so this problem never happens. Also, if there's nothing behind it (i.e. only the desktop) the problem doesn't happen as well. Now if I open Steam, which is runs on XWayland, It will go on top of IntelliJ: > | Dolphin | > | | IntelliJ | > | | | Steam | > | | | | > |--| | | >|--| | > |--| Anything that I type on Steam gets captured by the Steam window as expected, but if I bring IntelliJ to the front: > | Dolphin | > | | Steam | > | | | IntelliJ | > | | | | > |--| | | >|--| | > |--| The *Icons-only Task Manager* shows that IntelliJ is focused, but anything that I type or click on IntelliJ, gets sent to Steam instead (which is very awkward). The same happens with applications like Slack that also runs on XWayland: I type on IntelliJ, but the keys go to Slack instead. I notice this problem very often because it's not uncommon for me to have IntelliJ, RustRover, PyCharm and WebStorm all running at the same time, and I very often find myself trying to type on IntelliJ only to find out that all the keystrokes went to PyCharm (despite the Task Manager showing that IntelliJ is focused). Reproducing this problem is very tricky, there are days that I start and finish my job without it ever happening, but once it starts happening, not even closing all IDEA instances and opening again fixes it. The only workaround is to either minimize all windows and only have the desktop behind the IDE, or to have a native Wayland application behind the IDE, like Firefox for example: > | Dolphin | > | | Steam | > | | | Firefox | > | | | | IntelliJ | > | | | | | > |--| | | | >|--| | | > |--| | > |--| This is something that never happened on Plasma 5 (at least for me), but TBF, it's only happening with IntelliJ, no other X11 application running under XWayland suffers from this, and Java applications have always been problematic under XWayland. One small problem I noticed was that when I launched Steam, IntelliJ was forcefully brought to the foreground and RustRover got highlighted in the Task Manager (as if it requested focus). This was the first time that something stole the focus forcefully even with the “Focus Stealing Prevention” set to “High”. Note that I don't think “Focus Stealing Prevention” has anything to do with the problem as I only changed this setting a couple of days ago, but I've been experiencing this “input being sent to the wrong window” since the official release of Plasma 6 (only with IntelliJ tho). System: > Operating System: Arch Linux > KDE Plasma Version: 6.0.2 > KDE Frameworks Version: 6.0.0 > Qt Version: 6.6.2 > Kernel Version: 6.8.1-arch1-1 (64-bit) > Graphics Platform: Wayland > Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor > Memory: 62,7 GiB of RAM > Graphics Processor: AMD Radeon RX 6800 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 483652] vcpkg build fails unless plugins are built statically
https://bugs.kde.org/show_bug.cgi?id=483652 --- Comment #4 from Jonathan Kimmitt --- Thanks for the patch. It does not immediately seem to solve the problem of the lack of pre-existence of kmm_gpgfile_export.h. I have placed a copy from a previous build in kmymoney/mymoney/storage/kmm_gpgfile_export.h which seems to solve the problem of the App not building. As of now the file is used in the ninja build before it is generated. However in this location in prevents the new version from being generated in the build directory, which might be a bad thing. There is no recipe for encryption support in vcpkg at the moment that would provide a better solution. The overall objective of static linking for me is to reduce reliance on fragile .dynlib files such as provided in /opt/homebrew and make the Application image portable to other Macs. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483759] New: Add ability to put a window in a portion of a tiling layout zone by placement Top/Bottom 25%
https://bugs.kde.org/show_bug.cgi?id=483759 Bug ID: 483759 Summary: Add ability to put a window in a portion of a tiling layout zone by placement Top/Bottom 25% Classification: Plasma Product: kwin Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Custom Tiling Assignee: kwin-bugs-n...@kde.org Reporter: jei...@gmail.com CC: notm...@gmail.com Target Milestone: --- SUMMARY When not using the custom tiling feature if I drag to a side and either the top or bottom 25% it will do a quarter of the screen. I would like the ability when I move a window using the tiling modifier into the top or bottom 25% of a zone to use the top or bottom half of that zone. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.10-273-tkg-linux-tkg (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4080/PCIe/SSE2 Product Name: X570M Pro4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483758] New: Add ability to lock tiling layout
https://bugs.kde.org/show_bug.cgi?id=483758 Bug ID: 483758 Summary: Add ability to lock tiling layout Classification: Plasma Product: kwin Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Custom Tiling Assignee: kwin-bugs-n...@kde.org Reporter: jei...@gmail.com CC: notm...@gmail.com Target Milestone: --- SUMMARY I have been accidently resizing windows that are tiled and that changes my tiling layout. I'd like it locked so even if I resize a window I can just put the window back by moving it with the modifier key. STEPS TO REPRODUCE 1. Put a window in a tile 2. Drag a side of a window 3. Tile layout is now different OBSERVED RESULT Layout is changed EXPECTED RESULT Layout is not changed SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.10-273-tkg-linux-tkg (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4080/PCIe/SSE2 Product Name: X570M Pro4 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 483652] vcpkg build fails unless plugins are built statically
https://bugs.kde.org/show_bug.cgi?id=483652 --- Comment #2 from Jonathan Kimmitt --- build/kmymoney/misc/kmm_gpgfile_export.h seems to get created as a result of the build process. However it is needed to compile kgpgfile.h; if you don't have a successful build than you cannot bootstrap the process without commenting out the reference to kgpgfile.h. I suppose this is some dependency issue in make, however I lack sufficient familiarity with this tool. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 483652] New: vcpkg build fails unless plugins are built statically
https://bugs.kde.org/show_bug.cgi?id=483652
Bug ID: 483652
Summary: vcpkg build fails unless plugins are built statically
Classification: Applications
Product: kmymoney
Version: git (master)
Platform: Compiled Sources
OS: macOS
Status: REPORTED
Severity: normal
Priority: NOR
Component: buildsystem
Assignee: kmymoney-de...@kde.org
Reporter: jonat...@kimmitt.co.uk
Target Milestone: ---
Created attachment 167252
--> https://bugs.kde.org/attachment.cgi?id=167252=edit
kmymoney MacOS execution backtrace
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. Install the manifest given in kmymoney git tree using "vcpkg install"
2. Configure using "cmake ..
-DCMAKE_TOOLCHAIN_FILE=/Users/jonathan/vcpkg/scripts/buildsystems/vcpkg.cmake
-G Ninja -DCMAKE_BUILD_TYPE=Debug"
3. ninja
4. lldb bin/kmymoney.app/Contents/MacOS/kmymoney
5. run
OBSERVED RESULT
as per attached backtrace
EXPECTED RESULT
The main window appears
SOFTWARE/OS VERSIONS
macOS:
Qt Version:
ADDITIONAL INFORMATION
To compile I had to comment out certain lines that caused errors. This might be
because it is expecting QT6 or some other version issue.
diff --git a/kmymoney/dialogs/kequitypriceupdatedlg.cpp
b/kmymoney/dialogs/kequitypriceupdatedlg.cpp
index 6773525d2..2cb63044c 100644
--- a/kmymoney/dialogs/kequitypriceupdatedlg.cpp
+++ b/kmymoney/dialogs/kequitypriceupdatedlg.cpp
@@ -417,7 +417,7 @@ public:
m_progressDelay.start();
m_quote.setDateRange(ui->m_fromDate->date(), ui->m_toDate->date());
-m_quote.setUseSingleQuoteSignal(true);
+ //FIXME!!m_quote.setUseSingleQuoteSignal(true);
m_abortUpdate = false;
for (int row = 0; !m_abortUpdate && row < rows; ++row) {
diff --git a/kmymoney/plugins/xml/kcm_xmlstorage.cpp
b/kmymoney/plugins/xml/kcm_xmlstorage.cpp
index a53d0a19b..50a524bbc 100644
--- a/kmymoney/plugins/xml/kcm_xmlstorage.cpp
+++ b/kmymoney/plugins/xml/kcm_xmlstorage.cpp
@@ -22,7 +22,9 @@
// Project Includes
#include "config-kmymoney.h"
+#ifdef ENABLE_GPG
#include "kgpgfile.h"
+#endif
#include "kmymoneysettings.h"
#define RECOVER_KEY_ID "0xD2B08440"
diff --git a/kmymoney/plugins/xml/kgpgkeyselectiondlg.cpp
b/kmymoney/plugins/xml/kgpgkeyselectiondlg.cpp
index 263381a19..530ee1f5a 100644
--- a/kmymoney/plugins/xml/kgpgkeyselectiondlg.cpp
+++ b/kmymoney/plugins/xml/kgpgkeyselectiondlg.cpp
@@ -18,7 +18,9 @@
// Project Includes
#include "config-kmymoney.h"
+#ifdef ENABLE_GPG
#include
+#endif
#include
class KGpgKeySelectionDlgPrivate
diff --git a/kmymoney/plugins/xml/xmlstorage.cpp
b/kmymoney/plugins/xml/xmlstorage.cpp
index 492eaf9a7..b8372b5de 100644
--- a/kmymoney/plugins/xml/xmlstorage.cpp
+++ b/kmymoney/plugins/xml/xmlstorage.cpp
@@ -36,7 +36,9 @@
#include "appinterface.h"
#include "icons.h"
+#ifdef ENABLE_GPG
#include "kgpgfile.h"
+#endif
#include "kgpgkeyselectiondlg.h"
#include "kmymoneyenums.h"
#include "kmymoneysettings.h"
diff --git a/kmymoney/widgets/passstore.cpp b/kmymoney/widgets/passstore.cpp
index e60048c93..fd7c16eeb 100644
--- a/kmymoney/widgets/passstore.cpp
+++ b/kmymoney/widgets/passstore.cpp
@@ -24,7 +24,9 @@
// Project Includes
#include "icons.h"
+#ifdef ENABLE_GPG
#include "kgpgfile.h"
+#endif
using namespace Icons;
--
You are receiving this mail because:
You are watching all bug changes.
[neon] [Bug 482305] Cannot install Kjots in KDE 6, dependency issue
https://bugs.kde.org/show_bug.cgi?id=482305 --- Comment #5 from Jonathan Riddell --- Could Zanshin or KNotes be a recommended replacement? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483332] Unable to run KDE Neon live
https://bugs.kde.org/show_bug.cgi?id=483332 --- Comment #2 from Jonathan Riddell --- The new neon-user-20240314-0716.iso image is similarly working fine for me -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482964] KDE neon 6.0 X11 session does not recover properly from a suspend state
https://bugs.kde.org/show_bug.cgi?id=482964 --- Comment #6 from Jonathan Richards --- (In reply to Nate Graham from comment #5) > Excellent, I had a feeling it would. Most likely it was Bug 481308 all > along, or one of the other ones fixed alongside that for 6.0.2. > > *** This bug has been marked as a duplicate of bug 481308 *** Many thanks - although I searched before reporting, I didn't find 481308 - must try harder! Also I note that my hypothesis about the QRhiGles2 message is wrong: that message occurs when switching between tty2 and tty3, with a Kwin popup about a graphics reset. Not a bug, not even a minor irritation. Thanks again Jonathan (In reply to Nate Graham from comment #5) > Excellent, I had a feeling it would. Most likely it was Bug 481308 all > along, or one of the other ones fixed alongside that for 6.0.2. > > *** This bug has been marked as a duplicate of bug 481308 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482964] KDE neon 6.0 X11 session does not recover properly from a suspend state
https://bugs.kde.org/show_bug.cgi?id=482964 Jonathan Richards changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Jonathan Richards --- (In reply to Nate Graham from comment #2) > Any chance you can try again with Plasma 6.0.2 which was released yesterday? > There are some changes in there what may have fixed this. Thanks, Nate. I have repeated steps 1 and 2 of my original report (i.e. suspending and resuming) and can confirm that the X11 session on tty2 is resumed exactly as I would expect. I've attached a list of the 6.0.2 packages that were updated; some change in there somewhere has eliminated this bug for me. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483237] NFS ioworker needs porting to KF6
https://bugs.kde.org/show_bug.cgi?id=483237 Jonathan Marten changed: What|Removed |Added Summary|Unknown protocol 'nfs' |NFS ioworker needs porting ||to KF6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482964] KDE neon 6.0 X11 session does not recover properly from a suspend state
https://bugs.kde.org/show_bug.cgi?id=482964 --- Comment #3 from Jonathan Richards --- Created attachment 167121 --> https://bugs.kde.org/attachment.cgi?id=167121=edit Extract from a pkcon update including plasma 6.0.2 Selected from the pkcon log with $ grep -E "^ .*6\.0\.2" 202403131931-update.log -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483237] Unknown protocol 'nfs'
https://bugs.kde.org/show_bug.cgi?id=483237 Jonathan Marten changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #5 from Jonathan Marten --- Setting to CONFIRMED as a reminder to port the NFS ioworker. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483332] Unable to run KDE Neon live
https://bugs.kde.org/show_bug.cgi?id=483332 --- Comment #1 from Jonathan Riddell --- The ISO works fine for me running in VirtualBox. I'll snapshot and make a new ISO and test that on real hardware -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482305] Cannot install Kjots in KDE 6, dependency issue
https://bugs.kde.org/show_bug.cgi?id=482305 --- Comment #3 from Jonathan Riddell --- KJots has no currently working released version unfortunately. We should make a dummy override package in Neon and remove it from apps.kde.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483313] Dolphin not allowing creation of files in NFS share
https://bugs.kde.org/show_bug.cgi?id=483313 Jonathan Marten changed: What|Removed |Added CC||j...@keelhaul.me.uk --- Comment #1 from Jonathan Marten --- Possibly related to bug 482899 (not recognising that group write access is allowed)? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483237] Unknown protocol 'nfs'
https://bugs.kde.org/show_bug.cgi?id=483237 Jonathan Marten changed: What|Removed |Added CC||j...@keelhaul.me.uk Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #3 from Jonathan Marten --- Bug update clash -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483237] Unknown protocol 'nfs'
https://bugs.kde.org/show_bug.cgi?id=483237 --- Comment #2 from Jonathan Marten --- Can you confirm how you "access my NFS directory location"? If the NFS filesystem is mounted on the system in the usual way, either by root or by the automounter, then it can be accessed through Dolphin in the same way as any other local filesystem. The NFS ioworker allows NFS servers to be accessed without needing mounting or root access, via a URL starting "nfs://server/path...". However, the build of this has been disabled (since October 2023) and it has been removed from kio-extras (since February 2024) since porting work to KF6 is required. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482964] KDE neon 6.0 X11 session does not recover properly from a suspend state
https://bugs.kde.org/show_bug.cgi?id=482964 Jonathan Richards changed: What|Removed |Added Summary|KDE neon 6.0 does not |KDE neon 6.0 X11 session |recover properly from a |does not recover properly |suspend state |from a suspend state -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458233] In some games, controlling the camera with mouse, camera occasionally snaps into a different position when using Wayland
https://bugs.kde.org/show_bug.cgi?id=458233 Jonathan Croteau-Dicaire changed: What|Removed |Added CC||jonathan.croteau.dicaire@gm ||ail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482964] KDE neon 6.0 does not recover properly from a suspend state
https://bugs.kde.org/show_bug.cgi?id=482964 --- Comment #1 from Jonathan Richards --- >From original reporter: Possibly the installed GLES packages are of interest (dpkg listing) ii libgles-dev:amd641.4.0-1 amd64Vendor neutral GL dispatch library -- GLES development files ii libgles1:amd64 1.4.0-1 amd64 Vendor neutral GL dispatch library -- GLESv1 support ii libgles2:amd64 1.4.0-1 amd64 Vendor neutral GL dispatch library -- GLESv2 support ii libnvidia-gl-535:amd64 535.161.07-0ubuntu0.22.04.1amd64 NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD ii libnvidia-gl-535:i386 535.161.07-0ubuntu0.22.04.1i386 NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482964] New: KDE neon 6.0 does not recover properly from a suspend state
https://bugs.kde.org/show_bug.cgi?id=482964 Bug ID: 482964 Summary: KDE neon 6.0 does not recover properly from a suspend state Classification: Plasma Product: plasmashell Version: 6.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jnoricha...@blueyonder.co.uk CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 166785 --> https://bugs.kde.org/attachment.cgi?id=166785=edit Extract from a pkcon update to KDE Neon 6.0 PROBLEM: It is my practice to suspend the PC overnight rather than shutdown and restart. Recently the Plasma session has not resumed properly from the suspend state. SUMMARY: Following a recent update, KDE neon 6.0 does not recover properly from a suspend state. The problem occurred first after updating on Mar 3, affecting several KDE packages (extract from pkcon log is attached) After this update, resuming an X11 session from a suspend state results in a black screen, i.e. the session is not rendered, although the session is functionally present (see steps to reproduce, below). The following error from /var/log/syslog seems to be relevant (this is the oldest) Mar 4 09:16:09 Odin sddm-greeter-qt6[4609]: QRhiGles2: Context is lost. Mar 4 09:16:14 Odin sddm-greeter-qt6[4609]: QRhiGles2: Context is lost. STEPS TO REPRODUCE: 1. Enter suspend state from X11 session command line in a Konsole window: [code]$ sudo systemctl suspend[/code] Observed: System suspends as expected, with no signal to monitor, standby indication on motherboard. 2. Resume with momentary power switch activation Observed: Signal to monitor is restored, screen is deep black. 3. Move mouse Observed: mouse cursor, which changes according to the UI elements not being displayed: the edges of the Konsole window are "visible" to the mouse cursor, and are displayed on the monitor as changed mouse cursor appearance. 4. Open a new shell on tty3 [Alt-Ctl-F3] and log in Observed: new session is successfully started. 5. [code]$top[/code] Observed: plasmashell is running, as are the backends of the desktop widgets. 6. Switch back to the X11 session on tty2 [Alt-Ctl-F2] Observed: black screen as at steps 2-3. 7. Switch again to tty3, examine /var/log/syslog $ grep -E "^Mar 9 10:1.*Gles2" /var/log/syslog Mar 9 10:10:19 Odin plasmashell[3285]: QRhiGles2: Context is lost. Mar 9 10:15:53 Odin plasmashell[3285]: QRhiGles2: Context is lost. Mar 9 10:18:06 Odin plasmashell[3285]: QRhiGles2: Context is lost. Observed: every time the X11 session is asked to write to tty2, the QRhiGles2 message is issued. Also Observed: comments at https://codebrowser.dev/qt6/qtbase/src/gui/rhi/qrhigles2.cpp.html are incomprehensible to ordinary humans :) 8. From tty3, restart the sddm greeter $ sudo service sddm restart Observed: an X11 session, properly rendered on the screen is started, but on tty1. tty2 session is ended. Also observed: the same effect can be achieved by issuing the restart command "blind" in the non-displaying X11 session Konsole on tty2: it's there, and functional, just not displaying anything. Info Centre report: Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-25-generic (64-bit) Graphics Platform: X11 Processors: 6 × AMD Phenom(tm) II X6 1090T Processor Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 481993] Discover fails to launch after upgrade to Neon 6.0
https://bugs.kde.org/show_bug.cgi?id=481993 Jonathan Verner changed: What|Removed |Added CC||jonathan.ver...@matfyz.cz -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 482077] powerdevil can pass -1 to KIdleTime::addIdleTimeout()
https://bugs.kde.org/show_bug.cgi?id=482077 --- Comment #56 from Jonathan Lopes --- (In reply to Dāvis from comment #55) > But I disagree that this is Powerdevil's bug. KWin should either respect > this and notify after ~50days or ignore it and potentially let application > know this in some way. > > Powerdevil doing some stupid shit is just another bug - of course should be > fixed but that doesn't mean KWin shouldn't be fixed aswell because ANY > application can send garbage to it. I think this was already addressed by this commit: https://invent.kde.org/frameworks/kidletime/-/commit/68a1e22b643e04cbe813108e4b1c5ec2460b097e (In reply to Vlad Zahorodnii from comment #50) > It looks like a regression after > https://invent.kde.org/plasma/powerdevil/-/merge_requests/301/diffs > > powerdevil used to have "timeout > 0" guards, which are missing now I didn't see your message but I think we both found the same thing. Thanks for looking out Vlad Zahorodnii, now it's just a matter of time until it's fixed. Thank everyone as well for helping! -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 482077] powerdevil can pass -1 to KIdleTime::addIdleTimeout()
https://bugs.kde.org/show_bug.cgi?id=482077 --- Comment #53 from Jonathan Lopes --- Just a follow up, I just achieved to reproduce the same thing on my NixOS laptop, which was not suffering from this. On Energy Saving settings, deselect “Turn Off screen” on all modes: On AC Power, On Batter and On Low Battery (it might not be needed to change all of them, but this was what I did), then reboot, if you lock and unlock, this problem will happen (locking is enough actually). -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 482077] powerdevil can pass -1 to KIdleTime::addIdleTimeout()
https://bugs.kde.org/show_bug.cgi?id=482077 --- Comment #52 from Jonathan Lopes --- (In reply to Jonathan Lopes from comment #51) > Does have a check. Ignore this last line, I mistakenly moved it to the end lmao. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 482077] powerdevil can pass -1 to KIdleTime::addIdleTimeout()
https://bugs.kde.org/show_bug.cgi?id=482077 --- Comment #51 from Jonathan Lopes --- Created attachment 166718 --> https://bugs.kde.org/attachment.cgi?id=166718=edit powerdevil.gdb (In reply to Vlad Zahorodnii from comment #49) > (In reply to Jonathan Lopes from comment #48) > > 2652 is powerdevil > > > > > $ ps -p 2652 -o command > > > COMMAND > > > /usr/lib/org_kde_powerdevil > > Hmm, can you attach gdb to powerdevil and add a breakpoint in > KIdleTime::addIdleTimeout please? Sure. I noticed that if I enable my Energy Saving settings and then disable, this prevents the problem from happening until the next boot (but only if you change before the flood starts, it won't help if it's already flooding the logs). I looked at the source code and I found this relevant section: https://invent.kde.org/plasma/powerdevil/-/blob/Plasma/6.0/daemon/actions/bundled/dpms.cpp?ref_type=heads#L220-227 There's no condition to check if the setting is enabled in the first place, while this one: https://invent.kde.org/plasma/powerdevil/-/blob/Plasma/6.0/daemon/actions/bundled/dpms.cpp?ref_type=heads#L177-179 Which supports my first attempt to add a breakpoint to powerdevil after having changed its settings, when I enabled, it loaded the default values in memory, when I disabled, those values were not reset. But after rebooting, the problem was back since those values will not be set as the setting is disabled. That's my guess, I don't really know if this is indeed the cause of the problem, but it looks like. Does have a check. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482077] Journal is flooded with "QObject::startTimer: Timers cannot have negative intervals"
https://bugs.kde.org/show_bug.cgi?id=482077 --- Comment #48 from Jonathan Lopes --- (In reply to Vlad Zahorodnii from comment #46) > > It looks like some application is using > > ext_idle_notifier_v1::get_idle_notification() with 4294967295ms as timeout > > value, it's uint so this is kinda valid... > > can you apply the patch that I've attached to the bug report. it's going to > be print the executable path and the pid of the offender Done, this is what I get after locking and unlocking: > kwin_wayland[2289]: "" 2652 wants an idle notification with too big timeout > 4294967295 2652 is powerdevil > $ ps -p 2652 -o command > COMMAND > /usr/lib/org_kde_powerdevil -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482077] Journal is flooded with "QObject::startTimer: Timers cannot have negative intervals"
https://bugs.kde.org/show_bug.cgi?id=482077 --- Comment #47 from Jonathan Lopes --- Created attachment 166711 --> https://bugs.kde.org/attachment.cgi?id=166711=edit Kwin IdleDetector breakpoint (In reply to Vlad Zahorodnii from comment #23) > Could you please add a breakpoint in KWin::IdleDetector::IdleDetector > constructor? I wonder who passes -1 timeout to the IdleDetector. There it is. I compiled kwin v6.0.1 from source and added a breakpoint on the constructor. I'll apply your patch and test it again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482077] Journal is flooded with "QObject::startTimer: Timers cannot have negative intervals"
https://bugs.kde.org/show_bug.cgi?id=482077 --- Comment #45 from Jonathan Lopes --- (In reply to Vlad Zahorodnii from comment #23) > Could you please add a breakpoint in KWin::IdleDetector::IdleDetector > constructor? I wonder who passes -1 timeout to the IdleDetector. I'll try to do this right now, give me a couple of minutes. (In reply to Vlad Zahorodnii from comment #32) > Can somebody share their ~/.config/powerdevilrc alongside with > ~/.config/kscreenlockerrc please? > cat ~/.config/kscreenlockerrc > [$Version] > update_info=kscreenlocker.upd:0.1-autolock > > [Daemon] > Autolock=false > Timeout=20 > cat ~/.config/powerdevilrc > [AC][Display] > DimDisplayWhenIdle=false > TurnOffDisplayWhenIdle=false > > [AC][SuspendAndShutdown] > AutoSuspendAction=0 > PowerButtonAction=0 > > [BatteryManagement] > BatteryCriticalAction=1 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 482267] Startup slow with Picture of the day (bing)
https://bugs.kde.org/show_bug.cgi?id=482267 Jonathan Villemaire-Krajden changed: What|Removed |Added CC||jonathan+...@j-vk.com --- Comment #1 from Jonathan Villemaire-Krajden --- I have the same issue with the NASA picture of the day when it's not loaded yet (eg first boot in the morning). It takes a few seconds to startup during which it's stuck on the splash screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482077] Journal is flooded with "QObject::startTimer: Timers cannot have negative intervals"
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #22 from Jonathan Lopes ---
Created attachment 14
--> https://bugs.kde.org/attachment.cgi?id=14=edit
gdb output from QObject::startTimer breakpoint
(In reply to Dāvis from comment #21)
> Created attachment 166630 [details]
> kwin_wayland
>
> (In reply to Jonathan Lopes from comment #16)
> > [...]
> > If I had enough time, I could try to plug a debugger on kwin_wayland to find
> > what is causing this problem. However, I have basically zero experience with
> > C++ debugging (although I can figure out with basic directions), so even if
> > I find some time to do it, I don't even know where to start.
>
> It's described in
> https://community.kde.org/KWin/Debugging#TL;DR_for_bug_reporters
> But I think "continue" there is wrong, atleast that didn't work for me, but
> this worked fine
> $ sudo -E gdb -pid (pidof kwin_wayland) -batch -ex "thread apply all
> backtrace"
I should've read the documentation first, would've saved me a lot of time, but
there it is, I've attached the backtrace from two calls to QObject::startTimer
with a negative interval, both points to the same location:
> #0 QObject::startTimer
> (this=0x58f34afb5dc0, interval=std::chrono::duration = { -1ms },
> timerType=Qt::CoarseTimer)
> at
> /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobject.cpp:1883
> #1 0x77a34d9991f7 in QTimer::start (this=0x58f34afb5dc0)
> at
> /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qtimer.cpp:192
> #2 0x77a3502041ee in KWin::IdleDetector::activity (this=0x58f34bc25920)
> at /usr/src/debug/kwin/kwin-6.0.1/src/idledetector.cpp:53
> #3 KWin::IdleDetector::activity (this=0x58f34bc25920)
> at /usr/src/debug/kwin/kwin-6.0.1/src/idledetector.cpp:50
> #4 0x77a35021636d in KWin::InputRedirection::simulateUserActivity
> (this=)
> at /usr/src/debug/kwin/kwin-6.0.1/src/input.cpp:3235
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 482077] Journal is flooded with "QObject::startTimer: Timers cannot have negative intervals"
https://bugs.kde.org/show_bug.cgi?id=482077 --- Comment #17 from Jonathan Lopes --- Just to let you know, 6.0.1 has just hit Arch Linux's stable repositories today, but the problem is still reproducible. > Operating System: Arch Linux > KDE Plasma Version: 6.0.1 > KDE Frameworks Version: 6.0.0 > Qt Version: 6.6.2 > Kernel Version: 6.7.8-arch1-1 (64-bit) > Graphics Platform: Wayland > Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor > Memory: 62,7 GiB of RAM > Graphics Processor: AMD Radeon RX 6800 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482077] Journal is flooded with "QObject::startTimer: Timers cannot have negative intervals"
https://bugs.kde.org/show_bug.cgi?id=482077 --- Comment #16 from Jonathan Lopes --- (In reply to alex from comment #14) > (In reply to Jonathan Lopes from comment #11) > > So, to make it happen, just lock the screen and move your mouse on the lock > > screen, then unlock > > That is not enough for me. I can reproduce only by suspending and waking up > my laptop. > Also, killing the kwin_wayland process helps only until the next suspend. It seems that the behaviour is very inconsistent across systems. I've just made a clean installation of NixOS Unstable on my Laptop with KDE Plasma 6, and I cannot reproduce it there, only on my Arch Linux machine. For now, I'm just restraining myself from locking my computer unless it's absolutely necessary. I don't have any power saving feature enabled, so it'll never sleep or lock the screen automatically. I've been running it for 2 days straight without locking or sleeping and the problem did not manifest. (In reply to Nate Graham from comment #13) > Cannot reproduce that on my all-Intel hardware, FWIW. My laptop is a full Intel machine as well, and it doesn't happen there, but I'm afraid that this is something else. Since my Intel machine has a clean installation of NixOS that I just did this weekend, there are virtually zero things to interact with Plasma 6 that could be the main cause of this (it's only Plasma 6, kf6, Firefox and neovim). If I had enough time, I could try to plug a debugger on kwin_wayland to find what is causing this problem. However, I have basically zero experience with C++ debugging (although I can figure out with basic directions), so even if I find some time to do it, I don't even know where to start. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482050] kile did not start
https://bugs.kde.org/show_bug.cgi?id=482050 Jonathan Riddell changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #5 from Jonathan Riddell --- Unfortunately the Kile developers say it's not ready yet so there is no currently supported release -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482431] knetwalk can`t be start
https://bugs.kde.org/show_bug.cgi?id=482431 --- Comment #1 from Jonathan Riddell --- Similarly this works for me on newly installed and upgraded systems. Do other apps work? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482430] systemsetings can`t be start
https://bugs.kde.org/show_bug.cgi?id=482430 --- Comment #1 from Jonathan Riddell --- This does work on a newly installed system and on upgraded systems I've tried so it suggests something is missing from your install. Do you have neon-desktop package installed? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482244] libkchart5-2 repeatedly fails to install.
https://bugs.kde.org/show_bug.cgi?id=482244 Jonathan Riddell changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Jonathan Riddell --- thanks for helping -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482417] here I collected several bugs
https://bugs.kde.org/show_bug.cgi?id=482417 Jonathan Riddell changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Jonathan Riddell --- I'm afraid this isn't a useful bug report. Issues need to be filed separately with a text description of the problem and how to recreate it and the expected outcome, in English, with any screenshots and videos also in English -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482050] kile did not start
https://bugs.kde.org/show_bug.cgi?id=482050 --- Comment #4 from Jonathan Riddell --- Unfortunately Kile hasn't had a stable release in many years and even the latest unstable release is 2 years old. However looking at Git the app does seem to have some development ongoing so I'll enquire about that. Otherwise it should be declared unsupported by KDE as there is not currently a release that builds or runs. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 482015] Kup-backup tray icon not enabled in the tray - disappeared from tray settings
https://bugs.kde.org/show_bug.cgi?id=482015 Jonathan Meek changed: What|Removed |Added CC||jonathan.l.m...@gmail.com --- Comment #4 from Jonathan Meek --- Exact same issue. Is there a way to manually trigger backups from the command line as a workaround? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482077] Journal is flooded with "QObject::startTimer: Timers cannot have negative intervals"
https://bugs.kde.org/show_bug.cgi?id=482077 --- Comment #12 from Jonathan Lopes --- (In reply to Jonathan Lopes from comment #11) > I found a way to reliably reproduce it, and a way to reliably stop it from > happening (although not an ideal one). > > So, to make it happen, just lock the screen and move your mouse on the lock > screen, then unlock. That's it. Now you have the journalctl flooded with > this message. > > And how to reliably stop it until the next boot? > > > kill -9 $PID > > Whereas $PID is the pid of the process causing the flood in the first place, > so in my case I see this in my journal: > > > kwin_wayland[2296]: QObject::startTimer: Timers cannot have negative > > intervals > > I run: > > > kill -9 2296 > > That's all. It'll not happen ever again until the next boot, you can lock > and unlock freely. I tried to compare the processes open before and after > killing kwin_wayland, but I didn't find anything relevant, other than kded5 > in my case, I'll uninstall kded5 and try again, but I doubt it is the root > cause. I forgot to mention, this will kill your entire kwin session, if you gonna do it, do right after booting the system, otherwise anything that's open, will be gone. On the matter of kded5, I uninstalled it and tried again, still the same problem, but killing kwin solved it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482077] Journal is flooded with "QObject::startTimer: Timers cannot have negative intervals"
https://bugs.kde.org/show_bug.cgi?id=482077 --- Comment #11 from Jonathan Lopes --- I found a way to reliably reproduce it, and a way to reliably stop it from happening (although not an ideal one). So, to make it happen, just lock the screen and move your mouse on the lock screen, then unlock. That's it. Now you have the journalctl flooded with this message. And how to reliably stop it until the next boot? > kill -9 $PID Whereas $PID is the pid of the process causing the flood in the first place, so in my case I see this in my journal: > kwin_wayland[2296]: QObject::startTimer: Timers cannot have negative intervals I run: > kill -9 2296 That's all. It'll not happen ever again until the next boot, you can lock and unlock freely. I tried to compare the processes open before and after killing kwin_wayland, but I didn't find anything relevant, other than kded5 in my case, I'll uninstall kded5 and try again, but I doubt it is the root cause. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482077] Journal is flooded with "QObject::startTimer: Timers cannot have negative intervals"
https://bugs.kde.org/show_bug.cgi?id=482077 --- Comment #9 from Jonathan Lopes --- I just did a test, I disabled Power Saving on my mouse and keyboard, left my machine idling for an hour, connected through SSH and checked journalctl, no messages there. I then proceed to unlock it and check journalctl again, and there it is, flooded with the messages, but no openrazer logs interleaving this time: > kwin_wayland[2296]: QObject::startTimer: Timers cannot have negative intervals > kwin_wayland[2296]: QObject::startTimer: Timers cannot have negative intervals > kwin_wayland[2296]: QObject::startTimer: Timers cannot have negative intervals > kwin_wayland[2296]: QObject::startTimer: Timers cannot have negative intervals > kwin_wayland[2296]: QObject::startTimer: Timers cannot have negative intervals > kwin_wayland[2296]: QObject::startTimer: Timers cannot have negative intervals > systemd[1]: Starting Fingerprint Authentication Daemon... > kwin_wayland[2296]: QObject::startTimer: Timers cannot have negative intervals > kwin_wayland[2296]: QObject::startTimer: Timers cannot have negative intervals > kwin_wayland[2296]: QObject::startTimer: Timers cannot have negative intervals > kwin_wayland[2296]: QObject::startTimer: Timers cannot have negative intervals > kwin_wayland[2296]: QObject::startTimer: Timers cannot have negative intervals > kwin_wayland[2296]: QObject::startTimer: Timers cannot have negative intervals > kwin_wayland[2296]: QObject::startTimer: Timers cannot have negative intervals > kwin_wayland[2296]: QObject::startTimer: Timers cannot have negative intervals So the problem lies on something going to “idle” mode (or something like that), and then being restored back when Plasma is unlocked. The openrazer log being there was just a coincidence. Sadly, this log message does not tell much, I'm trying to find on KDE sources, but it's a lot to look into. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482077] Journal is flooded with "QObject::startTimer: Timers cannot have negative intervals"
https://bugs.kde.org/show_bug.cgi?id=482077 Jonathan Lopes changed: What|Removed |Added CC||joniwe...@gmail.com --- Comment #6 from Jonathan Lopes --- I'm experiencing the same on Arch Linux. Something that I noticed is that it happens everytime my Razer devices resumes from Power Saving mode: This is the log from journalctl -b -3: > kwin_wayland[2751]: QObject::startTimer: Timers cannot have negative intervals > openrazer-daemon[2346]: 2024-02-29 11:24:04 | razer.device0 > | INFO | Resuming RazerHuntsmanElite > kwin_wayland[2751]: QObject::startTimer: Timers cannot have negative intervals > openrazer-daemon[2346]: 2024-02-29 11:24:04 | razer.device0 > | INFO | Putting device back into driver mode. > openrazer-daemon[2346]: 2024-02-29 11:24:04 | razer.device1 > | INFO | Resuming RazerNagaProWireless > kwin_wayland[2751]: QObject::startTimer: Timers cannot have negative intervals > kernel: razermouse: Command timed out. status: 04 transaction_id.id: 1f > remaining_packets: 00 protocol_type: 00 data_size: 03, command_class: 0f, > command_id.id: 04 Params: 0100bf00 . > kernel: razermouse: Command timed out. status: 04 transaction_id.id: 1f > remaining_packets: 00 protocol_type: 00 data_size: 03, command_class: 0f, > command_id.id: 04 Params: 0104bf00 . > kscreenlocker_greet[957590]: qt.qpa.wayland: Could not create EGL surface > (EGL error 0x3000) > kscreenlocker_greet[957590]: qt.qpa.wayland: Could not create EGL surface > (EGL error 0x3000) > kernel: razermouse: Command timed out. status: 04 transaction_id.id: 1f > remaining_packets: 00 protocol_type: 00 data_size: 03, command_class: 0f, > command_id.id: 04 Params: 0101bf00 . > kscreenlocker_greet[957590]: qt.qpa.wayland: Could not create EGL surface > (EGL error 0x3000) > kscreenlocker_greet[957590]: Failed to write to the pipe: Bad file descriptor. > kwin_wayland[2751]: QObject::startTimer: Timers cannot have negative intervals Then again on journalctl -b -2: > kwin_wayland[5005]: QObject::startTimer: Timers cannot have negative intervals > kwin_wayland[5005]: QObject::startTimer: Timers cannot have negative intervals > kwin_wayland[5005]: QObject::startTimer: Timers cannot have negative intervals > openrazer-daemon[4602]: 2024-02-29 19:08:35 | razer.device0 > | INFO | Resuming RazerHuntsmanElite > kwin_wayland[5005]: QObject::startTimer: Timers cannot have negative intervals > kscreenlocker_greet[491184]: qt.qpa.wayland: Could not create EGL surface > (EGL error 0x3000) > openrazer-daemon[4602]: 2024-02-29 19:08:35 | razer.device0 > | INFO | Putting device back into driver mode. > openrazer-daemon[4602]: 2024-02-29 19:08:35 | razer.device1 > | INFO | Resuming RazerNagaProWireless > kscreenlocker_greet[491184]: qt.qpa.wayland: Could not create EGL surface > (EGL error 0x3000) > kscreenlocker_greet[491184]: qt.qpa.wayland: Could not create EGL surface > (EGL error 0x3000) > kwin_wayland[5005]: QObject::startTimer: Timers cannot have negative intervals > kernel: razermouse: Command timed out. status: 04 transaction_id.id: 1f > remaining_packets: 00 protocol_type: 00 data_size: 03, command_class: 0f, > command_id.id: 04 Params: 0100bf00 . > kscreenlocker_greet[491184]: Failed to write to the pipe: Bad file descriptor. > kernel: razermouse: Command timed out. status: 04 transaction_id.id: 1f > remaining_packets: 00 protocol_type: 00 data_size: 03, command_class: 0f, > command_id.id: 04 Params: 0104bf00 . > kwin_wayland[5005]: QObject::startTimer: Timers cannot have negative intervals > kernel: razermouse: Command timed out. status: 04 transaction_id.id: 1f > remaining_packets: 00 protocol_type: 00 data_size: 03, command_class: 0f, > command_id.id: 04 Params: 0101bf00 . > kwin_wayland[5005]: QObject::startTimer: Timers cannot have negative intervals > kwin_wayland[5005]: QObject::startTimer: Timers cannot have negative intervals > kwin_wayland[5005]: QObject::startTimer: Timers cannot have negative intervals > kwin_wayland[5005]: QObject::startTimer: Timers cannot have negative intervals > kwin_wayland[5005]: QObject::startTimer: Timers cannot have negative intervals On “journalctl -b -1” it didn't happened because I booted, updated and restarted. But now on -b0: > kwin_wayland[2318]: QObject::startTimer: Timers cannot have negative intervals > kwin_wayland[2318]: QObject::startTimer: Timers cannot have negative intervals &
[kate] [Bug 482206] Kate crashes when closing a tab with a Rust file (and Rust Analyzer LSP) via KRunner and Baloo
https://bugs.kde.org/show_bug.cgi?id=482206 --- Comment #2 from Jonathan Lopes --- Created attachment 166286 --> https://bugs.kde.org/attachment.cgi?id=166286=edit video reproducing the crash -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 482206] Kate crashes when closing a tab with a Rust file (and Rust Analyzer LSP) via KRunner and Baloo
https://bugs.kde.org/show_bug.cgi?id=482206 --- Comment #1 from Jonathan Lopes --- Created attachment 166285 --> https://bugs.kde.org/attachment.cgi?id=166285=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 482206] New: Kate crashes when closing a tab with a Rust file (and Rust Analyzer LSP) via KRunner and Baloo
https://bugs.kde.org/show_bug.cgi?id=482206 Bug ID: 482206 Summary: Kate crashes when closing a tab with a Rust file (and Rust Analyzer LSP) via KRunner and Baloo Classification: Applications Product: kate Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: joniwe...@gmail.com Target Milestone: --- Application: kate (24.02.0) Qt Version: 6.6.2 Frameworks Version: 6.0.0 Operating System: Linux 6.7.6-arch1-2 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.0.0 [CoredumpBackend] -- Information about the crash: I enabled Baloo indexing and wanted to try it out, so I searched for a text, more specifically "allow-hyphen", and pressed `Enter` on the first one that appeared. Kate launched but crashed after I tried to close the tab. I can see the following in the journal prior to its crash (after this is the core dump attached by Dr. Konqi): > systemd[1884]: Started Kate - Advanced Text Editor. > kate[554123]: kf.config.core: Watching absolute paths is not supported > "/usr/share/color-schemes/BreezeDark.colors" > kwin_wayland[2318]: kf.config.core: Watching absolute paths is not supported > "/usr/share/color-schemes/BreezeDark.colors" > baloorunner[554123]: KCrash: Application 'kate' crashing... > crashRecursionCounter = 2 After a couple of more tries and carefully redoing my steps, I found a way to reproduce 100% of the time on my end. Here's how: Have Rust Analyzer configured in Kate and open a random text file. In my case, I just created an empty file for the sake of simplicity, and left it unrelated to the project (outside the Rust project tree). > touch random-text-file Then open it, and with Kate still open, press Alt+F2 to bring KRunner and search for a text that is on a Rust project, then press `Enter` on the first result. As soon as Kate is brought to the foreground, try to close the tab, it'll crash. If it doesn't crash on the first attempt, try again with the same Kate instance running. I recorded a video reproducing this problem. With OBS running, I never managed to get on the first try, but I always got on the second one (guess you need perfect timing). It does not happen if there is no Kate instance running, and I also noticed that KRunner needs to be invoked twice to work sometimes, but this is beside the point. I'll try to upload the video after submitting the report. Things I tried: - Different Rust projects: still crashes. - Different LSPs: tried gopls and json, neither crashed. The crash can be reproduced every time. -- Backtrace (Reduced): #5 0x7a4b77893c6a in operator== (p2=..., p1=...) at /usr/include/qt6/QtCore/qshareddata.h:202 #7 0x7a4b79c2255f in DiagnosticsView::addMarks (item=0x6522898d68a0, doc=0x652288a02fd0, this=0x6522887f0570) at /usr/src/debug/kate/kate-24.02.0/apps/lib/diagnostics/diagnosticview.cpp:1044 #8 DiagnosticsView::addMarksRec (this=this@entry=0x6522887f0570, doc=doc@entry=0x652288a02fd0, item=0x6522898d68a0) at /usr/src/debug/kate/kate-24.02.0/apps/lib/diagnostics/diagnosticview.cpp:1088 #9 0x7a4b79c221aa in DiagnosticsView::addMarksRec (this=this@entry=0x6522887f0570, doc=doc@entry=0x652288a02fd0, item=) at /usr/src/debug/kate/kate-24.02.0/apps/lib/diagnostics/diagnosticview.cpp:1090 #10 0x7a4b79c221aa in DiagnosticsView::addMarksRec (this=this@entry=0x6522887f0570, doc=doc@entry=0x652288a02fd0, item=) at /usr/src/debug/kate/kate-24.02.0/apps/lib/diagnostics/diagnosticview.cpp:1090 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 481815] GPU mark as GPU 2 even with only one GPU
https://bugs.kde.org/show_bug.cgi?id=481815 --- Comment #11 from Jonathan Croteau-Dicaire --- Thank you, I now have a setup where I can code, compile and debug ksystemstats and the GPU plugin. I was thinking, maybe we should count graphics card based on vendor. Instead of counting GPU 1..2..3..X we could have AMD 1, NVIDIA 1, INTEL 1 etc. I don't think we should remove the number to keep things consistent with other sensor. This would help people that have an AMD+NVIDIA and INTEL+NVIDIA or INTEL+AMD better identify which GPU is witch. The only setup where it would change "nothing" is an AMD+AMD setup. We could maybe also use a sort based on pci port used to keep things consistent between reboot. This solution could be implemented without doing my other suggestion. I am not sure if I want to change the gpuId (I assume this is the string used by the monitor app to save witch gpu they report). In my case, this is because it broke when I changed my graphics card that I investigated what happened. But at the same time, we could argue that it is an udev issues and not a KDE one. But I also think that it doesn't make any sense to jump number in our numbering. So, I am asking for your feedback on these two suggestions and if we want to change the gpuId too. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 481815] GPU mark as GPU 2 even with only one GPU
https://bugs.kde.org/show_bug.cgi?id=481815 --- Comment #6 from Jonathan Croteau-Dicaire --- I found this merge request : https://github.com/dylanaraps/neofetch/issues/1646 for neofetch One person sent this suggestion : glxinfo -B | grep -Po '(?<=^OpenGL renderer string: ).*(?= \(.*\)$)' (https://github.com/dylanaraps/neofetch/issues/1646) On my side, it seems to return a reasonable GPU name (https://github.com/dylanaraps/neofetch/issues/1646), but I don't like the idea of relying on the output of a command to get the GPU name -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 481815] GPU mark as GPU 2 even with only one GPU
https://bugs.kde.org/show_bug.cgi?id=481815 --- Comment #5 from Jonathan Croteau-Dicaire --- I cloned the project on my desktop and compiled it. I see that there is three project kstatsviewer, ksystemstats and ksystemstatstest. If I want to investigate why my GPU got the name GPU 2 which one should I use (and with which argument) and do you have pointer or advice on how to set up my environment to investigate and understand why this is happening? ksystemstats seems to have a replace option that could be useful to redo the discovery phase of the sensor, I assume. But I prefer to have your advice before doing random things. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 481815] GPU mark as GPU 2 even with only one GPU
https://bugs.kde.org/show_bug.cgi?id=481815 --- Comment #4 from Jonathan Croteau-Dicaire --- I think I found something interesting The return of the command : `kstatsviewer --list | grep gpu` ``` gpu/all/usage All GPUs Usage gpu/gpu1/power1 GPU 2 PPT gpu/gpu1/totalVram GPU 2 Total Video Memory gpu/gpu1/temp2 GPU 2 junction gpu GPU gpu/gpu1/usage GPU 2 Usage gpu/all/usedVram All GPUs Used Memory gpu/gpu1 GPU 2 gpu/gpu1/usedVram GPU 2 Video Memory Used gpu/gpu1/temperature GPU 2 Temperature gpu/all/totalVram All GPUs Total Memory gpu/gpu1/memoryFrequency GPU 2 Memory Frequency gpu/gpu1/in0 GPU 2 vddgfx gpu/gpu1/power GPU 2 Power gpu/all All GPUs gpu/gpu1/temp3 GPU 2 mem gpu/gpu1/coreFrequency GPU 2 Frequency gpu/gpu1/name GPU 2 Name gpu/gpu1/fan1 GPU 2 Fan 1 ``` It seems that the software is correctly detecting my gpu as gpu1, but giving it the name GPU 2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 481815] GPU mark as GPU 2 even with only one GPU
https://bugs.kde.org/show_bug.cgi?id=481815 --- Comment #3 from Jonathan Croteau-Dicaire --- (In reply to Arjen Hiemstra from comment #2) > So to a certain extent this is intentional: The GPU plugin uses the DRM > device number to determine what each device is. This is because of a > previous bug where just blindly iterating "/dev/drm/card*" resulted in cards > changing across reboots because the order wasn't necessarily fixed. See > https://invent.kde.org/plasma/ksystemstats/-/blob/master/plugins/gpu/ > LinuxBackend.cpp?ref_type=heads#L35 for the relevant code. The reason you > end up with card 2 is most likely that there's an iGPU as card 1 that we > don't support. That pretty strange. My CPU (Ryzen 7 3700X) doesn't have any iGPU and I removed my NVIDIA before adding the AMD GPU. I don't have a /dev/drm/ folder, but I got a /dev/dri/ folder. I only got card1 and renderD128 in it (and a by-path folder) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481903] stutter when framerate is lower than screen refresh
https://bugs.kde.org/show_bug.cgi?id=481903 --- Comment #4 from Jonathan Isom --- (In reply to Zamundaaa from comment #3) > While NVidia has a workaround for Wayland native apps, that workaround can > introduce some glitches as well. They're of a different sort though, so this > is a bit surprising. > I implemented an optimization for the NVidia driver just after 5.93.0 was > tagged, which might be relevant. Can you still reproduce this with 6.0.0? I have not been able to reproduce it in any wayland apps anymore. I am pretty sure that I was experiencing with a wayland app, but that one decided to stop doing it. All the other occurrences are Xwayland. Thank you for your time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481903] stutter when framerate is lower than screen refresh
https://bugs.kde.org/show_bug.cgi?id=481903 --- Comment #2 from Jonathan Isom --- (In reply to Zamundaaa from comment #1) > This is a NVidia driver bug, see > https://gitlab.freedesktop.org/xorg/xserver/-/issues/1317 for more details While I don't disagree about the Nvidia driver bug, I have been experiencing it with wayland apps as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481903] stutter when framerate is lower than screen refresh
https://bugs.kde.org/show_bug.cgi?id=481903 Jonathan Isom changed: What|Removed |Added Version|unspecified |5.93.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481903] New: stutter when framerate is lower than screen refresh
https://bugs.kde.org/show_bug.cgi?id=481903 Bug ID: 481903 Summary: stutter when framerate is lower than screen refresh Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: jei...@gmail.com Target Milestone: --- Created attachment 166141 --> https://bugs.kde.org/attachment.cgi?id=166141=edit Video of glxgears running SUMMARY I am experiencing a stutter or flicker that almost looks like it is re-showing prior frames. Experienced it in Yuzu, freetube and glxgears(when framelimited). When I tried to capture with Spectacle it didn't capture it in the recording. Attached from my phone. STEPS TO REPRODUCE 1. Run 'MANGOHUD_CONFIG="fps_limit=20" mangohud glxgears' OBSERVED RESULT flicker EXPECTED RESULT No flicker SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.7.6-273-tkg-linux-tkg (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4080/PCIe/SSE2 Product Name: X570M Pro4 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 481815] GPU mark as GPU 2 even with only one GPU
https://bugs.kde.org/show_bug.cgi?id=481815 --- Comment #1 from Jonathan Croteau-Dicaire --- I completely forgot to mention. I know my way around programming, I was a Qt developer at another job. So I don't necessary need someone else to do the patch. A pointer to what to look for (if this is a real issue and not some strange expected behaviour that I fail to understand) could help me make a patch if necessary. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481841] Discover reports printer KCM installed, but nowhere to be found in System Settings
https://bugs.kde.org/show_bug.cgi?id=481841 --- Comment #1 from Jonathan Riddell --- Do you have the package print-manager installed? -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 481815] New: GPU mark as GPU 2 even with only one GPU
https://bugs.kde.org/show_bug.cgi?id=481815 Bug ID: 481815 Summary: GPU mark as GPU 2 even with only one GPU Classification: Applications Product: plasma-systemmonitor Version: 5.27.10 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: jonathan.croteau.dica...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 166092 --> https://bugs.kde.org/attachment.cgi?id=166092=edit Sensor list with only GPU 2 SUMMARY I recently changed from an Nvidia (3070) to an AMD GPU (7900 XT). Now the plasma-systemmonitor and the widget see the new GPU as GPU 2 even if there is no GPU 1 present. I am not sure if this is a bug with my setup that would happen even without the fact that I had an Nvidia in this system before or a remnant of the Nvidia GPU. I don't think this is the correct behaviour and if there is only one GPU it should be marked as GPU 0 OBSERVED RESULT The only GPU in the sensor list is GPU 2 EXPECTED RESULT The only GPU in the sensor list should be GPU 0 SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.6-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: A520M DS3H AC -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481720] Could not delete /home/mine/��� .
https://bugs.kde.org/show_bug.cgi?id=481720 Jonathan Marten changed: What|Removed |Added CC||j...@keelhaul.me.uk --- Comment #1 from Jonathan Marten --- Is this the problem of not being able to handle file names that are not valid UTF-8, bug 165044? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 423035] Turn off screen shortcut turns the screen back on automatically
https://bugs.kde.org/show_bug.cgi?id=423035 Jonathan Georgiou changed: What|Removed |Added CC||jonathangeorgiou94@proton.m ||e --- Comment #17 from Jonathan Georgiou --- I am experiencing this on Wayland on Fedora 39 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 QT Version: 5.15.12 Kernel version: 6.7.3-200.fc39x86_64 Graphics Platform: Wayland I get the issue both when assigning a shortcut through plasma settings and when running kscreen-doctor --dpms off, even if I add the reported sleep workaround. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480353] Cube effect not working on live ISO or after install
https://bugs.kde.org/show_bug.cgi?id=480353 Jonathan Riddell changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480704] BIG CRASH AFTER LATEST UPDATE IN TESTING EDITION - 2024-02-01
https://bugs.kde.org/show_bug.cgi?id=480704 --- Comment #32 from Jonathan Riddell --- Valter Mura: I'm afraid I'm unable to help here, I think your system has some dbgsym packages installed which are not well handled, try removing e.g. libkf5declarative5-dbgsym and the other pim 5 packages tagwerk19: any other issues? -- You are receiving this mail because: You are watching all bug changes.
