[krusader] [Bug 415826] Implement FileManager1 dbus interface
https://bugs.kde.org/show_bug.cgi?id=415826 Davide Gianforte changed: What|Removed |Added CC||dav...@gengisdave.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Davide Gianforte --- Hi, I tried your steps: same result. I also tried to set other programs as default file manager (FileLight, Gwenview), but Spectacle keeps opening Dolphin. I also did logout/login but no changes. It does work from the K menu - History, I can open recent folder with the default file manager, no need to logout/login. Looking at the code of Spectacle, the Open button simply does a KRun on the designated folder. Must investigate. Operating System: Slackware 14.2 KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.65.0 Qt Version: 5.13.2 Kernel Version: 5.4.7 OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 415817] "Set Coordinates Manually..." always treats input as J2000 even if Jnow is selected.
https://bugs.kde.org/show_bug.cgi?id=415817 Jasem Mutlaq changed: What|Removed |Added Version Fixed In||3.4.0 Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kst ||ars/9ea44f783fcafe1ec16152b ||c45d564b2531f31a0 Status|REPORTED|RESOLVED --- Comment #1 from Jasem Mutlaq --- Git commit 9ea44f783fcafe1ec16152bc45d564b2531f31a0 by Jasem Mutlaq. Committed on 03/01/2020 at 07:18. Pushed by mutlaqja into branch 'master'. Explicitly treat JNow and J2000 differently when setting the sky point RA and DE components FIXED-IN:3.4.0 M +17 -4kstars/dialogs/focusdialog.cpp https://commits.kde.org/kstars/9ea44f783fcafe1ec16152bc45d564b2531f31a0 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 414762] mousearea onClicked dialog popup opens in wrong place unless window is minimized and reopened
https://bugs.kde.org/show_bug.cgi?id=414762 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411058] Occasional spurious scroll events in apps under XWayland
https://bugs.kde.org/show_bug.cgi?id=411058 --- Comment #6 from Carl Wilson --- Created attachment 124863 --> https://bugs.kde.org/attachment.cgi?id=124863=edit Events logged with xinput test-xi2 --root I discover that to trigger this issue, the focus has to be changed into the XWayland window - that is, suppose Chromium and Konsole are placed side-by-side and the current focus is in the latter's window. If I move the pointer onto Chromium, nothing happens and I can scroll the content inside using gestures without hassle. However, if I click the Chromium window to switch the focus to it, this issue will be exhibited. The attachment is a sample log obtained with xinput test-xi2 --root . It seems to be pretty messy, and I have to admit that I don't have much knowledge about the input stack. Anyway I will try to describe what I have done. At Line 8, I moved the cursor from a Wayland window into Chromium's XWayland window. Then the cursor continued moving in XWayland until maybe Line 266, when I began to perform two-finger scroll in it. That should end at Line 935, when I began moving the cursor back to the adjacent Wayland window. It should finally reach the border at Line 1335. After a while, I began the next part of the experiment and the cursor entered XWayland maybe at Line 1345? It moved for a short time before I did a tap-to-click gesture at Line 1555. Then a storm of spurious events happens, where all seem identical to the one from Line 1567 to Line 1577. The effect of this event should cause Chromium to scroll upward infinitely this time. I tried to perform a two-finger downward scroll, but it would be greeted with this spurious upward scroll and cancels the effect of previous operation. Or in a separate trial not attached here, I tried to drag the scrollbar to scroll downward by using "tap-to-hold" gesture and drag it in that direction. But as soon as I release my finger, it just scrolls upwards again. Then at Line 3955, I pressed the "T" key on my keyboard. After that, the problem is gone and I can scroll in that window as usual. It's worth mentioning that keys for alphabets or numbers do this trick, but clicking "Ctrl" won't work and Chromium keep scrolling. Linux/KDE Plasma: 5.4.6-arch3-1 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 libinput version: 1.14.3 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 415710] plasma-discover crash when reinstall inkscape by inkscape-0.92.2.flatpak file
https://bugs.kde.org/show_bug.cgi?id=415710 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Nate Graham --- Thanks. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 414804] Krunner does not reliably find windows
https://bugs.kde.org/show_bug.cgi?id=414804 mojo_lo changed: What|Removed |Added CC||moj...@gmail.com --- Comment #1 from mojo_lo --- Same issue. Windows rarely ever show up in krunner search results. - For example, typing "firefox" (with a Firefox window open) has yielded a 'Windows' result once, but never again. - Typing in "kate" (with a Kate window open) produces no 'Windows' results. - If Kate's window title is "Untitled -- Kate", krunner shows a 'Windows' result for a split second when I start typing "Unti". When I type the next "t", the result disappears and I can never get it to show up again. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415008] KWin-5.17.4 hangs inside loop in QXcbConnection::getTimestamp()
https://bugs.kde.org/show_bug.cgi?id=415008
--- Comment #4 from Alexander Potashev ---
(In reply to Alexander Potashev from comment #3)
> Same problem on Fedora 31: kwin_x11 hangs on start, consuming 100% CPU (1
> CPU core).
>
> KDE Plasma Version: 5.17.4
> KDE Frameworks Version: 5.64.0
Cannot reproduce upon reboot.
Before reboot I tried to restart kwin_x11 from command line and it hanged
again. After a while I got an error like this on the command line:
"""
Couldn't start kglobalaccel from org.kde.kglobalaccel.service:
QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply.
Possible causes include: the remote application did not send a reply, the
message bus security policy blocked the reply, the reply timeout expired, or
the network connection was broken.")
"""
...however according to GDB kwin_x11 was still stuck on line 335 in
kglobalaccel.cpp inside method KGlobalAccelPrivate::updateGlobalShortcut()
here:
const QList scResult(shortcutFromIntList(result));
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 415831] New: Widgets Causing Plasma Crash
https://bugs.kde.org/show_bug.cgi?id=415831 Bug ID: 415831 Summary: Widgets Causing Plasma Crash Product: plasmashell Version: 5.17.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dewis...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.4) Qt Version: 5.14.0 Frameworks Version: 5.65.0 Operating System: Linux 5.4.6-2-MANJARO x86_64 Distribution: Manjaro Linux -- Information about the crash: - What I was doing when the application crashed: I was tinkering with widgets. I may have had too many going that were interfereing with the normal operation of the GPU. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7faef2507cc0 (LWP 1384))] Thread 47 (Thread 0x7fadcdffa700 (LWP 17867)): #0 0x7faef68019ef in poll () at /usr/lib/libc.so.6 #1 0x7faec9e82c14 in () at /usr/lib/libpulse.so.0 #2 0x7faec9e90059 in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #3 0x7faec9e9a301 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7faec9e9a3b1 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7faec9e8a61e in () at /usr/lib/libpulse.so.0 #6 0x7faec9e08d1c in () at /usr/lib/pulseaudio/libpulsecommon-13.0.so #7 0x7faef5fcb4cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7faef680c2d3 in clone () at /usr/lib/libc.so.6 Thread 46 (Thread 0x7fadcf3fc700 (LWP 17862)): #0 0x7faef5fd1c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7faef6b8fcc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7faef6b8fda2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7faef88fb18b in () at /usr/lib/libQt5Quick.so.5 #4 0x7faef88fb41b in () at /usr/lib/libQt5Quick.so.5 #5 0x7faef6b89fd6 in () at /usr/lib/libQt5Core.so.5 #6 0x7faef5fcb4cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7faef680c2d3 in clone () at /usr/lib/libc.so.6 Thread 45 (Thread 0x7fae14f8f700 (LWP 17861)): #0 0x7faef5fd1c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7faef6b8fcc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7faef6b8fda2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7faef88fb18b in () at /usr/lib/libQt5Quick.so.5 #4 0x7faef88fb41b in () at /usr/lib/libQt5Quick.so.5 #5 0x7faef6b89fd6 in () at /usr/lib/libQt5Core.so.5 #6 0x7faef5fcb4cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7faef680c2d3 in clone () at /usr/lib/libc.so.6 Thread 44 (Thread 0x7fadcfffd700 (LWP 17860)): #0 0x7faef5fd1c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7faef6b8fcc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7faef6b8fda2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7faef88fb18b in () at /usr/lib/libQt5Quick.so.5 #4 0x7faef88fb41b in () at /usr/lib/libQt5Quick.so.5 #5 0x7faef6b89fd6 in () at /usr/lib/libQt5Core.so.5 #6 0x7faef5fcb4cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7faef680c2d3 in clone () at /usr/lib/libc.so.6 Thread 43 (Thread 0x7fadce7fb700 (LWP 17823)): #0 0x7faef5fd1c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7faef6b8fcc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7faef6b8fda2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7faef88fb18b in () at /usr/lib/libQt5Quick.so.5 #4 0x7faef88fb41b in () at /usr/lib/libQt5Quick.so.5 #5 0x7faef6b89fd6 in () at /usr/lib/libQt5Core.so.5 #6 0x7faef5fcb4cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7faef680c2d3 in clone () at /usr/lib/libc.so.6 Thread 42 (Thread 0x7fae217fd700 (LWP 17094)): #0 0x7faef68019ef in poll () at /usr/lib/libc.so.6 #1 0x7faef506d120 in () at /usr/lib/libglib-2.0.so.0 #2 0x7faef506d1f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7faef6dbccdc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7faef6d6339c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7faef6b88e62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7faef6b89fd6 in () at /usr/lib/libQt5Core.so.5 #7 0x7faef5fcb4cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7faef680c2d3 in clone () at /usr/lib/libc.so.6 Thread 41 (Thread
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #7 from Andrew Udvare --- Rebooted with Breeze theme (and all other appearance settings set to Breeze) and still got the same issue. Just for reference, this is a KF5 5.65.0 installation. Plasma-desktop and related is at 5.17.4. Qt is at 5.14.0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #6 from Andrew Udvare --- I rebooted and still get the same issue. About to try switching to Breeze widget style. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415008] KWin-5.17.4 hangs inside loop in QXcbConnection::getTimestamp()
https://bugs.kde.org/show_bug.cgi?id=415008 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com --- Comment #3 from Alexander Potashev --- Same problem on Fedora 31: kwin_x11 hangs on start, consuming 100% CPU (1 CPU core). KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 413086] Can't create .tar.lz4 nor .tar.zst files.
https://bugs.kde.org/show_bug.cgi?id=413086 --- Comment #11 from Tony --- Welp new year, new snapshot (20200101) for Tumbleweed and with this one the issue seems fixed, all working OK now. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 413086] Can't create .tar.lz4 nor .tar.zst files.
https://bugs.kde.org/show_bug.cgi?id=413086 Tony changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415830] New: Drag and Drop
https://bugs.kde.org/show_bug.cgi?id=415830 Bug ID: 415830 Summary: Drag and Drop Product: kwin Version: 5.17.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: jesterflint...@gmail.com Target Milestone: --- SUMMARY When drag and dropping a file, if the destination window is not maximized, we cannot reach the destination. That is, for eg, i have 2 dolphin windows open, both maximized, i have a vlc window open, not maximized, floating. now, if i want to drag a file from one dolphin window to the vlc,as the vlc is not maximized, i have to take the file through a dolphin window. now when the pointer with the file reaches a dolphin window, the vlc window minimizes, making it impossible to drop inside vlc. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.4.3-arch3-1 (available in About System) KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 415829] New: Cant delete created activities
https://bugs.kde.org/show_bug.cgi?id=415829 Bug ID: 415829 Summary: Cant delete created activities Product: frameworks-kactivities Version: 5.65.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: jesterflint...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Create a few new activities in activities switcher 2. Try to delete the created activity OBSERVED RESULT The delete button (-) does nothing EXPECTED RESULT The unwanted activity window to be deleted SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.4.3-arch3-1 (available in About System) KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415828] New: Memory leak
https://bugs.kde.org/show_bug.cgi?id=415828 Bug ID: 415828 Summary: Memory leak Product: plasmashell Version: 5.17.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: jesterflint...@gmail.com Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Use a lot of RAM, i used google-chrome-stable, chromium, google-chrome-beta, okular and music player (i used about 5/8 gb) for some time (atleast an hour or 2). 2. Close all the applications OBSERVED RESULT Plasmashell using 15-20% CPU of my 8 core i7-6700hq. Plasmashell using 600 mb ram. EXPECTED RESULT Plasma shell not using this much of cpu and RAM SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.4.6-arch3-1 (kernel) (available in About System) KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION Sorry if its a duplicate, i searched and found one with opensuse and different plasma version. Thank you for the awesome Plasma DE. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414810] Bug in selection tool
https://bugs.kde.org/show_bug.cgi?id=414810 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 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 414691] Wrong image selected when dragging and dropping reference images
https://bugs.kde.org/show_bug.cgi?id=414691 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 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 414583] growing selection often results in rotating canvas also
https://bugs.kde.org/show_bug.cgi?id=414583 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[KScreen] [Bug 413995] Display Bug
https://bugs.kde.org/show_bug.cgi?id=413995 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 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.
[lattedock] [Bug 414064] Latte dock doesn't start when booting into a single screen from a dual screen configuration
https://bugs.kde.org/show_bug.cgi?id=414064 --- 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.
[systemsettings] [Bug 414188] System Settings Application Style Adwaita-Dark crash Colors (choose colors scheme).
https://bugs.kde.org/show_bug.cgi?id=414188 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 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 415301] Plasma crashes after enabling Display configuration in System Tray Settings
https://bugs.kde.org/show_bug.cgi?id=415301 --- Comment #3 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.
[unknown] [Bug 414677] Frames bug out when played
https://bugs.kde.org/show_bug.cgi?id=414677 --- 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.
[lattedock] [Bug 407533] Zoom on hover does not always register cursor movement correctly
https://bugs.kde.org/show_bug.cgi?id=407533 --- Comment #23 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.
[dolphin] [Bug 415360] Default for executables changes to show an error message
https://bugs.kde.org/show_bug.cgi?id=415360 --- Comment #3 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.
[Breeze] [Bug 415722] Add Audacity project mime type icon
https://bugs.kde.org/show_bug.cgi?id=415722
Carson Black changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit||https://commits.kde.org/bre
||eze-icons/4bba41c56947523f8
||5af35bbaf6109289154296c
Status|REPORTED|RESOLVED
--- Comment #1 from Carson Black ---
Git commit 4bba41c56947523f85af35bbaf6109289154296c by Carson Black.
Committed on 03/01/2020 at 04:06.
Pushed by cblack into branch 'master'.
Add application/x-audacity-project icon
Summary: BUG: 415722
Test Plan:
* Takes the audacity app icon, simplifies it slightly and monochromizes it.
Getting it pixel-aligned was quite hard and I didn't do a very good job at it I
think :)
{F7852129}
{F7852130}
{F7852131}
{F7852132}
{F7852133}
Will clean the SVG file up and put it in icons-dark when the style is agreed
upon
Reviewers: #vdg, ndavis, ngraham, broulik
Reviewed By: #vdg, ndavis, ngraham
Subscribers: cblack, ndavis, kde-frameworks-devel
Tags: #frameworks
Differential Revision: https://phabricator.kde.org/D26326
A +15 -0icons-dark/mimetypes/16/application-x-audacity-project.svg
A +15 -0icons-dark/mimetypes/22/application-x-audacity-project.svg
A +38 -0icons-dark/mimetypes/32/application-x-audacity-project.svg
A +38 -0icons-dark/mimetypes/64/application-x-audacity-project.svg
A +15 -0icons/mimetypes/16/application-x-audacity-project.svg
A +15 -0icons/mimetypes/22/application-x-audacity-project.svg
A +36 -0icons/mimetypes/32/application-x-audacity-project.svg
A +38 -0icons/mimetypes/64/application-x-audacity-project.svg
https://commits.kde.org/breeze-icons/4bba41c56947523f85af35bbaf6109289154296c
--
You are receiving this mail because:
You are watching all bug changes.
[elisa] [Bug 415827] New: Unable to enqueue all tracks at once
https://bugs.kde.org/show_bug.cgi?id=415827 Bug ID: 415827 Summary: Unable to enqueue all tracks at once Product: elisa Version: 20.03.70 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: quantumtravel...@gmail.com Target Milestone: --- Clicking play button or enqueue button on albums, artists, or tracks pages will not affect the playlist in any way. STEPS TO REPRODUCE 1. Navigate to "Albums" page, "Artists" page, or "Tracks" page 2. At the top of the page, click Enqueue or Play Now button OBSERVED RESULT Nothing happens in the application, terminal output shows this warning: "Could not convert argument 0 at" "onEntriesToEnqueue@qrc:/qml/DataGridView.qml:61" "Passing incompatible arguments to C++ functions from JavaScript is dangerous and deprecated." "This will throw a JavaScript TypeError in future releases of Qt!" EXPECTED RESULT All tracks are added to playlist. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux (available in About System) KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 415785] Kamoso effects crash
https://bugs.kde.org/show_bug.cgi?id=415785 Nate Graham changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #3 from Nate Graham --- Yeap, that'll do it. Always gotta restart after updating the graphics drivers or else all hell breaks loose! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412322] With 2 monitors, application allways opens on the left
https://bugs.kde.org/show_bug.cgi?id=412322 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=415821 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415821] Windows jump on left screen even if not primary
https://bugs.kde.org/show_bug.cgi?id=415821 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=412322 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415591] In a multi-display setup, KDE apps only remember window size across program launches when closed on the left-most display
https://bugs.kde.org/show_bug.cgi?id=415591 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=412322 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412322] With 2 monitors, application allways opens on the left
https://bugs.kde.org/show_bug.cgi?id=412322 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=415591 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415821] Windows jump on left screen even if not primary
https://bugs.kde.org/show_bug.cgi?id=415821 Nate Graham changed: What|Removed |Added Component|common |general Assignee|kscreen-bugs-n...@kde.org |kwin-bugs-n...@kde.org Product|KScreen |kwin CC||n...@kde.org Version|git |5.17.4 See Also||https://bugs.kde.org/show_b ||ug.cgi?id=415591 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415591] In a multi-display setup, KDE apps only remember window size across program launches when closed on the left-most display
https://bugs.kde.org/show_bug.cgi?id=415591 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=415821 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415818] Suggestion: enhance compositor auto suspend by window focus tracking condition
https://bugs.kde.org/show_bug.cgi?id=415818 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 415812] Remote images are not displayed until "View" toolbar button is pressed
https://bugs.kde.org/show_bug.cgi?id=415812 Nate Graham changed: What|Removed |Added Keywords||regression Status|REPORTED|CONFIRMED CC||n...@kde.org Ever confirmed|0 |1 --- Comment #1 from Nate Graham --- How bizarre. Can reproduce. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 415819] Notification entry in history too small in height resulting in an overlap
https://bugs.kde.org/show_bug.cgi?id=415819 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415819] Notification entry in history too small in height resulting in an overlap
https://bugs.kde.org/show_bug.cgi?id=415819 Nate Graham changed: What|Removed |Added Version|5.65.0 |5.17.4 Product|frameworks-knotifications |plasmashell CC||plasma-b...@kde.org Target Milestone|--- |1.0 Assignee|kdelibs-b...@kde.org|k...@privat.broulik.de Component|general |Notifications -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 345114] Selected items in a list view have white text on light-blue background when the widget is inactive
https://bugs.kde.org/show_bug.cgi?id=345114 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #2 from Nate Graham --- This was an issue with that particular KCM as far as I can tell, which has since been fixed by rewriting its front-end completely. I haven't see anything else with this issue. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 376430] Some scrollbars unusable with wacom
https://bugs.kde.org/show_bug.cgi?id=376430 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||n...@kde.org Status|REPORTED|NEEDSINFO --- Comment #4 from Nate Graham --- Can anyone confirm that this is still happening? Much much more KDE software has gotten QMI-ified since this was reported, but I haven't heard any more reports. Maybe fixed? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 358302] Highlighted checkbox or radio button becomes visually inverted
https://bugs.kde.org/show_bug.cgi?id=358302 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Nate Graham --- Fixed now. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 358271] Some comboboxes are missing shadows and are hard to click
https://bugs.kde.org/show_bug.cgi?id=358271 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED CC||n...@kde.org Resolution|--- |FIXED --- Comment #3 from Nate Graham --- Works fine now. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 415606] DialogButtonBox styling does not respect color scheme
https://bugs.kde.org/show_bug.cgi?id=415606 --- Comment #3 from Nate Graham --- Example code that shows the issue (seen in the screenshot attached to this bug) can be found at https://cgit.kde.org/knewstuff.git/tree/src/qtquick/qml/Dialog.qml#n96 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 415710] plasma-discover crash when reinstall inkscape by inkscape-0.92.2.flatpak file
https://bugs.kde.org/show_bug.cgi?id=415710 --- Comment #2 from a44881...@gmail.com --- No, I downloaded if officially. Thanks! Hsieh, Tsung-Lun Nate Graham 於 2020年1月3日 週五 01:00 寫道： > https://bugs.kde.org/show_bug.cgi?id=415710 > > Nate Graham changed: > >What|Removed |Added > > > Summary|plasma-discover crush when |plasma-discover crash when >|reinstall inkscape by |reinstall inkscape by >|inkscape-0.92.2.flatpak |inkscape-0.92.2.flatpak >|file|file > Component|discover|Flatpak Backend > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > CC||jgrul...@redhat.com, >||n...@kde.org > > --- Comment #1 from Nate Graham --- > So you downloaded the inkscape-0.92.2.flatpak file locally? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 415785] Kamoso effects crash
https://bugs.kde.org/show_bug.cgi?id=415785 --- Comment #2 from Jeff --- Ok, confirmed, I am not having the issues any more. This is a fresh install so I looked at my bash history file to see what mesa/intel packages I installed. These packages were all installed before Kamoso but I may not have refreshed X in any way before trying Kamoso and getting the crashes. vulkan-intel mesa-utils intel-media-driver lib32-vulkan-intel Thanks again! On 1/2/20 8:00 AM, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=415785 > > Nate Graham changed: > > What|Removed |Added > > CC||n...@kde.org > > --- Comment #1 from Nate Graham --- > Crashing deep in the Intel GPU driver. :/ > -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 415826] New: Implement FileManager1 dbus interface
https://bugs.kde.org/show_bug.cgi?id=415826 Bug ID: 415826 Summary: Implement FileManager1 dbus interface Product: krusader Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: dennis.lis...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- Some programs use it to open file manager, fail to open Krusader and fall back to other file managers instead. For example: - make Krusader the default file manager, - open Spectacle, - press Tools - Open Screenshots Folder, - observe that the directory did not open in Krusader (in my case it was Dolphin instead). -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 415688] printscr key doesn't capture screenshot with selected options when Spectacle is already open
https://bugs.kde.org/show_bug.cgi?id=415688 Nate Graham changed: What|Removed |Added Summary|Keyboard shortcut doesn't |printscr key doesn't |capture screenshot with |capture screenshot with |selected options|selected options when ||Spectacle is already open Resolution|NOT A BUG |--- Status|RESOLVED|REPORTED --- Comment #5 from Nate Graham --- Thanks, now I understand! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 415688] printscr key doesn't capture screenshot with selected options when Spectacle is already open
https://bugs.kde.org/show_bug.cgi?id=415688 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 411691] Only happens in Opensuse 15.1 in most games the cards will only autodrop a few, and then it stops., often crashes when Yukon is selected
https://bugs.kde.org/show_bug.cgi?id=411691 --- Comment #8 from Anton Aylward --- On 02/01/2020 17:51, Albert Astals Cid wrote: > https://bugs.kde.org/show_bug.cgi?id=411691 > > --- Comment #7 from Albert Astals Cid --- > Can you use the actual commands and not zypper? > Yes, after researching and finding out what 'flatpak' is I installed that with zypper and then ran the text you stated. I required a lot to be loaded, even on top of the flatpak environment, and after 3/4 hour even the first 500Mb wasn't yet loaded. Not a wonderful server! All this just to install a test version of a 1/2M program. This seems to be a resource-heavy way of going about it. It seems to demand an whole new execution environment. it seems a very heavy way of developing & testing compared to what I've been doing the past couple of decades. If the patches are available as a delta I can apply them to my distribution source. SUSE has good tool for that. I can define a personal repository and let other SUSE users test and verify and then push upstream to the rolling release. All without the heavyweight you're asking of me to simply test what you COULD have pushed out at a RPM or source package that I could compile myself. Sorry, this is too heavy for me. There are so many simpler, lighter, long established ways of testing patches for me to follow this route. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415825] New: plasmashell segfaults when hitting "disconnect" button in network manager
https://bugs.kde.org/show_bug.cgi?id=415825 Bug ID: 415825 Summary: plasmashell segfaults when hitting "disconnect" button in network manager Product: plasmashell Version: 5.16.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: i...@martin-konrad.net CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.5) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-24-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: This happened when I hit the "disconnect" button in network manager (from the systray). The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x55eabf51ad20) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 [Current thread is 1 (Thread 0x7fe1d8d5f880 (LWP 2511))] Thread 25 (Thread 0x7fe133a9b700 (LWP 11105)): #0 0x7fe1dba842c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x55eac556ec50) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7fe1dba842c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55eac556ec00, cond=0x55eac556ec28) at pthread_cond_wait.c:508 #2 0x7fe1dba842c6 in __pthread_cond_wait (cond=0x55eac556ec28, mutex=0x55eac556ec00) at pthread_cond_wait.c:638 #3 0x7fe1dc600def in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe1dc600ee1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe1de4197b9 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fe1de419a1a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fe1dc5facc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fe1dba7d669 in start_thread (arg=) at pthread_create.c:479 #9 0x7fe1dc27f323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7fe165462700 (LWP 24943)): #0 0x7fe1dba842c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x55eac4cec4a0) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7fe1dba842c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55eac4cec450, cond=0x55eac4cec478) at pthread_cond_wait.c:508 #2 0x7fe1dba842c6 in __pthread_cond_wait (cond=0x55eac4cec478, mutex=0x55eac4cec450) at pthread_cond_wait.c:638 #3 0x7fe1dc600def in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe1dc600ee1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe1de4197b9 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fe1de419a1a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fe1dc5facc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fe1dba7d669 in start_thread (arg=) at pthread_create.c:479 #9 0x7fe1dc27f323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7fe165c63700 (LWP 12565)): #0 0x7fe1dc272c2f in __GI___poll (fds=0x7fe1440563c0, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe1b5ec81c6 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7fe1b5eb9831 in pa_mainloop_poll () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7fe1b5eb9eb3 in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fe1b5eb9f60 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fe1b5ec810d in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7fe1b5d9837c in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.0.so #7 0x7fe1dba7d669 in start_thread (arg=) at pthread_create.c:479 #8 0x7fe1dc27f323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7fe1667fc700 (LWP 22099)): #0 0x7fe1dba842c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x55eac15bce44) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7fe1dba842c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55eac15bcdf0, cond=0x55eac15bce18) at pthread_cond_wait.c:508 #2 0x7fe1dba842c6 in __pthread_cond_wait (cond=0x55eac15bce18, mutex=0x55eac15bcdf0) at pthread_cond_wait.c:638 #3 0x7fe1dc600def in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe1dc600ee1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe1b53f5ea0 in
[kwin] [Bug 415750] KWin crashes randomly
https://bugs.kde.org/show_bug.cgi?id=415750 Roman Gilg changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #2 from Roman Gilg --- *** Bug 415824 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415824] Assert in composite.cpp
https://bugs.kde.org/show_bug.cgi?id=415824 Roman Gilg changed: What|Removed |Added Status|REPORTED|RESOLVED CC||subd...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Roman Gilg --- *** This bug has been marked as a duplicate of bug 415750 *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 415688] Keyboard shortcut doesn't capture screenshot with selected options
https://bugs.kde.org/show_bug.cgi?id=415688 --- Comment #4 from Extrasklep --- Yeah exactly, instead it captures the full screen or the option that was selected the last time the "Take a New Screenshot" button was pressed like I said in the original post (In reply to Nate Graham from comment #3) > Oh you mean that when Spectacle is already running, pressing printscreen > should take a screenshot according to what's in the combobox, exactly as if > the "Take a new screenshot" button had been pressed? -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 411691] Only happens in Opensuse 15.1 in most games the cards will only autodrop a few, and then it stops., often crashes when Yukon is selected
https://bugs.kde.org/show_bug.cgi?id=411691 --- Comment #7 from Albert Astals Cid --- Can you use the actual commands and not zypper? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415824] New: Assert in composite.cpp
https://bugs.kde.org/show_bug.cgi?id=415824 Bug ID: 415824 Summary: Assert in composite.cpp Product: kwin Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: k...@davidedmundson.co.uk Target Milestone: --- Application: kwin_x11 (5.17.80) (Compiled from sources) Qt Version: 5.14.0 Frameworks Version: 5.66.0 Operating System: Linux 5.4.1-arch1-1 x86_64 Windowing system: X11 Distribution: Arch Linux -- Information about the crash: git master of today, haven't investigated further, thought I'd post as-is anyway. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f55490c6880 (LWP 9534))] Thread 4 (Thread 0x7f5533027700 (LWP 9551)): #0 0x7f554f667c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f55336495fc in () at /usr/lib/dri/i965_dri.so #2 0x7f55336491f8 in () at /usr/lib/dri/i965_dri.so #3 0x7f554f6614cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f554d4542d3 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f5541e41700 (LWP 9548)): #0 0x7f554d449ae6 in ppoll () at /usr/lib/libc.so.6 #1 0x7f554dc49ad8 in qt_ppoll(pollfd*, nfds_t, timespec const*) (fds=0x7f5538000d38, nfds=1, timeout_ts=0x0) at /home/david/projects/qt/src/qtbase/src/corelib/kernel/qcore_unix.cpp:132 #2 0x7f554dc49b1c in qt_safe_poll(pollfd*, unsigned long, timespec const*) (fds=0x7f5538000d38, nfds=1, timeout_ts=0x0) at /home/david/projects/qt/src/qtbase/src/corelib/kernel/qcore_unix.cpp:155 #3 0x7f554dc4b502 in QEventDispatcherUNIX::processEvents(QFlags) (this=0x7f5538000b60, flags=...) at /home/david/projects/qt/src/qtbase/src/corelib/kernel/qeventdispatcher_unix.cpp:500 #4 0x7f554dbb79e9 in QEventLoop::processEvents(QFlags) (this=0x7f5541e40ce0, flags=...) at /home/david/projects/qt/src/qtbase/src/corelib/kernel/qeventloop.cpp:138 #5 0x7f554dbb7d23 in QEventLoop::exec(QFlags) (this=0x7f5541e40ce0, flags=...) at /home/david/projects/qt/src/qtbase/src/corelib/kernel/qeventloop.cpp:225 #6 0x7f554d94bfd4 in QThread::exec() (this=0x55f9c2da3260) at /home/david/projects/qt/src/qtbase/src/corelib/thread/qthread.cpp:536 #7 0x7f5550df73a3 in QQmlThreadPrivate::run() (this=0x55f9c2da3260) at /home/david/projects/qt/src/qtdeclarative/src/qml/qml/ftw/qqmlthread.cpp:155 #8 0x7f554d94ee91 in QThreadPrivate::start(void*) (arg=0x55f9c2da3260) at /home/david/projects/qt/src/qtbase/src/corelib/thread/qthread_unix.cpp:342 #9 0x7f554f6614cf in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f554d4542d3 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f5543d07700 (LWP 9539)): #0 0x7f554dc4d449 in QVector::capacity() const (this=0x7f553c000bf0) at ../../include/QtCore/../../../../src/qtbase/src/corelib/tools/qvector.h:94 #1 0x7f554dc4c102 in QVector::reserve(int) (this=0x7f553c000bf0, asize=1) at ../../include/QtCore/../../../../src/qtbase/src/corelib/tools/qvector.h:427 #2 0x7f554dc4b3f5 in QEventDispatcherUNIX::processEvents(QFlags) (this=0x7f553c000b60, flags=...) at /home/david/projects/qt/src/qtbase/src/corelib/kernel/qeventdispatcher_unix.cpp:489 #3 0x7f554dbb79e9 in QEventLoop::processEvents(QFlags) (this=0x7f5543d06cb0, flags=...) at /home/david/projects/qt/src/qtbase/src/corelib/kernel/qeventloop.cpp:138 #4 0x7f554dbb7d23 in QEventLoop::exec(QFlags) (this=0x7f5543d06cb0, flags=...) at /home/david/projects/qt/src/qtbase/src/corelib/kernel/qeventloop.cpp:225 #5 0x7f554d94bfd4 in QThread::exec() (this=0x7f554f505dc0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at /home/david/projects/qt/src/qtbase/src/corelib/thread/qthread.cpp:536 #6 0x7f554f44a379 in QDBusConnectionManager::run() (this=0x7f554f505dc0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at /home/david/projects/qt/src/qtbase/src/dbus/qdbusconnection.cpp:179 #7 0x7f554d94ee91 in QThreadPrivate::start(void*) (arg=0x7f554f505dc0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at /home/david/projects/qt/src/qtbase/src/corelib/thread/qthread_unix.cpp:342 #8 0x7f554f6614cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f554d4542d3 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f55490c6880 (LWP 9534)): [KCrash Handler] #6 0x7f554d390f25 in raise () at /usr/lib/libc.so.6 #7 0x7f554d37a897 in abort () at /usr/lib/libc.so.6 #8 0x7f554d943dc8 in qt_message_fatal(QtMsgType, QMessageLogContext const&, QString const&) (context=..., message=...) at /home/david/projects/qt/src/qtbase/src/corelib/global/qlogging.cpp:1894 #9 0x7f554d940406 in
[krita] [Bug 415227] Crashes when I right click
https://bugs.kde.org/show_bug.cgi?id=415227 Antti Savolainen changed: What|Removed |Added CC||antti.s...@gmail.com --- Comment #3 from Antti Savolainen --- Had this bug a week ago when right clicking while brush is selected. It is now gone with krita 4.2.8 (git 16a7bae). Possibly accidentally fixed. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 415823] Copying files from desktop to phone with Ctrl+C not possible
https://bugs.kde.org/show_bug.cgi?id=415823 naitsirch changed: What|Removed |Added CC||naitsi...@e.mail.de -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 415823] New: Copying files from desktop to phone with Ctrl+C not possible
https://bugs.kde.org/show_bug.cgi?id=415823 Bug ID: 415823 Summary: Copying files from desktop to phone with Ctrl+C not possible Product: kdeconnect Version: 1.3.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: naitsi...@e.mail.de Target Milestone: --- I have installed kdeconnect 1.3.3 on my Debian Buster. Pairing with my Android phone works great and copying text also. But when I try to copy files with Ctrl+C in Dolphin from my desktop to my phone's sdcard nothing happens. But I can transfer the files with drag STEPS TO REPRODUCE 1. Connect android phone with KDE Connect app to plasma desktop 2. Grant access to the sdcard 3. Open phone's sdcard with dolphin 4. Select a local file in Dolphin and press Ctrl+C 5. Press Ctrl+V on the sdcard. OBSERVED RESULT Nothing happens. EXPECTED RESULT File is copied. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Debian GNU/Linux 10 KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415557] Face detection - Advanced settings : restricted folder scope not taken into account
https://bugs.kde.org/show_bug.cgi?id=415557 Maik Qualmann changed: What|Removed |Added Resolution|WORKSFORME |FIXED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415557] Face detection - Advanced settings : restricted folder scope not taken into account
https://bugs.kde.org/show_bug.cgi?id=415557 --- Comment #11 from Maik Qualmann --- Git commit 812eda4a540edb2ce1ec07ec63270b591c6ed164 by Maik Qualmann. Committed on 02/01/2020 at 22:01. Pushed by mqualmann into branch 'master'. move "clear and rebuild training data" to the Maintenance tool M +0-1core/app/views/sidebar/peoplesidebarwidget.cpp M +1-28 core/utilities/facemanagement/widgets/facescanwidget.cpp M +0-6core/utilities/facemanagement/widgets/facescanwidget.h M +0-2core/utilities/facemanagement/widgets/facescanwidget_p.h M +26 -9core/utilities/maintenance/maintenancedlg.cpp https://invent.kde.org/kde/digikam/commit/812eda4a540edb2ce1ec07ec63270b591c6ed164 -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 415089] Dolphin Kio-gdrive authentication with Google account fails
https://bugs.kde.org/show_bug.cgi?id=415089 Francisco Cribari changed: What|Removed |Added CC||crib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 415822] New: Discover Software Manager allows package updates without prompt for password authentication
https://bugs.kde.org/show_bug.cgi?id=415822 Bug ID: 415822 Summary: Discover Software Manager allows package updates without prompt for password authentication Product: Discover Version: 5.12.8 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: l...@llpmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Discover Software Manager allows package updates without prompt for password authentication STEPS TO REPRODUCE 1.Boot Discover 2.Select Update Button 3. Select Update All OBSERVED RESULT Updates package without password authentication. EXPECTED RESULT Dialoge box requiring password authentication before package update. SOFTWARE/OS VERSIONS Windows: macOS: Kubuntu: 18.04 (available in About System) KDE Plasma Version: 5.12.9 KDE Frameworks Version:5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION Kernal:5.3.0-26-generic -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 415821] New: Windows jump on left screen even if not primary
https://bugs.kde.org/show_bug.cgi?id=415821 Bug ID: 415821 Summary: Windows jump on left screen even if not primary Product: KScreen Version: git Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: bap...@gmail.com Target Milestone: --- SUMMARY If you set the primary display on right of a secondary display, wen you plug the secondary display windows from the main display jump on the left one, where they should stay on the primary one. STEPS TO REPRODUCE 1. Open display configuration while 2 displays are plugged. 2. Put your primary display (in my case, laptop screen) on the right of the secondary one (in my case hdmi-plugged monitor). 3. Unplug secondary display. 4. Open some windows. 5. Plug secondary windows. OBSERVED RESULT Windows jump to the secondary display. EXPECTED RESULT Primary display should remain identical in every way. Secondary display, whatever its position, should be empty when plugged. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 Kernel Version: 5.4.2-1-MANJARO OS Type: 64-bit Processors: 4 × Intel® Core™ i7-7500U CPU @ 2.70GHz Memory: 15,5 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets are permanently repositioned when fullscreen games lower display resolution
https://bugs.kde.org/show_bug.cgi?id=360478 Bruzzlee changed: What|Removed |Added CC||bruzzlee...@gmail.com --- Comment #45 from Bruzzlee --- Same issue here. Other reason. If Plasma wakes up after the "Screen Energy Saving" was active the icons and widgets are rearranged. I have two monitors. One monitor turns on faster than the other, resulting in a change in resolution. The same behaviour can be reproduced when the main monitor is turned off, so that the second monitor with a lower resolution becomes the default screen. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 414554] Installed CMake target contains absolute paths and cannot be relocated
https://bugs.kde.org/show_bug.cgi?id=414554 Torsten Rahn changed: What|Removed |Added Resolution|--- |FIXED CC||r...@kde.org Status|REPORTED|RESOLVED --- Comment #2 from Torsten Rahn --- Closed by commit R34:3eb10f4339df: Patch from Samuel OMalley to make the include directory movable. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #103 from Vitalii Hladiienko --- (In reply to Daniel Vrátil from comment #50) > I've now did the necessary changes and filed a request to have the login > enabled again. Best of luck in 2020, everyone! Indeed, is there any news on the progress of the request you filed, Daniel? Since this issue is now relevant not only to KMail but the whole K-stack, it seems a bit odd for Google to ~ignore~ process the request for so long. Sorry if I've missed it, but does this request cover just KMail or will KOrganizer get fixed as well as a result? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415820] New: Plasma crash after resuming from a suspend and starting to enter a password for user login
https://bugs.kde.org/show_bug.cgi?id=415820 Bug ID: 415820 Summary: Plasma crash after resuming from a suspend and starting to enter a password for user login Product: plasmashell Version: 5.17.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kvanton@yandex.ru CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.4) Qt Version: 5.13.2 Frameworks Version: 5.65.0 Operating System: Linux 5.3.13-050313-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: Plasma crash after resuming from a suspend and starting to enter a password for user login. At first, the input field hung (keyboard and mouse did not respond) I deleted the USB bluetooth dongle (although there were no problems with it before, but somehow I wanted it that way) mouse and input field still did not respond I pressed the ctr+alt+2 to go to tty2, there the user was already authorized earlier. I switched to tty2 and started htop, in order to check the CPU/RAM load. But at that moment the plasma recovered and I was thrown into tty1 and the login screen. After entering, I saw a plasma crash message -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc6a8863000 (LWP 3395))] Thread 15 (Thread 0x7fc615937700 (LWP 17708)): #0 0x7fc69f5369f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55cb8b1103a4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fc69f5369f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55cb8b110350, cond=0x55cb8b110378) at pthread_cond_wait.c:502 #2 0x7fc69f5369f3 in __pthread_cond_wait (cond=0x55cb8b110378, mutex=0x55cb8b110350) at pthread_cond_wait.c:655 #3 0x7fc6a265daeb in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x55cb8b110350) at thread/qwaitcondition_unix.cpp:146 #4 0x7fc6a265daeb in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x55cb88b7adc0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fc6a265ddf9 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x55cb88b7adc8, mutex=mutex@entry=0x55cb88b7adc0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7fc6a66c8ec8 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x55cb88b7adb8) at scenegraph/qsgthreadedrenderloop.cpp:245 #7 0x7fc6a66c8ec8 in QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x55cb88b7ad40) at scenegraph/qsgthreadedrenderloop.cpp:710 #8 0x7fc6a66c92fa in QSGRenderThread::run() (this=0x55cb88b7ad40) at scenegraph/qsgthreadedrenderloop.cpp:739 #9 0x7fc6a2656b52 in QThreadPrivate::start(void*) (arg=0x55cb88b7ad40) at thread/qthread_unix.cpp:360 #10 0x7fc69f5306db in start_thread (arg=0x7fc615937700) at pthread_create.c:463 #11 0x7fc6a1efc88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7fc61c9fd700 (LWP 17707)): #0 0x7fc6a1eeb0b4 in __GI___libc_read (fd=92, buf=0x7fc61c9fcbde, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fc66a47a021 in pa_read () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #2 0x7fc66ad80a2e in pa_mainloop_prepare () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7fc66ad814a0 in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fc66ad81560 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fc66ad8f3c9 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7fc66a4a9318 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #7 0x7fc69f5306db in start_thread (arg=0x7fc61c9fd700) at pthread_create.c:463 #8 0x7fc6a1efc88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7fc644884700 (LWP 12223)): #0 0x7fc69f5369f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55cb88871134) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fc69f5369f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55cb888710e0, cond=0x55cb88871108) at pthread_cond_wait.c:502 #2 0x7fc69f5369f3 in __pthread_cond_wait (cond=0x55cb88871108, mutex=0x55cb888710e0) at pthread_cond_wait.c:655 #3 0x7fc6a265daeb in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x55cb888710e0) at thread/qwaitcondition_unix.cpp:146 #4 0x7fc6a265daeb in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x55cb8f5a1d40, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fc6a265ddf9 in
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 --- Comment #107 from Rafael Linux User --- Is that true I wait it for summer, but I forgot my hopes. If it's solved, my congratulations for all developers that fix this long-term issue! They will make happy to all that bet for KDE as the Linux environment for business. ;) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415770] Environment variable 'GTK2_RC_FILES' is ignored
https://bugs.kde.org/show_bug.cgi?id=415770 --- Comment #2 from Guilherme Silva --- That was fast! Thanks a bunch, guys! -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #102 from David Sijbesma --- Hi everybody, first of all, Happy New Year! I'm pretty curious, is there any idea about an eta of a fixed version? Next to that, is ther anything I can help with? Cheers, David On Sun, 2019-12-29 at 16:34 +, David Bate wrote: > https://bugs.kde.org/show_bug.cgi?id=404990 > > --- Comment #100 from David Bate --- > Looks like this has now gone across the KDE platform. After re- > installing > KDE/Tumbleweed, I can no longer sign into google via the system > settings > > online accounts nor via dolphin > networks. > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415702] Cannot abort or stop find Duplicate process
https://bugs.kde.org/show_bug.cgi?id=415702 --- Comment #10 from Alexandre Belz --- Thank you Maik ! will test asap. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415557] Face detection - Advanced settings : restricted folder scope not taken into account
https://bugs.kde.org/show_bug.cgi?id=415557 --- Comment #10 from Alexandre Belz --- Thank you both of you ! And Happy New year ! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415770] Environment variable 'GTK2_RC_FILES' is ignored
https://bugs.kde.org/show_bug.cgi?id=415770 Mikhail Zolotukhin changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||5.18.0 Latest Commit||https://commits.kde.org/kde ||-gtk-config/5734413d8105699 ||252a3a0cfbba2265169581909 Resolution|--- |FIXED --- Comment #1 from Mikhail Zolotukhin --- Git commit 5734413d8105699252a3a0cfbba2265169581909 by Mikhail Zolotukhin. Committed on 02/01/2020 at 20:29. Pushed by gikari into branch 'master'. Respect GTK2_RC_FILES environmental variable Summary: If the above variable is set and it does not contain multiple paths, write GTK2 config into the designated config file, instead of the default one. FIXED-IN: 5.18.0 Test Plan: Check if the custom file provided by env variable is modified, when changing any settings, that are synchronized by kded module (icon theme, cursor theme etc) Simple test: # `mv ~/.gtkrc-2.0 ~/.gtkrc-2.0.bak` # `export GTK2_RC_FILES=~/.gtkrc-2.0.bak` # Restart kded5 with the above env variable # Change e.g. icon theme and see, that `.gtkrc-2.0.bak` is modified, but `.gtkrc-2.0` Reviewers: ngraham Reviewed By: ngraham Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D26375 M +4-1kded/configeditor.cpp https://commits.kde.org/kde-gtk-config/5734413d8105699252a3a0cfbba2265169581909 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415796] face thumbnail zoom level too wide
https://bugs.kde.org/show_bug.cgi?id=415796 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.0.0 Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/1fa3e45ac800 ||83b5b738b9a912d068adb19e4dd ||6 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Maik Qualmann --- Git commit 1fa3e45ac80083b5b738b9a912d068adb19e4dd6 by Maik Qualmann. Committed on 02/01/2020 at 20:26. Pushed by mqualmann into branch 'master'. change face thumbnail zoom level FIXED-IN: 7.0.0 M +1-1NEWS M +1-1core/app/items/delegate/itemfacedelegate.cpp M +6-3core/utilities/facemanagement/database/faceutils.cpp M +1-1core/utilities/facemanagement/database/faceutils.h https://invent.kde.org/kde/digikam/commit/1fa3e45ac80083b5b738b9a912d068adb19e4dd6 -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 411691] Only happens in Opensuse 15.1 in most games the cards will only autodrop a few, and then it stops., often crashes when Yukon is selected
https://bugs.kde.org/show_bug.cgi?id=411691 --- Comment #6 from Anton Aylward --- (In reply to Albert Astals Cid from comment #1) > This seems as something we already fixed. > > Can you try using kpat from our "nightly experimental" flatpak and see if > you can reproduce the problem? > > flatpak remote-add --if-not-exists flathub > https://flathub.org/repo/flathub.flatpakrepo > flatpak remote-add --if-not-exists kdeapps --from > https://distribute.kde.org/kdeapps.flatpakrepo > flatpak install kdeapps org.kde.kpat > flatpak run org.kde.kpat Unable to install on my OpenSuse 15.1 That is not recognized as a repesitory. === # zypper addrepo https://flathub.org/repo/flathub.flatpakrepo flatpack Adding repository 'flathub' .[done] Repository 'flathub' successfully added URI : https://flathub.org/repo/flathub.flatpakrepo Enabled : Yes GPG Check : Yes Autorefresh : No Priority: 99 (default priority) main:/etc/X11/xorg.conf.d # zypper install --from flatpack kpat Error building the cache: [flatpack|https://flathub.org/repo/flathub.flatpakrepo] Valid metadata not found at specified URL Warning: Skipping repository 'flathub' because of the above error. === That seems to be a file if unknown type and not a repository when I try browsing that directly and trying to see what else is at https://flathub.org/repo/ gets a "403 Forbidden" response. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415796] face thumbnail zoom level too wide
https://bugs.kde.org/show_bug.cgi?id=415796 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- We always added a fixed value of 70 pixels in all directions for the thumbnail. This is fine for big images with big faces. With small faces, too much environment is shown. I have now changed this and we are using 10% of the longest side of the face rectangle as the value. Although this will now add new thumbnails to the database, it might be a good idea to start with digiKam-7.0.0 with an empty thumbnail DB. Maik -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 415089] Dolphin Kio-gdrive authentication with Google account fails
https://bugs.kde.org/show_bug.cgi?id=415089 --- Comment #13 from Bob Recny --- Just adding a data point since the discussion has all been Kubuntu so far. I'm getting the same on Manjaro KDE. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 415089] Dolphin Kio-gdrive authentication with Google account fails
https://bugs.kde.org/show_bug.cgi?id=415089 Bob Recny changed: What|Removed |Added CC||n8...@arrl.net -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 415819] Notification entry in history too small in height resulting in an overlap
https://bugs.kde.org/show_bug.cgi?id=415819 --- Comment #1 from Postix --- You can also see that the title of the problematic notification elides instead of line breaks as the other notification with the same content. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 415819] Notification entry in history too small in height resulting in an overlap
https://bugs.kde.org/show_bug.cgi?id=415819 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 415819] New: Notification entry in history too small in height resulting in an overlap
https://bugs.kde.org/show_bug.cgi?id=415819 Bug ID: 415819 Summary: Notification entry in history too small in height resulting in an overlap Product: frameworks-knotifications Version: 5.65.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: pos...@posteo.eu CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 124861 --> https://bugs.kde.org/attachment.cgi?id=124861=edit Screenshot of the issue. SUMMARY As you can see in the screenshot, one notification's height was too small, resulting in an overlap with the notification beneath. "Do not reply to this email. You can add" and "[my mail address] has 1 new" overlap. This is the very first time I experienced it. After receiving a new notification and closing and opening the history, the issue was gone. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION Scaling: 1.5 Forced Font DPI: 144 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415818] New: Suggestion: enhance compositor auto suspend by window focus tracking condition
https://bugs.kde.org/show_bug.cgi?id=415818 Bug ID: 415818 Summary: Suggestion: enhance compositor auto suspend by window focus tracking condition Product: kwin Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: tempel.jul...@gmail.com Target Milestone: --- With KWin's auto suspend feature for compositing, the application has to actively tell the compositor to continue compositing when alt + tabbing out of a fullscreen window to have compositing again enabled for regular desktop usage. The Proton fullscreen hack does this, but (m)any other applications don't. This is true for e.g. Feral's Linux ports like Shadow of the Tomb Raider. When alt + tabbing out of the game, compositing doesn't turn itself on again. When switching out of a fullscreen window to the desktop (and any other window), the expectation is that compositing automatically turns on again until the user switches back to the fullscreen window, as desktop activity without compositor is a bad experience (tearing, no shadows, animations, transparency...). Also manually pressing keyboard buttons to do so is very inconvenient. As Roman has reaffirmed recently, implementing unredirect for KWin Xorg is out of scope due developer resources being limited and Wayland not yet being where it should be (totally understandable point imho). Now, perhaps there is room for a tradeoff that would require investing less efforts: I wonder if the auto suspend feature could be enhanced so that KWin automatically turns compositing on again when alt + tabbing out of a fullscreen window (and vice versa)? What if one more condition for turning off compositing was added: The application must not only tell KWin to suspend compositing, but its fullscreen window additionally also requires to have received focus before KWin actually does so. So KWin would e.g. poll each 0.5 seconds (or is there a better solution?) if the window requesting compositing to be suspended has focus (via FocusIn/Out events or _NET_WM_ACTIVE_WINDOW, which is offered as an option by Compton/Picom?). This should make sure that the compositor is always turned off when the fullscreen application is actually in use, while still maintaining compositing for desktop usage at the same time. The feature for that kind of window tracking could be made available as a separate checkbox (which might be turned off by default). This should make Plasma more attractive for people who game on Linux. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 415817] New: "Set Coordinates Manually..." always treats input as J2000 even if Jnow is selected.
https://bugs.kde.org/show_bug.cgi?id=415817 Bug ID: 415817 Summary: "Set Coordinates Manually..." always treats input as J2000 even if Jnow is selected. Product: kstars Version: 3.3.9 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: a...@randomuseless.info Target Milestone: --- SUMMARY The option to "Set Coordinates Manually..." has the option to input RA and Dec as either J2000 or Jnow. The buttons have no effect, though. The conversion from J2000 to Jnow is always applied, even if Jnow coordinates were entered and the Jnow button was clicked. This causes the wrong location to be used if Jnow coordinates are entered. STEPS TO REPRODUCE 1. Pointing -> Set Coordinates Manually... 2. In the dialog that pops up, the default is Jnow coordinates. Leave it set to Jnow and enter Jnow coordinates for Pollux: RA=07h 46m 31.63s, Dec=27:58:32.82 3. Leave the option set to Jnow and hit "OK". OBSERVED RESULT The sky view will change but Pollux will not be in the center. The error is equal to the difference between Jnow and J2000. EXPECTED RESULT The sky view will change and Pollux will be in the center of the view. The test can be redone by leaving the button set at Jnow but inputting the J2000 coordinates of Pollux: RA=07h 45m 19.38s, Dec=28:01:34.72. Leave it set for Jnow and hit "OK". The sky view will now center on Pollux even though the wrong datum was used. SOFTWARE/OS VERSIONS Windows: macOS: 10.14.6 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.
[digikam] [Bug 395501] Cannot define top level Tag name for faces
https://bugs.kde.org/show_bug.cgi?id=395501 caulier.gil...@gmail.com changed: What|Removed |Added CC||time...@free.fr --- Comment #18 from caulier.gil...@gmail.com --- *** Bug 279948 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 279948] Let the user decide which Tag is the root of people tags
https://bugs.kde.org/show_bug.cgi?id=279948 caulier.gil...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from caulier.gil...@gmail.com --- *** This bug has been marked as a duplicate of bug 395501 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415557] Face detection - Advanced settings : restricted folder scope not taken into account
https://bugs.kde.org/show_bug.cgi?id=415557 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #9 from caulier.gil...@gmail.com --- yes, Maik, i think too that Maintenance is the right place for this feature. Gilles -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415816] New: Selecting file name when renaming a file on the desktop is not constrained to file name field.
https://bugs.kde.org/show_bug.cgi?id=415816 Bug ID: 415816 Summary: Selecting file name when renaming a file on the desktop is not constrained to file name field. Product: plasmashell Version: 5.17.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: dekaymail+...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When renaming a file on the desktop, I can select both the text of the filename and other file icons at the same time. STEPS TO REPRODUCE 1. Start with a column of icons on the plasma desktop. Pick a file somewhere in the middle and use F2 to start renaming the file. 2. With the mouse, select the text of the filename by clicking and dragging. Keeping the left mouse button down, extend the selection out past the filename field and up to other icons. OBSERVED RESULT Both the filename text *and* other icons on the desktop are selected at the same time. This is unexpected behavior. For example, if I selected Delete, would it delete the text and the selected files? EXPECTED RESULT When renaming a file inline, the selection should be confined to the filename field only and not extended to other files on the desktop. Note that this works properly when renaming a file in Dolphin's various views, so the problem seems to be specific with plasma desktop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.4 KDE Frameworks Version: KDE 5.65.0 Qt Version: 5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415814] Plasma Integration Extension for Thunderbird
https://bugs.kde.org/show_bug.cgi?id=415814 Postix changed: What|Removed |Added See Also||https://bugzilla.mozilla.or ||g/show_bug.cgi?id=1603489 --- Comment #4 from Postix --- Haven't seen that [3] is from Kai. :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415814] Plasma Integration Extension for Thunderbird
https://bugs.kde.org/show_bug.cgi?id=415814 --- Comment #3 from Postix --- What a pity! There are indeed no relevant functions in the WebExtension API. [1] Do you know the relevant bug reports or have opened one for the desired API changes and/or notification, Kai? I only found the following: [2] WebExtensions needs a "new mail arrived" event [3] Add WebExtension API for opening email viewer --- [1] https://readthedocs.org/projects/thunderbird-webextensions/downloads/pdf/latest/ [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1599380 [3] https://bugzilla.mozilla.org/show_bug.cgi?id=1603489 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 415757] vex x86->IR: unhandled instruction bytes: 0x66 0xF 0xCE 0x4F
https://bugs.kde.org/show_bug.cgi?id=415757 --- Comment #6 from Alex Henrie --- (In reply to Julian Seward from comment #5) > And you're aware of the as-yet unmerged PDB reading fixes at [1], yes? > https://bugs.kde.org/show_bug.cgi?id=253657 Yes, I know about those patches. There are also patches somewhere to make Wine produce PDB files for its own DLLs, but they have not been accepted into Wine yet. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412803] Pen Pressure creates blobs/circles along any and every stroke
https://bugs.kde.org/show_bug.cgi?id=412803 Sam changed: What|Removed |Added CC||hiebertsaman...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 415815] New: kontact crashes when swithcing from akregator to kmail
https://bugs.kde.org/show_bug.cgi?id=415815 Bug ID: 415815 Summary: kontact crashes when swithcing from akregator to kmail Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: t...@timfolger.net Target Milestone: --- Application: kontact (5.13.0 (19.12.0)) Qt Version: 5.13.1 Frameworks Version: 5.65.0 Operating System: Linux 5.3.12-2-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: I'm running kontact version 5.13.0, kde plasma 5.17.4, kde frameworks 5.65.0, Qt 5.13.1, kernel 5.3.12-2 on opensuse tumbleweed. After a recent upgrade kontact has been crashing whenever I switch from akregator to kmail. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f88a0460a80 (LWP 3718))] Thread 24 (Thread 0x7f8801443700 (LWP 6212)): #0 0x7f88af1a29ca in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f88a917d366 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f88a917dd33 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f88a917deb1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f88a9135ff1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f88a91391db in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f88a9139584 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f88a91801a5 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f88af19bf2a in start_thread () from /lib64/libpthread.so.0 #9 0x7f88b16cb4af in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7f8827656700 (LWP 6209)): #0 0x7f88ae79a594 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f88ae74ece1 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #2 0x7f88ae74f222 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f88ae74f39f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f88b03b898b in QEventDispatcherGlib::processEvents (this=0x7f8884001e60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f88b03610cb in QEventLoop::exec (this=this@entry=0x7f8827655b20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f88b0199021 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f88b019a1a2 in QThreadPrivate::start (arg=0x5575ea325de0) at thread/qthread_unix.cpp:360 #8 0x7f88af19bf2a in start_thread () from /lib64/libpthread.so.0 #9 0x7f88b16cb4af in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7f8802c46700 (LWP 6202)): #0 0x7f88b16bc60c in read () from /lib64/libc.so.6 #1 0x7f88ae79616f in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f88ae74edd7 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f88ae74f222 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f88ae74f39f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f88b03b898b in QEventDispatcherGlib::processEvents (this=0x7f8814025ff0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f88b03610cb in QEventLoop::exec (this=this@entry=0x7f8802c45b20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f88b0199021 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f88b019a1a2 in QThreadPrivate::start (arg=0x5575e757cd80) at thread/qthread_unix.cpp:360 #9 0x7f88af19bf2a in start_thread () from /lib64/libpthread.so.0 #10 0x7f88b16cb4af in clone () from /lib64/libc.so.6 Thread 21 (Thread 0x7f8881ffb700 (LWP 6185)): #0 0x7f88af1a29ca in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f88a917d366 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f88a917dd33 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f88a917deb1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f88a9135ff1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f88a91391db in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f88a9139584 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f88a91801a5 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f88af19bf2a in start_thread () from /lib64/libpthread.so.0 #9 0x7f88b16cb4af in clone () from /lib64/libc.so.6 Thread 20 (Thread 0x7f880bfff700 (LWP 5316)): #0 0x7f88b16c0bdf in poll () from /lib64/libc.so.6 #1 0x7f88a4b354f2 in ?? () from /usr/lib64/libpulse.so.0 #2 0x7f88a4b26e39 in pa_mainloop_poll () from /usr/lib64/libpulse.so.0
[digikam] [Bug 415702] Cannot abort or stop find Duplicate process
https://bugs.kde.org/show_bug.cgi?id=415702 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.0.0 Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/e4a4fc3e7d3f ||d9e4aac5faa1583a67ec298b57a ||4 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #9 from Maik Qualmann --- Git commit e4a4fc3e7d3fd9e4aac5faa1583a67ec298b57a4 by Maik Qualmann. Committed on 02/01/2020 at 19:02. Pushed by mqualmann into branch 'master'. use the old signal/slot method for Windows FIXED-IN: 7.0.0 M +1-1NEWS M +8-2core/utilities/maintenance/maintenancetool.cpp https://invent.kde.org/kde/digikam/commit/e4a4fc3e7d3fd9e4aac5faa1583a67ec298b57a4 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415557] Face detection - Advanced settings : restricted folder scope not taken into account
https://bugs.kde.org/show_bug.cgi?id=415557 Maik Qualmann changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED Version Fixed In||7.0.0 --- Comment #8 from Maik Qualmann --- The album selector is already deactivated when the training option is activated. We will think about moving the training mode into the maintenance tool. I close the bug for now. Maik -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 415636] "invalid kns backend" error in seen Discover due to ksysguard's knsrc file
https://bugs.kde.org/show_bug.cgi?id=415636 Paradoxe changed: What|Removed |Added CC||pubc...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 --- Comment #106 from Łukasz Szeremeta --- (In reply to Nate Graham from comment #105) > This is now implemented with the new kio-fuse system! > > https://cgit.kde.org/kio-fuse.git/ > > Go bug your distros of choice to package it and ship it by default! > > Let's all give a big round of applause to Alexander Saoutkin and Fabian Vogt > who took the lead on this challenging and important project. Yay, finally this was done. Yes, big applause to Alexander Saoutkin and Fabian Vogt. Hope that this will be added to KDE Neon soon :-) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 398446] FUSE-mounted remote locations accessed with a KIO-using app are not visible in non-KDE open/save dialog
https://bugs.kde.org/show_bug.cgi?id=398446 Nate Graham changed: What|Removed |Added Summary|Remote locations accessed |FUSE-mounted remote |with a KIO-using app are|locations accessed with a |not visible in a non-KDE|KIO-using app are not |file picker |visible in non-KDE ||open/save dialog Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Nate Graham --- I wonder if this will require changes to GTK. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415814] Plasma Integration Extension for Thunderbird
https://bugs.kde.org/show_bug.cgi?id=415814 --- Comment #2 from Kai Uwe Broulik --- None of the suggested features are possible with Thunderbird's WebMail extension API. The only feature that I managed to implement is boarding pass extraction (main focus of this project) and finding contacts and mails in KRunner (and even that doesn't really work well with the API Thunderbird provides) The notifications should just be fixed in Thunderbird directly... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 362834] F4 doesn't open terminal in the current directory at least on MTP and SMB
https://bugs.kde.org/show_bug.cgi?id=362834 Bug 362834 depends on bug 75324, which changed state. Bug 75324 Summary: Integrate KIO Slaves into file system using FUSE gateway https://bugs.kde.org/show_bug.cgi?id=75324 What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
