[dolphin] [Bug 488154] Addition of a dedicated Tags Panel
https://bugs.kde.org/show_bug.cgi?id=488154 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 Jason Straight changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #22 from Jason Straight --- I see now. The original problem remains. For a while, there was an additional issue where it would hang and (possibly) unhang itself after a bit. The original problem where the desktop contents all freeze and it doesn't recover is still an issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #21 from Jason Straight --- I don't think this is the same as the bug it was marked as a duplicate of, which was marked as resolved in Feb. I'm still having the same freeze. In fact I just had it while I was writing this. Unless the changes still have not made it into release? I'm currently on: Operating System: openSUSE Tumbleweed 20240517 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-1-default (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i9-12900H Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Strix G733ZW_G733ZW System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[baloo-widgets] [Bug 432720] Tag management window needs a search/filter field
https://bugs.kde.org/show_bug.cgi?id=432720 --- Comment #5 from Jason Straight --- (In reply to tagwerk19 from comment #4) > You can have a look at the "Tags:" option in the information (F11) panel. > There are (unfortunately) several different dialogs in use for manipulating > tags Yeah. I can tag files from several different places, but they all lack the ability to set multiple tags at one time by typing them. I either have to scroll through the list of hundreds of tags to find what ones I want to apply, or I have to type one, save it, open the tag editor again, type another one, save it, etc. I would hope I would be able to just type something like "dog; picture; outside; home", and have it apply all 4 tags to it. -- You are receiving this mail because: You are watching all bug changes.
[baloo-widgets] [Bug 432720] Tag management window needs a search/filter field
https://bugs.kde.org/show_bug.cgi?id=432720 --- Comment #2 from Jason Straight --- Tagging is such a nuisance. Was just doing some and it would be really nice if it got some attention. Also, being able to tag with just typing. Like in the input field it could autocomplete tag names, and just enter several of them with commas. Any that don't exist would be created. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 401892] Have tab notification icons show up in kde tray
https://bugs.kde.org/show_bug.cgi?id=401892 --- Comment #2 from Jason Straight --- I've recently learned that the non-qt applications used libunity in the past to do notification badges, which is what I was thinking without knowing the correct terminology. Windows does it, and a lot of apps used to do it in the past if libunity was installed. I don't know how many still support that? That is, of course, on the task bar, and not in the tray, but the same outcome I'm looking for - a way for website notifications to be easily visible when there are unread messages. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 480817] When accessing smb:// locations, dolphin does not use kwallet saved passwords. Also, no option to save password/login when it's asked.
https://bugs.kde.org/show_bug.cgi?id=480817 Jason Straight changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Jason Straight --- Fixed for me with smb:// locations on 6.0. No longer presents for user/pass, and logs in with saved credentials. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481862] Minimizing of non-kde/qt windows doesn't give focus to last active window
https://bugs.kde.org/show_bug.cgi?id=481862 Jason Straight changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #6 from Jason Straight --- Working in 6.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481862] Minimizing of non-kde/qt windows doesn't give focus to last active window
https://bugs.kde.org/show_bug.cgi?id=481862 --- Comment #4 from Jason Straight --- (In reply to Vlad Zahorodnii from comment #3) > Cannot reproduce I reproduced with a fresh user. Are you on the same version (rc2/5.93) as me? Maybe it's already fixed? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481862] Minimizing of non-kde/qt windows doesn't give focus to last active window
https://bugs.kde.org/show_bug.cgi?id=481862 --- Comment #2 from Jason Straight --- (In reply to Nate Graham from comment #1) > Are all of the tested apps using XWayland? They are. What do you know - an actual use for xeyes. >Are you using the Slide Back effect? No. I am using squash, but I also tried without it. >Do you have any other non-default KWin effects active? No. Everything is Defaults under Desktop Effects. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481862] New: Minimizing of non-kde/qt windows doesn't give focus to last active window
https://bugs.kde.org/show_bug.cgi?id=481862 Bug ID: 481862 Summary: Minimizing of non-kde/qt windows doesn't give focus to last active window Classification: Plasma Product: kwin Version: 5.93.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: j.straight-...@straights.net Target Milestone: --- In wayland (not tested on xorg), when I minimize a non QT application, focus is not given to the last active window. I noticed this to be an issue while trying to get Keepass auto-type working on Wayland with the KPUinput plug-in. When Keepass minimizes itself to perform the auto-type, the last active window is not given focus, and the password is not properly sent to the intended window because of that. I experimented by minimizing and restoring some windows and realized this to be the case with every non QT application I tried. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #19 from Jason Straight --- I found a workaround for the momentary freezes of desktop contents. It's not ideal, but it's more ideal than disabling compositing on kwin_x11. I really wish I could use wayland, but I just can't not have working autotype in my password manager for the amount of remote work I do, where copy/paste isn't an option. The workaround I found was to disable glamor (acceleration) in the modesetting x11 driver with `Option "AccelMethod" "none"`. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 338999] [unspecific] Desktop freezes time to time on plasma 5 (collection of various unrelated problems, WONTFIX)
https://bugs.kde.org/show_bug.cgi?id=338999 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #18 from Jason Straight --- Created attachment 165767 --> https://bugs.kde.org/attachment.cgi?id=165767=edit kwin_x11 gdb.txt 5.93.0-1 I'm no dev, so I can't really say if it's the same issue from looking at the trace, but this is with X and on arch this time. The last trace on X was with opensuse TW. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #16 from Jason Straight --- Xorg still freezes, but at least I can say that wayland does not, including on RC2. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 480817] New: When accessing smb:// locations, dolphin does not use kwallet saved passwords. Also, no option to save password/login when it's asked.
https://bugs.kde.org/show_bug.cgi?id=480817 Bug ID: 480817 Summary: When accessing smb:// locations, dolphin does not use kwallet saved passwords. Also, no option to save password/login when it's asked. Classification: Applications Product: dolphin Version: 24.01.95 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: j.straight-...@straights.net CC: kfm-de...@kde.org Target Milestone: --- When connecting to a remote share, for which I previously had a password saved (on plasma/frameworks 5), I was asked for the authentication credentials for it, and not given an option to save them. Maybe this belongs in kio? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #14 from Jason Straight --- I can't say what changed from last night to today with certainty, but the wayland session is no longer having this issue. kernel, qt, libgl, or kde updates? But I'm happy about that. I guess I'll have to try an X session to see. Operating System: openSUSE Tumbleweed 20240130 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 Kernel Version: 6.7.2-1-default (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i9-12900H Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Strix G733ZW_G733ZW System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #12 from Jason Straight --- No problems on kwinft, compiz, Gnome. Definitely a kwin only issue. Compiled kwinft for dev branch last night and it's been going without a freeze, or at least for a lot longer than I could have gone on kwin without one. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #11 from Jason Straight --- With plasma6, this is now also present in Wayland, but the behavior changed a little, and my fix no longer works. Now, it'll freeze for several seconds and recover, every few minutes. It seems watching videos in the browser makes it happen more often. Most of the time, I'm lucky to get 5-10 minutes. On Xorg, It's still dependent on compositing being enabled. If disabled, it doesn't happen. I've tried turning off every effect, to no avail. I've tried every environment variable option for kwin. Still only happens with intel driver. Switching to nvidia driver doesn't have issue. Tried w/o a task bar, in case it was something to do with thumbnails. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480286] New: Mouse pointer only shows up on one screen on Wayland
https://bugs.kde.org/show_bug.cgi?id=480286 Bug ID: 480286 Summary: Mouse pointer only shows up on one screen on Wayland Classification: Plasma Product: kwin Version: 5.92.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: j.straight-...@straights.net Target Milestone: --- On my intel/nividia optimus laptop, using intel drivers, with external monitor connected, the mouse cursor only shows up on one of the external screens. It disappears moving to other screens. At work (including the built-in), I have 3 screens. At home I have 2. Both locations, only one screen has a visible mouse cursor. It disappears while moving. I can right click and get the desktop context menu pop-up. So, it's working. It's just not visible. I've tried with a new user / profile. Same outcome. Operating System: EndeavourOS KDE Plasma Version: 5.92.0 KDE Frameworks Version: 5.248.0 Qt Version: 6.7.0 Kernel Version: 6.7.1-arch1-1 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i9-12900H Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Strix G733ZW_G733ZW System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 478329] New: Would it be possible to have browser integration create a system tray icon for message notifications?
https://bugs.kde.org/show_bug.cgi?id=478329 Bug ID: 478329 Summary: Would it be possible to have browser integration create a system tray icon for message notifications? Classification: Plasma Product: plasma-browser-integration Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: j.straight-...@straights.net Target Milestone: --- I wonder if this would be the application to hand such a thing? When you have several browser windows and tabs open and some of them are messaging, calendar, e-mail, etc., unless you go checking them every few seconds, you have no good way to know if you have messages that require attention. Plasma's notifications are hard to filter through, and don't cut it. My thought is that if browser integration could create a system tray icon and show a message count there, or at least an unread indicator badge, since I know every site isn't exactly the same with its title updates, then I could use my browser for those types of pages much more efficiently. Maybe you could configure which domains, tabs, or only have pinned tabs monitored, etc. I know apps like Ferdium exist, but I really miss my browser extensions when I use a messaging app. I can use PWA's, but that's an even worse issue of having to check more windows for waiting messages. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351175] "Auto-Hide" mode does not work when panel is on an edge between two screens
https://bugs.kde.org/show_bug.cgi?id=351175 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #10 from Jason Straight --- I'm no longer on Tumbleweed (for now). Using Endeavour. Just today I decided to see if I still have the problem by disabling my startup script that runs `kwin_x11 --replace` on login. A little while later, kwin froze. Just thought it was worth mentioning that it still exists and it's not isolated to a single distro. Operating System: EndeavourOS KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.1-arch1-1 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i9-12900H Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Strix G733ZW_G733ZW System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 474994] New: baloo needs to support logical NOT
https://bugs.kde.org/show_bug.cgi?id=474994 Bug ID: 474994 Summary: baloo needs to support logical NOT Classification: Frameworks and Libraries Product: frameworks-baloo Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: baloo-bugs-n...@kde.org Reporter: j.straight-...@straights.net Target Milestone: --- It would be nice if searching with baloo frameworks supported NOT as well as the supported AND and OR. For example: I would like to be able to search `tags:"Automobiles" AND NOT tags:"1970 C-10"` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 Jason Straight changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468480] Crash when playing fourth video
https://bugs.kde.org/show_bug.cgi?id=468480 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t --- Comment #23 from Jason Straight --- Mine was crashing all the time. I tried the 8.1.0 appimage and it was also doing it, until I did two things, and I don't know which of the two, or both?, made the difference. Now I'm trying to crash it on videos and can't. What I think fixed it was going to settings in video and removing all the codecs for video, restarting digikam, then enabling ffmpeg again and restarting it again. The other thing I did before that, but it was still doing it after, was to remove the digikam thumbnails files in my Pictures folder. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #7 from Jason Straight --- I noticed something else about my "fix" for this, where I have a script run to dbus toggle compositing off/on. During the last couple weeks, I have never had a freeze using this method, but there's another bug that disappeared for me as well. Most times I would shut down or reboot my machine, it wouldn't finish shutting down. It would get stuck on a "shutting down" type message on the TTY. I was able to toggle to TTY7 and back and it would continue shutting down. But, since I've been toggling compositing on every login, I have not had that issue. I know there's another bug (saw mentioned on reddit) where SDDM is supposedly addressing that bug, but it could be related, or maybe some people are suffering that issue for another reason. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #6 from Jason Straight --- Comment on attachment 160034 --> https://bugs.kde.org/attachment.cgi?id=160034 kwin_x11 gdb backtrace This was taken as per instructed, after kwin_x11 was frozen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #5 from Jason Straight --- Created attachment 160034 --> https://bugs.kde.org/attachment.cgi?id=160034=edit kwin_x11 gdb backtrace -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #4 from Jason Straight --- Dur. I had a stupid moment, apparently. I was thinking your instructions included a kill and restarting with gdb. lol. I'll try this weekend. Thanks again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #3 from Jason Straight --- (In reply to Jason Straight from comment #2) > (In reply to Nate Graham from comment #1) > > From the description, it does sound like kwin_x11 is what's freezing here, > > not xorg. While frozen, switch to a real tty and run the following: > > > > sudo gdb --pid `pidof kwin_x11` > > > > wait for that to load and type: > > set logging on > > set pagination off > > bt > > quit > > > > This will save a file called gdb.txt in your home directory with the > > backtrace. > > Thanks. The problem is that if I kill it, or toggle it, it never crashes > then. lol Freezes, I mean. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- Comment #2 from Jason Straight --- (In reply to Nate Graham from comment #1) > From the description, it does sound like kwin_x11 is what's freezing here, > not xorg. While frozen, switch to a real tty and run the following: > > sudo gdb --pid `pidof kwin_x11` > > wait for that to load and type: > set logging on > set pagination off > bt > quit > > This will save a file called gdb.txt in your home directory with the > backtrace. Thanks. The problem is that if I kill it, or toggle it, it never crashes then. lol -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 Jason Straight changed: What|Removed |Added Version|git-stable-Plasma/5.27 |5.27.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] New: kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 Bug ID: 471136 Summary: kwin_x11 freezes xorg under certain conditions Classification: Plasma Product: kwin Version: git-stable-Plasma/5.27 Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: j.straight-...@straights.net Target Milestone: --- I had previously filed another bug, but it was closed as we were thinking it was kernel/i915 driver fault at the time. New information brings me back to kwin being at fault. ## ISSUE: Starting in February sometime, Tumbleweed updated from 6.1.8 to 6.1.10 kernel. Since then, and every kernel newer than 6.1.8, I have been experiencing freezing with kwin. ## WHY I THINK IT'S KWIN NOW: Through trials and tribulations of 4 months, I have found that if, after logging in, I disable compositing with ctrl-alt-f12, and then re-enable it with ctrl-alt-f12, it will not freeze. I have tested this method for 4 days now and not had a single freeze with many hours long sessions (12+). Normally, I'd be lucky to go anywhere from minutes to a few hours before freezing. It seems like causing the freeze might be expedited by playing video in a browser (tested with Vivaldi and Firefox). I've been testing by always having a browser window open playing a youtube video of 10 hours of oceanscapes, or something, on mute. ## DETAILS OF FREEZE: - Entire desktop image is frozen - Pointer still works - Pointer still operates on desktop under frozen image (more on that below) - killall -9 kwin_x11 and relaunching kwin_x11 recovers - If during the freeze, I tried to operate on any windows with pointer, they now show up in updated positions/sizes, etc. - Does not happen if compositing is disabled - Does not happen on kernels older than 6.1.9 - Does not happen with any other program - Does not happen on Gnome/Xorg - Does not happen on Wayland (But too many other things don't work for me) - Does not happen if compositing is toggled off then on after logging in - Does not happen a 2nd time if kwin is killed and restarted - Happens with a new user and user profile with default settings ## DEBUG? I would be willing to get a backtrace if I can. I've already installed debug symbols. I don't know exactly how - especially since it doesn't seem to want to do it if I launch kwin manually. ## SYSTEM: Operating System: openSUSE Tumbleweed 20230614 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.9 Kernel Version: 6.3.7-1-default (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i9-12900H Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Strix G733ZW_G733ZW System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 342326] window contents freeze
https://bugs.kde.org/show_bug.cgi?id=342326 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466622] kwin_x11 entire desktop freeze, mouse still works, killing kwin_x11 fixes, seems to only be on kernels newer than 6.1.8 for me (intel i915)
https://bugs.kde.org/show_bug.cgi?id=466622 --- Comment #3 from Jason Straight --- I was just about to call it quits to pack in to go to work and it froze again - compositing disabled. It looks like maybe they've seen (figured something out?) over on the i915 bug page. So we'll see where it goes from there. > Ville Syrjälä commented on a discussion: > Looks like the vblank worker somehow got stuck. > Let's try to add a timeout and some extra debugs: > https://github.com/vsyrjala/linux.git vblank_work_debug -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466622] kwin_x11 entire desktop freeze, mouse still works, killing kwin_x11 fixes, seems to only be on kernels newer than 6.1.8 for me (intel i915)
https://bugs.kde.org/show_bug.cgi?id=466622 --- Comment #2 from Jason Straight --- (In reply to Nate Graham from comment #1) > Thanks for the detailed bug report. Info from > https://gitlab.freedesktop.org/drm/intel/-/issues/8226 indicates that it may > even be a kernel bug. But I'll let the KWin developers handle this. > > Does it happen when compositing it turned off? Compositing turned off? Ee. lol I was hoping there would be progress (an answer) before I had to resort to testing that. :D I've been watching video (the thing that seems to make it most obvious) since you suggested it w/o issue, but that's not definitive yet. I'll continue to test and report back. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466622] New: kwin_x11 entire desktop freeze, mouse still works, killing kwin_x11 fixes, seems to only be on kernels newer than 6.1.8 for me (intel i915)
https://bugs.kde.org/show_bug.cgi?id=466622 Bug ID: 466622 Summary: kwin_x11 entire desktop freeze, mouse still works, killing kwin_x11 fixes, seems to only be on kernels newer than 6.1.8 for me (intel i915) Classification: Plasma Product: kwin Version: 5.27.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: j.straight-...@straights.net Target Milestone: --- I'm not really sure if this is entirely upstream, because the only thing it seems to affect is kwin. No other programs freeze or crash. My desktop will randomly freeze and require me to switch to a vtty and kill kwin_x11, which then gets restarted and everything is fine. The image is frozen - the desktop is not. So I'm _guessing_ it's related to compositor and effects. Even though the desktop image is frozen, the audio continues to play, and I can click where the (now frozen) video controls are to pause and restart the audio. I have filed this bug on the i915 drivers bug tracker here: https://gitlab.freedesktop.org/drm/intel/-/issues/8226 It only started happening after changes to i915 post 6.1.8. Linux 6.1.8 has been perfectly stable for me. Originally, I thought it only happened during playing videos in a browser, but it has since happened while not doing that, but it seems to happen more (often) while playing videos. I might go a couple days, or I might have 2 freezes in 10 minutes. Maybe someone can tell me what I might be able to do to enable some debugging logging for kwin and the compositor effects to help us pinpoint what's causing this? Thanks. Next time it happens, I'll try alt-shift-f12 before killing it. I tried that earlier today, but I had the key combo wrong I think. Operating System: openSUSE Tumbleweed 20230227 KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-1-default+ (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i9-12900H Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Strix G733ZW_G733ZW System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456988] On X11, Panel autohide with "Keep Window Thumbnails = Always" leaves panel image always visible but non-interactive
https://bugs.kde.org/show_bug.cgi?id=456988 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 463154] New: Plasma Network Manager Widget list of networks glitches during connection
https://bugs.kde.org/show_bug.cgi?id=463154 Bug ID: 463154 Summary: Plasma Network Manager Widget list of networks glitches during connection Classification: Plasma Product: plasma-nm Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: j.straight-...@straights.net Target Milestone: --- When using Network Manager Widget as a drop down/pop-up, during negotiation of a connection it corrupts the output of the list of networks and displays a large blank area. Scrolling jumps around. It's impossible to click on anything until the connection times out. If I add the widget to the desktop, expanded to a size that displays the list, it doesn't seem to exhibit the same behavior and works properly. It only seems to do this if you use the icon mode and have it pop-up/down to display the list. It has always been like this, and for some reason I just kept forgetting to file a report on it. I do have many wireless networks in my list, and several VPN's. Video example: https://youtube.com/shorts/7GhpGsmkaKI?feature=share -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459681] Resuming from powersaving/sleep results in display misconfiguration and lost window positions
https://bugs.kde.org/show_bug.cgi?id=459681 --- Comment #15 from Jason Straight --- It seems that what really makes the Windows come up in the wrong spot is when they're snapped to a screen edge. Where I see it is my 2nd monitor, which is an ultra wide, and I often have windows snapped to one side or the other. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 462859] Modifying message tags appearance creates duplicate message tags
https://bugs.kde.org/show_bug.cgi?id=462859 --- Comment #2 from Jason Straight --- More details: I think it might be limited to changing the background color. I've tried changing some other attributes and it created no duplicates. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 462859] Modifying message tags appearance creates duplicate message tags
https://bugs.kde.org/show_bug.cgi?id=462859 --- Comment #1 from Jason Straight --- I should elaborate that if you go to right click a message and tag it; Then you'll see the duplicates in the context menu. The duplicates do not show up immediately in Appearance until you close and re-open kmail. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 462859] New: Modifying message tags appearance creates duplicate message tags
https://bugs.kde.org/show_bug.cgi?id=462859 Bug ID: 462859 Summary: Modifying message tags appearance creates duplicate message tags Classification: Applications Product: kmail2 Version: 5.21.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: j.straight-...@straights.net Target Milestone: --- Go to settings > appearance > Message Tags Create a couple to few tags. Change the background color on any of them and hit okay. Every change to any tag attribute seems to create a duplicate of the most recently created tag. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446654] Feature Request: mirror a panel on all monitors
https://bugs.kde.org/show_bug.cgi?id=446654 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 401863] baloo creates multiple entries for files residing on multi-device btrfs file systems
https://bugs.kde.org/show_bug.cgi?id=401863 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459681] Resuming from powersaving/sleep results in display misconfiguration and lost window positions
https://bugs.kde.org/show_bug.cgi?id=459681 --- Comment #11 from Jason Straight --- Update: I switched to OpenSuSE Tumbleweed and no longer have the problems with the resolution being change after waking the screens, but the positions of the windows are not restored. They're shifted to the right, with whatever window was snapped to the right being partially off-screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459681] Resuming from powersaving/sleep results in display misconfiguration and lost window positions
https://bugs.kde.org/show_bug.cgi?id=459681 --- Comment #10 from Jason Straight --- If I use my thunderbolt usb 4 docking station, everything works fine. Still displayport. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459681] Resuming from powersaving/sleep results in display misconfiguration and lost window positions
https://bugs.kde.org/show_bug.cgi?id=459681 --- Comment #9 from Jason Straight --- Another observation that (so far) seems true, in case it helps: It only seems to have a problem the first time it sleeps the screens after a reboot. After it does the first time, I reconfigure my screen resolution, position, and refresh rate and then every time it sleeps afterwards it successfully wakes the screens with the right settings and window positions. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459681] Resuming from powersaving/sleep results in display misconfiguration and lost window positions
https://bugs.kde.org/show_bug.cgi?id=459681 --- Comment #8 from Jason Straight --- When it does come back with the proper screen settings, the windows appear to be in the right spots. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459681] Resuming from powersaving/sleep results in display misconfiguration and lost window positions
https://bugs.kde.org/show_bug.cgi?id=459681 --- Comment #7 from Jason Straight --- The reason I get the idea it has something to do with timing/time is because it takes a while of sitting for this to trigger. For testing, I set my screen sleep to 1 minute. If I wake the monitors right after they go to sleep, they wake up fine. If I wait for the monitor to wake back up and tell me there's no signal on DP, then it goes back to sleep. If I wake it up within several seconds of that, it still wakes up fine. I don't know exactly what the "safe" time is, maybe it's less than a couple minutes. But when it bugs out on me is after I've left it for about 5 or more minutes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459681] Resuming from powersaving/sleep results in display misconfiguration and lost window positions
https://bugs.kde.org/show_bug.cgi?id=459681 --- Comment #6 from Jason Straight --- (In reply to Zamundaaa from comment #5) > After you change the monitor settings back, do the windows move back to > their correct places again? No. Not in X anyway. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459681] Resuming from powersaving/sleep results in display misconfiguration and lost window positions
https://bugs.kde.org/show_bug.cgi?id=459681 --- Comment #4 from Jason Straight --- (In reply to Nate Graham from comment #3) > That will be because of another bug (monitor information stored in a > different way on Wayland vs X11). If you correct those things, reboot, and > then try to reproduce the issue, does it happen again? Still happens. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459681] Resuming from powersaving/sleep results in display misconfiguration and lost window positions
https://bugs.kde.org/show_bug.cgi?id=459681 --- Comment #2 from Jason Straight --- (In reply to Nate Graham from comment #1) > Is it any better with the Wayland session? Afraid not. First try - it lost my screen resolution and refresh rate. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459681] New: Resuming from powersaving/sleep results in display misconfiguration and lost window positions
https://bugs.kde.org/show_bug.cgi?id=459681 Bug ID: 459681 Summary: Resuming from powersaving/sleep results in display misconfiguration and lost window positions Classification: Plasma Product: kwin Version: 5.25.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: j.straight-...@straights.net Target Milestone: --- Still having issues with multiple screens on Xorg with 5.25.90 Beta. I have a 3440x1440@144Hz displayport screen oriented above my laptop's built in 1080 screen. Firefox was snapped to the right side of the wide screen. Upon waking from screen powersaving, Firefox is now half off the right side of the screen. Another powersave/wakeup immediately afterwards resulted in my displays being misconfigured. I feel like maybe it has to do with the time required for the external display to initialize after waking? kde now has it configured as a 1920x1080@60Hz display. I have to go into display settings and change it back to 3440x1440@144Hz. When it gets switched to 1080, it also ends up moving all windows to the built-in lower display. Operating System: EndeavourOS KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.9-arch1-g14-1 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i9-12900H Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Strix G733ZW_G733ZW System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 458075] New: Add a menu/.desktop item for Spectacle Annotate (spectacle -E) to more easily open files with annotate
https://bugs.kde.org/show_bug.cgi?id=458075 Bug ID: 458075 Summary: Add a menu/.desktop item for Spectacle Annotate (spectacle -E) to more easily open files with annotate Product: Spectacle Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: j.straight-...@straights.net CC: k...@david-redondo.de Target Milestone: --- Now that you can load existing images for annotation with spectacle, it would be nice to have that be pre-configured by default to be available for image files from a right click, etc. For myself, I've created a menu item [Spectacle Annotate] to run "spectacle -E %u" and added the file association for image files I work with. I think this should be there by default as part of spectacle. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock
https://bugs.kde.org/show_bug.cgi?id=435113 --- Comment #103 from Jason Straight --- (In reply to Nate Graham from comment #98) > For anyone who was originally experiencing this issue (like, a few months > ago or earlier) can you configm that it's fixed for you in Plasma 5.25.4? Or > is it still happening? After going home and then back to work where I have 2 of the same model mouse, I had to manually move the mouse pointer speed up a tick, apply, and back down to its original position. So it's still just setting itself to some default. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock
https://bugs.kde.org/show_bug.cgi?id=435113 --- Comment #99 from Jason Straight --- (In reply to Nate Graham from comment #98) > For anyone who was originally experiencing this issue (like, a few months > ago or earlier) can you configm that it's fixed for you in Plasma 5.25.4? Or > is it still happening? It doesn't seem to be happening. I've tried rebooting and suspend/resume several times now. I've just recently noticed that I think this was a compound problem for me. I have two Logitech G600 mice. One at home, and one at work. I've recently noticed that they often aren't acting right after resume and boot until I cycle the profiles on them. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 453090] Can't connect to a Windows samba share with samba-libs 4.16
https://bugs.kde.org/show_bug.cgi?id=453090 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455231] New: Icons only task manager window thumbnails missing
https://bugs.kde.org/show_bug.cgi?id=455231 Bug ID: 455231 Summary: Icons only task manager window thumbnails missing Product: plasmashell Version: 5.24.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: j.straight-...@straights.net Target Milestone: 1.0 After updating kde frameworks today, window thumbnails no longer work on task manager. The tooltips show up with an icon for the application, rather than the window thumbnails. Operating System: EndeavourOS KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.18.3-arch1-1 (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i9-12900H Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 430193] renderwidget.cpp overriding threadCount for real_time mlt option
https://bugs.kde.org/show_bug.cgi?id=430193 --- Comment #10 from Jason Straight --- This is still an issue. I rendered today and saw real_time is hard limited to -4, even if I try to set it in the other options widget. My encoding times are severely hampered because of this and my GPU (nvidia) is only being about 25% utilized for video encoding. Several times slower than ffmpeg or handbrake at encoding with similar options. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 402154] Baloo reindexes everything after every reboot
https://bugs.kde.org/show_bug.cgi?id=402154 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 450390] New: Wish to have mouse settings remembered per device, like screens, audio devices and their levels, and storage devices are
https://bugs.kde.org/show_bug.cgi?id=450390 Bug ID: 450390 Summary: Wish to have mouse settings remembered per device, like screens, audio devices and their levels, and storage devices are Product: systemsettings Version: 5.24.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_mouse Assignee: plasma-b...@kde.org Reporter: j.straight-...@straights.net Target Milestone: --- Much like other device settings are remembered by a device identifier, or UUID, it would be nice if, when switching mouse devices, the settings were remembered and applied when plugging a device in. So if you have a laptop and use different mouse devices at work and home, and yet another portable one, the profile (especially acceleration) could be applied for the right device. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450388] New: Mouse acceleration lost upon suspend resume
https://bugs.kde.org/show_bug.cgi?id=450388 Bug ID: 450388 Summary: Mouse acceleration lost upon suspend resume Product: plasmashell Version: 5.24.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Input Method Assignee: plasma-b...@kde.org Reporter: j.straight-...@straights.net CC: aleix...@kde.org Target Milestone: 1.0 Recently (in the last few weeks), the behavior of mouse acceleration changed. I apologize that I'm not sure if this is an Xorg issue, or a KDE one; or which component to file this under. It used to be that my mouse acceleration was remembered upon suspend and resume, but now, after resume, I have to go into mouse settings, where I see the slider in the position it's supposed to be in, but that's not the factor that's being used. I have to slide the pointer, hit apply, slide it again, and hit apply again. I'm running Xorg and Nvidia on Arch. Operating System: EndeavourOS KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 31.2 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2060/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433794] kwin compositor crash recovery handling is overly annoying
https://bugs.kde.org/show_bug.cgi?id=433794 --- Comment #1 from Jason Straight --- After someone on reddit said, "Lemme guess, you're using an Arch distro." and continued that all these kinds of problems seem to be on Arch systems, I tried OpenSuSE TW, and was surprised that the problem did not exist there. I've been TW since then [many months] without this issue. Tried Arch on an external SSD a few weeks back and the issue was still there. No clue what Arch does differently. Just FYI for anyone else finding this. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 441814] Plasma printers applet doesn't shift text to make room when expanding a printer
https://bugs.kde.org/show_bug.cgi?id=441814 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 441814] New: Plasma printers applet doesn't shift text to make room when expanding a printer
https://bugs.kde.org/show_bug.cgi?id=441814 Bug ID: 441814 Summary: Plasma printers applet doesn't shift text to make room when expanding a printer Product: print-manager Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: dantt...@gmail.com Reporter: j.straight-...@straights.net CC: plasma-b...@kde.org Target Milestone: --- Created attachment 141181 --> https://bugs.kde.org/attachment.cgi?id=141181=edit Screenshot showing failure to make room for dropdown text action items Maybe it doesn't handle a high number of printers well? If you look at my included screenshot, you'll see that I expanded the e-STIDIO2550C to access the options to "configure" and "view print queue", but they are rendered behind the printer below it and are unclickable. Operating System: openSUSE Tumbleweed 20210829 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.12-2-default (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2060/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 441499] network:/ protocol no longer valid - can't use dolphin to browse local network mdns/dnssd devices
https://bugs.kde.org/show_bug.cgi?id=441499 --- Comment #2 from Jason Straight --- (In reply to Nate Graham from comment #1) > This was intentional; we weren't aware that this was useful for anything. > > When you do discover a printer with it, what can you do with it? If you're familiar with Windows network discovery, it works like that. It will show the device, and you could get information about it, or just double click the device and it would open the admin webpage. So, in my workplace, I admin a network with many printers and MFP's on the network. It was nice to be able to go to network:/, and see all network printers, expand their listing (which displayed the services they offered, including the admin web interface), launch that web interface link and have it open in the browser. network:/ used to give you mostly the same info/links that were presented by running "avahi-browse -rat". -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 441499] New: network:/ protocol no longer valid - can't use dolphin to browse local network mdns/dnssd devices
https://bugs.kde.org/show_bug.cgi?id=441499 Bug ID: 441499 Summary: network:/ protocol no longer valid - can't use dolphin to browse local network mdns/dnssd devices Product: frameworks-kio Version: 5.85.0 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: j.straight-...@straights.net CC: kdelibs-b...@kde.org Target Milestone: --- Prior to the latest version, there was a "Network" category/protocol in dolphin under "Network" that showed locally discovered avahi mdns/dnssd devices [like printers] that was very useful. It's gone now, and kde doesn't support network:/ at all. It says "invalid protocol" Currently on OpenSuSE TW, but verified that's gone and not working in Neon also. If that stuff is supposed to be under zeroconf now, I have never had zeroconf:/ [in 20+ yrs of KDE, across numerous distros] populate anything more than localhost. Operating System: openSUSE Tumbleweed 20210820 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.12-1-default (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2060/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433094] No way to disable tearing prevention
https://bugs.kde.org/show_bug.cgi?id=433094 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t --- Comment #17 from Jason Straight --- (In reply to S. Christian Collins from comment #16) > This results in perfectly smooth, tear-free animation on the high refresh > rate display, and lower framerate, still tear-free animation on the other > display. Note that I am leaving out the "KWIN_X11_FORCE_SOFTWARE_VSYNC=1" > setting, as adding it results in dropped frames. Can you tell me how you monitored for the dropped frames, or was it just an observation? Also, how are you monitoring the FPS for kwin? With the built in compositor 'effect'? That shows me topped at 100fps, which is an improvement, but not the 144 I was expecting. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 434917] kio-fuse randomly named directory makes working with flatpaks difficult
https://bugs.kde.org/show_bug.cgi?id=434917 Jason Straight changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #6 from Jason Straight --- After following this down the rabbit hole, I'm convinced this is something that would be a non-issue if flatpak/gtk worked like it was supposed. Not a KDE/kiofuse problem. Thanks for pointing me in that direction. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 434917] kio-fuse randomly named directory makes working with flatpaks difficult
https://bugs.kde.org/show_bug.cgi?id=434917 --- Comment #5 from Jason Straight --- So it appears that portals only work with certain file choosers, and the programs I'm trying to use remotely don't use [the standard GTK one](https://blogs.gnome.org/mclasen/2016/07/08/portals-using-gtk-in-a-flatpak/), I'm guessing. I was able to access the kio-fuse-* folder from some gnome apps. So, this will probably remain to be an issue with several apps. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 434917] kio-fuse randomly named directory makes working with flatpaks difficult
https://bugs.kde.org/show_bug.cgi?id=434917 --- Comment #4 from Jason Straight --- (In reply to Fabian Vogt from comment #3) > The API is used to open files from the host file system. In file open > dialogs you can navigate to any location and select also files inside > kio-fuse mounts. Whenever I navigate to the xdg-run folder the kio-fuse-* folder is not present to the file dialog in any non kde program. Maybe my OpenSuSE is missing a required GTK package. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 434917] kio-fuse randomly named directory makes working with flatpaks difficult
https://bugs.kde.org/show_bug.cgi?id=434917 --- Comment #2 from Jason Straight --- (In reply to Fabian Vogt from comment #1) > Why do you pass --filesystem manually instead of using portals? I'm unsure how to use portals in this context. I thought that portals in flatpak were accessible via the API's and were something the desktop environment or developer would implement use of. I don't seem to be able to find any useful information for an end user to use portals to solve this kind of problem. If you have a source, I'd appreciate a link or two. Thanks. > In any case, there's https://invent.kde.org/system/kio-fuse/-/issues/18 with > some more discussion. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 434917] New: kio-fuse randomly named directory makes working with flatpaks difficult
https://bugs.kde.org/show_bug.cgi?id=434917 Bug ID: 434917 Summary: kio-fuse randomly named directory makes working with flatpaks difficult Product: kiofuse Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: a.saout...@gmail.com Reporter: j.straight-...@straights.net CC: fab...@ritter-vogt.de, kio-bugs-n...@kde.org Target Milestone: --- Accessing remote filesystems with flatpaks is a pain due to the fuse mountpoint being random at every use. I order to access a remote filesystem with a flatpak program, like brackets, you have to run it like flatpak run --filesystem=xdg-run/kio-fuse-OexuTR io.brackets.Brackets The fact that kio-fuse-OexuTR is different every time really complicates this. Why is this necessary? I don't think gvfs does it this way. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433794] New: kwin compositor crash recovery handling is overly annoying
https://bugs.kde.org/show_bug.cgi?id=433794 Bug ID: 433794 Summary: kwin compositor crash recovery handling is overly annoying Product: kwin Version: 5.21.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: j.straight-...@straights.net Target Milestone: --- Running nvidia on my laptop, when I disconnect external monitors, or suspend/resume, the compositor often crashes. I get that that probably can't be helped, but recovery is more annoying than it needs to be. Currently, I have to go into compositor settings and click the re-enable detection error message (ctrl-alt-f12 doesn't work). Then I have to change a setting twice. Once to get it to turn compositor back on, and once to change the setting back to where I want it to be, now that the compositor is enabled and working again. It would be nice if simply clicking the re-enable would turn the compositor back on, with current settings. I tried to figure out if there was a way to do this automatically with dbus and set a hotkey for it, but couldn't figure out what needed to be done, if it's even possible. Operating System: Manjaro Linux KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.11.2-1-MANJARO OS Type: 64-bit Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.5 GiB of RAM Graphics Processor: GeForce RTX 2060/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409980] Window thumbnails and titles are missing for all windows of an app when one window is playing media
https://bugs.kde.org/show_bug.cgi?id=409980 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427340] Systemd startup: things in autostart don't autostart
https://bugs.kde.org/show_bug.cgi?id=427340 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 433234] Poor incremental search results in Kickoff for the first two characters
https://bugs.kde.org/show_bug.cgi?id=433234 --- Comment #3 from Jason Straight --- Not OP, but yes. Krunner does the same thing for me. I have, on the launcher, disabled all searching except for applications. Not that that matters. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433166] Plasma slows to a crawl with low CPU usage after certain system setting changes
https://bugs.kde.org/show_bug.cgi?id=433166 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433234] Poor incremental search results in Kickoff for the first two characters
https://bugs.kde.org/show_bug.cgi?id=433234 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433215] Regression: can no longer delete or disable unwanted fonts
https://bugs.kde.org/show_bug.cgi?id=433215 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 433237] Kate doesn't restore session on startup
https://bugs.kde.org/show_bug.cgi?id=433237 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t --- Comment #1 from Jason Straight --- I've never used this feature before, but it got me curious. If you open some files and save/name a session then it will open the last used one. If you don't save/load a session then you seem to be in a sessionless instance and it therefore will not load the last session, because you weren't technically in a named/saved session. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 432856] Can't reopen remote files using common "File, Open recent" menu option
https://bugs.kde.org/show_bug.cgi?id=432856 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 432628] Dolphin can't preview files accessed via smb:// in the information panel
https://bugs.kde.org/show_bug.cgi?id=432628 --- Comment #9 from Jason Straight --- (In reply to Harald Sitter from comment #8) > Which phonon backend do you have installed? junfan@V ~ % yay -Q | grep phonon phonon-qt5 4.11.1-2 phonon-qt5-gstreamer 4.10.0-2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 432719] No easy/intuitive way to clear search tags in dolphin
https://bugs.kde.org/show_bug.cgi?id=432719 --- Comment #2 from Jason Straight --- (In reply to Nate Graham from comment #1) > You can also just delete the text "tag:jason" in the search field. That's the problem. It doesn't work. The tag drop down stays with tag:jason. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 432720] New: File properties tag management needs improvement
https://bugs.kde.org/show_bug.cgi?id=432720 Bug ID: 432720 Summary: File properties tag management needs improvement Product: dolphin Version: 20.12.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: j.straight-...@straights.net CC: kfm-de...@kde.org Target Milestone: --- Created attachment 135551 --> https://bugs.kde.org/attachment.cgi?id=135551=edit file property tags First, I feel like this should probably be linked to a library, not dolphin, but I have no idea which one. It has to do with file properties. When you edit properties/tags for an object managing them is cumbersome when you have many. There should be a filter field to narrow them down. Perhaps one that autocompletes, so you can type in part of a tag name, it will filter them down to those that match as you type, and then you can click (or arrow key/enter) on the tag you want to add/remove for the file. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 432719] New: No easy/intuitive way to clear search tags in dolphin
https://bugs.kde.org/show_bug.cgi?id=432719 Bug ID: 432719 Summary: No easy/intuitive way to clear search tags in dolphin Product: dolphin Version: 20.12.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: j.straight-...@straights.net CC: kfm-de...@kde.org Target Milestone: --- Created attachment 135550 --> https://bugs.kde.org/attachment.cgi?id=135550=edit dolphin search When doing a file search from Dolphin and using the search input field to search for example "tag:penguin", dolphin will add that tag filter to the dropdown menu, and the only way to clear it is to expand that and un-select that tag, or to quit dolphin and restart it. If you have hundreds of tags, like I do, then the dropdown menu for tags doesn't fit on the screen, and you can't clear it. There should be an easy way to reset the search. Closing just the search doesn't clear it. I think the whole tagging system could honestly use a different approach. Maybe use scrollable dropdown filters, the way digikam does it, and the top one could be an option to 'clear' or 'reset'? Operating System: Manjaro Linux KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.14-1-MANJARO OS Type: 64-bit Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.5 GiB of RAM Graphics Processor: GeForce RTX 2060/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 432628] Dolphin file previews don't work with remote smb despite being under the remote preview file size limit
https://bugs.kde.org/show_bug.cgi?id=432628 Jason Straight changed: What|Removed |Added Platform|unspecified |Manjaro Version|unspecified |20.12.2 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 432628] Dolphin file previews don't work with remote smb despite being under the remote preview file size limit
https://bugs.kde.org/show_bug.cgi?id=432628 --- Comment #6 from Jason Straight --- For the record, we're talking about the same preview right? The pane on the right? The play button is what doesn't work for me. Dolphin 20.12.2 on Manjaro Operating System: Manjaro Linux KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.14-1-MANJARO OS Type: 64-bit Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.5 GiB of RAM Graphics Processor: GeForce RTX 2060/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 432628] Dolphin file previews don't work with remote smb with kio-fuse?
https://bugs.kde.org/show_bug.cgi?id=432628 --- Comment #4 from Jason Straight --- I've actually got that set to 10MB. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 432628] Dolphin file previews don't work with remote smb with kio-fuse?
https://bugs.kde.org/show_bug.cgi?id=432628 --- Comment #2 from Jason Straight --- Created attachment 135544 --> https://bugs.kde.org/attachment.cgi?id=135544=edit Dolphin browsing shared smb folder containing sounds -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 432627] drag and drop from remote locations (dolphin/kio-fuse) to apps not working
https://bugs.kde.org/show_bug.cgi?id=432627 --- Comment #7 from Jason Straight --- Okay, thanks for that explanation. So, should we file reports when we find apps that don't work with opening (double or right click), and drag and drop, or not? I'm certainly glad that the changes we've seen in the last year on this have taken place. It has made things so much nicer working with remote shares and KDE. For now, what I end up doing is hitting F4 to open a shell in dolphin, pwd to get the location to the fuse mount, paste that to dolphin and use that for drag and drop operations. It's a bit of a kludge, but a lot better than it was prior to kio-fuse integration. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 432627] drag and drop from remote locations (dolphin/kio-fuse) to apps not working
https://bugs.kde.org/show_bug.cgi?id=432627 --- Comment #5 from Jason Straight --- s/vnc/vlc -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 432627] drag and drop from remote locations (dolphin/kio-fuse) to apps not working
https://bugs.kde.org/show_bug.cgi?id=432627 --- Comment #4 from Jason Straight --- Sorry. I know you shouldn't have to educate me, but if all those apps can take file paths, how do they break? Even with VLC accepting smb:// urls doesn't that cause problems when the share it's trying to access is password protected? Sure kio may auth the share, but then it passes the url to vnc and vnc needs to authenticate. In fact, to get around that, I've set vlc to use the file path %F, rather than the %U url to get around that, and it works better than passing the smb://, IMO. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 432627] drag and drop from remote locations (dolphin/kio-fuse) to apps not working
https://bugs.kde.org/show_bug.cgi?id=432627 --- Comment #2 from Jason Straight --- Why not just use the fuse path for everything smb related, if fuse is supported on the host system? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 423189] Cannot make default script active
https://bugs.kde.org/show_bug.cgi?id=423189 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t --- Comment #3 from Jason Straight --- I don't know if this helps or not, but thunderbird with the sieve addon can make the script active. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 432628] New: Dolphin file previews don't work with remote smb with kio-fuse?
https://bugs.kde.org/show_bug.cgi?id=432628 Bug ID: 432628 Summary: Dolphin file previews don't work with remote smb with kio-fuse? Product: kiofuse Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: a.saout...@gmail.com Reporter: j.straight-...@straights.net Target Milestone: --- Not sure if this should be filed under dolphin, or kio-fuse. Navigating to a remote folder with multimedia files, like sound/video doesn't allow me to play the previews in the preview pane in Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 432627] New: drag and drop from remote locations (dolphin/kio-fuse) to apps not working
https://bugs.kde.org/show_bug.cgi?id=432627 Bug ID: 432627 Summary: drag and drop from remote locations (dolphin/kio-fuse) to apps not working Product: kiofuse Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: a.saout...@gmail.com Reporter: j.straight-...@straights.net Target Milestone: --- If I access a remote smb share with dolphin, I can drag and drop a text file on an open kate to open the text file. This seems to be about the only app it works with. Even KDE apps I've tried don't work. What I know doesn't work: - Thunderbird e-mail attaching - videos with kdenlive - pictures with krita - Audio files with audacity - text and source files with vscode Seems like if an icon is dragged/dropped to an app, it should send the app the local path (if one is available). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358930] moving the mouse over a different application icon immediately changes the window list
https://bugs.kde.org/show_bug.cgi?id=358930 Jason Straight changed: What|Removed |Added CC||j.straight-...@straights.ne ||t -- You are receiving this mail because: You are watching all bug changes.
