[plasmashell] [Bug 358317] xembedsniproxy crashes when clicking on empty fcitx icon
https://bugs.kde.org/show_bug.cgi?id=358317 Pulfer changed: What|Removed |Added CC||pul...@list.ru --- Comment #5 from Pulfer --- (In reply to David Edmundson from comment #3) > Fixed with 988a7bef7e84a4a2fc6a2f6ec6145e093dfb84f8 Perhaps this commit should be pushed to master branch as well? It's still only in Plasma/5.5. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 358854] New: Import CSV or QIF doesn't retain full payee field
https://bugs.kde.org/show_bug.cgi?id=358854 Bug ID: 358854 Summary: Import CSV or QIF doesn't retain full payee field Product: kmymoney Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: kmymoney-de...@kde.org Reporter: cbwie...@gmail.com Importing from CSV or QIF is getting the last two words of the Payee/Description field. The text that should be imported is enclosed in "" as specified and the CSV Importer is showing the full text when I use that method. I have tried without the "", but I get the same result. I even created a QIF with the correct values, and I still get the same error. This should show the same value in the Imported Rows as are in the CSV Importer. This should include all data in the field. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 352637] when Importing QIF or CSV the memo field is omitted only on deposits if it contains the word "payments" or "payment"
https://bugs.kde.org/show_bug.cgi?id=352637 Clark Wierda changed: What|Removed |Added CC||cbwie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 352637] when Importing QIF or CSV the memo field is omitted only on deposits if it contains the word "payments" or "payment"
https://bugs.kde.org/show_bug.cgi?id=352637 Clark Wierda changed: What|Removed |Added CC|cbwie...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 355116] KMyMKMyMoney Vers.: 4.7.2 Import CSV only "," akzepted - I need ";"
https://bugs.kde.org/show_bug.cgi?id=355116 Clark Wierda changed: What|Removed |Added CC||cbwie...@gmail.com --- Comment #11 from Clark Wierda --- So the suggested fix is to revert to the older version and call it done? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 278236] Cannot drag file onto chromium upload form input
https://bugs.kde.org/show_bug.cgi?id=278236 Amrit changed: What|Removed |Added CC||amritdhaka...@gmail.com --- Comment #9 from Amrit --- I have encountered this bug again in plasma 5. Here are my version information: Dolphin: 15.12.1 KDE Frameworks 5.16.0 Qt 5.5.1 (built against 5.5.0) the xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 358834] Crash when trying to configure VPN
https://bugs.kde.org/show_bug.cgi?id=358834 Christoph Feck changed: What|Removed |Added Product|kde |plasma-nm CC||jgrul...@redhat.com Component|general |editor Assignee|unassigned-b...@kde.org |lu...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3
https://bugs.kde.org/show_bug.cgi?id=353203 --- Comment #49 from microcai --- you should not remove dbus-update-activation-environment --systemd --all just remove --systemd leave it as dbus-update-activation-environment --all the all problem solved. if you delete the call to dbus-update-activation-environment then it will still delay 25 seconds. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 --- Comment #45 from Andreas Hartmetz --- ..and frankly, I don't feel like gold-plating the solution to this mess. It's not going to be pretty either way, nobody cares too much except when their stuff breaks (ours did), and there are many people to convince to effect really big changes. There is bigger fish to fry. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 --- Comment #44 from Andreas Hartmetz --- I don't think that either dynamic properties or changing behavior that has been pretty much proven to be not broken by being around for over 10 years with no complaints will fly upstream, and I don't think they are a very good idea myself. For Qt5, an application attribute might be a good idea. For Qt6, I don't know. I mean there is the small problem that pseuso-SM for applications that think ignoring SM is fine only works if it asks absolutely nothing from applications. An application attribute might even work there as well: if you do care about SM, you have let's say at least 20 lines to write so you can live with another trivial one. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 352924] delayed crash upon any pen input anywhere within main window
https://bugs.kde.org/show_bug.cgi?id=352924 --- Comment #10 from Rafael --- Just want to report that in the Krita 3.0 Alpha 1 this bug is fixed. Thank you devs for everything, finally can use Krita again :D. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 342401] allow splits on payees
https://bugs.kde.org/show_bug.cgi?id=342401 --- Comment #3 from harry bennett --- Jack, thanks for the reply. Totally understand the time thing. To All, Just to be clear I wasn't really expecting it to be fixed, I generally take "confirmed" as "someone read this" and hopefully, put it on the todo list. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 358723] Gwenview, Dolphin, and many other apps crash when clicking 'Network' folder in the dir tree view.
https://bugs.kde.org/show_bug.cgi?id=358723 Takahiro Hashimoto changed: What|Removed |Added CC||fa...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358853] New: include not found in a header causes random parsing/highlighting/code completion glitches
https://bugs.kde.org/show_bug.cgi?id=358853 Bug ID: 358853 Summary: include not found in a header causes random parsing/highlighting/code completion glitches Product: kdevelop Version: git master Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: david.nolden@art-master.de When an include is not found (even if it's not needed at all), then the semantic analysis, highlighting, code completion, etc. becomes seriously broken. It seems that clang internally just stops processing the translation-unit at some point and leaves it half-processed. Ideally this would be fixed in clang so that such situations are handled more gracefully. But before that, given how serious the implications are, KDevelop's problem reporter should at least show an error, pointing out the problem. Currently, when the #include was missing in a recursively included header, then the problem-reporter stays completely empty, leaving the user cluelessly with a half-processed document. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[phonon-backend-gstreamer] [Bug 358831] kmessagedialog freezes when sound notification are activated
https://bugs.kde.org/show_bug.cgi?id=358831 Christoph Feck changed: What|Removed |Added Assignee|cf...@kde.org |dvra...@kde.org Component|general |general Version|5.1.0 |unspecified Product|frameworks-kwidgetsaddons |phonon-backend-gstreamer CC||cf...@kde.org, ||myr...@kde.org, ||romain.per...@gmail.com, ||sit...@kde.org, ||tdfisc...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358852] New: Plasma crashed
https://bugs.kde.org/show_bug.cgi?id=358852 Bug ID: 358852 Summary: Plasma crashed Product: plasmashell Version: 5.4.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: reinhardau...@gmx.at CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.3) Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I am using openSUSE Leap 42.1, with KDE 4.14.16, Plasmashell 5.4.3, I used Firefox 43.0.3 and was surfing the internet. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f35071067c0 (LWP 1799))] Thread 10 (Thread 0x7f34f09b7700 (LWP 1801)): #0 0x7f35005d4c1d in poll () from /lib64/libc.so.6 #1 0x7f350555b422 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f350555d00f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f34f2b303c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f3500cd332f in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7f34ffdd00a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7f35005dd04d in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7f34edce7700 (LWP 1823)): #0 0x7f34fcc491c9 in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x7f34fcc4b44b in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f34fcc4bd80 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f34fcc4bf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f3500f05d8b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f3500eacd53 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f3500cce61a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7f3503ff0df8 in ?? () from /usr/lib64/libQt5Qml.so.5 #8 0x7f3500cd332f in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x7f34ffdd00a4 in start_thread () from /lib64/libpthread.so.0 #10 0x7f35005dd04d in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7f34dbff7700 (LWP 1844)): #0 0x7f34ffdd405f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f34e6bcba33 in ?? () from /usr/lib64/dri/swrast_dri.so #2 0x7f34e6bcb5a7 in ?? () from /usr/lib64/dri/swrast_dri.so #3 0x7f34ffdd00a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f35005dd04d in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f34db7f6700 (LWP 1845)): #0 0x7f34ffdd405f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f34e6bcba33 in ?? () from /usr/lib64/dri/swrast_dri.so #2 0x7f34e6bcb5a7 in ?? () from /usr/lib64/dri/swrast_dri.so #3 0x7f34ffdd00a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f35005dd04d in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f34d5ab7700 (LWP 1848)): #0 0x7f35005d4c1d in poll () from /lib64/libc.so.6 #1 0x7f34fcc4be64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f34fcc4bf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f3500f05d8b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f3500eacd53 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f3500cce61a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f3503ff0df8 in ?? () from /usr/lib64/libQt5Qml.so.5 #7 0x7f3500cd332f in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7f34ffdd00a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7f35005dd04d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f34c700 (LWP 1851)): #0 0x7f34fcc8dcf9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f34fcc4b4b9 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f34fcc4bd80 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f34fcc4bf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f3500f05d8b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f3500eacd53 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f3500cce61a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7f3503ff0df8 in ?? () from /usr/lib64/libQt5Qml.so.5 #8 0x7f3500cd332f in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x7f34ffdd00a4 in start_thread () from /lib64/libpthread.so.0 #10 0x7f35005dd04d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f34ce727700 (LWP 1858)): #0 0x7f34ffdd405f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0
[kexi] [Bug 348473] Kexi query parameters do not work in COLUMNS section
https://bugs.kde.org/show_bug.cgi?id=348473 --- Comment #1 from Jarosław Staniek --- Created attachment 96949 --> https://bugs.kde.org/attachment.cgi?id=96949&action=edit a db file with a test query -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358851] New: KMail crashed while some folder is moving to another one
https://bugs.kde.org/show_bug.cgi?id=358851 Bug ID: 358851 Summary: KMail crashed while some folder is moving to another one Product: kmail2 Version: 5.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: zhuravlov...@ya.ru Application: kmail (5.1) Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: 1) import mail by wizard from previous version of KMail's maildir folder with sub-folders, completed without problems, "akonadictl fsck" is almost fine; 2) start to reorganize folders manually via KMail GUI interface: move imported folders from "/Local/KMail-Import" to "/Local" (one level up); 3) during the process, having folders layout e.g. /Local /Local/Folder1 /Local/Folder1/Subfolder1 /Local/KMail-Import/Folder1 /Local/KMail-Import/Folder1/Subfolder2 with /Local/Folder1 being folded in GUI, that is the left view looks like: - /Local + /Folder1 - /KMail-Import - /Folder1 - /Subfolder2 when I drag by mouse Subfolder2 onto Folder1, select "Move, not Copy" in the popup menu, then KMail crashes immediately. The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f69a39a2800 (LWP 20196))] Thread 23 (Thread 0x7f697d082700 (LWP 20198)): #0 0x7f6996c63e42 in () at /usr/lib64/libglib-2.0.so.0 #1 0x7f6996c63f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #2 0x7f69a1510d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f69a14b7d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f69a12d961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f69a12de32f in () at /usr/lib64/libQt5Core.so.5 #6 0x7f69971800a4 in start_thread () at /lib64/libpthread.so.0 #7 0x7f69a09d804d in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f6977fff700 (LWP 20199)): #0 0x7f6996ca5cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f6996c638fc in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7f6996c63df8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f6996c63f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f69a1510d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f69a14b7d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f69a12d961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f69a12de32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f69971800a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f69a09d804d in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f69777fe700 (LWP 20201)): #0 0x7f69a09cfc1d in poll () at /lib64/libc.so.6 #1 0x7f6996c63e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f6996c63f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f69a1510d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f69a14b7d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f69a12d961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f69a12de32f in () at /usr/lib64/libQt5Core.so.5 #7 0x7f69971800a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f69a09d804d in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f6976ffd700 (LWP 20205)): #0 0x7f69a1510d84 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #1 0x7f69a14b7d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #2 0x7f69a12d961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #3 0x7f69a12de32f in () at /usr/lib64/libQt5Core.so.5 #4 0x7f69971800a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f69a09d804d in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f69767fc700 (LWP 20211)): #0 0x7fff73f69ae6 in clock_gettime () #1 0x7f69a09e4c9d in clock_gettime () at /lib64/libc.so.6 #2 0x7f69a138f7d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f69a150f3b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f69a150f945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f69a1510b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f6996c634ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f6996c63d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f6996c63f7c in g_main_context_iteration () at /usr/lib64/libglib-2
[plasmashell] [Bug 358849] Minimum plasmoid width and height not respected
https://bugs.kde.org/show_bug.cgi?id=358849 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358849] Minimum plasmoid width and height not respected
https://bugs.kde.org/show_bug.cgi?id=358849 Kai Uwe Broulik changed: What|Removed |Added Severity|major |normal CC||k...@privat.broulik.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358850] New: KWin crash after closing window from Present Windows
https://bugs.kde.org/show_bug.cgi?id=358850 Bug ID: 358850 Summary: KWin crash after closing window from Present Windows Product: kwin Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: k...@privat.broulik.de Application: kwin_x11 (5.5.90) (Compiled from sources) Qt Version: 5.5.1 Operating System: Linux 4.2.0-22-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: I was in VLC player settings when it suddenly opened a fullscreen player window I was unable to exit from (eg. double click the window did nothing), so I invoked Present Windows by screen corner to closethe VLC fullscreen window. After I closed it, VLC quit and KWin crashed. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2f2d000840 (LWP 1798))] Thread 5 (Thread 0x7f2f15045700 (LWP 1814)): #0 0x7f2f2cb018dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f2f2aab3bd2 in poll (__timeout=-1, __nfds=1, __fds=0x7f2f15044c80) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0xb49e00, cond=cond@entry=0xb49e40, vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:459 #3 0x7f2f2aab574f in xcb_wait_for_event (c=0xb49e00) at ../../src/xcb_in.c:623 #4 0x7f2f158e57e9 in QXcbEventReader::run (this=0xb544c0) at qxcbconnection.cpp:1229 #5 0x7f2f2ad70a6e in QThreadPrivate::start (arg=0xb544c0) at thread/qthread_unix.cpp:331 #6 0x7f2f2bfe56aa in start_thread (arg=0x7f2f15045700) at pthread_create.c:333 #7 0x7f2f2cb0ceed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f2f0d63d700 (LWP 1850)): #0 0x7f2f2cb03743 in select () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f2f2afa3b7f in qt_safe_select (nfds=12, fdread=fdread@entry=0x7f2f0a78, fdwrite=fdwrite@entry=0x7f2f0d08, fdexcept=fdexcept@entry=0x7f2f0f98, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75 #2 0x7f2f2afa567e in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7f2f0f98, writefds=0x7f2f0d08, readfds=0x7f2f0a78, nfds=, this=0x7f2f08c0) at kernel/qeventdispatcher_unix.cpp:320 #3 QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f2f08e0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196 #4 0x7f2f2afa5bae in QEventDispatcherUNIX::processEvents (this=0x7f2f08c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #5 0x7f2f2af4f50a in QEventLoop::exec (this=this@entry=0x7f2f0d63cd60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f2f2ad6bac4 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7f2f256e8c35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f2f2ad70a6e in QThreadPrivate::start (arg=0xd8c300) at thread/qthread_unix.cpp:331 #9 0x7f2f2bfe56aa in start_thread (arg=0x7f2f0d63d700) at pthread_create.c:333 #10 0x7f2f2cb0ceed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f2f061c3700 (LWP 1865)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2f29e89194 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f2f29e891d9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f2f2bfe56aa in start_thread (arg=0x7f2f061c3700) at pthread_create.c:333 #4 0x7f2f2cb0ceed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f2f0e2db700 (LWP 15903)): #0 0x7f2f2cb03743 in select () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f2f2afa3b7f in qt_safe_select (nfds=11, fdread=fdread@entry=0x7f2f0811c978, fdwrite=fdwrite@entry=0x7f2f0811cc08, fdexcept=fdexcept@entry=0x7f2f0811ce98, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75 #2 0x7f2f2afa567e in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7f2f0811ce98, writefds=0x7f2f0811cc08, readfds=0x7f2f0811c978, nfds=, this=0x7f2f08033040) at kernel/qeventdispatcher_unix.cpp:320 #3 QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f2f0811c7e0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196 #4 0x7f2f2afa5bae in QEventDispatcherUNIX::processEvents (this=0x7f2f08033040, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #5 0x7f2f2af4f50a in QEventLoop::exec (this=this@entry=0x7f2f0e2dad60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f2f2ad6bac4 in QThread::exec (this=) at thread/qthread.cpp:503 #7
[digikam] [Bug 358843] Add link to source code web interface to main menu
https://bugs.kde.org/show_bug.cgi?id=358843 --- Comment #2 from DrSlony --- Sorry, where? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 342401] allow splits on payees
https://bugs.kde.org/show_bug.cgi?id=342401 --- Comment #2 from Jack --- It looks like less than a quarter of the wishlist items are confirmed. I don' think this really has any particular meaning or importance - other than perhaps a developer will confirm an item as an unofficial way of increasing the priority. As has been said on the mailing list, developer time is rather scarce, and the current priority is conversion to Frameworks. Once that is complete (and there is no timeline yet) there may be more attention to fixing remaining bugs, and then to addressing wishlist items. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358846] New: Recreatable crash: Turn off open gl + play animation + stroke while playing = crash
https://bugs.kde.org/show_bug.cgi?id=358846 Bug ID: 358846 Summary: Recreatable crash: Turn off open gl + play animation + stroke while playing = crash Product: krita Version: 2.9.10 Platform: unspecified OS: MS Windows Status: UNCONFIRMED Severity: critical Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: j3480...@trbvm.com First, thanks Krita team, please keep improve this product! As the summary says, if you are running Krita with OpenGL support unchecked in display options and then press play on the timeline so an animation loops a few frames, and then lastly try to make a stroke while the animation is playing, Krita will crash every time. If you stroke this way during animation play with OpenGL enabled Krita will just snap to the last frame and remain stable. I'm very much hoping this reveals issues with brushstroke related crashes because Krita stops responding extremely often pretty much always while attempting random regular strokes (using anything from a cintiq pressure enabled pen to a regular mouse click and drag.) Krita crashes just as much with OpenGL activated as with not, I just can't yet find a reproducible method to crash with OpenGL on, it's very random. When crashing on a stroke the cursor will just disappear and Krita will become unresponsive, requiring a task manager end process procedure to quit. I have tried operating from fresh boots with nothing else running and with many different settings configurations and the random crashes persist. My intuition tells me stroke crashes happen most often when cursor movement is idle for a moment then on the redetection of movement there is a conflict somewhere. Before crashes I often see a fraction of a second where the cursor is following my motion like normal and then it disappears and I know the session is over. Please prioritize this as it's a complete workflow killer. I have classified it as critical because I have lost hours of work to this bug chain. Awesome job on Krita so far guys, the animation setup is to die for, I just want it to stop...dying! :) Reproducible: Always Steps to Reproduce: 1. Deactivate OpenGL in display settings. 2. Make a few frames on the animation timeline and press play so it loops. 3. While it's playing touch a brush to the canvas and try to make a stroke. Actual Results: Crashes every time without fail. Expected Results: It should stop the animation and rest on the exact frame when an interrupting stroke is detected. You guys rock. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 358848] New: Chroma subsampling incorrectly described
https://bugs.kde.org/show_bug.cgi?id=358848
Bug ID: 358848
Summary: Chroma subsampling incorrectly described
Product: digikam
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Export
Assignee: digikam-de...@kde.org
Reporter: b...@londonlight.org
Continuation of https://plus.google.com/u/0/+digikam/posts/SExHL5iCt8f
https://quickgit.kde.org/?p=digikam.git&a=blob&h=f33c15ca92309ff6e8ec2e7a296bd88df0682c63&hb=b5be6c56a43af98a639e2668ff99d8a47fd6504a&f=libs%2Fdimg%2Floaders%2Fjpegloader.cpp
Case 1: 2x1 1x1 1x1 = 4:2:2
Chroma halved horizontally.
You call it "low".
Case 2: 2x2 1x1 1x1 = 4:2:0
Chroma quartered in 2x2 blocks.
You call it "medium".
Case 3: 4x1 1x1 1x1 = 4:1:1
Chroma quartered in 4x1 blocks.
You call it "high".
Tooltip:
https://quickgit.kde.org/?p=digikam.git&a=blob&h=afa4beb83a6173345f516261ec442c199557738e&hb=b5be6c56a43af98a639e2668ff99d8a47fd6504a&f=libs%2Fdimg%2Floaders%2Fjpegsettings.cpp
4:2:0 and 4:1:1 both quarter the chroma resolution, but in different ways.
4:1:1 is uncommon, but if you want to have it then I think it is misleading to
call 4:1:1 "high" and 4:2:0 "medium", as they both destroy 3/4 of the color but
in different ways.
Just saying "little to no visual difference" is not good, because the
difference can be the opposite of "little" depending on the image, and this
explanation does nothing to prepare the user for what sort of difference to
expect. I would not call this "little to no" http://i.imgur.com/zfvnrML.png
Saying that only 4:1:1 "tends to alter colors" leads the user to think the
other options don't when in fact they all butcher colors.
Lastly, 4:2:0 and 4:1:1 both quarter the resolution, so I wouldn't call one
"high" and the other "medium".
Here is my proposal:
d->subSamplingCB->setWhatsThis(i18n("Chroma subsampling reduces file
size by taking advantage of the eye's lesser sensitivity to color resolution.
How perceptible the difference is depends on the image - real-life full-sized
photos will generally show no difference, while sharp, down-scaled photos and
pixel-fine colorful watermarks and text may lose fine color detail."
"NoneJ:a:b 4:4:4, h/v 1/1No chroma subsampling, highest
quality but lowest compression."
"MediumJ:a:b 4:2:2, h/v 2/1Chroma halved horizontally,
average compression, average quality."
"High 2x1J:a:b 4:2:0, h/v 2/2Chroma quartered in 2x2 blocks,
high compression but low quality."
"High 4x1J:a:b 4:1:1, h/v 4/1Chroma quartered in 4x1 blocks,
high compression but low quality."));
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 358848] Chroma subsampling incorrectly described
https://bugs.kde.org/show_bug.cgi?id=358848 DrSlony changed: What|Removed |Added CC||b...@londonlight.org -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 358847] New: crash on close in php documentation
https://bugs.kde.org/show_bug.cgi?id=358847 Bug ID: 358847 Summary: crash on close in php documentation Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Language Support: PHP Assignee: kdevelop-bugs-n...@kde.org Reporter: m...@milianw.de Application: kdevelop (4.90.91) Qt Version: 5.5.1 Operating System: Linux 4.3.3-3-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc0cf265880 (LWP 17537))] Thread 15 (Thread 0x7fc0cdd7f700 (LWP 17538)): #0 0x7fc0e60e618d in poll () from /usr/lib/libc.so.6 #1 0x7fc0da314ae2 in ?? () from /usr/lib/libxcb.so.1 #2 0x7fc0da316757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7fc0cee70379 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7fc0e6ce5b8e in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fc0df0394a4 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fc0e60ef13d in clone () from /usr/lib/libc.so.6 Thread 14 (Thread 0x7fc0bebcd700 (LWP 17540)): #0 0x7fc0df03f428 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fc0e6ce6d66 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7fc0e406f39e in KDevelop::DUChainPrivate::CleanupThread::run (this=0x4b29c50) at /home/milian/projects/kf5/src/extragear/kdevelop/kdevplatform/language/duchain/duchain.cpp:281 #3 0x7fc0e6ce5b8e in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7fc0df0394a4 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7fc0e60ef13d in clone () from /usr/lib/libc.so.6 Thread 13 (Thread 0x7fc0bc8f7700 (LWP 17542)): #0 0x7fc0e60e618d in poll () from /usr/lib/libc.so.6 #1 0x7fc0dcd4ffbc in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fc0dcd500cc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fc0e6f1d54f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fc0e6ec457a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fc0e6ce0be4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fc0e6ce5b8e in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7fc0df0394a4 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7fc0e60ef13d in clone () from /usr/lib/libc.so.6 Thread 12 (Thread 0x7fc0998f6700 (LWP 17687)): #0 0x7fc0df03f07f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fc0e6ce6e2b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7fc0e33a0d6f in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=0x3e14510, th=0x50d7630) at /home/milian/projects/kf5/src/frameworks/threadweaver/src/weaver.cpp:594 #3 0x7fc0e33a0be2 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x3e14510, th=0x50d7630, threadWasBusy=true, suspendIfInactive=false, justReturning=false) at /home/milian/projects/kf5/src/frameworks/threadweaver/src/weaver.cpp:554 #4 0x7fc0e33aae54 in ThreadWeaver::WorkingHardState::applyForWork (this=0x3e210e0, th=0x50d7630, wasBusy=true) at /home/milian/projects/kf5/src/frameworks/threadweaver/src/workinghardstate.cpp:66 #5 0x7fc0e33ab0b2 in non-virtual thunk to ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /home/milian/projects/kf5/src/frameworks/threadweaver/src/workinghardstate.cpp:61 #6 0x7fc0e33a0edf in ThreadWeaver::Weaver::applyForWork (this=0x3e14510, th=0x50d7630, wasBusy=true) at /home/milian/projects/kf5/src/frameworks/threadweaver/src/weaver.cpp:568 #7 0x7fc0e33a61b0 in ThreadWeaver::Thread::run (this=0x50d7630) at /home/milian/projects/kf5/src/frameworks/threadweaver/src/thread.cpp:103 #8 0x7fc0e6ce5b8e in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7fc0df0394a4 in start_thread () from /usr/lib/libpthread.so.0 #10 0x7fc0e60ef13d in clone () from /usr/lib/libc.so.6 Thread 11 (Thread 0x7fc09b08d700 (LWP 17688)): #0 0x7fc0df03f07f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fc0e6ce6e2b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7fc0e33a0d6f in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=0x3e14510, th=0x7fc09034a9b0) at /home/milian/projects/kf5/src/frameworks/threadweaver/src/weaver.cpp:594 #3 0x7fc0e33a0be2 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x3e14510, th=0x7fc09034a9b0, threadWasBusy=true, suspendIfInactive=false, justReturning=false) at /home/milian/projects/kf5/src/frameworks/thread
[kdevelop] [Bug 358847] crash on close in php documentation
https://bugs.kde.org/show_bug.cgi?id=358847 Milian Wolff changed: What|Removed |Added Keywords||release_blocker Status|UNCONFIRMED |CONFIRMED Priority|NOR |VHI Target Milestone|--- |5.0.0 Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358849] New: Minimum plasmoid width and height not respected
https://bugs.kde.org/show_bug.cgi?id=358849 Bug ID: 358849 Summary: Minimum plasmoid width and height not respected Product: plasmashell Version: 5.5.4 Platform: Chakra URL: https://trello-attachments.s3.amazonaws.com/56abd64f97 b1bfc661e26b82/798x280/bfb8839da8d85dbc0d8026e1869cbb8 f/chakra-welcome-plasmoid.png OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: luc...@bluewin.ch CC: bhus...@gmail.com, plasma-b...@kde.org When I add a new plasmoid the minimum width and height are not respected. All plasmoids are affected. For instance if I add the note plasmoid an icon is shown instead of the "post-it" image. This is the QML code that set the minimum layout values: property int minimumWidth: 540 property int minimumHeight: 480 Layout.minimumWidth: minimumWidth < buttonRow.width ? buttonRow.width : minimumWidth Layout.minimumHeight: minimumHeight Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358428] No pressure sensitivity with Cintiq 13HD and Windows 10 at all times
https://bugs.kde.org/show_bug.cgi?id=358428 --- Comment #8 from elfro...@gmail.com --- Created attachment 96948 --> https://bugs.kde.org/attachment.cgi?id=96948&action=edit krita.bak -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358428] No pressure sensitivity with Cintiq 13HD and Windows 10 at all times
https://bugs.kde.org/show_bug.cgi?id=358428 elfro...@gmail.com changed: What|Removed |Added Resolution|FIXED |WONTFIX --- Comment #7 from elfro...@gmail.com --- Hello, thanks for the attention. it turns out that everytime I restart my computer, the krita.bak solution stops working, which in turn I have to do it again and again, let me upload the latest krita.bak for you, thanks -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358845] New: Incorrect alignment of string with drop-down list
https://bugs.kde.org/show_bug.cgi?id=358845 Bug ID: 358845 Summary: Incorrect alignment of string with drop-down list Product: kmail2 Version: 5.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: config dialog Assignee: kdepim-b...@kde.org Reporter: alvare...@kde.org See screenshot. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358845] Incorrect alignment of string with drop-down list
https://bugs.kde.org/show_bug.cgi?id=358845 --- Comment #1 from André Marcelo Alvarenga --- Created attachment 96947 --> https://bugs.kde.org/attachment.cgi?id=96947&action=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[kshisen] [Bug 358773] kshisen shows as stuck when obvious moves remain
https://bugs.kde.org/show_bug.cgi?id=358773 --- Comment #3 from Frederik Schwarzer --- Thank you for the screen shot. I will try to reproduce this tomorrow. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356727] Plasma Panel sometimes disappears with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=356727 Phil Schaf changed: What|Removed |Added CC||flying-sh...@web.de -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 355928] kscreen reports change of primary screen without apparent reason
https://bugs.kde.org/show_bug.cgi?id=355928 Mark Ferguson changed: What|Removed |Added CC||markfe...@gmail.com --- Comment #13 from Mark Ferguson --- I had the same issue when in Kubuntu when I upgraded to Plasma 5.5.3 and KDE’s Frameworks 5.18.0 from Plasma 5.4.3 and KDE Applications 15.08.3. Prior to the upgrade I did not see this log message at all. org.kde.KScreen[1335]: kscreen: Primary output changed from KScreen::Output(Id: 639 , Name: "DP-2" ) ( "DP-2" ) to KScreen::Output(Id: 639 , Name: "DP-2" ) ( "DP-2" ) I downgraded again to Plasma 5.4.3 (KDE Applications 15.08.3.) because the system logs where starting to fill up with these log messages. This error message comes form the libkscreen package (src/config.cpp) The method that prints this message is called void Config::setPrimaryOutput(const OutputPtr &newPrimary) It is actually classified as a debug message so I am wondering if it is a log level issue or a bug which is causing this method to be called more often than it should? As mention I do not see this message in the system logs on Plasma 5.4.3 (KDE Applications 15.08.3.). Though I could get the message on the command line when running kscreen-console. I could also stop the message by creating ~/.config/QtProject/qtlogging.ini and adding: [Rules] kscreen.debug=false I am guessing if upgrading again to Plasma 5.5.3 (KDE’s Frameworks 5.18.0) the log messages could be turned of by adding the qtlogging.ini change above to the /etc/xdg/QtProject/ directory. I haven't been able to test whether this would work and I will probably won't have time this week. I would also be reluctant to do this unless it can be confirmed that the calling of Config::setPrimaryOutput so many times is not a bug? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 342401] allow splits on payees
https://bugs.kde.org/show_bug.cgi?id=342401 --- Comment #1 from harry bennett --- a year has gone by and this is still "unconfirmed"? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 358843] Add link to source code web interface to main menu
https://bugs.kde.org/show_bug.cgi?id=358843 caulier.gil...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||caulier.gil...@gmail.com Resolution|--- |INVALID --- Comment #1 from caulier.gil...@gmail.com --- All is here ... https://www.digikam.org/download?q=download/GIT Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 358844] Add "fit" or "bounding box" resize option
https://bugs.kde.org/show_bug.cgi?id=358844 DrSlony changed: What|Removed |Added CC||b...@londonlight.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 358844] New: Add "fit" or "bounding box" resize option
https://bugs.kde.org/show_bug.cgi?id=358844 Bug ID: 358844 Summary: Add "fit" or "bounding box" resize option Product: digikam Version: 4.14.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Batch Queue Manager Assignee: digikam-de...@kde.org Reporter: b...@londonlight.org Resizing is a very frequently used feature, however digiKam's implementation lacks any way to have portrait and landscape photos resized together so they end up in a predictable size. Please add an option to resize: - Width - Height - Bounding box (sometimes called "fit") The third option lets you specify dimensions within which the image must fit, e.g. 1920x1080, regardless of the photo's orientation. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 Guillaume DE BURE changed: What|Removed |Added CC||guillaume.deb...@gmail.com --- Comment #43 from Guillaume DE BURE --- Guys, I just wanted to say a big thanks for looking into this :). Being the original reporter of related bug #341930, session management in *very* important for me. While your technical discussion is way far above my technical abilities, if there is anything I can do, like testing patches, please feel free to ask ! Thanks again :) :) :) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 303877] valgrind doesn't support compressed debuginfo sections.
https://bugs.kde.org/show_bug.cgi?id=303877 Philippe Waroquiers changed: What|Removed |Added CC||philippe.waroquiers@skynet. ||be --- Comment #18 from Philippe Waroquiers --- An alternative is also the simple/super small 'inflate' implementation in zlib code zlib-1.2.8/contrib/puff.h and puff.c This is a fully independent inflate implementation (no #include). There are some drawbacks (2 times slower than the real zlib inflate, and as it does not do memory allocation, inflate fails if the target buffer is too small (and so, you must redo the inflate with a bigger buffer). If the debug info stores the uncompressed size, then this is not a problem -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 358843] Add link to source code web interface to main menu
https://bugs.kde.org/show_bug.cgi?id=358843 DrSlony changed: What|Removed |Added CC||b...@londonlight.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 358494] KDevelop/KatePart/KTextEditor should always ensure that the file ends with a newline
https://bugs.kde.org/show_bug.cgi?id=358494 Christoph Cullmann changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||cullm...@kde.org Resolution|--- |FIXED --- Comment #1 from Christoph Cullmann --- Done, Kevin already changed the default, now the key is altered to enforce that the default will be in action for the next frameworks release. https://phabricator.kde.org/rKTEXTEDITOR54536d9cc9da -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 356211] In debug session "Variable ToolTip" doesn't resize vertically
https://bugs.kde.org/show_bug.cgi?id=356211 Piotr Mierzwinski changed: What|Removed |Added Version|4.90.90 |4.90.91 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 353088] kate (15.08.1) interface freeze if reloading changed file, moving the window solves the problem.
https://bugs.kde.org/show_bug.cgi?id=353088 --- Comment #1 from Christoph Cullmann --- Git commit 1525fd5ff7c9bb890e4deac5465876bc1cbaa7f3 by Christoph Cullmann. Committed on 31/01/2016 at 21:11. Pushed by cullmann into branch 'master'. remove some suspicious setUpdatesEnabled calls M +0-6src/document/katedocument.cpp http://commits.kde.org/ktexteditor/1525fd5ff7c9bb890e4deac5465876bc1cbaa7f3 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 356211] In debug session "Variable ToolTip" doesn't resizing vertically
https://bugs.kde.org/show_bug.cgi?id=356211 --- Comment #2 from Piotr Mierzwinski --- Your welcome. This is only one thing what I can do now. Sorry. Fixing requires more or less diving in source code and analyze how does it work. I don't have so much time for this :(. You have a lot of experiences with KDevelop code, so for you it's a lot easier. Recently I discover one thing, maybe will be helpful. Namely, KDevelop beta1 (mentioned on your homesite and packaged in couple of distributions - KaOS, Mageia Cauldron) doesn't have this bug. The same for bug 355159. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 355159] CRASH in KDevelop::VariableToolTip::slotLinkActivated(QString const&) ... at /home/piotr/kf5/src/kdevplatform/debugger/variable/variabletooltip.cpp:185
https://bugs.kde.org/show_bug.cgi?id=355159 --- Comment #5 from Piotr Mierzwinski --- Recently I discover one thing, maybe will be helpful. Namely, KDevelop beta1 (mentioned on your homesite and packaged in couple of distributions: KaOS, Mageia Cauldron) doesn't have this bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 358843] New: Add link to source code web interface to main menu
https://bugs.kde.org/show_bug.cgi?id=358843 Bug ID: 358843 Summary: Add link to source code web interface to main menu Product: digikam Version: 4.14.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: b...@londonlight.org I was unable to find a way to browse the digiKam source code online, I had to ask for a link on IRC. It would be good if there was an easy to find link to the web interface of your source code repository, preferably in the main menu. This link: https://quickgit.kde.org/?p=digikam.git If the link is already somewhere on your website, I was unable to find it. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 356211] In debug session "Variable ToolTip" doesn't resize vertically
https://bugs.kde.org/show_bug.cgi?id=356211 Piotr Mierzwinski changed: What|Removed |Added Summary|In debug session "Variable |In debug session "Variable |ToolTip" doesn't resizing |ToolTip" doesn't resize |vertically |vertically -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 355898] Wrong syntax highlighting for Perl
https://bugs.kde.org/show_bug.cgi?id=355898
Christoph Cullmann changed:
What|Removed |Added
Resolution|--- |WONTFIX
CC||cullm...@kde.org
Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Christoph Cullmann ---
This is a feature ;)
You can fold stuff by writing:
# {{{
# }}}
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 353935] Kate's editor component in various apps shares the same settings.
https://bugs.kde.org/show_bug.cgi?id=353935 Christoph Cullmann changed: What|Removed |Added CC||spa...@wp.pl --- Comment #1 from Christoph Cullmann --- *** Bug 349006 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 349006] KWrite and Kate have the same configuration
https://bugs.kde.org/show_bug.cgi?id=349006 Christoph Cullmann changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||cullm...@kde.org --- Comment #1 from Christoph Cullmann --- *** This bug has been marked as a duplicate of bug 353935 *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 347327] Kate doesn't show properly large fonts
https://bugs.kde.org/show_bug.cgi?id=347327 Christoph Cullmann changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||cullm...@kde.org Resolution|--- |WORKSFORME --- Comment #2 from Christoph Cullmann --- This should be fixed in the KF5 version. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 353813] File System Browser freezes Kate when opening a file in a folder with thousands of files
https://bugs.kde.org/show_bug.cgi?id=353813 Christoph Cullmann changed: What|Removed |Added Component|kfile |general Assignee|pfeif...@kde.org|fa...@kde.org CC||kdelibs-b...@kde.org Product|kio |frameworks-kio -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 353813] File System Browser freezes Kate when opening a file in a folder with thousands of files
https://bugs.kde.org/show_bug.cgi?id=353813 Christoph Cullmann changed: What|Removed |Added Product|kate|kio CC||cullm...@kde.org Version|5.0.0 |unspecified Component|general |kfile Assignee|kwrite-bugs-n...@kde.org|pfeif...@kde.org --- Comment #1 from Christoph Cullmann --- This is then some KDirOperator issue. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358842] New: Doubling the project frame rate doubles the video playback speed
https://bugs.kde.org/show_bug.cgi?id=358842 Bug ID: 358842 Summary: Doubling the project frame rate doubles the video playback speed Product: kdenlive Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: pbkai...@gmail.com When changing from 30fps to 60fps the project monitor plays back the video at double speed. Reproducible: Always Steps to Reproduce: 1. Add some clips to the timeline 2. Go to Project Settings 3. Set the profile from HD 720p 30fps to 60fps Actual Results: project monitor is on double speed Expected Results: stay at the same speed but the frame should be more dense. This is a major bug when combining with the speed effect -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 353285] Kate crashes when discard changes in file
https://bugs.kde.org/show_bug.cgi?id=353285 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #3 from Christoph Cullmann --- Hi, can't reproduce either with e.g. Kate 15.12. Please reopen and provide some hints how to get that crash with recent versions, thanks, and sorry for the problems :/ -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 357481] KMail doesn't honor the "always sign with GPG" flag in idendity when replying
https://bugs.kde.org/show_bug.cgi?id=357481 --- Comment #8 from Christian Boltz --- Just for the records: a debugging session on IRC (thanks for doing that!) showed that - the test works (fails without my patch, and succeeds with it) - the test needs GPG signing enabled in the default idendity to work - my patch fixes the issue -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 357097] kate v.15.08.3 segfaults when saving a new file
https://bugs.kde.org/show_bug.cgi?id=357097 Christoph Cullmann changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME CC||cullm...@kde.org --- Comment #6 from Christoph Cullmann --- I had that crash once, too, this seems to be some now fixed error in platformintegration. Please try Kate 15.12 with some up to date frameworks, like 5.14 or so, should work their. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 356968] Ark plugin extracthere makes Dolphin crash after drag and drop
https://bugs.kde.org/show_bug.cgi?id=356968 Elvis Angelaccio changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #3 from Elvis Angelaccio --- Closing, the OP told me that this problem was resolved after updating its system. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 342512] Crash during code folding, embedded in KDevelop [KateLineLayout::viewLineCount]
https://bugs.kde.org/show_bug.cgi?id=342512 Christoph Cullmann changed: What|Removed |Added Latest Commit||http://commits.kde.org/ktex ||teditor/46bae1d04176fe966e2 ||cd973eef07581ec1ef92a Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Christoph Cullmann --- Git commit 46bae1d04176fe966e2cd973eef07581ec1ef92a by Christoph Cullmann. Committed on 31/01/2016 at 20:47. Pushed by cullmann into branch 'master'. delay emitting of verticalScrollPositionChanged until all stuff is consistent for folding M +14 -8src/view/kateviewinternal.cpp M +1-1src/view/kateviewinternal.h http://commits.kde.org/ktexteditor/46bae1d04176fe966e2cd973eef07581ec1ef92a -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 356246] Kate spins endlessly doing getcwd() or i18n()
https://bugs.kde.org/show_bug.cgi?id=356246 Christoph Cullmann changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO CC||cullm...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #5 from Christoph Cullmann --- Hmm, sorry, no idea how to reproduce that to fix it :/ If you have some config file that triggers that, please attach it, but I guess they are gone now after the rm -rf -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 358841] New: Installation directions are both wrong and complex
https://bugs.kde.org/show_bug.cgi?id=358841 Bug ID: 358841 Summary: Installation directions are both wrong and complex Product: neon Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: n...@kde.org Reporter: regmeple...@gmail.com From http://www.phoronix.com/forums/forum/software/desktop-linux/848907-kde-neon-is-now-live-providing-bleeding-edge-kde-packages-for-ubuntu?p=849059#post849059 Directions for installation on the NEON website are wrong in some parts and more complex than needed in other ones. 1. Traditional way to download and install a repository authentication key is "wget -q -O - 'http://archive.neon.kde.org.uk/public.key' | sudo apt-key add -" all in one line with no temporary file left behind. 2. The "sudo apt update" is to by typed on a new command line, not on the same one as apt-add-repository 3. The command "sudo apt install neon-desktop" didn't pull all the needed packages as I already have Kubuntu 15.10, all the needed packages were kept on hold to avoid incoherencies. I had to run more than once "apt-get -y install" with those held back packages (the package list was too long), then run "apt-get upgrade" and finally the usual "apt-get -y autoremove" and "apt-get -y clean" in order to try to get a "clean" upgrade. Reproducible: Always Steps to Reproduce: Already explained in the description Actual Results: . Expected Results: . . -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 354056] Deleted emails stay, but greyed out
https://bugs.kde.org/show_bug.cgi?id=354056 S. Bryant changed: What|Removed |Added CC||st...@bawue.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358840] New: kmail composer: menu item "send" missing
https://bugs.kde.org/show_bug.cgi?id=358840 Bug ID: 358840 Summary: kmail composer: menu item "send" missing Product: kmail2 Version: 5.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: kde-b...@cboltz.de In KMail 4.x, the "messages" menu in the composer had the following menu items: - send email - send email with [transport submenu] - send later - send later with [transport submenu] In KMail 5.1.1, the "send email" menu item is missing, so you can't send a mail now with the default transport. The workaround is to use the toolbar or the keyboard shortcut, but I'd like to have the menu entry back ;-) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358838] New: kdenlive project file has HTML tags and bad headers
https://bugs.kde.org/show_bug.cgi?id=358838 Bug ID: 358838 Summary: kdenlive project file has HTML tags and bad headers Product: kdenlive Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: pbkai...@gmail.com Sometimes the project file begins to have < tags instead of "<" sign. Also there is "" in the middle of the project. The main bin playlist also has some weird customeffects parameters. This often corrupts the file and makes the project reopening impossible And this often breaks the timeline objects like clips and transitions Reproducible: Sometimes Steps to Reproduce: 1. Deepen in some video editing project 2. Eventually you will see html tags in the project file 3. Actual Results:Expected Results: Correctly edited xml file -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 358839] New: Splash screen not easily customizable from the splash screen settings menu.
https://bugs.kde.org/show_bug.cgi?id=358839 Bug ID: 358839 Summary: Splash screen not easily customizable from the splash screen settings menu. Product: ksplash Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: l.lu...@kde.org Reporter: opensou...@skiboy.net I would like the splash screen and KDE icon to be easily changeable from System Settings > Workspace Theme > Splash Screen. I would like to be able to change the background and icon on the splash screen, just like I am able to change the background image for the lock screen and login screen. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 353958] Akregator marks all unread feeds in list as read when set status to unread and click on one of the unread articles
https://bugs.kde.org/show_bug.cgi?id=353958 S. Bryant changed: What|Removed |Added CC||st...@bawue.de --- Comment #6 from S. Bryant --- This bug still exists with Akregator 5.1.1 in OpenSuse Leap 42.1. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 298511] Change returned type of static function in it's definition (cpp file) made remove word "static" in it's declaration (header)
https://bugs.kde.org/show_bug.cgi?id=298511 Milian Wolff changed: What|Removed |Added Keywords||release_blocker Target Milestone|--- |5.0.0 Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED Priority|NOR |VHI -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358837] New: this error warning appeared out of nowhere as i was drawing
https://bugs.kde.org/show_bug.cgi?id=358837 Bug ID: 358837 Summary: this error warning appeared out of nowhere as i was drawing Product: krita Version: unspecified Platform: MS Windows URL: http://sta.sh/0p4kwy9rth8 OS: MS Windows Status: UNCONFIRMED Severity: minor Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: gollyolli...@gmail.com I was just drawing and krita suddenly showed this error. it stated "Krita has encountered an internal error: ASSERT (krita): "isRunning()" in file C:\dev\desktop64\p\calligra\krita\plugins\tools\defaulttools\kis_tool_line_helper.cpp, line 158 Please report a bug to developers! Press Ignore to try to continue. Press Abort to see developers information (all unsaved data will be lost)" I don't know what to do. Reproducible: Didn't try -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 344119] 100% CPU usage after closing konsole, after upgrading to 3.0.1/KF5.6.0 with nvidia driver
https://bugs.kde.org/show_bug.cgi?id=344119 --- Comment #33 from Rex Dieter --- fyi, according to followups in bug #343803 This should be fixed in newer versions of nvidia driver, reportedly at least in 361.18 -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 358836] New: Instant Messaging Plasmoid should close when "Configure Now..." is pressed.
https://bugs.kde.org/show_bug.cgi?id=358836 Bug ID: 358836 Summary: Instant Messaging Plasmoid should close when "Configure Now..." is pressed. Product: telepathy Version: 15.08.2 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: chat-plasmoid Assignee: kde-telepathy-b...@kde.org Reporter: opensou...@skiboy.net Minor bug here using KDE Neon. If no accounts are set up with KDE, the plasmoid shows a "Configure Now..." button. The Ideal thing for this to do is close the plasmoid's pop-up and open up the configuration window. Instead of doing this, it only opens the window. The user can't click outside of the plasmoid pop-up to close it. The only way to close it is to click on its icon in the panel. Reproducible: Always Steps to Reproduce: 1. Click the instant messaging plasmoid icon in the panel 2. Click "Configure Now..." Actual Results: The plasmoid pop-up fails to close, and the configuration window opens. Expected Results: The software should have closed the plasmoid pop up, and opened the configuration window. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 358835] New: No PDF preview, neither in the icon space nor in the preview panel
https://bugs.kde.org/show_bug.cgi?id=358835 Bug ID: 358835 Summary: No PDF preview, neither in the icon space nor in the preview panel Product: dolphin Version: 15.08.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: view-engine: icons mode Assignee: dolphin-bugs-n...@kde.org Reporter: fle...@users.sourceforge.net I have installed ffmpgethumbs and kdegraphics-thumbnailers, but there still is no option to preview PDFs. This has been plaguing KDE5 since I use it... Reproducible: Always Steps to Reproduce: 1. Open a dir with PDF files 2. Make sure itś in preview mode 3. Notice no way to select PDF preview, and (as a result) there is no PDf preview. Expected Results: As in KDE4, thumbnails are small rendring of PDF files, and the preview pane shows the PDf file. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329697] digiKam crash when browsing albums (qt-sqlite plugin broken due to BC issue with libsqlite)
https://bugs.kde.org/show_bug.cgi?id=329697 --- Comment #156 from caulier.gil...@gmail.com --- *** Bug 358832 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 343246] plasma 5 doesn't allow different wallpapers and widgets for each virtual desktop
https://bugs.kde.org/show_bug.cgi?id=343246 --- Comment #41 from scotter59 --- Thank you guys, do like the KDE interface. :) Scott M On Sun, Jan 31, 2016 at 2:15 PM, Nikola Schnelle via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=343246 > > --- Comment #40 from Nikola Schnelle --- > (In reply to scotter59 from comment #39) > > Just wish to add my dissatisfaction with the decision to prevent unique > > wallpapers on Virtual Desktops. > > > > I have been using KDE 4 up to this point, today I upgraded my machine, > > stronger better faster and brought down the latest Mine with KDE 5. Was > > setting up my new world which included a different wallpaper, it was the > > envy of my workplace. We work directly with Microsoft and I would rub > their > > faces in our cool GUI environment. The cube, the different images the > > clarity made things pop. So as I was configuring I spent significant > time > > trying to find the option. > > > > The "activities" are an interesting feature but usually I start off my > day > > clean and work across the Virtual Desktops. If I may suggest maybe > > disabling multiple activities with a warning, if one chooses different > > wallpaper on VD's and vice versa. On KDE 4 I did not have any issues > with > > this, over the years that I used it. > > > > Eh, see the WONTFIX resolution, not a good choice. > > Otherwise thanks guys for a great UI. > > This feature is coming back. > This is main bug report (and read this comment): > https://bugs.kde.org/show_bug.cgi?id=341143#c167 > > -- > You are receiving this mail because: > You are on the CC list for the bug. > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 343246] plasma 5 doesn't allow different wallpapers and widgets for each virtual desktop
https://bugs.kde.org/show_bug.cgi?id=343246 --- Comment #40 from Nikola Schnelle --- (In reply to scotter59 from comment #39) > Just wish to add my dissatisfaction with the decision to prevent unique > wallpapers on Virtual Desktops. > > I have been using KDE 4 up to this point, today I upgraded my machine, > stronger better faster and brought down the latest Mine with KDE 5. Was > setting up my new world which included a different wallpaper, it was the > envy of my workplace. We work directly with Microsoft and I would rub their > faces in our cool GUI environment. The cube, the different images the > clarity made things pop. So as I was configuring I spent significant time > trying to find the option. > > The "activities" are an interesting feature but usually I start off my day > clean and work across the Virtual Desktops. If I may suggest maybe > disabling multiple activities with a warning, if one chooses different > wallpaper on VD's and vice versa. On KDE 4 I did not have any issues with > this, over the years that I used it. > > Eh, see the WONTFIX resolution, not a good choice. > Otherwise thanks guys for a great UI. This feature is coming back. This is main bug report (and read this comment): https://bugs.kde.org/show_bug.cgi?id=341143#c167 -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 358798] Source formatter every time selects language as "C"
https://bugs.kde.org/show_bug.cgi?id=358798 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #3 from Piotr Mierzwinski --- @Kevin. This is just regular bug report. Fixing the problem is not urgent for me. I didn't mark it anywhere as important/urgent. Milian (in one of bug report) told me, if I find any in sourceformatter then I might to report it. I understand that release blockers are more important, and this bug doesn't block release. Would be nice if someone mark it as confirmed. I know that any patches are highly appreciated. You told me about it earlier (bug related with "crash in debugger"). Unfortunately I don't have so much time to dive in not known source code, analyze how does it work, fix, test and prepare patch. Sorry. Anyway. I can report bugs. I hope this is helpful. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329697] digiKam crash when browsing albums (qt-sqlite plugin broken due to BC issue with libsqlite)
https://bugs.kde.org/show_bug.cgi?id=329697 caulier.gil...@gmail.com changed: What|Removed |Added CC||pierre.monl...@free.fr --- Comment #155 from caulier.gil...@gmail.com --- *** Bug 358829 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 358829] DK 4.0 crash when clicking on thumbmail
https://bugs.kde.org/show_bug.cgi?id=358829 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |DUPLICATE CC||caulier.gil...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from caulier.gil...@gmail.com --- *** This bug has been marked as a duplicate of bug 329697 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 358832] [DK 4.0.0] Crash when drag and drop a tag under another tag
https://bugs.kde.org/show_bug.cgi?id=358832 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from caulier.gil...@gmail.com --- *** This bug has been marked as a duplicate of bug 329697 *** -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 358732] qstring-uneeded-heap-allocations: fixit changes QString to QLatin1String even if a QString function (sprintf, arg...) on that object
https://bugs.kde.org/show_bug.cgi?id=358732
Sergio Martins changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
Latest Commit||http://commits.kde.org/claz
||y/2d119b58204d2357ed418077e
||3780afa8415ed6a
--- Comment #1 from Sergio Martins ---
Git commit 2d119b58204d2357ed418077e3780afa8415ed6a by Sergio Martins.
Committed on 31/01/2016 at 18:59.
Pushed by smartins into branch 'master'.
qstring-uneeded-heap-allocations: Fix wrong usage of QL1S
QString("").sprintf() can't be replaced with QL1S, only QSL.
M +1-1checks/qstringuneededheapallocations.cpp
M +7-0tests/qstring-uneeded-heap-allocations/main.cpp
M +2-0tests/qstring-uneeded-heap-allocations/main.cpp.expected
M +7-0
tests/qstring-uneeded-heap-allocations/main.cpp_fixed.cpp.expected
http://commits.kde.org/clazy/2d119b58204d2357ed418077e3780afa8415ed6a
--
You are receiving this mail because:
You are watching all bug changes.
[telepathy] [Bug 347219] files overlap with gnome account
https://bugs.kde.org/show_bug.cgi?id=347219 --- Comment #11 from Matt Scheirer --- I made a bug report against the account-providers package on Launchpad: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1540135 If I don't hear a reply soon I'll start poking pspmteam members. It would be insane to go against accounts-sso standards because Ubuntu package maintainers can't fix dependencies, especially when they are the only distro shipping their account-plugins in the first place! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 354043] Kate freezes at opening some random files
https://bugs.kde.org/show_bug.cgi?id=354043 Christoph Cullmann changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||cullm...@kde.org Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Christoph Cullmann --- Hi, can't reproduce that, sorry. Please try out some current KF5 version again. If you have some way to reproduce, please reopen. Sorry for the hassle :/ -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 348934] Kwrite hangs while opening non-empty files via sftp
https://bugs.kde.org/show_bug.cgi?id=348934 Christoph Cullmann changed: What|Removed |Added Resolution|--- |FIXED CC||cullm...@kde.org Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Cullmann --- Author: David Faure Date: Fri May 15 01:52:15 2015 +0200 Fix single-thread deadlocks when using proxies BUG: 346214 FIXED-IN: 5.11 CHANGELOG: fix deadlock when using network proxies Change-Id: I216d365f21fb2be886e8515cf255cf49c1bad115 -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 358257] Please forward port the option "Outline active window title" from KDE4
https://bugs.kde.org/show_bug.cgi?id=358257 Hugo Pereira Da Costa changed: What|Removed |Added Severity|normal |wishlist CC||hugo.pere...@free.fr --- Comment #1 from Hugo Pereira Da Costa --- Hello, Thanks for reporting and sorry for the delay at answering. The reason for dropping the feature is because of lack of manpower: the said feature was adding a lot of complexity to the code, making it hard to maintain. Since Oxygen is not the default style/decoration anymore, everything that would fall in this category has been dropped, in order to have more time to allocate to the default styles and decorations (breeze). This to say: I will not close the report (because this is a legitimate wish). It is unlikely however that I will have time to work on this. Maybe someone else will show up. Two side remarks: - even in non "outline" mode, oxygen uses a different shadow to show the active window with respect to inactive, which is possibly less visible than the titlebar color, but that you can also change to something more striking (e.g.: red) - Breeze, the defaut window decoration, does use different titlebar colors between active and inactive, and thus fixes the issue 'as is'. Kindly, Hugo -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 315400] File chooser UI has margins around complete window
https://bugs.kde.org/show_bug.cgi?id=315400 jose...@email.it changed: What|Removed |Added Summary|Open/Save dialog UI has |File chooser UI has margins |double margins |around complete window -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 315400] Open/Save dialog UI has double margins
https://bugs.kde.org/show_bug.cgi?id=315400 jose...@email.it changed: What|Removed |Added Product|kfile |frameworks-kio CC||kdelibs-b...@kde.org Version|4.10.90 |unspecified Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358536] Calendar Widget arrows are not displayed (missing character)
https://bugs.kde.org/show_bug.cgi?id=358536 --- Comment #3 from jose...@email.it --- actually not -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 330203] Move search bar close button to the upper right corner
https://bugs.kde.org/show_bug.cgi?id=330203 --- Comment #2 from Gregor Mi --- Thanks for auto-close :) For me, the issue is not solved, but it needs a more general discussion before doing something in kate alone. So I started a discussion here: https://forum.kde.org/viewtopic.php?f=285&t=130864&p=350716 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 358834] New: Crash when trying to configure VPN
https://bugs.kde.org/show_bug.cgi?id=358834 Bug ID: 358834 Summary: Crash when trying to configure VPN Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jessetalav...@aol.com Application: kde5-nm-connection-editor (5.4.2) Qt Version: 5.4.2 Operating System: Linux 4.2.0-25-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: I was just deleting a duplicate VPN entry, and then the thing crashed. -- Backtrace: Application: Connection editor (kde5-nm-connection-editor), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 0x7f627a65f12d in NetworkManager::Connection::settings (this=0x0) at ../../src/connection.cpp:112 #7 0x00415b1e in ConnectionEditor::slotItemDoubleClicked (this=0x1cb4e10, index=...) at ../../editor/connectioneditor.cpp:549 #8 0x7f6277fd6617 in QtPrivate::QSlotObjectBase::call (a=0x7ffcae084fa0, r=0x1cb4e10, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #9 QMetaObject::activate (sender=sender@entry=0x1e35920, signalOffset=, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffcae084fa0) at kernel/qobject.cpp:3702 #10 0x7f6277fd6f87 in QMetaObject::activate (sender=sender@entry=0x1e35920, m=m@entry=0x7f6278d808e0 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffcae084fa0) at kernel/qobject.cpp:3582 #11 0x7f6278ac4d75 in QAbstractItemView::doubleClicked (this=this@entry=0x1e35920, _t1=...) at .moc/moc_qabstractitemview.cpp:597 #12 0x7f6278b1002a in QTreeView::mouseDoubleClickEvent (this=0x1e35920, event=0x7ffcae085710) at itemviews/qtreeview.cpp:1947 #13 0x7f62788b6587 in QWidget::event (this=this@entry=0x1e35920, event=event@entry=0x7ffcae085710) at kernel/qwidget.cpp:8661 #14 0x7f62789b076e in QFrame::event (this=0x1e35920, e=0x7ffcae085710) at widgets/qframe.cpp:526 #15 0x7f6278ad3a4b in QAbstractItemView::viewportEvent (this=this@entry=0x1e35920, event=event@entry=0x7ffcae085710) at itemviews/qabstractitemview.cpp:1689 #16 0x7f6278b1220c in QTreeView::viewportEvent (this=0x1e35920, event=0x7ffcae085710) at itemviews/qtreeview.cpp:1306 #17 0x7f6277fa5d0c in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=this@entry=0x1b85b50, receiver=receiver@entry=0x1de1150, event=event@entry=0x7ffcae085710) at kernel/qcoreapplication.cpp:1031 #18 0x7f6278873b6c in QApplicationPrivate::notify_helper (this=this@entry=0x1b85b50, receiver=receiver@entry=0x1de1150, e=e@entry=0x7ffcae085710) at kernel/qapplication.cpp:3716 #19 0x7f6278879c7a in QApplication::notify (this=, receiver=0x1de1150, e=0x7ffcae085710) at kernel/qapplication.cpp:3280 #20 0x7f6277fa5f1b in QCoreApplication::notifyInternal (this=0x7ffcae085fc0, receiver=receiver@entry=0x1de1150, event=event@entry=0x7ffcae085710) at kernel/qcoreapplication.cpp:935 #21 0x7f62788786f2 in QCoreApplication::sendSpontaneousEvent (event=0x7ffcae085710, receiver=0x1de1150) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #22 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x1de1150, event=event@entry=0x7ffcae085710, alienWidget=alienWidget@entry=0x1de1150, nativeWidget=0x1cb4e10, buttonDown=buttonDown@entry=0x7f6278d99a10 , lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:2751 #23 0x7f62788cd440 in QWidgetWindow::handleMouseEvent (this=this@entry=0x1def390, event=event@entry=0x7ffcae085ba0) at kernel/qwidgetwindow.cpp:543 #24 0x7f62788cf78b in QWidgetWindow::event (this=0x1def390, event=0x7ffcae085ba0) at kernel/qwidgetwindow.cpp:210 #25 0x7f6278873b8c in QApplicationPrivate::notify_helper (this=this@entry=0x1b85b50, receiver=receiver@entry=0x1def390, e=e@entry=0x7ffcae085ba0) at kernel/qapplication.cpp:3720 #26 0x7f6278879230 in QApplication::notify (this=0x7ffcae085fc0, receiver=0x1def390, e=0x7ffcae085ba0) at kernel/qapplication.cpp:3503 #27 0x7f6277fa5f1b in QCoreApplication::notifyInternal (this=0x7ffcae085fc0, receiver=receiver@entry=0x1def390, event=event@entry=0x7ffcae085ba0) at kernel/qcoreapplication.cpp:935 #28 0x7f62782c8736 in QCoreApplication::sendSpontaneousEvent (event=0x7ffcae085ba0, receiver=0x1def390) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #29 QGuiApplicationPrivate::processMouseEvent (e=0x1e4df00) at kernel/qguiapplication.cpp:1815 #30 0x7f62782ca005 in QGuiApplicationPrivate::processWindowSystemEvent (e=e@entry=0x1e4df00) at kernel/qguiapplication.cpp:1576 #31 0x7f62782af5b8 in QWindowSystemInterface::sendWindowSystemEvents (flags=...) at kernel/qwindowsysteminterface.cpp:572 #32 0x7f6268c9e250 in use
[kio] [Bug 358833] New: KIO_file process using 100% CPU or more
https://bugs.kde.org/show_bug.cgi?id=358833 Bug ID: 358833 Summary: KIO_file process using 100% CPU or more Product: kio Version: 4.14.1 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: nfs Assignee: unassigned-b...@kde.org Reporter: reach...@gmail.com While copying (right clicked to select in one folder and pasted into another folder using dolphin) a ~450GB folder from an 500GB exfat external drive to a local 1TB ext4 drive on my machine, the KIO_file was using 100% of my CPU. I was monitoring CPU usage using top and KIO_file usage stayed below ~70 for most of the operation. During the last ~20min or so the CPU stayed between 99% and 100% with brief spikes from 120% to 175%. The system did not crash, it only became less responsive. I was looking for ways to optimize file copying operations and did not find any. I am new to KDE so if this is in the wrong place let me know please. Reproducible: Didn't try Steps to Reproduce: 1. right click to select in one folder and pasted into another folder using dolphin 2. run top and monitor progress Actual Results: >=99% CPU usage by KIO_file Expected Results: <99% CPU usage by KIO_file System Notes: AMD FX8320 3.5Ghz 8core CPU 16GB Ram Description:Linux Mint 17.3 Rosa Release:17.3 Codename: rosa (The Version list of choices was only up to 4.14.1) KDE Development Platform: 4.14.2 Operating System: Ubuntu 14.04.3 LTS (Linux Mint KDE) Kernel: Linux 3.19.0-32-generic Architecture: x86_64 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724
--- Comment #42 from Thomas Lübking ---
So, looking into the Qt sources a bit more it seems that
a) Session management is FUBAR in Qt5 and actually was likewise FU in Qt4 -
adding the proposed flag will only restore the completely FU condition of Qt4,
ie. allow clients (KDE) to workaround the brokeness ...
b) this actually *only* seems to affect the xcb platform
("GuiApplicationPrivate::commitData()" is only called by
"QPlatformSessionManager::appCommitData()" which is only called by
"sm_performSaveYourself(QXcbSessionManager *sm)" in QXcbSessionManager)
Restoring the Qt4 state however won't cut it: KApplication is deprecated and
there's no Guarantee for a KMainWindow around. Also every "plain" Qt5 client
that can be found on KDE users desktops (qupzilla, trojita, ... whatever) won't
be covered.
If you "seem to be the expert on session management" we need to define a
roadmap out of this mess, or it's never gonna happen.
What do you think about this process:
1. emit commitDataRequest()
2. at this point either the logout should be canceled (requires API addition on
QSessionManager to wire up sm_cancel; internal requirement only though. Maybe
kept in d_ptr contexts) or there thould be no windows with
QWidget::isWindowModified() or modal transients around since that indicates
some user interaction should have taken place but didn't
3. If we detect missing interaction, spam a QMessageBox and inform/ask the
user:
"It looks like the application should have intercepted the logout request,
but didn't. Do you wish to cancel the logout and explicitly save data? Since
this is an application bug and this failsafe check will be removed with Qt6,
please file a bug against the application."
4. If this still didn't cancel the logout, start closing windows depending on
an application attribute (see below) and a trumping environment variable
QT_CLOSE_WINDOWS_ON_LOGOUT_REQUEST (to pass the user ultimate control over the
behavior)
5. Remove attribute, failsafe check and (actually even documented, we can NO
WAY just remove this in Qt5) window closing in Qt6
I'd go for the application attribute since indeed there's little point in
adding functions to implement a short-term workaround.
Actually, I might even be in favor of a dynamic property
(QObject::setProperty()) since it will spare the clients compile time checks -
we an add this to KFooBar now, even though Qt 5.6 (or whatever) is not on the
horizon.
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 347147] keyword missing in csound
https://bugs.kde.org/show_bug.cgi?id=347147 --- Comment #4 from dSP --- Thanks I currently don't use Kate and Csound. I will check when I find time. On 31 Jan 2016 5:51 pm, "Christoph Cullmann via KDE Bugzilla" < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=347147 > > Christoph Cullmann changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > Status|UNCONFIRMED |NEEDSINFO > > --- Comment #3 from Christoph Cullmann --- > If you still want that, please take a look at > > https://docs.kde.org/stable5/en/applications/katepart/highlight.html > > If you provide some file as patch on https://git.reviewboard.kde.org/ we > can > have that, otherwise this won't happen. > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 358832] New: [DK 4.0.0] Crash when drag and drop a tag under another tag
https://bugs.kde.org/show_bug.cgi?id=358832 Bug ID: 358832 Summary: [DK 4.0.0] Crash when drag and drop a tag under another tag Product: digikam Version: 4.0.0 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: pierre.monl...@free.fr Application: digikam (4.0.0) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.13.0-76-generic x86_64 Distribution: Linux Mint 17.3 Rosa -- Information about the crash: - What I was doing when the application crashed: I selected a tag from the tag tree and drap and drop it inside another when. After selecting "move it" from the menu, DK crashed. - Custom settings of the application: -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0e3f6c8ac0 (LWP 11753))] Thread 9 (Thread 0x7f0e13bf1700 (LWP 11760)): #0 0x7f0e317b161d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0e317b19a9 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0e3176fbda in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0e31770048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0e3177030a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f0e20d4d336 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x7f0e31794f05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f0e33d8d754 in ?? () from /usr/lib/nvidia-304/libGL.so.1 #8 0x7f0e34cfc182 in start_thread (arg=0x7f0e13bf1700) at pthread_create.c:312 #9 0x7f0e3882147d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 8 (Thread 0x7f0e133f0700 (LWP 11761)): #0 0x7f0e317b161a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0e317b1979 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0e3176fed5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0e317700ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0e31770129 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f0e31794f05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f0e33d8d754 in ?? () from /usr/lib/nvidia-304/libGL.so.1 #7 0x7f0e34cfc182 in start_thread (arg=0x7f0e133f0700) at pthread_create.c:312 #8 0x7f0e3882147d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 7 (Thread 0x7f0e026f9700 (LWP 11764)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f0e3a4fa816 in wait (time=18446744073709551615, this=0x1162300) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=this@entry=0x1162210, mutex=mutex@entry=0x1162208, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x005e3d9e in Digikam::ScanController::run (this=0x1161f80) at /build/buildd/digikam-4.0.0/core/digikam/database/scancontroller.cpp:725 #4 0x7f0e3a4fa32f in QThreadPrivate::start (arg=0x1161f80) at thread/qthread_unix.cpp:349 #5 0x7f0e33d8d754 in ?? () from /usr/lib/nvidia-304/libGL.so.1 #6 0x7f0e34cfc182 in start_thread (arg=0x7f0e026f9700) at pthread_create.c:312 #7 0x7f0e3882147d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 6 (Thread 0x7f0e01ef8700 (LWP 11765)): #0 0x7f0e3881412d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f0e3176ffe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0e317700ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0e3a6297be in QEventDispatcherGlib::processEvents (this=0x7f0df8f0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #4 0x7f0e3a5fb0af in QEventLoop::processEvents (this=this@entry=0x7f0e01ef7a20, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f0e3a5fb3a5 in QEventLoop::exec (this=this@entry=0x7f0e01ef7a20, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f0e3a4f7c5f in QThread::exec (this=this@entry=0x11638c0) at thread/qthread.cpp:537 #7 0x7f0e3a5dc823 in QInotifyFileSystemWatcherEngine::run (this=0x11638c0) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x7f0e3a4fa32f in QThreadPrivate::start (arg=0x11638c0) at thread/qthread_unix.cpp:349 #9 0x7f0e33d8d754 in ?? () from /usr/lib/nvidia-304/libGL.so.1 #10 0x7f0e34cfc182 in start_thread (arg=0x7f0e01ef8700) at pthread_create.c:312 #11 0x7f0e3882147d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 5 (Thread 0x7f0e123ee700 (LWP 11867)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sys
[konsole] [Bug 344119] 100% CPU usage after closing konsole, after upgrading to 3.0.1/KF5.6.0 with nvidia driver
https://bugs.kde.org/show_bug.cgi?id=344119 thomi_ch changed: What|Removed |Added CC||i...@win-soft.ch --- Comment #32 from thomi_ch --- can confirm problem here: konsole 15.08.0 nvidia 352.63 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 358830] Display file name in window title
https://bugs.kde.org/show_bug.cgi?id=358830 Elvis Angelaccio changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Elvis Angelaccio --- Thanks for reporting. Indeed Ark's window title is not consistent with other KDE applications'. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358016] Plasmashell crashed just after login to desktop
https://bugs.kde.org/show_bug.cgi?id=358016 --- Comment #1 from p...@alicious.com --- Created attachment 96944 --> https://bugs.kde.org/attachment.cgi?id=96944&action=edit New crash information added by DrKonqi plasmashell (5.5.3) using Qt 5.5.1 - What I was doing when the application crashed: Attempting to start avast! from a search in the kickstart menu. -- Backtrace (Reduced): #6 0x7f3d7a21ea48 in memcpy (__len=96, __src=0x18, __dest=0x7f3d5c003868) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #7 mdb_txn_renew0 (txn=txn@entry=0x7f3d5c0037e0) at mdb.c:2593 #8 0x7f3d7a21fc10 in mdb_txn_begin (env=0x7f3d54003b10, parent=, flags=, ret=0x7f3d6fffe9c8) at mdb.c:2740 #9 0x7f3d7a8a3c6e in Baloo::SearchStore::exec (this=this@entry=0x7f3d6fffeab0, term=..., offset=0, limit=10, sortResults=) at ../../../src/lib/searchstore.cpp:74 #10 0x7f3d7a892c12 in Baloo::Query::exec (this=this@entry=0x7f3d6fffeb60) at ../../../src/lib/query.cpp:210 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358016] Plasmashell crashed just after login to desktop
https://bugs.kde.org/show_bug.cgi?id=358016 p...@alicious.com changed: What|Removed |Added CC||p...@alicious.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 303877] valgrind doesn't support compressed debuginfo sections.
https://bugs.kde.org/show_bug.cgi?id=303877 --- Comment #17 from Tom Hughes --- That's certainly useful to know about - it even has an "inflate only" version. It will still need some patching to stop it use memcpy/memset etc. -- You are receiving this mail because: You are watching all bug changes.
