[krita] [Bug 399347] KoPopup Button sometimes pops popup widget up on the wrong monitor
https://bugs.kde.org/show_bug.cgi?id=399347 --- Comment #7 from Gremriel --- If I move the Cintiq to the right of the main monitor, the options popup stays on the Cintiq. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377142] Move Tool Sluggish Performance in Wrap-around Mode
https://bugs.kde.org/show_bug.cgi?id=377142 Emmet O'Neill changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Emmet O'Neill --- This seems to no longer be an issue, as the performance hit seems minimal even on my pretty mediocre laptop. I think this can be closed and marked as fixed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397612] Filter Mask (Color Adjustment) crashes or loses settings when converting image color space.
https://bugs.kde.org/show_bug.cgi?id=397612 Emmet O'Neill changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396066] Wayland session is coring right after login [amdgpu/DisplayPort]
https://bugs.kde.org/show_bug.cgi?id=396066 Mustafa Muhammad changed: What|Removed |Added CC||mustafa10...@gmail.com --- Comment #19 from Mustafa Muhammad --- (In reply to Shmerl from comment #18) > It can be a downstream issue with Debian specifically (since according to > Mesa developers, it doesn't happen on Arch). So I also opened a Debian bug: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909636 I'm not a developer, but I suggest you try booting the latest Neon ISO to check if it works on your hardware, if it does, it is upstream or distribution issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399591] Qt 5.12 Beta ~ on Wayland, PlasmaShell panel popups are drawn at top-left of screen
https://bugs.kde.org/show_bug.cgi?id=399591 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk Resolution|--- |UPSTREAM --- Comment #3 from David Edmundson --- Fixed with latest 5.12 after the beta -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399593] Konsole had locked up, then Plasma crashed upon using xkill
https://bugs.kde.org/show_bug.cgi?id=399593 David Edmundson changed: What|Removed |Added Component|general |generic-crash Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395447] wallpaper selection menu shows old thumbnail when files are replaced
https://bugs.kde.org/show_bug.cgi?id=395447 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #2 from Kai Uwe Broulik --- >From what I can tell the wallpaper list uses its own KImageCache but never invalidates it. This is despite just using KIO::PreviewJob which has its own caching anyway. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399591] Qt 5.12 Beta ~ on Wayland, PlasmaShell panel popups are drawn at top-left of screen
https://bugs.kde.org/show_bug.cgi?id=399591 --- Comment #4 from Kyle Devir --- So it's already been caught! :) Thanks David. :) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 399473] [feature] proper exit after SIGHUP
https://bugs.kde.org/show_bug.cgi?id=399473 --- Comment #6 from RJVB --- To get this back to a hopefully more constructive state (and ignoring for the moment whether or not calling Qt API from a signal handler is an issue or not): what would be the best way to make the exit procedure as least block-prone and non-interactive as possible? Would it be enough to shunt the KSaveSelectDialog? And before I get in too deep: is there a reason behind the selection of signals currently connected to a graceful exit, IOW, are any of these sent in a context where it would NOT be OK to discard unsaved changes? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399592] Qt 5.12 Beta ~ on Wayland, trying to start Spectacle causes kwin_wayland to segfault
https://bugs.kde.org/show_bug.cgi?id=399592 Kyle Devir changed: What|Removed |Added Product|Spectacle |kwin Assignee|m...@baloneygeek.com |kwin-bugs-n...@kde.org Version|18.08.1 |5.14.0 Component|General |platform-drm -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399347] KoPopup Button sometimes pops popup widget up on the wrong monitor
https://bugs.kde.org/show_bug.cgi?id=399347 Emmet O'Neill changed: What|Removed |Added CC||emmetoneill@gmail.com Keywords||multiscreen -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 399050] Signature spoofing in PGP encrypted email (ID layer)
https://bugs.kde.org/show_bug.cgi?id=399050 --- Comment #8 from Jens Mueller --- Created attachment 115532 --> https://bugs.kde.org/attachment.cgi?id=115532&action=edit Screenshots of testcases -- You are receiving this mail because: You are watching all bug changes.
[knotes] [Bug 399551] Knotes Crash on start
https://bugs.kde.org/show_bug.cgi?id=399551 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- Could you make sure all your packages are up-to-date? Looks like you may have an issue with mixed versions of libraries. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399594] New: Collection being thrown away again and again
https://bugs.kde.org/show_bug.cgi?id=399594 Bug ID: 399594 Summary: Collection being thrown away again and again Product: digikam Version: 5.9.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Database-Files Assignee: digikam-bugs-n...@kde.org Reporter: djse...@home.nl Target Milestone: --- https://forum.kde.org/viewtopic.php?f=255&t=153810 When restarting the SMB (samba) service on the (linux) server, the network share holding the pictures is unavailable for a few seconds. Digikam (on Windows) immediately removes the tree from collection. I have looked through the options/preferences and did not find an option to prevent this behaviour. The share is added as 'Network Share.' BUT, even more, several times lately the collection disappeared while SMB (samba) was still running. I don't know why, but this behaviour of collections fully disappearing again and again is highly undesirable. Note the rescan time on 1Gbit/s for 2 items / 300 GB is 40-60 minutes. Requesting: Digikam not dropping the collection when unavailable. Instead display a status 'collection unavailable.' Especially when the root folder of a collection is unavailable Digikam should be smart enough to realize this is probably a reachability issue rather than the user moving or removing the full tree, otherwise the user would have also remove or readded the tree in Digikam settings. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394383] Icon applet added to desktop should respect single/double click setting
https://bugs.kde.org/show_bug.cgi?id=394383 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com --- Comment #1 from Alexander Mentyu --- Can reproduce also on Wayland Operating System: KDE neon Developer Edition KDE Plasma Version: 5.14.80 Qt Version: 5.11.1 KDE Frameworks Version: 5.51.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395659] Icon from theme switches to default after closing application
https://bugs.kde.org/show_bug.cgi?id=395659 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com --- Comment #1 from Alexander Mentyu --- Can you please add more info - Qt/Frameworks versions, custom settings used, etc. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 399050] Signature spoofing in PGP encrypted email (ID layer)
https://bugs.kde.org/show_bug.cgi?id=399050 --- Comment #9 from Jens Mueller --- Hi Jan, > You might see different results from what I see because > different servers parse garbage input in a different way. That's interesting, however I'd not rely on the config of the IMAP server for end-to-end security (which PGP is assumed to provide). > As a side note, I do not think that *that* would be a > security issue because e-mail headers are forgeable Absolutely, but a lot of users assume that PGP can exactly counter the problem of forgeable email headers using digital signatures (even though a binding between the From:/Sender: address and the email address in the matching PGP has never been defined in the OpenPGP standard). > Trojita always unconditionally shows both Sender and > From fields if they are present. Yes, but only the display name, not the actual email address. For me, the testcases look as shown in attachment 115532. > Do you see a security problem in here? Depends on your point of view. I would not say those issues are super-bad. However, if we really want to rely on PGP for critical tasks I'd say there is still room for improvement in the UI of mail clients. Assume you receive a signed email from you employer with testcase #2 which includes a task-to-be-done-immediately (e.g. "The President: >>launch missiles<<") -- you may be stressed and not look into the signature details and just do it... > What we could do is to always show the e-mail address > which was matched. Would that make sense from your > point of view? Yes, I think it's a good practice to explicitly show the email address of the matching key (if available) and therefore answer the signed-by-whom question (or at least deligate it back to the user). Greetings Jens -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399564] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=399564 --- Comment #7 from JordanL --- Should have mentioned, this bug was also present in 5.13.*. -- You are receiving this mail because: You are watching all bug changes.
[kst] [Bug 399595] New: first 1 M lines for 3 million line data file not shown in graph
https://bugs.kde.org/show_bug.cgi?id=399595 Bug ID: 399595 Summary: first 1 M lines for 3 million line data file not shown in graph Product: kst Version: unspecified Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: view objects Assignee: k...@kde.org Reporter: markku.poy...@wmail.fi Target Milestone: --- SUMMARY first 1 M lines for 3 million line data file not shown in graph STEPS TO REPRODUCE 1. make 3 million lines of data 2. create graph from that 3. maximize graph to show all data OBSERVED RESULT first about 1 M data points not drawn EXPECTED RESULT all points drawn SOFTWARE VERSIONS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394383] Icon applet added to desktop should respect single/double click setting
https://bugs.kde.org/show_bug.cgi?id=394383 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Kai Uwe Broulik --- This was decided against, see discussion in the linked bug report. *** This bug has been marked as a duplicate of bug 348960 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348960] Double click to open file/folders do not work with "icon" and "trash" plasmoids
https://bugs.kde.org/show_bug.cgi?id=348960 Kai Uwe Broulik changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #13 from Kai Uwe Broulik --- *** Bug 394383 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395659] Icon from theme switches to default after closing application
https://bugs.kde.org/show_bug.cgi?id=395659 Kai Uwe Broulik changed: What|Removed |Added Component|Icon Applet |Icons-only Task Manager Assignee|plasma-b...@kde.org |h...@kde.org CC||k...@privat.broulik.de, ||plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 391706] 1384f275ab2f1ad1841753ee163af6d1b0bb952b causes problems mounting internal partitions, eSATA-hdds, and LUKS-containers
https://bugs.kde.org/show_bug.cgi?id=391706 --- Comment #26 from José Alberto --- This is back for LUKS containers (or maybe it was never completely gone, I did never tested LUKS containers, I didn't even knew what they were last time I posted here). I have recorded a video, just in case it helps. It will be in this link for a month: https://my.owndrive.com/index.php/s/fshtH0Oi70eKQhG Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395659] Icon from theme switches to default after closing application
https://bugs.kde.org/show_bug.cgi?id=395659 Eike Hein changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Eike Hein --- It should always be the icon from the theme. How did you pin the launchers? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 391995] Inhibition handling is illogical
https://bugs.kde.org/show_bug.cgi?id=391995 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de Status|REPORTED|RESOLVED Version Fixed In||5.13.0 Resolution|--- |FIXED Latest Commit||https://cgit.kde.org/powerd ||evil.git/commit/?id=152400c ||1b6880506ee1395011686c2b191 ||f419a0 --- Comment #1 from Kai Uwe Broulik --- Was fixed in Plasma 5.13 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 399501] kio master fails to compile looking for KIO::SlaveInterface::open64()
https://bugs.kde.org/show_bug.cgi?id=399501 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #1 from Fabian Vogt --- Make sure that cmake contains the fix for https://gitlab.kitware.com/cmake/cmake/issues/16640. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399564] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=399564 --- Comment #8 from JordanL --- 5.13.* was the first release I tried Wayland in, so this bug might have been around long before that. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399594] Collection being thrown away again and again
https://bugs.kde.org/show_bug.cgi?id=399594 Maik Qualmann changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- You can test the digiKam-6.0.0-beta1: https://files.kde.org/digikam/ Create a backup of your database, digiKam-6.0.0 will slightly change the database if you want to go back to an older version. Maik *** This bug has been marked as a duplicate of bug 377849 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377849] albums disappear when the network is interrupted.
https://bugs.kde.org/show_bug.cgi?id=377849 Maik Qualmann changed: What|Removed |Added CC||djse...@home.nl --- Comment #34 from Maik Qualmann --- *** Bug 399594 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399594] Collection being thrown away again and again
https://bugs.kde.org/show_bug.cgi?id=399594 Maik Qualmann changed: What|Removed |Added Version Fixed In||6.0.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399596] New: Tag tree keeps reverting back to incorrect format after re-adding collection
https://bugs.kde.org/show_bug.cgi?id=399596
Bug ID: 399596
Summary: Tag tree keeps reverting back to incorrect format
after re-adding collection
Product: digikam
Version: 5.9.0
Platform: MS Windows
OS: MS Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: Tags-Engine
Assignee: digikam-bugs-n...@kde.org
Reporter: djse...@home.nl
Target Milestone: ---
With https://bugs.kde.org/show_bug.cgi?id=399594 happening much lately, it
caught my eye that the tag tree is being reverted to an already corrected
format.
Example to make it clear:
Tree:
Cars
--Brand 1
Model A
Model B
--Brand 2
Model A
--Brand 3
Model A
People
--Person 2
--Person 4
People
--Person 1
--Person 2
--Person 3
--Person 4
--Person 5
--Person 6
See above how all of a sudden the people subtree and some of the persons are
(duplicated) inside a car brand. I have no idea how that happened in the first
place. There were also pictures in the end points of that wrong tagtrees, but
not as much as in the correct tag tree. So I untagged those pictures and added
the right tags to them. After that I deleted the wrong tag tree ('People'
inside car 'brand 3.')
The collection gets rescanned, and voila, the tree as shown above is present
again, just without pictures in the wrong parts.
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 395903] Krita merges layers it shouldn't
https://bugs.kde.org/show_bug.cgi?id=395903 Eoin O'Neill changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://commits.kde.org/kri ||ta/a2f1b0cbe30055a7687c21f3 ||34310b463cbfbf4f --- Comment #3 from Eoin O'Neill --- Git commit a2f1b0cbe30055a7687c21f334310b463cbfbf4f by Eoin O'Neill. Committed on 10/10/2018 at 08:47. Pushed by eoinoneill into branch 'master'. Fixed Merge Multiple 'putAfter' Bug Causing Wrong Layers To Merge Fixed bug where invalid putAfter was causing incorrect nodes to merge when lowest most 'active' node was invisible. M +9-0libs/image/kis_layer_utils.cpp https://commits.kde.org/krita/a2f1b0cbe30055a7687c21f334310b463cbfbf4f -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399402] The shortcut "Alt + º", in spanish keyboard, stops working in KDE neon 18.04
https://bugs.kde.org/show_bug.cgi?id=399402 --- Comment #1 from BugCoder --- In KDE Plasma Version: 5.14.0 still it doesn't work -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 399597] New: Korganizer crashing when creating a todo
https://bugs.kde.org/show_bug.cgi?id=399597 Bug ID: 399597 Summary: Korganizer crashing when creating a todo Product: korganizer Version: 5.9.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: t...@tcit.fr Target Milestone: --- Application: korganizer (5.9.1) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.15.0-36-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: Creating a todo task (just title). Tasks are synched over CalDAV. The crash does not seem to be reproducible. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fed4c7ac880 (LWP 19106))] Thread 5 (Thread 0x7fed1700 (LWP 19111)): #0 0x7fed47f920b4 in __GI___libc_read (fd=12, buf=0x7fed1fffeb10, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fed3dba8a00 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fed3db63f27 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fed3db643e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fed3db6454c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fed48ae9a9b in QEventDispatcherGlib::processEvents (this=0x7fed14000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fed48a8ddea in QEventLoop::exec (this=this@entry=0x7fed1fffed20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #7 0x7fed488b8b8a in QThread::exec (this=) at thread/qthread.cpp:525 #8 0x7fed488c3aab in QThreadPrivate::start (arg=0x55dce06ec490) at thread/qthread_unix.cpp:367 #9 0x7fed3fc386db in start_thread (arg=0x7fed1700) at pthread_create.c:463 #10 0x7fed47fa388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fed2483e700 (LWP 19109)): #0 0x7fed47f96bf9 in __GI___poll (fds=0x55dce11d07f0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fed3db64439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fed3db6454c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fed48ae9a9b in QEventDispatcherGlib::processEvents (this=0x7fed18000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fed48a8ddea in QEventLoop::exec (this=this@entry=0x7fed2483dd20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7fed488b8b8a in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7fed488c3aab in QThreadPrivate::start (arg=0x55dce06c2f40) at thread/qthread_unix.cpp:367 #7 0x7fed3fc386db in start_thread (arg=0x7fed2483e700) at pthread_create.c:463 #8 0x7fed47fa388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fed25a4f700 (LWP 19108)): #0 0x7fed3db6393d in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fed3db6436b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fed3db6454c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fed48ae9a9b in QEventDispatcherGlib::processEvents (this=0x7fed2b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fed48a8ddea in QEventLoop::exec (this=this@entry=0x7fed25a4ecf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7fed488b8b8a in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7fed47440e45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fed488c3aab in QThreadPrivate::start (arg=0x7fed476b8d60) at thread/qthread_unix.cpp:367 #8 0x7fed3fc386db in start_thread (arg=0x7fed25a4f700) at pthread_create.c:463 #9 0x7fed47fa388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fed2c8bf700 (LWP 19107)): #0 0x7fed47f96bf9 in __GI___poll (fds=0x7fed2c8bec28, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fed3d6f6747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fed3d6f836a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fed2f679129 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fed488c3aab in QThreadPrivate::start (arg=0x55dce05d8350) at thread/qthread_unix.cpp:367 #5 0x7fed3fc386db in start_thread (arg=0x7fed2c8bf700) at pthread_create.c:463 #6 0x7fed47fa388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fed4c7ac880 (LWP 19106)): [KCrash Handler] #6 0x7fed48a6118c in QSortFilterProxyModel::parent (this=0x55dce096af90, child=...) at itemmodels/qsortfilterproxymodel.cpp:2002
[krita] [Bug 399575] layer remains visible after undo of creation
https://bugs.kde.org/show_bug.cgi?id=399575 Emmet O'Neill changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kri ||ta/20406f0cb05f81cfa5f752d9 ||c6b43f1ebc1a476f Resolution|--- |FIXED --- Comment #1 from Emmet O'Neill --- Git commit 20406f0cb05f81cfa5f752d9c6b43f1ebc1a476f by Emmet O'Neill. Committed on 10/10/2018 at 09:35. Pushed by emmetoneill into branch 'master'. Fix KisImageLayerAddCommand Redo/Undo Updating Bug. M +1-1libs/ui/kis_node_juggler_compressed.cpp https://commits.kde.org/krita/20406f0cb05f81cfa5f752d9c6b43f1ebc1a476f -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398826] On 16bits images, applying "w)_Texture_normal_map" make crash Krita
https://bugs.kde.org/show_bug.cgi?id=398826 Eoin O'Neill changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kri ||ta/f7e40ac3580422e81ca341c1 ||27aa0b4831f495f8 Status|ASSIGNED|RESOLVED --- Comment #2 from Eoin O'Neill --- Git commit f7e40ac3580422e81ca341c127aa0b4831f495f8 by Eoin O'Neill. Committed on 10/10/2018 at 09:37. Pushed by eoinoneill into branch 'master'. Kis Tangent Normal Paintop Now Works in 16-Bit and 32-Bit Image Modes. This updates the normal paint-top to work properly in non-8bit image modes. I believe that most normal maps are usually 8bit, but this will at least prevent a crash and produce the expected behavior regardless of image mode. M +1-1plugins/paintops/tangentnormal/kis_tangent_normal_paintop.cpp https://commits.kde.org/krita/f7e40ac3580422e81ca341c127aa0b4831f495f8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398877] [Recent Documents/Open Recent] bug with Templates
https://bugs.kde.org/show_bug.cgi?id=398877 Eoin O'Neill changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://commits.kde.org/kri ||ta/cf6a4209b832595fec51844d ||7bdaaab80b10fb94 --- Comment #2 from Eoin O'Neill --- Git commit cf6a4209b832595fec51844d7bdaaab80b10fb94 by Eoin O'Neill. Committed on 10/10/2018 at 09:38. Pushed by eoinoneill into branch 'master'. Template Files No Longer Added to 'Recent Documents' List on the Krita Greeting Page This is a fix intended to prevent any unintentional edits to Krita's template files. M +8-0libs/ui/KisMainWindow.cpp https://commits.kde.org/krita/cf6a4209b832595fec51844d7bdaaab80b10fb94 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399339] Ctrl+W shortcut is ambiguous. (+etc)
https://bugs.kde.org/show_bug.cgi?id=399339 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/c59cd318046bf4f4e298133a |ta/583b98af98e3b53f3a255bb2 |fe6895bdee8bf1cc|a625f43f678f0178 --- Comment #7 from Boudewijn Rempt --- Git commit 258e657733f5eec8b37a6138ccc72ad7a0834b55 by Boudewijn Rempt. Committed on 10/10/2018 at 07:36. Pushed by rempt into branch 'krita/4.1'. Remove the export_to_pdf action definition M +0-12 krita/kritamenu.action https://commits.kde.org/krita/258e657733f5eec8b37a6138ccc72ad7a0834b55 --- Comment #8 from Boudewijn Rempt --- Git commit 583b98af98e3b53f3a255bb2a625f43f678f0178 by Boudewijn Rempt. Committed on 10/10/2018 at 07:36. Pushed by rempt into branch 'krita/4.1'. Just remove all those hard-coded QMdiWindow system menu actions... Because on Windows setting the shortcut to nothing doesn't work. (cherry picked from commit c59cd318046bf4f4e298133afe6895bdee8bf1cc) M +1-0libs/ui/KisMainWindow.cpp https://commits.kde.org/krita/583b98af98e3b53f3a255bb2a625f43f678f0178 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395412] SVG text tool not selectable and text not editable when text has been moved inside an hidden group (made then visible)
https://bugs.kde.org/show_bug.cgi?id=395412 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/792b9f89944e8f5117a3859c |ta/90bdcc003ae61d8f60fdcd0c |1d922896b0b921ae|d80f2f57f0a3401f --- Comment #3 from Boudewijn Rempt --- Git commit 90bdcc003ae61d8f60fdcd0cd80f2f57f0a3401f by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 10/10/2018 at 07:36. Pushed by rempt into branch 'krita/4.1'. Fix lockness vector tools after a node being transitively locked by a group There is a weird synchronizations mechanism between flake layer system and Krita layer system. The patch just makes it a little bit more consistent. (cherry picked from commit 792b9f89944e8f5117a3859c1d922896b0b921ae) M +0-2libs/image/kis_base_node.cpp M +0-11 libs/image/kis_base_node.h M +1-0libs/image/kis_node.cpp M +6-0libs/image/kis_node.h M +0-1libs/image/kis_selection_mask.cpp M +2-2libs/ui/canvas/kis_canvas2.cpp M +21 -19 libs/ui/flake/kis_node_shape.cpp M +0-1libs/ui/flake/kis_node_shape.h https://commits.kde.org/krita/90bdcc003ae61d8f60fdcd0cd80f2f57f0a3401f -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399339] Ctrl+W shortcut is ambiguous. (+etc)
https://bugs.kde.org/show_bug.cgi?id=399339 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/c59cd318046bf4f4e298133a |ta/583b98af98e3b53f3a255bb2 |fe6895bdee8bf1cc|a625f43f678f0178 --- Comment #7 from Boudewijn Rempt --- Git commit 258e657733f5eec8b37a6138ccc72ad7a0834b55 by Boudewijn Rempt. Committed on 10/10/2018 at 07:36. Pushed by rempt into branch 'krita/4.1'. Remove the export_to_pdf action definition M +0-12 krita/kritamenu.action https://commits.kde.org/krita/258e657733f5eec8b37a6138ccc72ad7a0834b55 --- Comment #8 from Boudewijn Rempt --- Git commit 583b98af98e3b53f3a255bb2a625f43f678f0178 by Boudewijn Rempt. Committed on 10/10/2018 at 07:36. Pushed by rempt into branch 'krita/4.1'. Just remove all those hard-coded QMdiWindow system menu actions... Because on Windows setting the shortcut to nothing doesn't work. (cherry picked from commit c59cd318046bf4f4e298133afe6895bdee8bf1cc) M +1-0libs/ui/KisMainWindow.cpp https://commits.kde.org/krita/583b98af98e3b53f3a255bb2a625f43f678f0178 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399157] Preview on the text tool: scale in the preview
https://bugs.kde.org/show_bug.cgi?id=399157 --- Comment #3 from Boudewijn Rempt --- Git commit 596403bd3fe6bd695146a6e6aa6a2c4f16d3a0bf by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 10/10/2018 at 07:36. Pushed by rempt into branch 'krita/4.1'. Disable zoom-in/out actions when editing text in rich-text mode Qt doesn't support zooming of the text that has fixed font hight size using char-format. We should implement our own zooming for that. (cherry picked from commit 7bf022087a55b667835a6ad2fe2008765900bfd6) M +12 -2plugins/tools/svgtexttool/SvgTextEditor.cpp M +3-0plugins/tools/svgtexttool/SvgTextEditor.h https://commits.kde.org/krita/596403bd3fe6bd695146a6e6aa6a2c4f16d3a0bf -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399598] New: Can't pick colors from palettes anymore (nightly build)
https://bugs.kde.org/show_bug.cgi?id=399598 Bug ID: 399598 Summary: Can't pick colors from palettes anymore (nightly build) Product: krita Version: git master Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: freebo...@tiscali.it Target Milestone: --- Created attachment 115533 --> https://bugs.kde.org/attachment.cgi?id=115533&action=edit (Video example) (Krita 4.2.0-pre-alpha (git 715ad13) - Ubuntu 14.04 LTS, Unity) In the latest nightly build, it seems that picking colors from palettes is not working (see video): 1. start (fresh configs) 2. "CTRL + N" (new document) 3. toolbar > click the foreground color 4. pick a color sample from the palette Actual Results: the foreground color doesn't change Possibly related: Bug 399587 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359310] Remember scroll position when going back in FolderView popup
https://bugs.kde.org/show_bug.cgi?id=359310 Thomas Surrel changed: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-desktop/6736bdaa4bbd7c7 ||89e0049af4c57717725ac72b2 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Thomas Surrel --- Git commit 6736bdaa4bbd7c789e0049af4c57717725ac72b2 by Thomas Surrel. Committed on 10/10/2018 at 09:50. Pushed by thsurrel into branch 'master'. [Folder View] Remember selected item when navigating in subfolders Summary: When using the folder view in a panel as a popup, being in list view mode, getting into subfolders and back with arrow keys had a weird behaviour: the currentItem would just stay the same accross folders. This patch restores both the proper selected item and the scrolling position when navigating back. Test Plan: - Add a folder view in a panel, configure it in list view mode - Enter a subfolder and go back The folder you had gone into should be selected and the scrolling position should be the same than when you entered it. Reviewers: #plasma, broulik, hein Reviewed By: #plasma, hein Subscribers: anthonyfieroni, ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D15840 M +13 -2containments/desktop/package/contents/ui/FolderView.qml https://commits.kde.org/plasma-desktop/6736bdaa4bbd7c789e0049af4c57717725ac72b2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399598] Can't pick colors from palettes anymore (nightly build)
https://bugs.kde.org/show_bug.cgi?id=399598 Boudewijn Rempt changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||b...@valdyas.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399596] Tag tree keeps reverting back to incorrect format after re-adding collection
https://bugs.kde.org/show_bug.cgi?id=399596 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- I think the tag metadata will be stored in the images like this. You have to start with a clean new database, preferably with digiKam-6.0.0-beta1. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395853] Global menu doesnt empty itself after window is minimized
https://bugs.kde.org/show_bug.cgi?id=395853 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com --- Comment #1 from Alexander Mentyu --- Panel global menu applet? Possible solution would be display some right click desktop menu options -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399598] Can't pick colors from palettes anymore (nightly build)
https://bugs.kde.org/show_bug.cgi?id=399598 Anna Medonosova changed: What|Removed |Added CC||anna.medonos...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399145] Masks can be added to locked layer
https://bugs.kde.org/show_bug.cgi?id=399145 Eoin O'Neill changed: What|Removed |Added Latest Commit||https://commits.kde.org/kri ||ta/8e19e4649445e6633a29e558 ||6d923ede5cb0d4a4 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Eoin O'Neill --- Git commit 8e19e4649445e6633a29e5586d923ede5cb0d4a4 by Eoin O'Neill. Committed on 10/10/2018 at 09:53. Pushed by eoinoneill into branch 'master'. Masks Can No Longer Be Added to Locked Layers This corrects unexpected behavior of being able to add masks to a locked layer even though you could not edit the masks immediately after. Now, trying to add a mask to a locked layer will not work. M +20 -0libs/ui/kis_mask_manager.cc https://commits.kde.org/krita/8e19e4649445e6633a29e5586d923ede5cb0d4a4 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398915] a locked layer can be modified by a filter
https://bugs.kde.org/show_bug.cgi?id=398915 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/83a05fffb07d27b3e8452250 |ta/817cc8bb81fb1f269dc0b5ed |a36327923741108e|a42588578fd0b4e7 --- Comment #3 from Boudewijn Rempt --- Git commit 817cc8bb81fb1f269dc0b5eda42588578fd0b4e7 by Boudewijn Rempt, on behalf of Emmet O'Neill. Committed on 10/10/2018 at 07:40. Pushed by rempt into branch 'krita/4.1'. Prevent opening filter dialogs on non-editable layers. This functionally prevents filters from being used to modify locked layers. (cherry picked from commit 83a05fffb07d27b3e8452250a36327923741108e) M +7-0libs/ui/kis_filter_manager.cc https://commits.kde.org/krita/817cc8bb81fb1f269dc0b5eda42588578fd0b4e7 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399111] Shortcut for tools in tooltip doesn't show up for the fill tool when the shortcut scheme has is default.
https://bugs.kde.org/show_bug.cgi?id=399111 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/a28ce83a44f827f13ce2d9ea |ta/7c304d5d332d1e519699a4a9 |c41fd2f987253cc1|2afb1760c26dd3f3 --- Comment #2 from Boudewijn Rempt --- Git commit 7c304d5d332d1e519699a4a92afb1760c26dd3f3 by Boudewijn Rempt, on behalf of Emmet O'Neill. Committed on 10/10/2018 at 07:41. Pushed by rempt into branch 'krita/4.1'. Fix missing shortcut from Fill Tool tooltip. tool when the shortcut scheme has is default." (cherry picked from commit a28ce83a44f827f13ce2d9eac41fd2f987253cc1) M +1-1libs/widgets/KoToolBoxButton_p.h M +1-1plugins/tools/basictools/kis_tool_fill.h https://commits.kde.org/krita/7c304d5d332d1e519699a4a92afb1760c26dd3f3 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394399] Color Pickers: First time picking a color with blending enabled on fresh Krita instance causes hue to jump to red.
https://bugs.kde.org/show_bug.cgi?id=394399 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/189679b7108a99f6d15234c7 |ta/38e8b09351cf1bfab37495ba |e7738407c0b0f9ee|96c8c227605bf3dd --- Comment #4 from Boudewijn Rempt --- Git commit 38e8b09351cf1bfab37495ba96c8c227605bf3dd by Boudewijn Rempt, on behalf of Emmet O'Neill. Committed on 10/10/2018 at 07:44. Pushed by rempt into branch 'krita/4.1'. Avoid blending bug on first color pick. In a newly opened Krita instance, the starting foreground color is always in a 16-bit RGBA16 format, regardless of the color space of newly created/opened Krita document. As such, using the color picker's blending feature (which mixes a newly picked color with the user's previous color) immediately after the program starts results in an incorrect or undefined output color. This bug mitigates the problem and fixes the bug request by simply restricting to "pure" (without radius or blending) picking on the first use. (cherry picked from commit 189679b7108a99f6d15234c7e7738407c0b0f9ee) M +8-0libs/ui/tool/kis_tool_utils.cpp https://commits.kde.org/krita/38e8b09351cf1bfab37495ba96c8c227605bf3dd -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399435] crash when rightclicking the animation timeline.
https://bugs.kde.org/show_bug.cgi?id=399435 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/b3a62eb6d7863de12d2f9409 |ta/b8dae8a7476734b306c80b8e |1b48c5ec5de47c85|8680916af16a2000 --- Comment #3 from Boudewijn Rempt --- Git commit b8dae8a7476734b306c80b8e8680916af16a2000 by Boudewijn Rempt. Committed on 10/10/2018 at 07:39. Pushed by rempt into branch 'krita/4.1'. Since the places where this method is called check whether 0 is returned or not, it's wrong to assert here. (cherry picked from commit b3a62eb6d7863de12d2f94091b48c5ec5de47c85) M +1-1libs/image/kis_layer.cc M +4-2libs/image/kis_paint_device.cc M +1-1libs/image/kis_paint_device.h https://commits.kde.org/krita/b8dae8a7476734b306c80b8e8680916af16a2000 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399146] Merging layers with alpha-inheritance ignores some of the merged layers
https://bugs.kde.org/show_bug.cgi?id=399146 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/e64348e6935882fa6af2d608 |ta/deb13f3496e3ca0ee1c121bb |99860d4c1a45feb4|ba71f0e6090ce57d --- Comment #4 from Boudewijn Rempt --- Git commit deb13f3496e3ca0ee1c121bbba71f0e6090ce57d by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 10/10/2018 at 07:42. Pushed by rempt into branch 'krita/4.1'. Make merge multiple layers work consistently with weird nodes If the node is not composed with NORMAL composite mode or has inherit alpha enabled we should update the stack after the node is removed. (cherry picked from commit e64348e6935882fa6af2d60899860d4c1a45feb4) M +12 -1libs/image/kis_layer_utils.cpp https://commits.kde.org/krita/deb13f3496e3ca0ee1c121bbba71f0e6090ce57d -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399135] Polyline Tool Fill Option not working on Paint Layer
https://bugs.kde.org/show_bug.cgi?id=399135 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/512e4565add1d3b602fb5c32 |ta/685c0d72eb9a0a44ccb4b00c |8a30b723301ec473|df7e6807a4e695f6 --- Comment #2 from Boudewijn Rempt --- Git commit 685c0d72eb9a0a44ccb4b00cdf7e6807a4e695f6 by Boudewijn Rempt, on behalf of Sven Langkamp. Committed on 10/10/2018 at 07:37. Pushed by rempt into branch 'krita/4.1'. Fill polyline if some fill style was selected (cherry picked from commit 512e4565add1d3b602fb5c328a30b723301ec473) M +4-0libs/image/kis_painter.cc https://commits.kde.org/krita/685c0d72eb9a0a44ccb4b00cdf7e6807a4e695f6 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399203] Krita doesn't exit / quit / closes
https://bugs.kde.org/show_bug.cgi?id=399203 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/715ad1317627a2bdd41241ed |ta/269bc11497141dd9e545eeaf |772fda705a5beffd|47a6a890f529e1df --- Comment #6 from Boudewijn Rempt --- Git commit 269bc11497141dd9e545eeaf47a6a890f529e1df by Boudewijn Rempt, on behalf of Jouni Pentikäinen. Committed on 10/10/2018 at 07:44. Pushed by rempt into branch 'krita/4.1'. Fix unsuccessful restoring of a session blocking Krita from closing (cherry picked from commit 715ad1317627a2bdd41241ed772fda705a5beffd) M +1-1libs/ui/KisPart.cpp M +5-4libs/ui/KisSessionResource.cpp https://commits.kde.org/krita/269bc11497141dd9e545eeaf47a6a890f529e1df -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399340] "Brush Presets" docker and "Choose brush preset" dialog not synced
https://bugs.kde.org/show_bug.cgi?id=399340 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/cacb932322dbec056af869ed |ta/6073432833ff65456bcaf861 |424d212ba76761db|8de3a7abcd1a8a83 --- Comment #2 from Boudewijn Rempt --- Git commit 6073432833ff65456bcaf8618de3a7abcd1a8a83 by Boudewijn Rempt. Committed on 10/10/2018 at 07:43. Pushed by rempt into branch 'krita/4.1'. Reset the brush preset docker's current preset on creating a new document (cherry picked from commit cacb932322dbec056af869ed424d212ba76761db) M +3-2plugins/dockers/presetdocker/presetdocker_dock.cpp M +1-3plugins/dockers/presetdocker/presetdocker_dock.h https://commits.kde.org/krita/6073432833ff65456bcaf8618de3a7abcd1a8a83 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399166] SVG image will not be imported as vector layer in Krita 4.1.3
https://bugs.kde.org/show_bug.cgi?id=399166 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/4511c00ff053a235fc8d04f1 |ta/b98ae216d3dc5a0664f41a83 |12f334b2c722600e|4c07735da3917c8c --- Comment #3 from Boudewijn Rempt --- Git commit b98ae216d3dc5a0664f41a834c07735da3917c8c by Boudewijn Rempt. Committed on 10/10/2018 at 07:41. Pushed by rempt into branch 'krita/4.1'. Import SVG as vector layers (cherry picked from commit 4511c00ff053a235fc8d04f112f334b2c722600e) M +9-3libs/ui/kis_image_manager.cc M +17 -4libs/ui/kis_import_catcher.cc M +30 -24 libs/ui/kis_layer_manager.cc M +8-8libs/ui/kis_layer_manager.h M +12 -12 libs/ui/kis_mask_manager.cc M +5-5libs/ui/kis_mask_manager.h M +20 -19 libs/ui/kis_node_manager.cpp M +1-1libs/ui/kis_node_manager.h https://commits.kde.org/krita/b98ae216d3dc5a0664f41a834c07735da3917c8c -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376950] Krita doesn't read alpha channel from tiff files
https://bugs.kde.org/show_bug.cgi?id=376950 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/dbc50b47f101282690b0db24 |ta/15c4692c7599cf150a72296a |97773ef32b639de5|af07363c963e12ff --- Comment #13 from Boudewijn Rempt --- Git commit 15c4692c7599cf150a72296aaf07363c963e12ff by Boudewijn Rempt. Committed on 10/10/2018 at 07:42. Pushed by rempt into branch 'krita/4.1'. Fix loading the alpha channel from Photoshop TIFF files Photoshop apparently thinks that EXTRASAMPLE_UNSPECIFIED specifies correctly that the extra sample is an alpha channel. This is not true, but everyone thinks they can mess with the tiff standard, so just read it like that. (cherry picked from commit dbc50b47f101282690b0db2497773ef32b639de5) M +6-1plugins/impex/tiff/kis_tiff_converter.cc https://commits.kde.org/krita/15c4692c7599cf150a72296aaf07363c963e12ff -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379199] "Recently used color" is not influenced by fill function
https://bugs.kde.org/show_bug.cgi?id=379199 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/80647e8b318aeab5c39be56d |ta/a00fa257e48b10139dea5601 |53136d9a1b47bb88|cb989a6802caf0da --- Comment #3 from Boudewijn Rempt --- Git commit a00fa257e48b10139dea5601cb989a6802caf0da by Boudewijn Rempt, on behalf of Sven Langkamp. Committed on 10/10/2018 at 07:40. Pushed by rempt into branch 'krita/4.1'. Update color history after fill (cherry picked from commit 80647e8b318aeab5c39be56d53136d9a1b47bb88) M +2-0libs/ui/actions/kis_selection_action_factories.cpp https://commits.kde.org/krita/a00fa257e48b10139dea5601cb989a6802caf0da -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399169] color picker doesn't sample alpha correctly
https://bugs.kde.org/show_bug.cgi?id=399169 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/4976def25dc7e744acc34371 |ta/a570dae50e39836e2e9e5dd8 |473a61aa55070ae4|e22cee2ba629bafe --- Comment #8 from Boudewijn Rempt --- Git commit a570dae50e39836e2e9e5dd8e22cee2ba629bafe by Boudewijn Rempt, on behalf of Emmet O'Neill. Committed on 10/10/2018 at 07:40. Pushed by rempt into branch 'krita/4.1'. Color picker now correctly picks alpha values. (cherry picked from commit 4976def25dc7e744acc34371473a61aa55070ae4) M +0-1libs/ui/tool/kis_tool_utils.cpp M +1-1libs/ui/tool/kis_tool_utils.h M +3-4libs/ui/tool/strokes/kis_color_picker_stroke_strategy.cpp M +2-2plugins/tools/basictools/kis_tool_colorpicker.cc https://commits.kde.org/krita/a570dae50e39836e2e9e5dd8e22cee2ba629bafe -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372605] alt-draging frames outside loaded time line length crashes Krita
https://bugs.kde.org/show_bug.cgi?id=372605 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/9fd4a43232a377e89708a695 |ta/4e88becceec72dba02a457bc |36223c9951d751e9|63c179e4e521a65a --- Comment #8 from Boudewijn Rempt --- Git commit 4e88becceec72dba02a457bc63c179e4e521a65a by Boudewijn Rempt, on behalf of Jouni Pentikäinen. Committed on 10/10/2018 at 07:41. Pushed by rempt into branch 'krita/4.1'. Fix moving keyframes beyond last column of the timeline (cherry picked from commit 9fd4a43232a377e89708a69536223c9951d751e9) M +4-4plugins/dockers/animation/timeline_frames_model.cpp https://commits.kde.org/krita/4e88becceec72dba02a457bc63c179e4e521a65a -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360541] HiDPI option in Qt also scales the canvas widget
https://bugs.kde.org/show_bug.cgi?id=360541 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/9d95d8d5386eecba733392c5 |ta/3d77d9f5bae507e8461acc84 |514f230c82f65ee5|6389bac207849bb5 --- Comment #29 from Boudewijn Rempt --- Git commit 3d77d9f5bae507e8461acc846389bac207849bb5 by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 10/10/2018 at 07:40. Pushed by rempt into branch 'krita/4.1'. Fix canvas scale in HiDPI mode Qt has a bit complicated way to deal with openGL widget in scaled HiDPI mode. The openGL widget's framebuffer is stored in hardware pixels (physical coordinates), but before calling paintGL, Qt sets manual scaling with glOrtho that makes this FBO look as if it is stored in logical pixels. This patch basically takes it into account by setting a correct physical resolution in KisZoomManager::updateScreenResolution(). It has one non- trivial consequence. Now, when setting zoom to 100% and having pixel aspect mode activated, Flake coordinate system does **not** have 100% zoom, because it is measured in logical coordinates, but not in physical ones, which are bigger. Fixes T2299 (cherry picked from commit 9d95d8d5386eecba733392c5514f230c82f65ee5) M +1-1libs/ui/KisMainWindow.cpp M +3-0libs/ui/KisMainWindow.h M +7-0libs/ui/KisView.cpp M +2-0libs/ui/KisView.h M +1-0libs/ui/canvas/kis_canvas2.cpp M +19 -1libs/ui/canvas/kis_coordinates_converter.cpp M +2-0libs/ui/canvas/kis_coordinates_converter.h M +32 -5libs/ui/kis_zoom_manager.cc M +6-0libs/ui/kis_zoom_manager.h M +2-1libs/ui/opengl/kis_opengl_canvas2.cpp https://commits.kde.org/krita/3d77d9f5bae507e8461acc846389bac207849bb5 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399596] Tag tree keeps reverting back to incorrect format after re-adding collection
https://bugs.kde.org/show_bug.cgi?id=399596 --- Comment #2 from Sebas --- After clearing all tags from the wrong tag tree from the images and applying tags from the right tree format it seems to go good with the images, but... the tag tree format from the example keeps coming back. Empty of course. I did not try database maintenance by the way. Will do that and report back. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399397] Krita crashes after dragging entries in recent documents
https://bugs.kde.org/show_bug.cgi?id=399397 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/24d2b6bee643d75ffd5bcef7 |ta/f8cd40ae135fd1a892abd53d |54e26f94b861d126|f588d993614d41bf --- Comment #2 from Boudewijn Rempt --- Git commit f8cd40ae135fd1a892abd53df588d993614d41bf by Boudewijn Rempt. Committed on 10/10/2018 at 07:38. Pushed by rempt into branch 'krita/4.1'. M +1-0libs/ui/widgets/KisWelcomePageWidget.cpp https://commits.kde.org/krita/f8cd40ae135fd1a892abd53df588d993614d41bf -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 391706] 1384f275ab2f1ad1841753ee163af6d1b0bb952b causes problems mounting internal partitions, eSATA-hdds, and LUKS-containers
https://bugs.kde.org/show_bug.cgi?id=391706 --- Comment #27 from Stefan Brüns --- (In reply to José Alberto from comment #26) > This is back for LUKS containers (or maybe it was never completely gone, I > did never tested LUKS containers, I didn't even knew what they were last > time I posted here). > > I have recorded a video, just in case it helps. It will be in this link for > a month: https://my.owndrive.com/index.php/s/fshtH0Oi70eKQhG > > Thanks! Please describe exactly - how your setup looks like - what you do - what happens I will *not* try to extract information from some random internet video link! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395447] wallpaper selection menu shows old thumbnail when files are replaced
https://bugs.kde.org/show_bug.cgi?id=395447 Kai Uwe Broulik changed: What|Removed |Added Version Fixed In||5.15.0 Latest Commit||https://commits.kde.org/pla ||sma-workspace/de6f8246ecabc ||3a4102c7c29ce3a7f6c4987cfec Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Kai Uwe Broulik --- Git commit de6f8246ecabc3a4102c7c29ce3a7f6c4987cfec by Kai Uwe Broulik. Committed on 10/10/2018 at 10:04. Pushed by broulik into branch 'master'. [Background Model] Use own QCache for thumbnails Previously it would use an on-disk KImageCache which would never be invalidated. Moreover, it just uses KIO::PreviewJob which does its own more clever (compares mtime and other properties) on-disk caching already. It is using its own QCache rather than QPixmapCache to not jeopardize other caching for the potentially large wallpaper thumbnails that are only relevant while the dialog is open. FIXED-IN: 5.15.0 Differential Revision: https://phabricator.kde.org/D16095 M +0-1wallpapers/image/CMakeLists.txt M +13 -15 wallpapers/image/backgroundlistmodel.cpp M +2-3wallpapers/image/backgroundlistmodel.h https://commits.kde.org/plasma-workspace/de6f8246ecabc3a4102c7c29ce3a7f6c4987cfec -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 399050] Signature spoofing in PGP encrypted email (ID layer)
https://bugs.kde.org/show_bug.cgi?id=399050 Jan Kundrát changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #10 from Jan Kundrát --- > That's interesting, however I'd not rely on the config of the > IMAP server for > end-to-end security (which PGP is assumed to provide). And we are not, which is why I also added that second sentence :). E-mail headers and ESMTP-level envelopes not being covered by PGP. The IMAP server "can lie to us", and I claim that this does not open any extra attack vector compared to, e.g., your ESMTP host maliciously mangling stuff on delivery. That was my point. > Depends on your point of view. I would not say those issues are super-bad. > However, if we really want to rely on PGP for critical tasks > I'd say there is > still room for improvement in the UI of mail clients. Assume you receive a > signed email from you employer with testcase #2 which includes a > task-to-be-done-immediately (e.g. "The President: >>launch > missiles<<") -- you > may be stressed and not look into the signature details and just do it... Thanks for reporting this. I think that adding the signer's recipient address into the "valid signature" area will be an improvement. For anybody reading this -- patches welcome, I will only have a chance to work on this in a week or two, I guess. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399564] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=399564 David Edmundson changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kwi ||n/6724955a762413bcc6b87e490 ||9eadab593376f2a --- Comment #9 from David Edmundson --- Git commit 6724955a762413bcc6b87e4909eadab593376f2a by David Edmundson. Committed on 10/10/2018 at 10:14. Pushed by davidedmundson into branch 'Plasma/5.14'. [qpa] Always keep a at least one screen Summary: Qt does not like having no screens. Both Qt XCB and Wayland QPAs have systems pretend there's always at least 1 screen present. Kwin already uses a dummy screen on startup, this patch reinserts the dummy screen if the platform states that all real screens are removed. Test Plan: Logged in, everything still worked Did not reproduce the original bug Reviewers: #kwin, zzag Reviewed By: #kwin, zzag Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D16096 M +6-0plugins/qpa/integration.cpp https://commits.kde.org/kwin/6724955a762413bcc6b87e4909eadab593376f2a -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 257760] KPageWidget problems when using a custom header
https://bugs.kde.org/show_bug.cgi?id=257760 Christoph Feck changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #7 from Christoph Feck --- It's now possible to hide the header, see https://phabricator.kde.org/D15099 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 391706] 1384f275ab2f1ad1841753ee163af6d1b0bb952b causes problems mounting internal partitions, eSATA-hdds, and LUKS-containers
https://bugs.kde.org/show_bug.cgi?id=391706 --- Comment #28 from José Alberto --- (In reply to Stefan Brüns from comment #27) > (In reply to José Alberto from comment #26) > > This is back for LUKS containers (or maybe it was never completely gone, I > > did never tested LUKS containers, I didn't even knew what they were last > > time I posted here). > > > > I have recorded a video, just in case it helps. It will be in this link for > > a month: https://my.owndrive.com/index.php/s/fshtH0Oi70eKQhG > > > > Thanks! > > Please describe exactly > - how your setup looks like > - what you do > - what happens > > I will *not* try to extract information from some random internet video link! I didn't open a new bug because the setup has always been the same, you can find all the things you ask for in the first comment talking about luks containers. If you need more info than that, just ask more specifically and I'll give more information (see https://bugs.kde.org/show_bug.cgi?id=391706#c14 ). The video was *not* even necessary, I just added it in case it helps, it's not a random internet video, I recorded it. I cared to do it very straightforward so you can see what is happening (starts without pendrive, plug the pendrive, click on luks partition in dolphin, get the bug, repeat the bug by unmounting and mounting again). > I will *not* try to extract information from some random internet video link! Don't worry, I will not do it ever again, it seems I wasted my time on it. I did what I could, I don't have enough knowledge to try to fix it (if I had it, I would have tried it instead of recording a video, yes). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399127] Vector object fills itself when gradient stroke is selected in tool settings
https://bugs.kde.org/show_bug.cgi?id=399127 Emmet O'Neill changed: What|Removed |Added Status|CONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399599] New: Hidden files retain visual cue
https://bugs.kde.org/show_bug.cgi?id=399599 Bug ID: 399599 Summary: Hidden files retain visual cue Product: dolphin Version: 18.08.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: max.schett...@posteo.de Target Milestone: --- Hidden files in the preview have a visual indication that they are hidden, i.e., they are slightly transparent. When a hidden file is renamed such that it's not hidden anymore, this indication remains, until, e.g., refreshing dolphin via F5. STEPS TO REPRODUCE 0. Ensure hidden files are shown in dolphin (Ctrl+H) 1. Create a hidden file 2. Rename the file (removing the dot in front) OBSERVED RESULT The file retains its transparency EXPECTED RESULT Transparency should be removed SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399600] New: Inconsistent metadata in pictures and database when some albums are read-only
https://bugs.kde.org/show_bug.cgi?id=399600 Bug ID: 399600 Summary: Inconsistent metadata in pictures and database when some albums are read-only Product: digikam Version: 6.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Maintenance Assignee: digikam-bugs-n...@kde.org Reporter: iwannaber...@gmail.com Target Milestone: --- SUMMARY Not sure if a bug or a feature request. I like to keep my database synchronized with the metadata found inside the pictures and vice-versa. I share several library folder with other relatives, and each one is free to manage and edit their portion of the library however they want. Therefore, so some folders are read-only. When you reorganize or modify tags in pictures that are read-only, digikam does not show any warning messages, it just carries on, makes the changes in digikam's database, and leave the original pictures untouched. This leads to a mismatch between the database and the metadata stored in the pictures. Re-reading the metadata on those pictures restores the original state, confirming that picture files were not written. I think there should be a warning message when a picture could not be modified, and also digikam should not change the metadata for those pictures in the database. STEPS TO REPRODUCE 1. Edit picture in read-only album (e.g. add a tag or a face rectangle). 2. Observe how changes appear to have been successfully applied in digikam. 3. Re-scan the picture for metadata. OBSERVED RESULT Picture is restored back to the original information. Other users cannot see those changes in their library, leading to inconsistencies between users. EXPECTED RESULT A warning should appear saying that this album/picture is read only. That edit should not be reflected in digikam's metadata. SOFTWARE VERSIONS digikam-6.0.0-beta1-20181009T192839-x86-64.appimage in Ubuntu 16.04 64bit ADDITIONAL INFORMATION If a mix of read-only and read-write pictures are modified, the database should reflect both changes, only changing tags/faces/dates/etc. for the read-write elements, leaving the rest intact. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399600] Inconsistent metadata in pictures and database when some albums are read-only
https://bugs.kde.org/show_bug.cgi?id=399600 IWBR changed: What|Removed |Added CC||iwannaber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 393238] Reduce shadow size/strength for background windows
https://bugs.kde.org/show_bug.cgi?id=393238 Michael D changed: What|Removed |Added CC||nortex...@gmail.com --- Comment #5 from Michael D --- (In reply to Nate Graham from comment #3) > That wouldn't make sense; the Oxygen effect was more of a highlight, but the > Breeze effect is a shadow, not a highlight. > > What we could do is maybe reduce the shadow strength for inactive windows to > help distinguish the foreground window from others. macOS does this. macOS's shadows are also enormous, though, and reducing the shadow size for smaller shadows wouldn't make sense. E.g., I don't think reducing the shadow strength of inactive windows for medium-sized or smaller shadows makes sense. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 399245] Restore UI functionality related to "Show HTML side bar"
https://bugs.kde.org/show_bug.cgi?id=399245 imraro changed: What|Removed |Added CC||imr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[massif-visualizer] [Bug 399601] New: v0.7 - "mark as custom allocator" does not seem to do anything useful
https://bugs.kde.org/show_bug.cgi?id=399601 Bug ID: 399601 Summary: v0.7 - "mark as custom allocator" does not seem to do anything useful Product: massif-visualizer Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: massif-visuali...@kde.org Reporter: a...@weej.com Target Milestone: 0.4 SUMMARY In a massif profile I have, we have various C++ "allocate" methods that call other allocate methods (composed allocators). Unfortunately marking any of these stack frames as a custom allocator doesn't seem to do anything useful STEPS TO REPRODUCE 1. Load a profile containing stack traces that have "allocate"-like function calls 2. Right click such function calls and click "mark as custom allocator" OBSERVED RESULT * Item added to custom allocators list, but no change in stack traces EXPECTED RESULT * Item added to custom allocators list, and stack traces re-organized to show actual memory users, not allocators. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: n/a KDE Frameworks Version: n/a Qt Version: ADDITIONAL INFORMATION Running on Ubuntu 18.04, massif-visualizer installed from repo. Wondering if this is just a user error, or if it seems like a bug I can try to provide test cases and example massif reports. Many thanks for your great work! -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399602] New: "Draw window background gradient" should be renamed to "Draw title bar background gradient"
https://bugs.kde.org/show_bug.cgi?id=399602 Bug ID: 399602 Summary: "Draw window background gradient" should be renamed to "Draw title bar background gradient" Product: Breeze Version: 5.13.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: window decoration Assignee: unassigned-b...@kde.org Reporter: nortex...@gmail.com Target Milestone: --- Oxygen used to have an option to draw the window background gradient. But in breeze, what this option does is really just draw the title bar gradient. It should therefore be renamed to "Draw title bar background gradient". Since we're on the topic of renaming decorator options, in "Draw separator between Title Bar and Window", 'Title Bar' and 'Window' should not be capitalized. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 398847] Kaddressbook not parsing gmail contacts
https://bugs.kde.org/show_bug.cgi?id=398847 Jacopo Torrini changed: What|Removed |Added CC||jac...@gmail.com --- Comment #3 from Jacopo Torrini --- I confirm this bug for me. KAddressBook 5.9.1 KDE 5.14.0 KDE Frameworks 5.50.0 Qt 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396080] Global menu is lost when using doublecmd-qt5
https://bugs.kde.org/show_bug.cgi?id=396080 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com --- Comment #1 from Alexander Mentyu --- Sometimes after pressing F5 the panel menu widget is not displaying in panel at all - not empty space but the complete absence of the menu widget on panel. Sometimes after pressing F5 the menu widget stays in panel, closing Copy files dialog of doublecmd makes the panel menu widget becomes empty space but not removes it from panel, one more press F5 in doublecmd makes the menu panel widget disappears completely from panel. Operating System: Netrunner Rolling KDE Plasma Version: 5.13.5 Qt Version: 5.11.2 KDE Frameworks Version: 5.50.0 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 399603] New: KDE applications (Kontacts, KOrganizer etc.) crash at start
https://bugs.kde.org/show_bug.cgi?id=399603 Bug ID: 399603 Summary: KDE applications (Kontacts, KOrganizer etc.) crash at start Product: korganizer Version: 5.7.3 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: tanacs...@gmail.com Target Milestone: --- Application: korganizer (5.7.3) Qt Version: 5.11.1 Frameworks Version: 5.49.0 Operating System: Linux 4.18.0-1-amd64 x86_64 Distribution: Debian GNU/Linux testing (buster) -- Information about the crash: - What I was doing when the application crashed: Updated Debian from stable to Testing. Since that these applications crash. The crash can be reproduced every time. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcc4366ea80 (LWP 4074))] Thread 3 (Thread 0x7fcc416c7700 (LWP 4076)): #0 0x7fcc50b74739 in __GI___poll (fds=0x7fcc34004db0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fcc4c3ebe46 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fcc4c3ebf6c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fcc5109e24b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fcc5104b25b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fcc50e9a176 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fcc5082e545 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fcc50ea3d47 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fcc4d6f2f2a in start_thread (arg=0x7fcc416c7700) at pthread_create.c:463 #9 0x7fcc50b7eedf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fcc427f7700 (LWP 4075)): #0 0x7fcc50b74739 in __GI___poll (fds=0x7fcc427f6a38, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fcc4c179cf7 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fcc4c17b90a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fcc433786d9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fcc50ea3d47 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fcc4d6f2f2a in start_thread (arg=0x7fcc427f7700) at pthread_create.c:463 #6 0x7fcc50b7eedf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fcc4366ea80 (LWP 4074)): [KCrash Handler] #6 0xfff0 in ?? () #7 0x7fcc52fecf9d in KontactInterface::PimUniqueApplication::start(QStringList const&, bool) () from /usr/lib/x86_64-linux-gnu/libKF5KontactInterface.so.5 #8 0x55c94fcd90f3 in main () at ./src/main.cpp:55 #9 0x7fcc50aa9b17 in __libc_start_main (main=0x55c94fcd8df0 , argc=1, argv=0x7ffe849fa288, init=, fini=, rtld_fini=, stack_end=0x7ffe849fa278) at ../csu/libc-start.c:310 #10 0x55c94fcd92fa in _start () at /usr/include/x86_64-linux-gnu/qt5/QtCore/qdebug.h:125 The reporter indicates this bug may be a duplicate of or related to bug 389840. Possible duplicates by query: bug 398557, bug 398152, bug 396724, bug 396700, bug 389840. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396169] Global menu doesn't work well with Virtualbox (Virtual machine menu Device->USB hides randomly)
https://bugs.kde.org/show_bug.cgi?id=396169 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com --- Comment #1 from Alexander Mentyu --- Optical Drives, Network, USB submenus are shown only on first hover over them after it they aren't shown. Other submenus in 'Devices' menu are shown after subsequent hovers over them virtualbox 5.2.18-1 Operating System: Netrunner Rolling KDE Plasma Version: 5.13.5 Qt Version: 5.11.2 KDE Frameworks Version: 5.50.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399600] Inconsistent metadata in pictures and database when some albums are read-only
https://bugs.kde.org/show_bug.cgi?id=399600 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- What did you expect ? That DK write metadata in image even if file are read only ? We will never do that, even if it's possible technically. So for me it's not a bug, but a normal behavior. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399604] New: Discover chrashed when opening chrome-.deb.
https://bugs.kde.org/show_bug.cgi?id=399604 Bug ID: 399604 Summary: Discover chrashed when opening chrome-.deb. Product: Discover Version: 5.14.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: m...@emilharder.dk Target Milestone: --- Application: plasma-discover (5.14.0) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.15.0-36-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: - Openened .deb for the Chrome browser, downloaded from firefox. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f94b82a5c80 (LWP 31538))] Thread 11 (Thread 0x7f94652d7700 (LWP 31559)): #0 0x7f94b383e839 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f94b3f40564 in QSemaphore::acquire(int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f94b4147d70 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f94b171121b in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #4 0x7f94b17ab0fd in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #5 0x7f94b4147ad5 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f94b1706e59 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #7 0x7f94b17076f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #8 0x7f94b4147ad5 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f94b17a4d2f in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #10 0x7f94b17a1850 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7f94b17a1be5 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #12 0x7f94b17862e1 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #13 0x7f94b4147ad5 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f94b174eb73 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #15 0x7f94b174ec24 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #16 0x7f94b17624e1 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #17 0x7f94b572fe8c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f94b573745f in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f94b4118ab8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f94b41736dd in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f94adda6287 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f94adda64c0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f94adda654c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f94b4172a9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f94b4116dea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f94b3f41b8a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f94b3f4caab in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f94aff426db in start_thread (arg=0x7f94652d7700) at pthread_create.c:463 #29 0x7f94b384488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f947d773700 (LWP 31550)): #0 0x7f94aff48ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f947d772c30, expected=0, futex_word=0x7f9468005554) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f94aff48ed9 in __pthread_cond_wait_common (abstime=0x7f947d772d00, mutex=0x7f9468005500, cond=0x7f9468005528) at pthread_cond_wait.c:533 #2 0x7f94aff48ed9 in __pthread_cond_timedwait (cond=0x7f9468005528, mutex=0x7f9468005500, abstime=0x7f947d772d00) at pthread_cond_wait.c:667 #3 0x7f94b3f4d850 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f94b3f4425d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f94b3f4caab in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f94aff426db in start_thread (arg=0x7f947d773700) at pthread_create.c:463 #7 0x7f94b384488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f947df74700 (LWP 31549)): #0 0x7f94b3837bf9 in __GI___poll (fds=0x7f946800abb0, nfds=1, timeout=14796) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f94adda6439 in () at /usr/lib/x
[krusader] [Bug 107242] "Flat mode": show files without directory structure (path as a column in the list)
https://bugs.kde.org/show_bug.cgi?id=107242 Nick changed: What|Removed |Added Component|general |general Version|2.3.1 |2.7.1 Product|cervisia|krusader Assignee|christian.lo...@hamburg.de |krusader-bugs-n...@kde.org CC||krusader-bugs-n...@kde.org, ||nickefo...@gmail.com --- Comment #1 from Nick --- Please implement this feature. It's already 13 years since it has been reported and it's key feature. It has been mentioned several times in threads and blogs: https://unix.stackexchange.com/questions/156401/flat-view-of-directories https://zaley44.wordpress.com/2016/07/19/xtree-clones-for-linux-and-ubuntu/ and it's implemented in Total Commander since forever and also in Double Commander. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399599] Hidden files retain visual cue
https://bugs.kde.org/show_bug.cgi?id=399599 Julian Schraner changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||juliquad...@gmail.com Ever confirmed|0 |1 --- Comment #1 from Julian Schraner --- Confirmed, a rename should trigger a refresh of the visuals. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 321201] Fade Desktop effect takes place while fullscreen effect (desktop grid) is active
https://bugs.kde.org/show_bug.cgi?id=321201 David Edmundson changed: What|Removed |Added Version Fixed In||5.15.0 Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kwi ||n/b1b1360ec3fb0cfed2d3d ||b90985cf8495aa8 Resolution|--- |FIXED --- Comment #9 from David Edmundson --- Git commit b1b1360ec3fb0cfed2d3db90985cf8495aa8 by David Edmundson. Committed on 10/10/2018 at 11:32. Pushed by davidedmundson into branch 'master'. [effects/fadedesktop] Set animation as a fullscreen effect Summary: This lets other effects know whether they should inhibit or not which reduces visual glitches of overlapping animations. FIXED-IN: 5.15.0 Test Plan: Switched desktops, they still faded Reviewers: #kwin, zzag Subscribers: zzag, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D15474 M +18 -3effects/fadedesktop/package/contents/code/main.js https://commits.kde.org/kwin/b1b1360ec3fb0cfed2d3db90985cf8495aa8 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399600] Inconsistent metadata in pictures and database when some albums are read-only
https://bugs.kde.org/show_bug.cgi?id=399600 --- Comment #2 from IWBR --- No no, if a library is read only, of course there's no way of changing that. I meant that at least showing a warning when a file could not be modified would be helpful. I understand digikam is not responsible for other people's changes in a picture library, but it currently works very well in doing so, except for minor issues like this. A more simple solution I propose would be to automatically re-scan the picture metadata after a file has been modified. Such option already seems to exist (Settings, Configure digikam, Metadata, "Rescan files when files are modified"). This way, only changes that have been really applied will show in digikam, maintaining database-metadata integrity. So basically a Warning message + Metadata re-scan after changes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399592] Qt 5.12 Beta ~ on Wayland, trying to start Spectacle causes kwin_wayland to segfault
https://bugs.kde.org/show_bug.cgi?id=399592 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk Resolution|--- |BACKTRACE --- Comment #1 from David Edmundson --- Crashes should have a backtrace otherwise it's very hard to match them up with anything. And it doesn't crash here -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399600] Inconsistent metadata in pictures and database when some albums are read-only
https://bugs.kde.org/show_bug.cgi?id=399600 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #3 from Maik Qualmann --- It is actually a duplicate of its Bug 391891. There are users who purposely set their images to read only to protect them from change. I do not think they want to see a warning dialog all the time, probably no notification either. Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399580] Kwin Crashes after disabling Laptop monitor
https://bugs.kde.org/show_bug.cgi?id=399580 David Edmundson changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Crashes need a backtrace otherwise it's very hard to do anything. It's possible this is a duplicate of 399564 which is fixed in 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399600] Inconsistent metadata in pictures and database when some albums are read-only
https://bugs.kde.org/show_bug.cgi?id=399600 --- Comment #4 from IWBR --- Well, yep, it's based on this bug, but here I focus on the fact that the library can differ from the picture metadata because digikam (and users) thinks these changes have been applied when they have not. For instance, imagine one user correcting the date on one picture. He hits on apply, the change is reflected in digikam, so he considers the job is done. But internally, digikam found the file is read-only, didn't apply any changes, and shows mismatching information that won't be updated to other people (which might use digikam or other software to view those pictures). As I said, just re-scanning metadata when files have been modified should solve this issue. Plus the read-only warning (or greying-out the OK and Apply buttons, I don't know, but at least some feedback would be helpful). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397912] ALT key menu activation priority (top menubar vs. kwin button)
https://bugs.kde.org/show_bug.cgi?id=397912 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com --- Comment #1 from Alexander Mentyu --- Can you please tell what exact shortcuts are you using? Alt+F3 launches KWin menu ok Alt+F launches global title menu ok Operating System: Netrunner Rolling KDE Plasma Version: 5.13.5 Qt Version: 5.11.2 KDE Frameworks Version: 5.50.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398357] Different menues appear one by one with a latency in between
https://bugs.kde.org/show_bug.cgi?id=398357 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com --- Comment #1 from Alexander Mentyu --- Can it be linked to compositor speed settings? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399600] Inconsistent metadata in pictures and database when some albums are read-only
https://bugs.kde.org/show_bug.cgi?id=399600 --- Comment #5 from Maik Qualmann --- No, it does not work. For example, I have all my tags and all changes only in the database and also changed date. Therefore, re-reading and cleaning up the database before re-reading is also optional. And re-reading the metadata after each write would push performance into the basement when writing lots of metadata. For this they have the maintenance tool to later write the missing metadata into the images. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399600] Inconsistent metadata in pictures and database when some albums are read-only
https://bugs.kde.org/show_bug.cgi?id=399600 --- Comment #6 from IWBR --- Of course, re-reading the metadata from the images after changes should only occur if the option is checked (I suppose now it only detects external changes, right?). I actually manually re-read pictures after changes since date changes are not reflected in windows until I do so (bug #391440). It's a small price for keeping metadata-database consistency. Also, when writing large amounts of pictures, digikam already shows a warning. (PS: I don't get what you mean by "push performance into the basement") -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397912] ALT key menu activation priority (top menubar vs. kwin button)
https://bugs.kde.org/show_bug.cgi?id=397912 --- Comment #2 from avlas --- > Can you please tell what exact shortcuts are you using? Not sure I follow... I guess my explanation wasn't clear enough, so I try to clarify it further: when using the global menu, if one activates a particular application menu via ALT + underlined_character, that specific menu is triggered both at the globalmenu as well as within the application (via the kwin menu button). I think this behavior doesn't make much sense both functionally (depending on the application location the menues overlap) and visually (the look and feel of the menues opened in parallel doesn't look good), so I suggest using only the global menu if both the applet and the kwin menu button are available. I think this priority makes sense because one cannot have the global menu applet without the kwin menu button, but the kwin menu button can stand alone. Let me know if this doesn't clarify the question. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 323819] Windows with imported KWin rules for acitivities aren't visible
https://bugs.kde.org/show_bug.cgi?id=323819 David Edmundson changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk --- Comment #5 from David Edmundson --- Yeah, it sucks that we had an ID change, but it's too late to migrate stuff now. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 399605] New: plasma wayland session crash and shows login screen again
https://bugs.kde.org/show_bug.cgi?id=399605 Bug ID: 399605 Summary: plasma wayland session crash and shows login screen again Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: nisankho...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY I have installed KDE NEON on my two laptops all works perfect but when i do use plasma wayland than there a issue arise ... STEPS TO REPRODUCE 1. Start the system , login using plasma ( wayland ) 2. Open the terminal and do some stuff like commands , list directory , apt commands etc 3. Try to copy something from the terminal text or copy the previous command from terminal using mouse/touchpad 4. click the copy from pop up menu , screen becomes blank dark and few moments later it shows SDDM login screen SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.0 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION Distro : KDE neon 5.14 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398360] last menu entries remain accessible and functional when no window is under focus
https://bugs.kde.org/show_bug.cgi?id=398360 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Alexander Mentyu --- *** This bug has been marked as a duplicate of bug 395853 *** -- You are receiving this mail because: You are watching all bug changes.
