[kmymoney] [Bug 473079] kMyMoney does not open window on start
https://bugs.kde.org/show_bug.cgi?id=473079 Thomas Baumgart changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #5 from Thomas Baumgart --- AppImage builds have been moved. Please read https://kmymoney.org/appimage.html for updated information. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476930] Unable to change or preview non-Breeze splash screens
https://bugs.kde.org/show_bug.cgi?id=476930 --- Comment #4 from David Redondo --- I found that oxygen was not converted; https://invent.kde.org/plasma/oxygen/-/commit/807f6216ae0cf0bc16bfa4eef573d24a295450b8 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 477078] New: misbehavior on long lines
https://bugs.kde.org/show_bug.cgi?id=477078 Bug ID: 477078 Summary: misbehavior on long lines Classification: Applications Product: konsole Version: 23.08.3 Platform: Neon OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: michael.hm...@gmail.com Target Milestone: --- after latest upgrade, konsole (and Yakuake) is misbehaving after scrolling down or down up over long lines which occupy several terminal lines soon such a line is reached the next keypress up or down jumps to the next line and the window below stays black with a "@" placeholder for the occupied space by the text which is not visible this behavior renders the program useless since Yakuake behaves the same way the problem is probably not the program itself, but I have no idea where I could look at the problem appears also on Arch with the same plasma version upgraded thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452188] While playing Apex Legends player's aim (mouse) spins and looks straight downwards.
https://bugs.kde.org/show_bug.cgi?id=452188 Yao Mitachi changed: What|Removed |Added CC||yao...@protonmail.com --- Comment #11 from Yao Mitachi --- https://discuss.kde.org/t/bug-fix-cursor-issue-camera-snapping-into-downward-facing-position-in-some-games/7384 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474352] KDE crashing when closing an instance of a grouped application .
https://bugs.kde.org/show_bug.cgi?id=474352 --- Comment #2 from jasoncolleg...@gmail.com --- Created attachment 163210 --> https://bugs.kde.org/attachment.cgi?id=163210=edit New crash information added by DrKonqi plasmashell (5.24.7) using Qt 5.15.3 - What I was doing when the application crashed: This happen when right clicking a group of windows from Dolphin with the intent to close the group. It happened before the context menu appeared, and I had to right click again. -- Backtrace (Reduced): #4 0x7fdba579fad8 in QSGTexture::setFiltering(QSGTexture::Filtering) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fdba57d07af in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fdba57b73dc in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fdba57bc965 in QSGBatchRenderer::Renderer::renderBatches() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7fdba57bd352 in QSGBatchRenderer::Renderer::render() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476830] Keyboard layout applet not shown on Wayland
https://bugs.kde.org/show_bug.cgi?id=476830 --- Comment #4 from Silver Salonen --- (In reply to Nate Graham from comment #2) > Ah, it's just Bug 449531, which is fixed in Plasma 6 I did read through that bug first too, and it seemed to me that what I hit was not that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474352] KDE crashing when closing an instance of a grouped application .
https://bugs.kde.org/show_bug.cgi?id=474352 jasoncolleg...@gmail.com changed: What|Removed |Added CC||jasoncolleg...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458233] In some games, controlling the camera with mouse, camera occasionally snaps into a different position when using Wayland
https://bugs.kde.org/show_bug.cgi?id=458233 --- Comment #38 from Yao Mitachi --- (In reply to Nate Graham from comment #37) > See https://discuss.kde.org/c/development/sponsored-work/31 if you'd like to > go down that path. Done. I can chip in $50. https://discuss.kde.org/t/bug-fix-cursor-issue-camera-snapping-into-downward-facing-position-in-some-games/7384 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476830] Keyboard layout applet not shown on Wayland
https://bugs.kde.org/show_bug.cgi?id=476830 --- Comment #3 from Silver Salonen --- > Does it appear if you restart plasmashell with `systemctl restart --user > plasma-plasmashell.service`? No, it does not. I've restarted plasmashell many times after starting using Wayland, but I've never once seen the keyboard layout icon at system tray under Wayland. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372496] Support tmux control mode
https://bugs.kde.org/show_bug.cgi?id=372496 --- Comment #6 from mastergeek.elli...@gmail.com --- +1 >From my point of view, tmux integration is Mac's "killer feature" that Linux lacks. I would love to see this get implemented. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372496] Support tmux control mode
https://bugs.kde.org/show_bug.cgi?id=372496 mastergeek.elli...@gmail.com changed: What|Removed |Added CC||mastergeek.elli...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 476537] Network speed widget shows nothing
https://bugs.kde.org/show_bug.cgi?id=476537 --- Comment #4 from Nicola Mori --- Well, this is disappointing. A standard feature breaks in the current stable version and there's no plan to fix it. Not everybody will jump on Plasma 6 on day 0 so I was expecting more care for the 5.27 series. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 456108] baloo reindexes files with date of 0 or prior to UNIX epoch on every restart
https://bugs.kde.org/show_bug.cgi?id=456108 --- Comment #3 from skierpage --- I enabled baloo logging and restarted baloo, and baloo reindexed a bunch of files with the same modified times in 1970-0-01 (1969 in my timezone). The journal included lines like ... baloo_file[21819]: kf.baloo: "/home/spage/programs/skrooge_dev/skrooge/flatpak_build-dir/files/share/doc/HTML/en/skrooge/dashboard_report.png" mtime/ctime changed: 0 / 1675907011 -> 28800 / 1675907011 I think this is saying baloo thought the file's mtime was 0 and now thinks it's 28800, so it reindexed. My timezone is PST -0800, which is 28,800 seconds before GMT. baloo appears to not handle the timezone here, although `balooshow` does display the correct localtime (with no timezone) for recently updated files If I manually call for reindex with `balooctl index /path/to/1970_file`, the command prints Skipping: /home/spage/programs/skrooge_dev/skrooge/flatpak_build-dir/files/share/doc/HTML/en/skrooge/dashboard_report.png Reason: Already indexed I don't know if this skip happens when baloo thinks it needs to reindex these files. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 474538] The EWS fetched mails are frequently corrupted
https://bugs.kde.org/show_bug.cgi?id=474538 Pierluigi Frullani changed: What|Removed |Added CC||p...@frumar.it --- Comment #7 from Pierluigi Frullani --- I have the same problem. I'm using Kmail since the beggining and never had such problem neither with imap/pop and their counterpart in ssl. Moreover the account that trigger the problem was in Imap and had no problem, but then Microsoft decided to remove the access in Imap and had to convert. Now I have the probem. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 477077] New: Clicking on SMS message from an Android SMS/MMS chat that contains images frequently crashes
https://bugs.kde.org/show_bug.cgi?id=477077 Bug ID: 477077 Summary: Clicking on SMS message from an Android SMS/MMS chat that contains images frequently crashes Classification: I don't know Product: kde Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dvd_id...@yahoo.com Target Milestone: --- Application: kdeconnect-sms (22.08.3) Qt Version: 5.15.10 Frameworks Version: 5.99.0 Operating System: Linux 5.15.23-gentoo x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.26.5 [KCrashBackend] -- Information about the crash: Start by connecting phone to KDE Connect as usual. Send some SMS back and forth to a receiver (Rcvr). disconnect and reconnect some hours later, after sending some MMS photos back and forth a few times away from home base. Then reconnect, and attempt to read messages from Rcvr with those MMS photos in. KDE Connect SMS crashes. The crash can be reproduced every time. -- Backtrace: Application: KDE Connect SMS (kdeconnect-sms), signal: Aborted [KCrash Handler] #4 0x7f37258738dc in __pthread_kill_implementation () at /lib64/libc.so.6 #5 0x7f37258257a2 in raise () at /lib64/libc.so.6 #6 0x7f372580f4b2 in abort () at /lib64/libc.so.6 #7 0x7f3725c75d63 in qt_message_output(QtMsgType, QMessageLogContext const&, QString const&) [clone .cold] () at /usr/lib64/libQt5Core.so.5 #8 0x7f3725c8c6af in () at /usr/lib64/libQt5Core.so.5 #9 0x7f370f0a2027 in QMediaPlayer::QMediaPlayer(QObject*, QFlags) () at /usr/lib64/libQt5Multimedia.so.5 #10 0x7f370f18243a in QDeclarativeAudio::classBegin() () at /usr/lib64/qt5/qml/QtMultimedia/libdeclarative_multimedia.so #11 0x7f3727293be4 in QQmlObjectCreator::createInstance(int, QObject*, bool) () at /usr/lib64/libQt5Qml.so.5 #12 0x7f3727295cf5 in QQmlObjectCreator::setPropertyBinding(QQmlPropertyData const*, QV4::CompiledData::Binding const*) () at /usr/lib64/libQt5Qml.so.5 #13 0x7f3727297769 in QQmlObjectCreator::setupBindings(bool) () at /usr/lib64/libQt5Qml.so.5 #14 0x7f37272930de in QQmlObjectCreator::populateInstance(int, QObject*, QObject*, QQmlPropertyData const*) () at /usr/lib64/libQt5Qml.so.5 #15 0x7f3727293efa in QQmlObjectCreator::createInstance(int, QObject*, bool) () at /usr/lib64/libQt5Qml.so.5 #16 0x7f3727295cf5 in QQmlObjectCreator::setPropertyBinding(QQmlPropertyData const*, QV4::CompiledData::Binding const*) () at /usr/lib64/libQt5Qml.so.5 #17 0x7f3727297769 in QQmlObjectCreator::setupBindings(bool) () at /usr/lib64/libQt5Qml.so.5 #18 0x7f37272930de in QQmlObjectCreator::populateInstance(int, QObject*, QObject*, QQmlPropertyData const*) () at /usr/lib64/libQt5Qml.so.5 #19 0x7f3727293efa in QQmlObjectCreator::createInstance(int, QObject*, bool) () at /usr/lib64/libQt5Qml.so.5 #20 0x7f3727294df3 in QQmlObjectCreator::create(int, QObject*, QQmlInstantiationInterrupt*, int) () at /usr/lib64/libQt5Qml.so.5 #21 0x7f37272945e6 in QQmlObjectCreator::createInstance(int, QObject*, bool) () at /usr/lib64/libQt5Qml.so.5 #22 0x7f3727294df3 in QQmlObjectCreator::create(int, QObject*, QQmlInstantiationInterrupt*, int) () at /usr/lib64/libQt5Qml.so.5 #23 0x7f3727225f3f in QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () at /usr/lib64/libQt5Qml.so.5 #24 0x7f37272268fa in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () at /usr/lib64/libQt5Qml.so.5 #25 0x7f37254e83c2 in QQmlDelegateModelPrivate::object(QQmlListCompositor::Group, int, QQmlIncubator::IncubationMode) () at /usr/lib64/libQt5QmlModels.so.5 #26 0x7f37277757bf in QQuickRepeaterPrivate::requestItems() () at /usr/lib64/libQt5Quick.so.5 #27 0x7f3727778933 in QQuickRepeater::componentComplete() () at /usr/lib64/libQt5Quick.so.5 #28 0x7f3727290303 in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () at /usr/lib64/libQt5Qml.so.5 #29 0x7f372722645a in QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () at /usr/lib64/libQt5Qml.so.5 #30 0x7f37272268fa in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () at /usr/lib64/libQt5Qml.so.5 #31 0x7f37254e83c2 in QQmlDelegateModelPrivate::object(QQmlListCompositor::Group, int, QQmlIncubator::IncubationMode) () at /usr/lib64/libQt5QmlModels.so.5 #32 0x7f37277350c7 in QQuickItemViewPrivate::createItem(int, QQmlIncubator::IncubationMode) () at /usr/lib64/libQt5Quick.so.5 #33 0x7f37277459fb in QQuickListViewPrivate::applyInsertionChange(QQmlChangeSet::Change const&, QQuickItemViewPrivate::ChangeResult*, QList*, QList*) () at /usr/lib64/libQt5Quick.so.5 #34 0x7f3727735c5c in QQuickItemViewPrivate::applyModelChanges(QQuickItemViewPrivate::ChangeResult*,
[plasmashell] [Bug 465354] Sub-menus go under panel on Wayland
https://bugs.kde.org/show_bug.cgi?id=465354 Pawel changed: What|Removed |Added CC||bednarczyk.pa...@outlook.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477076] New: Cannot set shortcut key sequence.
https://bugs.kde.org/show_bug.cgi?id=477076 Bug ID: 477076 Summary: Cannot set shortcut key sequence. Classification: Plasma Product: kwin Version: git-stable-Plasma/5.27 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: xpusosto...@gmail.com Target Milestone: --- SUMMARY KDE in general seems to accept key sequences (as one finds in emacs) as valid keyboard overrides. e.g., you can set "Open" to be C-x C-f. However kwin does it, it only allows you to set single keys. Since the emacs command to close a window is C-x 5 0, that makes it impossible to set that sequence. STEPS TO REPRODUCE 1. go into settings., shortcuts find a key to override in the Kwin section (e.g. Close Window) 2. Observe you can't set window functions to sequences of keys OBSERVED RESULT can't set key sequence EXPECTED RESULT Be able to set key sequence like you can in other parts of KDE. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: kwin 5.27.8 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 477075] New: Font doesn't look the same when updating from 5.1.5 to 5.2.1
https://bugs.kde.org/show_bug.cgi?id=477075 Bug ID: 477075 Summary: Font doesn't look the same when updating from 5.1.5 to 5.2.1 Classification: Applications Product: krita Version: 5.2.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: notof...@gmail.com Target Milestone: --- Created attachment 163209 --> https://bugs.kde.org/attachment.cgi?id=163209=edit Text in Font tool vs text when saved STEPS TO REPRODUCE 1. Create a file with text with "Bahnscrift Semibold" font in Krita 5.1.5 2. Update Krita from 5.1.5 to 5.2.1 3. Enter the file SOFTWARE/OS VERSIONS Windows: 11 23H2 ADDITIONAL INFORMATION: Link to the font and the project file: https://drive.google.com/drive/folders/1B6TpUc7iCbvDbg0xt3IPWK10VYnUfsmo?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459136] When Maliit virtual keyboard disappears, non-active windows that got resized don't return to their original size
https://bugs.kde.org/show_bug.cgi?id=459136 Shubham Arora changed: What|Removed |Added Ever confirmed|0 |1 CC||shubhamar...@protonmail.com Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 477074] Splash screen blocking desktop when login sound enabled
https://bugs.kde.org/show_bug.cgi?id=477074 --- Comment #1 from James --- Possibly related to "uim-pref-gtk" -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 477074] New: Splash screen blocking desktop when login sound enabled
https://bugs.kde.org/show_bug.cgi?id=477074 Bug ID: 477074 Summary: Splash screen blocking desktop when login sound enabled Classification: Plasma Product: ksplash Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: conro...@msn.com Target Milestone: --- Created attachment 163208 --> https://bugs.kde.org/attachment.cgi?id=163208=edit Splash screen SUMMARY *** Splash screen remains for 15-20 seconds if i login sound is enabled. blocking access to the desktop. *** STEPS TO REPRODUCE 1. Enable login sound in notifications 2. logout and back in 3. Wait 15-20 sec for desktop to show SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian Unstable / 12 (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Happens on Opensuse KDE as well. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432175] Window to add a digital camera is not properly maximized
https://bugs.kde.org/show_bug.cgi?id=432175 Patrick Silva changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Patrick Silva --- Tested on Arch Linux running Plasma 6 alpha e neon unstable; cannot reproduce. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 431422] Elisa intermittently crashed in KFileMetaData::Property::Property() when fetching lyrics tag
https://bugs.kde.org/show_bug.cgi?id=431422 Stefan Brüns changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=458607 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 458607] Elisa crashes on launch in KFileMetaData::ExtractorCollectionPrivate::getExtractors() with existing playlist and shuffle enabled
https://bugs.kde.org/show_bug.cgi?id=458607 Stefan Brüns changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=431422 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 458607] Elisa crashes on launch in KFileMetaData::ExtractorCollectionPrivate::getExtractors() with existing playlist and shuffle enabled
https://bugs.kde.org/show_bug.cgi?id=458607 Stefan Brüns changed: What|Removed |Added Assignee|pinak.ah...@gmail.com |matthieu_gall...@yahoo.fr Version|5.97.0 |22.08.0 Component|general |general Product|frameworks-kfilemetadata|Elisa --- Comment #3 from Stefan Brüns --- Likely duplicate of 431422 KFileMetadata::ExtractorCollection is reentrant, but not thread safe. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466342] While 2 screens are connected, after resuming from hibernation, the secondary screen is set as the primary screen
https://bugs.kde.org/show_bug.cgi?id=466342 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #33 from fanzhuyi...@gmail.com --- fyi I tried on neon unstable and this issue is no longer happening for me. Could other people also test on neon unstable, if possible? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474382] On Wayland, no titlebar buttons on CSD-using Firefox in Plasma 6
https://bugs.kde.org/show_bug.cgi?id=474382 fanzhuyi...@gmail.com changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #16 from fanzhuyi...@gmail.com --- Actually it might have been an automatic system update that I was not aware of. Anyways right now I can not reproduce it after many restarts (previously it was consistently reproducible 100%). @guimarcalsilva, do you still have this issue after applying the latest updates? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467333] Error on exiftool install on Win10 64bit
https://bugs.kde.org/show_bug.cgi?id=467333 --- Comment #5 from caulier.gil...@gmail.com --- Git commit fbe53f85b92395f438214e0223792471e06c3c4c by Gilles Caulier. Committed on 16/11/2023 at 05:08. Pushed by cgilles into branch 'master'. NSIS MXE: kill all background exiftool.exe process running in backgroud before to copy file in the system Related: bug 437813 M +4-0project/bundles/mxe/installer/digikam.nsi https://invent.kde.org/graphics/digikam/-/commit/fbe53f85b92395f438214e0223792471e06c3c4c -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 437813] exiftool.exe is preventing the installation if digiKam is terminate inexplicably
https://bugs.kde.org/show_bug.cgi?id=437813 --- Comment #34 from caulier.gil...@gmail.com --- Git commit fbe53f85b92395f438214e0223792471e06c3c4c by Gilles Caulier. Committed on 16/11/2023 at 05:08. Pushed by cgilles into branch 'master'. NSIS MXE: kill all background exiftool.exe process running in backgroud before to copy file in the system Related: bug 467333 M +4-0project/bundles/mxe/installer/digikam.nsi https://invent.kde.org/graphics/digikam/-/commit/fbe53f85b92395f438214e0223792471e06c3c4c -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 437813] exiftool.exe is preventing the installation if digiKam is terminate inexplicably
https://bugs.kde.org/show_bug.cgi?id=437813 --- Comment #33 from caulier.gil...@gmail.com --- Git commit 6dad6403945a91b950eb28239654aa51d25ac6f5 by Gilles Caulier. Committed on 16/11/2023 at 05:04. Pushed by cgilles into branch 'master'. NSIS VCPKG: kill all background exiftool.exe process running in backgroud before to copy file in the system Related: bug 467333 M +4-0project/bundles/vcpkg/installer/digikam.nsi https://invent.kde.org/graphics/digikam/-/commit/6dad6403945a91b950eb28239654aa51d25ac6f5 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467333] Error on exiftool install on Win10 64bit
https://bugs.kde.org/show_bug.cgi?id=467333 --- Comment #4 from caulier.gil...@gmail.com --- Git commit 6dad6403945a91b950eb28239654aa51d25ac6f5 by Gilles Caulier. Committed on 16/11/2023 at 05:04. Pushed by cgilles into branch 'master'. NSIS VCPKG: kill all background exiftool.exe process running in backgroud before to copy file in the system Related: bug 437813 M +4-0project/bundles/vcpkg/installer/digikam.nsi https://invent.kde.org/graphics/digikam/-/commit/6dad6403945a91b950eb28239654aa51d25ac6f5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474382] On Wayland, no titlebar buttons on CSD-using Firefox in Plasma 6
https://bugs.kde.org/show_bug.cgi?id=474382 --- Comment #15 from fanzhuyi...@gmail.com --- fyi after a few restarts right now my firefox titlebar buttons are back. I did not update the system. I might have tweaked a few settings, but I don't recall changing anything that seemed super relevant to this. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 475825] Tokodon crash when clicking "Notifications" in sidebar
https://bugs.kde.org/show_bug.cgi?id=475825 --- Comment #16 from sfal...@cloverleaf-linux.org --- Just as an aside, it's intermittent for me, it didn't do it at all today (although if I'm supposed to be getting notification popups or the notifications icon updating, *that* isn't working) -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 475825] Tokodon crash when clicking "Notifications" in sidebar
https://bugs.kde.org/show_bug.cgi?id=475825 --- Comment #15 from sfal...@cloverleaf-linux.org --- (In reply to Joshua Goins from comment #14) > Oh something I forgot to ask but someone reminded me, which servers are you > connecting to? If you don't wish to disclose that, the name of the server > software is fine. For me, fosstodon and my personal instance at mastodon.naturalorder.me (Mastodon 4.4.1 I think) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 476029] Dolphin crashes when trying to delete file, after using custom service menu
https://bugs.kde.org/show_bug.cgi?id=476029 fanzhuyi...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #5 from fanzhuyi...@gmail.com --- I am closing this as fixed since this doesn't happen on neon unstable. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 476476] Delete key does not work in dolphin rename
https://bugs.kde.org/show_bug.cgi?id=476476 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from fanzhuyi...@gmail.com --- Works in latest neon unstable, so closing this. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 467320] KDEConnect syncs contacts, but it does not show up in KAddressBook.
https://bugs.kde.org/show_bug.cgi?id=467320 --- Comment #1 from Russell Haley --- In https://bugs.kde.org/show_bug.cgi?id=456140#c1, Nicolas says the SMS app is supposed to know the contacts, but I was just seeing phone numbers until I installed the kpeoplevcard Fedora package and manually imported the vcard directory into KAddressBook. Maybe the manual import would've been unnecessary if I had restarted kdeconnect on my desktop after installing kpeoplevcard? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477073] Automatically login with Wayland session stopped work couple days (maybe week) ago
https://bugs.kde.org/show_bug.cgi?id=477073 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from fanzhuyi...@gmail.com --- Based on your description, it seems that you cannot log into the plasma session at all. Is that what is happening? If so, can you log into the plasma session with the latest neon unstable iso? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475729] plasma crash when closing notification message
https://bugs.kde.org/show_bug.cgi?id=475729 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475605] Black screen with only cursor on wake from sleep.
https://bugs.kde.org/show_bug.cgi?id=475605 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #9 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472005] Touchpad disabled after booting, but can be re-enabled in settings
https://bugs.kde.org/show_bug.cgi?id=472005 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #8 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476428] I don't have option to save my picture like .kra
https://bugs.kde.org/show_bug.cgi?id=476428 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476414] ときどきキャンバスが真っ暗になる。プレビューをみると、しっかり描けてはいるらしい
https://bugs.kde.org/show_bug.cgi?id=476414 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476158] scroll inconsistencies on graphics tablet
https://bugs.kde.org/show_bug.cgi?id=476158 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 467320] KDEConnect syncs contacts, but it does not show up in KAddressBook.
https://bugs.kde.org/show_bug.cgi?id=467320 Russell Haley changed: What|Removed |Added CC||yumpusamongus+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 477072] spectacle on plasma 6 will enlarge when taking rectangular area screenshots
https://bugs.kde.org/show_bug.cgi?id=477072 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kfilemetadata] [Bug 421317] Baloo is crashing at startup
https://bugs.kde.org/show_bug.cgi?id=421317 --- Comment #13 from Stefan Brüns --- Git commit fd24c90c1e465324baa81a622f8767b62eef by Stefan Brüns. Committed on 16/11/2023 at 04:18. Pushed by bruns into branch 'kf5'. [ExtractorProcess] Handle signal mangling by DrKonqi DrKonqui catches the SIGSEGV or SIGILL from a misbehaving extractor, and then eventually quits the process. This may happen either by re-raising the signal, or just are regular `_exit(253)`. Which one is used depends on the kernel `/proc/sys/kernel/core_pattern` setting - if it uses a pipe, the signal will be reraised. The unexpected exit status was not handled before, and could cause a blocking indexer, as neither a `done()` or `failed()` signal would ever be emitted. This also causes the list of failed files to stay empty, i.e. `balooctl failed` would not return anything. (cherry picked from commit 819cb757b5742372cf017fba84955178c1f1a7d1) M +1-1autotests/unit/file/CMakeLists.txt M +1-1src/file/CMakeLists.txt M +12 -4src/file/extractorprocess.cpp https://invent.kde.org/frameworks/baloo/-/commit/fd24c90c1e465324baa81a622f8767b62eef -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kfilemetadata] [Bug 421317] Baloo is crashing at startup
https://bugs.kde.org/show_bug.cgi?id=421317 --- Comment #12 from Stefan Brüns --- Git commit 819cb757b5742372cf017fba84955178c1f1a7d1 by Stefan Brüns. Committed on 14/11/2023 at 01:28. Pushed by bruns into branch 'master'. [ExtractorProcess] Handle signal mangling by DrKonqi DrKonqui catches the SIGSEGV or SIGILL from a misbehaving extractor, and then eventually quits the process. This may happen either by re-raising the signal, or just are regular `_exit(253)`. Which one is used depends on the kernel `/proc/sys/kernel/core_pattern` setting - if it uses a pipe, the signal will be reraised. The unexpected exit status was not handled before, and could cause a blocking indexer, as neither a `done()` or `failed()` signal would ever be emitted. This also causes the list of failed files to stay empty, i.e. `balooctl failed` would not return anything. M +1-1src/file/CMakeLists.txt M +12 -4src/file/extractorprocess.cpp https://invent.kde.org/frameworks/baloo/-/commit/819cb757b5742372cf017fba84955178c1f1a7d1 -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 475825] Tokodon crash when clicking "Notifications" in sidebar
https://bugs.kde.org/show_bug.cgi?id=475825 --- Comment #14 from Joshua Goins --- Oh something I forgot to ask but someone reminded me, which servers are you connecting to? If you don't wish to disclose that, the name of the server software is fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477073] Automatically login with Wayland session stopped work couple days (maybe week) ago
https://bugs.kde.org/show_bug.cgi?id=477073 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com Keywords||qt6, wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477073] New: Automatically login with Wayland session stopped work couple days (maybe week) ago
https://bugs.kde.org/show_bug.cgi?id=477073 Bug ID: 477073 Summary: Automatically login with Wayland session stopped work couple days (maybe week) ago Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: piotr.mierzwin...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY As in subject. Instead of this I get login screen, which also I cannot change (after enter password it returns to old one). Additionally I cannot set automatically login with Wayland session in System Settings. When I open "Login screen (SDDM( -> Behavior " I can see set session "Plasma (X11)", but I use Wayland. After I change to Wayland and enter the password it switches (in combobox) to Plasma (X11) again. I had this have set several months ago and recently stopped work. STEPS TO REPRODUCE 1. Start System Settings 2. Login screen (SDDM( -> Behavior 3. Set session Wayland 4. Press Apply OBSERVED RESULT In result of start Plasma I can see login screen. Switch to Wayland doesn't work in System Settings. EXPECTED RESULT Should be able to automatically login with Wayland session, as it happens some time ago. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.81 KDE Frameworks Version: 5.245 Qt Version: 6.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477070] mplayer in version which doesn't support wayland
https://bugs.kde.org/show_bug.cgi?id=477070 Piotr Mierzwinski changed: What|Removed |Added Keywords||wayland CC||piotr.mierzwin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 477072] New: spectacle on plasma 6 will enlarge when taking rectangular area screenshots
https://bugs.kde.org/show_bug.cgi?id=477072 Bug ID: 477072 Summary: spectacle on plasma 6 will enlarge when taking rectangular area screenshots Classification: Applications Product: Spectacle Version: 24.01.75 Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: 1900011...@pku.edu.cn CC: k...@david-redondo.de Target Milestone: --- Created attachment 163207 --> https://bugs.kde.org/attachment.cgi?id=163207=edit resize to 200% When I use spectacle on plasma 5.27.80 I press meta+shift+prtsc and my screen suddenly enlarged to 200%, but active window/whole screen have no problem X11 and Wayland have the same issue I have a global scale of 200%, so spectacle actually enlarge to 400% Operating System: Arch Linux KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 Kernel Version: 6.6.1-arch1-1 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471927] Plasma crashes in moment of click menu application outside of KDE
https://bugs.kde.org/show_bug.cgi?id=471927 Piotr Mierzwinski changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WORKSFORME |--- --- Comment #15 from Piotr Mierzwinski --- Sorry, is there anybody who is able to reproduce this issue? I face with this any time when I only want to use synaptic or vlc or Opera (one accidentally click and all session crashed). This doesn't happen in X11 session. I tested in xfce4. Maybe this problem happens only in Neon Unstable Edition, but in Fedora all works well. I'm not able to test this in Fedora. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477070] mplayer in version which doesn't support wayland
https://bugs.kde.org/show_bug.cgi?id=477070 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477071] sddm cannot use plasma settings on kde 5.27.80
https://bugs.kde.org/show_bug.cgi?id=477071 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477069] `print` dbus signal doesn't work
https://bugs.kde.org/show_bug.cgi?id=477069 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477071] New: sddm cannot use plasma settings on kde 5.27.80
https://bugs.kde.org/show_bug.cgi?id=477071 Bug ID: 477071 Summary: sddm cannot use plasma settings on kde 5.27.80 Classification: Applications Product: systemsettings Version: 5.27.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_sddm Assignee: plasma-b...@kde.org Reporter: 1900011...@pku.edu.cn CC: k...@david-redondo.de, k...@davidedmundson.co.uk Target Milestone: --- https://github.com/sddm/sddm/issues/1828 My plasma 6 use font dpi fixed to 192, or I say, screen enlarge to 200%, but when I synchronize it to sddm, it says: Warning from helper: Could not copy "/home/firestar/.config/fontconfig/." to "/var/lib/sddm/.config/fontconfig/." Warning from helper: Could not copy "/home/firestar/.config/fontconfig/.." to "/var/lib/sddm/.config/fontconfig/.." Synchronization successful and the font of sddm is still too small (dpi=96) Also, the cursor settings failed to synchronize Operating System: Arch Linux KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 Kernel Version: 6.6.1-arch1-1 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476563] Lockscreen shows black screen without possibility to back to normal
https://bugs.kde.org/show_bug.cgi?id=476563 --- Comment #8 from Piotr Mierzwinski --- I work with laptop. BTW. Today, after yesterday update, I observed similar issue, but instead of black screen I got screen with lockscreen background (and with watch). Of course there was mouse cursor. Switching didn't help, even restart of sddm didn't. Plugging off cord from monitor and plug in again didn't help. I needed to restart my PC. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 475115] baloo_file crashes in Baloo::XAttrIndexer::run() every start of Plasma
https://bugs.kde.org/show_bug.cgi?id=475115 --- Comment #2 from Piotr Mierzwinski --- (In reply to Nate Graham from comment #1) > I'm guessing you've set some comments/extended attributes on at least one of > your files? I didn't set any "comments/extended attributes". -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477070] New: mplayer in version which doesn't support wayland
https://bugs.kde.org/show_bug.cgi?id=477070 Bug ID: 477070 Summary: mplayer in version which doesn't support wayland Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Unstable Edition Assignee: neon-b...@kde.org Reporter: piotr.mierzwin...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY I refer to bug: https://bugs.kde.org/show_bug.cgi?id=476377 where I reported issue that mplayer is not able to switch to full screen. It turned out that this is because too old version of mplayer provided by Neon Unstable Edition. Could you please upgrade mplayer to version 1.5.x or higher to it be able to support Wayland? Thank you in advance. STEPS TO REPRODUCE 1. mplayer video file 2. Press "F" 3. OBSERVED RESULT Happens nothing EXPECTED RESULT I should get full screen with opened video file. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.81 KDE Frameworks Version: 5.245 Qt Version: 6.6 Graphics Platform: Wayland Mesa Intel® Xe Graphic ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476377] One cannot switch mplayer to full screen in Wayland session
https://bugs.kde.org/show_bug.cgi?id=476377 --- Comment #2 from Piotr Mierzwinski --- (In reply to Nate Graham from comment #1) > Works for me with mplayer-1.5.1 on Fedora KDE run on Plasma 6. If you're > using an older version of mplayer, it might be that it doesn't have Wayland > support yet. Regardless, this is an app issue, not a problem with Plasma or > KWin. Thank you for checking. Seems this is problem of distribution I use. I use mplayer version 1.4. It looks like that n Neon Unstable Edition there is an old version -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 476815] Discover cannot find sddm package
https://bugs.kde.org/show_bug.cgi?id=476815 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #2 from Piotr Mierzwinski --- (In reply to Nate Graham from comment #1) > Right, Discover is an "app store" and not a package manager. It's not meant > to find technical packages like SDDM that your distro should have already > pre-installed for you. Seems below message published at Nov 3rd, 2023 in "This week in KDE: Plasma 6 Alpha approaches" was misleading. I cannot find what I "expecting when you search for something that exists and is available". "Discover’s search has been hugely improved, and now generally always returns the results you’re expecting when you search for something that exists and is available" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477069] New: `print` dbus signal doesn't work
https://bugs.kde.org/show_bug.cgi?id=477069
Bug ID: 477069
Summary: `print` dbus signal doesn't work
Classification: Plasma
Product: kwin
Version: 5.27.80
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: scripting
Assignee: kwin-bugs-n...@kde.org
Reporter: ad.liu@gmail.com
Target Milestone: ---
SUMMARY
print() in kwin script doesn't generate dbus signal.
STEPS TO REPRODUCE
1. plasma-interactiveconsole --kwin
2. print("hello")
3. Execute
OBSERVED RESULT
No output.
EXPECTED RESULT
"hello" in the output panel.
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.245.0
Qt Version: 6.6.0
Kernel Version: 6.6.1-arch1-1 (64-bit)
Graphics Platform: offscreen
Processors: 12 × AMD Ryzen 5 5600H with Radeon Graphics
Memory: 13.5 GiB of RAM
Graphics Processor: AMD Radeon Graphics
--
You are receiving this mail because:
You are watching all bug changes.
[Tokodon] [Bug 473787] Accounts do not persist on software restart
https://bugs.kde.org/show_bug.cgi?id=473787 Joshua Goins changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 475825] Tokodon crash when clicking "Notifications" in sidebar
https://bugs.kde.org/show_bug.cgi?id=475825 Joshua Goins changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #13 from Joshua Goins --- I believe it, still having trouble replicating it unfortunately :/ Interesting that this happens on Flatpak too, I might try that next -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476563] Lockscreen shows black screen without possibility to back to normal
https://bugs.kde.org/show_bug.cgi?id=476563 Piotr Mierzwinski changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #7 from Piotr Mierzwinski --- (In reply to Nate Graham from comment #6) > > Alt+F2 doesn't work > It's actually Alt+Ctrl+F3. Hit that, and then hit Alt+Ctrl+F2 again. Does > that resolve it? > > Is this with a laptop, or a desktop? Such switching doesn't help, even restart of sddm (sudo killall sddm). Workaround is to plug off power cord and plug it again. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 322922] Dolphin should not store .directory files inside the actual directory to avoid cluttering and polluting the filesystem; should instead store this data in extended attributes
https://bugs.kde.org/show_bug.cgi?id=322922 King Kang Kong changed: What|Removed |Added CC||r2b2x3+kde...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 477068] DB must be purged whenever the DB scheme/contents change in an incompatible way
https://bugs.kde.org/show_bug.cgi?id=477068 Stefan Brüns changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=475919 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 475919] Dolphin search shows doubled results
https://bugs.kde.org/show_bug.cgi?id=475919 Stefan Brüns changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=477068 CC||stefan.bruens@rwth-aachen.d ||e -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 477068] DB must be purged whenever the DB scheme/contents change in an incompatible way
https://bugs.kde.org/show_bug.cgi?id=477068 Stefan Brüns changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=474973 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 474973] baloosearch (as well as Dolphin and other apps using baloo) do not find anything when serching files inside the Downloads directory
https://bugs.kde.org/show_bug.cgi?id=474973
Stefan Brüns changed:
What|Removed |Added
CC||stefan.bruens@rwth-aachen.d
||e
See Also||https://bugs.kde.org/show_b
||ug.cgi?id=477068
--- Comment #31 from Stefan Brüns ---
(In reply to tagwerk19 from comment #27)
> Maybe I'm a step further. I have a system where I see the same behaviour,
> something I consider a remarkable step forward 8-/
>
> Bad news is it's a "bashed about" Neon Unstable, not something I can
> reproduceably rebuild. Further bad news is that if I leave the configuration
> and test files untouched, do a "balooctl6 purge" and reindex, the behaviour
> goes away.
>
> That would help explain why the issue is so slippery. It also means that
> when you have the issue, copy your .local/share/baloo/index somewhere safe
> so you can go back to it.
>
> It's also quite possible that this is one cause of the problem rather then
> "the" cause, but what I see is:
>
>$ baloosearch -i test
> 144044ed0da2dd /home/test/testfiles/test.txt
> 14ba61fc01 /home/test/testfiles
> 14ba61ed0da2dd /home/test/testfiles
> Elapsed: 0.297092 msecs
>
> [...]
>
> $ baloosearch -i test
> 144044ed0da2dd /home/test/testfiles/test.txt
> 14ba61ed0da2dd /home/test/testfiles
> Elapsed: 0.410179 msecs
>
> $ baloosearch -i -d /home/test/testfiles test
> 144044ed0da2dd /home/test/testfiles/test.txt
> 14ba61ed0da2dd /home/test/testfiles
> Elapsed: 0.307979 msecs
>
> The index has two records for the /home/test/testfiles folder with different
> DocIDs and the "test.txt" file was created with the new format DocID and it
> was not found in the search. After the reindex, it was found.
("WARNING: term points to unknown document 5698695752383489 (/???)" - that is
143eeffc01 in hex, so it points to the same problem)
@tagwerk19 Thanks for investigating this.
I think the conclusion this is caused by the change of the FSID generation
(https://invent.kde.org/frameworks/baloo/-/merge_requests/131) is spot on, and
shows that the MR is missing the required safety measures. (Although the MR
mentioned this problem explicitly.)
The change was obviously not tested and analyzed for possible side effect. But
my reservations were unfortunately just ignored, and the change merged
nevertheless, without prior notice (24 minutes from removing the Draft status,
"resolving" all comments and merging it).
After the change, the DB contents are semantically garbage, and the DB has to
be purged (You have noticed this before, I know). This should have been done
automatically, but nobody implemented it. Nobody announced the breakage to the
broader public.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-baloo] [Bug 477068] New: DB must be purged whenever the DB scheme/contents change in an incompatible way
https://bugs.kde.org/show_bug.cgi?id=477068 Bug ID: 477068 Summary: DB must be purged whenever the DB scheme/contents change in an incompatible way Classification: Frameworks and Libraries Product: frameworks-baloo Version: 5.112.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: stefan.bru...@rwth-aachen.de CC: tagwer...@innerjoin.org Target Milestone: --- Up to now code changes were done to no cause any incompatibility issues with existing DB contents, but unfortunate https://invent.kde.org/frameworks/baloo/-/merge_requests/131 introduced such a change. To be able to deal with such issues, the DB should contain a version to notify about incompatible changes of the DB scheme etc. The DB should be recreated in such a case, and the library should check if the DB is compatible (which could happen with e.g. KF5 and KF6 installed at the same time). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476996] Allow window border to render on plasmashell windows too.
https://bugs.kde.org/show_bug.cgi?id=476996 Nate Graham changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #6 from Nate Graham --- No, it's not explained anywhere. Not everything is or even needs to be explained. If developers explained every reason behind every aspect of the system, they would spend all their time doing that, and no time actually developing it. Life's too short. :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477016] Brightness flicker with adaptive sync
https://bugs.kde.org/show_bug.cgi?id=477016 --- Comment #2 from wokim --- (In reply to Zamundaaa from comment #1) > It's not a bug, Mesa enabling or disabling vrr for specific fullscreen > programs is an X11 thing and has no relevance on Wayland. > The brightness flicker is something that I consider a bug, and one that > should be fixable in KWin. The brightness flicker is fixable by disabling VRR for any fullscreen desktop programs with (frequent) user input, like Firefox. I just tested it in Windows 10, and there VRR is also disabled in browsers when they're fullscreen. And as many programs/games don't play nice with VRR (causing flickering and/or stuttering), it would be very nice to be able to add a rule property in Window Rules that controls VRR for a certain window/program. As a side note, being able to add a rule property in Window Rules that can automatically set a refresh rate depending on the program/game would also be great. Though a lot less important than being able to control VRR per program/game. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 477046] shortcut causing window switch often causes stuck modifiers (data loss possible)
https://bugs.kde.org/show_bug.cgi?id=477046 --- Comment #1 from Denis Lisov --- I'm not really sure whether this is a problem with Yakuake or with the component that provides global shortcut handling in the Wayland session (not sure what exactly that component is). I haven't managed to reproduce it without Yakuake yet, but the reproducer is not 100% reliable for me, so I'm not sure it's not there. Another interesting point is that is affects not only the app I switch to, but also the global shortcut handling - Esc opens/closes task manager like Ctrl+Esc, `=` opens/closes Yakuake like Ctrl+= is configured to, etc. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland on VMs (VMWare, VirtualBox, ...)
https://bugs.kde.org/show_bug.cgi?id=427060 --- Comment #47 from Michael SB --- (In reply to hallucynogenyc from comment #46) > same issue > > fresh arch install > vmware workstation player 17 Yeah this bug on Plasma Wayland has been persisting for a long time across distros, while Plasma x11 session behaves quite sluggish on VMWare Player (for example resizing windows), which unfortunately has rendered KDE unusable for me as guest on my work Windows PC. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477067] plasmashell crashes on global theme change
https://bugs.kde.org/show_bug.cgi?id=477067 fanzhuyi...@gmail.com changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477067] New: plasmashell crashes on global theme change
https://bugs.kde.org/show_bug.cgi?id=477067 Bug ID: 477067 Summary: plasmashell crashes on global theme change Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Global Theme packages Assignee: plasma-b...@kde.org Reporter: fanzhuyi...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 163206 --> https://bugs.kde.org/attachment.cgi?id=163206=edit backtrace Application: plasmashell (5.81.0) Qt Version: 6.6.0 Frameworks Version: 5.245.0 Operating System: Linux 6.2.0-36-generic x86_64 Windowing System: Wayland Distribution: KDE neon Unstable Edition DrKonqi: 5.81.0 [CoredumpBackend] -- Information about the crash: Steps to reproduce: 1. open settings, go to global theme 2. select any different theme, select both appearance settings and desktop and window layout 3. click apply Observed behavior: plasmashell crashes The crash can be reproduced every time. -- Backtrace: Application: plasmashell (plasmashell), signal: Segmentation fault -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465354] Sub-menus go under panel on Wayland
https://bugs.kde.org/show_bug.cgi?id=465354 Bug Janitor Service changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland on VMs (VMWare, VirtualBox, ...)
https://bugs.kde.org/show_bug.cgi?id=427060 hallucynoge...@gmail.com changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED CC||hallucynoge...@gmail.com --- Comment #46 from hallucynoge...@gmail.com --- same issue fresh arch install vmware workstation player 17 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477066] New: When resuming from sleep my primary monitor changes
https://bugs.kde.org/show_bug.cgi?id=477066 Bug ID: 477066 Summary: When resuming from sleep my primary monitor changes Classification: Plasma Product: plasmashell Version: 5.27.9 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: jus...@kde.org CC: notm...@gmail.com Target Milestone: 1.0 1. Suspend device with multiple monitors 2. Wake up device Observed result: The first monitor that wakes up becomes the primary. Desired result: No change in primary display Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.11-300.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474382] On Wayland, no titlebar buttons on CSD-using Firefox in Plasma 6
https://bugs.kde.org/show_bug.cgi?id=474382 guimarcalsi...@gmail.com changed: What|Removed |Added Summary|On X11, no titlebar buttons |On Wayland, no titlebar |on CSD-using Firefox in |buttons on CSD-using |Plasma 6|Firefox in Plasma 6 --- Comment #14 from guimarcalsi...@gmail.com --- (In reply to fanzhuyifan from comment #11) > Created attachment 163203 [details] > gedit works > > (In reply to Nate Graham from comment #10) > > Thanks. Can you also reproduce this issue in other CSD apps that are not > > using Libadwaita? For example Telegram and Gedit (not GNOME Text). Or is it > > only Firefox? > > Cannot reproduce on telegram and gedit. See attachments > Also I forgot to mention that all these tests have been happening on wayland > (not sure why there is a X11 in the title) > Tested all three default themes, with same result (breeze, breeze-dark, > breeze-twilight) Oh yeah you're right. This affects Wayland, not X. I think I pasted the wrong "about system" info in the OP and that must have caused the confusion. I'll update the title. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474382] On X11, no titlebar buttons on CSD-using Firefox in Plasma 6
https://bugs.kde.org/show_bug.cgi?id=474382 fanzhuyi...@gmail.com changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474382] On X11, no titlebar buttons on CSD-using Firefox in Plasma 6
https://bugs.kde.org/show_bug.cgi?id=474382 --- Comment #13 from fanzhuyi...@gmail.com --- Created attachment 163205 --> https://bugs.kde.org/attachment.cgi?id=163205=edit firefox does not work -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474382] On X11, no titlebar buttons on CSD-using Firefox in Plasma 6
https://bugs.kde.org/show_bug.cgi?id=474382 --- Comment #12 from fanzhuyi...@gmail.com --- Created attachment 163204 --> https://bugs.kde.org/attachment.cgi?id=163204=edit telegram works -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474382] On X11, no titlebar buttons on CSD-using Firefox in Plasma 6
https://bugs.kde.org/show_bug.cgi?id=474382 --- Comment #11 from fanzhuyi...@gmail.com --- Created attachment 163203 --> https://bugs.kde.org/attachment.cgi?id=163203=edit gedit works (In reply to Nate Graham from comment #10) > Thanks. Can you also reproduce this issue in other CSD apps that are not > using Libadwaita? For example Telegram and Gedit (not GNOME Text). Or is it > only Firefox? Cannot reproduce on telegram and gedit. See attachments Also I forgot to mention that all these tests have been happening on wayland (not sure why there is a X11 in the title) Tested all three default themes, with same result (breeze, breeze-dark, breeze-twilight) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476833] folder view in a panel
https://bugs.kde.org/show_bug.cgi?id=476833 --- Comment #4 from Massimiliano Agosti --- Shortcuts are working correctly from Dolphin . I copied the shorcut on the Desktop; it works. It's Folder View widgets that does not work properly anymore since a recent update (from Backports ppa I presume). I personalized the default icon of folders; I still see it in Dolphin but no more in Folder View widget where it's shown like the classic Brezza one. Il 15/11/23 23:58, Nate Graham ha scritto: > https://bugs.kde.org/show_bug.cgi?id=476833 > > --- Comment #3 from Nate Graham --- > Can you try giving them execute permissions and see if that helps? > > If you move the shortcuts to the desktop (the actual desktop, as in navigate > to > "desktop://" in Dolphin) and then open them, does it work? > -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380514] KDE Discover doesn't make adequate use of user reviews
https://bugs.kde.org/show_bug.cgi?id=380514
`{third: "Beedell", first: "Roke"}`{.JSON5}
changed:
What|Removed |Added
CC||rvdois+RVU4Z9@rokejulianloc
||khart.anonaddy.com
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 382251] Discover could use an "open " button that appears for installed software
https://bugs.kde.org/show_bug.cgi?id=382251
`{third: "Beedell", first: "Roke"}`{.JSON5}
changed:
What|Removed |Added
CC||rvdois+RVU4Z9@rokejulianloc
||khart.anonaddy.com
--
You are receiving this mail because:
You are watching all bug changes.
[kde] [Bug 476960] Manual screen RGB color adjustment, outside of applying an ICC profile
https://bugs.kde.org/show_bug.cgi?id=476960 --- Comment #6 from tomasbe...@protonmail.com --- Like how xrandr can manipulate gamma for the final output, I believe you can manually adjust the RGB balance while keeping the ICC profile you are using. In practice and visually, the manual adjustment would be on top of the resulting color output from the profile. If generating an ICC profile also gives the expected result then either way is fine. My digital art is hobbyist, but even if I wasn't an artist, I would still like to fix the white balance and tint of my screen so white is pure white and not a greenish white. It really increases the color quality of the screen and the experience is much better. We don't always rely on just ICC profiles for calibration. Even on professional monitors the built-in settings for RGB balance, gamma, etc are very useful. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405935] Allow people to change the name used for their reviews
https://bugs.kde.org/show_bug.cgi?id=405935
--- Comment #3 from `{third: "Beedell", first: "Roke"}`{.JSON5}
---
Is this still possible? I don't see any option to do so.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 476483] Scrollbar handles are incorrectly sized and positioned until the window is resized
https://bugs.kde.org/show_bug.cgi?id=476483 --- Comment #6 from ratijas --- Git commit f6f39673e58e42ab195a44ab39dfea1c6b59ee6c by ivan tkachenko. Committed on 15/11/2023 at 23:14. Pushed by ratijas into branch 'master'. ScrollBar: Drop workaround for size being initially stuck on Qt 6 Fixed upstream for Qt 6.6+ M +1-6org.kde.desktop/ScrollBar.qml https://invent.kde.org/frameworks/qqc2-desktop-style/-/commit/f6f39673e58e42ab195a44ab39dfea1c6b59ee6c -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405935] Allow people to change the name used for their reviews
https://bugs.kde.org/show_bug.cgi?id=405935
`{third: "Beedell", first: "Roke"}`{.JSON5}
changed:
What|Removed |Added
CC||rvdois+RVU4Z9@rokejulianloc
||khart.anonaddy.com
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 476982] Support pen calibration in UI
https://bugs.kde.org/show_bug.cgi?id=476982 --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1833 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476813] Plasmashell crash trying to change global theme
https://bugs.kde.org/show_bug.cgi?id=476813 Nate Graham changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #8 from Nate Graham --- Ok, let's call it fixed for now. Things are moving quickly at the moment. :) I thikn the issue with debug symbols is a Neon bug; see Bug 476912. -- You are receiving this mail because: You are watching all bug changes.
[XWaylandVideoBridge] [Bug 474966] On Gnome, a thin white line will appear on the top left of the secondary monitor screen when XWaylandVideoBridge is running. After using screen-capture then terminat
https://bugs.kde.org/show_bug.cgi?id=474966 --- Comment #2 from keith.farwell...@gmail.com --- Comment on attachment 163200 --> https://bugs.kde.org/attachment.cgi?id=163200 Shows the linme of white pixels that appears when XWaylandVideoBridge is running STEPS TO REPRODUCE 1. Have a single monitor using the Gnome Desktop Environment 2. Open or have running in the background the XWaylandVideoBridge OBSERVED RESULT: A thin white line is present at the top-left corner, the same length as an icon tile. EXPECTED RESULT: No such line should be present SOFTWARE/OS VERSIONS OS: Nobara Linux 38 Kernel: 6.5.9-201.fsync.fc38.x86_64 DE: Gnome 44.2 (extensions enabled) Extensions Enabled: AppIndicator and KStatusNotifierItem Support ArcMenu DashToPanel DesktopIcons NG GameMode Just Perfection Wireless HID Windowing System: Wayland GPU: Radeon 7900 XTX Additional Infromation: This white line disappears if a window is placed over it, a game is started, or when moving to an alternate workspace. However, when returning back to the desktop environment or the default workspace, the line reappears. Monitor is a 240Hz 2560x1440p SDR landscape. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474382] On X11, no titlebar buttons on CSD-using Firefox in Plasma 6
https://bugs.kde.org/show_bug.cgi?id=474382 Nate Graham changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Severity|normal |major Resolution|--- |WAITINGFORINFO Summary|No titlebar buttons on |On X11, no titlebar buttons |CSD-using Firefox in Plasma |on CSD-using Firefox in |6 |Plasma 6 --- Comment #10 from Nate Graham --- Thanks. Can you also reproduce this issue in other CSD apps that are not using Libadwaita? For example Telegram and Gedit (not GNOME Text). Or is it only Firefox? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476492] On Framework laptop, while lid is closed, system does not stay asleep if power cable is connected
https://bugs.kde.org/show_bug.cgi?id=476492 --- Comment #7 from Jeremi Campagna --- (In reply to Natalie Clarius from comment #6) > (In reply to Jeremi Campagna from comment #5) > > > more often than not > > So sometimes it does go back to sleep? Immediately or after some period? If it does, it seems to be immediate. It's not exactly reliable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476813] Plasmashell crash trying to change global theme
https://bugs.kde.org/show_bug.cgi?id=476813 --- Comment #7 from iodream...@gmail.com --- There was an update through the package manager recently and i couldn't trigger the bug anymore. I thought i would wait for an iso update and see if the bug is still there and report after that. If it is i will try to install the debug packages. I did wonder however why the debuginfod produced an incomplete trace. I guess this is because the debuginfod server doesn't have all the qt6 symbols? -- You are receiving this mail because: You are watching all bug changes.
