[kscreenlocker] [Bug 493422] No longer possible to show clock on prompt but hide it when prompt is hidden
https://bugs.kde.org/show_bug.cgi?id=493422 --- Comment #2 from Be --- What is the use case for only showing the clock in the very specific situation after the mouse or keyboard have been touched? Turning the binary option into a three state option could do this, but I'm unclear what the purpose would be and if that would be worth the complexity in the code and preferences GUI. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 493239] New: crash logging in
/qml/ftw/qqmlrefcount_p.h:73 #70 0x76f9d195 in QQmlNotifier::emitNotify (endpoint=, a=0x0) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/qqmlnotifier.cpp:70 #71 0x749fc42d in doActivate (sender=0x5614b4e0, signal_index=37, argv=0x0) at /usr/src/debug/qt6-qtbase-6.7.2-6.fc40.x86_64/src/corelib/kernel/qobject.cpp:3976 #72 0x749f2bc7 in QMetaObject::activate (sender=sender@entry=0x5614b4e0, m=m@entry=0x722436e0 , local_signal_index=local_signal_index@entry=34, argv=argv@entry=0x0) at /usr/src/debug/qt6-qtbase-6.7.2-6.fc40.x86_64/src/corelib/kernel/qobject.cpp:4146 #73 0x72119577 in QQuickPopup::modalChanged (this=this@entry=0x5614b4e0) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/redhat-linux-build/src/quicktemplates/QuickTemplates2_autogen/include/moc_qquickpopup_p.cpp:1653 #74 0x7211fa6f in QQuickPopup::setModal (this=0x5614b4e0, modal=false) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/quicktemplates/qquickpopup.cpp:2102 #75 0x76f05a6b in QQmlPropertyData::writeProperty (this=, target=, value=, flags=...) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/qqmlpropertydata_p.h:336 #76 GenericBinding<1>::doStore (this=, value=, pd=, flags=...) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/qqmlbinding.cpp:275 #77 GenericBinding<1>::write (this=0x562f7c90, result=..., isUndefined=, flags=...) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/qqmlbinding.cpp:238 #78 0x76efdfe1 in QQmlBinding::doUpdate (this=0x562f7c90, watcher=..., flags=..., scope=...) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/qqmlbinding.cpp:701 #79 0x76f01d18 in QQmlBinding::update (this=0x562f7c90, flags=...) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/qqmlbinding.cpp:164 #80 0x76f9d195 in QQmlNotifier::emitNotify (endpoint=, a=0x0) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/qqmlnotifier.cpp:70 #81 0x749fc42d in doActivate (sender=0x5614b4e0, signal_index=49, argv=0x0) at /usr/src/debug/qt6-qtbase-6.7.2-6.fc40.x86_64/src/corelib/kernel/qobject.cpp:3976 #82 0x7212592f in QQuickPopupItem::itemChange (this=, change=QQuickItem::ItemEnabledHasChanged, data=...) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/quicktemplates/qquickpopupitem.cpp:283 #83 0x775fac04 in QQuickItemPrivate::itemChange (this=this@entry=0x561555f0, change=change@entry=QQuickItem::ItemEnabledHasChanged, data=...) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/quick/items/qquickitem.cpp:6866 #84 0x775fb4fa in QQuickItemPrivate::setEffectiveEnableRecur (this=0x561555f0, scope=0x0, newEffectiveEnable=) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/quick/items/qquickitem.cpp:6673 #85 0x76f05a6b in QQmlPropertyData::writeProperty (this=, target=, value=, flags=...) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/qqmlpropertydata_p.h:336 #86 GenericBinding<1>::doStore (this=, value=, pd=, flags=...) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/qqmlbinding.cpp:275 #87 GenericBinding<1>::write (this=0x562f5fb0, result=..., isUndefined=, flags=...) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/qqmlbinding.cpp:238 #88 0x76efdfe1 in QQmlBinding::doUpdate (this=0x562f5fb0, watcher=..., flags=..., scope=...) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/qqmlbinding.cpp:701 #89 0x76f01d18 in QQmlBinding::update (this=0x562f5fb0, flags=...) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/qqmlbinding.cpp:164 #90 0x76f9d195 in QQmlNotifier::emitNotify (endpoint=, a=0x0) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/qqmlnotifier.cpp:70 #91 0x749fc42d in doActivate (sender=0x5610ece0, signal_index=73, argv=0x0) at /usr/src/debug/qt6-qtbase-6.7.2-6.fc40.x86_64/src/corelib/kernel/qobject.cpp:3976 #92 0x76f9d195 in QQmlNotifier::emitNotify (endpoint=, a=0x0) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/qqmlnotifier.cpp:70 #93 0x749fc42d in doActivate (sender=0x7fff9002cf30, signal_index=40, argv=0x0) at /usr/src/debug/qt6-qtbase-6.7.2-6.fc40.x86_64/src/corelib/kernel/qobject.cpp:3976 #94 0x7fffb004c848 in ColumnView::visibleItemsChanged (this=0x0) at src/layouts/KirigamiLayouts_autogen/include/moc_columnview.cpp:1274 #95 ContentItem::updateVisibleItems (this=0x5613c710) at /home/be/kde/src/kirigami/src/layouts/columnview.cpp:728 #96 0x7fffb0047a63 in ContentItem::geometryChange (this=0x0, newGeometry=..., oldGeometry=...) at /home/be/kde/src/kirigami/src/layouts/columnview.cpp:896 #97 0x775f5dd6 in QQuickItem::setWidth (th
[systemsettings] [Bug 472587] Option to hide clock from login & lock screens *completely*
https://bugs.kde.org/show_bug.cgi?id=472587 --- Comment #11 from Be --- Note that the GUI for configuring hiding the clock from the login screen will be in 6.3, not 6.2. In 6.2, manually editing the SDDM theme's theme.conf.user file to change `showClock = true` to `showClock = false` should hide the clock. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472587] Option to hide clock from login & lock screens *completely*
https://bugs.kde.org/show_bug.cgi?id=472587 --- Comment #6 from Be --- Merge requests for login screen: https://invent.kde.org/plasma/sddm-kcm/-/merge_requests/74 https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/2366 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472587] Option to hide clock from login & lock screens *completely*
https://bugs.kde.org/show_bug.cgi?id=472587 Be changed: What|Removed |Added Assignee|plasma-b...@kde.org |b...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472587] Option to hide clock from login & lock screens *completely*
https://bugs.kde.org/show_bug.cgi?id=472587 --- Comment #5 from Be --- Merge requests for the lock screen: https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/2365 https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4499 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 479130] The QtMultimedia backend is severely broken
https://bugs.kde.org/show_bug.cgi?id=479130 --- Comment #9 from Be --- For anyone coming here encountering this bug in Fedora 40: the Elisa version 24.02.2 with the fix is already available in updates-testing. Run `dnf update --enablerepo=updates-testing elisa-player` to install it before it moves to the main updates repository. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472587] Option to hide clock from login & lock screens *completely*
https://bugs.kde.org/show_bug.cgi?id=472587 --- Comment #4 from Be --- After updating to KDE 6, the file /usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml is still there for the lock screen, but the file that needs editing for the login screen has moved to /usr/share/sddm/themes/breeze/Main.qml. In both cases, set the `visible` property to always `false` for the clock. I would like a proper solution to this that doesn't require me hacking QML files after package updates. SDDM is still around in KDE 6.0, but looking at https://invent.kde.org/plasma/plasma-desktop/-/issues/91 it seems its future in KDE is still unclear? In the meantime, changing the existing "Clock: Keep visible when unlocking prompt disappears" to a simple boolean toggle to show the clock on the lock screen could be done regardless of whatever happens with the display manager. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 486092] New: playback does not advance to next track in playlist
https://bugs.kde.org/show_bug.cgi?id=486092 Bug ID: 486092 Summary: playback does not advance to next track in playlist Classification: Applications Product: Elisa Version: 24.02.1 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: b...@gmx.com Target Milestone: --- SUMMARY Upon upgrading to KDE 6 / Fedora 40, Elisa will no longer advance playback to the next track in the playlist after any track finishes. STEPS TO REPRODUCE 1. Load any tracks into the playlist 2. Press play 3. Wait for the current track to finish, or seek towards the end of the track OBSERVED RESULT Elisa stops playing when the currently playing track finishes EXPECTED RESULT Elisa continues playing the rest of the playlist SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Tracks play fine when selecting them in the playlist; there's nothing wrong with the next track that's preventing playback. Changing repeat mode (none/playlist/track) doesn't do anything; Elisa won't play the next track regardless of the repeat mode. Shuffle mode doesn't make a difference either. I removed ~/.config/elisarc and ~/.local/share/elisa/elisaDatabase.db and restarted Elisa, but this did not fix the issue. Using pipewire-pulseaudio-1.0.5-1.fc40.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 429672] track progress/seek bar unusable at minimum window width
https://bugs.kde.org/show_bug.cgi?id=429672 --- Comment #3 from Be --- Hiding the volume slider is an interesting idea. Maybe collapse it to just an icon that pops out a vertical slider when pressed? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472587] option to hide clock from login & lock screens
https://bugs.kde.org/show_bug.cgi?id=472587 Be changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- Ever confirmed|0 |1 --- Comment #3 from Be --- As noted in the first comment, the existing configuration option has no effect on the login screen before logging in or starting to type on the lock screen. I don't know what the point of the existing option is or if it's really worthwhile to have it there. I suggest replacing it with a simple boolean toggle to hide the clock from both the login screen and lock screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472587] option to hide clock from login & lock screens
https://bugs.kde.org/show_bug.cgi?id=472587 --- Comment #1 from Be --- I also hacked the Clock component in /usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml to set the visible property to always `false` to hide the clock from the lock screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472587] New: option to hide clock from login & lock screens
https://bugs.kde.org/show_bug.cgi?id=472587 Bug ID: 472587 Summary: option to hide clock from login & lock screens Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Session Management Assignee: plasma-b...@kde.org Reporter: b...@gmx.com Target Milestone: 1.0 SUMMARY I would like to not have to see a clock when using my computer. This is already easy to configure in Plasma by removing the clock applet from the default panel, but there is still a clock on the login and lock screens. System Settings > Workspace Behavior > Screen Locking already has a boolean option "Clock: Keep visible when unlocking prompt disappears" but this has no effect on the login screen before logging in or starting to type on the lock screen. I have hacked my own quick solution to this by deleting the the labels from the QML in /usr/share/sddm/themes/breeze/components/Clock.qml but I would like a permanent solution that doesn't require editing code. ADDITIONAL INFORMATION It is currently unclear how Plasma will handle logins in the future: https://invent.kde.org/plasma/plasma-desktop/-/issues/91 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465965] blurry red-on-black and black-on-red text with high DPI scaling on Plasma Wayland with Intel UHD Graphics 770
https://bugs.kde.org/show_bug.cgi?id=465965 Be changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #11 from Be --- Well this is interesting. I tried plugging my monitor into my laptop (same software setup, Plasma Wayland with Fedora 37) with a USB-C to HDMI cable and couldn't reproduce the issue. Then I tried using the same cable with my desktop and couldn't reproduce the issue. Then I tried switching back to the HDMI to HDMI cable which reproduced the issue, fiddled around in the monitor's settings, and now the issue is gone. I'm not sure what changed. I think the issue when away when I enabled "game mode" on the monitor, but then I tried disabling it and couldn't reproduce it... anyway, it seems the problem was something in the monitor rather than my desktop computer. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465965] blurry red-on-black and black-on-red text with high DPI scaling on Plasma Wayland with Intel UHD Graphics 770
https://bugs.kde.org/show_bug.cgi?id=465965 --- Comment #10 from Be --- Are you able to see the difference with the photo rather than the screenshots? It's most prominent comparing the red "A" with the purple "A". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465965] blurry red-on-black and black-on-red text with high DPI scaling on Plasma Wayland with Intel UHD Graphics 770
https://bugs.kde.org/show_bug.cgi?id=465965 --- Comment #9 from Be --- Those screenshots were taken with Spectacle. I'm not sure if this bug can be captured by screenshots... which may hint that the bug is pretty low down in the graphics stack. FWIW, I'm using a Samsung QN32Q60AAFXZA 32 inch 3840 x 2160 monitor connected via HDMI. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465965] blurry red-on-black and black-on-red text with high DPI scaling on Plasma Wayland with Intel UHD Graphics 770
https://bugs.kde.org/show_bug.cgi?id=465965 --- Comment #7 from Be --- Created attachment 156403 --> https://bugs.kde.org/attachment.cgi?id=156403&action=edit close up photo of Konsole with red text on black I can see the blurriness when looking at the attached screenshots in Plasma Wayland, but not when viewing the screenshots in GNOME. So here is a close up photo of my monitor taken with my phone camera. Notice the jagged edges of the text "HEAD detatched at" compared to the surrounding text, particularly the rounded edges of "b" and "d" and the slanted edges of "A". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465965] blurry red-on-black and black-on-red text with high DPI scaling on Plasma Wayland with Intel UHD Graphics 770
https://bugs.kde.org/show_bug.cgi?id=465965 --- Comment #6 from Be --- I am unable to reproduce this with Weston or GNOME (Wayland) running the same applications. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465965] blurry red-on-black and black-on-red text with high DPI scaling on Plasma Wayland with Intel UHD Graphics 770
https://bugs.kde.org/show_bug.cgi?id=465965 --- Comment #5 from Be --- Created attachment 156399 --> https://bugs.kde.org/attachment.cgi?id=156399&action=edit Kate with Breeze Light (looks okay) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465965] blurry red-on-black and black-on-red text with high DPI scaling on Plasma Wayland with Intel UHD Graphics 770
https://bugs.kde.org/show_bug.cgi?id=465965 --- Comment #4 from Be --- Created attachment 156398 --> https://bugs.kde.org/attachment.cgi?id=156398&action=edit red text on white background in LibreOffice (looks okay) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465965] blurry red-on-black and black-on-red text with high DPI scaling on Plasma Wayland with Intel UHD Graphics 770
https://bugs.kde.org/show_bug.cgi?id=465965 --- Comment #3 from Be --- Created attachment 156397 --> https://bugs.kde.org/attachment.cgi?id=156397&action=edit red text on black background in LibreOffice -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465965] blurry red-on-black and black-on-red text with high DPI scaling on Plasma Wayland with Intel UHD Graphics 770
https://bugs.kde.org/show_bug.cgi?id=465965 --- Comment #2 from Be --- Created attachment 156396 --> https://bugs.kde.org/attachment.cgi?id=156396&action=edit black text on red background in LibreOffice -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465965] blurry red-on-black and black-on-red text with high DPI scaling on Plasma Wayland with Intel UHD Graphics 770
https://bugs.kde.org/show_bug.cgi?id=465965 --- Comment #1 from Be --- Created attachment 156395 --> https://bugs.kde.org/attachment.cgi?id=156395&action=edit Konsole with red text on black background -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465965] New: blurry red-on-black and black-on-red text with high DPI scaling on Plasma Wayland with Intel UHD Graphics 770
https://bugs.kde.org/show_bug.cgi?id=465965 Bug ID: 465965 Summary: blurry red-on-black and black-on-red text with high DPI scaling on Plasma Wayland with Intel UHD Graphics 770 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: b...@gmx.com Target Milestone: --- Created attachment 156394 --> https://bugs.kde.org/attachment.cgi?id=156394&action=edit Kate with Breeze Dark SUMMARY In Plasma Wayland sessions, the interface of red text on a dark background or dark text on a red background is blurry using my Intel UHD Graphics 770 when the screen scale factor is 200%. See attached screenshots. STEPS TO REPRODUCE 1. Log into Plasma Wayland session 2. Set monitor scale factor to 200% in Display and Monitor system settings 3. Open an application with red text OBSERVED RESULT Red text is blurry. EXPECTED RESULT Text scales smoothly. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.11-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 24 × 12th Gen Intel® Core™ i9-12900K Memory: 62.1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 770 Manufacturer: ASUS ADDITIONAL INFORMATION I am unable to reproduce this when using my GeForce RTX 3060 Lite Hash Rate, using Plasma X11, or setting the screen scale factor to 100%. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461427] Native Wayland apps appear blurry after switching off and on a display with scaling enabled
https://bugs.kde.org/show_bug.cgi?id=461427 Be changed: What|Removed |Added CC||b...@gmx.com --- Comment #2 from Be --- I am also running into this issue on Fedora. It first started occurring a few weeks ago on Fedora 36 when I installed Plasma 5.26 from Fedora's updates-testing repo. I was hoping it would be fixed when updating to Fedora 37, but alas, it is still happening. This only happens with Qt applications; Firefox, Thunderbird, Electron (Signal Desktop), and GTK (GNOME Calculator) are unaffected. I have a 3840 x 2160 screen that I use with my desktop. My laptop also has a 3840 x 2160 screen but is unaffected, so I suspect there is some setting which is contributing to this. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 342092] Space (%20) appended to the end of search strings passed to populate function of service scripts
https://bugs.kde.org/show_bug.cgi?id=342092 --- Comment #3 from Be --- Uh, Amarok is a dead project at this point. I'm surprised the bugs haven't all been closed already. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 184325] amarok wish: fetch lyrics from the ID3 lyrics tag
https://bugs.kde.org/show_bug.cgi?id=184325 Be changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #16 from Be --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 459682] New: kateprojectplugin.so undefined symbol error in AppImage
https://bugs.kde.org/show_bug.cgi?id=459682 Bug ID: 459682 Summary: kateprojectplugin.so undefined symbol error in AppImage Classification: Applications Product: kate Version: 22.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: b...@gmx.com Target Milestone: --- SUMMARY Using the AppImage, the Project Plugin fails to load. STEPS TO REPRODUCE 1. wget https://binary-factory.kde.org/job/Kate_Release_appimage-centos7/lastSuccessfulBuild/artifact/kate-22.08.1-637-linux-64-gcc.AppImage 2. chmod +x ./kate-22.08.1-637-linux-64-gcc.AppImage 3. ./kate-22.08.1-637-linux-64-gcc.AppImage 4. Settings -> Configure Kate -> Plugins -> check Project Plugin, click Ok OBSERVED RESULT kf.coreaddons: "Could not load plugin from /tmp/.mount_kate-2ZCrpA7/usr/plugins/ktexteditor/kateprojectplugin.so: Cannot load library /tmp/.mount_kate-2ZCrpA7/usr/plugins/ktexteditor/kateprojectplugin.so: (/lib64/libQt5Quick.so.5: undefined symbol: _ZN15QVulkanInstanceC1Ev, version Qt_5)" EXPECTED RESULT Project Plugin loads. SOFTWARE/OS VERSIONS release 22.08.01 AppImage on Fedora 36 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454779] QMenus mispositioned using Wayland QPA with multiple monitors when top edges of monitors are not aligned
https://bugs.kde.org/show_bug.cgi?id=454779 --- Comment #4 from Be --- Ping David, could you link to that upstream Qt bug? -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 454850] URIs are not encoded
https://bugs.kde.org/show_bug.cgi?id=454850 Be changed: What|Removed |Added Summary|URIs are not|URIs are not encoded -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 454850] New: URIs are not
https://bugs.kde.org/show_bug.cgi?id=454850 Bug ID: 454850 Summary: URIs are not Product: xdg-desktop-portal-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: b...@gmx.com CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- The documentation for the D-Bus API specifies several places where a URI is returned. However, the returned value is not URI encoded; spaces are still spaces rather than %20. The GNOME XDG Destop Portal backend does encode these URIs. This lead to me, as an application developer developing using KDE, neglecting to deal with URI encoding, producing code that only worked on KDE but not GNOME. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 36 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.17.11-300.fc36.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION https://codeberg.org/Be.ing/moire/issues/4 https://github.com/PolyMeilex/rfd/pull/70 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454779] QMenus mispositioned using Wayland QPA with multiple monitors when top edges of monitors are not aligned
https://bugs.kde.org/show_bug.cgi?id=454779 --- Comment #1 from Be --- Monitor scale factor does not affect this. The crucial aspect is whether the top edges of the monitors are aligned in Display Configuration. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454779] New: QMenus mispositioned using Wayland QPA with multiple monitors when top edges of monitors are not aligned
https://bugs.kde.org/show_bug.cgi?id=454779 Bug ID: 454779 Summary: QMenus mispositioned using Wayland QPA with multiple monitors when top edges of monitors are not aligned Product: kwin Version: 5.24.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: b...@gmx.com Target Milestone: --- Created attachment 149423 --> https://bugs.kde.org/attachment.cgi?id=149423&action=edit screenshot of mispositioned menu STEPS TO REPRODUCE 1. Connect external monitor 2. Start Plasma Wayland session 3. Open Display Configuration in System Settings 4. Drag representations of monitors such that their top edges are not aligned, click Apply 5. Open QWidgets application, for example Kate, and open a menu OBSERVED RESULT Menu is shown in an incorrect position, for example to the right side of the window EXPECTED RESULT Menu is shown at the clicked location SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Fedora 36 ADDITIONAL INFORMATION Workarounds: 1. Start Qt application with `-platform xcb` to run with XWayland (not great due to blurry high DPI scaling) 2. Align tops of monitors in Display Configuration I cannot reproduce this with GNOME Wayland, so it seems to be an issue in the interaction between KWin and Qt's Wayland QPA. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 107302] Per-screen virtual desktops
https://bugs.kde.org/show_bug.cgi?id=107302 Be changed: What|Removed |Added CC||b...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451158] Incorrect cursor scaling on wayland gtk apps
https://bugs.kde.org/show_bug.cgi?id=451158 Be changed: What|Removed |Added CC||b...@gmx.com --- Comment #2 from Be --- I am also running into this bug with kwin 5.24.5 on Fedora 36. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 441879] Randomize mode that picks random albums, not random tracks
https://bugs.kde.org/show_bug.cgi?id=441879 Be changed: What|Removed |Added CC||b...@gmx.com --- Comment #4 from Be --- Rather than shuffling by album within the current playlist, I'd like to have a sorting option for the albums grid that sorts randomly. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 450968] New: discard/revert lines and hunks in unstaged Git diffs
https://bugs.kde.org/show_bug.cgi?id=450968 Bug ID: 450968 Summary: discard/revert lines and hunks in unstaged Git diffs Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: b...@gmx.com Target Milestone: --- Currently there is only an option to discard all changes to an unstaged file when right clicking the file in the file list of the Git view. It would be nice to be able to discard specific lines and hunks within unstaged diffs to give finer control than discarding all changes in the file. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 433518] audio output does not work after restarting PulseAudio
https://bugs.kde.org/show_bug.cgi?id=433518 Be changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Be --- (In reply to Be from comment #1) > I took a quick look at how Elisa outputs audio and see it uses the very high > level QMediaPlayer class, so the bug might be upstream in Qt. Hmm, the error I originally reported showed an error from the VLC backend rather than QMediaPlayer. Anyway, I can't reproduce this anymore with Elisa 21.08.1, Pipewire 0.3.40, and Wireplumber 0.4.5. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 433518] audio output does not work after restarting PulseAudio
https://bugs.kde.org/show_bug.cgi?id=433518 --- Comment #1 from Be --- I took a quick look at how Elisa outputs audio and see it uses the very high level QMediaPlayer class, so the bug might be upstream in Qt. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 443026] segmentation fault when switching Git branches with clangd C++ LSP
https://bugs.kde.org/show_bug.cgi?id=443026 Be changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #5 from Be --- Unfortunately I am still getting this crash with the master branch (commit 82bb95cbbfe3f58639f35dce57582b52ee6b06ed). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 443026] segmentation fault when switching Git branches with clangd C++ LSP
https://bugs.kde.org/show_bug.cgi?id=443026 --- Comment #3 from Be --- Thanks for the quick fix! I confirm this is fixed in the master branch. I am glad I took the time to report the bug with a backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 443026] New: segmentation fault when switching Git branches with clangd C++ LSP
https://bugs.kde.org/show_bug.cgi?id=443026 Bug ID: 443026 Summary: segmentation fault when switching Git branches with clangd C++ LSP Product: kate Version: 21.08.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: b...@gmx.com Target Milestone: --- Created attachment 141959 --> https://bugs.kde.org/attachment.cgi?id=141959&action=edit backtrace of the crash STEPS TO REPRODUCE 1. Open C++ file 2. Switch Git branches OBSERVED RESULT Kate crashes EXPECTED RESULT Kate does not crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 KDE Plasma Version: 5.85.0 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Refer to the attached backtrace. There seems to be an infinite (or extremely deep) loop. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 433518] New: audio output does not work after restarting PulseAudio
https://bugs.kde.org/show_bug.cgi?id=433518 Bug ID: 433518 Summary: audio output does not work after restarting PulseAudio Product: elisa Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: b...@gmx.com Target Milestone: --- SUMMARY Elisa does not output audio if the PulseAudio server is restarted while Elisa is running. This occurs both with PulseAudio and pipewire-pulse. STEPS TO REPRODUCE 1. Play music in Elisa 2. Restart PulseAudio server 3. Try to play music in Elisa again OBSERVED RESULT Elisa behaves as if it can play audio (the play button works and the track position slider advances), but there is no audio output. EXPECTED RESULT Audio output reconnects when PulseAudio server is restarted. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 33 (available in About System) KDE Plasma Version: 5.78.0 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION PipeWire's console output repeatedly shows: [027a1590] vlcpulse audio output error: cannot write: Connection terminated when pressing play after restarting PulseAudio. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 432629] New: background parser crash
https://bugs.kde.org/show_bug.cgi?id=432629 Bug ID: 432629 Summary: background parser crash Product: kdevelop Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: b...@gmx.com Target Milestone: --- Application: kdevelop (5.6.40) Qt Version: 5.15.2 Frameworks Version: 5.78.0 Operating System: Linux 5.10.7-200.fc33.x86_64 x86_64 Windowing system: X11 Distribution: Fedora 33 (Workstation Edition) -- Information about the crash: - What I was doing when the application crashed: KDevelop was running the parser in the background. I did not have the KDevelop window visible. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Aborted [KCrash Handler] #4 0x7f181e6209d5 in raise () from /lib64/libc.so.6 #5 0x7f181e6098a4 in abort () from /lib64/libc.so.6 #6 0x7f181ebaa48f in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5 #7 0x7f181eba9894 in qt_assert(char const*, char const*, int) () from /lib64/libQt5Core.so.5 #8 0x7f17d122235a in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, QFlags, QHash&, QHash const&, KDevelop::IndexedString const&, ClangIndex*, std::function const&) (file=0x7f1742261df0, imports=..., session=..., features=..., includedFiles=..., unsavedRevisions=..., parseDocument=..., index=0x203b190, abortFunction=...) at ../plugins/clang/duchain/clanghelpers.cpp:163 #9 0x7f17d12d42c8 in ClangParseJob::run (this=0x861de20) at ../plugins/clang/clangparsejob.cpp:341 #10 0x7f18218b13ff in ThreadWeaver::IdDecorator::run(QSharedPointer, ThreadWeaver::Thread*) () from /lib64/libKF5ThreadWeaver.so.5 #11 0x7f18218b1dfb in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () from /lib64/libKF5ThreadWeaver.so.5 #12 0x7f18218b09b7 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () from /lib64/libKF5ThreadWeaver.so.5 #13 0x7f18218aef16 in ThreadWeaver::Thread::run() () from /lib64/libKF5ThreadWeaver.so.5 #14 0x7f181ebdfdf0 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #15 0x7f181da793f9 in start_thread () from /lib64/libpthread.so.0 #16 0x7f181e6e4903 in clone () from /lib64/libc.so.6 Thread 13 (Thread 0x7f17b15d9640 (LWP 10056) "Queue(0xd71f60)"): #1 0x7f17f779530f in llvm_execute_on_thread_impl(void* (*)(void*), void*, llvm::Optional, (anonymous namespace)::JoiningPolicy) [clone .isra.0] () from /lib64/libLLVM-11.so #2 0x7f17f7795436 in llvm::llvm_execute_on_thread(void (*)(void*), void*, llvm::Optional) () from /lib64/libLLVM-11.so #3 0x7f17f76c7d1b in llvm::CrashRecoveryContext::RunSafelyOnThread(llvm::function_ref, unsigned int) () from /lib64/libLLVM-11.so #4 0x7f17b2bb4799 in clang_parseTranslationUnit2FullArgv () from /lib64/libclang.so.11 #5 0x7f17b2bb488a in clang_parseTranslationUnit2 () from /lib64/libclang.so.11 #6 0x7f17d124014c in ParseSessionData::ParseSessionData (this=0x7f17a6905c10, unsavedFiles=..., index=0x203b190, environment=..., options=...) at ../plugins/clang/duchain/parsesession.cpp:327 #7 0x7f17d12d48e8 in ClangParseJob::createSessionData (this=0x8615d10) at ../plugins/clang/clangparsejob.cpp:387 #8 0x7f17d12d3cc7 in ClangParseJob::run (this=0x8615d10) at ../plugins/clang/clangparsejob.cpp:303 #9 0x7f18218b13ff in ThreadWeaver::IdDecorator::run(QSharedPointer, ThreadWeaver::Thread*) () from /lib64/libKF5ThreadWeaver.so.5 #10 0x7f18218b1dfb in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () from /lib64/libKF5ThreadWeaver.so.5 #11 0x7f18218b09b7 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () from /lib64/libKF5ThreadWeaver.so.5 #12 0x7f18218aef16 in ThreadWeaver::Thread::run() () from /lib64/libKF5ThreadWeaver.so.5 #13 0x7f181ebdfdf0 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #14 0x7f181da793f9 in start_thread () from /lib64/libpthread.so.0 #15 0x7f181e6e4903 in clone () from /lib64/libc.so.6 Thread 12 (Thread 0x7f17d1154640 (LWP 9874) "KDevelop::Compl"): #1 0x7f181cbc0d13 in g_main_context_check () from /lib64/libglib-2.0.so.0 #2 0x7f181cc1269d in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #3 0x7f181cbbdd43 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f181edc770b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f181ed7957b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f181ebdeb67 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f1821b108cf
[elisa] [Bug 431862] New: playlist shows horizontal scrollbar with long track titles
https://bugs.kde.org/show_bug.cgi?id=431862 Bug ID: 431862 Summary: playlist shows horizontal scrollbar with long track titles Product: elisa Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: b...@gmx.com Target Milestone: --- Created attachment 135028 --> https://bugs.kde.org/attachment.cgi?id=135028&action=edit screenshot of Elisa playlist with long track titles SUMMARY When a track with a title longer than the available width is in the playlist, Elisa shows a horizontal scrollbar for the playlist. However, this horizontal scrollbar doesn't actually let me scroll side to side; it only wastes vertical space. It is not possible to drag a splitter to resize the playlist to show the whole track title. Hovering the cursor over the track does show the full title. STEPS TO REPRODUCE 1. Load a track with a very long title into the playlist OBSERVED RESULT A horizontal scrollbar is shown at the bottom of the playlist EXPECTED RESULT I'm not sure what the best way to handle this would be. Should the playlist be resizable by the user? Should it automatically resize to accommodate the track title length? Should it just show the part of the track title that fits without a horizontal scrollbar? SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 33 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION see attached screenshot -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kfilemetadata] [Bug 431422] Elisa intermittently crashed in KFileMetaData::Property::Property() when fetching lyrics tag
https://bugs.kde.org/show_bug.cgi?id=431422 --- Comment #2 from Be --- In Elisa's preferences "Music indexing" defaulted to "Scan the filesystem directly". I tried switching that to "Use fast native indexer" but the crash still occurs. There is no pattern other than it happens at the end of tracks. It does not happen consistently with any particular files. AFAIK none of my files have lyrics tags. I just checked some files in Picard and did not see any lyrics tags. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 431422] New: intermittent crash when finishing playing a track
https://bugs.kde.org/show_bug.cgi?id=431422 Bug ID: 431422 Summary: intermittent crash when finishing playing a track Product: elisa Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: b...@gmx.com Target Milestone: --- Created attachment 134728 --> https://bugs.kde.org/attachment.cgi?id=134728&action=edit backtrace of the crash SUMMARY This crash occurs sometimes at the end of a track before starting to play the next one. See attached backtrace. SOFTWARE/OS VERSIONS Elisa: master branch, commit 422afda69bad7160f86c3d0607ab4487ccd94ce6 Linux: Fedora 33 KDE Frameworks Version: 5.78 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372774] crash redoing edits
https://bugs.kde.org/show_bug.cgi?id=372774 Be changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #2 from Be --- I have not encountered this recently. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 430133] New: middle panel and playlist not touch flickable
https://bugs.kde.org/show_bug.cgi?id=430133 Bug ID: 430133 Summary: middle panel and playlist not touch flickable Product: elisa Version: 20.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: b...@gmx.com Target Milestone: --- The middle panel and playlist are not flickable by touching and dragging. The "party mode" playlist is though. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 430099] UI for removing album from playlist
https://bugs.kde.org/show_bug.cgi?id=430099 --- Comment #2 from Be --- I agree that would be a good way to implement this. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 430099] New: UI for removing album from playlist
https://bugs.kde.org/show_bug.cgi?id=430099 Bug ID: 430099 Summary: UI for removing album from playlist Product: elisa Version: 20.08.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: b...@gmx.com Target Milestone: --- Removing an album from the playlist currently requires removing each track one by one, or alternatively replacing the whole playlist with another album. It should only take one click to remove an album from the playlist. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 429675] New: clicking tracks in "party mode" playlist does not start playback if no track is currently playing
https://bugs.kde.org/show_bug.cgi?id=429675 Bug ID: 429675 Summary: clicking tracks in "party mode" playlist does not start playback if no track is currently playing Product: elisa Version: 20.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: b...@gmx.com Target Milestone: --- SUMMARY Clicking tracks in "party mode" playlist does not start playback if no track is currently playing. STEPS TO REPRODUCE 1. Add tracks to playlist. Do not play any of them. 2. Enable party mode 3. Click tracks in party mode playlist OBSERVED RESULT Track does not start playing. EXPECTED RESULT Track starts playing. SOFTWARE/OS VERSIONS Elisa 20.08.3 Flatpak Fedora 33 with GNOME 3.38 -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 429672] New: track progress/seek bar unusable at minimum width
https://bugs.kde.org/show_bug.cgi?id=429672 Bug ID: 429672 Summary: track progress/seek bar unusable at minimum width Product: elisa Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: b...@gmx.com Target Milestone: --- Created attachment 133660 --> https://bugs.kde.org/attachment.cgi?id=133660&action=edit screenshot of Elisa at minimum width When the window is shrunk to its minimum width, the track progress/seek bar becomes unusably small. I suggest moving it to its own row below a certain window width. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 429671] New: file deletion UI
https://bugs.kde.org/show_bug.cgi?id=429671 Bug ID: 429671 Summary: file deletion UI Product: elisa Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: b...@gmx.com Target Milestone: --- It would be nice to be able to delete files and groups of files (albums, artists, genres) from Elisa. I'm not sure where this would fit into the UI well without making it too easy to click accidentally or too obtrustive. The View Details window for tracks could be a place to add a button. Also the top right of the album view in the middle pane could be a good place. Of course, this should have a confirmation dialog before deleting the files. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 429670] New: seldomly played albums
https://bugs.kde.org/show_bug.cgi?id=429670 Bug ID: 429670 Summary: seldomly played albums Product: elisa Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: b...@gmx.com Target Milestone: --- A feature I really like in Lollypop is the "Seldomly played albums" view. I prefer this to searching music I have recently played. It reminds me of music that I love but have not listened to in a long time. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 428442] New: preferences window is too tall for 768 px high screen
https://bugs.kde.org/show_bug.cgi?id=428442 Bug ID: 428442 Summary: preferences window is too tall for 768 px high screen Product: kdevelop Version: 5.6.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: b...@gmx.com Target Milestone: --- Created attachment 132869 --> https://bugs.kde.org/attachment.cgi?id=132869&action=edit screenshot of preferences Running KDevelop on my old laptop with a 1366 x 768 px screen, the preferences window is too tall so the bottom buttons get cut off. See attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 419889] New: popup notification when build finishes
https://bugs.kde.org/show_bug.cgi?id=419889 Bug ID: 419889 Summary: popup notification when build finishes Product: kdevelop Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: b...@gmx.com Target Milestone: --- It would be a nice feature if KDevelop popped up a desktop notification when a build finishes so I don't have to keep watching it. If this would be annoying for some, maybe a preference option could disable it. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 403484] many classes not resolved by C++ indexer
https://bugs.kde.org/show_bug.cgi?id=403484 Be changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Be --- Thank you for investigating. Yes, Fedora 29 ships Clang 7. I downloaded the AppImage and these errors no longer appear. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 403484] New: many classes not resolved by C++ indexer
https://bugs.kde.org/show_bug.cgi?id=403484 Bug ID: 403484 Summary: many classes not resolved by C++ indexer Product: kdevelop Version: 5.3.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: b...@gmx.com Target Milestone: --- SUMMARY Something is wrong with the C++ indexer in 5.3.1 but I'm not exactly sure what's going wrong. There are lots of classes that don't get resolved. I see errors like "member access to incomplete type" and other errors related to incomplete types even though the header file for that class is #included. When I open the header file for those classes which the indexer isn't resolving, there is a warning which says "Header is not guarded against multiple inclusions", which is wrong. I can get that warning to go away by clicking the refresh button in the Problems area, but when I switch to another file then switch back to that header, the erroneous warning comes back. I have tried reopening the project and clearing the cache (both multiple times), but the problem persists. This is a regression. KDevelop used to parse this code fine. I don't know what the last working version was. STEPS TO REPRODUCE 1. Download code from https://github.com/kshitij98/mixxx/tree/effects_refactoring 2. Set up KDevelop project as described at https://mixxx.org/wiki/doku.php/kdevelop 3. Open src/effects/effectslot.cpp OBSERVED RESULT lots of unresolved symbols EXPECTED RESULT All symbols resolved, able to use "show uses", "jump to declaration", and "jump to definition features" with accurate and complete results. SOFTWARE/OS VERSIONS GNOME 3.30.2 KDE Frameworks Version: 5.53 Qt Version: 5.11.1 OS: Fedora 29, using KDevelop package from Fedora -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 241032] Background parser uses up too much memory
https://bugs.kde.org/show_bug.cgi?id=241032 Be changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #5 from Be --- I provided the requested information but there was no a response before this bug expired. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 376350] Screenshots of single window can be sized wrongly
https://bugs.kde.org/show_bug.cgi?id=376350 --- Comment #2 from Be --- Created attachment 108890 --> https://bugs.kde.org/attachment.cgi?id=108890&action=edit Mixxx Preferences window another screenshot of the bug -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 376350] Screenshots of single window can be sized wrongly
https://bugs.kde.org/show_bug.cgi?id=376350 Be changed: What|Removed |Added CC||b...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378190] New: Xdebug support for PHP debugging
https://bugs.kde.org/show_bug.cgi?id=378190 Bug ID: 378190 Summary: Xdebug support for PHP debugging Product: kdevelop Version: 5.1.0 Platform: unspecified OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Language Support: PHP Assignee: kdevelop-bugs-n...@kde.org Reporter: b...@gmx.com Target Milestone: --- There was a plugin for supporting Xdebug for PHP debugging with kdevplatform 4, now hosted on GitHub: https://github.com/KDE/kdev-xdebug It would be great to bring Xdebug support back to KDevelop 5. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377389] background parser hogs memory and CPU while working with git
https://bugs.kde.org/show_bug.cgi?id=377389 --- Comment #2 from Be --- I'm using an old Intel Core i5 2410M with 4GB of RAM. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377389] New: background parser hogs memory and CPU while working with git
https://bugs.kde.org/show_bug.cgi?id=377389 Bug ID: 377389 Summary: background parser hogs memory and CPU while working with git Product: kdevelop Version: 5.0.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: code completion Assignee: kdevelop-bugs-n...@kde.org Reporter: b...@gmx.com Target Milestone: --- The background parser automatically starts as soon as I switch git branches. This makes it difficult to work with git while KDevelop is open. For example, when switching to another branch then merging a branch into that, the background parser will have to parse the project twice, but I only need it to run after I am done with a series of git operations. Stopping the background parsing after each step is not practical, as it slows down my system dramatically as soon as the background parser starts. I can think of two workarounds: 1. Add an action to KDevelop to suspend/resume background parsing that could be bound to a global keyboard shortcut. This would require the user to remember to use it before starting to work with git. 2. Add an optional timer to delay the start of the background parser. However, this could get annoying when all that the user needs to do is switch to a different branch. Related: https://bugs.kde.org/show_bug.cgi?id=241032 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 241032] Background parser uses up too much memory
https://bugs.kde.org/show_bug.cgi?id=241032 Be changed: What|Removed |Added CC||b...@gmx.com --- Comment #2 from Be --- I can reproduce on a computer with 4 GB of RAM using KDevelop 5.0.3 from the Fedora repository. Typical resident memory usage for KDevelop with the background parser is around 2.2 GB. I work on Mixxx which is a large C++ project. I have written instructions for setting up KDevelop to work on this project: http://mixxx.org/wiki/doku.php/kdevelop Before I turned on a swap partition KDevelop was unusable for me (sometimes Linux's out of memory killer kicked in). With a swap partition, it still slows down my system a lot; I cannot work with KDevelop, Firefox, Thunderbird, and Mixxx open simultaneously, let alone build Mixxx with all those open. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372774] New: crash redoing edits
https://bugs.kde.org/show_bug.cgi?id=372774 Bug ID: 372774 Summary: crash redoing edits Product: kdevelop Version: 5.0.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: b...@gmx.com Target Milestone: --- Application: kdevelop (5.0.2) Qt Version: 5.6.1 Frameworks Version: 5.27.0 Operating System: Linux 4.6.7-300.rt14.1.fc24.ccrma.x86_64+rt x86_64 Distribution: "Fedora release 24 (Twenty Four)" -- Information about the crash: - What I was doing when the application crashed: I was redoing edits on a JavaScript file by pressing Ctrl + Shift + Z The crash does not seem to be reproducible. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff8592b1940 (LWP 2617))] Thread 24 (Thread 0x7ff7daffd700 (LWP 4636)): #0 0x7ff86c865bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff86c32fbc4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7ff86c32fc09 in () at /lib64/libQt5Script.so.5 #3 0x7ff86c8605ca in start_thread () at /lib64/libpthread.so.0 #4 0x7ff8736130ed in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7ff7c30f6700 (LWP 2784)): #0 0x7ff87360756d in poll () at /lib64/libc.so.6 #1 0x7ff869f7da06 in g_main_context_iterate (priority=, n_fds=1, fds=0x7ff7b4002870, timeout=, context=0x7ff7b4000990) at gmain.c:4135 #2 0x7ff869f7da06 in g_main_context_iterate (context=context@entry=0x7ff7b4000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3835 #3 0x7ff869f7db1c in g_main_context_iteration (context=0x7ff7b4000990, may_block=1) at gmain.c:3901 #4 0x7ff87440d24b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7ff8743bc5ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7ff87421b343 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7ff8717f63cf in KDevelop::CompletionWorkerThread::run() () at /lib64/libKDevPlatformLanguage.so.10 #8 0x7ff87421f99a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7ff86c8605ca in start_thread () at /lib64/libpthread.so.0 #10 0x7ff8736130ed in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7ff7c8929700 (LWP 2780)): #0 0x7ff869fc1a09 in g_mutex_lock (mutex=mutex@entry=0x7ff7c4000990) at gthread-posix.c:1335 #1 0x7ff869f7cf65 in g_main_context_prepare (context=context@entry=0x7ff7c4000990, priority=priority@entry=0x7ff7c8928a70) at gmain.c:3444 #2 0x7ff869f7d92b in g_main_context_iterate (context=context@entry=0x7ff7c4000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3820 #3 0x7ff869f7db1c in g_main_context_iteration (context=0x7ff7c4000990, may_block=1) at gmain.c:3901 #4 0x7ff87440d24b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7ff8743bc5ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7ff87421b343 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7ff8717f63cf in KDevelop::CompletionWorkerThread::run() () at /lib64/libKDevPlatformLanguage.so.10 #8 0x7ff87421f99a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7ff86c8605ca in start_thread () at /lib64/libpthread.so.0 #10 0x7ff8736130ed in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7ff7dbfff700 (LWP 2772)): #0 0x7ff86c865bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff87422001a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7ff8706a68c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7ff8706aaa78 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7ff8706a5a3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7ff8706a8909 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7ff87421f99a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7ff86c8605ca in start_thread () at /lib64/libpthread.so.0 #8 0x7ff8736130ed in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7ff7fcff9700 (LWP 2771)): #0 0x7ff86c865bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff87422001a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7ff8706a68c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool
[amarok] [Bug 364354] Amarok stutters and hangs system before crashing
https://bugs.kde.org/show_bug.cgi?id=364354 Be changed: What|Removed |Added Resolution|BACKTRACE |FIXED --- Comment #6 from Be --- Whatever was causing this, it hasn't been an issue since upgrading to Fedora 24. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 369848] New: crash reopening KDevelop
https://bugs.kde.org/show_bug.cgi?id=369848 Bug ID: 369848 Summary: crash reopening KDevelop Product: kdevelop Version: 5.0.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: b...@gmx.com Application: kdevelop (5.0.0) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.6.7-300.rt11.1.fc24.ccrma.x86_64+rt x86_64 Distribution: "Fedora release 24 (Twenty Four)" -- Information about the crash: - What I was doing when the application crashed: Opening KDevelop. It seemed KDevelop closed normally last time, then it asked me to clear the cache when I reopened it, which I did. Thereafter, it crashed. I had a Wordpress project (PHP, CSS, JS) opened. The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f001fef6940 (LWP 18129))] Thread 14 (Thread 0x7effd700 (LWP 18276)): #0 0x7f003b007959 in QMutex::unlock() () at /lib64/libQt5Core.so.5 #1 0x7f003b1fbfe1 in postEventSourcePrepare(_GSource*, int*) () at /lib64/libQt5Core.so.5 #2 0x7f0030bc1f59 in g_main_context_prepare (context=context@entry=0x7effcc000990, priority=priority@entry=0x7effdfffeaa0) at gmain.c:3442 #3 0x7f0030bc292b in g_main_context_iterate (context=context@entry=0x7effcc000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3820 #4 0x7f0030bc2b1c in g_main_context_iteration (context=0x7effcc000990, may_block=1) at gmain.c:3901 #5 0x7f003b1fc24b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f003b1ab5ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f003b00a343 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f0038515fe3 in KDevelop::CompletionWorkerThread::run() (this=0x268fe40) at /home/be/sw/kde/extragear/kdevelop/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89 #9 0x7f003b00e99a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7f00334a65ca in start_thread (arg=0x7effd700) at pthread_create.c:333 #11 0x7f003a401f6d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7effe4c2a700 (LWP 18263)): #0 0x7f00334abf79 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f003b00eff8 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f003b00b92d in QThreadPoolThread::run() () at /lib64/libQt5Core.so.5 #3 0x7f003b00e99a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #4 0x7f00334a65ca in start_thread (arg=0x7effe4c2a700) at pthread_create.c:333 #5 0x7f003a401f6d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7effe542b700 (LWP 18261)): #0 0x7f0030bc2184 in g_main_context_query (context=context@entry=0x7effd4000990, max_priority=2147483647, timeout=timeout@entry=0x7effe542ab44, fds=fds@entry=0x7effd4003270, n_fds=n_fds@entry=1) at gmain.c:3539 #1 0x7f0030bc2978 in g_main_context_iterate (context=context@entry=0x7effd4000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3822 #2 0x7f0030bc2b1c in g_main_context_iteration (context=0x7effd4000990, may_block=1) at gmain.c:3901 #3 0x7f003b1fc24b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f003b1ab5ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f003b00a343 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f003b00e99a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f00334a65ca in start_thread (arg=0x7effe542b700) at pthread_create.c:333 #8 0x7f003a401f6d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7effe6ffd700 (LWP 18243)): #0 0x7f00334abbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f003b00f01a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f00373448c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7f0037348a68 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7f0037343a3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7f0037348ac2 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*
[kdevelop] [Bug 368432] crash on startup
https://bugs.kde.org/show_bug.cgi?id=368432 --- Comment #1 from Be --- Created attachment 100983 --> https://bugs.kde.org/attachment.cgi?id=100983&action=edit GDB backtrace -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368432] New: crash on startup
https://bugs.kde.org/show_bug.cgi?id=368432 Bug ID: 368432 Summary: crash on startup Product: kdevelop Version: 5.0.0 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: b...@gmx.com This started happening after I switched git branches outside of KDevelop. Reproducible: Always Steps to Reproduce: 1. Start KDevelop -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368424] New: detect JavaScript function expressions assigned to variables for function outline search bar
https://bugs.kde.org/show_bug.cgi?id=368424
Bug ID: 368424
Summary: detect JavaScript function expressions assigned to
variables for function outline search bar
Product: kdevelop
Version: 5.0.0
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: Language Support: QML/JavaScript
Assignee: kdevelop-bugs-n...@kde.org
Reporter: b...@gmx.com
The function outline search bar works for JS functions defined with the syntax:
function functionName (args) {stuff};
but not with functions defined as expressions assigned to a variable:
functionName = function (args) {stuff};
Considering that variables can be reassigned to a function expression at any
point, to support this something would have to be added to the GUI to move
between places in the code where the variable is assigned to a different
function.
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
[amarok] [Bug 299461] amarok: song starts playing before gain is adjusted
https://bugs.kde.org/show_bug.cgi?id=299461 Be changed: What|Removed |Added CC||b...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 364354] Amarok stutters and hangs system before crashing
https://bugs.kde.org/show_bug.cgi?id=364354 --- Comment #4 from Be --- Hm, so this may have something to do with PulseAudio. It happened again and I left my computer for a while (after unplugging my speakers from my sound card). When I came back, Amarok had not crashed, but my system was taking a long time to respond to anything until I quit Amarok. I restarted Amarok and got a warning from Phonon saying that various outputs could not be found, including PulseAudio. Amarok wouldn't output any sound (maybe it was playing to my onboard sound card?) so I started pavucontrol to check if my USB sound card (an RME Babyface Pro in class compliant mode) got disconnected and PulseAudio wasn't detecting it, but pavucontrol showed the error in the attached screenshot. I ran 'pulseaudio -D' and restarted Amarok, then Amarok worked fine. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 364354] Amarok stutters and hangs system before crashing
https://bugs.kde.org/show_bug.cgi?id=364354 --- Comment #3 from Be --- Created attachment 99668 --> https://bugs.kde.org/attachment.cgi?id=99668&action=edit error when starting pavucontrol after quitting Amarok -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 364354] Amarok stutters and hangs system before crashing
https://bugs.kde.org/show_bug.cgi?id=364354 --- Comment #2 from Be --- Okay, I installed debugging symbols for Amarok. I'll attach a new backtrace when I get one, but I don't exactly know how to reproduce the issue. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 364354] New: Amarok stutters and hangs system before crashing
https://bugs.kde.org/show_bug.cgi?id=364354 Bug ID: 364354 Summary: Amarok stutters and hangs system before crashing Product: amarok Version: 2.8.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: b...@gmx.com Application: amarok (2.8.0) KDE Platform Version: 4.14.18 Qt Version: 4.8.7 Operating System: Linux 4.4.12-300.rt19.1.fc23.ccrma.x86_64+rt x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: Occasionally, when Amarok is playing and I am away from my computer, it will stutter playback and the system freezes. Usually I disconnect the power to forcibly restart my computer, but on this occasion, I disconnected my speaker and let my computer be for a while. When I came back to my computer, I saw that Amarok had crashed. The crash can be reproduced sometimes. -- Backtrace: Application: Amarok (amarok), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f39a81fc940 (LWP 14530))] Thread 14 (Thread 0x7f395e0a5700 (LWP 14537)): #0 0x7f39a395eeb9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f396a1276c2 in my_service_thread_sleep () at /usr/lib64/mysql/libmysqld.so.18 #2 0x7f396a1226a8 in ma_checkpoint_background () at /usr/lib64/mysql/libmysqld.so.18 #3 0x7f39a395960a in start_thread () at /lib64/libpthread.so.0 #4 0x7f39a4df478d in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f395d8a4700 (LWP 14538)): #0 0x7f39a395eeb9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f39a54c18d4 in QWaitCondition::wait(QMutex*, unsigned long) (time=6, this=0x55bf8a2fae50) at thread/qwaitcondition_unix.cpp:84 #2 0x7f39a54c18d4 in QWaitCondition::wait(QMutex*, unsigned long) (this=, mutex=0x55bf8a309dd8, time=6) at thread/qwaitcondition_unix.cpp:158 #3 0x7f39a7ba9bff in AbstractDirectoryWatcher::run() () at /lib64/libamaroklib.so.1 #4 0x7f39a298e712 in ThreadWeaver::JobRunHelper::runTheJob(ThreadWeaver::Thread*, ThreadWeaver::Job*) (this=this@entry=0x7f395d8a3c50, th=th@entry=0x55bf8a1ba050, job=job@entry=0x55bf8a309db0) at /usr/src/debug/kdelibs-4.14.18/threadweaver/Weaver/Job.cpp:106 #5 0x7f39a298e91e in ThreadWeaver::Job::execute(ThreadWeaver::Thread*) (this=0x55bf8a309db0, th=0x55bf8a1ba050) at /usr/src/debug/kdelibs-4.14.18/threadweaver/Weaver/Job.cpp:135 #6 0x7f39a298dfeb in ThreadWeaver::Thread::run() (this=0x55bf8a1ba050) at /usr/src/debug/kdelibs-4.14.18/threadweaver/Weaver/Thread.cpp:108 #7 0x7f39a54c138c in QThreadPrivate::start(void*) (arg=0x55bf8a1ba050) at thread/qthread_unix.cpp:352 #8 0x7f39a395960a in start_thread () at /lib64/libpthread.so.0 #9 0x7f39a4df478d in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f395d0a3700 (LWP 14539)): #0 0x7f399ea3a719 in g_mutex_lock (mutex=mutex@entry=0x7f39540009a0) at gthread-posix.c:1338 #1 0x7f399e9f5110 in g_main_context_acquire (context=0x7f39540009a0) at gmain.c:3214 #2 0x7f399e9f6025 in g_main_context_iterate (context=context@entry=0x7f39540009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3790 #3 0x7f399e9f627c in g_main_context_iteration (context=0x7f39540009a0, may_block=may_block@entry=1) at gmain.c:3901 #4 0x7f39a5600e7e in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f39540008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #5 0x7f39a55cf131 in QEventLoop::processEvents(QFlags) (this=this@entry=0x7f395d0a2c40, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f39a55cf4a5 in QEventLoop::exec(QFlags) (this=this@entry=0x7f395d0a2c40, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f39a54bea99 in QThread::exec() (this=this@entry=0x55bf8a313f90) at thread/qthread.cpp:538 #8 0x7f39a55af203 in QInotifyFileSystemWatcherEngine::run() (this=0x55bf8a313f90) at io/qfilesystemwatcher_inotify.cpp:265 #9 0x7f39a54c138c in QThreadPrivate::start(void*) (arg=0x55bf8a313f90) at thread/qthread_unix.cpp:352 #10 0x7f39a395960a in start_thread () at /lib64/libpthread.so.0 #11 0x7f39a4df478d in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f394700 (LWP 14540)): #0 0x7f39a395eb10 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f39a54c18f6 in QWaitCondition::wait(QMutex*, unsigned long) (time=18446744073709551615, this=0x55bf8a311290) at thread/qwaitcondition_unix.cpp:86 #2 0x7f39a54c18f6 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x55bf8a311168, mutex=0x55bf8a1b94e0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7f39a298c6ec in ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned(Th
