[korganizer] [Bug 475679] New: Search shows no results
https://bugs.kde.org/show_bug.cgi?id=475679 Bug ID: 475679 Summary: Search shows no results Classification: Applications Product: korganizer Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: kdepim-b...@kde.org Reporter: david.perez.ingeni...@gmail.com Target Milestone: --- Created attachment 162340 --> https://bugs.kde.org/attachment.cgi?id=162340=edit screenshot in italian language SUMMARY STEPS TO REPRODUCE 1. I have a calendar with lots of data, in a personal calendar stored in a local file. 2. I search for a string I know it is very frequent, by pressing Ctrl+F. 3. I select of the "search in" options and by type of event. 4. I select the right date range. OBSERVED RESULT No results. For some other keywords I get some results. EXPECTED RESULT Lots of results SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Plasma based on Ubuntu 22.04 (available in About System) KDE Plasma Version: 5.27 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 472230] Kate crashed when switching files with Ctrl+Tab
https://bugs.kde.org/show_bug.cgi?id=472230 --- Comment #10 from Waqar Ahmed --- If you find a way to reproduce this that would be great. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472901] Screen flickers when switching virtual desktop with touchpad gesture and animations are off
https://bugs.kde.org/show_bug.cgi?id=472901 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/4507 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 475614] crash after Ctrl+Tab after updating to 23.04.3
https://bugs.kde.org/show_bug.cgi?id=475614 Waqar Ahmed changed: What|Removed |Added CC||waqar@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Waqar Ahmed --- *** This bug has been marked as a duplicate of bug 472230 *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 472230] Kate crashed when switching files with Ctrl+Tab
https://bugs.kde.org/show_bug.cgi?id=472230 --- Comment #9 from Waqar Ahmed --- *** Bug 475614 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #42 from pallaswept --- (In reply to pallaswept from comment #41) > Literally every way but one (be running KDE). I just said this but then I realised there's not even that one way - let's not forget, this: > Remember that my original reason for being here was that I had built a > software package on the desktop, and the files had since been deleted, but > their entries were still there in the list in the config file. happened in a KDE session (I'm ALWAYS in a KDE session, it's the best, why would I not be? :) ) So it'll *always* do it if KDE isn't running, and *sometimes even when it is*. The point is there's a theoretically insanely high number of ways to trigger this and it doesn't matter what they are if you just, to quote the second sentence of my first post: > To fix this will require two parts, firstly to only track items directly ON > the desktop, and NOT their contents, Which Harald has now done, yay! > and secondly, to REMOVE items that are no longer present on the desktop. Which is why I said it was important to get this second part done, to be, as Harald put it, "comprehensive" in the solution. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 475672] marble crashed when starting in GNOME
https://bugs.kde.org/show_bug.cgi?id=475672 Matt Fagnani changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Matt Fagnani --- This problem didn't happen after I updated to qadwaitadecorations-0.1.2-5.fc39 https://bodhi.fedoraproject.org/updates/FEDORA-2023-69e9a0f475 which was marked as fixing a kdenlive crash with a similar trace https://bugzilla.redhat.com/show_bug.cgi?id=2244239 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 475636] System Monitor crashed sometimes when starting in GNOME with the error "stack smashing detected"
https://bugs.kde.org/show_bug.cgi?id=475636 Matt Fagnani changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Matt Fagnani --- This problem didn't happen after I updated to qadwaitadecorations-0.1.2-5.fc39 https://bodhi.fedoraproject.org/updates/FEDORA-2023-69e9a0f475 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #41 from pallaswept --- Oh and BTW that means that 'N' was infinite because all we have to do to reproduce this is not be running KDE when we remove the files and there are practically infinite ways to go about that. Literally every way but one (be running KDE). So you can see why I wasn't satisfied with my first and now proven correct description of the nature of the fault being ignored and told to go log a new case. I think I've made my point sufficiently, yeh? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #40 from pallaswept --- There, I reproduced it. Create the three foo*.txt files exactly as above Log out Log into IceWM session Open xterm Delete foo*.txt files Result: cat .config/plasma-org.kde.plasma.desktop-appletsrc | rg screenmapping [ScreenMapping] screenMapping=desktop:/tmuxkeys3.txt,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/pwdumpalways2.txt,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/userworking/pipewire.service,1,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/foo1.txt,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/tmuxkeys2.conf.txt,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/pwdumpxbox.txt,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/userworking/default.target.wants/ydotool.service,1,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/userworking/wireplumber.service,1,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/foo2.txt,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/jctlpw.txt,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/userworking/pipewire-pulse.service,1,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/tmuxkeys.conf.txt,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,file:///home/pallaswept/Desktop/Mouse-actions GUI.desktop,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/OpenRGB.desktop,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/userworking/default.target.wants,1,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/userworking/dbus-org.bluez.obex.service,1,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/userworking/pipewire.socket,1,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/Media,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/foo3.txt,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef ~ls Desktop/ total 119M 0 drwxr-xr-x 1 pallaswept pallaswept 218 Oct 16 14:52 ./ 0 drwx--x---+ 1 pallaswept pallaswept 1.2K Oct 16 14:53 ../ 115M -rw-r--r-- 1 pallaswept pallaswept 115M Oct 1 19:22 jctlpw.txt 0 drwxr-xr-x 1 pallaswept pallaswept 478 Sep 10 02:50 Media/ 4.0K -rwx-- 1 pallaswept pallaswept 305 Aug 25 02:30 OpenRGB.desktop* 1.6M -rw-r--r-- 1 pallaswept pallaswept 1.6M Oct 5 17:49 pwdumpalways2.txt 1.6M -rw-r--r-- 1 pallaswept pallaswept 1.6M Oct 16 06:15 pwdumpxbox.txt 28K -rw-r--r-- 1 pallaswept pallaswept 27K Oct 4 21:36 tmuxkeys2.conf.txt 32K -rw-r--r-- 1 pallaswept pallaswept 30K Oct 6 05:44 tmuxkeys3.txt 32K -rw-r--r-- 1 pallaswept pallaswept 29K Oct 2 15:29 tmuxkeys.conf.txt Note the foo*.txt file still present in the screenmapping section but no longer exist since I just deleted them. First I tried just dropping to a TTY by hiting ctrl+alt+f5, logging in as a different user (root because why not) and deleting them when KDE was still running, and then I ctrl+alt F1 back to my running KDE session and it had instantly removed them from the screenmappinges entry. So I figured, let's not do it with KDE running, and see how it fares. Now we know. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 474708] Crash on exit after editing a project... Possibly related to having deleted a sequence clip.
https://bugs.kde.org/show_bug.cgi?id=474708 --- 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.
[kdenlive] [Bug 473434] Project Playback Delay and Program Crash
https://bugs.kde.org/show_bug.cgi?id=473434 --- 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.
[kdeconnect] [Bug 474394] The name org.kde.kdeconnect was not provided by any .service fil
https://bugs.kde.org/show_bug.cgi?id=474394 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |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.
[kmymoney] [Bug 475108] New Transaction Crashes App
https://bugs.kde.org/show_bug.cgi?id=475108 --- 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.
[kdenlive] [Bug 471034] Try opening kdenlive file and application crashes repeatedly. Tried other files with different names...repeats crash
https://bugs.kde.org/show_bug.cgi?id=471034 --- 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.
[kdenlive] [Bug 443028] kdenlive 21.08.1 crashes on start (Neon 5.22)
https://bugs.kde.org/show_bug.cgi?id=443028 --- 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.
[kdenlive] [Bug 452833] [libvpx @0000000002bcb340] Transparency encoding with auto_alt_ref does not work Rotoscope render
https://bugs.kde.org/show_bug.cgi?id=452833 --- 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.
[kdenlive] [Bug 440191] Audio wont render
https://bugs.kde.org/show_bug.cgi?id=440191 --- 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.
[kwin] [Bug 475677] Dragging a Window with Wobbly Windows Enabled Inappropriately Resizes the Window
https://bugs.kde.org/show_bug.cgi?id=475677 Dashon changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #5 from Dashon --- I resolved the issue by nuking a bunch of files in .local. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #39 from pallaswept --- More specifics to show that the entries in my screenmapping are nonexistent files: ls ~/Desktop/userworking ls: cannot access '/home/pallaswept/Desktop/userworking': No such file or directory <--- Isn't this there and full of backups of systemd unit files? find ~/Desktop/ -name *.service 2 find ~/Desktop/ -name *.socket find ~/Desktop/ -name *.desktop /home/pallaswept/Desktop/OpenRGB.desktop <--- where is Mouse-actions GUI.desktop? IT IS A THING I SWEAR. So, to fix this, you have two ways that can work: 1) Find every possible way out of an undefined number of possible ways, to remove a file, and have it left in the list, and fix every one of them (ie hey, pallaswept, I can't reproduce it, so you reproduce it, N times for the N variations that cause this (N being an undefined number that could be infinite for all we know), and log a new case N times) OR Just check that the entries in the list actually exist and remove them if they don't. Tell me which one is more sane. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 475678] New: Erro ao usar o Assistente de Conffiguração de E-mail do Kmail
https://bugs.kde.org/show_bug.cgi?id=475678 Bug ID: 475678 Summary: Erro ao usar o Assistente de Conffiguração de E-mail do Kmail Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Account Wizard Assignee: kdepim-b...@kde.org Reporter: marleysantos...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: accountwizard (0.2) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 5.14.21-150500.55.31-default x86_64 Windowing System: X11 Distribution: "openSUSE Leap 15.5" DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: Estava tentando configurar meus e-mails e do nada o Assitente deu crash The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Assistente de contas (accountwizard), signal: Segmentation fault [KCrash Handler] #4 0x7fa57c40cabb in QVector::indexOf (from=0, t=: 0x55dacb814f50, this=0x55dacb873ac0) at ../../include/QtCore/../../src/corelib/tools/qvector.h:1009 #5 QAbstractItemModelPrivate::removePersistentIndexData (this=0x55dacb817900, data=data@entry=0x55dacb814f50) at itemmodels/qabstractitemmodel.cpp:648 #6 0x7fa57c40ccf9 in QPersistentModelIndexData::destroy (data=0x55dacb814f50) at itemmodels/qabstractitemmodel.cpp:87 #7 0x7fa57d28714a in QAbstractItemViewPrivate::~QAbstractItemViewPrivate (this=0x55dacb85ec40, __in_chrg=) at itemviews/qabstractitemview.cpp:125 #8 0x7fa57d2b9df9 in QListViewPrivate::~QListViewPrivate (this=0x55dacb85ec40, __in_chrg=) at itemviews/qlistview.cpp:1765 #9 0x7fa57c4a95d6 in QScopedPointerDeleter::cleanup (pointer=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:60 #10 QScopedPointer >::~QScopedPointer (this=0x55dacb76a328, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:107 #11 QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:990 #12 0x7fa57d05f8bb in QWidget::~QWidget (this=0x55dacb76a320, __in_chrg=) at kernel/qwidget.cpp:1402 #13 0x7fa57d12f60d in QComboBoxListView::~QComboBoxListView (this=0x55dacb76a320, __in_chrg=) at ../../include/QtWidgets/5.15.8/QtWidgets/private/../../../../../src/widgets/widgets/qcombobox_p.h:84 #14 QComboBoxListView::~QComboBoxListView (this=0x55dacb76a320, __in_chrg=) at ../../include/QtWidgets/5.15.8/QtWidgets/private/../../../../../src/widgets/widgets/qcombobox_p.h:84 #15 0x7fa57c49ebeb in QObjectPrivate::deleteChildren (this=this@entry=0x55dacb8a7d60) at kernel/qobject.cpp:2137 #16 0x7fa57d05f836 in QWidget::~QWidget (this=0x55dacb8b8c30, __in_chrg=) at kernel/qwidget.cpp:1524 #17 0x7fa57d132fcd in QComboBoxPrivateContainer::~QComboBoxPrivateContainer (this=0x55dacb8b8c30, __in_chrg=) at ../../include/QtWidgets/5.15.8/QtWidgets/private/../../../../../src/widgets/widgets/qcombobox_p.h:214 #18 QComboBoxPrivateContainer::~QComboBoxPrivateContainer (this=0x55dacb8b8c30, __in_chrg=) at ../../include/QtWidgets/5.15.8/QtWidgets/private/../../../../../src/widgets/widgets/qcombobox_p.h:214 #19 0x7fa57c49ebeb in QObjectPrivate::deleteChildren (this=this@entry=0x55dacb809420) at kernel/qobject.cpp:2137 #20 0x7fa57d05f836 in QWidget::~QWidget (this=0x55dacb8a3870, __in_chrg=) at kernel/qwidget.cpp:1524 #21 0x7fa57db237f9 in Kleo::KeySelectionCombo::~KeySelectionCombo (this=0x55dacb8a3870, __in_chrg=) at /usr/src/debug/libkleo-22.12.3-bp155.1.6.x86_64/src/ui/keyselectioncombo.h:29 #22 0x7fa57c49ebeb in QObjectPrivate::deleteChildren (this=this@entry=0x55dacb816640) at kernel/qobject.cpp:2137 #23 0x7fa57d05f836 in QWidget::~QWidget (this=0x55dacb7dedc0, __in_chrg=) at kernel/qwidget.cpp:1524 #24 0x55dac9eaa527 in Page::~Page (this=0x55dacb7dedc0, __in_chrg=) at /usr/src/debug/kmail-account-wizard-22.12.3-bp155.1.9.x86_64/build/src/accountwizard_autogen/EWIEGA46WW/../../../../src/page.h:14 #25 CryptoPage::~CryptoPage (this=0x55dacb7dedc0, __in_chrg=) at /usr/src/debug/kmail-account-wizard-22.12.3-bp155.1.9.x86_64/build/src/accountwizard_autogen/EWIEGA46WW/../../../../src/cryptopage.h:24 #26 CryptoPage::~CryptoPage (this=0x55dacb7dedc0, __in_chrg=) at /usr/src/debug/kmail-account-wizard-22.12.3-bp155.1.9.x86_64/build/src/accountwizard_autogen/EWIEGA46WW/../../../../src/cryptopage.h:24 #27 0x7fa57c49ebeb in QObjectPrivate::deleteChildren (this=this@entry=0x55dacb718090) at kernel/qobject.cpp:2137 #28 0x7fa57d05f836 in QWidget::~QWidget (this=0x55dacb719350, __in_chrg=) at kernel/qwidget.cpp:1524 #29 0x7fa57b5cf1bd in KPageStackedWidget::~KPageStackedWidget (this=0x55dacb719350, __in_chrg=) at
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #38 from pallaswept --- Just to be more precise, here's my alias so that you can be sure my 'ls' listing that shows all the files in the directory (none are hidden) and also shows that the list contains all the files that do exist, and a bunch of files that don't exist: alias ls='ls -shalF --color' -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #37 from pallaswept --- Here I can prove it easier than I thought. My intention was to create a few files on the desktop, have them added to the screenmapping entry, then try a few different ways to remove them until I found one that made it remain in the screenmapping entry. So I did this, making these 3 'foo' files on the desktop: ~>echo foo1 > ~/Desktop/foo1.txt ~>echo foo1 > ~/Desktop/foo2.txt ~>echo foo1 > ~/Desktop/foo3.txt Then I thought, I'll check the screenmapping and make sure they've been added, before I try to remove them and have them remain in that list ~>cat .config/plasma-org.kde.plasma.desktop-appletsrc | rg screenmapping [ScreenMapping] screenMapping=desktop:/userworking/default.target.wants/ydotool.service,1,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/userworking/default.target.wants,1,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/Media,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/userworking/dbus-org.bluez.obex.service,1,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/userworking/pipewire-pulse.service,1,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/pwdumpxbox.txt,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/tmuxkeys2.conf.txt,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/userworking/pipewire.service,1,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/userworking/wireplumber.service,1,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/foo1.txt,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/tmuxkeys3.txt,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/foo2.txt,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/foo3.txt,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/OpenRGB.desktop,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/tmuxkeys.conf.txt,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/jctlpw.txt,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/userworking/pipewire.socket,1,daba52e7-d61d-46e5-a570-bf4e3a1014ef,file:///home/pallaswept/Desktop/Mouse-actions GUI.desktop,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef,desktop:/pwdumpalways2.txt,0,daba52e7-d61d-46e5-a570-bf4e3a1014ef WTF. Half of those files don't even exist already. Proof: ~>ls ~/Desktop total 119M 0 drwxr-xr-x 1 pallaswept pallaswept 266 Oct 16 14:07 ./ 0 drwx--x---+ 1 pallaswept pallaswept 1.2K Oct 16 12:58 ../ 4.0K -rw-r--r-- 1 pallaswept pallaswept5 Oct 16 14:07 foo1.txt 4.0K -rw-r--r-- 1 pallaswept pallaswept5 Oct 16 14:07 foo2.txt 4.0K -rw-r--r-- 1 pallaswept pallaswept5 Oct 16 14:07 foo3.txt 115M -rw-r--r-- 1 pallaswept pallaswept 115M Oct 1 19:22 jctlpw.txt 0 drwxr-xr-x 1 pallaswept pallaswept 478 Sep 10 02:50 Media/ 4.0K -rwx-- 1 pallaswept pallaswept 305 Aug 25 02:30 OpenRGB.desktop* 1.6M -rw-r--r-- 1 pallaswept pallaswept 1.6M Oct 5 17:49 pwdumpalways2.txt 1.6M -rw-r--r-- 1 pallaswept pallaswept 1.6M Oct 16 06:15 pwdumpxbox.txt 28K -rw-r--r-- 1 pallaswept pallaswept 27K Oct 4 21:36 tmuxkeys2.conf.txt 32K -rw-r--r-- 1 pallaswept pallaswept 30K Oct 6 05:44 tmuxkeys3.txt 32K -rw-r--r-- 1 pallaswept pallaswept 29K Oct 2 15:29 tmuxkeys.conf.txt Notice all the entries in the screenmapping that don't even exist in the file listing? btw I alias ls to 'ls -Flash', so no, they aren't hidden or something. They're files I deleted ages ago. -- 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 #30 from Pollux --- (In reply to Yao Mitachi from comment #29) > (In reply to Torabi from comment #28) > > For FFXIV, setting the mouse cursor to the software cursor appears to fix > > the problem for me. > > If you have the window unfocused, and then click on it, does the camera view > snap to point at the top of your character's head, like it does for me? Yeah that happens to me aswell when playing games like overwatch, apex, cs2 etc -- 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 #29 from Yao Mitachi --- (In reply to Torabi from comment #28) > For FFXIV, setting the mouse cursor to the software cursor appears to fix > the problem for me. If you have the window unfocused, and then click on it, does the camera view snap to point at the top of your character's head, like it does for me? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 372408] Option to omit shadow and transparent border from windows in Active Window and Window Under Cursor modes
https://bugs.kde.org/show_bug.cgi?id=372408 daant...@gmail.com changed: What|Removed |Added CC||daant...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376425] Light table window not activated or brought to front
https://bugs.kde.org/show_bug.cgi?id=376425 caulier.gil...@gmail.com changed: What|Removed |Added Version|8.1.0 |8.2.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376425] Light table window not activated or brought to front
https://bugs.kde.org/show_bug.cgi?id=376425 --- Comment #12 from caulier.gil...@gmail.com --- yes both BQM and LT share the same code to brought to the front when it is selected a second time. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470391] Cannot uninstall or update Nightly build
https://bugs.kde.org/show_bug.cgi?id=470391 --- Comment #20 from Judah Richardson --- OK. Well, the signed Win64 builds are the only ones I can test because they're the only ones I can install at all -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470391] Cannot uninstall or update Nightly build
https://bugs.kde.org/show_bug.cgi?id=470391 caulier.gil...@gmail.com changed: What|Removed |Added Version|7.7.0 |8.2.0 --- Comment #19 from caulier.gil...@gmail.com --- Hi Judah No, the MXE based installer still not signed (cross compiled under Linux). Only the installer from the KDE binary factory is compiled under Windows and is signed with Microsoft tools. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 472338] No longer loading twitter timelines
https://bugs.kde.org/show_bug.cgi?id=472338 --- Comment #4 from Tallowwood --- org.kde.choqok.twitterapi: Error: "You currently have access to a subset of Twitter API v2 endpoints and limited v1.1 endpoints (e.g. media post, oauth) only. If you need access to this endpoint, you may need a different access level. You can learn more here: https://developer.twitter.com/en/portal/product; -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376825] Tag displays do not display correctly after new database is selected
https://bugs.kde.org/show_bug.cgi?id=376825 caulier.gil...@gmail.com changed: What|Removed |Added Version|5.5.0 |8.2.0 --- Comment #7 from caulier.gil...@gmail.com --- Hi Bill, SQLite core database id the binary file storing the lead information about photo stored in your collection. It's explained here : https://docs.digikam.org/fr/setup_application/database_settings.html#the-sqlite-database Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419903] Editor view very slow.
https://bugs.kde.org/show_bug.cgi?id=419903 caulier.gil...@gmail.com changed: What|Removed |Added Version|7.0.0 |8.2.0 -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 472338] No longer loading twitter timelines
https://bugs.kde.org/show_bug.cgi?id=472338 Tallowwood changed: What|Removed |Added CC||e.microco...@gmx.net --- Comment #3 from Tallowwood --- I confirm the same issue on this installation. Operating System: openSUSE Leap 15.4 Name : choqok Version: 1.7.0-lp154.47.38 Arch : x86_64 Source package : choqok-1.7.0-lp154.47.38.src -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466837] Detailed progress indicator twiddles open for every long running action
https://bugs.kde.org/show_bug.cgi?id=466837 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.2.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469643] digiKam 8.0 crashes when starting, as soon as the scanning completes
https://bugs.kde.org/show_bug.cgi?id=469643 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.2.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469643] digiKam 8.0 crashes when starting, as soon as the scanning completes
https://bugs.kde.org/show_bug.cgi?id=469643 Marvin changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #10 from Marvin --- Hi Gilles, Thank you for following up. And apologies for my disappearance from this issue. What happened was that I kept updating stable and beta versions, then started tracing the errors and deleting images that I believe were causing problems, but that took quite some time with the many decades of pictures that I've collected. At some point, when I start digiKam, I'd get an error: - You have insufficient privileges on the database. Following privileges are not assigned to you: ALTER TABLE Check your privileges on the database and restart digiKam. - The app still starts, and I can hit the OK button, then check for latest version, and initiate an upgrade. Installer would do uninstall of current version, then installs the latest, with no visible errors. As I never got through a full scan, I just decided to clean up completely, install the latest daily build 2023-10-14 I could find, create new database and let it scan all subdirectories. I'm back to this PC after several hours and I see that digiKam is still working, it has "No active process" and would like to think that the issue is gone. Thank you for your help! -- 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 --- Comment #6 from kde-bugzi...@hexology.xyz --- Created attachment 162339 --> https://bugs.kde.org/attachment.cgi?id=162339=edit coredumpctl info This is the coredump from plasmashell --replace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475677] Dragging a Window with Wobbly Windows Enabled Inappropriately Resizes the Window
https://bugs.kde.org/show_bug.cgi?id=475677 --- Comment #4 from Dashon --- I disabled wobbly windows and it is still happening. At this point I don't know what is going on. Some windows even get resized to the point that they are nonexistent and I have to kill them from system monitor. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475677] Dragging a Window with Wobbly Windows Enabled Inappropriately Resizes the Window
https://bugs.kde.org/show_bug.cgi?id=475677 --- Comment #3 from Dashon --- After swtich back to x11. It seems it is now happening there as well. I think it may have something to do with the scaling factor between wayland and x11. Seems like all types of stuff got wonky after switching between the two. -- 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 --- Comment #5 from kde-bugzi...@hexology.xyz --- Created attachment 162338 --> https://bugs.kde.org/attachment.cgi?id=162338=edit DISPLAY=:0 plasmashell --replace -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 469005] Very high memory used while screen recording (possibly cursor related)
https://bugs.kde.org/show_bug.cgi?id=469005 Dashon changed: What|Removed |Added CC||sparky123558w...@gmail.com --- Comment #13 from Dashon --- I've tested all choices in this thread, webm, mkv, mouse pointer, no mouse pointer. On a system with 64 GB of ram. Screen recording with spectacle got up to about 27GB in about 20 seconds. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #36 from pallaswept --- (In reply to Nate Graham from comment #35) > Non-existent items get removed for me. TL;DR: Try harder, because it's a thing. Remember that my original reason for being here was that I had built a software package on the desktop, and the files had since been deleted, but their entries were still there in the list in the config file. That was what caused the crash that brought me here. Like I said, I ha ve backups, I could restore them and spend a week trying to figure out exactly what I did, but let's be reasonable here. I didn't come here just for your good looks :) The failure to remove deleted files from the list in the config file is literally why I'm here. If it had added all the subdirectories (the thing that's just been patched) and then cleaned up after itself, there'd have been 4 entries in that list in the config file and the crash would have never happened. Certainly, deleting them in certain ways causes them to be removed Certainly, deleting them in other ways causes them not to be removed If you can't reproduce the failure to remove files and have them remain in the list in the config file, try harder :D Because it's a thing. It was in my first post for a reason. Just as it was for the file being added to the list in the first place - remember all the people who copied lots of files to the desktop and didn't get any entries, and said "hey I can't reproduce this" (including the man who write the fix we have now that fixes exactly what he couldn't reproduce!), but meanwhile all the reports of people with source code that was being added as subdirectories? This is that, in reverse. Sometimes you add the files and KDE knows about it and adds them to the list, sometimes you add them in some other way and it doesn't add them to the list. Sometimes you remove the files and KDE knows about it and removes them from the list, sometimes you remove them in some other way and it doesn't remove them from the list. > If you have a reproducible way to make that happen, it would be good to > submit a new bug report that indicates how you can reproduce it. Are we really going to start all over with the "I can't reproduce it, it isn't a thing", thing? It's a thing. I swear. If it weren't, I would never have even had the crash that led me to create this account to make that post that started off by explaining that it's the 2nd half of the problem. > in general this feature works, and any issues with it are edge case bugs. The feature that *does* work, is that when KDE sees it get removed, it removes it from the list. The feature that *doesn't exist*, is checking that entries which are in the list, have not been removed. There's no check to make sure it didn't miss something. That's why, when my software I built from a directory on the desktop, created thousands of files (downloading python and rust dependencies for the package I was building), and subsequently deleted them as part of the build script, and KDE didn't notice, those entries stayed in the list, and my PC crashed the next time I rebooted, and that's why I'm here. It's a thing. Reproducing it might be tricky, I get it but let's not pretend it's not a thing, and that there isn't a 'trap' there, where if, for some inexplicable reason, KDE fails to remove a non-existent file from the list, **it will never check to make sure it removed everything it should have.** -- 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 --- Comment #4 from kde-bugzi...@hexology.xyz --- Created attachment 162337 --> https://bugs.kde.org/attachment.cgi?id=162337=edit Screen after waking from sleep -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466837] Detailed progress indicator twiddles open for every long running action
https://bugs.kde.org/show_bug.cgi?id=466837 --- Comment #5 from randy.w...@gmail.com --- This is working fine now for me on Windows using both the released 8.1 and the pre-release 8.2. Thanks! On Sun, Oct 15, 2023 at 4:00 AM wrote: > https://bugs.kde.org/show_bug.cgi?id=466837 > > --- Comment #4 from caulier.gil...@gmail.com --- > @randy.w...@gmail.com, > > This problem still reproducible with the new digiKam 8.2.0 pre-release > Windows > installer available at usual place: > > https://files.kde.org/digikam/ > > This new bundle is based on last Qt framework 5.15.11 and KDE framework > 5.110. > > Thanks in advance > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475677] Dragging a Window with Wobbly Windows Enabled Inappropriately Resizes the Window
https://bugs.kde.org/show_bug.cgi?id=475677 Dashon changed: What|Removed |Added CC||sparky123558w...@gmail.com --- Comment #2 from Dashon --- Created attachment 162335 --> https://bugs.kde.org/attachment.cgi?id=162335=edit Example of the resizing Also I have the wobbly window slider on the highest setting. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475677] Dragging a Window with Wobbly Windows Enabled Inappropriately Resizes the Window
https://bugs.kde.org/show_bug.cgi?id=475677 --- Comment #1 from Dashon --- I can't seem to reproduce it on my laptop with a trackpad at 1080p, but it is super easy to trigger on my desktop at 1440p -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475677] New: Dragging a Window with Wobbly Windows Enabled Inappropriately Resizes the Window
https://bugs.kde.org/show_bug.cgi?id=475677 Bug ID: 475677 Summary: Dragging a Window with Wobbly Windows Enabled Inappropriately Resizes the Window Classification: Plasma Product: kwin Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: sparky123558w...@gmail.com Target Milestone: --- SUMMARY In a wayland session, (Doesn't Happen on Xorg). If you have wobbly windows enabled and you move the window up and down enough times. The window will slowly resize itself. STEPS TO REPRODUCE 1. Enable wobbly windows inside of system settings -> search for desktop effects -> search for wobbly windows. 2. In a wayland session, drag any resizable window by its titlebar up and down. OBSERVED RESULT Window slowly gets smaller and smaller. EXPECTED RESULT The window should stay the same size. The drag action should not trigger the resize action. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 Kernel Version: 6.5.7-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C95 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475625] Krita refuses to open recently created, and older kra files
https://bugs.kde.org/show_bug.cgi?id=475625 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 464090] Differing interaction with a top Plasma panel on Xorg and Wayland
https://bugs.kde.org/show_bug.cgi?id=464090 Dashon changed: What|Removed |Added CC||sparky123558w...@gmail.com --- Comment #2 from Dashon --- I'm also having this issue even with the panel autohidden it still starts with a few pixels in between the top of the screen and the yakuake window. Furthermore. The bottom part of yakuake's window where the tab name is also appears to be cutoff. -- 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 #28 from Torabi --- For FFXIV, setting the mouse cursor to the software cursor appears to fix the problem for me. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 471159] Spectacle screen recording doesn't cut the video correctly
https://bugs.kde.org/show_bug.cgi?id=471159 adelaune...@outlook.com changed: What|Removed |Added CC||adelaune...@outlook.com --- Comment #2 from adelaune...@outlook.com --- I experience this issue as well On Fedora 39 Prerelease KDE Plasma: 5.27.8 KDE Frameworks: 5.110.0 QT Version: 5.15.10 Kernel: 6.5.6-300.f39.x86_64 Graphics Platform: Wayland CPU: AMD Ryzen 3600 GPU: NVidia 3080 ti I have a feeling it might be Nvidia related :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475676] Dragging icons in task manager is buggy
https://bugs.kde.org/show_bug.cgi?id=475676 --- Comment #1 from mashkal2...@gmail.com --- Created attachment 162334 --> https://bugs.kde.org/attachment.cgi?id=162334=edit buggy buggy buggy had to compress the video -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475676] New: Dragging icons in task manager is buggy
https://bugs.kde.org/show_bug.cgi?id=475676 Bug ID: 475676 Summary: Dragging icons in task manager is buggy Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: mashkal2...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY As far as I can tell, there are 3 separate issues: 1) Dragging an application icon over the application launcher activates the application launcher. This should not happen - the application launcher should only activate when the mousedown event happens when the mouse is over the application launcher icon. 2) Sometimes, an application is duplicated when dragging. 3) Sometimes, applications get stuck and cannot be dragged all the way to the right. Note that this is *not* just because some of the open applications are not pinned to the taskbar - sometimes the icon be dragged gets "stuck" on an application that is *not* open but *is* pinned to the taskbar. See the attached video. All 3 issues should be readily visible. STEPS TO REPRODUCE 1. Just drag the icons around. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 Kernel Version: 6.2.0-34-generic (64-bit) Graphics Platform: X11 -- 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 rablarid...@gmail.com changed: What|Removed |Added CC||rablarid...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475635] "Show FPS" effect does nothing
https://bugs.kde.org/show_bug.cgi?id=475635 --- Comment #2 from mashkal2...@gmail.com --- After restarting my machine, it seems to work as expected now. I can't reproduce the issue any more -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 170124] Set as wallpaper on individual activities/desktops option
https://bugs.kde.org/show_bug.cgi?id=170124 Quinten Kock changed: What|Removed |Added CC||quinten@quinten.space --- Comment #27 from Quinten Kock --- I'd like to chime in to say that I would definitely like to have this. The most important consideration is that Dolphin *does* have it, shockingly, and Gwenview is much better for browsing images than Dolphin. When looking at changing my wallpaper, I currently do "browse for the right image in Gwenview -> look at the filename -> hunt for the right filename in Dolphin -> right click, set as wallpaper". Being able to do the last step directly in Gwenview would be a significant improvement. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475067] plymouth-kcm caused crash apon saving changes of boot splash screen
https://bugs.kde.org/show_bug.cgi?id=475067 rustmil...@proton.me changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |DUPLICATE --- Comment #5 from rustmil...@proton.me --- *** This bug has been marked as a duplicate of bug 449222 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449222] SystemSettings5 Crashes in KCMPlymouth::save()
https://bugs.kde.org/show_bug.cgi?id=449222 rustmil...@proton.me changed: What|Removed |Added CC||rustmil...@proton.me --- Comment #6 from rustmil...@proton.me --- *** Bug 475067 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 475675] New: Budgeting Reports Need current month and year-to-date option.
https://bugs.kde.org/show_bug.cgi?id=475675 Bug ID: 475675 Summary: Budgeting Reports Need current month and year-to-date option. Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: sbrog...@gmail.com Target Milestone: --- SUMMARY The Budget report section has Budgeted vs Actual This Year. Users would be greatly served by having this data for Current month and Year-to-date. If the range is changed to current month, the "Actual This Year" is also restricted to current month. Should be actual year-to-date. SOFTWARE/OS VERSIONS Windows: 11 macOS: Linux/KDE Plasma: (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.
[kmymoney] [Bug 475674] New: Create a Lock File when running KMyMoney
https://bugs.kde.org/show_bug.cgi?id=475674 Bug ID: 475674 Summary: Create a Lock File when running KMyMoney Classification: Applications Product: kmymoney Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: 3...@coupe7.com Target Milestone: --- I use KMM on multiple systems. My data file is shared between my various Linux systems and several backup servers via Synthing. When I forget to close KMM before opening it on a different system, I can end up with 2 versions of the KMM data file. I have created a workaround with a script that starts KMM (kmymoney.sh). It checks to see if there is a lock file present at the designated path. If the lock file is present, I use Zenity to display a message that file is already open on a different system and I display the name of the system where KMM is already running. If the lock file is not present, I create the lock file which has the same name as the KMM data file that I am trying to open plus .lock. The lock file has the name of the host that is running KMM. Synthing syncs this file to my backup systems and any system that is online immediately. If I put a system to sleep without closing KMM, the lock file is still present. If I then wake up or boot up a different system, it will receive the lock file and prevent me from running KMM with the same data file. It would be ideal if KMM handled all of this internally. By default i think the lock file should be stored in the same path as the data file but it might make sense to make it configurable. The home directory would not work for my setup since I do not sync my entire home directory with Syncthing. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419903] Editor view very slow.
https://bugs.kde.org/show_bug.cgi?id=419903 --- Comment #15 from g...@afk74.de --- (In reply to caulier.gilles from comment #14) > @g...@afk74.de, > > > This problem still reproducible with the new digiKam 8.2.0 pre-release > Windows > installer available at usual place: > > https://files.kde.org/digikam/ > > This new bundle is based on last Qt framework 5.15.11 and KDE framework > 5.110. > > Thanks in advance > > Gilles Caulier Yes, still reproducible. File is still read in 4kb chunks. Same file takes now 1.9s. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376825] Tag displays do not display correctly after new database is selected
https://bugs.kde.org/show_bug.cgi?id=376825 --- Comment #6 from Bill Goodman --- The first sequence works OK now. I cannot test the second sequence because digiKam fails when trying to create a new database. When the New Database Folder dialog is displayed, I click "Create New Database". digiKam fails with a dialog saying "The SQLite core database was not found, please set the correct location in the next dialog." I do not know what a "SQLite core database" is or where one would be located. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376425] Light table window not activated or brought to front
https://bugs.kde.org/show_bug.cgi?id=376425 --- Comment #11 from Bill Goodman --- I note that the Batch Queue Manager window has the same problem. It is not brought to the front when it is selected a second time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473220] When displays wake up and one screen has been deactivated previously, screen layout not correctly restored until plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=473220 Malte changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- Version|5.27.7 |master --- Comment #11 from Malte --- Sorry, didn't have time to come back to this issue until now. I've just tested with the neon-unstable-20231015-1119 build and can confirm that the problem still exists with latest Plasma 6, so reopening. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 468387] Website is not fully translated
https://bugs.kde.org/show_bug.cgi?id=468387 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/websites/kate-editor-org/-/merge_requests/56 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376425] Light table window not activated or brought to front
https://bugs.kde.org/show_bug.cgi?id=376425 --- Comment #10 from Bill Goodman --- No change. The Light table window still is not brought to the front to be visible. Tested on Windows 11. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 471979] plasma-systemmonitor: graphical artefacts with nouveau kernel module
https://bugs.kde.org/show_bug.cgi?id=471979 Sébastien P. changed: What|Removed |Added CC||sebastien.pica...@ovh.fr --- Comment #2 from Sébastien P. --- Got something similar but also with other apps (plasmashell, so entire session). --- Oct 15 20:05:05 fixe kernel: nouveau :02:00.0: gr: TRAP_PROP - TP 0 - Unknown CUDA fault at address 00201b0800 Oct 15 20:05:05 fixe kernel: nouveau :02:00.0: gr: TRAP_PROP - TP 0 - e0c: , e18: 0ff2, e1c: , e20: , e24: 0903 Oct 15 20:05:05 fixe kernel: nouveau :02:00.0: gr: TRAP_PROP - TP 1 - Unknown CUDA fault at address 00201bbc00 Oct 15 20:05:05 fixe kernel: nouveau :02:00.0: gr: TRAP_PROP - TP 1 - e0c: , e18: 0ff2, e1c: , e20: , e24: 0903 Oct 15 20:05:05 fixe kernel: nouveau :02:00.0: gr: 0020 [] ch 12 [001ebee000 plasmashell[2525]] subc 3 class 8297 mthd 15f0 data 01780178 Oct 15 20:05:05 fixe kernel: nouveau :02:00.0: fb: trapped write at 00201b0800 on channel 12 [1ebee000 plasmashell[2525]] engine 00 [PGRAPH] client 0b [PROP] subclient 09 [LOCAL] reason 0002 [PAGE_NOT_PRESENT] --- The problem appears a few months ago (august), but I did not have the time to check it before (due to a dead mother board in august which has been changed now; I though it was linked… but no). This can lead to random crash (system hang, impossible to do anything, no mouse, no keyboard). Qt: 5.15.10 Framework: 5.110.0 Plasma: 5.27.8 KDE apps: 23.04.3 02:00.0 VGA compatible controller: NVIDIA Corporation G96C [GeForce 9500 GT] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G96C [GeForce 9500 GT] => with Nouveau driver / kernel 6.1.57 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475673] It's possible to resize Kickoff from the bottom with a floating panel
https://bugs.kde.org/show_bug.cgi?id=475673 --- Comment #1 from guimarcalsi...@gmail.com --- Created attachment 162333 --> https://bugs.kde.org/attachment.cgi?id=162333=edit Bug is not present when borders aren't rounded Hm... Weird. I restarted the VM and I can't reproduce it anymore no matter how many times I restart it or what kind of session I use. Interestingly, the rounded bottom corners on Kickoff that appear on the video also disappeared, and the left edge is also touching the screen border now, while it wasn't before. I guess it's supposed to float, so maybe this bug is still valid when Kickoff does what it is supposed to do. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 473897] Cannot add Google Groupware, "Configured account does not exist" then "Resource is not configured"
https://bugs.kde.org/show_bug.cgi?id=473897 --- Comment #33 from Serena Star --- Created attachment 162332 --> https://bugs.kde.org/attachment.cgi?id=162332=edit First Google Groupware works, 2nd doesn't My first Google Groupware account works perfectly but the 2nd one fails, and shows nothing. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 473897] Cannot add Google Groupware, "Configured account does not exist" then "Resource is not configured"
https://bugs.kde.org/show_bug.cgi?id=473897 --- Comment #32 from Serena Star --- Tried to revisit this issue by trying to set up my primary google account. I have one account working, but the 2nd one says "not configured" and then "Can't fetch password". I tried adding the "[network] section" to the broken 2nd account but it fixes nothing. Bringing up the configuration window for Google Groupware just shows it all unpopulated. I can log into my 2nd Google account as many times as I want to no avail. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 370382] Using non-default size for custom stamp pixelates the stamp
https://bugs.kde.org/show_bug.cgi?id=370382 Candid Dauth changed: What|Removed |Added CC||cdauth+bugs.kde.org@cdauth. ||eu --- Comment #3 from Candid Dauth --- This is still the case in Okular 23.08.2. It would be really nice if this got fixed! I have my signature as an SVG file and am trying to an Okular stamp to insert my signature into a document and then use the "Print to PDF" functionality to generate a signed PDF to send. However, the signature is so blurry that it really cannot be used. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 377487] Find and highlight all instances of a searched word
https://bugs.kde.org/show_bug.cgi?id=377487 Ismael changed: What|Removed |Added CC||i.garca9...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 426133] Search in all open files
https://bugs.kde.org/show_bug.cgi?id=426133 Ismael changed: What|Removed |Added CC||i.garca9...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 399446] Okular wishlist: Search term occurrences summary panel
https://bugs.kde.org/show_bug.cgi?id=399446 Ismael changed: What|Removed |Added CC||i.garca9...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 470769] Feature: additional tab ("Results found") in the left panel with links to lines where term was found
https://bugs.kde.org/show_bug.cgi?id=470769 Ismael changed: What|Removed |Added CC||i.garca9...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 161157] search over all tabs
https://bugs.kde.org/show_bug.cgi?id=161157 Ismael changed: What|Removed |Added CC|i.garca9...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 161157] search over all tabs
https://bugs.kde.org/show_bug.cgi?id=161157 Ismael changed: What|Removed |Added CC||i.garca9...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475673] It's possible to resize Kickoff from the bottom with a floating panel
https://bugs.kde.org/show_bug.cgi?id=475673 guimarcalsi...@gmail.com changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470391] Cannot uninstall or update Nightly build
https://bugs.kde.org/show_bug.cgi?id=470391 --- Comment #18 from Judah Richardson --- @Gilles: Thanks for your efforts to fix this. Unfortunately this build suffers from the UAC installation failure bug (https://bugs.kde.org/show_bug.cgi?id=464084). Do the signed Nightly builds contain the fix? I may be able to test that (can't guarantee a timeline). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 451866] Searching all tabbed files
https://bugs.kde.org/show_bug.cgi?id=451866 i.garca9...@gmail.com changed: What|Removed |Added CC||i.garca9...@gmail.com --- Comment #1 from i.garca9...@gmail.com --- I think it would be a functionality that would massively improve Okular. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475673] New: It's possible to resize Kickoff from the bottom with a floating panel
https://bugs.kde.org/show_bug.cgi?id=475673 Bug ID: 475673 Summary: It's possible to resize Kickoff from the bottom with a floating panel Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: guimarcalsi...@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 Created attachment 162331 --> https://bugs.kde.org/attachment.cgi?id=162331=edit Resizing from sides without enough useful space SUMMARY Now it's possible to resize Kickoff from the bottom when using the default floating panel. It's also possible to resize it from the left (near the screen edge) but that's a pre-existing issue. Allowing to resize from those positions is pointless because there's not enough space. I'm filling this for Kickoff but it's likely the same issue would be present for other applets if they also floated (currently, they overlap the panel due to BUG 475147 ). Check the attached video. STEPS TO REPRODUCE 1. Open Kickoff with a floating panel 2. Try to resize from the bottom (or the left side) OBSERVED RESULT It's possible to pointlessly try to resize it from those positions. EXPECTED RESULT Only allow resizing when there's enough space to resize SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.6.0 ADDITIONAL INFORMATION Tested on X11 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475625] Krita refuses to open recently created, and older kra files
https://bugs.kde.org/show_bug.cgi?id=475625 Andreas Sturmlechner changed: What|Removed |Added URL||https://bugs.gentoo.org/915 ||831 CC||ast...@gentoo.org --- Comment #4 from Andreas Sturmlechner --- (In reply to Halla Rempt from comment #3) > That means it's a gentoo build issue -- we cannot solve that. It works fine on my Gentoo system, jftr. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 475672] marble crashed when starting in GNOME
https://bugs.kde.org/show_bug.cgi?id=475672 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 475672] New: marble crashed when starting in GNOME
https://bugs.kde.org/show_bug.cgi?id=475672 Bug ID: 475672 Summary: marble crashed when starting in GNOME Classification: Applications Product: marble Version: 23.08.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: matt.fagn...@bell.net Target Milestone: --- Created attachment 162330 --> https://bugs.kde.org/attachment.cgi?id=162330=edit Full trace of all threads of marble crash SUMMARY marble 23.08.1 crashed 4/4 times when starting in GNOME 45.0 on Wayland in a Fedora 39 KDE Plasma installation. coredumpctl gdb showed the memory access error _q_value= in frame 6 in QAtomicOps::loadRelaxed which looked like an invalid pointer. The trace had functions like QAdwaitaDecorations::updateColors from qadwaitadecorations-0.1.2-1.fc39.x86_64 which I think is used for Qt programs in GNOME in Fedora. Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `marble'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __pthread_kill_implementation (threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; [Current thread is 1 (Thread 0x7f530edf4f80 (LWP 43363))] (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7f530d2ae8a3 in __pthread_kill_internal (signo=11, threadid=) at pthread_kill.c:78 #2 0x7f530d25c8ee in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #3 0x7f530fc44945 in KCrash::defaultCrashHandler(int) () at /lib64/libKF5Crash.so.5 #4 0x7f530d25c9a0 in () at /lib64/libc.so.6 #5 std::__atomic_base::load(std::memory_order) const (__m=std::memory_order_relaxed, this=0x0001) at /usr/include/c++/13/bits/atomic_base.h:503 #6 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=) at /usr/include/qt5/QtCore/qatomic_cxx11.h:239 #7 QBasicAtomicInteger::loadRelaxed() const (this=0x0001) at /usr/include/qt5/QtCore/qbasicatomic.h:107 #8 QtPrivate::RefCount::deref() (this=0x0001) at /usr/include/qt5/QtCore/qrefcount.h:66 #9 QMap::~QMap() (this=, this=) at /usr/include/qt5/QtCore/qmap.h:338 #10 QMap::operator=(QMap&&) (other=..., this=0x55d4453fb630) at /usr/include/qt5/QtCore/qmap.h:349 #11 QAdwaitaDecorations::updateColors(bool) (this=0x55d4453fb5f0, useDarkColors=) at /usr/src/debug/qadwaitadecorations-0.1.2-1.fc39.x86_64/src/qadwaitadecorations.cpp:156 #12 0x7f52978209cb in operator() (watcher=0x55d444eea140, __closure=0x55d4453e3c40) --Type for more, q to quit, c to continue without paging--c at /usr/src/debug/qadwaitadecorations-0.1.2-1.fc39.x86_64/src/qadwaitadecorations.cpp:124 #13 QtPrivate::FunctorCall, QtPrivate::List, void, QAdwaitaDecorations::initConfiguration():: >::call (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #14 QtPrivate::Functor, 1>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #15 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x55d4453e3c30, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #16 0x7f530dae84f1 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffea3cd3c60, r=, this=0x55d4453e3c30) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #17 doActivate(QObject*, int, void**) (sender=0x55d444eea140, signal_index=3, argv=0x7ffea3cd3c60) at kernel/qobject.cpp:3925 #18 0x7f530dae3417 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7f530ef315e0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffea3cd3c60) at kernel/qobject.cpp:3985 #19 0x7f530ef16cc1 in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) (this=, _t1=) at .moc/moc_qdbuspendingcall.cpp:158 #20 0x7f530daded9b in QObject::event(QEvent*) (this=0x55d444eea140, e=0x55d444e4b1c0) at kernel/qobject.cpp:1347 #21 0x7f530e7aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x55d444eea140, e=0x55d444e4b1c0) at kernel/qapplication.cpp:3640 #22 0x7f530dab4218 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55d444eea140, event=0x55d444e4b1c0) at kernel/qcoreapplication.cpp:1064 #23 0x7f530dab4432 in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=, event=) at kernel/qcoreapplication.cpp:1462 #24 0x7f530dab76c5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x55d444817e80) at kernel/qcoreapplication.cpp:1821 #25
[neon] [Bug 475148] QTWidget applications on QT5 are not getting themed with Breeze on Neon Unstable
https://bugs.kde.org/show_bug.cgi?id=475148 guimarcalsi...@gmail.com changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #4 from guimarcalsi...@gmail.com --- Fixed by https://invent.kde.org/neon/neon/seeds/-/commit/775c0bc0e84dd0d0a256064154307f1dbd47974b -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440397] Plasma fails to launch with Wayland and NVidia (kwin_scene_opengl: Creating the OpenGL rendering failed: "query surface failed")
https://bugs.kde.org/show_bug.cgi?id=440397 --- Comment #19 from Dashon --- (In reply to Nate Graham from comment #15) > New bug report please. I'm having the same issue as comment #14. Did anyone ever file a new bug report like you asked. Should I file one? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440397] Plasma fails to launch with Wayland and NVidia (kwin_scene_opengl: Creating the OpenGL rendering failed: "query surface failed")
https://bugs.kde.org/show_bug.cgi?id=440397 Dashon changed: What|Removed |Added CC||sparky123558w...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381819] amd64: unhandled instruction bextr (0x8F 0xEA 0x78 0x10 0xD0 0x8 0x4) from BMI1
https://bugs.kde.org/show_bug.cgi?id=381819 --- Comment #28 from Mark Wielaard --- *** Bug 448026 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 448026] unhandled instruction bytes: 0x8F 0x6A 0x78 0x10 0xC8 0x4 0x4 0x0 0x0 0xC1
https://bugs.kde.org/show_bug.cgi?id=448026 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Mark Wielaard --- This is BEXTR, Bit field extract (with register), part of BMI1 *** This bug has been marked as a duplicate of bug 381819 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 475671] New: Cannot accept fingerprint during add network folder using fish prototcol
https://bugs.kde.org/show_bug.cgi?id=475671 Bug ID: 475671 Summary: Cannot accept fingerprint during add network folder using fish prototcol Classification: Applications Product: dolphin Version: 23.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: vbsamp...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 162329 --> https://bugs.kde.org/attachment.cgi?id=162329=edit fingerprint prompt not working SUMMARY Dolphin fish protocol fingerprint prompt is not working. Options are not clickable and cant even close it unless stopped it from progress indicator from bottom right. STEPS TO REPRODUCE 1. Goto network 2. Click on Add Network Folder 3. Select Secure Shell (ssh) 4. Give the details of any ssh server which is working in terminal (in my case I can do ssh sam@192.168.1.2 and I get prompt) 5. Use fish protocol 5. We get a prompt to add fingerprint to known hosts but the "Yes" and "No" is not clickable 7. In order to cancel it I have to click on the stop button in the notification in down right corner and then close the popup OBSERVED RESULT EXPECTED RESULT Yes or No should be clickable and fish protocol needs to be working SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 23.04 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Dolphin Version: 23.04.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475670] Merge the kcharselector into emoji selector
https://bugs.kde.org/show_bug.cgi?id=475670 Daniele Basso changed: What|Removed |Added CC||d.bas...@proton.me -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475670] New: Merge the kcharselector into emoji selector
https://bugs.kde.org/show_bug.cgi?id=475670 Bug ID: 475670 Summary: Merge the kcharselector into emoji selector Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Archlinux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Emoji Selector Assignee: plasma-b...@kde.org Reporter: d.bas...@proton.me Target Milestone: 1.0 Good night, I am interested on merging the applicative to select whole characters onto the one to select emojis. It should be interesting to press meta + period and being able to select various caracters instead of being able to do it with emojis only. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475669] New: After a window is shaded, windows underlying it cannot be focused
https://bugs.kde.org/show_bug.cgi?id=475669 Bug ID: 475669 Summary: After a window is shaded, windows underlying it cannot be focused Classification: Plasma Product: kwin Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ken.l.hug...@gmail.com Target Milestone: --- SUMMARY Once a window is shaded, any window which was below the shaded window cannot be selected and the title bar of the window is unresponsive. However, is a portion of the underlying window was visible prior to shading, that portion of the window and its title bar still work correctly. STEPS TO REPRODUCE 1. Move Window A over Window B 2. Shade Window A 3. Attempt to move focus to Window B OBSERVED RESULT Window B will not receive the focus if it was entirely shaded by Window A. If any portions of Window B were not shaded by Window A, the focus can be changed. EXPECTED RESULT Any portion of Window B should be able to receive focus SOFTWARE/OS VERSIONS Platform: Manjaro Linux KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 475668] File Picker Show Preview Pane Option Is Greyed Out During File Saves on Firefox
https://bugs.kde.org/show_bug.cgi?id=475668 --- Comment #1 from Richard Steven Hack --- Created attachment 162328 --> https://bugs.kde.org/attachment.cgi?id=162328=edit Picture of greyed out Show Preview Pane option in KDE File Picker -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 475668] New: File Picker Show Preview Pane Option Is Greyed Out During File Saves on Firefox
https://bugs.kde.org/show_bug.cgi?id=475668 Bug ID: 475668 Summary: File Picker Show Preview Pane Option Is Greyed Out During File Saves on Firefox Classification: Plasma Product: xdg-desktop-portal-kde Version: 5.27.8 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: richardstevenh...@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- SUMMARY *** When trying to save a file using the KDE file picker on Firefox, the Show Preview Pane option is greyed out. It cannot be clicked on to activate it and F11 does not work. This only occurs on Firefox - other KDE file dialogs are unaffected. *** STEPS TO REPRODUCE 1. Do a clean install of Firefox - do nothing to modify Firefox except use about:config to set the XDG settings to 1 to enable the KDE file picker instead of the GTK file picker. 2. Run Firefox, browse to an image file on the Internet. 3. Do a Save Page As which opens the KDE File Picker. OBSERVED RESULT The Show Preview Pane option is greyed out and neither a click nor F11 can activate it. EXPECTED RESULT The Show Preview Pane should be available for activation by a mouse click or F11. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSUSE Tumbleweed Snapshot 20231012 (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Kernel Version: 6.5.6-1-default (64-bit) Graphics Platform; X11 Processor: Ryzen 5 2600X Ram: 64GB Graphics Processor: AMD Radeon RX 550 Series Note that the Show Preview Pane option functions normally in all file save and open operations in other KDE applications. See attached photo of the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475072] Apps are displayed on the wrong screen
https://bugs.kde.org/show_bug.cgi?id=475072 --- Comment #6 from gregmad...@yahoo.com --- (In reply to Nate Graham from comment #5) > You can set which screen is primary on the Display and Monitor page in > System Settings. > > In general on Wayland apps and windows open on the screen with the mouse on > it. If you'd like to change this you can do so in System Settings > Window > Behavior, or using the "Window Rules" feature to force them to always appear > on a particular screen. I have set my screen as primary this way using "Display and Monitor" section. Moreover, inside of "Windows behavior", I have added a kwin script called "Always open on primary screen". When activated, all the apps opening on the wrong screen (the lefmost one). If disabled, some of the scripts are displayed on the primary one, and some others (like games) on the leftmost. In my case, some of the apps (including games) are definitely not opening where my mouse cursor is. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 395914] Sidecar files are replaced if reading sidecar files is not enabled
https://bugs.kde.org/show_bug.cgi?id=395914 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||8.2.0 Latest Commit||https://invent.kde.org/grap ||hics/digikam/-/commit/1d7c8 ||ae301946d363838df04ec6d33a8 ||27661598 Resolution|--- |FIXED --- Comment #13 from Maik Qualmann --- Git commit 1d7c8ae301946d363838df04ec6d33a827661598 by Maik Qualmann. Committed on 15/10/2023 at 21:06. Pushed by mqualmann into branch 'master'. always read from sidecar when write is enabled FIXED-IN: 8.2.0 M +1-1NEWS M +5-0core/libs/metadataengine/engine/metaengine.cpp M +12 -3core/utilities/setup/metadata/setupmetadata.cpp M +0-3core/utilities/setup/metadata/setupmetadata_sidecars.cpp https://invent.kde.org/graphics/digikam/-/commit/1d7c8ae301946d363838df04ec6d33a827661598 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 475650] DRD does not work with C11 threads
https://bugs.kde.org/show_bug.cgi?id=475650 --- Comment #4 from Paul Floyd --- It's OK now on FreeBSD and I've also checked with musl and Illumos. -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 475667] New: cannot make new events in kalendar
https://bugs.kde.org/show_bug.cgi?id=475667 Bug ID: 475667 Summary: cannot make new events in kalendar Classification: Applications Product: Merkuro Version: 22.04.3 Platform: Kubuntu OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: droid...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 162327 --> https://bugs.kde.org/attachment.cgi?id=162327=edit gdb results from the run and bt commands SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. open kalendar app (either from apps menu or from popup from clock widget) 2. from day view, scroll past the NOW indicator and create a new event 3. try to save the new event OBSERVED RESULT error message appears (Invalid parent collection) also attached is the gdb output from the run and bt commands EXPECTED RESULT new event is created and appears on the calendar SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.3 Kernel Version: 6.2.0-34-generic (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
