[systemsettings] [Bug 465752] System Settings crashes when launching Flatpak Permissions KCM
https://bugs.kde.org/show_bug.cgi?id=465752 Lemuel Simon changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DOWNSTREAM --- Comment #2 from Lemuel Simon --- (In reply to Nate Graham from comment #1) > Thank you for the bug report! Unfortunately the backtrace is incomplete and > missing debug symbols that we need to figure out exactly what's going wrong. > Could you please install debug symbols for flatpak-kcm and systemsettings, > reproduce the crash, and attach a new symbolicated backtrace? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports > > Thanks again! It turns out it was indeed a packaging issue. Force re-installing 'kcm_flatpak' fixed the crash. Closing the issue. Thanks Nate! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465752] New: System Settings crashes when launching Flatpak Permissions KCM
https://bugs.kde.org/show_bug.cgi?id=465752 Bug ID: 465752 Summary: System Settings crashes when launching Flatpak Permissions KCM Classification: Applications Product: systemsettings Version: 5.27.0 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lemuelsimo...@protonmail.com Target Milestone: --- Application: systemsettings (5.27.0) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.10-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.0 [KCrashBackend] -- Information about the crash: This problem comes with the addition of the Flapak Permissions KCM, that came with the Plasma 5.27 update. When searching for the KCM in KRunner or System Settings, the icon is broken/missing. Selecting the Flatpak KCM will immediately crash System Settings. Running it in the terminal doesn't give much info as to what went wrong either. I want to assume it is a packaging issue, but I'm not seeing anything obvious in the package spec files. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7f76548a8640 in flatpak_installation_list_installed_refs_by_kind () from /lib64/libflatpak.so.0 #5 0x7f7654939338 in ?? () from /usr/lib64/qt5/plugins/plasma/kcms/systemsettings/kcm_flatpak.so #6 0x7f765493a2de in ?? () from /usr/lib64/qt5/plugins/plasma/kcms/systemsettings/kcm_flatpak.so #7 0x7f768b8004e8 in KPluginFactory::create(char const*, QWidget*, QObject*, QList const&, QString const&) () from /lib64/libKF5CoreAddons.so.5 #8 0x7f768b76df59 in KCModuleLoader::loadModule(KPluginMetaData const&, QWidget*, QList const&) () from /lib64/libKF5KCMUtils.so.5 #9 0x7f768b77127d in ?? () from /lib64/libKF5KCMUtils.so.5 #10 0x7f768b7718a8 in KCModuleProxy::realModule() const () from /lib64/libKF5KCMUtils.so.5 #11 0x7f768bf4d080 in ModuleView::updatePageIconHeader(KPageWidgetItem*) () from /lib64/libsystemsettingsview.so.3 #12 0x7f768bf5050a in ModuleView::addModule(MenuItem*, QStringList const&) () from /lib64/libsystemsettingsview.so.3 #13 0x7f765a92c1d9 in ?? () from /usr/lib64/qt5/plugins/systemsettingsview/systemsettings_sidebar_mode.so #14 0x7f765a92eef1 in ?? () from /usr/lib64/qt5/plugins/systemsettingsview/systemsettings_sidebar_mode.so #15 0x7f765a92f883 in ?? () from /usr/lib64/qt5/plugins/systemsettingsview/systemsettings_sidebar_mode.so #16 0x7f76882de3a3 in QQmlObjectOrGadget::metacall (this=this@entry=0x7fffa71ba640, type=type@entry=QMetaObject::InvokeMetaMethod, index=, index@entry=27, argv=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/qml/qml/qqmlobjectorgadget.cpp:51 #17 0x7f76881bb799 in CallMethod (callType=, callArgs=0x2, engine=, argTypes=, argCount=, returnType=, index=, object=...) at /usr/include/qt5/QtCore/qvarlengtharray.h:189 #18 CallPrecise (object=..., data=..., engine=engine@entry=0x564671da4aa0, callArgs=callArgs@entry=0x7f765622b5b8, callType=callType@entry=QMetaObject::InvokeMetaMethod) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/qml/jsruntime/qv4qobjectwrapper.cpp:1553 #19 0x7f76881bd3fb in CallOverloaded (callType=, propertyCache=, callArgs=, engine=, data=..., object=...) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/qml/jsruntime/qv4qobjectwrapper.cpp:1629 #20 QV4::QObjectMethod::callInternal (this=, thisObject=, argv=, argc=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/qml/jsruntime/qv4qobjectwrapper.cpp:2117 #21 0x7f76881d9e86 in QV4::FunctionObject::call (argc=, argv=, thisObject=, this=) at ../../include/QtQml/5.15.8/QtQml/private/../../../../../../src/qml/jsruntime/qv4functionobject_p.h:202 #22 QV4::Moth::VME::interpret (frame=0x7f7654911168, engine=0x564671da4aa0, code=0x5646722c7b60 "\340\206\024\210v\177") at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/qml/jsruntime/qv4vme_moth.cpp:757 #23 0x7f76881dd5cf in QV4::Moth::VME::exec (frame=frame@entry=0x7fffa71ba900, engine=engine@entry=0x564671da4aa0) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/qml/jsruntime/qv4vme_moth.cpp:466 #24 0x7f768817050e in QV4::Function::call (this=this@entry=0x564671e0c820, thisObject=, argv=argv@entry=0x7f765622b500, argc=, context=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/qml/jsruntime/qv4function.cpp:69 #25 0x7f76882f8b5d in QQmlJavaScriptExpression::evaluate (this=this@entry=0x564672eb5be0, callData=callData@entry=0x7f765622b4d0, isUndefined=isUndefined@entry=0x0) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/qml/qml/qqmljavascriptexpression.cpp:212 #26
[kio-extras] [Bug 457532] Stop generating thumbnails for broken/incomplete files
https://bugs.kde.org/show_bug.cgi?id=457532 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 461225] [Feature Request] Ability to generate a shortcut of a file/folder, in the Desktop folder.
https://bugs.kde.org/show_bug.cgi?id=461225 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 461225] New: [Feature Request] Ability to generate a shortcut of a file/folder, in the Desktop folder.
https://bugs.kde.org/show_bug.cgi?id=461225 Bug ID: 461225 Summary: [Feature Request] Ability to generate a shortcut of a file/folder, in the Desktop folder. Classification: Applications Product: dolphin Version: 22.08.2 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: lemuelsimo...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 153345 --> https://bugs.kde.org/attachment.cgi?id=153345=edit Windows Explorer, shortcut to desktop. SUMMARY This feature is basically a rip-off of an ability Windows Explorer has: being able to create a shortcut of a file or folder, on the Desktop. I think it would be a neat addition to folks that have desktop icons enabled, and to Windows refugees (done in part by the Steam Deck). Symlinks already do the job well, but it isn't as intuitive as 'Right-click > Copy to > Copy to Desktop (Shortcut)'. There's also a third-party service by Intika that allows this: https://store.kde.org/p/1290373 . SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.14.21-150400.24.21-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 Manufacturer: LENOVO Product Name: 2347G2U System Version: ThinkPad T430 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 456356] Cannot right-click and run executable file; there's no "Open/Launch/Execute" menu item
https://bugs.kde.org/show_bug.cgi?id=456356 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460909] The Network Widget would forget text sensors at random, at launch.
https://bugs.kde.org/show_bug.cgi?id=460909 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460909] New: The Network Widget would forget text sensors at random, at launch.
https://bugs.kde.org/show_bug.cgi?id=460909 Bug ID: 460909 Summary: The Network Widget would forget text sensors at random, at launch. Classification: Plasma Product: plasmashell Version: 5.26.1 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: lemuelsimo...@protonmail.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 SUMMARY Sometimes when Plasmashell starts up, the System Monitor Network Widget (desktop) would load without the text-only sensors. In this case, Upload/Download are the line chart sensors, and SSID/IPv4 Address are the Text-Only sensors. Plasmashell would 'forget' that those Text-Only sensors were selected. Configuring the widget doesn't work either, as re-selecting the missing Text-Only sensors and clicking 'Apply' doesn't add them back to the widget. They are only restored once Plasmashell is restarted. STEPS TO REPRODUCE 1. Login/Start Plasma 2. Add Network Widget to desktop. 3. Add Text-only sensors to the Network Widget. 4. Log out and back in. OBSERVED RESULT Sometimes when Plasma starts, the selected Text-Only sensors in the System Monitor widget do not show. EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.14.21-150400.24.21-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 Manufacturer: LENOVO Product Name: 2347G2U System Version: ThinkPad T430 ADDITIONAL INFORMATION I want to say that this is a regression, as I've only seen this bug happen when I upgraded to 5.26. I didn't report it when I found the bug in the beta, as my build wasn't from the git. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 460899] KRunner plugins do not use user-defined keywords.
https://bugs.kde.org/show_bug.cgi?id=460899 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 460899] New: KRunner plugins do not use user-defined keywords.
https://bugs.kde.org/show_bug.cgi?id=460899 Bug ID: 460899 Summary: KRunner plugins do not use user-defined keywords. Classification: Plasma Product: krunner Version: 5.26.1 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lemuelsimo...@protonmail.com CC: alexander.loh...@gmx.de Target Milestone: --- SUMMARY KRunner does not use any of the user-defined keywords to trigger specific searches with a given plugin. It always uses the default setting, even after restarting Plasma or KRunner. STEPS TO REPRODUCE 1. Go to System Settings 2. Go to Plasma Search 3. Find any plugin with custom keyword support (only Dictionary, Terminate Applications and Spell Checking plugins were tested). 4. Change the keyword/trigger word. 5. Apply changes and try a keyword in KRunner via the Kickoff or plain KRunner. OBSERVED RESULT None of the plugins will use the user-defined keywords. EXPECTED RESULT The custom keywords would trigger a specific plugin. Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.14.21-150400.24.21-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 Manufacturer: LENOVO Product Name: 2347G2U System Version: ThinkPad T430 ADDITIONAL INFORMATION I've tried these keywords: Terminate Applications: !k, !t, die, k, t Dictionary: !d, !def, def Spell Checking: !sp, sp This problem is not very new, as I've had it since 5.24.1...I'm somewhat lazy when it comes to bug reports. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459363] System Monitor widget does not refresh/display IP address on system wake.
https://bugs.kde.org/show_bug.cgi?id=459363 Lemuel Simon changed: What|Removed |Added Version|5.25.90 |5.26.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459363] System Monitor widget does not refresh/display IP address on system wake.
https://bugs.kde.org/show_bug.cgi?id=459363
--- Comment #2 from Lemuel Simon ---
I'm sure a dumb-fire solution can be used.
Like have the SSID and IP{4,6} labels refresh by time intervals like the other
stats.
I'm not sure how expensive it would be though.
--
You are receiving this mail because:
You are watching all bug changes.
[NeoChat] [Bug 460830] Neochat crashes while logging in for the first time.
https://bugs.kde.org/show_bug.cgi?id=460830 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 460830] Neochat crashes while logging in for the first time.
https://bugs.kde.org/show_bug.cgi?id=460830 Lemuel Simon changed: What|Removed |Added Summary|Neochat crashes while |Neochat crashes while |loggin in for the first |logging in for the first |time. |time. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 460830] New: Neochat crashes while loggin in for the first time.
https://bugs.kde.org/show_bug.cgi?id=460830 Bug ID: 460830 Summary: Neochat crashes while loggin in for the first time. Classification: Applications Product: NeoChat Version: unspecified Platform: OpenSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: lemuelsimo...@protonmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: neochat (22.09) Qt Version: 5.15.6 Frameworks Version: 5.99.0 Operating System: Linux 5.14.21-150400.24.21-default x86_64 Windowing System: X11 Distribution: "openSUSE Leap 15.4" DrKonqi: 5.26.1 [KCrashBackend] -- Information about the crash: Neochat would crash immediately after the user enters the password to their Matrix account, within the 'Login' setup page. It is reproducable on every run. There are no issues in my Matrix account, as I can login with the Element online client just fine. According to Element's 'Security and Privacy' settings category, Neochat DOES indeed show-up as a logged-in device. However, as mentioned before, it always crashes before it can show anything. The crash can be reproduced every time. -- Backtrace: Application: NeoChat (neochat), signal: Segmentation fault [KCrash Handler] #4 0x7fb8870dfc21 in Quotient::GetNotificationsJob::GetNotificationsJob(QString const&, Quotient::Omittable, QString const&) () from /usr/lib64/libQuotient.so.0.6 #5 0x004b66cc in Quotient::Connection::callApi (runningPolicy=Quotient::ForegroundRequest, this=0x2b0e660) at /usr/include/Quotient/connection.h:438 #6 Quotient::Connection::callApi (this=0x2b0e660) at /usr/include/Quotient/connection.h:450 #7 RoomListModel::handleNotifications (this=this@entry=0x7ffc8f160d00) at /usr/src/debug/neochat-22.09-lp154.25.2.x86_64/src/roomlistmodel.cpp:207 #8 0x004b7a11 in RoomListModel::setConnection (this=0x7ffc8f160d00, connection=0x2b0e660) at /usr/src/debug/neochat-22.09-lp154.25.2.x86_64/src/roomlistmodel.cpp:121 #9 0x7fb88382a7fb in QtPrivate::QSlotObjectBase::call (a=0x7ffc8f15fbd0, r=0x7ffc8f160cc0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #10 doActivate (sender=0x753240 , signal_index=14, argv=0x7ffc8f15fbd0) at kernel/qobject.cpp:3919 #11 0x7fb883823c72 in QMetaObject::activate (sender=, m=m@entry=0x74ff80 , local_signal_index=local_signal_index@entry=11, argv=argv@entry=0x0) at kernel/qobject.cpp:3979 #12 0x0048dc53 in Controller::activeConnectionChanged (this=) at /usr/src/debug/neochat-22.09-lp154.25.2.x86_64/build/src/neochat_autogen/EWIEGA46WW/moc_controller.cpp:741 #13 0x0049ea79 in Controller::setActiveConnection (this=, connection=) at /usr/src/debug/neochat-22.09-lp154.25.2.x86_64/src/controller.cpp:595 #14 0x0049f6ed in operator() (__closure=0x1adc580) at /usr/src/debug/neochat-22.09-lp154.25.2.x86_64/src/controller.cpp:293 #15 QtPrivate::FunctorCall, QtPrivate::List<>, void, Controller::invokeLogin() >::call (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #16 QtPrivate::Functor::, 0>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #17 QtPrivate::QFunctorSlotObject::, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x1adc570, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #18 0x7fb88382a7fb in QtPrivate::QSlotObjectBase::call (a=0x7ffc8f15fd60, r=0x753240 , this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #19 doActivate (sender=0x2b0e660, signal_index=8, argv=0x7ffc8f15fd60) at kernel/qobject.cpp:3919 #20 0x7fb887050a42 in Quotient::Connection::Private::completeSetup(QString const&) () from /usr/lib64/libQuotient.so.0.6 #21 0x7fb887050b54 in ?? () from /usr/lib64/libQuotient.so.0.6 #22 0x7fb887057e70 in Quotient::Connection::Private::checkAndConnect(QString const&, std::function const&, std::optional const&) () from /usr/lib64/libQuotient.so.0.6 #23 0x7fb887058b77 in Quotient::Connection::assumeIdentity(QString const&, QString const&, QString const&) () from /usr/lib64/libQuotient.so.0.6 #24 0x004a103e in operator() (__closure=) at /usr/src/debug/neochat-22.09-lp154.25.2.x86_64/src/controller.cpp:310 #25 QtPrivate::FunctorCall, QtPrivate::List, void, Controller::invokeLogin():: >::call (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #26 QtPrivate::Functor, 1>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #27 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #28 0x7fb88382a7fb in QtPrivate::QSlotObjectBase::call
[kdeconnect] [Bug 457436] Kde Connect crash when receiving message on my phone
https://bugs.kde.org/show_bug.cgi?id=457436 --- Comment #2 from Lemuel Simon --- Created attachment 152906 --> https://bugs.kde.org/attachment.cgi?id=152906=edit New crash information added by DrKonqi kdeconnectd (22.08.2) using Qt 5.15.6 The crash usually occurs if I reboot my phone, of if the phone re-connects to the same Wi-Fi network of my laptop. It happens fairly often as well, for as long as I've been using KDE Connect (~2 years). I'm only now reporting this as Dr. Konqi back then would refuse to obtain crash information from daemons spawned by 'kded' or 'kinit' (...forgot the name of it.) -- Backtrace (Reduced): #6 0x7fd843e4861b in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=this@entry=0x7fd8028646e0, msg=msg@entry=0x7fd846254798 "Fatal Error: Got cmd %d, while waiting for an answer!") at global/qlogging.cpp:893 #8 0x7fd84618ffca in KIO::SlaveBase::waitForAnswer (this=this@entry=0x7fd7fc004e20, expected1=expected1@entry=84, expected2=expected2@entry=65, data=..., pCmd=pCmd@entry=0x7fd802864754) at /usr/src/debug/kio-5.99.0-lp154.364.1.x86_64/src/core/slavebase.cpp:1121 #9 0x7fd846191b95 in KIO::SlaveBase::canResume (this=this@entry=0x7fd7fc004e20, offset=12288) at /usr/src/debug/kio-5.99.0-lp154.364.1.x86_64/src/core/slavebase.cpp:1088 #10 0x7fd802873654 in FileProtocol::put (this=0x7fd7fc004e10, url=..., _mode=-1, _flags=...) at /usr/src/debug/kio-5.99.0-lp154.364.1.x86_64/src/ioslaves/file/file.cpp:546 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 457436] Kde Connect crash when receiving message on my phone
https://bugs.kde.org/show_bug.cgi?id=457436 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457101] Application launcher + all panels (All plasmashell components) freeze upon typing characters into the launcher
https://bugs.kde.org/show_bug.cgi?id=457101 --- Comment #7 from Lemuel Simon --- (In reply to gregorystarr00 from comment #3) > (In reply to Lemuel Simon from comment #1) > > Hmm...so far, I can't reproduce the issue. This requires further > > investigation. > > > > There can be many reasons why the search function would behave like that. It > > could be hardware (slow & old HDD) or software (rouge KRunner plugin, > > Baloo(???)). Does searching in KRunner behave the same (ALT+F2)? If so, try > > disabling the file search plugins. Also, use a system-monitor like HTop or > > Ksysguard when trying to search again, to get an idea as to which > > application is abusing CPU or I/O. > > I'm running on a M.2 SSd, so I don't think it's hardware speed. I have Baloo > disabled because it was wreaking havoc on my system and using up massive > amounts of ram in the past - is that possibly a cause? Sorry for the late response. Disabling Baloo should render KRunner's file search useless. There has to be another cause. What CPU are using? Also, try disabling KRunner plugins and experiment. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457101] Application launcher + all panels (All plasmashell components) freeze upon typing characters into the launcher
https://bugs.kde.org/show_bug.cgi?id=457101 Lemuel Simon changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|WORKSFORME |--- --- Comment #6 from Lemuel Simon --- Re-opening as the user is still active and encounters this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459363] System Monitor widget does not refresh/display IP address on system wake.
https://bugs.kde.org/show_bug.cgi?id=459363 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m --- Comment #1 from Lemuel Simon --- (In reply to Lemuel Simon from comment #0) > The IP Address doesn't show up anymore, but the Network Name (SSID) does. Apparently, although the SSID shows, the network name isn't refreshed. It will show the name of the previous connection, before the system slept or hibernated. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459363] New: System Monitor widget does not refresh/display IP address on system wake.
https://bugs.kde.org/show_bug.cgi?id=459363 Bug ID: 459363 Summary: System Monitor widget does not refresh/display IP address on system wake. Classification: Unclassified Product: plasmashell Version: 5.25.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: lemuelsimo...@protonmail.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 Created attachment 152205 --> https://bugs.kde.org/attachment.cgi?id=152205=edit System Monitor widget doesn't display IP Address when system wakes from sleep. SUMMARY The text sensors of the System Monitor that displays any IP address (v4 or v6) will not refresh when the system wakes from sleep. On wake, the field will remain blank until the user manually triggers 'Edit Mode' and attempt to resize the widget. STEPS TO REPRODUCE 1. Have a System Monitor widget with any IP Address displaying text-sensor. 2. Put system to sleep. 3. Wake system. 4. Observe, that the IP Address no longer displays. OBSERVED RESULT The IP Address doesn't show up anymore, but the Network Name (SSID) does. The IP Address will re-appear if the user enters "Edit Mode" in Plasmashell and grabs the edge of the widget to resize it. EXPECTED RESULT The IP Address sensor would refresh normally on wake. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.5 Kernel Version: 5.14.21-150400.24.18-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 Manufacturer: LENOVO System Version: ThinkPad T430 ADDITIONAL INFORMATION This bug isn't a regression of the Plasma 5.26 beta, it existed in 5.25. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458156] Notification icon is tilted sometimes
https://bugs.kde.org/show_bug.cgi?id=458156 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m --- Comment #1 from Lemuel Simon --- Hi! Did this happen in a X11 session or a Wayland one? There are bugs specific to each session, so this info helps us narrow it down. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 457652] Yakuake crash when closing tab while moving mouse with Settings::focusFollowsMouse() == true
https://bugs.kde.org/show_bug.cgi?id=457652 Lemuel Simon changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #4 from Lemuel Simon --- (In reply to Stefan Siegel from comment #2) > Created attachment 151426 [details] > Video of yakuake crashing Ah... At first, it was hard to trigger on my end, but now I can do so consistently. Changing the bug status to confirmed, thanks for videos and screenshots! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457101] Application launcher + all panels (All plasmashell components) freeze upon typing characters into the launcher
https://bugs.kde.org/show_bug.cgi?id=457101 Lemuel Simon changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||lemuelsimo...@protonmail.co ||m --- Comment #1 from Lemuel Simon --- Hmm...so far, I can't reproduce the issue. This requires further investigation. There can be many reasons why the search function would behave like that. It could be hardware (slow & old HDD) or software (rouge KRunner plugin, Baloo(???)). Does searching in KRunner behave the same (ALT+F2)? If so, try disabling the file search plugins. Also, use a system-monitor like HTop or Ksysguard when trying to search again, to get an idea as to which application is abusing CPU or I/O. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 457652] Yakuake crash when closing tab while moving mouse with Settings::focusFollowsMouse() == true
https://bugs.kde.org/show_bug.cgi?id=457652 Lemuel Simon changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||lemuelsimo...@protonmail.co ||m --- Comment #1 from Lemuel Simon --- Hmm...I cannot seem to reproduce the crash. I've tried enabling and disabling the 'Focus Terminals when mouse pointer' and following the steps. Can you upload a tiny video of the bug in action? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457829] Ctrl + F do not work in System Settings - Desktop Effects
https://bugs.kde.org/show_bug.cgi?id=457829 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m --- Comment #1 from Lemuel Simon --- Hello! I've checked it myself. The cursor does indeed move to the search box, but although the search box 'looks' focused, it doesn't accept input. Can you confirm this? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457861] Wallpaper accent color sometimes has bad contrast on Breeze Dark.
https://bugs.kde.org/show_bug.cgi?id=457861 --- Comment #3 from Lemuel Simon --- Created attachment 151312 --> https://bugs.kde.org/attachment.cgi?id=151312=edit The worst one. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457861] Wallpaper accent color sometimes has bad contrast on Breeze Dark.
https://bugs.kde.org/show_bug.cgi?id=457861 --- Comment #2 from Lemuel Simon --- Created attachment 151311 --> https://bugs.kde.org/attachment.cgi?id=151311=edit Another sample. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457861] Wallpaper accent color sometimes has bad contrast on Breeze Dark.
https://bugs.kde.org/show_bug.cgi?id=457861 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m --- Comment #1 from Lemuel Simon --- Created attachment 151310 --> https://bugs.kde.org/attachment.cgi?id=151310=edit Sample wallpaper for bad contrast. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457861] New: Wallpaper accent color sometimes has bad contrast on Breeze Dark.
https://bugs.kde.org/show_bug.cgi?id=457861 Bug ID: 457861 Summary: Wallpaper accent color sometimes has bad contrast on Breeze Dark. Product: systemsettings Version: 5.25.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: lemuelsimo...@protonmail.com CC: noaha...@gmail.com, tantalising...@gmail.com, uhh...@gmail.com Target Milestone: --- Created attachment 151309 --> https://bugs.kde.org/attachment.cgi?id=151309=edit Poor contrast on the highlighed items. SUMMARY The current implementation of the wallpaper-generated accent color does not account for dark color schemes. Depending on the wallpaper, the automatically-chosen accent color may appear to dark to see. It would blend-into the background of the color theme, so highlighted/selected buttons/sliders are not legible in Plasma. The 'hyperlink text' that one would find in Spectacle, when you save a screenshot, would also be completely illegible. STEPS TO REPRODUCE 1. Select the default, unmodified Breeze Dark color theme or Global Theme. 2. Select the 'From Wallpaper' option in the Colors KCM. 3. Cycle to a dark wallpaper. 4. Open the Application Launcher (Kick-off) OBSERVED RESULT With the wallpaper's accent color applied on Breeze Dark, highlighted/selected buttons/sliders are not legible in Plasma, and "Hyperlink Text" is either too dark or invisible due to poor contrast. EXPECTED RESULT The accent colors are bright enough to stand-out, when using Breeze Dark or another similarly dark color-scheme. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.14.21-150400.24.18-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 Manufacturer: LENOVO Product Name: 2347G2U System Version: ThinkPad T430 ADDITIONAL INFORMATION I would submit a screenshot of the bug in action, as well as some of the offending wallpapers that trigger this behavior. Unfortunately, I couldn't get a screenshot of Spectacle, it hides before the shot. I have seen these two bug reports, but I don't believe they are the same to the current one. https://bugs.kde.org/show_bug.cgi?id=442820 https://bugs.kde.org/show_bug.cgi?id=445040 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457821] Blurry or Missing icons in Plasmashell upon icon theme change or app installation/removal.
https://bugs.kde.org/show_bug.cgi?id=457821 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m --- Comment #1 from Lemuel Simon --- Created attachment 151308 --> https://bugs.kde.org/attachment.cgi?id=151308=edit Switching icon theme triggers blurry/missing icon bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457821] New: Blurry or Missing icons in Plasmashell upon icon theme change or app installation/removal.
https://bugs.kde.org/show_bug.cgi?id=457821 Bug ID: 457821 Summary: Blurry or Missing icons in Plasmashell upon icon theme change or app installation/removal. Product: plasmashell Version: 5.25.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lemuelsimo...@protonmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY As the title reads, some icons throughout Plasma tend to be rendered blurry or missing entirely. This tends to happen when an application is installed/removed/updated or if the icon theme changes. Applying new accent colors via the wallpaper sometimes trigger this too (this is also considered a 'theme change'). The only way to rectify the problem is to manually restart plasmashell with "kquitapp5 plasmashell && kstart5 plasmashell > /dev/null 2>&1 || kstart5 plasmashell > /dev/null 2>&1", afterwards all icons show normally...until another application gets updated. I am using the Breeze Dark and "Redmond Dark with Square Highlights" by Paul Mc Auley, which inherits the Breeze Dark icons anyway. It is also reproducible with any other icon-theme I've tried. STEPS TO REPRODUCE 1. Start Plasma. 2. Change the icon theme in System Settings. 3. Open the Application Launcher (Kickoff) and find entries with missing icons scattered around. OBSERVED RESULT As the title reads, some icons throughout Plasma tend to be rendered blurry or missing entirely. EXPECTED RESULT All application icons show normally in Plasma's widgets and application menu (that's a widget...) SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.14.21-150400.24.11-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 ADDITIONAL INFORMATION Oddly enough, when the bug occurs, the same icons go missing almost every-time: Heimdall, AntiMicro, SpeedCrunch, RetroArch, XTerm, Zotero. These icons get blurry every-time when shown in categories in the Kicker (smaller icons): System Settings, Dolphin. The 'Battery and Brightness' widget has blurry icons in its notifications too. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 457532] New: Stop generating thumbnails for broken/incomplete files.
https://bugs.kde.org/show_bug.cgi?id=457532 Bug ID: 457532 Summary: Stop generating thumbnails for broken/incomplete files. Product: kio-extras Version: 22.04.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Thumbnails and previews Assignee: plasma-b...@kde.org Reporter: lemuelsimo...@protonmail.com Target Milestone: --- SUMMARY Currently, the generator will endlessly attempt to make thumbnails for pictures or videos that are corrupted or currently downloading. Downloading a video and looking at the file (while downloading) in Dolphin skyrockets CPU usage and abuses I/O bandwidth, making HDD users' system practically unusable unless they exit the program (Dolphin, File Picker,etc). Can a timeout be implemented as a safeguard? STEPS TO REPRODUCE 1. Open Dolphin or File Picker with thumbnails enabled. 2. Go to a directory with images/videos. 3. Find at least one broken image. OBSERVED RESULT If there is at least one broken image, the thumbnailer will abuse the CPU and Disk I/O, freezing the computer indefinitely. EXPECTED RESULT In the event of a broken image, try loading a preview for a set amount of time (5~10 seconds?) before displaying a 'broken image' placeholder and cancelling the operation. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.14.21-150400.24.11-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 Manufacturer: LENOVO Product Name: 2347G2U System Version: ThinkPad T430 ADDITIONAL INFORMATION One could argue that the proposed behavior would be bad for slower media (SMB, Optical Media, etc), but I'm thinking that the logic can be applied specifically to images that 'fail' to be parsed/loaded correctly (if that is even possible). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457508] Disc Images mount successfully, but aren't shown under the 'Places' panel.
https://bugs.kde.org/show_bug.cgi?id=457508 --- Comment #3 from Lemuel Simon --- (In reply to Kwon-Young Choi from comment #1) > Hello, > > How do you mount the iso file ? > Would it be possible to transmit the iso file so that I can test it on my > system ? Hi, I mount the ISO file by right-clicking on the file and selecting 'mount'. No third-party services were used in Dolphin. Transmitting the ISO may be an issue, as I deal with copyrighted software in my line of work. I used the Windows 10 LTSC iso (distributed on Microsoft's website) and Hiren's PE. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457509] Plasmashell freezes until the Network Widget confirms 'Limited/No Internet Access'
https://bugs.kde.org/show_bug.cgi?id=457509 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457509] New: Plasmashell freezes until the Network Widget confirms 'Limited/No Internet Access'
https://bugs.kde.org/show_bug.cgi?id=457509 Bug ID: 457509 Summary: Plasmashell freezes until the Network Widget confirms 'Limited/No Internet Access' Product: plasmashell Version: 5.25.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: lemuelsimo...@protonmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY Basically, if one connects to a Wi-Fi hotspot with 'Limited/No Internet Access', Plasma's UI freezes anywhere between 8 - 15 seconds, until it actually reflects that information on the widget. It seems like while Plasma's 'Frozen', NM or the widget is figuring out whether the connection has Internet. STEPS TO REPRODUCE 1. Connect to hot-spot without Internet Access or with DNS issues. 2. Try interacting with Plasmashell, while the Network Widget is testing the connection. OBSERVED RESULT Plasmashell freezes for a couple seconds, while the Network Manager figures out Internet Availability. EXPECTED RESULT Plasmashell doesn't freeze during the check. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.14.21-150400.24.11-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 Manufacturer: LENOVO Product Name: 2347G2U System Version: ThinkPad T430 ADDITIONAL INFORMATION Granted, this scenario is quite niche. I'm just mentioning it for the sake of polish (if any is required). -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 457507] KRunner launches either Dolphin or Thunar, depending where user clicks.
https://bugs.kde.org/show_bug.cgi?id=457507 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457508] Disc Images mount successfully, but aren't shown under the 'Places' panel.
https://bugs.kde.org/show_bug.cgi?id=457508 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457508] New: Disc Images mount successfully, but aren't shown under the 'Places' panel.
https://bugs.kde.org/show_bug.cgi?id=457508 Bug ID: 457508 Summary: Disc Images mount successfully, but aren't shown under the 'Places' panel. Product: dolphin Version: 22.04.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plugins: ISO mounting Assignee: kwon-young.c...@hotmail.fr Reporter: lemuelsimo...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Mounted disc images mount correctly, they show up in the 'Disks and Devices' widget under the 'Non-removable' devices section. They can also be found mounted at `/run/media/$USER/*` just fine. However, Dolphin does not show the disc image being mounted in the Places panel. Killing and re-launching Dolphin doesn't work either. I currently have a shortcut pointing to `/run/media/$USER` as a workaround. STEPS TO REPRODUCE 1. Mount a disc image in Dolphin (*.iso). 2. Look for entry in Dolphin's Places Panel OBSERVED RESULT The disc image doesn't show up in the Places panel at all. EXPECTED RESULT The disc image is shown in the Places panel. The user can easily unmount the image. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.14.21-150400.24.11-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 Manufacturer: LENOVO Product Name: 2347G2U System Version: ThinkPad T430 ADDITIONAL INFORMATION For some reason, Thunar File Manager can see the disc images mounted by Dolphin. It is shown in Thunar's Places panel and one can unmount the image there as well. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 457507] New: KRunner launches either Dolphin or Thunar, depending where user clicks.
https://bugs.kde.org/show_bug.cgi?id=457507 Bug ID: 457507 Summary: KRunner launches either Dolphin or Thunar, depending where user clicks. Product: krunner Version: 5.25.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: locations Assignee: plasma-b...@kde.org Reporter: lemuelsimo...@protonmail.com CC: alexander.loh...@gmx.de Target Milestone: --- Created attachment 151126 --> https://bugs.kde.org/attachment.cgi?id=151126=edit KRunner launches non-default file manager (Thunar) with 'Open Containing Folder'. SUMMARY The bug is difficult to describe. If I were to type the preferred folder in KRunner, it shows up as a 'Recent' location. If I click in the center of the drop-down list, it launches Dolphin (the default file manager). However, if I click the folder icon to 'Open Containing Folder' (Shift + Enter), it launches Thunar, the non-default file manager. STEPS TO REPRODUCE 1. Open KRunner. 2. Type location. 3. Press center of drop-down list to navigate to location. 4. Repeat steps 1-2, but press the folder icon (Open Containing Folder) instead. OBSERVED RESULT Can launch two different file manager (default and non-default) depending on where the drop-down list was clicked or the keys used to select the entry (Enter vs. Shift + Enter). EXPECTED RESULT Always launch the default file manager in KRunner locations. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.14.21-150400.24.11-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 Manufacturer: LENOVO Product Name: 2347G2U System Version: ThinkPad T430 ADDITIONAL INFORMATION I have both XFCE and Plasma installed, but I used SDDM to start the session and the session environment variable reads 'KDE'. Dolphin is the default application for folder/inode in File Associations. I'm wondering if there was some black magic (Read: override) involved with the XFCE session. I've attached a video of the bug in action. -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 390250] Can't change icons anymore
https://bugs.kde.org/show_bug.cgi?id=390250 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m Resolution|--- |WORKSFORME Status|REPORTED|NEEDSINFO --- Comment #4 from Lemuel Simon --- Is this problem still reproducible in the Current Plasma LTS (5.24) or regular release (5.25). I cannot seem to reproduce that problem in the editor. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 455367] Vertical unreadable `% Complete` progress bars
https://bugs.kde.org/show_bug.cgi?id=455367 --- Comment #12 from Lemuel Simon --- Huh, I just reported this problem yesterday under Breeze, check here: https://bugs.kde.org/show_bug.cgi?id=457084 . The Classik/Classy application style is a Breeze-fork but it doesn't have this issue. Given that it affects multiple Qt-applications that applies the Breeze style, I think this should be relocated to the 'Breeze' product with the QStyle component for visibility. Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.14.21-150400.22-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 455367] Vertical unreadable `% Complete` progress bars
https://bugs.kde.org/show_bug.cgi?id=455367 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m --- Comment #11 from Lemuel Simon --- *** Bug 457084 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 457084] Some Qt-based (QWidgets?) applications have their progress bar rotated vertically.
https://bugs.kde.org/show_bug.cgi?id=457084 Lemuel Simon changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Lemuel Simon --- Seems like other folks had a similar problem over here: https://bugs.kde.org/show_bug.cgi?id=455367 . I'll mark this one as a dupe and move further discussion over there. *** This bug has been marked as a duplicate of bug 455367 *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 457084] Some Qt-based (QWidgets?) applications have their progress bar rotated vertically.
https://bugs.kde.org/show_bug.cgi?id=457084 --- Comment #4 from Lemuel Simon --- (In reply to Nate Graham from comment #3) > Just tried with KTorrent and all KDE stuff from git master; could not > reproduce. Hmm, I would assume that was already fixed in git master. Would it make sense to close this report and re-open it IF it persists in the 5.26 release? The bug tracker is swamped as is. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 457089] Media Player plugin doesn't release wake-lock.
https://bugs.kde.org/show_bug.cgi?id=457089 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 457089] New: Media Player plugin doesn't release wake-lock.
https://bugs.kde.org/show_bug.cgi?id=457089 Bug ID: 457089 Summary: Media Player plugin doesn't release wake-lock. Product: ktorrent Version: 22.04.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: lemuelsimo...@protonmail.com Target Milestone: --- SUMMARY After playing a video in KTorrent via the Media Player plugin, KTorrent doesn't release the wake-lock, preventing screen-locking or sleep from occurring long after the video is finished or stopped. STEPS TO REPRODUCE 1. Open KTorrent. 2. Enable the Media Player plugin under the 'Plugins' tab. 3. Play a video in KTorrent using the Media Player. OBSERVED RESULT The 'Battery & Brightness' widget still reports KTorrent having the wake-lock active. The laptop stays on, no screen-locking occurs unless triggered explicitly. EXPECTED RESULT KTorrent will release the wake-lock as soon as playback has finished. Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.14.21-150400.22-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 Manufacturer: LENOVO Product Name: 2347G2U System Version: ThinkPad T430 ADDITIONAL INFORMATION I am using the Phonon GStreamer-backend, but I haven't noticed the same behavior with other media players using the framework (Dragon Media Player). -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 457084] Some Qt-based (QWidgets?) applications have their progress bar rotated vertically.
https://bugs.kde.org/show_bug.cgi?id=457084 --- Comment #2 from Lemuel Simon --- Created attachment 150879 --> https://bugs.kde.org/attachment.cgi?id=150879=edit The Classy/Classik application theme (Breeze-fork). The bug doesn't occur. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 457084] Some Qt-based (QWidgets?) applications have their progress bar rotated vertically.
https://bugs.kde.org/show_bug.cgi?id=457084 --- Comment #1 from Lemuel Simon --- Created attachment 150878 --> https://bugs.kde.org/attachment.cgi?id=150878=edit Fusion application style, bug doesn't occur. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 457084] New: Some Qt-based (QWidgets?) applications have their progress bar rotated vertically.
https://bugs.kde.org/show_bug.cgi?id=457084 Bug ID: 457084 Summary: Some Qt-based (QWidgets?) applications have their progress bar rotated vertically. Product: Breeze Version: 5.25.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: QStyle Assignee: plasma-b...@kde.org Reporter: lemuelsimo...@protonmail.com CC: noaha...@gmail.com, uhh...@gmail.com Target Milestone: --- Created attachment 150876 --> https://bugs.kde.org/attachment.cgi?id=150876=edit Screenshot of the progress-bar bug in Breeze. SUMMARY In some QWidget applications such as KTorrent, their progress-bars are flipped vertically instead of horizontally. STEPS TO REPRODUCE 1. Open K-Torrent or another QWidget-based application (not all trigger this bug...). 2. Go to a page with a progress-bar. OBSERVED RESULT The progress-bar in some QWidget-based applications are rotated vertically. Another application-style like Qt's Fusion or Paul Mc Auley's Classy/Classik would show normally, but Breeze's doesn't. EXPECTED RESULT The progress-bar is horizontal is it normally would. Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.14.21-150400.22-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 Manufacturer: LENOVO Product Name: 2347G2U System Version: ThinkPad T430 ADDITIONAL INFORMATION I think this is another regression, but again, I'm not sure when it happened. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433132] Panel stays hidden after setting autohide
https://bugs.kde.org/show_bug.cgi?id=433132 Lemuel Simon changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||lemuelsimo...@protonmail.co ||m Resolution|--- |WAITINGFORINFO --- Comment #3 from Lemuel Simon --- I can't seem to reproduce the bug...or at least not as easily. Does this bug still occur in Plasma 5.25.2? If it does, how do you reliably trigger it? Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.14.21-150400.22-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429603] Dolphin refuses to launch AppImages marked as executables
https://bugs.kde.org/show_bug.cgi?id=429603 --- Comment #11 from Lemuel Simon --- (In reply to Nate Graham from comment #10) > Lemuel, can you please file a new bug report for that separate issue? Thanks! No problem. I've opened a new one over here: https://bugs.kde.org/show_bug.cgi?id=456356 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 456356] New: Cannot 'right-click' and run executable file; 'Execute' option isn't listed in menu.
https://bugs.kde.org/show_bug.cgi?id=456356 Bug ID: 456356 Summary: Cannot 'right-click' and run executable file; 'Execute' option isn't listed in menu. Product: dolphin Version: 22.04.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: lemuelsimo...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Double-clicking to launch AppImages, .exe's or .sh's work normally. However, right-clicking then running isn't possible as there is no 'Execute' option listed in the menu. Same with .desktop files; they work if you double-click, but you cannot right-click and execute. STEPS TO REPRODUCE 1. Find executable file in Dolphin (already marked as executable in 'File Properties'.) 2. Right-click on executable file to show the 'right-click menu'. 3. Attempt to locate a 'Run/Execute/Launch' option in the menu. OBSERVED RESULT An 'execute' option is not listed in the right-click menu of the selected executable file. EXPECTED RESULT An 'execute' option should be listed for the user to right-click and execute the file. Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Kernel Version: 5.14.21-150400.22-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 ADDITIONAL INFORMATION I was advised to open this bug report, as I posted the issue in the wrong thread here: https://bugs.kde.org/show_bug.cgi?id=429603 Seems like the option did exist at some point as indicated here: https://bugs.kde.org/show_bug.cgi?id=357469 I can't tell when the regression occurred though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455924] Plasmashell (KRunner/Kickoff) refuse to launch '.exe' files.
https://bugs.kde.org/show_bug.cgi?id=455924 --- Comment #4 from Lemuel Simon --- (In reply to Nate Graham from comment #1) > I assume you're expecting it to launch with WINE? Yes, exactly that. I see in the linked merge requests that there were some security implications there (as previously suspected). Is it possible to do what Dolphin does and prompt the user before it's executed? -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 455929] Appmenu is not exported again when windows are toggled from tray icon.
https://bugs.kde.org/show_bug.cgi?id=455929 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m --- Comment #1 from Lemuel Simon --- (In reply to Lemuel Simon from comment #0) > SUMMARY > Referring to the bug reports here: > https://github.com/Zren/material-decoration/issues/63 and here: > https://bugs.kde.org/show_bug.cgi?id=455152 Forgot to add the rest of the Summary... The appmenu of Claws Mail (GTK 3) and Strawberry(Qt5/6) will stop being exported if they are toggled by tray icons. If the main window for Strawberry was exited, the main window will respawn from the tray without the menu being exported. With Claws Mail, the bug is triggered by simply toggling the main window with the tray icon. In both instances, one must relaunch the applications to see the menus exported again. -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 455929] New: Appmenu is not exported again when windows are toggled from tray icon.
https://bugs.kde.org/show_bug.cgi?id=455929 Bug ID: 455929 Summary: Appmenu is not exported again when windows are toggled from tray icon. Product: kded-appmenu Version: 5.25.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: export Assignee: plasma-b...@kde.org Reporter: lemuelsimo...@protonmail.com Target Milestone: --- SUMMARY Referring to the bug reports here: https://github.com/Zren/material-decoration/issues/63 and here: https://bugs.kde.org/show_bug.cgi?id=455152 STEPS TO REPRODUCE 1. Launch Strawberry(Qt5) or Claws Mail (GTK3) with their tray icons enabled. 2. Toggle-show Strawberry's/Claw's main window with tray icon. 3. Close main window by clicking 'X' (the tray icon should still be there). 4. Press Strawberry/Claws tray icon to show the main window again. OBSERVED RESULT The appmenu is no longer exported; KDE's Global Menu, Psifodotos' Appmenu and Zren's Material LIM no longer display the menu. Running `xprop` on Strawberry confirms that the menu is no longer exported. EXPECTED RESULT The Global Menu is exported. ADDITIONAL INFORMATION For testing, I've launched an XFCE session with Valapanel's Appmenu (https://gitlab.com/vala-panel-project/vala-panel-appmenu) and tried to replicate the bug, but it doesn't occur there at all. Strawberry's and Claw's menus are always displayed when the main window is visible, even when going through the aforementioned steps. So, I believe it is an issue with how the appmenu is exported in KDE's service daemon. Here is some output from `xprop -f _NET_WM_ICON 8i | sort`: When Claws Mail (GTK3) works: ``` bitmap id # of mask for icon: 0x2e0001d bitmap id # to use for icon: 0x2e00016 Client accepts input or input focus: True _GTK_MENUBAR_OBJECT_PATH(UTF8_STRING) = "/org/appmenu/gtk/window/0" _GTK_THEME_VARIANT(UTF8_STRING) = "dark" _GTK_UNIQUE_BUS_NAME(UTF8_STRING) = ":1.384" icon window: 0x0 Initial state is Normal State. _KDE_NET_WM_ACTIVITIES(STRING) = "b7a1258d-7ce5-442f-a07e-134d0e623274" _KDE_NET_WM_APPMENU_OBJECT_PATH(STRING) = "/MenuBar/26" _KDE_NET_WM_APPMENU_SERVICE_NAME(STRING) = "org.kde.plasma.gmenu_dbusmenu_proxy" _KDE_NET_WM_FRAME_STRUT(CARDINAL) = 0, 0, 24, 0 _KDE_NET_WM_USER_CREATION_TIME(CARDINAL) = 138810479 _NET_FRAME_EXTENTS(CARDINAL) = 0, 0, 24, 0 _NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE, _NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_SHADE, _NET_WM_ACTION_MAXIMIZE_VERT, _NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE _NET_WM_DESKTOP(CARDINAL) = 1 _NET_WM_ICON(CARDINAL): Type mismatch: assumed size 8 bits, actual size 32 bits. _NET_WM_ICON_GEOMETRY(CARDINAL) = 245, 740, 36, 28 _NET_WM_ICON_NAME(UTF8_STRING) = "20180...@roytec.edu@outlook.office365.com - Claws Mail 4.0.0" _NET_WM_NAME(UTF8_STRING) = "20180...@roytec.edu@outlook.office365.com - Claws Mail 4.0.0" _NET_WM_OPAQUE_REGION(CARDINAL) = 0, 0, 1044, 609 _NET_WM_PID(CARDINAL) = 4986 _NET_WM_STATE(ATOM) = _NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 48234501, 48234502 _NET_WM_USER_TIME(CARDINAL) = 138820050 _NET_WM_USER_TIME_WINDOW(WINDOW): window id # 0x2e4 _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL program specified base size: 320 by 200 program specified location: 0, 0 program specified minimum size: 320 by 200 _UNITY_OBJECT_PATH(UTF8_STRING) = "/org/appmenu/gtk/window/0" window gravity: NorthWest window id # of group leader: 0x2e1 window state: Normal WM_CLASS(STRING) = "claws-mail", "Claws-mail" WM_CLIENT_LEADER(WINDOW): window id # 0x2e1 WM_CLIENT_MACHINE(STRING) = "Leap.T430" WM_HINTS(WM_HINTS): WM_ICON_NAME(STRING) = "20180...@roytec.edu@outlook.office365.com - Claws Mail 4.0.0" WM_LOCALE_NAME(STRING) = "en_US.UTF-8" WM_NAME(STRING) = "20180...@roytec.edu@outlook.office365.com - Claws Mail 4.0.0" WM_NORMAL_HINTS(WM_SIZE_HINTS): WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING, _NET_WM_SYNC_REQUEST WM_STATE(WM_STATE): WM_WINDOW_ROLE(STRING) = "mainwindow" XdndAware(ATOM) = BITMAP ``` When Claws Mail (GTK3) doesn't work: ``` bitmap id # of mask for icon: 0x2e0001d bitmap id # to use for icon: 0x2e00016 Client accepts input or input focus: True _GTK_MENUBAR_OBJECT_PATH(UTF8_STRING) = "/org/appmenu/gtk/window/0" _GTK_THEME_VARIANT(UTF8_STRING) = "dark" _GTK_UNIQUE_BUS_NAME(UTF8_STRING) = ":1.384" icon window: 0x0 Initial state is Normal State. _KDE_NET_WM_ACTIVITIES(STRING) = "b7a1258d-7ce5-442f-a07e-134d0e623274" _KDE_NET_WM_APPMENU_OBJECT_PATH(STRING) = "/MenuBar/27" _KDE_NET_WM_APPMENU_SERVICE_NAME(STRING) =
[dolphin] [Bug 429603] Dolphin refuses to launch AppImages marked as executables
https://bugs.kde.org/show_bug.cgi?id=429603 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m --- Comment #6 from Lemuel Simon --- Currently on Dolphin version 22.04.2. Double-clicking to launch AppImages, .exe's or .sh's work normally. However, right-clicking then running isn't possible as there is no 'Execute' option listed in the menu. Same with .desktop files; they work if you double-click, but you cannot right-click and execute. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455924] Plasmashell (KRunner/Kickoff) refuse to launch '.exe' files.
https://bugs.kde.org/show_bug.cgi?id=455924 Lemuel Simon changed: What|Removed |Added Platform|Other |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455924] Plasmashell (KRunner/Kickoff) refuse to launch '.exe' files.
https://bugs.kde.org/show_bug.cgi?id=455924 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455924] New: Plasmashell (KRunner/Kickoff) refuse to launch '.exe' files.
https://bugs.kde.org/show_bug.cgi?id=455924 Bug ID: 455924 Summary: Plasmashell (KRunner/Kickoff) refuse to launch '.exe' files. Product: plasmashell Version: 5.25.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lemuelsimo...@protonmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Although the Windows executable is marked 'executable' and the drive is mounted with the execution bit, Plasma (Kickoff and KRunner) will refuse to launch the program, citing 'For security reasons, launching executable is not allowed in this context.'. However, if I were to navigate to the executable's location with Dolphin and launch it, it works normally. STEPS TO REPRODUCE 1. Open KRunner or Kickoff. 2. Type-in name of program. 'Eg. Ultrakill.exe' 3. Click to run the executable. OBSERVED RESULT Instead of the program launching, a notification shows up stating 'For security reasons, launching executables is not allowed in this context.'. EXPECTED RESULT The program should be able to execute from Plasmashell. Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.2 Kernel Version: 5.14.21-150400.22-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 ADDITIONAL INFORMATION I understand that these measures are there for 'security', but the criteria for what is allowed or blocked is vague and potentially frustrating to the end-user. This issue affected Dolphin earlier: https://bugs.kde.org/show_bug.cgi?id=429603 . Can the logic be dumbed-down to match GNOME's? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442301] system monitor sensor widget: "could not prompt the user for which application to start"
https://bugs.kde.org/show_bug.cgi?id=442301 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m --- Comment #4 from Lemuel Simon --- I can reproduce this problem on the System Monitor Widget with Plasma version 5.25.1. Was just about to make a bug report about it, but it seems like it already existed. Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.2 Kernel Version: 5.14.21-150400.22-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439100] Plasma crashed after instaling Active Window Control +Global Menu widget
https://bugs.kde.org/show_bug.cgi?id=439100 Lemuel Simon changed: What|Removed |Added Resolution|WORKSFORME |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439100] Plasma crashed after instaling Active Window Control +Global Menu widget
https://bugs.kde.org/show_bug.cgi?id=439100 Lemuel Simon changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||lemuelsimo...@protonmail.co ||m Resolution|--- |WORKSFORME --- Comment #1 from Lemuel Simon --- (In reply to Marcin Jurgielewicz from comment #0) > Application: plasmashell (5.18.5) > > Qt Version: 5.12.8 > Frameworks Version: 5.68.0 > Operating System: Linux 5.8.0-59-generic x86_64 > Windowing system: X11 > Distribution: Ubuntu 20.04.2 LTS > > -- Information about the crash: > - What I was doing when the application crashed: After compiling and > instaling Active Window Control there is an error with this widget that > global menu didint work, so i tried another widget for that function, maybe > this can work together with AWC. After having both widgets on, mentioned > functionality Blobal menu appered from both sources. But only global menu > work on AWC, trying global menu on another widget giving plasma crash. > > - Custom settings of the application: > > The crash can be reproduced every time. > Hello there! Does this problem still occur in the latest Plasma LTS release (5.24)? I couldn't reproduce the issue in versions 5.24 and 5.25. Also, please note that the Active Window Control widget has been unmaintained for years now and Psifidoto's 'Window Buttons Widget' is a spiritual successor to the aforementioned widget. Check it out here: https://github.com/psifidotos/applet-window-buttons . I assume that packages should be available for Ubuntu as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454906] Adding apps to the panel as widgets corrupt the panel's layout.
https://bugs.kde.org/show_bug.cgi?id=454906 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454906] New: Adding apps to the panel as widgets corrupt the panel's layout.
https://bugs.kde.org/show_bug.cgi?id=454906 Bug ID: 454906 Summary: Adding apps to the panel as widgets corrupt the panel's layout. Product: plasmashell Version: 5.24.90 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: lemuelsimo...@protonmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 149491 --> https://bugs.kde.org/attachment.cgi?id=149491=edit Video of the panel widget bug. (Ignore the graphical glitches, as my *real* panel is set to autohide.) This bug can occur on a fresh install too, I've reproduced it in the KDE Neon Testing image too. SUMMARY Adding an application to Plasma's panel as a widget will corrupt/destroy the layout of all widgets on the panel, on restarting Plasmashell or logging-out and in, rendering it unusable until the panel is deleted. (A video of the bug was attached as well. The bug will be reproduced on the top panel, I don't want to nuke my working panel again...) STEPS TO REPRODUCE (WARNING: THIS WILL DESTROY YOUR PANEL.) 1. Open Kickoff. 2. Right click on any application. 3. Select 'Add to Panel (Widget)' 4. Restart Plasmashell by logging out and back in (or running `kquitapp5 plasmashell && kstart5 plasmashell > /dev/null 2>&1`) 5. Watch Plasma's panel load corrupted. OBSERVED RESULT Plasma's panel is corrupted; all widgets overlap one another to one corner (I'm not sure if the direction is affected by the alignment settings). EXPECTED RESULT Widgets on Plasma's panel show normally. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.3 KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-150300.59.68-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 Manufacturer: LENOVO Product Name: 2347G2U System Version: ThinkPad T430 ADDITIONAL INFORMATION I'm confident that this is a regression in the Plasma 5.25 Beta (5.24.90) as it worked normally in 5.24.5. I've just upgraded yesterday (missed the Beta Testing day...) and immediately after logging back in, this error occurred. I can't remove the widget easily as I need to 'hover' over it first; that is impossible as all widgets overlap one another. I cannot move the widgets on the panel either, so I just removed the panel and started from scratch. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453921] System Settings doesn't detect default Plasma styles.
https://bugs.kde.org/show_bug.cgi?id=453921 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453921] New: System Settings doesn't detect default Plasma styles.
https://bugs.kde.org/show_bug.cgi?id=453921 Bug ID: 453921 Summary: System Settings doesn't detect default Plasma styles. Product: systemsettings Version: 5.24.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_desktoptheme Assignee: plasma-b...@kde.org Reporter: lemuelsimo...@protonmail.com Target Milestone: --- Created attachment 148904 --> https://bugs.kde.org/attachment.cgi?id=148904=edit Screenshot of empty Plasma Styles list, within System Settings. SUMMARY The default Plasma styles (Air/Oxygen, Breeze) with their color-scheme adaptive variants are absent from System Settings. However, third-party styles (like Materia) are shown normally. STEPS TO REPRODUCE 1. Open System Settings 2. Navigate to 'Appearance' -> 'Global Theme' -> 'Plasma Style' 3. Attempt to select a Plasma Style. OBSERVED RESULT None of the default styles are shown in the System Settings. Only third-party styles are listed. EXPECTED RESULT Both default and third-party styles are shown in System Settings. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.3 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-150300.59.63-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 ADDITIONAL INFORMATION I've only seen this bug since the recent KDE Frameworks update to 5.94. However, the issue may have persisted even before then. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 321374] Multiple accounts
https://bugs.kde.org/show_bug.cgi?id=321374 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m --- Comment #13 from Lemuel Simon --- I would like to see this feature as well. KDE desperately lacks a dead-simple email client that 'just works'. KMail has been a buggy mess for years. Multi-account support is a killer feature to have! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445767] Global menu items overlap with other panel applets when the opened app has many menus
https://bugs.kde.org/show_bug.cgi?id=445767 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m --- Comment #3 from Lemuel Simon --- Would this be related to this bug? https://bugs.kde.org/show_bug.cgi?id=396404 This report may be a duplicate, but I'll need to be sure. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434877] High CPU usage
https://bugs.kde.org/show_bug.cgi?id=434877 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m --- Comment #16 from Lemuel Simon --- To add to this bug report, I believe System Monitor's whole UI is affected by this, regardless of a graph being present or not. Updating window content via moving graphs or just scrolling the processes list is very expensive to the CPU. Going on the default 'Processes' page and scrolling the processes page (with no graphs enabled) will easily spike the CPU usage to 40%+. Doing the same thing in KSysGuard will only raise ~7% at most. Is it that GPU rendering isn't happening at all? Operating System: openSUSE Leap 15.3 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-150300.59.49-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433769] Disk state not available in System Monitor
https://bugs.kde.org/show_bug.cgi?id=433769 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m --- Comment #1 from Lemuel Simon --- (In reply to lnxusr from comment #0) > ADDITIONAL INFORMATION > Ksysguard displays this info in the CPU column which would be acceptable but > I think a separate column for disk state would be a better option. Forgive my ignorance, but what kind information does 'disk state' convey exactly? I'm aware of I/O rates and disk temperatures. I can't remember seeing it in KSysGuard. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 442095] process names indented too far in Tree View
https://bugs.kde.org/show_bug.cgi?id=442095 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m --- Comment #12 from Lemuel Simon --- Hmm...I think this happens because an 'icon' is expected within that gap. Say, if look a program with an icon (Firefox, Kate,ect), the icon will fill the gap. However, most processes don't have one (systemd,KWin,plasmashell), and there isn't a 'fallback' or 'placeholder' icon for such processes in System Monitor. I suggest that the generic 'terminal/console' icon be used for that (if icons are enabled). I think it would appropriate since its 'command line' or background processes anyway. Thoughts? -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 429563] Icon / Menu for System Tray
https://bugs.kde.org/show_bug.cgi?id=429563 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m --- Comment #1 from Lemuel Simon --- (In reply to Richard Llom from comment #0) > Since there is now a unified background service (KSystemStats) for sensor > data, it would be nice to also have a system tray menu, which would use that > service. The menu would be used to give some stats on a quick glance. > > For reference, this is what gnome has: > https://github.com/xtranophilist/gnome-shell-extension-sensors > Technically, this existed in Plasma 5.21 and onwards with the 'System Monitor Sensor' widget that you can place in the panel or desktop area. You can add any amount of 'sensors' offered by KSystemStats as a pie chart, bar graph or plain text. You can also launch System Monitor there as well. Is there something in particular that isn't provided by the widget? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428854] Nightcolor fails to activate after KWin or the whole session is restarted; must manually toggle it off and on again
https://bugs.kde.org/show_bug.cgi?id=428854 --- Comment #17 from Lemuel Simon --- (In reply to Lemuel Simon from comment #16) > I am not sure if this was mentioned elsewhere, but I believe to problem is > caused by a conflict between Night Color and 'Gamma Settings'. Night Color > has worked consistently well for me (Plasma 5.24.1) until I open the > 'Display Configuration' KCM in System Settings. Doing so would immediately > 'reset' the display, getting rid of Night Color's red tint (while Night > Color is still enabled.) Maybe that's why Night Color would 'disappear' > shortly after activating at login, 'Gamma Settings/Display Configuration' > gets triggered and fiddles with the gamma values. > > I have tested in X11, not sure how the Wayland session handles that. > > Operating System: openSUSE Leap 15.3 > KDE Plasma Version: 5.24.1 > KDE Frameworks Version: 5.91.0 > Qt Version: 5.15.2 > Kernel Version: 5.3.18-150300.59.49-default (64-bit) > Graphics Platform: X11 > Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz > Memory: 7.6 GiB of RAM > Graphics Processor: Mesa DRI Intel® HD Graphics 4000 I'm wondering if this is related: https://bugs.kde.org/show_bug.cgi?id=413134 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428854] Nightcolor fails to activate after KWin or the whole session is restarted; must manually toggle it off and on again
https://bugs.kde.org/show_bug.cgi?id=428854 --- Comment #16 from Lemuel Simon --- I am not sure if this was mentioned elsewhere, but I believe to problem is caused by a conflict between Night Color and 'Gamma Settings'. Night Color has worked consistently well for me (Plasma 5.24.1) until I open the 'Display Configuration' KCM in System Settings. Doing so would immediately 'reset' the display, getting rid of Night Color's red tint (while Night Color is still enabled.) Maybe that's why Night Color would 'disappear' shortly after activating at login, 'Gamma Settings/Display Configuration' gets triggered and fiddles with the gamma values. I have tested in X11, not sure how the Wayland session handles that. Operating System: openSUSE Leap 15.3 KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-150300.59.49-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396404] Limit the length of appmenu / global menu
https://bugs.kde.org/show_bug.cgi?id=396404 --- Comment #4 from Lemuel Simon --- Created attachment 146955 --> https://bugs.kde.org/attachment.cgi?id=146955=edit Lattedock with Global Menu (applet-window-appmenu), automatically resized, all widgets fit in the panel. Currently, the workaround is to ditch both the default Global Menu and Plasma's Panel, and replace them with Psifodotos' Latte Dock and Global Menu (applet-window-appmenu) solutions. Whatever he did, made Lattedock and his Global Menu smart enough to resize/limit it's content width, so the other widgets would fit in the panel. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396404] Limit the length of appmenu / global menu
https://bugs.kde.org/show_bug.cgi?id=396404 --- Comment #3 from Lemuel Simon --- Created attachment 146954 --> https://bugs.kde.org/attachment.cgi?id=146954=edit Global Menu with Bleachbit, everything is pushed out of the panel. However...fire up something like Bleachbit with a LARGE menu, everything to the right of the Global Menu widget is pushed out. System Tray, Pager, Clock, everything. This can be a huge PITA with smaller screens (eg. Small laptops). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396404] Limit the length of appmenu / global menu
https://bugs.kde.org/show_bug.cgi?id=396404 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m --- Comment #2 from Lemuel Simon --- Created attachment 146953 --> https://bugs.kde.org/attachment.cgi?id=146953=edit Global Menu with KDevelop, Clock and 'Show Desktop' Widgets partially pushed out of Plasma's Tray A couple years later, it is still a problem as of Plasma 5.24.1. Large or medium sized global menus will push out other widget to the rightmost side of the tray. The attached screenshot is a minor case... -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 450159] Akonadi Console always crashes on start.
https://bugs.kde.org/show_bug.cgi?id=450159 Lemuel Simon changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Lemuel Simon --- Ok, there was a missing package. The OpenSUSE package did not install the `akonadi-search` package. Akonadi Console works normally after installing that. This is a bug of the OpenSUSE packages. I'm closing this bug as 'RESOLVED' until further notice. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 450159] Akonadi Console always crashes on start.
https://bugs.kde.org/show_bug.cgi?id=450159 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 450159] New: Akonadi Console always crashes on start.
https://bugs.kde.org/show_bug.cgi?id=450159 Bug ID: 450159 Summary: Akonadi Console always crashes on start. Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: akonadiconsole Assignee: kdepim-b...@kde.org Reporter: lemuelsimo...@protonmail.com Target Milestone: --- Application: akonadiconsole (5.19.2 (21.12.2)) Qt Version: 5.15.2 Frameworks Version: 5.90.0 Operating System: Linux 5.3.18-150300.59.46-default x86_64 Windowing System: X11 Distribution: "openSUSE Leap 15.3" DrKonqi: 5.24.0 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Opened Konsole and launched 'akonadiconsole' there. I get this message: 'Please register the custom scheme 'cid' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler.'. It crashes immediately afterwards, the GUI doesn't spawn. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Console (akonadiconsole), signal: Segmentation fault [KCrash Handler] #4 SearchWidget::openStore (this=this@entry=0x5580ed95b480, idx=idx@entry=0) at /usr/src/debug/akonadiconsole-21.12.2-lp153.177.3.x86_64/src/searchwidget.cpp:132 #5 0x7f6b4903eec2 in SearchWidget::SearchWidget (this=0x5580ed95b480, parent=) at /usr/src/debug/akonadiconsole-21.12.2-lp153.177.3.x86_64/src/searchwidget.cpp:106 #6 0x7f6b48ffd552 in MainWidget::MainWidget (this=0x5580ec14ce80, parent=0x7f6aec010b50) at /usr/src/debug/akonadiconsole-21.12.2-lp153.177.3.x86_64/src/mainwidget.cpp:60 #7 0x7f6b48ffe660 in MainWindow::MainWindow (this=0x7f6aec010b50, parent=, __in_chrg=, __vtt_parm=) at /usr/src/debug/akonadiconsole-21.12.2-lp153.177.3.x86_64/src/mainwindow.cpp:24 #8 0x7f6b48ff69be in InstanceSelector::slotAccept (this=this@entry=0x7fff44dcf680) at /usr/src/debug/akonadiconsole-21.12.2-lp153.177.3.x86_64/src/instanceselector.cpp:85 #9 0x7f6b48ff7c0b in InstanceSelector::InstanceSelector (this=0x7fff44dcf680, remoteHost=..., parent=, flags=...) at /usr/src/debug/akonadiconsole-21.12.2-lp153.177.3.x86_64/src/instanceselector.cpp:52 #10 0x5580ea9681fc in main (argc=, argv=) at /usr/src/debug/akonadiconsole-21.12.2-lp153.177.3.x86_64/src/main.cpp:73 [Inferior 1 (process 21718) detached] Possible duplicates by query: bug 94620, bug 398557, bug 394827, bug 384812, bug 382062. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449635] Battery applet doesn't list apps inhibiting sleep.
https://bugs.kde.org/show_bug.cgi?id=449635 Lemuel Simon changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||5.24.0 --- Comment #16 from Lemuel Simon --- (In reply to Lemuel Simon from comment #15) > Created attachment 146447 [details] > Battery and Brightness applet show sleep inhibiting apps again. > > I just updated to Plasma 5.24 today. Sleep inhibiting apps are now listed in > the 'Battery and Brightness' applet as it did before. It works as expected, > so I'll close the bug. @Ratijas, thanks for looking into the matter. You > responses were quick and thorough, highly appreciated. Uhh...I'm second-guessing here. Applets work but Plasma Engine Explorer still shows nothing if the Inhibitions data source is selected under Power Management. Separate issues, yeah? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449635] Battery applet doesn't list apps inhibiting sleep.
https://bugs.kde.org/show_bug.cgi?id=449635 --- Comment #15 from Lemuel Simon --- Created attachment 146447 --> https://bugs.kde.org/attachment.cgi?id=146447=edit Battery and Brightness applet show sleep inhibiting apps again. I just updated to Plasma 5.24 today. Sleep inhibiting apps are now listed in the 'Battery and Brightness' applet as it did before. It works as expected, so I'll close the bug. @Ratijas, thanks for looking into the matter. You responses were quick and thorough, highly appreciated. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449635] Battery applet doesn't list apps inhibiting sleep.
https://bugs.kde.org/show_bug.cgi?id=449635 --- Comment #13 from Lemuel Simon --- Created attachment 146375 --> https://bugs.kde.org/attachment.cgi?id=146375=edit PowerManagementItem.qml for Plasma 5.23.90 OK, I've attached the requested file. Sorry for the late response. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449635] Battery applet doesn't list apps inhibiting sleep.
https://bugs.kde.org/show_bug.cgi?id=449635 --- Comment #11 from Lemuel Simon --- (In reply to ratijas from comment #10) > No, I can assure you there were no plans on removing inhibitions from the > «Battery and Brightness» applet. This is most certainly a bug is our data > sources on backend part. Then 'Display Configuration' is reading another data source, as in, its not using the backend? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449635] Battery applet doesn't list apps inhibiting sleep.
https://bugs.kde.org/show_bug.cgi?id=449635 --- Comment #9 from Lemuel Simon --- Created attachment 146367 --> https://bugs.kde.org/attachment.cgi?id=146367=edit Vivaldi playing Youtube video, inhibiting sleep, shown in 'Display Configuration' applet. Apparently, this information is shown in the 'Display Configuration' applet instead of the Battery Applet. The 'Wakelock' for Chromium shows up there while playing a video (see screenshot). This may not be a bug after all, but a 'questionable' redesign. I found this out by mistake and Display Configuration applet is not visible by default. It isn't as discoverable as when it was in the Battery Applet. ~~Also, why is Presentation Mode in both the Battery Applet and the Display Configuration applet, but the Wakelock only shown in the latter?~~ Should I close this bug? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449635] Battery applet doesn't list apps inhibiting sleep.
https://bugs.kde.org/show_bug.cgi?id=449635 --- Comment #7 from Lemuel Simon --- (In reply to ratijas from comment #6) > > I've just realized that this was to be done in Plasma Engine Explorer than > > Qt5 Dbus Viewer. My apologies. > > I was asking for both, so you did everything right. Thank you! > > > Plasma Engine Explorer, Inhibitions data source doesn't expand. > > Just to clarify: I see you typed in "Inhibitions" in the source name, so I > assume you explicitly "Request"ed it, and it still does not expand, correct? > If so, then it rules out the possibility of a bug in applet frontend, and we > gotta investigate data providers. That assumption is correct. I clicked on the entry and it didn't expand, so I tried manually typing it in. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449635] Battery applet doesn't list apps inhibiting sleep.
https://bugs.kde.org/show_bug.cgi?id=449635 --- Comment #5 from Lemuel Simon --- Created attachment 146309 --> https://bugs.kde.org/attachment.cgi?id=146309=edit Plasma Engine Explorer, Inhibitions data source doesn't expand. I've just realized that this was to be done in Plasma Engine Explorer than Qt5 Dbus Viewer. My apologies. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449635] Battery applet doesn't list apps inhibiting sleep.
https://bugs.kde.org/show_bug.cgi?id=449635 --- Comment #4 from Lemuel Simon --- Created attachment 146294 --> https://bugs.kde.org/attachment.cgi?id=146294=edit ListInhibitions dbus method (fake inhibitor 'foo' 'bar') The fake inhibitor shows up in Dbus Viewer as well. Still isn't reflected in the battery applet. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449635] Battery applet doesn't list apps inhibiting sleep.
https://bugs.kde.org/show_bug.cgi?id=449635 --- Comment #3 from Lemuel Simon --- Created attachment 146293 --> https://bugs.kde.org/attachment.cgi?id=146293=edit ListInhibitions dbus method ListInhibitions method successfully shows Vivaldi (web browser) inhibit sleep while playing a video. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449635] Battery applet doesn't list apps inhibiting sleep.
https://bugs.kde.org/show_bug.cgi?id=449635 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449635] Battery applet doesn't list apps inhibiting sleep.
https://bugs.kde.org/show_bug.cgi?id=449635 --- Comment #1 from Lemuel Simon --- Created attachment 146290 --> https://bugs.kde.org/attachment.cgi?id=146290=edit Vivaldi playing music, inhibiting sleep, doesn't appear in applet. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449635] New: Battery applet doesn't list apps inhibiting sleep.
https://bugs.kde.org/show_bug.cgi?id=449635 Bug ID: 449635 Summary: Battery applet doesn't list apps inhibiting sleep. Product: plasmashell Version: 5.23.90 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Battery Monitor Assignee: plasma-b...@kde.org Reporter: lemuelsimo...@protonmail.com CC: k...@privat.broulik.de, m...@ratijas.tk Target Milestone: 1.0 SUMMARY As of Plasma 5.23.90, the battery applet will no longer list the applications inhibiting sleep or the screen timeout, although the inhibitors work. The feature worked in 5.23, so I think it may be a regression. STEPS TO REPRODUCE 1. Open Retroarch/MPV/Dragonplayer/Youtube in Chrome 2. Play media (games/videos) 3. Open battery applet in Plasma Panel or Latte Dock. OBSERVED RESULT The applications inhibiting sleep are not listed in the battery applet anymore. However, sleep is inhibited by the applications as they normally would. EXPECTED RESULT Chromium/Retroarch/Dragonplayer would be listed in the battery applet if something is playing. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.3 KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-150300.59.43-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379669] KDevelop continues to hang on exit in itemrepository.h [Bucket::deleteItem]
https://bugs.kde.org/show_bug.cgi?id=379669 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m --- Comment #44 from Lemuel Simon --- *** Bug 448684 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 448684] KDevelop process does not terminate.
https://bugs.kde.org/show_bug.cgi?id=448684 Lemuel Simon changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Lemuel Simon --- (In reply to Igor Kushnir from comment #1) > Duplicate of Bug 379669? It may be a duplicate indeed. I didn't see this bug before. *** This bug has been marked as a duplicate of bug 379669 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 448684] KDevelop process does not terminate.
https://bugs.kde.org/show_bug.cgi?id=448684 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 448684] New: KDevelop process does not terminate.
https://bugs.kde.org/show_bug.cgi?id=448684 Bug ID: 448684 Summary: KDevelop process does not terminate. Product: kdevelop Version: 5.7.211201 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: lemuelsimo...@protonmail.com Target Milestone: --- SUMMARY Upon quitting KDevelop normally (Alt+F4 or closing the window), the window closes, but a `kdevelop` process is left in the background. The process would hog a single thread/CPU core with 100% usage, and it doesn't go away. No errors are thrown and no crashes occur. This is reproducible on every launch and exit of KDevelop. Clearing `~/.cache/kdevduchain` or `~.cache/kdevelop` doesn't change the outcome. Running it with `strace` doesn't show anything useful and running it in the console doesn't show anything either. STEPS TO REPRODUCE 1. Launch KDevelop 2. Quit KDevelop (doesn't matter if a session is chosen or not). OBSERVED RESULT KDevelop doesn't terminate and must be forcefully killed with 'kill -9'. The process hogs the CPU thread or core and upon relaunch (if the process is still active), the new KDevelop instance would complain about a session already being active. EXPECTED RESULT KDevelop's processes terminate normally. No zombie or background processes left behind. ADDITIONAL INFORMATION: I would like to think this was a regression, as this problem didn't occur in previous versions (IIRC). I do not recall having this problem two months ago. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.3 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-59.37-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442864] System Settings freezes completely if 'Night Color' KCM is selected.
https://bugs.kde.org/show_bug.cgi?id=442864 Lemuel Simon changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #4 from Lemuel Simon --- Since then, I have done a wipe and re-installation of '/' and preserved the '/home partition'. The bug is no longer reproducible in KDE 5.23.3, I'm certain that it was corruption on the root partition. I'll close the bug until I encounter it again. Thanks for your time. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 441123] Dolphin does not create, save thumbnails
https://bugs.kde.org/show_bug.cgi?id=441123 Lemuel Simon changed: What|Removed |Added CC|lemuelsimo...@protonmail.co | |m | -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 443806] Dolphin should allow option to cache thumbnails for separate encrypted devices / locations (KDialog too?)
https://bugs.kde.org/show_bug.cgi?id=443806 --- Comment #3 from Lemuel Simon --- (In reply to flan_suse from comment #2) > For any users or developers reading this, here is a summarized version of > how things stand now, as of version 21.08.1 default behaviour: > > * Local folder on same filesystem, no encryption > Cached thumbnails? Yes! > > * Local folder on same filesystem, LUKS encryption > Cached thumbnails? Yes! > If you don't mind me asking, what is your partition scheme? I have a LVM on LUKS setup with Home,Root & Swap subvolumes in openSUSE Leap (Argon). However, the thumbnail cache doesn't get created at all! '~/.cache/thumbnails' doesn't exist and thumbnails are painstakingly re-generated every time I open '~/Pictures' with Dolphin, Gwenview or the KDE File Picker. -- You are receiving this mail because: You are watching all bug changes.
