[kwin] [Bug 405592] Kwin hangs randomly in _XReply()
https://bugs.kde.org/show_bug.cgi?id=405592 Paraddi changed: What|Removed |Added CC||spara...@gmail.com --- Comment #5 from Paraddi --- I was able to compile build libX11-1.6.9 from libX11-1.6.9.tar.gz in the https://www.x.org/releases/individual/lib/ and was able to build and freeze it by increasing the CPU load of the Qt Application by quickly switching two buttons in the HMI through touch. Other related components in the machine are as follows, Qt 5.9.7, KWIN 4.11.19-8, libXi 1.7.9-1 , xinput 1.6.2 and x11-server 1.20.1-5.6 [local@bues3-sun724 ~]$ pstack 2883 Thread 3 (Thread 0x7f994c3af700 (LWP 2885)): #0 0x7f995cafd20d in poll () from /lib64/libc.so.6 #1 0x7f995539c082 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f995539de6f in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f994eb6fe19 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7f995d85be71 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f995d2f6dd5 in start_thread () from /lib64/libpthread.so.0 #6 0x7f995cb07ead in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f9949d6b700 (LWP 3041)): #0 0x7f995cafd20d in poll () from /lib64/libc.so.6 #1 0x7f9958bf5c4c in g_main_context_iterate.isra.22 () from /lib64/libglib-2.0.so.0 #2 0x7f9958bf5d7c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f995da5445c in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f995da046db in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f995d8577f8 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f994eabb3b5 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x7f995d85be71 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f995d2f6dd5 in start_thread () from /lib64/libpthread.so.0 #9 0x7f995cb07ead in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f995ff27900 (LWP 2883)): #0 0x7f995d2fa965 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f995603a685 in _XReply (dpy=dpy@entry=0xb3dd60, rep=rep@entry=0x7ffcea17fbc0, extra=extra@entry=0, discard=discard@entry=1) at xcb_io.c:603 #2 0x7f995603cf33 in _XSeqSyncFunction (dpy=0xb3dd60) at XlibInt.c:224 #3 0x7f995603c753 in _XError (dpy=dpy@entry=0xb3dd60, rep=rep@entry=0x7f9944004500) at XlibInt.c:1493 #4 0x7f9956039867 in handle_error (dpy=0xb3dd60, err=0x7f9944004500, in_XReply=) at xcb_io.c:199 #5 0x7f9956039915 in handle_response (dpy=0xb3dd60, response=0x7f9944004500, in_XReply=) at xcb_io.c:324 #6 0x7f995603a75a in _XReply (dpy=0xb3dd60, rep=0x7ffcea17fdf0, extra=0, discard=0) at xcb_io.c:656 #7 0x7f994e69e2fe in XIQueryDevice () from /lib64/libXi.so.6 #8 0x7f994eb972bf in QXcbConnection::handleEnterEvent() () from /lib64/libQt5XcbQpa.so.5 #9 0x7f994eb82c47 in QXcbWindow::handleEnterNotifyEvent(int, int, int, int, unsigned char, unsigned char, unsigned int) () from /lib64/libQt5XcbQpa.so.5 #10 0x7f994eb83193 in QXcbWindow::handleXIEnterLeave(xcb_ge_event_t*) () from /lib64/libQt5XcbQpa.so.5 #11 0x7f994eb99f8c in QXcbConnection::xi2HandleEvent(xcb_ge_event_t*) () from /lib64/libQt5XcbQpa.so.5 #12 0x7f994eb6e2a2 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () from /lib64/libQt5XcbQpa.so.5 #13 0x7f994eb7019e in QXcbConnection::processXcbEvents() () from /lib64/libQt5XcbQpa.so.5 #14 0x7f995da2f1de in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #15 0x7f995e3fdd8c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #16 0x7f995e404f68 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #17 0x7f995da05be6 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #18 0x7f995da08503 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #19 0x7f995da54ab3 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #20 0x7f9958bf5969 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #21 0x7f9958bf5cc8 in g_main_context_iterate.isra.22 () from /lib64/libglib-2.0.so.0 #22 0x7f9958bf5d7c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #23 0x7f995da5445c in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #24 0x7f995da046db in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #25 0x7f995da0cc04 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #26 0x004263a9 in main () [local@bues3-sun724 ~]$ -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412867] Allow individual plasmoids/widgets to override tooltip settings
https://bugs.kde.org/show_bug.cgi?id=412867 --- Comment #2 from george fb --- I must be stupid, I'm sorry. At the moment you either have tooltips for every widget/plasmoid (task manager, tray etc) or none. It would be nice if some widgets, like the task manager, the system tray and maybe others (or even all), could override the setting "Display informational tooltips on mouse hover" in Desktop Behavior > Workspace. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412867] Allow individual plasmoids/widgets to override tooltip settings
https://bugs.kde.org/show_bug.cgi?id=412867 george fb changed: What|Removed |Added Summary|Allow individual|Allow individual |plasmoids/widgets to|plasmoids/widgets to |overwrite tooltip settings |override tooltip settings --- Comment #1 from george fb --- Pressed enter by mistake, sorry. At the moment you either have tooltips for every widget/plasmoid (task manager, tray etc) or none. It would be nice if some widgets could override -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412867] Allow individual plasmoids/widgets to overwrite tooltip settings
https://bugs.kde.org/show_bug.cgi?id=412867 george fb changed: What|Removed |Added Summary|Allow individual|Allow individual |plasmoids/widgets |plasmoids/widgets to ||overwrite tooltip settings -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412867] New: Allow individual plasmoids/widgets
https://bugs.kde.org/show_bug.cgi?id=412867 Bug ID: 412867 Summary: Allow individual plasmoids/widgets Product: systemsettings Version: 5.16.5 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: georgefb...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Solus 4.0 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412828] Color selector crashed the program
https://bugs.kde.org/show_bug.cgi?id=412828 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 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.
[dolphin] [Bug 411754] Dolphin crash when opening pdf file with Okular
https://bugs.kde.org/show_bug.cgi?id=411754 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.
[dolphin] [Bug 411718] Dolphin shows the wrong file type for Python
https://bugs.kde.org/show_bug.cgi?id=411718 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 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.
[skrooge] [Bug 412360] All items entered are gone
https://bugs.kde.org/show_bug.cgi?id=412360 --- Comment #24 from Dave --- But all this is doing is reinstalling ver. 2.15.0 The flash on the screen when l begin the process indicates 2.20.0 but what loads is 2.15.0The third line of code up from the bottom clearly shows.. skrooge-kf5 is already the newest version (2.15.0-0ubuntu1~ppa1). is there not updated code?Dave dave@linuxmint18 ~ $ sudo apt-get updateIgn:1 http://packages.linuxmint.com sylvia InReleaseHit:2 http://packages.linuxmint.com sylvia Release Ign:3 http://dl.google.com/linux/chrome/deb stable InRelease Hit:4 http://dl.google.com/linux/chrome/deb stable Release Hit:5 http://security.ubuntu.com/ubuntu xenial-security InRelease Hit:7 http://archive.canonical.com/ubuntu xenial InRelease Hit:8 http://ppa.launchpad.net/s-mankowski/ppa-kf5/ubuntu xenial InRelease Hit:9 https://repo.skype.com/deb stable InRelease Hit:10 http://archive.ubuntu.com/ubuntu xenial InReleaseHit:12 http://archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:13 http://archive.ubuntu.com/ubuntu xenial-backports InRelease Reading package lists... Done dave@linuxmint18 ~ $ sudo apt-get install skrooge-kf5Reading package lists... DoneBuilding dependency tree Reading state information... Doneskrooge-kf5 is already the newest version (2.15.0-0ubuntu1~ppa1).0 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.dave@linuxmint18 ~ $ sudo apt-get install skrooge-kf5 On Friday, October 11, 2019, 04:24:37 p.m. EDT, Stephane MANKOWSKI wrote: https://bugs.kde.org/show_bug.cgi?id=412360 --- Comment #23 from Stephane MANKOWSKI --- Remove this version from Flathub.org and install "skrooge-kf5". You just have to search "skrooge-kf5" and install it. -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 412234] Feature request: display time since the last delayed short and long breaks + time until the next short and long breaks
https://bugs.kde.org/show_bug.cgi?id=412234 --- Comment #3 from jpg --- The only tooltip I have is the name of the software that is "RSIBreak". "the time since the last short and the last long breaks that are delayed" is useful to see if I bypassed too longer the last breaks. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 412866] New: Archive won't delete after X articles
https://bugs.kde.org/show_bug.cgi?id=412866 Bug ID: 412866 Summary: Archive won't delete after X articles Product: akregator Version: GIT (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: rexthec...@gmail.com Target Milestone: --- SUMMARY My default archive setting is to delete articles older than 365 days and do not expire important articles. I did subscribe to a feed that posts like 500 articles every day, I do not have time to read all those. When I did set that one feed's archive setting to limit archive to 200 articles it did not work. The article count keep going up long after 200. STEPS TO REPRODUCE 1. Set Akregator's default archive setting to 365 days. 2. Subscribe to an article that posts very often. 3. Set that feed's settings to a limit of 200. OBSERVED RESULT The feed's archive setting is ignored. EXPECTED RESULT I expect the feed's article number never goes above 200 if the settings is set to that. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 19.04 GNOME: 3.32.1 OS type: 64-bit Virtualization: VMware ADDITIONAL INFORMATION Tested the bug on an clean VM, got the exact same bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392731] Allow two clicks to rename items like in Dolphin
https://bugs.kde.org/show_bug.cgi?id=392731 ber...@codewiz.org changed: What|Removed |Added CC||ber...@codewiz.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412865] New: Memory leak when spamming notifications
https://bugs.kde.org/show_bug.cgi?id=412865 Bug ID: 412865 Summary: Memory leak when spamming notifications Product: plasmashell Version: 5.16.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: danc...@disroot.org CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When notifications is being spammed, memory will leak. STEPS TO REPRODUCE Since notify-send is slow, I'll use notifications from Accessibility. 1. Enable notifications for modifiers and locking keys 2. Enable notification pop-ups for modifier keys when it's active and inactive 3. Play around with the keys 4. Check plasmashell memory usage OBSERVED RESULT Memory is being leaked, even when notifications being cleared, still cannot free the memory being used. I was able to get plasmashell to use up to a GB of RAM. EXPECTED RESULT Memory being freed as soon the notifications are cleared. SOFTWARE/OS VERSIONS Distro: Arch Linux Kernel: 4.19.78-1-lts KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION None -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 412864] Latte dock crashed when changing layout
https://bugs.kde.org/show_bug.cgi?id=412864 Karmanyaah Malhotra changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED Platform|unspecified |Archlinux Packages --- Comment #1 from Karmanyaah Malhotra --- Rebooted and it works -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 412864] New: Latte dock crashed when changing layout
https://bugs.kde.org/show_bug.cgi?id=412864 Bug ID: 412864 Summary: Latte dock crashed when changing layout Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: karmanya...@gmail.com Target Milestone: --- Application: latte-dock (0.9.3) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 5.3.5-arch1-1-ARCH x86_64 Distribution: "EndeavourOS Linux" -- Information about the crash: - What I was doing when the application crashed: When I was changing the layout from either the right click menu and the customize layouts menu, Latte crashed. The crash can be reproduced every time. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f185def9e40 (LWP 19673))] Thread 6 (Thread 0x7f183700 (LWP 19693)): #0 0x7f18619a0c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1862b41660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f1862b41752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f1864815dad in () at /usr/lib/libQt5Quick.so.5 #4 0x7f186481605e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f1862b3b5b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f186199a4cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f18626672d3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f184ee22700 (LWP 19688)): #0 0x7f18619a0c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f184f44366c in () at /usr/lib/dri/i965_dri.so #2 0x7f184f443268 in () at /usr/lib/dri/i965_dri.so #3 0x7f186199a4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f18626672d3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f1855633700 (LWP 19687)): #0 0x7f186265c9ef in poll () at /usr/lib/libc.so.6 #1 0x7f1860a6e180 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1860a6e251 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f1862d61a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1862d084ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f1862b3a385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f18644ac849 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f1862b3b5b0 in () at /usr/lib/libQt5Core.so.5 #8 0x7f186199a4cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f18626672d3 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f1857fff700 (LWP 19680)): #0 0x7f186265c9ef in poll () at /usr/lib/libc.so.6 #1 0x7f1860a6e180 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1860a6e251 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f1862d61a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1862d084ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f1862b3a385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f1862ff2b37 in () at /usr/lib/libQt5DBus.so.5 #7 0x7f1862b3b5b0 in () at /usr/lib/libQt5Core.so.5 #8 0x7f186199a4cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f18626672d3 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f185d0f0700 (LWP 19676)): #0 0x7f186265c9ef in poll () at /usr/lib/libc.so.6 #1 0x7f1864c33630 in () at /usr/lib/libxcb.so.1 #2 0x7f1864c352db in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f185dab6101 in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7f1862b3b5b0 in () at /usr/lib/libQt5Core.so.5 #5 0x7f186199a4cf in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f18626672d3 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f185def9e40 (LWP 19673)): [KCrash Handler] #5 0x55fb60ce97f6 in Latte::Corona::availableScreenRectWithCriteria(int, QList, QList) const () #6 0x55fb60dcca83 in Latte::WindowSystem::Tracker::Windows::updateAvailableScreenGeometries() () #7 0x7f1862d35b70 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #8 0x7f1862d35b70 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #9 0x55fb60cd6e63 in Latte::Corona::availableScreenRectChangedFrom(Latte::View*) () #10 0x7f1862d35b70 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #11 0x55fb60ce1b8b in Latte::ViewPart::Effects::qt_metacall(QMetaObject::Call, int, void**) () #12 0x7f186440a346 in QQmlPropertyPrivate::write(QObject*, QQmlPropertyData const&, QVariant const&, QQmlContextData*, QFlags) () at
[krita] [Bug 412844] When you place any layer right below the 'group layer', it doesn't go inside the group
https://bugs.kde.org/show_bug.cgi?id=412844 --- Comment #4 from acc4commissi...@gmail.com --- (In reply to Ahab Greybeard from comment #3) > Logically, I can think of two situations where it's useful to have these two > different actions. Mind if I ask what it might be? I do think it's good to have separation at below the whole group. So that we can decide whether we put the layer inside or outside. But when we put the layer right below the top 'group category layer', it should always go inside the group, I think. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409748] Brush preset docker/dropdown only saves las used tag if when quiting krita the tag is not set to "All".
https://bugs.kde.org/show_bug.cgi?id=409748 acc4commissi...@gmail.com changed: What|Removed |Added CC||acc4commissi...@gmail.com --- Comment #7 from acc4commissi...@gmail.com --- Did you try resetting krita by deleting kritarc file? I had the exact same issue and deleting the file fixed it. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 Patrick Silva changed: What|Removed |Added CC||heire...@exherbo.org --- Comment #11 from Patrick Silva --- *** Bug 412863 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412863] Checkboxes and radio buttons have the wrong colors with non-dark Breeze
https://bugs.kde.org/show_bug.cgi?id=412863 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com --- Comment #4 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 412078 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 407409] Discover lists Snap packages without icon in search results
https://bugs.kde.org/show_bug.cgi?id=407409 --- Comment #5 from Patrick Silva --- Created attachment 123152 --> https://bugs.kde.org/attachment.cgi?id=123152=edit screen recording on neon unstable -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 407409] Discover lists Snap packages without icon in search results
https://bugs.kde.org/show_bug.cgi?id=407409 Patrick Silva changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #4 from Patrick Silva --- This bug is not completelly fixed. Sometimes the app icon only appears after I hover over the snap package listed in the search resuls and then move the cursor outside it. I recorded a video on Neon unstable edition showing this behavior. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 133927] Tileable windows with split bar between them
https://bugs.kde.org/show_bug.cgi?id=133927 Nate Graham changed: What|Removed |Added Keywords||usability Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 133927] Tileable windows with split bar between them
https://bugs.kde.org/show_bug.cgi?id=133927 Nate Graham changed: What|Removed |Added CC||matejm98m...@gmail.com --- Comment #6 from Nate Graham --- *** Bug 397095 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 133927] Tileable windows with split bar between them
https://bugs.kde.org/show_bug.cgi?id=133927 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|RESOLVED|REPORTED Resolution|DUPLICATE |--- --- Comment #5 from Nate Graham --- Not really a duplicate. The requested feature is one that almost every other platform has at this point so I don't think it's unreasonable to have a bug report that tracks implementing it natively in KWin, without needing any 3rd party scripts. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397095] When 2 apps are tiled on a screen, resizing one could also resize the other...
https://bugs.kde.org/show_bug.cgi?id=397095 Nate Graham changed: What|Removed |Added Resolution|INTENTIONAL |DUPLICATE CC||n...@kde.org --- Comment #2 from Nate Graham --- *** This bug has been marked as a duplicate of bug 133927 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) writing a *ton* of data while re-indexing unchanged files
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #38 from Kai Krakow --- (In reply to Martin Steigerwald from comment #35) > I like the idea to use one DB per filesystem. This way you can save the > complete filesystem UUID and/or other identifying information *once* and use > the full 64 bit for the inode number thing. Such things are always difficult (the same for your hidden ID file in the root of an FS): It requires permissions you may not have, thus you may decide to use the most top-level directory you have write permissions to. And at that point I'd define that the storage path is undefined. Other solution: Name the index files by UUID and store it at a defined location. We'll have other problems now: Do you really want multiple multi-GB mmaps LMDB files mapped at once in RAM? With even more chaotic random access patterns (and their potential to push your precious cache out of memory)? Also, multi-file databases are hard to sync with each other: At some point we may need to ensure integrity between all the files. This won't end well. I'm all in for a single-DB approach. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) writing a *ton* of data while re-indexing unchanged files
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #37 from Martin Steigerwald --- It is probably too late for me or I am not into programming enough at the moment, to fully understand what you propose. :) May be something to bring to the suitable Phabricator tasks, maybe Overhaul Baloo database scheme: https://phabricator.kde.org/T9805 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412863] Checkboxes and radio buttons have the wrong colors with non-dark Breeze
https://bugs.kde.org/show_bug.cgi?id=412863 --- Comment #2 from Heiko Becker --- Created attachment 123150 --> https://bugs.kde.org/attachment.cgi?id=123150=edit gtk3_preview 1 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412863] Checkboxes and radio buttons have the wrong colors with non-dark Breeze
https://bugs.kde.org/show_bug.cgi?id=412863 --- Comment #3 from Heiko Becker --- Created attachment 123151 --> https://bugs.kde.org/attachment.cgi?id=123151=edit gtk3_preview 2 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412863] Checkboxes and radio buttons have the wrong colors with non-dark Breeze
https://bugs.kde.org/show_bug.cgi?id=412863 --- Comment #1 from Heiko Becker --- Created attachment 123149 --> https://bugs.kde.org/attachment.cgi?id=123149=edit screenshot firefox 2 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412863] New: Checkboxes and radio buttons have the wrong colors with non-dark Breeze
https://bugs.kde.org/show_bug.cgi?id=412863 Bug ID: 412863 Summary: Checkboxes and radio buttons have the wrong colors with non-dark Breeze Product: Breeze Version: 5.16.90 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: uhh...@gmail.com Reporter: heire...@exherbo.org Target Milestone: --- Created attachment 123148 --> https://bugs.kde.org/attachment.cgi?id=123148=edit screenshot firefox 1 They don't have the familiar blue but instead they are coloured black. Sometimes the blue appears on mouse-over and stays, but the behaviour seems a bit unpredictable. I'll attach two examples from firefox and two from gtk3_preview SOFTWARE/OS VERSIONS KDE Plasma Version: 5.16.90 (also present in 5.17.0) KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 404372] App icon is not loaded when I open a Snap url for the first time
https://bugs.kde.org/show_bug.cgi?id=404372 --- Comment #5 from Patrick Silva --- (In reply to Aleix Pol from comment #3) > Are you sure it's not the same issue as this? (also yours) > https://bugs.kde.org/show_bug.cgi?id=407409 Maybe. Bug 407409 is not completelly fixed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412828] Color selector crashed the program
https://bugs.kde.org/show_bug.cgi?id=412828 --- Comment #2 from nya.thecuteness.na...@gmail.com --- I apologize for my ill informed critic, I was unaware that there were multiple color sets that could be displayed and as a result when I updated the program assumed it was altered upon seeing a different set of colors than what i was used to. I discovered it shortly after the bug report so it was a bit late to take back my comment. Anyways I attached the kritacrash.log file you asked for and hope it provides information that can make the program a bit more stable. I would like to add that this is the only time its happened and couldve just been a fluke caused by my laptop failing to execute the process properly If it couldnt be told by my lack of knowledge on the program, Im fairly new to it and still discovering things so please disregard any snarky comments in my initial report On Fri, Oct 11, 2019 at 3:55 AM Boudewijn Rempt wrote: > https://bugs.kde.org/show_bug.cgi?id=412828 > > Boudewijn Rempt changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > CC||b...@valdyas.org > Component|Tools/Colorize |Color Selectors >Platform|Other |MS Windows > > --- Comment #1 from Boudewijn Rempt --- > The configuration panel for the color selector hasn't changed in many > years -- > so I don't understand your "like it used to be". > > Please try to find the kritacrash.log file in %APPDATA%\local and attach > it to > this bug; then we might be able to figure out what happened. Right now, > your > description does not provide enough information to try and debug the > problem. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 404372] App icon is not loaded when I open a Snap url for the first time
https://bugs.kde.org/show_bug.cgi?id=404372 --- Comment #4 from Patrick Silva --- (In reply to Patrick Silva from comment #2) > sometimes the app icon is never loaded. Some examples below: > > https://snapcraft.io/konversation > > https://snapcraft.io/handbrake-jz > > Operating System: KDE neon Unstable Edition > KDE Plasma Version: 5.16.80 > KDE Frameworks Version: 5.63.0 > Qt Version: 5.12.3 On Neon unstable edition, icons of konversion and handbrake appear after I swith to another window (Opera browser in my case) and switch back to Discover. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) writing a *ton* of data while re-indexing unchanged files
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #36 from Kai Krakow --- Oh, nice... Sometimes it helps to talk about a few things. I could think of the following solution: Add another UUID->CounterID mapping table to the database, that is easy to achieve. Everytime we encounter a new UUID, we increase the CounterID one above the maximum value in the DB and use that as a file system identifier. We can now bit-reverse the CounterID so that the least-significant bits switch position with the highest. The result will be XOR'ed with the 64-bit inode number. Et voila: There's a DocID. What do you think? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) writing a *ton* of data while re-indexing unchanged files
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #35 from Martin Steigerwald --- I like the idea to use one DB per filesystem. This way you can save the complete filesystem UUID and/or other identifying information *once* and use the full 64 bit for the inode number thing. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) writing a *ton* of data while re-indexing unchanged files
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #34 from Martin Steigerwald --- I would not worry all that much about redoing the database for a format change. In the end what we have now that it re-indexes anyway. And yes, I have a multi device BTRFS. Actually a BTRFS RAID 1. I wonder whether Baloo would be better off by using filesystem UUID together with 64 bit inode number as an identifier. However using a complete filesystem UUID may need too much storage, I don't know. Another idea would be to mark each indexed file with an kind of ID or timestap using extended attributes. However, that might get lost as well and it won't work on filesystems not supporting those. A third idea would be to write an 32 bit identifier as a filesystem ID into a hidden file below the root directory of the filesystem or a hidden sub directory of it. This would at least avoid using an identifier that could change. It would not solve the 32 bit for inode number not enough for storing a 64 bit inode number issue. However this might be a change that might be easiest to apply short term. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 412861] WebEngine crashes, KHTML not for daily usage
https://bugs.kde.org/show_bug.cgi?id=412861 Allan Sandfeld changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||k...@carewolf.com --- Comment #1 from Allan Sandfeld --- You are using a buggy OpenGL driver, and said driver crashes: Use one that isn't buggy. Note if you use Qt 5.12, QtWebEngine would automatically disable OpenGL with said driver because it is so buggy, if you use 5.13, it would switch to single-threaded mode and work around the bugs. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) writing a *ton* of data while re-indexing unchanged files
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #33 from Kai Krakow --- Also, LMDB is totally the wrong tool when using 32-bit systems because your index cannot grow beyond a certain size before crashing baloo. I'm not sure if 32-bit systems are still a thing - but if they are, the decision for LMDB was clearly wrong. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) writing a *ton* of data while re-indexing unchanged files
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #32 from Kai Krakow --- (In reply to Martin Steigerwald from comment #30) > I believe this bug is at > least about two or three independent issues, but as you told, let's have it > about the re-indexing files thing. I bet getting rid of needlessly > re-indexing files will be one of the most effective to sort out performance > issues with Baloo. I changed bug subject accordingly. That's why I started a task to better distinguish between which problem is what in Phabricator: https://phabricator.kde.org/T11859 And that's why I suggested a few comments ago to concentrate on fixing the re-indexing bug first. But it turned out to be not that easy. Together with the other performance issues and especially the tight coupling of mmap, access patterns, and available memory, I think it's worth rethinking if LMDB is still the right tool: mmap introduces a lot of problems and there's no easy way around it. There's to many things to think of to optimize access patterns then. It's unlikely to be done anytime when looking at the problems exposed by the database scheme already. LMDB seems to be designed around the idea to be the only user of system RAM, or at least only use a very smallish part of it (which may not be that small if you have huge amounts of RAM). That's unlikely to be the situation on systems where baloo is used. Bad design choices have already been made and been meshed deeply into the database scheme, which makes it difficult to migrate existing installations. BTW: Following up on your comment #2 was totally unintentional but actually I followed up and explained why that happens. ;-) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) writing a *ton* of data while re-indexing unchanged files
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #31 from Kai Krakow --- As far as I understand from researching the discussions in phabricator, this problem won't be easy to fix as it is baked into the design decision that defined the database scheme. Based on the fact that the DocId (which is used to find if a file still exists, or changed, or just moved unmodified) is a 64-bit value which is actually made of a 32-bit st_dev (device id) and 32-bit ino (inode number), I see two problems here: 1. btrfs uses 64-bit inode numbers, at some point, numbers will overflow and the baloo database becomes confused. 2. multi-dev btrfs (and I think you also use that, as I do) may have an unstable st_dev number across reboots, resulting in changed DocIds every once in a while after reboot The phabricator discussions point out that other (primarily network) file systems suffer the same problem: They have unstable st_dev values maybe even after reconnect. User space file systems even depend on mount order for the st_dev value. Changing this is no easy task, it would require a format change which either invalidates your DB, or it needs migration. So I'm currently evaluating if it makes sense to switch to a key/value store that doesn't rely on mmap (as it has clear downsides on a typical desktop system). This would allow to easily change the database scheme in the same step as the index would've to be recreated anyways. I'm currently digging my nose into Facebook's RocksDB, it looks mostly good except that it was optimized solely around flash-based storage. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412862] The graphics tablet, won't work after upgrade to Catalina, only with this software.
https://bugs.kde.org/show_bug.cgi?id=412862 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|RESOLVED CC||b...@valdyas.org Resolution|--- |UPSTREAM --- Comment #1 from Boudewijn Rempt --- I'm sorry, but there is _no_ tablet specific code in Krita for macOS. If there is a problem on Catalina, it's either a bug in Catalina, or a problem with the tablet driver. We cannot do anything here. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412862] New: The graphics tablet, won't work after upgrade to Catalina, only with this software.
https://bugs.kde.org/show_bug.cgi?id=412862 Bug ID: 412862 Summary: The graphics tablet, won't work after upgrade to Catalina, only with this software. Product: krita Version: 4.2.7 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: critical Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: riccardoplatan...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Catalina Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION After upgraded my Mac to Catalina, my graphics tablet stop to work with this software. Please, can you fix this problem? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 412745] Support macOS Catalina (10.15)
https://bugs.kde.org/show_bug.cgi?id=412745 riccardoplatan...@gmail.com changed: What|Removed |Added CC||riccardoplatan...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) writing a *ton* of data while re-indexing unchanged files
https://bugs.kde.org/show_bug.cgi?id=404057 Martin Steigerwald changed: What|Removed |Added Summary|Uses an insane amount of|Uses an insane amount of |memory (RSS/PSS) and writes |memory (RSS/PSS) writing a |a *ton* of data while |*ton* of data while |indexing|re-indexing unchanged files --- Comment #30 from Martin Steigerwald --- (In reply to Kai Krakow from comment #28) > (In reply to Kai Krakow from comment #19) […] > Following up with more details: > > The problem seems to be the following: > > After reboot, the indexer finds all files as changed. For every file in the > index, it will log to stdout/stderr: > > "path to file" id seems to have changed. Perhaps baloo was not running, and > this file was deleted + re-created Kai, please see my comment #2 of this bug report: https://bugs.kde.org/show_bug.cgi?id=404057#c2 I got exactly the same message. Just have been rereading what I wrote as I have not been aware of it anymore. So yes, that is indeed an important issue here. I believe this bug is at least about two or three independent issues, but as you told, let's have it about the re-indexing files thing. I bet getting rid of needlessly re-indexing files will be one of the most effective to sort out performance issues with Baloo. I changed bug subject accordingly. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) and writes a *ton* of data while indexing
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #29 from Kai Krakow --- During the re-index job after reboot, baloo shows very strange behavior when evaluating the indexSize: $ balooctl indexSize File Size: 6,83 GiB Used: 25,48 MiB PostingDB: 1.018,96 MiB 3998.360 % PositionDB: 1,73 GiB 6957.158 % DocTerms: 909,35 MiB 3568.271 % DocFilenameTerms: 131,17 MiB 514.700 % DocXattrTerms: 4,00 KiB 0.015 % IdTree: 31,09 MiB 121.980 % IdFileName: 107,08 MiB 420.172 % DocTime: 67,19 MiB 263.642 % DocData: 67,14 MiB 263.473 % ContentIndexingDB: 3,99 MiB15.650 % FailedIdsDB:0 B 0.000 % MTimeDB: 12,53 MiB49.172 % Also, "File Size" increases with every reboot while "Used" stays around the same when compared after baloo has decided to idle. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 412226] KBibTeX crashes when closing after saving
https://bugs.kde.org/show_bug.cgi?id=412226 Thomas Fischer changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Thomas Fischer --- I have not been able to reproduce this crash. Any ideas how to reproduce this crash without keeping KBibTeX a few days open? Also, to get more details, I recommend to launch KBibTeX from the command line and append the output of the last 20 lines or so. For example, File::property mentioned in the crash report prints out a warning if it thinks there is something wrong. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 412861] New: WebEngine crashes, KHTML not for daily usage
https://bugs.kde.org/show_bug.cgi?id=412861
Bug ID: 412861
Summary: WebEngine crashes, KHTML not for daily usage
Product: konqueror
Version: unspecified
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: konq-b...@kde.org
Reporter: tigrank2...@gmail.com
Target Milestone: ---
Hello there, I installed Debian 10 and Konqueror does not work with WebEngine
I tried the following
1. Open General Konqueror settings
2. Switch to KHTML
3. Log out and back in
Well, as I expected, it worked! But still, I do not want to use KHTML as a web
browser engine, I switched the settings back, I ran konqueror from terminal and
it gave me this:
_
KonqFrame(0x5571e4630f60) QObject(0x0)
Normal history navigation logic failed! Falling back to opening url directly.
QUrl("https://www.google.com/search?source=hp=S-OgXfTsHKiMrwSgkIb4Dw=hello=hello_l=psy-ab.3..0i19l10.13871.15348..15591...0.0..0.109.453.3j2..01..gws-wiz...0i324j0i3j0i30.ZJ6gQXYLVdU=0ahUKEwi0vvmhg5XlAhUoxosKHSCIAf8Q4dUDCAc=5;)
[1413:1433:1012/002320.337061:ERROR:nss_util.cc(727)] After loading Root Certs,
loaded==false: NSS error code: -8018
QObject::connect: No such signal ValidatorsDialog::okClicked()
QObject::connect: No such signal ValidatorsDialog::cancelClicked()
QObject::connect: No such signal ValidatorsDialog::okClicked()
QObject::connect: No such signal ValidatorsDialog::cancelClicked()
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1204, resource
id: 20975682, major code: 40 (TranslateCoords), minor code: 0
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
konqueror: ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Assertion `kref'
failed.
Received signal 6
#0 0x7ffa2b96cbde
#1 0x7ffa2b96ccf0
#2 0x7ffa2b96d327
#3 0x7ffa51541840
#4 0x7ffa515417bb gsignal
#5 0x7ffa5152c535 abort
#6 0x7ffa5152c40f
#7 0x7ffa5153a102 __assert_fail
#8 0x7ffa3f5c159f nouveau_pushbuf_data
#9 0x7ffa3f5c1503 nouveau_pushbuf_data
#10 0x7ffa3f5c162f
#11 0x7ffa3f5c1a7f
#12 0x7ffa3f5c2670 nouveau_pushbuf_kick
#13 0x7ffa43365db6
#14 0x7ffa434e88af
#15 0x7ffa430c3b37
#16 0x7ffa482a1243
#17 0x7ffa49acb146
#18 0x7ffa4fbd9c4b QOpenGLContext::swapBuffers()
#19 0x7ffa4fe6dc74 QPlatformBackingStore::composeAndFlush()
#20 0x7ffa49996e94
#21 0x7ffa50181ad3
#22 0x7ffa50183504
#23 0x7ffa50184b12
#24 0x7ffa50184e69
#25 0x7ffa5019ba35 QWidgetPrivate::syncBackingStore()
#26 0x7ffa501b36b8 QWidget::event()
#27 0x7ffa502b9de4 QMainWindow::event()
#28 0x7ffa50c7017b KMainWindow::event()
#29 0x7ffa50cba115 KXmlGuiWindow::event()
#30 0x7ffa51759d4c KonqMainWindow::event()
#31 0x7ffa501754b1 QApplicationPrivate::notify_helper()
#32 0x7ffa5017c950 QApplication::notify()
#33 0x7ffa4f7a15a9 QCoreApplication::notifyInternal2()
#34 0x7ffa4f7a459b QCoreApplicationPrivate::sendPostedEvents()
#35 0x7ffa4f7f3233
#36 0x7ffa4d34ef2e g_main_context_dispatch
#37 0x7ffa4d34f1c8
#38 0x7ffa4d34f25c g_main_context_iteration
#39 0x7ffa4f7f2863 QEventDispatcherGlib::processEvents()
#40 0x7ffa49a0b3e1
#41 0x7ffa4f7a027b QEventLoop::exec()
#42 0x7ffa4f7a8262 QCoreApplication::exec()
#43 0x7ffa517a2729 kdemain
#44 0x7ffa5152e09b __libc_start_main
#45 0x5571e2f3c08a _start
r8: r9: 7fffd4a36220 r10: 0008 r11:
0246
r12: 7ffa3f5c4052 r13: 7ffa3f5c4068 r14: 02d3 r15:
di: 0002 si: 7fffd4a36220 bp: 7ffa5168eee0 bx:
0006
dx: ax: cx: 7ffa515417bb sp:
7fffd4a36220
ip: 7ffa515417bb efl: 0246 cgf: 002b0033 erf:
trp: msk: cr2:
[end of stack trace]
Calling _exit(1). Core file will not be generated.
_
I thought KHTML would be a good web alternative, but I cannot use it and
WebEngine does not work properly
SOFTWARE/OS VERSIONS
Windows: not
macOS: not
Linux/KDE Plasma: Debian 10 buster x86_64 Linux 4.19.0-6-amd64
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-solid] [Bug 394348] Umounting mounted disk image (e.g. .iso file) does not remove it from Device Notifier
https://bugs.kde.org/show_bug.cgi?id=394348 --- Comment #78 from Nick Stefanov --- I noticed something interesting - if I unmount the previously mounted disk via device notifier or Dolphin and I close Dolphin, the mounted image is gone from the side bar's devices section after I open Dolphin again. But the device isn't released and no image can be mounted until I unmount the previous image via CDEmu or restart. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412769] It's impossible to unlock session
https://bugs.kde.org/show_bug.cgi?id=412769 Antonio Rojas changed: What|Removed |Added CC||rull...@gmail.com --- Comment #2 from Antonio Rojas --- *** Bug 412855 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 412855] Cannot unlock a plasma session
https://bugs.kde.org/show_bug.cgi?id=412855 Antonio Rojas changed: What|Removed |Added Resolution|--- |DUPLICATE CC||aro...@archlinux.org Status|REPORTED|RESOLVED --- Comment #1 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 412769 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) and writes a *ton* of data while indexing
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #28 from Kai Krakow --- (In reply to Kai Krakow from comment #19) > After testing this a few days, with my patches it works flawlessly: No > performance impact, krunner finds result immediately without thrashing the > HDD, etc. That is, until you reboot: While with the patches it has no longer > any perceived negative impact on desktop responsiveness, I see that Baloo > still re-indexes all files. > > Steps to reproduce: > > 1. Start baloo for the first time (aka "remove your index") > 2. Let it complete a full indexing cycle > 3. Observe "balooctl indexSize" to see that there's no file left to index > 4. Also observe that it has data in "ContentIndexingDB" > 5. Reboot > 6. Observe "balooctl indexSize" to see that "ContentIndexingDB" changed back >to 0 bytes > 7. Observe "balooctl status" and wait until it finished checking for missing >files > 8. Observe both commands to see how baloo now refills the ContentIndexingDB >and adds all your files to the index again, resulting in double the amount >of files after finishing the second run > 9. From now on, on every reboot, the index only grows, constantly forgetting >the ContentIndexDB and re-adding all files. > > This behavior is with and without my patches. > > @Martin Is this what you've seen, too? Following up with more details: The problem seems to be the following: After reboot, the indexer finds all files as changed. For every file in the index, it will log to stdout/stderr: "path to file" id seems to have changed. Perhaps baloo was not running, and this file was deleted + re-created This results in a lot of transactions to the database, blowing it up in size (due to its lock-free implementation it appends to the database before freeing the old data) and creating high IO pressure due to a lot of fsync calls going on in short succession. What follows: After removing all the seemingly changed files from the database, it re-indexes all those files. This in turn appends to the database again it seems, probably because its unlikely to find big enough "holes" at the beginning of the database: Although a lot of data has been removed, it has probably been filled with meta data updates, leaving no space to put back in the content index data. This access patterns adds up after some time, spreading out data more and more, leading to very random access patterns. The kernel will start to struggle with the mmap because it constantly swaps in new pages: Due to the random and wide spread access patterns, it becomes more and more less likely that memory pages are already swapped in. Access behavior becomes more and more seeky, the database contents could be said to be too fragmented. This will introduce high desktop latency because baloo will start to dominate the cache with its mmap. After all, we should keep in mind that LMDBs design is made for systems primarily running only the database, but not mixed with desktop workloads. The phabricator site already has some valuable analysis and ideas of this which I collected here: https://phabricator.kde.org/T11859 Thinks that currently help here a lot: - Remove fsync from baloo via patch (this seems to have the biggest impact) - Limiting the working set memory baloo can use by using cgroups Removing fsync from baloo could mean that the database is not crash-safe. Thus, I suggest to not use my fsync patch upstream until extensive testing of such situations (I do not know how to do that, it's a tedious task depending on a vast amount of factors) or until someone comes up with some clever recovery/transaction idea. Maybe the LMDB author has some more insight on this. Limiting memory with cgroups helps because cgroups can limit RAM usage by accounting for both heap and cache usage: It effectively hinders baloo from dominating the cache and thus impacting desktop performance too much. The read-ahead patch reduces additional pressure on the cache occupancy. It should also be possible to use madvise()/fadvise() to actively instruct the kernel that baloo no longer uses some memory or doesn't plan on doing so in the future. I'm not sure if baloo and/or LMDB use these functions or how they use them. Also, I wonder if LMDB uses MAP_HUGETLB. It may be worth checking if flipping this setting improves or worsens things because I can think of different scenarios: 1. hugetlb uses 2 MB page size which could reduce the IOPS needed to work on spatially near data in the DB (good) 2. 2 MB page size could increase the IO throughput needed when paging DB data in, thus negatively impacting the rest of the system (bad) 3. LMDB should grow the database in bigger chunks to reduce external fragmentation of the index file, hugetlb could help that (undecided) 4. hugetlb with very random, spread-out access patterns could increase the memory pressure (bad) 5. 4k pages with very random access patterns could reduce memory pressure
[skrooge] [Bug 412831] Filter for custom properties have to be prefixed with v_operation_display_all
https://bugs.kde.org/show_bug.cgi?id=412831 Stephane MANKOWSKI changed: What|Removed |Added Status|REPORTED|ASSIGNED Assignee|guillaume.deb...@gmail.com |steph...@mankowski.fr Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 412360] All items entered are gone
https://bugs.kde.org/show_bug.cgi?id=412360 --- Comment #23 from Stephane MANKOWSKI --- Remove this version from Flathub.org and install "skrooge-kf5". You just have to search "skrooge-kf5" and install it. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 340748] Disable auto-WHO for Twitch servers.
https://bugs.kde.org/show_bug.cgi?id=340748 --- Comment #6 from Eike Hein --- Could be, if the Twitch server announces some sort of cap bit related to this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412860] Mouse pointer randomly appearing when pop up shows up
https://bugs.kde.org/show_bug.cgi?id=412860 --- Comment #1 from Manga Tengu --- in case this doesn't show in the ticket (I fill the form though...) This is on macOS mojave latest + Krita 4.2.7.1 but the problem is not new at all. Just had a hard time to pin point it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412860] New: Mouse pointer randomly appearing when pop up shows up
https://bugs.kde.org/show_bug.cgi?id=412860 Bug ID: 412860 Summary: Mouse pointer randomly appearing when pop up shows up Product: krita Version: 4.2.7-beta1 Platform: Other OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- SUMMARY Mouse pointer randomly appearing on the brush outline after popup appears. STEPS TO REPRODUCE 1. Set cursor shape to no cursor in preferences. Now when using the brush you shouldn't see the mouse cursor 2. While still using the brush tool, for example cmd+O to display the open... pop up reproduces quite well the problem 3. Close the pop up. Sometimes you still have the cursor stuck on your brush shape (doesn't always work so you need to repeat a few times if it doesn't) OBSERVED RESULT You have a mouse cursor stuck in the middle of your brush shape. To get rid of it I need to get the cursor out of the canvas and back. EXPECTED RESULT No cursor stuck in the middle of the brush shape 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.
[plasmashell] [Bug 412859] New: Plasma crashed when linux was updating
https://bugs.kde.org/show_bug.cgi?id=412859 Bug ID: 412859 Summary: Plasma crashed when linux was updating Product: plasmashell Version: 5.16.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: columbusutri...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.5) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 5.3.4-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I opened terminal, wrote "sudo pacman -Syu" and started updating the folowing packages: archlinux-keyring-20191007-1 ark-19.08.2-1 assimp-5.0.0-1 at-spi2-atk-2.34.1-1 baloo-widgets-19.08.2-1 blender-17:2.80-5 calibre-4.1.0-1 chromium-77.0.3865.120-1 clang-9.0.0-2 clazy-1.5-3 colord-1.4.4+9+g1ce26da-1 compiler-rt-9.0.0-2 coreutils-8.31-2 cups-filters-1.25.11-1 dconf-editor-3.34.2-1 dhcpcd-8.0.6-1 diffutils-3.7-2 dolphin-19.08.2-1 doxygen-1.8.16-2 ffmpegthumbnailer-2.2.2-1 ffmpegthumbs-19.08.2-1 file-5.37-3 filesystem-2019.10-1 firefox-69.0.3-1 gdk-pixbuf2-2.40.0-1 graphviz-2.42.2-2 grep-3.3-2 gvfs-1.42.1-1 gvfs-mtp-1.42.1-1 gwenview-19.08.2-1 gzip-1.10-2 jdk-openjdk-13.u33-1 jre-openjdk-13.u33-1 jre-openjdk-headless-13.u33-1 kaccounts-integration-19.08.2-1 kate-19.08.2-1 kbd-2.2.0-4 kcachegrind-19.08.2-1 kcachegrind-common-19.08.2-1 kdevelop-5.4.2-2 kdialog-19.08.2-1 kget-19.08.2-1 kio-extras-19.08.2-1 konsole-19.08.2-1 kwrite-19.08.2-1 less-551-2 lib32-gdk-pixbuf2-2.40.0-1 lib32-libglvnd-1.2.0-2 lib32-libx11-1.6.9-1 lib32-llvm-libs-9.0.0-1 lib32-mesa-19.2.1-1 lib32-vulkan-radeon-19.2.1-1 libconfig-1.7.2-2 libglvnd-1.2.0-2 libkdcraw-19.08.2-1 libkipi-19.08.2-1 libkomparediff2-19.08.2-1 liblphobos-2:1.17.0-4 libnma-1.8.24-1 libpgm-5.2.122-4 libreoffice-still-6.2.7-3 librsvg-2:2.46.1-1 libsoup-2.68.2-1 libx11-1.6.9-3 linux-5.3.5.arch1-1 llvm-libs-9.0.0-3 mesa-19.2.1-1 meson-0.52.0-1 mkinitcpio-26-1 network-manager-applet-1.8.24-1 nm-connection-editor-1.8.24-1 noto-fonts-20190926-2 npm-6.12.0-1 openshadinglanguage-1.10.6-3 openvdb-6.2.1-1 pacman-contrib-1.2.0-2 parted-3.3-1 polkit-0.116-3 postgresql-libs-11.5-4 python-attrs-19.2.0-1 python-msgpack-0.6.2-1 python2-attrs-19.2.0-1 python2-msgpack-0.6.2-1 qbs-1.14.0-1 qt5-tools-5.13.1-2 qtcreator-4.10.1-2 rust-1:1.38.0-2 sed-4.7-2 signon-kwallet-extension-19.08.2-1 spectacle-19.08.2-1 sqlite-3.30.0-1 tar-1.32-2 telegram-desktop-1.8.15-1 vala-0.46.3-1 vte-common-0.58.1-1 vte3-0.58.1-1 vulkan-radeon-19.2.1-1 which-2.21-4 xdg-dbus-proxy-0.1.2-1 xf86-video-intel-1:2.99.917+893+gbff5eca4-1 xorgproto-2019.1-3 - Unusual behavior I noticed: 1. When I clicked on right button on the desktop and selected "Add Panel" menu, that panel suddenly disappeared. 2. When screen started locking, screen blinked with black color, very strange. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8797a9b880 (LWP 648))] Thread 22 (Thread 0x7f87327fc700 (LWP 1430)): #0 0x7f879ba85c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f879c5ba660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f879c5ba752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f879e39edad in () at /usr/lib/libQt5Quick.so.5 #4 0x7f879e39f05e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f879c5b45b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f879ba7f4cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f879c2402d3 in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7f8732ffd700 (LWP 1429)): #0 0x7f879ba85c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f87864ab62c in () at /usr/lib/dri/radeonsi_dri.so #2 0x0029 in () #3 0x in () Thread 20 (Thread 0x7f87337fe700 (LWP 1428)): #0 0x7f879ba85c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f879c5ba660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f879c5ba752 in
[Discover] [Bug 412807] Discover crashes -- segmentation fault
https://bugs.kde.org/show_bug.cgi?id=412807 --- Comment #2 from David C. Bryant --- On Thursday, October 10, 2019 9:13:18 AM CDT you wrote: > https://bugs.kde.org/show_bug.cgi?id=412807 > > Aleix Pol changed: > >What|Removed |Added > > Resolution|--- |FIXED > Status|REPORTED|RESOLVED > > --- Comment #1 from Aleix Pol --- > This issue was fixed recently, it was a packaging issue in Qt. You will have > to use the terminal to update. You can do so by calling "pkcon update". > > Sorry for the inconvenience. :/ Sorry to tell you this, Aleix, but it's still a problem. I ran pkcon and got as far as entering root's pwd. Then I got this message: Fatal error: E: http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libgl1-mesa-dri amd64 19.0.8-0ubuntu0~18.04.2 is not (yet) available (404 Not Found [IP: 91.189.91.24 80]) So it looks like something about the repository is still all hosed up. Thanks! D. Bryant Canyon Lake, Texas -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409748] Brush preset docker/dropdown only saves las used tag if when quiting krita the tag is not set to "All".
https://bugs.kde.org/show_bug.cgi?id=409748 --- Comment #6 from Storm Engineer --- As of 4.3.0-prealpha (git 3e21da9), this issue is still present for me. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409749] Stylus eraser keeps resetting to basic brush
https://bugs.kde.org/show_bug.cgi?id=409749 --- Comment #1 from Storm Engineer --- As of 4.3.0-prealpha (git 3e21da9), this issue is still present for me. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394414] Brush preset thumbnails are the wrong aspect and often hidden and unselectable
https://bugs.kde.org/show_bug.cgi?id=394414 Storm Engineer changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #17 from Storm Engineer --- Sorry, I missed when this was closed. The issue is still present for me with 4.3.0-prealpha (git 3e21da9) Reopening as requested. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402646] kdeinit5 crash every startup.
https://bugs.kde.org/show_bug.cgi?id=402646 --- Comment #10 from Ahmad Samir --- >From the other bug reports it seems that the bug is triggered when receiving a notification from KDE Connect, e.g. when you receive an sms on your phone and KDE Connect notifies you of it on the desktop. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402646] kdeinit5 crashes when receiving a notification from KDE Connect
https://bugs.kde.org/show_bug.cgi?id=402646 Ahmad Samir changed: What|Removed |Added Summary|kdeinit5 crash every|kdeinit5 crashes when |startup.|receiving a notification ||from KDE Connect -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 412858] New: kwin_wayland crash immediately after startup
https://bugs.kde.org/show_bug.cgi?id=412858 Bug ID: 412858 Summary: kwin_wayland crash immediately after startup Product: kwayland-integration Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ragnarok...@gmail.com Target Milestone: --- Created attachment 123145 --> https://bugs.kde.org/attachment.cgi?id=123145=edit backtrace SUMMARY kwin_wayland crashes immediately after I run it from the command line. STEPS TO REPRODUCE 1. run 'kwin_wayland' with no arguments in a terminal. OBSERVED RESULT Segmentation fault with the backtrace attached. EXPECTED RESULT Successful startup without a segmentation fault. SOFTWARE/OS VERSION Operating System: Fedora 30 KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 Kernel Version: 5.2.7-200.fc30.x86_64 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4300M CPU @ 2.60GHz Memory: 7.7 GiB of RAM ADDITIONAL INFORMATION > rpm -qa name *wayland* | sort kf5-kwayland-5.59.0-2.fc30.x86_64 kwayland-integration-5.15.5-1.fc30.x86_64 kwayland-integration-debuginfo-5.15.5-1.fc30.x86_64 kwayland-integration-debugsource-5.15.5-1.fc30.x86_64 kwin-wayland-5.15.5-2.fc30.x86_64 kwin-wayland-debuginfo-5.15.5-2.fc30.x86_64 libwayland-client-1.17.0-1.fc30.i686 libwayland-client-1.17.0-1.fc30.x86_64 libwayland-cursor-1.17.0-1.fc30.i686 libwayland-cursor-1.17.0-1.fc30.x86_64 libwayland-egl-1.17.0-1.fc30.i686 libwayland-egl-1.17.0-1.fc30.x86_64 libwayland-server-1.17.0-1.fc30.i686 libwayland-server-1.17.0-1.fc30.x86_64 qt5-qtwayland-5.12.4-7.fc30.x86_64 qt5-qtwayland-devel-5.12.4-7.fc30.x86_64 xorg-x11-server-Xwayland-1.20.5-7.fc30.x86_64 > rpm -qa name *kwin* | sort kf5-kwindowsystem-5.59.0-1.fc30.x86_64 kwin-5.15.5-2.fc30.x86_64 kwin-common-5.15.5-2.fc30.x86_64 kwin-common-debuginfo-5.15.5-2.fc30.x86_64 kwin-debuginfo-5.15.5-2.fc30.x86_64 kwin-debugsource-5.15.5-2.fc30.x86_64 kwin-libs-5.15.5-2.fc30.x86_64 kwin-libs-debuginfo-5.15.5-2.fc30.x86_64 kwin-wayland-5.15.5-2.fc30.x86_64 kwin-wayland-debuginfo-5.15.5-2.fc30.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402646] kdeinit5 crash every startup.
https://bugs.kde.org/show_bug.cgi?id=402646 Ahmad Samir changed: What|Removed |Added CC||szots...@gmail.com --- Comment #9 from Ahmad Samir --- *** Bug 412821 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 412821] KIO crashed kdeinit5 in FileProtocol::put (SYSCALL_CANCEL)
https://bugs.kde.org/show_bug.cgi?id=412821 Ahmad Samir changed: What|Removed |Added Resolution|--- |DUPLICATE CC||a.samir...@gmail.com Status|REPORTED|RESOLVED --- Comment #2 from Ahmad Samir --- *** This bug has been marked as a duplicate of bug 402646 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402646] kdeinit5 crash every startup.
https://bugs.kde.org/show_bug.cgi?id=402646 Ahmad Samir changed: What|Removed |Added Ever confirmed|1 |0 Resolution|FIXED |--- Status|RESOLVED|REPORTED CC||a.samir...@gmail.com --- Comment #8 from Ahmad Samir --- Still an issue, given how many duplicates we're still seeing... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402646] kdeinit5 crash every startup.
https://bugs.kde.org/show_bug.cgi?id=402646 Ahmad Samir changed: What|Removed |Added CC||elxr...@gmail.com --- Comment #7 from Ahmad Samir --- *** Bug 406365 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 406365] kdeinit5 signal: Aborted
https://bugs.kde.org/show_bug.cgi?id=406365 Ahmad Samir changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Ahmad Samir --- *** This bug has been marked as a duplicate of bug 402646 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) and writes a *ton* of data while indexing
https://bugs.kde.org/show_bug.cgi?id=404057 Kai Krakow changed: What|Removed |Added Attachment #122925|0 |1 is obsolete|| --- Comment #27 from Kai Krakow --- Comment on attachment 122925 --> https://bugs.kde.org/attachment.cgi?id=122925 Prepare simpler coding of environment flags Has been merged into master -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 412572] After exiting a multimedia tab, mpris still shows the multimedia as running
https://bugs.kde.org/show_bug.cgi?id=412572 Olivier Churlaud changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Olivier Churlaud --- Can't reproduce anymore. I close it -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412813] Changes in report not taken into account
https://bugs.kde.org/show_bug.cgi?id=412813 --- Comment #6 from Thomas Baumgart --- Bonjour Patrick, that one has been fixed in 5.0.2. See https://bugs.kde.org/show_bug.cgi?id=392519 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412857] New: Plasma crash at startup
https://bugs.kde.org/show_bug.cgi?id=412857 Bug ID: 412857 Summary: Plasma crash at startup Product: plasmashell Version: 5.16.5 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: davide...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.5) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 5.0.0-31-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: Nothing, the system just booted up. The only change was I swhitched GPU during the boot process, before the GRUB menu for choosing the boot OS I have a dual boot system, with als two GPU, connected to the monitor with an HDMI swhitch so that I can select one or another for working. -- 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 0x7f8ab30f8880 (LWP 2130))] Thread 25 (Thread 0x7f89f36ee700 (LWP 2404)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f8aacbfb254 in QSemaphore::acquire(int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f8aace0e980 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f8aa9d6075b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #4 0x7f8aa9e09aed in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #5 0x7f8aace0e715 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8aa9d56959 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #7 0x7f8aa9d57215 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #8 0x7f8aace0e715 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f8aa9e025df in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #10 0x7f8aa9df734b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7f8aa9df7995 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #12 0x7f8aa9dd3ef1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #13 0x7f8aace0e715 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f8aa9d9e553 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #15 0x7f8aa9d9e604 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #16 0x7f8aa9db1c91 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #17 0x7f8aae744eac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f8aae74c4b0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f8aac48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f8aace3c628 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f8aa634b417 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f8aa634b650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f8aa634b6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f8aace3b9bf in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f8aacddbeaa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f8aacbf73ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f8aacbf8b72 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f8aa97066db in start_thread (arg=0x7f89f36ee700) at pthread_create.c:463 #29 0x7f8aac4f588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7f89f3fff700 (LWP 2403)): #0 0x7f8aa970c9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55985c2bc334) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55985c2bc2e0, cond=0x55985c2bc308) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55985c2bc308, mutex=0x55985c2bc2e0) at pthread_cond_wait.c:655 #3 0x7f8aacbffb0b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f8aacbffe19 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8ab0f70ec8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f8ab0f712fa in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7
[okular] [Bug 412856] New: Okular prompts for password when none is needed for display
https://bugs.kde.org/show_bug.cgi?id=412856 Bug ID: 412856 Summary: Okular prompts for password when none is needed for display Product: okular Version: 1.3.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: ingo.stra...@gmx.net Target Milestone: --- SUMMARY I have a PDF where a password is used to protect against editing. But the password is not needed for display only. This file cannot be opened in okular on my system. STEPS TO REPRODUCE 1. Open https://www.bgfg.de/fileadmin/bgfg/Geschaeftsberichte/Geschaeftsbericht_2018_BGFG_Jahrbuchteil_END-Doppelseiten-WEB.pdf in okular 2. Click "cancel" when asked for password OBSERVED RESULT Error is shown that the file cannot be opened EXPECTED RESULT The file should be displayed and there should be no password prompt. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Leap 15.0 (available in About System) KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.45.0 Qt Version: 5.9.4 ADDITIONAL INFORMATION Opening the file with Master PDF Editor in the same machine or with Adobe Reader on another PC does not prompt for a password and displays the file just fine. In an earlier bug (https://bugs.kde.org/show_bug.cgi?id=365460) there was mention of poppler, so here are all installed poppler RPMs with version: libpoppler73-0.62.0-lp150.2.5.x86_64 libpoppler-glib8-0.62.0-lp150.2.5.x86_64 libpoppler-qt5-1-0.62.0-lp150.2.3.x86_64 poppler-data-0.4.8-lp150.1.3.noarch poppler-tools-0.62.0-lp150.2.5.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412152] [Wayland] cannot start session
https://bugs.kde.org/show_bug.cgi?id=412152 Tony changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=412684 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412684] [Wayland] kwin_wayland[3904]: segfault at 10 ip 00007f35691b6c30 sp 00007ffcf514ce98 error 4 in libKF5WaylandServer.so.5.63.0[7f3569191000+60000]
https://bugs.kde.org/show_bug.cgi?id=412684 Tony changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=412152 --- Comment #5 from Tony --- Ralated/duplicated https://bugs.kde.org/show_bug.cgi?id=412152 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411480] Problems with database migration on remote host
https://bugs.kde.org/show_bug.cgi?id=411480 Maik Qualmann changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED Version Fixed In||6.4.0 --- Comment #4 from Maik Qualmann --- Ok, thanks, I'll close the bug. My suggestion from comment 2 should have helped. It may happen again after a new MySQL server release that an upgrade must be performed. If necessary reopen the bug. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 412855] New: Cannot unlock a plasma session
https://bugs.kde.org/show_bug.cgi?id=412855 Bug ID: 412855 Summary: Cannot unlock a plasma session Product: kscreenlocker Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: greeter Assignee: plasma-b...@kde.org Reporter: rull...@gmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY Once a plasma session becomes locked, it cannot be unlocked. STEPS TO REPRODUCE 1. Log into a plasma session. 2. Allow the screen lock to engage or lock screen with Ctrl-Alt-L 3. Enter password to unlock session. OBSERVED RESULT After entry of password, screen widgets disappear showing just the wallpaper then after a second the screen widgets redisplay prompting for a password. EXPECTED RESULT Screen should be unlocked and desktop displayed. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.16.90 KDE Frameworks Version: 5.62.0 Qt Version: 5.14.0 Kernel Version: 5.3.5-arch1-1-ARCH OS Type: 64-bit Processors: 4 × Intel® Core™ i5 CPU M 430 @ 2.27GHz Memory: 7.5 GiB of RAM kscreenlocker 5.16.90-1 ADDITIONAL INFORMATION System up to date with latest kde-unstable, testing and community-testing packages. >From journalctl: Oct 11 16:41:29 richards-aspire audit[6220]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 pid=6220 comm="kscreenlocker_g" exe="/usr/lib/kscreenlocker_greet" sig=11 res=1 Oct 11 16:41:29 richards-aspire kernel: kscreenlocker_g[6220]: segfault at 18 ip 7f7a414cc351 sp 7fff8226d6b0 error 4 in libQt5Qml.so.5.14.0[7f7a4143c000+305000] Oct 11 16:41:29 richards-aspire kernel: Code: f2 0f 1f 84 00 00 00 00 00 89 d8 48 83 c2 02 c1 e0 05 29 d8 89 c3 0f b7 42 fe 01 c3 49 39 d4 77 e8 4d 01 fe 41 0f b7 06 31 d2 <48> 8b 75 18 66 89 44 24 0e 89 d8 f7 75 08 89 d0 4c 8b 24 c6 49 89 Oct 11 16:41:29 richards-aspire kernel: audit: type=1701 audit(1570808489.447:57): auid=1000 uid=1000 gid=1000 ses=2 pid=6220 comm="kscreenlocker_g" exe="/usr/lib/kscreenlocker_greet" sig=11 res=1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412854] Digikam Impossible to select "write metadata in Raw files" in configuration menu
https://bugs.kde.org/show_bug.cgi?id=412854 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412854] Digikam Impossible to select "write metadata in Raw files" in configuration menu
https://bugs.kde.org/show_bug.cgi?id=412854 Maik Qualmann changed: What|Removed |Added Version Fixed In||6.4.0 CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- Fixed with Bug 387351 Maik -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412823] Please add a refresh function.
https://bugs.kde.org/show_bug.cgi?id=412823 Matthijs Tijink changed: What|Removed |Added CC||matthijstij...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Matthijs Tijink --- You can already refresh by pulling down on the device select screen. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412854] Digikam Impossible to select "write metadata in Raw files" in configuration menu
https://bugs.kde.org/show_bug.cgi?id=412854 caulier.gil...@gmail.com changed: What|Removed |Added Component|Metadata-Editor |Setup-Metadata -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412854] Digikam Impossible to select "write metadata in Raw files" in configuration menu
https://bugs.kde.org/show_bug.cgi?id=412854 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- Hi, This option have been disabled due to the huge risk to destroy RAW image with the Exiv2 metadata engine. But after few release, a lots of users vote to reactive this option. You will find it in current 6.3.0 stable release, or you can try the 6.4.0 pre release AppImage available here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412844] When you place any layer right below the 'group layer', it doesn't go inside the group
https://bugs.kde.org/show_bug.cgi?id=412844 --- Comment #3 from Ahab Greybeard --- Logically, I can think of two situations where it's useful to have these two different actions. However, this will be a decision for the all powerful developers and nothing to do with me. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412844] When you place any layer right below the 'group layer', it doesn't go inside the group
https://bugs.kde.org/show_bug.cgi?id=412844 --- Comment #2 from acc4commissi...@gmail.com --- Logically, for this particular position(right below the group category layer), I think it shouldn't be separated. (But the dicision is yours...) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412854] New: Digikam Impossible to select "write metadata in Raw files" in configuration menu
https://bugs.kde.org/show_bug.cgi?id=412854 Bug ID: 412854 Summary: Digikam Impossible to select "write metadata in Raw files" in configuration menu Product: digikam Version: 5.9.0 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Editor Assignee: digikam-bugs-n...@kde.org Reporter: germain.lecou...@laposte.net Target Milestone: --- I can not select the option "configuration / metadata / if possible write metadata in Raw file" since I changed distribution (Digikam 5.9 / Emmabuntus Debian Strech). It works correctly on another computer (Digikam 5.3 / MX 18). I compared the list of installed packages between the 2 stations. It's the same except for version numbers of course. Note: I can only run Digikam via command line, after putting "unset QT_QPA_PLATFORMTHEME". But Irt said this point is due to delay to have a good gateway between KDE and Gnome desktop and it not concerns this forum. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 10 (by Emmabuntus Deb3 distribution) (available in About System) KDE Plasma Version: none KDE Frameworks Version: none Gnome Version: 3.30.2 / Qt5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412844] When you place any layer right below the 'group layer', it doesn't go inside the group
https://bugs.kde.org/show_bug.cgi?id=412844 Ahab Greybeard changed: What|Removed |Added Ever confirmed|0 |1 CC||ahab.greybe...@hotmail.co.u ||k Status|REPORTED|CONFIRMED --- Comment #1 from Ahab Greybeard --- There are two distinct but barely separated positions which are outside-below the group or inside-top of the group. This is useful but unless you pay attention, remember the difference and move carefully it can be confusing. It would be nice if they could be more distinct, maybe by being more physically separated or maybe by the outside-below position having a different highlight colour, or both. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412346] Personal settings not being saved
https://bugs.kde.org/show_bug.cgi?id=412346 Christoph Feck changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from Christoph Feck --- Thanks for the update; changing status. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 412853] New: Download/Upload speed is sorted upside down
https://bugs.kde.org/show_bug.cgi?id=412853 Bug ID: 412853 Summary: Download/Upload speed is sorted upside down Product: ksysguard Version: 5.16.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: matejm98m...@gmail.com Target Milestone: --- With CPU or memory usage, arrow pointing down means: "highest on top" but with networks speeds it means "lowest on top". -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363438] measure point for transform position is not considered
https://bugs.kde.org/show_bug.cgi?id=363438 wolthera changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||griffinval...@gmail.com Resolution|--- |FIXED --- Comment #2 from wolthera --- This has been fixed since... 4.1, I think. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412845] Plasma crashed on session restore
https://bugs.kde.org/show_bug.cgi?id=412845 --- Comment #2 from Aleksey Kontsevich --- Link: https://github.com/ConteZero/tw-updater-plasmoid/issues/3 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397400] Masking reference pictures
https://bugs.kde.org/show_bug.cgi?id=397400 wolthera changed: What|Removed |Added Resolution|--- |DUPLICATE CC||griffinval...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from wolthera --- *** This bug has been marked as a duplicate of bug 399061 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399061] Crop reference images dynamically
https://bugs.kde.org/show_bug.cgi?id=399061 wolthera changed: What|Removed |Added CC||jo.y.v...@gmail.com --- Comment #1 from wolthera --- *** Bug 397400 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411181] F4 no longer moves keyboard focus to Konsole panel after it's been opened and closed at least once
https://bugs.kde.org/show_bug.cgi?id=411181 gwar...@gmail.com changed: What|Removed |Added CC||gwar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407238] 100% transparency in SDR images look like white on HDR display
https://bugs.kde.org/show_bug.cgi?id=407238 Tymond changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/32ab64c9010967 ||2c6b363c996d236a203516ab95 Resolution|--- |FIXED --- Comment #3 from Tymond --- Git commit 32ab64c90109672c6b363c996d236a203516ab95 by Agata Cacko. Committed on 11/10/2019 at 14:20. Pushed by tymond into branch 'master'. Fix transparency checkers looked white on HDR display On HDR displays before this commit transparency checkers looked white because it was just a SDR image showed in full HDR glory. Hence both light and darker light grey checkers looked just bright white, no different from each other, even though in fact their colors were different. This commit fixes this behaviour by converting the colors properly from SDR/sRGB to Rec2020-pq (or other display format) as it should be done. Related: bug 406698 M +24 -14 libs/ui/opengl/kis_opengl_image_textures.cpp https://invent.kde.org/kde/krita/commit/32ab64c90109672c6b363c996d236a203516ab95 -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 404451] sncf confirmation email types to help development
https://bugs.kde.org/show_bug.cgi?id=404451 --- Comment #18 from Philippe ROUBACH --- Created attachment 123144 --> https://bugs.kde.org/attachment.cgi?id=123144=edit confirmation mail of "La fourchette" android app I am not sure itinerary takes care of this sort of mail. But when I saw the itinerary part in this mail I found it is very handy. Perhaps an enhancement ? All runs well but not for adding this event "a restaurant reservation" The beginning is good "12 h" but the end is not good "23 h 59". It must be "14 h" https://play.google.com/store/apps/details?id=com.lafourchette.lafourchette -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406698] Transform Tool has SDR preview on HDR image
https://bugs.kde.org/show_bug.cgi?id=406698 --- Comment #8 from Tymond --- Git commit 32ab64c90109672c6b363c996d236a203516ab95 by Agata Cacko. Committed on 11/10/2019 at 14:20. Pushed by tymond into branch 'master'. Fix transparency checkers looked white on HDR display On HDR displays before this commit transparency checkers looked white because it was just a SDR image showed in full HDR glory. Hence both light and darker light grey checkers looked just bright white, no different from each other, even though in fact their colors were different. This commit fixes this behaviour by converting the colors properly from SDR/sRGB to Rec2020-pq (or other display format) as it should be done. Related: bug 407238 M +24 -14 libs/ui/opengl/kis_opengl_image_textures.cpp https://invent.kde.org/kde/krita/commit/32ab64c90109672c6b363c996d236a203516ab95 --- Comment #9 from Tymond --- Git commit 5b53507f5abf544e9e33ad9aaf10073e1121a332 by Agata Cacko. Committed on 11/10/2019 at 14:20. Pushed by tymond into branch 'master'. Fix background color conversion Background color should be converted using the monitor profile instead of display converter. M +12 -6libs/ui/opengl/kis_opengl_canvas2.cpp M +5-0libs/ui/opengl/kis_opengl_image_textures.cpp M +1-0libs/ui/opengl/kis_opengl_image_textures.h https://invent.kde.org/kde/krita/commit/5b53507f5abf544e9e33ad9aaf10073e1121a332 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406698] Transform Tool has SDR preview on HDR image
https://bugs.kde.org/show_bug.cgi?id=406698 --- Comment #9 from Tymond --- Git commit 5b53507f5abf544e9e33ad9aaf10073e1121a332 by Agata Cacko. Committed on 11/10/2019 at 14:20. Pushed by tymond into branch 'master'. Fix background color conversion Background color should be converted using the monitor profile instead of display converter. M +12 -6libs/ui/opengl/kis_opengl_canvas2.cpp M +5-0libs/ui/opengl/kis_opengl_image_textures.cpp M +1-0libs/ui/opengl/kis_opengl_image_textures.h https://invent.kde.org/kde/krita/commit/5b53507f5abf544e9e33ad9aaf10073e1121a332 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406698] Transform Tool has SDR preview on HDR image
https://bugs.kde.org/show_bug.cgi?id=406698 --- Comment #8 from Tymond --- Git commit 32ab64c90109672c6b363c996d236a203516ab95 by Agata Cacko. Committed on 11/10/2019 at 14:20. Pushed by tymond into branch 'master'. Fix transparency checkers looked white on HDR display On HDR displays before this commit transparency checkers looked white because it was just a SDR image showed in full HDR glory. Hence both light and darker light grey checkers looked just bright white, no different from each other, even though in fact their colors were different. This commit fixes this behaviour by converting the colors properly from SDR/sRGB to Rec2020-pq (or other display format) as it should be done. Related: bug 407238 M +24 -14 libs/ui/opengl/kis_opengl_image_textures.cpp https://invent.kde.org/kde/krita/commit/32ab64c90109672c6b363c996d236a203516ab95 -- You are receiving this mail because: You are watching all bug changes.
