[kdenlive] [Bug 365090] git master-2016-07-05: Compile error, mis-detects mlt version
https://bugs.kde.org/show_bug.cgi?id=365090 --- Comment #1 from Evert Vorster --- Created attachment 99852 --> https://bugs.kde.org/attachment.cgi?id=99852&action=edit Screenshot of the compile error Added in a screenshot of the compile error. I have only one version of mlt installed, and all files installed are tracked by Arch's package manager. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 355229] akonadiconsole browser does not show any resource entries
https://bugs.kde.org/show_bug.cgi?id=355229 David Faure changed: What|Removed |Added Latest Commit||http://commits.kde.org/akon ||adi/381acbc294dcecb0d4beb63 ||721080d231e4bca38 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from David Faure --- Git commit 381acbc294dcecb0d4beb63721080d231e4bca38 by David Faure. Committed on 05/07/2016 at 07:02. Pushed by dfaure into branch 'master'. Port StatisticsProxyModel to KExtraColumnsProxyModel. * this fixes sibling() - the unittest confirmed Dan's assessment that sibling() got broken for StatisticsProxyModel with Qt5. * this reduces the number of dataChanged signals emitted by the proxy: instead of dataChanged((row,0) (row,0)) + dataChanged((row,1) (row,3)) the proxy now emits dataChanged((row,0) (row,3)) directly * I also removed the code emitting dataChanged for parent indexes, the reasoning was "so that cumulative totals can be updated", but there are no cumulative totals anywhere in this proxy (other than the tooltip). * the awful model-index-struct-casting hack is no longer necessary, the code is much simpler, there are now unittests (both here and for the base class KExtraColumnsProxyModel in kitemmodels)... M +1-0autotests/libs/CMakeLists.txt A +241 -0autotests/libs/statisticsproxymodeltest.cpp [License: LGPL (v2+)] A +79 -0autotests/libs/test_model_helpers.h [License: LGPL (v2+)] M +72 -279 src/core/models/statisticsproxymodel.cpp M +9-18 src/core/models/statisticsproxymodel.h http://commits.kde.org/akonadi/381acbc294dcecb0d4beb63721080d231e4bca38 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal
https://bugs.kde.org/show_bug.cgi?id=361615 --- Comment #2 from Julian Seward --- Do you have a small test case which demonstrates that Valgrind's behaviour at present, differs from when the program is run "natively" ? I'd be happier about this if you have something directly that demonstrates that V's behaviour differs from that of the kernel, in this respect. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 305332] show Recently used files in main window on startup
https://bugs.kde.org/show_bug.cgi?id=305332 rockonthemoo...@gmail.com changed: What|Removed |Added Version|0.24.0 |0.25.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 358535] Remove all colors schemes except Breeze and Breeze dark
https://bugs.kde.org/show_bug.cgi?id=358535 rockonthemoo...@gmail.com changed: What|Removed |Added Version|5.6.4 |5.6.95 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 362935] [AsusWRT] Assertion 'sizeof(TTEntryC) <= 88' failed
https://bugs.kde.org/show_bug.cgi?id=362935 --- Comment #1 from Julian Seward --- valgrind: m_transtab.c:2459 (vgPlain_init_tt_tc): Assertion 'sizeof(TTEntryC) <= 88' failed was a temporary problem; I am sure it has now been fixed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kemoticons] [Bug 358534] Remove Glass emoticon theme
https://bugs.kde.org/show_bug.cgi?id=358534 rockonthemoo...@gmail.com changed: What|Removed |Added Version|5.22.0 |5.23.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 315400] File chooser UI has margins around complete window
https://bugs.kde.org/show_bug.cgi?id=315400 rockonthemoo...@gmail.com changed: What|Removed |Added Version|5.22.0 |5.23.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365091] New: hotkeys daemon start at login button does nothing
https://bugs.kde.org/show_bug.cgi?id=365091 Bug ID: 365091 Summary: hotkeys daemon start at login button does nothing Product: systemsettings Version: 5.6.5 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_khotkeys Assignee: k...@michael-jansen.biz Reporter: lists.jjo...@free.fr In systemsettings, whether I check or uncheck in personalized shortcuts->launch daemon at session start the apply button is not activated. I join a screenshot to better explain, the buggy button has a yellow circle. Reproducible: Always Steps to Reproduce: 1.systemsettings 2.shortcuts 3.personalized 4.activate daemon Actual Results: the button toggles checked unchecked, but I can't save Expected Results: apply button activated to save the change -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365091] hotkeys daemon start at login button does nothing
https://bugs.kde.org/show_bug.cgi?id=365091 --- Comment #1 from José JORGE --- Created attachment 99853 --> https://bugs.kde.org/attachment.cgi?id=99853&action=edit screenshot of the bug It is in french... -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 365092] New: Frequent disconnects on fast networks
https://bugs.kde.org/show_bug.cgi?id=365092 Bug ID: 365092 Summary: Frequent disconnects on fast networks Product: kopete Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kopete-bugs-n...@kde.org Reporter: ronnybren...@gmail.com Hi Kopete-Team, Maybe this is related to https://bugs.kde.org/show_bug.cgi?id=198789. This bug is still not fixed for me: https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/486518 I am still having very very frequent disconnects in Kubuntu 16.04, kopete Qt: 4.8.7, KDE Development Platform: 4.14.16, Kopete: 1.8.3 The problem appears only on fast LAN connections like at university, it seems. At the moment I am using this workaround: https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/486518/comments/10 Thanks for your help. Best regards, Ronny Reproducible: Always Steps to Reproduce: 1. Use kopete on a fast connection. Perhaps low latency to the jabber server. Actual Results: Disconnects and reconnects every few seconds. Kopete is unusable in this state. Expected Results: A proper jabber server connection. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 364435] Crash - Unrecognized instruction for Arm64 LDPSW
https://bugs.kde.org/show_bug.cgi?id=364435 Julian Seward changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Julian Seward --- This has been fixed in the trunk now. *** This bug has been marked as a duplicate of bug 360425 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 360425] arm64 unsupported instruction ldpsw
https://bugs.kde.org/show_bug.cgi?id=360425 Julian Seward changed: What|Removed |Added CC||jh...@codeaurora.org --- Comment #8 from Julian Seward --- *** Bug 364435 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365079] Digikam 5.0 beta 7 crashes while showing the splash image.
https://bugs.kde.org/show_bug.cgi?id=365079 --- Comment #4 from Hans-Peter --- As i wrote in previous messages, i did compile it on my Linux box, no difference to the pre-packed binaries. HP -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365013] Clicking 'save' offers something like /tmp/.mount_SPDYDZ/usr instead of $HOME
https://bugs.kde.org/show_bug.cgi?id=365013 --- Comment #3 from tim-...@baverstock.org.uk --- Perhaps the default location for saving files could be made a preference? $HOME is certainly better than a missing directory, but my $HOME is awfully cluttered - it'd be nice to be able to nominate $HOME/pictures/2016-Q2/ or something. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 359950] Wrong result comparing doubles on x87
https://bugs.kde.org/show_bug.cgi?id=359950 --- Comment #6 from Tom Hughes --- Note that I didn't mean spills/reloads that valgrind's internal implementation does, but rather any spills/reloads that the original compiler generated. My understanding was that those would use the normal memory location for the variable, which as a double would only be 64 bits and hence would lose precision. Are you saying that gcc instead allocates an 80 bit temporary location for the spill to avoid losing precision? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365087] No translation.
https://bugs.kde.org/show_bug.cgi?id=365087 Boudewijn Rempt changed: What|Removed |Added Severity|normal |wishlist Ever confirmed|0 |1 CC||b...@valdyas.org Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Boudewijn Rempt --- That's correct. I have no idea how to add translations to snap packages, in fact. But snap is not officially supported: the official way to get Krita 3.0 is as appimages, and those do contain the translations. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365079] Digikam 5.0 beta 7 crashes while showing the splash image.
https://bugs.kde.org/show_bug.cgi?id=365079 --- Comment #5 from caulier.gil...@gmail.com --- Ok If code is compiled, i recommend to re-install the system from scratch. You can also use a VM to test. I'm 99% sure that core system libraries are broken or something like that. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 359524] bt, btc, btr and bts instruction improperly translated by VEX on x86-64
https://bugs.kde.org/show_bug.cgi?id=359524 --- Comment #3 from lm...@cam.ac.uk --- Thx for your reply. The implementation surely works, but the workaround adds side effects that the original program would not have, eg when doing taint tracking -- which is what we were doing... -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 363735] After opening a project file the tab Project Overview shows nothing; window does not get repainted
https://bugs.kde.org/show_bug.cgi?id=363735 Freek de Kruijf changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Freek de Kruijf --- Problem seems to have been resolved. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365093] New: System does not log USB-Stics automatically
https://bugs.kde.org/show_bug.cgi?id=365093 Bug ID: 365093 Summary: System does not log USB-Stics automatically Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: hugo.lech...@freenet.de CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.26-21-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: after starting the system I hve to start the USB stics by klicking in Dolphin. Then the "Orte" use the path. I saved a file to a stic, I had not "opened" before, so the error happened. I don't know, what means "KDE ist aus Quelltexten kompiliert" ? 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 0x7fb393d417c0 (LWP 1563))] Thread 7 (Thread 0x7fb37d774700 (LWP 1568)): #0 0x7fb38d243bbd in poll () from /lib64/libc.so.6 #1 0x7fb392197422 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fb39219900f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fb37f8c53c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fb38d93e32f in QThreadPrivate::start (arg=0x1aca020) at thread/qthread_unix.cpp:331 #5 0x7fb38ca4d0a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7fb38d24bfed in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7fb376b40700 (LWP 1576)): #0 0x7fb38991e1c9 in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x7fb38992044b in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb389920d80 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb389920f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7fb38db70d8b in QEventDispatcherGlib::processEvents (this=0x7fb378c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fb38db17d53 in QEventLoop::exec (this=this@entry=0x7fb376b3fdf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fb38d93961a in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7fb390c4de18 in ?? () from /usr/lib64/libQt5Qml.so.5 #8 0x7fb38d93e32f in QThreadPrivate::start (arg=0x1b9dc70) at thread/qthread_unix.cpp:331 #9 0x7fb38ca4d0a4 in start_thread () from /lib64/libpthread.so.0 #10 0x7fb38d24bfed in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fb369709700 (LWP 1597)): #0 0x7fb38d243bbd in poll () from /lib64/libc.so.6 #1 0x7fb389920e64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb389920f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb38db70d8b in QEventDispatcherGlib::processEvents (this=0x7fb3640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fb38db17d53 in QEventLoop::exec (this=this@entry=0x7fb369708df0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fb38d93961a in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7fb390c4de18 in ?? () from /usr/lib64/libQt5Qml.so.5 #7 0x7fb38d93e32f in QThreadPrivate::start (arg=0x1eb8c00) at thread/qthread_unix.cpp:331 #8 0x7fb38ca4d0a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7fb38d24bfed in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fb363dc5700 (LWP 1601)): #0 0x7fb389962cf9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7fb3899204b9 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb389920d80 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb389920f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7fb38db70d8b in QEventDispatcherGlib::processEvents (this=0x7fb35c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fb38db17d53 in QEventLoop::exec (this=this@entry=0x7fb363dc4df0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fb38d93961a in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7fb390c4de18 in ?? () from /usr/lib64/libQt5Qml.so.5 #8 0x7fb38d93e32f in QThreadPrivate::start (arg=0x1fa0430) at thread/qthread_unix.cpp:331 #9 0x7fb38ca4d0a4 in start_thread () from /lib64/libpthread.so.0 #10 0x7fb38d24bfed in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fb3624f1700 (LWP 1602)): #0 0x7fb38ca5103f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fb39341c86b in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7fb39341c899 in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7fb38ca4d0a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7fb38d24bfed in clone () from /l
[kipiplugins] [Bug 365049] Export to Piwigo not working - Dialog box not responding
https://bugs.kde.org/show_bug.cgi?id=365049 Frédéric COIFFIER changed: What|Removed |Added Summary|Export to Piwigi not|Export to Piwigo not |working - Dialog box not|working - Dialog box not |responding |responding -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 359950] Wrong result comparing doubles on x87
https://bugs.kde.org/show_bug.cgi?id=359950
--- Comment #7 from Julian Seward ---
(In reply to Tom Hughes from comment #6)
> Note that I didn't mean spills/reloads that valgrind's internal
> implementation does, but rather any spills/reloads that the original
> compiler generated.
Yes -- that's also what I meant.
> Are you saying that gcc instead allocates an 80 bit temporary
> location for the spill to avoid losing precision?
Well I *thought* that was the case, but it seems I am wrong. Using
this spill-inducing loop
int main ( int argc, char** argv )
{
double a, b, c, d, e, f, g, h;
a=b=c=d=e=f=g=h=1.2345;
int i;
for (i = 0; i < 1234 * argc; i++) {
a += i * 1.2;
b += a * 1.3;
c += d / 1.4;
d += e - 1.5;
e += f + 1.6;
f += g - 1.7;
g += h * 1.8;
h += a - (b*c) + (d*e*f/g);
}
return (a-b-c-d-e-f-g-h > 987.345 ? 1 : 0);
}
I get the assembly (for the loop body) below, which uses 64-bit loads
and stores (fstpl -16(%ebp), fmull -16(%ebp), etc) with gcc6 -m32 -O2.
To get 80-bit accesses (fstpt, fldt) I need to change the declaration
to be "long double".
Ah well. Live and learn. Now I am wondering why I believed gcc did
always do 80-bit spills/reloads.
.L3:
movl%eax, -28(%ebp)
addl$1, %eax
fildl -28(%ebp)
cmpl%edx, %eax
fmull .LC1
faddp %st, %st(1)
fldl.LC2
fmul%st(1), %st
faddl -24(%ebp)
fld %st(0)
fstpl -24(%ebp)
fldl.LC3
fdivr %st(7), %st
faddl -16(%ebp)
fstpl -16(%ebp)
fld %st(3)
fsubs .LC4
faddp %st, %st(7)
fldl.LC5
fadd%st(5), %st
faddp %st, %st(4)
fldl.LC6
fsubr %st(6), %st
faddp %st, %st(5)
fldl.LC7
fmul%st(3), %st
faddp %st, %st(6)
fld %st(6)
fmul%st(4), %st
fmul%st(5), %st
fdiv%st(6), %st
fxch%st(1)
fmull -16(%ebp)
fsubr %st(2), %st
faddp %st, %st(1)
faddp %st, %st(2)
jne .L3
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 365094] New: *.crt files do not show icons
https://bugs.kde.org/show_bug.cgi?id=365094 Bug ID: 365094 Summary: *.crt files do not show icons Product: Breeze Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: guoyunhebr...@gmail.com CC: kain...@gmail.com http://i.imgur.com/yITs45F.png MIME type: application/pkix-cert Icon: application-pkix-cert Icon size: 64px Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 365095] New: Missing application-menu action icon in oxygen-icons5
https://bugs.kde.org/show_bug.cgi?id=365095 Bug ID: 365095 Summary: Missing application-menu action icon in oxygen-icons5 Product: Oxygen Version: unspecified Platform: ROSA RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: icons Assignee: n...@oxygen-icons.org Reporter: pul...@list.ru There's no application-menu action icon in oxygen-icons5. It's used in Dolphin main window interface so it's quite important. oxygen-icons5 5.23.0, dolphin 16.04.2. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364850] If any docker is in focus e.g. layer docker , canvas zoom function with mouse scrollwheel is gone. The contents of the dockers is scrolled instead of canvas zoom
https://bugs.kde.org/show_bug.cgi?id=364850 Raghavendra kamath changed: What|Removed |Added Summary|If a layer in layer docker |If any docker is in focus |is clicked and the docker |e.g. layer docker , canvas |has a scrollbar , canvas|zoom function with mouse |zoom with scrollwheel is|scrollwheel is gone. The |gone|contents of the dockers is ||scrolled instead of canvas ||zoom -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364850] If any docker is in focus e.g. layer docker , canvas zoom function with mouse scrollwheel is gone. The contents of the dockers is scrolled instead of canvas zoom
https://bugs.kde.org/show_bug.cgi?id=364850 Raghavendra kamath changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 365096] New: Kontact crash when selecting settings
https://bugs.kde.org/show_bug.cgi?id=365096 Bug ID: 365096 Summary: Kontact crash when selecting settings Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: i...@alvin.be Application: kontact (5.2.2) Qt Version: 5.6.0 Frameworks Version: 5.23.0 Operating System: Linux 4.6.3-300.fc24.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: When you select Configure Kontact from the Settings menu kontact will immediately crash. Probably related to 331173, but with more recent version of kdepim. Extra: I removed knotes and installed kjots (which is not visible in Kontact) -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fecbd2e8940 (LWP 3915))] Thread 30 (Thread 0x7fec2bbdb700 (LWP 4305)): #0 0x7fecd3eed1b4 in timerSourcePrepareHelper(GTimerSource*, int*) () from /lib64/libQt5Core.so.5 #1 0x7fecd3eed285 in timerSourcePrepare(_GSource*, int*) () from /lib64/libQt5Core.so.5 #2 0x7feccc2e5f7d in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #3 0x7feccc2e696b in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7feccc2e6b5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7fecd3eed65b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7fecd3e9ca6a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7fecd3cfca03 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7fecd3d0103a in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7feccd5125ca in start_thread () from /lib64/libpthread.so.0 #10 0x7fecd30f4ead in clone () from /lib64/libc.so.6 Thread 29 (Thread 0x7fec40fe3700 (LWP 4303)): #0 0x7fecd30e4f8d in read () from /lib64/libc.so.6 #1 0x7feccc3297a0 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7feccc2e6524 in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7feccc2e69e4 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7feccc2e6b5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7fecd3eed65b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7fecd3e9ca6a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7fecd3cfca03 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7fecd3d0103a in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7feccd5125ca in start_thread () from /lib64/libpthread.so.0 #10 0x7fecd30f4ead in clone () from /lib64/libc.so.6 Thread 28 (Thread 0x7fec417e4700 (LWP 4301)): #0 0x7fecd30e932d in poll () from /lib64/libc.so.6 #1 0x7feccc2e6a46 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7feccc2e6b5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fecd3eed65b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7fecd3e9ca6a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7fecd3cfca03 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7fecd3d0103a in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7feccd5125ca in start_thread () from /lib64/libpthread.so.0 #8 0x7fecd30f4ead in clone () from /lib64/libc.so.6 Thread 27 (Thread 0x7fec42e42700 (LWP 4299)): #0 0x7fecd30e932d in poll () from /lib64/libc.so.6 #1 0x7feccc2e6a46 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7feccc2e6b5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fecd3eed65b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7fecd3e9ca6a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7fecd3cfca03 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7fecd3d0103a in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7feccd5125ca in start_thread () from /lib64/libpthread.so.0 #8 0x7fecd30f4ead in clone () from /lib64/libc.so.6 Thread 26 (Thread 0x7fec43e44700 (LWP 4297)): #0 0x7feccc32ab64 in g_mutex_unlock () from /lib64/libglib-2.0.so.0 #1 0x7feccc2e62a9 in g_main_context_query () from /lib64/libglib-2.0.so.0 #2 0x7feccc2e69b8 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7feccc2e6b5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7fecd3eed65b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7fecd3e9ca6a in QEventLoop::exec(QFlags)
[Oxygen] [Bug 365095] Missing application-menu action icon in oxygen-icons5
https://bugs.kde.org/show_bug.cgi?id=365095 --- Comment #1 from Pulfer --- Created attachment 99854 --> https://bugs.kde.org/attachment.cgi?id=99854&action=edit Missing icon for Control button -- You are receiving this mail because: You are watching all bug changes.
[kdf] [Bug 361723] kdf in kf5 does not show all mounted compared to kdf in kde4
https://bugs.kde.org/show_bug.cgi?id=361723 --- Comment #15 from Burkhard Lueck --- Disk configuration + mount points please see attachments Device notifier applet + dolphin show correct numbers, e.g. Intenso USB stick (mounted on /) 58,4 GiB free 1 TB SSD (mounted on /) 920,46 GiB / 94,36 GiB free 1,4 TB HD (mounted on /media/bb/HGST-1,5TB-sda1/) 798,76 GiB free 1,4 TB HD (mounted on /media/bb/HGST-1,5TB-sdc1/) 1,3 TiB free kdf has for all devices the numbers of the SSD mounted on / : 905,6 GiB / 94,3 GiB free 1) why 905,6 in kdf and 920,46 in notifier/ dolphin? 2) for unmounted devices the disk size is correctly shown in kdf -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 344584] php tag inside inline javascript function is not highlighted correctly
https://bugs.kde.org/show_bug.cgi?id=344584 Nikola Kovacs changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #4 from Nikola Kovacs --- Works with Kate 15.12.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365097] New: Krunner has broken shadow / corners
https://bugs.kde.org/show_bug.cgi?id=365097 Bug ID: 365097 Summary: Krunner has broken shadow / corners Product: plasmashell Version: 5.6.95 Platform: Neon Packages URL: http://i.imgur.com/8qUPVhm.png OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kont...@soee.pl CC: bhus...@gmail.com, plasma-b...@kde.org As attached image shows, krunner widget has broken corner / shadows. Reproducible: Always Steps to Reproduce: 1. Run krunner 2. See broken corners / shadows Actual Results: Two bottom corners are broken and makes teh shadow looks broken. Expected Results: Whole shadow around krunner widget shoudl be visible without whitespaces. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365097] Krunner has broken shadow / corners
https://bugs.kde.org/show_bug.cgi?id=365097 Jonathan Riddell changed: What|Removed |Added CC||j...@jriddell.org --- Comment #1 from Jonathan Riddell --- The reporter is using KDE neon User Edition with Plasma 5.7 I also get this on KDE neon Developer Edition unstable branches (git master, 5.7.90) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365098] New: Crash when sorting on import window
https://bugs.kde.org/show_bug.cgi?id=365098 Bug ID: 365098 Summary: Crash when sorting on import window Product: digikam Version: 4.14.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: p...@alicious.com Application: digikam (4.14.0) KDE Platform Version: 4.14.15 Qt Version: 4.8.6 Operating System: Linux 4.2.0-36-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: Sorting the images in the import window, they were filtered to JPEG/JFIF and then when choosing to group by folder the application crashed. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f10a399fb80 (LWP 9879))] Thread 6 (Thread 0x7f1078a34700 (LWP 9880)): #0 0x7f109c35088d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f1082ee412c in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 #2 0x7f1098d8c6aa in start_thread (arg=0x7f1078a34700) at pthread_create.c:333 #3 0x7f109c35be9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f1071cb4700 (LWP 9881)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f109cec8286 in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x10adb40) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=this@entry=0x10ada80, mutex=mutex@entry=0x10ada78, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x00604864 in Digikam::ScanController::run (this=0x10b7dc0) at /build/digikam-48Y6Xx/digikam-4.14.0/core/app/database/scancontroller.cpp:725 #4 0x7f109cec7d1c in QThreadPrivate::start (arg=0x10b7dc0) at thread/qthread_unix.cpp:349 #5 0x7f1098d8c6aa in start_thread (arg=0x7f1071cb4700) at pthread_create.c:333 #6 0x7f109c35be9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f10714b3700 (LWP 9882)): #0 0x7f109453f2d0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f109d00820e in QEventDispatcherGlib::processEvents (this=0x7f10640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #2 0x7f109cfd60d1 in QEventLoop::processEvents (this=this@entry=0x7f10714b2a00, flags=...) at kernel/qeventloop.cpp:149 #3 0x7f109cfd6445 in QEventLoop::exec (this=this@entry=0x7f10714b2a00, flags=...) at kernel/qeventloop.cpp:204 #4 0x7f109cec54f9 in QThread::exec (this=this@entry=0x1173b80) at thread/qthread.cpp:538 #5 0x7f109cfb6133 in QInotifyFileSystemWatcherEngine::run (this=0x1173b80) at io/qfilesystemwatcher_inotify.cpp:265 #6 0x7f109cec7d1c in QThreadPrivate::start (arg=0x1173b80) at thread/qthread_unix.cpp:349 #7 0x7f1098d8c6aa in start_thread (arg=0x7f10714b3700) at pthread_create.c:333 #8 0x7f109c35be9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f1070cb2700 (LWP 9885)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f109cec8286 in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x13a42f0) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=this@entry=0x11c7d10, mutex=mutex@entry=0x11c7d08, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7f10a1530082 in Digikam::ParkingThread::run (this=0x11c7cf0) at /build/digikam-48Y6Xx/digikam-4.14.0/core/libs/threads/threadmanager.cpp:119 #4 0x7f109cec7d1c in QThreadPrivate::start (arg=0x11c7cf0) at thread/qthread_unix.cpp:349 #5 0x7f1098d8c6aa in start_thread (arg=0x7f1070cb2700) at pthread_create.c:333 #6 0x7f109c35be9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f101b7fe700 (LWP 9956)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f109cec8286 in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x13f21520) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=, mutex=0x154db7b8, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x00877ba4 in Digikam::CameraController::run (this=0x154b7c60) at /build/digikam-48Y6Xx/digikam-4.14.0/core/utilities/importui/backend/cameracontroller.cpp:401 #4 0x7f109cec7d1c in QThreadPrivate::start (arg=0x154b7c60) at thread/qthread_unix.cpp:349 #5 0x7f1098d8c6aa in start_thread (arg=0x7f101b7fe700) at pthread_create.c:333 #6 0x7f109c35be9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f10a399fb80 (LWP 9879
[plasmashell] [Bug 365097] Krunner has broken shadow / corners
https://bugs.kde.org/show_bug.cgi?id=365097 Jonathan Riddell changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 344584] php tag inside inline javascript function is not highlighted correctly
https://bugs.kde.org/show_bug.cgi?id=344584 Buovjaga changed: What|Removed |Added Resolution|FIXED |WORKSFORME --- Comment #5 from Buovjaga --- Great! Let's set to WFM as we have no idea what fixed it. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 348573] The Dutch translation for the documentation of lokalize is missing in kde-l10n-nl.x.y.x.tar.xz
https://bugs.kde.org/show_bug.cgi?id=348573 Freek de Kruijf changed: What|Removed |Added Summary|Tar file of lokalize only |The Dutch translation for |contains the English|the documentation of |documentation |lokalize is missing in ||kde-l10n-nl.x.y.x.tar.xz --- Comment #2 from Freek de Kruijf --- So this bug report should be handled by the people who do the packaging for kde-l10n-LANG. This bug is still present in version 16.03.90. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365099] New: Settings window - scrollbar for smaller window covers buttons
https://bugs.kde.org/show_bug.cgi?id=365099 Bug ID: 365099 Summary: Settings window - scrollbar for smaller window covers buttons Product: plasmashell Version: 5.6.95 Platform: Neon Packages URL: http://i.imgur.com/Fo6tBVM.png OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: kont...@soee.pl If we open Systray settings window and got to Elements section, than if scrollbar is rendered (for smaller sized window) it hovers the 'cancel' buttons for shortcuts (see attached screenshot). Reproducible: Always Steps to Reproduce: 1. Open Systray settings window 2. Go to Elements section 3. If scrollbar isnot visible, make teh window a bit smaller to have it 4. Observe how the scrollbar covers buttons Actual Results: 'Cancel' buttons are partially covered by scrollbar. Expected Results: Scrollbar should be rendered next to buttons not cover them. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 350779] krunner forgets enabled categories, when switching KDE regional settings to another language
https://bugs.kde.org/show_bug.cgi?id=350779 --- Comment #5 from Vytautas --- Doesn't have categories some kind of ID, general (unique) category name or something? Using human readable caption as key is absolutely wrong. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365099] Settings window - scrollbar for smaller window covers buttons
https://bugs.kde.org/show_bug.cgi?id=365099 Rik Mills changed: What|Removed |Added CC||rik.mill...@gmail.com --- Comment #1 from Rik Mills --- Same behaviour here in Plasma 5.6.5 - FW 5.23, from kubuntu backports. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 365100] New: Power button ignored
https://bugs.kde.org/show_bug.cgi?id=365100 Bug ID: 365100 Summary: Power button ignored Product: Powerdevil Version: 5.6.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: gordan.kre...@steatoda.com Pressing power button has no effect. No matter which action is configured in System settings -> Power management -> Energy Saving -> When power button pressed, nothing happens. Checkbox "Button events handling" is checked. Action for "When laptop lid closed" works ok. Power button hardware is working properly (tested with xev, sends keycode 124/XF86PowerOff). According to systemd, PowerDevil is configured to handle events: gkresic@mata:~$ systemd-inhibit --list Who: PowerDevil (UID 1000/gkresic, PID 1338/kded5) What: handle-power-key:handle-suspend-key:handle-hibernate-key:handle-lid-switch Why: KDE handles power events Mode: block Who: NetworkManager (UID 0/root, PID 869/NetworkManager) What: sleep Why: NetworkManager needs to turn off networks Mode: delay 2 inhibitors listed. gkresic@mata:~$ Reproducible: Always Steps to Reproduce: 1. Set any action when power button is pressed 2. Press power button Actual Results: Nothing happens. Expected Results: Configured action (suspend, lock screen, ...) should be triggered. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 365100] Power button ignored
https://bugs.kde.org/show_bug.cgi?id=365100 Gordan Krešić changed: What|Removed |Added CC||gordan.kre...@steatoda.com -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 365095] Missing application-menu action icon in oxygen-icons5
https://bugs.kde.org/show_bug.cgi?id=365095 --- Comment #2 from pinheiro --- Comment on attachment 99854 --> https://bugs.kde.org/attachment.cgi?id=99854 Missing icon for Control button so what does control do? I'm sill on 4.x series plus what how should i name it? i guess breeze has it so i would, just copy the name over , sso just need to know the name ;) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365097] Krunner has broken shadow / corners
https://bugs.kde.org/show_bug.cgi?id=365097 --- Comment #2 from Jonathan Riddell --- doesn't happen on a fresh install. may be due to upgrading from Plasma 5.6 -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 365049] Export to Piwigo not working - Dialog box not responding
https://bugs.kde.org/show_bug.cgi?id=365049 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #5 from Maik Qualmann --- The question is which version of kipiplugins you in Fedora exactly use? Piwigo is now ported to the QNetworkAccessManager. I have just tested it again with my server. It works as expected. Also incorrect entries are correctly displayed with a message box. Maik -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 360378] arm64: Unhandled instruction 0x5E280844 (sha1h s4, s2)
https://bugs.kde.org/show_bug.cgi?id=360378 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364482] Plasma Wayland : the minimizing animation of a window won't play unless mouse pointer leaves task manager area
https://bugs.kde.org/show_bug.cgi?id=364482 tro...@free.fr changed: What|Removed |Added Summary|Plasma Wayland : minimizing |Plasma Wayland : the |a window to the Task bar|minimizing animation of a |causes a one second lag |window won't play unless ||mouse pointer leaves task ||manager area -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #127 from Samuel --- While the comment was made that KDE Plasma Version 5.7 was going to resolve problems with an external display, I have found that it has made these problems worse! I am on Kubuntu 16.04 and when I encounter big problems, I delete the files in ~/.local/share/kscreen and then use System Settings to set the displays as I want them. In my opinion the worsening indicates that work is being done in this area and has yet to be completed. The release schedule for 5.7 can be found here: https://community.kde.org/Schedules/Plasma_5. By scrolling down the list you will see that every week a new version is released, ie 5.7.1, 5.7.2 and thereafter it is about every fortnight. So, I am patiently waiting for this problem to be fixed and I will jump for joy when it is finally fixed! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364482] Plasma Wayland : the minimizing animation of a window won't play unless mouse pointer leaves task manager area
https://bugs.kde.org/show_bug.cgi?id=364482 --- Comment #3 from tro...@free.fr --- I edited the title for better explanation. Forget the "one second thing", it is false. The animation plays only if my mouse pointer leaves the task manager area. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 365095] Missing application-menu action icon in oxygen-icons5
https://bugs.kde.org/show_bug.cgi?id=365095 --- Comment #3 from Pulfer --- I guess you just need to copy categories/applications-system.png to actions/application-menu.png KDE4 Dolphin used "applications-system" icon for this "Control" button. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 343690] Missing windows tabbing
https://bugs.kde.org/show_bug.cgi?id=343690 Paul Fee changed: What|Removed |Added CC||paul.f@gmail.com --- Comment #13 from Paul Fee --- Is there a target release for this feature? I had used it before in KDE4 and I'm now missing it with KDE5 on Fedora 23. No need to squeeze it in past any release freezes, just wondering what future release will have it so it'll then make its way down into distro packages. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 362935] [AsusWRT] Assertion 'sizeof(TTEntryC) <= 88' failed
https://bugs.kde.org/show_bug.cgi?id=362935 --- Comment #2 from Sergey --- Just tried the latest r15901 on a slightly different platform (ASUS RT-AC87U) and with different executable. Result is the same: admin@RT-AC87U-0C18:/tmp/home/root# valgrind ssh ==704== Memcheck, a memory error detector ==704== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==704== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info ==704== Command: ssh ==704== valgrind: m_transtab.c:2459 (vgPlain_init_tt_tc): Assertion 'sizeof(TTEntryC) <= 88' failed. Segmentation fault -- You are receiving this mail because: You are watching all bug changes.
[kronometer] [Bug 365101] New: Last column of lap view not stretched
https://bugs.kde.org/show_bug.cgi?id=365101 Bug ID: 365101 Summary: Last column of lap view not stretched Product: kronometer Version: unspecified Platform: Other URL: http://i.imgur.com/ciqfMsZ.png OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kdemail.net Reporter: elvis.angelac...@kdemail.net See attached screenshot. The bug cannot be reproduced on Kubuntu 16.04 with Qt 5.5, so this looks like either a regression or a behavior change in Qt 5.6/5.7. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 232843] KGzipFilter cannot inflate multi-member gzip archives
https://bugs.kde.org/show_bug.cgi?id=232843 Martin Sandsmark changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/karc ||hive/853496897f5216909337ed ||8711e1b8391ae1b6a3 --- Comment #17 from Martin Sandsmark --- Git commit 853496897f5216909337ed8711e1b8391ae1b6a3 by Martin T. H. Sandsmark. Committed on 04/07/2016 at 22:32. Pushed by sandsmark into branch 'master'. Handle multiple gzip streams If kgzipfilter notices that zlib didn't read all the data, it tries to re-init the stream and read the rest of the buffer. This is tested by the unit test from Sune. The case where there's more than two streams available in the current buffer is tested in a unit test added separately. If the split between the streams falls right between two buffers, we need KCompressionDevice to notice that there's data left and try to continue decompressing. This is easy to test by setting BUFFER_SIZE to the size of the first stream in the unit test data (28 bytes). REVIEW: 128369 M +0-1autotests/kfiltertest.cpp M +7-2src/kcompressiondevice.cpp M +38 -10 src/kgzipfilter.cpp http://commits.kde.org/karchive/853496897f5216909337ed8711e1b8391ae1b6a3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 363998] DigiKam sees Nikon D700 but cannot import files
https://bugs.kde.org/show_bug.cgi?id=363998 --- Comment #6 from Ray Di Mascio --- I'm using DigiKam 4.14.0 with KDE 4.14.13 if that's what you are asking. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365086] Krita Preferences Dialog -> Can't Set Mouse Scroll as Shortcut / Accelerator / Hotkey
https://bugs.kde.org/show_bug.cgi?id=365086 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #1 from Boudewijn Rempt --- Hi Loren, You can configure ctrl-mousewheel for zoom in the canvas input settings page, not the keyboard shortcuts page. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 343690] Missing windows tabbing
https://bugs.kde.org/show_bug.cgi?id=343690 --- Comment #14 from Martin Gräßlin --- > Is there a target release for this feature? Sorry no, there is no target release for this feature yet. With every release cycle I hope to find some time for it, but well... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365059] Crash when dropping a layer with Transform Mask to another open document, in Tabs mode.
https://bugs.kde.org/show_bug.cgi?id=365059 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||b...@valdyas.org Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365059] Crash when dropping a layer with Transform Mask to another open document, in Tabs mode.
https://bugs.kde.org/show_bug.cgi?id=365059 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/krit ||a/d91b1ee38718f4920ba78cf4b ||f73e71cc25e93ec --- Comment #3 from Boudewijn Rempt --- Git commit d91b1ee38718f4920ba78cf4bf73e71cc25e93ec by Boudewijn Rempt. Committed on 05/07/2016 at 11:56. Pushed by rempt into branch 'krita/3.0'. M +3-1libs/image/kis_mask.cc http://commits.kde.org/krita/d91b1ee38718f4920ba78cf4bf73e71cc25e93ec -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #190 from linuxfluesterer --- (In reply to loop.rw from comment #189) > Ok guys, please stop useless bashing of the devs. While I also am impatient > to see the features back, I realize it is not a trivial matter but actually > a quite complex architectural change. David said they are working on it so > please be patient. > > As a side note however it is becoming more difficult updating different > systems ... Hmm, ok, the fundament of Plasma 5 may be more difficult than the one of KDE... But only if the fundament is well, the building can should be started. I will not offend any dev here, but maybe Plasma could be compared with our German airport BER, an absolute desaster and in the end nobody is really content. I agree to Arran (com ment 188), who said: >Just on afterthought: this situation resembles the European Union. If a >majority >of the EU-PARLIAMENT (min. 376 MEPs) make by vote a decision, this result has >no >binding value to the 28 Commissars nor to the 28 head of States. They can >decide >whatever they want. Democracy at its best??? I am rather sure, Plasma devs could have prevented this trouble situation. As I said before, I am still using KDE version 4.14.10. Anyway, lost time for every Plasma users, who have a serious demand for lost features (and, much more important, broken functions!). -Linuxfluesterer -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365102] New: Can't change "Desktop" font
https://bugs.kde.org/show_bug.cgi?id=365102 Bug ID: 365102 Summary: Can't change "Desktop" font Product: systemsettings Version: 5.6.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: kcm_fonts Assignee: unassigned-b...@kde.org Reporter: kokok...@gmail.com CC: unassigned-b...@kde.org In Kde4, systemsettings font module provided a way to change the font used by the Desktop elements like the taskbar or the folderview widget. In Plasmashell this option is not implemented (yet?) I whish it will be added ina Desktop-wide manner, or at least a way to customize the fonts used by single desktop elemens. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365057] Krita crashes when duplicate a file layer.
https://bugs.kde.org/show_bug.cgi?id=365057 --- Comment #3 from Boudewijn Rempt --- There is something very fishy going on here... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365057] Krita crashes when duplicate a file layer.
https://bugs.kde.org/show_bug.cgi?id=365057 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #2 from Boudewijn Rempt --- Here's the backtrace: (gdb) bt #0 0x7fff940663e0 in ?? () #1 0x708afd89 in QMetaObject::cast(QObject*) const () from /home/boud/dev/deps/lib/libQt5Core.so.5 #2 0x75a4eb64 in qobject_cast (object=) at /home/boud/dev/deps/include/QtCore/qobject.h:518 #3 KoShapeFactoryBase::pruneDocumentResourceManager (this=0x5a42390, obj=) at /home/boud/dev/krita/libs/flake/KoShapeFactoryBase.cpp:255 #4 0x708d2a06 in QObject::event(QEvent*) () from /home/boud/dev/deps/lib/libQt5Core.so.5 #5 0x717077dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /home/boud/dev/deps/lib/libQt5Widgets.so.5 #6 0x7170bc12 in QApplication::notify(QObject*, QEvent*) () from /home/boud/dev/deps/lib/libQt5Widgets.so.5 #7 0x778ea6d7 in KisApplication::notify (this=, receiver=0x5a42390, event=0x7fff9402a5b0) at /home/boud/dev/krita/libs/ui/KisApplication.cpp:505 #8 0x708a7955 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /home/boud/dev/deps/lib/libQt5Core.so.5 #9 0x708a973a in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /home/boud/dev/deps/lib/libQt5Core.so.5 #10 0x708f8353 in ?? () from /home/boud/dev/deps/lib/libQt5Core.so.5 #11 0x7fffebd41c84 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #12 0x7fffebd41ed8 in ?? () from /usr/lib64/libglib-2.0.so.0 #13 0x7fffebd41f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #14 0x708f79dc in QEventDispatcherGlib::processEvents(QFlags) () from /home/boud/dev/deps/lib/libQt5Core.so.5 #15 0x708a5b2b in QEventLoop::exec(QFlags) () from /home/boud/dev/deps/lib/libQt5Core.so.5 #16 0x708ad886 in QCoreApplication::exec() () from /home/boud/dev/deps/lib/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365057] Krita crashes when duplicate a file layer.
https://bugs.kde.org/show_bug.cgi?id=365057 --- Comment #4 from Boudewijn Rempt --- Git commit 0f1fc73b2470c329279b76dc4ea6071e6553a1b4 by Boudewijn Rempt. Committed on 05/07/2016 at 12:49. Pushed by rempt into branch 'krita/3.0'. Register KisImageSP as a metatype This avoids the following error when using file layers: Cloning KisFileLayer "/home/boud/Dropbox/pictures/florence_2016/P1010109.JPG" QObject::connect: Cannot queue arguments of type 'KisImageSP' (Make sure 'KisImageSP' is registered using qRegisterMetaType().) Because it allows KisImageSP to be used as an argument in a queued signal/slot connection. M +7-0libs/image/kis_image.cc http://commits.kde.org/krita/0f1fc73b2470c329279b76dc4ea6071e6553a1b4 --- Comment #5 from Boudewijn Rempt --- Git commit 9e07c0ab3797500f99eb38cec5736634a2c66781 by Boudewijn Rempt. Committed on 05/07/2016 at 12:49. Pushed by rempt into branch 'krita/3.0'. Store the resource managers in QPointers That way we're save when checking whether they have been deleted. M +12 -10 libs/flake/KoShapeFactoryBase.cpp M +1-2libs/flake/KoShapeFactoryBase.h http://commits.kde.org/krita/9e07c0ab3797500f99eb38cec5736634a2c66781 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365057] Krita crashes when duplicate a file layer.
https://bugs.kde.org/show_bug.cgi?id=365057 --- Comment #4 from Boudewijn Rempt --- Git commit 0f1fc73b2470c329279b76dc4ea6071e6553a1b4 by Boudewijn Rempt. Committed on 05/07/2016 at 12:49. Pushed by rempt into branch 'krita/3.0'. Register KisImageSP as a metatype This avoids the following error when using file layers: Cloning KisFileLayer "/home/boud/Dropbox/pictures/florence_2016/P1010109.JPG" QObject::connect: Cannot queue arguments of type 'KisImageSP' (Make sure 'KisImageSP' is registered using qRegisterMetaType().) Because it allows KisImageSP to be used as an argument in a queued signal/slot connection. M +7-0libs/image/kis_image.cc http://commits.kde.org/krita/0f1fc73b2470c329279b76dc4ea6071e6553a1b4 --- Comment #5 from Boudewijn Rempt --- Git commit 9e07c0ab3797500f99eb38cec5736634a2c66781 by Boudewijn Rempt. Committed on 05/07/2016 at 12:49. Pushed by rempt into branch 'krita/3.0'. Store the resource managers in QPointers That way we're save when checking whether they have been deleted. M +12 -10 libs/flake/KoShapeFactoryBase.cpp M +1-2libs/flake/KoShapeFactoryBase.h http://commits.kde.org/krita/9e07c0ab3797500f99eb38cec5736634a2c66781 -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 200776] Switching from krdc via alt-tab sends "alt key" to the remote desktop
https://bugs.kde.org/show_bug.cgi?id=200776 Sektor van Skijlen changed: What|Removed |Added CC||ethou...@gmail.com --- Comment #13 from Sektor van Skijlen --- This is still a problem. I like krdc (over gvncviewer) exactly because it switches desktops and windows of the main system on Alt-Tab and Alt- other keys. There's still a problem with locked Alt key when I switch the krdc window to another window. The problem is, in particular, when I switch back and the whole desktop inside behaves as if the Alt key were pressed, even if it's actually not pressed (which changes the behavior of any key combination). So I propose a solution: please make krdc on the event of "lose focus" (which may be a result of Alt-Tab), send the Key Release (or whatever it's called) events for Alt - as I can see above, probably the same can be required for Control, Shift and Meta. To prevent unnecessary flooding, it can simply record Key Press and Key Release events to update the modifier key state, and on Lose Focus event send Release events only to the keys that were remembered as currently Pressed. If this can make things bad for anyone, you can make it an option - but really it shouldn't be harmful, as it's hard to imagine a situation when the window is NOT focused and any key is pressed. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 361127] VIM highlighting is different than original VIM
https://bugs.kde.org/show_bug.cgi?id=361127 --- Comment #8 from Matteo Croce --- Created attachment 99855 --> https://bugs.kde.org/attachment.cgi?id=99855&action=edit vim makefile highlighting -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 361127] VIM highlighting is different than original VIM
https://bugs.kde.org/show_bug.cgi?id=361127 --- Comment #9 from Matteo Croce --- Created attachment 99856 --> https://bugs.kde.org/attachment.cgi?id=99856&action=edit kate makefile highlighting -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365057] Krita crashes when duplicate a file layer.
https://bugs.kde.org/show_bug.cgi?id=365057 Boudewijn Rempt changed: What|Removed |Added Latest Commit||http://commits.kde.org/krit ||a/8acd0ee3d49e41dabcb386e00 ||191dc71c018f9a0 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #6 from Boudewijn Rempt --- Git commit e719375b09edf3984b3c03c79b627f7187bd2e4b by Boudewijn Rempt. Committed on 05/07/2016 at 12:57. Pushed by rempt into branch 'krita/3.0'. Rename member variable to m_paintDevice We should only be calling KisImage or QImage instances "image", otherwise the scope for confusion is too big. M +11 -10 libs/ui/kis_file_layer.cpp M +2-2libs/ui/kis_file_layer.h http://commits.kde.org/krita/e719375b09edf3984b3c03c79b627f7187bd2e4b --- Comment #7 from Boudewijn Rempt --- Git commit 8acd0ee3d49e41dabcb386e00191dc71c018f9a0 by Boudewijn Rempt. Committed on 05/07/2016 at 13:12. Pushed by rempt into branch 'krita/3.0'. Pass a clone of the paint device instead of the image back to the file layer, because resetting the import document deletes it, which checks whether the image is still in use, and if it is, asserts. M +13 -11 libs/ui/kis_file_layer.cpp M +1-1libs/ui/kis_file_layer.h M +4-1libs/ui/kis_safe_document_loader.cpp M +1-1libs/ui/kis_safe_document_loader.h http://commits.kde.org/krita/8acd0ee3d49e41dabcb386e00191dc71c018f9a0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365057] Krita crashes when duplicate a file layer.
https://bugs.kde.org/show_bug.cgi?id=365057 Boudewijn Rempt changed: What|Removed |Added Latest Commit||http://commits.kde.org/krit ||a/8acd0ee3d49e41dabcb386e00 ||191dc71c018f9a0 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #6 from Boudewijn Rempt --- Git commit e719375b09edf3984b3c03c79b627f7187bd2e4b by Boudewijn Rempt. Committed on 05/07/2016 at 12:57. Pushed by rempt into branch 'krita/3.0'. Rename member variable to m_paintDevice We should only be calling KisImage or QImage instances "image", otherwise the scope for confusion is too big. M +11 -10 libs/ui/kis_file_layer.cpp M +2-2libs/ui/kis_file_layer.h http://commits.kde.org/krita/e719375b09edf3984b3c03c79b627f7187bd2e4b --- Comment #7 from Boudewijn Rempt --- Git commit 8acd0ee3d49e41dabcb386e00191dc71c018f9a0 by Boudewijn Rempt. Committed on 05/07/2016 at 13:12. Pushed by rempt into branch 'krita/3.0'. Pass a clone of the paint device instead of the image back to the file layer, because resetting the import document deletes it, which checks whether the image is still in use, and if it is, asserts. M +13 -11 libs/ui/kis_file_layer.cpp M +1-1libs/ui/kis_file_layer.h M +4-1libs/ui/kis_safe_document_loader.cpp M +1-1libs/ui/kis_safe_document_loader.h http://commits.kde.org/krita/8acd0ee3d49e41dabcb386e00191dc71c018f9a0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365013] Clicking 'save' offers something like /tmp/.mount_SPDYDZ/usr instead of $HOME
https://bugs.kde.org/show_bug.cgi?id=365013 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #4 from Boudewijn Rempt --- Hum, actually the pictures directory should be the default. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365013] Clicking 'save' offers something like /tmp/.mount_SPDYDZ/usr instead of $HOME
https://bugs.kde.org/show_bug.cgi?id=365013 --- Comment #5 from Boudewijn Rempt --- And there's also code to remember the last used folder. I'll investigate a bit. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365093] System does not log USB-Stics automatically
https://bugs.kde.org/show_bug.cgi?id=365093 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 348414 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348157] The symbol on the notification which pops when you could not mount a device is wrong
https://bugs.kde.org/show_bug.cgi?id=348157 --- Comment #6 from VP --- I think that this bug can be closed since the notification system has changed its behaviour and icons and now it tells with the right icon that was possible/impossible to mount/unmount a device. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365013] Clicking 'save' offers something like /tmp/.mount_SPDYDZ/usr instead of $HOME
https://bugs.kde.org/show_bug.cgi?id=365013 --- Comment #6 from Boudewijn Rempt --- Argh, now I remember... Having the current working directory as the default directory for saving was added because people wanted to start krita from a terminal and have the the current directory as default save dir. So I guess we'd best fix the apprun command to not change the working directory. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365005] Canvas Rotate cursor icon conflicts with selection tool.
https://bugs.kde.org/show_bug.cgi?id=365005 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Boudewijn Rempt --- Hi, Thanks for your report. Have you by any chance rebound shortcuts for canvas rotate? Here, the rotate icon only shows up when pressing space-shift for rotate, not just shift. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364984] group not editable at new window view.
https://bugs.kde.org/show_bug.cgi?id=364984 --- Comment #3 from Boudewijn Rempt --- Then I think that there must be something going on as well, because with just the steps mentioned, I just cannot reproduce the issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364887] [WACOM] Pressure Sensitivity Not Working (only for Krita)
https://bugs.kde.org/show_bug.cgi?id=364887 Boudewijn Rempt changed: What|Removed |Added Summary|Pressure Sensitivity Not|[WACOM] Pressure |Working (only for Krita)|Sensitivity Not Working ||(only for Krita) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364850] If any docker is in focus e.g. layer docker , canvas zoom function with mouse scrollwheel is gone. The contents of the dockers is scrolled instead of canvas zoom
https://bugs.kde.org/show_bug.cgi?id=364850 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #6 from Boudewijn Rempt --- I suspect it's a Qt version problem or a window manager problem. Can you please check whether the appimage also shows this behaviour for you? -- You are receiving this mail because: You are watching all bug changes.
[kajongg] [Bug 365104] New: Kajongg crashes at startup
https://bugs.kde.org/show_bug.cgi?id=365104 Bug ID: 365104 Summary: Kajongg crashes at startup Product: kajongg Version: 4.13.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: wolfg...@rohdewald.de Reporter: kyri...@alumni.princeton.edu CC: kde-games-b...@kde.org Application: kajongg (4.13.0) KDE Platform Version: 4.14.21 Qt Version: 4.8.7 Operating System: Linux 4.6.3-300.fc24.x86_64 x86_64 Distribution: "Fedora release 24 (Twenty Four)" -- Information about the crash: - What I was doing when the application crashed: I started the kajongg from the application launcher, and the application crashed. The crash can be reproduced every time. -- Backtrace: Application: Kajongg (kajongg), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #4 0x in () #5 0x7f065a62a137 in sip_api_get_cpp_ptr () at /usr/lib64/python2.7/site-packages/sip.so #6 0x7f065a62adce in sip_api_convert_to_type () at /usr/lib64/python2.7/site-packages/sip.so #7 0x7f0657069a46 in pyqtSignal_descr_get () at /usr/lib64/python2.7/site-packages/PyQt4/QtCore.so #8 0x7f0662eb0ff3 in _PyObject_GenericGetAttrWithDict () at /lib64/libpython2.7.so.1.0 #9 0x7f0662ece180 in slot_tp_getattr_hook () at /lib64/libpython2.7.so.1.0 #10 0x7f0662f0839b in PyEval_EvalFrameEx () at /lib64/libpython2.7.so.1.0 #11 0x7f0662f1076c in PyEval_EvalCodeEx () at /lib64/libpython2.7.so.1.0 #12 0x7f0662e9983c in function_call () at /lib64/libpython2.7.so.1.0 #13 0x7f0662e74ed3 in PyObject_Call () at /lib64/libpython2.7.so.1.0 #14 0x7f0662e83d2c in instancemethod_call () at /lib64/libpython2.7.so.1.0 #15 0x7f0662e74ed3 in PyObject_Call () at /lib64/libpython2.7.so.1.0 #16 0x7f0662ecb8e7 in slot_tp_init () at /lib64/libpython2.7.so.1.0 #17 0x7f0662eca65e in type_call () at /lib64/libpython2.7.so.1.0 #18 0x7f0662e74ed3 in PyObject_Call () at /lib64/libpython2.7.so.1.0 #19 0x7f0662f0c5a6 in PyEval_EvalFrameEx () at /lib64/libpython2.7.so.1.0 #20 0x7f0662f1076c in PyEval_EvalCodeEx () at /lib64/libpython2.7.so.1.0 #21 0x7f0662f10859 in PyEval_EvalCode () at /lib64/libpython2.7.so.1.0 #22 0x7f0662f2a08f in run_mod () at /lib64/libpython2.7.so.1.0 #23 0x7f0662f2b2a2 in PyRun_FileExFlags () at /lib64/libpython2.7.so.1.0 #24 0x7f0662f2c4b5 in PyRun_SimpleFileExFlags () at /lib64/libpython2.7.so.1.0 #25 0x7f0662f3e4a0 in Py_Main () at /lib64/libpython2.7.so.1.0 #26 0x7f066215c731 in __libc_start_main () at /lib64/libc.so.6 #27 0x5629f4c577e9 in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 365103] New: "Icons Tint to Match Highlight" makes icons invisible when "draw a thin line to indicate focus" is activated
https://bugs.kde.org/show_bug.cgi?id=365103 Bug ID: 365103 Summary: "Icons Tint to Match Highlight" makes icons invisible when "draw a thin line to indicate focus" is activated Product: Breeze Version: 5.6.95 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: robby.engelm...@igfs-ev.de The new feature "Icons Tint to Match Highlight" introduced with plasma 5.7 makes icons invisible when "draw a thin line to indicate focus" is activated in Breeze Widget style. Reproducible: Always Steps to Reproduce: 1.active Breeze styles everywhere 2.go to systemsettings -> Widget Style --> Configure Breeze Widget Style 3.activate "Draw a thin line to indicate focus in menus and menu bars Actual Results: enjoy invisible icons in menus and menu bars Expected Results: icons should not be tinted in that case -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329976] SCAN : digiKam does not update database after picture renaming
https://bugs.kde.org/show_bug.cgi?id=329976 swatilodh...@gmail.com changed: What|Removed |Added CC||swatilodh...@gmail.com --- Comment #6 from swatilodh...@gmail.com --- Are you able to reproduce the issue with 5.0.0 version? In a new folder, I have a list of pictures: - picture 01.jpg - picture 02.jpg ... - picture 5.jpg 1) digiKam reads the images fine. 2) Outside digikam (digikam is closed), I delete 'picture 3.jpg' and rename the next pictures: 'picture 4.jpg' becomes 'picture 3.jpg' 'picture 5.jpg' becomes 'picture 4.jpg' 3) When I open digiKam again, these images are correctly identified, with their respective properties -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 348414] Crash in KNotification::flags() (NotifyByAudio::onAudioFinished)
https://bugs.kde.org/show_bug.cgi?id=348414 David Edmundson changed: What|Removed |Added CC||hugo.lech...@freenet.de --- Comment #45 from David Edmundson --- *** Bug 365093 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kajongg] [Bug 365104] Kajongg crashes at startup
https://bugs.kde.org/show_bug.cgi?id=365104 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu --- Comment #1 from Rex Dieter --- Fedora 24 ships with kajongg-16.04.2-1.fc24 in (stable) updates. I'd encourage you to update and try again. -- You are receiving this mail because: You are watching all bug changes.
[kajongg] [Bug 365104] Kajongg crashes at startup
https://bugs.kde.org/show_bug.cgi?id=365104 Rex Dieter changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #2 from Rex Dieter --- OK, I can reproduce this crash, with the newer version, investigating... -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 365103] "Icons Tint to Match Highlight" makes icons invisible when "draw a thin line to indicate focus" is activated
https://bugs.kde.org/show_bug.cgi?id=365103 Kai Uwe Broulik changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||k...@privat.broulik.de, ||notm...@gmail.com --- Comment #1 from Kai Uwe Broulik --- @Marco: need to check for that setting before painting the icon in its "selected" state -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365105] New: QSystemTrayIcon with context menu does not react after second show
https://bugs.kde.org/show_bug.cgi?id=365105
Bug ID: 365105
Summary: QSystemTrayIcon with context menu does not react after
second show
Product: plasmashell
Version: 5.6.5
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: System Tray
Assignee: plasma-b...@kde.org
Reporter: goto...@gmx.net
During development with Qt I noticed a bug in the Plasma's system tray when
using QSystemTrayIcon:
If the system tray has a context menu set and is shown after one hide
(show->hide->show) the tray doesn't react anymore:
* no context menu shown on right click
* left click doesn't emit signal
Reproducible: Always
Steps to Reproduce:
1.Try this code inside a QMainWindow:
QSystemTrayIcon *sysTray = new QSystemTrayIcon(this);
sysTray->setIcon(style()->standardIcon(QStyle::SP_DesktopIcon));
QMenu *trayMenu = new QMenu(this);
sysTray->setContextMenu(trayMenu);
connect(sysTray, &QSystemTrayIcon::activated,
[=](QSystemTrayIcon::ActivationReason){ qDebug() << "clicked";
});
sysTray->show();
sysTray->hide();
sysTray->show();
2. compile
3. run:)
Actual Results:
left click on tray does not do anything ("clicked" not printed)
Expected Results:
print "clicked" to std output
This does not happen in LXQt, so I assume it is related to KF5.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 365105] QSystemTrayIcon with context menu does not react after second show
https://bugs.kde.org/show_bug.cgi?id=365105 A. Bikadorov changed: What|Removed |Added CC||goto...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 365103] "Icons Tint to Match Highlight" makes icons invisible when "draw a thin line to indicate focus" is activated
https://bugs.kde.org/show_bug.cgi?id=365103 --- Comment #2 from Marco Martin --- I'll do that :) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 363741] akonadi server 16.04.2: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 Sven Eden changed: What|Removed |Added CC||sven.e...@gmx.de --- Comment #14 from Sven Eden --- I tried this and removed the search folder. After a restart of both akonadi and kontact (I had gdb hooked to the akonadiserver process) and trying to do a search, gdb caught a SIGSEGV with the following trace: Thread 60 "QThread" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fd009ffb700 (LWP 17593)] 0x7fcfe854b9a8 in vtable for Xapian::Internal::QueryTerm () from /usr/lib64/libxapian-1.3.so.8 (gdb) bt #0 0x7fcfe854b9a8 in vtable for Xapian::Internal::QueryTerm () from /usr/lib64/libxapian-1.3.so.8 #1 0x7fcfe82a301b in ExternalPostList::ExternalPostList (this=0x7fcff009f1e0, db=..., source_=, factor_=, matcher=0x7fd009ff9d10) at matcher/externalpostlist.cc:40 #2 0x7fcfe81b5d4b in Xapian::Internal::QueryPostingSource::postlist (this=, qopt=0x7fd009ff9630, factor=1) at api/queryinternal.cc:739 #3 0x7fcfe81b40b1 in Xapian::Query::Internal::postlist_sub_xor (this=, ctx=..., qopt=, factor=) at api/queryinternal.cc:634 #4 0x7fcfe81b5533 in Xapian::Internal::QueryBranch::do_or_like (this=this@entry=0x7fcff001bd60, ctx=..., qopt=qopt@entry=0x7fd009ff9630, factor=factor@entry=1, elite_set_size=elite_set_size@entry=0, first=first@entry=1) at api/queryinternal.cc:1186 #5 0x7fcfe81b5afa in Xapian::Internal::QueryAndMaybe::postlist (this=0x7fcff001bd60, qopt=0x7fd009ff9630, factor=1) at api/queryinternal.cc:1550 #6 0x7fcfe82a32da in LocalSubMatch::get_postlist (this=0x7fcff009a6c0, matcher=0x7fd009ff9d10, total_subqs_ptr=0x7fd009ff979c) at matcher/localsubmatch.cc:204 #7 0x7fcfe82a9741 in MultiMatch::get_mset (this=this@entry=0x7fd009ff9d10, first=first@entry=0, maxitems=95894, check_at_least=check_at_least@entry=95894, mset=..., stats=..., mdecider=0x0, sorter=0x0) at matcher/multimatch.cc:419 #8 0x7fcfe81a4641 in Xapian::Enquire::Internal::get_mset (this=0x7fcff009a830, first=, maxitems=, check_at_least=, check_at_least@entry=0, rset=rset@entry=0x0, mdecider=0x0) at api/omenquire.cc:548 #9 0x7fcfe81a4984 in Xapian::Enquire::get_mset (this=this@entry=0x7fd009ffa030, first=, maxitems=, check_at_least=check_at_least@entry=0, rset=rset@entry=0x0, mdecider=0x0) at api/omenquire.cc:906 #10 0x7fcfe05e967d in Akonadi::Search::XapianSearchStore::exec (this=0x7fcff003fe70, query=...) at /home/portage/kde-apps/akonadi-search-16.04.2/work/akonadi-search-16.04.2/xapian/xapiansearchstore.cpp:177 #11 0x7fd00919e2e5 in Akonadi::Search::Query::exec (this=this@entry=0x7fd009ffa2a0) at /home/portage/kde-apps/akonadi-search-16.04.2/work/akonadi-search-16.04.2/core/query.cpp:252 #12 0x7fd0095f5f6d in SearchPlugin::search (this=, akonadiQuery=..., collections=..., mimeTypes=...) at /home/portage/kde-apps/akonadi-search-16.04.2/work/akonadi-search-16.04.2/akonadiplugin/searchplugin.cpp:348 #13 0x0053ed1d in Akonadi::Server::SearchRequest::searchPlugins (this=this@entry=0x7fd009ffa880) at /home/portage/kde-apps/akonadi-16.04.2/work/akonadi-16.04.2/src/server/search/searchrequest.cpp:112 #14 0x0053ef7f in Akonadi::Server::SearchRequest::exec (this=this@entry=0x7fd009ffa880) at /home/portage/kde-apps/akonadi-16.04.2/work/akonadi-16.04.2/src/server/search/searchrequest.cpp:123 #15 0x00443944 in Akonadi::Server::SearchManager::updateSearchImpl (this=, collection=..., cond=0x7fceeaffc4e0) at /home/portage/kde-apps/akonadi-16.04.2/work/akonadi-16.04.2/src/server/search/searchmanager.cpp:350 #16 0x004fbea5 in Akonadi::Server::SearchManager::qt_static_metacall (_o=, _c=, _id=, _a=) at /home/portage/kde-apps/akonadi-16.04.2/work/akonadi-16.04.2_build/src/server/moc_searchmanager.cpp:108 #17 0x7fd0165f8711 in QObject::event (this=0x27ac890, e=) at kernel/qobject.cpp:1256 #18 0x7fd0165cfaaa in doNotify (receiver=, event=) at kernel/qcoreapplication.cpp:1090 #19 0x7fd0165cfbda in QCoreApplication::notifyInternal2 (receiver=0x27ac890, event=event@entry=0x7fceec0deef0) at kernel/qcoreapplication.cpp:1015 #20 0x7fd0165d1c2a in QCoreApplication::sendEvent (event=0x7fceec0deef0, receiver=) at kernel/qcoreapplication.h:225 #21 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x27ab840) at kernel/qcoreapplication.cpp:1650 #22 0x7fd0165d20e8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1508 #23 0x7fd01661ec13 in postEventSourceDispatch (s=0x7fcff00012d0) at kernel/qeventdispatcher_glib.cpp:270 #24 0x7fd013da07f7 in g_main_dispatch (context=0x7fcff990) at /home/po
[frameworks-baloo] [Bug 359119] baloo_file_extractor got mad and ate 3 gigabytes of my RAM
https://bugs.kde.org/show_bug.cgi?id=359119 --- Comment #3 from J'informatique --- Hi to give you more information, I am using: KDE Frameworks 5.23.0 Qt 5.6.0 (built against 5.6.0) Distributor ID: neon Description:KDE neon User Edition 5.6 Release:16.04 Codename: xenial -- You are receiving this mail because: You are watching all bug changes.
[kronometer] [Bug 365101] Last column of lap view not stretched
https://bugs.kde.org/show_bug.cgi?id=365101 Elvis Angelaccio changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||2.1.1 Latest Commit||http://commits.kde.org/kron ||ometer/d3e7b682183ce28239ca ||2dc419c455cfdc0f664a --- Comment #1 from Elvis Angelaccio --- Git commit d3e7b682183ce28239ca2dc419c455cfdc0f664a by Elvis Angelaccio. Committed on 05/07/2016 at 13:59. Pushed by elvisangelaccio into branch '2.1'. Fix lap-view's last column on Qt > 5.5 Something changed in Qt 5.7 (or possibly Qt 5.6), resulting in an ugly non-stretched last column in the lap view. This used to work fine with Qt <= 5.5. This patch fixes this issue and doesn't seem to introduce regressions (tested with Qt 5.7 and Qt 5.5) FIXED-IN: 2.1.1 M +0-1src/mainwindow.cpp http://commits.kde.org/kronometer/d3e7b682183ce28239ca2dc419c455cfdc0f664a -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364813] Selection tools create a big black blob on the canvas before crashing.
https://bugs.kde.org/show_bug.cgi?id=364813 --- Comment #9 from Joe --- Sorry for the delay, I was out of town. Here is my screenshot of Krita. I do have the animation portion, I just did not activate it on the Dockers. On Thu, Jun 30, 2016 at 8:09 AM, Boudewijn Rempt via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=364813 > > Boudewijn Rempt changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > Status|UNCONFIRMED |NEEDSINFO > > --- Comment #8 from Boudewijn Rempt --- > Can you please attach a screenshot of the about box so we can verify which > version of Krita you are running? > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364848] Krita adds more to memory usage, after opening and closing several files
https://bugs.kde.org/show_bug.cgi?id=364848 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #3 from Boudewijn Rempt --- Created attachment 99858 --> https://bugs.kde.org/attachment.cgi?id=99858&action=edit memcheck log -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364848] Krita adds more to memory usage, after opening and closing several files
https://bugs.kde.org/show_bug.cgi?id=364848 --- Comment #4 from Boudewijn Rempt --- Created attachment 99859 --> https://bugs.kde.org/attachment.cgi?id=99859&action=edit massif run Opened and closed a bunch of images in a row. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365106] New: GUI for Ctrl + Alt + Backspace setting doesn't work
https://bugs.kde.org/show_bug.cgi?id=365106 Bug ID: 365106 Summary: GUI for Ctrl + Alt + Backspace setting doesn't work Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: caip...@fastmail.fm CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org This setting can be checked in the settings for a new KDE Neon install, but it doesn't do anything. Reproducible: Always Steps to Reproduce: 1. Open the Keyboard Hardware and Layout settings 2. Check the option in the advanced tab to enable the Ctrl + Alt + Backspace shortcut Actual Results: It doesn't do anything because Ubuntu (the base for Neon) prevents that toggle from working, according to https://forum.kde.org/viewtopic.php?f=309&t=133697&p=359377#p359377 Expected Results: The shortcut should work as expected, since that setting is provided by a clean KDE Neon install. Since KDE Neon is provided as an ISO/installable OS by itself, it should either overwrite Canonical's limitation for that shortcut, or hide it from the GUI. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364850] If any docker is in focus e.g. layer docker , canvas zoom function with mouse scrollwheel is gone. The contents of the dockers is scrolled instead of canvas zoom
https://bugs.kde.org/show_bug.cgi?id=364850 --- Comment #7 from Raghavendra kamath --- Boud i think you are right. I made a mistake of not stating my qt version. My qt version is 5.7 I tested the appimage as well as 3.0 from repositories which don't have this issue, so yes I think you are right about qt version issue -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365105] QSystemTrayIcon with context menu does not react after second show
https://bugs.kde.org/show_bug.cgi?id=365105 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Could you just upload a small demo app as you've clearly written one. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365005] Canvas Rotate cursor icon conflicts with selection tool.
https://bugs.kde.org/show_bug.cgi?id=365005 --- Comment #2 from Zafio --- Hi! I wasn't sure, but I set the canvas input settings o Krita's default and I still see the cursor pressing just Shift. Forgot to mention this is Windows. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348157] The symbol on the notification which pops when you could not mount a device is wrong
https://bugs.kde.org/show_bug.cgi?id=348157 David Edmundson changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #7 from David Edmundson --- thanks VP -- You are receiving this mail because: You are watching all bug changes.
