[kwin] [Bug 441980] [kdesrc-build] master build failure: "error: invalid conversion from ‘xcb_window_t’ {aka ‘unsigned int’} to ‘EGLNativeWindowType’ {aka ‘void*’} [-fpermissive]"

2021-09-04 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=441980 Kyle Devir changed: What|Removed |Added Summary|[kdesrc-build] build|[kdesrc-build] master build

[kwin] [Bug 441980] [kdesrc-build] master build failure: "error: invalid conversion from ‘xcb_window_t’ {aka ‘unsigned int’} to ‘EGLNativeWindowType’ {aka ‘void*’} [-fpermissive]"

2021-09-04 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=441980 Kyle Devir changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[kwin] [Bug 440372] kwin fails to compile with >=libglvnd-1.3.4 on Linux: "invalid conversion from ‘xcb_window_t’"

2021-09-04 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=440372 Kyle Devir changed: What|Removed |Added CC||kyle.de...@mykolab.com --- Comment #8 from Kyle

[dolphin] [Bug 442010] New: In a new instance, Dolphin freezes for a long period the first time trying to open a file, with no freezes on any subsequent files

2021-09-04 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=442010 Bug ID: 442010 Summary: In a new instance, Dolphin freezes for a long period the first time trying to open a file, with no freezes on any subsequent files Product: dolphin

[dolphin] [Bug 442010] In a new instance, Dolphin freezes for a long period the first time trying to open a file, with no freezes on any subsequent files

2021-09-04 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=442010 Kyle Devir changed: What|Removed |Added CC||kyle.de...@mykolab.com -- You are receiving this

[dolphin] [Bug 442010] In a new instance, Dolphin freezes for a long period the first time trying to open a file, with no freezes on any subsequent files

2021-09-04 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=442010 --- Comment #1 from Kyle Devir --- I've noticed that the exact same issue pops up when attempting to open Dolphin from Konsole via "Open File Manager" Wayland backend freezes and the connection dies. Using the XCB backend, initial

[dolphin] [Bug 442010] In a new instance, Dolphin freezes for a long period the first time trying to open a file, with no freezes on any subsequent files

2021-09-04 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=442010 --- Comment #2 from Kyle Devir --- Right-clicking in Dolphin also creates the freezing issue -- You are receiving this mail because: You are watching all bug changes.

[dolphin] [Bug 442010] In a new instance, Dolphin freezes for a long period the first time trying to open a file, with no freezes on any subsequent files

2021-09-04 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=442010 --- Comment #3 from Kyle Devir --- The right-clicking freeze never unfreezes... -- You are receiving this mail because: You are watching all bug changes.

[krunner] [Bug 436435] New: KRunner silently crashes when search results should be displayed

2021-04-30 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436435 Bug ID: 436435 Summary: KRunner silently crashes when search results should be displayed Product: krunner Version: unspecified Platform: Compiled Sources OS: Linux

[krunner] [Bug 436435] KRunner silently crashes when search results should be displayed

2021-04-30 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436435 --- Comment #2 from Kyle Devir --- Actually, it seems KRunner works just fine via `gdb /run/media/valmar/DataSSD/kde/usr-2021-04-30-17-35/bin/krunner`... -- You are receiving this mail because: You are watching all bug changes.

[krunner] [Bug 436435] KRunner silently crashes when search results should be displayed

2021-04-30 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436435 Kyle Devir changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[krunner] [Bug 436435] KRunner silently crashes when search results should be displayed

2021-04-30 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436435 Kyle Devir changed: What|Removed |Added Resolution|FIXED |NOT A BUG --- Comment #5 from Kyle Devir --- I

[krunner] [Bug 436435] KRunner silently crashes when search results should be displayed

2021-04-30 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436435 --- Comment #6 from Kyle Devir --- Now, this scripted setup hasn't changed since my prior build, which was from a week or two ago. So something has broken since. I even tried `kdesrc-build --refresh-build krunner`, to no avail. -- You are rece

[krunner] [Bug 436435] KRunner silently crashes when search results should be displayed

2021-04-30 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436435 --- Comment #8 from Kyle Devir --- Wouldn't that come as part of a `kdesrc-build baloo` build? Because I'm pretty certain it has been. -- You are receiving this mail because: You are watching all bug changes.

[krunner] [Bug 436435] KRunner silently crashes when search results should be displayed

2021-04-30 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436435 --- Comment #9 from Kyle Devir --- Starting KRunner via `/run/media/valmar/DataSSD/kde/usr-2021-04-30-17-35/bin/krunner` in Konsole makes it work perfectly. (usr is a symlink to usr-2021-04-30-17-35) -- You are receiving this mail because: You are

[krunner] [Bug 436435] KRunner silently crashes when search results should be displayed

2021-04-30 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436435 --- Comment #10 from Kyle Devir --- So, this isn't KRunner's fault, so much as whatever KDE component isn't honouring the exported paths, and is just somehow blindly running `/usr/bin/krunner`... Sorry for the confusion. :) Now to g

[krunner] [Bug 436435] KRunner silently crashes when search results should be displayed

2021-04-30 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436435 Kyle Devir changed: What|Removed |Added Assignee|alexander.loh...@gmx.de |kyle.de...@mykolab.com CC

[krunner] [Bug 436435] KRunner silently crashes when search results should be displayed

2021-04-30 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436435 --- Comment #12 from Kyle Devir --- Actually, that doesn't seem to be true... a few other KDE processes don't seem to honour the exported paths either... :| -- You are receiving this mail because: You are watching all bug changes.

[krunner] [Bug 436435] KRunner silently crashes when search results should be displayed

2021-04-30 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436435 --- Comment #14 from Kyle Devir --- Yeah, I use the systemd startup ~ that's the default now, I think? Yeah, upon checking, it has to be the systemd startup method, going by journalctl collecting krunner's output. So, somehow, the CMake

[krunner] [Bug 436435] KRunner silently crashes when search results should be displayed

2021-04-30 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436435 --- Comment #15 from Kyle Devir --- Should I start another bug related to that? -- You are receiving this mail because: You are watching all bug changes.

[krunner] [Bug 436435] KRunner silently crashes when search results should be displayed

2021-05-01 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436435 --- Comment #16 from Kyle Devir --- H... From `/run/media/valmar/DataSSD/kde/usr-2021-04-30-17-35/lib/systemd/user/plasma-plasmashell.service`: ``` [Unit] Description=KRunner PartOf=graphical-session.target [Service] ExecStart=/run/media/valmar

[krunner] [Bug 436435] KRunner silently crashes when search results should be displayed

2021-05-01 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436435 --- Comment #17 from Kyle Devir --- Whoops, from `/run/media/valmar/DataSSD/kde/usr-2021-04-30-17-35/lib/systemd/user/plasma-krunner.service`, I mean. -- You are receiving this mail because: You are watching all bug changes.

[krunner] [Bug 436435] KRunner silently crashes when search results should be displayed

2021-05-01 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436435 --- Comment #18 from Kyle Devir --- Hm. Is KRunner integrated into the Application Launcher widget's searching capabilities? If so, that seems to find kdesrc-build KRunner just fine. -- You are receiving this mail because: You are watchin

[krunner] [Bug 436450] New: [kdesrc-build] startplasma startup uses "/usr" for pathing when looking for "plasma-krunner.service", instead of honoring exported paths

2021-05-01 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436450 Bug ID: 436450 Summary: [kdesrc-build] startplasma startup uses "/usr" for pathing when looking for "plasma-krunner.service", instead of honoring exported paths Product: krunner

[krunner] [Bug 436450] [kdesrc-build] startplasma startup uses "/usr" for pathing when looking for "plasma-krunner.service", instead of honoring exported paths

2021-05-01 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436450 Kyle Devir changed: What|Removed |Added CC||kyle.de...@mykolab.com -- You are receiving this

[krunner] [Bug 436435] KRunner silently crashes when search results should be displayed

2021-05-01 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436435 --- Comment #20 from Kyle Devir --- ``` [D-BUS Service] Name=org.kde.krunner Exec=/run/media/valmar/DataSSD/kde/usr-2021-04-30-17-35/bin/krunner SystemdService=plasma-krunner.service ``` -- You are receiving this mail because: You are watching all

[plasmashell] [Bug 436450] [kdesrc-build] startplasma startup uses "/usr" for pathing when looking for "plasma-krunner.service", instead of honoring exported paths

2021-05-03 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436450 --- Comment #2 from Kyle Devir --- Yes, I am. -- You are receiving this mail because: You are watching all bug changes.

[frameworks-kded] [Bug 436776] New: [kdesrc-build] KDE applications always call kded5 from "/usr/bin", rather than kdesrc-build install prefix

2021-05-08 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436776 Bug ID: 436776 Summary: [kdesrc-build] KDE applications always call kded5 from "/usr/bin", rather than kdesrc-build install prefix Product: frameworks-kded Version: unspecified Pl

[frameworks-kded] [Bug 436776] [kdesrc-build] KDE applications always call kded5 from "/usr/bin", rather than kdesrc-build install prefix

2021-05-08 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436776 --- Comment #1 from Kyle Devir --- Whoops ~ forgot to mention that right-clicking folders also triggers it. -- You are receiving this mail because: You are watching all bug changes.

[frameworks-kded] [Bug 436776] [kdesrc-build] KDE applications always call kded5 from "/usr/bin", rather than kdesrc-build install prefix

2021-05-09 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436776 --- Comment #3 from Kyle Devir --- (In reply to Nicolas Fella from comment #2) > In order for kded and other DBus-activated things to work correctly you need > to configure DBus to take the custom location into account. > &g

[frameworks-kded] [Bug 436776] [kdesrc-build] KDE applications always call kded5 from "/usr/bin", rather than kdesrc-build install prefix

2021-05-09 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436776 Kyle Devir changed: What|Removed |Added Ever confirmed|0 |1 Resolution|NOT A BUG

[frameworks-kded] [Bug 436776] [kdesrc-build] KDE applications always call kded5 from "/usr/bin", rather than kdesrc-build install prefix

2021-05-09 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436776 --- Comment #5 from Kyle Devir --- Created attachment 138269 --> https://bugs.kde.org/attachment.cgi?id=138269&action=edit kdesrc-build prefix build kded5 dying with correct paths -- You are receiving this mail because: You are watching

[frameworks-kded] [Bug 436776] [kdesrc-build] KDE applications always call kded5 from "/usr/bin", rather than kdesrc-build install prefix

2021-05-09 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436776 --- Comment #6 from Kyle Devir --- Created attachment 138270 --> https://bugs.kde.org/attachment.cgi?id=138270&action=edit /usr/bin/kded5 and friends started with Dolphin file / folder right-click -- You are receiving this mail because:

[frameworks-kded] [Bug 436776] [kdesrc-build] KDE applications always call kded5 from "/usr/bin", rather than kdesrc-build install prefix

2021-05-09 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436776 Kyle Devir changed: What|Removed |Added CC||kyle.de...@mykolab.com -- You are receiving this

[frameworks-kded] [Bug 436776] [kdesrc-build] KDE applications always call kded5 from "/usr/bin", rather than kdesrc-build install prefix

2021-05-10 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436776 --- Comment #8 from Kyle Devir --- Created attachment 138309 --> https://bugs.kde.org/attachment.cgi?id=138309&action=edit kded5 after copying files kded5 is now called from the kdesrc-build prefix after coping said files. Still crashes tho

[frameworks-kded] [Bug 436776] [kdesrc-build] KDE applications always call kded5 from "/usr/bin", rather than kdesrc-build install prefix

2021-05-10 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436776 --- Comment #9 from Kyle Devir --- > sudo cp -r ~/kde/usr/share/dbus-1/ /usr/share/ > sudo cp -r ~/kde/usr/share/polkit-1/actions/* /usr/share/polkit-1/actions/ Would be nice to have this documented for future, or at least, made clearer, if it a

[frameworks-kded] [Bug 436776] [kdesrc-build] KDE applications always call kded5 from "/usr/bin", rather than kdesrc-build install prefix

2021-05-11 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=436776 --- Comment #11 from Kyle Devir --- (In reply to Nate Graham from comment #10) > That's what I personally do, but I've resisted adding it to the wiki since > it overwrites system files. This is fine... until it isn't. :) On Arch

[kio-extras] [Bug 435451] New: Open file dialog involving thumbnails crashes kdeinit in ThumbnailProtocol::get

2021-04-07 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=435451 Bug ID: 435451 Summary: Open file dialog involving thumbnails crashes kdeinit in ThumbnailProtocol::get Product: kio-extras Version: unspecified Platform: Compiled Sources

[ktorrent] [Bug 473361] New: [kdesrc-build] [kf6] libtorrent build failure

2023-08-14 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=473361 Bug ID: 473361 Summary: [kdesrc-build] [kf6] libtorrent build failure Classification: Applications Product: ktorrent Version: unspecified Platform: Compiled Sources OS: Linux

[kwin] [Bug 475648] New: kwin_wayland crashing when starting Firefox Nightly with Wayland backend

2023-10-15 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=475648 Bug ID: 475648 Summary: kwin_wayland crashing when starting Firefox Nightly with Wayland backend Classification: Plasma Product: kwin Version: git master Platform: Compiled So

[kwin] [Bug 475648] kwin_wayland crashing when starting Firefox Nightly with Wayland backend

2023-10-15 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=475648 --- Comment #1 from Kyle Devir --- Generating the GDB backtrace was consuming all of my RAM, so I had to kill it, but got this info: #0 0x7f3e11f91324 in std::__uniq_ptr_impl >::_M_ptr (this=0x10) at /usr/include/c++/13.2.1/bits/unique_ptr.h:

[kwin] [Bug 475648] kwin_wayland crashing when starting Firefox Nightly with Wayland backend

2023-10-15 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=475648 Kyle Devir changed: What|Removed |Added CC||kyle.de...@mykolab.com -- You are receiving this

[kwin] [Bug 475648] kwin_wayland crashing when starting Firefox Nightly with Wayland backend

2023-10-23 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=475648 --- Comment #3 from Kyle Devir --- (In reply to Vlad Zahorodnii from comment #2) > Do you know if you ran kwin with > https://invent.kde.org/plasma/kwin/-/commit/ > 8d3b4a21c8ec67d62b683d02512fa790a82e6ea3 ? Yes. Still crashes for me. (I re

[kwin] [Bug 475648] kwin_wayland crashing when starting Firefox Nightly with Wayland backend

2023-10-24 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=475648 --- Comment #5 from Kyle Devir --- (In reply to fanzhuyifan from comment #4) > Are you using a nvidia gpu? Many people (with nvidia) reported problems > running firefox on wayland with `egl-wayland` version 1.1.12. Either > downgrading to

[kwin] [Bug 475648] kwin_wayland ~ Firefox Nightly crashing with Wayland backend when gfx.webrender.compositor.force-enabled set to true

2023-10-24 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=475648 Kyle Devir changed: What|Removed |Added Summary|kwin_wayland crashing when |kwin_wayland ~ Firefox

[kwin] [Bug 475648] kwin_wayland ~ Firefox Nightly crashing with Wayland backend when gfx.webrender.compositor.force-enabled set to true

2023-10-24 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=475648 --- Comment #6 from Kyle Devir --- So, through testing a new Firefox profile, I discovered the culprit: Setting gfx.webrender.compositor.force-enabled to true results in a crash with the Wayland backend, but not the X11 backend. I hope this helps

[kwin] [Bug 475648] kwin_wayland ~ Firefox Nightly crashing with Wayland backend when gfx.webrender.compositor.force-enabled set to true

2023-10-24 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=475648 --- Comment #7 from Kyle Devir --- >From Firefox troubleshooting info: WEBRENDER_COMPOSITOR: default: disabled, Disabled by default, Blocklisted; failure code FEATURE_FAILURE_DISABLED env: blocklisted, Blocklisted by gfxInfo, Blocklisted; failure c

[kwin] [Bug 475648] kwin_wayland ~ Firefox Nightly crashing with Wayland backend when gfx.webrender.compositor.force-enabled set to true

2023-10-26 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=475648 --- Comment #10 from Kyle Devir --- (In reply to Vlad Zahorodnii from comment #8) > I also run firefox with gfx.webrender.compositor.force-enabled=true. Maybe > you've changed something else too? Can you start with a fresh profile please? (

[kwin] [Bug 448284] New: Mesa commit 83916ae0, "egl/wayland: add initial dma-buf feedback support" interacts badly with kwin_wayland's dma-buf feedback code, causing Mesa to fallback to llvmpipe

2022-01-11 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=448284 Bug ID: 448284 Summary: Mesa commit 83916ae0, "egl/wayland: add initial dma-buf feedback support" interacts badly with kwin_wayland's dma-buf feedback code, causing Mesa to

[kwin] [Bug 448284] Mesa commit 83916ae0, "egl/wayland: add initial dma-buf feedback support" interacts badly with kwin_wayland's dma-buf feedback code, causing Mesa to fallback to llvmpipe

2022-01-11 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=448284 Kyle Devir changed: What|Removed |Added CC||kyle.de...@mykolab.com -- You are receiving this

[kwin] [Bug 448284] Mesa commit 83916ae0, "egl/wayland: add initial dma-buf feedback support" interacts badly with kwin_wayland's dma-buf feedback code, causing Mesa to fallback to llvmpipe

2022-01-13 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=448284 --- Comment #8 from Kyle Devir --- @jason > Since I'm affected by this issue as well, I've added debug prints to > default_dmabuf_feedback_format_table for fd and errno after mmap. Thanks for the testing, as I don't know how to

[kwin] [Bug 448284] Mesa commit 83916ae0, "egl/wayland: add initial dma-buf feedback support" interacts badly with kwin_wayland's dma-buf feedback code, causing Mesa to fallback to llvmpipe

2022-01-14 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=448284 --- Comment #14 from Kyle Devir --- Can confirm there is no fallback to llvmpipe now. Thanks for the hard work, as usual. :) -- You are receiving this mail because: You are watching all bug changes.

[frameworks-kio] [Bug 447719] New: In Dolphin, trying to create, move or copy files and folders in/to a root-owned folder fails

2021-12-30 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=447719 Bug ID: 447719 Summary: In Dolphin, trying to create, move or copy files and folders in/to a root-owned folder fails Product: frameworks-kio Version: git master Platform: Compiled

[frameworks-kio] [Bug 447719] In Dolphin, trying to create, move or copy files and folders in/to a root-owned folder fails

2021-12-30 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=447719 Kyle Devir changed: What|Removed |Added CC||kyle.de...@mykolab.com --- Comment #1 from Kyle

[frameworks-kio] [Bug 447719] In Dolphin, trying to create, move or copy files and folders in/to a root-owned folder fails

2021-12-30 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=447719 --- Comment #3 from Kyle Devir --- This is what I use to run my KDE build: https://invent.kde.org/-/snippets/2026 I don't think I'm missing anything... -- You are receiving this mail because: You are watching all bug changes.

[frameworks-kio] [Bug 447719] In Dolphin, trying to create, move or copy files and folders in/to a root-owned folder fails

2021-12-31 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=447719 --- Comment #4 from Kyle Devir --- Running "source ./prefix.sh" and then "bin/kauth_tester" in the kio kdesrc-build build directory yields this output: https://invent.kde.org/-/snippets/2027 And this backtrace: https://invent.kde

[frameworks-kio] [Bug 447719] In Dolphin, trying to create, move or copy files and folders in/to a root-owned folder fails

2022-01-01 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=447719 Kyle Devir changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[drkonqi] [Bug 437376] New: Build failures with GCC 11.1.0 caused by 40b95326e2d1a3ac216b6e957430165e4fbc8417

2021-05-19 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=437376 Bug ID: 437376 Summary: Build failures with GCC 11.1.0 caused by 40b95326e2d1a3ac216b6e957430165e4fbc8417 Product: drkonqi Version: unspecified Platform: Compiled Sources

[drkonqi] [Bug 437376] Build failures with GCC 11.1.0 caused by 40b95326e2d1a3ac216b6e957430165e4fbc8417

2021-05-19 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=437376 Kyle Devir changed: What|Removed |Added CC||kyle.de...@mykolab.com -- You are receiving this

[kwin] [Bug 434624] New: Fullscreen direct scanout-happy applications cause "importing the dmabuf for direct scanout failed: Invalid argument" spam in session logs

2021-03-19 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=434624 Bug ID: 434624 Summary: Fullscreen direct scanout-happy applications cause "importing the dmabuf for direct scanout failed: Invalid argument" spam in session logs Product: kwin

[kwin] [Bug 434624] Fullscreen direct scanout-happy applications cause "importing the dmabuf for direct scanout failed: Invalid argument" spam in session logs

2021-03-19 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=434624 Kyle Devir changed: What|Removed |Added CC||kyle.de...@mykolab.com -- You are receiving this

[kwin] [Bug 434624] Fullscreen direct scanout-happy applications cause "importing the dmabuf for direct scanout failed: Invalid argument" spam in session logs

2021-03-19 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=434624 Kyle Devir changed: What|Removed |Added CC||xaver.h...@gmail.com -- You are receiving this

[kwin] [Bug 434624] Fullscreen direct scanout-happy applications cause "importing the dmabuf for direct scanout failed: Invalid argument" spam in session logs

2021-03-20 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=434624 --- Comment #2 from Kyle Devir --- > The logging only happens if you have debug logging active. Right... I should have mentioned that in the steps to reproduce part, but I forgot about it. > After some more investigation (hit the problem right

[dolphin] [Bug 492537] New: Dolphin crashing

2024-09-02 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=492537 Bug ID: 492537 Summary: Dolphin crashing Classification: Applications Product: dolphin Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED

[dolphin] [Bug 492537] Dolphin crashing

2024-09-02 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=492537 --- Comment #2 from Kyle Devir --- #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7312d36a5463 in __pthread_kill_internal (threadid=, signo=6) at pthread_kill.c:78 #2

[dolphin] [Bug 492537] Dolphin crashing

2024-09-02 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=492537 --- Comment #3 from Kyle Devir --- (gdb) bt full #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 tid = ret = 0 pd = old_mask = {__val = {0}} ret

[plasmashell] [Bug 412108] New: [5.17 Beta] plasmashell crashes after trying to start

2019-09-20 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=412108 Bug ID: 412108 Summary: [5.17 Beta] plasmashell crashes after trying to start Product: plasmashell Version: 5.16.90 Platform: Archlinux Packages OS: Linux Status: REPORTED

[plasmashell] [Bug 412108] [5.17 Beta] plasmashell crashes on start

2019-09-20 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=412108 Kyle Devir changed: What|Removed |Added Summary|[5.17 Beta] plasmashell |[5.17 Beta] plasmashell

[plasmashell] [Bug 412108] [5.17 Beta] plasmashell crashes on start

2019-09-20 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=412108 Kyle Devir changed: What|Removed |Added CC||kyle.de...@mykolab.com -- You are receiving this

[plasmashell] [Bug 412108] [5.17 Beta] plasmashell crashes on start

2019-09-21 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=412108 --- Comment #1 from Kyle Devir --- Okay, weirdly, starting a KWin Wayland session seems to have resolved it. I was getting the crashes on the X11 KWin session, but after it starting working on Wayland, the X11 crashes were also resolved. I have no

[frameworks-kio] [Bug 416973] New: Dolphin won't run binaries or scripts, even when set to always ask on opening, and the binary or script is executable

2020-01-30 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=416973 Bug ID: 416973 Summary: Dolphin won't run binaries or scripts, even when set to always ask on opening, and the binary or script is executable Product: frameworks-kio Ver

[frameworks-kio] [Bug 416973] Dolphin won't run binaries or scripts, even when set to always ask on opening, and the binary or script is executable

2020-01-30 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=416973 Kyle Devir changed: What|Removed |Added Platform|Other |Archlinux Packages CC

[frameworks-kio] [Bug 416973] Dolphin won't run binaries or scripts, even when set to always ask on opening, and the binary or script is executable

2020-01-30 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=416973 Kyle Devir changed: What|Removed |Added Version|unspecified |5.66.0 -- You are receiving this mail because

[frameworks-kio] [Bug 416973] Dolphin won't run binaries or scripts, even when set to always ask on opening, and the binary or script is executable

2020-01-30 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=416973 --- Comment #1 from Kyle Devir --- So... this issue was fixed by editing ~/.config/kiorc ... :/ -- You are receiving this mail because: You are watching all bug changes.

[frameworks-kio] [Bug 416973] Dolphin won't run binaries or scripts, even when set to always ask on opening, and the binary or script is executable

2020-01-30 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=416973 Kyle Devir changed: What|Removed |Added CC|m.dlubakow...@gmail.com | -- You are receiving this mail because: You are

[kwin] [Bug 389495] When GTK3 applications request SSD, decorations are not shown

2018-02-09 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389495 Kyle Devir changed: What|Removed |Added Summary|When GTK3 applications |When GTK3 applications |request

[kwin] [Bug 389495] When GTK3 applications request SSD, decorations are not shown

2018-02-20 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389495 --- Comment #32 from Kyle Devir --- >From GTK bugzilla: > This bug is obsolete anyway - we've proposed an updated protocol for > standardization. You can expect a patch for that fairly soon. Urgh... why not just fix the original bug a

[kwin] [Bug 389495] When GTK3 applications request SSD, decorations are not shown

2018-02-20 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389495 --- Comment #33 from Kyle Devir --- Thoughts, Martin? Apparently, David Edmundson has had some involvement, so that's nice. :) https://lists.freedesktop.org/archives/wayland-devel/2018-February/037119.html -- You are receiving this mail because

[kwin] [Bug 389495] When GTK3 applications request SSD, decorations are not shown

2018-02-23 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389495 Kyle Devir changed: What|Removed |Added Attachment #110142|0 |1 is obsolete

[kwin] [Bug 389495] When GTK3 applications request SSD, decorations are not shown

2018-02-23 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389495 Kyle Devir changed: What|Removed |Added Attachment #110146|0 |1 is obsolete

[kwin] [Bug 389495] When GTK3 applications request SSD, decorations are not shown

2018-02-23 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389495 Kyle Devir changed: What|Removed |Added Attachment #110929|0 |1 is obsolete

[plasmashell] [Bug 375539] [Qt 5.8] Plasmashell windows are not marked as Desktop

2017-01-30 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=375539 Kyle Devir changed: What|Removed |Added CC||kyle.de...@mykolab.com -- You are receiving this

[kwin] [Bug 389117] New: GTK3 apps started with GDK_BACKEND=wayland don't have correct or consistent decorations

2018-01-17 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389117 Bug ID: 389117 Summary: GTK3 apps started with GDK_BACKEND=wayland don't have correct or consistent decorations Product: kwin Version: 5.11.95 Platform: Archlinux Packages

[kwin] [Bug 389117] GTK3 apps started with GDK_BACKEND=wayland don't have correct or consistent decorations

2018-01-17 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389117 Kyle Devir changed: What|Removed |Added CC||kyle.de...@mykolab.com -- You are receiving this

[kwin] [Bug 389117] GTK3 apps started with GDK_BACKEND=wayland have incorrect or inconsistent decorations

2018-01-18 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389117 Kyle Devir changed: What|Removed |Added Summary|GTK3 apps started with |GTK3 apps started with

[kwin] [Bug 389117] GTK3 apps started with GDK_BACKEND=wayland have incorrect or inconsistent decorations

2018-01-18 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389117 --- Comment #6 from Kyle Devir --- Created attachment 109979 --> https://bugs.kde.org/attachment.cgi?id=109979&action=edit Official Gnome GTK3 application CSDs The official Gnome GTK3 application CSDs now work as expected, however... --

[kwin] [Bug 389117] GTK3 apps started with GDK_BACKEND=wayland have incorrect or inconsistent decorations

2018-01-18 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389117 Kyle Devir changed: What|Removed |Added Attachment #109979|Official Gnome GTK3 |Official Gnome GTK3 description

[kwin] [Bug 389117] GTK3 apps started with GDK_BACKEND=wayland have incorrect or inconsistent decorations

2018-01-18 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389117 --- Comment #7 from Kyle Devir --- Created attachment 109980 --> https://bugs.kde.org/attachment.cgi?id=109980&action=edit Other non-Gnome GTK3 applications with patch Unfortunately, non-Gnome GTK3 applications like Libreoffice and Darktabl

[kwin] [Bug 389298] New: Some SDL2 apps run with SDL_VIDEODRIVER=wayland under kwin_wayland experience alpha transparency bleeding weirdness

2018-01-21 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389298 Bug ID: 389298 Summary: Some SDL2 apps run with SDL_VIDEODRIVER=wayland under kwin_wayland experience alpha transparency bleeding weirdness Product: kwin Version: 5.11.9

[kwin] [Bug 389298] Some SDL2 apps run with SDL_VIDEODRIVER=wayland under kwin_wayland experience alpha transparency bleeding weirdness

2018-01-21 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389298 --- Comment #1 from Kyle Devir --- Created attachment 110035 --> https://bugs.kde.org/attachment.cgi?id=110035&action=edit GZDoom menu with more alpha bleeding -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 389298] Some SDL2 apps run with SDL_VIDEODRIVER=wayland under kwin_wayland experience alpha transparency bleeding weirdness

2018-01-21 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389298 Kyle Devir changed: What|Removed |Added CC||kyle.de...@mykolab.com -- You are receiving this

[kwin] [Bug 389298] Some SDL2 apps run with SDL_VIDEODRIVER=wayland under kwin_wayland experience alpha transparency bleeding weirdness

2018-01-21 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389298 --- Comment #2 from Kyle Devir --- Note that this doesn't occur when I run this on Weston. Alpha transparency works as expected. Running with SDL_VIDEODRIVER=x11 also avoids the problem. -- You are receiving this mail because: You are watchin

[kwin] [Bug 389298] GZDoom (SDL2), at least, run with SDL_VIDEODRIVER=wayland under kwin_wayland experience alpha transparency bleeding weirdness

2018-01-21 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389298 Kyle Devir changed: What|Removed |Added Summary|Some SDL2 apps run with |GZDoom (SDL2), at least

[kwin] [Bug 389298] GZDoom (SDL2), at least, run with SDL_VIDEODRIVER=wayland under kwin_wayland experience alpha transparency bleeding weirdness

2018-01-22 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389298 --- Comment #4 from Kyle Devir --- GZDoom is free, and should be in your distro's repositories. You can also download the game files for Doom for free from here: http://doomgod.com/wads/iwads/ -- You are receiving this mail because: Yo

[kwin] [Bug 389117] GTK3 apps started with GDK_BACKEND=wayland have incorrect or inconsistent decorations

2018-01-23 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389117 --- Comment #10 from Kyle Devir --- Martin, can this be reopened, as the submitted fix doesn't solve the sheer lack of decorations for applications like Libreoffice (using the GTK3 VCL backend), Darktable, RawTherapee, MyPaint, and the like. They

[kwin] [Bug 389117] GTK3 apps started with GDK_BACKEND=wayland have incorrect or inconsistent decorations

2018-01-23 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389117 --- Comment #12 from Kyle Devir --- Ah, now I understand. Sorry for the confusion. New bug report time! :) -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 389361] New: Non-Gnome GTK3 apps started with GDK_BACKEND=wayland have no decorations

2018-01-23 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389361 Bug ID: 389361 Summary: Non-Gnome GTK3 apps started with GDK_BACKEND=wayland have no decorations Product: kwin Version: 5.11.95 Platform: Archlinux Packages OS: Li

[kwin] [Bug 389361] Non-Gnome GTK3 apps started with GDK_BACKEND=wayland have no decorations

2018-01-23 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389361 Kyle Devir changed: What|Removed |Added CC||kyle.de...@mykolab.com -- You are receiving this

[kwin] [Bug 389361] Non-Gnome GTK3 apps started with GDK_BACKEND=wayland have no decorations

2018-01-24 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389361 --- Comment #1 from Kyle Devir --- Created attachment 110088 --> https://bugs.kde.org/attachment.cgi?id=110088&action=edit Mentioned GTK3 applications shown with decorations in Weston The applications have decorations in Weston. --

[kwin] [Bug 389361] Non-Gnome GTK3 apps started with GDK_BACKEND=wayland have no decorations

2018-01-24 Thread Kyle Devir
https://bugs.kde.org/show_bug.cgi?id=389361 --- Comment #3 from Kyle Devir --- So... where to now? Is there a way to force CSD borders somehow, because Weston provides them. Maybe I should open another bug, but worded differently, to reflect that they're specifically lacking KWin decora

<    1   2   3   >