[kexi] [Bug 276293] Wrong Icon at new Database Project
https://bugs.kde.org/show_bug.cgi?id=276293 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 156811] kexi crashes on importing mdb database.
https://bugs.kde.org/show_bug.cgi?id=156811 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 266824] Crash when clicking on the icon to assign action
https://bugs.kde.org/show_bug.cgi?id=266824 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 145429] Kexi Crash on MDB Import (Linux - Debian/Ubuntu)
https://bugs.kde.org/show_bug.cgi?id=145429 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 162947] Kexi crashes when adding new field to existing table
https://bugs.kde.org/show_bug.cgi?id=162947 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 336986] Map element is rendered only once per report
https://bugs.kde.org/show_bug.cgi?id=336986 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 336202] Non-uniform style of wording for tooltips of "Create" actions
https://bugs.kde.org/show_bug.cgi?id=336202 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 317764] Kexi crashed after data export
https://bugs.kde.org/show_bug.cgi?id=317764 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 283237] Kexi crashes sometimes in Queries when switching to data view
https://bugs.kde.org/show_bug.cgi?id=283237 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 307772] report crash when click to design mode
https://bugs.kde.org/show_bug.cgi?id=307772 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 287236] Kexi doesn't link on windows
https://bugs.kde.org/show_bug.cgi?id=287236 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 341750] Selected line doesn't stay in query data view
https://bugs.kde.org/show_bug.cgi?id=341750 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 319174] In Kubuntu 13.04, date entries are not retained in Kexi when entered in forms.
https://bugs.kde.org/show_bug.cgi?id=319174 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 351543] CTRL+S doesn't save record in form/table data edit mode
https://bugs.kde.org/show_bug.cgi?id=351543 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 339250] Keyboard 'delete' button does not work on Reports elements
https://bugs.kde.org/show_bug.cgi?id=339250 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 299394] Kexi crashed while switching to data view after query criteria changes
https://bugs.kde.org/show_bug.cgi?id=299394 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 279711] Kexi date of birth crash
https://bugs.kde.org/show_bug.cgi?id=279711 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 299392] Crash on switching to query data view
https://bugs.kde.org/show_bug.cgi?id=299392 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 288589] Cut and ctrl+z leads to crash
https://bugs.kde.org/show_bug.cgi?id=288589 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 283092] Kexi crashes on saving query design
https://bugs.kde.org/show_bug.cgi?id=283092 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 304757] Expose Undo/Redo in Table Designer to the user
https://bugs.kde.org/show_bug.cgi?id=304757 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 282285] Kexi crashes on mdb import
https://bugs.kde.org/show_bug.cgi?id=282285 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 358636] SQL queries don't work
https://bugs.kde.org/show_bug.cgi?id=358636 Jarosław Staniek changed: What|Removed |Added Latest Commit||http://commits.kde.org/call ||igra/2bb05472bca81d13565cf9 ||501ae04589d38e00a4 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Version Fixed In||2.9.11 --- Comment #2 from Jarosław Staniek --- Git commit 2bb05472bca81d13565cf9501ae04589d38e00a4 by Jaroslaw Staniek. Committed on 29/01/2016 at 19:43. Pushed by staniek into branch 'calligra/2.9'. Kexi: Make SQL queries work and fix Summary: - parses in Kexi>=2.9.7 but results in invalid (boolean) type/value - for convenience, if either argument is of text type, operator "+" is now assumed to be identical to operator || - also fix SELECT "a" || "b" for MySQL (using CONCAT() is needed) https://phabricator.kde.org/T677 FIXED-IN:2.9.11 Test Plan: Try test queries from the project attached at https://bugs.kde.org/show_bug.cgi?id=358636. Try other queries that use text columns instead of string constants. Reviewers: piggz, wicik Subscribers: Kexi-Devel-list Projects: #kexi, #calligra:_3.0 Differential Revision: https://phabricator.kde.org/D867 M +7-2kexi/kexidb/drivers/mysql/mysqldriver.cpp M +6-1kexi/kexidb/drivers/mysql/mysqldriver.h M +6-1libs/db/driver.cpp M +10 -1libs/db/driver.h M +20 -2libs/db/expression.cpp http://commits.kde.org/calligra/2bb05472bca81d13565cf9501ae04589d38e00a4 -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 358636] SQL queries don't work
https://bugs.kde.org/show_bug.cgi?id=358636 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356343] Rendering issue after upgrade to kwin 5.5
https://bugs.kde.org/show_bug.cgi?id=356343 Luc Lalonde changed: What|Removed |Added CC||luc.lalo...@polymtl.ca --- Comment #20 from Luc Lalonde --- This bug (seen on dual-head setup) reared is solved for me since I upgraded to Plasma 5.5.4. Yay! I can come back from GNOME 3 purgatory and start using KDE again ;-) Thank You! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 338506] image wallpapers are blurry in scaled and scaled and cropped mode
https://bugs.kde.org/show_bug.cgi?id=338506 dpross1...@gmail.com changed: What|Removed |Added CC||dpross1...@gmail.com --- Comment #39 from dpross1...@gmail.com --- I think this bug should get a higher priority, just because you can tell that a lot of work went into making Plasma 5 beautiful, and this bug spoils it. I am okay with working around it by saving cropped versions of my photos and using the centered wallpaper mode, but the average user isn't going to know what the problem is or how to work around it. They'll just get frustrated and switch to something else, which would be a shame. I'm looking forward to this getting fixed soon (fingers crossed). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 345403] "Terminal Size" setting in profile ignored
https://bugs.kde.org/show_bug.cgi?id=345403 subdiff changed: What|Removed |Added CC||subd...@gmail.com --- Comment #27 from subdiff --- Hi! FYI I requested a review for a possible fix: https://git.reviewboard.kde.org/r/126924/ The maintainer Kurt plans to look on the patch in the next few days. But I have not much experience in coding KDE stuff. So don't expect the fix to be perfect. It could also be the case, that it's not acceptable at all. You can still try it out though if you wish to by downloading the diff and compiling Konsole yourself with the patch (git apply mypatch). In any case, if there is something you want to have changed about the patch, just tell me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358749] New: Plasma crash when closing application
https://bugs.kde.org/show_bug.cgi?id=358749 Bug ID: 358749 Summary: Plasma crash when closing application Product: plasmashell Version: 5.5.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: br...@ioda-net.ch CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-2-default x86_64 Distribution: "openSUSE Tumbleweed (20160126) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: This time I closed a qml widget (weather configuration) I describe the cpu & plateform in bug #358748 The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd98eb9e900 (LWP 20217))] Thread 16 (Thread 0x7fd97683c700 (LWP 20220)): #0 0x7fd98811c24d in poll () at /lib64/libc.so.6 #1 0x7fd98cff2432 in () at /usr/lib64/libxcb.so.1 #2 0x7fd98cff4007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fd978fbce29 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fd98880d94f in () at /usr/lib64/libQt5Core.so.5 #5 0x7fd9879234a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7fd988124bdd in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7fd96f5ef700 (LWP 20227)): #0 0x7fd9848534b9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fd984810168 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd98481036c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd988a3252b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fd9889dc63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd988808b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fd98bad89a5 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fd98880d94f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fd9879234a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fd988124bdd in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7fd9633f2700 (LWP 20228)): #0 0x7fd9848534d4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fd98480fcd9 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd984810208 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd98481036c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fd988a3252b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd9889dc63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fd988808b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fd98bad89a5 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7fd98880d94f in () at /usr/lib64/libQt5Core.so.5 #9 0x7fd9879234a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7fd988124bdd in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7fd961b55700 (LWP 20229)): #0 0x7fd9848534b9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fd98480f899 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd984810193 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd98481036c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fd988a3252b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd9889dc63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fd988808b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fd98bad89a5 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7fd98880d94f in () at /usr/lib64/libQt5Core.so.5 #9 0x7fd9879234a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7fd988124bdd in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7fd95bfff700 (LWP 20230)): #0 0x7fd98792907f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd98e280a84 in () at /usr/lib64/libQt5Script.so.5 #2 0x7fd98e280ac9 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fd9879234a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fd988124bdd in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7fd8d3df9700 (LWP 20235)): #0 0x7fd9848534d4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fd98480f910 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd984810193 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd98481036c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fd988a3252b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd9889dc63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fd98880
[plasmashell] [Bug 358748] New: Plasma crash when closing an application
https://bugs.kde.org/show_bug.cgi?id=358748 Bug ID: 358748 Summary: Plasma crash when closing an application Product: plasmashell Version: 5.5.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: br...@ioda-net.ch CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-2-default x86_64 Distribution: "openSUSE Tumbleweed (20160126) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I was closing the nvidia-settings apps. But this kind of crashes (at least from a non expert eyes) happen a lot. The computer is a Dell Precison Mobile Workstation M7510 with Intel(R) Xeon(R) CPU E3-1535M v5 @ 2.90GHz Intel Gpu (unactive) P530 Nvidia Quadro M2000M Nvidia drivers used are 352.79 The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcf08c7e900 (LWP 4419))] Thread 35 (Thread 0x7fcef091c700 (LWP 4422)): #0 0x7fcf021fc24d in poll () at /lib64/libc.so.6 #1 0x7fcf070d2432 in () at /usr/lib64/libxcb.so.1 #2 0x7fcf070d4007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fcef309ce29 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fcf028ed94f in () at /usr/lib64/libQt5Core.so.5 #5 0x7fcf01a034a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7fcf02204bdd in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7fcee97b6700 (LWP 4439)): #0 0x7fcf01a0bcfc in __lll_lock_wait () at /lib64/libpthread.so.0 #1 0x7fcf01a05bb2 in pthread_mutex_lock () at /lib64/libpthread.so.0 #2 0x7fcefdd15fcc in () at /usr/X11R6/lib64/libGL.so.1 #3 0x7fcefdd1ab11 in () at /usr/X11R6/lib64/libGL.so.1 #4 0x7fcefdd1b018 in () at /usr/X11R6/lib64/libGL.so.1 #5 0x7fcef999b001 in () at /usr/lib64/tls/libnvidia-tls.so.352.79 #6 0x7fcefe932210 in () at /usr/lib64/libglib-2.0.so.0 #7 0x7fcefe8efd94 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #8 0x7fcefe8f0208 in () at /usr/lib64/libglib-2.0.so.0 #9 0x7fcefe8f036c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #10 0x7fcf02b1252b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7fcf02abc63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #12 0x7fcf028e8b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #13 0x7fcf05bb89a5 in () at /usr/lib64/libQt5Qml.so.5 #14 0x7fcf028ed94f in () at /usr/lib64/libQt5Core.so.5 #15 0x7fcf01a034a4 in start_thread () at /lib64/libpthread.so.0 #16 0x7fcf02204bdd in clone () at /lib64/libc.so.6 Thread 33 (Thread 0x7fcedd564700 (LWP 4447)): #0 0x7fcf021fc24d in poll () at /lib64/libc.so.6 #1 0x7fcefe8f0264 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fcefe8f036c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fcf02b1252b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fcf02abc63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fcf028e8b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fcf05bb89a5 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fcf028ed94f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fcf01a034a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fcf02204bdd in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7fced7b86700 (LWP 4453)): #0 0x7fcf021f822d in read () at /lib64/libc.so.6 #1 0x7fcef999af75 in () at /usr/lib64/tls/libnvidia-tls.so.352.79 #2 0x7fcefe932210 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fcefe8efd94 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7fcefe8f0208 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7fcefe8f036c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7fcf02b1252b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fcf02abc63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7fcf028e8b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7fcf05bb89a5 in () at /usr/lib64/libQt5Qml.so.5 #10 0x7fcf028ed94f in () at /usr/lib64/libQt5Core.so.5 #11 0x7fcf01a034a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7fcf02204bdd in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7fced61fb700 (LWP 4462)): #0 0x7fcf01a0907f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fcf08360a84 in () at /usr/lib64/libQt5Script.so.5 #2 0x7fcf08360ac9 in () at /usr/lib64/libQt5Script.so.5 #3 0x0
[kdenlive] [Bug 358223] Rotoscoping effect crashes kdenlive when played
https://bugs.kde.org/show_bug.cgi?id=358223 Try Again changed: What|Removed |Added CC||tryagainp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 358747] New: Amarok doesn't allow podcast scroll
https://bugs.kde.org/show_bug.cgi?id=358747 Bug ID: 358747 Summary: Amarok doesn't allow podcast scroll Product: amarok Version: 2.8.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Playback Assignee: amarok-bugs-d...@kde.org Reporter: danikva...@gmail.com CC: ma...@laitl.cz Amarok does not allow me to change position in a podcast, even if it is downloaded Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 357591] K3B Start
https://bugs.kde.org/show_bug.cgi?id=357591 Johannes Obermayr changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||johannesoberm...@gmx.de --- Comment #1 from Johannes Obermayr --- Please do on konsole: $ kdebugdialog --on k3b $ k3b Then attach full output here and set status back to UNCONFIRMED. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358734] [Hard] Incorrect 2nd square HSV color picker (checked by HCG color model)
https://bugs.kde.org/show_bug.cgi?id=358734 --- Comment #4 from acterhd --- Here is topic about HCG color model. https://forum.kde.org/viewtopic.php?f=288&t=130828 Also, In my github you can found modded files of krita. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 356359] Can't open documents with non-ascii filenames
https://bugs.kde.org/show_bug.cgi?id=356359 dani...@promorange.com changed: What|Removed |Added CC||dani...@promorange.com --- Comment #13 from dani...@promorange.com --- I experienced this issue after changing Collation in the Detailed Settings, now it looks to be solved by uncommenting the new locale in /etc/locale.gen and running # locale-gen as root. My current locale: LANG=en_DK.UTF-8 LC_CTYPE="en_DK.UTF-8" LC_NUMERIC=cs_CZ.UTF-8 LC_TIME="en_DK.UTF-8" LC_COLLATE=cs_CZ.UTF-8 LC_MONETARY=cs_CZ.UTF-8 LC_MESSAGES="en_DK.UTF-8" LC_PAPER="en_DK.UTF-8" LC_NAME="en_DK.UTF-8" LC_ADDRESS="en_DK.UTF-8" LC_TELEPHONE="en_DK.UTF-8" LC_MEASUREMENT="en_DK.UTF-8" LC_IDENTIFICATION="en_DK.UTF-8" LC_ALL= -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 358746] New: system settings crash upon close
https://bugs.kde.org/show_bug.cgi?id=358746 Bug ID: 358746 Summary: system settings crash upon close Product: systemsettings Version: 5.5.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: benk...@gmail.com Application: systemsettings5 (5.5.4) Qt Version: 5.5.1 Operating System: Linux 4.4.0-1-default x86_64 Distribution: "openSUSE Tumbleweed (20160117) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Every time I open system settings and open an individual kcm module, it crashes upon close. It doesn't appear to matter what I actually do in it, as long as I open a kcm. It does not crash if I merely open system settings and close it immediately. I do have system settings configured to display settings in a tree rather than as an icon grid, if that is relevant. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7cc1cf48c0 (LWP 27240))] Thread 3 (Thread 0x7f7cace59700 (LWP 27241)): #0 0x7f7cbda6f24d in poll () at /lib64/libc.so.6 #1 0x7f7cba899432 in () at /usr/lib64/libxcb.so.1 #2 0x7f7cba89b007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f7caf7dde29 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f7cbe16094f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f7cba0224a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f7cbda77bdd in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f7c95e0e700 (LWP 27264)): #0 0x7f7cbda6b22d in read () at /lib64/libc.so.6 #1 0x7f7cb598ff75 in () at /usr/lib64/nvidia/tls/libnvidia-tls.so.352.63 #2 0x7f7cb9b47210 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f7cb9b04d94 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7f7cb9b05208 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f7cb9b0536c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7f7cbe38552b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f7cbe32f63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7f7cbe15bb1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7f7cbc7089a5 in () at /usr/lib64/libQt5Qml.so.5 #10 0x7f7cbe16094f in () at /usr/lib64/libQt5Core.so.5 #11 0x7f7cba0224a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7f7cbda77bdd in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f7cc1cf48c0 (LWP 27240)): [KCrash Handler] #6 0x7f7cbdd2db98 in main_arena () at /lib64/libc.so.6 #7 0x7f7cbe362f19 in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () at /usr/lib64/libQt5Core.so.5 #8 0x7f7c9e749e66 in KParts::PartManager::~PartManager() () at /usr/lib64/libKF5Parts.so.5 #9 0x7f7c9e749ff9 in KParts::PartManager::~PartManager() () at /usr/lib64/libKF5Parts.so.5 #10 0x7f7cbe35d5ab in QObjectPrivate::deleteChildren() () at /usr/lib64/libQt5Core.so.5 #11 0x7f7cbe3668c0 in QObject::~QObject() () at /usr/lib64/libQt5Core.so.5 #12 0x7f7c9ee7b37b in KHTMLPart::~KHTMLPart() () at /usr/lib64/libKF5KHtml.so.5 #13 0x7f7c9ee7b479 in KHTMLPart::~KHTMLPart() () at /usr/lib64/libKF5KHtml.so.5 #14 0x7f7cbe35fda0 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #15 0x7f7cbfe6d8cc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #16 0x7f7cbfe729d6 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #17 0x7f7cbe331cf3 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #18 0x7f7cbe334016 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #19 0x7f7cbe385103 in () at /usr/lib64/libQt5Core.so.5 #20 0x7f7cb9b05097 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #21 0x7f7cb9b052c8 in () at /usr/lib64/libglib-2.0.so.0 #22 0x7f7cb9b0536c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #23 0x7f7cbe38550f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #24 0x7f7cbe32f63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #25 0x7f7cbe3372fd in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #26 0x0041074e in main () Possible duplicates by query: bug 355275. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358745] Strange drag and drop behaviour in folder view desktop layout
https://bugs.kde.org/show_bug.cgi?id=358745 --- Comment #1 from garwol --- Created attachment 96905 --> https://bugs.kde.org/attachment.cgi?id=96905&action=edit screen recording of a bug -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 349206] k3b.notifyrc, k3bui.rc and k3bdeviceui.rc is installed in deprecated path (kf5 branch)
https://bugs.kde.org/show_bug.cgi?id=349206 --- Comment #1 from Gustavo Alvarez --- not at all k3b.notifyrc still installed in wrong path the patch: http://sl1pkn07.wtf/paste/view/raw/b022d97f -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 355047] app-cdr/k3b-9999 (git version from kde-overlay) fails to build
https://bugs.kde.org/show_bug.cgi?id=355047 Johannes Obermayr changed: What|Removed |Added CC||johannesoberm...@gmx.de Resolution|--- |FIXED Latest Commit||734d5c452b987223f77519be5cc ||a94820289d077 Version Fixed In||2.9.90 Status|CONFIRMED |RESOLVED -- 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 #2 from Martin Klapetek --- Thanks for the report Do you perhaps see similar issues with other characters around Plasma? The panel clock, perhaps? -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 349206] k3b.notifyrc, k3bui.rc and k3bdeviceui.rc is installed in deprecated path (kf5 branch)
https://bugs.kde.org/show_bug.cgi?id=349206 Johannes Obermayr changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||2.9.90 Latest Commit||077056f1bee52782c8609e041a7 ||2a0337df954ac Resolution|--- |FIXED CC||johannesoberm...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 349204] kf5 port no detect the libmad plugin
https://bugs.kde.org/show_bug.cgi?id=349204 Johannes Obermayr changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||2.9.90 Status|CONFIRMED |RESOLVED Latest Commit||046a102f8042a2542c949de1e99 ||87baf5722e48a -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358745] Strange drag and drop behaviour in folder view desktop layout
https://bugs.kde.org/show_bug.cgi?id=358745 garwol changed: What|Removed |Added CC||garwol4...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358745] New: Strange drag and drop behaviour in folder view desktop layout
https://bugs.kde.org/show_bug.cgi?id=358745 Bug ID: 358745 Summary: Strange drag and drop behaviour in folder view desktop layout Product: plasmashell Version: 5.4.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: garwol4...@gmail.com CC: plasma-b...@kde.org Icons placement after dragging on desktop is often unpredictable. Its hard to place icon in desired location, it usually "snaps" to a grid next to it, if its not dropped exactly in the middle of a grid. Icons dragged out of view are placed in random positions, icons dropped under the panel cause extension of view and appearing of scrollbar at the edge of desktop. Reproducible: Always Steps to Reproduce: 1. drag icon over the desktop 2. drop out of view or under panel 3. icon is placed in wrong position -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358629] Notification popup not shown with 2 screen extended desktop
https://bugs.kde.org/show_bug.cgi?id=358629 --- Comment #3 from Martin Klapetek --- Ok; plasma-workspace? -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 358744] New: Kopete crashes on closing message tab
https://bugs.kde.org/show_bug.cgi?id=358744 Bug ID: 358744 Summary: Kopete crashes on closing message tab Product: kopete Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kopete-bugs-n...@kde.org Reporter: malte.ge...@googlemail.com Application: kopete (1.7.3) KDE Platform Version: 4.14.15 Qt Version: 4.8.6 Operating System: Linux 4.2.0-25-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: Kopete is crashing if i close a message tab. It is also crashing on quitting kopete with the main window menu item "Quit" The crash can be reproduced every time. -- Backtrace: Application: Kopete (kopete), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5d83eb7840 (LWP 2656))] Thread 4 (Thread 0x7f5d6c06a700 (LWP 2660)): #0 0x7f5d7b632884 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f5d7b5eda59 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5d7b5ee167 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5d7b5ee2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f5d8194620e in QEventDispatcherGlib::processEvents (this=0x7f5d640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #5 0x7f5d819140d1 in QEventLoop::processEvents (this=this@entry=0x7f5d6c069d40, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f5d81914445 in QEventLoop::exec (this=this@entry=0x7f5d6c069d40, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f5d818034f9 in QThread::exec (this=this@entry=0x10bf060) at thread/qthread.cpp:538 #8 0x7f5d818f4133 in QInotifyFileSystemWatcherEngine::run (this=0x10bf060) at io/qfilesystemwatcher_inotify.cpp:265 #9 0x7f5d81805d1c in QThreadPrivate::start (arg=0x10bf060) at thread/qthread_unix.cpp:349 #10 0x7f5d7beda6aa in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #11 0x7f5d801d1eed in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7f5d62039700 (LWP 2667)): #0 0x7fffaf1aeb6d in clock_gettime () #1 0x7f5d801e038d in clock_gettime () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7f5d81860565 in do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:127 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:144 #4 0x7f5d819470a5 in QTimerInfoList::updateCurrentTime (this=0x7f5d54002ce0) at kernel/qeventdispatcher_unix.cpp:354 #5 QTimerInfoList::timerWait (this=0x7f5d54002ce0, tm=...) at kernel/qeventdispatcher_unix.cpp:460 #6 0x7f5d819458dc in timerSourcePrepareHelper (src=, timeout=0x7f5d62038b14) at kernel/qeventdispatcher_glib.cpp:143 #7 0x7f5d7b5ed77d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f5d7b5ee11b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f5d7b5ee2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f5d8194620e in QEventDispatcherGlib::processEvents (this=0x7f5d540008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #11 0x7f5d819140d1 in QEventLoop::processEvents (this=this@entry=0x7f5d62038ce0, flags=...) at kernel/qeventloop.cpp:149 #12 0x7f5d81914445 in QEventLoop::exec (this=this@entry=0x7f5d62038ce0, flags=...) at kernel/qeventloop.cpp:204 #13 0x7f5d818034f9 in QThread::exec (this=) at thread/qthread.cpp:538 #14 0x7f5d6851cb2a in ?? () from /usr/lib/kde4/kopete_jabber.so #15 0x7f5d81805d1c in QThreadPrivate::start (arg=0x13c4d40) at thread/qthread_unix.cpp:349 #16 0x7f5d7beda6aa in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #17 0x7f5d801d1eed in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7f5d58ebc700 (LWP 8955)): #0 0x7f5d801c249d in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f5d7b6314e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5d7b5edcd4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5d7b5ee190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f5d7b5ee2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f5d8194620e in QEventDispatcherGlib::processEvents (this=0x7f5d480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #6 0x7f5d819140d1 in QEventLoop::processEvents (this=this@entry=0x7f5d58ebbd40, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f5d81914445 in QEventLoop::exec (this=this@entry=0x7f5d58ebbd40, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f5d818034f9 in QThread::exec (this=this@entry=0x273ac50) at thread/qthread.cpp:538 #9 0x7f5d818f4133 in QInotifyFileSystemWat
[rkward] [Bug 358743] New: Plugin windows disappear behind main window, when closing detached plot preview
https://bugs.kde.org/show_bug.cgi?id=358743 Bug ID: 358743 Summary: Plugin windows disappear behind main window, when closing detached plot preview Product: rkward Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: rkward-de...@kde.org Reporter: thomas.friedrichsme...@ruhr-uni-bochum.de Reported for tracking on behalf of Meik: > speaking of the plot previews, one thing that is constantly bugging > me is that disabling a preview automatically "hides" the dialog > window behind RKWard's main window. ---Session Info--- -- Frontend -- RKWard version: 0.6.4z+0.6.5+devel1 KDE version (runtime): 4.14.13 KDE version (compile time): 4.14.13 Qt build key: x86_64 linux g++-4 full-config Local KDE directory: /home/thomas/.kde/ RKWard storage directory: /home/thomas/.rkward/ Backend version (as known to the frontend): 3.2.2 Debug message file (this may contain relevant diagnostic output in case of trouble): /tmp/rkward.frontend.j10241 -- Backend -- Debug message file (this may contain relevant diagnostic output in case of trouble): /tmp/rkward.rbackend.J10247 R version (compile time): 3.2.2 (2015-08-14 r69053) R runtime session info: R version 3.2.2 (2015-08-14) Platform: x86_64-pc-linux-gnu (64-bit) Running under: Ubuntu 15.10 locale: [1] LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C [3] LC_TIME=de_DE.UTF-8 LC_COLLATE=en_US.UTF-8 [5] LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=C [7] LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 [9] LC_ADDRESS=de_DE.UTF-8LC_TELEPHONE=de_DE.UTF-8 [11] LC_MEASUREMENT=de_DE.UTF-8LC_IDENTIFICATION=de_DE.UTF-8 attached base packages: [1] stats graphics grDevices utils datasets methods base other attached packages: [1] rkward_0.6.3 loaded via a namespace (and not attached): [1] tools_3.2.2 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 353482] Akonadi will not load in PMI files.
https://bugs.kde.org/show_bug.cgi?id=353482 bu...@gmx.at changed: What|Removed |Added CC||bu...@gmx.at -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 353482] Akonadi will not load in PMI files.
https://bugs.kde.org/show_bug.cgi?id=353482 --- Comment #11 from bu...@gmx.at --- Created attachment 96904 --> https://bugs.kde.org/attachment.cgi?id=96904&action=edit New crash information added by DrKonqi kaddressbook (5.0.2) using Qt 5.5.1 - What I was doing when the application crashed: I just opened the application. I have one Google contact account configured. -- Backtrace (Reduced): #7 0xb54d226a in Akonadi::Tag::operator= (this=0xbffd4df4, other=...) at ../../../../akonadi/src/core/tag.cpp:80 #8 0xb54d23cf in Akonadi::Tag::Tag (this=0xbffd4df4, other=...) at ../../../../akonadi/src/core/tag.cpp:72 #9 0xb5571537 in Akonadi::TagModelPrivate::tagForIndex (this=0x91d0b80, index=...) at ../../../../akonadi/src/core/models/tagmodel_p.cpp:105 #10 0xb557032c in Akonadi::TagModel::data (this=0x91d1cd0, index=..., role=258) at ../../../../akonadi/src/core/models/tagmodel.cpp:91 #11 0xb7626145 in CategorySelectWidgetPrivate::slotTagsInserted (this=0x91cdd80, parent=..., start=0, end=0) at ../../kaddressbook/categoryselectwidget.cpp:173 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 358742] New: Kontact (Akregator) crashed after clicking "more" on a feed
https://bugs.kde.org/show_bug.cgi?id=358742 Bug ID: 358742 Summary: Kontact (Akregator) crashed after clicking "more" on a feed Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: bor...@gmail.com Application: kontact (4.14.9) KDE Platform Version: 4.14.9 Qt Version: 4.8.6 Operating System: Linux 3.16.7-29-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: Was reading a feed in the Kontact (Akregator) window. Clicked on "more" to read more of the feed, which switched me to Firefox. As I read the feed in the firefox browser I noticed that Kontact had closed and the crash Reporting Assistant was up on the screen. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3af4812800 (LWP 1630))] Thread 45 (Thread 0x7f3ad7316700 (LWP 1637)): #0 0x7f3aebe1605f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3aef5bc686 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f3aef5bc6b9 in () at /usr/lib64/libQtWebKit.so.4 #3 0x7f3aebe120a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f3af1d9f08d in clone () at /lib64/libc.so.6 Thread 44 (Thread 0x7f3a96a13700 (LWP 1653)): #0 0x7f3aebe1605f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3aef32ee7d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f3aef5e41e6 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x7f3aebe120a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f3af1d9f08d in clone () at /lib64/libc.so.6 Thread 43 (Thread 0x7f3a7f156700 (LWP 1781)): #0 0x7f3af1d96c5d in poll () at /lib64/libc.so.6 #1 0x7f3aeb846be4 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f3aeb846cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f3af25190de in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7f3af24eae6f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f3af24eb165 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f3af23e80bf in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7f3af23ea79f in () at /usr/lib64/libQtCore.so.4 #8 0x7f3aebe120a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f3af1d9f08d in clone () at /lib64/libc.so.6 Thread 42 (Thread 0x7f3a777fe700 (LWP 7340)): #0 0x7f3af1d96c5d in poll () at /lib64/libc.so.6 #1 0x7f3aeb846be4 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f3aeb846f0a in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0 #3 0x7f3a58ae8946 in () at /usr/lib64/libgio-2.0.so.0 #4 0x7f3aeb86bb85 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f3aebe120a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f3af1d9f08d in clone () at /lib64/libc.so.6 Thread 41 (Thread 0x7f3a77fff700 (LWP 7341)): #0 0x7f3aeb8464ae in g_main_context_query () at /usr/lib64/libglib-2.0.so.0 #1 0x7f3aeb846b52 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f3aeb846cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f3aeb846d29 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f3aeb86bb85 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f3aebe120a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f3af1d9f08d in clone () at /lib64/libc.so.6 Thread 40 (Thread 0x7f3a51479700 (LWP 7344)): #0 0x7f3aebe1605f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3a514e0d79 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #2 0x7f3a514e1819 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #3 0x7f3aebe120a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f3af1d9f08d in clone () at /lib64/libc.so.6 Thread 39 (Thread 0x7f3a50c78700 (LWP 7345)): #0 0x7f3aebe1605f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3a514e0d79 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #2 0x7f3a514e1819 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #3 0x7f3aebe120a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f3af1d9f08d in clone () at /lib64/libc.so.6 Thread 38 (Thread 0x7f3a50477700 (LWP 7346)): #0 0x7f3aebe1605f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3a514e0d79 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #2 0x7f3a514e1819 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin
[kdenlive] [Bug 358741] New: 15.13 git master: extract frame exports proxy clip frame instead of original clip frame
https://bugs.kde.org/show_bug.cgi?id=358741 Bug ID: 358741 Summary: 15.13 git master: extract frame exports proxy clip frame instead of original clip frame Product: kdenlive Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: wegwerf-1-...@gmx.de When extracting a frame in the clip monitor from a clip with a proxy, Kdenlive exports the frame from the proxy. This results in low quality exported frames. Instead, Kdenlive should export the frame from the original clip but never from the proxy clip. Reproducible: Always Steps to Reproduce: 1. Add clip to project. 2. Create proxy for clip. 3. Export frame from this clip with proxy. 4. Check quality of exported frame. Actual Results: Low-quality frame exported from proxy clip. Expected Results: Original quality frame exported from original clip. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358741] 15.13 git master: extract frame exports proxy clip frame instead of original clip frame
https://bugs.kde.org/show_bug.cgi?id=358741 wegwerf-1-...@gmx.de changed: What|Removed |Added CC||wegwerf-1-...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 358740] New: Utils::isInitializedExternally: getSingleDecl fails to account for multiple declarations
https://bugs.kde.org/show_bug.cgi?id=358740
Bug ID: 358740
Summary: Utils::isInitializedExternally: getSingleDecl fails to
account for multiple declarations
Product: clazy
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: j...@kde.org
CC: smart...@kde.org
The following minimal example causes an assertion failure within clang in a
code path triggered by the clazy plugin:
#include
void x()
{
QList list;
int a, b;
}
Here's the backtrace:
(gdb) bt
#0 0x7fffec04989b in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
#1 0x7fffec04ae51 in __GI_abort () at abort.c:89
#2 0x7fffec041fb8 in __assert_fail_base (fmt=0x7fffec18ace0 "%s%s%s:%u:
%s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fffe4b00fe0
"isSingleDecl() && \"Isn't a declgroup\"",
file=file@entry=0x7fffe4b01006 "/usr/include/clang/AST/DeclGroup.h",
line=line@entry=88, function=function@entry=0x7fffe4b01029 "clang::Decl
*clang::DeclGroupRef::getSingleDecl()") at assert.c:92
#3 0x7fffec042076 in __GI___assert_fail (assertion=0x7fffe4b00fe0
"isSingleDecl() && \"Isn't a declgroup\"", file=0x7fffe4b01006
"/usr/include/clang/AST/DeclGroup.h", line=88,
function=0x7fffe4b01029 "clang::Decl
*clang::DeclGroupRef::getSingleDecl()") at assert.c:101
#4 0x7fffe4a02cea in clang::DeclGroupRef::getSingleDecl() () from
/home/jkt/.local/lib64/ClangLazy.so
#5 0x7fffe4a028c9 in clang::DeclStmt::getSingleDecl() () from
/home/jkt/.local/lib64/ClangLazy.so
#6 0x7fffe4acb339 in Utils::isInitializedExternally(clang::VarDecl*) ()
from /home/jkt/.local/lib64/ClangLazy.so
#7 0x7fffe4a0877e in
InefficientQListBase::shouldIgnoreVariable(clang::VarDecl*) const () from
/home/jkt/.local/lib64/ClangLazy.so
#8 0x7fffe4a08828 in InefficientQListBase::VisitDecl(clang::Decl*) () from
/home/jkt/.local/lib64/ClangLazy.so
#9 0x7fffe49dbe26 in CheckBase::VisitDeclaration(clang::Decl*) () from
/home/jkt/.local/lib64/ClangLazy.so
#10 0x7fffe4a45323 in (anonymous
namespace)::LazyASTConsumer::VisitDecl(clang::Decl*) () from
/home/jkt/.local/lib64/ClangLazy.so
#11 0x7fffe4a45285 in clang::RecursiveASTVisitor<(anonymous
namespace)::LazyASTConsumer>::WalkUpFromDecl(clang::Decl*) () from
/home/jkt/.local/lib64/ClangLazy.so
#12 0x7fffe4a7ba45 in clang::RecursiveASTVisitor<(anonymous
namespace)::LazyASTConsumer>::WalkUpFromNamedDecl(clang::NamedDecl*) () from
/home/jkt/.local/lib64/ClangLazy.so
#13 0x7fffe4a7dfa5 in clang::RecursiveASTVisitor<(anonymous
namespace)::LazyASTConsumer>::WalkUpFromValueDecl(clang::ValueDecl*) () from
/home/jkt/.local/lib64/ClangLazy.so
#14 0x7fffe4a7def5 in clang::RecursiveASTVisitor<(anonymous
namespace)::LazyASTConsumer>::WalkUpFromDeclaratorDecl(clang::DeclaratorDecl*)
() from /home/jkt/.local/lib64/ClangLazy.so
#15 0x7fffe4a7eba5 in clang::RecursiveASTVisitor<(anonymous
namespace)::LazyASTConsumer>::WalkUpFromVarDecl(clang::VarDecl*) () from
/home/jkt/.local/lib64/ClangLazy.so
#16 0x7fffe4a4223d in clang::RecursiveASTVisitor<(anonymous
namespace)::LazyASTConsumer>::TraverseVarDecl(clang::VarDecl*) () from
/home/jkt/.local/lib64/ClangLazy.so
#17 0x7fffe4a3ecf5 in clang::RecursiveASTVisitor<(anonymous
namespace)::LazyASTConsumer>::TraverseDecl(clang::Decl*) () from
/home/jkt/.local/lib64/ClangLazy.so
#18 0x7fffe4a56654 in clang::RecursiveASTVisitor<(anonymous
namespace)::LazyASTConsumer>::TraverseDeclStmt(clang::DeclStmt*) () from
/home/jkt/.local/lib64/ClangLazy.so
#19 0x7fffe4a46c41 in clang::RecursiveASTVisitor<(anonymous
namespace)::LazyASTConsumer>::TraverseStmt(clang::Stmt*) () from
/home/jkt/.local/lib64/ClangLazy.so
#20 0x7fffe4a5641f in clang::RecursiveASTVisitor<(anonymous
namespace)::LazyASTConsumer>::TraverseCompoundStmt(clang::CompoundStmt*) ()
from /home/jkt/.local/lib64/ClangLazy.so
#21 0x7fffe4a46be7 in clang::RecursiveASTVisitor<(anonymous
namespace)::LazyASTConsumer>::TraverseStmt(clang::Stmt*) () from
/home/jkt/.local/lib64/ClangLazy.so
#22 0x7fffe4a7e5f0 in clang::RecursiveASTVisitor<(anonymous
namespace)::LazyASTConsumer>::TraverseFunctionHelper(clang::FunctionDecl*) ()
from /home/jkt/.local/lib64/ClangLazy.so
#23 0x7fffe4a41e20 in clang::RecursiveASTVisitor<(anonymous
namespace)::LazyASTConsumer>::TraverseFunctionDecl(clang::FunctionDecl*) ()
from /home/jkt/.local/lib64/ClangLazy.so
#24 0x7fffe4a3eb66 in clang::RecursiveASTVisitor<(anonymous
namespace)::LazyASTConsumer>::TraverseDecl(clang::Decl*) () from
/home/jkt/.local/lib64/ClangLazy.so
#25 0x7fffe4a45215 in clang::RecursiveASTVisitor<(anonymous
namespace)::LazyASTConsumer>::TraverseDeclContextHelper(clang::DeclContext*) ()
from /home/jkt/.local/lib64/ClangLa
[calligraflow] [Bug 358739] New: Flow needs the option to label a connector
https://bugs.kde.org/show_bug.cgi?id=358739 Bug ID: 358739 Summary: Flow needs the option to label a connector Product: calligraflow Version: 2.9.7 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: yue@mail.com Reporter: danikva...@gmail.com There needs to be an option to label connectors in Calligra Flow Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 337079] sddm theme doesn't focus password field
https://bugs.kde.org/show_bug.cgi?id=337079 Hugo Parente Lima changed: What|Removed |Added CC||hugo...@gmail.com --- Comment #17 from Hugo Parente Lima --- No focus to me too on start-up. sddm 0.13.0-2 plasma 5.5.4 notebook + monitor -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 325335] kio-mtp fails with Windows Phone 8X
https://bugs.kde.org/show_bug.cgi?id=325335 Ysarior changed: What|Removed |Added CC||brice.saug...@scle.fr -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358738] New: Krita crashes when opening any file or creating new one
https://bugs.kde.org/show_bug.cgi?id=358738 Bug ID: 358738 Summary: Krita crashes when opening any file or creating new one Product: krita Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: federico.fi...@gmail.com Application: krita (2.9.10 (git ed01576)) KDE Platform Version: 4.14.2 (Compiled from sources) Qt Version: 4.8.6 Operating System: Linux 3.16.0-38-generic x86_64 Distribution: Linux Mint 17.2 Rafaela -- Information about the crash: - What I was doing when the application crashed: Open a .kra file or create a new file. Krita crashes seconds later, before the action is complete. The crash can be reproduced every time. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6cbb149800 (LWP 2843))] Thread 7 (Thread 0x7f6c8b7fe700 (LWP 2851)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6cb8ee2816 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f6cb8ede95b in QSemaphore::acquire(int) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x7f6cb729ac1e in KisTileDataPooler::waitForWork (this=this@entry=0x297f930) at /home/federico/kde4/src/calligra/krita/image/tiles3/kis_tile_data_pooler.cc:165 #4 0x7f6cb729b03d in KisTileDataPooler::run (this=0x297f930) at /home/federico/kde4/src/calligra/krita/image/tiles3/kis_tile_data_pooler.cc:187 #5 0x7f6cb8ee232f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f6cb3156182 in start_thread (arg=0x7f6c8b7fe700) at pthread_create.c:312 #7 0x7f6cb868247d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 6 (Thread 0x7f6c8bfff700 (LWP 2852)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6cb8ee2816 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f6cb8eded63 in QSemaphore::tryAcquire(int, int) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x7f6cb72b7653 in KisTileDataSwapper::waitForWork (this=) at /home/federico/kde4/src/calligra/krita/image/tiles3/swap/kis_tile_data_swapper.cpp:86 #4 0x7f6cb72b78ea in KisTileDataSwapper::run (this=0x297f970) at /home/federico/kde4/src/calligra/krita/image/tiles3/swap/kis_tile_data_swapper.cpp:92 #5 0x7f6cb8ee232f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f6cb3156182 in start_thread (arg=0x7f6c8bfff700) at pthread_create.c:312 #7 0x7f6cb868247d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 5 (Thread 0x7f6c8a7fc700 (LWP 2854)): #0 0x7f6cb8679da3 in select () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f6cb900f2c7 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timeval const*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f6cb9014824 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timeval*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x7f6cb9014c92 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f6cb8fe30af in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7f6cb8fe33a5 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f6cb8edfc5f in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f6cb8fc4823 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7f6cb8ee232f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7f6cb3156182 in start_thread (arg=0x7f6c8a7fc700) at pthread_create.c:312 #10 0x7f6cb868247d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7f6c89ffb700 (LWP 2855)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6cb8ee2816 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f6cb9eb3e16 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #3 0x7f6cb8ee232f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f6cb3156182 in start_thread (arg=0x7f6c89ffb700) at pthread_create.c:312 #5 0x7f6cb868247d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7f6c88f7e700 (LWP 2856)): #0 0x7f6cb8679da3 in select () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f6cb900f2c7 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timeval const*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #
[krita] [Bug 358734] [Hard] Incorrect 2nd square HSV color picker (checked by HCG color model)
https://bugs.kde.org/show_bug.cgi?id=358734 acterhd changed: What|Removed |Added Attachment #96903|0 |1 is obsolete|| -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358734] [Hard] Incorrect 2nd square HSV color picker (checked by HCG color model)
https://bugs.kde.org/show_bug.cgi?id=358734 --- Comment #3 from acterhd --- Created attachment 96903 --> https://bugs.kde.org/attachment.cgi?id=96903&action=edit Changed files Most files was changed. Later I give real patch. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355570] plasmashell crashes every time I right click on a folder and move the mouse up and down on the context menu.
https://bugs.kde.org/show_bug.cgi?id=355570 sac changed: What|Removed |Added CC||j1563...@trbvm.com --- Comment #3 from sac --- (In reply to John Choate from comment #2) > I fixed this by doing the following in Dolphin: > Configure Dolphin > Services > Uncheck 'File to activity linking plugin'. > Plasmashell and dolphin have not crashed when hovering mouse in the context > menu since I did that. Great thanks. I already created 357453, including a detailed dumb of the crash until I found this bug and workaround by coincidence. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358629] Notification popup not shown with 2 screen extended desktop
https://bugs.kde.org/show_bug.cgi?id=358629 --- Comment #2 from Ian Newton --- Plasma 5.18.0 -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 358655] Umbrello does not import private class
https://bugs.kde.org/show_bug.cgi?id=358655 --- Comment #12 from Ken Standard --- OK, maybe we are having a language barrier - not sure. When talking about "project import" for a Qt project, you cannot ignore the .pro file - it is the project. Are we redefining "project" to mean only the .h,.hpp,/h++, etc. and the .cpp implementations in the "project"? Or are we accepting the "project" definition as is common to Qt and defined by the .pro file. Besides all that. When the actions described are performed and the entire project is imported correctly. It serves no purpose for me to post a bug if I have not performed every options to resolve the problem BEFORE submitting the bug. That should be obvious from comment 8. My point is that I should not have to do half of that. The project files should alreays be displayed according to the filter pattern, instead it must be modified first, then they are displayed. Secondly, folders are included in the selection process but that does not select the files underneath that match the selection pattern - not intuitive. Do one or the other but not both. Even when all the files in a folder are selected, the import to a class diagram is not always 100%. Sometimes files are not converted. I gave the example of a .cpp file where a "//" comment was detected as an error. This syntax is completely valid C++ comment style and should not error. When coverted to a "C" style comment (/* */) there is no error. This is not proper - both are correct. I submitted the bug because your procedure in comment 11 does not work - especially if headers and implementation files are in separate folders or if there are multiple sub-projects. I don't want to get too far afield here but my original bug is still valid and I think I have proven it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357453] Plasma5 Crash on folder view desktop while selecting properties of an icon
https://bugs.kde.org/show_bug.cgi?id=357453 sac changed: What|Removed |Added Platform|Ubuntu Packages |Compiled Sources Depends on||355570 --- Comment #2 from sac --- "I fixed this by doing the following in Dolphin: Configure Dolphin > Services > Uncheck 'File to activity linking plugin'." --> workaround working for me, too; Amazing that a crash for the complete Shell that affects >90% of the userbase can be open for months (because of a new feature that is probably only used/known by 1%). Reason why we're not flooded with tickets is that the automatic bug reporting cannot be used for this one (I was just able to create the dump by luck after many trys). I suggest to deactivate Dolphin " 'File to activity linking plugin'" by default as a first solution measure. Fixing this feature (whatever it does) can be done in a seperate INC. If someone's currently collecting donations for a QA, ping me and I'll support ;) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355570] plasmashell crashes every time I right click on a folder and move the mouse up and down on the context menu.
https://bugs.kde.org/show_bug.cgi?id=355570 sac changed: What|Removed |Added Blocks||357453 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 358737] New: Dolphin crashes after click on "Configure Dolphin"
https://bugs.kde.org/show_bug.cgi?id=358737
Bug ID: 358737
Summary: Dolphin crashes after click on "Configure Dolphin"
Product: dolphin
Version: 15.12.1
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: sdi...@live.de
Application: dolphin (15.12.1)
KDE Platform Version: 5.5.4
Qt Version: 5.5.1
Operating System: Linux 4.1.16-1-lts x86_64
Distribution: Antergos
Output to stderr:
KSambaShare: Could not find smb.conf!
QLayout: Cannot add a null widget to QVBoxLayout/
QLayout: Cannot add a null widget to QVBoxLayout/
initialization OK, home trash dir: "/home/sebastian/.local/share/Trash"
"Tag 'b' is not defined in message {<__kuit_internal_top__>Check this box
to allow automatic deletion o...}."
"Tag 'b' is not defined in message {<__kuit_internal_top__>Check this box
to allow automatic deletion o...}."
QLayout: Attempting to add QLayout "" to PreviewsSettingsPage "", which already
has a layout
QLayout: Cannot add a null widget to QVBoxLayout/
QLayout: Cannot add a null widget to QVBoxLayout/
initialization OK, home trash dir: "/home/sebastian/.local/share/Trash"
"Tag 'b' is not defined in message {<__kuit_internal_top__>Check this box
to allow automatic deletion o...}."
"Tag 'b' is not defined in message {<__kuit_internal_top__>Check this box
to allow automatic deletion o...}."
QLayout: Attempting to add QLayout "" to PreviewsSettingsPage "", which already
has a layout
QLayout: Cannot add a null widget to QVBoxLayout/
QLayout: Cannot add a null widget to QVBoxLayout/
initialization OK, home trash dir: "/home/sebastian/.local/share/Trash"
"Tag 'b' is not defined in message {<__kuit_internal_top__>Check this box
to allow automatic deletion o...}."
"Tag 'b' is not defined in message {<__kuit_internal_top__>Check this box
to allow automatic deletion o...}."
QLayout: Attempting to add QLayout "" to PreviewsSettingsPage "", which already
has a layout
When I was using valgrind to analyse the problem, no crash occurred.
Reproducible: Sometimes
Steps to Reproduce:
1. Left click on Control menu
2. Left click on Configure Dolphin
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 358734] [Hard] Incorrect 2nd square HSV color picker (checked by HCG color model)
https://bugs.kde.org/show_bug.cgi?id=358734 --- Comment #2 from acterhd --- Created attachment 96902 --> https://bugs.kde.org/attachment.cgi?id=96902&action=edit HCG screenshot Bug fixed version (with HCG color model). -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 358736] New: KDE component crashes during logging
https://bugs.kde.org/show_bug.cgi?id=358736 Bug ID: 358736 Summary: KDE component crashes during logging Product: kdelibs Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: kded Assignee: unassigned-b...@kde.org Reporter: andriy.trotse...@gmail.com Application: kded4 (4.14.9) KDE Platform Version: 4.14.9 Qt Version: 4.8.6 Operating System: Linux 3.16.7-29-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I've logged into the KDE and it's crashed. It's happens under root and regular user. It was started today, after two new updates was installed (I dont remember which one). The crash can be reproduced every time. -- Backtrace: Application: KDE Daemon (kded4), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa570292780 (LWP 3498))] Thread 4 (Thread 0x7fa54e598700 (LWP 3558)): #0 0x7ffcdd6c4b35 in () #1 0x7fff in () #2 0x6ef19260 in () #3 0x30002ee07fa5 in () #4 0x4e597c687fa5 in () #5 0x4e597c007fa5 in () #6 0x7fff7fa5 in () #7 0x6ef19000 in () #8 0x4e597c707fa5 in () #9 0x6d8cdccd7fa5 in () #10 0x6efcc5477fa5 in () #11 0x6ee3ed477fa5 in () #12 0x00027fa5 in () #13 0x30001c20 in () #14 0x05217fa5 in () #15 0x30002ee0 in () #16 0x00099b527fa5 in () #17 0x6ef1a875 in () #18 0x7fa5 in () #19 0x4e597c647fa5 in () #20 0x4e597c707fa5 in () #21 0x4e597c687fa5 in () #22 0x7fa5 in () #23 0x6ef18f8c in () #24 0x7fa5 in () #25 0x in () Thread 3 (Thread 0x7fa54db90700 (LWP 3572)): #0 0x7fa56d8b8c5d in poll () at /lib64/libc.so.6 #1 0x7fa56a9cbbe4 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa56a9cbcec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa56ef190de in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7fa56eeeae6f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7fa56eeeb165 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7fa56ede80bf in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7fa552bf0287 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #8 0x7fa56edea79f in () at /usr/lib64/libQtCore.so.4 #9 0x7fa56eb540a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7fa56d8c108d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fa54d38f700 (LWP 3573)): #0 0x7fa56d8b8c5d in poll () at /lib64/libc.so.6 #1 0x7fa56a9cbbe4 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa56a9cbcec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa56ef190de in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7fa56eeeae6f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7fa56eeeb165 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7fa56ede80bf in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7fa56edea79f in () at /usr/lib64/libQtCore.so.4 #8 0x7fa56eb540a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fa56d8c108d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fa570292780 (LWP 3498)): [KCrash Handler] #5 0x7fa55388e730 in KScreen::Mode::size() const () at /usr/lib64/libkscreen.so.1 #6 0x7fa553aa2559 in () at /usr/lib64/kde4/kded_kscreen.so #7 0x7fa553aa2ea0 in () at /usr/lib64/kde4/kded_kscreen.so #8 0x7fa553aa4cfb in () at /usr/lib64/kde4/kded_kscreen.so #9 0x7fa553a9c6b7 in KScreenDaemon::applyIdealConfig() () at /usr/lib64/kde4/kded_kscreen.so #10 0x7fa553a9c8ee in KScreenDaemon::applyConfig() () at /usr/lib64/kde4/kded_kscreen.so #11 0x7fa56ef001fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #12 0x7fa56ef001fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #13 0x7fa553aa701e in () at /usr/lib64/kde4/kded_kscreen.so #14 0x7fa56ef001fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #15 0x7fa56bc71b5f in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () at /usr/lib64/libQtDBus.so.4 #16 0x7fa56ef0459e in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4 #17 0x7fa56e06876c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #18 0x7fa56e06ecad in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #19 0x7fa56fc
[KScreen] [Bug 355928] kscreen reports change of primary screen without apparent reason
https://bugs.kde.org/show_bug.cgi?id=355928 Maxime Chassagneux changed: What|Removed |Added CC||maxime.chassagn...@gmail.co ||m --- Comment #12 from Maxime Chassagneux --- Lot of this kind of line for me too (NVIDIA driver) org.kde.KScreen[1506]: kscreen: Primary output changed from KScreen::Output(Id: 638 , Name: "DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 638 , Name: "DVI-D-0" ) ( "DVI-D-0" ) All the time, the same line. Dual head conf ( 2 HDMI , my screen + one TV ) Some time, I have this line too : kscreen_backend[1722]: segfault at 10 ip 7f9ededaba22 sp 7ffd5cbe2dd0 error 4 in KSC_XRandR.so[7f9eded98000+2] And after, all context menu on plasma don't appear. Don't know if it's concerns about this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358735] New: Several seemingly related monitor connect/disconnect issues
https://bugs.kde.org/show_bug.cgi?id=358735 Bug ID: 358735 Summary: Several seemingly related monitor connect/disconnect issues Product: plasmashell Version: master Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: t...@r.je CC: bhus...@gmail.com, plasma-b...@kde.org I have a desktop and laptop and both suffer problems with monitors, I'm assuming these are related as the problems are similar. My desktop suffers the problem detailed here: https://bugs.kde.org/show_bug.cgi?id=340267 but with slightly different results: 1. Turn the monitor off 2. Turn the monitor on 3. Sometimes plasma will crash entirely and return to SDDM 3a. Sometimes plasma will still be running but in an unstable state, all window decorations will disappear from opened windows and new programs cannot be launched. Existing programs can be used as normal (although not moved around the screen or minimized/maximized). I have to fix this by restarting SDDM in another TTY Alternative problem: 1. Log out of plasma back to the SDDM login screen 2. Turn off the monitor 3. Turn on the monitor 4. SDDM now displays a black screen and a mouse pointer. The only way to recover is switching to a different TTY and restarting SDDM. This may be an SDDM bug, if it is, it may help you track down the problems with Plasma. Hardware: nvidia GTX 980Ti using nvidia driver + Asus P287Q Secondly, I have different, but similar problems with my laptop Firstly using HDMI out: 1. Sometimes when connecting a HDMI monitor plasma would crash entirely and require restarting SDDM manually. This hasn't happened since 5.5 so may have been resolved, although it was always intermittent. 2. This still happens, after disconnecting a HDMI monitor plasma will become unstable. Programs will crash and odd display issues will appear on the laptop screen, e.g. fuzzy lines on places on the screen and wrongly drawn pixels 3. When a monitor is connected using mini-displayport the laptop screen turns off and the desktop is only displayed on the external monitor. This in itself is likely not a bug, however when pressing the keyboard key to cycle monitor states (e.g. clone, different desktop, etc) different effects occur: 3a. If the external monitor is displaying the desktop and the laptop screen is off, it works fine 3b. If the external monitor is set up as a clone of the laptop screen it works fine 3c. If the external monitor is a separate screen that increases the size of the desktop strange things start to happen: 3c. i) Sometimes the laptop screen will freeze entirely but if I move the mouse around so it appears on the external monitor, I can use the external monitor perfectly, open programs on it and use them (with the laptop screen showing the same frozen image) 3c. ii) Sometimes plasma will become unstable. Programs will crash and new programs cannot be opened. 3c. iii) Sometimes (and this is less frequently than the other two) it will work as expected 4. If I've been using the external monitor in one if its usable states (3a, 3b, 3c. iii) and unplug the monitor, I almost always have to restart SDDM soon afterwards due to crashes and strange behaviour. Hardware: Asus N550 monitor using Intel graphics driver I realise these may be somewhat unreleated, however there is a huge problem with KDE and external monitors. On both my laptop and desktop I have to restart SDDM daily due to issues with unplugging/plugging in/sleeping monitors. Let me know if you'd like me to post any logs (and how to turn them on/find them). Both desktop and laptop are running ArchLinux with up to date packages from their official repos. I do not have the testing repo enabled. Reproducible: Sometimes -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 358359] HIgh cpu consumption and apt-check process infinte fork
https://bugs.kde.org/show_bug.cgi?id=358359 Yözen Hernández changed: What|Removed |Added CC||yzhern...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 343369] Menu in QtQuickControls Combo Box on Breeze Dark Theme Unreadable
https://bugs.kde.org/show_bug.cgi?id=343369 richardlm changed: What|Removed |Added CC||richard.l...@gmail.com --- Comment #19 from richardlm --- Same here. However I was wondering if this actual theme related or by the (combo box) implementation in the GUI. For Example: System Settings -> Multimedia -> Audio Volume -> Configuration The combo boxes here doesn't follow color sheme, but they also appear rather random on the screen (see attachment 96556). Where as in System Settings -> Multimedia -> Audio and Video -> Audio Hardware Setup Combo box follows color sheme and is correctly placed. HTH -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358734] [Hard] Incorrect 2nd square HSV color picker (checked by HCG color model)
https://bugs.kde.org/show_bug.cgi?id=358734 --- Comment #1 from acterhd --- Some info: https://github.com/acterhd/hcg-color I wrote C++ version for QT. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358734] New: [Hard] Incorrect 2nd square HSV color picker (checked by HCG color model)
https://bugs.kde.org/show_bug.cgi?id=358734 Bug ID: 358734 Summary: [Hard] Incorrect 2nd square HSV color picker (checked by HCG color model) Product: krita Version: 2.9.10 Platform: Other OS: other Status: UNCONFIRMED Severity: normal Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: acte...@gmail.com Hello. I found bug with HSV2 square. Found by HCG color model patch for source code. I see that square is not right, slider moves to wrong directions. Reproducible: Always Steps to Reproduce: Very hard question. Need patch source code for support HCG (HST) color model. Need move sliders for check square. This patch are complex. Actual Results: Wrong color picker, from HCG view point. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 358733] New: KDE Connect Crash
https://bugs.kde.org/show_bug.cgi?id=358733 Bug ID: 358733 Summary: KDE Connect Crash Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: milesjpar...@gmail.com Application: kdeconnectd (0.1) KDE Platform Version: 4.14.14 Qt Version: 4.8.7 Operating System: Linux 3.18.11 x86_64 Distribution (Platform): Slackware Packages -- Information about the crash: - What I was doing when the application crashed: I was trying to connect my phone to KDE connect. When prompted to "accept" KDEConnect crashed The crash can be reproduced every time. -- Backtrace: Application: kdeconnect (kdeconnectd), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa19fb7e7c0 (LWP 1515))] Thread 2 (Thread 0x7fa18b937700 (LWP 1521)): #0 0x7fa19d4cfe85 in () at /usr/lib64/qt/lib/libQtCore.so.4 #1 0x7fa19d4ce80c in () at /usr/lib64/qt/lib/libQtCore.so.4 #2 0x7fa19d4ce8b5 in () at /usr/lib64/qt/lib/libQtCore.so.4 #3 0x7fa1992cff7d in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #4 0x7fa1992d0883 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7fa1992d0a5c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7fa19d4cf0fe in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/qt/lib/libQtCore.so.4 #7 0x7fa19d49f601 in QEventLoop::processEvents(QFlags) () at /usr/lib64/qt/lib/libQtCore.so.4 #8 0x7fa19d49f915 in QEventLoop::exec(QFlags) () at /usr/lib64/qt/lib/libQtCore.so.4 #9 0x7fa19d398c69 in QThread::exec() () at /usr/lib64/qt/lib/libQtCore.so.4 #10 0x7fa19d39b3ec in () at /usr/lib64/qt/lib/libQtCore.so.4 #11 0x7fa19d817704 in start_thread () at /lib64/libpthread.so.0 #12 0x7fa19c7a7f8d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fa19fb7e7c0 (LWP 1515)): [KCrash Handler] #6 0x7fa19b9a54c0 in QCA::Provider::Context::provider() const () at /usr/lib64/libqca.so.2 #7 0x7fa19b9bc59d in QCA::PublicKey::toPEM() const () at /usr/lib64/libqca.so.2 #8 0x7fa19f7aafa8 in Device::sendOwnPublicKey() () at /usr/lib64/libkdeconnectcore.so.1 #9 0x7fa19f7ae1b8 in Device::acceptPairing() () at /usr/lib64/libkdeconnectcore.so.1 #10 0x7fa19f794895 in () at /usr/lib64/libkdeconnectcore.so.1 #11 0x7fa19d4b3e60 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/qt/lib/libQtCore.so.4 #12 0x7fa19f379195 in KNotification::activate(unsigned int) () at /usr/lib64/libkdeui.so.5 #13 0x7fa19f37aa58 in () at /usr/lib64/libkdeui.so.5 #14 0x7fa19d4b3e60 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/qt/lib/libQtCore.so.4 #15 0x7fa19f49aaf4 in () at /usr/lib64/libkdeui.so.5 #16 0x7fa19f49b073 in () at /usr/lib64/libkdeui.so.5 #17 0x7fa19da56175 in () at /usr/lib64/qt/lib/libQtDBus.so.4 #18 0x7fa19d4b9951 in QObject::event(QEvent*) () at /usr/lib64/qt/lib/libQtCore.so.4 #19 0x7fa19e5ff54c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/qt/lib/libQtGui.so.4 #20 0x7fa19e60601c in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/qt/lib/libQtGui.so.4 #21 0x7fa19f34f88a in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5 #22 0x7fa19d4a0c3d in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/qt/lib/libQtCore.so.4 #23 0x7fa19d4a3e9e in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/qt/lib/libQtCore.so.4 #24 0x7fa19d4cef6e in () at /usr/lib64/qt/lib/libQtCore.so.4 #25 0x7fa1992d0787 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #26 0x7fa1992d09b8 in () at /usr/lib64/libglib-2.0.so.0 #27 0x7fa1992d0a5c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #28 0x7fa19d4cf0de in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/qt/lib/libQtCore.so.4 #29 0x7fa19e6a2aa6 in () at /usr/lib64/qt/lib/libQtGui.so.4 #30 0x7fa19d49f601 in QEventLoop::processEvents(QFlags) () at /usr/lib64/qt/lib/libQtCore.so.4 #31 0x7fa19d49f915 in QEventLoop::exec(QFlags) () at /usr/lib64/qt/lib/libQtCore.so.4 #32 0x7fa19d4a4ef9 in QCoreApplication::exec() () at /usr/lib64/qt/lib/libQtCore.so.4 #33 0x004012f4 in () #34 0x7fa19c6c06d0 in __libc_start_main () at /lib64/libc.so.6 #35 0x004013a9 in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kmailcvt] [Bug 358725] TheBat! mail-account does not show in list for import to kmail
https://bugs.kde.org/show_bug.cgi?id=358725 Laurent Montel changed: What|Removed |Added Version Fixed In||5.2 Latest Commit||http://commits.kde.org/kdep ||im/3a10f1c5896ee60467beaa1d ||29ffa05fb11de110 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Laurent Montel --- Git commit 3a10f1c5896ee60467beaa1d29ffa05fb11de110 by Montel Laurent. Committed on 29/01/2016 at 12:42. Pushed by mlaurent into branch 'master'. Fix Bug 358725 - TheBat! mail-account does not show in list for import to kmail Reactivate it even if we are not on windows we can have access to it. FIXED-IN: 5.2 M +0-2importwizard/autodetect/thebat/thebatimportdata.cpp http://commits.kde.org/kdepim/3a10f1c5896ee60467beaa1d29ffa05fb11de110 -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 358732] New: 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
Bug ID: 358732
Summary: qstring-uneeded-heap-allocations: fixit changes
QString to QLatin1String even if a QString function
(sprintf, arg...) on that object
Product: clazy
Version: unspecified
Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: oo.o+...@windbuechse.samba-tng.org
CC: smart...@kde.org
Created attachment 96901
--> https://bugs.kde.org/attachment.cgi?id=96901&action=edit
testcase for QString with sprintf
If a QString is created and a function of that object get's called ist must not
be converted to a QLatin1String.
That class has only a minimal set of functions and for example arg or sprintf
is not supported.
testcase_qstring.cpp:21:5: warning: QString(const char*) being called
[-Wclazy-qstring-uneeded-heap-allocations]
QString("").sprintf("0x%02X", 0x1E);
If the (automatic) fixit get applied there is than a no member error.
testcase_with_fixit.cpp:21:23: error: no member named 'sprintf' in
'QLatin1String'
QLatin1String("").sprintf("0x%02X", 0x1E);
--
You are receiving this mail because:
You are watching all bug changes.
[umbrello] [Bug 358731] Message 'too big indentation amount' on windows
https://bugs.kde.org/show_bug.cgi?id=358731 Ralf Habacker changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/umbr ||ello/01b2b16339521c051049b5 ||3662ecf890ac0cbe49 Status|UNCONFIRMED |RESOLVED Version Fixed In||2.18.2 (KDE Applications ||15.12.2) --- Comment #1 from Ralf Habacker --- Git commit 01b2b16339521c051049b53662ecf890ac0cbe49 by Ralf Habacker. Committed on 29/01/2016 at 12:42. Pushed by habacker into branch 'Applications/15.12'. Fix 'Message "too big indentation amount" on windows'. The type of the struct's ...CodeGenerationState are changed into classes, constructors are added and class members are initialized to useful defaults. The code generator line ending type is initialized accordingly to the platform umbrello is build for. FIXED-IN:2.18.2 (KDE Applications 15.12.2) M +2-7umbrello/codegenerators/codegenerationpolicy.cpp M +64 -5umbrello/optionstate.h http://commits.kde.org/umbrello/01b2b16339521c051049b53662ecf890ac0cbe49 -- You are receiving this mail because: You are watching all bug changes.
[kmailcvt] [Bug 358725] TheBat! mail-account does not show in list for import to kmail
https://bugs.kde.org/show_bug.cgi?id=358725 --- Comment #1 from Laurent Montel --- The bat ! indeed it's disable from linux I think that we can't access to it. But you're right we can I will reactivate it now. (but for kdepim 5.2) -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 352512] 5.0.xx after a crash, the restore session pops up twice then akregator crashes
https://bugs.kde.org/show_bug.cgi?id=352512 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.2 Status|CONFIRMED |RESOLVED --- Comment #23 from Laurent Montel --- I recreate a new widget to inform if we want to restore session (for akregator 5.2). It's better now. We can or not restore session as previously. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 358731] New: Message 'too big indentation amount' on windows
https://bugs.kde.org/show_bug.cgi?id=358731 Bug ID: 358731 Summary: Message 'too big indentation amount' on windows Product: umbrello Version: 2.17.3 (KDE Applications 15.08.3) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: ralf.habac...@freenet.de Running umbrello on Windows shows the following warning ' too big indentation amount x' Reproducible: Always Steps to Reproduce: 1. start dbgview from https://live.sysinternals.com/dbgview.exe 2. download umbrello from http://download.kde.org/stable/umbrello/2.17.3/ and install 3. start umbrello Actual Results: In dbgview the related message is printed. Expected Results: The bug causing this message should be fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358722] ASAN: Use after free
https://bugs.kde.org/show_bug.cgi?id=358722 Martin Gräßlin changed: What|Removed |Added URL||https://git.reviewboard.kde ||.org/r/126925/ Flags||ReviewRequest+ -- 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
--- Comment #3 from Takahiro Hashimoto ---
(In reply to Eike Hein from comment #2)
> This seems to be kio rather than Plasma?
I'm sorry if I don't point correct module category for this bug report.
Please let me explain the reason why I think my fixes suits for this bug.
First, certainly, the root cause of crash is the ASSERT, empty check of
UDS_NAME in kio/core/kcoredirlister.cpp. UDS_NAME should not be empty,
described in kio/core/udsentry.h:177 [1]
---
175 /// Filename - as displayed in directory listings etc.
176 /// "." has the usual special meaning of "current directory"
177 /// UDS_NAME must always be set and never be empty, neither contain
'/'.
178 ///
179 /// Note that KIO will append the UDS_NAME to the url of their
180 /// parent directory, so all kioslaves must use that naming scheme
181 /// ("url_of_parent/filename" will be the full url of that file).
182 /// To customize the appearance of files without changing the url
183 /// of the items, use UDS_DISPLAY_NAME.
184 UDS_NAME = 6 | UDS_STRING,
Second, the lack of UDS_NAME in the dirlist is caused by 'remote' kioslave
implementation.
In this case, the wrong .desktop name is specified in
kioslave/remote/remoteimpl.cpp in plasma-workspace. One of my patches[2] is to
fix it.
The last, 'Network' folder is created by createWizardEntry() in
kioslave/remote/kio_remote.cpp.
It's my guess, for some situation, for example, of knetattach isn't installed,
createWizardEntry() returns bool value. I'd like to add the check of this value
if correct dir entry is created or not with my patch.[3]
Of course much better solution makes me happy. Please let me have your
comment:)
[1]
https://quickgit.kde.org/?p=kio.git&a=blob&h=9b2153061cc3f9552eb18a6dc950a904fb4d4285&hb=7f3dbd33391ca62d9944e00490933f801f555ba2&f=src%2Fcore%2Fudsentry.h
[2] https://git.reviewboard.kde.org/r/126893/diff/1#0
[3] https://git.reviewboard.kde.org/r/126892/diff/1#index_header
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 358646] Rendering breaks if Triple Buffer detection gives NOT available
https://bugs.kde.org/show_bug.cgi?id=358646 --- Comment #14 from Martin Gräßlin --- And I'm sorry to say the patch doesn't help -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358646] Rendering breaks if Triple Buffer detection gives NOT available
https://bugs.kde.org/show_bug.cgi?id=358646 --- Comment #13 from Martin Gräßlin --- > Just to be sure: it's a phone video because that was the convenient thing to > do, not because it doesn't show up with recordmydesktop et al.? For convenience. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 342032] Context menu for Images inside HTML messages should offer saving them
https://bugs.kde.org/show_bug.cgi?id=342032 Jan Kundrát changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/troj ||ita/f7d1ecb05347c524d97e194 ||fd9fc56a78a496449 Status|UNCONFIRMED |RESOLVED --- Comment #1 from Jan Kundrát --- Git commit f7d1ecb05347c524d97e194fd9fc56a78a496449 by Jan Kundrát. Committed on 27/01/2016 at 14:19. Pushed by gerrit into branch 'master'. Add support for downloading of embedded images Change-Id: I0a2cd63bb3a628c7119ffdea4386863d51f3ed94 M +15 -2src/Gui/SimplePartWidget.cpp M +1-0src/Gui/SimplePartWidget.h M +29 -0src/Imap/Network/FileDownloadManager.cpp M +2-0src/Imap/Network/FileDownloadManager.h http://commits.kde.org/trojita/f7d1ecb05347c524d97e194fd9fc56a78a496449 -- 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 Eike Hein changed: What|Removed |Added Version|master |unspecified Component|Folder |remote Target Milestone|1.0 |--- Assignee|h...@kde.org|unassigned-b...@kde.org Product|plasmashell |kio --- Comment #2 from Eike Hein --- This seems to be kio rather than Plasma? -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 358655] Umbrello does not import private class
https://bugs.kde.org/show_bug.cgi?id=358655 --- Comment #11 from Ralf Habacker --- (In reply to Ken Standard from comment #4) > Not seeing it here. > > In fact the whole source import process is very rough and is not as intuitive > as one would expect. What could be simplier as 1. Start umbrello 2. setup required language with 'Code'->Active Language' (defaults to c++) 3. click on 'Code'->'Import project', select directory and wait until import is finished. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358722] ASAN: Use after free
https://bugs.kde.org/show_bug.cgi?id=358722
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0 |1
--- Comment #4 from Thomas Lübking ---
Workspace holds a pointer pointing Compositor::self() which is nuked by
Application::destroyCompositor() (so m_compositor in workspace now dangles)
This was previously prevented by noop'ing destroyCompositor() as long as there
was Workspace::self() and boke with
commit 1998d5ac1ad92011505f0e00761ccc618099fa19
Date: Tue Nov 10 08:52:40 2015 +0100
[wayland] Improve tear-down to not crash if X11 applications are still
around
We need to destroy the compositor after Xwayland terminated and after
the internal Wayland connection is destroyed. This means when destroying
the Workspace we may no longer destroy the Compositor at the same time.
Also we need to ensure that other tear down functionality doesn't call
into the no longer existing internal client connection.
With this change kwin doesn't crash when exiting with Wayland and/or
X11 windows still open.
...
void Application::destroyCompositor()
{
-if (Workspace::self()) {
-// compositor is destroyed together with Workspace
-return;
-}
delete Compositor::self();
}
...
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 358583] Gt Master 2016-01-26 - cannot make a proxy of a stabilised .mlt file.
https://bugs.kde.org/show_bug.cgi?id=358583 --- Comment #1 from Jean-Baptiste Mardelle --- Git commit 50b186e2268e61577680d40ebad0a1ead6cb8dcb by Jean-Baptiste Mardelle. Committed on 29/01/2016 at 11:02. Pushed by mardelle into branch 'master'. Fix proxy for playlist clips M +1-1src/mltcontroller/producerqueue.cpp http://commits.kde.org/kdenlive/50b186e2268e61577680d40ebad0a1ead6cb8dcb -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 358655] Umbrello does not import private class
https://bugs.kde.org/show_bug.cgi?id=358655 --- Comment #10 from Ralf Habacker --- (In reply to Ken Standard from comment #5) > I have discovered an interesting phenomenon that affects this situation. On umbrello start c++ is predefined as standard and opening the import wizard shows file extensions supported by the cxx support. > If the .pro file contains either comments (lines with #) or an > include(include.file) there is a log message that treats it as an error. .pro files are not intended to be imported by the c++ import. > Also, files are not displayed in the files list of the wizard - only folders > - unless the list of filter patterns is modified. You cleaned up the list of file patterns and entered *.pro as extension to search for ? As said .pro is not a supported file extension for c++ import. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358730] New: KDE Instant Messaging - Google account setup
https://bugs.kde.org/show_bug.cgi?id=358730 Bug ID: 358730 Summary: KDE Instant Messaging - Google account setup Product: plasmashell Version: 5.5.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: nev...@ergulec.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.3) Qt Version: 5.5.1 Operating System: Linux 4.3.0-040300-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: I am trying to set my gmail chat account , when i pushed the configure button - the application crushed -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4f4d905800 (LWP 10084))] Thread 10 (Thread 0x7f4f38d06700 (LWP 10087)): #0 0x7f4f480088dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f4f4c0d6bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f4f4c0d874f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f4f3ae4f7e9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f4f486fea6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4f477ea6aa in start_thread (arg=0x7f4f38d06700) at pthread_create.c:333 #6 0x7f4f48013eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7f4f32405700 (LWP 10089)): #0 0x7f4f44de2884 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f4f44d9dc19 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4f44d9e190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4f44d9e2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f4f4893650b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4f488dd50a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f4f486f9ac4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4f4afa7c35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f4f486fea6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f4f477ea6aa in start_thread (arg=0x7f4f32405700) at pthread_create.c:333 #10 0x7f4f48013eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f4f26fa5700 (LWP 10090)): #0 0x7f4f480088dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f4f44d9e1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4f44d9e2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4f4893650b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f4f488dd50a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4f486f9ac4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f4f4afa7c35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f4f486fea6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f4f477ea6aa in start_thread (arg=0x7f4f26fa5700) at pthread_create.c:333 #9 0x7f4f48013eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f4f25182700 (LWP 10091)): #0 0x7f4f44d9dc24 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f4f44d9e190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4f44d9e2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4f4893650b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f4f488dd50a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4f486f9ac4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f4f4afa7c35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f4f486fea6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f4f477ea6aa in start_thread (arg=0x7f4f25182700) at pthread_create.c:333 #9 0x7f4f48013eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f4f1f7bc700 (LWP 10094)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f4f4d350194 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f4f4d3501d9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f4f477ea6aa in start_thread (arg=0x7f4f1f7bc700) at pthread_create.
[kwin] [Bug 358646] Rendering breaks if Triple Buffer detection gives NOT available
https://bugs.kde.org/show_bug.cgi?id=358646
--- Comment #12 from Thomas Lübking ---
diff --git a/glxbackend.cpp b/glxbackend.cpp
index c59c647..9a8e0e1 100644
--- a/glxbackend.cpp
+++ b/glxbackend.cpp
@@ -751,7 +751,7 @@ void GlxBackend::endRenderingFrame(const QRegion
&renderedRegion, const QRegion
} else {
// Make sure that the GPU begins processing the command stream
// now and not the next time prepareRenderingFrame() is called.
-glFlush();
+glXWaitGL();
}
if (overlayWindow()->window()) // show the window only after the first
pass,
Just to be sure: it's a phone video because that was the convenient thing to
do, not because it doesn't show up with recordmydesktop et al.?
--
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 Dmitry Roshchin changed: What|Removed |Added CC||dmi...@roshchin.org -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 358655] Umbrello does not import private class
https://bugs.kde.org/show_bug.cgi?id=358655 --- Comment #9 from Ralf Habacker --- (In reply to Ken Standard from comment #8) > Comment 7: I find no dock window, list, or other window, named or titled > "Protocol". The import wizard has a "Logger" window and the main window has > a "Log" dock window. Sorry for confusion. "Protokoll" is the german translation of 'log'. I'm refering to the "log" window. The log window is filled with errors from import regardless started an import from the import wizard or using menu entry 'code'->'import project' -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 358728] Crash when opening the Fonts KCM (QRasterPaintEngine::renderHintsChanged)
https://bugs.kde.org/show_bug.cgi?id=358728 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at --- Comment #2 from Wolfgang Bauer --- FYI, the garbled font rendering should be fixed in 5.5.4. See Bug#336089. No idea if that would also fix your crash though. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358116] messageviewer leaks temporary files with mail parts in it
https://bugs.kde.org/show_bug.cgi?id=358116 --- Comment #7 from Sandro Knauß --- I've created a patch that should improve the situation: https://phabricator.kde.org/D883 Still we have no handling, if the application crashes, but we now delete the temp dirs directly, if the object is deleted. It would be great to test it in the wild. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356992] Intel Mesa drivers not supported EGL_SWAP_BEHAVIOR_PRESERVED_BIT
https://bugs.kde.org/show_bug.cgi?id=356992 Thomas Lübking changed: What|Removed |Added CC||devuran...@gmx.net --- Comment #36 from Thomas Lübking --- *** Bug 356882 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356882] No compositing with Mesa 11.1.0 (EGL 1.5) and Plasma/KWin 5.5.1 when using EGL OpenGL interface
https://bugs.kde.org/show_bug.cgi?id=356882 Thomas Lübking changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #17 from Thomas Lübking --- Yupp, it's apparently a dupe then (see comment #8) - since we didn't know for sure, I only CC'd this one and waited for confirmation ;-) *** This bug has been marked as a duplicate of bug 356992 *** -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 358729] New: Baloo crashes on log in
https://bugs.kde.org/show_bug.cgi?id=358729 Bug ID: 358729 Summary: Baloo crashes on log in Product: Baloo Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@vhanda.in Reporter: dverb...@xs4all.nl CC: pinak.ah...@gmail.com Application: baloo_file (5.15.0) Qt Version: 5.4.2 Operating System: Linux 4.2.0-27-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: I booted up and logged in, a few seconds later I got the Baloo crash report. This is repeatable. This install is a few days old but with a re used /home. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 [Current thread is 1 (Thread 0x7fa2eb45f800 (LWP 1393))] Thread 2 (Thread 0x7fa19f393700 (LWP 1497)): [KCrash Handler] #6 0x7fa2e94e2267 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #7 0x7fa2e94e3eca in __GI_abort () at abort.c:89 #8 0x7fa2e7cf71b2 in mdb_assert_fail (env=0x990950, expr_txt=expr_txt@entry=0x7fa2e7d031cf "rc == 0", func=func@entry=0x7fa2e7d03ac5 <__FUNCTION__.6980> "mdb_page_dirty", line=line@entry=1945, file=0x7fa2e7d031b0 "mdb.c") at mdb.c:1369 #9 0x7fa2e7cf75f5 in mdb_page_dirty (txn=0x994070, mp=) at mdb.c:1945 #10 0x7fa2e7cf87cb in mdb_page_alloc (num=num@entry=1, mp=mp@entry=0x7fa19f392158, mc=0x7fa19f392690) at mdb.c:2126 #11 0x7fa2e7cf8a29 in mdb_page_touch (mc=mc@entry=0x7fa19f392690) at mdb.c:2244 #12 0x7fa2e7cfa664 in mdb_cursor_touch (mc=mc@entry=0x7fa19f392690) at mdb.c:6086 #13 0x7fa2e7cfd27a in mdb_cursor_put (mc=0x7fa19f392690, key=0x7fa19f392a80, data=0x7fa19f392a90, flags=) at mdb.c:6221 #14 0x7fa2e7cffb29 in mdb_put (txn=, dbi=, key=key@entry=0x7fa19f392a80, data=data@entry=0x7fa19f392a90, flags=flags@entry=0) at mdb.c:8395 #15 0x7fa2ea64e51d in Baloo::DocumentDB::put (this=this@entry=0x7fa19f392b60, docId=docId@entry=15798985658730505, list=...) at ../../../src/engine/documentdb.cpp:77 #16 0x7fa2ea666f80 in Baloo::WriteTransaction::addDocument (this=0x7fa198003190, doc=...) at ../../../src/engine/writetransaction.cpp:61 #17 0x7fa2ea660b79 in Baloo::Transaction::addDocument (this=this@entry=0x7fa19f392c90, doc=...) at ../../../src/engine/transaction.cpp:235 #18 0x0041bcff in Baloo::NewFileIndexer::run (this=0x8bc720) at ../../../src/file/newfileindexer.cpp:72 #19 0x7fa2e9f9fe73 in QThreadPoolThread::run (this=0x9ef5e0) at thread/qthreadpool.cpp:93 #20 0x7fa2e9fa32be in QThreadPrivate::start (arg=0x9ef5e0) at thread/qthread_unix.cpp:337 #21 0x7fa2e8c156aa in start_thread (arg=0x7fa19f393700) at pthread_create.c:333 #22 0x7fa2e95b3eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fa2eb45f800 (LWP 1393)): #0 __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 #1 0x7fa2e8c17cfd in __GI___pthread_mutex_lock (mutex=0x7fa2eb5da040) at ../nptl/pthread_mutex_lock.c:80 #2 0x7fa2e7cf69c2 in mdb_txn_renew0 (txn=txn@entry=0x994070) at mdb.c:2566 #3 0x7fa2e7cf7c10 in mdb_txn_begin (env=0x990950, parent=parent@entry=0x0, flags=flags@entry=0, ret=ret@entry=0x7ffc623afb08) at mdb.c:2740 #4 0x7fa2ea6604bb in Baloo::Transaction::Transaction (this=0x7ffc623afb00, db=..., type=Baloo::Transaction::ReadWrite) at ../../../src/engine/transaction.cpp:54 #5 0x0042853f in Baloo::MetadataMover::removeFileMetadata (this=0x990ad0, file=...) at ../../../src/file/metadatamover.cpp:65 #6 0x7fa2ea1b3617 in QtPrivate::QSlotObjectBase::call (a=0x7ffc623afc50, r=0x990ad0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #7 QMetaObject::activate (sender=sender@entry=0x97e4e0, signalOffset=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffc623afc50) at kernel/qobject.cpp:3702 #8 0x7fa2ea1b3f87 in QMetaObject::activate (sender=sender@entry=0x97e4e0, m=m@entry=0x6448a0 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffc623afc50) at kernel/qobject.cpp:3582 #9 0x00431d65 in Baloo::PendingFileQueue::removeFileIndex (this=this@entry=0x97e4e0, _t1=...) at moc_pendingfilequeue.cpp:216 #10 0x00426776 in Baloo::PendingFileQueue::processCache (this=0x97e4e0) at ../../../src/file/pendingfilequeue.cpp:89 #11 0x7fa2ea1b3617 in QtPrivate::QSlotObjectBase::call (a=0x7ffc623afdd0, r=0x97e4e0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #12 QMetaObject::activate (sender=sender@entry=0x97e4f8, signalOf
[kmail2] [Bug 358116] messageviewer leaks temporary files with mail parts in it
https://bugs.kde.org/show_bug.cgi?id=358116
--- Comment #6 from Sandro Knauß ---
Well I can reproduce this behaviour with a simple testcase. This one fails:
QString path;
{
NodeHelper helper;
path = helper.createTempDir(QStringLiteral("foo"));
QVERIFY(QDir(path).exists());
}
QEventLoop loop;
QTimer::singleShot(0, &loop, &QEventLoop::quit);
loop.exec();
QVERIFY(!QDir(path).exists());
if I change the singleShot to something like 11000 (11secs) if passes.
The problem here is that if the NodeHelper instance is deleted the tempfiles
are deleted also only 10secs after the application and not directly with the
deletion of NodeHelper. I see no need to wait 10secs when the object is already
deleted.
NodeHelper::~NodeHelper()
{
//Don't delete it it will delete in class with a deleteLater;
if (mAttachmentFilesDir) {
mAttachmentFilesDir->removeTempFiles();
mAttachmentFilesDir = 0;
}
}
void AttachmentTemporaryFilesDirs::removeTempFiles()
{
QTimer::singleShot(d->mDelayRemoveAll, this,
&AttachmentTemporaryFilesDirs::slotRemoveTempFiles);
}
^^ d->mDelayRemoveAll is 10secs.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 358728] Crash when opening the Fonts KCM (QRasterPaintEngine::renderHintsChanged)
https://bugs.kde.org/show_bug.cgi?id=358728 --- Comment #1 from Willem --- Created attachment 96900 --> https://bugs.kde.org/attachment.cgi?id=96900&action=edit Garbled font rendering in the Font Management KCM -- You are receiving this mail because: You are watching all bug changes.
