[systemsettings] [Bug 440244] System Settings does not show video preview for desktop effects
https://bugs.kde.org/show_bug.cgi?id=440244 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #6 from Thiago Sueto --- So, from what I understand, this is ultimately a downstream issue: if a package is missing that prevents the video from running, the video just doesn't show up / loads endlessly. Particularly problematic for example if you use only flatpaks for videos and don't actually have codecs installed system wide. Perhaps we could have a cleaner solution by showing a message after a given timeout? Like: after 15 seconds, if the video is not loaded, show a Label saying "The preview took too long to run. [ ? ]", with the [ ? ] being a ContextualHelpButton saying something like "Your system might be missing essential packages needed to show this preview. Please check with your distribution." Then we'd have the necessary software mentioned in https://community.kde.org/Distributions/Packaging_Recommendations, and point distros to that to fix things for their users. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478620] Mouse navigation with numpad doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=478620 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #5 from Thiago Sueto --- *** Bug 490825 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 490825] [Mouse navigation] Use number pad to move cursor does nothing on Wayland
https://bugs.kde.org/show_bug.cgi?id=490825 Thiago Sueto changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Thiago Sueto --- Oops, my bad. I did not see there was an existing bug report open. *** This bug has been marked as a duplicate of bug 478620 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 490826] New: [Keyboard filters] Slow keys does nothing on Wayland
https://bugs.kde.org/show_bug.cgi?id=490826 Bug ID: 490826 Summary: [Keyboard filters] Slow keys does nothing on Wayland Classification: Applications Product: systemsettings Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_accessibility Assignee: plasma-b...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- SUMMARY If you go to the Accessibility KCM, Keyboard Filters, enabling "Slow keys" does nothing on Wayland, while on X11 it works. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240629 KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.7-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 Manufacturer: Dell Inc. Product Name: Inspiron 5567 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 490825] [Mouse navigation] Use number pad to move cursor does nothing on Wayland
https://bugs.kde.org/show_bug.cgi?id=490825 Thiago Sueto changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 490825] New: [Mouse navigation] Use number pad to move cursor does nothing on Wayland
https://bugs.kde.org/show_bug.cgi?id=490825 Bug ID: 490825 Summary: [Mouse navigation] Use number pad to move cursor does nothing on Wayland Classification: Applications Product: systemsettings Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_accessibility Assignee: plasma-b...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- SUMMARY If you go to the Accessibility KCM, Mouse Navigation, enabling "Use number pad to move cursor" does nothing on Wayland, while on X11 it works. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240629 (Krypton) KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.7-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 Manufacturer: Dell Inc. Product Name: Inspiron 5567 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 487286] Flatpak KCM does not detect flatpaks installed in another installation
https://bugs.kde.org/show_bug.cgi?id=487286 --- Comment #2 from Thiago Sueto --- (In reply to ratijas from comment #1) > Is this basically a duplicate of https://bugs.kde.org/show_bug.cgi?id=485189 > ? Or maybe that one is for supporting GUI to manually add them, and this one > is "simply" to work with what's already registered with Flatpak… Yeah, the other bug report is for the lack of a GUI to set a custom installation. This one is about the flatpak KCM being unable to detect any flatpaks from a custom installation that was already set. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 487286] New: Flatpak KCM does not detect flatpaks installed in another installation
https://bugs.kde.org/show_bug.cgi?id=487286 Bug ID: 487286 Summary: Flatpak KCM does not detect flatpaks installed in another installation Classification: Applications Product: systemsettings Version: git-stable-Plasma/5.27 Platform: SteamOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_flatpak Assignee: plasma-b...@kde.org Reporter: herzensch...@gmail.com CC: joshiesuha...@gmail.com, m...@ratijas.tk Target Milestone: --- SUMMARY I'm on SteamOS (Steam Deck running Plasma 5). To save space on my Steam Deck, I have an extra installation for flatpaks that is stored on my SD card, as per flatpak-installation: https://man.archlinux.org/man/extra/flatpak/flatpak-installation.5.en Once I moved all my flatpaks to my SD card, the flatpak KCM stopped being able to detect my flatpaks. STEPS TO REPRODUCE 1. Create a file /etc/flatpak/installations.d/extra.conf 2. Add a conf file pointing to some non-standard installation 3. sudo flatpak install --installation= 4. Check the flatpak KCM app list EXAMPLE CONFIG [Installation "sdcard"] Path=/run/media/mmcblk0p1/flatpak/ DisplayName=Extra Installation StorageType=sdcard OBSERVED RESULT The flatpak installed to the custom installation path does not show up in the KCM. EXPECTED RESULT The flatpak installed to the custom installation path should show up in the KCM. SOFTWARE/OS VERSIONS Operating System: SteamOS 3.5.19 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.9 Kernel Version: 6.1.52-valve16-1-neptune-61 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Custom APU 0405 Memory: 14.5 GiB of RAM Graphics Processor: AMD Custom GPU 0405 Manufacturer: Valve Product Name: Jupiter System Version: 1 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485189] Provide GUI method to define a custom installation following flatpak-installation
https://bugs.kde.org/show_bug.cgi?id=485189 --- Comment #4 from Thiago Sueto --- > But where is it discouraged? Sorry, I meant to say it's generally discouraged to do root operations *in immutable distributions*. SteamOS is one, and they caution the user (twice) that they should know what they're doing and that their changes might be reset, and they don't have a sudo password by default, as mentioned in https://help.steampowered.com/en/faqs/view/671A-4453-E8D2-323C. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485189] Provide GUI method to define a custom installation following flatpak-installation
https://bugs.kde.org/show_bug.cgi?id=485189 --- Comment #2 from Thiago Sueto --- > Where do the manpages say that? "more system-wide installations can be defined via configuration files /etc/flatpak/installations.d/" A user path like ~/.local/share/flatpak/installations.d doesn't seem to work. See: https://github.com/flatpak/flatpak/issues/4403 > And how would it be any different to what discover would do under the hood? I don't know. I'm not familiar with how root files persist in immutable distros yet. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485189] New: Provide GUI method to define a custom installation following flatpak-installation
https://bugs.kde.org/show_bug.cgi?id=485189 Bug ID: 485189 Summary: Provide GUI method to define a custom installation following flatpak-installation Classification: Applications Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Flatpak Backend Assignee: plasma-b...@kde.org Reporter: herzensch...@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com, trav...@redhat.com Target Milestone: --- I am on a Steam Deck with 64 GB of storage running default Plasma 5 and I have an external SD card with 512 GB. My flatpaks take a substantial amount of space and I'd like to move the place where they're stored to the SD card (/dev/mmcblk0p1). But according to https://docs.flatpak.org/en/latest/tips-and-tricks.html#adding-a-custom-installation and https://man7.org/linux/man-pages/man5/flatpak-installation.5.html this needs root, which is discouraged to do manually. I'd like Discover to have a setting option for this as suggested here by a flatpak contributor: https://github.com/flatpak/flatpak/issues/1224#issuecomment-1310764573 -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 464394] [develop.kde.org] Breeze icon browser doesn't work
https://bugs.kde.org/show_bug.cgi?id=464394 --- Comment #4 from Thiago Sueto --- Alexander did a merge request (https://invent.kde.org/documentation/develop-kde-org/-/merge_requests/375) that is now merged, but it didn't cause any changes to https://develop.kde.org/frameworks/breeze-icons/. My guess is it's because the CI needs to be updated to run icon_extractor.py before deploying the website? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 482985] Konsole ignores the \e[0;1m reset code
https://bugs.kde.org/show_bug.cgi?id=482985 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #6 from Thiago Sueto --- > it produces horrible results with programs such as Paru. > (https://imgur.com/a/GEgGI8V) That was intentional. Whether you personally disliked the color or not, you can see how the paru output now actually makes each step clear and the most important information easy to find now. Pretty sure before it was all white with pretty much no distinction at all, maybe at most bold IIRC. > First check whether the environment is set and then don't override that. This sounds like a possible fix if I understand correctly, yes. > Is it possible to discuss to revert this? I'd much rather fix the actual issue, the fact that the palette overrides custom colors set manually by the user / ignores the reset code. Reverting this would be just a temporary paliative that doesn't fix the issue. Especially given we already provide custom palettes and let users set the intense color themselves. As a workaround you can do yourself, you can set Foreground Intense Color back to white (255,255,255), which was the original default anyway. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 484276] New: Impossible to Ctrl + click on absolute file paths
https://bugs.kde.org/show_bug.cgi?id=484276 Bug ID: 484276 Summary: Impossible to Ctrl + click on absolute file paths Classification: Applications Product: konsole Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- SUMMARY Konsole and Yakuake only accept Ctrl + click for urls (https://) and x-scheme-handlers (file://). It should be possible to use Ctrl + click for absolute paths too. As a workaround, it's possible to just make all file paths directly clickable by going to Edit Current Profile -> Mouse -> Miscellaneous -> Underline files, but that's not ideal. The reason for reporting this is that I want to make this tip here better: https://develop.kde.org/docs/getting-started/building/kdesrc-build-tips/ , the idea being that the user doesn't need to set anything by default and can just Ctrl+click. kdesrc-build used to use file:// URLs so they were clickable with Ctrl, but now it uses absolute paths instead. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 483816] Since updating to plasma 6, screenshot from external screen are blurry
https://bugs.kde.org/show_bug.cgi?id=483816 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484264] New: Activating Overview via keyboard shortcut immediately after desktop switching does not show Overview
https://bugs.kde.org/show_bug.cgi?id=484264 Bug ID: 484264 Summary: Activating Overview via keyboard shortcut immediately after desktop switching does not show Overview Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- SUMMARY If you have multiple virtual desktops and switch between them with Meta+Ctrl+arrow and then immediately activate Overview with Meta+W, Overview does not show up. The desktop sliding animation probably blocks it for a few moments. Overview runs fine if you wait a couple seconds first. STEPS TO REPRODUCE 1. Meta+Ctrl+arrow to switch desktop 2. Meta+W to activate Overview OBSERVED RESULT Overview does not show up. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240319 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-1-default (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 484088] Editing a reply that includes a quote adds a mangled copy of it into the message text
https://bugs.kde.org/show_bug.cgi?id=484088 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 483164] New: Web shortcuts do not show icons
https://bugs.kde.org/show_bug.cgi?id=483164 Bug ID: 483164 Summary: Web shortcuts do not show icons Classification: Plasma Product: krunner Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: webshortcuts Assignee: plasma-b...@kde.org Reporter: herzensch...@gmail.com CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY When attempting to use any web shortcut, the icon that was supposed to show up in the listing to the left side of the query is missing. STEPS TO REPRODUCE 1. Alt+Space to open KRunner 2. Try "google: blep" OBSERVED RESULT No icon next to query. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240308 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.7-1-default (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 Manufacturer: Dell Inc. Product Name: Inspiron 5567 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 482590] kdiff3 segfaults when used with git mergetool
https://bugs.kde.org/show_bug.cgi?id=482590 --- Comment #2 from Thiago Sueto --- My kdiff3 version is: kdiff3 1.11.70 (64 bit) I'm on openSUSE Krypton with Plasma 6, but isma mentioned experiencing this bug in Plasma 5 before. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 482590] New: kdiff3 segfaults when used with git mergetool
https://bugs.kde.org/show_bug.cgi?id=482590
Bug ID: 482590
Summary: kdiff3 segfaults when used with git mergetool
Classification: Applications
Product: kdiff3
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: application
Assignee: reeves...@gmail.com
Reporter: herzensch...@gmail.com
Target Milestone: ---
Attempting to run git mergetool while having kdiff3 installed to resolve
conflicts for a rebase causes kdiff3 to segfault with output like this:
```
This message is displayed because 'merge.tool' is not configured.
See 'git mergetool --tool-help' or 'git help config' for more details.
'git mergetool' will now attempt to use one of the following tools:
opendiff kdiff3 tkdiff xxdiff meld tortoisemerge gvimdiff diffuse diffmerge
ecmerge p4merge araxis bc codecompare smerge emerge vimdiff nvimdiff
Merging:
README.md
Normal merge conflict for 'README.md':
{local}: modified file
{remote}: modified file
Hit return to start merge resolution tool (kdiff3):
/usr/libexec/git/mergetools/kdiff3: line 11: 22393 Segmentation fault
(core dumped) "$merge_tool_path" --auto --L1 "$MERGED (Base)" --L2 "$MERGED
(Local)" --L3 "$MERGED (Remote)" -o "$MERGED" "$BASE" "$LOCAL" "$REMOTE" >
/dev/null 2>&1
merge of README.md failed
```
Running kdiff3 separately runs just fine.
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-systemmonitor] [Bug 482167] New: Default refresh interval is too fast
https://bugs.kde.org/show_bug.cgi?id=482167 Bug ID: 482167 Summary: Default refresh interval is too fast Classification: Applications Product: plasma-systemmonitor Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: herzensch...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- I'd like a more reasonable refresh interval for plasma-systemmonitor. Currently it updates at about half a second or less. Or as the "Minimum time between updates" setting says: "No limit". Fast graphical refresh intervals are a well known way to get an application to use too much CPU, and this issue becomes even worse in conjunction with https://bugs.kde.org/show_bug.cgi?id=429152 (Graphs can consume excessive CPU resources on platforms with weak Intel GPUs and high-resolution displays). A system monitor should be lightweight and quick to process, and thus reliable when the machine is under stress, it shouldn't be using as many hardware resources as it does. The default should be something more reasonable, probably something between the range of 1s to 2s. 1.5s is probably the best compromise. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 482164] New: No way to set a global custom refresh interval
https://bugs.kde.org/show_bug.cgi?id=482164 Bug ID: 482164 Summary: No way to set a global custom refresh interval Classification: Applications Product: plasma-systemmonitor Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: herzensch...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Currently to set the refresh interval on plasma-systemmonitor, you need to go to Edit Page, click on the graph/table you want to change, and alter "Minimum time between updates". The default refresh interval is unreasonably fast (half a second or less?) so I wanted to decrease its speed, but I had to go to each graph/table on each page to alter everything. I'd like a global setting for this. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kquickcharts] [Bug 429152] Graphs can consume excessive CPU resources on platforms with weak Intel GPUs and high-resolution displays
https://bugs.kde.org/show_bug.cgi?id=429152 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #11 from Thiago Sueto --- I have the same Intel UHD Graphics 620 and I also have a Radeon R7 M445 as dGPU on my laptop, and the CPU usage results are still bad for me on Plasma 6: starts at 15%, stabilizes between 8%-13% with a max peak of 17%. Reducing the refresh times of all elements on the page does not help. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480737] Crash upon running kcm_lookandfeel on openSUSE Krypton (Plasma 6)
https://bugs.kde.org/show_bug.cgi?id=480737 Thiago Sueto changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480737] New: Crash upon running kcm_lookandfeel on openSUSE Krypton (Plasma 6)
https://bugs.kde.org/show_bug.cgi?id=480737 Bug ID: 480737 Summary: Crash upon running kcm_lookandfeel on openSUSE Krypton (Plasma 6) Classification: Applications Product: systemsettings Version: master Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: kcm_lookandfeel Assignee: plasma-b...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- SUMMARY Segmentation fault when running systemsettings kcm_lookandfeel SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240131 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.7.2-1-default (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i7-5500U CPU @ 2.40GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 Manufacturer: Dell Inc. Product Name: Inspiron 7348 System Version: A13 BACKTRACE Thread 15 (Thread 0x7fffe34006c0 (LWP 12956) "QQmlThread"): #0 QQmlPropertyCacheCreator::propertyCacheForObject (error=0x7fffe33feaf8, context=..., obj=0x7fffc052e948, this=0x7fffe33ff1d0) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/build/include/QtQml/6.6.1/QtQml/private/../../../../../../src/qml/jsruntime/qv4resolvedtypereference_p.h:90 #1 QQmlPropertyCacheCreator::buildMetaObjectRecursively (this=this@entry=0x7fffe33ff1d0, objectIndex=22, context=..., isVMERequired=isVMERequired@entry=QQmlPropertyCacheCreator::VMEMetaObjectIsRequired::Maybe) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/build/include/QtQml/6.6.1/QtQml/private/../../../../../../src/qml/qml/qqmlpropertycachecreator_p.h:277 #2 0x7635d297 in QQmlPropertyCacheCreator::buildMetaObjectRecursively (this=this@entry=0x7fffe33ff1d0, objectIndex=20, context=..., isVMERequired=isVMERequired@entry=QQmlPropertyCacheCreator::VMEMetaObjectIsRequired::Maybe) at /usr/include/qt6/QtCore/qendian.h:258 #3 0x7635d297 in QQmlPropertyCacheCreator::buildMetaObjectRecursively (this=this@entry=0x7fffe33ff1d0, objectIndex=13, context=..., isVMERequired=isVMERequired@entry=QQmlPropertyCacheCreator::VMEMetaObjectIsRequired::Maybe) at /usr/include/qt6/QtCore/qendian.h:258 #4 0x7635d297 in QQmlPropertyCacheCreator::buildMetaObjectRecursively (this=this@entry=0x7fffe33ff1d0, objectIndex=1, context=..., isVMERequired=isVMERequired@entry=QQmlPropertyCacheCreator::VMEMetaObjectIsRequired::Maybe) at /usr/include/qt6/QtCore/qendian.h:258 #5 0x7635d297 in QQmlPropertyCacheCreator::buildMetaObjectRecursively (this=0x7fffe33ff1d0, objectIndex=0, context=..., isVMERequired=) at /usr/include/qt6/QtCore/qendian.h:258 #6 0x763535ef in QQmlPropertyCacheCreator::buildMetaObjectsIncrementally (this=0x7fffe33ff1d0) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/build/include/QtQml/6.6.1/QtQml/private/../../../../../../src/qml/qml/qqmlpropertycachecreator_p.h:223 #7 QQmlTypeCompiler::compile (this=0x7fffe33ff440) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/qqmltypecompiler.cpp:62 #8 0x763638f0 in QQmlTypeData::compile(QQmlRefPointer const&, QV4::ResolvedTypeReferenceMap*, std::function const&) (dependencyHasher=..., resolvedTypeCache=0x7fffe33ff370, typeNameCache=..., this=) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/qqmltypedata.cpp:852 #9 QQmlTypeData::done (this=) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/qqmltypedata.cpp:502 #10 0x762a8f3b in QQmlDataBlob::tryDone (this=0x5588b390) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/qqmldatablob.cpp:485 #11 QQmlDataBlob::tryDone (this=0x5588b390) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/qqmldatablob.cpp:476 #12 0x76371410 in QQmlTypeLoader::setData (this=this@entry=0x559b28b0, blob=..., d=...) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/qqmltypeloader.cpp:415 #13 0x76371c1a in QQmlTypeLoader::setData (this=this@entry=0x559b28b0, blob=..., fileName=...) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/qqmltypeloader.cpp:395 #14 0x76375655 in QQmlTypeLoader::loadThread (this=0x559b28b0, blob=...) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/qqmltypeloader.cpp:260 #15 0x763796c5 in QQmlThread::createMessageFromMethod const&), QQmlRefPointer const&>(void (QQmlTypeLoaderThread::*&&)(QQmlRefPointer const&), QQmlRefPointer const&)::I::call(QQmlThread*) () at /usr/include/c++/13/bits/invoke.h:71 #16 0x76279054 in QQmlThreadPrivate::threadEvent (this=0x557fa1e0) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/ftw/qqmlthread.cpp:148 #17 QQmlThreadPrivate::event (this=0x557fa1e0, e=0x55e61320) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/ftw/qqmlthread.cpp:105 #18 0x000
[frameworks-kio] [Bug 191632] It should be easier to add a template to "Create New..." menu (e.g. look into ~/Templates)
https://bugs.kde.org/show_bug.cgi?id=191632 Thiago Sueto changed: What|Removed |Added CC||codestr...@posteo.org --- Comment #11 from Thiago Sueto --- *** Bug 412657 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 412657] Make it easier to add new items to the File > "Create New" menu
https://bugs.kde.org/show_bug.cgi?id=412657 Thiago Sueto changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED CC||herzensch...@gmail.com --- Comment #2 from Thiago Sueto --- *** This bug has been marked as a duplicate of bug 191632 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 191632] It should be easier to add a template to "Create New..." menu (e.g. look into ~/Templates)
https://bugs.kde.org/show_bug.cgi?id=191632 Thiago Sueto changed: What|Removed |Added CC||jagannatha...@gmail.com --- Comment #10 from Thiago Sueto --- *** Bug 400263 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 400263] Better workflow for creating template files
https://bugs.kde.org/show_bug.cgi?id=400263 Thiago Sueto changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED CC||herzensch...@gmail.com --- Comment #3 from Thiago Sueto --- *** This bug has been marked as a duplicate of bug 191632 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476166] Unable to change user avatar in Plasma 6
https://bugs.kde.org/show_bug.cgi?id=476166 Thiago Sueto changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476166] New: Unable to change user avatar in Plasma 6
https://bugs.kde.org/show_bug.cgi?id=476166 Bug ID: 476166 Summary: Unable to change user avatar in Plasma 6 Classification: Applications Product: systemsettings Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_users Assignee: plasma-b...@kde.org Reporter: herzensch...@gmail.com CC: uhh...@gmail.com Target Milestone: --- SUMMARY Attempting to change the user avatar fails. STEPS TO REPRODUCE 1. Go to the Users KCM 2. Click on the current avatar icon 3. Click on the option to select a new file 4. Choose the file and confirm the dialog OBSERVED RESULT The dialog closes as though nothing happened, showing the avatar icon list. EXPECTED RESULT The avatar should be updated. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.6.0 Kernel Version: 6.5.8-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Plasma 6 was compiled with kdesrc-build. This is a clean compile, from scratch, using simple kdesrc-build workspace. Running System Settings from the terminal, I see two relevant errors. The first when opening the avatar list: qrc:/qt/qml/org/kde/kirigamiaddons/components/Avatar.qml:201:9: QML QQuickImage: Cannot open: file:///home/blumen/.face?0 The second after clicking ok in the dialog: qrc:/kcm/kcm_users/PicturesSheet.qml:137: Error: Cannot assign [undefined] to QUrl -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 475056] [Plasma 6] Deleting and recreating a command keyboard shortcut generates a new .desktop file every time
https://bugs.kde.org/show_bug.cgi?id=475056 Thiago Sueto changed: What|Removed |Added Summary|Deleting and recreating a |[Plasma 6] Deleting and |command keyboard shortcut |recreating a command |generates a new .desktop|keyboard shortcut generates |file every time |a new .desktop file every ||time -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 475056] Deleting and recreating a command keyboard shortcut generates a new .desktop file every time
https://bugs.kde.org/show_bug.cgi?id=475056 Thiago Sueto changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 475056] New: Deleting and recreating a command keyboard shortcut generates a new .desktop file every time
https://bugs.kde.org/show_bug.cgi?id=475056
Bug ID: 475056
Summary: Deleting and recreating a command keyboard shortcut
generates a new .desktop file every time
Classification: Frameworks and Libraries
Product: frameworks-kglobalaccel
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdelibs-b...@kde.org
Reporter: herzensch...@gmail.com
Target Milestone: ---
SUMMARY
If you create a new keyboard shortcut that triggers a command, assign it a
shortcut (so it appears in ~/.config/kglobalshortcutsrc), delete it, and
recreate it, it generates a new .desktop file in ~/.local/share/applications
following the naming scheme executable{,-1,-2,-3,...,-n}.desktop.
The curious thing is that the entries in ~/.config/kglobalshortcutsrc do
disappear fine when you delete a shortcut, it's just the .desktop file that
doesn't.
So if the user keeps testing to figure whether a command works well or not,
they might end up with several redundant .desktop files.
STEPS TO REPRODUCE
1. Go to Shortcuts -> Add Command...
2. Create a new command /usr/bin/kdialog --msgbox "Sup"
3. Assign a shortcut to it, for example, Meta+K
4. Click Apply
5. Verify that ~/.config/kglobalshortcutsrc contains a kdialog entry, it should
point to kdialog.desktop
6. Delete the shortcut via System Settings
7. Create a new one that also uses kdialog
8. Verify that ~/.config/kglobalshortcutsrc contains a kdialog entry, it should
point to kdialog-2.desktop
OBSERVED RESULT
Every time you recreate the shortcut, a new desktop entry gets added to
~/.local/share/applications without removing the original.
EXPECTED RESULT
Every time you delete the shortcut, the original desktop entry gets deleted,
and every time you create a new shortcut using the same executable, the new
desktop entry reuses its name.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 472114] The sidebar doesn't show subcategories or it gets too small depending on window size
https://bugs.kde.org/show_bug.cgi?id=472114 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 231867] Group view should allow a field other than the title to be shown
https://bugs.kde.org/show_bug.cgi?id=231867 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #4 from Thiago Sueto --- I recently created a custom collection with Tellico and removed the Title field, instead using a more descriptive field called Repository. Now the Group view will show groups but not the name of each record, showing a list filled with empty items. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473922] Meta+number does not work on Plasma 6
https://bugs.kde.org/show_bug.cgi?id=473922 Thiago Sueto changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473922] New: Meta+number does not work on Plasma 6
https://bugs.kde.org/show_bug.cgi?id=473922 Bug ID: 473922 Summary: Meta+number does not work on Plasma 6 Classification: Plasma Product: plasmashell Version: master Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: herzensch...@gmail.com CC: qydwhotm...@gmail.com Target Milestone: 1.0 Trying to open/go to applications pinned to the panel does not work with the Meta/Super/Win + number shortcut. Running: qdbus6 org.kde.kglobalaccel /component/plasmashell org.kde.kglobalaccel.Component.invokeShortcut "activate task manager entry 1" Also does not work, for any entry, despite the fact that something like: qdbus6 org.kde.kglobalaccel /component/plasmashell org.kde.kglobalaccel.Component.invokeShortcut "show-on-mouse-pos" Does work. I also noticed that the new kglobalacceld is not actually running as a systemd service or directly from the command line, it just exits normally immediately after execution, with no stdout. systemctl status --user plasma-kglobalaccel.service (which is supposed to run kglobalacceld) says Active: inactive (dead), despite its logs saying: Starting KDE Global Shortcuts Server... Started KDE Global Shortcuts Server. Deleting kglobalshortcutsrc, khotkeysrc or kwinrc and restarting makes no difference. This is from Plasma 6 compiled with kdesrc-build yesterday (28/08). I compiled both kglobalaccel and kglobalacceld for good measure, no difference. I'm not sure if this is a bug in plasmashell or kglobalacceld. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470900] "More options" menu does not fit to 1366x768 screen
https://bugs.kde.org/show_bug.cgi?id=470900 --- Comment #7 from Thiago Sueto --- Created attachment 160410 --> https://bugs.kde.org/attachment.cgi?id=160410&action=edit Panel on the side. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470900] "More options" menu does not fit to 1366x768 screen
https://bugs.kde.org/show_bug.cgi?id=470900 --- Comment #6 from Thiago Sueto --- Created attachment 160409 --> https://bugs.kde.org/attachment.cgi?id=160409&action=edit Panel at the top. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470900] "More options" menu does not fit to 1366x768 screen
https://bugs.kde.org/show_bug.cgi?id=470900 --- Comment #5 from Thiago Sueto --- Created attachment 160408 --> https://bugs.kde.org/attachment.cgi?id=160408&action=edit Panel at the bottom. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470900] "More options" menu does not fit to 1366x768 screen
https://bugs.kde.org/show_bug.cgi?id=470900 Thiago Sueto changed: What|Removed |Added Status|RESOLVED|REOPENED CC||herzensch...@gmail.com Resolution|FIXED |--- --- Comment #4 from Thiago Sueto --- This isn't fixed for me. Just compiled Plasma 6 the other day. The additional options available when in Edit Mode are unusable in 1366x768 screens unless you use the panel on the sides. I'll add screenshots. When at the top, it's impossible to see anything useful in the options menu. When at the bottom, it's impossible to delete panels. When on the sides, the options dialog (?) unnecessarily takes all available space. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 465485] Use OpenURI for attachments
https://bugs.kde.org/show_bug.cgi?id=465485 Thiago Sueto changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||herzensch...@gmail.com --- Comment #3 from Thiago Sueto --- Can confirm. In fact, the clickable attachment text at the top of the email (next to to, from, date), when clicked, shows this "Open With" window containing only Kontact apps, whereas the bottom section that is especially made for attachments simply doesn't do anything when clicked. Is KMail doing anything different than what's mentioned in https://docs.flatpak.org/en/latest/portals.html#portal-support-in-qt-and-kde ? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 465440] Using Page.contentItem causes the layout to use the available space behind headerbar
https://bugs.kde.org/show_bug.cgi?id=465440 --- Comment #3 from Thiago Sueto --- Created attachment 158721 --> https://bugs.kde.org/attachment.cgi?id=158721&action=edit Cards go behind the headerbar when using Page.contentItem. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 465440] Using Page.contentItem causes the layout to use the available space behind headerbar
https://bugs.kde.org/show_bug.cgi?id=465440 Thiago Sueto changed: What|Removed |Added Summary|Cards spawn behind |Using Page.contentItem |headerbar when the Page's |causes the layout to use |contentItem is set |the available space behind ||headerbar -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468077] It's now harder to draw an unfilled circle/ellipse/square/rectangle
https://bugs.kde.org/show_bug.cgi?id=468077 --- Comment #10 from Thiago Sueto --- (In reply to Stefan from comment #9) > If this is something usable, I'd love to finish it. But would need some > guidance, review and advice. Would that be possible? Hello Stefan, just send an MR to the Spectacle project. :) This way * other people will know there's someone working on this * the other devs can better assist you by reviewing the code -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 464239] Bookmark menu opens dropdown in a new window if application launcher is open
https://bugs.kde.org/show_bug.cgi?id=464239 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #3 from Thiago Sueto --- To be more precise, this happens when Konsole is not currently focused. Just having another application open and focused and then clicking on Bookmarks is enough to trigger the bug. This seems to only happen with this specific menu. Given https://community.kde.org/Guidelines_and_HOWTOs/Wayland_Porting_Notes#Popup_Menus it might be worth checking how the parent is being set for the bookmark menu specifically? -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 469066] New: Allow to disable message previews when hovering over groups/contacts list
https://bugs.kde.org/show_bug.cgi?id=469066 Bug ID: 469066 Summary: Allow to disable message previews when hovering over groups/contacts list Classification: Applications Product: NeoChat Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: herzensch...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- I don't really care about hovering over contacts or groups to check the last message in a conversation most of the time, I just open that conversation instead. If the preview has two lines, it blocks view of the contact/group just above in the list. And there's a weird bug (probably not in Neochat) where if the previewed last message is long enough, the tooltip displaying the preview extends behind the cursor, making opening conversations difficult. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 469064] New: Add a template for QRC files
https://bugs.kde.org/show_bug.cgi?id=469064 Bug ID: 469064 Summary: Add a template for QRC files Classification: Applications Product: kdevelop Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- In Qt6 there's qt_add_qml_module() which I prefer, but for Qt5 you need to copy a template for .qrc files every time you need to make one. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 469026] Searching for "iso" doesn't find "Popsicle"
https://bugs.kde.org/show_bug.cgi?id=469026 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 466855] No option to reverse order
https://bugs.kde.org/show_bug.cgi?id=466855 Thiago Sueto changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||herzensch...@gmail.com --- Comment #1 from Thiago Sueto --- Can confirm. Sorting by reverse order is needed to listen to podcasts with specialized topics (for example, language learning podcasts) or serialized podcasts (where you follow a story from episode to episode, particularly popular for criminology podcasts). Examples: Deutsche Welle - Warum Nicht? https://www.dw.com/de/deutsch-warum-nicht/s-2235 Good Serialized Podcasts https://www.podchaser.com/lists/good-serialized-podcasts-107a97Ze7c True Crime Podcasts https://www.stylist.co.uk/entertainment/podcasts/best-true-crime-podcasts/244331 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426047] Various KCMs randomly crash in their destructors when switching to a different KCM
https://bugs.kde.org/show_bug.cgi?id=426047 --- Comment #42 from Thiago Sueto --- I haven't been able to reproduce this since 2020 when I reported this if I'm not misremembering. Can confirm I can't reproduce this in either X11 or Wayland with current openSUSE Tumbleweed and on MicroOS Desktop Plasma. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468476] New: KCM doesn't show name of third party theme if it uses metadata.json instead of metadata.desktop
https://bugs.kde.org/show_bug.cgi?id=468476
Bug ID: 468476
Summary: KCM doesn't show name of third party theme if it uses
metadata.json instead of metadata.desktop
Classification: Applications
Product: systemsettings
Version: 5.27.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: kcm_desktoptheme
Assignee: plasma-b...@kde.org
Reporter: herzensch...@gmail.com
Target Milestone: ---
Very easy to reproduce:
Create a file ~/.local/share/plasma/desktopthemes/electrostorm/metadata.json
with the following contents:
{
"KPlugin": {
"Authors": [
{
"Name": "A Plasma Theme Designer",
"Email": "my@mail.address",
}
],
"Name": "Electrostorm",
"Description": "Brings a very dynamic electrical energy atmosphere to
the desktop",
"Id": "electrostorm",
"Version": "0.1",
"Category": "",
"EnabledByDefault": true,
"License": "GPL",
"Website": ""
},
"X-Plasma-API": "5.0"
}
It will show up with an empty name in System Settings -> Appearance -> Plasma
Style. You don't even need any other file to reproduce.
The equivalent metadata.desktop shows up correctly:
[Desktop Entry]
Name=Electrostorm
Comment=Brings a very dynamic electrical energy atmosphere to the desktop
X-KDE-PluginInfo-Author=A Plasma Theme Designer
X-KDE-PluginInfo-Email=my@mail.address
X-KDE-PluginInfo-Name=electrostorm
X-KDE-PluginInfo-Version=0.1
X-KDE-PluginInfo-Website=
X-KDE-PluginInfo-License=GPL
X-Plasma-API=5.0
--
You are receiving this mail because:
You are watching all bug changes.
[Spectacle] [Bug 468077] It's now harder to draw an unfilled circle/ellipse/square/rectangle
https://bugs.kde.org/show_bug.cgi?id=468077 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 468393] New: Experimental Konsole flatpak: cannot open a new tab with a different profile
https://bugs.kde.org/show_bug.cgi?id=468393 Bug ID: 468393 Summary: Experimental Konsole flatpak: cannot open a new tab with a different profile Classification: Applications Product: konsole Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- In the kdeapps flatpak repository, there's an experimental Konsole flatpak that can be tested. It runs the host shell just fine, possibly because of https://invent.kde.org/packaging/flatpak-kde-applications/-/commit/3806b155aace455be639a2cf61d5be271ec24bdf. It cannot open new tabs with a different profile when I go to File -> New Tab -> select profile. This works with non-flatpak Konsole/Yakuake even under weird circumstances like those mentioned in https://bugs.kde.org/show_bug.cgi?id=468391 where I can run a different profile that runs distrobox. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 468391] New: Konsole should be able to switch to/from a distrobox profile
https://bugs.kde.org/show_bug.cgi?id=468391 Bug ID: 468391 Summary: Konsole should be able to switch to/from a distrobox profile Classification: Applications Product: konsole Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- SUMMARY Distrobox is a tool used to run podman/docker containers and integrate them in userspace. See: https://github.com/89luca89/distrobox It comes in MicroOS Desktop by default and I think also Fedora Kinoite. In these distros, you're expected to never install anything to your host root, only to install userspace applications as flatpaks and using terminal tools from inside a distrobox container. One cool thing people can do is to make a custom terminal profile that runs and enters a distrobox container, then setting it as the default profile, so it's immediately ready as soon as you open your terminal. I use this with both Konsole and Yakuake. See: https://github.com/89luca89/distrobox/blob/main/docs/useful_tips.md#using-distrobox-as-main-cli By default, using a distrobox profile breaks the Konsole SSH plugin, but I managed to work around this by enveloping distrobox in a shell (I use fish in the container): /usr/bin/bash -c "distrobox enter mycontainer -- fish --login" So the only thing that I think is missing from the UX is being able to switch from/to distrobox profiles, but this doesn't work. Right clicking and attempting to change the profile does nothing. This only works if I go to File -> New Tab -> select a different profile, but this sounds more like a workaround for the fact Konsole can't switch to/from distrobox. FWIW, GNOME Terminal isn't able to switch from/to distrobox either, and it doesn't even have an option to create a new tab running a specific profile, so Konsole is way better off than it. But it would be great to have this functionality. STEPS TO REPRODUCE 1. Install podman + distrobox 2. Create a distrobox container with distrobox create 3. Create a Konsole profile that runs /usr/bin/distrobox enter 4. Right click the terminal and attempt to switch to a distrobox profile OR 3. Create a Konsole profile that runs /usr/bin/distrobox enter and make it the default 4. Right click the terminal and attempt to switch away from the distrobox profile -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 420529] "Background activity" notification appears while an app installed via flatpak/flathub is running
https://bugs.kde.org/show_bug.cgi?id=420529 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #22 from Thiago Sueto --- https://www.reddit.com/r/kde/comments/11ul75n/comment/jcrlzdu/?utm_source=share&utm_medium=web2x&context=3 > I once had this popup on one of my applications packaged as Flatpak as well. > From my testing on KDE it seems to get triggered when an application - > launched as Flatpak loses focus and / or has a tray icon - doesn't implement > the xdg background portal. > As for my app, I implemented xdg background portal using libportal and that > popup went away. This indeed seems to happen on an individual app basis. Telegram and KSnip work correctly and only trigger the notification when they're *closed* to the tray. Other apps do not work correctly. Additionally, this bug can lead to destructive behavior that I found out in the MicroOS Desktop channel: Firefox triggers this notification, and if the user clicks on Learn More and then select the option to stop it from running in the background, Firefox simply closes, and every time it gets opened again, it's immediately closed. The only way to revert the operation is by using Flatseal, going to the app's Portal settings and either clicking the cleanup/undo icon or allowing the app to run in the background. The Flatpak KCM lacks these settings, last I saw. So this is hard for users to find out, and if they cannot find this, they become incapable of reopening the application. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdoctools] [Bug 467128] New: kde-no-chunk.xsl and kde-web.xsl do not work
https://bugs.kde.org/show_bug.cgi?id=467128 Bug ID: 467128 Summary: kde-no-chunk.xsl and kde-web.xsl do not work Classification: Frameworks and Libraries Product: frameworks-kdoctools Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: herzensch...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Manually setting the --stylesheet used for meinproc5 to these two styles does not work, the resulting content does not display properly. -- You are receiving this mail because: You are watching all bug changes.
[docs.kde.org] [Bug 467029] Web-Page part of Website is down! [ 404 Error ]
https://bugs.kde.org/show_bug.cgi?id=467029 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #2 from Thiago Sueto --- develop.kde.org got some major restructuring (it's now flatter and we have no Use, Extend, Build and Deploy, and this bug report was made after the fact. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466325] New: No way to enable/disable apps running in the background
https://bugs.kde.org/show_bug.cgi?id=466325 Bug ID: 466325 Summary: No way to enable/disable apps running in the background Classification: Applications Product: systemsettings Version: 5.27.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_flatpak Assignee: plasma-b...@kde.org Reporter: herzensch...@gmail.com CC: joshiesuha...@gmail.com Target Milestone: --- When a flatpak app is running in the background (e.g. as a tray icon once the main window is closed) on Wayland, a notification shows up asking if the user wants to keep it running in the background or not. You can test this with Telegram or KSnip, a notification shows up once you press the X close button and it goes to the tray. If the user disallows the app from running in the background, they can easily revert this setting using Flatseal (it's one of the last options at the bottom of the page), but they cannot with the Flatpak KCM. This is particularly problematic when combined with a separate but destructive issue where applications notify they're running in the background when they're actually not (this is the case with Firefox, for instance), so the notification appears when the window is still in the foreground. Once the user disallows Firefox from running in the background, the moment they try to open it, it closes again, making it impossible to use. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461399] In overview effect, Virtual Desktops are shown as flattened arrangement, but spatial arrangement is preserved from the perspective of using the touchpad switching gestures
https://bugs.kde.org/show_bug.cgi?id=461399 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465716] New: Support for synchronized lyrics file in the same folder
https://bugs.kde.org/show_bug.cgi?id=465716 Bug ID: 465716 Summary: Support for synchronized lyrics file in the same folder Classification: Applications Product: Elisa Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: herzensch...@gmail.com Target Milestone: --- Currently Elisa already does synchronized lyrics that are embedded into the Lyrics id3 tag. Apparently the same formatting used for synchronized lyrics in the Lyrics id3 tag is used for LRC files: https://en.wikipedia.org/wiki/LRC_(file_format), so if you copy the contents of an LRC file and put it into the song metadata with Kid3 it shows up in Elisa. Usually, when a music player supports LRC files, you just need to have an LRC file in the same folder as the song. It would be nice if Elisa supported this. If you want to test this with an LRC file, you can use Android's LRC Editor on a certain song or I can supply one. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 460260] On a multi screen setup on Wayland, KDE app windows do not remember the size they had if the primary monitor is not the leftmost one.
https://bugs.kde.org/show_bug.cgi?id=460260 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #16 from Thiago Sueto --- The exact behavior of this bug happens like the following for me: = 1: Primary monitor on the right : Left is external screen, Right is laptop screen Resize in right and close in right = FORGOTTEN Resize in right and close in left = REMEMBER Resize in left and close in left = REMEMBER Resize in left and close in right = REMEMBER 2: Primary monitor on the left : Left is external screen, Right is laptop screen Resize in right and close in right = FORGOTTEN Resize in right and close in left = REMEMBER Resize in left and close in left = REMEMBER Resize in left and close in right = REMEMBER --- 1: Primary monitor on the right : Left is laptop screen, Right is external monitor Resize in right and close in right = FORGOTTEN Resize in right and close in left = REMEMBER Resize in left and close in left = REMEMBER Resize in left and close in right = REMEMBER 2: Primary monitor on the left : Left is laptop screen, Right is external monitor Resize in right and close in right = FORGOTTEN Resize in right and close in left = REMEMBER Resize in left and close in left = REMEMBER Resize in left and close in right = REMEMBER = I rebooted every time I changed the primary screen or moved the screen to the other side. The conclusion I arrive here is that primary monitor is indeed not what matters, like deafpolygon noted. Additionally, whether the screen is internal or external does not matter. In my case, the bug only happens when you resize and close the app in the right screen, no matter which one it is. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 465553] New: konsoleprofiles widget does not show default readonly profile as an option, only custom ones
https://bugs.kde.org/show_bug.cgi?id=465553 Bug ID: 465553 Summary: konsoleprofiles widget does not show default readonly profile as an option, only custom ones Classification: Plasma Product: kdeplasma-addons Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: konsoleprofiles Assignee: plasma-b...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- SUMMARY The widget's list of Konsole profiles does not show the Built-in profile as an option. STEPS TO REPRODUCE 1. Add a widget to the panel 2. Click it OBSERVED RESULT No profile named "Built-in". EXPECTED RESULT The "Built-in" profile should show up. SOFTWARE/OS VERSIONS Operating System: openSUSE MicroOS 20230208 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.10-1-default (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 465446] Card.banner breaks when using headerOrientation: Qt.Horizontal
https://bugs.kde.org/show_bug.cgi?id=465446 --- Comment #1 from Thiago Sueto --- It works only with an image. To test, simply add the following to the banner (or any other icon): source: "https://kde.org/stuff/clipart/logo/kde-logo-white-blue-rounded-128x128.png"; -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 465445] headerOrientation: Qt.Horizontal is missing left margin of header when used in a Kirigami.Card
https://bugs.kde.org/show_bug.cgi?id=465445 Thiago Sueto changed: What|Removed |Added Summary|headerOrientation is|headerOrientation: |missing left margin of |Qt.Horizontal is missing |header when used in a |left margin of header when |Kirigami.Card |used in a Kirigami.Card -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 465446] New: Card.banner breaks when using headerOrientation: Qt.Horizontal
https://bugs.kde.org/show_bug.cgi?id=465446 Bug ID: 465446 Summary: Card.banner breaks when using headerOrientation: Qt.Horizontal Classification: Frameworks and Libraries Product: frameworks-kirigami Version: 5.102.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: herzensch...@gmail.com CC: notm...@gmail.com Target Milestone: Not decided Created attachment 156048 --> https://bugs.kde.org/attachment.cgi?id=156048&action=edit Image of a Card with broken banner See the reproducible example attached. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 465445] headerOrientation is missing left margin of header when used in a Kirigami.Card
https://bugs.kde.org/show_bug.cgi?id=465445 Thiago Sueto changed: What|Removed |Added Attachment #156046|0 |1 is obsolete|| --- Comment #1 from Thiago Sueto --- Created attachment 156047 --> https://bugs.kde.org/attachment.cgi?id=156047&action=edit Image showing how a Card with headerOrientation makes the header lose its left margin. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 465445] New: headerOrientation is missing left margin of header when used in a Kirigami.Card
https://bugs.kde.org/show_bug.cgi?id=465445 Bug ID: 465445 Summary: headerOrientation is missing left margin of header when used in a Kirigami.Card Classification: Frameworks and Libraries Product: frameworks-kirigami Version: 5.102.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: herzensch...@gmail.com CC: notm...@gmail.com Target Milestone: Not decided Created attachment 156046 --> https://bugs.kde.org/attachment.cgi?id=156046&action=edit Image showing how a Card with headerOrientation makes the header lose its left margin. The attached file can be run in qmlscene to reproduce the issue. Just change the Card to an AbstractCard to see how it should look like. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 465440] Cards spawn behind headerbar when the Page's contentItem is set
https://bugs.kde.org/show_bug.cgi?id=465440 --- Comment #2 from Thiago Sueto --- Created attachment 156037 --> https://bugs.kde.org/attachment.cgi?id=156037&action=edit Card inside a Page.contentItem -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 465440] Cards spawn behind headerbar when the Page's contentItem is set
https://bugs.kde.org/show_bug.cgi?id=465440 --- Comment #1 from Thiago Sueto --- Created attachment 156036 --> https://bugs.kde.org/attachment.cgi?id=156036&action=edit Card inside a Layout that's inside a Page.contentItem -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 465440] New: Cards spawn behind headerbar when the Page's contentItem is set
https://bugs.kde.org/show_bug.cgi?id=465440 Bug ID: 465440 Summary: Cards spawn behind headerbar when the Page's contentItem is set Classification: Frameworks and Libraries Product: frameworks-kirigami Version: 5.102.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: herzensch...@gmail.com CC: notm...@gmail.com Target Milestone: Not decided See the examples, they can be run with qmlscene. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 450869] PageRow API documentation return 404 on api.kde.org
https://bugs.kde.org/show_bug.cgi?id=450869 Thiago Sueto changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||herzensch...@gmail.com --- Comment #2 from Thiago Sueto --- The PageRow API page is now fixed: https://invent.kde.org/frameworks/kapidox/-/merge_requests/31 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 464429] Kirigami ScrollablePage has empty space above content when refreshing
https://bugs.kde.org/show_bug.cgi?id=464429 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Thiago Sueto --- Reproducible with Kirigami 5.102. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465121] New: Hangs / freeze on Wayland when opening/closing apps
https://bugs.kde.org/show_bug.cgi?id=465121 Bug ID: 465121 Summary: Hangs / freeze on Wayland when opening/closing apps Classification: Plasma Product: kwin Version: 5.26.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- SUMMARY Since a few versions ago I've been experiencing a few hangs / freezes when closing apps. Only now did I get logs for it. Here's the error message from `sudo journalctl -f` (lapinetouch is the machine hostname): fev 01 11:12:55 lapinetouch kernel: Asynchronous wait on fence :00:02.0:kwin_wayland[1936]:6330 timed out (hint:intel_atomic_commit_ready [i915]) fev 01 11:12:55 lapinetouch kernel: Asynchronous wait on fence :00:02.0:kwin_wayland[1936]:632e timed out (hint:intel_atomic_commit_ready [i915]) fev 01 11:12:59 lapinetouch kernel: i915 :00:02.0: [drm] GPU HANG: ecode 8:0: fev 01 11:12:59 lapinetouch kernel: i915 :00:02.0: [drm] Resetting rcs0 for stopped heartbeat on rcs0 STEPS TO REPRODUCE Open or close a lot windows at a time, eventually you can reproduce the issue SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230118 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.6-1-vanilla (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i7-5500U CPU @ 2.40GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 Manufacturer: Dell Inc. Product Name: Inspiron 7348 System Version: A13 ADDITIONAL INFORMATION Just today a user on reddit mentioned a similar thing with the same log message: https://www.reddit.com/r/kde/comments/10qquun/comment/j6rs0dk/?utm_source=share&utm_medium=web2x&context=3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 465096] New: When GlobalDrawer isMenu: true, calling open() still opens the drawer instead of the menu
https://bugs.kde.org/show_bug.cgi?id=465096 Bug ID: 465096 Summary: When GlobalDrawer isMenu: true, calling open() still opens the drawer instead of the menu Classification: Frameworks and Libraries Product: frameworks-kirigami Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: herzensch...@gmail.com CC: notm...@gmail.com Target Milestone: Not decided This might not be a valid bug since the user is expected to open the drawer by clicking its button, but I noticed that if a global drawer shows up as a menu, calling its open() function causes it to still show up as a global drawer, but in a inactive/disabled state. The expected behavior would be that the menu is opened instead. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 465054] QtQuick Controls Button does not inherit from Kirigami.Theme when using Kirigami.Theme.inherit: true
https://bugs.kde.org/show_bug.cgi?id=465054 Thiago Sueto changed: What|Removed |Added Summary|QtQuick Controls Button |QtQuick Controls Button |does not inherit from |does not inherit from |Kirigami.Theme |Kirigami.Theme when using ||Kirigami.Theme.inherit: ||true -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 465054] New: QtQuick Controls Button does not inherit from Kirigami.Theme
https://bugs.kde.org/show_bug.cgi?id=465054 Bug ID: 465054 Summary: QtQuick Controls Button does not inherit from Kirigami.Theme Classification: Frameworks and Libraries Product: frameworks-kirigami Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: herzensch...@gmail.com CC: notm...@gmail.com Target Milestone: Not decided Created attachment 155800 --> https://bugs.kde.org/attachment.cgi?id=155800&action=edit Kirigami.Theme.inherit example from Colors tutorial. When attempting to reproduce the example from https://develop.kde.org/docs/use/kirigami/style-colors/#color-set, it seems QQC2.Buttons don't inherit from Kirigami.Theme. The code example is added as an attachment. It can be run with qmlscene. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 465053] New: Global Drawer gets attached to the mouse after clicking an action that contains nested actions
https://bugs.kde.org/show_bug.cgi?id=465053 Bug ID: 465053 Summary: Global Drawer gets attached to the mouse after clicking an action that contains nested actions Classification: Frameworks and Libraries Product: frameworks-kirigami Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: herzensch...@gmail.com CC: notm...@gmail.com Target Milestone: Not decided Created attachment 155799 --> https://bugs.kde.org/attachment.cgi?id=155799&action=edit Global Drawer example from Actions tutorial. When attempting to reproduce the example from https://develop.kde.org/docs/use/kirigami/introduction-actions/, I found a bug in how the global drawer behaves when using actions that contain nested actions. The code example is added as an attachment. It can be run with qmlscene. STEPS TO REPRODUCE * Open global drawer on the upper left side * Click View * Move the mouse from the right to the left OBSERVED RESULT * The global drawer opens and attaches to the mouse movement EXPECTED RESULT * The global drawer simply opens -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 465052] New: CardsGridView has no padding on the left side
https://bugs.kde.org/show_bug.cgi?id=465052 Bug ID: 465052 Summary: CardsGridView has no padding on the left side Classification: Frameworks and Libraries Product: frameworks-kirigami Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: herzensch...@gmail.com CC: notm...@gmail.com Target Milestone: Not decided Created attachment 155798 --> https://bugs.kde.org/attachment.cgi?id=155798&action=edit CardGridView example from Kirigami Gallery tutorial. When attempting to reproduce the example in https://develop.kde.org/docs/use/kirigami/introduction-kirigami-gallery/ , the result lacks left padding between the cards and the left side of the window. The code example is added as an attachment. It can be run with qmlscene. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 464394] [develop.kde.org] Breeze icon browser doesn't work
https://bugs.kde.org/show_bug.cgi?id=464394 --- Comment #1 from Thiago Sueto --- So the breeze-icons page seems to be linked to from https://develop.kde.org/design/. This same issue also happens with https://develop.kde.org/frameworks/oxygen-icons/, but it is not linked to anywhere on Develop. The source code is in https://invent.kde.org/documentation/develop-kde-org/-/tree/master/content/frameworks, out of which the Kirigami page works fine, perhaps these two were moved at some point? The readme mentions that for this to work one needs to run scripts/icon_extractor.py , https://invent.kde.org/documentation/develop-kde-org#extract-icon-metadata , so I'm guessing this is a thing for the KDE Web team or for the people handling the CI that generates the website. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 464222] New: KMainWindow: autoSaveGroup() and autoSaveConfigGroup() are too easy to misuse
https://bugs.kde.org/show_bug.cgi?id=464222 Bug ID: 464222 Summary: KMainWindow: autoSaveGroup() and autoSaveConfigGroup() are too easy to misuse Classification: Frameworks and Libraries Product: frameworks-kxmlgui Version: 5.101.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- While I was taking a look at the KMainWindow documentation, I found out that both KMainWindow::autoSaveGroup() and KMainWindow::autoSaveConfigGroup() can only be used with setAutoSaveSettings(QString&, bool). Attempting to use them with setAutoSaveSettings(KConfigGroup&, bool) causes a segmentation fault. If this is intentional, then this API is too easy to misuse and probably needs a naming change or something else. If this isn't intentional, it's a bug. Either way, I mentioned this in the new documentation fixes. It was already mentioned for autoSaveGroup(), but autoSaveConfigGroup() didn't mention this requirement before, which was rather dangerous. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 463251] When no central widget is set, the Help menu generates a button to activate KCommandBar, which when clicked makes the application segfault
https://bugs.kde.org/show_bug.cgi?id=463251 Thiago Sueto changed: What|Removed |Added Summary|When no central widget is |When no central widget is |set, the Help menu |set, the Help menu |autogenerates a button to |generates a button to |activate KCommandBar, which |activate KCommandBar, which |makes the application |when clicked makes the |segfault|application segfault -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 463251] New: When no central widget is set, the Help menu autogenerates a button to activate KCommandBar, which makes the application segfault
https://bugs.kde.org/show_bug.cgi?id=463251 Bug ID: 463251 Summary: When no central widget is set, the Help menu autogenerates a button to activate KCommandBar, which makes the application segfault Classification: Frameworks and Libraries Product: frameworks-kxmlgui Version: 5.101.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- Result of running the following in an example program where simply not having a central widget causes the activation of KCommandBar to crash the application: gdb ./build/kxmlguiwindowexample -batch -ex "set debuginfod enabled on" -ex "set logging file kxmlguiwindowlog.txt" -ex "set logging on" -ex "run" -ex "thread apply all backtrace" -ex "quit" [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x711ff6c0 (LWP 1760)] [New Thread 0x7fffebfff6c0 (LWP 1765)] [New Thread 0x7fffe37fe6c0 (LWP 1766)] [New Thread 0x7fffe994d6c0 (LWP 1796)] [New Thread 0x7fffe914c6c0 (LWP 1797)] [New Thread 0x7fffe894b6c0 (LWP 1798)] [New Thread 0x7fffe3fff6c0 (LWP 1799)] [New Thread 0x7fffe2ffd6c0 (LWP 1800)] [New Thread 0x7fffe27fc6c0 (LWP 1801)] [Thread 0x7fffe27fc6c0 (LWP 1801) exited] [Thread 0x7fffe2ffd6c0 (LWP 1800) exited] Thread 1 "kxmlguiwindowex" received signal SIGSEGV, Segmentation fault. QWidget::pos (this=0x0) at kernel/qwidget.cpp:3413 3413QPoint result = data->crect.topLeft(); Thread 8 (Thread 0x7fffe3fff6c0 (LWP 1799) "kxmlguiwin:sh2"): #0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x4e8218) at futex-internal.c:57 #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x4e8218, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #2 0x7509008f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x4e8218, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #3 0x75092cd0 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x4e81c8, cond=0x4e81f0) at pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x4e81f0, mutex=0x4e81c8) at pthread_cond_wait.c:618 #5 0x7fffe9cbaa5b in cnd_wait (mtx=0x4e81c8, cond=0x4e81f0) at ../src/c11/impl/threads_posix.c:135 #6 util_queue_thread_func (input=input@entry=0x4e9690) at ../src/util/u_queue.c:287 #7 0x7fffe9d03f27 in impl_thrd_routine (p=) at ../src/c11/impl/threads_posix.c:67 #8 0x7509398d in start_thread (arg=) at pthread_create.c:442 #9 0x7511a380 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 7 (Thread 0x7fffe894b6c0 (LWP 1798) "kxmlguiwin:sh1"): #0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x4e8218) at futex-internal.c:57 #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x4e8218, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #2 0x7509008f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x4e8218, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #3 0x75092cd0 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x4e81c8, cond=0x4e81f0) at pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x4e81f0, mutex=0x4e81c8) at pthread_cond_wait.c:618 #5 0x7fffe9cbaa5b in cnd_wait (mtx=0x4e81c8, cond=0x4e81f0) at ../src/c11/impl/threads_posix.c:135 #6 util_queue_thread_func (input=input@entry=0x4e9220) at ../src/util/u_queue.c:287 #7 0x7fffe9d03f27 in impl_thrd_routine (p=) at ../src/c11/impl/threads_posix.c:67 #8 0x7509398d in start_thread (arg=) at pthread_create.c:442 #9 0x7511a380 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 6 (Thread 0x7fffe914c6c0 (LWP 1797) "kxmlguiwin:sh0"): #0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x4e8218) at futex-internal.c:57 #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x4e8218, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #2 0x7509008f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x4e8218, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #3 0x7ff
[ktimetracker] [Bug 462785] New: Checkbox for tasks doesn't integrate with Breeze Dark
https://bugs.kde.org/show_bug.cgi?id=462785 Bug ID: 462785 Summary: Checkbox for tasks doesn't integrate with Breeze Dark Classification: Applications Product: ktimetracker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aspotas...@gmail.com Reporter: herzensch...@gmail.com Target Milestone: --- Created attachment 154432 --> https://bugs.kde.org/attachment.cgi?id=154432&action=edit Dark checkboxes in dark theme See attachment. -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 462784] New: Add monochrome tray icon for KTimeTracker
https://bugs.kde.org/show_bug.cgi?id=462784 Bug ID: 462784 Summary: Add monochrome tray icon for KTimeTracker Classification: Applications Product: ktimetracker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aspotas...@gmail.com Reporter: herzensch...@gmail.com Target Milestone: --- Pretty self explanatory. The current tray icon looks dated and doesn't match the current monochrome Breeze style used in the tray. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462311] Opening apps from overview will eventually crash kwin
https://bugs.kde.org/show_bug.cgi?id=462311 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #1 from Thiago Sueto --- Hello Uladzislau, currently this bug report is not actionable, we need a backtrace to do anything about it. Could you please follow the instructions in https://community.kde.org/KWin/Debuggin and https://fedoraproject.org/wiki/StackTraces and make a comment here with the backtrace? -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 461961] New: Add the Repeat button in the UI instead of the settings
https://bugs.kde.org/show_bug.cgi?id=461961 Bug ID: 461961 Summary: Add the Repeat button in the UI instead of the settings Classification: Applications Product: Haruna Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: herzensch...@gmail.com Target Milestone: --- There's a Repeat toggle in Settings > Configure > Playlist, but given its usefulness I think it should be shown directly as a button in the UI. Ideally with all three typical modes: Repeat One, Repeat All, Don't Repeat. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 444136] Konsole window upon reload has vertical height too small on my 3 monitor setup with panel in middle screen
https://bugs.kde.org/show_bug.cgi?id=444136 Thiago Sueto changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||herzensch...@gmail.com --- Comment #2 from Thiago Sueto --- This is still reproducible in Konsole 22.04.1, but it seems to be an X11 exclusive bug. You can test this with a RHEL 9 or Fedora 36 system, for instance. It doesn't happen when running as a Wayland window. It happens when running as an XWayland window, but only when there is no prior window size recorded in the konsolerc. It does not happen when running as an XWayland window after a window size is recorded in the konsolerc, window sizes are saved correctly. In the X11 session, if you delete the konsolerc file and open Konsole it shows up fine, but when it writes to the file it writes the same weird window sizes. Those seem to be arbitrary sizes. Given the mention of "Let applications remember their positions and sizes" which is a known source of issues on Xorg, perhaps it would make sense for a KWin dev to look into this. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 433276] Images are not displayed correctly in Klipper
https://bugs.kde.org/show_bug.cgi?id=433276 --- Comment #3 from Thiago Sueto --- Sorry, I meant I can reproduce this on Plasma 5.25.3 with Spectacle 22.04.1 and master. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 433276] Images are not displayed correctly in Klipper
https://bugs.kde.org/show_bug.cgi?id=433276 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Thiago Sueto --- I can reproduce this issue on both 5.25.3 and master. Possibly related Reddit post: https://www.reddit.com/r/kde/comments/w78dq1/where_was_the_option_to_enable_image_thumbnails/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450248] [Wayland] Displaying the window thumbnail in Task Manager is very performance-intensive and can cause the desktop to lag
https://bugs.kde.org/show_bug.cgi?id=450248 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 456593] plasma-wayland-protocol builds, but doesn't install properly
https://bugs.kde.org/show_bug.cgi?id=456593 Thiago Sueto changed: What|Removed |Added Summary|kdesrc-build uses |plasma-wayland-protocol |plasma-wayland-protocols|builds, but doesn't install |from system instead of |properly |built one | --- Comment #6 from Thiago Sueto --- Alexander Lohnau over #kde-devel assisted me with this issue, plasma-wayland-protocols did not install at all, so kguiaddons wasn't able to find kde/usr/lib64/cmake/PlasmaWaylandProtocols/PlasmaWaylandProtocolsConfig.cmake. I had to cd to kde/build/plasma-wayland-protocols and run `ninja install` manually. That it didn't install properly is clearly a bug, so I'm renaming this issue. I'm not sure if this would be a kdesrc-build bug or a plasma-wayland-protocols bug. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 456593] kdesrc-build uses plasma-wayland-protocols from system instead of built one
https://bugs.kde.org/show_bug.cgi?id=456593 --- Comment #5 from Thiago Sueto --- (system info I mean) -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 456593] kdesrc-build uses plasma-wayland-protocols from system instead of built one
https://bugs.kde.org/show_bug.cgi?id=456593 --- Comment #4 from Thiago Sueto --- Almost forgot, system requirements: Operating System: Red Hat Enterprise Linux 9.0 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.14.0-70.17.1.el9_0.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 456593] kdesrc-build uses plasma-wayland-protocols from system instead of built one
https://bugs.kde.org/show_bug.cgi?id=456593 --- Comment #3 from Thiago Sueto --- Created attachment 150542 --> https://bugs.kde.org/attachment.cgi?id=150542&action=edit refresh build error? -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 456593] kdesrc-build uses plasma-wayland-protocols from system instead of built one
https://bugs.kde.org/show_bug.cgi?id=456593 --- Comment #2 from Thiago Sueto --- Created attachment 150541 --> https://bugs.kde.org/attachment.cgi?id=150541&action=edit stderr and stdout of kdesrc-build command -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 456593] kdesrc-build uses plasma-wayland-protocols from system instead of built one
https://bugs.kde.org/show_bug.cgi?id=456593 --- Comment #1 from Thiago Sueto --- Created attachment 150540 --> https://bugs.kde.org/attachment.cgi?id=150540&action=edit kdesrc-buildrc -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 456593] New: kdesrc-build uses plasma-wayland-protocols from system instead of built one
https://bugs.kde.org/show_bug.cgi?id=456593 Bug ID: 456593 Summary: kdesrc-build uses plasma-wayland-protocols from system instead of built one Product: kdesrc-build Version: Git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mp...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- I followed the installation instructions in https://community.kde.org/Get_Involved/development#Set_up_kdesrc-build KGuiAddons fails to build because it's not finding the built plasma-wayland-protocols from master, it's instead attempting to use my system version (1.5.0): CMake Error at CMakeLists.txt:55 (find_package): Could not find a configuration file for package "PlasmaWaylandProtocols" that is compatible with requested version "1.7.0". The following configuration files were considered but not accepted: /usr/lib64/cmake/PlasmaWaylandProtocols/PlasmaWaylandProtocolsConfig.cmake, version: 1.5.0 /lib64/cmake/PlasmaWaylandProtocols/PlasmaWaylandProtocolsConfig.cmake, version: 1.5.0 I'll add my kdesrc-buildrc as attachment together with the stdout/stderr of running kdesrc-build plasma-desktop systemsettings krunner --include-dependencies. I also found it rather weird that trying to run --refresh-build still renders a message "No changes from build, skipping install (--refresh-build this module to force install)". I'll add this as an attachment too. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 372408] Option to omit shadow and transparent border from windows in Active Window and Window Under Cursor modes
https://bugs.kde.org/show_bug.cgi?id=372408 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
