[kdf] [Bug 397196] "KDEInit could not launch /usr/bin/kdf" when KDiskFree started by clicking Dolphin status bar is closed
https://bugs.kde.org/show_bug.cgi?id=397196 Andrei A. Lomov changed: What|Removed |Added CC||lo...@math.nsc.ru --- Comment #2 from Andrei A. Lomov --- Reproducible on Debian Stable (2019-09-20) install KDiskFree open menu, click KDiskFree close KDiskFree, an error message appears: KDEInit could not launch '/usr/bin/kdf' The error message does not appear when I close KDiskFree started via konsole $ kdf Not reproducible on Debian Testing. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 413461] New: Latte-dock is badly positioned on Debian Wayland
https://bugs.kde.org/show_bug.cgi?id=413461 Bug ID: 413461 Summary: Latte-dock is badly positioned on Debian Wayland Product: lattedock Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: prog-amat...@tutamail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. To have Debian sid (GNOME 3.34, kernel 5, and connect on Wayland session) 2. To install Latte-dock from Software center 3. Enjoy The dock is on middle of my screen and I can't move it down (mouse click or "bottom" buttton). Bottom button should position Latte-dock on the bottom of the screen. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Debian Sid Wayland (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: Sorry to post here despite I am on Debian, but I just have followed the bug tracker link for latte-dock. Thank you -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412160] Kwin (Kwin_x11) segmentation fault causes by libthread_db.
https://bugs.kde.org/show_bug.cgi?id=412160 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.
[kdev-python] [Bug 411956] Fails to build against Python 3.8
https://bugs.kde.org/show_bug.cgi?id=411956 --- Comment #5 from David Geiger --- Confirmed on Mageia Cauldron that now kdev-python build against python 3.8. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 413460] New: KDE CONNECT CRASHES
https://bugs.kde.org/show_bug.cgi?id=413460 Bug ID: 413460 Summary: KDE CONNECT CRASHES Product: kdeconnect Version: 1.3.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: carlos.r.castr...@gmail.com Target Milestone: --- Application: kdeconnectd (1.3.5) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.0.0-32-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: Nothing special happens when I'm surfing the internet using Opera, this error hadn't happened before. - Unusual behavior I noticed: The crash can be reproduced sometimes. -- Backtrace: Application: Demonio de KDE Connect (kdeconnectd), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff2b95fb800 (LWP 16391))] Thread 4 (Thread 0x7ff29e1e7700 (LWP 16402)): #0 0x7ff2b648cbf9 in __GI___poll (fds=0x7ff290004a10, nfds=1, timeout=10031) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ff2b0fb55c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff2b0fb56dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff2b6ddf9db in QEventDispatcherGlib::processEvents (this=0x7ff29b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7ff2b6d7feaa in QEventLoop::exec (this=this@entry=0x7ff29e1e6da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7ff2b6b9b3ca in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7ff2b6b9cb72 in QThreadPrivate::start (arg=0x556fe080e930) at thread/qthread_unix.cpp:360 #7 0x7ff2b31526db in start_thread (arg=0x7ff29e1e7700) at pthread_create.c:463 #8 0x7ff2b649988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7ff29e9e8700 (LWP 16400)): #0 0x7ff2b64880b4 in __GI___libc_read (fd=7, buf=0x7ff29e9e7b60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7ff2b0ffa2d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff2b0fb50b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff2b0fb5570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff2b0fb56dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff2b6ddf9db in QEventDispatcherGlib::processEvents (this=0x7ff298000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7ff2b6d7feaa in QEventLoop::exec (this=this@entry=0x7ff29e9e7d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7ff2b6b9b3ca in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7ff2b72560e5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7ff2b6b9cb72 in QThreadPrivate::start (arg=0x7ff2b74cdd80) at thread/qthread_unix.cpp:360 #10 0x7ff2b31526db in start_thread (arg=0x7ff29e9e8700) at pthread_create.c:463 #11 0x7ff2b649988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7ff2a760d700 (LWP 16393)): #0 0x7ff2b648cbf9 in __GI___poll (fds=0x7ff2a760cca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ff2af8d2747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7ff2af8d436a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7ff2aa3f2f00 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7ff2b6b9cb72 in QThreadPrivate::start (arg=0x556fe07ae170) at thread/qthread_unix.cpp:360 #5 0x7ff2b31526db in start_thread (arg=0x7ff2a760d700) at pthread_create.c:463 #6 0x7ff2b649988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7ff2b95fb800 (LWP 16391)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7ff2b63b8801 in __GI_abort () at abort.c:79 #8 0x7ff2b67f5957 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x7ff2b67fbab6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x7ff2b67fbaf1 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #11 0x7ff2b67fbd79 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #12 0x7ff2b6dbb9bf in QVector::realloc (this=this@entry=0x7ff2b878cf38 , aalloc=, options=..., options@entry=...) at ../../include/QtCore/../../src/corelib/tools/qvector.h:713 #13 0x7ff2b6db62e7 in QVector::detach (this=0x7ff2b878cf38 ) at ../../include/QtCore/../../src/corelib/tools/qvector.h:396 #14 QVector::data (this=0x7ff2b878cf38 ) at ../../include/QtCore/../../src/corelib/tools/qvector.h:132 #15 QVector::operator[] (i=5, this=0x7ff2b878cf38 ) at
[valgrind] [Bug 413410] unhandled amd64-darwin syscall: mach:50 (on macOS 10.15)
https://bugs.kde.org/show_bug.cgi?id=413410 Rhys Kidd changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=402696 --- Comment #2 from Rhys Kidd --- Actually, the specific error message you reported is already tracked here at bz#402696 (tzset) due to valgrind missing support for a mach call. However, I'd still be interested in your feedback on the other questions. I'll leave this bug report open for a little while, but the main error reported in your log is a duplicate of bz#402696. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 402696] eq_SyscallStatus the 'impossible' happened with: unhandled amd64-darwin syscall: mach:50 (tzset)
https://bugs.kde.org/show_bug.cgi?id=402696 Rhys Kidd changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=413410 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 413410] unhandled amd64-darwin syscall: mach:50 (on macOS 10.15)
https://bugs.kde.org/show_bug.cgi?id=413410 Rhys Kidd changed: What|Removed |Added Assignee|jsew...@acm.org |rhysk...@gmail.com Depends on||412745 Summary|Mac Os 10.15 valgrind |unhandled amd64-darwin |3.15.0 |syscall: mach:50 (on macOS ||10.15) CC||rhysk...@gmail.com --- Comment #1 from Rhys Kidd --- Hi - thanks for the bug report. Valgrind currently does not support macOS 10.15, with a substantial amount of work to go. See further tracker bug at bz#412745. Couple of questions: - What out of tree patches have you applied to valgrind to get it to build? (I presume that you build your own version of valgrind from the below log). - What is the target program that you are tracing? If proprietary, can you recreate the same log/errors with a simple C program that you can share here. Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=412745 [Bug 412745] Support macOS Catalina (10.15) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 412745] Support macOS Catalina (10.15)
https://bugs.kde.org/show_bug.cgi?id=412745 Rhys Kidd changed: What|Removed |Added Blocks||413410 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=413410 [Bug 413410] unhandled amd64-darwin syscall: mach:50 (on macOS 10.15) -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 413459] New: Support compilation albums
https://bugs.kde.org/show_bug.cgi?id=413459 Bug ID: 413459 Summary: Support compilation albums Product: elisa Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: squeakypanca...@disroot.org Target Milestone: --- Created attachment 123489 --> https://bugs.kde.org/attachment.cgi?id=123489=edit Screenshot SUMMARY Elisa treats every artist in a compilation as having their own album with the same album name even if they are in the same folder. STEPS TO REPRODUCE 1. have an album with multiple artists 2. open Elisa 3. OBSERVED RESULT Each artist is treated as having their own album EXPECTED RESULT Albums with the same name but different artists in the same folder should be displayed as one album. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 270808] External hard disks should be spun down when 'safely removed'
https://bugs.kde.org/show_bug.cgi?id=270808 Gordon Lack changed: What|Removed |Added CC||gordon.l...@dsl.pipex.com --- Comment #69 from Gordon Lack --- And powering off an external drive can be a real pain, as I then need to physically unplug and re-insert as device if I want to use it again. I may well want to unmount a device (as I don;t need it "now"), but leave it plugged in as I may need it later. So I've opened https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1827778 to re-add the option to *just* unmount a device. -- You are receiving this mail because: You are watching all bug changes.
[knotes] [Bug 413458] New: Can't remove alarm
https://bugs.kde.org/show_bug.cgi?id=413458 Bug ID: 413458 Summary: Can't remove alarm Product: knotes Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: matheus...@infonet.com.br CC: myr...@kde.org Target Milestone: --- SUMMARY An alarm keeps showing up even with the note deleted. STEPS TO REPRODUCE 1. Create a note. 2. Configure an alarm to it. 3. Remove the alarm when it appears on screen. OBSERVED RESULT The alarm keeps showing up many times during the day, probably one hour after. EXPECTED RESULT The alarm should never show up again, since the note had been deleted and the alarm removed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 10 Stable (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION kernel 4.19.0-6-amd64 -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 412455] Segfault of LabPlot2 when opening settings dropdown
https://bugs.kde.org/show_bug.cgi?id=412455 --- Comment #8 from waterlub...@rocketmail.com --- (In reply to Alexander Semke from comment #7) > (In reply to waterlubber from comment #6) > > (In reply to Alexander Semke from comment #4) > > > (In reply to waterlubber from comment #3) > > > > I tried with some other KDE/QT applications, like KDenlive (with the > > > > same > > > > menu option) and KStars, and was not able to reproduce the issue there. > > > > It > > > > appears to be limited to LabPlot2. > > > I manage to reproduce this only once on my computer. Hard to > > > understand/debug unfortunately... > > > > > > Is LabPlot linked to the same KF5 libraries as kdenlive? > > > > > > Any chance to compile the new version released today > > > (https://labplot.kde.org/2019/10/24/labplot-2-7-released/) and try again? > > > > I updated to the latest version from the Arch repos -- version 2.7 -- and > > experienced the same issue. > > I also tried compiling the latest version and running from there -- same > > problem. > > > > Would compiling with debug flags help? How would I go about that? > Your system seems to have already some debug symbols installed. From the > backtrace you pasted in your first comment, the crash happens in Thread 1 > and the last frames are > > #6 0x7f3939161fe5 in () at /usr/lib/libKF5ConfigWidgets.so.5 > #7 0x7f3937dc3b70 in QMetaObject::activate(QObject*, int, int, void**) > () at /usr/lib/libQt5Core.so.5 > #8 0x7f39388dee07 in QMenu::popup(QPoint const&, QAction*) () at > /usr/lib/libQt5Widgets.so.5 > #9 0x7f39388e1099 in QMenu::internalDelayedPopup() () at > /usr/lib/libQt5Widgets.so.5 > > It crashes in KF5ConfigWidgets somewhere. We miss the debug information here > so I cannot say what is causing the problem here. Either we get the debug > symbols for KF5ConfigWidgets on your system or I can try to reproduce it > locally or try to see from the code what could cause such a problem. > > Just to double confirm, kdenlinve that doesn't have this problem is also > using KDE Frameworks 5.63, right? Yes, kdenlive shows that it's running on 5.63.0. I also tried moving ~/.config/labplot2rc to see if it was a configuration problem, but the issue remained. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413300] night color interferes with color correction for monitor
https://bugs.kde.org/show_bug.cgi?id=413300 Vasily Khoruzhick changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413422] No access of photo collection via digiKam
https://bugs.kde.org/show_bug.cgi?id=413422 --- Comment #4 from MR --- Erasing did the trick! Thanks a lot Maik. Got another 111.000 photos to sort, and there is just no alternative to digikam. Regards Am 25.10.19 um 11:15 schrieb Maik Qualmann: > https://bugs.kde.org/show_bug.cgi?id=413422 > > --- Comment #3 from Maik Qualmann --- > First of all the database stays where it always was. Under the path where > trying to open the database is a very very old database with version 1. > > "/media/mr/ADATA HD720/- PHOTO -/digikam4.db" > > Attempting to upgrade from version 1 to version 8 will fail - not possible > anymore. Here is the next problem, version 8 is also old, your digiKam version > is also very old. First correct the path of the database or delete the > digikamrc file to start a new setup. > > Maik > -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 --- Comment #11 from Albert Astals Cid --- I'm 93% sure this is a duplicate of 396137 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413304] Chinese characters instead of Polish diacritical marks
https://bugs.kde.org/show_bug.cgi?id=413304 Albert Astals Cid changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #11 from Albert Astals Cid --- Sadly, needs someone to be able to reproduce it before being able to fix it -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 413377] Setting auto-login for a user does not change config files
https://bugs.kde.org/show_bug.cgi?id=413377 WojtasJD changed: What|Removed |Added CC||wojta...@notowany.pl --- Comment #1 from WojtasJD --- I can confirm this behavior on two machines with KDE neon 5.17.1 installed - in my case I cannot switch off auto-login for a user in "user-manager": 1. Issue this command from Konsole: $ kcmshell5 user_manager 2. Unset auto-login for a user 3. After entering password (ID: org.freedesktop.accounts.user-administration) Konsole throws this: QDBusArgument: read from a write-only object QDBusArgument: read from a write-only object QDBusArgument: read from a write-only object 4. After entering password (ID: org.kde.kcontrol.kcmsddm.save) Konsole throws this: Warning from helper: QFSFileEngine::open: No file name specified Warning from helper: Empty filename passed to function 5. Close and open "user-manager" - setting is not saved. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413446] Mouse stuck on left side
https://bugs.kde.org/show_bug.cgi?id=413446 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Boudewijn Rempt --- Um, from irc i got the impression that you also figured out the bug was fixed? "18:55:48 <+Crack> yo I was the guy that posted earlier about the cursor issue I fixed it " Is that the case? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413304] Chinese characters instead of Polish diacritical marks
https://bugs.kde.org/show_bug.cgi?id=413304
--- Comment #10 from pyj...@protonmail.com ---
(In reply to Albert Astals Cid from comment #9)
> Do you get any warning if you start okular from the command line (i.e.
> konsole)?
No, I don't get any error but when I open test.markdown file i get every time
strange message:
`discarding "Send sms via KDE Connect" ("ShareUrl")`
--
You are receiving this mail because:
You are watching all bug changes.
[kstars] [Bug 413457] New: Red Butten and Android
https://bugs.kde.org/show_bug.cgi?id=413457 Bug ID: 413457 Summary: Red Butten and Android Product: kstars Version: 3.3.6 Platform: Other OS: other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: alepalm...@gmail.com Target Milestone: --- Hi Kstars Team could you install a red button at the next update that is clearly arranged in the desk bar? on my Huawei P20 Pro With Android 9.1, the KStars is not running after it had updated. Thank you and a good weekend A.Palmieri -- You are receiving this mail because: You are watching all bug changes.
[kde-windows] [Bug 413039] Critical: could not load fallback mirror list from QUrl
https://bugs.kde.org/show_bug.cgi?id=413039 --- Comment #32 from Jeditobe --- Ralf Habacker -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413455] New: Plasma (wayland) crash on closing firefox
https://bugs.kde.org/show_bug.cgi?id=413455 Bug ID: 413455 Summary: Plasma (wayland) crash on closing firefox Product: plasmashell Version: 5.17.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: loic.gro...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.1) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-19-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: Closing a Firefox (Nightly running on Wayland backend) window - Unusual behavior I noticed: The firefox window was glitching (garbled display when maximized) Other windows on the desktop (including DRKonqi) are also glitching -- 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=0x55b943f0a350) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 [Current thread is 1 (Thread 0x7f1dd5e57800 (LWP 1595))] Thread 11 (Thread 0x7f1da8b2a700 (LWP 3098)): [KCrash Handler] #6 0x7f1dd92be44a in wl_proxy_marshal_constructor () at /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 #7 0x7f1dd85b in QtWaylandClient::QWaylandWindow::handleUpdate() () at /usr/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #8 0x7f1dd4081740 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #9 0x7f1dd9e0b7f1 in QOpenGLContext::swapBuffers(QSurface*) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #10 0x7f1ddb4d9caa in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7f1ddb4dd9d8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7f1dd981fcc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f1dd8cc9669 in start_thread (arg=) at pthread_create.c:479 #14 0x7f1dd94a2323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f1da9467700 (LWP 1698)): #0 0x7f1dd8cd02c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b943386cd0) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f1dd8cd02c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55b943386c80, cond=0x55b943386ca8) at pthread_cond_wait.c:508 #2 0x7f1dd8cd02c6 in __pthread_cond_wait (cond=0x55b943386ca8, mutex=0x55b943386c80) at pthread_cond_wait.c:638 #3 0x7f1dd9825def in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f1dd9825ee1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f1ddb4dd7b9 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f1ddb4dda1a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f1dd981fcc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f1dd8cc9669 in start_thread (arg=) at pthread_create.c:479 #9 0x7f1dd94a2323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f1db8b5e700 (LWP 1678)): #0 0x7f1dd808d58d in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f1dd808ebac in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1dd808fefb in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1dd809096b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f1dd8090b73 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f1dd9a3e6c3 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f1dd99e563b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1dd981ea75 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f1dd981fcc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f1dd8cc9669 in start_thread (arg=) at pthread_create.c:479 #10 0x7f1dd94a2323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f1dab7bc700 (LWP 1671)): #0 0x7f1dd94912ac in __GI___libc_read (nbytes=16, buf=0x7f1dab7bbb50, fd=35) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7f1dd94912ac in __GI___libc_read (fd=35, buf=0x7f1dab7bbb50, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f1dd80d863f in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1dd809058e in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f1dd80909e2 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f1dd8090b73 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6
[kde-windows] [Bug 413039] Critical: could not load fallback mirror list from QUrl
https://bugs.kde.org/show_bug.cgi?id=413039 --- Comment #31 from Jeditobe --- > Here is an update of the installer May I kindly ask you to upload the new binary to https://github.com/KDE/kdewin-installer/releases/tag/v1.4.0 as well So we can reuse it for ReactOS RAPPS -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 413418] KDE Partition Manager crashes when opening partition information on USB drive
https://bugs.kde.org/show_bug.cgi?id=413418 --- Comment #1 from Andrius Štikonas --- I've seen this backtrace before but I was never able to reliably reproduce it myself. Would you be able to try the following patch (to the kpmcore repository)? It should print partition()->capacity() to the terminal, just to double check that we are not dividing by 0. Note this patch does not fix crash, this is just for diagnostics. diff --git a/src/gui/partwidget.cpp b/src/gui/partwidget.cpp index 57ebf23..e3ff2af 100644 --- a/src/gui/partwidget.cpp +++ b/src/gui/partwidget.cpp @@ -21,6 +21,8 @@ #include "fs/filesystem.h" #include "util/capacity.h" +#include + #include #include #include @@ -93,6 +95,7 @@ void PartWidget::paintEvent(QPaintEvent*) if (partition() == nullptr) return; +qDebug() << partition()->capacity(); const int usedPercentage = static_cast(partition()->used() * 100 / partition()->capacity()); const int w = width() * usedPercentage / 100; -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 413456] New: [Marble Maps 1.2] No map data is downloaded
https://bugs.kde.org/show_bug.cgi?id=413456 Bug ID: 413456 Summary: [Marble Maps 1.2] No map data is downloaded Product: marble Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android Assignee: marble-b...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- Created attachment 123488 --> https://bugs.kde.org/attachment.cgi?id=123488=edit Screenshot displaying the issue I installed Marble maps 1.2.0 using the APK found at https://files.kde.org/marble/downloads/android/. The star map, sun and moon display correctly when zoomed out fully, but no street map data at all is displayed (even land mass/continent data) at any zoom level. I have attempted clearing the application's cache, data and reinstalling. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 413316] Can't see the contents of my Nextcloud calendar
https://bugs.kde.org/show_bug.cgi?id=413316 aux...@gmail.com changed: What|Removed |Added CC||aux...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413446] Mouse stuck on left side
https://bugs.kde.org/show_bug.cgi?id=413446 --- Comment #3 from Crack --- Created attachment 123487 --> https://bugs.kde.org/attachment.cgi?id=123487=edit tablet logging I figured it out -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413354] Memory leak
https://bugs.kde.org/show_bug.cgi?id=413354 Andrius changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #7 from Andrius --- Strange: when I first set the wallpaper as "Astronomy Picture of the Day", RAM and CPU spikes for a minute or so, but then drops to normal. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413354] Memory leak
https://bugs.kde.org/show_bug.cgi?id=413354 Andrius changed: What|Removed |Added Resolution|WORKSFORME |--- Ever confirmed|1 |0 Status|RESOLVED|REPORTED --- Comment #6 from Andrius --- Still the same for me -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 397347] UdevQt: unhandled device action "bind"
https://bugs.kde.org/show_bug.cgi?id=397347 Germano Massullo changed: What|Removed |Added Version|5.48.0 |5.59.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413454] New: Plasma crashes when closing Spotify
https://bugs.kde.org/show_bug.cgi?id=413454 Bug ID: 413454 Summary: Plasma crashes when closing Spotify Product: plasmashell Version: 5.16.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ch...@rpgfiction.net CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.5) Qt Version: 5.12.5 Frameworks Version: 5.60.0 Operating System: Linux 4.19.72-gentoo-richBOOK x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: Closing Spotify after a longer session. The bug seems time-related, as it cannot be reproduced by simply retrying. Then, after some hours, next time it will crash again. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdcd94bb040 (LWP 4417))] Thread 14 (Thread 0x7fdc77fff700 (LWP 9628)): #0 0x7fdcde3b311c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdcdf49aa90 in () at /usr/lib64/libQt5Core.so.5 #2 0x7fdcdf49a8aa in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7fdce110856f in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fdce11087c0 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7fdcdf49404e in () at /usr/lib64/libQt5Core.so.5 #6 0x7fdcde3ac408 in start_thread () at /lib64/libpthread.so.0 #7 0x7fdcdf12331f in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7fdc766fc700 (LWP 9627)): #0 0x7fdcdf112b90 in read () at /lib64/libc.so.6 #1 0x7fdcd998d05d in pa_read () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #2 0x7fdcdca7c277 in pa_mainloop_prepare () at /usr/lib64/libpulse.so.0 #3 0x7fdcdca7cbd8 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7fdcdca7cc80 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7fdcdca8b099 in () at /usr/lib64/libpulse.so.0 #6 0x7fdcd99baf91 in () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #7 0x7fdcde3ac408 in start_thread () at /lib64/libpthread.so.0 #8 0x7fdcdf12331f in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7fdc8fdff700 (LWP 6544)): #0 0x7fdcde3b311c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdcdf49aa90 in () at /usr/lib64/libQt5Core.so.5 #2 0x7fdcdf49a8aa in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7fdce110856f in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fdce11087c0 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7fdcdf49404e in () at /usr/lib64/libQt5Core.so.5 #6 0x7fdcde3ac408 in start_thread () at /lib64/libpthread.so.0 #7 0x7fdcdf12331f in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7fdca9425700 (LWP 5642)): #0 0x7fdcde3b311c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdcdf49aa90 in () at /usr/lib64/libQt5Core.so.5 #2 0x7fdcdf49a8aa in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7fdce110856f in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fdce11087c0 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7fdcdf49404e in () at /usr/lib64/libQt5Core.so.5 #6 0x7fdcde3ac408 in start_thread () at /lib64/libpthread.so.0 #7 0x7fdcdf12331f in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7fdca8a6e700 (LWP 5461)): #0 0x7fdcde3b311c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdcdf49aa90 in () at /usr/lib64/libQt5Core.so.5 #2 0x7fdcdf49a8aa in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7fdce110856f in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fdce11087c0 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7fdcdf49404e in () at /usr/lib64/libQt5Core.so.5 #6 0x7fdcde3ac408 in start_thread () at /lib64/libpthread.so.0 #7 0x7fdcdf12331f in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fdcab10b700 (LWP 5429)): #0 0x7fdcde3b311c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdcdf49aa90 in () at /usr/lib64/libQt5Core.so.5 #2 0x7fdcdf49a8aa in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7fdce110856f in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fdce11087c0 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7fdcdf49404e in () at /usr/lib64/libQt5Core.so.5 #6 0x7fdcde3ac408 in start_thread () at /lib64/libpthread.so.0 #7 0x7fdcdf12331f in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fdcbd4dd700 (LWP 5344)): #0 0x7fdcdf682ed1 in
[frameworks-solid] [Bug 397347] UdevQt: unhandled device action "bind"
https://bugs.kde.org/show_bug.cgi?id=397347 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413446] Mouse stuck on left side
https://bugs.kde.org/show_bug.cgi?id=413446 --- Comment #2 from Crack --- (In reply to wolthera from comment #1) > Could you add a tabletlog? > > https://docs.krita.org/en/KritaFAQ.html#what-if-your-tablet-is-not- > recognized-by-krita > > Then we can see if there's something weird going on with how Krita gets the > events, or something else is happening... where does krita save the log data -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 397347] UdevQt: unhandled device action "bind"
https://bugs.kde.org/show_bug.cgi?id=397347 Germano Massullo changed: What|Removed |Added CC||germano.massu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 413453] kf5.kio.core: [...] Please fix the "kio_kamera" KIO slave
https://bugs.kde.org/show_bug.cgi?id=413453
--- Comment #1 from Germano Massullo ---
kf5.kio.core.dirlister: QUrl("file:///tmp/gwenview.fOPVXf.part") ->
QUrl("file:///tmp/gwenview.fOPVXf")
kf5.kio.core.dirlister: Item not found:
QUrl("file:///tmp/gwenview.fOPVXf.part")
kf5.kio.core.dirlister: QUrl("file:///tmp/gwenview.ahwoCw.part") ->
QUrl("file:///tmp/gwenview.ahwoCw")
kf5.kio.core.dirlister: Item not found:
QUrl("file:///tmp/gwenview.ahwoCw.part")
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kio] [Bug 413453] New: kf5.kio.core: [...] Please fix the "kio_kamera" KIO slave
https://bugs.kde.org/show_bug.cgi?id=413453
Bug ID: 413453
Summary: kf5.kio.core: [...] Please fix the "kio_kamera" KIO
slave
Product: frameworks-kio
Version: 5.59.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: fa...@kde.org
Reporter: germano.massu...@gmail.com
CC: kdelibs-b...@kde.org
Target Milestone: ---
In kdedebugsettings I enabled kiocore and dolphind debuginfos since MTP does
not work properly.
In journalctl I can read some related messages like
kdeinit5[20672]: kf5.kio.core: UDSEntry for '.' not found, creating a default
one. Please fix the "kio_kamera" >
kwrite[18203]: kf5.kio.core: mimeType() not emitted when sending first data!;
job URL = QUrl("camera:/Nikon%252>
kdeinit5[20672]: kf5.kio.core: finished() called after error()! Please fix the
"kio_kamera" KIO slave
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 412684] [Wayland] kwin_wayland[3904]: segfault at 10 ip 00007f35691b6c30 sp 00007ffcf514ce98 error 4 in libKF5WaylandServer.so.5.63.0[7f3569191000+60000]
https://bugs.kde.org/show_bug.cgi?id=412684 --- Comment #19 from WojtasJD --- KDE neon updated from 5.17 to 5.17.1 and logging to a Wayland session is working again - thanks. But there is another issue with killed keyboard & mouse after resuming from sleep, like this https://forums.opensuse.org/showthread.php/530065-KDE-Plasma-on-Wayland-no-mouse-and-keyboard-after-resume - but this is a case for another bug report... -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 413452] New: Everything is detected as a 'web browser' sometimes something else, but mostly a browser
https://bugs.kde.org/show_bug.cgi?id=413452 Bug ID: 413452 Summary: Everything is detected as a 'web browser' sometimes something else, but mostly a browser Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: tigrank2...@gmail.com Target Milestone: --- Created attachment 123486 --> https://bugs.kde.org/attachment.cgi?id=123486=edit KGet opening screenshot, shouldn't it be 'Download manager'? SUMMARY STEPS TO REPRODUCE 1. Open a not instantly opening app (example: Ark) 2. Hover over it 3. An info box comes up I see 'web browser' description Maybe use it's real description (for Ark it is 'Archiving tool') It is not only in Ark, it is on other software too Sometimes it's something else For example KGet shows up as Software Center or something SOFTWARE/OS VERSIONS Linux: neon 5.0.0-32-generic #34~18.04.2-Ubuntu SMP Thu Oct 10 10:36:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux (available in About System) KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 --- Comment #33 from Wulf --- Yes now I have this problem also with nextcloud. Both Arch Linux: Desktop and Raspi (Nextcloudserver) And there is still Bug https://bugs.kde.org/show_bug.cgi?id=355441, which I also have with nextcloud -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407889] Shift-clicking in folder view with list view mode stops working properly after a restart
https://bugs.kde.org/show_bug.cgi?id=407889 Alex changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #3 from Alex --- Reopening, apparently I just got lucky when resizing panels back then. At least I have more information on how to reproduce it now. Using a panel attached to the left or right screen edge and not making the panel "thick" enough will consistently reproduce this bug, at least on my machine. Don't know if things like screen resolution matter or not. Panels attached to the top or bottom edge work fine regardless of thickness. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 380012] CalDAV-sync not working with Communigate
https://bugs.kde.org/show_bug.cgi?id=380012 Steffen Hartmann changed: What|Removed |Added CC||hast0...@gmail.com --- Comment #6 from Steffen Hartmann --- I have the same problem on my arch installation. Nextcloud sync doesn't work for calendar entries. Calendars names are shown however. Also contact sync runs fine. I have also some older (about Month) Neon installation where sync runs fine - after update it fails. The update also brought the new notifications "bell". -- Operating System: Arch Linux KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Kernel Version: 5.3.7-arch1-1-ARCH OS Type: 64-bit Processors: 8 × Intel® Xeon® CPU E5-1620 v3 @ 3.50GHz Memory: 15,5 GiB -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 Steffen Hartmann changed: What|Removed |Added CC||hast0...@gmail.com --- Comment #32 from Steffen Hartmann --- Also a problem for me. Since the last update I can't sync to my nextcloud server anymore. I don't understand the explanations but the behavior is just as described in this bug report. --- Operating System: Arch Linux KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Kernel Version: 5.3.7-arch1-1-ARCH OS Type: 64-bit Processors: 8 × Intel® Xeon® CPU E5-1620 v3 @ 3.50GHz Memory: 15,5 GiB -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 413451] New: Explicit OLED support for brightness control (laptops)
https://bugs.kde.org/show_bug.cgi?id=413451 Bug ID: 413451 Summary: Explicit OLED support for brightness control (laptops) Product: Powerdevil Version: 5.16.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mdedetr...@gmail.com Target Milestone: --- SUMMARY Due to OLED displays not having a backlight, the typical way of handling brightness (i.e. the brightness control) does not work, ergo changing the brightness slider doesn't actually have any effect. From doing some research it appears that the way this is handled is as an exception case i.e. detect if the display is an OLED and then instead change the gamma instead of the backlight brightness directly from the linux kernel. There is a general topic on reddit here https://www.reddit.com/r/linux/comments/cmf0vi/the_state_of_oled_brightness_on_linux/ with some useful information. System76 which sells linux laptops that have OLED's have also open sourced their solution for the displays (i.e. see https://github.com/pop-os/system76-oled, the solution uses xrandr to solve the problem, i.e. equivalent of xrandr --output eDP-1 --brightness ). It would be great if this functionality was built into KDE's brightness control, from what I know there aren't actually that many laptop OLED displays, they all appear to be created from Samsung so detecting them shouldn't be too hard. SOFTWARE/OS VERSIONS Linux Kernel Version: 5.3.7 (available in About System) KDE Plasma Version: 5.16.5 Distribution: Nixos Unstable -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413450] New: Click and drag window by contents on newly redesigned applets
https://bugs.kde.org/show_bug.cgi?id=413450 Bug ID: 413450 Summary: Click and drag window by contents on newly redesigned applets Product: systemsettings Version: 5.17.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pepk...@gmail.com Target Milestone: --- SUMMARY Newly redesigned settings applets are inconsistent when it comes to "click and drag contents" behaviour. I'm used to moving windows that way on plasma, but not it scrolls contents like it does on mobile apps. It's not how proper convergence works and it brings inconsistencies to the world of KDE, and how many phones run Plasma versus desktops. Yes, I'm salty. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 413449] New: Baloo file Extractor crash directly at KDE start
https://bugs.kde.org/show_bug.cgi?id=413449 Bug ID: 413449 Summary: Baloo file Extractor crash directly at KDE start Product: frameworks-baloo Version: 5.54.0 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: stefan.bru...@rwth-aachen.de Reporter: suprafl...@arcor.de Target Milestone: --- Application: baloo_file_extractor (5.54.0) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.9.0-4-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: - What I was doing when the application crashed: Immediatly after login baloo_file_extractor crashes when all other tasks have become ready (taskbar, net, widgets ...) Happens since upgrade from Deb 9 to Deb 10 The crash can be reproduced every time. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcc77f8b480 (LWP 2700))] Thread 3 (Thread 0x7fcc69343700 (LWP 3021)): #0 0x7fcc7b6c6819 in __GI___poll (fds=0x7fcc6401a840, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fcc7a6b8136 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fcc7a6b825c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fcc7bbda87b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fcc7bb8827b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fcc7b9d7ec6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fcc7cb00545 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fcc7b9e1aa7 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fcc7b2b8fa3 in start_thread (arg=) at pthread_create.c:486 #9 0x7fcc7b6d14cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fcc76d7e700 (LWP 2798)): #0 0x7fcc7b6c6819 in __GI___poll (fds=0x7fcc76d7dcb8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fcc7a642cf7 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fcc7a64491a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fcc77b21d79 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fcc7b9e1aa7 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fcc7b2b8fa3 in start_thread (arg=) at pthread_create.c:486 #6 0x7fcc7b6d14cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fcc77f8b480 (LWP 2700)): [KCrash Handler] #6 0x7fcc7b60f7bb in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x7fcc7b5fa535 in __GI_abort () at abort.c:79 #8 0x7fcc7b47b3b2 in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #9 0x7fcc7b471c6c in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #10 0x7fcc7b471dde in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #11 0x7fcc7b4724c5 in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #12 0x7fcc7b472aff in mdb_get () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #13 0x7fcc7cbb34cd in Baloo::IdTreeDB::get(unsigned long long) () at /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #14 0x7fcc7cbaf214 in Baloo::DocumentUrlDB::add(unsigned long long, unsigned long long, QByteArray const&) () at /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #15 0x7fcc7cbaf9e9 in Baloo::DocumentUrlDB::put(unsigned long long, QByteArray const&) () at /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #16 0x7fcc7cbcd63f in Baloo::WriteTransaction::addDocument(Baloo::Document const&) () at /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #17 0x55bb8fe4ffa2 in () #18 0x55bb8fe51d07 in () #19 0x7fcc7bbbe556 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7fcc7bbb313b in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7fcc7c5044b1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7fcc7c50b950 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7fcc7bb895a9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7fcc7bbd9c78 in QTimerInfoList::activateTimers() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7fcc7bbda4d4 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7fcc7a6b7f2e in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7fcc7a6b81c8 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7fcc7a6b825c in g_main_context_iteration () at
[plasma-pa] [Bug 413448] New: Plasmoid shows a big margin in right side
https://bugs.kde.org/show_bug.cgi?id=413448 Bug ID: 413448 Summary: Plasmoid shows a big margin in right side Product: plasma-pa Version: 5.17.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: panabu...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 123485 --> https://bugs.kde.org/attachment.cgi?id=123485=edit Audio plasmoid SUMMARY Audio plasmoid shows a big margin in the right side, which it wasn't shown with plasma 5.17.0. When the plasmoid is opened from the system tray the bug is not happening and it shows as normal. STEPS TO REPRODUCE 1. Add Plasmoid to a bar 2. Click on it OBSERVED RESULT The plasmoid shows a big right margin EXPECTED RESULT Show as usual SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE NEON (available in About System) KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION Using late dock 0.9.3 4k screen but using resolution 2560x1440 with a scaling factor of 1.4 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413446] Mouse stuck on left side
https://bugs.kde.org/show_bug.cgi?id=413446 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com --- Comment #1 from wolthera --- Could you add a tabletlog? https://docs.krita.org/en/KritaFAQ.html#what-if-your-tablet-is-not-recognized-by-krita Then we can see if there's something weird going on with how Krita gets the events, or something else is happening... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413085] Basic-5 Size preset is producing jittering, jagged stroke outlines
https://bugs.kde.org/show_bug.cgi?id=413085 --- Comment #5 from Dmitry Kazakov --- Yes, the bug happens because of the auto-precision option. It looks like the way how it is calculated has changed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413447] New: KDE plasma crash
https://bugs.kde.org/show_bug.cgi?id=413447 Bug ID: 413447 Summary: KDE plasma crash 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: roger.li...@cedalo.com 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-19-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: I was trying to connect/disconnect a VPN using the network icon in the system tray. Not entirely sure what happened, and I haven't been able to reproduce it I'm afraid. -- 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=0x55979cfd7174) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 [Current thread is 1 (Thread 0x7f01658bb880 (LWP 3433))] Thread 21 (Thread 0x7f00f3fff700 (LWP 6323)): #0 0x7f01685e02c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x55979ccab7d0) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f01685e02c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55979ccab780, cond=0x55979ccab7a8) at pthread_cond_wait.c:508 #2 0x7f01685e02c6 in __pthread_cond_wait (cond=0x55979ccab7a8, mutex=0x55979ccab780) at pthread_cond_wait.c:638 #3 0x7f016915cdef in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f016915cee1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f014a853ea0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f014a857c3e in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f014a853072 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f014a855b83 in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f0169156cc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f01685d9669 in start_thread (arg=) at pthread_create.c:479 #11 0x7f0168ddb323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f0108a84700 (LWP 6322)): #0 0x7f01685e02c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x55979ccab7d0) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f01685e02c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55979ccab780, cond=0x55979ccab7a8) at pthread_cond_wait.c:508 #2 0x7f01685e02c6 in __pthread_cond_wait (cond=0x55979ccab7a8, mutex=0x55979ccab780) at pthread_cond_wait.c:638 #3 0x7f016915cdef in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f016915cee1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f014a853ea0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f014a857c3e in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f014a853072 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f014a855b83 in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f0169156cc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f01685d9669 in start_thread (arg=) at pthread_create.c:479 #11 0x7f0168ddb323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f0109285700 (LWP 6321)): #0 0x7f01685e02c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x55979ccab7d0) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f01685e02c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55979ccab780, cond=0x55979ccab7a8) at pthread_cond_wait.c:508 #2 0x7f01685e02c6 in __pthread_cond_wait (cond=0x55979ccab7a8, mutex=0x55979ccab780) at pthread_cond_wait.c:638 #3 0x7f016915cdef in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f016915cee1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f014a853ea0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6
[krita] [Bug 413446] New: Mouse stuck on left side
https://bugs.kde.org/show_bug.cgi?id=413446 Bug ID: 413446 Summary: Mouse stuck on left side Product: krita Version: 4.2.7.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: chandlerbron...@gmail.com Target Milestone: --- Created attachment 123484 --> https://bugs.kde.org/attachment.cgi?id=123484=edit Cursor is stuck SUMMARY Whenever I try to use the cursor on Krita it is stuck to the left side of the screen I just upgraded from 4.0.2 to 4.2.7. My monitor is an Ace-Pen 1060 it is not a supported monitor but it worked fine before on 4.0.2. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 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.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 Martin Corley changed: What|Removed |Added CC||martin.cor...@ed.ac.uk -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 412048] Favourite compositions do not show up in right click context menu
https://bugs.kde.org/show_bug.cgi?id=412048 emohr changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||kdenlive/commit/107db117216 ||8f1fc1579a4b557e733d7abb554 ||14 Status|CONFIRMED |RESOLVED Version Fixed In||19.12 --- Comment #3 from emohr --- Solved with https://invent.kde.org/kde/kdenlive/commit/107db1172168f1fc1579a4b557e733d7abb55414 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385828] Status icons disappears in Plasma 5.11
https://bugs.kde.org/show_bug.cgi?id=385828 --- Comment #41 from Aleksey Kontsevich --- (In reply to Konrad Materka from comment #40) > When icons are missing, do you have xembedsniproxy running? Yes. > Can you restart it before you restart the apps with missing icons? Will try next time. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413445] New: Discover not showing PPAs and other sources
https://bugs.kde.org/show_bug.cgi?id=413445 Bug ID: 413445 Summary: Discover not showing PPAs and other sources Product: Discover Version: 5.17.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: techxga...@outlook.com CC: aleix...@kde.org Target Milestone: --- Created attachment 123483 --> https://bugs.kde.org/attachment.cgi?id=123483=edit Sources list on Discover SUMMARY Discover lists only the Snap backend on the sources page. I remember it used to list sources from PPAs before. SOFTWARE/OS VERSIONS Operating System: Kubuntu 19.10 KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-19-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15.6 GiB of RAM ADDITIONAL INFORMATION I don't have Flatpak so it's not listed there. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 413272] Neon appstream data disagrees with itself
https://bugs.kde.org/show_bug.cgi?id=413272 --- Comment #5 from Nate Graham --- *** Bug 403119 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 403119] Plasma components are counted as apps when viewing updates and installed apps
https://bugs.kde.org/show_bug.cgi?id=403119 Nate Graham changed: What|Removed |Added Resolution|FIXED |DUPLICATE --- Comment #12 from Nate Graham --- *** This bug has been marked as a duplicate of bug 413272 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413444] Opening Photoshop file causes crash
https://bugs.kde.org/show_bug.cgi?id=413444 --- Comment #3 from wolthera --- I am sorry, a mistake must have happened? I cannot see the psd? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413444] Opening Photoshop file causes crash
https://bugs.kde.org/show_bug.cgi?id=413444 --- Comment #2 from Stephen Bennington --- Hi, Here is a simple one. Thanks, Stephen -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 403119] Plasma components are counted as apps when viewing updates and installed apps
https://bugs.kde.org/show_bug.cgi?id=403119 Aleix Pol changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #11 from Aleix Pol --- Looks solved to me. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 403119] Plasma components are counted as apps when viewing updates and installed apps
https://bugs.kde.org/show_bug.cgi?id=403119 --- Comment #10 from Aleix Pol --- Created attachment 123481 --> https://bugs.kde.org/attachment.cgi?id=123481=edit addons are addons -- You are receiving this mail because: You are watching all bug changes.
[kxkb] [Bug 408855] Added language layout doesn't appear in language list
https://bugs.kde.org/show_bug.cgi?id=408855 Konstantin Kharlamov changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #9 from Konstantin Kharlamov --- After a while the problem seem to have disappeared on its own, so right now there's nothing I can do to debug it. Hopefully it was fixed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413444] Opening Photoshop file causes crash
https://bugs.kde.org/show_bug.cgi?id=413444 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com --- Comment #1 from wolthera --- Hey, thanks for adding the crashlog. Could you share the PSD file that causes the crash? That would really speed up resolving the bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413443] Changing ForegroundNormal and ForegroundLink causes systemsettings to crash when I access Display and Monitor -> Compositor
https://bugs.kde.org/show_bug.cgi?id=413443 --- Comment #1 from 15nucl...@gmail.com --- Better wording for additional information: There problem does not arise when I create a new user on the used system and then try to access Display and Monitor -> Compositor. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413443] Changing ForegroundNormal and ForegroundLink causes systemsettings to crash when I access Display and Monitor -> Compositor
https://bugs.kde.org/show_bug.cgi?id=413443 --- Comment #2 from 15nucl...@gmail.com --- The problem does* -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413444] New: Opening Photoshop file causes crash
https://bugs.kde.org/show_bug.cgi?id=413444 Bug ID: 413444 Summary: Opening Photoshop file causes crash Product: krita Version: 4.2.7 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: step...@stephenbennington.fr Target Milestone: --- Created attachment 123480 --> https://bugs.kde.org/attachment.cgi?id=123480=edit Mac OS crash report fro Krita SUMMARY I am using Krita on a Mac running Mojave 10.14.6. I am finding that opening any .psd file causes an instant crash. ( I have tested various documents even the most simple single layer file. ) I am using the latest 4.2.7 build. If I go back to a Krita version 3 the psd’s open OK. I have not had this problem until recently so I am not sure if Krita has changed or something in my system. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413443] Changing ForegroundNormal and ForegroundLink causes systemsettings to crash when I access Display and Monitor -> Compositor
https://bugs.kde.org/show_bug.cgi?id=413443 15nucl...@gmail.com changed: What|Removed |Added Summary|Systemsettings crashes when |Changing ForegroundNormal |I access Display and|and ForegroundLink causes |Monitor -> Compositor |systemsettings to crash ||when I access Display and ||Monitor -> Compositor -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413443] New: Systemsettings crashes when I access Display and Monitor -> Compositor
https://bugs.kde.org/show_bug.cgi?id=413443 Bug ID: 413443 Summary: Systemsettings crashes when I access Display and Monitor -> Compositor Product: systemsettings Version: 5.17.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: 15nucl...@gmail.com Target Milestone: --- SUMMARY In ~/.config/kdeglobals, when you change the values for ForegroundLink or ForegroundNormal in Colors:View or Colors:Window, causes systemsettings to crash when you try to access Display and Monitor -> Compositor STEPS TO REPRODUCE 1. Go to ~/.config/kdeglobals 2. Change the values for ForegroundLink or ForegroundNormal in Colors:View or Colors:Window 3. Access Display and Monitor -> Compositor OBSERVED RESULT Systemsettings crashes. EXPECTED RESULT Systemsettings doesn't crash and I can change the options for Compositor. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.3.7-arch1-1-ARCH 64-bit KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION I am using full Sweet theme suite, so the colors were set by Sweet. There is no problem when I create a new user on the used system. I have attached information given by KDE Crash Handler and console output when I start systemsettings from the console. # KDE CRASH HANDLER OUTPUT Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdeb2a6c800 (LWP 2426))] Thread 5 (Thread 0x7fde97bff700 (LWP 2436)): #0 0x7fdeb551a637 in ?? () from /usr/lib/libglib-2.0.so.0 #1 0x7fdeb551a82f in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #2 0x7fdeb551c118 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7fdeb551c241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7fdeb7cd5a1c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fdeb7c7c4ec in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7fdeb7aae385 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7fdeb6db7849 in ?? () from /usr/lib/libQt5Qml.so.5 #8 0x7fdeb7aaf5b0 in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7fdeb630b4cf in start_thread () from /usr/lib/libpthread.so.0 #10 0x7fdeb773b2d3 in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7fdea22fc700 (LWP 2435)): #0 0x7fdeb77309ef in poll () from /usr/lib/libc.so.6 #1 0x7fdeb551c170 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fdeb551c241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fdeb7cd5a1c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fdeb7c7c4ec in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fdeb7aae385 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fdeb6db7849 in ?? () from /usr/lib/libQt5Qml.so.5 #7 0x7fdeb7aaf5b0 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7fdeb630b4cf in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fdeb773b2d3 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7fdea8898700 (LWP 2433)): #0 0x7fdeb772c42c in read () from /usr/lib/libc.so.6 #1 0x7fdeb54cc9f0 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fdeb551aa31 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7fdeb551c118 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7fdeb551c241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7fdeb7cd5a1c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7fdeb7c7c4ec in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7fdeb7aae385 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x7fdeb6db7849 in ?? () from /usr/lib/libQt5Qml.so.5 #9 0x7fdeb7aaf5b0 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7fdeb630b4cf in start_thread () from /usr/lib/libpthread.so.0 #11 0x7fdeb773b2d3 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7fdeabfff700 (LWP 2429)): #0 0x7fdeb77309ef in poll () from /usr/lib/libc.so.6 #1 0x7fdeb551c170 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fdeb551c241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fdeb7cd5a1c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fdeb7c7c4ec in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fdeb7aae385 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fdeb7f0fb37 in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x7fdeb7aaf5b0 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7fdeb630b4cf in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fdeb773b2d3 in clone () from
[plasmashell] [Bug 385828] Status icons disappears in Plasma 5.11
https://bugs.kde.org/show_bug.cgi?id=385828 --- Comment #40 from Konrad Materka --- I have no clue... Probably applications are run before the StatusNotifierWatcher and are not able to register icon. In such case, usually they create legacy icon instead. When icons are missing, do you have xembedsniproxy running? Can you restart it before you restart the apps with missing icons? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413044] Minimize All Script fails to restore all windows
https://bugs.kde.org/show_bug.cgi?id=413044 Vlad Zahorodnii changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||5.17.2 Latest Commit||https://commits.kde.org/kwi ||n/a738ecce85c14b7cc4e7d1f3c ||1c01c3db1c9c0e7 Resolution|--- |FIXED --- Comment #5 from Vlad Zahorodnii --- Git commit a738ecce85c14b7cc4e7d1f3c1c01c3db1c9c0e7 by Vlad Zahorodnii. Committed on 25/10/2019 at 14:39. Pushed by vladz into branch 'Plasma/5.17'. [scripting] Provide conversion functions for AbstractClient Summary: If no conversion functions are provided for a QObject-subclass, then QScriptEngine will use QScriptEngine::newQObject() method without any special options to convert an instance of that QObject-subclass to a QScriptValue. However, it's very important that every client object is wrapped with PreferExistingWrapperObject option. We need that option because a script may set a property on a client object and that property must remain until it's deleted by the script. FIXED-IN: 5.17.2 Test Plan: New test. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: davidedmundson, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D24944 M +1-0autotests/integration/scripting/CMakeLists.txt A +170 -0autotests/integration/scripting/minimizeall_test.cpp [License: GPL (v2)] M +15 -0scripting/meta.cpp M +8-0scripting/meta.h M +12 -4scripts/CMakeLists.txt https://commits.kde.org/kwin/a738ecce85c14b7cc4e7d1f3c1c01c3db1c9c0e7 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 310881] shortcut alt-1 gets intercepted, event does not reach the active window
https://bugs.kde.org/show_bug.cgi?id=310881 --- Comment #20 from Joakim --- (In reply to Joakim from comment #19) > @Kübi **Works for me!** also after logging out and back in. > > Thanks mate! and just to clarify, this works for me on Swedish (se) layout, so not specific to Hungarian. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399499] Crash in makeInterleavedArrays
https://bugs.kde.org/show_bug.cgi?id=399499 --- Comment #46 from Mateus N. Coelho --- (In reply to David Edmundson from comment #37) > Can someone who can reproduce this run > > > QT_LOGGING_RULES="kwin_scene_opengl.debug=true;libkwinglutils.debug=true'" > kwin_x11 --replace > > from a terminal trigger a crash and then paste the whole output here please. qt.core.logging: Ignoring malformed logging rule: 'libkwinglutils.debug=true'' Module 'org.kde.kwin.decoration' does not contain a module identifier directive - it cannot be protected from external registrations. kwin_scene_opengl: Initializing OpenGL compositing OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce MX130/PCIe/SSE2 OpenGL version string: 4.6.0 NVIDIA 430.26 OpenGL shading language version string: 4.60 NVIDIA Driver: NVIDIA Driver version: 430.26 GPU class: Unknown OpenGL version: 4.6 GLSL version: 4.60 X server version: 1.20.4 Linux kernel version: 5.0 Requires strict binding:no GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no kwin_scene_opengl: 0x0: OpenGL debug output initialized kwin_scene_opengl: Initializing fences for synchronization with the X command stream kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 1 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) will use SYSTEM HEAP memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 1 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_DYNAMIC_DRAW) has been mapped WRITE_ONLY in SYSTEM HEAP memory (fast). kwin_scene_opengl: OpenGL 2 compositing successfully initialized kf5.kcoreaddons.desktopparser: Property type "Url" is not a known QVariant type. Found while parsing property definition for "X-KWin-Video-Url" in "/usr/share/kservicetypes5/kwineffect.desktop" kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 2 (bound to GL_ELEMENT_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20084: Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping. kwin_scene_opengl: 0x20092: Program/shader state performance warning: Vertex shader in program 1 is being recompiled based on GL state. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations. kwin_scene_opengl: 0x20071: Buffer detailed info: Buffer object 3 (bound to GL_ARRAY_BUFFER_ARB, usage hint is GL_STATIC_DRAW) will use VIDEO memory as the source for buffer object operations.
[kwin] [Bug 413044] Minimize All Script fails to restore all windows
https://bugs.kde.org/show_bug.cgi?id=413044 Vlad Zahorodnii changed: What|Removed |Added Flags||ReviewRequest+ URL||https://phabricator.kde.org ||/D24944 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 413442] New: kscreenlocker crashes after several hours of idle time
https://bugs.kde.org/show_bug.cgi?id=413442 Bug ID: 413442 Summary: kscreenlocker crashes after several hours of idle time Product: kscreenlocker Version: unspecified Platform: Slackware Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: greeter Assignee: plasma-b...@kde.org Reporter: ste...@gmail.com CC: bhus...@gmail.com Target Milestone: --- Created attachment 123479 --> https://bugs.kde.org/attachment.cgi?id=123479=edit Console output from manually starting kscreenlocker_greet with --testing option SUMMARY kscreenlocker crashes after several hours of idle time STEPS TO REPRODUCE 1. Screen Locking configured to start automatically after 20 minutes 2. Unlocking without password setting: 300 seconds 3. After waking from sleep: not set 4. Appearance settings follows in steps 5-10 below 5. Media controls: set Show 6. Wallpaper type: Slideshow 7. Positioning: Scaled and Cropped 8. Order: Random 9. Change every: 0 hours 2 minutes 0 seconds 10. All 22 stock wallpapers are selected OBSERVED RESULT After several hours of idle (~ 6 to 8 hours) the screen locker crashes with below message. “The screen locker is broken and unlocking is not possible anymore. In order to unlock switch to a virtual terminal (e.g. Ctrl+Alt+F2), log in as root and execute the command: # ck-unlock-session ” EXPECTED RESULT No crash. Continued operation. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Slackware/14.2 -current (available in About System) KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION package: kscreenlocker-5.17.0-x86_64-1alien (behavior not observed in previous package kscreenlocker-5.16.5-x86_64-1alien and can be remedied by installing it) This behavior appears related to bugs 405219 and 371175. When disabling the automatic start and manually starting kscreenlocker with: "/usr/lib64/kscreenlocker_greet --testing" a segmentation fault will occur. The console output which precedes the seg fault is added as an attachment. Some relevant system log output in /var/log/messages: Oct 24 06:40:50 kiai dbus-daemon[1777]: [session uid=1000 pid=1775] Successfully activated service 'org.kde.runners.baloo' Oct 24 07:00:01 kiai -- MARK -- Oct 24 07:20:01 kiai -- MARK -- Oct 24 07:40:01 kiai -- MARK -- Oct 24 08:00:01 kiai -- MARK -- Oct 24 08:20:01 kiai -- MARK -- Oct 24 08:40:01 kiai -- MARK -- Oct 24 09:00:01 kiai -- MARK -- Oct 24 09:20:01 kiai -- MARK -- Oct 24 09:40:01 kiai -- MARK -- Oct 24 10:00:01 kiai -- MARK -- Oct 24 10:20:01 kiai -- MARK -- Oct 24 10:40:01 kiai -- MARK -- Oct 24 11:00:01 kiai -- MARK -- Oct 24 11:20:01 kiai -- MARK -- Oct 24 11:40:01 kiai -- MARK -- Oct 24 12:00:01 kiai -- MARK -- Oct 24 12:20:01 kiai -- MARK -- Oct 24 12:40:01 kiai -- MARK -- Oct 24 13:00:01 kiai -- MARK -- Oct 24 13:09:02 kiai kernel: [191359.983592] kscreenlocker_g[25671]: segfault at 7f7e20008eb8 ip 7f7b52abce00 sp 7fffa506cfb0 error 4 in libQt5Core.so.5.13.1[7f7b528ed000+2d3000] -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 403120] Plasma updates are displayed very messily
https://bugs.kde.org/show_bug.cgi?id=403120 --- Comment #4 from Nate Graham --- *** This bug has been marked as a duplicate of bug 413272 *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 413272] Neon appstream data disagrees with itself
https://bugs.kde.org/show_bug.cgi?id=413272 --- Comment #4 from Nate Graham --- *** Bug 404341 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 404341] collapse duplicative update information
https://bugs.kde.org/show_bug.cgi?id=404341 --- Comment #3 from Nate Graham --- *** This bug has been marked as a duplicate of bug 413272 *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 413272] Neon appstream data disagrees with itself
https://bugs.kde.org/show_bug.cgi?id=413272 --- Comment #3 from Nate Graham --- *** Bug 403120 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 403118] Installed page is cluttered and dangerous
https://bugs.kde.org/show_bug.cgi?id=403118 --- Comment #6 from Nate Graham --- *** This bug has been marked as a duplicate of bug 413272 *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 413272] Neon appstream data disagrees with itself
https://bugs.kde.org/show_bug.cgi?id=413272 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #2 from Nate Graham --- *** Bug 403118 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413432] Folder View generates unsharp landscape thumbnails (whereas portrait/square thumbnails look fine).
https://bugs.kde.org/show_bug.cgi?id=413432 David Edmundson changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413432] Folder View generates unsharp landscape thumbnails (whereas portrait/square thumbnails look fine).
https://bugs.kde.org/show_bug.cgi?id=413432 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Flags|Usability+ |Usability- -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 413441] New: QtQuick dialog: when installing an item, show the "Installing" text on the item itself, not using a passivenotification
https://bugs.kde.org/show_bug.cgi?id=413441 Bug ID: 413441 Summary: QtQuick dialog: when installing an item, show the "Installing" text on the item itself, not using a passivenotification Product: frameworks-knewstuff Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jpwhit...@kde.org Reporter: n...@kde.org CC: kdelibs-b...@kde.org Target Milestone: --- the item being installed already becomes desaturated and shows a spinner. So that's the logical place to show the "Installing..." text. Right now, since it's a passiveNotification, it times out quickly leaving you wondering what's going on if the installation takes more than 7 seconds. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 413440] New: QtQuick dialog: header label on item detail page probably needs Layout.fillWidth: true set on it
https://bugs.kde.org/show_bug.cgi?id=413440 Bug ID: 413440 Summary: QtQuick dialog: header label on item detail page probably needs Layout.fillWidth: true set on it Product: frameworks-knewstuff Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jpwhit...@kde.org Reporter: n...@kde.org CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 123478 --> https://bugs.kde.org/attachment.cgi?id=123478=edit Elided text ...Because right now it elides, and the Install button isn't pushed over all the way to the right like it should be. See attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 413439] New: QtQuick dialog: show loading status messages in the view with a spinner or progress indicator, not using PassiveNotifications
https://bugs.kde.org/show_bug.cgi?id=413439 Bug ID: 413439 Summary: QtQuick dialog: show loading status messages in the view with a spinner or progress indicator, not using PassiveNotifications Product: frameworks-knewstuff Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jpwhit...@kde.org Reporter: n...@kde.org CC: kdelibs-b...@kde.org Target Milestone: --- When the dialog first loads, it sends several passiveNotifications in rapid succession. The loading UX would be better if it was more like how Discover does it IMO: with the status messages shown under a spinner or progress bar in the empty view itself, disappearing when the view becomes populated. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 413437] QtQuick dialog: Don't show "Pick your installation option" sheet when there's only one option
https://bugs.kde.org/show_bug.cgi?id=413437 Nate Graham changed: What|Removed |Added Summary|Don't show "Pick your |QtQuick dialog: Don't show |installation option" sheet |"Pick your installation |when there's only one |option" sheet when there's |option |only one option -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 413438] New: Buttons in "Create a new Vault" window have pixelated icons if fractional display scaling is used
https://bugs.kde.org/show_bug.cgi?id=413438 Bug ID: 413438 Summary: Buttons in "Create a new Vault" window have pixelated icons if fractional display scaling is used Product: Plasma Vault Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 123477 --> https://bugs.kde.org/attachment.cgi?id=123477=edit screenshot STEPS TO REPRODUCE 1. set display scale factor to 1.2 in system settings > display and monitor > display configuration 2. restart plasma session 3. click on "Vaults" icon in system tray, click on "Create a new Vault..." button OBSERVED RESULT As we can see in the attached screenshot, the buttons on bottom have pixelated icons. EXPECTED RESULT crisp icons SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.14.0 beta2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 413437] New: Don't show "Pick your installation option" sheet when there's only one option
https://bugs.kde.org/show_bug.cgi?id=413437 Bug ID: 413437 Summary: Don't show "Pick your installation option" sheet when there's only one option Product: frameworks-knewstuff Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jpwhit...@kde.org Reporter: n...@kde.org CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 123476 --> https://bugs.kde.org/attachment.cgi?id=123476=edit There's only one option here It's unnecessary -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 413436] New: QtQuick dialog: "i" icon in corner looks unnecessary
https://bugs.kde.org/show_bug.cgi?id=413436 Bug ID: 413436 Summary: QtQuick dialog: "i" icon in corner looks unnecessary Product: frameworks-knewstuff Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jpwhit...@kde.org Reporter: n...@kde.org CC: kdelibs-b...@kde.org Target Milestone: --- Delegates have an "info" icon in the top-right corner. I'm not sure what this communicates, and it's not clickable. Would recommend removing it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 413435] New: QtQuick dialog: Use finger button when hovering over delegates that respond to single-click
https://bugs.kde.org/show_bug.cgi?id=413435 Bug ID: 413435 Summary: QtQuick dialog: Use finger button when hovering over delegates that respond to single-click Product: frameworks-knewstuff Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jpwhit...@kde.org Reporter: n...@kde.org CC: kdelibs-b...@kde.org Target Milestone: --- When you single-click on a delegate, it takes you to the page for that item. Because the delegates look selectable (they have a selection highlight when hovered over), you expect that a single-click will select the item rather than go into it. To make the enter-on-click behavior less unexpected, the cursor should use the finger pointer when hovering over any of the single-clickable delegates. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 413434] New: QtQuick dialog: Close button is not really needed, and the row it sits in could be removed
https://bugs.kde.org/show_bug.cgi?id=413434 Bug ID: 413434 Summary: QtQuick dialog: Close button is not really needed, and the row it sits in could be removed Product: frameworks-knewstuff Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jpwhit...@kde.org Reporter: n...@kde.org CC: kdelibs-b...@kde.org Target Milestone: --- The window's titlebar will have a close button. So there's not really a need for there to be a close button at the bottom of the window with a whole row of its own. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 413433] New: QtQuick dialog: header is empty
https://bugs.kde.org/show_bug.cgi?id=413433 Bug ID: 413433 Summary: QtQuick dialog: header is empty Product: frameworks-knewstuff Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jpwhit...@kde.org Reporter: n...@kde.org CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 123475 --> https://bugs.kde.org/attachment.cgi?id=123475=edit Empty header A picture says a thousand words. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413432] Folder View generates unsharp landscape thumbnails (whereas portrait/square thumbnails look fine).
https://bugs.kde.org/show_bug.cgi?id=413432 --- Comment #2 from Gerhard Dittes --- Regarding the attachment, the images with the motorcycles provide obviously better examples than those with the beer (my bad ;-) ). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413432] Folder View generates unsharp landscape thumbnails (whereas portrait/square thumbnails look fine).
https://bugs.kde.org/show_bug.cgi?id=413432 Gerhard Dittes changed: What|Removed |Added Flags||Usability+, VisualDesign+ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413432] Folder View generates unsharp landscape thumbnails (whereas portrait/square thumbnails look fine).
https://bugs.kde.org/show_bug.cgi?id=413432 --- Comment #1 from Gerhard Dittes --- Created attachment 123474 --> https://bugs.kde.org/attachment.cgi?id=123474=edit Screenshot showing the quality differences/decrease between portrait and landscape images in "Folder View" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413432] New: Folder View generates unsharp landscape thumbnails (whereas portrait/square thumbnails look fine).
https://bugs.kde.org/show_bug.cgi?id=413432 Bug ID: 413432 Summary: Folder View generates unsharp landscape thumbnails (whereas portrait/square thumbnails look fine). Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: g-...@web.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Folder View (/Desktop) generates poor image previews -- but only for landscape images. I.e., for the case that the with of the image is bigger than its height, the corresponding thumbnail gets exremely "unsharp". Square or landscape images look satisfactorily, though. Please see attached screenshot (also showing a comparison with Dolphin). STEPS TO REPRODUCE 1. Put an image having landscape size on your Desktop (e.g. a common photo, ratio 4:3) 2. Put another image with portrait properties on your Desktop or make a copy of the first one and cut it to portrait (e.g. ratio 2:3) OBSERVED RESULT First image looks unsharp. Second image looks fine. EXPECTED RESULT Both images look sharp. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian GNU/Linux & KDE Neon Unstable Edition KDE Plasma Version: 1.14.5 & 1.17.80 KDE Frameworks Version: 5.54.0 & 5.62.0 Qt Version: 5.11.3 & 5.13.1 ADDITIONAL INFORMATION Related (resolved) bugs: https://bugs.kde.org/show_bug.cgi?id=355592 https://bugs.kde.org/show_bug.cgi?id=376848 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413431] Clicking on notification's close button triggers the default action in addition to closing it
https://bugs.kde.org/show_bug.cgi?id=413431 Kai Uwe Broulik changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Kai Uwe Broulik --- Yeah, noticed that, too. I bet has to do with some of the phone shufflings around. NotificationItem used to be a MouseArea iirc. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413431] New: Clicking on notification's close button triggers the default action in addition to closing it
https://bugs.kde.org/show_bug.cgi?id=413431 Bug ID: 413431 Summary: Clicking on notification's close button triggers the default action in addition to closing it Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: n...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 All KDE stuff built from source on top of openSUSE Tumbleweed. When I click on the close button for notification sent by riot's web app, it closes the notification and then immediately switches to the tab containing the web app. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 413430] New: Unlock computer by simply unlocking the phone
https://bugs.kde.org/show_bug.cgi?id=413430 Bug ID: 413430 Summary: Unlock computer by simply unlocking the phone Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: raitarohik...@protonmail.com Target Milestone: --- SUMMARY Right now I have a command under kde connect (loginctl unlock-session) that allows to unlock the laptop. Pretty straight forward stuff. Except I kinda wish to have an option where if I unlock my phone kde connect automatically unlocks the linux session as well, without me having to open kconn, go to actions and find where unlock command is. Seems that chrome-os actually let's you do that now. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 413052] When an album comprises multiple discs, the secondary level of sorting should be by track number, not alphabetical
https://bugs.kde.org/show_bug.cgi?id=413052 Nate Graham changed: What|Removed |Added Resolution|FIXED |NOT A BUG Latest Commit|https://invent.kde.org/kde/ | |elisa/commit/fe840744eeb2dc | |5266310d86e0660aaa783a7a74 | -- You are receiving this mail because: You are watching all bug changes.
