[krita] [Bug 401988] Crash on touching graphic tablet pen on canvas
https://bugs.kde.org/show_bug.cgi?id=401988 Boudewijn Rempt changed: What|Removed |Added CC||johnny.strom@linuxsolutions ||.fi --- Comment #18 from Boudewijn Rempt --- *** Bug 402844 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402844] Crash when putting down pencil on huion drawing tablet.
https://bugs.kde.org/show_bug.cgi?id=402844 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Boudewijn Rempt --- This is a bug in Qt 5.11.3 and 5.12. There's a workaround in 4.1.7.101, but apparently Debian doesn't package that yet. You can always use the appimage, which uses a version of Qt that isn't broken. *** This bug has been marked as a duplicate of bug 401988 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402844] New: Crash when putting down pencil on huion drawing tablet.
https://bugs.kde.org/show_bug.cgi?id=402844 Bug ID: 402844 Summary: Crash when putting down pencil on huion drawing tablet. Product: krita Version: 4.1.7 Platform: Debian testing OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: johnny.st...@linuxsolutions.fi Target Milestone: --- SUMMARY Crash when putting down pencil on huion drawing tablet. STEPS TO REPRODUCE 1. Start krita 2. Use huion pencil on the tablet 3. Crash OBSERVED RESULT Crash when using the huion pencil. Other applications do work with the huion pencil. The mouse do work. EXPECTED RESULT Not to crash. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: plasmashell 5.14.3 KDE Frameworks Version: Qt Version: 5.11.3 ADDITIONAL INFORMATION [New Thread 0x7fff8dffe700 (LWP 4662)] free(): double free detected in tcache 2 Thread 1 "krita" received signal SIGABRT, Aborted. 0x74baa85b in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) thread apply all backtrace Thread 36 (Thread 0x7fff8dffe700 (LWP 4662)): #0 0x72bc53d9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x74f9436c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x74f8c1d2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x74f93cd7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x72bbefa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x74c6c88f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 35 (Thread 0x7fff8d7fd700 (LWP 4661)): #0 0x72bc53d9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x74f9436c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x74f8c1d2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x74f93cd7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x72bbefa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x74c6c88f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 34 (Thread 0x7fff8cffc700 (LWP 4660)): #0 0x72bc53d9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x74f9436c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x74f8c1d2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x74f93cd7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x72bbefa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x74c6c88f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 33 (Thread 0x7fff5bff4700 (LWP 4659)): #0 0x72bc53d9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x74f9436c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x74f8c1d2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x74f93cd7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x72bbefa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x74c6c88f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 28 (Thread 0x7fffb0eef700 (LWP 4654)): #0 0x72bc53d9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x74f9436c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x74f8c1d2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x74f93cd7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x72bbefa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x74c6c88f in clone () from /lib/x86_64-linux-gnu/libc.so.6 --Type for more, q to quit, c to continue without paging-- Thread 27 (Thread 0x7fffb1ef1700 (LWP 4653)): #0 0x72bc53d9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x74f9436c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x74f8c1d2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x74f93cd7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x72bbefa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x74c6c88f in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 26 (Thread 0x7fffb16f0700 (LWP 4652)): #0 0x72bc53d9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
[kate] [Bug 402788] KWrite crashed while searching
https://bugs.kde.org/show_bug.cgi?id=402788 Lothar changed: What|Removed |Added CC||loh@googlemail.com --- Comment #1 from Lothar --- The search & replace stuff is recently heavy modified but has worked so far without trouble. Happens this in all files or some special? How big was it e.g. and what kind of type C++, HTML, (which highlighting), untypical many columns, what ever. Can you provide a test file when it is somehow special? >From master branch, last commit? -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 402409] Save the last session when the function created by default
https://bugs.kde.org/show_bug.cgi?id=402409 Baltasar changed: What|Removed |Added CC||bort...@kde-espana.es -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402764] Caps Lock as additional Super does not trigger Alt+F1 shortcut
https://bugs.kde.org/show_bug.cgi?id=402764 --- Comment #3 from Martin Flöser --- Could you please try to restart KWin? It's possible that we do not get informed about keymap changes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402650] Wayland touchscreen keyboard doesn't show up anymore
https://bugs.kde.org/show_bug.cgi?id=402650 --- Comment #4 from Martin Flöser --- (In reply to mihael.vercek from comment #2) > Created attachment 117269 [details] > output with WAYLAND_DEBUG=1 > > output is the same even without this flag You need to do this from the Wayland session, not from a tty. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402650] Wayland touchscreen keyboard doesn't show up anymore
https://bugs.kde.org/show_bug.cgi?id=402650 Martin Flöser changed: What|Removed |Added Attachment #117270|text/x-log |text/plain mime type|| -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402433] Google Maps Doesn't Zoom With Mouse Wheel
https://bugs.kde.org/show_bug.cgi?id=402433 --- Comment #3 from caulier.gil...@gmail.com --- under Mageia6.1, the lib64qt5webkit*-devel are the 5.212 alpha version, so a code not published at stable, later than 5.9.1 : https://github.com/qt/qtwebkit Look the branch 5.212 in git hub and last commit done in january 2018. I know that the maintainer of this component working for Digia left the project after than Qt team decide to promote QtWebEngine instead QtWebkit. Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402433] Google Maps Doesn't Zoom With Mouse Wheel
https://bugs.kde.org/show_bug.cgi?id=402433 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #2 from caulier.gil...@gmail.com --- Maik, The AppImage and the Windows version of QWebKit (not QWebView witch is the QML interface to native web browser), is the last one available 5.9.1, not the 5.5.0 : https://cgit.kde.org/digikam.git/tree/project/bundles/3rdparty/ext_qtwebkit/CMakeLists.txt#n13 https://github.com/mxe/mxe/blob/master/src/qtwebkit.mk#L11 Gilles -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 402843] New: Holdiays on digital clock crash plasmashell
https://bugs.kde.org/show_bug.cgi?id=402843 Bug ID: 402843 Summary: Holdiays on digital clock crash plasmashell Product: kdeplasma-addons Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: fuzzy-clock Assignee: plasma-b...@kde.org Reporter: darinsmil...@gmail.com Target Milestone: --- Neon Dev Unstable Plasma 5.14.8: Enabling holidays on digital clock causes plasma crash upon Apply. STEPS TO REPRODUCE 1. Right click on clock 2. Select Digital Clock settings | Calendar 3. Check the Holidays box and click Apply Plasma crashes immediately and will not restart. To recover, comment this line in ~/.config/plasma-org.kde.plasma.desktop-appletsrc: # enabledCalendarPlugins=/usr/lib/x86_64-linux-gnu/qt5/plugins/plasmacalendarplugins/holidaysevents.so OBSERVED RESULT Plasmashell crashes and will not restart. Error thrown: $ plasmashell & [1] 4046 darin@imagineNU:~$ org.kde.plasmaquick: Applet preload policy set to 1 file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:61:28: Unable to assign [undefined] to int file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:52:27: Unable to assign [undefined] to int trying to show an empty dialog KActivities: Database connection: "kactivities_db_resources_139651008317504_readonly" query_only: QVariant(qlonglong, 1) journal_mode:QVariant(QString, "wal") wal_autocheckpoint: QVariant(qlonglong, 100) synchronous: QVariant(qlonglong, 0) Closing SQL connection: "kactivities_db_resources_139651008317504_readonly" KActivities: Database connection: "kactivities_db_resources_139651008317504_readonly" query_only: QVariant(qlonglong, 1) journal_mode:QVariant(QString, "wal") wal_autocheckpoint: QVariant(qlonglong, 100) synchronous: QVariant(qlonglong, 0) Nothing to load - the client id is empty Nothing to load - the client id is empty Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion r [1]+ Exit 2 plasmashell EXPECTED RESULT no crashing and holidays on calendar SOFTWARE/OS VERSIONS Linux/KDE Plasma: Yes (available in About System) KDE Plasma Version: 5.14.8 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifyconfig] [Bug 393153] Knotify does not show the text to speech option
https://bugs.kde.org/show_bug.cgi?id=393153 --- 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.
[ktouch] [Bug 401735] ktouch does not work appropriately
https://bugs.kde.org/show_bug.cgi?id=401735 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401800] Even so I enabled pen pressure, pen pressure is not working
https://bugs.kde.org/show_bug.cgi?id=401800 Bug Janitor Service changed: What|Removed |Added Resolution|NOT A BUG |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 401787] Can't open mailbox
https://bugs.kde.org/show_bug.cgi?id=401787 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 394056] Falkon snap fails to start
https://bugs.kde.org/show_bug.cgi?id=394056 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Systemd KCM] [Bug 361558] No clear way to run Systemd KCM from terminal if systemsettings5 not installed
https://bugs.kde.org/show_bug.cgi?id=361558 --- 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.
[valgrind] [Bug 399584] Support macOS Mojave (10.14)
https://bugs.kde.org/show_bug.cgi?id=399584 ajafri changed: What|Removed |Added CC||ajafr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 402842] New: Can not print with kate and kwrite
https://bugs.kde.org/show_bug.cgi?id=402842 Bug ID: 402842 Summary: Can not print with kate and kwrite Product: kate Version: 18.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: mister.free...@laposte.net Target Milestone: --- SUMMARY I use archlinux, I can not print with kate (18.12.0-1 version) and kwrite, I get an error from cups : [CAPTFILTER] Input File Error If I use okular then I can print without problem, no problem also with libreoffice, so there is a problem for the print feature in kate and kwrite, my printer is a usb device "Canon LBP 3000" STEPS TO REPRODUCE 1. install kate (18.12.0-1 version) 2. use a usb printer device like canon lpb 3000 3. print a text from kate or kwrite 4. you will notice that the printer will refuse to print 5. if you try another software (okular, libreoffice) then you can print without problems OBSERVED RESULT no print with kate and kwrite EXPECTED RESULT the printer should print SOFTWARE/OS VERSIONS Linux/KDE Plasma: archlinux 64 bits, plasma-framework 5.53.0-1, plasma-desktop 5.14.4-2, kate 18.12.0-1 Qt Version: 5.12.0-1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402764] Caps Lock as additional Super does not trigger Alt+F1 shortcut
https://bugs.kde.org/show_bug.cgi?id=402764 --- Comment #2 from Dalton Durst --- Sure. Here's a Caps Lock press: >KeyPress event, serial 50, synthetic NO, window 0x4a1, >root 0x5d5, subw 0x0, time 567230, (64,-10), root:(64,791), >state 0x0, keycode 66 (keysym 0xffeb, Super_L), same_screen YES, >XLookupString gives 0 bytes: >XmbLookupString gives 0 bytes: >XFilterEvent returns: False > >KeyRelease event, serial 50, synthetic NO, window 0x4a1, >root 0x5d5, subw 0x0, time 567654, (64,-10), root:(64,791), >state 0x40, keycode 66 (keysym 0xffeb, Super_L), same_screen YES, >XLookupString gives 0 bytes: >XFilterEvent returns: False And here's a real Super key: >KeyPress event, serial 50, synthetic NO, window 0x4a1, >root 0x5d5, subw 0x0, time 570606, (64,-10), root:(64,791), >state 0x0, keycode 133 (keysym 0xffeb, Super_L), same_screen YES, >XKeysymToKeycode returns keycode: 66 >XLookupString gives 0 bytes: >XmbLookupString gives 0 bytes: >XFilterEvent returns: False > >KeyRelease event, serial 51, synthetic NO, window 0x4a1, >root 0x5d5, subw 0x0, time 570782, (64,-10), root:(64,791), >state 0x40, keycode 133 (keysym 0xffeb, Super_L), same_screen YES, >XKeysymToKeycode returns keycode: 66 >XLookupString gives 0 bytes: >XFilterEvent returns: False -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 372745] Segmentation fault on connect to phone in Debian sid (kdeconnect 1.0.1-1)
https://bugs.kde.org/show_bug.cgi?id=372745 Ariel Garcia changed: What|Removed |Added Version|unspecified |1.3.3 Platform|Other |Debian testing --- Comment #7 from Ariel Garcia --- I still see this bug in kdeconnect 1.3.3, Debian testing (see backtrace in Bug #402839). Any hint how to "workaround" this at the network level? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 401739] Kmail crashes while open on fresh start system, attempting to reopen it results in the completely empty application window, no mailbox or mail message available
https://bugs.kde.org/show_bug.cgi?id=401739 --- Comment #6 from avlas --- If bug 402253 is truly a duplicate of this, the affected users can benefit of the workaround I found. See https://bugs.kde.org/show_bug.cgi?id=402253#c14 and https://bugs.kde.org/show_bug.cgi?id=402253#c16 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 402839] kdeconnectd segfaults as soon as the phone tries to connect
https://bugs.kde.org/show_bug.cgi?id=402839 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 372745 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 372745] Segmentation fault on connect to phone in Debian sid (kdeconnect 1.0.1-1)
https://bugs.kde.org/show_bug.cgi?id=372745 Christoph Feck changed: What|Removed |Added CC||aog20...@gmail.com --- Comment #6 from Christoph Feck --- *** Bug 402839 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400010] kdeconnectd closed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400010 Christoph Feck changed: What|Removed |Added CC||chr...@protonmail.com --- Comment #14 from Christoph Feck --- *** Bug 401755 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401755] /usr/lib/kdeconnectd crashes on connection to phone
https://bugs.kde.org/show_bug.cgi?id=401755 Christoph Feck changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #10 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 400010 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 367480] Crash inside Baloo::PostingCodec::decode
https://bugs.kde.org/show_bug.cgi?id=367480 --- Comment #126 from Wantoyo --- Created attachment 117274 --> https://bugs.kde.org/attachment.cgi?id=117274=edit New crash information added by DrKonqi baloo_file (5.53.0) using Qt 5.12.0 - What I was doing when the application crashed: I'm just startup my system login and suddenly show this bug on pupup notifications -- Backtrace (Reduced): #7 0x7f382076d8cd in memcpy (__len=203667448, __src=0x7ef80c2f44a8, __dest=) at /usr/include/bits/string_fortified.h:34 #8 Baloo::PostingCodec::decode (this=this@entry=0x7f381a1438c7, arr=...) at /usr/src/debug/baloo5-5.53.0-1.1.x86_64/src/codecs/postingcodec.cpp:42 #9 0x7f382075aee9 in Baloo::PostingDB::get (this=this@entry=0x7f381a1439b0, term=...) at /usr/src/debug/baloo5-5.53.0-1.1.x86_64/src/engine/postingdb.cpp:100 #10 0x7f382076b13a in Baloo::WriteTransaction::commit (this=0x7ef80c003400) at /usr/src/debug/baloo5-5.53.0-1.1.x86_64/src/engine/writetransaction.cpp:275 #11 0x7f3820761712 in Baloo::Transaction::commit (this=this@entry=0x7f381a143ae0) at /usr/src/debug/baloo5-5.53.0-1.1.x86_64/src/engine/transaction.cpp:269 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 367480] Crash inside Baloo::PostingCodec::decode
https://bugs.kde.org/show_bug.cgi?id=367480 Wantoyo changed: What|Removed |Added CC||wanto...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402841] New: Animation curve opacity doesn't display correctly during playback and sometimes during timeline scrolling
https://bugs.kde.org/show_bug.cgi?id=402841 Bug ID: 402841 Summary: Animation curve opacity doesn't display correctly during playback and sometimes during timeline scrolling Product: krita Version: 4.1.5 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: tristanbaymu...@gmail.com Target Milestone: --- Created attachment 117273 --> https://bugs.kde.org/attachment.cgi?id=117273=edit gif of the problem STEPS TO REPRODUCE 1. set up a new krita document 2. show the transparent layer (layer 2) in the timeline 3. create a new frame and opacity keyframe for that layer 4. draw on the frame so there's a visible difference than before 5. make some opacity keyframes so krita animates the opacity from frame to frame 6. scroll before and after hitting play to see the difference (as well as watching what happens while it's playing) OBSERVED RESULT [see middle of attachment] EXPECTED RESULT [see beginning of attachment] SOFTWARE/OS VERSIONS Windows: 10 Note: because of the really small file size limit, the gif had to basically be compressed/resized to microscopic proportions so the text is probably hard to read, and you may have to put it into your web browser to zoom in on it -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 402840] The application bar immediately hides then appears again on hover
https://bugs.kde.org/show_bug.cgi?id=402840 felixbra...@quicknet.nl changed: What|Removed |Added URL||https://gfycat.com/MajorExe ||mplaryAffenpinscher -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 402840] New: The application bar immediately hides then appears again on hover
https://bugs.kde.org/show_bug.cgi?id=402840 Bug ID: 402840 Summary: The application bar immediately hides then appears again on hover Product: latte-dock Version: 0.8.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: felixbra...@quicknet.nl Target Milestone: --- SUMMARY The docks application bar immediately hides, then reappears when hovering. This only appears to happen when the dock is positioned on the left side of the screen STEPS TO REPRODUCE 1. Set the location of the dock to "Left", the alignment to "Center" and the visibility to "Dodge all Windows" or "Dodge Active" 2. Move the cursor left side of the screen to allow the dock to appear OBSERVED RESULT The dock immediately hides itself and then appears quickly sometimes. EXPECTED RESULT The dock should appear and not hide immediately. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION It seems to depend on the speed of the cursor moving to the left side. The most consistent way seems to be to move the cursor the the pixel right before the hover of the dock is triggered. Then moving it one pixel on the left to trigger it. See this gif: https://gfycat.com/MajorExemplaryAffenpinscher for a visual explanation of how to trigger this bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400010] kdeconnectd closed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400010 --- Comment #13 from Ariel Garcia --- (In reply to Ariel Garcia from comment #11) > (In reply to Christoph Feck from comment #8) > > Backtrace from comment #7 is completely unrelated to backtrace from comment > > #1. > > This means i should open a new bug right? Submitted Bug #402839 for my case. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 402839] New: kdeconnectd segfaults as soon as the phone tries to connect
https://bugs.kde.org/show_bug.cgi?id=402839 Bug ID: 402839 Summary: kdeconnectd segfaults as soon as the phone tries to connect Product: kdeconnect Version: 1.3.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: aog20...@gmail.com Target Milestone: --- Created attachment 117272 --> https://bugs.kde.org/attachment.cgi?id=117272=edit Backtrace segfault in Debian testing SUMMARY kdeconnectd segfaults as soon as my phone tries to connect (pairing did work). STEPS TO REPRODUCE 1. Have the KDEconnect app installed in the phone, pair it (this worked). 2. Have the KDEconnect app running in the phone. 3. Allow the phone to connect to the local network over wifi. OBSERVED RESULT I get a crash notification for kdeconnectd in my KDE desktop. EXPECTED RESULT No crash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian buster/testing KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION Will attach backtrace. -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 378481] Entering **/**/17 in a date field saves as the year 1917
https://bugs.kde.org/show_bug.cgi?id=378481 Jarosław Staniek changed: What|Removed |Added Status|CONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 378481] Entering **/**/17 in a date field saves as the year 1917
https://bugs.kde.org/show_bug.cgi?id=378481 --- Comment #5 from Jarosław Staniek --- Fix in progress. Sample info KEXI shows on output when LC_TIME=en_US is used: Two-digit year formats for dates are not allowed so KEXI will alter date format "M/d/yy" by replacing two-digits years with four-digits for accuracy. New input format is "M/d/", new input mask is "90/90/" and new output format is "M/d/". This change will affect input and display. Set the General/AllowTwoDigitYearFormats option to true to enable use of two-digit year formats. -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 378481] Entering **/**/17 in a date field saves as the year 1917
https://bugs.kde.org/show_bug.cgi?id=378481 Jarosław Staniek changed: What|Removed |Added Assignee|kexi-b...@kde.org |stan...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401755] /usr/lib/kdeconnectd crashes on connection to phone
https://bugs.kde.org/show_bug.cgi?id=401755 Ariel Garcia changed: What|Removed |Added CC||aog20...@gmail.com --- Comment #9 from Ariel Garcia --- Possibly a duplicate of bug #400010. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400010] kdeconnectd closed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400010 Ariel Garcia changed: What|Removed |Added Component|common |kcm --- Comment #12 from Ariel Garcia --- The backtrace of Bug #401755 does however look very similar to this one, maybe also a duplicate. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386086] [Wayland] Firefox flatpak crashed plasma.
https://bugs.kde.org/show_bug.cgi?id=386086 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #4 from David Edmundson --- Crash is in Qt please reopen if seen with Qt > 5.12 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398272] Plasma crashed after changing panel menu from Kicker to Kickoff on Wayland
https://bugs.kde.org/show_bug.cgi?id=398272 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk Resolution|--- |UPSTREAM --- Comment #1 from David Edmundson --- Crash is in Qt, please reopen if seen with Qt5.12 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390727] Plasmashell does not cover 1440p monitor and behaves strangely
https://bugs.kde.org/show_bug.cgi?id=390727 --- Comment #16 from David Edmundson --- Output implies Qt is wrong. Please reopen if you still have an issue with Qt >=5.12 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391271] When loging out wayland session, do the windows get a proper close signal?
https://bugs.kde.org/show_bug.cgi?id=391271 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #6 from David Edmundson --- Normally ksmserver terminates everything - but naturally that only happens on X. Will need a cross toolkit solution and changes in Qt. Roman was quite interested in this work at some point. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374651] Tray based app cannot run properly
https://bugs.kde.org/show_bug.cgi?id=374651 --- Comment #7 from David Edmundson --- We also don't force QT_QPA_PLATFORM anymore, so older Qt will use XCB by default anyway. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374651] Tray based app cannot run properly
https://bugs.kde.org/show_bug.cgi?id=374651 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM CC||k...@davidedmundson.co.uk --- Comment #6 from David Edmundson --- If it bundles its own Qt, there's not much we can do. Once they upgrade they'll get a Qt with built in SNI support. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378694] applications menu cutted
https://bugs.kde.org/show_bug.cgi?id=378694 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- Is this still an issue? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400010] kdeconnectd closed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400010 --- Comment #11 from Ariel Garcia --- (In reply to Christoph Feck from comment #8) > Backtrace from comment #7 is completely unrelated to backtrace from comment > #1. This means i should open a new bug right? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400010] kdeconnectd closed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400010 Christoph Feck changed: What|Removed |Added CC||da...@erdius.net --- Comment #10 from Christoph Feck --- *** Bug 402430 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400010] kdeconnectd closed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400010 Christoph Feck changed: What|Removed |Added CC||andythe_gr...@pm.me --- Comment #9 from Christoph Feck --- *** Bug 402799 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 402799] KDE connect Segmentation Fault.
https://bugs.kde.org/show_bug.cgi?id=402799 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 400010 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 402430] kdeconnect crashing
https://bugs.kde.org/show_bug.cgi?id=402430 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 400010 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400010] kdeconnectd closed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400010 --- Comment #8 from Christoph Feck --- Backtrace from comment #7 is completely unrelated to backtrace from comment #1. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 --- Comment #94 from David Edmundson --- >Uh, no. KDE applications are expected to use KIO. Absolutely, I wasn't suggesting otherwise. What I'm saying is that any code paths that check the url.scheme() == file and take a different path need to still go through KIO. I can think of at least 3 examples in plasma over the last year where this happened. Otherwise putting FUSE mounts on the system has the risk of making our own apps worse. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400010] kdeconnectd closed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400010 --- Comment #7 from Ariel Garcia --- Created attachment 117271 --> https://bugs.kde.org/attachment.cgi?id=117271=edit Backtrace segfault in Debian testing As soon as my phone connects to the local net and the KDEconnect app tries to contact my desktop, kdeconnectd crashes. This is the backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400010] kdeconnectd closed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400010 --- Comment #6 from Ariel Garcia --- There are some other similar bugs regarding kdeconnectd crashing, but relate to older versions, so they are probably a different crash. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 402799] KDE connect Segmentation Fault.
https://bugs.kde.org/show_bug.cgi?id=402799 --- Comment #2 from Ariel Garcia --- There are some other similar bugs regarding kdeconnectd crashing, but relate to older versions, so they are probably a different crash. Uploading my log in Bug #400010 since it is the oldest of the three bugs affecting kdeconnect 1.3.3. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 402430] kdeconnect crashing
https://bugs.kde.org/show_bug.cgi?id=402430 --- Comment #2 from Ariel Garcia --- There are some other similar bugs regarding kdeconnectd crashing, but relate to older versions, so they are probably a different crash. Uploading my log in Bug #400010 since it is the oldest of the three bugs affecting kdeconnect 1.3.3. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 402430] kdeconnect crashing
https://bugs.kde.org/show_bug.cgi?id=402430 Ariel Garcia changed: What|Removed |Added CC||aog20...@gmail.com --- Comment #1 from Ariel Garcia --- Possibly the same as Bug #402799 (Suse) and Bug #400010 (Neon). I also observe this crash in Debian testing: KDEconnect is completely unusable, since it crashes as soon as my android phone tries to connect. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400010] kdeconnectd closed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400010 Ariel Garcia changed: What|Removed |Added CC||aog20...@gmail.com --- Comment #5 from Ariel Garcia --- Possibly the same as Bug #402799 (Suse) and Bug #402430 (Arch). I also observe this crash in Debian testing: KDEconnect is completely unusable, since it crashes as soon as my android phone tries to connect. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 402799] KDE connect Segmentation Fault.
https://bugs.kde.org/show_bug.cgi?id=402799 Ariel Garcia changed: What|Removed |Added CC||aog20...@gmail.com --- Comment #1 from Ariel Garcia --- Possibly the same as Bug #402430 (Arch) and Bug #400010 (Neon). I also observe this crash in Debian testing: KDEconnect is completely unusable, since it crashes as soon as my android phone tries to connect. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 357239] Decrease/Increase Thumbnail size Icons are misleading
https://bugs.kde.org/show_bug.cgi?id=357239 Johannes Zarl-Zierl changed: What|Removed |Added Latest Commit||https://commits.kde.org/kph ||otoalbum/899b0f643924aac62a ||49dd85e2f9aa1b3ef806b6 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Johannes Zarl-Zierl --- Git commit 899b0f643924aac62a49dd85e2f9aa1b3ef806b6 by Johannes Zarl-Zierl. Committed on 03/01/2019 at 22:25. Pushed by johanneszarl into branch 'master'. Replace thumbnail storage size buttons with settings shortcut. Reasons for the change: - Decrease clutter - Changing storage size is quite expensive and not done often M +8-31 MainWindow/StatusBar.cpp M +2-3MainWindow/StatusBar.h M +5-0MainWindow/Window.cpp https://commits.kde.org/kphotoalbum/899b0f643924aac62a49dd85e2f9aa1b3ef806b6 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 365420] Usage of "Adapt signature" to rename argument in constructor inserts keyword "void" in its declaration
https://bugs.kde.org/show_bug.cgi?id=365420 Piotr Mierzwinski changed: What|Removed |Added Version|5.1.1 |5.3.1 Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #6 from Piotr Mierzwinski --- Either I found new case when constructor is broken by inserting void on its begin or this is just regression. Initial code looks like below: Header file (myclass.h): public: MyClass(); cpp file (myclass.cpp): MyClass::MyClass() { // some code } Steps to reproduce: 1. instead of "// some code" in definition of constructor put code like below: if (bParam) ; 2. copy to clipboard string like: "bool bParam" 3. paste copied string as parameter for constructor in cpp file. After that definition will look like this: MyClass::MyClass( bool bParam ) 4. Click on end above line, KDevelop will show two solutions, suggesting how to fix the code 5. Click into the first one and after click into the second one 6. Switch to header file CURRENT RESULT: public: void MyClass( bool bParam ); EXPECTED RESULT: public: MyClass( bool bParam ); -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402433] Google Maps Doesn't Zoom With Mouse Wheel
https://bugs.kde.org/show_bug.cgi?id=402433 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Maik Qualmann --- I suspect a problem with the used QWebView (WebKit) version. I can confirm the problem for the AppImage and the Windows version. Under my native Linux, the mouse wheel zoom works with both QWebView and of course QWebEngine. I believe I have read that openSUSE QWebView ships with updates and not the original version, which has stopped at Qt-5.5. Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402650] Wayland touchscreen keyboard doesn't show up anymore
https://bugs.kde.org/show_bug.cgi?id=402650 --- Comment #2 from mihael.ver...@gmail.com --- Created attachment 117269 --> https://bugs.kde.org/attachment.cgi?id=117269=edit output with WAYLAND_DEBUG=1 output is the same even without this flag -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402650] Wayland touchscreen keyboard doesn't show up anymore
https://bugs.kde.org/show_bug.cgi?id=402650 --- Comment #3 from mihael.ver...@gmail.com --- Created attachment 117270 --> https://bugs.kde.org/attachment.cgi?id=117270=edit session log -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390330] Calendar top column does not contain all the days. Only Sat, Sun
https://bugs.kde.org/show_bug.cgi?id=390330 --- Comment #8 from Chris Holland --- Git commit e5949866bb8f019a416930e2eb58bea363ff0ebf by Chris Holland. Committed on 03/01/2019 at 21:58. Pushed by cholland into branch 'master'. [Calendar] Expose firstDayOfWeek in MonthView This allows for calendar widgets to override the Locale. Users may want to start the week on a Sunday, Saturday, or Monday without changing their locale's date formatting. Differential Revision: https://phabricator.kde.org/D15321 M +1-0src/declarativeimports/calendar/qml/MonthView.qml https://commits.kde.org/plasma-framework/e5949866bb8f019a416930e2eb58bea363ff0ebf -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 402837] kpat / kpatience gives an error on "Help about Freecell" (or other Solitaire variants)
https://bugs.kde.org/show_bug.cgi?id=402837 --- Comment #3 from Yuri Chornoivan --- (In reply to Albert Astals Cid from comment #2) > I'd say Yuri broke this with his changes to khelpclient in > https://phabricator.kde.org/D16350 And I'd say this was broken beforehand (not by me even this time). It does not work in Mageia 6 (Applications 17.12, KF 5.42). Just does not work differently (shows index.html when trying to show /usr/share/doc/HTML/en//kpat/index.html#freecell). It is a bug in KPat. I'll try to create a review request to fix it soon. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 399646] Brightness control adjusts the wrong backlight control (multiple GPUs)
https://bugs.kde.org/show_bug.cgi?id=399646 Jason Tibbitts changed: What|Removed |Added CC||ti...@math.uh.edu --- Comment #1 from Jason Tibbitts --- I can confirm with a Thinkpad W530. My situation is exactly the same. I'm running Fedora 29 which has powerdevil 5.14.4 currently. I haven't previously tried to run Linux on one of these laptops so I have no idea if this worked at some point in the past. Supposedly (from a quick chat with Matthew Garrett on IRC) the desktop environment needs to figure out which output port needs to be adjusted, follow that to the device (graphics card) and then look for the backlight in /sys/class/backlight which corresponds to the device. I have to give this laptop to a user, but I think I have another on hand to test if there's a patch I can try. -- You are receiving this mail because: You are watching all bug changes.
[kgeography] [Bug 337964] Map not updated for Russia
https://bugs.kde.org/show_bug.cgi?id=337964 Albert Astals Cid changed: What|Removed |Added Latest Commit||https://commits.kde.org/kge ||ography/8119d8bb874f5ee01e9 ||fa9044d04d7bda655adc5 Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #4 from Albert Astals Cid --- Git commit 8119d8bb874f5ee01e9fa9044d04d7bda655adc5 by Albert Astals Cid, on behalf of Laurent G. Committed on 03/01/2019 at 21:41. Pushed by aacid into branch 'Applications/18.12'. Update Moscow federal city and oblast Subscribers: kde-edu Tags: #kde_edu Differential Revision: https://phabricator.kde.org/D17950 M +---data/russia_subjects.png https://commits.kde.org/kgeography/8119d8bb874f5ee01e9fa9044d04d7bda655adc5 -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 402837] kpat / kpatience gives an error on "Help about Freecell" (or other Solitaire variants)
https://bugs.kde.org/show_bug.cgi?id=402837 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org, ||mon...@kde.org, ||yurc...@ukr.net --- Comment #2 from Albert Astals Cid --- I'd say Yuri broke this with his changes to khelpclient in https://phabricator.kde.org/D16350 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 399646] Brightness control adjusts the wrong backlight control (multiple GPUs)
https://bugs.kde.org/show_bug.cgi?id=399646 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 378481] Entering **/**/17 in a date field saves as the year 1917
https://bugs.kde.org/show_bug.cgi?id=378481 Bug 378481 depends on bug 369518, which changed state. Bug 369518 Summary: Input and display of Date/Time/Date Time values broken https://bugs.kde.org/show_bug.cgi?id=369518 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 369518] Input and display of Date/Time/Date Time values broken
https://bugs.kde.org/show_bug.cgi?id=369518 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 369518] Input and display of Date/Time/Date Time values broken
https://bugs.kde.org/show_bug.cgi?id=369518 Jarosław Staniek changed: What|Removed |Added Latest Commit||https://phabricator.kde.org ||/R71:e43e8e4a9c05bfa5101e4a ||7ea7c4949c1f9eaab7 Target Milestone|3.2 |--- Version Fixed In||3.0.0 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Jarosław Staniek --- Apparently fixed in 3.0.0 stable already :) https://phabricator.kde.org/R71:e43e8e4a9c05bfa5101e4a7ea7c4949c1f9eaab7 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 355756] KPA settings dialog mangles annotation dialog layout and produces strange warning
https://bugs.kde.org/show_bug.cgi?id=355756 Johannes Zarl-Zierl changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||4.7.1 Resolution|--- |FIXED --- Comment #18 from Johannes Zarl-Zierl --- I think this is no longer present in current versions of KPhotoAlbum. I'm therefore closing it. Please reopen it if you think my assessment is incorrect/incomplete. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402809] Clicking on "Import" toolbar button in import preview does nothing
https://bugs.kde.org/show_bug.cgi?id=402809 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #3 from Maik Qualmann --- The selection of the action depending on the image selection is bad, because after the start of import always the first image is selected. I think "Download New" is the best choice for the most users. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402809] Clicking on "Import" toolbar button in import preview does nothing
https://bugs.kde.org/show_bug.cgi?id=402809 Maik Qualmann changed: What|Removed |Added Version Fixed In||6.0.0 Latest Commit||https://commits.kde.org/dig ||ikam/8d577da6a46d8fa1113a46 ||f2958ab08fc34b9321 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Maik Qualmann --- Git commit 8d577da6a46d8fa1113a46f2958ab08fc34b9321 by Maik Qualmann. Committed on 03/01/2019 at 20:58. Pushed by mqualmann into branch 'master'. use download new as default action for the download tool button FIXED-IN: 6.0.0 M +2-1NEWS M +3-0core/utilities/import/main/importui.cpp https://commits.kde.org/digikam/8d577da6a46d8fa1113a46f2958ab08fc34b9321 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 347702] OpenGL viewer
https://bugs.kde.org/show_bug.cgi?id=347702 Johannes Zarl-Zierl changed: What|Removed |Added Status|REPORTED|RESOLVED CC||johan...@zarl-zierl.at Resolution|--- |UNMAINTAINED --- Comment #5 from Johannes Zarl-Zierl --- It seems that the OpenGL image viewer in KIPI plugins has been discontinued. I'm closing this bug - please reopen if this was in error… -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 402819] online search can't use ieeexplore engine
https://bugs.kde.org/show_bug.cgi?id=402819 Thomas Fischer changed: What|Removed |Added Latest Commit||d68693a647ff15a3b71d2699bfc ||504d2e2e3dc7f Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED Version Fixed In||0.8.2 --- Comment #1 from Thomas Fischer --- I am quite sure that this problem has been fixed in the upcoming version 0.8.2. Please check and verify yourself: 1. Get 'run-kbibtex.sh' from here: https://cgit.kde.org/scratch/thomasfischer/kbibtex-related.git/tree/run 2. Run this script as follows: bash run-kbibtex.sh https://anongit.kde.org/kbibtex.git kbibtex/0.8 Some details on the script are provided in the README.txt file: https://cgit.kde.org/scratch/thomasfischer/kbibtex-related.git/tree/run/README.txt -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 374608] KphotoAlbum is not multithreaded
https://bugs.kde.org/show_bug.cgi?id=374608 Johannes Zarl-Zierl changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Johannes Zarl-Zierl --- I still think that your problem is IO of your system. Either way, we have greatly improved the performance for reading new images in version 5.4 (and yes, we do use multithreading). I think this can be closed... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402552] Crash of plasmashell in SwitchWindow::makeMenu() on latest git opensuse packages ( current day 25-12-2018)
https://bugs.kde.org/show_bug.cgi?id=402552 Nate Graham changed: What|Removed |Added Version Fixed In||5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 402838] New: Strange placing of spaces while saving multiline strings
https://bugs.kde.org/show_bug.cgi?id=402838 Bug ID: 402838 Summary: Strange placing of spaces while saving multiline strings Product: lokalize Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: sdepi...@gmail.com Reporter: mario.blaetterm...@gmail.com CC: sha...@ukr.net Target Milestone: --- SUMMARY While saving a file, Lokalize behaves some odd in comparison with other translations editors. For all multiline strings (which are dynamically wrapped at 80 characters as usual) a whitespace character gets not placed at the end of a wrapped line, but at teh beginning of the next one. STEPS TO REPRODUCE 1. Open a po file which has some already translated multiline strings. 2. Change one of that strings. 3. Save the file. OBSERVED RESULT All strings changed by Localize get the whitespaces at the beginning of the line, like in the following string: #. type: Plain text msgid "" "When writing scripts that need to decompress files, it is recommended to " "always use the name B with appropriate arguments (B or B) instead of the names B and B." msgstr "" "Beim Schreiben von Skripten, die Dateien dekomprimieren müssen, wird es" " empfohlen, immer den Namen B mit den entsprechenden Argumenten B" " oder B) anstelle der Namen B und B zu verwenden." EXPECTED RESULT The whitespaces should be at the end of the lines. The same string as above after launching "msgcat -w 80": #. type: Plain text msgid "" "When writing scripts that need to decompress files, it is recommended to " "always use the name B with appropriate arguments (B or B) " "instead of the names B and B." msgstr "" "Beim Schreiben von Skripten, die Dateien dekomprimieren müssen, wird es " "empfohlen, immer den Namen B mit den entsprechenden Argumenten B " "oder B) anstelle der Namen B und B zu verwenden." I don't know if it's essential for the compatibility that the files are not fully canonical (in comparison with Poedit or Gnome Translation Editor), but the effect of a basic command line tool like msgcat shows me that it's at least a bit strange. Maybe it could lead to undesired behavior in other environments which parse *.po files. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel 4.20.0 (Archlinux) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53.0 Qt Version: 5.12.0 Lokalize Version: 18.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 402837] kpat / kpatience gives an error on "Help about Freecell" (or other Solitaire variants)
https://bugs.kde.org/show_bug.cgi?id=402837 Shlomi Fish changed: What|Removed |Added See Also||https://bugs.mageia.org/sho ||w_bug.cgi?id=24120 --- Comment #1 from Shlomi Fish --- Add link to downstream bug -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 402837] New: kpat / kpatience gives an error on "Help about Freecell" (or other Solitaire variants)
https://bugs.kde.org/show_bug.cgi?id=402837 Bug ID: 402837 Summary: kpat / kpatience gives an error on "Help about Freecell" (or other Solitaire variants) Product: kpat Version: unspecified Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: co...@kde.org Reporter: shlo...@shlomifish.org CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY kpat / kpatience gives an error on "Help about Freecell" (or "Help about" other Solitaire variants) It gives this error: <<< Could not find filename freecell.html in /usr/share/doc/HTML/en//kpat/freecell.html. >>> Version-Release number of selected component (if applicable): Cauldron. I have both kpat and kpat-handbook installed. How reproducible: Always. STEPS TO REPRODUCE 1. start kpat. 2. Select Freecell. 3. On the menubar, select Help -> Help with Freecell. 4. error. OBSERVED RESULT error EXPECTED RESULT Display the rules for the solitaire variant. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Mageia v7 x86-64 (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402827] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=402827 Martin Flöser changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO --- Comment #1 from Martin Flöser --- Unfortunately the backtrace is lacking debug. If you are able to reproduce please install debug packages and try to get a backtrace. Best chance is to attach to running KWin through ssh. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385842] slow transitions after splitting audio from clip
https://bugs.kde.org/show_bug.cgi?id=385842 --- Comment #5 from S. Christian Collins --- So I see that audio clips are now split from video automatically in the current kdenlive nightly, so I can no longer compare transitions with/without the split. However, I can compare the nightly performance vs. 18.12.0, and here are the transition results: * 18.12.0 video clips with audio integrated: full FPS, 16% CPU usage. * 18.12.0 audio split to separate tracks: very low FPS, sound breaks up and playback rate slows considerably, 58% CPU usage. * 2019-1-3 nightly with audio auto-split to separate tracks: very low FPS, but audio and playback speed are normal, 16% CPU usage. (FYI, I have an i7 with hyperthreading, so the CPU usage numbers are not fully accurate.) So, the experience has improved in regards to CPU usage and playback speed, but FPS is still not near where it is with the audio integrated with the video clip as it is in early versions of Kdenlive. Also, what happened to the single-click dissolve transition? I used to be able to click on the corner of a video clip to add a dissolve transition with the clip beneath it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402535] Krita memory leaks or endless loop when using freehand brush with perspective assistant
https://bugs.kde.org/show_bug.cgi?id=402535 --- Comment #2 from genosim...@gmail.com --- Hi, i created a youtube video with me showing the bug: https://www.youtube.com/watch?v=EEmA1dGu3sU . It is very reliable to reproduce, just requires some specific setup to happen. I hope it helps a bit -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 402720] Kate hangs when trying to highlight some Wesnoth configuration files
https://bugs.kde.org/show_bug.cgi?id=402720 Nibaldo G. changed: What|Removed |Added Version Fixed In||5.54.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 391115] Very slow search, full text search (FTS) proposition for huge speedup.
https://bugs.kde.org/show_bug.cgi?id=391115 --- Comment #6 from Maik Qualmann --- Git commit abd32eefb24ac94c6a5343869578eabdd9ec9f9d by Maik Qualmann. Committed on 03/01/2019 at 19:43. Pushed by mqualmann into branch 'master'. use ReadWriteLock for the CollectionManager Loading a large item view is now about 4x faster here with MySQL Related: bug 391840 M +9-9core/libs/database/collection/collectionmanager_album.cpp M +43 -39 core/libs/database/collection/collectionmanager_location.cpp M +2-0core/libs/database/collection/collectionmanager_p.h https://commits.kde.org/digikam/abd32eefb24ac94c6a5343869578eabdd9ec9f9d -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 391840] Timeline does not show any pictures if range is too big
https://bugs.kde.org/show_bug.cgi?id=391840 --- Comment #8 from Maik Qualmann --- Git commit abd32eefb24ac94c6a5343869578eabdd9ec9f9d by Maik Qualmann. Committed on 03/01/2019 at 19:43. Pushed by mqualmann into branch 'master'. use ReadWriteLock for the CollectionManager Loading a large item view is now about 4x faster here with MySQL Related: bug 391115 M +9-9core/libs/database/collection/collectionmanager_album.cpp M +43 -39 core/libs/database/collection/collectionmanager_location.cpp M +2-0core/libs/database/collection/collectionmanager_p.h https://commits.kde.org/digikam/abd32eefb24ac94c6a5343869578eabdd9ec9f9d -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 402720] Kate hangs when trying to highlight some Wesnoth configuration files
https://bugs.kde.org/show_bug.cgi?id=402720 Dominik Haumann changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/syn ||tax-highlighting/c276c7003d ||3569001b12e8095e896da88f134 ||13e --- Comment #3 from Dominik Haumann --- Git commit c276c7003d3569001b12e8095e896da88f13413e by Dominik Haumann, on behalf of Nibaldo González. Committed on 03/01/2019 at 19:35. Pushed by dhaumann into branch 'master'. WML: fix infinite loop in contexts switch & only highlight tags with valid names Summary: In the `wml.xml` file an infinite context switch between `section` and `error` is generated, through `lineEndContext`: in a line break, the `section` context sends to `error` and then this is #poped in the line break, causing an infinite cycle. This causes that Kate freezes. This is reproducible by typing the `[` character and then a line break. This bug is reproducible only in KSyntaxHighlighting, since in KF5.48 there is no problem. It's probably necessary to add a guard that avoids infinite context changes. Also, the WML highlighter is a little old and I have seen some problems in sample files. The highlighter considers all content between `[` and `]` as tag. According to the documentation [1]: ``` Also, tag and key names follow a special format. They will contain only alphanumeric characters and underscores; in particular, they will not contain +, -, or whitespace. ``` Considering this, and based on the VSCode highlighter, I modified the code so that only tags with valid names are highlighted. **References:** * [1] Wesnoth Wiki. SyntaxWML, Tag and Attribute Structures: https://wiki.wesnoth.org/SyntaxWML#Tag_and_Attribute_Structures * [2] Wesnoth Markup Language syntax highlightning for VS Code: https://github.com/Byteron/wml , https://marketplace.visualstudio.com/items?itemName=Bitron.wml Reviewers: #framework_syntax_highlighting, dhaumann, cullmann Reviewed By: #framework_syntax_highlighting, dhaumann Subscribers: kwrite-devel, kde-frameworks-devel Tags: #kate, #frameworks Differential Revision: https://phabricator.kde.org/D17891 A +101 -0autotests/folding/test.pbl.fold A +108 -0autotests/html/test.pbl.html A +101 -0autotests/input/test.pbl A +101 -0autotests/reference/test.pbl.ref M +14 -10 data/syntax/wml.xml https://commits.kde.org/syntax-highlighting/c276c7003d3569001b12e8095e896da88f13413e -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402807] Progress manager doesn't seem to be involved in the fingerprint scanning (v6.0 beta 3)
https://bugs.kde.org/show_bug.cgi?id=402807 --- Comment #3 from b...@wt.net --- Maik, thanks for the update but if the search for affected images takes so long why not fork that to another (interruptible) thread as well? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 402709] scheduler does not start a sequence when frames exist although repeat until terminated is selected
https://bugs.kde.org/show_bug.cgi?id=402709 --- Comment #2 from Wolfgang Reissenberger --- The latest commit on the master branch is 2bd1ad0433ce9a0cabce2b693ebc4bc50be6e703 It seems like lightFramesRequired is not used properly, since it does not take into account, whether the image sequence is multiply run. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 --- Comment #93 from Konstantin Kharlamov --- (In reply to Christoph Feck from comment #92) > > First pre-requisite step is making all KDE apps robust to blocking calls on > > files which it thinks are safe as they're on the local file system. > > Uh, no. KDE applications are expected to use KIO. You would have to fix all > _other_ applications, which don't use the KIO API. I guess applications > using GIO are also safe, because (I hope) GIO was also designed > asynchronous. But POSIX API is synchronous, and users of those applications > just have to live with UI hangs unless they use separate threads for IO. It's okay to use KIO, nobody advises to drop it. Idea is just to improve a usability on FUSE mounts a little bit. You can't reasonably expect every existing app out there to implement a new protocol just to make it compatible with KDE. Also, imagine how bloated servers would become if every terminal utility would implement KIO just because on KDE-powered desktops it's the way to go. - The main selling point of FUSE is that nobody have to implement anything, it just works™. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 --- Comment #92 from Christoph Feck --- > First pre-requisite step is making all KDE apps robust to blocking calls on > files which it thinks are safe as they're on the local file system. Uh, no. KDE applications are expected to use KIO. You would have to fix all _other_ applications, which don't use the KIO API. I guess applications using GIO are also safe, because (I hope) GIO was also designed asynchronous. But POSIX API is synchronous, and users of those applications just have to live with UI hangs unless they use separate threads for IO. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402807] Progress manager doesn't seem to be involved in the fingerprint scanning (v6.0 beta 3)
https://bugs.kde.org/show_bug.cgi?id=402807 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- The problem is that searching for affected images can take quite a while and is done in the main thread until the fingerprint thread can start. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402807] Progress manager doesn't seem to be involved in the fingerprint scanning (v6.0 beta 3)
https://bugs.kde.org/show_bug.cgi?id=402807 --- Comment #1 from Maik Qualmann --- Git commit 0faafedf850331640950624056d2835a20323537 by Maik Qualmann. Committed on 03/01/2019 at 18:15. Pushed by mqualmann into branch 'master'. set explicit a wait cursor M +2-2core/libs/database/similaritydb/similaritydb.cpp M +2-2core/libs/database/similaritydb/similaritydb.h M +5-0core/utilities/maintenance/fingerprintsgenerator.cpp M +5-0core/utilities/maintenance/thumbsgenerator.cpp https://commits.kde.org/digikam/0faafedf850331640950624056d2835a20323537 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397595] Window Decorations are not properly highlighting the selected theme
https://bugs.kde.org/show_bug.cgi?id=397595 Valerio Pilo changed: What|Removed |Added CC||valerio.pilo+...@gmail.com Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Valerio Pilo --- Fixed by commit ef1692eea6912c7a70773901bcfd91fb70d0b8cf in kwin: [kcmkwin/kwindecoration] Set current decoration index on start Summary: Fixes the preselected decoration style on module load. Also: * Prevent the module state to be set to modified on resize. * Fix QML errors in logs. Reviewers: davidedmundson Reviewed By: davidedmundson Subscribers: davidedmundson, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D17775 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381806] Window Decorations KCM pop up even there is no change
https://bugs.kde.org/show_bug.cgi?id=381806 Valerio Pilo changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||valerio.pilo+...@gmail.com Resolution|--- |FIXED --- Comment #12 from Valerio Pilo --- Fixed by commit ef1692eea6912c7a70773901bcfd91fb70d0b8cf in kwin: [kcmkwin/kwindecoration] Set current decoration index on start Summary: Fixes the preselected decoration style on module load. Also: * Prevent the module state to be set to modified on resize. * Fix QML errors in logs. Reviewers: davidedmundson Reviewed By: davidedmundson Subscribers: davidedmundson, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D17775 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 402773] Current Track is missing, not showing anything.
https://bugs.kde.org/show_bug.cgi?id=402773 --- Comment #6 from hong --- Clementine works! -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 402836] New: When link with anchor (url#anchor) is opened on new tab in background Falkon jump to the bottom of the page
https://bugs.kde.org/show_bug.cgi?id=402836 Bug ID: 402836 Summary: When link with anchor (url#anchor) is opened on new tab in background Falkon jump to the bottom of the page Product: Falkon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: sgd.or...@gmail.com Target Milestone: --- SUMMARY When link with anchor (url#anchor) is opened on new tab in background Falkon jump to the bottom of the page STEPS TO REPRODUCE 1. Open link on new tab in background with address like url#anchor. Example: https://community.kde.org/Get_Involved#Bug_Reporting 2. Wait until the tab is fully loaded 3. Switch to the tab and observe where falkon jumped OBSERVED RESULT Falkon jumps to the end of the page. EXPECTED RESULT Falkon should jump to the place where anchor is located. SOFTWARE/OS VERSIONS Operating System: Artix KDE Plasma Version: 5.14.4 Qt Version: 5.12.0 KDE Frameworks Version: 5.53.0 Kernel Version: 4.19.13-1-lts OS Type: 64-bit ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.