[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock
https://bugs.kde.org/show_bug.cgi?id=435113 Janek Bevendorff changed: What|Removed |Added CC||k...@jbev.net -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 441412] New: Application Launcher focus not working as expected
https://bugs.kde.org/show_bug.cgi?id=441412 Bug ID: 441412 Summary: Application Launcher focus not working as expected Product: frameworks-plasma Version: 5.85.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: components Assignee: notm...@gmail.com Reporter: k...@jbev.net CC: plasma-b...@kde.org Target Milestone: --- When clicking the menu button on the desktop panel or pressing the Windows key, the application launcher opens with the search field focused (so far everything as expected). Without typing anything, the first entry in my list of favourites is marked with a selection border (even though the actual focus is in the search field), so I would expect that entry to be executed when I simply hit Enter, but that doesn't happen. I first have to move the focus over to the icons panel, so it's either "Left Arrow + Enter" (whereas "Up Arrow + Enter" unintuitively messes with the categories) or "Enter + Enter", which is confusing and annoying. This focusing behaviour gets even more annoying for search results. Here a single Enter stroke already launches the selected application (which is good), but sometimes the search is quite dumb and doesn't select the desired app first (and apparently doesn't remember previous searches either). One example would be "Discord" and "Discover". When I type "dis", "Discover" is always the entry that gets selected first (but is literally never the one I want), so I either have to spell out the whole name or simply select the entry above it, which is "Discord". However, to select it, I have to tap the Up Arrow key twice: Once for selecting the results panel and one more time for changing the selection before I can press Enter. This way, my muscle memory trained on other platforms has more than once launched "Discover" instead of "Discord". STEPS TO REPRODUCE (scenario 1) 1. Launch application menu 2. Press enter to launch pre-selected app from favourites panel 3. Get frustrated STEPS TO REPRODUCE (scenario 2) 1. Launch application menu 2. Type something 3. Try to select result above pre-selected entry by pressing up-arrow OBSERVED RESULT App favourites or search results panel needs to be selected explicitly before keyboard can interact with it. EXPECTED RESULT Results panel shouldn't have separate focus. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 21.04 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 431593] Please redesign or remove KeePassXC icons
https://bugs.kde.org/show_bug.cgi?id=431593 --- Comment #7 from Janek Bevendorff --- Thanks. I know this request is a bit strange perhaps, so thank you for removing the icons regardless. I love the Breeze theme in general, but the KeePassXC icons didn't quite transport the visuals of our branding. I wouldn't know that we are actively setting IconThemePath anywhere. If anything, it's Qt doing that under the hood. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 431593] Please redesign or remove KeePassXC icons
https://bugs.kde.org/show_bug.cgi?id=431593 --- Comment #4 from Janek Bevendorff --- > I'm confused about this request. If you want to enforce the use of your > upstream icons, you should be able to do that without any help from us. As > far as I know, we do not force apps to use breeze-icons. Icons within the application are no problem. But this is about the launcher and tray icons, which are taken from the system theme no matter what. > A possibly relevant merge request was started @ > https://invent.kde.org/frameworks/breeze-icons/-/merge_requests/74 Thanks -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 431593] New: Please redesign or remove KeePassXC icons
https://bugs.kde.org/show_bug.cgi?id=431593 Bug ID: 431593 Summary: Please redesign or remove KeePassXC icons Product: Breeze Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: k...@jbev.net CC: kain...@gmail.com Target Milestone: --- Breeze ships with a number of different override icons for KeePassXC: 1. A normal colourful one: https://raw.githubusercontent.com/KDE/breeze-icons/master/icons/apps/48/keepassxc.svg 2. A monochrome version: https://raw.githubusercontent.com/KDE/breeze-icons/master/icons/status/22/keepassxc-unlocked.svg 3. A monochrome version with an orange padlock: https://raw.githubusercontent.com/KDE/breeze-icons/master/icons/status/22/keepassxc-locked.svg We are not particularly happy with the way these icons were designed. The main flaws are: The colourful variant is using the wrong green tone and the shading is totally off (particularly the direction of the background gradient is wrong). If you want to provide a shaded override icon, please base it on our shaded macOS icon (without the background of course): https://github.com/keepassxreboot/keepassxc/blob/develop/share/macosx/keepassxc.iconset/icon_512x512%402x.png The monochrome variant has totally wrong proportions and the orange padlock doesn't fit the style at all. We have different versions for light and dark themes, which have been carefully adjusted for legibility even at low resolutions. In fact, our version has much higher fidelity and works better at small tray sizes than the highly simplified Breeze icon, which to me looks rather glitchy. Mind you, the light variant is not simply a colour-inverted dark variant. It is shape-inverted. See: https://github.com/keepassxreboot/keepassxc/tree/develop/share/icons/application/scalable/apps We are trying not to allow custom overrides for our icons, but Plasma seems to be ignoring that request and shows the Breeze overrides anyway. Generally, we would prefer not to be overridden by third-party icons at all, but if you need to show custom icons, please stick closer to the original and consider my requests. Personally, I have deleted the Breeze overrides from my system. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414785] New: Notifications cause system lag
https://bugs.kde.org/show_bug.cgi?id=414785 Bug ID: 414785 Summary: Notifications cause system lag Product: plasmashell Version: 5.17.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: k...@jbev.net CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Whenever a notification appears, my system starts lagging, including a sudden break in audio playback. Also, when I am copying files or downloading something in Chrome (with Plasma integration add-on), desktop effects show noticeable delay while the operation is running. For example, switching virtual desktops feels very sluggish, whereas without a progress notification going, it's fast and snappy. This happens even when the copy/download status notification popup isn't visible. As long as there is a hidden notification tracking the progress of an operation, the system is laggy. STEPS TO REPRODUCE 1. Play some music 2. Trigger a notification Alternatively: 1. Download a large file 2. Switch between desktops OBSERVED RESULT Audio stutter and effect delays. EXPECTED RESULT None of that. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 19.10 KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64 Qt Version: 5.12 GPU: Nvidia GTX 1080 Ti with 435.21 proprietary driver CPU: AMD Ryzen Threadripper 2920X -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413670] New: Keyboard modifier event for Capslock fired (incorrectly?) on key release in Wayland
https://bugs.kde.org/show_bug.cgi?id=413670 Bug ID: 413670 Summary: Keyboard modifier event for Capslock fired (incorrectly?) on key release in Wayland Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: k...@jbev.net Target Milestone: --- SUMMARY I am trying to implement the detection of caps lock in my application for Wayland. This in itself already requires around 30 lines of code using KWayland (way worse with the plain C API), compared to the single-line solutions for Windows or macOS or the three lines for X11, but worst of all, I noticed that the modifier change event is called both on key press and key release with different bit flags set. The first activation has bit #2 set, the second activate does not, so my application thinks that caps lock had been released again until I press any other key, which triggers the event a third time. I thought at first that this was just a bug in my implementation, but then I noticed that the caps lock indicator in the Plasma tray has the same issue and is only shown as long as I hold caps lock down. STEPS TO REPRODUCE 1. subscribe to KWayland::Client::Keyboard::modifiersChanged() for a keyboard 2. log the status of the `locked` bitmask 3. press and release caps lock OBSERVED RESULT Event is triggered a second time on key release with `locked & 0x10 == 0`. EXPECTED RESULT Event is either triggered only on key press or key release does not unset the caps lock bit SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon KDE Plasma Version: 5.17.80 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION I tried using the KDE-proprietary org_kde_kwin_keystate protocol extension as an alternative that requires fewer LOCs, but the compositor doesn't even announce this extension. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404375] Artifacts and flickering with Intel and Nvidia GPUs since Qt 5.12
https://bugs.kde.org/show_bug.cgi?id=404375 Janek Bevendorff changed: What|Removed |Added CC||k...@jbev.net --- Comment #11 from Janek Bevendorff --- I started seeing this on Arch Linux with Plasma 5.17. I am not exactly sure what triggers it, but I seem to be getting it mostly (but not only) after certain events like changing some compositing-related settings or other actions that somehow mess with the compositor. Once it starts, I get massive screen flicker whenever I open a new window and random black spots appear when a game decides to suspend compositing. Flickering only goes away after restarting KWin. I have an Nvidia card running with the proprietary driver. -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 391908] Cannot log into Google account with YubiKey
https://bugs.kde.org/show_bug.cgi?id=391908 Janek Bevendorff changed: What|Removed |Added Version|15.08.2 |git-latest -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 391908] Cannot log into Google account with YubiKey
https://bugs.kde.org/show_bug.cgi?id=391908 Janek Bevendorff changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Janek Bevendorff --- Any chance this gets fixed? I would really like to add my Drive account to Dolphin, but it's impossible. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388919] Plasma crashed after a modification in systray settings.
https://bugs.kde.org/show_bug.cgi?id=388919 Janek Bevendorff <k...@jbev.net> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||k...@jbev.net --- Comment #3 from Janek Bevendorff <k...@jbev.net> --- I can confirm this. 1. Right click the down arrow in the tray 2. Click System Tray Settings 3. Enable or disable some icons there 4. Click OK 5. Watch Plasma restart itself Happens 100% of the time. -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 391908] New: Cannot log into Google account with YubiKey
https://bugs.kde.org/show_bug.cgi?id=391908 Bug ID: 391908 Summary: Cannot log into Google account with YubiKey Product: KAccounts Version: 15.08.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: KCM Assignee: kde-telepathy-b...@kde.org Reporter: k...@jbev.net Target Milestone: --- I cannot connect my Google account, which is secure with a YubiKey as second factor. YubiKeys only work in Chrome, so trying to log in with the KDE online auth client shows an error message on the Google login page. This is not surprising and would also not be a problem if clicking the link for choosing a different method (i.e. Authenticator or SMS TOTP code), wouldn't close the authentication window and abort the process with an authentication error. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391907] New: Glide effect affects logout screen
https://bugs.kde.org/show_bug.cgi?id=391907 Bug ID: 391907 Summary: Glide effect affects logout screen Product: kwin Version: 5.12.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: k...@jbev.net Target Milestone: --- The logout screen / overlay that appears when clicking the logout or shutdown button in the menu is affected by the Glide desktop effect. I would expect this screen to always fade in, but instead it's scaled in like normal windows which looks really weird when Glide is active. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380209] Speed labels and speed graph empty after showing the applet twice
https://bugs.kde.org/show_bug.cgi?id=380209 Janek Bevendorff <k...@jbev.net> changed: What|Removed |Added CC||k...@jbev.net -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379433] Project is automatically selected when a file is saved
https://bugs.kde.org/show_bug.cgi?id=379433 --- Comment #5 from Janek Bevendorff <k...@jbev.net> --- Please check out this fix: https://phabricator.kde.org/D6019 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 380319] New: KDevelop master crashes upon startup when no files are opened
https://bugs.kde.org/show_bug.cgi?id=380319 Bug ID: 380319 Summary: KDevelop master crashes upon startup when no files are opened Product: kdevelop Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: k...@jbev.net Target Milestone: --- Application: kdevelop (5.1.40) Qt Version: 5.8.0 Frameworks Version: 5.34.0 Operating System: Linux 4.10.5-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I could start KDevelop, but once I closed all open files, it crashed and I couldn't start it again. I deleted all sessions in ~/.local/share/kdevelop/sessions/*, same result. KDevelop and KDevPlatform are both built from the current master branch. The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f354b279d80 (LWP 24877))] Thread 6 (Thread 0x7f34f98f7700 (LWP 25193)): #0 0x7f353eae039d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f354449821b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f354a4aa7a6 in () at /usr/lib/libQt5Qml.so.5 #3 0x7f354a47bba2 in () at /usr/lib/libQt5Qml.so.5 #4 0x7f354a47d18c in () at /usr/lib/libQt5Qml.so.5 #5 0x7f354a47dc46 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f354a47de8e in QQmlImports::addLibraryImport(QQmlImportDatabase*, QString const&, QString const&, int, int, QString const&, QString const&, bool, QList*) () at /usr/lib/libQt5Qml.so.5 #7 0x7f354a4427f9 in QQmlTypeLoader::Blob::addImport(QV4::CompiledData::Import const*, QList*) () at /usr/lib/libQt5Qml.so.5 #8 0x7f354a44315a in () at /usr/lib/libQt5Qml.so.5 #9 0x7f354a45 in () at /usr/lib/libQt5Qml.so.5 #10 0x7f354a43c578 in () at /usr/lib/libQt5Qml.so.5 #11 0x7f354a43cd32 in () at /usr/lib/libQt5Qml.so.5 #12 0x7f354a43dede in () at /usr/lib/libQt5Qml.so.5 #13 0x7f354a43df6d in () at /usr/lib/libQt5Qml.so.5 #14 0x7f354a4aa3d4 in () at /usr/lib/libQt5Qml.so.5 #15 0x7f354a4aaa3a in () at /usr/lib/libQt5Qml.so.5 #16 0x7f3545386d7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #17 0x7f354538e494 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #18 0x7f354467bd38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #19 0x7f354467defd in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #20 0x7f35446d2af3 in () at /usr/lib/libQt5Core.so.5 #21 0x7f353aa917b7 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #22 0x7f353aa91a20 in () at /usr/lib/libglib-2.0.so.0 #23 0x7f353aa91acc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #24 0x7f35446d2f0f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #25 0x7f354467a3aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #26 0x7f354449244a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #27 0x7f354a4aa085 in () at /usr/lib/libQt5Qml.so.5 #28 0x7f3544496e9c in () at /usr/lib/libQt5Core.so.5 #29 0x7f353eada297 in start_thread () at /usr/lib/libpthread.so.0 #30 0x7f354388025f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f34fa9a8700 (LWP 25171)): #0 0x7f35438762bd in poll () at /usr/lib/libc.so.6 #1 0x7f353aa919b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f353aa91acc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f35446d2f2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f354467a3aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f354449244a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f3544496e9c in () at /usr/lib/libQt5Core.so.5 #7 0x7f353eada297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f354388025f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f350c69c700 (LWP 24924)): #0 0x7f354388d09f in __libc_enable_asynccancel () at /usr/lib/libc.so.6 #1 0x7f35438762b2 in poll () at /usr/lib/libc.so.6 #2 0x7f353aa919b6 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f353aa91acc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f35446d2f2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f354467a3aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f354449244a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7
[kdevelop] [Bug 379433] Project is automatically selected when a file is saved
https://bugs.kde.org/show_bug.cgi?id=379433 Janek Bevendorff <k...@jbev.net> changed: What|Removed |Added CC||k...@jbev.net --- Comment #4 from Janek Bevendorff <k...@jbev.net> --- I'll have a look -- 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 Janek Bevendorff <k...@jbev.net> changed: What|Removed |Added CC||k...@jbev.net --- Comment #17 from Janek Bevendorff <k...@jbev.net> --- Would it be possible to remove this "feature"? It is super annoying. We are also fighting with ugly text artifacts in our application. We also cannot read back any text from the user interface, because whatever text we read from a label or menu entry is probably not what we initially wrote there. This has already cost me a lot of time to hunt down weird bugs where things somehow didn't work on KDE, but on all other platforms. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 364642] 16.04.3: kio_sftp is broken
https://bugs.kde.org/show_bug.cgi?id=364642 Janek Bevendorff <k...@jbev.net> changed: What|Removed |Added CC||k...@jbev.net --- Comment #6 from Janek Bevendorff <k...@jbev.net> --- I don't know if this is the same issue, but it may well be. My system log is getting spammed every few seconds with the following line: kdeinit5[19264]: log_kio_sftp: special(): polling I don't have any active SFTP connection right now, but Dolphin seems to have some dead sockets: sftp.so [kdeinit5] sftp local:/run/user/1000/klauncherTJ2531.1.slave-socket local:/run/user/1000/dolphinwX8815.8.slave-socket ... When I kill those sftp processes, I suddenly get a credentials window for a connection I used hours ago (I remember that I needed to try several times, because some connection attempts simply didn't return). Not sure if this is a Dolphin or KIO issue. Using KDE 5.9, kio kio 5.31.0 on Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 376916] Breeze GTK theme severely broken in Thunderbird
https://bugs.kde.org/show_bug.cgi?id=376916 --- Comment #3 from Janek Bevendorff <k...@jbev.net> --- Possible that it got updated as well. Wasn't exactly sure what caused the problem. It's still an issue, though. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 376916] Breeze GTK theme severely broken in Thunderbird
https://bugs.kde.org/show_bug.cgi?id=376916 --- Comment #1 from Janek Bevendorff <k...@jbev.net> --- Created attachment 104221 --> https://bugs.kde.org/attachment.cgi?id=104221=edit Conversation, note the gray background around the white rectangle, the reply and forward buttons also used to have white background -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 376916] New: Breeze GTK theme severely broken in Thunderbird
https://bugs.kde.org/show_bug.cgi?id=376916 Bug ID: 376916 Summary: Breeze GTK theme severely broken in Thunderbird Product: Breeze Version: 5.9.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: gtk theme Assignee: scionicspec...@gmail.com Reporter: k...@jbev.net Target Milestone: --- Created attachment 104220 --> https://bugs.kde.org/attachment.cgi?id=104220=edit Compose window With the latest update to 5.9.2, my Thunderbird started looking terrible. I got solid black lines as widget separators and my conversations (Thunderbird Conversations plugin) got an ugly gray background with a white rectangle instead of a fully white background. I attached screenshots to depict better what I mean. Everything worked fine in 5.9.0 (and probably 5.9.1). Native GTK applications look fine. Firefox seems to work as well, but Thunderbird looks terrible. Using Plasma 5.9.2 on Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 376680] File type icons not suitable for dark themes
https://bugs.kde.org/show_bug.cgi?id=376680 --- Comment #2 from Janek Bevendorff <k...@jbev.net> --- Created attachment 104121 --> https://bugs.kde.org/attachment.cgi?id=104121=edit Project Explorer Icons Sure. There you go. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 337891] Synchronise editor windows between Code and Debug modes
https://bugs.kde.org/show_bug.cgi?id=337891 Janek Bevendorff <k...@jbev.net> changed: What|Removed |Added Version|unspecified |5.1.0 CC||k...@jbev.net --- Comment #7 from Janek Bevendorff <k...@jbev.net> --- Is this still being worked on? It annoys the crap out of me that every time I start debugging, I completely lose track of where in the code I am. One more thing that annoys me is that the view doesn't automatically jump to the current line when stopping at a break point or crashing. I always have to open the Frame Stack window (which also isn't opened by default and quite hidden inside the menus) and click on an entry in the stack trace first. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376648] New: Magic lamp produces artifacts when "minimizing" to tray
https://bugs.kde.org/show_bug.cgi?id=376648 Bug ID: 376648 Summary: Magic lamp produces artifacts when "minimizing" to tray Product: kwin Version: 5.9.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: k...@jbev.net Target Milestone: --- When an application minimizes to tray (i.e. minimizes and then hides the window, so there is no taskbar button anymore), the magic lamp effect is targeted towards the cursor position instead of the taskbar. This works well most of the time, but sometimes it creates severe rendering artifacts in the form of moving vertical or horizontal bars. This effect is especially obvious when the cursor position is more to the center of the screen than to the edges. To generally improve the visuals of that effect, it would maybe also be good not to use the cursor position as a single pixel but rather an area of a few pixels. I don't know if that would get rid of the above-mentioned artifacts, but it would overall look less glitchy. KWin Support Information: == Version === KWin version: 5.9.0 Qt Version: 5.8.0 Qt compile version: 5.8.0 XCB compile version: 1.12 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_INPUT: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11901000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Blur: 0 onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 9 decorationButtonsRight: 6, 3, 4, 5 borderSize: 3 gridUnit: 10 font: Noto Sans,10,-1,5,50,0,0,0,0,0,Regular smallSpacing: 2 largeSpacing: 10 Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 1 glSmoothScale: 1 xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: false glStrictBindingFollowsDriver: true glCoreProfile: true glPreferBufferSwap: 99 glPlatformInterface: 1 windowsBlockCompositing: true Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 1 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: no Number of Screens: 2 Screen 0: - Name: DVI-I-1 Geometry: 0,0,2560x1440 Refresh Rate: 59.9506 Screen 1: - Name: DVI-D-0 Geometry: 2560,0,2560x1440 Refresh Rate: 59.9506 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 960/PCIe/SSE2 OpenGL version string: 3.1.0 NVIDIA 375.26 OpenGL platform interface: GLX OpenGL shading language version string: 1.40 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 375.26 GPU class: Unknown OpenGL version: 3.1 GLSL version: 1.40 X server version: 1.19.1 Linux kernel version: 4.9.6 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: yes Loaded Effects: --- zoom
[kwin] [Bug 370612] Artifacts when dragging maximized (wobbly) windows to different screen
https://bugs.kde.org/show_bug.cgi?id=370612 Janek Bevendorff <k...@jbev.net> changed: What|Removed |Added Version|5.8.0 |5.9.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 373093] Search / Find box unreadable when using dark theme
https://bugs.kde.org/show_bug.cgi?id=373093 --- Comment #8 from Janek Bevendorff <k...@jbev.net> --- I did set it in the application. So if with "runtime switching" you also mean the program restoring the color theme at startup, then your observation is correct. The problem, however, is not that I changed the setting at runtime and it would be gone after a full restart (like those artifacts that often appear when switching Plasma themes where certain UI elements keep their old appearance until I restart my session). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376609] New: Glide effect not activated at startup
https://bugs.kde.org/show_bug.cgi?id=376609 Bug ID: 376609 Summary: Glide effect not activated at startup Product: kwin Version: 5.9.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: k...@jbev.net Target Milestone: --- Since the last update, the Glide effect isn't activated at startup anymore. When I restart the system, windows just appear and disappear instantly without any animation. Most of the time I can fix it by going to the effects settings and turning the effect off and on again (no joke intended). Using Plasma 5.9.0 on Arch Linux with official Nvidia driver (375.26) KWin Support Information: The following information should be used when requesting support on e.g. http://forum.kde.org. It provides information about the currently running instance, which options are used, what OpenGL driver and which effects are running. Please post the information provided underneath this introductory text to a paste bin service like http://paste.kde.org instead of pasting into support threads. == Version === KWin version: 5.9.0 Qt Version: 5.8.0 Qt compile version: 5.8.0 XCB compile version: 1.12 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_INPUT: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11901000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Blur: 0 onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 9 decorationButtonsRight: 6, 3, 4, 5 borderSize: 3 gridUnit: 10 font: Noto Sans,10,-1,5,50,0,0,0,0,0 smallSpacing: 2 largeSpacing: 10 Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 1 glSmoothScale: 1 xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: false glStrictBindingFollowsDriver: true glCoreProfile: true glPreferBufferSwap: 99 glPlatformInterface: 1 windowsBlockCompositing: true Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 1 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: no Number of Screens: 2 Screen 0: - Name: DVI-I-1 Geometry: 0,0,2560x1440 Refresh Rate: 59.9506 Screen 1: - Name: DVI-D-0 Geometry: 2560,0,2560x1440 Refresh Rate: 59.9506 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 960/PCIe/SSE2 OpenGL version string: 3.1.0 NVIDIA 375.26 OpenGL platform interface: GLX OpenGL shading language version string: 1.40 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 375.26 GPU class: Unknown OpenGL version: 3.1 GLSL version: 1.40 X server version: 1.19.1 Linux kernel version: 4.9.6 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: yes Loaded Effects: --- zoom dimscreen
[frameworks-ktexteditor] [Bug 373093] Search / Find box unreadable when using dark theme
https://bugs.kde.org/show_bug.cgi?id=373093 --- Comment #4 from Janek Bevendorff <k...@jbev.net> --- I'm using the latest Git revision of KDevelop/KDevplatform on KF 5.30. I have the issue with both the Breeze Dark theme as well as the Krita Dark theme by David Revoy. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376180] New: Add support for switching between global menus without closing and reopening
https://bugs.kde.org/show_bug.cgi?id=376180 Bug ID: 376180 Summary: Add support for switching between global menus without closing and reopening Product: plasmashell Version: 5.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: k...@jbev.net CC: plasma-b...@kde.org Target Milestone: 1.0 The new global application menu does not allow easy switching of (sub)menus. Expected behavior: When I open a menu (e.g. File), the user should be able to switch to the next one (e.g. Edit) simply by moving the mouse. Current behavior: The first menu must be closed explicitly by clicking somewhere else before the user can switch to another menu. Motivation: It happens very often that I don't quite remember which application menu a certain action was in, that the application is new to me and I want to explore the menu or that I accidentally opened the wrong one. The easiest way to quickly browse through different (traditional) menus is to simply move the mouse to the next menu. With the new global application menu, this isn't possible which makes the global menu extremely tedious to use. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 344867] Setting custom background image in kcm_sddm does not work
https://bugs.kde.org/show_bug.cgi?id=344867 --- Comment #33 from Janek Bevendorff <k...@jbev.net> --- I can confirm this. I had a wallpaper set before 5.9.0 and now it's gone. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 372635] do not follow mousepointer when accessing krunner via keyboard
https://bugs.kde.org/show_bug.cgi?id=372635 Janek Bevendorff <k...@jbev.net> changed: What|Removed |Added CC||k...@jbev.net Version|5.8.4 |5.8.5 --- Comment #6 from Janek Bevendorff <k...@jbev.net> --- Either I never noticed it before or this must have been introduced by a recent update. It annoys the crap out of me as well. The KRunner list usually has a length of about half my screen height and one quarter its width. Since I rarely have my mouse cursor anywhere but around the center of my screen, it's very likely that I select something I didn't intend to select. What I notice is: when I invoke KRunner and type something, the first list item is selected, but then the selection is replaced by whatever my cursor is hovering over. I think the best solution would be to only change the selection if I actually move my mouse cursor. When I use the keyboard, I don't touch the mouse, so the cursor is stationary. A stationary cursor should not change the selection. An easy criterion for checking this would be if the cursor has moved since the last KRunner list update. If it hasn't, don't let it select anything. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 373088] Current tab highlighting counter-intuitive when using dark themes
https://bugs.kde.org/show_bug.cgi?id=373088 --- Comment #7 from Janek Bevendorff <k...@jbev.net> --- I agree that Breeze is the nicest theme of all those. But the inverted colors are clearly confusing and counter-intuitive. I'm not quite sure where the error lies, though. This weird tab coloring also appears with other dark color schemes, such as various Krita color schemes. So it could either be that they are all just based on each other and inherit the same bug or that it is really an issue with the Breeze widget style. The fact that changing the widget style leads to correct tab coloring lets strongly assume it is. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 373088] Current tab highlighting counter-intuitive when using dark themes
https://bugs.kde.org/show_bug.cgi?id=373088 --- Comment #2 from Janek Bevendorff <k...@jbev.net> --- Well, no matter which module this bug is in, it should be fixed and I don't want to change my widget style just because I use a different color theme. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 355540] Tooltips color wrong in gtk applications
https://bugs.kde.org/show_bug.cgi?id=355540 Janek Bevendorff <k...@jbev.net> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Version|5.7.2 |5.8.4 Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 373093] Search / Find box unreadable when using dark theme
https://bugs.kde.org/show_bug.cgi?id=373093 --- Comment #1 from Janek Bevendorff <k...@jbev.net> --- Created attachment 102531 --> https://bugs.kde.org/attachment.cgi?id=102531=edit Find in document: no matches found -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 373093] New: Search / Find box unreadable when using dark theme
https://bugs.kde.org/show_bug.cgi?id=373093 Bug ID: 373093 Summary: Search / Find box unreadable when using dark theme Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: k...@jbev.net Target Milestone: --- Created attachment 102530 --> https://bugs.kde.org/attachment.cgi?id=102530=edit Find in document, matches found When searching for text inside a document (Ctrl+F) the text inside the search / find box becomes unreadable when using a dark UI theme (see screenshots). The reason for this is that the background color is changed to either a light green or light red, but the text color is the default theme color. This works for bright themes with black text, but not at all for dark themes with white text. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 373092] Add Krita Dark Syntax Schema
https://bugs.kde.org/show_bug.cgi?id=373092 Janek Bevendorff <k...@jbev.net> changed: What|Removed |Added Version|unspecified |Git Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 373092] New: Add Krita Dark Syntax Schema
https://bugs.kde.org/show_bug.cgi?id=373092 Bug ID: 373092 Summary: Add Krita Dark Syntax Schema Product: kate Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: k...@jbev.net Target Milestone: --- Hi, I really like the new Breeze Dark syntax highlighting schema. However, for the UI I prefer slightly toned-down colors such as those provided by the Krita Dark theme. The background color is less intensive and a little more neutral, but still dark enough to be easy on the eye. Unfortunately, there is no matching syntax schema, so the editor area always looks a little off when using a different dark theme than Breeze Dark. It would therefore be great if Kate (and KDevelop) would also ship with a Krita Dark Schema. The colors would be basically the same as the Breez Dark Theme with the following changes: Editor Background Colors: Text Area: #313131 Current Line: #393939 Icon Border: Background Area: #363636 Word Wrap Marker: #424242 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 373088] New: Current tab highlighting counter-intuitive when using dark themes
https://bugs.kde.org/show_bug.cgi?id=373088 Bug ID: 373088 Summary: Current tab highlighting counter-intuitive when using dark themes Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: k...@jbev.net Target Milestone: --- Created attachment 102529 --> https://bugs.kde.org/attachment.cgi?id=102529=edit Guess which one is the active tab. Hint: it's not main.cpp When using the Breeze Dark theme (or any other dark theme such as Krita Dark), highlighting of the current tab is completely counter-intuitive. While with the normal (bright) Breeze theme, the current tab has a brighter background color than any of the other tabs, it is the other way round for dark themes (see attached screenshot). This is so absolutely counter-intuitive that even after many weeks of using KDevelop I'm still clicking the wrong tabs again and again, although I know that the colors are wrong. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 372803] Kontact crashes on launch
https://bugs.kde.org/show_bug.cgi?id=372803 Janek Bevendorff <k...@jbev.net> changed: What|Removed |Added CC||k...@jbev.net --- Comment #3 from Janek Bevendorff <k...@jbev.net> --- nvidia driver version 375.20 has a bug which leads to crashes or freezes when opening multiple OpenGL contexts or Vulkan instances. Downgrading to 375.10 should solve the problem until a fix is released. See https://devtalk.nvidia.com/default/topic/977518/linux/problems-with-multiple-opengl-applications-running-simultaneously-with-375-20-on-a-gtx970/post/5024978/#5024978 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372863] KDevelop freezes when opening parallel session
https://bugs.kde.org/show_bug.cgi?id=372863 --- Comment #3 from Janek Bevendorff <k...@jbev.net> --- Apparently, this is an NVIDIA bug in the driver version 375.20 which will be addressed with the next 375.xx release. For the meantime users should downgrade to 375.10 https://devtalk.nvidia.com/default/topic/977518/linux/problems-with-multiple-opengl-applications-running-simultaneously-with-375-20-on-a-gtx970/post/5024978/#5024978 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372863] KDevelop freezes when opening parallel session
https://bugs.kde.org/show_bug.cgi?id=372863 --- Comment #2 from Janek Bevendorff <k...@jbev.net> --- I was suspecting that. And indeed, I'm having similar issues with my lock screen. All graphics drivers drivers are up to date. This continuous flow of breaking bugs is super annoying right now. Only recently there was the problem that unlocking the screen or shutting down was prevented by a Qt bug, then plasma sessions messed up the screen config upon reboot and now this. I'll investigate further. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372863] New: KDevelop freezes when opening parallel session
https://bugs.kde.org/show_bug.cgi?id=372863 Bug ID: 372863 Summary: KDevelop freezes when opening parallel session Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: k...@jbev.net Target Milestone: --- When I open a second (parallel) KDevelop session, the program seems to enter an infinite loop. The window contents aren't updated (no draw refresh), my CPU goes to 100% and I can only kill KDevelop forcefully. To gather some debug information, I started KDevelop and then ran a second instance in a different session (kdevelop -s othersession) via GDB. The following is printed to the console: Starting program: /usr/bin/kdevelop -s kdevelop [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0x7fffd75cf700 (LWP 24210)] [New Thread 0x7fffd5803700 (LWP 24211)] [New Thread 0x7fffc4a7f700 (LWP 24212)] [New Thread 0x7fffb8505700 (LWP 24231)] [New Thread 0x7fffb7d04700 (LWP 24232)] [Thread 0x7fffb8505700 (LWP 24231) exited] [Thread 0x7fffb7d04700 (LWP 24232) exited] [New Thread 0x7fffb7d04700 (LWP 24235)] QOpenGLFramebufferObject: Unsupported framebuffer format. QOpenGLFramebufferObject: Unsupported framebuffer format. QOpenGLFramebufferObject: Unsupported framebuffer format. QOpenGLFramebufferObject: Unsupported framebuffer format. QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment. and then KDevelop hangs. After sending it a SIGINT, I get the following backtrace: #0 0x7fffc5b8409a in () at /usr/lib/libnvidia-glcore.so.375.20 #1 0x7fffc5b15ef1 in () at /usr/lib/libnvidia-glcore.so.375.20 #2 0x7fffc5b18121 in () at /usr/lib/libnvidia-glcore.so.375.20 #3 0x7fffc5b19071 in () at /usr/lib/libnvidia-glcore.so.375.20 #4 0x7fffc5766b54 in () at /usr/lib/libnvidia-glcore.so.375.20 #5 0x7fffc5768b06 in () at /usr/lib/libnvidia-glcore.so.375.20 #6 0x7fffeab9cf12 in QSGBatchRenderer::Renderer::unmap(QSGBatchRenderer::Buffer*, bool) () at /usr/lib/libQt5Quick.so.5 #7 0x7fffeab9ec67 in QSGBatchRenderer::Renderer::uploadBatch(QSGBatchRenderer::Batch*) () at /usr/lib/libQt5Quick.so.5 #8 0x7fffeaba924c in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #9 0x7fffeabb4bff in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #10 0x7fffeabb52cb in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #11 0x7fffeabc4ebe in QSGRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5 #12 0x7fffeac0e17e in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /usr/lib/libQt5Quick.so.5 #13 0x7fffeacf24d8 in QQuickRenderControl::render() () at /usr/lib/libQt5Quick.so.5 #14 0x7fffeb2732da in () at /usr/lib/libQt5QuickWidgets.so.5 #15 0x7fffeb274f44 in QQuickWidget::resizeEvent(QResizeEvent*) () at /usr/lib/libQt5QuickWidgets.so.5 #16 0x7631334e in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #17 0x762cbe0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #18 0x762d3581 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #19 0x755ebde0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #20 0x7630bc62 in QWidgetPrivate::sendPendingMoveAndResizeEvents(bool, bool) () at /usr/lib/libQt5Widgets.so.5 #21 0x7630fae3 in QWidgetPrivate::show_helper() () at /usr/lib/libQt5Widgets.so.5 #22 0x76312945 in QWidget::setVisible(bool) () at /usr/lib/libQt5Widgets.so.5 #23 0x72947890 in () at /usr/lib/libKDevPlatformSublime.so.10 #24 0x7fffb5f215ab in () at /usr/lib/qt/plugins/kdevplatform/26/kdevwelcomepage.so #25 0x7fffb5f218a3 in () at /usr/lib/qt/plugins/kdevplatform/26/kdevwelcomepage.so #26 0x76a1a10b in KPluginFactory::create(char const*, QWidget*, QObject*, QList const&, QString const&) () at /usr/lib/libKF5CoreAddons.so.5 #27 0x77ac35a7 in KDevelop::PluginController::loadPluginInternal(QString const&) () at /usr/lib/libKDevPlatformShell.so.10 #28 0x0041298a in () #29 0x74c5f291 in __libc_start_main () at /usr/lib/libc.so.6 #30 0x0040682a in _start () -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372795] KDevelop crashes after running unit tests when CTest is already running
https://bugs.kde.org/show_bug.cgi?id=372795 --- Comment #1 from Janek Bevendorff <k...@jbev.net> --- Additional information: this is absolutely reproducible. I have a Qt project (KeePassXC https://github.com/keepassxreboot/keepassxc/ ) and when I enable the CMake option WITH_GUI_TESTS, rebuild and then click "Run All Tests" in the Unit Tests panel, KDevelop first runs the GUI tests in tests/gui and then asks me twice (!) if I want to terminate the running CTest instance before running the other non-GUI tests. Confirming the second dialog reliably crashes KDevelop. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372795] New: KDevelop crashes after running unit tests when CTest is already running
https://bugs.kde.org/show_bug.cgi?id=372795 Bug ID: 372795 Summary: KDevelop crashes after running unit tests when CTest is already running Product: kdevelop Version: 5.0.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: k...@jbev.net Target Milestone: --- Application: kdevelop (5.0.2) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.8.8-2-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Ran unit tests. One instance of CTest was already running, so I was asked if I wanted to terminate it. For some reason, this dialog popped up twice. After confirming the first one, my unit tests were executed, after confirming the second dialog, KDevelop crashed. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9718215800 (LWP 4112))] Thread 16 (Thread 0x7f969e7fc700 (LWP 4252)): #0 0x7f970c9e6ecc in g_main_context_query () at /usr/lib/libglib-2.0.so.0 #1 0x7f970c9e76f8 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f970c9e789c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f971599e72b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f971594823a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f971576b0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f971576fd78 in () at /usr/lib/libQt5Core.so.5 #7 0x7f970e9d6454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f97150857df in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f969700 (LWP 4245)): #0 0x7f970e9dc10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9715770c2b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f970a0f01c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f970a0f4988 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f970a0ef263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f970a0f49e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f970a0ef263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f970a0f49e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f970a0ef263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f970a0f49e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f970a0ef263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f970a0f49e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f970a0ef263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7f970a0f49e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7f970a0ef263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7f970a0f49e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #16 0x7f970a0ef263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #17 0x7f970a0f49e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #18 0x7f970a0ef263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #19 0x7f970a0f49e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #20 0x7f970a0ef263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #21 0x7f970a0f49e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #22 0x7f970a0ef263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #23 0x7f970a0f49e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #24 0x7f970a0ef263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #25 0x7f970a0f21f9 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #26 0x7f971576fd78 in () at /usr/lib/libQt5Core.so.5 #27 0x7f970e9d6454 in start_thread () at /usr/lib/libpthread.so.0 #28 0x7f97150857df in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7f96bcff9700 (LWP 4244)): #0 0x7f970e9dc10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9715770c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
[plasmashell] [Bug 371734] Multiscreen lost configuration of the desktop
https://bugs.kde.org/show_bug.cgi?id=371734 --- Comment #15 from Janek Bevendorff <k...@jbev.net> --- Looks like it's working since I deleted the old activity and created a new one. But it's still a bug that shouldn't occur and should be fixed. I also still have these double desktop handles which is rather peculiar. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371734] Multiscreen lost configuration of the desktop
https://bugs.kde.org/show_bug.cgi?id=371734 Janek Bevendorff <k...@jbev.net> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||k...@jbev.net Ever confirmed|0 |1 --- Comment #14 from Janek Bevendorff <k...@jbev.net> --- One funny thing I noticed here is: I have two of these desktop handles which bring up the desktop context menu (Show Desktop, Add Widgets, Activities, Lock Widgets etc.). One of them is clickable and movable, the other is fixed and doesn't react to any mouse events. When I create a new activity, that new activity does not have duplicate handles. However, when I delete the original activity, the screen shortly goes black and then the new activity suddenly also has these double handles. Right after logging in, only the screen which still has the correct wallpaper (but the wrong panels) has duplicate handles, the other screen (which lost its wallpaper and widgets) does not, just like the newly created activity. As soon as I correct the wallpaper, that screen also gets double handles. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371734] Multiscreen lost configuration of the desktop
https://bugs.kde.org/show_bug.cgi?id=371734 Janek Bevendorff <k...@jbev.net> changed: What|Removed |Added CC||lloe...@gmail.com --- Comment #13 from Janek Bevendorff <k...@jbev.net> --- *** Bug 365249 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365249] KDE plasma 5.7.0 - dual monitor problem
https://bugs.kde.org/show_bug.cgi?id=365249 Janek Bevendorff <k...@jbev.net> changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #4 from Janek Bevendorff <k...@jbev.net> --- Looks like there are a couple of similar reports which look like the same problem to me. I'll mark them as duplicate. Reopen if you disagree. *** This bug has been marked as a duplicate of bug 371734 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371734] Multiscreen lost configuration of the desktop
https://bugs.kde.org/show_bug.cgi?id=371734 Janek Bevendorff <k...@jbev.net> changed: What|Removed |Added CC||johan.claudebreuninger@gmai ||l.com --- Comment #12 from Janek Bevendorff <k...@jbev.net> --- *** Bug 370434 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370434] Multi screen support broken in Plasma 5.8.0
https://bugs.kde.org/show_bug.cgi?id=370434 Janek Bevendorff <k...@jbev.net> changed: What|Removed |Added CC||k...@jbev.net Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #19 from Janek Bevendorff <k...@jbev.net> --- *** This bug has been marked as a duplicate of bug 371734 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371819] Plasma looses my panel position and wallpaper on each reboot, 4 monitors
https://bugs.kde.org/show_bug.cgi?id=371819 Janek Bevendorff <k...@jbev.net> changed: What|Removed |Added CC||k...@jbev.net Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #7 from Janek Bevendorff <k...@jbev.net> --- *** This bug has been marked as a duplicate of bug 371734 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371734] Multiscreen lost configuration of the desktop
https://bugs.kde.org/show_bug.cgi?id=371734 Janek Bevendorff <k...@jbev.net> changed: What|Removed |Added CC||tuxene...@mail.ru --- Comment #11 from Janek Bevendorff <k...@jbev.net> --- *** Bug 371819 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365249] KDE plasma 5.7.0 - dual monitor problem
https://bugs.kde.org/show_bug.cgi?id=365249 --- Comment #3 from Janek Bevendorff <k...@jbev.net> --- Additional information: when I switch the primary monitor, the panels do switch, that messes up the task manager. Windows from the left screen are shown in the task manager from the right screen vice versa. Manually moving the panels from on screen to the other works, but again, all that is gone when I reboot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365249] KDE plasma 5.7.0 - dual monitor problem
https://bugs.kde.org/show_bug.cgi?id=365249 Janek Bevendorff <k...@jbev.net> changed: What|Removed |Added Ever confirmed|0 |1 Severity|major |grave Version|5.7.0 |5.8.0 CC||k...@jbev.net Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Janek Bevendorff <k...@jbev.net> --- I have the same issue in Plasma 5.8.0. My primary monitor is the right-most monitor. When I log in, the panel from my left-hand (non-primary) monitor is on the right-hand monitor and vice versa. The widgets from the left monitor are also on the right while the left monitor itself has no widgets at all and the default Plasma wallpaper. When I go to the screen system settings and change the primary monitor to be the left one and then back to the right one, the panels switch position, but the left monitor still has the wrong wallpaper and no widgets. I always have to correct all this after every reboot because when I log out and log back in, my monitor desktop setup is messed up again. This is super annoying. I thought multi-monitor issues were solved, but this is completely broken here. One interesting side node: I have two of these "Desktop" handles which open the plasma desktop context menu as if I had two plasma desktops on top of each other. One of them is clickable and movable, the other isn't (see screenshot). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365249] KDE plasma 5.7.0 - dual monitor problem
https://bugs.kde.org/show_bug.cgi?id=365249 --- Comment #2 from Janek Bevendorff <k...@jbev.net> --- Created attachment 102291 --> https://bugs.kde.org/attachment.cgi?id=102291=edit Duplicate desktop handles -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 370422] kscreenlocker crashes when unlocking the session after resume from s2ram
https://bugs.kde.org/show_bug.cgi?id=370422 Janek Bevendorff <k...@jbev.net> changed: What|Removed |Added CC||k...@jbev.net --- Comment #11 from Janek Bevendorff <k...@jbev.net> --- I have a similar issue. Since the last update I cannot unlock my session anymore (on the desktop). I try four times and then the lock screen tells me that I have to use loginctl unlock-sessions. When I run kscreenlocker_greet manually, I unfortuantely only get a very useless stack trace and since I'm on arch, it's not that easy to install debug symbols, especially, when I don't really know for what package. #0 0x72df1ad0 in pthread_mutex_lock () from /usr/lib/libpthread.so.0 #1 0x7fffdcdf2e1c in ?? () from /usr/lib/libGLX_nvidia.so.0 #2 0x7fffdcdc9dc8 in ?? () from /usr/lib/libGLX_nvidia.so.0 #3 0x7fffd8806e89 in ?? () from /usr/lib/libEGL.so.1 #4 0x77de9ae8 in _dl_fini () from /lib64/ld-linux-x86-64.so.2 #5 0x73dce990 in __run_exit_handlers () from /usr/lib/libc.so.6 #6 0x73dce9ea in exit () from /usr/lib/libc.so.6 #7 0x73db9298 in __libc_start_main () from /usr/lib/libc.so.6 #8 0x0040946a in ?? () #9 0x7fffe158 in ?? () #10 0x001c in ?? () #11 0x0003 in ?? () #12 0x7fffe512 in ?? () #13 0x7fffe52f in ?? () #14 0x7fffe54c in ?? () #15 0x in ?? () >From the top part I would say this stack trace is different, but who knows... The bottom part, unfortunately, doesn't give any information about which packages need debug symbols. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 371042] Contrast issues with Breeze Dark Schema
https://bugs.kde.org/show_bug.cgi?id=371042 --- Comment #9 from Janek Bevendorff <k...@jbev.net> --- Yeah, that looks fine. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 371042] Contrast issues with Breeze Dark Schema
https://bugs.kde.org/show_bug.cgi?id=371042 --- Comment #7 from Janek Bevendorff <k...@jbev.net> --- Strange, I had a different color, although I haven't changed anything. With #31363b it's a little better, but not optimal. I would make the current line color darker. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 371042] Contrast issues with Breeze Dark Schema
https://bugs.kde.org/show_bug.cgi?id=371042 --- Comment #5 from Janek Bevendorff <k...@jbev.net> --- That's a little better. I think for normal text it's okay. But the issue with the current line still persists. The current line color is #3f3b51 and that makes comments very hard to read, even with the new color. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 370715] [PATCH] C++/boost indentation style is broken with automatic closing brackets
https://bugs.kde.org/show_bug.cgi?id=370715 --- Comment #26 from Janek Bevendorff <k...@jbev.net> --- Thanks. I'm a long-term KDE user and contributor to this bug tracker, but haven't really submitted any patches so far. :-) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 371197] Running certain unit tests freezes KDevelop and Plasma panels
https://bugs.kde.org/show_bug.cgi?id=371197 --- Comment #2 from Janek Bevendorff <k...@jbev.net> --- I'm not sure if this stacktrace is really helpful. There is no stack trace until I try to send it a SIGINT which kdevelop ignores. I can only kill it with SIGKILL. BTW I realized that not only Plasma panels are frozen, but also, e.g., Dolphin. Here's the stacktrace: Thread 1 "kdevelop" received signal SIGINT, Interrupt. 0x703800b3 in select () from /usr/lib/libc.so.6 #0 0x703800b3 in select () at /usr/lib/libc.so.6 #1 0x7fffd982a351 in () at /usr/lib/libQt5XcbQpa.so.5 #2 0x7fffd982a96f in () at /usr/lib/libQt5XcbQpa.so.5 #3 0x7fffd982c438 in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x716c66ab in QInternalMimeData::formats() const () at /usr/lib/libQt5Gui.so.5 #5 0x7fffd982c8e0 in () at /usr/lib/libQt5XcbQpa.so.5 #6 0x716c6936 in QInternalMimeData::retrieveData(QString const&, QVariant::Type) const () at /usr/lib/libQt5Gui.so.5 #7 0x7118d02b in () at /usr/lib/libQt5Core.so.5 #8 0x7118e16d in QMimeData::data(QString const&) const () at /usr/lib/libQt5Core.so.5 #9 0x75346a71 in KIO::isClipboardDataCut(QMimeData const*) () at /usr/lib/libKF5KIOWidgets.so.5 #10 0x70041f5b in KFilePreviewGenerator::Private::applyCutItemEffect(KFileItemList const&) () at /usr/lib/libKF5KIOFileWidgets.so.5 #11 0x70044de8 in KFilePreviewGenerator::Private::updateCutItems() () at /usr/lib/libKF5KIOFileWidgets.so.5 #12 0x71192659 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #13 0x716c28e9 in QClipboard::emitChanged(QClipboard::Mode) () at /usr/lib/libQt5Gui.so.5 #14 0x7fffd982abb0 in () at /usr/lib/libQt5XcbQpa.so.5 #15 0x7fffd9830d98 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () at /usr/lib/libQt5XcbQpa.so.5 #16 0x7fffd98318a5 in QXcbConnection::processXcbEvents() () at /usr/lib/libQt5XcbQpa.so.5 #17 0x711934b9 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #18 0x71e46e0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #19 0x71e4e581 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #20 0x71166de0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #21 0x7116956d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #22 0x711bb303 in () at /usr/lib/libQt5Core.so.5 #23 0x7fffe849b587 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #24 0x7fffe849b7f0 in () at /usr/lib/libglib-2.0.so.0 #25 0x7fffe849b89c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #26 0x711bb70f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #27 0x7116523a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #28 0x7116d73c in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #29 0x0040f1f5 in main () -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 371197] New: Running certain unit tests freezes KDevelop and Plasma panels
https://bugs.kde.org/show_bug.cgi?id=371197 Bug ID: 371197 Summary: Running certain unit tests freezes KDevelop and Plasma panels Product: kdevelop Version: 5.0.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: k...@jbev.net The vimode_modes unit test from the KTextEditor sources (from ktexteditor/autotests/src/vimode) freezes both KDevelop (the whole application) as well as my Plasma panels (not all of Plasma, though, just the panels) when run from the Unit Test tool panel. I don't know why this is (hell, I don't even know what exactly the test does), but this behavior is reproducible every time. Running the vimode_modes executable as standalone from the terminal works fine, though. I generally have the impression, that certain unit tests interfere with the responsiveness of the KDevelop UI. The vimode_keys test also freezes KDevelop for a couple of seconds, but then finishes and puts KDevelop back in a usable state. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets
https://bugs.kde.org/show_bug.cgi?id=370715 --- Comment #23 from Janek Bevendorff <k...@jbev.net> --- Thanks for the tip. I added a new Q_INVOKABLE to expose setAutoBrackets() to test scripts. The only possible pitfall I see here is that you have to explicitly disable auto brackets again at the end of your test, because the config is taken over to successive tests. I hope this won't backfire should "auto brackets on" become a default setting at some point. But in that case most tests would fail anyway, so not a big deal I guess. I submitted a patch with all the changes to Phabricator: https://phabricator.kde.org/D3104 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets
https://bugs.kde.org/show_bug.cgi?id=370715 --- Comment #21 from Janek Bevendorff <k...@jbev.net> --- Well, it has tests, but they fail (actually, the C++ ones don't, but only because I haven't adjusted them yet to my latest changes in the indenter which allow for auto brackets). Additionally, one already existing test for the C++ indenter fails now as I said above, but not in a way that would consider buggy. The reason why my tests fail is still that I can't get the test environment to enable auto brackets. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 371042] Contrast issues with Breeze Dark Schema
https://bugs.kde.org/show_bug.cgi?id=371042 --- Comment #1 from Janek Bevendorff <k...@jbev.net> --- I would suggest making the comment color a little lighter and highlight all docblock comments in green instead of gray. Certain tags in doc comments are already green, why not make everything that color to distinguish doc comments from normal comments (similar to IntelliJ's Darcula theme)? Tags could then either be bold, italics or just a little brighter in color. The same could work for the stuff within angle brackets (instead of unreadable black). -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 358776] per-project tab colors not updated on palette change
https://bugs.kde.org/show_bug.cgi?id=358776 Janek Bevendorff <k...@jbev.net> changed: What|Removed |Added CC||k...@jbev.net --- Comment #5 from Janek Bevendorff <k...@jbev.net> --- Not sure if it's worth reopening for this, but the file tabs still need a restart of KDevelop after changing the color scheme. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 371042] New: Contrast issues with Breeze Dark Schema
https://bugs.kde.org/show_bug.cgi?id=371042 Bug ID: 371042 Summary: Contrast issues with Breeze Dark Schema Product: frameworks-ktexteditor Version: 5.27.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: k...@jbev.net Created attachment 101609 --> https://bugs.kde.org/attachment.cgi?id=101609=edit Screenshot The Breeze Dark Schema has some contrast issues. Comments are pretty hard to read in general, but with highlighting for the current line, it becomes extra hard. Additionally, the highlighting of email addresses (and other stuff between <…>) inside comments is rendered as black text, making it almost impossible to read. I added a screenshot demonstrating these contrast issues. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets
https://bugs.kde.org/show_bug.cgi?id=370715 --- Comment #19 from Janek Bevendorff <k...@jbev.net> --- Created attachment 101608 --> https://bugs.kde.org/attachment.cgi?id=101608=edit Indenter Patch Yes, sure, I can append it here. The patch I uploaded includes the failing unit tests (because the auto bracket modeline) is ignored and is therefore not ready for merging yet. Since I couldn't leave it alone, I also experimented a little more with the C++ indenter. It had some functionality to consume characters to allow some sort of overwrite mode for brackets. That's pretty useful, but it completely breaks auto brackets. With a resolution for bug #370716 this should be a feature of the editor component anyway. So I removed that. It causes one unit test which tests comma consumption to fail, but not in a way that I would say the new behavior is buggy. With this consumption feature removed and a few more fixes to semicolon placement, auto brackets seem to work properly even with the C++ indenter. What do you think? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets
https://bugs.kde.org/show_bug.cgi?id=370715 --- Comment #17 from Janek Bevendorff <k...@jbev.net> --- Okay, I fixed it in C++/boost style as well. However, that indenter is overall a little broken. The only effect auto brackets had on it was that it inserted semicolons after opening braces. I fixed the semicolons and some over-indentation after condition or loop headers, but not the rest. It's not generating bullshit code anymore, but getting it to not ignore automatically inserted closing braces seems to be beyond reasonable effort. However, I still have the problem, that I can't produce proper unit tests, because the auto bracket modeline seems to be ignored. Otherwise I'd already submit the patches to Phabricator. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 371008] New: KDevelop crashes when reloading file
https://bugs.kde.org/show_bug.cgi?id=371008 Bug ID: 371008 Summary: KDevelop crashes when reloading file Product: kdevelop Version: 5.0.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: jbev_kdebugs...@refining-linux.org Application: kdevelop (5.0.1) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.8.1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: KDevelop tends to crash when files were modified externally. I experience this most often when I right click on a file in the project explorer and select Git->Revert. This can crash KDevelop when the file reloads. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1e8e86c800 (LWP 2123))] Thread 20 (Thread 0x7f1e07042700 (LWP 12917)): #0 0x7f1e8b67a48d in poll () at /usr/lib/libc.so.6 #1 0x7f1e82f66786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1e82f6689c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f1e8bf9c72b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1e8bf4623a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f1e8bd690f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f1e8bd6dd78 in () at /usr/lib/libQt5Core.so.5 #7 0x7f1e84f52454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f1e8b6837df in clone () at /usr/lib/libc.so.6 Thread 19 (Thread 0x7f1de37fe700 (LWP 12916)): #0 0x7f1e82fabdd4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f1e82f6673a in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1e82f6689c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f1e8bf9c72b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1e8bf4623a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f1e8bd690f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f1e8bd6dd78 in () at /usr/lib/libQt5Core.so.5 #7 0x7f1e84f52454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f1e8b6837df in clone () at /usr/lib/libc.so.6 Thread 18 (Thread 0x7f1de3fff700 (LWP 2648)): #0 0x7f1e84f5810f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1e7f83cac4 in () at /usr/lib/libQt5Script.so.5 #2 0x7f1e7f83cb09 in () at /usr/lib/libQt5Script.so.5 #3 0x7f1e84f52454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f1e8b6837df in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7f1e114d1700 (LWP 2251)): #0 0x7f1e8b6764ed in read () at /usr/lib/libc.so.6 #1 0x7f1e82faaa10 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1e82f66235 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f1e82f66724 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f1e82f6689c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f1e8bf9c72b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f1e8bf4623a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f1e8bd690f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f1e8984a84f in () at /usr/lib/libKDevPlatformLanguage.so.10 #9 0x7f1e8bd6dd78 in () at /usr/lib/libQt5Core.so.5 #10 0x7f1e84f52454 in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f1e8b6837df in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f1e22b5c700 (LWP 2247)): #0 0x7f1e8b690024 in __libc_enable_asynccancel () at /usr/lib/libc.so.6 #1 0x7f1e8b67a482 in poll () at /usr/lib/libc.so.6 #2 0x7f1e82f66786 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f1e82f6689c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f1e8bf9c72b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f1e8bf4623a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f1e8bd690f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f1e8bd6dd78 in () at /usr/lib/libQt5Core.so.5 #8 0x7f1e84f52454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f1e8b6837df in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f1e237fe700 (LWP 2229)): #0 0x7f1e84f5810f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1e8bd6ec2b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f1e806701c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f1e80674988 in () at
[kate] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets
https://bugs.kde.org/show_bug.cgi?id=370715 --- Comment #16 from Janek Bevendorff <jbev_kdebugs...@refining-linux.org> --- I can't get Kate (and therefore the editor) to respect the auto-brackets on modeline. Any tips? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets
https://bugs.kde.org/show_bug.cgi?id=370715
--- Comment #14 from Janek Bevendorff <jbev_kdebugs...@refining-linux.org> ---
I played a little with the ktexteditor code. The culprit for the C-style
indenter is this part (line 774):
} else if (firstPos == column - 1 && c == '}') {
var indentation = findLeftBrace(line, firstPos);
if (indentation == -1)
indentation = -2;
return indentation;
}
When I manually enter "{}", then firstPos is 4 and column is 6. However,
when using automatic bracket completion, my cursor is at 5, so the
condition is true and findLeftBrace() is called which retrieves a cursor
to the preceding brace like that:
var cursor = document.anchor(line, column, '{');
But since the cursor is before the insert position, this always results
in a (1, 0) cursor and therefore always unindents the line. My fix would
be to extend the initial check with one more condition:
} else if (firstPos == column - 1 && c == '}' &&
document.charAt(line, firstPos) == '}') {
This would simply check if the inserted character is actually where the
cursor is. If not, it was probably inserted automatically.
The C++/boost indenter seems to be a lot more complex and I haven't
looked into that issue yet.
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets
https://bugs.kde.org/show_bug.cgi?id=370715
--- Comment #13 from Janek Bevendorff <jbev_kdebugs...@refining-linux.org> ---
I downloaded a KDE Neon ISO to test this in KWrite and make sure it's
reproducible on other systems. I can indeed reproduce both issues:
C++/boost inserting {; instead of {} and C unindenting the line.
BTW C indenter also indents incorrectly in if statements when you want
the brace to be in its own line.
When I have this code
class X
{
private:
void foo()
{
if (true) |
}
};
and press enter, I get
class X
{
private:
void foo()
{
if (true)
|
}
};
which is okay. But when I type an opening brace, I get
class X
{
private:
void foo()
{
if (true)
{|}
}
};
This can't even be corrected by pressing Ctrl+Z. The unindentation for
the method foo() can be corrected this way, but when I press Ctrl+Z
here, I end up with
class X
{
private:
void foo()
{
if (true)
{|}
}
};
When I have the opening braces on the same line as the method or if
condition header, indentation works as expected.
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 371002] New: White text selection in Chrome when browser window loses focus
https://bugs.kde.org/show_bug.cgi?id=371002 Bug ID: 371002 Summary: White text selection in Chrome when browser window loses focus Product: Breeze Version: 5.7.95 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: gtk theme Assignee: scionicspec...@gmail.com Reporter: jbev_kdebugs...@refining-linux.org When I select text in Chrome and then click somewhere else on my desktop so that the Chrome window loses the focus, the formerly blue text selection becomes almost white which makes it impossible to read the selected (and also white) text. Other applications are not affected (although their inactive selection color is also brighter than the active selection color). For some reason, bugs.kde.org is one of the few websites that don't have this problem with text selection. However, the problem does appear with selection input fields (such as the Component and the Version fields in the guided editor or the advanced search). When they lose focus, the selection becomes unreadable. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 371002] White text selection in Chrome when browser window loses focus
https://bugs.kde.org/show_bug.cgi?id=371002 Janek Bevendorff <jbev_kdebugs...@refining-linux.org> changed: What|Removed |Added Version|5.7.95 |5.8.0 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 370716] Automatically overwrite closing brackets
https://bugs.kde.org/show_bug.cgi?id=370716 --- Comment #8 from Janek Bevendorff <jbev_kdebugs...@refining-linux.org> --- It should have the same logic as the already existing bracket matching/highlighting. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 370716] Automatically overwrite closing brackets
https://bugs.kde.org/show_bug.cgi?id=370716 --- Comment #6 from Janek Bevendorff <jbev_kdebugs...@refining-linux.org> --- It somehow also doesn't eat brackets when a new pair has been inserted within. So foo(bar(|)) will result in foo(bar())|) when typing ")" twice. The inner bracket is overwritten, but the outer bracket is not which is super annoying. Generally, I don't think it would be a problem to just consume any closing brackets as long as they have a corresponding opening bracket. You can a lot more than you lose. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets
https://bugs.kde.org/show_bug.cgi?id=370715
--- Comment #7 from Janek Bevendorff <jbev_kdebugs...@refining-linux.org> ---
Actually, what I said is not quite correct. Not the enter key unindents the
braces, but the completion of the closing brace. As soon as I type "{", the
line gets unindented:
class Foo
{
public:
void foo()
|
};
entering "{" leads to
class Foo
{
public:
void foo()
{|}
};
and then enter behaves correctly, but the line is already unindented:
class Foo
{
public:
void foo()
{
|
}
};
If the braces are already there and I just hit enter, they stay in place:
class Foo
{
public:
void foo()
{|}
};
now enter results in the desired
class Foo
{
public:
void foo()
{
|
}
};
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 370716] Automatically overwrite closing brackets
https://bugs.kde.org/show_bug.cgi?id=370716 --- Comment #4 from Janek Bevendorff <jbev_kdebugs...@refining-linux.org> --- I have to say, there are some corner cases where bracket eating has already annoyed me in IntelliJ. This is mostly, when revising brackets within brackets. But generally, this happens a lot less and is a lot less annoying than always ending with excess brackets because I'm too lazy to move my hand over to the arrow keys. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 370716] Automatically overwrite closing brackets
https://bugs.kde.org/show_bug.cgi?id=370716 --- Comment #2 from Janek Bevendorff <jbev_kdebugs...@refining-linux.org> --- I think that's what IntelliJ does. It always "eats" the braces and brackets as long as there are corresponding opening ones. It doesn't care if they were already there, just typed by the user or inserted automatically. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets
https://bugs.kde.org/show_bug.cgi?id=370715
--- Comment #6 from Janek Bevendorff <jbev_kdebugs...@refining-linux.org> ---
Either there or in the C++/boost indenter. All other indenters seem to work
fine with the automatic brace placement, but either don't indent my cursor
inside the braces, i.e.,
class Foo
{
public:
void foo()
{
|}
};
or do some very funky stuff such as
class Foo
{
public:
void foo()
{
|}
};
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets
https://bugs.kde.org/show_bug.cgi?id=370715
--- Comment #4 from Janek Bevendorff <jbev_kdebugs...@refining-linux.org> ---
Well, yeah, what I said. I want to have
class Foo
{
public:
void foo()
{
|
}
};
but with the C-style indenter I end up with
class Foo
{
public:
void foo()
{
|
}
};
even when I initially was at the correct indentation level, i.e. there:
class Foo
{
public:
void foo()
{|
};
As soon as I hit enter, the braces are automatically unindented.
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 370716] New: Automatically overwrite closing brackets
https://bugs.kde.org/show_bug.cgi?id=370716 Bug ID: 370716 Summary: Automatically overwrite closing brackets Product: kdevelop Version: 5.0.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: jbev_kdebugs...@refining-linux.org This is a feature which all JetBrains IDEs (IntelliJ IDEA, CLion, PyCharm etc.) have and which is super useful and makes working with automatically inserted closing brackets a lot more fun. When I type something like void foo(int bar|) (with | showing the current cursor position and the closing bracket automatically inserted), I usually need to move my finger to the right arrow key to skip the closing bracket. However, in IntelliJ I can simply type ")" instead which does the same, so I have void foo(int bar)| In KDevelop, however, I end up with void foo(int bar)|) Would be great if this could be implemented. This also makes it easy to not get lost in too many consecutive closing brackets, because you simply type ")" until the editor tries to insert a new one and then you know you reached the end (which isn't always obvious just with highlighting). Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets
https://bugs.kde.org/show_bug.cgi?id=370715 --- Comment #2 from Janek Bevendorff <jbev_kdebugs...@refining-linux.org> --- What "normal" C++ indenter do you mean? I only have "C style" and "C++/boost style". The former doesn't indent class methods properly and the latter is broken. Also for some reason all new files use the C-style indenter, even when set to C++ mode until I close and reopen the file (with "Override Kate indentation mode" turned on). -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 370715] C++/boost indentation style is broken with automatic closing brackets
https://bugs.kde.org/show_bug.cgi?id=370715 Janek Bevendorff <jbev_kdebugs...@refining-linux.org> changed: What|Removed |Added Component|ident |code completion -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 370715] New: C++/boost indentation style is broken with automatic closing brackets
https://bugs.kde.org/show_bug.cgi?id=370715
Bug ID: 370715
Summary: C++/boost indentation style is broken with automatic
closing brackets
Product: kdevelop
Version: 5.0.1
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: ident
Assignee: kdevelop-bugs-n...@kde.org
Reporter: jbev_kdebugs...@refining-linux.org
When automatic placement of closing brackets is enabled, the C++/boost
indentation style is broken.
When I enter an opening brace for a function body, it is completed with a
semicolon before the cursor instead of a closing brace after the cursor.
This can be tested with the following code (I denoted the current cursor
position with a pipe character |):
class Foo
{
public:
void foo()
|
};
Now when I type an opening brace after foo(), the result is this:
class Foo
{
public:
void foo()
{;|
};
although it should be this:
class Foo
{
public:
void foo()
{
|
}
};
With plain C style, it works, however then the indentation is wrong as both the
opening and the closing brace are automatically unindented:
class Foo
{
public:
void foo()
{
|
}
};
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 49719] breakpoints are hard to see with dark themes, icon border should be enabled by default
https://bugs.kde.org/show_bug.cgi?id=49719 Janek Bevendorff <jbev_kdebugs...@refining-linux.org> changed: What|Removed |Added Summary|breakpoints are not visible |breakpoints are hard to see |in editor window|with dark themes, icon ||border should be enabled by ||default -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 49719] breakpoints are not visible in editor window
https://bugs.kde.org/show_bug.cgi?id=49719 Janek Bevendorff <jbev_kdebugs...@refining-linux.org> changed: What|Removed |Added CC||jbev_kdebugs_01@refining-li ||nux.org Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 Version|unspecified |5.0.1 --- Comment #2 from Janek Bevendorff <jbev_kdebugs...@refining-linux.org> --- Sorry to reopen this, but I'd like to suggest enabling this setting by default. It took me about 10 minutes to figure out how to set breakpoints properly and another 30 minutes to learn about the "icon border". In 99% of the IDEs out there it is a common UI pattern to click on the line number gutter to set a break point which adds a red dot there. In KDevelop this didn't work. So I looked for a different way and finally found it in the right click context menu. However, it didn't seem to do anything. The reason why I though it didn't work at first was that the line highlight is so subtle that I completely overlooked it (talking about Breeze Dark theme, with default it's a little better). Then I thought "why the heck can't I just click the gutter" and wanted to open a feature request here and finally found this issue after a long thorough search. Only then I learned about the existence of "icon border" feature or what it is supposed to do (even if I knew it, I couldn't tell what it does from the name). I therefore suggest activating this feature by default. I don't see a reason why it should be disabled. I would also suggest changing the weird pixel emoji to a conventional red dot. It's clear what a red dot means (every other IDE uses red dots) and it stands out more and is less likely to be overlooked. With the default editor theme, both line highlight and icon are more or less visible, but with dark themes, they are both really hard to see. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370610] Automatically adjust window titlebar / window frame color to application theme
https://bugs.kde.org/show_bug.cgi?id=370610 --- Comment #3 from Janek Bevendorff <jbev_kdebugs...@refining-linux.org> --- Alright. I'll open this as a bug for Krita then. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370612] Artifacts when dragging maximized (wobbly) windows to different screen
https://bugs.kde.org/show_bug.cgi?id=370612 --- Comment #3 from Janek Bevendorff <jbev_kdebugs...@refining-linux.org> --- Sure. https://paste.kde.org/pl2kiokt6 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 370617] SMTP config dialog uses wrong default port
https://bugs.kde.org/show_bug.cgi?id=370617 --- Comment #2 from Janek Bevendorff <jbev_kdebugs...@refining-linux.org> --- 467 ist for TLS, but kind of obsolete. The standard port is 587 (usually with STARTTLS) which every server should use these days. But 25 ist definitely wrong, so I strongly disagree that this is a WONTFIX. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 370618] New: Cannot sync large amounts of mail through IMAP
https://bugs.kde.org/show_bug.cgi?id=370618 Bug ID: 370618 Summary: Cannot sync large amounts of mail through IMAP Product: Akonadi Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: jbev_kdebugs...@refining-linux.org CC: kdepim-b...@kde.org, vkra...@kde.org I've really been wanting to switch from Thunderbird to KMail for years now, but every time I try it, I run into the same issue again: Akonadi can't cope with my mail account. The raw maildir on the server has a size of 1.4GB and consists of thousands of mails, many with attachments. There are actually quite a few reports of hangs and freezes here, but I'm not quite sure whether any of them is related. My problem is: Akonadi starts syncing and then suddenly hangs and nothing's happening anymore. When I turn off "Download all mails for offline use", it sometimes gets to 100%, but instead of finishing, it continues with 110% until something like 180%. I also can't see any mails in KMail until Akonadi has finished the full sync (which can take a long time or doesn't happend at all). Reproducible: Always Steps to Reproduce: 1. Set up a mail account with > 1GB of mail 2. Try to sync it via Akonadi IMAP resource 3. Get frustrated Actual Results: KMail is completely useless because I can't get Akonadi to fetch mails from my IMAP account. Expected Results: Akonadi shouldn't hang, no matter how big the maildir behind the IMAP account is and it houldn't be necessary to restart Akonadi a hundred times to get through all the mails. Akonadi should also deliver already synced mails to KMail immediately, so that I don't have to wait for the full sync to finish before I can see any mail. A full sync, especially with download for offline use can take minutes or even hours. However, fetching just the mail headers is fast and should enable KMail to list mails within seconds, even for very large maildirs (Thunderbird actually manages to do that). It should also be possible to move mails to the front of the download queue, so I can click a mail in KMail during sync to show its contents immediately. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 370617] New: SMTP config dialog uses wrong default port
https://bugs.kde.org/show_bug.cgi?id=370617 Bug ID: 370617 Summary: SMTP config dialog uses wrong default port Product: kmail2 Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jbev_kdebugs...@refining-linux.org The SMTP configuration dialog suggests port 25 as default. This wrong. Port 25 is supposed to be the relay port, not the submission port. The correct port is 587. Many SMTP servers also accept mail submissions via port 25, but only for compatibility reasons. Some servers even block port 25 completely. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 370615] New: Cannot delete SMTP accounts
https://bugs.kde.org/show_bug.cgi?id=370615 Bug ID: 370615 Summary: Cannot delete SMTP accounts Product: kmail2 Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jbev_kdebugs...@refining-linux.org SMTP accounts in Settings->Accounts->Sending cannot be deleted. When clicking the "Remove" button, existing accounts are simply cleared and renamed to "Unnamed". Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370612] Artifacts when dragging maximized (wobbly) windows to different screen
https://bugs.kde.org/show_bug.cgi?id=370612 --- Comment #1 from Janek Bevendorff <jbev_kdebugs...@refining-linux.org> --- Created attachment 101552 --> https://bugs.kde.org/attachment.cgi?id=101552=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370612] New: Artifacts when dragging maximized (wobbly) windows to different screen
https://bugs.kde.org/show_bug.cgi?id=370612 Bug ID: 370612 Summary: Artifacts when dragging maximized (wobbly) windows to different screen Product: kwin Version: 5.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: jbev_kdebugs...@refining-linux.org When I drag a maximized window to another screen with the "Wobbly Windows" effect turned on, weird flickering artifacts are shown on the original screen. Sometimes these are just a few pixels, sometimes they show large parts of the window. This does not happen when dragging non-maximized windows. The attached screenshot shows a quite extreme example which I could only achieve with Chrome and the "Use system titlebar and borders" setting turned off (with that setting turned on, artifacts are usually less dramatic). However, some artifacts can also be produced with other applications such as Krita. Using proprietary nvidia driver and TwinView. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370610] New: Automatically adjust window titlebar / window frame color to application theme
https://bugs.kde.org/show_bug.cgi?id=370610 Bug ID: 370610 Summary: Automatically adjust window titlebar / window frame color to application theme Product: kwin Version: 5.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: jbev_kdebugs...@refining-linux.org I don't know if this is possible, but it would be great if Kwin could automatically adjust the titlebar/window frame color to an application's color scheme. Programs with dark KDE color schemes (such as Krita) look pretty awful with bright window borders. This can be fixed by adding windows rules for changing the window color scheme, but it would be better if Kwin could do that automatically. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering
https://bugs.kde.org/show_bug.cgi?id=353983 Janek Bevendorff <jbev_kdebugs...@refining-linux.org> changed: What|Removed |Added Version|5.7.4 |5.8.0 --- Comment #39 from Janek Bevendorff <jbev_kdebugs...@refining-linux.org> --- This still happens in 5.8.0 and is super annoying. Now I don't know if this is a bug specifically in Chrome or indeed a general NVIDIA issue, but when I started an application that disables compositing, not only the Plasma panels showed this bug, but also the Chrome UI froze until I minimized and restored the window. Anyhow, this bug is a super show stopper and deserves a fix. Any more insight on what exactly may be causing it? -- You are receiving this mail because: You are watching all bug changes.
