[frameworks-kservice] [Bug 430157] KDE .desktop parser complains about files that have Type= "Application" but no Exec line, although this situation is normal.
https://bugs.kde.org/show_bug.cgi?id=430157 Matt McDonald changed: What|Removed |Added CC||gardotd...@gmail.com --- Comment #5 from Matt McDonald --- (In reply to Ahmad Samir from comment #4) > I had read that comment; my previous message was sort of my reply to that, > creating a .desktop file that violates the desktop entry spec is wrong, and > then when tools that comply with the spec print errors about that, the > .desktop file should be fixed or removed. The problem is that it (the .desktop file) inherently *can't* be fixed, but the .desktop file is required for Wayland in order to be able to actually show the right icon when a window is open. So basically it can't be fixed, and it can't be removed. The only/best solution I can think of, because this is an extraordinarily edge case, is to add an exception to kservice that specifically ignores (or at least doesn't print any errors related to) the qemu.desktop file. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438127] latte crashes occasionally at login of dual-monitor setup
https://bugs.kde.org/show_bug.cgi?id=438127 --- Comment #18 from Matt McDonald --- (In reply to Michail Vourlakos from comment #17) > https://userbase.kde.org/LatteDock/HowToReportCrashes > > provided back traces are not employable. > They do not point to any related latte library and they do not provide the > needed followed codepath Alright well I'll try to use ddd and collect the correct information and provide it asap. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438127] latte crashes occasionally at login of dual-monitor setup
https://bugs.kde.org/show_bug.cgi?id=438127 --- Comment #16 from Matt McDonald --- It says to mark the bug as "REPORTED" but I've never seen that option. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438127] latte crashes occasionally at login of dual-monitor setup
https://bugs.kde.org/show_bug.cgi?id=438127 Matt McDonald changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #15 from Matt McDonald --- (In reply to Bug Janitor Service from comment #14) > This bug has been in NEEDSINFO status with no change for at least > 30 days. The bug is now closed as RESOLVED > WORKSFORME > due to lack of needed information. > > For more information about our bug triaging procedures please read the > wiki located here: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > Thank you for helping us make KDE software even better for everyone! I've provided the info needed on two separate occasions, but no one replied. I would like this reopened. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438127] latte crashes occasionally at login of dual-monitor setup
https://bugs.kde.org/show_bug.cgi?id=438127 Matt McDonald changed: What|Removed |Added CC||gardotd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438127] latte crashes occasionally at login of dual-monitor setup
https://bugs.kde.org/show_bug.cgi?id=438127 --- Comment #12 from Matt McDonald --- Created attachment 143786 --> https://bugs.kde.org/attachment.cgi?id=143786=edit New crash information added by DrKonqi latte-dock (0.10.4) using Qt 5.15.2 - What I was doing when the application crashed: Happened again at login after removing the media widget. Will try again after removing the other widgets mentioned. -- Backtrace (Reduced): #4 0x7fc537d1f860 in QSGTexture::setFiltering(QSGTexture::Filtering) () at /usr/lib/libQt5Quick.so.5 #5 0x7fc537d50b3c in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5 #6 0x7fc537d3741a in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #7 0x7fc537d3cb96 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #8 0x7fc537d3d5a5 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438127] latte crashes occasionally at login of dual-monitor setup
https://bugs.kde.org/show_bug.cgi?id=438127 --- Comment #11 from Matt McDonald --- (In reply to Michail Vourlakos from comment #9) > I wouldnt be surprised if this is a crash from one of: > 1. Virtual Desktop Bar. > 2. Media Bar > 3. Event Calendar > > as this is a startup crash make sure that you have followed steps from > proper latte autostarting at: > https://psifidotos.blogspot.com/2021/08/latte-dock-v0101-bug-fix-release.html > > for the applets you need to remove them one by one in order to find the > faulter in case it is an applet creating the issue. Sorry I somehow missed the email notification here. I don't restore my Plasma sessions. I start with a clean one. And I only have one Latte instance in my Autostart. I can't submit the crash report as the option is always grayed out. No idea why (when things like KWin crash, the option isn't grayed out, it's not like I've removed some system component). I've removed the mentioned widgets and will see if it changes anything. Before removing the widgets it would crash on login about 8 times out of 10. It almost never crashes during sessions after that, though. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438127] latte crashes occasionally at login of dual-monitor setup
https://bugs.kde.org/show_bug.cgi?id=438127 --- Comment #8 from Matt McDonald --- Created attachment 143146 --> https://bugs.kde.org/attachment.cgi?id=143146=edit Current Latte Layout -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438127] Latte Dock Crashes at Login
https://bugs.kde.org/show_bug.cgi?id=438127 --- Comment #5 from Matt McDonald --- (In reply to Gabriel from comment #4) > Created attachment 143115 [details] > New crash information added by DrKonqi > > latte-dock (0.10.3) using Qt 5.15.2 > > - What I was doing when the application crashed: > Shortly after waking my computer and unlocking a previous session, I opened > Plasma settings and searched for "feedback." It was around this time that I > noticed the "crashed" frowning icon in Latte Dock. > > Some other info that may be relevant: > - I have a dual-head setup > - My wallpaper on one monitor is static > - The wallpaper on the other monitor changes to a random selection on a > schedule > - One monitor refresh rate is 144Hz; the other is 60Hz > - One monitor is connected via DVI; the other HDMI > - I do not use the standard Plasma panel at all as I replaced it with Latte > Dock and a couple of widgets (Digital Clock, Panon) > > -- Backtrace (Reduced): > #4 0x7ffb8dae6860 in QSGTexture::setFiltering(QSGTexture::Filtering) () > at /usr/lib/libQt5Quick.so.5 > #5 0x7ffb8db17b3c in > QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState > const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5 > #6 0x7ffb8dafe41a in > QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch > const*) () at /usr/lib/libQt5Quick.so.5 > #7 0x7ffb8db03b96 in QSGBatchRenderer::Renderer::renderBatches() () at > /usr/lib/libQt5Quick.so.5 > #8 0x7ffb8db045a5 in QSGBatchRenderer::Renderer::render() () at > /usr/lib/libQt5Quick.so.5 I also have a dual-monitor setup, but both monitors are identical models. 1440p 165Hz. It happens about once every 2 or 3 logins. Once I'm logged in and it crashes and I restart it, it usually doesn't crash again for the duration of that session. It also crashes often when coming back to Plasma after shutting down my single-GPU passthrough VM. I'll try to get a backtrace again next time it happens but the drkonqi has been telling me there's no info. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438127] Latte Dock Crashes at Login
https://bugs.kde.org/show_bug.cgi?id=438127 Matt McDonald changed: What|Removed |Added Resolution|WORKSFORME |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443951] 5.23.0 Has Horrible Compositing Issues - Black Boxes and Flickering showing up
https://bugs.kde.org/show_bug.cgi?id=443951 --- Comment #51 from Matt McDonald --- (In reply to Rajinder Yadav from comment #50) > I am on openSUSE TW, how can I check if this fix has made it is? I am still > seeing this problem today, which seems to have shown up last week. > > I made a quick video, but unable to capture the flickering: > https://www.youtube.com/watch?v=YMKQJ-kWfVg > > Something all I need to do is open a new window and both my monitor will go > into rapid flickering which is really jarring! > > Operating System: openSUSE Tumbleweed 20211025 > KDE Plasma Version: 5.23.1 > KDE Frameworks Version: 5.87.0 > Qt Version: 5.15.2 > Kernel Version: 5.14.14-1-default (64-bit) > Graphics Platform: X11 > Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor > Memory: 62.7 GiB of RAM > Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 >Version Fixed In: 5.23.2 ... > Operating System: openSUSE Tumbleweed 20211025 > KDE Plasma Version: 5.23.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443951] 5.23.0 Has Horrible Compositing Issues - Black Boxes and Flickering showing up
https://bugs.kde.org/show_bug.cgi?id=443951
--- Comment #28 from Matt McDonald ---
(In reply to Vlad Zahorodnii from comment #27)
> Correction: m_vbo is an instance property. The issue seems to affect s_fbo.
> With the following patch
>
> diff --git a/src/libkwineffects/kwingltexture.cpp
> b/src/libkwineffects/kwingltexture.cpp
> index de08572ef..3e3c0fb8d 100644
> --- a/src/libkwineffects/kwingltexture.cpp
> +++ b/src/libkwineffects/kwingltexture.cpp
> @@ -334,6 +334,10 @@ void GLTexturePrivate::cleanup()
> {
> s_supportsFramebufferObjects = false;
> s_supportsARGB32 = false;
> +if (s_fbo) {
> +glDeleteFramebuffers(1, _fbo);
> +s_fbo = 0;
> +}
> }
>
> bool GLTexture::isNull() const
>
> I can't reproduce the bug.
I just built KWin with that patch and I can't get the bug to trigger as of
right now. I've alt-tabbed and opened windows and disabled and enabled
compositing like crazy, and I can't reproduce it anymore. I'll obviously keep
trying and will report what I find.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 443951] 5.23.0 Has Horrible Compositing Issues - Black Boxes and Flickering showing up
https://bugs.kde.org/show_bug.cgi?id=443951 --- Comment #25 from Matt McDonald --- I just hit alt-tab, then opened Konsole -> right-click -> Edit current profile then toggled compositing on and off and caused the issue as well. Yeah after my initial comment saying I could force it just by toggling compositing I found that it doesn't do it every time, but yeah... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443951] 5.23.0 Has Horrible Compositing Issues - Black Boxes and Flickering showing up
https://bugs.kde.org/show_bug.cgi?id=443951 --- Comment #20 from Matt McDonald --- I mean I can try it just for the sake of it but that parameter is specifically for preserving VRAM for suspend/resume, and I've never suspended this PC once. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443951] 5.23.0 Has Horrible Compositing Issues - Black Boxes and Flickering showing up
https://bugs.kde.org/show_bug.cgi?id=443951 --- Comment #19 from Matt McDonald --- (In reply to Vlad Zahorodnii from comment #18) > Can somebody verify whether setting `NVreg_PreserveVideoMemoryAllocations=1` > makes any difference? https://bugs.kde.org/show_bug.cgi?id=443341#c7 Maybe I should have been more clear but I don't suspend or hibernate my system, so that parameter doesn't apply. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443951] 5.23.0 Has Horrible Compositing Issues - Black Boxes and Flickering showing up
https://bugs.kde.org/show_bug.cgi?id=443951 --- Comment #16 from Matt McDonald --- Created attachment 142734 --> https://bugs.kde.org/attachment.cgi?id=142734=edit Journalctl take 2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443951] 5.23.0 Has Horrible Compositing Issues - Black Boxes and Flickering showing up
https://bugs.kde.org/show_bug.cgi?id=443951 --- Comment #15 from Matt McDonald --- Okay so full screen repaints isn't cutting it. After selecting the option earlier, I couldn't force the bug by switching to a TTY and back, but after I rebooted to test KWIN_USE_BUFFER_AGE=0 in my /etc/environment, and switching back and forth between "Automatic," "Only when cheap," and "Full screen repaints," I saw the issue on all three - which also means that KWIN_USE_BUFFER_AGE=0 doesn't help. kwin_x11 --replace still works to fix it. I'll attach the journalctl messages from this go-round. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443951] 5.23.0 Has Horrible Compositing Issues - Black Boxes and Flickering showing up
https://bugs.kde.org/show_bug.cgi?id=443951 --- Comment #13 from Matt McDonald --- Oh I'm also seeing a really horrible new bug where right-clicking tray icons on the system tray to bring up their menu will often cause the desktop to lose it's mind. Like, open windows will rapidly rotate in and out of focus, I'll get 20 "Configure Desktop and Wallpaper" windows opening (as if I right-clicked and selected "Configure Desktop and Wallpaper" a dozen or more times), I can't click on any window or do anything for like 3 minutes, I have to just wait for it to stop having a nervous breakdown. I'm not sure if this is related or not, but this also never once happened before 5.23 and I've seen it happen about twice a day since the upgrade (and it happens on both 470 and 495 Nvidia drivers). I'll try to get logs from that next time it happens too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443951] 5.23.0 Has Horrible Compositing Issues - Black Boxes and Flickering showing up
https://bugs.kde.org/show_bug.cgi?id=443951 --- Comment #12 from Matt McDonald --- Created attachment 142706 --> https://bugs.kde.org/attachment.cgi?id=142706=edit Journalctl log section -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443951] 5.23.0 Has Horrible Compositing Issues - Black Boxes and Flickering showing up
https://bugs.kde.org/show_bug.cgi?id=443951 --- Comment #11 from Matt McDonald --- (In reply to Vlad Zahorodnii from comment #10) > Can you please check a couple more things? > > * does this glitch show up with KWIN_USE_BUFFER_AGE=0 envvar? > * does this glitch show up with fullscreen repaints? (in order to force > fullscreen compositing, go to compositor settings and select "full screen > repaints" tearing prevention) > * when the glitch occurs, can you check kwin's logs? - I can't seem to force it with fullscreen repaints enabled. Obviously for performance reasons I hope to not have to keep that option enabled. - I put `KWIN_USE_BUFFER_AGE=0 in my /etc/environment and will try to force it (without full screen repaints) next reboot. - Actually I just got out of Doom Eternal and the bug appeared (obviously this was without full screen repaints) so I have the journalctl logs from that moment, but there doesn't seem to be much. I'll upload the relevant section as an attachment. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443951] 5.23.0 Has Horrible Compositing Issues - Black Boxes and Flickering showing up
https://bugs.kde.org/show_bug.cgi?id=443951 --- Comment #9 from Matt McDonald --- (In reply to Matt McDonald from comment #8) > Alt-Tabbing out of Control (the game) triggered it again. kwin_x11 --replace > fixed it. Actually just disabling and re-enabling compositing with Alt+Shift+F12 causes it. It wasn't the alt-tabbing out of the game, it was that I have desktop effects disabled and re-enabled upon startup and exit of the game. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443951] 5.23.0 Has Horrible Compositing Issues - Black Boxes and Flickering showing up
https://bugs.kde.org/show_bug.cgi?id=443951 --- Comment #8 from Matt McDonald --- Alt-Tabbing out of Control (the game) triggered it again. kwin_x11 --replace fixed it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443951] 5.23.0 Has Horrible Compositing Issues - Black Boxes and Flickering showing up
https://bugs.kde.org/show_bug.cgi?id=443951 --- Comment #7 from Matt McDonald --- Okay, so I can force it to happen every time by switching to a TTY and back. kwin_x11 --replace fixes it *most* times, once it caused everything to go wonky and I had to log out and back in, but yeah it generally fixes it. But before 5.23 I could change to a TTY and back and this wouldn't happen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443951] 5.23.0 Has Horrible Compositing Issues - Black Boxes and Flickering showing up
https://bugs.kde.org/show_bug.cgi?id=443951 --- Comment #6 from Matt McDonald --- (In reply to Vlad Zahorodnii from comment #3) > Based on the video, it seems like it's nvidia. > > > After a period of time, compositing will go completely wonky. > Have you noticed anything that is more likely to trigger these visual > artifacts? Playing Games that trigger disabling the compositor (by using the "disable desktop effects" toggle in Lutris), so basically enabling and disabling the compositor, and watching videos in browsers. >Can you also confirm that restart kwin fixes it? I'll try and trigger it and see if kwin_x11 --replace fixes it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443951] 5.23.0 Has Horrible Compositing Issues - Black Boxes and Flickering showing up
https://bugs.kde.org/show_bug.cgi?id=443951 --- Comment #5 from Matt McDonald --- Created attachment 142572 --> https://bugs.kde.org/attachment.cgi?id=142572=edit qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443951] 5.23.0 Has Horrible Compositing Issues - Black Boxes and Flickering showing up
https://bugs.kde.org/show_bug.cgi?id=443951 Matt McDonald changed: What|Removed |Added CC||gardotd...@gmail.com --- Comment #1 from Matt McDonald --- Created attachment 142568 --> https://bugs.kde.org/attachment.cgi?id=142568=edit qdbus org.kde.KWin -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443951] New: 5.23.0 Has Horrible Compositing Issues - Black Boxes and Flickering showing up
https://bugs.kde.org/show_bug.cgi?id=443951 Bug ID: 443951 Summary: 5.23.0 Has Horrible Compositing Issues - Black Boxes and Flickering showing up Product: kwin Version: 5.23.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: gardotd...@gmail.com Target Milestone: --- Created attachment 142567 --> https://bugs.kde.org/attachment.cgi?id=142567=edit output of cat /proc/`pidof kwin_x11`/maps | grep gl SUMMARY Only hours after updating to 5.23.0, I've noticed horrible black boxes and flickering issues showing up. When fullscreening and un-fullscreening a video on YouTube in Brave Browser, black boxes show up everywhere when un-fullscreening and disappear when going back to fullscreen. Resizing windows causes really awful flickering. Popups like OBS's settings menu cause the whole screen behind the window to go black, and then you can make the black disappear by dragging the window around. It's really bad. Rebooting temporarily fixes it, but it always comes back. This issue was not present on 5.22. STEPS TO REPRODUCE 1. Upgrade to 5.23.0 2. Make sure compositing is enabled, OpenGL 3.1 3. After a period of time, compositing will go completely wonky. OBSERVED RESULT Compositing is essentially broken EXPECTED RESULT Compositing doesn't cause giant black boxes and flickering. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Two short video clips demonstrating the issue(s): Black Boxes when fullscreen/unfullscreening: https://youtu.be/g5oObBP07VU Black everything, flickering when resizing: https://youtu.be/P0NMTpt5pW0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443480] New: Global Menu Activation Breaks When Using Two Monitors
https://bugs.kde.org/show_bug.cgi?id=443480 Bug ID: 443480 Summary: Global Menu Activation Breaks When Using Two Monitors Product: plasmashell Version: 5.22.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: gardotd...@gmail.com CC: mvourla...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY If you use two monitors and have a panel with the Global Menu widget on each monitor, it glitches out to where it will only follow one monitor. For example, if I have Monitor 1 (Primary) and Monitor 2, if I open Dolphin, there will be no Global Menu on Monitor 1. If I move it to Monitor 2, the Global Menu activates on BOTH Monitor 1's panel and Monitor 2's panel. If I move Dolphin back to Monitor 1, the Global Menu (on both monitors) disappears. If I delete the Global Menu widget and re-add it, it will temporarily work as expected (where the Global Menu activates when the app is on that monitor). Actually now that I'm typing this I tried removing the second Global Menu and the first one is still only following monitor 2. It's hard to explain, so here's a video: https://youtu.be/LveDjmk34KY STEPS TO REPRODUCE 1. Have two monitors with a panel on each monitor 2. Add global menu to the main monitor's panel (or both panels) 3. For a short time it will work as intended, but it always reverts to this behavior at some point (always after a reboot too from what I can tell) OBSERVED RESULT Global Menu follows the wrong display EXPECTED RESULT Global Menu follows the correct display SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, kernel 5.14.7 (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 *Note: Under the Version drop down on this bug report page, 5.22.5 isn't available. I'm on 5.22.5. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 438127] New: Latte Dock Crashes at Login
https://bugs.kde.org/show_bug.cgi?id=438127 Bug ID: 438127 Summary: Latte Dock Crashes at Login Product: kde Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: gardotd...@gmail.com Target Milestone: --- Application: latte-dock (0.9.91) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.6-159-tkg-cfs x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: It was as I logged in. I just recently changed my dock/panel setup, and added two new latte dock panels to replace the system panel at the top of each monitor. When I logged in, Latte crashed. The crash can be reproduced sometimes. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [KCrash Handler] #4 0x7f5ca867e840 in QSGTexture::setFiltering(QSGTexture::Filtering) () at /usr/lib/libQt5Quick.so.5 #5 0x7f5ca86afb1c in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5 #6 0x7f5ca86963fa in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #7 0x7f5ca869bb76 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #8 0x7f5ca869c585 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #9 0x7f5ca8683602 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #10 0x7f5ca86f2123 in QSGOpenGLLayer::grab() () at /usr/lib/libQt5Quick.so.5 #11 0x7f5ca86f275e in QSGOpenGLLayer::updateTexture() () at /usr/lib/libQt5Quick.so.5 #12 0x7f5ca8861b97 in QQuickOpenGLShaderEffectMaterial::updateTextures() const () at /usr/lib/libQt5Quick.so.5 #13 0x7f5ca8683dad in QSGRenderer::preprocess() () at /usr/lib/libQt5Quick.so.5 #14 0x7f5ca86835c9 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #15 0x7f5ca86f2123 in QSGOpenGLLayer::grab() () at /usr/lib/libQt5Quick.so.5 #16 0x7f5ca86f275e in QSGOpenGLLayer::updateTexture() () at /usr/lib/libQt5Quick.so.5 #17 0x7f5ca8861b97 in QQuickOpenGLShaderEffectMaterial::updateTextures() const () at /usr/lib/libQt5Quick.so.5 #18 0x7f5ca8683dad in QSGRenderer::preprocess() () at /usr/lib/libQt5Quick.so.5 #19 0x7f5ca86835c9 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #20 0x7f5ca86f2123 in QSGOpenGLLayer::grab() () at /usr/lib/libQt5Quick.so.5 #21 0x7f5ca86f275e in QSGOpenGLLayer::updateTexture() () at /usr/lib/libQt5Quick.so.5 #22 0x7f5ca8861b97 in QQuickOpenGLShaderEffectMaterial::updateTextures() const () at /usr/lib/libQt5Quick.so.5 #23 0x7f5ca8683dad in QSGRenderer::preprocess() () at /usr/lib/libQt5Quick.so.5 #24 0x7f5ca86835c9 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #25 0x7f5ca8683af4 in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #26 0x7f5ca86e9dd3 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5 #27 0x7f5ca8759d81 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () at /usr/lib/libQt5Quick.so.5 #28 0x7f5ca86f8a67 in () at /usr/lib/libQt5Quick.so.5 #29 0x7f5ca86f9447 in () at /usr/lib/libQt5Quick.so.5 #30 0x7f5ca66a3f7f in () at /usr/lib/libQt5Core.so.5 #31 0x7f5ca59c6259 in start_thread () at /usr/lib/libpthread.so.0 #32 0x7f5ca61ac5e3 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f5c6dbe9640 (LWP 933034) "QSGRenderThread"): #1 0x7f5ca59cc270 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #2 0x7f5ca66aa00c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #3 0x7f5ca86f6f37 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f5ca86f948b in () at /usr/lib/libQt5Quick.so.5 #5 0x7f5ca66a3f7f in () at /usr/lib/libQt5Core.so.5 #6 0x7f5ca59c6259 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f5ca61ac5e3 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f5c6f1fe640 (LWP 933033) "CPMMListener"): #1 0x7f5c9ac502d1 in () at /usr/lib/libnvidia-glcore.so.465.31 #2 0x7f5c9ac4ddba in () at /usr/lib/libnvidia-glcore.so.465.31 #3 0x7f5ca59c6259 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f5ca61ac5e3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f5c6fbff640 (LWP 933032) "QSGRenderThread"): #1 0x7f5ca59cc270 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #2 0x7f5ca66aa00c in QWaitCondition::wait(QMutex*, QDeadlineTimer)
[kwin] [Bug 424311] Severe Rendering Issues on Latest Nvidia Driver (450.57) (Arch)
https://bugs.kde.org/show_bug.cgi?id=424311 Matt McDonald changed: What|Removed |Added CC||gardotd...@gmail.com --- Comment #70 from Matt McDonald --- I think I'm experiencing something similar. With compositing enabled, either I get horrible artifacting/blurring, or it'll just crash and disable the compositor. I'm running an RTX 3090, and I thought it was my motherboard because the RGB lighting on the motherboard stopped working the other day. So my brand new replacement (as in brand-new, not an RMA) motherboard came in today, I rebuilt, and I'm experiencing the same issues in both Arch and Manjaro. The only difference is that I can actually run some games so far, before with the other motherboard games wouldn't even launch anymore. I have an RMA approved with EVGA to get a replacement card, but after seeing this I'm not sure if there's anything even wrong with the card. -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 417495] Application launcher shortcuts well recorded but launch nothing
https://bugs.kde.org/show_bug.cgi?id=417495 Matt McDonald changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #29 from Matt McDonald --- How is this not confirmed yet? -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 417495] Application launcher shortcuts well recorded but launch nothing
https://bugs.kde.org/show_bug.cgi?id=417495 --- Comment #28 from Matt McDonald --- Actually I've now discovered that this bug is even present on window actions. For example, the default KDE shortcut for "Close" is CTRL+W, which I kept, and added Meta+Shift+Q as an alternate. Neither work (and I tested the CTRL+W before I touched anything, and it doesn't work either). It seems that the majority of all of KDE's global shortcuts are broken. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 425930] "Edit Dock" menu crashes when trying to toggle on "Advanced Options" on second monitor dock
https://bugs.kde.org/show_bug.cgi?id=425930 --- Comment #6 from Matt McDonald --- (In reply to Michail Vourlakos from comment #4) > This is not reproducable in my multi-screen system. Please try again with > latest commits. Sorry I've had some hardware issues that necessitated both a reinstall and temporary use of a single monitor, I should hopefully have my second monitor setup back up and running today. Will report back. -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 417495] Application launcher shortcuts well recorded but launch nothing
https://bugs.kde.org/show_bug.cgi?id=417495 Matt McDonald changed: What|Removed |Added CC||gardotd...@gmail.com --- Comment #26 from Matt McDonald --- I also have this bug on Manjaro Linux 20.0.3 (Plasma 5.19.4). Weirdly my old install that I just wiped the other day, that had been around for months, had working shortcuts (they must have been grandfathered, as others have said). But now all new shortcuts fail unless I use the "Custom Shortcuts" menu instead of the "Global Shortcuts" as intended. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 425930] "Edit Dock" menu crashes when trying to toggle on "Advanced Options" on second monitor dock
https://bugs.kde.org/show_bug.cgi?id=425930 --- Comment #3 from Matt McDonald --- (In reply to Michail Vourlakos from comment #2) > 1. How did you install Latte git version? > 2. What is your last commit in your git version? 1.mkdir build && cd build cmake -DCMAKE_INSTALL_PREFIX=/usr \ -DCMAKE_BUILD_TYPE=Release .. Followed by the usual make install 2. fe34392e -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 425930] "Edit Dock" menu crashes when trying to toggle on "Advanced Options" on second monitor dock
https://bugs.kde.org/show_bug.cgi?id=425930 --- Comment #1 from Matt McDonald --- Created attachment 131256 --> https://bugs.kde.org/attachment.cgi?id=131256=edit Video showing crash. MP4 clip showing crash -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 425930] New: "Edit Dock" menu crashes when trying to toggle on "Advanced Options" on second monitor dock
https://bugs.kde.org/show_bug.cgi?id=425930 Bug ID: 425930 Summary: "Edit Dock" menu crashes when trying to toggle on "Advanced Options" on second monitor dock Product: lattedock Version: git (master) Platform: Compiled Sources OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: gardotd...@gmail.com Target Milestone: --- SUMMARY When using two monitors, after creating a second dock, and moving it to the second monitor, it's impossible to toggle on "Advanced Settings." Every attempt results in a crash of Plasma. DrKonqi doesn't trigger, no error messages, nothing, Plasma just exits. STEPS TO REPRODUCE 1. Create a Latte Dock on Primary monitor. 2. Right-click dock, select "Edit Dock." 3. At the bottom, select "+ New Dock" 4. Move new dock to second monitor 5. Right-click on second dock, select "Edit Dock." 6. Toggle on "Advanced Settings." OBSERVED RESULT You will see the settings window pop up as if it's going to expand into advanced settings, only the bottom half is a transparent window (you can still see the edges if you have shadows or any desktop effects), followed by a full crash of latte (all docks will close and latte has to be launched again manually)> I've tried rebooting, I tried moving the dock BACK to the first monitor, and trying to toggle advanced settings on from there, nothing works. I've attached a video. I have indeed found a workaround, which is to toggle Advanced Settings on BEFORE moving it to the second monitor. That's the only way to get it to work, as once you move it, you can't even move it back without it crashing. It's also hard to even get to this point, because Latte constantly crashes when more than one dock is running, it's pretty unstable at least on the master branch. Tested on both Arch Linux and Manjaro, kwin vanilla and kwin-lowlatency. Numerous kernels. Video attached. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415914] New: Plasma System Settings Crashes When Selecting "Configure Icon Sizes"
https://bugs.kde.org/show_bug.cgi?id=415914 Bug ID: 415914 Summary: Plasma System Settings Crashes When Selecting "Configure Icon Sizes" Product: systemsettings Version: 5.17.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: gardotd...@gmail.com Target Milestone: --- Application: systemsettings5 (5.17.4) Qt Version: 5.14.0 Frameworks Version: 5.65.0 Operating System: Linux 5.5.0-rc4-3-tkg-pds x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I was in System Settings, under the "Icons" section. There's a button to configure system icon sizes. Clicking on it crashes the application. I tried it 5 times after the first crash, so 6 total. 6 attempts, 6 crashes. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f135d27c840 (LWP 2975))] Thread 29 (Thread 0x7f12dae93700 (LWP 3017)): #0 0x7f1360579c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f13531a9edc in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f13531a9ad8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f13605734cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f13619922d3 in clone () at /usr/lib/libc.so.6 Thread 28 (Thread 0x7f12dbfff700 (LWP 3015)): #0 0x7f13619879ef in poll () at /usr/lib/libc.so.6 #1 0x7f135f963120 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f135f9631f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f1361f40cdc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1361ee739c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f1361d0ce62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f1360fd2249 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f1361d0dfd6 in () at /usr/lib/libQt5Core.so.5 #8 0x7f13605734cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f13619922d3 in clone () at /usr/lib/libc.so.6 Thread 27 (Thread 0x7f12edc35700 (LWP 3005)): #0 0x7f1360579c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f13531a9edc in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f13531a9ad8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f13605734cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f13619922d3 in clone () at /usr/lib/libc.so.6 Thread 26 (Thread 0x7f12ee636700 (LWP 3004)): #0 0x7f1360579c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f13531a9edc in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f13531a9ad8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f13605734cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f13619922d3 in clone () at /usr/lib/libc.so.6 Thread 25 (Thread 0x7f12ef537700 (LWP 3003)): #0 0x7f1360579c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f13531a9edc in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f13531a9ad8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f13605734cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f13619922d3 in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7f12efd38700 (LWP 3002)): #0 0x7f1360579c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f13531a9edc in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f13531a9ad8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f13605734cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f13619922d3 in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7f12f9fd1700 (LWP 3000)): #0 0x7f13619879ef in poll () at /usr/lib/libc.so.6 #1 0x7f135f963120 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f135f9631f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f1361f40cdc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1361ee739c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f1361d0ce62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f1360fd2249 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f1361d0dfd6 in () at /usr/lib/libQt5Core.so.5 #8 0x7f13605734cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f13619922d3 in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7f12fb641700 (LWP 2998)): #0 0x7f13619879ef in poll () at /usr/lib/libc.so.6 #1 0x7f135f963120 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f135f9631f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f1361f40cdc in QEventDispatcherGlib::processEvents(QFlags) ()
[filelight] [Bug 415732] Filelight 19.12.0-1 in Arch Linux Fails to Launch
https://bugs.kde.org/show_bug.cgi?id=415732 --- Comment #1 from Matt McDonald --- UPDATE: This seems to be some sort of bug related to qt5ct and gtk2. When qt5ct is uninstalled, the program launches. When qt5ct, if in the "style" section you set it to "gtk2," the program fails to launch. This may actually be a qt5ct bug, or a bug in the interaction between qt5ct and filelight, because I have a couple other qt5 programs installed, such as radeon-profile, that work regardless of whether style is set to gtk2 in qt5ct or not. Filelight seems to be the only program affected. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 415732] Filelight 19.12.0-1 in Arch Linux Fails to Launch
https://bugs.kde.org/show_bug.cgi?id=415732 Matt McDonald changed: What|Removed |Added CC||gardotd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 415732] New: Filelight 19.12.0-1 in Arch Linux Fails to Launch
https://bugs.kde.org/show_bug.cgi?id=415732 Bug ID: 415732 Summary: Filelight 19.12.0-1 in Arch Linux Fails to Launch Product: filelight Version: 19.12 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: martin.sandsm...@kde.org Reporter: gardotd...@gmail.com Target Milestone: --- Created attachment 124800 --> https://bugs.kde.org/attachment.cgi?id=124800=edit kcrash.txt backtrace log SUMMARY Filelight has randomly stopped working, nothing has changed in any configuration options on my system, it worked one day, then all of the sudden it won't launch at all, fails immediately on launch. Uninstalled the package, then rebuilt it with debug symbols to get a backtrace. Backtrace shows segmentation fault, but whatever else it says is far beyond me. STEPS TO REPRODUCE 1. On Arch Linux or Manjaro (problem persists on both my Arch and Manjaro installs), attempt to launch filelight. OBSERVED RESULT Filelight immediately crashes without even opening EXPECTED RESULT Filelight opens SOFTWARE/OS VERSIONS Arch Linux/Manjaro Linux 18.1.4 KDE Plasma Version: N/A KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION Backtrace file attached -- You are receiving this mail because: You are watching all bug changes.
