[gwenview] [Bug 393735] When opening an image file, the complete contents of the file's directory are also opened
https://bugs.kde.org/show_bug.cgi?id=393735 --- Comment #3 from Don Curtis --- (In reply to Henrik Fehlauer from comment #1) > > every other image in that directory has also been opened for inspection > Now sure what you mean by that. When I open the thumbnail bar, after the required image has opened, all of the other images in that directory are displayed in the thumbnail bar. > > Normally upon clicking on an image in Dolphin, Gwenview should open and > display only that image. If you have the Thumbnail bar enabled, afterwards > the thumbnails of the other images should be displayed eventually (and > cached for later). It opens and displays the "clicked" (in Dolphin) image only after about 25 seconds. AFAICS, at that point in time the thumbnail bar has been loaded with previews of the other images in the directory. I normally have the thumbnail bar "closed"/"hidden". -- I haven't found any means to 'disable' the thumbnail bar. > > Would you be able to record a short screencast/video of what you mean > exactly? I'll see about a series of screenshots. > > > Selecting all 58 images needs about 30 seconds before they're displayed. > Again I'm not really sure what you are trying to do here. Could you give > exact steps, and describe what you expected to happen vs. what really > happened? Dolphin, directory, , . -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 393735] When opening an image file, the complete contents of the file's directory are also opened
https://bugs.kde.org/show_bug.cgi?id=393735 --- Comment #4 from Don Curtis --- (In reply to Nate Graham from comment #2) > I think he's saying that he thinks that Gwenview took too long to load > because it was fetching data for the other images in the folder for the > purpose of building thumbnails in the thumbnail bar. Yes, exactly … -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 390341] kwin_wayland: crash often on copy and paste keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=390341 Markus Rathgeb changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #16 from Markus Rathgeb --- The problem with the Chrome Browser did not occur the last weeks anymore. Something has been changed. I don't know what has been changed, but at least I cannot reproduce. -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 393705] export query crashes KEXI
https://bugs.kde.org/show_bug.cgi?id=393705 --- Comment #5 from Barrie Backhurst --- (In reply to Jarosław Staniek from comment #2) > Git commit a00f37b024e1a0888de3266af9acff99e6f21aa2 by Jaroslaw Staniek. > Committed on 01/05/2018 at 21:29. > Pushed by staniek into branch '3.1'. > > Fix loading object data for given type and ID > > FIXED-IN:3.1.1 > > M +1-1src/KDbConnection.cpp > > https://commits.kde.org/kdb/a00f37b024e1a0888de3266af9acff99e6f21aa2 I have rebuilt kdb with the patch and the export works fine now Thankyou -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 393735] When opening an image file, the complete contents of the file's directory are also opened
https://bugs.kde.org/show_bug.cgi?id=393735 --- Comment #5 from Don Curtis --- Forget the screen shots. If the Gwenview history has been cleared, it displays an image clicked on in Dolphin within a second or two. Please note that, Gwenview has to be started from the KDE Plasma Application Launcher and the "Recent Folders" also has to be cleared if this performance is to be achieved. However, given an empty Gwenview history, simply opening an empty Gwenview session via the Plasma Application Launcher takes about 5 seconds to display and a further 20 to 25 seconds before the Menus become active. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 393735] When opening an image file, the complete contents of the file's directory are also opened
https://bugs.kde.org/show_bug.cgi?id=393735 --- Comment #6 from Don Curtis --- I seem to recall that, the newer KDE Plasma versions exhibit a better start-up time -- at least that's what the newest openSUSE Leap 15 comments are saying … -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 391499] KGPG crashes on setting trust level for self keypair
https://bugs.kde.org/show_bug.cgi?id=391499 --- Comment #4 from Rolf Eike Beer --- > I recompiled kgpg. > I killed the running kgpg and ran it from Konsole. Got the following: > $ kgpg This could very likely run the kgpg binary in your path, which probably is the distro one. Try "./kgpg" in your build directory. Please also make sure to have debug symbols and messages enabled, see https://utils.kde.org/projects/kgpg/building.php Please use "-D CMAKE_BUILD_TYPE=Debug" instead of DebugFull, this is obsolete and does not work anymore (will fix it later). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393754] New: Feature Request: Add api for changing document background color and opacity.
https://bugs.kde.org/show_bug.cgi?id=393754 Bug ID: 393754 Summary: Feature Request: Add api for changing document background color and opacity. Product: krita Version: 4.0.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: jhoolm...@gmail.com Target Milestone: --- Something in the lines of Document.setBackground(QColor color, float opacity) maybe? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393754] Feature Request: Add api for changing document background color and opacity.
https://bugs.kde.org/show_bug.cgi?id=393754 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393727] QDesktopServices::openUrl() fails on KDE Plasma
https://bugs.kde.org/show_bug.cgi?id=393727 --- Comment #5 from Kayra Akman --- (In reply to Moonchild from comment #4) > >I have filed the following bug report for Qt: > I'm using a GTK system and your test application works here. It just > triggers gvfs-open, so i think you just have some system misconfiguration > (IMO). It turned out Falkon was not recognized/reported as a web browser. Please see Comment #2 by me. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393737] Clear terminal display when closing and opening it
https://bugs.kde.org/show_bug.cgi?id=393737 Kayra Akman changed: What|Removed |Added CC||ckak...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 393638] Renaming Function
https://bugs.kde.org/show_bug.cgi?id=393638 --- Comment #2 from Milian Wolff --- could be due to nested event loops -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382698] xwayland windows react wrongly to middle/right clicks on maximise button
https://bugs.kde.org/show_bug.cgi?id=382698 --- Comment #3 from Frederik Gladhorn --- I think you are right and I simply mixed up the two. I agree of course that it's not the most important feature in the world, but it's on of the small stumbling blocks that makes me come back to using X instead. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 393220] [improvement] Possibility of showing the fitting line beyond the generating data points
https://bugs.kde.org/show_bug.cgi?id=393220 --- Comment #2 from urcind...@gmail.com --- (In reply to Stefan Gerlach from comment #1) > The evaluated range can now be changed the same as the range for fitting. Thanks very much. I just tried out this new feature. I found two issues: a) The initial value field of the evaluation range does not accept negative numbers. b) The last value field of the valuation range does not accept numbers larger than 99,99 (with the help of the up arrow) or 99 (if you just type it). My locale is set to Spanish and my number format uses the comma as the decimal separator. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393727] QDesktopServices::openUrl() fails on KDE Plasma
https://bugs.kde.org/show_bug.cgi?id=393727 --- Comment #6 from David Rosca --- Can you test with "xdg-open", that's what QDesktopServices::openUrl() should be calling. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393526] Dolphin crashed while copying 2 folders to SD
https://bugs.kde.org/show_bug.cgi?id=393526 --- Comment #2 from pfla...@gmail.com --- Hi Christopher, No, I finished copying (50GB) of stuff to SDHC without running into another crash. Thanks Allen Lau On Tue, May 1, 2018 at 6:06 PM, Christoph Feck wrote: > https://bugs.kde.org/show_bug.cgi?id=393526 > > Christoph Feck changed: > >What|Removed |Added > > >Severity|normal |crash > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 390934] Kaffeine 2.0.14 doesn't find leadtek DTV1800h and DTV1000-T PCI tuner cards
https://bugs.kde.org/show_bug.cgi?id=390934 Mauro Carvalho Chehab changed: What|Removed |Added Version|unspecified |2.0.14 -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 393222] kaffeine-2.0.14: build error: no matching function for call to ‘asString(DvbTransponderBase::TransmissionType)
https://bugs.kde.org/show_bug.cgi?id=393222 Mauro Carvalho Chehab changed: What|Removed |Added Version|unspecified |2.0.14 -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 393650] On scheduled recording, user can inadvertently initiate a second recording on the same channel.
https://bugs.kde.org/show_bug.cgi?id=393650 Mauro Carvalho Chehab changed: What|Removed |Added Version|unspecified |2.0.14 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 393738] Many "timeline:" and "search:" URLs no longer work
https://bugs.kde.org/show_bug.cgi?id=393738 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #4 from Kai Uwe Broulik --- search:/ isn't a real thing, the KFilePlacesModel rewrites that to baloosearch or filenamesearch depending on whether Baloo is to be used or not. I think this needs a better solution than adjusting every user of that URL (I fixed most in KIO but as you can tell there's more..) I just tried bisecting Baloo about the timeline:/ one but it looks the change is elsehwere. Perhaps some of the KUriFilter or KUrlNavigator changes that happened recently? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392653] Failed to send email. Network unreachable
https://bugs.kde.org/show_bug.cgi?id=392653 --- Comment #1 from wincak --- After I reported this issue it fixed itself eventually and sending email started working again without my direct intervention. For some time I was unable to reproduce the issue until it reappeared after recent software upgrade and disappeared again soon. I believe the upgrade process somehow breaks communication between KMail and Akonadi components and reboot fixes it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391317] popup - an application is requesting additional multimedia codecs
https://bugs.kde.org/show_bug.cgi?id=391317 --- Comment #14 from Krasi Georgiev --- Just now the same DOS was triggered by kde_powerdevil. basically just disconnected the power adaptor and started getting all these messages again. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 393755] New: No corresponding option in conf for GUI's pad "Mouse click emulation"
https://bugs.kde.org/show_bug.cgi?id=393755 Bug ID: 393755 Summary: No corresponding option in conf for GUI's pad "Mouse click emulation" Product: systemsettings Version: 5.12.4 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: michal.dybc...@gmail.com Target Milestone: --- Created attachment 112371 --> https://bugs.kde.org/attachment.cgi?id=112371&action=edit Pad "Mouse click emulation" option with grayed out sub-options At the moment Plasma's pad settings are stored in ~/.config/touchpadrc Enabling the "Mouse click emulation" in GUI is adding a line: Tapping=true Disabling the option is either making that line disappear or adds: Tapping=false The issue is: in GUI we have 3 sub-options for 1, 2 and 3 finger taps and they are grayed out. So either corresponding options are not developed yet or unknown, or incorrectly applied in conf. I'm raising this issue because this is how it looks like since a long time and middle click (3 finger tap) is producing notices with pasted text on a desktop which is supper annoying. On the other hand 1 finger tap is a necessity so it forces us to have this on (true) and yet don't allow us to disable 3 finger tap (middle mouse click emulation). This may create conflicts with libinput-gestures where we can define 3 finger swipes which they work wonderfully but not on Plasma, because each 3 finger swipe is interpreted as two actions: swipe and tap, producing unwanted notes on desktop space or pasting clipboard output to windows. I tried to counteract it with adding a line to: /etc/X11/xorg.conf.d/30-touchpad.conf Option "MiddleEmulation" "False" Didn't work, even after deleting touchpadrc and reboot. So far there seems to be no working method to disable 3 finger taps and if tap is on, it's on for all options. Some workaround would be to add an option to define what middle click (wheel click) does in mouse settings and we could choose: no effect, but mouse settings don't have such GUI option so far. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 377157] [Wayland] It's not possible to take a picture of a rectangle region
https://bugs.kde.org/show_bug.cgi?id=377157 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #5 from Fabian Vogt --- kwin has a dbus interface to do this, so #c1 is wrong (at least now). -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393727] QDesktopServices::openUrl() fails on KDE Plasma
https://bugs.kde.org/show_bug.cgi?id=393727
--- Comment #7 from Kayra Akman ---
(In reply to David Rosca from comment #6)
> Can you test with "xdg-open", that's what QDesktopServices::openUrl() should
> be calling.
xdg-open was not available on my system. After installing the xdg-utils package
openUrl() successfully opened Falkon. So it was neither Qt, nor KDE
Plasma/Falkon issue.
I've checked the relevant function in Qt
(http://code.qt.io/cgit/qt/qtbase.git/tree/src/platformsupport/services/genericunix/qgenericunixservices.cpp?h=5.9.5#n106)
If xdg-open is not available, Qt checks for kmfclient on KDE. If that check
fails, it checks for well-known browsers. That last check explains why Firefox
was opened although Falkon was the default browser.
Maybe Falkon should be added upstream into the "if (desktop ==
QByteArray("KDE"))" section.
--
You are receiving this mail because:
You are watching all bug changes.
[Falkon] [Bug 392805] Loading an URL from another application does not raise Falkon window to the top
https://bugs.kde.org/show_bug.cgi?id=392805 David Rosca changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #5 from David Rosca --- This should stay closed, because it works correctly. What the reporter wants is to steal focus, but that can only work on X11 and I don't think is a good idea. Currently it asks window manager to activate and raise the window, and it's up to window manager to handle it. If you use KWin, then you must set "Focus stealing prevention" to "None" to get the behavior you want. It works with firefox/chrome because they force raise the window, instead of letting the window manager decide what to do. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 393755] No corresponding option in conf for GUI's pad "Mouse click emulation"
https://bugs.kde.org/show_bug.cgi?id=393755 --- Comment #1 from Michał Dybczak --- To add some info, libinput documentation is here: https://www.systutorials.com/docs/linux/man/4-libinput/ Middle click emulation that I want to turn off is described: Option "MiddleEmulation" "bool" Enables middle button emulation. When enabled, pressing the left and right buttons simultaneously produces a middle mouse button click. What is suspicious, you can't press left and right when using pad so this option may be only for mouse and that would explain why Option "MiddleEmulation" "False" is not working in /etc/X11/xorg.conf.d/30-touchpad.conf This would also imply, that at the moment there is no correct libinput option for that GUI options. Can someone more knowledgeable look into it? Another course of action could be: filing a bug to libinput to add such option so it could be finally linked with Plasma's pad settings GUI and its config. What do you think? We can't have such nice options be indefinitely grayed out... -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393727] QDesktopServices::openUrl() fails on KDE Plasma
https://bugs.kde.org/show_bug.cgi?id=393727 David Rosca changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #8 from David Rosca --- xdg-open is standard desktop utility, it should be installed by default with all desktop environments. If not, you should probably report bug to your distribution. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 393756] New: Baloo file extractor fail on logon
https://bugs.kde.org/show_bug.cgi?id=393756 Bug ID: 393756 Summary: Baloo file extractor fail on logon Product: frameworks-baloo Version: 5.44.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: greg.shepp...@bigpond.com Target Milestone: --- Application: baloo_file_extractor (5.44.0) Qt Version: 5.9.4 Frameworks Version: 5.44.0 Operating System: Linux 4.16.5-200.fc27.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Every logon, the same message appears that baloo has crashed. this has been occuring since Fedora 22 (previously reported), now occurring with F27. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5b5037b500 (LWP 1759))] Thread 3 (Thread 0x7f5b31f55700 (LWP 1846)): #0 0x7f5b4c912c6b in poll () from /lib64/libc.so.6 #1 0x7f5b47be2e99 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f5b47be2fac in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f5b4d768c4b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f5b4d71696a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f5b4d5678ca in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f5b4ef37449 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x7f5b4d56bde2 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f5b4b81650b in start_thread () from /lib64/libpthread.so.0 #9 0x7f5b4c91d16f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f5b3b7c0700 (LWP 1760)): #0 0x7f5b4c912c6b in poll () from /lib64/libc.so.6 #1 0x7f5b4756bfe7 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f5b4756ddda in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f5b3e35ebf9 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7f5b4d56bde2 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f5b4b81650b in start_thread () from /lib64/libpthread.so.0 #6 0x7f5b4c91d16f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f5b5037b500 (LWP 1759)): [KCrash Handler] #6 0x7f5b4c8c79a1 in __memmove_sse2_unaligned_erms () from /lib64/libc.so.6 #7 0x7f5b4d56e200 in QByteArray::QByteArray(char const*, int) () from /lib64/libQt5Core.so.5 #8 0x7f5b4f5d6511 in Baloo::IdFilenameDB::get(unsigned long long) () from /lib64/libKF5BalooEngine.so.5 #9 0x7f5b4f5cff0f in Baloo::DocumentUrlDB::get(unsigned long long) const () from /lib64/libKF5BalooEngine.so.5 #10 0x7f5b4f5e0834 in Baloo::Transaction::documentUrl(unsigned long long) const () from /lib64/libKF5BalooEngine.so.5 #11 0x55f4536d7878 in Baloo::App::processNextFile() () #12 0x7f5b4d74c934 in QSingleShotTimer::timerEvent(QTimerEvent*) () from /lib64/libQt5Core.so.5 #13 0x7f5b4d74121b in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #14 0x7f5b4e38492c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #15 0x7f5b4e38c174 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #16 0x7f5b4d717be7 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #17 0x7f5b4d767f5b in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #18 0x7f5b4d768829 in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #19 0x7f5b47be2b77 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #20 0x7f5b47be2f20 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #21 0x7f5b47be2fac in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #22 0x7f5b4d768c2f in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #23 0x7f5b4d71696a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #24 0x7f5b4d71f094 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #25 0x55f4536d6a2f in main () Possible duplicates by query: bug 373006. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 380133] Cannot see/change default browser settings
https://bugs.kde.org/show_bug.cgi?id=380133 Kayra Akman changed: What|Removed |Added Component|general |kcm_componentchooser Assignee|plasma-b...@kde.org |unassigned-b...@kde.org CC||ckak...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 393220] [improvement] Possibility of showing the fitting line beyond the generating data points
https://bugs.kde.org/show_bug.cgi?id=393220 --- Comment #3 from Stefan Gerlach --- The limits for the spin boxes are now set from the default to more realistic values. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 380133] Cannot see/change default browser settings
https://bugs.kde.org/show_bug.cgi?id=380133 --- Comment #3 from Kayra Akman --- While dealing with Bug 393727 I have noticed the issue described in this bug report is valid for Plasma 5.12 on Kubuntu 18.04. I have Firefox and Falkon installed on my system. When I choose Falkon "in the following application" drop-down of Default Applications > Web Browser, links open in Falkon as expected. If I choose the "in an application based on the contents of the URL" option, links open in Firefox. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393748] Plasma freezes on multiple file CUT - Length of time determined by number of file
https://bugs.kde.org/show_bug.cgi?id=393748 Hicks1gb changed: What|Removed |Added CC||hicks...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 392591] System Config, Discovery and Shutdown Dialog crash after a time
https://bugs.kde.org/show_bug.cgi?id=392591 Aleix Pol changed: What|Removed |Added CC||aespe...@gmail.com --- Comment #5 from Aleix Pol --- *** Bug 393596 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 393735] When opening an image file, the complete contents of the file's directory are also opened
https://bugs.kde.org/show_bug.cgi?id=393735 --- Comment #7 from Henrik Fehlauer --- I'm confused. First you say you have good performance with a clean history: > If the Gwenview history has been cleared, it displays an > image clicked on in Dolphin within a second or two But then you are saying the opposite: > given an empty Gwenview history, simply opening an empty Gwenview > session via the Plasma Application Launcher takes about 5 seconds > to display and a further 20 to 25 seconds The only explanation I have for this is that you have a slow network folder added to your Places panel. Could you tell us more about where you are opening images from, and what your Places panel contains? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 393596] Discover crash
https://bugs.kde.org/show_bug.cgi?id=393596 Aleix Pol changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Aleix Pol --- *** This bug has been marked as a duplicate of bug 392591 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 393683] Problemi aggiornamenti
https://bugs.kde.org/show_bug.cgi?id=393683 Aleix Pol changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Aleix Pol --- We need more information than that. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 393640] Couldn't open appstream://org.kde.knotes.desktop
https://bugs.kde.org/show_bug.cgi?id=393640 Aleix Pol changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Aleix Pol --- Please answer Antonio's question. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 393735] When opening an image file, the complete contents of the file's directory are also opened
https://bugs.kde.org/show_bug.cgi?id=393735 --- Comment #8 from Don Curtis --- (In reply to Henrik Fehlauer from comment #7) > I'm confused. First you say you have good performance with a clean history: > > > If the Gwenview history has been cleared, it displays an > > image clicked on in Dolphin within a second or two > But then you are saying the opposite: > > > given an empty Gwenview history, simply opening an empty Gwenview > > session via the Plasma Application Launcher takes about 5 seconds > > to display and a further 20 to 25 seconds > > The only explanation I have for this is that you have a slow network folder > added to your Places panel. Could you tell us more about where you are > opening images from, and what your Places panel contains? Yes, in the Places panel there're 3 directories on two network servers: - 2 SMB shares on an AVM FRITZ!Box DSL Router; - one NFS auto-mount point on a QNAP NAS. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393757] New: Layer style doesn't work inside clipping group
https://bugs.kde.org/show_bug.cgi?id=393757 Bug ID: 393757 Summary: Layer style doesn't work inside clipping group Product: krita Version: 4.1 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: layer styles Assignee: krita-bugs-n...@kde.org Reporter: ngmstu...@yahoo.co.uk Target Milestone: --- As summary suggests, if you have a layer inside a clipping group with inherit alpha enabled, it ignores the Layer style, in my case I have used an outer glow. I am using WIN7 OS -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 393602] Hardcoded style
https://bugs.kde.org/show_bug.cgi?id=393602 Aleix Pol changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #1 from Aleix Pol --- Please report to Kvantum. Tested here, worked properly. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393758] New: crash during assigned tag
https://bugs.kde.org/show_bug.cgi?id=393758 Bug ID: 393758 Summary: crash during assigned tag Product: digikam Version: 5.9.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: umv...@gmail.com Target Milestone: --- Application: digikam (5.9.0) Qt Version: 5.10.0 Frameworks Version: 5.45.0 Operating System: Linux 4.4.126-48-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: crash during assigned tag and save in xmp digikam is slowly than i must to reopen The crash can be reproduced sometimes. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7575e32a00 (LWP 10616))] Thread 46 (Thread 0x7f75249d0700 (LWP 10847)): #0 0x7f756dc310ff in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7571f7ce8b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x1fdf8b0) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, readWriteLock=0x23134e8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:239 #3 0x7f7569f8644b in QtAV::BlockingQueue::take() () from /usr/lib64/libQtAV.so.1 #4 0x7f7569ff60cb in QtAV::ExtractThread::run() () from /usr/lib64/libQtAV.so.1 #5 0x7f7571f7be0f in QThreadPrivate::start (arg=0x23134b0) at thread/qthread_unix.cpp:376 #6 0x7f756dc2c724 in start_thread () from /lib64/libpthread.so.0 #7 0x7f757128be8d in clone () from /lib64/libc.so.6 Thread 45 (Thread 0x7f73aeff5700 (LWP 10720)): #0 0x7f756dc310ff in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7571f7ce8b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x5c61a20) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, readWriteLock=0x5c615a8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:239 #3 0x7f7569f8644b in QtAV::BlockingQueue::take() () from /usr/lib64/libQtAV.so.1 #4 0x7f7569ff60cb in QtAV::ExtractThread::run() () from /usr/lib64/libQtAV.so.1 #5 0x7f7571f7be0f in QThreadPrivate::start (arg=0x5c61570) at thread/qthread_unix.cpp:376 #6 0x7f756dc2c724 in start_thread () from /lib64/libpthread.so.0 #7 0x7f757128be8d in clone () from /lib64/libc.so.6 Thread 44 (Thread 0x7f73af7f6700 (LWP 10719)): #0 0x7f756dc310ff in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7571f7ce8b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x5ac1630) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, readWriteLock=0x5af83e8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:239 #3 0x7f7569f8644b in QtAV::BlockingQueue::take() () from /usr/lib64/libQtAV.so.1 #4 0x7f7569ff60cb in QtAV::ExtractThread::run() () from /usr/lib64/libQtAV.so.1 #5 0x7f7571f7be0f in QThreadPrivate::start (arg=0x5af83b0) at thread/qthread_unix.cpp:376 #6 0x7f756dc2c724 in start_thread () from /lib64/libpthread.so.0 #7 0x7f757128be8d in clone () from /lib64/libc.so.6 Thread 43 (Thread 0x7f73afff7700 (LWP 10718)): #0 0x7f756dc310ff in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7571f7ce8b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x5af73a0) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, readWriteLock=0x5af6ee8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:239 #3 0x7f7569f8644b in QtAV::BlockingQueue::take() () from /usr/lib64/libQtAV.so.1 #4 0x7f7569ff60cb in QtAV::ExtractThread::run() () from /usr/lib64/libQtAV.so.1 #5 0x7f7571f7be0f in QThreadPrivate::start (arg=0x5af6eb0) at thread/qthread_unix.cpp:376 #6 0x7f756dc2c724 in start_thread () from /lib64/libpthread.so.0 #7 0x7f757128be8d in clone () from /lib64/libc.so.6 Thread 42 (Thread 0x7f73b07f8700 (LWP 10717)): #0 0x7f756dc310ff in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7571f7ce8b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x5af4d90) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, readWriteLock=0x5af48d8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:239 #3 0x7f7569f8644b in QtAV::BlockingQueue::take() () from /usr/lib64/libQtAV.so.1 #4 0x7f7569ff60cb in QtAV::ExtractThread::run() () from /usr/lib64/libQtAV.so.1 #5 0x7f7571f7be0f in QThreadPrivate::start (arg=0x5af48a0) at thread/qthread_unix.cpp:376 #6 0x7f756dc2c724 in start_thread () from /lib64/libpthread.so.0 #7 0x7f757128be8d in clone () from /lib64/libc.so.6 Thread 41 (Thread
[krita] [Bug 393757] Layer style doesn't work inside clipping group
https://bugs.kde.org/show_bug.cgi?id=393757 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Are you sure this isn't a duplicate of https://bugs.kde.org/show_bug.cgi?id=354376 ? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 306818] Okular cannot close instructions overlay in PDF
https://bugs.kde.org/show_bug.cgi?id=306818 --- Comment #8 from Andre Heinecke --- This example is extra fun... Although it uses the Hide Actions, which we now support, the trigger is different and not yet supported. The "Help" overlays are text edits with an actionMousePressed annotation. This is similar to Bug 307304 (where there are FocusIn / FocusOut) action triggers . I've opened a Task for this, as I really think that it's important to handle these triggers in forms: https://phabricator.kde.org/T8627 But for added fun: The Text edits with the help text are Read Only (thats why they look so strange if you Show Forms). So we now have a use case to show Widgets for Read Only form fields, because they could have actions attached. :-/ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393758] crash during assigned tag
https://bugs.kde.org/show_bug.cgi?id=393758 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|general |Thumbs-Engine --- Comment #1 from caulier.gil...@gmail.com --- It crash while recreating thumbnail... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393758] crash during assigned tag
https://bugs.kde.org/show_bug.cgi?id=393758 --- Comment #2 from caulier.gil...@gmail.com --- It will be instructive to see if you can reproduce this problem using current DK 6.0.0 pre-release AppImage bundle for Linux. https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393748] Plasma freezes on multiple file CUT - Length of time determined by number of file
https://bugs.kde.org/show_bug.cgi?id=393748 --- Comment #5 from Nick --- More Info, If I use Krusader instead of Dolphin to move those 120 files, plasmashell does not freeze. Plasmashell only freezes when using Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 377911] [Wayland] RDP doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=377911 --- Comment #8 from Markus Rathgeb --- Urs Wolfer, on my system freerdp comes with two binaries: /usr/bin/xfreerdp /usr/bin/wlfreerdp I assume for Wayland we should use wlfreerdp for Wayland. Do you work on KRDC on Wayland support? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 393759] New: System monitor crashes randomly when closed
https://bugs.kde.org/show_bug.cgi?id=393759 Bug ID: 393759 Summary: System monitor crashes randomly when closed Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: lucasjsolive...@gmail.com Target Milestone: --- Application: kdeinit5 (5.12.4) Qt Version: 5.10.0 Frameworks Version: 5.45.0 Operating System: Linux 4.13.0-39-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: This crash happens sometimes when I close the system monitor. The crash can be reproduced sometimes. -- Backtrace: Application: Monitor do sistema (kdeinit5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb8240fa780 (LWP 12452))] Thread 5 (Thread 0x7fb7e3fff700 (LWP 12474)): #0 0x7fb8221d074d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb81e7c538c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb81e7c5712 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb80b6e79d6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fb81e7ebbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb8206376ba in start_thread (arg=0x7fb7e3fff700) at pthread_create.c:333 #6 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fb7ebc92700 (LWP 12473)): #0 0x7fb81e809a90 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb81e7c52ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb81e7c549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb81e7c54d9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb81e7ebbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb8206376ba in start_thread (arg=0x7fb7ebc92700) at pthread_create.c:333 #6 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fb7fa960700 (LWP 12455)): #0 0x7fb8221cc27d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb81e370073 in ?? () from /usr/lib/nvidia-390/tls/libnvidia-tls.so.390.48 #2 0x7fb81e8086f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb81e7c4e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb81e7c5330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb81e7c549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fb8227815cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb82272864a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb822548554 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fb81877a2c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7fb82254d6eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fb8206376ba in start_thread (arg=0x7fb7fa960700) at pthread_create.c:333 #12 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fb8093f8700 (LWP 12453)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb82196e91c in std::condition_variable::wait(std::unique_lock&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #2 0x7fb80fbb77ae in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fb80fbb78c9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #4 0x7fb821973c80 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #5 0x7fb8206376ba in start_thread (arg=0x7fb8093f8700) at pthread_create.c:333 #6 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fb8240fa780 (LWP 12452)): [KCrash Handler] #6 0x7fb82210a428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7fb82210c02a in __GI_abort () at abort.c:89 #8 0x7fb82214c7ea in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fb822265ed8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #9 0x7fb82215537a in malloc_printerr (ar_ptr=, ptr=, str=0x7fb822265fe8 "double free or corruption (out)", action=3) at malloc.c:5006 #10 _int_free (av=, p=, have_lock=0) at malloc.c:3867 #11 0x7fb82215953c in __GI___libc_free (mem=) at malloc.c:2968 #12 0x7fb822754454 in QObjectPrivate::Connection::~Connection() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fb82275ed1c in QObject::~QObject() () from /usr/lib/
[kde] [Bug 393760] New: System monitor crashes randomly when closed
https://bugs.kde.org/show_bug.cgi?id=393760 Bug ID: 393760 Summary: System monitor crashes randomly when closed Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: lucasjsolive...@gmail.com Target Milestone: --- Application: kdeinit5 (5.12.4) Qt Version: 5.10.0 Frameworks Version: 5.45.0 Operating System: Linux 4.13.0-39-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: This crash happens sometimes when I close the system monitor. The crash can be reproduced sometimes. -- Backtrace: Application: Monitor do sistema (kdeinit5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb8240fa780 (LWP 12452))] Thread 5 (Thread 0x7fb7e3fff700 (LWP 12474)): #0 0x7fb8221d074d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb81e7c538c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb81e7c5712 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb80b6e79d6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fb81e7ebbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb8206376ba in start_thread (arg=0x7fb7e3fff700) at pthread_create.c:333 #6 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fb7ebc92700 (LWP 12473)): #0 0x7fb81e809a90 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb81e7c52ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb81e7c549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb81e7c54d9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb81e7ebbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb8206376ba in start_thread (arg=0x7fb7ebc92700) at pthread_create.c:333 #6 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fb7fa960700 (LWP 12455)): #0 0x7fb8221cc27d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb81e370073 in ?? () from /usr/lib/nvidia-390/tls/libnvidia-tls.so.390.48 #2 0x7fb81e8086f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb81e7c4e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb81e7c5330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb81e7c549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fb8227815cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb82272864a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb822548554 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fb81877a2c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7fb82254d6eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fb8206376ba in start_thread (arg=0x7fb7fa960700) at pthread_create.c:333 #12 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fb8093f8700 (LWP 12453)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb82196e91c in std::condition_variable::wait(std::unique_lock&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #2 0x7fb80fbb77ae in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fb80fbb78c9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #4 0x7fb821973c80 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #5 0x7fb8206376ba in start_thread (arg=0x7fb8093f8700) at pthread_create.c:333 #6 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fb8240fa780 (LWP 12452)): [KCrash Handler] #6 0x7fb82210a428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7fb82210c02a in __GI_abort () at abort.c:89 #8 0x7fb82214c7ea in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fb822265ed8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #9 0x7fb82215537a in malloc_printerr (ar_ptr=, ptr=, str=0x7fb822265fe8 "double free or corruption (out)", action=3) at malloc.c:5006 #10 _int_free (av=, p=, have_lock=0) at malloc.c:3867 #11 0x7fb82215953c in __GI___libc_free (mem=) at malloc.c:2968 #12 0x7fb822754454 in QObjectPrivate::Connection::~Connection() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fb82275ed1c in QObject::~QObject() () from /usr/lib/
[krita] [Bug 393757] Layer style doesn't work inside clipping group
https://bugs.kde.org/show_bug.cgi?id=393757 --- Comment #2 from brusheco --- (In reply to Boudewijn Rempt from comment #1) > Are you sure this isn't a duplicate of > https://bugs.kde.org/show_bug.cgi?id=354376 ? yes it appears so, apologies. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 393764] New: System monitor crashes randomly when closed
https://bugs.kde.org/show_bug.cgi?id=393764 Bug ID: 393764 Summary: System monitor crashes randomly when closed Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: lucasjsolive...@gmail.com Target Milestone: --- Application: kdeinit5 (5.12.4) Qt Version: 5.10.0 Frameworks Version: 5.45.0 Operating System: Linux 4.13.0-39-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: This crash happens sometimes when I close the system monitor. The crash can be reproduced sometimes. -- Backtrace: Application: Monitor do sistema (kdeinit5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb8240fa780 (LWP 12452))] Thread 5 (Thread 0x7fb7e3fff700 (LWP 12474)): #0 0x7fb8221d074d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb81e7c538c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb81e7c5712 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb80b6e79d6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fb81e7ebbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb8206376ba in start_thread (arg=0x7fb7e3fff700) at pthread_create.c:333 #6 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fb7ebc92700 (LWP 12473)): #0 0x7fb81e809a90 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb81e7c52ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb81e7c549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb81e7c54d9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb81e7ebbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb8206376ba in start_thread (arg=0x7fb7ebc92700) at pthread_create.c:333 #6 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fb7fa960700 (LWP 12455)): #0 0x7fb8221cc27d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb81e370073 in ?? () from /usr/lib/nvidia-390/tls/libnvidia-tls.so.390.48 #2 0x7fb81e8086f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb81e7c4e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb81e7c5330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb81e7c549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fb8227815cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb82272864a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb822548554 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fb81877a2c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7fb82254d6eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fb8206376ba in start_thread (arg=0x7fb7fa960700) at pthread_create.c:333 #12 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fb8093f8700 (LWP 12453)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb82196e91c in std::condition_variable::wait(std::unique_lock&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #2 0x7fb80fbb77ae in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fb80fbb78c9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #4 0x7fb821973c80 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #5 0x7fb8206376ba in start_thread (arg=0x7fb8093f8700) at pthread_create.c:333 #6 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fb8240fa780 (LWP 12452)): [KCrash Handler] #6 0x7fb82210a428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7fb82210c02a in __GI_abort () at abort.c:89 #8 0x7fb82214c7ea in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fb822265ed8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #9 0x7fb82215537a in malloc_printerr (ar_ptr=, ptr=, str=0x7fb822265fe8 "double free or corruption (out)", action=3) at malloc.c:5006 #10 _int_free (av=, p=, have_lock=0) at malloc.c:3867 #11 0x7fb82215953c in __GI___libc_free (mem=) at malloc.c:2968 #12 0x7fb822754454 in QObjectPrivate::Connection::~Connection() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fb82275ed1c in QObject::~QObject() () from /usr/lib/
[kde] [Bug 393763] New: System monitor crashes randomly when closed
https://bugs.kde.org/show_bug.cgi?id=393763 Bug ID: 393763 Summary: System monitor crashes randomly when closed Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: lucasjsolive...@gmail.com Target Milestone: --- Application: kdeinit5 (5.12.4) Qt Version: 5.10.0 Frameworks Version: 5.45.0 Operating System: Linux 4.13.0-39-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: This crash happens sometimes when I close the system monitor. The crash can be reproduced sometimes. -- Backtrace: Application: Monitor do sistema (kdeinit5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb8240fa780 (LWP 12452))] Thread 5 (Thread 0x7fb7e3fff700 (LWP 12474)): #0 0x7fb8221d074d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb81e7c538c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb81e7c5712 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb80b6e79d6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fb81e7ebbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb8206376ba in start_thread (arg=0x7fb7e3fff700) at pthread_create.c:333 #6 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fb7ebc92700 (LWP 12473)): #0 0x7fb81e809a90 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb81e7c52ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb81e7c549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb81e7c54d9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb81e7ebbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb8206376ba in start_thread (arg=0x7fb7ebc92700) at pthread_create.c:333 #6 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fb7fa960700 (LWP 12455)): #0 0x7fb8221cc27d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb81e370073 in ?? () from /usr/lib/nvidia-390/tls/libnvidia-tls.so.390.48 #2 0x7fb81e8086f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb81e7c4e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb81e7c5330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb81e7c549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fb8227815cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb82272864a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb822548554 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fb81877a2c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7fb82254d6eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fb8206376ba in start_thread (arg=0x7fb7fa960700) at pthread_create.c:333 #12 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fb8093f8700 (LWP 12453)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb82196e91c in std::condition_variable::wait(std::unique_lock&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #2 0x7fb80fbb77ae in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fb80fbb78c9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #4 0x7fb821973c80 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #5 0x7fb8206376ba in start_thread (arg=0x7fb8093f8700) at pthread_create.c:333 #6 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fb8240fa780 (LWP 12452)): [KCrash Handler] #6 0x7fb82210a428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7fb82210c02a in __GI_abort () at abort.c:89 #8 0x7fb82214c7ea in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fb822265ed8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #9 0x7fb82215537a in malloc_printerr (ar_ptr=, ptr=, str=0x7fb822265fe8 "double free or corruption (out)", action=3) at malloc.c:5006 #10 _int_free (av=, p=, have_lock=0) at malloc.c:3867 #11 0x7fb82215953c in __GI___libc_free (mem=) at malloc.c:2968 #12 0x7fb822754454 in QObjectPrivate::Connection::~Connection() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fb82275ed1c in QObject::~QObject() () from /usr/lib/
[kde] [Bug 393765] New: System monitor crashes randomly when closed
https://bugs.kde.org/show_bug.cgi?id=393765 Bug ID: 393765 Summary: System monitor crashes randomly when closed Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: lucasjsolive...@gmail.com Target Milestone: --- Application: kdeinit5 (5.12.4) Qt Version: 5.10.0 Frameworks Version: 5.45.0 Operating System: Linux 4.13.0-39-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: This crash happens sometimes when I close the system monitor. The crash can be reproduced sometimes. -- Backtrace: Application: Monitor do sistema (kdeinit5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb8240fa780 (LWP 12452))] Thread 5 (Thread 0x7fb7e3fff700 (LWP 12474)): #0 0x7fb8221d074d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb81e7c538c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb81e7c5712 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb80b6e79d6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fb81e7ebbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb8206376ba in start_thread (arg=0x7fb7e3fff700) at pthread_create.c:333 #6 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fb7ebc92700 (LWP 12473)): #0 0x7fb81e809a90 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb81e7c52ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb81e7c549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb81e7c54d9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb81e7ebbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb8206376ba in start_thread (arg=0x7fb7ebc92700) at pthread_create.c:333 #6 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fb7fa960700 (LWP 12455)): #0 0x7fb8221cc27d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb81e370073 in ?? () from /usr/lib/nvidia-390/tls/libnvidia-tls.so.390.48 #2 0x7fb81e8086f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb81e7c4e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb81e7c5330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb81e7c549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fb8227815cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb82272864a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb822548554 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fb81877a2c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7fb82254d6eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fb8206376ba in start_thread (arg=0x7fb7fa960700) at pthread_create.c:333 #12 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fb8093f8700 (LWP 12453)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb82196e91c in std::condition_variable::wait(std::unique_lock&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #2 0x7fb80fbb77ae in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fb80fbb78c9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #4 0x7fb821973c80 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #5 0x7fb8206376ba in start_thread (arg=0x7fb8093f8700) at pthread_create.c:333 #6 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fb8240fa780 (LWP 12452)): [KCrash Handler] #6 0x7fb82210a428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7fb82210c02a in __GI_abort () at abort.c:89 #8 0x7fb82214c7ea in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fb822265ed8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #9 0x7fb82215537a in malloc_printerr (ar_ptr=, ptr=, str=0x7fb822265fe8 "double free or corruption (out)", action=3) at malloc.c:5006 #10 _int_free (av=, p=, have_lock=0) at malloc.c:3867 #11 0x7fb82215953c in __GI___libc_free (mem=) at malloc.c:2968 #12 0x7fb822754454 in QObjectPrivate::Connection::~Connection() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fb82275ed1c in QObject::~QObject() () from /usr/lib/
[kde] [Bug 393761] New: System monitor crashes randomly when closed
https://bugs.kde.org/show_bug.cgi?id=393761 Bug ID: 393761 Summary: System monitor crashes randomly when closed Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: lucasjsolive...@gmail.com Target Milestone: --- Application: kdeinit5 (5.12.4) Qt Version: 5.10.0 Frameworks Version: 5.45.0 Operating System: Linux 4.13.0-39-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: This crash happens sometimes when I close the system monitor. The crash can be reproduced sometimes. -- Backtrace: Application: Monitor do sistema (kdeinit5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb8240fa780 (LWP 12452))] Thread 5 (Thread 0x7fb7e3fff700 (LWP 12474)): #0 0x7fb8221d074d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb81e7c538c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb81e7c5712 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb80b6e79d6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fb81e7ebbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb8206376ba in start_thread (arg=0x7fb7e3fff700) at pthread_create.c:333 #6 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fb7ebc92700 (LWP 12473)): #0 0x7fb81e809a90 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb81e7c52ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb81e7c549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb81e7c54d9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb81e7ebbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb8206376ba in start_thread (arg=0x7fb7ebc92700) at pthread_create.c:333 #6 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fb7fa960700 (LWP 12455)): #0 0x7fb8221cc27d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb81e370073 in ?? () from /usr/lib/nvidia-390/tls/libnvidia-tls.so.390.48 #2 0x7fb81e8086f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb81e7c4e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb81e7c5330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb81e7c549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fb8227815cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb82272864a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb822548554 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fb81877a2c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7fb82254d6eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fb8206376ba in start_thread (arg=0x7fb7fa960700) at pthread_create.c:333 #12 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fb8093f8700 (LWP 12453)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb82196e91c in std::condition_variable::wait(std::unique_lock&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #2 0x7fb80fbb77ae in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fb80fbb78c9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #4 0x7fb821973c80 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #5 0x7fb8206376ba in start_thread (arg=0x7fb8093f8700) at pthread_create.c:333 #6 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fb8240fa780 (LWP 12452)): [KCrash Handler] #6 0x7fb82210a428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7fb82210c02a in __GI_abort () at abort.c:89 #8 0x7fb82214c7ea in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fb822265ed8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #9 0x7fb82215537a in malloc_printerr (ar_ptr=, ptr=, str=0x7fb822265fe8 "double free or corruption (out)", action=3) at malloc.c:5006 #10 _int_free (av=, p=, have_lock=0) at malloc.c:3867 #11 0x7fb82215953c in __GI___libc_free (mem=) at malloc.c:2968 #12 0x7fb822754454 in QObjectPrivate::Connection::~Connection() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fb82275ed1c in QObject::~QObject() () from /usr/lib/
[kde] [Bug 393762] New: System monitor crashes randomly when closed
https://bugs.kde.org/show_bug.cgi?id=393762 Bug ID: 393762 Summary: System monitor crashes randomly when closed Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: lucasjsolive...@gmail.com Target Milestone: --- Application: kdeinit5 (5.12.4) Qt Version: 5.10.0 Frameworks Version: 5.45.0 Operating System: Linux 4.13.0-39-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: This crash happens sometimes when I close the system monitor. The crash can be reproduced sometimes. -- Backtrace: Application: Monitor do sistema (kdeinit5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb8240fa780 (LWP 12452))] Thread 5 (Thread 0x7fb7e3fff700 (LWP 12474)): #0 0x7fb8221d074d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb81e7c538c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb81e7c5712 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb80b6e79d6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fb81e7ebbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb8206376ba in start_thread (arg=0x7fb7e3fff700) at pthread_create.c:333 #6 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fb7ebc92700 (LWP 12473)): #0 0x7fb81e809a90 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb81e7c52ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb81e7c549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb81e7c54d9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb81e7ebbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb8206376ba in start_thread (arg=0x7fb7ebc92700) at pthread_create.c:333 #6 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fb7fa960700 (LWP 12455)): #0 0x7fb8221cc27d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb81e370073 in ?? () from /usr/lib/nvidia-390/tls/libnvidia-tls.so.390.48 #2 0x7fb81e8086f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb81e7c4e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb81e7c5330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb81e7c549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fb8227815cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb82272864a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb822548554 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fb81877a2c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7fb82254d6eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fb8206376ba in start_thread (arg=0x7fb7fa960700) at pthread_create.c:333 #12 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fb8093f8700 (LWP 12453)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb82196e91c in std::condition_variable::wait(std::unique_lock&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #2 0x7fb80fbb77ae in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fb80fbb78c9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #4 0x7fb821973c80 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #5 0x7fb8206376ba in start_thread (arg=0x7fb8093f8700) at pthread_create.c:333 #6 0x7fb8221dc41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fb8240fa780 (LWP 12452)): [KCrash Handler] #6 0x7fb82210a428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7fb82210c02a in __GI_abort () at abort.c:89 #8 0x7fb82214c7ea in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fb822265ed8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #9 0x7fb82215537a in malloc_printerr (ar_ptr=, ptr=, str=0x7fb822265fe8 "double free or corruption (out)", action=3) at malloc.c:5006 #10 _int_free (av=, p=, have_lock=0) at malloc.c:3867 #11 0x7fb82215953c in __GI___libc_free (mem=) at malloc.c:2968 #12 0x7fb822754454 in QObjectPrivate::Connection::~Connection() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fb82275ed1c in QObject::~QObject() () from /usr/lib/
[krusader] [Bug 393766] New: "Open terminal here" action opens shell in home directory
https://bugs.kde.org/show_bug.cgi?id=393766 Bug ID: 393766 Summary: "Open terminal here" action opens shell in home directory Product: krusader Version: 2.6.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: m...@fork.pl Reporter: k3rn...@gmail.com Target Milestone: --- The 'open terminal here' functionality, which I trigger from a keyboard shortcut, opens a terminal in the home directory (just like 'open terminal' does) instead of in the currently-browsed directory -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 393735] Opening an image from a network folder via Dolphin with a large recent files list is slow
https://bugs.kde.org/show_bug.cgi?id=393735 Henrik Fehlauer changed: What|Removed |Added Summary|When opening an image file, |Opening an image from a |the complete contents of|network folder via Dolphin |the file's directory are|with a large recent files |also opened |list is slow --- Comment #9 from Henrik Fehlauer --- Thanks for the update. Seems we have multiple issues in one bug here: 1. If you have an Autofs mounted NFS share, the Places panel will try to access it, which takes a while due to how the automounting works. I'm lost with the recent bugs reorganization and don't know anymore which bug is _really_ about this exact problem, but starting to browse from Bug 335498 should get you started in the maze of duplicates. 2. Gwenview trying to access images from your history and thus making opening a single image from Dolphin slow. Perhaps those checks can be avoided or done in the background, to prioritize opening of the image itself. Let's make this bug about the problem #2. Please don't forget to also tell us from where you were opening the image, i.e. from NFS or SMB, and whether SMB is also automounted or accessed via the smb:// kioslave. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 393760] System monitor crashes randomly when closed
https://bugs.kde.org/show_bug.cgi?id=393760 Christoph Feck changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- Reported as bug 393759. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 393761] System monitor crashes randomly when closed
https://bugs.kde.org/show_bug.cgi?id=393761 Christoph Feck changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- Reported as bug 393759. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 393763] System monitor crashes randomly when closed
https://bugs.kde.org/show_bug.cgi?id=393763 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Christoph Feck --- Reported as bug 393759. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 393762] System monitor crashes randomly when closed
https://bugs.kde.org/show_bug.cgi?id=393762 Christoph Feck changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- Reported as bug 393759. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 393764] System monitor crashes randomly when closed
https://bugs.kde.org/show_bug.cgi?id=393764 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Christoph Feck --- Reported as bug 393759. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 393765] System monitor crashes randomly when closed
https://bugs.kde.org/show_bug.cgi?id=393765 Christoph Feck changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- Reported as bug 393759. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 393759] System monitor crashes randomly when closed
https://bugs.kde.org/show_bug.cgi?id=393759 Christoph Feck changed: What|Removed |Added Product|kde |ksysguard Version|unspecified |5.12.4 Component|general |general Assignee|unassigned-b...@kde.org |ksysguard-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 393767] New: Sorting flatpaks by release date does not work. Discover uses alphabetical order instead.
https://bugs.kde.org/show_bug.cgi?id=393767 Bug ID: 393767 Summary: Sorting flatpaks by release date does not work. Discover uses alphabetical order instead. Product: Discover Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Flatpak Backend Assignee: aleix...@kde.org Reporter: bugsefor...@gmx.com CC: jgrul...@redhat.com Target Milestone: --- On neon dev unstable open discover click "settings" in sidebar click in some flatpak repository (flathub or kdeapps, for example) to show its packages click dropdown on top and set the apps sorting to release date Result: apps are sorted in alphabetical order -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 393688] DND Attachments from one existing message to new message
https://bugs.kde.org/show_bug.cgi?id=393688 Laurent Montel changed: What|Removed |Added Version Fixed In||18.04.1 Latest Commit||https://commits.kde.org/mes ||sagelib/21d0b28183d8aa2e3a4 ||f0017c5c453347a3a50da Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Laurent Montel --- Git commit 21d0b28183d8aa2e3a4f0017c5c453347a3a50da by Laurent Montel. Committed on 02/05/2018 at 11:52. Pushed by mlaurent into branch 'Applications/18.04'. Fix Bug 393688 - DND Attachments from one existing message to new message FIXED-IN: 18.04.1 M +1-1messageviewer/src/viewer/viewer_p.cpp https://commits.kde.org/messagelib/21d0b28183d8aa2e3a4f0017c5c453347a3a50da -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361852] pressing "Esc" doesn't clear the earlier transform position (continuous transform)
https://bugs.kde.org/show_bug.cgi?id=361852 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/ef43e85ef2815354e64c8358 |ta/c4740297fdf6ef5e5f8ea670 |3b4b734455d9d605|098d69b9aaf1cd0d --- Comment #11 from Boudewijn Rempt --- Git commit c4740297fdf6ef5e5f8ea670098d69b9aaf1cd0d by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Implement double Esc key press shortcut for canceling continued transform mode Now if you start a continued transform mode in the transform tool, you have two options: 1) Press Esc key once to reset the transformation to non-transformed state 2) Press Esc key twice to cancel changing the continued transformation CC:kimages...@kde.org (cherry picked from commit 59ffe8bf10c618e35632b466a34578fee79ca78b) M +5-1plugins/tools/tool_transform2/kis_tool_transform.cc https://commits.kde.org/krita/c4740297fdf6ef5e5f8ea670098d69b9aaf1cd0d -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364162] Copy Paste to Frame
https://bugs.kde.org/show_bug.cgi?id=364162 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/eca15c47e552827ec9440ac8 |ta/a4df42f88c2e9dd01e831102 |bcc8140e4c38b601|70ba5bfdf939d408 --- Comment #6 from Boudewijn Rempt --- Git commit a4df42f88c2e9dd01e83110270ba5bfdf939d408 by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix copy-pasting pixel data from animated layers Now when you copy-paste animated frame data, it is pasted into exactly the same time range position. It means that if you later merge down this data back to the original layer, you will not get a data loss. The data will be merged exactly into the position where it has been taken from. CC:kimages...@kde.org (cherry picked from commit 39ec1d47a59425969814dc840209ec2433bdd133) M +18 -2libs/ui/actions/KisPasteActionFactory.cpp M +17 -3libs/ui/actions/kis_selection_action_factories.cpp M +30 -3libs/ui/kis_clipboard.cc M +4-1libs/ui/kis_clipboard.h https://commits.kde.org/krita/a4df42f88c2e9dd01e83110270ba5bfdf939d408 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393010] Krita 4.0.1 fails to build on armv7l
https://bugs.kde.org/show_bug.cgi?id=393010 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/d3eb595b444d5b1981894044 |ta/b832b5f508c6f2378e47732f |48e93121d7796d17|7615bd13fa41a48d --- Comment #9 from Boudewijn Rempt --- Git commit b832b5f508c6f2378e47732f7615bd13fa41a48d by Boudewijn Rempt. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix build on ARM (partly) (cherry picked from commit 39e28e703aa8144c403c1ee53afc47c0121908c1) (cherry picked from commit 55e1d8deaf98721ed3fdaf72e4a6f942ea5b93a7) M +1-1CMakeLists.txt https://commits.kde.org/krita/b832b5f508c6f2378e47732f7615bd13fa41a48d -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393431] Some bugs found by PVS-Studio
https://bugs.kde.org/show_bug.cgi?id=393431 --- Comment #28 from Boudewijn Rempt --- Git commit c4a9acd24f1db7186548bab168b0abdc20d125b5 by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: misprint in KisPressureSizeOption::lodLimitations() (cherry picked from commit 9790c311ed0da5af6077ead5b4fb1165011aee2d) (cherry picked from commit 634b2f9da8b4e6eae69a84708392f5cba8a3a508) M +2-1plugins/paintops/libpaintop/kis_pressure_size_option.cpp https://commits.kde.org/krita/c4a9acd24f1db7186548bab168b0abdc20d125b5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393431] Some bugs found by PVS-Studio
https://bugs.kde.org/show_bug.cgi?id=393431 --- Comment #25 from Boudewijn Rempt --- Git commit 092c2fbeb5336278a3246c9caf0362b3665220bf by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: naver happening 'if' condition (cherry picked from commit df92768617243f78c08c681e0bb08c66db9de1f8) (cherry picked from commit 3037e8d4a5fa76cec32400f67ba19f403d9112d3) M +1-2plugins/tools/svgtexttool/SvgTextEditor.cpp https://commits.kde.org/krita/092c2fbeb5336278a3246c9caf0362b3665220bf --- Comment #26 from Boudewijn Rempt --- Git commit 4ba5ca4eeaab9c44856790ae257b923a9ff70cfd by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: loop is actually infinite Well, it seems like the loop should be infinite by design, though I'm not very sure :) Since this code is abandoned and not used in Krita atm, I just added a todo. (cherry picked from commit f912a10eda97ef6a6564db4db1991a3efbf879f4) (cherry picked from commit c2d5a2a0ed4a5302205635dd6eca15fde4f3c2db) M +4-3libs/flake/KoConnectionShape.cpp https://commits.kde.org/krita/4ba5ca4eeaab9c44856790ae257b923a9ff70cfd -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393431] Some bugs found by PVS-Studio
https://bugs.kde.org/show_bug.cgi?id=393431 --- Comment #26 from Boudewijn Rempt --- Git commit 4ba5ca4eeaab9c44856790ae257b923a9ff70cfd by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: loop is actually infinite Well, it seems like the loop should be infinite by design, though I'm not very sure :) Since this code is abandoned and not used in Krita atm, I just added a todo. (cherry picked from commit f912a10eda97ef6a6564db4db1991a3efbf879f4) (cherry picked from commit c2d5a2a0ed4a5302205635dd6eca15fde4f3c2db) M +4-3libs/flake/KoConnectionShape.cpp https://commits.kde.org/krita/4ba5ca4eeaab9c44856790ae257b923a9ff70cfd --- Comment #27 from Boudewijn Rempt --- Git commit e59b94ac787e3b303d26bfd88a4d92e2b0199740 by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: initializing non-POD struct with memset QVector is not a POD, so we shouldn't try to initialize it with bruteforce memset. (cherry picked from commit 1e67dff0b6b14abbbdbf417fb69f914c8d5bd213) (cherry picked from commit 0188944135a4b982b51902c818469b088c9b0c7f) M +10 -10 libs/psd/psd.h M +0-1libs/psd/psd_pattern.cpp https://commits.kde.org/krita/e59b94ac787e3b303d26bfd88a4d92e2b0199740 --- Comment #28 from Boudewijn Rempt --- Git commit c4a9acd24f1db7186548bab168b0abdc20d125b5 by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: misprint in KisPressureSizeOption::lodLimitations() (cherry picked from commit 9790c311ed0da5af6077ead5b4fb1165011aee2d) (cherry picked from commit 634b2f9da8b4e6eae69a84708392f5cba8a3a508) M +2-1plugins/paintops/libpaintop/kis_pressure_size_option.cpp https://commits.kde.org/krita/c4a9acd24f1db7186548bab168b0abdc20d125b5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393217] crash when resizing tool options applet w/ select shapes tool+vector layer
https://bugs.kde.org/show_bug.cgi?id=393217 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/19f6e2ab340570562a169599 |ta/29df640252a5efb132969437 |bbba5c59296807ac|9980fad39d5872fd --- Comment #7 from Boudewijn Rempt --- Git commit 29df640252a5efb1329694379980fad39d5872fd by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix crash when resizing the Tool Options for the shape selection tool KoFillConfigWidget should update visibility of the widgets explicitly in KoFillConfigWidget::activate() to ensure the widgets are really hidden (since recently shapeChanged() can skip the update if the mode hasn't changed) (cherry picked from commit 1ce1fc9276ca9dd95eedf6c6fe4a4888d6f63a4c) M +11 -2libs/ui/kis_stopgradient_editor.cpp M +3-0libs/ui/widgets/KoFillConfigWidget.cpp M +4-1libs/ui/widgets/kis_stopgradient_slider_widget.cpp https://commits.kde.org/krita/29df640252a5efb1329694379980fad39d5872fd -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385050] JJ: workflow improvement: create a group when several layers are selected and that user clicks on "add layer"
https://bugs.kde.org/show_bug.cgi?id=385050 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/c7ddbf1a0145d1c9a1fea017 |ta/3cdbd97f494bca91e80dea65 |78df709c508f7c80|fd3ef4f99dc4f38d --- Comment #9 from Boudewijn Rempt --- Git commit 3cdbd97f494bca91e80dea65fd3ef4f99dc4f38d by Boudewijn Rempt, on behalf of Seoras Macdonald. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Change the behaviour of the add layer button Summary: In the layers docker, if more than 1 layer is selected, then the add layer button now creates a quick group for the selected layers. Reviewers: #krita, rempt Reviewed By: #krita, rempt Subscribers: alvinhochun, woltherav Tags: #krita Differential Revision: https://phabricator.kde.org/D11507 (cherry picked from commit 77d75e3d811add37b909683d61ad8e779f8524e1) M +16 -1plugins/dockers/defaultdockers/kis_layer_box.cpp M +2-0plugins/dockers/defaultdockers/kis_layer_box.h https://commits.kde.org/krita/3cdbd97f494bca91e80dea65fd3ef4f99dc4f38d -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393431] Some bugs found by PVS-Studio
https://bugs.kde.org/show_bug.cgi?id=393431 --- Comment #28 from Boudewijn Rempt --- Git commit c4a9acd24f1db7186548bab168b0abdc20d125b5 by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: misprint in KisPressureSizeOption::lodLimitations() (cherry picked from commit 9790c311ed0da5af6077ead5b4fb1165011aee2d) (cherry picked from commit 634b2f9da8b4e6eae69a84708392f5cba8a3a508) M +2-1plugins/paintops/libpaintop/kis_pressure_size_option.cpp https://commits.kde.org/krita/c4a9acd24f1db7186548bab168b0abdc20d125b5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393087] Vector Break at Segment / Break at Point Crash
https://bugs.kde.org/show_bug.cgi?id=393087 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/25a628eb1ae047b37045cda4 |ta/ba377491cdd4bc825de07035 |bc705dfc2b0b5731|f7ed2e0a05545c84 --- Comment #4 from Boudewijn Rempt --- Git commit ba377491cdd4bc825de07035f7ed2e0a05545c84 by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix crashes on undo/redo of vector path points operations 1) KoPathToolSelection keeps pointers to the shapes and its path points, therefore it should subscribe to the updates on the shapes and their points (using ShapeChangeListener framework). 2) The patch also fixes a lot of bugs in "Join by segment" and "Merge points", which should behave correctly now. 3) The patch also partially implements "keep path point selection" idea, which selects newly created point after each operation. The stuff is achieved using KoPathShape::PointSelectionChangeListener listener. Related: bug 393209 (cherry picked from commit f919e7f2dbed028e8fdae89b58ed6f5af26760db) M +1-0libs/flake/CMakeLists.txt M +70 -2libs/flake/KoPathShape.cpp M +12 -0libs/flake/KoPathShape.h M +2-0libs/flake/KoPathShape_p.h M +5-11 libs/flake/commands/KoMultiPathPointMergeCommand.cpp M +9-0libs/flake/commands/KoPathBreakAtPointCommand.cpp A +70 -0libs/flake/commands/KoPathMergeUtils.cpp [License: GPL (v2+)] A +37 -0libs/flake/commands/KoPathMergeUtils.h [License: GPL (v2+)] M +13 -1libs/flake/commands/KoPathPointInsertCommand.cpp M +98 -120 libs/flake/commands/KoPathPointMergeCommand.cpp M +11 -0libs/flake/commands/KoPathPointRemoveCommand.cpp M +63 -39 libs/flake/commands/KoSubpathJoinCommand.cpp M +10 -3libs/flake/commands/KoSubpathJoinCommand.h M +15 -2libs/flake/tools/KoPathTool.cpp M +3-0libs/flake/tools/KoPathTool.h M +62 -0libs/flake/tools/KoPathToolSelection.cpp M +6-1libs/flake/tools/KoPathToolSelection.h M +4-0plugins/flake/pathshapes/ellipse/EllipseShape.cpp M +2-0plugins/flake/pathshapes/enhancedpath/EnhancedPathShape.cpp M +4-0plugins/flake/pathshapes/rectangle/RectangleShape.cpp M +2-0plugins/flake/pathshapes/spiral/SpiralShape.cpp M +2-0plugins/flake/pathshapes/star/StarShape.cpp https://commits.kde.org/krita/ba377491cdd4bc825de07035f7ed2e0a05545c84 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393431] Some bugs found by PVS-Studio
https://bugs.kde.org/show_bug.cgi?id=393431 --- Comment #30 from Boudewijn Rempt --- Git commit 3c97d1633c8f0578d6df105d7b8df71378826d0f by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: reordered function arguments Just a misprint or copy-paste (cherry picked from commit 6ed8fb329f8326444d983f5bb79c08bc982ab428) (cherry picked from commit 42b6c6b50a87d9ff586bdaf5c82d44a97d266805) M +1-1benchmarks/kis_gradient_benchmark.cpp M +1-1benchmarks/kis_random_iterator_benchmark.cpp M +1-1 plugins/flake/textshape/kotext/opendocument/KoTextSharedLoadingData.cpp https://commits.kde.org/krita/3c97d1633c8f0578d6df105d7b8df71378826d0f -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391696] Right click with wacom pen auto selects whatever I hover over on the popup palette
https://bugs.kde.org/show_bug.cgi?id=391696 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/c7e6c0184f951b4b4165a4bb |ta/93e1e39386eae6b23b390ab7 |b7e99107a9e36cb0|c3034c83f864a7ec --- Comment #12 from Boudewijn Rempt --- Git commit 93e1e39386eae6b23b390ab7c3034c83f864a7ec by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Disable right-clicking on popup palette With this patch it is not possible to select a palette item using the right-click of the stylus. All the distinct actions should be confirmed with the left button. Right-click on any part of the canvas just closes the entire palette. Related: bug 378484 (cherry picked from commit 20c9efffb70cf2757595fee8d7c56a5fe59d5664) M +24 -1libs/ui/kis_popup_palette.cpp M +5-0libs/ui/kis_popup_palette.h https://commits.kde.org/krita/93e1e39386eae6b23b390ab7c3034c83f864a7ec -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393431] Some bugs found by PVS-Studio
https://bugs.kde.org/show_bug.cgi?id=393431 --- Comment #25 from Boudewijn Rempt --- Git commit 092c2fbeb5336278a3246c9caf0362b3665220bf by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: naver happening 'if' condition (cherry picked from commit df92768617243f78c08c681e0bb08c66db9de1f8) (cherry picked from commit 3037e8d4a5fa76cec32400f67ba19f403d9112d3) M +1-2plugins/tools/svgtexttool/SvgTextEditor.cpp https://commits.kde.org/krita/092c2fbeb5336278a3246c9caf0362b3665220bf --- Comment #26 from Boudewijn Rempt --- Git commit 4ba5ca4eeaab9c44856790ae257b923a9ff70cfd by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: loop is actually infinite Well, it seems like the loop should be infinite by design, though I'm not very sure :) Since this code is abandoned and not used in Krita atm, I just added a todo. (cherry picked from commit f912a10eda97ef6a6564db4db1991a3efbf879f4) (cherry picked from commit c2d5a2a0ed4a5302205635dd6eca15fde4f3c2db) M +4-3libs/flake/KoConnectionShape.cpp https://commits.kde.org/krita/4ba5ca4eeaab9c44856790ae257b923a9ff70cfd --- Comment #27 from Boudewijn Rempt --- Git commit e59b94ac787e3b303d26bfd88a4d92e2b0199740 by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: initializing non-POD struct with memset QVector is not a POD, so we shouldn't try to initialize it with bruteforce memset. (cherry picked from commit 1e67dff0b6b14abbbdbf417fb69f914c8d5bd213) (cherry picked from commit 0188944135a4b982b51902c818469b088c9b0c7f) M +10 -10 libs/psd/psd.h M +0-1libs/psd/psd_pattern.cpp https://commits.kde.org/krita/e59b94ac787e3b303d26bfd88a4d92e2b0199740 --- Comment #28 from Boudewijn Rempt --- Git commit c4a9acd24f1db7186548bab168b0abdc20d125b5 by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: misprint in KisPressureSizeOption::lodLimitations() (cherry picked from commit 9790c311ed0da5af6077ead5b4fb1165011aee2d) (cherry picked from commit 634b2f9da8b4e6eae69a84708392f5cba8a3a508) M +2-1plugins/paintops/libpaintop/kis_pressure_size_option.cpp https://commits.kde.org/krita/c4a9acd24f1db7186548bab168b0abdc20d125b5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393431] Some bugs found by PVS-Studio
https://bugs.kde.org/show_bug.cgi?id=393431 --- Comment #31 from Boudewijn Rempt --- Git commit ea406629fcbfddadf560bc5ae1f5b51825d929be by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: memory leaks in unittests V773 The function was exited without releasing the pointer. A memory leak is possible. (cherry picked from commit 3ec75b535e65a286ef8f09369121c4cecfb3e607) M +5-5libs/brush/tests/kis_gbr_brush_test.cpp M +15 -28 libs/brush/tests/kis_imagepipe_brush_test.cpp M +2-5libs/image/tests/kis_clone_layer_test.cpp M +21 -30 libs/image/tests/kis_iterator_test.cpp M +21 -32 libs/image/tests/kis_iterators_ng_test.cpp M +3-4libs/image/tests/kis_simple_update_queue_test.cpp M +1-2libs/widgets/tests/zoomhandler_test.cpp M +1-2 plugins/paintops/libpaintop/tests/kis_embedded_pattern_manager_test.cpp https://commits.kde.org/krita/ea406629fcbfddadf560bc5ae1f5b51825d929be -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393431] Some bugs found by PVS-Studio
https://bugs.kde.org/show_bug.cgi?id=393431 --- Comment #25 from Boudewijn Rempt --- Git commit 092c2fbeb5336278a3246c9caf0362b3665220bf by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: naver happening 'if' condition (cherry picked from commit df92768617243f78c08c681e0bb08c66db9de1f8) (cherry picked from commit 3037e8d4a5fa76cec32400f67ba19f403d9112d3) M +1-2plugins/tools/svgtexttool/SvgTextEditor.cpp https://commits.kde.org/krita/092c2fbeb5336278a3246c9caf0362b3665220bf -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393431] Some bugs found by PVS-Studio
https://bugs.kde.org/show_bug.cgi?id=393431 --- Comment #25 from Boudewijn Rempt --- Git commit 092c2fbeb5336278a3246c9caf0362b3665220bf by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: naver happening 'if' condition (cherry picked from commit df92768617243f78c08c681e0bb08c66db9de1f8) (cherry picked from commit 3037e8d4a5fa76cec32400f67ba19f403d9112d3) M +1-2plugins/tools/svgtexttool/SvgTextEditor.cpp https://commits.kde.org/krita/092c2fbeb5336278a3246c9caf0362b3665220bf --- Comment #26 from Boudewijn Rempt --- Git commit 4ba5ca4eeaab9c44856790ae257b923a9ff70cfd by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: loop is actually infinite Well, it seems like the loop should be infinite by design, though I'm not very sure :) Since this code is abandoned and not used in Krita atm, I just added a todo. (cherry picked from commit f912a10eda97ef6a6564db4db1991a3efbf879f4) (cherry picked from commit c2d5a2a0ed4a5302205635dd6eca15fde4f3c2db) M +4-3libs/flake/KoConnectionShape.cpp https://commits.kde.org/krita/4ba5ca4eeaab9c44856790ae257b923a9ff70cfd --- Comment #27 from Boudewijn Rempt --- Git commit e59b94ac787e3b303d26bfd88a4d92e2b0199740 by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: initializing non-POD struct with memset QVector is not a POD, so we shouldn't try to initialize it with bruteforce memset. (cherry picked from commit 1e67dff0b6b14abbbdbf417fb69f914c8d5bd213) (cherry picked from commit 0188944135a4b982b51902c818469b088c9b0c7f) M +10 -10 libs/psd/psd.h M +0-1libs/psd/psd_pattern.cpp https://commits.kde.org/krita/e59b94ac787e3b303d26bfd88a4d92e2b0199740 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393431] Some bugs found by PVS-Studio
https://bugs.kde.org/show_bug.cgi?id=393431 --- Comment #29 from Boudewijn Rempt --- Git commit 41a1b4b9670450bc404512861508eb38b158f8ce by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: the loop iterates only once I don't know why it happened so, but it seems it is just a result of the fork of KDE's code (cherry picked from commit 2102af05a2c1b05b6ca9e67f9209c7e21502c600) (cherry picked from commit 26eef9065fa82ef2be34fb9c0a95062508aedf41) M +2-0libs/widgetutils/config/khelpclient.cpp https://commits.kde.org/krita/41a1b4b9670450bc404512861508eb38b158f8ce -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393431] Some bugs found by PVS-Studio
https://bugs.kde.org/show_bug.cgi?id=393431 --- Comment #35 from Boudewijn Rempt --- Git commit 90b42ce4bd465c67b7c13d65f6a3dd44b8c3ed6a by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: html correctness in about dialog (cherry picked from commit 2993d536bce0e0dffe7865f21c923e6a6fdb) (cherry picked from commit d85c28fe7be833f7bf9d2f332a51e5f31862cc31) M +1-1libs/ui/dialogs/kis_about_application.cpp https://commits.kde.org/krita/90b42ce4bd465c67b7c13d65f6a3dd44b8c3ed6a -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392526] Isometric grid has several drawing issues(with openGL disabled)
https://bugs.kde.org/show_bug.cgi?id=392526 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/871dd8aa89db17f1d6f0a528 |ta/8fc6453a1f6b0dee4f824040 |7130db435592f66f|732377300dc020f8 --- Comment #5 from Boudewijn Rempt --- Git commit 8fc6453a1f6b0dee4f824040732377300dc020f8 by Boudewijn Rempt, on behalf of Scott Petrovic. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. (cherry picked from commit 9cb343e72130a4f27d14eaa38a97b068f972d299) M +36 -5plugins/dockers/griddocker/grid_config_widget.cpp M +5-0plugins/dockers/griddocker/grid_config_widget.h M +8-0plugins/dockers/griddocker/griddocker_dock.cpp https://commits.kde.org/krita/8fc6453a1f6b0dee4f824040732377300dc020f8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393431] Some bugs found by PVS-Studio
https://bugs.kde.org/show_bug.cgi?id=393431 --- Comment #34 from Boudewijn Rempt --- Git commit e537b5f6a8aeb4bb9c6014a74c3388b0e9722a7b by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: uninitialized variables used in the loop (cherry picked from commit 9f76caa714c34891b77a277520c78188be10c56d) (cherry picked from commit 266785dfe95c103cc0ba1cceb3d9dc00d3afdb3d) M +2-2libs/ui/kis_painting_assistant.cc https://commits.kde.org/krita/e537b5f6a8aeb4bb9c6014a74c3388b0e9722a7b -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393431] Some bugs found by PVS-Studio
https://bugs.kde.org/show_bug.cgi?id=393431 --- Comment #32 from Boudewijn Rempt --- Git commit 1dba3bba6960524e1c84677636f8eef459819814 by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS Studio warning: avoid non-used return value warning in benchmarks V530 The return value of function 'atan2' is required to be utilized. V530 The return value of function 'drand48' is required to be utilized. (cherry picked from commit 6585c96eff6169884d07f3ef36de0d20480a57df) M +2-1benchmarks/kis_fast_math_benchmark.cpp M +2-1benchmarks/kis_stroke_benchmark.cpp https://commits.kde.org/krita/1dba3bba6960524e1c84677636f8eef459819814 --- Comment #33 from Boudewijn Rempt --- Git commit d8f702a102f9acb1690bed6f908b7d1cf637063d by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: parseTagName() should actually return some value (cherry picked from commit 7bc329344257c71716f95c4dbd85077566a408c0) (cherry picked from commit fa1b241513542375444539eefb5647dc886f7abe) M +11 -11 libs/ui/kisexiv2/kis_xmp_io.cpp https://commits.kde.org/krita/d8f702a102f9acb1690bed6f908b7d1cf637063d -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393431] Some bugs found by PVS-Studio
https://bugs.kde.org/show_bug.cgi?id=393431 --- Comment #32 from Boudewijn Rempt --- Git commit 1dba3bba6960524e1c84677636f8eef459819814 by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS Studio warning: avoid non-used return value warning in benchmarks V530 The return value of function 'atan2' is required to be utilized. V530 The return value of function 'drand48' is required to be utilized. (cherry picked from commit 6585c96eff6169884d07f3ef36de0d20480a57df) M +2-1benchmarks/kis_fast_math_benchmark.cpp M +2-1benchmarks/kis_stroke_benchmark.cpp https://commits.kde.org/krita/1dba3bba6960524e1c84677636f8eef459819814 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393431] Some bugs found by PVS-Studio
https://bugs.kde.org/show_bug.cgi?id=393431 --- Comment #33 from Boudewijn Rempt --- Git commit d8f702a102f9acb1690bed6f908b7d1cf637063d by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: parseTagName() should actually return some value (cherry picked from commit 7bc329344257c71716f95c4dbd85077566a408c0) (cherry picked from commit fa1b241513542375444539eefb5647dc886f7abe) M +11 -11 libs/ui/kisexiv2/kis_xmp_io.cpp https://commits.kde.org/krita/d8f702a102f9acb1690bed6f908b7d1cf637063d -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393431] Some bugs found by PVS-Studio
https://bugs.kde.org/show_bug.cgi?id=393431 --- Comment #36 from Boudewijn Rempt --- Git commit 9c16ca110fc9ee6abcd45dbed004ec3a24aba8dd by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: uninitialized variables in KisMinHeap Calling c-tors from other c-tors appeared in C++ much later than this code has been written :) (cherry picked from commit 368bd56bfd9341627197180ad277758d2d4ba257) (cherry picked from commit 7b77cbad1c1e0ed8d47fb81c8b5449837e9877a1) M +11 -9libs/ui/kis_min_heap.h https://commits.kde.org/krita/9c16ca110fc9ee6abcd45dbed004ec3a24aba8dd -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393431] Some bugs found by PVS-Studio
https://bugs.kde.org/show_bug.cgi?id=393431 --- Comment #37 from Boudewijn Rempt --- Git commit 60d253b834694eb585421200c867cc80f895b190 by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: for-each loop should accept a reference to actually do something (cherry picked from commit 03d026c9179f24acc7c3f3f669bf75480051b3ad) (cherry picked from commit 18834a3ba524b8526a63e0b98877976c47840e7a) M +1-1libs/global/kis_algebra_2d.cpp https://commits.kde.org/krita/60d253b834694eb585421200c867cc80f895b190 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384687] Clicking outside the red frame in the overview docker should pan the image.
https://bugs.kde.org/show_bug.cgi?id=384687 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/4381a51389f6fa9c9a08689b |ta/a45a0638dba4478389783ef3 |5ee5b2583f821a1f|242a9be5c8ebc282 --- Comment #11 from Boudewijn Rempt --- Git commit a45a0638dba4478389783ef3242a9be5c8ebc282 by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Clicking outside preview box moves view to that point Summary: Clicking outside of the preview box in the overview docker now moves the view of the canvas to be centered at that point. Patch by Seoras Macdonald Reviewers: #krita, dkazakov Reviewed By: #krita, dkazakov Subscribers: dkazakov, emmetoneill Differential Revision: https://phabricator.kde.org/D12178 (cherry picked from commit 0eb11f4eaf8439a675fa41a08d62fc5c75fbba8c) M +14 -3plugins/dockers/overview/overviewwidget.cc https://commits.kde.org/krita/a45a0638dba4478389783ef3242a9be5c8ebc282 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382315] Duplicating Global Selection mask crash
https://bugs.kde.org/show_bug.cgi?id=382315 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/e58c344bf34661e499294cc1 |ta/6a98d072fbef812c54655dfb |79a457192232a2c1|b1d8ffd31923307f --- Comment #11 from Boudewijn Rempt --- Git commit 6a98d072fbef812c54655dfbb1d8ffd31923307f by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix a crash when duplicating active global selection masks The problem was in the fact that KisGroupLayer::allowAsChild() forbade adding the second active mask to the same layer, letting the code silently continue without knowing that the mask was not created. In this patch we manually deactivate all the active masks before duplication process. (cherry picked from commit 3ef241fbe5eaec159300dc28ce6e5b89fb7bffa6) M +4-4libs/image/kis_node.cpp M +37 -2libs/ui/kis_node_juggler_compressed.cpp https://commits.kde.org/krita/6a98d072fbef812c54655dfbb1d8ffd31923307f -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393431] Some bugs found by PVS-Studio
https://bugs.kde.org/show_bug.cgi?id=393431 --- Comment #38 from Boudewijn Rempt --- Git commit efbcd85cc932ee5f8bd7af141cf265e343583d7e by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: possible memory leaks in production code Most of the leaks are hardly reproducible in normal circumstances. But the one in PNG converter is huge. PNG converter also had an invalid null pointer access, which didn't crash Krita only by a happy coincidence. (cherry picked from commit 6960317945ed3d44cc5d5ad5c6299d206c52aac6) (cherry picked from commit 2496b1264b1dd3fe5d2bf3a6e4129053e3672367) M +5-7libs/flake/svg/SvgParser.cpp M +3-3libs/ui/input/kis_input_manager_p.cpp M +46 -30 libs/ui/kis_png_converter.cpp M +5-1plugins/flake/textshape/TextTool.cpp M +8-7plugins/flake/textshape/kotext/BibliographyGenerator.cpp M +1-0plugins/flake/textshape/kotext/KoAnchorTextRange.cpp M +1-0plugins/flake/textshape/kotext/OdfTextTrackStyles.cpp M +6-8plugins/flake/textshape/kotext/opendocument/KoTextWriter.cpp M +18 -11 plugins/flake/textshape/kotext/opendocument/KoTextWriter_p.cpp M +4-3plugins/flake/textshape/kotext/opendocument/KoTextWriter_p.h M +3-3plugins/impex/ppm/kis_ppm_import.cpp M +3-6plugins/impex/psd/psd_layer_section.cpp M +2-5 plugins/tools/karbonplugins/tools/filterEffectTool/FilterEffectResource.cpp https://commits.kde.org/krita/efbcd85cc932ee5f8bd7af141cf265e343583d7e -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393431] Some bugs found by PVS-Studio
https://bugs.kde.org/show_bug.cgi?id=393431 --- Comment #38 from Boudewijn Rempt --- Git commit efbcd85cc932ee5f8bd7af141cf265e343583d7e by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: possible memory leaks in production code Most of the leaks are hardly reproducible in normal circumstances. But the one in PNG converter is huge. PNG converter also had an invalid null pointer access, which didn't crash Krita only by a happy coincidence. (cherry picked from commit 6960317945ed3d44cc5d5ad5c6299d206c52aac6) (cherry picked from commit 2496b1264b1dd3fe5d2bf3a6e4129053e3672367) M +5-7libs/flake/svg/SvgParser.cpp M +3-3libs/ui/input/kis_input_manager_p.cpp M +46 -30 libs/ui/kis_png_converter.cpp M +5-1plugins/flake/textshape/TextTool.cpp M +8-7plugins/flake/textshape/kotext/BibliographyGenerator.cpp M +1-0plugins/flake/textshape/kotext/KoAnchorTextRange.cpp M +1-0plugins/flake/textshape/kotext/OdfTextTrackStyles.cpp M +6-8plugins/flake/textshape/kotext/opendocument/KoTextWriter.cpp M +18 -11 plugins/flake/textshape/kotext/opendocument/KoTextWriter_p.cpp M +4-3plugins/flake/textshape/kotext/opendocument/KoTextWriter_p.h M +3-3plugins/impex/ppm/kis_ppm_import.cpp M +3-6plugins/impex/psd/psd_layer_section.cpp M +2-5 plugins/tools/karbonplugins/tools/filterEffectTool/FilterEffectResource.cpp https://commits.kde.org/krita/efbcd85cc932ee5f8bd7af141cf265e343583d7e --- Comment #39 from Boudewijn Rempt --- Git commit 4a5c56c34899cc98cdf4fd8a86266d7816bce3fe by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: brush spacing should be saved as double, not bool (cherry picked from commit 45cd5e436c54b1558856509f0c626d652fef9756) (cherry picked from commit 2b8f9f6daf2f125b98477c93e2ecbff925a6e6e7) M +1-1plugins/impex/brush/kis_brush_export.cpp https://commits.kde.org/krita/4a5c56c34899cc98cdf4fd8a86266d7816bce3fe -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 378484] Popup Palette usability issues of unwanted right-click selecting & holding-releasing right-click actions
https://bugs.kde.org/show_bug.cgi?id=378484 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/c7e6c0184f951b4b4165a4bb |ta/93e1e39386eae6b23b390ab7 |b7e99107a9e36cb0|c3034c83f864a7ec --- Comment #5 from Boudewijn Rempt --- Git commit 93e1e39386eae6b23b390ab7c3034c83f864a7ec by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Disable right-clicking on popup palette With this patch it is not possible to select a palette item using the right-click of the stylus. All the distinct actions should be confirmed with the left button. Right-click on any part of the canvas just closes the entire palette. Related: bug 391696 (cherry picked from commit 20c9efffb70cf2757595fee8d7c56a5fe59d5664) M +24 -1libs/ui/kis_popup_palette.cpp M +5-0libs/ui/kis_popup_palette.h https://commits.kde.org/krita/93e1e39386eae6b23b390ab7c3034c83f864a7ec -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393431] Some bugs found by PVS-Studio
https://bugs.kde.org/show_bug.cgi?id=393431 --- Comment #39 from Boudewijn Rempt --- Git commit 4a5c56c34899cc98cdf4fd8a86266d7816bce3fe by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: brush spacing should be saved as double, not bool (cherry picked from commit 45cd5e436c54b1558856509f0c626d652fef9756) (cherry picked from commit 2b8f9f6daf2f125b98477c93e2ecbff925a6e6e7) M +1-1plugins/impex/brush/kis_brush_export.cpp https://commits.kde.org/krita/4a5c56c34899cc98cdf4fd8a86266d7816bce3fe -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393431] Some bugs found by PVS-Studio
https://bugs.kde.org/show_bug.cgi?id=393431 --- Comment #40 from Boudewijn Rempt --- Git commit efba89b8abbc938178df2eee4a83ccba899a3586 by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. Fix PVS-Studio warning: reword correct but weird code The patch shouldn't change any behavior, just make the code more logical :) (cherry picked from commit c68f1701eb341dff0e2db8334ca912ac7c0542ea) (cherry picked from commit b9431cf492e9692766bb9634b1e023c09fe50f32) M +1-1libs/flake/KoPathShape.cpp M +3-2libs/flake/KoShape.cpp M +1-2libs/flake/commands/KoShapeReorderCommand.cpp M +1-2libs/flake/svg/SvgStyleParser.cpp M +1-3libs/global/kis_debug.cpp M +1-1libs/image/kis_convolution_worker_spatial.h M +1-2libs/image/kis_paint_layer.cc M +5-5libs/image/kis_processing_applicator.cpp M +5-5libs/image/kis_properties_configuration.cc M +5-14 libs/image/kis_selection_filters.cpp M +7-2libs/image/kis_transform_worker.cc M +1-5libs/image/kis_update_scheduler.cpp M +3-1libs/image/metadata/kis_meta_data_value.h M +0-7libs/image/tests/kis_mask_generator_test.cpp M +2-0libs/image/tests/kis_meta_data_test.cpp M +0-1libs/image/tiles3/kis_tiled_data_manager.cc M +5-5libs/odf/KoOdfNumberDefinition.cpp M +1-1libs/pigment/resources/KoColorSet.cpp M +1-1libs/psd/psd_utils.cpp M +48 -50 libs/ui/actions/kis_selection_action_factories.cpp M +1-3libs/ui/tool/kis_tool_paint.cc M +1-2plugins/color/lcms2engine/LcmsEnginePlugin.cpp M +2-1 plugins/dockers/advancedcolorselector/kis_color_selector_base.cpp M +2-5plugins/dockers/animation/kis_draggable_tool_button.cpp M +3-3plugins/dockers/lut/ocio_display_filter.cpp M +2-2plugins/flake/textshape/kotext/KoInlineTextObjectManager.cpp M +4-4plugins/flake/textshape/kotext/KoTextDebug.cpp M +1-2plugins/flake/textshape/textlayout/KoTextLayoutArea.cpp M +3-2plugins/impex/csv/csv_saver.cpp M +6-9plugins/impex/kra/kra_converter.cpp M +2-3plugins/impex/libkra/kis_kra_load_visitor.cpp M +1-1plugins/impex/libkra/kis_kra_load_visitor.h M +2-2plugins/impex/libkra/kis_kra_save_visitor.cpp M +1-2plugins/impex/ora/kis_open_raster_stack_load_visitor.cpp M +2-7plugins/impex/pdf/kis_pdf_import.cpp M +0-24 plugins/impex/psd/psd_additional_layer_info_block.cpp M +1-1plugins/impex/psd/psd_header.cpp M +1-1plugins/impex/psd/psd_pixel_utils.cpp M +0-1plugins/paintops/gridbrush/kis_grid_paintop.cpp M +1-2plugins/tools/basictools/kis_tool_move.cc https://commits.kde.org/krita/efba89b8abbc938178df2eee4a83ccba899a3586 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393353] Krita Crashes When Deleting Palette
https://bugs.kde.org/show_bug.cgi?id=393353 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/2f7426b865bb9629f28f7b24 |ta/f8556aa89078a5e20840eaab |cbaac286f777f367|0fdf91b350d37e53 --- Comment #4 from Boudewijn Rempt --- Git commit f8556aa89078a5e20840eaab0fdf91b350d37e53 by Boudewijn Rempt, on behalf of Scott Petrovic. Committed on 02/05/2018 at 11:54. Pushed by rempt into branch 'krita/4.0'. (cherry picked from commit e06636540f9fdd79a80b5a9bc24e7752b29e19e4) M +8-1plugins/dockers/palettedocker/palettedocker_dock.cpp https://commits.kde.org/krita/f8556aa89078a5e20840eaab0fdf91b350d37e53 -- You are receiving this mail because: You are watching all bug changes.
