[digikam] [Bug 404384] Show number of entries in group
https://bugs.kde.org/show_bug.cgi?id=404384 --- Comment #12 from Maik Qualmann --- It's the SQL query from a search album. But I just do not know where it would be possible if so many individual image ids could be passed. The face database is also broken. In a search, however, the number of items in the groub can not be correct, as some of the images in the group do not meet the criteria, I think we have a bug report too. Please test it with the normal album view. Maik -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 405059] Printer settings are not saved
https://bugs.kde.org/show_bug.cgi?id=405059 Ralf Habacker changed: What|Removed |Added Version Fixed In|4.8.4 |4.8.4, 5.0.4 -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 364701] Can't change language in Help menu
https://bugs.kde.org/show_bug.cgi?id=364701 Simon Depiets changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Simon Depiets --- You can now use a stable release, they include the translations https://binary-factory.kde.org/job/Lokalize_Release_win32/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405877] Rules to ignore global shortcuts ignored when mouse pointer grabbed.
https://bugs.kde.org/show_bug.cgi?id=405877 --- Comment #1 from Martin Flöser --- Please verify that your rule matches the window. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404384] Show number of entries in group
https://bugs.kde.org/show_bug.cgi?id=404384 --- Comment #11 from caulier.gil...@gmail.com --- yes, there is a way to filer debug output by categories using a shell variable, but as you said, it's to hack... this output is abnormal : digikam.database: " ( (Images.id IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?, digikam.geoiface: digikam.general: Cancel Main Thread digikam.database: Search query: "SELECT DISTINCT Images.id, Images.name, Images.album, Albums.albumRoot,ImageInformation.rating, Images.category, ImageInformation.format, ImageInformation.creationDate, Images.modificationDate, Images.fileSize,ImageInformation.width, ImageInformation.height,ImagePositions.latitudeNumber, ImagePositions.longitudeNumber FROM ImagesLEFT JOIN ImageInformation ON Images.id=ImageInformation.imageidLEFT JOIN ImageMetadataON Images.id=ImageMetadata.imageidLEFT JOIN VideoMetadataON Images.id=VideoM
[kaffeine] [Bug 403874] Kaffeine scanlist channels lost
https://bugs.kde.org/show_bug.cgi?id=403874 --- Comment #13 from compi-kil...@gmx.de --- ok, following works: do not start TV, or quitting it by maybe select "play audio CD" without having any CD inside. Then select "channels" from upper menue bar and scan there. It just can not read, scan, add or delete channels, when TV is running (streaming). I did not test /look at following yet: - Is it possible to select TV from side bar without having one channel automatically started - if no channel running eventhough being in TV mode, is it possible to scan again from channel selector at lower left corner (channel symbol under channel list) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405246] App discovery crash after installing .exe program (yandex-disk)
https://bugs.kde.org/show_bug.cgi?id=405246 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 403259] ramdisk's are not included in memory usage
https://bugs.kde.org/show_bug.cgi?id=403259 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 262333] Extend systemmonitor with a downloadable view of CUDA stress
https://bugs.kde.org/show_bug.cgi?id=262333 --- Comment #7 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405291] malfunction.brush shapes
https://bugs.kde.org/show_bug.cgi?id=405291 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405787] Cursor not working anymore after moving the cursor off the canvas and back
https://bugs.kde.org/show_bug.cgi?id=405787 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #8 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 377666] Memory history doesn't match actual RAM usage
https://bugs.kde.org/show_bug.cgi?id=377666 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 334258] CPU History and Network History are blank
https://bugs.kde.org/show_bug.cgi?id=334258 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 397304] CPU load doesn't match values from top
https://bugs.kde.org/show_bug.cgi?id=397304 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 383243] Empty CPU load graph with AMD Ryzen 5 1600
https://bugs.kde.org/show_bug.cgi?id=383243 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401808] kde fails to actualize a desktop at startup
https://bugs.kde.org/show_bug.cgi?id=401808 George R. Goffe changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|NOT A BUG |--- --- Comment #7 from George R. Goffe --- Hi, This problem still seems to exist, even with an OUT OF THE BOX FC31 system AND no other modifications of any kind. Is someone working this problem? If not, what do I need to do to get some action on this from the KDE folks? Please help, George... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380495] Freezes during login process
https://bugs.kde.org/show_bug.cgi?id=380495 --- Comment #11 from George R. Goffe --- This problem still seems to exist. Is anyone working this bug? George... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405751] plasma shell crash when I clicked on [Leave] menu
https://bugs.kde.org/show_bug.cgi?id=405751 jacky lau changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |MOVED --- Comment #2 from jacky lau --- After reading and tracing the code of plasmashell and sddm, I found this problem is cause by sddm failed to register "/org/freedesktop/DisplayManager/Seat-1" to dbus by using QDBusConnection::registerObject(). I change my seat name from seat-1 to seat_1, plasmashell wouldn't crash any more. This is sddm's bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401861] Menu search doesn't return any results if cursor happens to be positioned below the tab bar
https://bugs.kde.org/show_bug.cgi?id=401861 g...@protonmail.com changed: What|Removed |Added CC||g...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391322] Super (Meta) Key stops working
https://bugs.kde.org/show_bug.cgi?id=391322 g...@protonmail.com changed: What|Removed |Added CC||g...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405877] New: Rules to ignore global shortcuts ignored when mouse pointer grabbed.
https://bugs.kde.org/show_bug.cgi?id=405877 Bug ID: 405877 Summary: Rules to ignore global shortcuts ignored when mouse pointer grabbed. Product: kwin Version: 5.14.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: lo...@kde.bt.alestan.publicvm.com Target Milestone: --- SUMMARY Window rules for ignoring global shortcuts do not function when a window grabs the mouse pointer. This happens both with sdl2 windows and gtk3 windows, running under wayland or Xwayland (Xorg not tested). This happens both with qemu and dosbox. STEPS TO REPRODUCE 1. Create a rule to ignore global shortcuts for qemu 2. Launch qemu with the sdl or gtk backend 3. Click in the qemu window to grab the mouse pointer 4. Hit ctr-alt-delete or other global shortcut: shortcut is not passed through to qemu 5. Set qemu as the active window but don't grab the mouse (alt-tab to select qemu) 6. Hit ctrl-alt-delete or other global shortcut: shortcut is passed through to qemu OBSERVED RESULT Global keyboard shortcuts are not ignored and are not passed to the window with the locked pointer. For example, ctrl-alt-delete brings up the logout/shutdown menu, F12 opens the dropdown terminal emulator yakuake. EXPECTED RESULT Global keyboard shortcuts should be passed to the window with the locked mouse pointer. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 4.19.27-gentoo (available in About System) KDE Plasma Version: 5.14.5.1 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3-r2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 405876] New: Gwenview shows unnecessary notification when I open a file located in a Samba share
https://bugs.kde.org/show_bug.cgi?id=405876 Bug ID: 405876 Summary: Gwenview shows unnecessary notification when I open a file located in a Samba share Product: gwenview Version: 18.12.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 119043 --> https://bugs.kde.org/attachment.cgi?id=119043&action=edit screenshot SUMMARY Sometimes Gwenview shows the notification that we can see in my screenshot. I don't understand which criteria Gwenview uses to show or not this notification, it appears randomly when I open a file located in a Samba share. STEPS TO REPRODUCE 1. use Gwenview to open, via Dolphin, a file located in a Samba share OBSERVED RESULT sometimes a notification appears. See the attached screenshot. EXPECTED RESULT notification never appears SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 405875] New: Authentication window to authorize change in process priority reopens after being canceled
https://bugs.kde.org/show_bug.cgi?id=405875 Bug ID: 405875 Summary: Authentication window to authorize change in process priority reopens after being canceled Product: ksysguard Version: 5.15.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 119042 --> https://bugs.kde.org/attachment.cgi?id=119042&action=edit screenshot STEPS TO REPRODUCE 1. open ksysguard 2. in "Process table" tab, select any process and press F8 to change its priority 3. set the slider related to cpu scheduler as "High priority" and click "Ok" button (password dialog shows up) 4. cancel the password dialog OBSERVED RESULT password dialog shows up again along an error message. See the attached screenshot please. EXPECTED RESULT password dialog is canceled, it does not reopen and no error message appears SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Also reproducible on neon dev unstable. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 362857] Background transparency not applied when restoring session
https://bugs.kde.org/show_bug.cgi?id=362857 --- Comment #20 from Joe --- @neilsi...@gmail.com I think that is expected behavior, as full screen games generally flip the compositor/kwin off, thus no transparency. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405874] New: Kontact settings crashed
https://bugs.kde.org/show_bug.cgi?id=405874 Bug ID: 405874 Summary: Kontact settings crashed Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: g...@kani.hu Target Milestone: --- Application: kontact (5.10.1) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.18.0-15-lowlatency x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: After updates, I can't open Kontact settings dialog at all. I'm using Neon (bionic). The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4e8d211bc0 (LWP 23107))] Thread 35 (Thread 0x7f4d249d6700 (LWP 23222)): #0 0x7f4e835b4649 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f4e8356e4d0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4e8356e6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4e8a69415b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f4d2c0874b0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f4e8a63564a in QEventLoop::exec(QFlags) (this=this@entry=0x7f4d249d59e0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f4e8a45d41a in QThread::exec() (this=) at thread/qthread.cpp:531 #6 0x7f4e8a45ebc2 in QThreadPrivate::start(void*) (arg=0x556b803e87d0) at thread/qthread_unix.cpp:361 #7 0x7f4e8543b6db in start_thread (arg=0x7f4d249d6700) at pthread_create.c:463 #8 0x7f4e89b4688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 34 (Thread 0x7f4d25ffb700 (LWP 23213)): #0 0x7f4e85441ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f4d25ffa710, expected=0, futex_word=0x7f4d25ffa8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f4e85441ed9 in __pthread_cond_wait_common (abstime=0x7f4d25ffa7b0, mutex=0x7f4d25ffa8a8, cond=0x7f4d25ffa8d0) at pthread_cond_wait.c:533 #2 0x7f4e85441ed9 in __pthread_cond_timedwait (cond=0x7f4d25ffa8d0, mutex=0x7f4d25ffa8a8, abstime=0x7f4d25ffa7b0) at pthread_cond_wait.c:667 #3 0x7f4e7aaa0177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f4e7aaa0ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f4e7aaa0bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f4e7aa5e851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f4e7aa616b6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f4e7aa61974 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f4e7aaa2cd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f4e8543b6db in start_thread (arg=0x7f4d25ffb700) at pthread_create.c:463 #11 0x7f4e89b4688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 33 (Thread 0x7f4d267fc700 (LWP 23212)): #0 0x7f4e85441ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f4d267fb710, expected=0, futex_word=0x7f4d267fb8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f4e85441ed9 in __pthread_cond_wait_common (abstime=0x7f4d267fb7b0, mutex=0x7f4d267fb8a8, cond=0x7f4d267fb8d0) at pthread_cond_wait.c:533 #2 0x7f4e85441ed9 in __pthread_cond_timedwait (cond=0x7f4d267fb8d0, mutex=0x7f4d267fb8a8, abstime=0x7f4d267fb7b0) at pthread_cond_wait.c:667 #3 0x7f4e7aaa0177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f4e7aaa0ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f4e7aaa0bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f4e7aa5e851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f4e7aa616b6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f4e7aa61974 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f4e7aaa2cd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f4e8543b6db in start_thread (arg=0x7f4d267fc700) at pthread_create.c:463 #11 0x7f4e89b4688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 32 (Thread 0x7f4d26ffd700 (LWP 23211)): #0 0x7f4e85441ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f4d26ffc710, expected=0, futex_word=0x7f4d26ffc8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f4e85441ed9 in __pthread_cond_wait_common (abstime=0x7f4d26ffc7b0, mutex=0x7f4d26ffc8a8, cond=0x7f4d26ffc8d0) at pthread_cond_wait.c:533 #2 0x7f4e85441ed9 in __pthread_cond_timedwait (cond=0x7
[Discover] [Bug 393596] Discover crash
https://bugs.kde.org/show_bug.cgi?id=393596 Michael Mikowski changed: What|Removed |Added CC||z_mikow...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kgeography] [Bug 405419] Tajikistan Map Update
https://bugs.kde.org/show_bug.cgi?id=405419 --- Comment #8 from Albert Astals Cid --- What do you mean there are over 60 images to edit? It should just be one map, no? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403366] No apply/discard prompt shows up when I leave sddm_kcm after uncheck "Auto-login" without apply the change
https://bugs.kde.org/show_bug.cgi?id=403366 Albert Astals Cid changed: What|Removed |Added Latest Commit|https://commits.kde.org/sdd |https://commits.kde.org/sdd |m-kcm/ed3decc06e387217bc131 |m-kcm/0c76098e80c8ee61c7da9 |8597ba1e97183d3b9b3 |d85313461fc8a040651 --- Comment #3 from Albert Astals Cid --- Git commit 0c76098e80c8ee61c7da9d85313461fc8a040651 by Albert Astals Cid, on behalf of Laurent Montel. Committed on 25/03/2019 at 22:58. Pushed by aacid into branch 'Plasma/5.15'. Fixed issue causing changed signal to be called with false argument Summary: AdvanceConfig::changed signal is called with changed=false arguement when QGroupBox::clicked is called with checked=false causing the Apply button to remain disabled. Test Plan: 1. Open SDDM settings 2. Enable auto-login, save and close. 3. Open SDDM settings again 4. Uncheck auto-login Apply button should now be enabled. Same steps for Relogin after quit checkbox. Reviewers: mlaurent Reviewed By: mlaurent Subscribers: mlaurent, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D19959 (cherry picked from commit ed3decc06e387217bc1318597ba1e97183d3b9b3) M +4-2src/advanceconfig.cpp https://commits.kde.org/sddm-kcm/0c76098e80c8ee61c7da9d85313461fc8a040651 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405831] Crash with audio clips in Kdenlive Win 19.04beta-git2019
https://bugs.kde.org/show_bug.cgi?id=405831 --- Comment #6 from Justin Irwin --- Both still crash on my Windows 10. The crash also occurs on another Win10 PC I have so it is not just the one machine. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 405873] New: "Fold first line" stopped work for files opened in session
https://bugs.kde.org/show_bug.cgi?id=405873 Bug ID: 405873 Summary: "Fold first line" stopped work for files opened in session Product: kdevelop Version: 5.3.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: All editors Assignee: kdevelop-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- SUMMARY When I run KDevelop with several files in session and every has comment containing couple rows as first line then this first line is not folded. When I open new file looking the same as I above described then first line is folded correctly. STEPS TO REPRODUCE 1. set option: Configure KDevelop -> Editor -> Appearance -> Fold first line 2. open any session containing several files where each of them has comment containing couple rows as first line 3. go on top to any of loaded file OBSERVED RESULT first line is not folded EXPECTED RESULT first line should be not folded SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Issue looks like regression. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 197009] Enhancement: User-selected tab titles
https://bugs.kde.org/show_bug.cgi?id=197009 Mike Krutov changed: What|Removed |Added Status|CONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 197009] Enhancement: User-selected tab titles
https://bugs.kde.org/show_bug.cgi?id=197009 Mike Krutov changed: What|Removed |Added CC||mikhail.kru...@seznam.cz --- Comment #2 from Mike Krutov --- I've added a small patch that implements this feature request: https://phabricator.kde.org/D20052 -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 405850] connect-3arg-lambda should not warn in main()
https://bugs.kde.org/show_bug.cgi?id=405850 Sergio Martins changed: What|Removed |Added Assignee|unassigned-b...@kde.org |smart...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404384] Show number of entries in group
https://bugs.kde.org/show_bug.cgi?id=404384 --- Comment #10 from Christian Gruber --- Created attachment 119040 --> https://bugs.kde.org/attachment.cgi?id=119040&action=edit Digikam messages to the console while grouping -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404384] Show number of entries in group
https://bugs.kde.org/show_bug.cgi?id=404384 --- Comment #9 from Christian Gruber --- I combined my 001.gif,... files to a group and attached the debug messages. By the way, Digikam is VERY verbose. This is good for debugging, but bad for everyday usage. Can this somehow be reduced, preferably to 0? -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 381291] There are two actions (Find in Files..., Normal Fraction - \frac{}{}) that want to use the same shortcut (Alt+Shift+F). This is most probably a bug. Please report it in bugs.kde.or
https://bugs.kde.org/show_bug.cgi?id=381291 --- Comment #6 from signupem...@posteo.uk --- Created attachment 119039 --> https://bugs.kde.org/attachment.cgi?id=119039&action=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405872] New: Certain library files installed to the wrong directory.
https://bugs.kde.org/show_bug.cgi?id=405872 Bug ID: 405872 Summary: Certain library files installed to the wrong directory. Product: kdeconnect Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: halo117nac...@gmail.com Target Milestone: --- This is a build issue. Here's my problem. I wanted a newer version of KDEConnect that what's available for my distro, so I'm trying to build KDEConnect from source. However, when I install it, several important library files get installed to /usr/lib/i386-linux-gnu. This is weird, since my system is 64 bit, thus the files should be installed to /usr/lib/x86_64-linux-gnu. AFAIK, nothing gets installed to /usr/lib/x86_64-linux-gnu. IDK if I'm doing something wrong, or if there's a bug in cmake, or what. I got KDEConnect from this git repository: https://invent.kde.org/kde/kdeconnect-kde.git These are the commands I ran: mkdir build cd build cmake -DCMAKE_INSTALL_PREFIX=/usr .. make sudo make install KDEConnect works, and I'm able to pair my laptop to my phone, but I can't do anything beyond that: I can't browse the device (via sftp), I can't read/send SMS messages... heck, I can't even see how much battery my phone has. Creating a symlink in "/usr/lib/x86_64/qt5/plugins/kdeconnect", and having said link point to "/usr/lib/i386-linux-gnu/qt5/plugins/kdeconnect" seems to fix the issue (kdeconnectd will need to be restarted), but I find it odd that I even need to do that. I'm running Ubuntu 18.04. I don't know much about make or cmake, so IDK what I can do on my end. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 381291] There are two actions (Find in Files..., Normal Fraction - \frac{}{}) that want to use the same shortcut (Alt+Shift+F). This is most probably a bug. Please report it in bugs.kde.or
https://bugs.kde.org/show_bug.cgi?id=381291 signupem...@posteo.uk changed: What|Removed |Added CC||signupem...@posteo.uk --- Comment #5 from signupem...@posteo.uk --- I get an error along these lines - see attachment - on KsystemLog 17.12.3. The error occured when I disabled the coloured log lines option. Hopefully the problem has been fixed already. If it has, and you could help me get a more recent version of the program, I'd be grateful; it seems the one in my distro's repositories is ancient. Linux Mint 19.1 KsystemLog 17.12.3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 277620] Face recognition should propose the tagged name as default in the face identification page
https://bugs.kde.org/show_bug.cgi?id=277620 --- Comment #7 from IWBR --- I also think that, personally, this is not a very good idea. Suggesting a person based on a tag may induce some wrong "tagging", especially for pictures of people you barely know (as in old family pictures of relatives), which may cause some sort of "confirmation bias", in the case the original tag is also wrong. I think suggestions should be based on face recognition alone. I prefer to have some unknown/unconfirmed people in a picture than false positives. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 395723] The median line width of icons view mode is the same as the small width
https://bugs.kde.org/show_bug.cgi?id=395723 --- Comment #2 from Alan Dacey Sr. --- Update: I see this happening only in certain folders. I renamed then re-created a folder I use every day and the spacing issue disappeared. I didn't see any difference in the properties of either folder. Will save old folder is needed. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401828] none/tests/ppc64/test_isa_2_06_part1 failure on ppc64le (fcfids and fcfidus)
https://bugs.kde.org/show_bug.cgi?id=401828 --- Comment #5 from Will Schmidt --- Created attachment 119038 --> https://bugs.kde.org/attachment.cgi?id=119038&action=edit tentative / potential patch -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401828] none/tests/ppc64/test_isa_2_06_part1 failure on ppc64le (fcfids and fcfidus)
https://bugs.kde.org/show_bug.cgi?id=401828 --- Comment #4 from Will Schmidt --- So, it looks like the correct value is in the register, we are losing it somewhere in the cast from float to (raw/hex) on the call to printf. I'm undecided whether this is simply an improper cast, or if there is something additionally wrong here. tentative patch (attached) while I think on this a bit more... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405825] Feature request: "Video date" in XMP Metadata Editor
https://bugs.kde.org/show_bug.cgi?id=405825 --- Comment #2 from IWBR --- That was quick. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405856] Misplaced selection
https://bugs.kde.org/show_bug.cgi?id=405856 --- Comment #9 from Christian Gruber --- Created attachment 119037 --> https://bugs.kde.org/attachment.cgi?id=119037&action=edit Screencast showing the bug -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405856] Misplaced selection
https://bugs.kde.org/show_bug.cgi?id=405856 --- Comment #8 from Christian Gruber --- I have added a screencast as an attachment. First I created loads of GIF files, starting with 001.gif. In Digikam 5.6.0 I grouped then some random files: first I selected a bunch with shift-right, then I pulled the first one to the second one with the mouse and selected to group them. I pressed then the right-arrow key. Instead of jumping to the next entry, it jumped to the first one (001.gif). By the way, the command I used the big amount of pictures was: for i in $(seq -w 1 999); do convert -density 90 -pointsize 72 label:$i $i.gif; done -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389549] "Clear all faces on this image" Does Not Remove All People Tags
https://bugs.kde.org/show_bug.cgi?id=389549 Maik Qualmann changed: What|Removed |Added Latest Commit||https://commits.kde.org/dig ||ikam/38641a8cf4693399f32a89 ||c49afd1fd26a8b9538 Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||6.1.0 --- Comment #13 from Maik Qualmann --- Git commit 38641a8cf4693399f32a89c49afd1fd26a8b9538 by Maik Qualmann. Committed on 25/03/2019 at 21:21. Pushed by mqualmann into branch 'master'. remove all face tags with a write operation If the re-scan option was enabled, the tags were added again. FIXED-IN: 6.1.0 M +2-1NEWS M +7-6core/utilities/facemanagement/facegroup.cpp https://commits.kde.org/digikam/38641a8cf4693399f32a89c49afd1fd26a8b9538 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405871] New: Baloo crashes after restart
https://bugs.kde.org/show_bug.cgi?id=405871 Bug ID: 405871 Summary: Baloo crashes after restart Product: frameworks-baloo Version: 5.56.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: 842m...@gmail.com Target Milestone: --- Application: baloo_file_extractor (5.56.0) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: I'm on neon. This error message appears right after restart. 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 0x7ffa25653c80 (LWP 3533))] Thread 3 (Thread 0x7ff9ff0c8700 (LWP 3541)): #0 0x7ffa221660b4 in __GI___libc_read (fd=8, buf=0x7ff9ff0c7b60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7ffa1e87bcd0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ffa1e837027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffa1e8374e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ffa1e83764c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ffa22aad15b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7ff9f8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7ffa22a4e64a in QEventLoop::exec(QFlags) (this=this@entry=0x7ff9ff0c7d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7ffa2287641a in QThread::exec() (this=this@entry=0x7ffa246b9d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:531 #8 0x7ffa24442015 in QDBusConnectionManager::run() (this=0x7ffa246b9d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #9 0x7ffa22877bc2 in QThreadPrivate::start(void*) (arg=0x7ffa246b9d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #10 0x7ffa209d36db in start_thread (arg=0x7ff9ff0c8700) at pthread_create.c:463 #11 0x7ffa2217788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7ffa18987700 (LWP 3534)): #0 0x7ffa2216abf9 in __GI___poll (fds=0x7ffa18986cb8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ffa1e3c6747 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7ffa1e3c836a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7ffa19f0232a in QXcbEventQueue::run() (this=0x55a659c5ccd0) at qxcbeventqueue.cpp:225 #4 0x7ffa22877bc2 in QThreadPrivate::start(void*) (arg=0x55a659c5ccd0) at thread/qthread_unix.cpp:361 #5 0x7ffa209d36db in start_thread (arg=0x7ffa18987700) at pthread_create.c:463 #6 0x7ffa2217788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7ffa25653c80 (LWP 3533)): [KCrash Handler] #6 0x7ffa22094e97 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7ffa22096801 in __GI_abort () at abort.c:79 #8 0x7ffa21382932 in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #9 0x7ffa213777b5 in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #10 0x7ffa213789bb in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #11 0x7ffa21378c29 in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #12 0x7ffa2137a854 in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #13 0x7ffa2137ea7a in mdb_cursor_del () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #14 0x7ffa2138029c in () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #15 0x7ffa24adaf2e in Baloo::DocumentDB::del(unsigned long long) () at /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #16 0x7ffa24af431a in Baloo::WriteTransaction::removeDocument(unsigned long long) () at /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #17 0x55a657a4c37c in () #18 0x55a657a4cb9e in () #19 0x7ffa22a8cd04 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffce85365a0, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #20 0x7ffa22a8cd04 in QSingleShotTimer::timerEvent(QTimerEvent*) (this=0x55a659ca80a0) at kernel/qtimer.cpp:318 #21 0x7ffa22a8094b in QObject::event(QEvent*) (this=0x55a659ca80a0, e=) at kernel/qobject.cpp:1271 #22 0x7ffa2384683c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x55a659c570f0, receiver=receiver@entry=0x55a659ca80a0, e=e@entry=0x7ffce85368e0) at kernel/qapplication.cpp:3752 #23 0x7ffa2384ddd0 in QApplication::notify(QObject*, QEvent*) (this=0x7ff
[kmail2] [Bug 405791] Crash when clicking on a mail that contains vcard.vcf attachment
https://bugs.kde.org/show_bug.cgi?id=405791 --- Comment #2 from Christian --- Created attachment 119036 --> https://bugs.kde.org/attachment.cgi?id=119036&action=edit Example vcf that crashes my kmail instance With the attached (dummy) vcf file that contains two entries, I can reproduce this crash every time. To reproduce: Save the attached all.vcf file somewhere; create a new message to myself with this file attached and send the message; receive the message and left-click on it -> crash. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 403642] ASSERT failure in ResourceBase::collectionsRetrieved(): "Calling collectionsRetrieved() although no collection retrieval is in progress"
https://bugs.kde.org/show_bug.cgi?id=403642 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org --- Comment #3 from Daniel Vrátil --- Created attachment 119035 --> https://bugs.kde.org/attachment.cgi?id=119035&action=edit Patch for Akonadi Hi Milian, could you try with this patch? It appears that SyncCollectionTree here is just a victim of another bug triggered by the previous ChangeReply for collection modification. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405870] New: Discover's text almost unreadable in dark theme
https://bugs.kde.org/show_bug.cgi?id=405870 Bug ID: 405870 Summary: Discover's text almost unreadable in dark theme Product: Discover Version: 5.14.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: david.cortes.riv...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 119034 --> https://bugs.kde.org/attachment.cgi?id=119034&action=edit hard_to_read Steps to reproduce: * Set some dark color scheme such as Oxidian coast (System Settings -> Colors) * Make sure there are no installable updates through discovery (e.g. by updating everything) * Go to discovery's update section. Attached is a screenshot of how it looks like with a dark theme. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 405868] Copying big file to FAT32 system throws no warning
https://bugs.kde.org/show_bug.cgi?id=405868 Elvis Angelaccio changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Elvis Angelaccio --- This is fixed in KIO >= 5.54 *** This bug has been marked as a duplicate of bug 198772 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 198772] FAT32 file transfer: warn (and stop) before copying a file bigger than 4Gb
https://bugs.kde.org/show_bug.cgi?id=198772 Elvis Angelaccio changed: What|Removed |Added CC||david.cortes.rivera@gmail.c ||om --- Comment #18 from Elvis Angelaccio --- *** Bug 405868 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 405869] New: Scrollbar arrows don't change size along with scrollbar
https://bugs.kde.org/show_bug.cgi?id=405869 Bug ID: 405869 Summary: Scrollbar arrows don't change size along with scrollbar Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- Steps to reproduce: * Go to System Settings -> Application Style -> Widget Style, and select some style with a fixed scrollbar such as Oxygen or QTCurve. * Click Configure next to the style name, go to "Scrollbars" (for Oxygen), increase scrollbar width. Expected behavior: arrow pointers at the top and bottom of the bar should increase in size as the bar width increases. Actual behavior: arrow pointers stay the same size, becoming much smaller than the scrollbar itself as the size grows. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 405868] New: Copying big file to FAT32 system throws no warning
https://bugs.kde.org/show_bug.cgi?id=405868 Bug ID: 405868 Summary: Copying big file to FAT32 system throws no warning Product: dolphin Version: 18.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: david.cortes.riv...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- If I try to copy some big file (>2GB) to a FAT32 file system, dolphin will fail in the middle of it without giving a reason. Would be nicer if it would tell the user beforehand that the file system does not support such file sizes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390642] Cursor gets stuck with the wrong icon after moving between canvas and gui
https://bugs.kde.org/show_bug.cgi?id=390642 --- Comment #55 from zoltron --- (In reply to zoltron from comment #54) > (In reply to vanyossi from comment #53) > > @zoltron > > > > If the version stated in "Krita:About" is 4.1.7, you were not using the dmg > > I provided as it reads 4.2.0-beta (or something similar). > > > > The bug you are getting seems to be another one about the cursor getting > > stuck after zooming or rotating with touchpad gestures. It should not get > > stuck by simply moving the cursor between canvas and docker elements. If it > > gets stuck only by "moving the cursor around the interface with the tablet" > > then the bug is still present. > > sorry you are right, this happens only when zooming with touchpad gesture, i > tried with every versions of krita. bug is not fixed any version. i use dmg you provided. your dmg crashed when "split alpha" operation. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 404458] [git master] Re-imports my library instead of using existing one, and gets stuck on some file
https://bugs.kde.org/show_bug.cgi?id=404458 --- Comment #10 from Matthieu Gallien --- Could you test again and sent a new log with the current master code ? The logging should help understand what happen. It should report all cases where a track is not inserted in the music database. Thanks in advance -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404935] Window of another apps partially visible in Krita canvas
https://bugs.kde.org/show_bug.cgi?id=404935 Dmitry Kazakov changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||dimul...@gmail.com --- Comment #5 from Dmitry Kazakov --- I can confirm the bug on Linux... -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 393106] When I specify a path, it still uses baloo and looks everywhere for files
https://bugs.kde.org/show_bug.cgi?id=393106 Matthieu Gallien changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://commits.kde.org/eli ||sa/79054e47bb532eec4b3fbc87 ||2a7a1c5e32910456 Resolution|--- |FIXED --- Comment #6 from Matthieu Gallien --- Git commit 79054e47bb532eec4b3fbc872a7a1c5e32910456 by Matthieu Gallien. Committed on 25/03/2019 at 20:40. Pushed by mgallien into branch 'master'. Simplify and improve music indexers management Summary: start baloo first and if it is not available, start local file indexer remove management of track discovery sources simplify management of tracks by removing management of which source has discovered a track should allow users to easily switch from Baloo to local file system as tracks source improve management of tracks sources such that only baloo or local file system scanning is enabled no longer emit a signal when Elisa cannot watch a file for changes refactor the way we check for Baloo availability filter tracks by the configured paths when getting all tracks from Baloo use the same list of paths than plain file system scanning remove double checking for baloo configuration: not needed Baloo configuration is now checked before going into LocalBalooFileListing: no need to do it a second time add support for qt logging category and use it for file indexers improve management of indexers state and user reporting convert LocalBalooFileListing to only use categorized debug logs hopefully fix the display of busy indexers notifications when configuration change, display proper busy notification to the user indexing is no longer finished until tracks have been fully removed Test Plan: Only one indexer is active (baloo or plain old file indexer). Traces should help diagnose what happen Reviewers: ngraham Tags: #elisa Differential Revision: https://phabricator.kde.org/D19650 M +10 -10 autotests/alltracksproxymodeltest.cpp M +73 -266 autotests/databaseinterfacetest.cpp M +31 -31 autotests/datamodeltest.cpp M +15 -125 autotests/localfilelistingtest.cpp M +3-3autotests/manageheaderbartest.cpp M +3-3autotests/managemediaplayercontroltest.cpp M +47 -47 autotests/mediaplaylisttest.cpp M +6-6autotests/trackslistenertest.cpp M +36 -0src/CMakeLists.txt M +10 -3src/abstractfile/abstractfilelistener.cpp M +3-1src/abstractfile/abstractfilelistener.h M +57 -27 src/abstractfile/abstractfilelisting.cpp M +19 -10 src/abstractfile/abstractfilelisting.h M +21 -19 src/audiowrapper_libvlc.cpp A +117 -0src/baloo/baloodetector.cpp [License: LGPL (v3+)] A +67 -0src/baloo/baloodetector.h [License: LGPL (v3+)] M +69 -82 src/baloo/localbaloofilelisting.cpp M +0-6src/baloo/localbaloofilelisting.h M +1008 -616 src/databaseinterface.cpp M +39 -10 src/databaseinterface.h M +0-11 src/elisa_core.kcfg M +1-1src/elisaimport.cpp M +0-12 src/file/filelistener.cpp M +0-15 src/file/filelistener.h M +10 -22 src/file/localfilelisting.cpp M +0-15 src/file/localfilelisting.h M +1-1src/localFileConfiguration/localfileconfiguration.cpp M +48 -8src/musicaudiotrack.cpp M +10 -0src/musicaudiotrack.h M +173 -104 src/musiclistenersmanager.cpp M +48 -8src/musiclistenersmanager.h M +11 -15 src/qml/ElisaMainWindow.qml M +28 -11 src/qml/TrackImportNotification.qml https://commits.kde.org/elisa/79054e47bb532eec4b3fbc872a7a1c5e32910456 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405867] Discover crashes when launched from update tasktray icon
https://bugs.kde.org/show_bug.cgi?id=405867 --- Comment #1 from Sam --- The bug DOES NOT persist past reboot. Further notes: * I switched NVIDIA driver from 415 to 418 prior to reboot. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405844] Blending Modes Keyboard Shortcuts not working
https://bugs.kde.org/show_bug.cgi?id=405844 --- Comment #2 from zoltron --- (In reply to vanyossi from comment #1) > Mojave, krita 4.1.7 > > Works for me as stated in > https://docs.krita.org/en/reference_manual/blending_modes.html#hotkeys- > associated-with-blending-modes > > Blending mode change the brush paint blending mode, not the layer blending > mode. Some shortcuts have collisions (alt + shift + I) for example, but you > get a dialog. And if no collision I get blending mode wokring correctly. I thought the shortcuts were for the layer. I was wrong. is it possible to use shortcut for layers? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405867] New: Discover crashes when launched from update tasktray icon
https://bugs.kde.org/show_bug.cgi?id=405867 Bug ID: 405867 Summary: Discover crashes when launched from update tasktray icon Product: Discover Version: 5.13.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: nat...@outlook.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.13.5) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.20.17-042017-generic x86_64 Distribution: Ubuntu 18.10 -- Information about the crash: I got this crash when I attempted to launch Discover from the update notification systray icon. Repro steps: 1. Observe that there were available updates (4 in my case). 2. Click systray icon. 3. Click "Update" in the dialog that appears. Notes: * The program appears to crash early in its UI routine as the shape of the window seems to appear (visually - I have not inspected the callstack). If you need more information, please let me know. I do not know if the issue persists after reboot, will update after trying that. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7e8f70bc80 (LWP 21131))] Thread 11 (Thread 0x7f7e5700 (LWP 21142)): #0 0x7f7e94d8c219 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f7e950a3c25 in QBasicMutex::lockInternal() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f7e946b367b in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #3 0x7f7e946b3e95 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #4 0x7f7e9468e5a8 in QSslSocket::startClientEncryption() () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #5 0x7f7e9468f280 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #6 0x7f7e94696489 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #7 0x7f7e952826db in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f7e946583c3 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #9 0x7f7e9465b230 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #10 0x7f7e9466a37d in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7f7e960b34a1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f7e960baae0 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f7e95259499 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f7e952abd6a in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f7e92ae7c3e in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f7e92ae7ed8 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f7e92ae7f6c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f7e952ab15b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f7e9525816b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f7e950a70b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f7e950b0c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f7e93e3a164 in start_thread (arg=) at pthread_create.c:486 #23 0x7f7e94d92def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f7e70b03700 (LWP 21140)): #0 0x7f7e94d81f64 in __GI___libc_read (fd=25, buf=0x7f7e70b02cd0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7f7e92b2d180 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7e92ae791f in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7e92ae7df0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f7e92ae81d2 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f7e7295f7b6 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x7f7e92b10135 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f7e93e3a164 in start_thread (arg=) at pthread_create.c:486 #8 0x7f7e94d92def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f7e71304700 (LWP 21139)): #0 0x7f7e94d866d9 in __GI___poll (fds=0x55b6e85c6f70, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f7e92ae7e46 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7e92ae7f6c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7e92ae7fb1 in ()
[krita] [Bug 390642] Cursor gets stuck with the wrong icon after moving between canvas and gui
https://bugs.kde.org/show_bug.cgi?id=390642 --- Comment #54 from zoltron --- (In reply to vanyossi from comment #53) > @zoltron > > If the version stated in "Krita:About" is 4.1.7, you were not using the dmg > I provided as it reads 4.2.0-beta (or something similar). > > The bug you are getting seems to be another one about the cursor getting > stuck after zooming or rotating with touchpad gestures. It should not get > stuck by simply moving the cursor between canvas and docker elements. If it > gets stuck only by "moving the cursor around the interface with the tablet" > then the bug is still present. sorry you are right, this happens only when zooming with touchpad gesture, i tried with every versions of krita. bug is not fixed any version. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404375] Severe visual artifacts with Qt 5.12
https://bugs.kde.org/show_bug.cgi?id=404375 --- Comment #9 from Martin Flöser --- Well I don't know how often I told people to not animate opacity... In that point qml sucks. It's way too easy to do inefficient things like animating opacity or geometry. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 366627] Columns settings aren't retained
https://bugs.kde.org/show_bug.cgi?id=366627 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #5 from Patrick Silva --- I can't confirm this bug with ktorrent 5.1.1 on Arch linux. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 322060] Synced swapping on double buffered nvidia GPUs cause high CPU load
https://bugs.kde.org/show_bug.cgi?id=322060 Martin Flöser changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #155 from Martin Flöser --- Marking as fixed per latest comment -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405866] New: Transferring files using KDEConnect to PC (dolphin) freezes whole dolphin
https://bugs.kde.org/show_bug.cgi?id=405866 Bug ID: 405866 Summary: Transferring files using KDEConnect to PC (dolphin) freezes whole dolphin Product: kdeconnect Version: 1.10 Platform: Neon Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: t.ki...@gmail.com Target Milestone: --- SUMMARY Transferring files using KDEConnect to PC (dolphin) freezes whole dolphin STEPS TO REPRODUCE 1. Connect KDEConnect to PC, setup folders properly 2. Choose files to transfer to PC (using Dolphin), and on other tab of dolphin it starts 3. Switch tabs in Dolphin to original folder in phone OBSERVED RESULT Dolphin freezes for 5 minutes EXPECTED RESULT To just show the folder. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56 Qt Version: 5.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404375] Severe visual artifacts with Qt 5.12
https://bugs.kde.org/show_bug.cgi?id=404375 --- Comment #8 from Filip Fila --- Severe flickering and artifacts after re-enabling compositing *are* still an issue with Qt 5.12.2 OSD stutter issue was fixed with: https://phabricator.kde.org/R120:9a7de4e02399880a0e649bad32a40ad820fc87eb -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390642] Cursor gets stuck with the wrong icon after moving between canvas and gui
https://bugs.kde.org/show_bug.cgi?id=390642 --- Comment #53 from vanyossi --- @zoltron If the version stated in "Krita:About" is 4.1.7, you were not using the dmg I provided as it reads 4.2.0-beta (or something similar). The bug you are getting seems to be another one about the cursor getting stuck after zooming or rotating with touchpad gestures. It should not get stuck by simply moving the cursor between canvas and docker elements. If it gets stuck only by "moving the cursor around the interface with the tablet" then the bug is still present. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 166223] favorite folders for Akregator
https://bugs.kde.org/show_bug.cgi?id=166223 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 --- Comment #18 from Nicofo --- Additional comments: as stated in comment #8, a previous version of your appimage (2019-03-04) worked: LD_PRELOAD=/usr/lib64/libfreetype.so.6:/usr/lib64/libudev.so.1 ./digikam-6.1.0-git-20190304T120153-x86-64.appimage (the other libs preloaded were necessary with older versions of appimage, but there is no need to preload ssl/crypto/... libs) Maybe you can check what you changed in regards to libssl/crypto in your appimage builds since 04th of March ? Note: as said, using that appimage I can connect to Onedrive. Now if I relaunch the last version of digikam (with LD_PRELOAD=/usr/lib64/libcrypto.so.10), I'm still logged in Onedrive and can transfer files. So this is "just" the login process that fails: once logged in, it works. -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 367650] ~/.fonts deprecation ; please install new fonts to $XDG_DATA_HOME/fonts ; ~/.local/share/fonts
https://bugs.kde.org/show_bug.cgi?id=367650 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #4 from Patrick Silva --- Bug persists. Operating System: Arch Linux KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 405865] New: Dolphin crash
https://bugs.kde.org/show_bug.cgi?id=405865 Bug ID: 405865 Summary: Dolphin crash Product: dolphin Version: 18.12.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: albertocanet...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (18.12.3) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: I have omited to copy a folder when the same folder name alredy exist The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd6831d6e40 (LWP 31211))] Thread 4 (Thread 0x7fd65480f700 (LWP 31219)): #0 0x7fd682a4fbf9 in __GI___poll (fds=0x7fd6500049b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fd674f19539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd674f1964c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd67cba515b in QEventDispatcherGlib::processEvents (this=0x7fd65b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fd67cb4664a in QEventLoop::exec (this=this@entry=0x7fd65480eda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fd67c96e41a in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7fd67c96fbc2 in QThreadPrivate::start (arg=0x556a62920fc0) at thread/qthread_unix.cpp:361 #7 0x7fd6773016db in start_thread (arg=0x7fd65480f700) at pthread_create.c:463 #8 0x7fd682a5c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fd6616fb700 (LWP 31218)): #0 0x7fd6773079f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x556a62577eb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x556a62577e68, cond=0x556a62577e90) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x556a62577e90, mutex=0x556a62577e68) at pthread_cond_wait.c:655 #3 0x7fd662880dcb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7fd662880af7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7fd6773016db in start_thread (arg=0x7fd6616fb700) at pthread_create.c:463 #6 0x7fd682a5c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fd66a0bc700 (LWP 31215)): #0 0x7fd674f19546 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fd674f1964c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd67cba515b in QEventDispatcherGlib::processEvents (this=0x7fd65c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #3 0x7fd67cb4664a in QEventLoop::exec (this=this@entry=0x7fd66a0bbd70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #4 0x7fd67c96e41a in QThread::exec (this=) at thread/qthread.cpp:531 #5 0x7fd67d013015 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fd67c96fbc2 in QThreadPrivate::start (arg=0x7fd67d28ad80) at thread/qthread_unix.cpp:361 #7 0x7fd6773016db in start_thread (arg=0x7fd66a0bc700) at pthread_create.c:463 #8 0x7fd682a5c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fd6831d6e40 (LWP 31211)): [KCrash Handler] #6 0x7fd68114f5e4 in KIO::CopyJobPrivate::copyNextFile (this=this@entry=0x556a62c82c60) at ./src/core/copyjob.cpp:1614 #7 0x7fd68115034a in KIO::CopyJobPrivate::createNextDir (this=this@entry=0x556a62c82c60) at ./src/core/copyjob.cpp:1274 #8 0x7fd681152dce in KIO::CopyJobPrivate::slotResultConflictCreatingDirs (this=this@entry=0x556a62c82c60, job=job@entry=0x556a62cc4ab0) at ./src/core/copyjob.cpp:1224 #9 0x7fd681155b2b in KIO::CopyJob::slotResult (this=0x556a62cc33d0, job=0x556a62cc4ab0) at ./src/core/copyjob.cpp:2166 #10 0x7fd67cb77f3f in QtPrivate::QSlotObjectBase::call (a=0x7ffd50ff2f00, r=0x556a62cc33d0, this=0x556a62cc36a0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #11 QMetaObject::activate (sender=sender@entry=0x556a62cc4ab0, signalOffset=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffd50ff2f00) at kernel/qobject.cpp:3759 #12 0x7fd67cb784f7 in QMetaObject::activate (sender=sender@entry=0x556a62cc4ab0, m=m@entry=0x7fd67e7de500 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffd50ff2f00) at kernel/qobject.cpp:3631 #13 0x7fd67e58708c in KJob::result (this=this@entry=0x556a62cc4ab0, _t1=, _t1@entry=0x556a62cc4ab0, _t2=
[okular] [Bug 367959] Okular mangles some characters (non embedded fonts)
https://bugs.kde.org/show_bug.cgi?id=367959 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #9 from Patrick Silva --- Bug persists. I tested okular 1.6.3, inkscape 0.92.4, evince 3.32 and foxit pdf reader 2.4.4.0911 on Arch Linux. Only inkscape renders the attachment from comment 1 correctly. Operating System: Arch Linux KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 --- Comment #17 from Nicofo --- Thanks for investigating this ! I have libnssutils on my system. I just made several tests: 1) export LD_PRELOAD=/usr/lib64/libssl3.so:/usr/lib64/libnssutil3.so -> digikam crashes when I use the export to Onedrive tool. Same errors as in comment #11 (ending with : /tmp/.mount_digikaGNEWfx/AppRun: line 133: Segmentation fault (core dumped) digikam $@ 2) to not have the crash, I need to export another library (and just this one: no need to export ssl3 or ssl or nssutil): export LD_PRELOAD=/usr/lib64/libcrypto.so.10 But then I get the broken connection window (as attached in comment #11) Note: I cannot connect to Dropbox neither. I suppose this is the same issue. I don't know what kind of tests I can still do ? -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 368177] Bookmarks/places are separated and hard to use, and there's no "Recents"
https://bugs.kde.org/show_bug.cgi?id=368177 Patrick Silva changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 368177] Bookmarks/places are separated and hard to use, and there's no "Recents"
https://bugs.kde.org/show_bug.cgi?id=368177 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #8 from Patrick Silva --- Created attachment 119033 --> https://bugs.kde.org/attachment.cgi?id=119033&action=edit "Show bookmarks" in kdialog Bookmark icon is present after I press ctrl+s in chromium internet browser and enable "Show bookmarks" shown in my screenshot. Operating System: Arch Linux KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405728] plasma widget crashing
https://bugs.kde.org/show_bug.cgi?id=405728 David Edmundson changed: What|Removed |Added CC||outofmario1...@gmail.com --- Comment #5 from David Edmundson --- *** Bug 405864 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405864] Plasma crash when trying to configure desktop tweaks
https://bugs.kde.org/show_bug.cgi?id=405864 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- >#7 0x7fcc7ab46f86 in Kvantum::Style::drawItemText(QPainter*, QRect const&, *** This bug has been marked as a duplicate of bug 405728 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405864] New: Plasma crash when trying to configure desktop tweaks
https://bugs.kde.org/show_bug.cgi?id=405864 Bug ID: 405864 Summary: Plasma crash when trying to configure desktop tweaks Product: plasmashell Version: 5.15.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: outofmario1...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.15.3) Qt Version: 5.12.2 Frameworks Version: 5.56.0 Operating System: Linux 5.0.3-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Configuring desktop tweaks and updating the system. - Custom settings of the application: Kvantum Latte Dock Mac OS Kvantum theme and window decorations The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcc7c704880 (LWP 641))] Thread 28 (Thread 0x7fcbe93dc700 (LWP 1246)): #0 0x7fcc807a8afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcc814aac4c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fcc814aad3a in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fcc831fa91d in () at /usr/lib/libQt5Quick.so.5 #4 0x7fcc831fab8c in () at /usr/lib/libQt5Quick.so.5 #5 0x7fcc814a496c in () at /usr/lib/libQt5Core.so.5 #6 0x7fcc807a2a9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fcc8118eb23 in clone () at /usr/lib/libc.so.6 Thread 27 (Thread 0x7fcbe9bdd700 (LWP 1245)): #0 0x7fcc807a8afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcc6b56b104 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fcc6b56ae28 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fcc807a2a9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fcc8118eb23 in clone () at /usr/lib/libc.so.6 Thread 26 (Thread 0x7fcc10869700 (LWP 1237)): #0 0x7fcc81183c21 in poll () at /usr/lib/libc.so.6 #1 0x7fcc7f84e690 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fcc7f84e77e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fcc816b6cb4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fcc8165fa8c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fcc814a3569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fcc82eab109 in () at /usr/lib/libQt5Qml.so.5 #7 0x7fcc814a496c in () at /usr/lib/libQt5Core.so.5 #8 0x7fcc807a2a9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fcc8118eb23 in clone () at /usr/lib/libc.so.6 Thread 25 (Thread 0x7fcc11191700 (LWP 1162)): #0 0x7fcc807a8afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcc814aac4c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fcc814aad3a in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fcc831fa91d in () at /usr/lib/libQt5Quick.so.5 #4 0x7fcc831fab8c in () at /usr/lib/libQt5Quick.so.5 #5 0x7fcc814a496c in () at /usr/lib/libQt5Core.so.5 #6 0x7fcc807a2a9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fcc8118eb23 in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7fcc13fff700 (LWP 1161)): #0 0x7fcc807a8afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcc6b56b104 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fcc6b56ae28 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fcc807a2a9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fcc8118eb23 in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7fcc11b42700 (LWP 883)): #0 0x7fcc807a8afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcc814aac4c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fcc814aad3a in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fcc831fa91d in () at /usr/lib/libQt5Quick.so.5 #4 0x7fcc831fab8c in () at /usr/lib/libQt5Quick.so.5 #5 0x7fcc814a496c in () at /usr/lib/libQt5Core.so.5 #6 0x7fcc807a2a9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fcc8118eb23 in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7fcc12343700 (LWP 882)): #0 0x7fcc807a8afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcc6b56b104 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fcc6b56ae28 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fcc807a2a9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fcc8118eb23
[okular] [Bug 368588] Okular preview of certain PDF documents shows empty pages with Okular logo only
https://bugs.kde.org/show_bug.cgi?id=368588 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #10 from Patrick Silva --- Bug persists with okular 1.6.3, ghostscript 9.26, libspectre 0.2.8. Operating System: Arch Linux KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 368598] Zoom Out does not work when zoom is set to Fit Page or Fit Width and "Trim margins" is enabled
https://bugs.kde.org/show_bug.cgi?id=368598 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com Summary|Zoom Out does not work when |Zoom Out does not work when |zoom is set to Fit Page or |zoom is set to Fit Page or |Fit Width |Fit Width and "Trim ||margins" is enabled -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405847] SFTP corrupts DNG files
https://bugs.kde.org/show_bug.cgi?id=405847 --- Comment #4 from zhangchi...@gmail.com --- (In reply to zhangchi866 from comment #3) > (In reply to Erik Duisters from comment #2) > > The SFTP protocol is a slow protocol. Are you sure the copy process was > > complete before you try to open the image? I get the same behavior when I > > try to directly open images (jpg, png or raw's) on the phone's storage. Some > > programs handle the slow transfer speed well others don't > > I can confirm the copy is complete. I also tried with multiple images. The > corrupt files have altered content rather than being incomplete. > > However, I failed to reproduce the problem on another computer (under the > same network), which is really weird. I suppose only bugs in sftp or the > Android app can cause such behavior. Will do more test to tell what is going > on. Actually, just retried on the other computer and the problem emerges, although slightly different (corruption starts at different addresses, did 2 run, between which I killed kdeconnectd on my computer, and got 0x8000 & 0x0001c000, respectively). I have no idea why it worked as intended in the first try. By my understanding, kdeconnect is using system's sshfs program and that should be quite reliable, is it? -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 368851] Cannot add new files to a specific RAR archive
https://bugs.kde.org/show_bug.cgi?id=368851 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 --- Comment #16 from caulier.gil...@gmail.com --- This is strange because libnss is dropped for the list of bundled libraries in AppImage : https://cgit.kde.org/digikam.git/tree/project/bundles/appimage/04-build-appimage.sh#n265 This puzzle me. It's not clear to know which libraries must be used from native system or not. SSL is problematic because it require the most advanced version for security reasons. but SSL is relevant of plenty dependencies. I take a look into other AppImage project, and digiKam is the only one which require secure internet access. If you have also the libnssutils on your system, try to upload also this one with SSL library before to run digiKam. In fact, there is a combinaison to found. Note: In digiKam appimage, libssl3.so and libnssl3.so are included and must do the job without to preload files in memory from native system... Gilles -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 405272] KTextEditor: column count wrong for UTF32
https://bugs.kde.org/show_bug.cgi?id=405272 Dominik Haumann changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #6 from Dominik Haumann --- This is functions as designed. We even have API for this: 1. bool KTextEditor::Document::isValidTextPosition(Cursor) const https://api.kde.org/frameworks/ktexteditor/html/classKTextEditor_1_1Document.html#a31201a07310caab1246886d06e9b8559 2. bool KTextEditor::DocumentCursor::isValidTextPosition() const https://api.kde.org/frameworks/ktexteditor/html/classKTextEditor_1_1DocumentCursor.html#adc1e646dd9432cbf7aff21d456550ca8 There is no bug. And it's also correct that this is counted as multiple characters. With input methods, these character probably even can be edited. If you really think there is an issue, then please discuss with Qt developers on the Qt developer mailing lists. Kate won't change. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405847] SFTP corrupts DNG files
https://bugs.kde.org/show_bug.cgi?id=405847 --- Comment #3 from zhangchi...@gmail.com --- (In reply to Erik Duisters from comment #2) > The SFTP protocol is a slow protocol. Are you sure the copy process was > complete before you try to open the image? I get the same behavior when I > try to directly open images (jpg, png or raw's) on the phone's storage. Some > programs handle the slow transfer speed well others don't I can confirm the copy is complete. I also tried with multiple images. The corrupt files have altered content rather than being incomplete. However, I failed to reproduce the problem on another computer (under the same network), which is really weird. I suppose only bugs in sftp or the Android app can cause such behavior. Will do more test to tell what is going on. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405782] "VEX temporary storage exhausted" when attempting to debug slic3r-pe
https://bugs.kde.org/show_bug.cgi?id=405782 --- Comment #3 from wav...@thregr.org --- Done, sorry for the delay. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405782] "VEX temporary storage exhausted" when attempting to debug slic3r-pe
https://bugs.kde.org/show_bug.cgi?id=405782 --- Comment #2 from wav...@thregr.org --- Created attachment 119032 --> https://bugs.kde.org/attachment.cgi?id=119032&action=edit valgrind trace -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 403874] Kaffeine scanlist channels lost
https://bugs.kde.org/show_bug.cgi?id=403874 --- Comment #12 from compi-kil...@gmx.de --- (In reply to Mauro Carvalho Chehab from comment #11) > And run it from the git tree, instead of installing, with: > >$ src/kaffeine > > (you may also install, if you want - install instructions are also at the > README.md file) sorry, did not work in any. Also Re-install with newest version of both PC-LinuxOS and kaffeine did not work. I hope I find some time to test again this month -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405863] New: Kontact
https://bugs.kde.org/show_bug.cgi?id=405863 Bug ID: 405863 Summary: Kontact Product: kontact Version: 5.10.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: felicien.pil...@riseup.net Target Milestone: --- Application: kontact (5.10.3) Qt Version: 5.12.2 Frameworks Version: 5.56.0 Operating System: Linux 4.14.85-1-lts x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Segmentation fault when launching Kontact from the .desktop file. Korganizer standalone does work correctly. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3e3cab5b40 (LWP 5535))] Thread 47 (Thread 0x7f3cc5167700 (LWP 5611)): #0 0x7f3e3d69e4ed in syscall () at /usr/lib/libc.so.6 #1 0x7f3e3d9e0d15 in QSemaphore::acquire(int) () at /usr/lib/libQt5Core.so.5 #2 0x7f3cc6e1c877 in () at /usr/lib/qt/plugins/texttospeech/libqttexttospeech_flite.so #3 0x7f3e3d9de96c in () at /usr/lib/libQt5Core.so.5 #4 0x7f3e3c497a9d in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f3e3d6a3b23 in clone () at /usr/lib/libc.so.6 Thread 46 (Thread 0x7f3cc67b7700 (LWP 5608)): #0 0x7f3e3b81b414 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f3e3b86d685 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f3e3b86d77e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f3e3dbf0cb4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f3e3db99a8c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f3e3d9dd569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f3e3d9de96c in () at /usr/lib/libQt5Core.so.5 #7 0x7f3e3c497a9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f3e3d6a3b23 in clone () at /usr/lib/libc.so.6 Thread 45 (Thread 0x7f3cc7717700 (LWP 5607)): #0 0x7f3e3c49dafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3e3d845cd1 in __gthread_cond_wait (__mutex=, __cond=) at /build/gcc/src/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu/bits/gthr-default.h:864 #2 0x7f3e3d845cd1 in std::condition_variable::wait(std::unique_lock&) (this=, __lock=...) at /build/gcc/src/gcc/libstdc++-v3/src/c++11/condition_variable.cc:53 #3 0x7f3cd24fbf14 in () at /usr/lib/libQt5WebKit.so.5 #4 0x7f3cd24fc039 in () at /usr/lib/libQt5WebKit.so.5 #5 0x7f3e3d84c063 in std::execute_native_thread_routine(void*) (__p=0x56194b7e6110) at /build/gcc/src/gcc/libstdc++-v3/src/c++11/thread.cc:80 #6 0x7f3e3c497a9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f3e3d6a3b23 in clone () at /usr/lib/libc.so.6 Thread 44 (Thread 0x7f3cd37fe700 (LWP 5597)): #0 0x7fffd91939c9 in () #1 0x7fffd9193bcc in clock_gettime () #2 0x7f3e3d6b19f2 in clock_gettime () at /usr/lib/libc.so.6 #3 0x7f3e3dbf05a2 in () at /usr/lib/libQt5Core.so.5 #4 0x7f3e3dbeed8a in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #5 0x7f3e3dbef386 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #6 0x7f3e3dbf109d in () at /usr/lib/libQt5Core.so.5 #7 0x7f3e3b86cf5a in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #8 0x7f3e3b86d5b6 in () at /usr/lib/libglib-2.0.so.0 #9 0x7f3e3b86d77e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #10 0x7f3e3dbf0cb4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #11 0x7f3e3db99a8c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #12 0x7f3e3d9dd569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #13 0x7f3e3d9de96c in () at /usr/lib/libQt5Core.so.5 #14 0x7f3e3c497a9d in start_thread () at /usr/lib/libpthread.so.0 #15 0x7f3e3d6a3b23 in clone () at /usr/lib/libc.so.6 Thread 43 (Thread 0x7f3cd3fff700 (LWP 5596)): #0 0x7f3e3b81b414 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f3e3b86d478 in g_main_context_acquire () at /usr/lib/libglib-2.0.so.0 #2 0x7f3e3b86d537 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f3e3b86d77e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f3e3dbf0cb4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f3e3db99a8c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f3e3d9dd569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f3e3d9de96c in () at /usr/lib/libQt5Core.so.5 #8 0x7f3e3c497a9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f3e3d6a3
[dolphin] [Bug 267916] Dolphin User-Defined Tools/Services and configuration
https://bugs.kde.org/show_bug.cgi?id=267916 --- Comment #3 from andydecle...@gmail.com --- Created attachment 119031 --> https://bugs.kde.org/attachment.cgi?id=119031&action=edit dolphin-meld patch -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 267916] Dolphin User-Defined Tools/Services and configuration
https://bugs.kde.org/show_bug.cgi?id=267916 andydecle...@gmail.com changed: What|Removed |Added CC||andydecle...@gmail.com --- Comment #2 from andydecle...@gmail.com --- I know this is 8 years old, but still very much an annoyance, to the point that I maintain a patched package for Arch Linux's AUR: dolphin-meld It uses meld rather than kompare (I simply cannot figure out how to be productive with kompare), uses meld's icon rather than kompare's (meld's is actually hideous in the Papirus theme, but it seems the proper thing to do), and allows for up to three documents to be selected and compared. I'll attach the patch file, in case it helps someone interested in this bug. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 369137] Screen will not lock when switching virtual terminal
https://bugs.kde.org/show_bug.cgi?id=369137 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #4 from Patrick Silva --- I can't confirm at least on X11. I had plasma running on tty1, I switched to tty2 and logged-in using another user account. So I switched back to tty1 after the screen locking timeout, I could see plasma for a few milliseconds and then the screen was blocked. Operating System: Arch Linux KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400164] helgrind test encounters mips x-compiler warnings and assembler error
https://bugs.kde.org/show_bug.cgi?id=400164 Petar Jovanovic changed: What|Removed |Added CC||mips3...@gmail.com Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Petar Jovanovic --- I hope this is fixed with https://sourceware.org/git/?p=valgrind.git;a=commit;h=d6da48fe5ac2e94fe28184ff334cd6b2283ef9a6 Randy, can you confirm? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405802] Export metadata to csv file
https://bugs.kde.org/show_bug.cgi?id=405802 --- Comment #7 from Maurizio --- It is interesting to have the command integrated in digikam. :-). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405787] Cursor not working anymore after moving the cursor off the canvas and back
https://bugs.kde.org/show_bug.cgi?id=405787 --- Comment #7 from Takiro Ryo --- I tried the app image but the latest I could find was version 4.1.7 (https://krita.org/en/download/krita-desktop/) which is even older than my currently installed 4.1.7.101-2 (from the repositories). The app image of course works fine just as expected, since the 4.1.7.101-2 version does too. The issue only appears after upgrading to 4.1.8. To check if it doesn't affect the appimage I'd need one in version 4.1.8. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 322060] Synced swapping on double buffered nvidia GPUs cause high CPU load
https://bugs.kde.org/show_bug.cgi?id=322060 --- Comment #154 from Peter Eszlari --- I guess this bug can be closed now: https://phabricator.kde.org/D19867 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405843] kdeconnectd crashes and looses connection with android client after replying to a message.
https://bugs.kde.org/show_bug.cgi?id=405843 Simon changed: What|Removed |Added Assignee|si...@ergotech.com |albertv...@gmail.com Component|messaging-application |common --- Comment #1 from Simon --- Sorry you are having this issue! Could you install debug symbols for (at least) kdeconnectd, then capture a backtrace of the crash? The current backtraces don't give enough information for me to see where the crash is happening. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405843] kdeconnectd crashes and looses connection with android client after replying to a message.
https://bugs.kde.org/show_bug.cgi?id=405843 Simon changed: What|Removed |Added CC||si...@ergotech.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 --- Comment #15 from Nicofo --- It crashes digikam: $ export LD_PRELOAD=$LD_PRELOAD:/usr/lib64/libssl3.so $ ./digikam-6.1.0-git-20190323T220709-x86-64.appimage libfontconfig.so libfreetype.so libudev.so -- digiKam AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application -- Preloading shared libs: :/usr/lib64/libssl3.so digikam: /tmp/.mount_digikaiuWcKX/usr/lib/libnssutil3.so: version `NSSUTIL_3.38' not found (required by /usr/lib64/libssl3.so) -- You are receiving this mail because: You are watching all bug changes.