[plasmashell] [Bug 391322] Super (Meta) Key stops working
https://bugs.kde.org/show_bug.cgi?id=391322 --- Comment #11 from Rick --- um, I meant the bug must be in kwin -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391322] Super (Meta) Key stops working
https://bugs.kde.org/show_bug.cgi?id=391322 --- Comment #10 from Rick --- (In reply to Christoph Feck from comment #6) > If this happens again, please issue this dbus command: > > qdbus org.kde.plasmashell /PlasmaShell > org.kde.PlasmaShell.activateLauncherMenu > > If it shows the application launcher, the bug is in kwin. If it does not, > the bug is in plasmashell. The bug is in plasma shell. I've opened the lid of my laptop and the kicker bug was there. I ran the command in terminal and kicker started up. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389652] Interface freezes during initial scan
https://bugs.kde.org/show_bug.cgi?id=389652 caulier.gil...@gmail.com changed: What|Removed |Added Version|5.8.0 |6.1.0 -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 405726] "Vorbeugung gegen Übernahme der Aktivierung" exists twice in application-specific window settings
https://bugs.kde.org/show_bug.cgi?id=405726 Burkhard Lueck changed: What|Removed |Added CC||lu...@hube-lueck.de --- Comment #1 from Burkhard Lueck --- " stealing prevention" und "Focus protection" haben beide die gleiche Übersetzung: #. i18n: ectx: property (text), widget (QCheckBox, enable_fsplevel) #: ruleswidgetbase.ui:2151 #, kde-format msgid " stealing prevention" msgstr "Vorbeugung gegen Übernahme der A" #. i18n: ectx: property (text), widget (QCheckBox, enable_fpplevel) #: ruleswidgetbase.ui:2232 #, kde-format msgid "Focus protection" msgstr "Vorbeugung gegen Übernahme der Aktivierung" Übersetzungsvorschläge? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405725] Some elements render as transparent
https://bugs.kde.org/show_bug.cgi?id=405725 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #9 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404581] so i had just been working on a piece and i was very excited with how it was turning out but i had to leave because i wanted to buy something from a store. before i left i saved t
https://bugs.kde.org/show_bug.cgi?id=404581 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405585] Somewhere between Kate 17.12.3 and 18.12.2 code folding changed
https://bugs.kde.org/show_bug.cgi?id=405585 --- Comment #3 from prusselltechgr...@gmail.com --- Created attachment 118968 --> https://bugs.kde.org/attachment.cgi?id=118968=edit Kate 17 (leap) vs Kate 18 (tumbleweed): Image of top level code folding I'll take a look tomorrow in more detail, but it looks like it might be. It seems the end is one-off. The snippet of validated xml below focuses on highlighting blocks/code folding (see original attachment for xml and sample test file): I am running OpenSuSE Leap 15 which has Kate 17.12.3 (folding ok) and OpenSuSE Tumbleweed 20190315 which has Kate 18.12.3 (folding not ok). I am using Kate's Help > About Kate to obtain Kates version, as well as KDE Framework and QT versions as originally reported. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405585] Somewhere between Kate 17.12.3 and 18.12.2 code folding changed
https://bugs.kde.org/show_bug.cgi?id=405585 --- Comment #2 from prusselltechgr...@gmail.com --- Created attachment 118967 --> https://bugs.kde.org/attachment.cgi?id=118967=edit Kate 17 (leap) vs Kate 18 (tumbleweed): Image of block highlighting -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 405742] New: fcitx Cannot enter Chinese(fcitx 不能中文输入)
https://bugs.kde.org/show_bug.cgi?id=405742 Bug ID: 405742 Summary: fcitx Cannot enter Chinese(fcitx 不能中文输入) Product: kdevelop Version: 5.3.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: All editors Assignee: kdevelop-bugs-n...@kde.org Reporter: 1104589...@qq.com Target Milestone: --- 我的英语水平不好，翻译害怕语意错误！我只能中文提交这个bug 我当前使用的系统是debian9，桌面环境是xfce，使用的fcitx作为输入工具 fcitx的中文输入在其他app上工作非常正常！唯独kdevelop不做任何反应！ 我发现kdevelop是使用QT v5.x上的版本！Qt creater上也存在中文输入问题 但是我已经编译了最新的动态库完美解决中文输入！唯独kdevelop无动于衷！我不知道是否是Qt新版本引起kdevelop的输入异常！我试图查找官方的解决方案，但是这个bug我发现已经存在很久了，社区似乎不那么重视，今年已经是2019了还没解决问题！我似乎有点失望，我没时间参与kdevelop的产品维护，很想解决这个bug，至少对于我们中国用户体验太差了！我希望尽快修复！ 下面是为debian用户的一个这种方案: 虽然kdevelop使用fcitx不能正常的工作，但是ibus工作得很好！ 你可以安装ibus作为输入工具！但是你必须忍受ibus中文输入落后的中文输入体验！ -- You are receiving this mail because: You are watching all bug changes.
[basket] [Bug 321659] can't input any chinese character using fcitx input method
https://bugs.kde.org/show_bug.cgi?id=321659 cosoc <1104589...@qq.com> changed: What|Removed |Added CC||1104589...@qq.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405716] int-overflow in stack size Margin calculation
https://bugs.kde.org/show_bug.cgi?id=405716 Bart Van Assche changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Bart Van Assche --- A fix has been checked in on the master branch. Please verify. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405317] Cannot find file just created in home directory
https://bugs.kde.org/show_bug.cgi?id=405317 --- Comment #17 from Stefan Brüns --- There should be some reads from the inotify fd ... What do you get for $> cat /proc//fd Also try: $> killall baloo_file $> strace -einotify_add_watch baloo_file -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389652] Interface freezes during initial scan
https://bugs.kde.org/show_bug.cgi?id=389652 --- Comment #5 from IWBR --- This behavior still persists. During the initial scan, you cannot browse other albums/folders. In the command line, I see a bunch of "Database is locked." It would be great if one could browse the existing albums while the scan for new items is performed in the background. PS: in this specific case, the pictures are in a NAS, but the database is stored locally in a SSD drive. e.g.: Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 5250 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 6750 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 5500 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 7000 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 5750 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 7250 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405741] New: Converting an animated fill layer to a pixel layer removes the frames.
https://bugs.kde.org/show_bug.cgi?id=405741 Bug ID: 405741 Summary: Converting an animated fill layer to a pixel layer removes the frames. Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com Target Milestone: --- SUMMARY Animated fill layers when converted to pixel layers lose their frames. STEPS TO REPRODUCE 1. Take an animated fill layer. 2. Convert to a pixel layer 3. Observe how all frames are removed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405740] New: Animated fill layer has a frame lag in the cached animation playback.
https://bugs.kde.org/show_bug.cgi?id=405740 Bug ID: 405740 Summary: Animated fill layer has a frame lag in the cached animation playback. Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com Target Milestone: --- SUMMARY When playing back an animation with an animated fill layer, the fill layer will have a single frame 'lag' compared to the rest. STEPS TO REPRODUCE 1. Make an animation with an animated fill layer. 2. Ensure there's also pixel layers. 3. Scrub through it normally, everything is fine. 4. Press playback OBSERVED RESULT The fill layer will seem out of sync with the rest of the animation. EXPECTED RESULT Should be in sync. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405739] New: Alpha into mask on animated fill layer results in [asan crash]
https://bugs.kde.org/show_bug.cgi?id=405739 Bug ID: 405739 Summary: Alpha into mask on animated fill layer results in [asan crash] Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com Target Milestone: --- SUMMARY Apply "split alpha into mask" on animated fill layer with Address Sanitzer enabled, get this crash: = ==28661==ERROR: AddressSanitizer: heap-use-after-free on address 0x606003220d30 at pc 0x7fe94b8dca48 bp 0x7ffc96fbc1d0 sp 0x7ffc96fbc1c0 READ of size 8 at 0x606003220d30 thread T0 #0 0x7fe94b8dca47 in KisPixelSelection::KisPixelSelection(KisSharedPtr, KritaUtils::DeviceCopyMode, KisWeakSharedPtr) /home/wolthera/krita/src/libs/image/kis_pixel_selection.cpp:96 #1 0x7fe94b8fb648 in KisSelection::KisSelection(KisSharedPtr, KritaUtils::DeviceCopyMode, KisSharedPtr) /home/wolthera/krita/src/libs/image/kis_selection.cc:82 #2 0x7fe94b5561a9 in KisMask::Private::initSelectionImpl(KisSharedPtr, KisSharedPtr, KisSharedPtr) /home/wolthera/krita/src/libs/image/kis_mask.cc:181 #3 0x7fe94b07 in KisMask::initSelection(KisSharedPtr, KisSharedPtr) /home/wolthera/krita/src/libs/image/kis_mask.cc:153 #4 0x7fe94f484d30 in KisMaskManager::createMaskCommon(KisSharedPtr, KisSharedPtr, KisSharedPtr, KUndo2MagicString const&, QString const&, QString const&, bool, bool, bool) /home/wolthera/krita/src/libs/ui/kis_mask_manager.cc:172 #5 0x7fe94f4865cf in KisMaskManager::createTransparencyMask(KisSharedPtr, KisSharedPtr, bool) /home/wolthera/krita/src/libs/ui/kis_mask_manager.cc:218 #6 0x7fe94f4b01e9 in KisNodeManager::createNode(QString const&, bool, KisSharedPtr) /home/wolthera/krita/src/libs/ui/kis_node_manager.cpp:551 #7 0x7fe94f4bfe3e in KisNodeManager::slotSplitAlphaIntoMask() /home/wolthera/krita/src/libs/ui/kis_node_manager.cpp:1189 #8 0x7fe94feaa27a in KisNodeManager::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) /home/wolthera/krita/build/libs/ui/kritaui_autogen/EWIEGA46WW/moc_kis_node_manager.cpp:346 #9 0x7fe948c5fe24 in QMetaObject::activate(QObject*, int, int, void**) (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x2afe24) #10 0x7fe949a200f1 in QAction::triggered(bool) (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x1550f1) #11 0x7fe949a2270b in QAction::activate(QAction::ActionEvent) (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x15770b) #12 0x7fe949b973ab (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x2cc3ab) #13 0x7fe949b9e91a (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x2d391a) #14 0x7fe949b9f792 in QMenu::mouseReleaseEvent(QMouseEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x2d4792) #15 0x7fe949a66837 in QWidget::event(QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x19b837) #16 0x7fe949ba1aba in QMenu::event(QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x2d6aba) #17 0x7fe949a2683b in QApplicationPrivate::notify_helper(QObject*, QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x15b83b) #18 0x7fe949a2eca7 in QApplication::notify(QObject*, QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x163ca7) #19 0x7fe94fc2bf3c in KisApplication::notify(QObject*, QEvent*) /home/wolthera/krita/src/libs/ui/KisApplication.cpp:639 #20 0x7fe948c30327 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x280327) #21 0x7fe949a2d29e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x16229e) #22 0x7fe949a8179c (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x1b679c) #23 0x7fe949a84349 (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x1b9349) #24 0x7fe949a2683b in QApplicationPrivate::notify_helper(QObject*, QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x15b83b) #25 0x7fe949a2ddcf in QApplication::notify(QObject*, QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x162dcf) #26 0x7fe94fc2bf3c in KisApplication::notify(QObject*, QEvent*) /home/wolthera/krita/src/libs/ui/KisApplication.cpp:639 #27 0x7fe948c30327 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x280327) #28 0x7fe9491f852a in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5+0x11352a) #29 0x7fe9491f9694 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5+0x114694) #30 0x7fe9491d214a in
[okular] [Bug 405709] [Feature request] Printing to PDF - remember last used location
https://bugs.kde.org/show_bug.cgi?id=405709 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de --- Comment #2 from Michael Weghorn --- (In reply to Ovidiu-Florin BOGDAN from comment #0) > OBSERVED RESULT > The proposed location is always the location of the original file. That's not exactly what I get. The suggested path in my case is the working directory + a filename appended (based on the document that is open), which is not necessarily the same location as that of the currently open file. At a quick glance, it looks to me like the current handling is implemented in the Qt print dialog, more precisely the 'QUnixPrintWidget::QUnixPrintWidget' constructor, s. https://code.qt.io/cgit/qt/qtbase.git/tree/src/printsupport/dialogs/qprintdialog_unix.cpp#n1412 . (In reply to Ovidiu-Florin BOGDAN from comment #1) > Also it would be useful to remember the last printer used. It always > presents the default printer. I'm quite sure this is also what the Qt print dialog does, nothing Okular-specific. Kate e.g., which also uses the Qt print dialog, behaves the same way in my case. Calling QPrinter::setOutputFileName should probably make the above code take up the path set this way (though I didn't have any closer look), but I'm unsure whether it makes sense to do this specifically just for Okular (and what else would have to be taken into account). -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 381175] Add filename preview to Preferences window
https://bugs.kde.org/show_bug.cgi?id=381175
Nate Graham changed:
What|Removed |Added
Latest Commit|https://commits.kde.org/spe |https://commits.kde.org/spe
|ctacle/37448f5c48ee0d8799c3 |ctacle/4602c0efc01f7728c196
|dda6dbe5fc1e3fe41147|d7a5c98c30fe23ae3009
--- Comment #3 from Nate Graham ---
Git commit 4602c0efc01f7728c196d7a5c98c30fe23ae3009 by Nate Graham, on behalf
of David Redondo.
Committed on 21/03/2019 at 23:15.
Pushed by ngraham into branch 'Applications/19.04'.
Show preview of the filename in the save settings
Summary:
Shows the a preview of the configured filename template on the save settings
page. I'm not sure about the placement of the label but the functionality
should be there. This also again includes a small refactor to access the
placeholder replacement from outside of the ExportManager.
Test Plan: {F6697579}
Reviewers: #spectacle, #vdg, ngraham
Reviewed By: #spectacle, #vdg, ngraham
Subscribers: meven, ngraham, broulik
Tags: #spectacle
Differential Revision: https://phabricator.kde.org/D19775
M +6-1src/ExportManager.cpp
M +1-0src/ExportManager.h
M +26 -6src/Gui/SettingsDialog/SaveOptionsPage.cpp
M +4-0src/Gui/SettingsDialog/SaveOptionsPage.h
https://commits.kde.org/spectacle/4602c0efc01f7728c196d7a5c98c30fe23ae3009
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 405738] New: Windows title flickering - adding * into the title back and forth
https://bugs.kde.org/show_bug.cgi?id=405738 Bug ID: 405738 Summary: Windows title flickering - adding * into the title back and forth Product: systemsettings Version: 5.13.5 Platform: unspecified OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_launch Assignee: unassigned-b...@kde.org Reporter: jd...@protonmail.com Target Milestone: --- Application: systemsettings5 (5.13.5) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.18.0-16-generic x86_64 Distribution: Ubuntu 18.10 -- Information about the crash: 1. Open "system settings" from the start menu 2. In search field type "repo" or open "Launch Feedback" tab 3. Look at windows title. Windows title will flicker and change to "Launch Feedback *" back and forth very fast. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f690773c840 (LWP 8059))] Thread 7 (Thread 0x7f68e508d700 (LWP 8068)): #0 __GI___libc_read (fd=20, buf=0x7f68e508cb20, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7f690ac7e180 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f690ac3891f in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f690ac38df0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f690ac38f6c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f690e02c15b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f690dfd916b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f690de280b6 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f690d0e91f5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f690de31c87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f690bfae164 in start_thread (arg=) at pthread_create.c:486 #11 0x7f690db15def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f68e7f7d700 (LWP 8066)): #0 0x7f690ac7f509 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f690ac38571 in g_main_context_query () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f690ac38dc7 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f690ac38f6c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f690e02c15b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f690dfd916b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f690de280b6 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f690d0e91f5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f690de31c87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f690bfae164 in start_thread (arg=) at pthread_create.c:486 #10 0x7f690db15def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f68ed620700 (LWP 8065)): #0 __GI___libc_read (fd=15, buf=0x7f68ed61fb20, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7f690ac7e180 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f690ac3891f in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f690ac38df0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f690ac38f6c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f690e02c15b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f690dfd916b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f690de280b6 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f690d0e91f5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f690de31c87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f690bfae164 in start_thread (arg=) at pthread_create.c:486 #11 0x7f690db15def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f68fd160700 (LWP 8063)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x56551865e39c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x56551865e348, cond=0x56551865e370) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x56551865e370, mutex=0x56551865e348) at pthread_cond_wait.c:655 #3 0x7f68fdcc49cb in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #4 0x7f68fdcc4737 in ?? () from
[krita] [Bug 405737] New: Crash when transforming a frame [asan backtrace]
https://bugs.kde.org/show_bug.cgi?id=405737 Bug ID: 405737 Summary: Crash when transforming a frame [asan backtrace] Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com Target Milestone: --- SUMMARY Did a free transform on a frame, a rotation transform sepcifically. Did this about a dozen times before hitting this, so not easy to reproduce. = ==17960==ERROR: AddressSanitizer: heap-use-after-free on address 0x603002cc8a20 at pc 0x559276c44539 bp 0x7f77eab4c130 sp 0x7f77eab4c120 WRITE of size 4 at 0x603002cc8a20 thread T9282 (Thread (pooled)) #0 0x559276c44538 in std::__atomic_base::operator--() /usr/include/c++/7/bits/atomic_base.h:304 #1 0x7f784f8760c1 in bool QAtomicOps::deref(std::atomic&) /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:271 #2 0x7f784f875b47 in QBasicAtomicInteger::deref() /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:115 #3 0x7f784f88c471 in QSharedPointer::deref(QtSharedPointer::ExternalRefCountData*) (/home/wolthera/krita/inst/lib/x86_64-linux-gnu/kritaplugins/kritatooltransform.so+0xa0471) #4 0x7f784f88ab54 in QSharedPointer::deref() (/home/wolthera/krita/inst/lib/x86_64-linux-gnu/kritaplugins/kritatooltransform.so+0x9eb54) #5 0x7f784f885e0b in QSharedPointer::~QSharedPointer() (/home/wolthera/krita/inst/lib/x86_64-linux-gnu/kritaplugins/kritatooltransform.so+0x99e0b) #6 0x7f784f886755 in QSharedPointer::operator=(QSharedPointer const&) (/home/wolthera/krita/inst/lib/x86_64-linux-gnu/kritaplugins/kritatooltransform.so+0x9a755) #7 0x7f784f87b507 in ToolTransformArgs::operator=(ToolTransformArgs const&) /home/wolthera/krita/src/plugins/tools/tool_transform2/tool_transform_args.cc:132 #8 0x7f784fa027a4 in TransformStrokeStrategy::doStrokeCallback(KisStrokeJobData*) /home/wolthera/krita/src/plugins/tools/tool_transform2/strokes/transform_stroke_strategy.cpp:229 #9 0x7f78a7135021 in SimpleStrokeJobStrategy::run(KisStrokeJobData*) /home/wolthera/krita/src/libs/image/kis_simple_stroke_strategy.cpp:51 #10 0x7f78a714a7fc in KisStrokeJob::run() /home/wolthera/krita/src/libs/image/kis_stroke_job.h:44 #11 0x7f78a77bdff0 in KisUpdateJobItem::run() /home/wolthera/krita/build/libs/image/kritaimage_autogen/EWIEGA46WW/../../../../../src/libs/image/kis_update_job_item.h:91 #12 0x7f78a4786351 (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0xac351) #13 0x7f78a4781bc1 (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0xa7bc1) #14 0x7f78a37246da in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x76da) #15 0x7f78a3e6988e in __clone (/lib/x86_64-linux-gnu/libc.so.6+0x12188e) 0x603002cc8a20 is located 0 bytes inside of 24-byte region [0x603002cc8a20,0x603002cc8a38) freed by thread T9284 (Thread (pooled)) here: #0 0x7f78b05212d0 in operator delete(void*) (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xe12d0) #1 0x7f784f87548a in QtSharedPointer::ExternalRefCountData::operator delete(void*) /usr/include/x86_64-linux-gnu/qt5/QtCore/qsharedpointer_impl.h:167 #2 0x7f784f88c491 in QSharedPointer::deref(QtSharedPointer::ExternalRefCountData*) (/home/wolthera/krita/inst/lib/x86_64-linux-gnu/kritaplugins/kritatooltransform.so+0xa0491) #3 0x7f784f88ab54 in QSharedPointer::deref() (/home/wolthera/krita/inst/lib/x86_64-linux-gnu/kritaplugins/kritatooltransform.so+0x9eb54) #4 0x7f784f885e0b in QSharedPointer::~QSharedPointer() (/home/wolthera/krita/inst/lib/x86_64-linux-gnu/kritaplugins/kritatooltransform.so+0x99e0b) #5 0x7f784f886755 in QSharedPointer::operator=(QSharedPointer const&) (/home/wolthera/krita/inst/lib/x86_64-linux-gnu/kritaplugins/kritatooltransform.so+0x9a755) #6 0x7f784f87b507 in ToolTransformArgs::operator=(ToolTransformArgs const&) /home/wolthera/krita/src/plugins/tools/tool_transform2/tool_transform_args.cc:132 #7 0x7f784fa027a4 in TransformStrokeStrategy::doStrokeCallback(KisStrokeJobData*) /home/wolthera/krita/src/plugins/tools/tool_transform2/strokes/transform_stroke_strategy.cpp:229 #8 0x7f78a7135021 in SimpleStrokeJobStrategy::run(KisStrokeJobData*) /home/wolthera/krita/src/libs/image/kis_simple_stroke_strategy.cpp:51 #9 0x7f78a714a7fc in KisStrokeJob::run() /home/wolthera/krita/src/libs/image/kis_stroke_job.h:44 #10 0x7f78a77bdff0 in KisUpdateJobItem::run() /home/wolthera/krita/build/libs/image/kritaimage_autogen/EWIEGA46WW/../../../../../src/libs/image/kis_update_job_item.h:91 #11 0x7f78a4786351 (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0xac351) previously allocated by thread T0 here: #0 0x7f78b0520458 in operator new(unsigned long) (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xe0458) #1 0x7f784f88c2cd in
[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable
https://bugs.kde.org/show_bug.cgi?id=399167 David Faure changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #20 from David Faure --- Both fixes have been pushed in Applications/19.04 branch. (The fix for canceling is https://phabricator.kde.org/D19488) -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 405433] Apper crashes during Arch Linux update
https://bugs.kde.org/show_bug.cgi?id=405433 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/app ||er/d486706f3e9f7eefa4d44cd5 ||ace34eeaf7ba2ceb --- Comment #1 from Albert Astals Cid --- Git commit d486706f3e9f7eefa4d44cd5ace34eeaf7ba2ceb by Albert Astals Cid, on behalf of Alexander Kernozhitsky. Committed on 21/03/2019 at 22:11. Pushed by aacid into branch 'master'. Prevent crashing Apper on PackageModel::clearSelectedNotPresent() Summary: m_checkedPackages.erase() is called, but the iterator is not increased, therefore on the next iteration we use an invalid iterator Related: bug 401461, bug 402170 Test Plan: I just rebuilt Apper, ran it and installed the updates with it. The bug does not appear. Reviewers: dantti, apol Reviewed By: dantti Differential Revision: https://phabricator.kde.org/D19951 M +1-1libapper/PackageModel.cpp https://commits.kde.org/apper/d486706f3e9f7eefa4d44cd5ace34eeaf7ba2ceb -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 401461] Apper crashed after applying updates
https://bugs.kde.org/show_bug.cgi?id=401461 Albert Astals Cid changed: What|Removed |Added Latest Commit||https://commits.kde.org/app ||er/d486706f3e9f7eefa4d44cd5 ||ace34eeaf7ba2ceb Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Albert Astals Cid --- Git commit d486706f3e9f7eefa4d44cd5ace34eeaf7ba2ceb by Albert Astals Cid, on behalf of Alexander Kernozhitsky. Committed on 21/03/2019 at 22:11. Pushed by aacid into branch 'master'. Prevent crashing Apper on PackageModel::clearSelectedNotPresent() Summary: m_checkedPackages.erase() is called, but the iterator is not increased, therefore on the next iteration we use an invalid iterator Related: bug 405433, bug 402170 Test Plan: I just rebuilt Apper, ran it and installed the updates with it. The bug does not appear. Reviewers: dantti, apol Reviewed By: dantti Differential Revision: https://phabricator.kde.org/D19951 M +1-1libapper/PackageModel.cpp https://commits.kde.org/apper/d486706f3e9f7eefa4d44cd5ace34eeaf7ba2ceb -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405736] New: falkon:start doesn't automatically focus search bar
https://bugs.kde.org/show_bug.cgi?id=405736 Bug ID: 405736 Summary: falkon:start doesn't automatically focus search bar Product: Falkon Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: now...@gmail.com Reporter: a...@msgsafe.io Target Milestone: --- SUMMARY When using falkon:start as new tab page, opening a new tab doesn't focus the search not address bar. As you can't use the tab key to select either field, you are required to use your mouse to be able to navigate to a webpage or to start a search. STEPS TO REPRODUCE 1. Set falkon:start as page for new tab (in my case falkon:start is my homepage and my new tab is set to my homepage) 2. open a new tab 3. type a search/url OBSERVED RESULT The search field/address bar are not in focus and no search/URL can be input without clicking on said fields with the mouse. EXPECTED RESULT When opening the tab the search field is automatically selected and you can immediatly browse the web. SOFTWARE/OS VERSIONS Linux: Kernel 4.19 KDE Plasma Version: 5.15 KDE Frameworks Version: 5.56 Qt Version: 5.12 -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 402170] Apper segfaults on repeated update check
https://bugs.kde.org/show_bug.cgi?id=402170 Albert Astals Cid changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/app ||er/d486706f3e9f7eefa4d44cd5 ||ace34eeaf7ba2ceb Status|REPORTED|RESOLVED --- Comment #1 from Albert Astals Cid --- Git commit d486706f3e9f7eefa4d44cd5ace34eeaf7ba2ceb by Albert Astals Cid, on behalf of Alexander Kernozhitsky. Committed on 21/03/2019 at 22:11. Pushed by aacid into branch 'master'. Prevent crashing Apper on PackageModel::clearSelectedNotPresent() Summary: m_checkedPackages.erase() is called, but the iterator is not increased, therefore on the next iteration we use an invalid iterator Related: bug 405433, bug 401461 Test Plan: I just rebuilt Apper, ran it and installed the updates with it. The bug does not appear. Reviewers: dantti, apol Reviewed By: dantti Differential Revision: https://phabricator.kde.org/D19951 M +1-1libapper/PackageModel.cpp https://commits.kde.org/apper/d486706f3e9f7eefa4d44cd5ace34eeaf7ba2ceb -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405729] Kontact 5.10.3 crashes trying to "configure Kontact"
https://bugs.kde.org/show_bug.cgi?id=405729 Laurent Montel changed: What|Removed |Added Resolution|--- |DUPLICATE CC||mon...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Laurent Montel --- *** This bug has been marked as a duplicate of bug 405440 *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405440] Kontact crash when click on configure kontact
https://bugs.kde.org/show_bug.cgi?id=405440 Laurent Montel changed: What|Removed |Added CC||piedro.kul...@gmail.com --- Comment #11 from Laurent Montel --- *** Bug 405729 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 344181] konsole 256 color support differs from xterm/rxvt
https://bugs.kde.org/show_bug.cgi?id=344181 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405735] New: Text is not aligning correctly in working sheet.
https://bugs.kde.org/show_bug.cgi?id=405735 Bug ID: 405735 Summary: Text is not aligning correctly in working sheet. Product: krita Version: 4.1.5 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: leal_elizab...@hotmail.com Target Milestone: --- SUMMARY When I am in the text editing window I can align the text to the left, center or right but once I click 'save' the text is not aligning on my work sheet. STEPS TO REPRODUCE 1. Create a Text layer using the text tool. 2. Double click in the text to open the text editing window. 3. Select the text and align it to left, center or right. 4. Click 'Save' button. OBSERVED RESULT The text on the work sheet is not reflecting the changes made on the editing window. EXPECTED RESULT Text from work sheet should be aligned depending the orientation selected in the editing window. SOFTWARE/OS VERSIONS Windows: Windows 10 Home macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405700] Lensfun supported Camera is missing
https://bugs.kde.org/show_bug.cgi?id=405700 --- Comment #14 from Maik Qualmann --- Git commit 04eb24a5dd3f7984fe26e3af6630de3cd496e376 by Maik Qualmann. Committed on 21/03/2019 at 21:28. Pushed by mqualmann into branch 'master'. sort lenses M +1-1core/libs/dimg/filters/lens/lensfuncameraselector.cpp https://commits.kde.org/digikam/04eb24a5dd3f7984fe26e3af6630de3cd496e376 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405700] Lensfun supported Camera is missing
https://bugs.kde.org/show_bug.cgi?id=405700 --- Comment #13 from Maik Qualmann --- Git commit e69bcd7db60bf5b3c5ca0c944d05327b866ee40a by Maik Qualmann. Committed on 21/03/2019 at 21:24. Pushed by mqualmann into branch 'master'. do not sort the QComboBox model M +3-3core/libs/dimg/filters/lens/lensfuncameraselector.cpp https://commits.kde.org/digikam/e69bcd7db60bf5b3c5ca0c944d05327b866ee40a -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405585] Somewhere between Kate 17.12.3 and 18.12.2 code folding changed
https://bugs.kde.org/show_bug.cgi?id=405585 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com --- Comment #1 from Nibaldo G. --- Does it have to do with this?: https://phabricator.kde.org/D18516 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405734] New: PPC64, vrlwnm, vrlwmi, vrldrm, vrldmi do not work properly when me < mb
https://bugs.kde.org/show_bug.cgi?id=405734 Bug ID: 405734 Summary: PPC64, vrlwnm, vrlwmi, vrldrm, vrldmi do not work properly when me < mb Product: valgrind Version: 3.15 SVN Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: c...@us.ibm.com Target Milestone: --- The result is all zeros if the value of me < mb. The mask should wrap around from MSB back to LSB. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405733] New: PPC64, xvcvdpsp should write 32-bit result to upper and lower 32-bits of the 64-bit destination field.
https://bugs.kde.org/show_bug.cgi?id=405733 Bug ID: 405733 Summary: PPC64, xvcvdpsp should write 32-bit result to upper and lower 32-bits of the 64-bit destination field. Product: valgrind Version: 3.15 SVN Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: c...@us.ibm.com Target Milestone: --- The xvcvdpsp instruction currently only writes the result to the lower 32-bits of the destination field. It should write the same result to the upper and lower 32-bits of the result. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405700] Lensfun supported Camera is missing
https://bugs.kde.org/show_bug.cgi?id=405700 --- Comment #12 from Maik Qualmann --- The Powershot G9 X is included in the list... yes, "shot" with lowercase letters ... so it is strangely wise not always behind the G9 sorted but later behind a SX710... Maik -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 Thomas Monjalon changed: What|Removed |Added CC||tho...@monjalon.net --- Comment #27 from Thomas Monjalon --- Adding one more feedback about this annoying bug. This is what I see when running "akonadictl start": org.kde.pim.davresource: Error when uploading item: 420 "There was a problem with the request. The item was not modified on the server.\nThe file or folder caldav.fastmail.com does not exist. (0)." In case I can help, I am on IRC (tmonjalo). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405732] ASAN crash in input manager with creating guides.
https://bugs.kde.org/show_bug.cgi?id=405732 --- Comment #1 from wolthera --- Ok, this one is reproducable in an Address Sanitizer build :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405732] New: ASAN crash in input manager with creating guides.
https://bugs.kde.org/show_bug.cgi?id=405732 Bug ID: 405732 Summary: ASAN crash in input manager with creating guides. Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com Target Milestone: --- SUMMARY Got this crash running Krita with Address Sanitizer while making guides. Did not try to reproduce. = ==2320==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7ffd86a29248 at pc 0x7fd8f718dd40 bp 0x7ffd86a28ae0 sp 0x7ffd86a28ad0 READ of size 8 at 0x7ffd86a29248 thread T0 #0 0x7fd8f718dd3f in QPointF::toPoint() const /usr/include/x86_64-linux-gnu/qt5/QtCore/qpoint.h:409 #1 0x7fd8f72045ff in QEnterEvent::pos() const (/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaui.so.18+0x2b955ff) #2 0x7fd8f720085d in KisGuidesManager::Private::getDocPointFromEvent(QEvent*) /home/wolthera/krita/src/libs/ui/canvas/kis_guides_manager.cpp:580 #3 0x7fd8f7201092 in KisGuidesManager::eventFilter(QObject*, QEvent*) /home/wolthera/krita/src/libs/ui/canvas/kis_guides_manager.cpp:638 #4 0x7fd8f7ae75f0 in KisInputManager::eventFilter(QObject*, QEvent*) /home/wolthera/krita/src/libs/ui/input/kis_input_manager.cpp:178 #5 0x7fd8f7af8220 in KisInputManager::Private::CanvasSwitcher::eventFilter(QObject*, QEvent*) /home/wolthera/krita/src/libs/ui/input/kis_input_manager_p.cpp:272 #6 0x7fd8f0cd50ac in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x2800ac) #7 0x7fd8f1acb814 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x15b814) #8 0x7fd8f1ad2dcf in QApplication::notify(QObject*, QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x162dcf) #9 0x7fd8f7cd0f3c in KisApplication::notify(QObject*, QEvent*) /home/wolthera/krita/src/libs/ui/KisApplication.cpp:639 #10 0x7fd8f0cd5327 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x280327) #11 0x7fd8f1ad0948 in QApplicationPrivate::setFocusWidget(QWidget*, Qt::FocusReason) (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x160948) #12 0x7fd8f1b05c21 in QWidget::setFocus(Qt::FocusReason) (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x195c21) #13 0x7fd8f1b0a939 (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x19a939) #14 0x7fd8f0d04e24 in QMetaObject::activate(QObject*, int, int, void**) (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x2afe24) #15 0x7fd8f3b34c62 in KisTimedSignalThreshold::timeout() /home/wolthera/krita/build/libs/image/kritaimage_autogen/EWIEGA46WW/moc_kis_timed_signal_threshold.cpp:161 #16 0x7fd8f358fb15 in KisTimedSignalThreshold::forceDone() /home/wolthera/krita/src/libs/image/kis_timed_signal_threshold.cpp:58 #17 0x7fd8f358fcb0 in KisTimedSignalThreshold::start() /home/wolthera/krita/src/libs/image/kis_timed_signal_threshold.cpp:70 #18 0x7fd8f7af83fe in KisInputManager::Private::CanvasSwitcher::eventFilter(QObject*, QEvent*) /home/wolthera/krita/src/libs/ui/input/kis_input_manager_p.cpp:319 #19 0x7fd8f0cd50ac in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x2800ac) #20 0x7fd8f1acb814 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x15b814) #21 0x7fd8f1ad3ca7 in QApplication::notify(QObject*, QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x163ca7) #22 0x7fd8f7cd0f3c in KisApplication::notify(QObject*, QEvent*) /home/wolthera/krita/src/libs/ui/KisApplication.cpp:639 #23 0x7fd8f0cd5327 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x280327) #24 0x7fd8f1ad229e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x16229e) #25 0x7fd8f1b26a7f (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x1b6a7f) #26 0x7fd8f1b29349 (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x1b9349) #27 0x7fd8f1acb83b in QApplicationPrivate::notify_helper(QObject*, QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x15b83b) #28 0x7fd8f1ad2dcf in QApplication::notify(QObject*, QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x162dcf) #29 0x7fd8f7cd0f3c in KisApplication::notify(QObject*, QEvent*) /home/wolthera/krita/src/libs/ui/KisApplication.cpp:639 #30 0x7fd8f0cd5327 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x280327) #31 0x7fd8f129d52a in
[latte-dock] [Bug 405731] New: Not able to remove or move widgets in panel
https://bugs.kde.org/show_bug.cgi?id=405731 Bug ID: 405731 Summary: Not able to remove or move widgets in panel Product: latte-dock Version: git (master) Platform: Manjaro OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: himanshu.sp...@gmail.com Target Milestone: --- SUMMARY: I'm not able to remove or move widgets in latte panel. Instead it is allowing me to interact with the widgets. Took the latest pull from the git. STEPS TO REPRODUCE 1. Right click latte panel and open panel settings 2. Hover mouse on widgets OBSERVED RESULT: Doesn't show option to delete. Dragging widgets not possible too EXPECTED RESULT: Be able to remove widgets from panel or move them SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro KDE (available in About System) KDE Plasma Version: 5.15.3-1 KDE Frameworks Version: 5.56 (I think) Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405730] crashed when saving a kirat document
https://bugs.kde.org/show_bug.cgi?id=405730 --- Comment #3 from Boudewijn Rempt --- To amplify: apparently this "library" implements png export, duplicating what is already provided perfectly well by Qt. And gives it a priority higher than the native Qt png exporter. On saving a .kra file, we try to save the merged image as a png file. And then the libxfreeimage library crashes. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 --- Comment #13 from Nicofo --- Heu, I don't have libssl_conf.so on my system (Fedora 29). And "dnf provides libssl_conf.so" does not return anything. Note: under /usr/lib64, I have: $ ls /usr/lib64/libssl* /usr/lib64/libssl3.so/usr/lib64/libssl.so.1.1 /usr/lib64/libssl.so.10 /usr/lib64/libssl.so.1.1.1b /usr/lib64/libssl.so.1.0.2o -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 405683] clazy-const-signal-or-slot should not warn on Q_SCRIPTABLE slots
https://bugs.kde.org/show_bug.cgi?id=405683 Sergio Martins changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/cla ||zy/9e5066d5bf2ec5c06e89d78e ||42cc77ffdea54ba8 --- Comment #1 from Sergio Martins --- Git commit 9e5066d5bf2ec5c06e89d78e42cc77ffdea54ba8 by Sergio Martins. Committed on 21/03/2019 at 20:07. Pushed by smartins into branch 'master'. const-signal-or-slot: Add unit-test for Q_SCRIPTABLE Bug was fixed in previous commits, closing. M +7-0tests/const-signal-or-slot/main.cpp M +2-2tests/const-signal-or-slot/main.cpp.expected https://commits.kde.org/clazy/9e5066d5bf2ec5c06e89d78e42cc77ffdea54ba8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405730] crashed when saving a kirat document
https://bugs.kde.org/show_bug.cgi?id=405730 Boudewijn Rempt changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG CC||b...@valdyas.org Status|NEEDSINFO |RESOLVED --- Comment #2 from Boudewijn Rempt --- It's pretty simple: I see libfreeimage in the backtrace. That is a pretty sure sign of a Deepin Imageviewer infestation: gnu/libkritastore.so.17 #7 0x7fd63e7dabac in () at /usr/lib/x86_64-linux-gnu/libfreeimage.so.3 #8 0x7fd63e7cf0ed in FreeImage_GetFileTypeFromHandle () at /usr/lib/x86_64-linux-gnu/libfreeimage.so.3 #9 0x7fd63ea581de in FreeImageHandler::GetFIF(QIODevice*, QByteArray const&) () at /usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libxfreeimage.so #10 0x7fd63ea598ec in FreeimageQt5Plugin::capabilities(QIODevice*, QByteArray const&) const () at /usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libxfreeimage.so libxfreemimage.so is part of https://ubuntu.pkgs.org/18.04/ubuntu-universe-amd64/deepin-image-viewer_1.2.19-2_amd64.deb.html And because Qt loads all qimageio plugins, this gets loaded when Krita tries to make e.g. thumbnails, and causes crashes if there are files this abomination of a library cannot load. Uninstall Deepin : it's desperately buggy, with people who feel that it's a good idea to not check whether an image file longer than 0 bytes before starting to read it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405730] crashed when saving a kirat document
https://bugs.kde.org/show_bug.cgi?id=405730 wolthera changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||griffinval...@gmail.com Status|REPORTED|NEEDSINFO --- Comment #1 from wolthera --- Are you using the appimage, the ppa version or just a version from the Ubuntu repository? Or are you building yourself? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405730] New: crashed when saving a kirat document
https://bugs.kde.org/show_bug.cgi?id=405730 Bug ID: 405730 Summary: crashed when saving a kirat document Product: krita Version: 4.1.7 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: overman.supermund...@gmail.com Target Milestone: --- Application: krita (4.1.7) Qt Version: 5.9.5 Frameworks Version: 5.47.0 Operating System: Linux 4.18.0-16-generic x86_64 Distribution: Ubuntu 18.04.2 LTS -- Information about the crash: Everytime i try to save a document in native krita file, it crashes, exporting the document to a different formats work though The crash can be reproduced every time. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd678cf2280 (LWP 3062))] Thread 8 (Thread 0x7fd6037fe700 (LWP 4212)): [KCrash Handler] #6 0x7fd670827b68 in KoStore::pos() const () at /usr/lib/x86_64-linux-gnu/libkritastore.so.17 #7 0x7fd63e7dabac in () at /usr/lib/x86_64-linux-gnu/libfreeimage.so.3 #8 0x7fd63e7cf0ed in FreeImage_GetFileTypeFromHandle () at /usr/lib/x86_64-linux-gnu/libfreeimage.so.3 #9 0x7fd63ea581de in FreeImageHandler::GetFIF(QIODevice*, QByteArray const&) () at /usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libxfreeimage.so #10 0x7fd63ea598ec in FreeimageQt5Plugin::capabilities(QIODevice*, QByteArray const&) const () at /usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libxfreeimage.so #11 0x7fd6753abaae in () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #12 0x7fd6753abd8c in () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #13 0x7fd6753ac218 in QImageWriter::canWrite() const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #14 0x7fd6753ac3d7 in QImageWriter::write(QImage const&) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #15 0x7fd67537fc68 in QImageData::doImageIO(QImage const*, QImageWriter*, int) const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #16 0x7fd67537fe79 in QImage::save(QIODevice*, char const*, int) const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #17 0x7fd6157ba36b in () at /usr/lib/x86_64-linux-gnu/kritaplugins/kritakraexport.so #18 0x7fd6157bac8b in () at /usr/lib/x86_64-linux-gnu/kritaplugins/kritakraexport.so #19 0x7fd6157bafd5 in () at /usr/lib/x86_64-linux-gnu/kritaplugins/kritakraexport.so #20 0x7fd6157b6d7f in () at /usr/lib/x86_64-linux-gnu/kritaplugins/kritakraexport.so #21 0x7fd677a2f3b9 in KisImportExportManager::doExportImpl(QString const&, QSharedPointer, KisPinnedSharedPtr) () at /usr/lib/x86_64-linux-gnu/libkritaui.so.17 #22 0x7fd677a2f698 in KisImportExportManager::doExport(QString const&, QSharedPointer, KisPinnedSharedPtr, bool) () at /usr/lib/x86_64-linux-gnu/libkritaui.so.17 #23 0x7fd677a31905 in () at /usr/lib/x86_64-linux-gnu/libkritaui.so.17 #24 0x7fd674b9b2b2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7fd674b9e17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7fd66e2c46db in start_thread (arg=0x7fd6037fe700) at pthread_create.c:463 #27 0x7fd67428188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fd61cd89700 (LWP 3090)): #0 0x7fd66cc85064 in g_mutex_unlock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fd66cc3f0d9 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd66cc3f5c0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd66cc3f64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fd674dd59bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd674d7aa1a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fd674b9923a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fd65aacf2a6 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7fd674b9e17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fd66e2c46db in start_thread (arg=0x7fd61cd89700) at pthread_create.c:463 #10 0x7fd67428188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fd61e651700 (LWP 3088)): #0 0x7fd66cc85064 in g_mutex_unlock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fd66cc3ea88 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd66cc3f46b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd66cc3f64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fd674dd59bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5
[Breeze] [Bug 391134] Don't have an icon for num lock key
https://bugs.kde.org/show_bug.cgi?id=391134 Arvid Hansson changed: What|Removed |Added Status|CONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 391134] Don't have an icon for num lock key
https://bugs.kde.org/show_bug.cgi?id=391134 Arvid Hansson changed: What|Removed |Added Assignee|visual-des...@kde.org |arvid.hanss...@yahoo.se -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 391134] Don't have an icon for num lock key
https://bugs.kde.org/show_bug.cgi?id=391134 --- Comment #15 from Arvid Hansson --- The patch is up! https://phabricator.kde.org/D19952 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387703] After suspend, the task manager of the main screen panel displays the tasks of the second screen
https://bugs.kde.org/show_bug.cgi?id=387703 --- Comment #3 from kon...@gmx.com --- I just discovered another failure mode: 3) Sometimes a task manager set to only display tasks from the current screen displays no tasks at all. If I remove the filter, then all tasks are shown, as expected. To further add detail, unchecking the "show only tasks from the current screen" box, applying the changes, and then checking it again does not fix any of these errors. Neither does removing the task manager and then undoing that action. Only removing the task manager and then adding a new one will temporarily work around the issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405317] Cannot find file just created in home directory
https://bugs.kde.org/show_bug.cgi?id=405317
--- Comment #16 from dagobert...@mailbox.org ---
First of all: Sorry for my late response. I was really busy this week.
@NateGraham: I also have Frameworks 5.56 installed. One email told me that you
changed that entry back to version 5.55 on March the 17th. I am running KDE
Neon User Edition and update regularly.
@StefanBrüns:
> 1. Does this only affect files with parentheses?
No. I can reproduce it with "file1", "file2" and "file3" for example.
> 2. Can you run 'balooctl monitor' and then create the file?
For me baloo was inactive the whole time.
> Can you attach strace to the running baloo_file process ("strace -p ")
> and check if you get any output and/or errors when you touch a file?
$ ps -e | grep -i baloo
1305 ?00:00:28 baloo_file
21478 ?00:00:00 baloorunner
I am not really sure, how this actually works but I tried:
$ sudo strace -p 1305
strace: Process 1305 attached
restart_syscall(<... resuming interrupted poll ...>
Then I created some files via Dolphin and after a while got this output:
) = 1
read(3, "\1\0\0\0\0\0\0\0", 16) = 8
poll([{fd=3, events=POLLIN}, {fd=9, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLPRI}], 4, -1) = 1 ([{fd=3, revents=POLLIN}])
read(3, "\1\0\0\0\0\0\0\0", 16) = 8
poll([{fd=3, events=POLLIN}, {fd=9, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLPRI}], 4, -1^Cstrace: Process 1305 detached
Greetings
--
You are receiving this mail because:
You are watching all bug changes.
[kontact] [Bug 405729] New: Kontact 5.10.3 crashes trying to "configure Kontact"
https://bugs.kde.org/show_bug.cgi?id=405729 Bug ID: 405729 Summary: Kontact 5.10.3 crashes trying to "configure Kontact" Product: kontact Version: 5.10.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: piedro.kul...@gmail.com Target Milestone: --- SUMMARY Kontact crashes with segmentation fault when entering "configure kontact". STEPS TO REPRODUCE 1. open kontact, any section... 2. open menu "settings" 3. choose "configure kontact" OBSERVED RESULT Kontact crashes immediateley with a segfault EXPECTED RESULT Kontact shouldn't crash, obviously SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch linux fully updates (available in About System) Kontact 5.10.3 KDE Frameworks 5.56.0 Qt 5.12.2 (built against 5.12.1) ADDITIONAL INFORMATION This is serious. It makes Kontact unconfigurable. Since a "Personal" information maneger has to be configured to individual needs this is a complete showstopper rendering kontact basically unusable for any real life work scenario. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402433] Google Maps Doesn't Zoom With Mouse Wheel
https://bugs.kde.org/show_bug.cgi?id=402433 --- Comment #22 from hardy.pub...@gmail.com --- i386 Appimage works also. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405728] plasma widget crashing
https://bugs.kde.org/show_bug.cgi?id=405728 --- Comment #1 from David Edmundson --- Please report to kvantum. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405687] latte panels go haywire with display on the left
https://bugs.kde.org/show_bug.cgi?id=405687 --- Comment #31 from leftcrane --- Thanks for all the work! The bug is indeed fixed. I also got it working alongside a KWin rule to force all windows to the primary display. I had to make sure to negate lattedock in the rule, because otherwise it will eventually start grabbing DP-2 panels and putting them on DP-1 when both monitors are connected. Just dropping this here cause it's relevant to the multihead workflow with a latte dock and a secondary monitor on the left. KWin pushes most your windows to monitor on the left, regardless of whether it's primary, cause that's where the origin is. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #28 from Christoph Feck --- The name was replaced because it was wrong. It didn't return the width, but the number of pixels the cursor advances. If you wanted the width, you had to use boundingRect().width(). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405728] New: plasma widget crashing
https://bugs.kde.org/show_bug.cgi?id=405728 Bug ID: 405728 Summary: plasma widget crashing Product: plasmashell Version: 5.12.7 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: x...@gmx.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.7) (Compiled from sources) Qt Version: 5.9.5 Frameworks Version: 5.47.0 Operating System: Linux 4.18.0-16-generic x86_64 Distribution: Ubuntu 18.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: configured the widget named netspeed - Unusual behavior I noticed: crashed the screen got blanked - Custom settings of the application: nothing i was just configuring the widget The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f54f7853800 (LWP 2446))] Thread 16 (Thread 0x7f53f94f4700 (LWP 19829)): #0 0x7f54f06ab9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x558d016f6630) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x558d016f65e0, cond=0x558d016f6608) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x558d016f6608, mutex=0x558d016f65e0) at pthread_cond_wait.c:655 #3 0x7f54f15255ab in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f54f52aa6a8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f54f52aab0a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f54f152417d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f54f06a56db in start_thread (arg=0x7f53f94f4700) at pthread_create.c:463 #8 0x7f54f0e1f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f53eb7ff700 (LWP 19827)): #0 0x7f54f152300d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f54f175bdb1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f54eb97af51 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f54eb97b4e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f54eb97b64c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f54f175b9bb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f54f1700a1a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f54f151f23a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f54f46916f5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f54f152417d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f54f06a56db in start_thread (arg=0x7f53eb7ff700) at pthread_create.c:463 #11 0x7f54f0e1f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f53fb9f6700 (LWP 19047)): #0 0x7f54f06ab9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x558cfdb877b0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x558cfdb87760, cond=0x558cfdb87788) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x558cfdb87788, mutex=0x558cfdb87760) at pthread_cond_wait.c:655 #3 0x7f54f15255ab in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f54f52aa6a8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f54f52aab0a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f54f152417d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f54f06a56db in start_thread (arg=0x7f53fb9f6700) at pthread_create.c:463 #8 0x7f54f0e1f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f53fa1f5700 (LWP 2752)): #0 0x7f54f06ab9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x558cfc00db94) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x558cfc00db40, cond=0x558cfc00db68) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x558cfc00db68, mutex=0x558cfc00db40) at pthread_cond_wait.c:655 #3 0x7f54f15255ab in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f54f52aa6a8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f54f52aab0a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f54f152417d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7
[kdemultimedia] [Bug 404897] kdeinit5 crashes all the time
https://bugs.kde.org/show_bug.cgi?id=404897 --- Comment #10 from Christoph Feck --- *** Bug 405692 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 405692] Dolphin crashes when hovering a subtitle .sub file
https://bugs.kde.org/show_bug.cgi?id=405692 Christoph Feck changed: What|Removed |Added Resolution|FIXED |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #5 from Christoph Feck --- The file from comment #4 is a rendered (i.e. non-text) subtitle file. It has no video or audio streams, causing ffmpegthumbs to crash. ffmpegthumbs 18.12.3 fixed this case. I tested it, and got no crash. *** This bug has been marked as a duplicate of bug 404897 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405725] Some elements render as transparent
https://bugs.kde.org/show_bug.cgi?id=405725 --- Comment #8 from Boudewijn Rempt --- Best use Angle then. I guess might even want to remove the opengl option on Windows, there are always problems when trying to use opengl directly. -- You are receiving this mail because: You are watching all bug changes.
[kdemultimedia] [Bug 404897] kdeinit5 crashes all the time
https://bugs.kde.org/show_bug.cgi?id=404897 Christoph Feck changed: What|Removed |Added CC||meve...@gmail.com --- Comment #9 from Christoph Feck --- *** Bug 405727 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdemultimedia] [Bug 405727] ffmpeg crash with 3g2 file
https://bugs.kde.org/show_bug.cgi?id=405727 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Christoph Feck --- No crash with ffmpegthumbnailer 18.12.3. The file has no video, and the duplicate bug fixed this case. *** This bug has been marked as a duplicate of bug 404897 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405724] multi-screen to single screen slideshow memory leak
https://bugs.kde.org/show_bug.cgi?id=405724 --- Comment #3 from rtver...@gmail.com --- Created attachment 118966 --> https://bugs.kde.org/attachment.cgi?id=118966=edit output: QSG_INFO=1 plasmashell --replace -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364766] Graphics distorted after suspend/resume with nvidia
https://bugs.kde.org/show_bug.cgi?id=364766 --- Comment #82 from David Edmundson --- FWIW, my final (I hope) Qt patch was part of Qt5.12.2 This means just [QtQuickRendererSettings] GraphicsResetNotifications=true into ~/.config/kdeglobals should be enough without lockups. I want to hear more feedback before I make that the default -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 398963] Blurred background becomes black (or almost black) with a dark background
https://bugs.kde.org/show_bug.cgi?id=398963 Filip Fila changed: What|Removed |Added CC||tyx...@gmail.com --- Comment #3 from Filip Fila --- Can you please test with master (KDE Neon Dev Unstable)? The blur and darkening have been reduced so the problem might have been solved. -- You are receiving this mail because: You are watching all bug changes.
[kdemultimedia] [Bug 405727] ffmpeg crash with 3g2 file
https://bugs.kde.org/show_bug.cgi?id=405727 --- Comment #1 from Méven Car --- Created attachment 118965 --> https://bugs.kde.org/attachment.cgi?id=118965=edit stack trace It is a file part of taglib tests data -- You are receiving this mail because: You are watching all bug changes.
[kdemultimedia] [Bug 405727] New: ffmpeg crash with 3g2 file
https://bugs.kde.org/show_bug.cgi?id=405727 Bug ID: 405727 Summary: ffmpeg crash with 3g2 file Product: kdemultimedia Version: 18.12 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ffmpegthumbs Assignee: kde-multime...@kde.org Reporter: meve...@gmail.com Target Milestone: --- Created attachment 118964 --> https://bugs.kde.org/attachment.cgi?id=118964=edit file causing the crash SUMMARY Crash when trying to get a preview of a 3g2 file OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Kubuntu 18.10 KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.1 Kernel Version: 4.18.0-16-generic OS Type: 64-bit Processors: 12 × AMD Ryzen 5 1600 Six-Core Processor Memory: 15,7 Gio -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405724] multi-screen to single screen slideshow memory leak
https://bugs.kde.org/show_bug.cgi?id=405724 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||k...@davidedmundson.co.uk Status|REPORTED|NEEDSINFO --- Comment #2 from David Edmundson --- please attach output of QSG_INFO=1 plasmashell --replace and attach the log for the first few seconds -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 405726] New: "Vorbeugung gegen Übernahme der Aktivierung" exists twice in application-specific window settings
https://bugs.kde.org/show_bug.cgi?id=405726 Bug ID: 405726 Summary: "Vorbeugung gegen Übernahme der Aktivierung" exists twice in application-specific window settings Product: i18n Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: de Assignee: kde-i18n...@kde.org Reporter: kde-b...@cboltz.de Target Milestone: --- The dialog to set application-specific window settings has the option "Vorbeugung gegen Übernahme der Aktivierung" twice. My guess is that there are two similar options that were translated to the same german text. STEPS TO REPRODUCE 1. right-click window title bar 2. select Weitere Aktionen (more actions) - Spezielle Einstellungen für dieses Programm (specific settings for this program) 3. go to the Erscheinungsbild & Korrekturen (appearance and corrections) tab OBSERVED RESULT Two options labeled "Vorbeugung gegen Übernahme der Aktivierung" EXPECTED RESULT Only one option with that label (and most likely a different label for the other one) SOFTWARE/OS VERSIONS openSUSE Tumbleweed KDE Plasma Version: 5.13.3 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405725] Some elements render as transparent
https://bugs.kde.org/show_bug.cgi?id=405725 --- Comment #7 from Piotr --- With angle renderer selection outline and brush outline are solid black, no transparency effect. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405725] Some elements render as transparent
https://bugs.kde.org/show_bug.cgi?id=405725 --- Comment #6 from Piotr --- Created attachment 118963 --> https://bugs.kde.org/attachment.cgi?id=118963=edit Better screenshot -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405725] Some elements render as transparent
https://bugs.kde.org/show_bug.cgi?id=405725 --- Comment #5 from Boudewijn Rempt --- Showing the complete windows helps us understand whether it might be because of the document composition. Please enable Angle in the settings and try again. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405725] Some elements render as transparent
https://bugs.kde.org/show_bug.cgi?id=405725 --- Comment #4 from Piotr --- Sorry I cut only canvas, because I observe it only on canvas, to keep file small. As for renderer, it's OpenGL, GTX 660 driver ver. 23.21.13.8813 The line you see on the canvas is not part of document (It's solid gray) it's temporary outline that outline selection tools shows before you lift the pen. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405725] Some elements render as transparent
https://bugs.kde.org/show_bug.cgi?id=405725 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Boudewijn Rempt --- What GPU? Which driver version? Angle or OpenGL? And that screenshot doesn't show the complete Krita window so we cannot see what your image looks like. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405725] Some elements render as transparent
https://bugs.kde.org/show_bug.cgi?id=405725 --- Comment #2 from Piotr --- Created attachment 118962 --> https://bugs.kde.org/attachment.cgi?id=118962=edit Checkerboard from behind comming through -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405725] Some elements render as transparent
https://bugs.kde.org/show_bug.cgi?id=405725 --- Comment #1 from Piotr --- Some elements make parts of krita window transparent. Observed for brush outline and selection outline before commiting STEPS TO REPRODUCE 1. Put window with some distinct pattern behind Krita (I used white/red checkerboard) 2. "Draw" over canvas with outline selection tool 3. Observe pattern from behind comming through the lines. EXPECTED RESULT Lines should show canvas content not the window behind SOFTWARE/OS VERSIONS Windows: 10 Version 1809 x86-64 ADDITIONAL INFORMATION Krita prealpha git 703cbfb -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405725] New: Some elements render as transparent
https://bugs.kde.org/show_bug.cgi?id=405725 Bug ID: 405725 Summary: Some elements render as transparent Product: krita Version: unspecified Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: OpenGL Canvas Assignee: krita-bugs-n...@kde.org Reporter: postrows...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 404306] [Wayland] Sometimes Dolphin disappears (no entry in plasma panel and task switcher) when I open file properties window despite its process is still running according to Ksysguar
https://bugs.kde.org/show_bug.cgi?id=404306 mthw0 changed: What|Removed |Added CC||jari...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404853] digikam-6.0.0 faces engine fails to compile on PowerPC
https://bugs.kde.org/show_bug.cgi?id=404853 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/dig ||ikam/6a3da298103797d01fa0cb ||049cccaff39bd1583e Status|REPORTED|RESOLVED --- Comment #5 from caulier.gil...@gmail.com --- Git commit 6a3da298103797d01fa0cb049cccaff39bd1583e by Gilles Caulier. Committed on 21/03/2019 at 16:29. Pushed by cgilles into branch 'master'. add new optional configuration option to enable Faces Engine DNN support Related: bug 405625 M +2-0Mainpage.dox M +4-1NEWS M +1-0bootstrap.linux M +1-0bootstrap.macports M +1-0bootstrap.mxe M +1-0bootstrap.tarball M +8-5core/CMakeLists.txt M +6-3core/app/utils/digikam_config.h.cmake.in M +20 -11 core/libs/facesengine/CMakeLists.txt M +34 -22 core/libs/facesengine/facedb/facedb.cpp M +6-0core/libs/facesengine/facedb/facedb.h M +55 -8core/libs/facesengine/recognitiondatabase.cpp M +1-1core/libs/facesengine/recognitiondatabase.h M +3-0core/utilities/facemanagement/facescandialog.cpp https://commits.kde.org/digikam/6a3da298103797d01fa0cb049cccaff39bd1583e -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405625] digiKam 6.0.0 faces engine fails to compile on PowerPC with AltiVec enabled
https://bugs.kde.org/show_bug.cgi?id=405625 caulier.gil...@gmail.com changed: What|Removed |Added Latest Commit||https://commits.kde.org/dig ||ikam/6a3da298103797d01fa0cb ||049cccaff39bd1583e Resolution|DUPLICATE |FIXED --- Comment #2 from caulier.gil...@gmail.com --- Git commit 6a3da298103797d01fa0cb049cccaff39bd1583e by Gilles Caulier. Committed on 21/03/2019 at 16:29. Pushed by cgilles into branch 'master'. add new optional configuration option to enable Faces Engine DNN support Related: bug 404853 M +2-0Mainpage.dox M +4-1NEWS M +1-0bootstrap.linux M +1-0bootstrap.macports M +1-0bootstrap.mxe M +1-0bootstrap.tarball M +8-5core/CMakeLists.txt M +6-3core/app/utils/digikam_config.h.cmake.in M +20 -11 core/libs/facesengine/CMakeLists.txt M +34 -22 core/libs/facesengine/facedb/facedb.cpp M +6-0core/libs/facesengine/facedb/facedb.h M +55 -8core/libs/facesengine/recognitiondatabase.cpp M +1-1core/libs/facesengine/recognitiondatabase.h M +3-0core/utilities/facemanagement/facescandialog.cpp https://commits.kde.org/digikam/6a3da298103797d01fa0cb049cccaff39bd1583e -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405312] I can't type with Korean in "Project - Add Title Clip".
https://bugs.kde.org/show_bug.cgi?id=405312 emohr changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |NOT A BUG --- Comment #7 from emohr --- I'll close this Bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394981] Icons for JetBrains products are now only displayed in search
https://bugs.kde.org/show_bug.cgi?id=394981 Ilya Bizyaev changed: What|Removed |Added Version|5.14.5 |5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 405173] Add support for massif's --alloc-fn
https://bugs.kde.org/show_bug.cgi?id=405173 Milian Wolff changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Milian Wolff --- agreed -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 404633] Compatibility with ASAN
https://bugs.kde.org/show_bug.cgi?id=404633 Milian Wolff changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Milian Wolff --- I would also love to be able to check the heaptrack internals with ASAN - which isn't possible due to the issue you mention. In the tests I have separated most of this, such that I can run most of the internal code with ASAN enabled. But the symbol overloading logic cannot be checked - I never made it work. If you figure out how to play nice with ASAN I'd be all ears. For now, there's nothing I can do. Sorry! I'd love to give you a different answer, but right now I don't see any alternative :( -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399363] Can't move a rectangle
https://bugs.kde.org/show_bug.cgi?id=399363 --- Comment #7 from Boudewijn Rempt --- Git commit 861995e810b1ecfa5260903fd58ef89f199d3bc3 by Boudewijn Rempt. Committed on 21/03/2019 at 15:53. Pushed by rempt into branch 'master'. Shape layers: change the canvas compressor delay depending on image size This sort of keeps the best of both the fix for https://bugs.kde.org/show_bug.cgi?id=399363 and some responsiveness for smaller images. The real solution probably would be to render the vector shapes at the current zoom level, LoD-like (and only for the visible part, of course), but that's way out of scope for now. We might as well wish we could write our svg renderer without QPainter and with proper color management. Related: bug 405698 M +15 -2libs/ui/flake/kis_shape_layer_canvas.cpp M +2-2libs/ui/flake/kis_shape_layer_canvas.h https://commits.kde.org/krita/861995e810b1ecfa5260903fd58ef89f199d3bc3 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405698] Vector graphic - lagging
https://bugs.kde.org/show_bug.cgi?id=405698 --- Comment #4 from Boudewijn Rempt --- Git commit 861995e810b1ecfa5260903fd58ef89f199d3bc3 by Boudewijn Rempt. Committed on 21/03/2019 at 15:53. Pushed by rempt into branch 'master'. Shape layers: change the canvas compressor delay depending on image size This sort of keeps the best of both the fix for https://bugs.kde.org/show_bug.cgi?id=399363 and some responsiveness for smaller images. The real solution probably would be to render the vector shapes at the current zoom level, LoD-like (and only for the visible part, of course), but that's way out of scope for now. We might as well wish we could write our svg renderer without QPainter and with proper color management. Related: bug 399363 M +15 -2libs/ui/flake/kis_shape_layer_canvas.cpp M +2-2libs/ui/flake/kis_shape_layer_canvas.h https://commits.kde.org/krita/861995e810b1ecfa5260903fd58ef89f199d3bc3 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #19 from David Faure --- Git commit 8ff596c4fe15199b66262c624d8b7c8d8ec7368f by David Faure. Committed on 21/03/2019 at 15:50. Pushed by dfaure into branch 'Applications/19.04'. Akonadi: fix dangling transaction after itemsync failure Summary: TransactionSequence was emitting result() twice when rolling back. * How did this happen? The TransactionRollbackJob is (automatically) added as a subjob of the TransactionSequence, so when it finishes, slotResult is called (like for all subjobs), as well as rollbackResult(). Since the latter emits result() already [mostly for symmetry with commitResult()], we don't need to do that in slotResult (which doesn't do it for the case of committing, either). * Why is it a problem to emit result() twice? Well, first, it's against the law in KJob world. In practice, ItemSyncPrivate::slotTransactionResult was called twice (for the same TransactionSequence job) which made it decrement mTransactionJobs one time too many. As a result, checkDone() finished too early and didn't go into the "commit transaction" branch for other transactions. Leaving a transaction "open" is a good recipe for database deadlocks further down the line. * Why did the TransactionSequence roll back in the first place? In my case because of the infamous and not-yet fixed "Multiple merge candidates" problem, but it seems that it can also happen when having items without a part, according to Volker's investigations. All of these issues still need to be fixed, but at least akonadi seems to be still usable after they happen. Test Plan: Ctrl+L in kmail, with a folder having multiple items for the same RID Reviewers: dvratil, vkrause Reviewed By: dvratil Subscribers: kfunk, kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D19487 (cherry picked from commit f1281cf18f40fd69acd61c31b48f5ce43e138eea) M +0-2src/core/jobs/transactionsequence.cpp https://commits.kde.org/akonadi/8ff596c4fe15199b66262c624d8b7c8d8ec7368f -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 399167] Akonadi enters deadlock state which makes it completely unuseable
https://bugs.kde.org/show_bug.cgi?id=399167 --- Comment #18 from David Faure --- Git commit f1281cf18f40fd69acd61c31b48f5ce43e138eea by David Faure. Committed on 21/03/2019 at 15:49. Pushed by dfaure into branch 'master'. Akonadi: fix dangling transaction after itemsync failure Summary: TransactionSequence was emitting result() twice when rolling back. * How did this happen? The TransactionRollbackJob is (automatically) added as a subjob of the TransactionSequence, so when it finishes, slotResult is called (like for all subjobs), as well as rollbackResult(). Since the latter emits result() already [mostly for symmetry with commitResult()], we don't need to do that in slotResult (which doesn't do it for the case of committing, either). * Why is it a problem to emit result() twice? Well, first, it's against the law in KJob world. In practice, ItemSyncPrivate::slotTransactionResult was called twice (for the same TransactionSequence job) which made it decrement mTransactionJobs one time too many. As a result, checkDone() finished too early and didn't go into the "commit transaction" branch for other transactions. Leaving a transaction "open" is a good recipe for database deadlocks further down the line. * Why did the TransactionSequence roll back in the first place? In my case because of the infamous and not-yet fixed "Multiple merge candidates" problem, but it seems that it can also happen when having items without a part, according to Volker's investigations. All of these issues still need to be fixed, but at least akonadi seems to be still usable after they happen. Test Plan: Ctrl+L in kmail, with a folder having multiple items for the same RID Reviewers: dvratil, vkrause Reviewed By: dvratil Subscribers: kfunk, kde-pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D19487 M +0-2src/core/jobs/transactionsequence.cpp https://commits.kde.org/akonadi/f1281cf18f40fd69acd61c31b48f5ce43e138eea -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #27 from Kamil Dudka --- Comment on attachment 118961 --> https://bugs.kde.org/attachment.cgi?id=118961 patch to reenable numbers, v18.12 Works perfectly. Thanks for the quick fix! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405724] multi-screen to single screen slideshow memory leak
https://bugs.kde.org/show_bug.cgi?id=405724 --- Comment #1 from rtver...@gmail.com --- I'm rushing to get this bug report in before a meeting, and I missed something describing the steps I follow...though I am not sure if these are required in order to reproduce the leak: Step 3.5: sleep or hibernate Step 4: (switch screens when laptop is sleep or hibernate) Step 4.5: turn power back on with new monitor configuration. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 385885] Multi-monitor HiDPI screens with scaling: Rectangular Region mode causes graphical corruption on one of the screens
https://bugs.kde.org/show_bug.cgi?id=385885 --- Comment #25 from Michael Reiher --- Yes, exactly! see my comment #c5 :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405724] New: multi-screen to single screen slideshow memory leak
https://bugs.kde.org/show_bug.cgi?id=405724 Bug ID: 405724 Summary: multi-screen to single screen slideshow memory leak Product: plasmashell Version: 5.15.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Image Wallpaper Assignee: notm...@gmail.com Reporter: rtver...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY This is on a laptop hooked up to multiple monitors via docking station (laptop is closed & screen is off). After the last slideshow memory leak, I didn't start using slideshow again until recently. I had a running session for nearly two weeks with reasonable plasmashell memory usage - it started at about 90mb after a fresh boot, gradually rose to around 200mb, then hovered +/- from there. I then used the laptop disconnected from the docking station, using the laptop's screen. plasmashell memory usage rapidly rose to around 1.4gb during the roughly 8 hours that the laptop was on; though I was not at the laptop, it was mostly sitting on a desk idle. I then docked the laptop again (lid closed, laptop screen off), and memory usage has continued to rise in the roughly 1 hour that I've been using it back on the dock to a little over 1.5gb. STEPS TO REPRODUCE 1. configure slideshow, rapid shuffle time to exacerbate memory leak. 2. start new session with a screen turned off, but some other screens on. (ie, laptop screen off, desktop monitors on). 3. watch memory usage level off at reasonable usage. 4. swap screens (ie, turn on the ones that were off at #2 above, and turn off the ones that were on) 5. watch memory usage rise dramatically. OBSERVED RESULT plasmashell eats too much memory. EXPECTED RESULT plasmashell maintains balanced diet. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo. kernel 4.20.x & 5.0.3 (available in About System) KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.56 Qt Version: 5.11.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #26 from Éric Brunet --- Created attachment 118961 --> https://bugs.kde.org/attachment.cgi?id=118961=edit patch to reenable numbers, v18.12 Sorry, I was slow with updating this patch. The method horizontalAdvance seems to replace nicely the method width. Probably that they changed it because "width" was so difficult to remember... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403340] Lag in working with vectors
https://bugs.kde.org/show_bug.cgi?id=403340 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #5 from Boudewijn Rempt --- *** This bug has been marked as a duplicate of bug 405698 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405698] Vector graphic - lagging
https://bugs.kde.org/show_bug.cgi?id=405698 Boudewijn Rempt changed: What|Removed |Added CC||marcos...@tutanota.com --- Comment #3 from Boudewijn Rempt --- *** Bug 403340 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405698] Vector graphic - lagging
https://bugs.kde.org/show_bug.cgi?id=405698 --- Comment #2 from Boudewijn Rempt --- This probably the culprit: commit dc4e44f448ba5fc8379ac7751baf2638593b0ac0 Author: Emmet O'Neill Date: Sun Oct 14 22:35:40 2018 +0200 Improved responsiveness of moving large SVG objects. Added a KisSignalCompressor to the KisShapeLayerCanvas to reduce the number of updates. BUG:399363 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405698] Vector graphic - lagging
https://bugs.kde.org/show_bug.cgi?id=405698 Boudewijn Rempt changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405723] New: Crash when adding in multiple frame columns.
https://bugs.kde.org/show_bug.cgi?id=405723 Bug ID: 405723 Summary: Crash when adding in multiple frame columns. Product: krita Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com Target Milestone: --- Application: krita (4.2.0-pre-alpha (git 9429230)) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: 1. Animation with frames. 2. Rightclick timeline header for context menu. 3. Insert multiple columns. 4 columns, timing 1, frames 'before/left'. 4. Apply. You will see the new frames briefly, and then a crash. -- Backtrace: Application: Krita (krita), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f237ea35880 (LWP 3487))] Thread 16 (Thread 0x7f2302d0c700 (LWP 26429)): [KCrash Handler] #7 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #8 0x7f2371212801 in __GI_abort () at abort.c:79 #9 0x7f2371be7e7b in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f23735505f3 in kis_assert_common (assertion=0x7f2374e56100 "m_frames.contains(frameId)", file=0x7f2374e55cc0 "/home/wolthera/krita/src/libs/image/kis_paint_device.cc", line=466, throwException=false, isIgnorable=false) at /home/wolthera/krita/src/libs/global/kis_assert.cpp:90 #11 0x7f2373550db0 in kis_assert_recoverable (assertion=0x7f2374e56100 "m_frames.contains(frameId)", file=0x7f2374e55cc0 "/home/wolthera/krita/src/libs/image/kis_paint_device.cc", line=466) at /home/wolthera/krita/src/libs/global/kis_assert.cpp:103 #12 0x7f23749f7116 in KisPaintDevice::Private::currentFrameData (this=0x60d00016b9c0) at /home/wolthera/krita/src/libs/image/kis_paint_device.cc:466 #13 0x7f23749f7550 in KisPaintDevice::Private::currentNonLodData (this=0x60d00016b9c0) at /home/wolthera/krita/src/libs/image/kis_paint_device.cc:485 #14 0x7f23749f7a17 in KisPaintDevice::Private::currentData (this=0x60d00016b9c0) at /home/wolthera/krita/src/libs/image/kis_paint_device.cc:519 #15 0x7f23749f295e in KisPaintDevice::Private::dataManager (this=0x60d00016b9c0) at /home/wolthera/krita/src/libs/image/kis_paint_device.cc:120 #16 0x7f23749e02c2 in KisPaintDevice::defaultPixel (this=0x604001a78850) at /home/wolthera/krita/src/libs/image/kis_paint_device.cc:1463 #17 0x7f23749fc411 in KisPaintDevice::Private::KisPaintDeviceStrategy::extent (this=0x6030025bf2e0) at /home/wolthera/krita/src/libs/image/kis_paint_device_strategies.h:55 #18 0x7f23749de493 in KisPaintDevice::extent (this=0x604001a78850) at /home/wolthera/krita/src/libs/image/kis_paint_device.cc:1207 #19 0x7f23749ef589 in KisPaintDeviceCache::exactBoundsAmortized (this=0x6140ed48) at /home/wolthera/krita/src/libs/image/kis_paint_device_cache.h:74 #20 0x7f23749de65f in KisPaintDevice::exactBoundsAmortized (this=0x604001a78850) at /home/wolthera/krita/src/libs/image/kis_paint_device.cc:1227 #21 0x7f23746ac948 in KisLayer::changeRect (this=0x607000351f60, rect=..., pos=KisNode::N_FILTHY) at /home/wolthera/krita/src/libs/image/kis_layer.cc:922 #22 0x7f23746c3252 in KisLayerProjectionPlane::changeRect (this=0x6025e330, rect=..., pos=KisNode::N_FILTHY) at /home/wolthera/krita/src/libs/image/kis_layer_projection_plane.cpp:114 #23 0x7f237459da7f in KisBaseRectsWalker::calculateChecksum (leaf=..., requestedRect=...) at /home/wolthera/krita/src/libs/image/kis_base_rects_walker.h:416 #24 0x7f23745f0b40 in KisBaseRectsWalker::checksumValid (this=0x6110016b9710) at /home/wolthera/krita/src/libs/image/kis_base_rects_walker.h:171 #25 0x7f23745ea178 in KisSimpleUpdateQueue::processOneJob (this=0x611000b27548, updaterContext=...) at /home/wolthera/krita/src/libs/image/kis_simple_update_queue.cpp:114 #26 0x7f23745e9f31 in KisSimpleUpdateQueue::processQueue (this=0x611000b27548, updaterContext=...) at /home/wolthera/krita/src/libs/image/kis_simple_update_queue.cpp:95 #27 0x7f23745fc3fc in KisUpdateScheduler::tryProcessUpdatesQueue (this=0x6130010cc460) at /home/wolthera/krita/src/libs/image/kis_update_scheduler.cpp:441 #28 0x7f23745fbfb7 in KisUpdateScheduler::processQueues (this=0x6130010cc460) at /home/wolthera/krita/src/libs/image/kis_update_scheduler.cpp:398 #29 0x7f23745fcc2a in KisUpdateScheduler::spareThreadAppeared (this=0x6130010cc460) at /home/wolthera/krita/src/libs/image/kis_update_scheduler.cpp:467 #30 0x7f23745b0bdc in KisUpdaterContext::jobFinished (this=0x611000b275a0) at
[krita] [Bug 405698] Vector graphic - lagging
https://bugs.kde.org/show_bug.cgi?id=405698 Boudewijn Rempt changed: What|Removed |Added Ever confirmed|0 |1 CC||b...@valdyas.org Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 385885] Multi-monitor HiDPI screens with scaling: Rectangular Region mode causes graphical corruption on one of the screens
https://bugs.kde.org/show_bug.cgi?id=385885 --- Comment #24 from Nils Rother --- Okay, thanks to your video I can now reproduce this issue. On my system it seems to occur when DPI scaling is enabled (using QT_SCALE_FACTOR=1.4 to test) and my left monitor is set to a lower resolution than my right monitor, which is similar to the configuration shown in your video. The whole overlayed rectangle selection interface seems to be shifted left or right, depending on which monitor is selected as the primary one. Note that this does NOT happen when my right monitor is set to a lower resolution than the left one or both are set to the same resolution. I don't know what configurations could cause issues if you have >2 monitors as I don't have the hardware to test that. I'm gonna peruse the code a bit, maybe I can figure out why this is happening... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399696] Forced close with Internal Error message in kis_shortcut_matcher.cpp, line 557 [USE_QT_XCB]
https://bugs.kde.org/show_bug.cgi?id=399696 --- Comment #13 from Dmitry Kazakov --- Hi, Tyson! Could you check the very latest AppImage? It looks like older builds had non-patched Qt in it, so the problem was not fixed completely. The latest AppImage seem to have this problem solved: https://binary-factory.kde.org/job/Krita_Nightly_Appimage_Build/ PS: I should still try to fix this problem for the distribution builds, but it is a separate task. -- You are receiving this mail because: You are watching all bug changes.
