[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 --- Comment #19 from José Pekkarinen --- I'm already far from the versions this happened to me too, so not reproducing anymore, it can be closed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397280] kwin starts to crash at some random point
https://bugs.kde.org/show_bug.cgi?id=397280 --- Comment #5 from Christoph Feck --- Please ask for help in a forum of your distribution how to correctly install matching nvidia driver and kernel versions. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375971] kwin_wayland take 100% CPU
https://bugs.kde.org/show_bug.cgi?id=375971 Christoph Feck changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #20 from Christoph Feck --- Thanks for the update; closing. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 392913] NTFS mountpoints appears as hidden after mount
https://bugs.kde.org/show_bug.cgi?id=392913 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kio ||/f6df95e595ee3a5322fb70c7dd ||5860630f82ffdd Status|CONFIRMED |RESOLVED --- Comment #22 from Kai Uwe Broulik --- Git commit f6df95e595ee3a5322fb70c7dd5860630f82ffdd by Kai Uwe Broulik. Committed on 09/08/2018 at 07:46. Pushed by broulik into branch 'master'. Ignore NTFS hidden flag for root volume Those are always hidden as far as NTFS is concerned but leads to unwanted side-effects of NTFS volumes becoming inaccessible in the UI Differential Revision: https://phabricator.kde.org/D13782 M +14 -1src/ioslaves/file/file_unix.cpp https://commits.kde.org/kio/f6df95e595ee3a5322fb70c7dd5860630f82ffdd -- You are receiving this mail because: You are watching all bug changes.
[zanshin] [Bug 397299] New: Tasks assigned to a context shouldn't be shown in Inbox anymore
https://bugs.kde.org/show_bug.cgi?id=397299 Bug ID: 397299 Summary: Tasks assigned to a context shouldn't be shown in Inbox anymore Product: zanshin Version: 0.5.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: er...@kde.org Reporter: matthiasg...@gmail.com CC: mbe...@ipsquad.net Target Milestone: already done Use case: New Tasks I create i.e. through KRunner or on my cellphone are automatically synchronized an show up in my zanshin inbox. Problem: The only way to get them out of my inbox is to assign them to a project. Assigning them to a context lets them reside in the inbox as well. Desired behavior: Tasks assigned to a context shouldn't be shown in Inbox anymore. -- You are receiving this mail because: You are watching all bug changes.
[zanshin] [Bug 397300] New: Kontact integration of zanhsin does not save window properties
https://bugs.kde.org/show_bug.cgi?id=397300 Bug ID: 397300 Summary: Kontact integration of zanhsin does not save window properties Product: zanshin Version: 0.5.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: er...@kde.org Reporter: matthiasg...@gmail.com CC: mbe...@ipsquad.net Target Milestone: already done Use case: I use Zanshin from within Kontact - this is a great option. After selecting the calendar sources I want to use zanshin with, I want to hide them away by dragging down the border between the project list and calendar list. Problem: Zanshin does not save this setting. On each restart of Kontact, I have to do this "drag down" move again. Desired behavior: Zanshin should save these Window Properties throughout restarts of Kontact - just like it does when you use zanshin in standalone mode. There, it is even possible to tab the project/context list and the sources list. -- You are receiving this mail because: You are watching all bug changes.
[zanshin] [Bug 397301] New: Kontact module of zanshin does not use localization
https://bugs.kde.org/show_bug.cgi?id=397301 Bug ID: 397301 Summary: Kontact module of zanshin does not use localization Product: zanshin Version: 0.5.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: er...@kde.org Reporter: matthiasg...@gmail.com CC: mbe...@ipsquad.net Target Milestone: already done Use Case: I use zanshin as a module from within Kontact. My default localization in plasma and kontact is german. Problem: The module is only shown in english localization. Desired behavior: Module should use Kontacts / Plasmas default localization - just like zanshin does in standalone mode. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388808] interactions with the desktop area are sluggish
https://bugs.kde.org/show_bug.cgi?id=388808 --- Comment #1 from Gianni --- Update: Bug is still present on Plasma version: 5.13.5 OS: KDE neon 5.13 Compositor used: XRedender/OpenGL 2.0 Graphics: Mesa DRI Intel(R) 945GM I discovered that the bug doesn't show itself if I type "plasma renderer" into krunner and select "Rendering backend = software". I'd like to add that it's not just the rectangle selection animation that is sluggish, but every interaction with the desktop, such as moving objects, selecting text in notes and so on. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388808] interactions with the desktop area are sluggish
https://bugs.kde.org/show_bug.cgi?id=388808 Gianni changed: What|Removed |Added Version|5.10.5 |5.13.3 Platform|Kubuntu Packages|Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 397302] New: KDE Partition manager crashing after upgrade
https://bugs.kde.org/show_bug.cgi?id=397302 Bug ID: 397302 Summary: KDE Partition manager crashing after upgrade Product: partitionmanager Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: matsc...@gmail.com Target Milestone: --- Application: partitionmanager (3.3.1) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-29-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: application hangs at 50%, clicked cancel then it crash, went to send report The crash can be reproduced every time. -- Backtrace: Application: KDE Partition Manager (partitionmanager), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9cd4998840 (LWP 8277))] Thread 3 (Thread 0x7f9cac490700 (LWP 8396)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f9cd0f57765 in QBasicMutex::lockInternal() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f9cd0f57ac3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f9cd0f585b7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9cd0f58eb6 in QReadWriteLock::tryLockForWrite(int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9cd455cc18 in OperationStack::addDevice(Device*) () from /usr/lib/x86_64-linux-gnu/libkpmcore.so.7 #6 0x7f9cd4551b1c in DeviceScanner::scan() () from /usr/lib/x86_64-linux-gnu/libkpmcore.so.7 #7 0x7f9cd0f6016d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9ccc78a6db in start_thread (arg=0x7f9cac490700) at pthread_create.c:463 #9 0x7f9cd085688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f9cb8d78700 (LWP 8279)): #0 0x7f9ccaed297c in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f9ccaed336b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9ccaed354c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9cd119790b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9cd113c9ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9cd0f5b22a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9cd0066d45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f9cd0f6016d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9ccc78a6db in start_thread (arg=0x7f9cb8d78700) at pthread_create.c:463 #9 0x7f9cd085688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f9cd4998840 (LWP 8277)): [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #5 0x7f9cd0775801 in __GI_abort () at abort.c:79 #6 0x7f9cd0f4afa7 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9cd0f5a17d in QThread::~QThread() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9cd4597507 in ?? () from /usr/lib/x86_64-linux-gnu/libkpmcore.so.7 #9 0x7f9cd116b19b in QObjectPrivate::deleteChildren() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f9cd1ef6d4c in QWidget::~QWidget() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f9cd3d1273d in KMainWindow::~KMainWindow() () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #12 0x559d70e72184 in ?? () #13 0x7f9cd116e140 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f9cd1efb743 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f9cd200ec4b in QMainWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f9cd3d14b87 in KMainWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #17 0x7f9cd3d599e5 in KXmlGuiWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #18 0x7f9cd1ebc82c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f9cd1ec40f4 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f9cd113e9a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f9cd114111d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f9cd11982c3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f9ccaed3287 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu
[digikam] [Bug 397297] newly created folders not shown in the import from camera window
https://bugs.kde.org/show_bug.cgi?id=397297 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- You mean, after you have selected images and go to download, that then in the window with the tree view to select the target album, that new album does not exist? Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397303] New: loss of transparency/opacity with Intel (Broadwell) + mesa 18.0.5 + Xorg 1.18.4
https://bugs.kde.org/show_bug.cgi?id=397303 Bug ID: 397303 Summary: loss of transparency/opacity with Intel (Broadwell) + mesa 18.0.5 + Xorg 1.18.4 Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Look & Feel package Assignee: plasma-b...@kde.org Reporter: adwy...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Hi there, as result of Canonical's role-out of mesa 18.0.5 replacing 17.2.8 for Ubuntu Core 16.04 LTS, some users running KDE Neon User Edition and while being on Plasma version 5.13.2 to 5.13.4 + using Intel integrated graphics (especially Broadwell) experiencing loss of transparency/opacity in their Plasma Theme. relevant components: experienced with Neon in KDE Plasma version 5.13.2, 5.13.3 and 5.13.4 Xorg 1.18.4 Mesa 18.0.5 using OpenGL 3.1 The experiences are exchanged and documented (with screenshots) on: https://plus.google.com/105447283901275565289/posts/dMAvFe3pwbg I had a look into possible duplicates, especially into: https://bugs.kde.org/show_bug.cgi?id=392716 and further then related to https://bugs.freedesktop.org/show_bug.cgi?id=105871. But I am not sure, if this is to 100% the same issue, because disabling Compositor on startup doesn't change anything. And I am also just a user, therefore not too deep into that stuff, but happy to help, to provide more info and to test, wherever possible. For sure is, that the transparency towards KWin (Window Manager), configurable via Desktop Effects (e.g. window menus, dialogues etc.) is not affected and working properly. Only plasma theme related details, like control panel, application menu and Konsole is experiencing this loss of transparency. Other reported effects, like in Kubuntu 16.04 with Firefox Menus, e.g. https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780664 or https://bugs.freedesktop.org/show_bug.cgi?id=103699 are not experienced in Neon. One user (GIMP PRO) in the given Google+ thread, who experienced the transparency loss as well, in Plasma version 5.13.2 and 5.13.3 recently commented that it is restored on his system with the Neon update to version 5.13.4. It is not yet confirmed, what Intel hardware he's using. But Broadwell is definitely still affected. I hope, that this helps and that a solution can be found. Have much thanks in advance, Andreas -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 397304] New: CPU % field values incorrect
https://bugs.kde.org/show_bug.cgi?id=397304 Bug ID: 397304 Summary: CPU % field values incorrect Product: ksysguard Version: 5.12.6 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: paul...@hotmail.com Target Milestone: --- I have compared the CPU % against the top command and they are much lower and they do not add up to the total CPU %. I have selected All processes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 321897] Sheet effect doesn't set WindowClosedGrabRole and collides with fade effect on close for different duration
https://bugs.kde.org/show_bug.cgi?id=321897 Vlad Zagorodniy changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #35 from Vlad Zagorodniy --- The sheet effect grabs modal windows and the fade effect honors grab roles. So, marking this bug as fixed. If we want modal windows to fade in/out with the sheet effect, then the latter should fade them. Otherwise, effects don't have clear domain boundaries and we're screwed. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 --- Comment #32 from Gianni --- (In reply to David Edmundson from comment #31) > Another thing to try is typing "plasma renderer" into krunner > from there you can select "Rendering backend = software" > > Changes will apply after session restart. I would like to hear back on how > good the performance is. This is an interesting setting. The performance seems pretty good with better responsiveness and it also "solves" another bug I filed some time ago about sluggish desktop interaction #388808. Unfortunately this setting breaks something because I can't see the themes preview anymore in system settings -> workspace themes. Furthermore this doesn't solve the kscreenlocker_greet cpu issue. I don't know if this is the right place, but I'm interested in knowing what difference there is between setting XRender compositor and setting Rendering backend = software. (In reply to Christoph Feck from comment #30) > You can force OpenGL 2.1 for intel 915+ by enabling ARB_occlusion_query and > ARB_fragment_shader in drirc. Well, I didn't expect I could do that. Now I'm using OpenGL 2.1, so plasma provides more effects and seems more responsive, except for certain localized areas (like the workspace theme section, that apparently has become slower). Unfortunately, the kscreenlocker_greet issue is still present, but now that I have a capable opengl 2 graphic chip, I'm appending new qdbus and gdb debug info when using OpenGL 2 compositor. ps. These were really useful tips anyway, I apreciate that. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 Gianni changed: What|Removed |Added Attachment #114342|0 |1 is obsolete|| --- Comment #33 from Gianni --- Created attachment 114383 --> https://bugs.kde.org/attachment.cgi?id=114383&action=edit qdbus org.kde.KWin /KWin supportInformation on intel GMA950 with OpenGL 2 compositor qdbus org.kde.KWin /KWin supportInformation on intel GMA950 with OpenGL 2 compositor -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 --- Comment #34 from Gianni --- Created attachment 114384 --> https://bugs.kde.org/attachment.cgi?id=114384&action=edit gdb backtrace output of kscreenlocker_greet on intel GMA950 using OpenGL 2 compositor gdb backtrace output of kscreenlocker_greet on intel GMA950 using OpenGL 2 compositor -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 Gianni changed: What|Removed |Added Attachment #114379|0 |1 is obsolete|| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 339564] Maximize Effect miscalculate the position when dragging to maximize/restore
https://bugs.kde.org/show_bug.cgi?id=339564 Vlad Zagorodniy changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Vlad Zagorodniy --- Can't reproduce it, so marking it as resolved. The maximize effect keeps track of geometry while a window is being dragged. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 351849] Margins often cut when printing
https://bugs.kde.org/show_bug.cgi?id=351849 --- Comment #30 from Germano Massullo --- I tried to print using other computer and I had no problems No problem with (In reply to Michael Weghorn from comment #26) > (We can still discuss on why the options are no longer set after renaming > the lpoptions files twice, regardless of whether the bug is open or not.) Yes I would be interested in discussing this -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375518] global shortcuts show some oddities with foreign keyboard layouts
https://bugs.kde.org/show_bug.cgi?id=375518 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com --- Comment #4 from Alexander Mentyu --- Ctrl+Alt+K shortcut switches keyboard layouts from Ukrainian to Russian and from Russian to English in X11 but not in Wayland Distribution: KDE neon Developer Edition Kernel: 4.15.0-29-generic Plasma: 5.13.80 Apps: 18.11.70 Qt: 5.11.1 Frameworks: 5.48.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397305] New: failed to add tag to database
https://bugs.kde.org/show_bug.cgi?id=397305 Bug ID: 397305 Summary: failed to add tag to database Product: digikam Version: 5.8.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tags-Captions Assignee: digikam-bugs-n...@kde.org Reporter: s.nasri...@yahoo.com Target Milestone: --- I cannot add any tag neither can create new tag. This action always ended with error - "Failed to add tag to database". I use SQLite database to store relevant data. Reproducible: Always Steps to Reproduce: add new tag Actual Results: An error has occured during tag creation. Expected Results: new tag is added I am using Windows 7, 64-bits. DigiKam 5.8.0 Any suggestion is gladly welcome. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 397306] New: Wrong height of the list of files
https://bugs.kde.org/show_bug.cgi?id=397306 Bug ID: 397306 Summary: Wrong height of the list of files Product: dolphin Version: 18.04.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: leonid.krashe...@yandex.ru CC: elvis.angelac...@kde.org Target Milestone: --- Created attachment 114385 --> https://bugs.kde.org/attachment.cgi?id=114385&action=edit Screenshot See the screen shot. I see that every time I start dolphin. If I change the width of the left panel then dolphin is displayed correctly. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 351849] Margins often cut when printing
https://bugs.kde.org/show_bug.cgi?id=351849 --- Comment #31 from Michael Weghorn --- (In reply to Germano Massullo from comment #30) > I tried to print using other computer and I had no problems I'm glad to hear this. > Yes I would be interested in discussing this OK. Do you have a way to reproduce this in some way? (Otherwise it's impossible to further investigate the issue.) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 189999] Wobbly windows causes excessive painting when (not) moving windows
https://bugs.kde.org/show_bug.cgi?id=18 Vlad Zagorodniy changed: What|Removed |Added CC||vladz...@gmail.com --- Comment #6 from Vlad Zagorodniy --- @Martin Can we mark this bug as RESOLVED? It looks like the Wobbly Windows effect is doing its the best to reduce repaints. Also, I personally don't experience excessive CPU usage. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388808] interactions with the desktop area are sluggish
https://bugs.kde.org/show_bug.cgi?id=388808 --- Comment #2 from Gianni --- *Plasma version: 5.13.4 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 397307] New: Hide or show pointer only effects the following screenshot
https://bugs.kde.org/show_bug.cgi?id=397307 Bug ID: 397307 Summary: Hide or show pointer only effects the following screenshot Product: Spectacle Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: alex...@gmx.net Target Milestone: --- When a screenshot is taken, the mouse pointer is captured by default.* If a user decides to to exclude the mouse pointer, the option "Include mouse pointer" has to be unchecked and another screenshot has to be taken. Therefore, I suggest two always take two screenshots: One with the mouse and one without. Concretely, if the user unchecks "Include mouse pointer", the preview screenshot should be updated and the image without the pointer should be saved. * This should also work if the mouse pointer is excluded by default. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 351849] Margins often cut when printing
https://bugs.kde.org/show_bug.cgi?id=351849 --- Comment #32 from Germano Massullo --- (In reply to Michael Weghorn from comment #31) > (In reply to Germano Massullo from comment #30) > > Yes I would be interested in discussing this > > OK. Do you have a way to reproduce this in some way? (Otherwise it's > impossible to further investigate the issue.) Unfortunately I am no longer able to reproduce the issue :-( -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 397264] Cantor crashes with Python 2 backend when importing matplotlib.pyplot
https://bugs.kde.org/show_bug.cgi?id=397264 --- Comment #3 from Savor d'Isavano --- (In reply to Alexander Semke from comment #1) > The error seems to come from PySide/QtCore.so. I cannot reproduce this > problem here on openSuse. Does this import step works for when using python2 > directly in the terminal? Hi, it works: Python 2.7.15 (default, Jun 27 2018, 13:05:28) [GCC 8.1.1 20180531] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import matplotlib.pyplot as plt >>> plt >>> I'm running Arch and I have PySide2-5.11.0 and python-pyside-1.2.4 installed. Also note that the Python 3 session does not crash when running the import statement, but if doing actual plotting the backend server process terminates while Cantor remains running. (I may open a separate issue for this, but IMHO this behavior is saner than crashing) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 397307] Hide or show pointer only effects the following screenshot
https://bugs.kde.org/show_bug.cgi?id=397307 Henrik Fehlauer changed: What|Removed |Added CC||rk...@lab12.net --- Comment #1 from Henrik Fehlauer --- Thanks for your message. If we implemented your suggestion, changing options after the fact should also work for all of the other options. However, I don't think that's feasible from a performance and memory perspective, because the number of possible combinations would just be too high. The workflow is supposed to be like this: - Set options. - Take screenshot. - Save. Other apps use a more wizard-like workflow, but I think that's tedious and the current way serves most Spectacle users well enough. --- I suppose your use case was to exclude the mouse pointer after you took the screenshot, because you had no use for it? If so, we probably rather should disable the mouse pointer by default, see Bug 397121. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 352943] Show Desktop effects "Window Aperture" and "Eye on screen" should be mutually exclusive
https://bugs.kde.org/show_bug.cgi?id=352943 Vlad Zagorodniy changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED CC||vladz...@gmail.com --- Comment #1 from Vlad Zagorodniy --- Fixed by c7298b24e6369f9bf68e83ca1738cf060cc8c24e. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 397223] system settings crashes on close under Wayland
https://bugs.kde.org/show_bug.cgi?id=397223 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com --- Comment #1 from Alexander Mentyu --- Backtrace after executing steps in report Distribution: KDE neon Developer Edition Kernel: 4.15.0-29-generic Plasma: 5.13.80 Apps: 18.11.70 Qt: 5.11.1 Frameworks: 5.48.0 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 0x7f0a37828940 (LWP 2278))] Thread 5 (Thread 0x7f09fb5ef700 (LWP 2299)): #0 0x7f0a32e8074d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0a2c5a238c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0a2c5a249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0a337980bb in QEventDispatcherGlib::processEvents (this=0x7f09e800e060, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f0a3373f5ba in QEventLoop::exec (this=this@entry=0x7f09fb5eec50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7f0a335745e4 in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7f0a3128c195 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f0a3357f727 in QThreadPrivate::start (arg=0x75648b0) at thread/qthread_unix.cpp:367 #8 0x7f0a2e6246ba in start_thread (arg=0x7f09fb5ef700) at pthread_create.c:333 #9 0x7f0a32e8c41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f09fbfff700 (LWP 2293)): #0 0x7f0a32e7c27d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0a2c5e56f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0a2c5a1e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0a2c5a2330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0a2c5a2712 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f0a00ba39d6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x7f0a2c5c8bb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f0a2e6246ba in start_thread (arg=0x7f09fbfff700) at pthread_create.c:333 #8 0x7f0a32e8c41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f0a008ba700 (LWP 2292)): #0 0x7f0a32e8074d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0a2c5a238c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0a2c5a249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0a2c5a24d9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0a2c5c8bb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f0a2e6246ba in start_thread (arg=0x7f0a008ba700) at pthread_create.c:333 #6 0x7f0a32e8c41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f0a20c46700 (LWP 2280)): #0 0x7f0a32e8074d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0a2c5a238c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0a2c5a249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0a337980bb in QEventDispatcherGlib::processEvents (this=0x7f0a1c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f0a3373f5ba in QEventLoop::exec (this=this@entry=0x7f0a20c45c40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7f0a335745e4 in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7f0a33bdff35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f0a3357f727 in QThreadPrivate::start (arg=0x7f0a33e58d60) at thread/qthread_unix.cpp:367 #8 0x7f0a2e6246ba in start_thread (arg=0x7f0a20c46700) at pthread_create.c:333 #9 0x7f0a32e8c41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f0a37828940 (LWP 2278)): [KCrash Handler] #6 0x7f0a25ff05b9 in ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 #7 0x7f0a25fec7be in wl_proxy_destroy () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 #8 0x7f0a2453bc47 in KWayland::Client::PlasmaWindow::release() () from /usr/lib/x86_64-linux-gnu/libKF5WaylandClient.so.5 #9 0x7f0a2453bc6a in KWayland::Client::PlasmaWindow::~PlasmaWindow() () from /usr/lib/x86_64-linux-gnu/libKF5WaylandClient.so.5 #10 0x7f0a2453bd59 in KWayland::Client::PlasmaWindow::~PlasmaWindow() () from /usr/lib/x86_64-linux-gnu/libKF5WaylandClient.so.5 #11 0x7f0a3376baf3 in QObjectPrivate::deleteChildren (this=this@entry=0x7750960) at kernel/qobject.cpp:1997 #12 0x7f0a33775be4 in QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:1025 #13 0x7f0a2453c309 in KWayland::Client::PlasmaWindowManagement::~PlasmaWindowManagement() () from /
[kwin] [Bug 352943] Show Desktop effects "Window Aperture" and "Eye on screen" should be mutually exclusive
https://bugs.kde.org/show_bug.cgi?id=352943 Vlad Zagorodniy changed: What|Removed |Added Latest Commit||https://commits.kde.org/kwi ||n/c7298b24e6369f9bf68e83ca1 ||738cf060cc8c24e Version Fixed In||5.13.4 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 397308] New: Yakuake doesn't get focus if activated by mouse pointer
https://bugs.kde.org/show_bug.cgi?id=397308 Bug ID: 397308 Summary: Yakuake doesn't get focus if activated by mouse pointer Product: yakuake Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: and...@all-ein.net Target Milestone: --- Some times the Yakuake does not get focus when activated by mouse pointer. The Window comes don't but focus is still on the last thing that was focused. Version 3.0.5 Using Cionnamon -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 352943] Show Desktop effects "Window Aperture" and "Eye on screen" should be mutually exclusive
https://bugs.kde.org/show_bug.cgi?id=352943 Vlad Zagorodniy changed: What|Removed |Added Version Fixed In|5.13.4 |5.14.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 341393] desktop cube settings do not apply on subsequent changes
https://bugs.kde.org/show_bug.cgi?id=341393 Vlad Zagorodniy changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME CC||vladz...@gmail.com --- Comment #2 from Vlad Zagorodniy --- I also can't reproduce it. If you're still able to reproduce it, please reopen this bug report. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397305] failed to add tag to database
https://bugs.kde.org/show_bug.cgi?id=397305 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Can you download and start DebugView from Microsoft and then post the messages when you try to create a tag? Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361987] Morphing popups: When morphing to a bigger tooltip the old content is streched.
https://bugs.kde.org/show_bug.cgi?id=361987 Vlad Zagorodniy changed: What|Removed |Added CC||vladz...@gmail.com Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #8 from Vlad Zagorodniy --- (In reply to Artur O. from comment #6) > Transform/Morph the container but not the contents. The demo would be jquery > / webb since i dont have any knoledge in qml/qt/kde dev. Or since you don't > use kwin anymore maybe try to record the situation when it happens. As Thomas said, we can't do that because the Morphing Popups effect doesn't know anything about content, so the only viable option is to scale content. -- You are receiving this mail because: You are watching all bug changes.
[Planet KDE] [Bug 397309] New: Add back my feed to planet.
https://bugs.kde.org/show_bug.cgi?id=397309 Bug ID: 397309 Summary: Add back my feed to planet. Product: Planet KDE Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: feeds Assignee: j...@jriddell.org Reporter: aben...@kde.org Target Milestone: --- I had an issue for a few days with my domin. Now my planet is back to business. I would like to get it back. The link of the feed is: https://toscalix.com/feed/ -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 397292] Occasional delay when opening image file
https://bugs.kde.org/show_bug.cgi?id=397292 Henrik Fehlauer changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||rk...@lab12.net --- Comment #2 from Henrik Fehlauer --- > Gwenview sometimes delays when opening an image file. I'm not really sure what you mean by that, could you be more specific? For example: - How are you opening the image? - What is delayed exactly, opening of Gwenview, opening the image, displaying the image, general unresponsiveness of the whole computer? - Do you experience the delay also when switching to that image? > this image seems to consistently cause Gwenview to lag I don't notice anything wrong with that image, for me it's opening fine just like any other image really. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 397269] Touchpad is not working in Kde neon 18.04
https://bugs.kde.org/show_bug.cgi?id=397269 Nick te Lindert changed: What|Removed |Added CC||nicktelind...@gmail.com --- Comment #8 from Nick te Lindert --- I can confirm that my touchpad isn't working on my inspiron 15 3000. Which came preinstalled with ubuntu. I will try to install the synaptic drivers from xorg to see if that also solves the problem. The generic 18.04 is working correctly. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 351849] Margins often cut when printing
https://bugs.kde.org/show_bug.cgi?id=351849 --- Comment #33 from Michael Weghorn --- (In reply to Germano Massullo from comment #32) > (In reply to Michael Weghorn from comment #31) > > (In reply to Germano Massullo from comment #30) > > > Yes I would be interested in discussing this > > > > OK. Do you have a way to reproduce this in some way? (Otherwise it's > > impossible to further investigate the issue.) > > Unfortunately I am no longer able to reproduce the issue :-( Then I'd suggest to just be happy things are working as expected now. Should the problem still reappear at any point in time, there's still the option to investigate it again... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 264276] Extenders can be brought up twice when quickly clicking them
https://bugs.kde.org/show_bug.cgi?id=264276 --- Comment #3 from Vlad Zagorodniy --- > It would be great to know whether that's the case for Wayland. Looks like taks switcher window is being closed and opened. > The client would require a unique tag (maybe alongside the present property > data?) so the direction can be toggled based on this. The problem with this approach is that content can "jump". But, maybe, that's not that serious. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376648] Magic lamp produces artifacts when "minimizing" to tray
https://bugs.kde.org/show_bug.cgi?id=376648 Vlad Zagorodniy changed: What|Removed |Added CC||vladz...@gmail.com --- Comment #3 from Vlad Zagorodniy --- > When an application minimizes to tray KMail? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397310] New: rename issue
https://bugs.kde.org/show_bug.cgi?id=397310 Bug ID: 397310 Summary: rename issue Product: digikam Version: 5.6.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Albums-TreeView Assignee: digikam-bugs-n...@kde.org Reporter: gzi...@mail.ru Target Milestone: --- When I do rename of the file selection moves to next, but F2 (rename) not working, need to reselect (via mouse or keyboard). Also when I do rename of one file, it should not show progress dialog and should work much faster (please). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397310] rename issue
https://bugs.kde.org/show_bug.cgi?id=397310 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- I have never seen the problem with the selection. The dialog is necessary, in the current version it is also displayed here, if the renaming failed. Also, the renaming in the current developer version has been greatly accelerated. Your digiKam version is already quite old, can you use a more recent digiKam version (digiKam-5.9.0)? Which Linux distribution do you use? Maik -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 397276] composite transition with smaller clip causes unwanted cropping and displacement
https://bugs.kde.org/show_bug.cgi?id=397276 --- Comment #4 from Adam Spiers --- Thanks a lot for the reply! However I tried with the latest 18.04.1 AppImage and the problem is exactly the same. Regarding your other question, I originally installed kdenlive and its dependencies from the Packman openSUSE repositories, and if kdenlive 18.04.3 is not compatible with MLT 6.10.0 then that is a bug in the way these packages are packaged - check out line 74 of: https://pmbs.links2linux.org/package/view_file/Essentials/kdenlive/kdenlive.spec?expand=1 It only specifies a lower bound for MLT, not an upper bound, and currently the repository has MLT 6.10.0: https://pmbs.links2linux.org/package/show/Essentials/libmlt Is this upper bound documented anywhere? It's not mentioned at https://community.kde.org/Kdenlive/Development Thanks again! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372351] sphere cap deformation incorrectly scales sphere radius (should be cap radius only)
https://bugs.kde.org/show_bug.cgi?id=372351 Vlad Zagorodniy changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED CC||vladz...@gmail.com --- Comment #1 from Vlad Zagorodniy --- Fixed by https://phabricator.kde.org/R108:6408e0ba6045d03b8872eab71060ac8d6f13ee9f -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372351] sphere cap deformation incorrectly scales sphere radius (should be cap radius only)
https://bugs.kde.org/show_bug.cgi?id=372351 Vlad Zagorodniy changed: What|Removed |Added Version Fixed In||5.14.0 Latest Commit||https://commits.kde.org/kwi ||n/6408e0ba6045d03b8872eab71 ||060ac8d6f13ee9f -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397297] newly created folders not shown in the import from camera window
https://bugs.kde.org/show_bug.cgi?id=397297 --- Comment #2 from gzi...@mail.ru --- Yes. Download windows doesnt see newly created folders at all if they created after starting digikam in main window or in system. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397311] New: DIN A relation in "Aspect Ratio Crop"
https://bugs.kde.org/show_bug.cgi?id=397311 Bug ID: 397311 Summary: DIN A relation in "Aspect Ratio Crop" Product: digikam Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: ImageEditor Assignee: digikam-bugs-n...@kde.org Reporter: sicherl...@free.de Target Milestone: --- Dear Maintainer, it would be nice to have the possibility in "Aspect Ratio Crop" the relation DIN A (1:square root 2). Regards Reiner -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397310] rename issue
https://bugs.kde.org/show_bug.cgi?id=397310 --- Comment #2 from gzi...@mail.ru --- ubuntu 18.04, digikam from distro. I mean I do mass manual rename. So after renaming one file I want to rename next by pressing F2 again. And I mean the progress window should not be displayed if you doing rename only for one file (not the selection), not the rename dialog window, just progress. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 397312] New: konsole frequently segfaults during compilation of other applications
https://bugs.kde.org/show_bug.cgi?id=397312 Bug ID: 397312 Summary: konsole frequently segfaults during compilation of other applications Product: konsole Version: 18.04.3 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: gene...@sarifria.x10.bz Target Milestone: --- Created attachment 114386 --> https://bugs.kde.org/attachment.cgi?id=114386&action=edit backtrace (first line manually added) frequently occurs during compilation. could be related to #364135 . I'm unsure how to get debug information for all the required files (i couldn't seem to find all the packages providing them, and it won't let me send otherwise?) required files were: /usr/bin/konsole /usr/lib64/libQt5XcbQpa.so.5 /usr/lib64/libKF5Pty.so.5 /usr/lib64/libQt5Widgets.so.5 /usr/lib64/libkonsoleprivate.so.18 /usr/lib64/libQt5Core.so.5 /usr/lib64/libkdeinit5_konsole.so if you can tell me what packages provide them i'll happily install them and give a more useful backtrace. i'll include related files in the hopes it may help. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 --- Comment #35 from David Edmundson --- >I don't know if this is the right place, but I'm interested in knowing what >difference there is between setting XRender compositor and setting Rendering >backend = software. Compositor settings affect only the window manager. GL clients will still use GL. This setting affects only the clients (plasmashell / systemsettings / whatever) There are reasons to mix and match those two. (unfortunately it was requested my settings for plasma should be hidden) It seems I forgot to add the one line to support kscreenlocker :/ I shall add that for the next patch release. Sorry. In the meantime, you can export QT_QUICK_BACKEND=software globally and confirm if that fixes it. >and it also "solves" another bug I filed some time ago about sluggish desktop >interaction #388808. Awesome. >Unfortunately this setting breaks something because I can't see the themes >preview anymore in system settings -> workspace themes. That was reported and fixed this week. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397261] While undoing a stroke, the tiles don't refresh and messup the drawing
https://bugs.kde.org/show_bug.cgi?id=397261 Dmitry Kazakov changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||dimul...@gmail.com Resolution|--- |FIXED --- Comment #1 from Dmitry Kazakov --- The bug should be fixed by Andrew in: https://cgit.kde.org/krita.git/commit/?id=572b2ad2868b87a45297563db17fb9e3c98c52f5 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 397312] konsole frequently segfaults during compilation of other applications
https://bugs.kde.org/show_bug.cgi?id=397312 --- Comment #1 from gene...@sarifria.x10.bz --- see https://nofile.io/f/c8QrXjBNgyf/firefox-crash0.log for a log of a build that crashed konsole -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388808] RubberBand has repeated large texture uploads
https://bugs.kde.org/show_bug.cgi?id=388808 David Edmundson changed: What|Removed |Added Platform|Neon Packages |Kubuntu Packages CC||k...@davidedmundson.co.uk Ever confirmed|0 |1 Summary|interactions with the |RubberBand has repeated |desktop area are sluggish |large texture uploads Status|UNCONFIRMED |CONFIRMED Version|5.13.3 |5.10.5 --- Comment #3 from David Edmundson --- I don't want to have generic "it's sluggish" reports. As per that other thread the hardware is struggling with GL QtQuick. But in this case that hardware has highlighted a weak spot we should optimise regardless. RubberBand::RubberBand(QQuickItem *parent) : QQuickPaintedItem(parent) We're uploading a new texture the size of the band every single mouse move. Texture uploads are one of the slowest things we can do. A few thoughts: * Do we even want the QStyle theme on plasma? If not, we can just use a Rectangle / FrameSVG * If we do, we should render once and 9-tile it -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 261159] Wrong sliding animation for top edge autohide panels on screens with y-offset greater than 0
https://bugs.kde.org/show_bug.cgi?id=261159 Vlad Zagorodniy changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||vladz...@gmail.com Resolution|--- |FIXED --- Comment #2 from Vlad Zagorodniy --- Can't reproduce it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388808] RubberBand has repeated large texture uploads
https://bugs.kde.org/show_bug.cgi?id=388808 --- Comment #4 from Eike Hein --- Yeah, this has always been one of those "we know it's slow and just haven't gotten around to optimizing it yet" things yet. My one requirement is that FV doesn't hardcode the appearance of the rubberband. If it comes from QStyle or the Plasma theme I don't care much. I think consistency is nice, though. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 388174] valgrind with Wine quits with "Assertion 'cfsi_fits' failed"
https://bugs.kde.org/show_bug.cgi?id=388174 --- Comment #4 from Konstantin Kharlamov --- (In reply to Julian Seward from comment #3) > There have been a number of fixes to debuginfo reading in the git trunk > version recently. Can you try again with that, and see if this still > happens? Sorry for delay. Yeah, I just tested with git version, and it fails the same way. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397230] Plasma restarts constantly in a loop
https://bugs.kde.org/show_bug.cgi?id=397230 --- Comment #2 from Francisco F. --- I uninstalled GStreamer, Phonon and practically all KDE. Deleting cache and congfigurations. I reinstall everything and it remains the same. Then I update with Packman and it's still the same. With LXQt it works correctly. Restarting the computer or the KDE session sometimes stops restarting -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 397313] New: False positive on long double "uninitialised bytes"
https://bugs.kde.org/show_bug.cgi?id=397313
Bug ID: 397313
Summary: False positive on long double "uninitialised bytes"
Product: valgrind
Version: 3.12 SVN
Platform: Other
URL: https://github.com/ornladios/ADIOS/issues/184#issuecom
ment-411739144
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: axel.huebl@plasma.ninja
Target Milestone: ---
The following minimal example leads to a false positive in long double
variables on uninitialized bytes:
(minimal example by Norbert Podhorszki, ORNL)
#include
#include
#include
#include
#include
#include
#include
#include
int main (int argc, char ** argv)
{
charfilename[] = "test_longdouble_valgrind.data";
long double ld1 = 1.2345e+80;
long double *bufm = (long double *) malloc (sizeof(long double));
long double *bufc = (long double *) calloc (1, sizeof(long double));
memcpy (bufm, &ld1, sizeof(long double));
memcpy (bufc, &ld1, sizeof(long double));
int fd = creat(filename, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
write(fd, bufm, sizeof(long double));
write(fd, bufc, sizeof(long double));
close(fd);
free(bufm);
free(bufc);
return 0;
}
Valgrind complains about both the malloc'd and calloc'd buffers.
$ valgrind ./test_longdouble_valgrind
==15574== Memcheck, a memory error detector
==15574== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==15574== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==15574== Command: ./test_longdouble_valgrind
==15574==
==15574== Syscall param write(buf) points to uninitialised byte(s)
==15574==at 0x4F312C0: __write_nocancel (syscall-template.S:84)
==15574==by 0x40083F: main (in
/home/adios/work/test/other_tests/test_longdouble_valgrind)
==15574== Address 0x520404a is 10 bytes inside a block of size 16 alloc'd
==15574==at 0x4C2DB8F: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==15574==by 0x4007D8: main (in
/home/adios/work/test/other_tests/test_longdouble_valgrind)
==15574==
==15574== Syscall param write(buf) points to uninitialised byte(s)
==15574==at 0x4F312C0: __write_nocancel (syscall-template.S:84)
==15574==by 0x400855: main (in
/home/adios/work/test/other_tests/test_longdouble_valgrind)
==15574== Address 0x520409a is 10 bytes inside a block of size 16 alloc'd
==15574==at 0x4C2FB55: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==15574==by 0x4007EB: main (in
/home/adios/work/test/other_tests/test_longdouble_valgrind)
We are aware of the limitations listed here
http://valgrind.org/docs/manual/manual-core.html#manual-core.limits
but this still seems to be a bug.
Further information:
https://github.com/ornladios/ADIOS/issues/184#issuecomment-411728907
--
You are receiving this mail because:
You are watching all bug changes.
[korganizer] [Bug 397314] New: korganizer segfaults on exit
https://bugs.kde.org/show_bug.cgi?id=397314 Bug ID: 397314 Summary: korganizer segfaults on exit Product: korganizer Version: 5.7.3 Platform: Debian testing OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: onkekabo...@hotmail.com Target Milestone: --- Application: korganizer (5.7.3) Qt Version: 5.10.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.13 x86_64 Distribution: Debian GNU/Linux testing (buster) -- Information about the crash: - What I was doing when the application crashed: Korganizer always segfaults on exit. - Custom settings of the application: I have setup a view filter that hides completed TODOs. The crash can be reproduced every time. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2df783e2c0 (LWP 11036))] Thread 5 (Thread 0x7f2decf00700 (LWP 11041)): #0 0x7f2e0ced7739 in __GI___poll (fds=0x7f2de4003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f2e04006439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2e0400654c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2e0d41a64b in QEventDispatcherGlib::processEvents (this=0x7f2de4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f2e0d3c71fb in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f2e0d1fc316 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f2e0d200f90 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:376 #7 0x7f2e058edf2a in start_thread (arg=0x7f2decf00700) at pthread_create.c:463 #8 0x7f2e0cee1edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f2ded701700 (LWP 11039)): #0 0x7f2e0ced7739 in __GI___poll (fds=0x7f2de002b460, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f2e04006439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2e0400654c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2e0d41a64b in QEventDispatcherGlib::processEvents (this=0x7f2deb20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f2e0d3c71fb in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f2e0d1fc316 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f2e0d200f90 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:376 #7 0x7f2e058edf2a in start_thread (arg=0x7f2ded701700) at pthread_create.c:463 #8 0x7f2e0cee1edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f2dee912700 (LWP 11038)): #0 0x7f2e0ced7739 in __GI___poll (fds=0x7f2de8004db0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f2e04006439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2e0400654c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2e0d41a64b in QEventDispatcherGlib::processEvents (this=0x7f2de8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f2e0d3c71fb in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f2e0d1fc316 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f2e0c5a4015 in QDBusConnectionManager::run (this=0x7f2e0c618d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x7f2e0d200f90 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:376 #8 0x7f2e058edf2a in start_thread (arg=0x7f2dee912700) at pthread_create.c:463 #9 0x7f2e0cee1edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f2df51cb700 (LWP 11037)): #0 0x7f2e0ced7739 in __GI___poll (fds=0x7f2df51cac78, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f2e03b970f7 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f2e03b98d1a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f2df753e6e9 in QXcbEventReader::run (this=0x55ed13bac4e0) at qxcbconnection.h:408 #4 0x7f2e0d200f90 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:376 #5 0x7f2e058edf2a in start_thread (arg=0x7f2df51cb700) at pthread_create.c:463 #6 0x7f2e0cee1edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f2df783e2c0 (LWP 11036)): [KCrash Handler] #6 0x7f2e0bab8738 in QSharedPointer::data (this=0x82) at /usr/in
[kdevelop] [Bug 379669] KDevelop continues to hang on exit in itemrepository.h [Bucket::deleteItem]
https://bugs.kde.org/show_bug.cgi?id=379669 --- Comment #17 from David Nolden --- It doesn't make sense to fiddle around with the internals of the hash, when this only happens during shutdown. The question is what's different during shutdown than during the earlier cleanup calls. The last message by RJVB might indicate the problem. "deleteBucket" requires the types of items to be registered, so that it can call destructors (and eventually also delete other items referenced recursively). It seems that for some types, the factories are not registered. Maybe the problem is that some language plugin, which had some declared some types (what are 62 and 63?) was already unloaded and the factory unregistered. In that case, it would be necessary to make sure that the cleanup is called earlier, before any plugins are unloaded. By the way, it might also be a viable option to completely skip the final cleanup during shutdown. It updates the disk duchain cache, but the earlier cleanups that happen during runtime also update the disk cache, so the cache data loss would be bearable (depending on the duchain cleanup interval). -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 397315] New: IMAP folder does not refresh, no new mails show up, mail actions (e.g. move) do not have an effect
https://bugs.kde.org/show_bug.cgi?id=397315 Bug ID: 397315 Summary: IMAP folder does not refresh, no new mails show up, mail actions (e.g. move) do not have an effect Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: kdepim-b...@kde.org Reporter: ok...@suse.de CC: fab...@ritter-vogt.de Target Milestone: --- ## Observation After upgrade from openSUSE Leap 42.3 to openSUSE Leap 15.0 I have a recurring problem that kmail does not refresh folders for at least one IMAP account after a certain time, e.g. no new messages are received, actions on existing items does not do not have an effect, e.g. a move is not synced to the server. I called "kdebugsetting?" and enabled debug log output for all components already but so far that did not really provide me helpful details. What I tried as well is to delete all imap accounts and readd them. After that again all imap updates happen synchronous in two email clients (running thunderbird in parallel). Following https://de.manjaro.org/index.php?PHPSESSID=3m63tvu5ro6ud6tl7uuv1bleq0&topic=4795.0 I created an archive ~/local/tmp/akonadi_kontact_2018-07-20.tar.xz , deleted ~/.local/share/akonadi* as well as all config files with "mail" or "imap" in name from ~/.config/akonadi* as well as ~/.kde4/share/config/akonadi* and restarted akonadi and kmail, all messages got reindex when trying to access folders. I had to redo some settings, e.g. sent and archive folders. The versions of the packages are in most cases 17.12.3 as shipped with openSUSE Leap 15.0. Asked in IRC on freenode in #opensuse-kde, it was suggested to try libkf5imap5 >= 18.04.3 and follow https://techbase.kde.org/KDE_PIM/Akonadi/Debug_IMAP . I did update that package from KDE:Applications:18.04 but the same problem seems to appear. And it seems that IMAP is actually fine. seems something is trying to sync a folder and always at 4% for the same folder it gets stuck and then also INBOX is not updated anymore. Checking with akonadiconsole I can see that the agent in question is "akonadi_imap_resource_2" where the status is either "Syncing folder 2018 (4%)" or nothing at all in contrast to other agents including other imap resources that are in "Ready". The action "Show Task List" reveals ``` ResourceScheduler: Online current task: 1227 SyncCollection collection 129 queue 0 is empty queue 1 1 tasks: 1270 ChangeReplay queue 2 is empty queue 3 1 tasks: 1269 SyncCollectionAttributes collection 129 queue 4 4 tasks: 1228 SyncCollection collection 130 1229 SyncCollection collection 131 1230 SyncCollectionTreeDone 1273 SyncCollectionTree IMAP tasks: ``` And "Show Notification Logs shows: ``` Command: ItemChangeNotification Session: MessageViewer-94699637932608 MetaData: QVector() items: QVector(Item:271683(RID:208938, RREV:, mimetype: message/rfc822) resource: akonadi_imap_resource_2 parentCollection: 113 parentDestCollection: -1 destinationResource: itemParts: QSet() addedFlags: QSet(\SEEN) removedFlags: QSet() addedTags: QSet() removedTags: QSet() addedRelations: QSet() removedRelations: QSet() operation: 7 Command: ItemChangeNotification Session: kontact-476707713 MetaData: QVector() items: QVector(Item:271683(RID:208938, RREV:, mimetype: message/rfc822) resource: akonadi_imap_resource_2 parentCollection: 113 parentDestCollection: -1 destinationResource: itemParts: QSet(MDNStateAttribute) addedFlags: QSet() removedFlags: QSet() addedTags: QSet() removedTags: QSet() addedRelations: QSet() removedRelations: QSet() operation: 2 Command: ItemChangeNotification Session: kontact-476707713 MetaData: QVector() items: QVector(Item:271683(RID:208938, RREV:, mimetype: message/rfc822) resource: akonadi_imap_resource_2 parentCollection: 113 parentDestCollection: 129 destinationResource: akonadi_imap_resource_2 itemParts: QSet() addedFlags: QSet() removedFlags: QSet() addedTags: QSet() removedTags: QSet() addedRelations: QSet() removedRelations: QSet() operation: 3 ``` I can clean the task list by restarting or setting the agent to offline and online again but then the agent is again stuck in "Connection established." and folder contents still do not update. After some time it's "Ready", the INBOX folder still does not update. After some time it is back to "Syncing folder '2018' (4%)" and the task list shows comparable content as written above. Maybe there is some "faulty entry" that akonadi trips over? If yes, how could I identify that entry? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 397315] IMAP folder does not refresh, no new mails show up, mail actions (e.g. move) do not have an effect
https://bugs.kde.org/show_bug.cgi?id=397315 Fabian Vogt changed: What|Removed |Added Version|unspecified |5.8.3 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379669] KDevelop continues to hang on exit in itemrepository.h [Bucket::deleteItem]
https://bugs.kde.org/show_bug.cgi?id=379669 --- Comment #18 from David Nolden --- Btw. the cleanup is mainly concerning the on-disk cache structure. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 397316] New: akonadi loses connection with IMAP server after suspend (but not only, DB error too)
https://bugs.kde.org/show_bug.cgi?id=397316 Bug ID: 397316 Summary: akonadi loses connection with IMAP server after suspend (but not only, DB error too) Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: kdepim-b...@kde.org Reporter: yves.can...@ens-lyon.fr Target Milestone: --- Hi, I have redundant problems with kmail/akonadi, see: https://bugs.gentoo.org/661856 kmail shows it contacts IMAPS server (progression bar), but actually does not or does not show newer mails. And access to mails (even local) can be [too] long (minutes): I have to make many akonadictl fsck/restart, and each time, konsole reports a lot of errors. Many errors such as: Cleaning up missing external file: /home/ycaniou/.local/share/akonadi/file_db_data/47/794047_r0 for item: 218189 on part: 794047 org.kde.pim.akonadicore: Creating/updating items from the akonadi database failed: "" org.kde.pim.akonadicore: "" org.kde.pim.akonadicore: Creating/updating items from the akonadi database failed: "Multiple merge candidates, aborting" org.kde.pim.akonadicore: Error during ItemSync: "Multiple merge candidates, aborting" org.kde.pim.akonadiserver: DATABASE ERROR: org.kde.pim.akonadiserver: Error code: "1205" org.kde.pim.akonadiserver: DB error: "Lock wait timeout exceeded; try restarting transaction" org.kde.pim.akonadiserver: Error text: "Lock wait timeout exceeded; try restarting transaction QMYSQL3: Unable to execute statement" org.kde.pim.akonadiserver: Query: "UPDATE PimItemTable SET atime = ? WHERE ( ( PimItemTable.id = ? ) )" org.kde.pim.akonadiserver: Unable to update item access time org.kde.pim.akonadiserver: DATABASE ERROR: org.kde.pim.akonadiserver: Error code: "1205" org.kde.pim.akonadiserver: DB error: "Lock wait timeout exceeded; try restarting transaction" org.kde.pim.akonadiserver: Error text: "Lock wait timeout exceeded; try restarting transaction QMYSQL3: Unable to execute statement" org.kde.pim.akonadiserver: Query: "UPDATE PimItemTable SET rev = ?, remoteId = ?, remoteRevision = ?, gid = ?, collectionId = ?, mimeTypeId = ?, datetime = ?, atime = ?, dirty = ?, size = ? WHERE ( id = ? )" org.kde.pim.akonadiserver: Error during updating record with id 218741 in table "PimItemTable" "Lock wait timeout exceeded; try restarting transaction QMYSQL3: Unable to execute statement" org.kde.pim.akonadiserver: Error during updating record with id 794048 in table "PartTable" "Driver not loaded Driver not loaded" Cleaning up missing external file: /home/ycaniou/.local/share/akonadi/file_db_data/50/794050_r0 for item: 218190 on part: 794050 org.kde.pim.akonadiserver: Error during updating record with id 794050 in table "PartTable" "Driver not loaded Driver not loaded" Cleaning up missing external file: /home/ycaniou/.local/share/akonadi/file_db_data/51/794051_r0 for item: 218190 on part: 794051 Found duplicates 60 org.kde.pim.akonadiserver: DATABASE ERROR: org.kde.pim.akonadiserver: Error code: "1064" org.kde.pim.akonadiserver: DB error: "You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ') AND PartTable.storage = 1 )' at line 1" org.kde.pim.akonadiserver: Error text: "You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ') AND PartTable.storage = 1 )' at line 1 QMYSQL: Unable to execute query" org.kde.pim.akonadiserver: Query: "SELECT PartTable.id, PartTable.pimItemId, PartTable.partTypeId, PartTable.data, PartTable.datasize, PartTable.version, PartTable.storage FROM PartTable WHERE ( PartTable.pimItemId IN ( ) AND PartTable.storage = :0 )" Error while deleting duplicates Driver not loaded Driver not loaded Let me know what I can do to help. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388808] RubberBand has repeated large texture uploads
https://bugs.kde.org/show_bug.cgi?id=388808 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379669] KDevelop continues to hang on exit in itemrepository.h [Bucket::deleteItem]
https://bugs.kde.org/show_bug.cgi?id=379669 --- Comment #19 from RJVB --- >From memory, my patch mostly introduces common-sense error handling, it doesn't change anything else in the hash internals. I don't understand those, so I keep my hands off. I don't even understand why my attempts at handling deviant situations gracefully actually work instead of just moving the location of the crash, but it's a fact that they do. I won't claim it's a fix, provided you can prove that the situations currently not being handled can be avoided with 100% reliability. But if you can't prove that then it's more than a workaround and IMHO a fix for the crashes and hangs I've been seeing. And in that light it makes a whole lot more sense than just letting the code crash (regardless whether through an abort or after doing something with potential side-effects). Call it a necessary and hopefully temporary evil if you will, at least for production builds where all those Q_ASSERT checks become no-ops. As a user of a supposedly serious productivity tool I'm usually not interested in getting random aborts in order to help iron out a poorly understood glitch somewhere: the code should make reasonable attempts to recover from such a glitch if that is in anyway possible. IIRC I have also observed crashes at runtime, possibly (probably) when unloading projects. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 --- Comment #36 from Gianni --- (In reply to David Edmundson from comment #35) > Compositor settings affect only the window manager. GL clients will still use > GL. > This setting affects only the clients (plasmashell / systemsettings / > whatever) > There are reasons to mix and match those two. Thanks for explaining me. > In the meantime, you can export > QT_QUICK_BACKEND=software globally and confirm if that fixes it. I confirm that setting this env variable fixes the kscreenlocker_greet cpu issue for me! > >Unfortunately this setting breaks something because I can't see the themes > >preview anymore in system settings -> workspace themes. > > That was reported and fixed this week. Nice to hear! I hope to see this in the next bugfix update. In conclusion if I got this correctly the cpu issue was related to qt quick having bad performance issues (during screen lock) with outdated hardware not providing or providing an inefficient opengl backend. This is solved with setting the "plasma renderer" to "software", but this (until there's the patch you mentioned) doesnt comprehend kscreenlocker (or qtQuick?) so as a temporary workaround I also have to set QT_QUICK_BACKEND=software globally. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 393146] Memcheck fails assert "is_DebugInfo_active(di)" even though code built with -g
https://bugs.kde.org/show_bug.cgi?id=393146 Julian Seward changed: What|Removed |Added CC||jsew...@acm.org, ||philippe.waroquiers@skynet. ||be --- Comment #2 from Julian Seward --- I just hit this on x86_64 Linux, so maybe it's not OSX specific. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 396497] Timer display maintains opacity level from paused state when resumed/reset
https://bugs.kde.org/show_bug.cgi?id=396497 Peter Mühlenpfordt changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kde ||plasma-addons/28fe01674f6c9 ||a7fd644f9a753665f52d3188eaf --- Comment #1 from Peter Mühlenpfordt --- Git commit 28fe01674f6c9a7fd644f9a753665f52d3188eaf by Peter Mühlenpfordt. Committed on 09/08/2018 at 13:38. Pushed by muhlenpfordt into branch 'master'. [Timer applet] Reset opacity on timer start and reset Summary: When the Timer plasmoid is paused an opacity animation is used to signal this state. After resuming, restarting or resetting the timer the current opacity value is not reset which leads to nearly invisible and hard to read timer digits sometimes. This patch sets the opacity to 100% on timer (re)start and reset. Test Plan: * Start Timer plasmoid with e.g. 5 minutes countdown * Pause Timer by click * When opacity is low * Resume by click or * Restart with predefined time or * Reset timer * Opacity of running timer should always reset to 100% Reviewers: #plasma, davidedmundson Reviewed By: #plasma, davidedmundson Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D14701 M +2-1applets/timer/package/contents/ui/main.qml https://commits.kde.org/kdeplasma-addons/28fe01674f6c9a7fd644f9a753665f52d3188eaf -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397317] New: Huion H42
https://bugs.kde.org/show_bug.cgi?id=397317 Bug ID: 397317 Summary: Huion H42 Product: krita Version: 4.1.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: merten.groetsc...@web.de Target Milestone: --- Created attachment 114387 --> https://bugs.kde.org/attachment.cgi?id=114387&action=edit A video where I show how the Tablet driver closes I have an Huion H420, it worked in windos and and paint but when I open Krita i cant draw or move the cursor with the tablet. Im using the latest version of Krita ,but I can draw with the mouse. Also the little symbol down on my taskbar closes when Im opening Krita and I have to restart the program PenTabletDriver to use my tablet in Windos. Im really soryy for my bad englisch I come from Germany I hope you can understand what my Problem is. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 149903] impossible to open symlink
https://bugs.kde.org/show_bug.cgi?id=149903 Julian Schraner changed: What|Removed |Added Product|kio |kio-extras Component|tar |default Assignee|mbe...@ipsquad.net |plasma-b...@kde.org Version|unspecified |18.04.3 --- Comment #12 from Julian Schraner --- Okay, I'll move this report to kio-extras then. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388808] RubberBand has repeated large texture uploads
https://bugs.kde.org/show_bug.cgi?id=388808 --- Comment #5 from Gianni --- (In reply to David Edmundson from comment #3) > I don't want to have generic "it's sluggish" reports. As per that other > thread the hardware is struggling with GL QtQuick. I never meant to file a generic bug, but I couldn't produce a better description for what I saw. I entrusted the explanation of the problem to the appended video. I thought that if the "rubberband" was working on dolphin it ought to work the same way also on the bare desktop. I'm sorry if I caused confusion. > But in this case that hardware has highlighted a weak spot we should > optimise regardless. Glad to hear that. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 397318] New: [Wayland] Missing first input if typing too fast
https://bugs.kde.org/show_bug.cgi?id=397318 Bug ID: 397318 Summary: [Wayland] Missing first input if typing too fast Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tro...@free.fr CC: bhus...@gmail.com Target Milestone: --- On Wayland, if I lock my Plasma session and leave for several minutes, when I get back to the computer and type my password to unlock the session, in general some inputs are missed (my password is 6 characters long and only 5 "*" appear in the password field) ; I took the habit to type my password fast, without pressing any key before, since it works flawlessly on X11. But on Wayland, the first character I type is generally skipped. I think it also happen in SDDM. Plasma 5.13.4, Archlinux, KDE Frameworks 5.48. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 397313] False positive on long double "uninitialised bytes"
https://bugs.kde.org/show_bug.cgi?id=397313 --- Comment #1 from Axel --- Additional system information: Linux 4.9.0-5-amd64 x86_64 GNU/Linux gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516 sizeof(long double) == 16 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 397318] [Wayland] Missing first input if typing too fast
https://bugs.kde.org/show_bug.cgi?id=397318 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- I think that is intentional so the first key wakes up the screen first. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 397318] [Wayland] Missing first input if typing too fast
https://bugs.kde.org/show_bug.cgi?id=397318 --- Comment #2 from tro...@free.fr --- OK but on X11, it wakes the screen AND types my input. It's really convenient. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 337491] KDEPlatformTheme plugin causes text artifacts in Qt 5 application
https://bugs.kde.org/show_bug.cgi?id=337491 Oleksandr Natalenko changed: What|Removed |Added CC||oleksa...@natalenko.name --- Comment #31 from Oleksandr Natalenko --- It looks like the same applies to Clementine: https://github.com/clementine-player/Clementine/issues/5931 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 392913] NTFS mountpoints appears as hidden after mount
https://bugs.kde.org/show_bug.cgi?id=392913 Nate Graham changed: What|Removed |Added Version Fixed In||5.50 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379669] KDevelop continues to hang on exit in itemrepository.h [Bucket::deleteItem]
https://bugs.kde.org/show_bug.cgi?id=379669 --- Comment #20 from David Nolden --- Doing cleanup much earlier, e.g. in aboutToQuit, would probably be difficult, because you need to make sure that no duchain data structures (e.g. IndexedString) are accessed after that. All parsing must be finished, no "editor highlighting" or "code-completion" events queued in the event queue, etc. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379669] KDevelop continues to hang on exit in itemrepository.h [Bucket::deleteItem]
https://bugs.kde.org/show_bug.cgi?id=379669 --- Comment #21 from David Nolden --- I'm not saying what you're doing is bad, but it's probably not the most sustainable way to fix it. For example, this may leave unclaimed data in the duchain disk cache which will also consume memory in succeeding KDevelop runs, that can maybe never be reclaimed until the cache is cleared completely (which we usually do only after crashes). Maybe your other crashes with "project unloading" were also related to unloaded language plugins. Which language plugins do you use? Maybe a viable solution would be to generally avoid physically unloading language support plugins, because that may leave dangling data in the duchain cache which can not be handled any more during cleanup. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379669] KDevelop continues to hang on exit in itemrepository.h [Bucket::deleteItem]
https://bugs.kde.org/show_bug.cgi?id=379669 --- Comment #22 from David Nolden --- The reason why it helps is probably because it simply avoids the recursive destruction and data reclaim mechanisms. And if the data ranges are not put into the "free list", they will never be touched again and also not cause many problems, they will just stay sitting there consuming space and memory. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 397307] Hide or show pointer only effects the following screenshot
https://bugs.kde.org/show_bug.cgi?id=397307 --- Comment #2 from alex...@gmx.net --- You are right, I actually didn't consider all possible combinations and I also somehow hadn't seen the "Take a new screenshot button". With this in mind I think this FR can be closed. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 397307] Hide or show pointer only effects the following screenshot
https://bugs.kde.org/show_bug.cgi?id=397307 alex...@gmx.net changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 397307] Hide or show pointer only effects the following screenshot
https://bugs.kde.org/show_bug.cgi?id=397307 alex...@gmx.net changed: What|Removed |Added Resolution|INVALID |WONTFIX -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 397319] New: Cannot access kwallet after upgrading from Fedora 26 to Fedora 28
https://bugs.kde.org/show_bug.cgi?id=397319 Bug ID: 397319 Summary: Cannot access kwallet after upgrading from Fedora 26 to Fedora 28 Product: frameworks-kwallet Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: va...@kde.org Reporter: spa...@2deadmen.com CC: kdelibs-b...@kde.org Target Milestone: --- I have posted about this on the StackExchange website : https://unix.stackexchange.com/questions/461369/cannot-access-kwallet-after-upgrading-fedora-26-28 Here is the contents of that post: = When I try to open my wallet there is the standard read error that suggests the password may be incorrect. This happens both from kwalletmanager5 and using kwallet-query. The password is correct. My guess is something was changed in the KDE software with my upgrade to F28 yesterday. My understanding is that the best approach therefore would be to find a way to open the wallet somehow, say with an older version of kwalletmanager5, and export it to XML, then import it. What would be my options for accomplishing this? Or is there a better approach? = I have also posted this on the Fedora website: https://ask.fedoraproject.org/en/question/125129/cannot-access-kwallet-after-upgrading-f26-f28/ (currently awaiting moderation) I have tried installing KDE on a CentOS 7 machine, and it has the same issue. I have also tried backups of the kwl and salt files to ensure there is not some unknown issue with data corruption. I am currently open to any possible means to recover the kwallet. Please let me know what logs or information, if any, I can provide to clarify the context of this bug. Sorry, I wasn't sure about the version numbers involved, except for the fact that the kwalletmanager on Fedora 28 that I am using appears to be version 17.12.3. Thank you -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379669] KDevelop continues to hang on exit in itemrepository.h [Bucket::deleteItem]
https://bugs.kde.org/show_bug.cgi?id=379669 --- Comment #23 from RJVB --- > Maybe your other crashes with "project unloading" were also related to > unloaded language plugins. Which language plugins do you use? Possibly, but I cannot remember if I had any "interesting" terminal output at the time and haven't seen them for a while (thanks to my patch?). The big problem with this issue is that it appears to happen at random (the timeouts in certain operations may be responsible for that). That makes debugging it so tricky (and you really need to build without any optimisation, which is not an option for me for everyday use - which is how I use KDevelop...) I mostly work with C, C++ and ObjC(++) files, CMake files and the occasional Python file. But I've never taken stock exactly which language plugins get installed with KDevelop. I have a hunch (but no proof) that the dangling data that remains is only a single item at the time, not a whole tree, so the impact on subsequent sessions could be negligible. But I guess that impact could be made 0 by marking the duchain cache as dirty if the cleanup knowingly leaves dangling data, so that the whole cache gets rebuild during the next startup? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 397276] composite transition with smaller clip causes unwanted cropping and displacement
https://bugs.kde.org/show_bug.cgi?id=397276 --- Comment #5 from fritzib...@gmx.net --- I’m not a developer of Kdenlive. I just see that in some cases the code has to be adapted for MLT: https://phabricator.kde.org/R158:9b09dbb2b0de78d4eaf4011c8a462fdb3c6916b6. And this leads me to say stay with the AppImage. Could you redo the project again with the AppImage to see if you still get the crash? Don’t use the existing Kdenlive project because I assume the bug is “built in” now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 343465] Sliding Plasma dialog popups have corrupt corners
https://bugs.kde.org/show_bug.cgi?id=343465 Vlad Zagorodniy changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from Vlad Zagorodniy --- Can't reproduce it. So, marking it as RESOLVED WORKSFORME. If you are still able to reproduce it, please reopen this bug report. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397320] New: [Wish] No obvious way to probe the dirty/modified flag of the active document
https://bugs.kde.org/show_bug.cgi?id=397320 Bug ID: 397320 Summary: [Wish] No obvious way to probe the dirty/modified flag of the active document Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: nevinevi...@yahoo.com Target Milestone: --- I've been advised to open a wishbug for this. I am in the process of writing simple Python plugin. In short, I have a docker with two buttons for iterating back/forth through files from a given directory, replacing the open document with a new one. This operation implies that if the active document has unsaved changes they will be irreversibly lost. A possibility could be to always save the open file before switching it, but in this way iterating through the existing file list becomes much slower. Unnecessarily modifying files is generally not desirable on reliability and performance grounds. Therefore it would be useful to check out in advance if the active document has any unsaved changes. Oddly enough, I couldn't find any obviously named class member in the Krita Python API documentation for checking the modified/dirty status of a document, like for example something like isDirty(), or isModified(), etc. According to one developer on the official #Krita IRC channel, this doesn't seem to be currently possible. An alternative could be making Document::save() operate in a way that it doesn't actually save the document if no changes are detected, but it could be a potentially breaking change, and being able to save the document despite not having actually modified it could potentially have uses for some people. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 337355] plasma 5 panel gets too transparent in desktop cube
https://bugs.kde.org/show_bug.cgi?id=337355 Vlad Zagorodniy changed: What|Removed |Added CC||vladz...@gmail.com --- Comment #17 from Vlad Zagorodniy --- @Martin I propose to mark this bug as WONTFIX because we can't use the blur effect and the background effect with the desktop cube effect (also flip switch, cover switch, cube slide, glide, and so on). The only viable solution is to make panels such way that it doesn't matter whether background is blurred, something what Windows 7 did. For example, during the "fly" in/out animation, background behind windows is not blurred and most people don't notice that. Same with the Flip 3D: https://upload.wikimedia.org/wikipedia/ru/1/19/Windows_7_Flip_3D.jpg -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397278] dng conversion not possible
https://bugs.kde.org/show_bug.cgi?id=397278 Maik Qualmann changed: What|Removed |Added Version Fixed In||6.0.0 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Maik Qualmann --- Fixed with digiKam-6.0.0 pre-release and libraw-0.19. Maik -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397321] New: sending mail fails with server error with either ssl or tls
https://bugs.kde.org/show_bug.cgi?id=397321 Bug ID: 397321 Summary: sending mail fails with server error with either ssl or tls Product: kmail2 Version: 5.8.3 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: i...@jsteward.moe Target Milestone: --- I'm trying to send via Gmail with either TLS (587) or SSL (465), but either option fails with a cryptic "Server error". Receiving mail works just as expected. Not sure how to get debug information. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 397306] Wrong height of the list of files
https://bugs.kde.org/show_bug.cgi?id=397306 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||n...@kde.org Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Nate Graham --- Does the issue reproduce when using the Breeze widget theme? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 397296] "Reverse scroll direction" needs re-toggle on restart
https://bugs.kde.org/show_bug.cgi?id=397296 Nate Graham changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||n...@kde.org --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 395401 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395401] [evdev] Mouse settings are not loaded up at login
https://bugs.kde.org/show_bug.cgi?id=395401 Nate Graham changed: What|Removed |Added CC||pe...@traylorpark.com --- Comment #12 from Nate Graham --- *** Bug 397296 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
