[dolphin] [Bug 471279] Dolphin crash when dragging files or folders across or to the path navigation bar
https://bugs.kde.org/show_bug.cgi?id=471279 vindicator changed: What|Removed |Added CC||nroycea+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483538] [Wayland] VRAM leak when repeatedly switching between window icons
https://bugs.kde.org/show_bug.cgi?id=483538 --- Comment #7 from vindicator --- Created attachment 168764 --> https://bugs.kde.org/attachment.cgi?id=168764=edit Heaptrack Top-Down -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483538] [Wayland] VRAM leak when repeatedly switching between window icons
https://bugs.kde.org/show_bug.cgi?id=483538 --- Comment #6 from vindicator --- Created attachment 168763 --> https://bugs.kde.org/attachment.cgi?id=168763=edit Heaptrack Consumed -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483538] [Wayland] VRAM leak when repeatedly switching between window icons
https://bugs.kde.org/show_bug.cgi?id=483538 vindicator changed: What|Removed |Added CC||nroycea+...@gmail.com --- Comment #5 from vindicator --- I'm also encountering a memory leak when hovering over the applications in the status bar (not VRAM though). X11 (but probably wayland as well since I switched back to X11 after another unusable wayland issue). I'll be attaching screencaps of heaptrack's "Consumed" and "Top-Down" tabs. You'll notice the few areas in the chart where I intentionally hovered over each active application in the status bar back and forth several times, along with my time away from my computer (where there was no change). Is the thumbnail/preview being created and not cached or disposed of every time? Just cache it once for a given PID and dispose of it when the process terminates. My undesirable workaround for plasmashell as a whole is just to have it die by using "MemoryMax=600M" for the service, where it then just respawns fresh (though open applications in the statusbar may get rearranged each time). I used that for wayland too, but it was happening much more frequently (more than once a day vs probably a week+ on X11 before it dies), and it was worse for wayland because yesterday before I switched, plasmashell was stuck in a dying state and there were 2 processes open for it. I had to SIGKILL the earlier one. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472369] Please allow disabling resize-both-windows when quick tiling
https://bugs.kde.org/show_bug.cgi?id=472369 --- Comment #6 from vindicator --- I'll say that in my view the design should be to have quick-tiling set via the tile-editor for all new windows (and for those existing windows that are drag/dropped into the tile slot). Then to allow window-edge-binding, that ought to also be done in the tile-editor whereby you CTRL-click-(bind/group) each window you want bound together. Then outside of the tile-editor, you can resize any of those window edges and only the bound ones will resize with it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480376] Bring Back Compositing Setting
https://bugs.kde.org/show_bug.cgi?id=480376 --- Comment #8 from vindicator --- LOL! I hope I won't need to open up an issue for that. XD -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480376] Bring Back Compositing Setting
https://bugs.kde.org/show_bug.cgi?id=480376 --- Comment #6 from vindicator --- If you're referring to Alt+Shift+F12 to suspend compositing, I'm not seeing any counterpart to that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480376] Bring Back Compositing Setting
https://bugs.kde.org/show_bug.cgi?id=480376 --- Comment #4 from vindicator --- But the "Enable on startup" checkbox is solely for just that... "startup". If I uncheck it, compositiing is still enabled (just tested by moving the Settings window and seeing the grid). Like I've been saying, I believe there was a "disable" option under the rendering part that just shut it off right then and there. The only way for me to change the "enablement" was via dbus now. Also just tested by triggering "suspend", and no grid showed when moving the qdbus window. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480376] Bring Back Compositing Setting
https://bugs.kde.org/show_bug.cgi?id=480376 --- Comment #2 from vindicator --- Created attachment 165316 --> https://bugs.kde.org/attachment.cgi?id=165316=edit Compositing Choices Removed? I attached a screenshot for what it is now vs https://www.reddit.com/r/kde/comments/hl1lak/how_to_disable_compositing_under_wayland_the/ which is how I remember it existing (note the "rendering backend" option where I believe the "disable/x11/opengl" options were. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480376] New: Bring Back Compositing Setting
https://bugs.kde.org/show_bug.cgi?id=480376 Bug ID: 480376 Summary: Bring Back Compositing Setting Classification: Plasma Product: kwin Version: 5.27.10 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: nroycea+...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Due to a previous bug (linked below), I found that compositing was disabled on my system (the cause for that linked issue), but there was no setting available in the GUI to change such feature. I was forced to use QDBus to manually find it under KWin and re-enable it. STEPS TO REPRODUCE 1. Magically disable compositing (via some dbus app, or an older KDE version that had the compositing setting) 2. Try to use todays KDE's "Settings" to re-enable it. OBSERVED RESULT Compositing setting was removed quite some time ago EXPECTED RESULT The return of the compositing setting SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Ref: https://bugs.kde.org/show_bug.cgi?id=470998#c7 If I recall correctly, the setting allowed you to switch between disabled/X11/OpenGl. But for whatever reason, that option no longer exists. I know I've disabled it in the past (when the setting was available in Settings) because of rendering issues (not seen yet after re-enabling, but even now I'll have performance responsiveness issues). It's on a very old Gen7 Haswell with 8GB RAM (was waiting for Alder Lake, then Meteor Lake looked better, but not going to happen, so sight is set on Arrow Lake now). As an aside which can be ignored since I see it's expressed elsewhere many times over, I too don't care for the 5.27 tiling that was produced, where it locks windows-sizes to each other. That must change by becoming an option. My ideal is to have 25%-corner snapping, and even top-max snapping and side-edge snapping (as it all was before), but not to have any snapped window latch onto any other window edge when it is being resized. I can see the value for some, but when it's indiscriminate to which window(s) it latches onto, I see that as a problem. Even now when I start off with 1/4-snapping, which works out fine, then start doing other odd snapped window sizes (resized; non-1/4), any re-1/4-snapping now starts going off of where that oddly-snapped window is (or even "was", after that window was closed). Like I said, this rant can be ignored since it's all been said ad nauseam in other places and must already be on the dev's radar. It's only mildly related (via the linked reference). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470998] Tile Editor Launcher HotKey Meta+T Not Working
https://bugs.kde.org/show_bug.cgi?id=470998 --- Comment #6 from vindicator --- The issue was due to compositing somehow being disabled with the compositing setting no longer available now (whereas it used to allow you to switch between like x11,opengl,egl I think). I had to use dbus to even find the compositing setting and change the "active" state. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465937] Split does not reset to its original value once "adjacent quick-tiled windows" configuration ceases to exist
https://bugs.kde.org/show_bug.cgi?id=465937 vindicator changed: What|Removed |Added CC||nroycea+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478806] Plasmashell Coredump After Kscreenlock_greet[er] Fails To Display And Screen Remains Black
https://bugs.kde.org/show_bug.cgi?id=478806 vindicator changed: What|Removed |Added Resolution|BACKTRACE |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #2 from vindicator --- Welp, I borked that royally... I was in the middle of my reply and thought I'd try to restart the dbus session service, and it wiped out EVERYTHING I had open (dunno if that's just to be expected?). Plasmashell and kwin, konsoles, chrome, ..., all closed down and I had to switch tty to kill that session. I'm not sure I'll keep this succinct, but in essence, I think I'll close as "NOT A BUG" since I had been screwing around with dbus while exploring systemd-nspawn containers, and the symbol trace output showed just that, which prompted me to try just restarting the debug session to see if I could then restart the plasmashell service as well. I had screwed up dbus once before while experimenting and just ended up restarting my machine when things went awry. No need to restart my machine this time, but restarting that dbus session was apparently a no-no, and I had to restart that session altogether. For completeness since asked: * Starting program: /usr/bin/plasmashell [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0x706706c0 (LWP 813826)] [New Thread 0x7fffefe6f6c0 (LWP 813827)] QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' [New Thread 0x7fffecbf56c0 (LWP 813828)] [New Thread 0x7fffd7c1e6c0 (LWP 813829)] [Thread 0x7fffd7c1e6c0 (LWP 813829) exited] QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' [New Thread 0x7fffd7c1e6c0 (LWP 813830)] Checking screens: available: (QScreen(0x556ce790, name="HDMI-1")) redundant: QHash() fake: QSet() all: (QScreen(0x556ce790, name="HDMI-1")) Checking screens: available: (QScreen(0x556ce790, name="HDMI-1")) redundant: QHash() fake: QSet() all: (QScreen(0x556ce790, name="HDMI-1")) kf.dbusaddons: DBus session bus not found. To circumvent this problem try the following command (with bash): export $(dbus-launch) [Thread 0x7fffd7c1e6c0 (LWP 813830) exited] [Thread 0x7fffecbf56c0 (LWP 813828) exited] [Thread 0x706706c0 (LWP 813826) exited] [Thread 0x70b69040 (LWP 813823) exited] [Thread 0x7fffefe6f6c0 (LWP 813827) exited] [New process 813823] [Inferior 1 (process 813823) exited with code 01] * As you can see with "DBus session bus not found", that aligns with my messing around with containers before. Not sure what I could do to restart the dbus session without every process just dropping off the face of the earth. And for a little bonus, the dbus session output after I restarted from the first screwup (note the "timeout"s: * ... Dec 15 15:11:00 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activating service name='org.freedesktop.Notifications' requested by ':1.34' (uid=1000 pid=1691 comm="/usr/lib/kdeconnectd") Dec 15 15:11:18 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activating service name='org.kde.KSplash' requested by ':1.20' (uid=1000 pid=1561 comm="/usr/bin/plasmashell --no-respawn") Dec 15 15:12:00 computerName plasma_waitforname[1740]: org.kde.knotifications: WaitForName: Service was not registered within timeout Dec 15 15:12:00 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1 Dec 15 15:12:18 computerName plasma_waitforname[1777]: org.kde.knotifications: WaitForName: Service was not registered within timeout Dec 15 15:12:18 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activated service 'org.kde.KSplash' failed: Process org.kde.KSplash exited with status 1 Dec 15 15:24:41 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activating service name='org.freedesktop.Notifications' requested by ':1.36' (uid=1000 pid=1693 comm="/usr/bin/keepassxc") Dec 15 15:24:43 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.55' (uid=1000 pid=4055 comm="/opt/google/chrome/chrome --password> Dec 15 15:24:43 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Successfully activated service 'org.a11y.Bus' Dec 15 15:24:52 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Activating via systemd: service name='org.kde.krunner' unit='plasma-krunner.service' requested by ':1.18' (uid=1000 pid=1548 comm="/usr/bin/kglobalaccel5") Dec 15 15:24:52 computerName dbus-daemon[1375]: [session uid=1000 pid=1375] Successfully activated service 'org.kde.krunne
[plasmashell] [Bug 478806] New: Plasmashell Coredump After Kscreenlock_greet[er] Fails To Display And Screen Remains Black
https://bugs.kde.org/show_bug.cgi?id=478806 Bug ID: 478806 Summary: Plasmashell Coredump After Kscreenlock_greet[er] Fails To Display And Screen Remains Black Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: nroycea+...@gmail.com Target Milestone: 1.0 SUMMARY When the screen *BEGINS* the transition to lockscreen (idle), and I move my mouse to stop the transition, the screen remained black with only the mouse cursor showing/moving. Switching ttys, I tried to restart the plasmashell service (not sure that could be done from another tty), and it crashed. I used "loginctl" to lock all sessions and unlock that GUI one, where I could switch back to it, only to find plasmashell was still dead. With "konsole" still up, I again tried to restart plasmashell, but the same coredump was happening. I manually started plasmashell, circumventing the service, and it came back. Even with it being back, I STILL could not restart the plasmashell service without it coredumping. I'm currently still live on this system (no reboot yet) in case other testing would like to be done while in this state. STEPS TO REPRODUCE 1. Wait for screen lock to *start*, and move mouse to avoid it the moment the screen goes black (starting to lock). 2. Notice screen remains black and no unlocker is presented. Only the mouse cursor is displayed. 3. Switch tty and try to restart plasmashell service. //Fails 4. $ loginctl lock-sessions; loginctl list-sessions; loginctl unlock-session <#> 5. Switch back to GUI and notice plasmashell is still dead. 6. Try to restart plasmashell service in konsole and notice it coredumps again. 7. $ plasmashell --replace & //"--replace" not needed if "$ ps" doesn't show it running. 8. Notice plasmashell is now running after having started it manually from konsole. OBSERVED RESULT Crash EXPECTED RESULT Don't crash SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Dump: * Message: Process 698869 (plasmashell) of user 1000 dumped core. Stack trace of thread 698869: #0 0x7f3817b6283c n/a (libc.so.6 + 0x8e83c) #1 0x7f3817b12668 raise (libc.so.6 + 0x3e668) #2 0x7f3817afa4b8 abort (libc.so.6 + 0x264b8) #3 0x7f3817fd10c2 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0xa00c2) #4 0x7f38185a8402 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 + 0x13f402) #5 0x7f38185a8a99 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x13fa99) #6 0x7f38181ccc05 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x29bc05) #7 0x7f38185a8b46 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x13fb46) #8 0x7f3818e4bb9e _ZN19QApplicationPrivate4initEv (libQt5Widgets.so.5 + 0x175b9e) #9 0x556f3e29f3c6 n/a (plasmashell + 0x213c6) #10 0x7f3817afbcd0 n/a (libc.so.6 + 0x27cd0) #11 0x7f3817afbd8a __libc_start_main (libc.so.6 + 0x27d8a) #12 0x556f3e2a2515 n/a (plasmashell + 0x24515) Stack trace of thread 698870: #0 0x7f3817bd6f6f __poll (libc.so.6 + 0x102f6f) #1 0x7f3816c872b6 n/a (libglib-2.0.so.0 + 0xb82b6) #2 0x7f3816c27162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162) #3 0x7f381821bf7c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2eaf7c) #4 0x7f38181cbe74 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x29ae74) #5 0x7f38180284f6 _ZN7QThread4execEv (libQt5Core.so.5 + 0xf74f6) #6 0x7f3818b07a9a n/a (libQt5DBus.so.5 + 0x18a9a) #7 0x7f381802471a n/a (libQt5Core.so.5 + 0xf371a) #8 0x7f3817b609eb n/a (libc.so.6 + 0x8c9eb) #9 0x7f3817be47cc n/a (libc.so.6 + 0x1107cc) ELF object binary architecture: AMD x86-64 * -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472369] Please allow disabling resize-both-windows when quick tiling
https://bugs.kde.org/show_bug.cgi?id=472369 vindicator changed: What|Removed |Added CC||nroycea+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472368] Please allow disabling revert-to-original-size on quick tiling unsnap
https://bugs.kde.org/show_bug.cgi?id=472368 vindicator changed: What|Removed |Added CC||nroycea+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465423] "Move to [activity name]" Menu items do nothing
https://bugs.kde.org/show_bug.cgi?id=465423 --- Comment #17 from vindicator --- I am also currently on 5.27.6 w/X11, and the issue continues to persist for me. And with no logging appearing in the journal when I make the action, is not helping in finding a solution. I'd think it'd help KDE devs if an option/setting were given to users to enable debug/trace log entries for selectable components. Even if the GUI environment would be completely non-functional, a user could still switch tty and manually edit a kde config file which would be watched (inotify/dnotify) for changes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470998] Tile Editor Launcher HotKey Meta+T Not Working
https://bugs.kde.org/show_bug.cgi?id=470998 vindicator changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from vindicator --- LOL @ bot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470998] Tile Editor Launcher HotKey Meta+T Not Working
https://bugs.kde.org/show_bug.cgi?id=470998
--- Comment #3 from vindicator ---
(In reply to Nate Graham from comment #2)
> Vindicator, are you on X11 or Wayland when this happens?
>
> Also can you look in System Settings > Workspace Behavior > Desktop Effects
> and make sure that "Tiling Editor" is checked/enabled? Thanks!
X11
Yes, while "I've tried it with each
Settings->Workspace->{Shortcuts->Plasma->Toggle Tiles Editor, Workspace
Behavior->Desktop Effects->Tiling Editor} separately having ownership of the
Meta+T keys.", I also made sure "Workspace Behavior->Desktop Effects->Tiling
Editor" was enabled too. It still is (even had applied off/on states to make
sure they were taking).
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 470998] New: Tile Editor Launcher HotKey Meta+T Not Working
https://bugs.kde.org/show_bug.cgi?id=470998
Bug ID: 470998
Summary: Tile Editor Launcher HotKey Meta+T Not Working
Classification: Plasma
Product: kwin
Version: 5.27.5
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Custom Tiling
Assignee: kwin-bugs-n...@kde.org
Reporter: nroycea+...@gmail.com
CC: notm...@gmail.com
Target Milestone: ---
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
STEPS TO REPRODUCE
1. Press Meta+T
OBSERVED RESULT
Nothingness
EXPECTED RESULT
Tiling Editor
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
ADDITIONAL INFORMATION
After months, I finally snapped/raged at the tiling and decided to look into
why the quartiles weren't quartiling equally.
Seems someone touched how tiling was done. After looking at videos, it seems
like it may still be acceptable, except I can't get the Tiling Editor to come
up at all.
It just does nothing other than recognize the 't' character being pressed.
(Other meta shortcuts DO work). Even the journal doesn't show any output
related to it.
I've tried it with each Settings->Workspace->{Shortcuts->Plasma->Toggle Tiles
Editor, Workspace Behavior->Desktop Effects->Tiling Editor} separately having
ownership of the Meta+T keys.
I don't know if there's a command/dbus-interface that I can trigger the Tiling
Editor to pop-up, in case I'm missing some component package or something.
I'd expect that if I were missing something, that I'd be informed of a failure
when the key-combo is pressed.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 465423] "Move to [activity name]" Menu items do nothing
https://bugs.kde.org/show_bug.cgi?id=465423 --- Comment #14 from vindicator --- Again, not true for me. It doesn't matter how many times I attempt it, it never moves. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465423] "Move to [activity name]" Menu items do nothing
https://bugs.kde.org/show_bug.cgi?id=465423 --- Comment #12 from vindicator --- That isn't true for me either. If I click on "Show in activities" -> , it doesn't move it, or show it in that activity, nor does the checkbox even show as selected. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465423] "Show In Activities" Taskbar Context Menu Buttons Do Nothing
https://bugs.kde.org/show_bug.cgi?id=465423 vindicator changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|FIXED |--- Version|5.26.5 |5.27.4 --- Comment #10 from vindicator --- Given that I just tested the feature as I described in my OP, and got the same result, and my sys-info says: * Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.1-dirty (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i3-4130 CPU @ 3.40GHz Memory: 7.2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4400 * ... I'm going to have to disagree about it being "Fixed". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466887] New: Journal Flood: "QObject::connect: No such slot DesktopProtocol::_k_slotRedirection(KIO::Job *, QUrl)"
https://bugs.kde.org/show_bug.cgi?id=466887 Bug ID: 466887 Summary: Journal Flood: "QObject::connect: No such slot DesktopProtocol::_k_slotRedirection(KIO::Job *, QUrl)" Classification: Plasma Product: plasmashell Version: git-stable-Plasma/5.27 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nroycea+...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY I normally wear headphones, but when I turn on my A/V receiver, which takes my computer's HDMI output, plasmashell gets tough to respond before it dies out. STEPS TO REPRODUCE 1. Turn on A/V receiver. OBSERVED RESULT Plasmashell is tough to respond because it is so busy. There's a lot of I/O with plasmashell and kioslave5. The journal gets flooded with kioslave5 entries mentioned in the title. Eventually plasmashell dies out because a long time ago I set a systemd --user memory limit because it kept leaking. Once it restarts, things settle down. EXPECTED RESULT Normal usage. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I've even encountered a case where plasmashell constantly respawned. I increased the memory limit to 600MB (from 500MB). While it was flooding the log before dying out, I got a backtrace of kioslave5. ** 0x7f9f0a4b2ad6 in ppoll () from /usr/lib/libc.so.6 (gdb) bt #0 0x7f9f0a4b2ad6 in ppoll () from /usr/lib/libc.so.6 #1 0x7f9f0a870d0b in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/libQt5Core.so.5 #2 0x7f9f0a2971a4 in ?? () from /usr/lib/libQt5Network.so.5 #3 0x7f9f0a2988d6 in ?? () from /usr/lib/libQt5Network.so.5 #4 0x7f9f0a285eb7 in QAbstractSocket::waitForReadyRead(int) () from /usr/lib/libQt5Network.so.5 #5 0x7f9f0ab10dfa in ?? () from /usr/lib/libKF5KIOCore.so.5 #6 0x7f9f0ab4524a in KIO::SlaveBase::dispatchLoop() () from /usr/lib/libKF5KIOCore.so.5 #7 0x7f9f0ac5e514 in kdemain () from /usr/lib/qt/plugins/kf5/kio/desktop.so #8 0x564316096207 in ?? () #9 0x7f9f0a3db790 in ?? () from /usr/lib/libc.so.6 #10 0x7f9f0a3db84a in __libc_start_main () from /usr/lib/libc.so.6 #11 0x564316096465 in ?? () ** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465423] "Show In Activities" Taskbar Context Menu Buttons Do Nothing
https://bugs.kde.org/show_bug.cgi?id=465423 --- Comment #7 from vindicator --- It does not move/show in the other one. Nor is the checkbox show as being activated when using "Move to". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465423] "Show In Activities" Taskbar Context Menu Buttons Do Nothing
https://bugs.kde.org/show_bug.cgi?id=465423 --- Comment #5 from vindicator --- Although note there are some programs like Google Chrome which will give an option to not run the program in a kwin window (aka without titlebar). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465423] "Show In Activities" Taskbar Context Menu Buttons Do Nothing
https://bugs.kde.org/show_bug.cgi?id=465423 --- Comment #4 from vindicator --- That would be Steps 5-7, so yes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465423] "Show In Activities" Taskbar Context Menu Buttons Do Nothing
https://bugs.kde.org/show_bug.cgi?id=465423 --- Comment #2 from vindicator --- X11. I've got a 10ft pole for Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465423] New: "Show In Activities" Taskbar Context Menu Buttons Do Nothing
https://bugs.kde.org/show_bug.cgi?id=465423 Bug ID: 465423 Summary: "Show In Activities" Taskbar Context Menu Buttons Do Nothing Classification: Plasma Product: kwin Version: 5.26.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: activities Assignee: kwin-bugs-n...@kde.org Reporter: nroycea+...@gmail.com Target Milestone: --- SUMMARY If I try to use ANY activity context menu buttons for a program in the taskbar, no action occurs. It doesn't even register ANY entry in the journal. STEPS TO REPRODUCE 1. Open KCalc (or anything I'm sure) 2. Right-mouse on KCalc in the taskbar 3. "Show In Activities" -> ["Move to" | ] 4. Note how nothing happens 5. Click the KCalc window menu option at the top left 6. "Show In Activities" -> 7. Note how the program moves to the other activity this time. OBSERVED RESULT "Step" 4 and 7 EXPECTED RESULT Step 7 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Somewhat unrelated, but as others have said in their reports, I'd agree that the context menu ought to remain up when a checkbox is clicked, but it can close if the label next to the checkbox is clicked. It's similar to how gmail "labels" work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423372] Plasmashell Memory Leak
https://bugs.kde.org/show_bug.cgi?id=423372 --- Comment #14 from vindicator --- I'll leave this here, regarding that thought: https://gitlab.freedesktop.org/drm/intel/-/issues/2924#note_1324171 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405898] Taskbar Incorrect Drawing When Applications Open/Close Causing A Taskbar Item Resize
https://bugs.kde.org/show_bug.cgi?id=405898 vindicator changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405898] Taskbar Incorrect Drawing When Applications Open/Close Causing A Taskbar Item Resize
https://bugs.kde.org/show_bug.cgi?id=405898 vindicator changed: What|Removed |Added Version Fixed In||5.24.5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453206] Paste option in context menu does not work in details mode
https://bugs.kde.org/show_bug.cgi?id=453206 vindicator changed: What|Removed |Added CC||nroycea+...@gmail.com --- Comment #5 from vindicator --- I have that same experience and also noticed that if the folder has other folders as well and you context-menu in an open area for any of the folders (instead of files), the paste option will show. So for now, I have to have the destination folder open in another tab and drag it there, or just use the shortcut CTRL+V which is probably better to do anyway except for needing to switch between keyboard/mouse. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #211 from vindicator --- Folks, if they want you to create a new report, just do it and link back to this thread stating its long-standing age, along with the associated title "Desktop Icon position gets scrambled sometimes on reboot". (emphasis on "reboot") All parties get what they want. I would disagree that a new report should get created if the title still stands true. If the title is no longer true, then the report is "closed fixed". Having "fixed" ONE cause (where others still may remain), doesn't mean the title is no longer true. Other reports would be considered "duplicate" in my view. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak
https://bugs.kde.org/show_bug.cgi?id=428394 --- Comment #24 from vindicator --- One more correction (I hope), it wasn't vscode, but rather a hidden issue (much like the "SUnreclaim" from long ago)... https://www.reddit.com/r/archlinux/comments/tv9d8j/memory_available_unaccounted_for/ The short of that is "Unevictable" memory climbed (3GB) and wasn't showing associated with any process. When I came across a post about Intel's IGP leak(?), I remembered that issue was brought up regarding "notifications". I restarted the plasmashell service, and Unevictable dropped to 1GB (still way too high, given only konsole was open). I have yet to find out how to associate Unevictable memory with the related process(es), so I would know which one needs to be addressed accordingly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak
https://bugs.kde.org/show_bug.cgi?id=428394 --- Comment #23 from vindicator --- Another correction I guess... Now it's looking like it wasn't plasmashell/wayland. It seems to be visual studio code using the omnisharp extension. Again, the high memory usage just wasn't showing up in htop, so I have to hunt down where it's all going. I had ~600MB left, and after closing it, I has ~1800MB. In htop, that should've shown at the top for sorted memory, and it wasn't. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak
https://bugs.kde.org/show_bug.cgi?id=428394 --- Comment #22 from vindicator --- I guess "correction" for my last reply... I guess it wasn't killed because of memory, because it just happened again and the log showed: * Mar 31 08:24:09 computerName systemd[5495]: Stopped KDE Plasma Workspace. ░░ Subject: A stop job for unit UNIT has finished ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ An ExecStart= process belonging to unit UNIT has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. Mar 31 08:24:08 computerName kded5[6291]: Service "org.kde.StatusNotifierHost-511032" unregistered Mar 31 08:24:08 computerName plasmashell[511032]: The Wayland connection experienced a fatal error: Protocol error Mar 31 08:24:08 computerName plasmashell[511032]: The Wayland connection experienced a fatal error: Protocol error Mar 31 08:24:08 computerName plasmashell[511032]: xdg_wm_base@38: error 3: xdg_surface must not have a buffer at creation Mar 31 08:24:08 computerName kwin_wayland[6261]: QMetaProperty::read: Unable to handle unregistered datatype 'KWin::SessionState' for property 'KWin::EffectsHandlerImpl::sessionState' Mar 31 08:24:08 computerName kwin_wayland_wrapper[6261]: error in client communication (pid 511032) Mar 31 08:23:48 computerName kwin_wayland[6261]: This plugin does not support raise() * -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak
https://bugs.kde.org/show_bug.cgi?id=428394 vindicator changed: What|Removed |Added CC||nroycea+...@gmail.com --- Comment #21 from vindicator --- I am also getting this issue. I switched from x11 a few days ago and was pleased at first that it was now function (the dealbreaker-bugs I mentioned before were no longer an issue). I was noticing some severe memory pressure on my poor little 8GB system, but when looking at the reserved memory in htop, nothing was standing out. For the leak in x11, I set the systemd service for plasmashell to kill itself after a threshold was reached. This was the reason I gave wayland another try. But now it's here as well (in wayland) and even worse because I can't figure out where the memory is actually going. Before plasmashell restarted, I had ~500MB left, and after ~2GB. That kind of discrepancy was not showing in htop. Plasmashell basically holding at ~350MB. I took a look at df for /tmp which uses memory and that was normal (~2%). I also took a look at /proc/meminfo since there was a bug long in the past that was related to SUnreclaim I think, and that also didn't appear to be an issue. So I don't know if anyone has any other suggestions that I may be missing where memory could possibly be disappearing from and how I can find it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423372] Plasmashell Memory Leak
https://bugs.kde.org/show_bug.cgi?id=423372 --- Comment #12 from vindicator --- Created attachment 146252 --> https://bugs.kde.org/attachment.cgi?id=146252=edit heaptrack bottom/up -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423372] Plasmashell Memory Leak
https://bugs.kde.org/show_bug.cgi?id=423372 --- Comment #11 from vindicator --- Created attachment 146251 --> https://bugs.kde.org/attachment.cgi?id=146251=edit heaptrack caller/callee -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423372] Plasmashell Memory Leak
https://bugs.kde.org/show_bug.cgi?id=423372 --- Comment #10 from vindicator --- Created attachment 146250 --> https://bugs.kde.org/attachment.cgi?id=146250=edit htop plasmashell 635MB Name: plasma-workspace Version : 5.23.5-2 < 2 weeks of using heaptrack and plasmashell process climbed pass the 630MB used by heaptrack. Attaching 3 screenshots. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #174 from vindicator --- I think I can alieve you of your "Nvidia" "sneaking suspicion" with comment #7 (https://bugs.kde.org/show_bug.cgi?id=354802#c7), as well as my case being under the use of a very old Haswell IGP. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442844] plasmashell leaks a little bit of memory with every notification displayed (Intel GPU)
https://bugs.kde.org/show_bug.cgi?id=442844 --- Comment #23 from vindicator --- While I do have a few Activities set, I haven't used them in at least a couple of years. Something to take a look at is the memory usage when you do something like "Clear History" for notifications or clipboard. When I cleared my clipboard, plasmashell went from 307MB to 314MB (I had used --replace when plasmashell was >600MB). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442844] plasmashell leaks a little bit of memory with every notification displayed (Intel GPU)
https://bugs.kde.org/show_bug.cgi?id=442844 vindicator changed: What|Removed |Added CC||nroycea+...@gmail.com --- Comment #21 from vindicator --- Created attachment 144331 --> https://bugs.kde.org/attachment.cgi?id=144331=edit heaptrack summary I'm not using wayland and have had this issue for months I'd say. I only just now opted to "heaptrack" it over the past day. (attached screenshot of summary) It's currently consumed ~640MB (uptime ~12 days). I'm not sure how to interpret the output as it looks like the "perceived" leaks seem low. Maybe it just doesn't consider other stuff no longer used/meaningful as still not having yet leaked. I've got a very old Haswell (hurry up and give us an I3 Alder Lake Intel, I'm ready). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444385] Right-click on GTK icon in systray leads to fast random mouse clicks events
https://bugs.kde.org/show_bug.cgi?id=444385 --- Comment #10 from vindicator --- ? I saw no acknowledgement of the issue, including whether or not the suspected commit relates to the bug, and I was lending my experience with the issue AND including log output, whether it affirms the commit or may point elsewhere. I had no idea my submission would be a hindrance. Carry-on and ignore if you already know what's up. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444385] Right-click on GTK icon in systray leads to fast random mouse clicks events
https://bugs.kde.org/show_bug.cgi?id=444385 --- Comment #8 from vindicator --- /home/userName/.config/plasma-org.kde.plasma.desktop-appletsrc * [Containments][2][Applets][175][Configuration] localPath=/home/username/.local/share/plasma_icons/systemsettings (75).desktop url=file:///usr/share/applications/systemsettings.desktop * 75 instances? Yeah, no way would I have enjoyed manually clicking/removing them one-by-one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444385] Right-click on GTK icon in systray leads to fast random mouse clicks events
https://bugs.kde.org/show_bug.cgi?id=444385 vindicator changed: What|Removed |Added CC||nroycea+...@gmail.com --- Comment #7 from vindicator --- Created attachment 142947 --> https://bugs.kde.org/attachment.cgi?id=142947=edit Errant Mouse After Tray Click OH MY GOD! This is BY FAR the MOST egregious bug I've encountered with KDE... and that's so far beyond the "desktop icon scrambling" bug or the wayland issues, and it MUST get the highest priority nate/david/feck/whomever! I just now encountered this issue, and I had just upgraded my system last night, since my previous upgrade was on the 13th. I was composing an email reply in my browser and went to open up skype in the system tray and EVERYTHING went haywire. I had no control over "context menu" actions that were being taken. The browser brought up developer-tools. I figured it may be related to the compositor since dropping x-render happened, but on the other hand I don't see how since compositing and actions shouldn't be related. But still, I went to bring up settings and that too went haywire and the entire task tray started filling up. I had to switch to another tty since I couldn't stop any of it. I killed plasmashell, and I think that did it, but the damage was done, as shown in the attached image. I had already started removing a lot of those extra "settings" in the bar, but doesn't look like I made a dent, so I'm going to look for whatever file is in charge of the layout and manually clean it up there since that should be faster. In the journal, when it all went wrong (start at the bottom): * ...//More spam. Essentially 4-5 minutes of ungodly stress. Oct 27 11:13:05 computerName kwin_x11[1416]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 22988, resource id: 25168137, major code: 18 (ChangeProperty), minor code: 0 Oct 27 11:13:05 computerName kwin_x11[1416]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 22984, resource id: 25168136, major code: 18 (ChangeProperty), minor code: 0 ...//"Too many open files" you say? No /s Oct 27 11:12:17 computerName plasmashell[1499]: QProcessPrivate::createPipe: Cannot create pipe 0x5608cbbdb9b8 (Too many open files) Oct 27 11:12:17 computerName plasmashell[1499]: QProcessPrivate::createPipe: Cannot create pipe 0x5608c7f26fa8 (Too many open files) Oct 27 11:12:17 computerName plasmashell[1499]: Opening menu at 40 43 Oct 27 11:12:17 computerName plasmashell[1499]: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/KickoffItemDelegate.qml:140:9: QML IconItem: grabToImage: item's window is not visible Oct 27 11:12:17 computerName plasmashell[1499]: Opening menu at 40 42 ...//More spamming. Oct 27 11:12:00 computerName systemd[1383]: Started System Settings. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 820. ... Oct 27 11:11:20 computerName plasmashell[1499]: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/KickoffItemDelegate.qml:140:9: QML IconItem: grabToImage: item's window is not visible Oct 27 11:11:20 computerName plasmashell[1499]: Opening menu at 40 44 Oct 27 11:11:20 computerName plasmashell[1499]: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/KickoffItemDelegate.qml:140:9: QML IconItem: grabToImage: item's window is not visible ...//Also being spammed Oct 27 11:10:57 computerName plasmashell[1499]: Opening menu at 69 62 Oct 27 11:10:57 computerName plasmashell[1499]: Opening menu at 80 66 Oct 27 11:10:57 computerName plasmashell[1499]: Opening menu at 80 66 Oct 27 11:10:57 computerName plasmashell[1499]: Opening menu at 88 67 ...//HA! Yeah, make that thousands (lines 12304->47723). Oct 27 11:09:05 computerName kwin_x11[1416]: kwin_core: XCB error: 3 (BadWindow), sequence: 20823, resource id: 60817682, major code: 129 (SHAPE), minor code: 6 (Input) Oct 27 11:09:05 computerName kwin_x11[1416]: kwin_core: XCB error: 152 (BadDamage), sequence: 20822, resource id: 15787929, major code: 143 (DAMAGE), minor code: 2 (Destroy) Oct 27 11:08:49 computerName kwin_x11[1416]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 226, resource id: 60817649, major code: 14 (GetGeometry), minor code: 0 Oct 27 11:09:40 computerName plasmashell[45590]: [45638:45661:1027/110928.838481:ERROR:latency_info.cc(112)] CompositorFrameSinkSupport::MaybeSubmitCompositorFrame, LatencyInfo vector size 704 is too big. Oct 27 11:09:40 computerName plasmashell[45590]: [45638:45661:1027/110919.123894:ERROR:latency_info.cc(112)] CompositorFrameSinkSupport::MaybeSubmitCompositorFrame, LatencyInfo vector siz
[systemsettings] [Bug 443086] Add software rendering toggle for OpenGL backends
https://bugs.kde.org/show_bug.cgi?id=443086 vindicator changed: What|Removed |Added CC||nroycea+...@gmail.com --- Comment #1 from vindicator --- OH! This should be good (not). Much like how I refuse to install Wayland given amount and kind of bugs I've encountered, so too do I hate that xrender was removed. My most notable issue with OpenGl was when viewing videos in the browser or Kodi, at some random point in time (doesn't even have to be in that viewing session), rendering would get all borked. The audio would still play, but the video would freeze and may get some partial renders when moving my mouse or switching/moving windows. The only "fix" would be to switch rendering version (going back and forth between 2.0/3.1. Yeah, I'm definitely going to hate this and can't wait for Alder Lake to come out so I can upgrade to that (from Haswell) and this won't be an issue any longer... "hopefully". I'm quite certain I posted about this before, though don't see it in my bug post list. Maybe it didn't come with my email address change or something. Or maybe I hopped on someone else's post regarding my rendering issue. And yes, I've toyed with the X driver settings. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433260] Tabbing to select power/session item and pressing Enter/Return opens the selected/hovered item in the main view instead of doing nothing
https://bugs.kde.org/show_bug.cgi?id=433260 --- Comment #10 from vindicator --- Wwww! I'm mind-blown. I'm no meager/newb user either and never knew that. I just looked into it a TINY bit and came across: https://stackoverflow.com/a/16090932 I'm trying to think of what I can do (besides... OH! okay, I just tried this on this issue and it still didn't work.) 1. Press the Window key 2. Press the space bar key What happened: The space bar action was injected in the filter. What should have happened: The space bar action should have "clicked" (mouse press down and up) the selected item which would be the first favorite item. You could also press the right-arrow after step 1 to make sure the next favorite item is highlighted. The enter key, instead of doing nothing, would change the "highlighted" look to a "selected" look for the highlighted item. Once every item desired is selected, then the spacebar "clicks" all selected items (unless the last highlighted item is not selected, in which case, only that highlighted item is "clicked"). If you want to type (spacebar) in the filter, you'd need to tab/arrow to it first. I'd love to find some program/window or site (probably not "site" since that would be dependent on the browser complying with the system rules) that would definitively show the effects of these actions. As low-priority, it may be helpful in the keyboard settings to have a section where these things could be learned/tried-out. The mouse section could have an image of a mouse where the button actions are highlighted in the image when pressed/released. Not sure how that would pan out with the various types of mice buttons and their locations. Of course, it may just be easier to have a "help" link in those sections that explains these very basic (even though I didn't even know it) functions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433260] Tabbing to select power/session item and pressing Enter/Return opens the selected/hovered item in the main view instead of doing nothing
https://bugs.kde.org/show_bug.cgi?id=433260 --- Comment #8 from vindicator --- ? I would think that tabbing through various areas would automatically give that area focus. It is my contention that if an item is highlighted, it is selected, and as such, the activation SHOULD be the Enter key. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433248] Notifications spike the CPU - Part Deux
https://bugs.kde.org/show_bug.cgi?id=433248 vindicator changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #3 from vindicator --- Nope, an old Haswell IGP. I'll close this since I don't think I've encountered it since then. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 436923] I can't open some kinds of file types like: .AppImage and .run and I get the error
https://bugs.kde.org/show_bug.cgi?id=436923 vindicator changed: What|Removed |Added CC||nroycea+...@gmail.com --- Comment #5 from vindicator --- I encountered this issue as well when trying to open an executable in Dolphin on Archlinux. It runs when launched from the terminal Plasma: 5.21.5 Frameworks: 5.82.0 QT: 5.15.2 Dolphin: 21.04.1 Package: https://www.falstad.com/circuit/offline/ ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=23b129eee7f7751b48599b793e9e312d485e3e75, stripped It looks like it runs an instance of chrome(/electron?). Just launch "circuitjs1". -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 436020] File Association Isn't Respected
https://bugs.kde.org/show_bug.cgi?id=436020 --- Comment #4 from vindicator --- I'm familiar with race conditions. However it doesn't explain how it happened to begin with when chrome was NEVER in the list (kate, librewriter, notepad) from the start, until I added it to test if adding then removing it would make a difference. Besides, I would figure race conditions are typically quick, like in ms, or however long it takes for a thread to release hold of whatever it's got locked. Not something that wouldn't go on for an hour, or need multiple hours to release. Not a huge deal or anything. Just an annoyance (just select open-with for the file to force it). Should it happen again, I hope to remember to start up a video capture for evidence. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 436020] File Association Isn't Respected
https://bugs.kde.org/show_bug.cgi?id=436020 vindicator changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from vindicator --- Wow, okay, I have no idea what is going on, but I was setting things up so I could record a video for it, and I tested it again without making any changes, but only double-clicking on the readme file, and it opened in kate. I also went back to the original activity I was working in, and it opened fine there as well. I also removed the Chrome entry in file-association properties, and it also opened in kate with no issues. No clue what happened there. I had been changing the file-association properties in dolphin (right-mouse->properties->general->file-type-options). Again, nothing changed, as I was still in that same session as yesterday (no reboot, no logout, no closing of kate/chrome/dolphin, ...). I just woke up, saw your email, switched to another activity which was blank so I could record the process I did, tried clicking the file, and it opened just fine in kate. Bizarre. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436020] New: File Association Isn't Respected
https://bugs.kde.org/show_bug.cgi?id=436020 Bug ID: 436020 Summary: File Association Isn't Respected Product: plasmashell Version: 5.21.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: nroycea+...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY A markdown file associated with Kate, was opened using Chrome STEPS TO REPRODUCE 1. Double click on the markdown file (README.md) in dolphin. 2. Watch it open in Chrome 3. Change file association property, adding chrome to the list, but dropping it to the bottom. 4. Double click on the file again. OBSERVED RESULT Markdown file ALWAYS opens in the browser. EXPECTED RESULT Markdown file should open using the application it is associated with. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION * Apr 21 15:35:31 userName systemd[1208]: Started Google Chrome - Web Browser. Apr 21 15:35:32 userName plasmashell[310966]: Opening in existing browser session. * -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435399] plasmashell: Fontconfig error: Cannot load default config file: No such file: (null)
https://bugs.kde.org/show_bug.cgi?id=435399 --- Comment #4 from vindicator --- I get that, but can you tell me if it's "plasmashell" that is looking for a "default config file"? I'm going with the thought there is a kde/plasmashell config setting containing a key/name/variable that is currently empty or non-existent meant to be passed to fontconfig to do whatever magic it does. (eg. "~/.config/plasmashell_primary.config" containing/expecting "Fontconfig="). The reason this "bug" is open is because the error doesn't give me enough to go on to fix the issue because I don't know where to look. I see "plasmashell" making me think plasmashell looked up something it was expecting, which then passes it on to fontconfig a value that is "null". I guess a better/real example would be "plasmashellrc". That contains "[KTextEditor Renderer]" which contains "Font=". If it just contained "Font=" or that key didn't exist, THEN I'd expect this type of error. But I'd also expect the error would tell me it was related to "[KTextEditor Renderer]" in "plasmashellrc". That would be descriptive enough for me to act on. Maybe this is something I should be tossing to the "fontconfig" folks, but I'm thinking this is the right place. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435399] plasmashell: Fontconfig error: Cannot load default config file: No such file: (null)
https://bugs.kde.org/show_bug.cgi?id=435399 --- Comment #2 from vindicator --- It was just the journal. Is there any other place that plasmashell may log to with more detail? Full disclosure, I had to rebuild my os partition because of a previous catastrophic failure to that partition, so I started over from scratch EXCEPT for my /home which was safe on a different drive. Also, when rebuilding, I got more selective with what I installed rather than just the entire "plasma" group, I'd narrow down to what was required (like plasma-desktop) and then added what was then needed for things that were not functioning like widgets needed ksysguard installed. Otherwise they were just blank. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435399] New: plasmashell: Fontconfig error: Cannot load default config file: No such file: (null)
https://bugs.kde.org/show_bug.cgi?id=435399 Bug ID: 435399 Summary: plasmashell: Fontconfig error: Cannot load default config file: No such file: (null) Product: plasmashell Version: 5.21.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: nroycea+...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Title is the summary of what was found in the journal. STEPS TO REPRODUCE 1. Run KDE 2. Do stuff. No really, I have no clue what I'm doing that is causing the log entry. OBSERVED RESULT What's in the title EXPECTED RESULT Load the default config? Or at least tell me what config is trying to be loaded, but isn't there. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION $ fc-cache -v * ... fc-cache: succeeded * I had even looked at the /etc conf stuff and noticed the "deprecated" parts for 50-user, which I corrected for my account. There is no visual issue as far as I can tell, only an error log entry that I want to be able to correct. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435093] New: "/etc/sddm.conf.d" isn't considered
https://bugs.kde.org/show_bug.cgi?id=435093 Bug ID: 435093 Summary: "/etc/sddm.conf.d" isn't considered Product: systemsettings Version: 5.21.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_sddm Assignee: k...@davidedmundson.co.uk Reporter: nroycea+...@gmail.com CC: k...@david-redondo.de, plasma-b...@kde.org Target Milestone: --- SUMMARY sddm doesn't look in "/etc/sddm.conf.d" for .conf files. STEPS TO REPRODUCE 1. Copy /usr/lib/sddm/sddm.conf.d/default.conf into /etc/sddm.conf.d/ 2. Make a change you'll be able to recognize (eg. theme) 3. Restart sddm OBSERVED RESULT The change in the .conf will not be reflected in sddm. EXPECTED RESULT sddm will look in /etc/sddm.conf.d/ and load any configuration in there. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION man sddm.conf.5 mentions the search order for configuration files as: 1) /usr/lib/sddm/sddm.conf.d 2) /etc/sddm.conf.d 3) /etc/sddm.conf #2 is ignored. If I take that same changed conf from #2 and put that in #3 (where #3 didn't exist previously), it will load it then. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 430862] Kde5init crashes in ThumbnailProtocol::get() every time I take a screenshot or start the computer
https://bugs.kde.org/show_bug.cgi?id=430862 --- Comment #19 from vindicator --- I'm curious why the other posts (specifically older) "has been marked as a duplicate of this bug" I'd think the OG (first) post would be left alone and all of the others would've been considered duplicates. If you have an orange and put it in a replicator, the new orange is the duplicate, not the original orange. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434311] Edited Favorite Menu Item Doesn't Reflect The Change
https://bugs.kde.org/show_bug.cgi?id=434311 --- Comment #1 from vindicator --- I should add that the "command" change IS reflected in the sense that if you go back to that field in "properties", it'll show the change, but it is still launched with the previous command. Just not sure how best to title it accurately. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434311] New: Edited Favorite Menu Item Doesn't Reflect The Change
https://bugs.kde.org/show_bug.cgi?id=434311 Bug ID: 434311 Summary: Edited Favorite Menu Item Doesn't Reflect The Change Product: plasmashell Version: 5.21.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: nroycea+...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Add a menu program item as a favorite. 2. Edit the "favorite" item properties. Application->Command (to some other program or even something that doesn't exist). Save it (ok). 3. Launch that edited favorite. OBSERVED RESULT "Favorite" program launched using the previous command. EXPECTED RESULT "Favorite" program should be launched with the new edited command. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I encountered this when launching a script in the "command" field. It was a script which added "nice" and "ionice" but is no longer needed since the previous bug I reported was fixed. I changed that "command" field to the correct/original program/script and removed the old/unneeded script. journalctl showed that when I launched the "favorite" program, it was still looking for the script that was removed/deleted. But when I go to the program in the menu (either typed or in All Programs), the correct program is launched. After removing the program from "Favorites" and adding it back, it launched using the correct "command". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431446] Blinking panels and window contents not refreshing
https://bugs.kde.org/show_bug.cgi?id=431446 --- Comment #13 from vindicator --- I can say that after I removed the xf86-video-intel at the end of last month, things have been "ok" for me so far. I won't say it's "great", since I'll get some stuttering rendering issues sometimes when I hover over Kodi just so I can watch video in a small thumbnail view (whatever you'd want to call it), rather than a large window when I'm working on things. It only happens for that small video thumbnail though. But at least the rendering issue I had before hasn't happened since. I also stuck with xrender compositing rather than opengl solely because the cpu usage is higher, even when idle for opengl. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 430934] Nice/Ionice Not Being Honored In .desktop Exec
https://bugs.kde.org/show_bug.cgi?id=430934 vindicator changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from vindicator --- I dunno, but it looks fixed to me (kio 5.79.0-1) even though there's no other comments for this, so I'll just close it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431446] Blinking panels and window contents not refreshing
https://bugs.kde.org/show_bug.cgi?id=431446 --- Comment #11 from vindicator --- Nope. KWIN_USE_BUFFER_AGE=0 didn't make any difference. I'm still in a flickering environment and can only see any updates in this browser tab if I max/restore this window. * $ KWIN_USE_BUFFER_AGE=0 kwin_x11 --replace & [1] 141797 kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5079:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5081:48: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5083:48: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5087:47: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5089:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5097:48: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5101:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5103:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5107:45: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5110:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: Couldn't process include statement for 'us(\0)' kwin_xkbcommon: XKB: Abandoning symbols file "(unnamed)" kwin_xkbcommon: XKB: Failed to compile xkb_symbols kwin_xkbcommon: XKB: Failed to compile keymap kwin_core: XCB error: 10 (BadAccess), sequence: 2833, resource id: 308, major code: 142 (Composite), minor code: 2 (RedirectSubwindows) * * [ 69857.600] (II) intel(0): Modeline "1400x1050"x0.0 101.00 1400 1448 1480 1560 1050 1053 1057 1080 +hsync -vsync (64.7 kHz e) [ 70761.139] (EE) event3 - AT Translated Set 2 keyboard: client bug: event processing lagging behind by 23ms, your system is too slow [ 72240.460] (EE) intel(0): Failed to submit rendering commands (Bad address), disabling acceleration. [ 72385.800] (EE) event4 - Logitech M510: client bug: event processing lagging behind by 22ms, your system is too slow [ 72389.905] (EE) event4 - Logitech M510: client bug: event processing lagging behind by 15ms, your system is too slow [ 72566.569] (EE) event4 - Logitech M510: client bug: event processing lagging behind by 24ms, your system is too slow * With that "intel" error again, something is most definitely up with the driver I think. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431446] Blinking panels and window contents not refreshing
https://bugs.kde.org/show_bug.cgi?id=431446
vindicator changed:
What|Removed |Added
CC||nroycea+...@gmail.com
--- Comment #10 from vindicator ---
I think I have this issue as well, but I'm on 5.21.0.
I don't think I've experienced this "level" of an issue before and this is the
first time it's happened since I updated this past weekend.
My "normal" rendering issue comes from when I have "OpenGL" set as the
compositor.
Not immediately, but over time, I'll encounter rendering issues with video
playback that stutters/jitters/skips.
My "workaround" is simply to use "XRender" which is what I had done previously
(and it is still using xrender).
I'll also put out that that simply switching between OpenGL versions in the
compositor list sets things back on track... for awhile.
I am using X11. (I've learned my lesson with Wayland)
You stated that "restarting plasmashell" ("--replace"?) fixed it for you, but
not for me.
I also did a "replace" for kwin, but still no success.
While konsole rendered keystrokes just fine, no such luck with typing in Chrome
address bar.
One abnormal oddity that was probably leading up to the breakage (or letting me
know something was amiss before it all broke down) was while watching recorded
tv in kodi, there was some small/minor skippage (even though I was still using
xrender).
The only action I could take was CTRL-ALT-DEL my way to "logout".
Xorg:
"[ 68637.069] (EE) intel(0): Failed to submit rendering commands (Bad address),
disabling acceleration."
I don't know what time that was in relation to uptime.
Journalctl: (time which the clock stopped rendering was 09:07:##)
*
Feb 23 09:08:46 computerName plasmashell[1441]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:464:
TypeError: Cannot read property 'length' of undefined
Feb 23 09:07:57 computerName kwin_x11[1404]: qt.qpa.xcb: QXcbConnection: XCB
error: 9 (BadDrawable), sequence: 63014, resource id: 15333177, major code: 14
(GetGeometry), minor code: 0
Feb 23 09:07:57 computerName kwin_x11[1404]: qt.qpa.xcb: QXcbConnection: XCB
error: 3 (BadWindow), sequence: 63013, resource id: 15333177, major code: 3
(GetWindowAttributes), minor code: 0
Feb 23 09:07:55 computerName kwin_x11[1404]: qt.qpa.xcb: QXcbConnection: XCB
error: 9 (BadDrawable), sequence: 62514, resource id: 15333173, major code: 14
(GetGeometry), minor code: 0
Feb 23 09:07:55 computerName kwin_x11[1404]: qt.qpa.xcb: QXcbConnection: XCB
error: 3 (BadWindow), sequence: 62513, resource id: 15333173, major code: 3
(GetWindowAttributes), minor code: 0
Feb 23 09:05:06 computerName plasmashell[1441]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15:
QML QQuickItem: Binding loop detected for property "height"
*
If it happens again, THEN I'll give "KWIN_USE_BUFFER_AGE=0" a try. This may
just be a one-off for me.
I don't know if you'll still see this, but it just happened while I went to
another tab to look at other bugs. I'm going to try to save this.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 433260] New: Tabbing To Select Item (Restart) And Pressing Return Causes Settings To Open
https://bugs.kde.org/show_bug.cgi?id=433260 Bug ID: 433260 Summary: Tabbing To Select Item (Restart) And Pressing Return Causes Settings To Open Product: plasmashell Version: 5.21.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: nroycea+...@gmail.com CC: mvourla...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Using keyboard to get the system to restart via the menu doesn't work. STEPS TO REPRODUCE 1. Press the "Windows" key on your keyboard 2. Tab forward/reverse to Restart button 3. Press Enter OBSERVED RESULT Settings window opens. EXPECTED RESULT System restarts. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I don't think it actually causes the Settings window to open, but rather whatever was previously highlighted. In my case, if I were to perform the steps above using the forward tab, the "Systems Settings" is highlighted, even while I'm still tabbing through the other options which also visually show they are being tabbed to. However if I reverse tab to get to "Restart", nothing happens. I also just noticed that "System Settings" was also still highlight in this case, so I don't know what's up with that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433063] Network Speed widget is not working
https://bugs.kde.org/show_bug.cgi?id=433063 vindicator changed: What|Removed |Added CC|nroycea+...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433248] New: Notifications spike the CPU - Part Deux
https://bugs.kde.org/show_bug.cgi?id=433248 Bug ID: 433248 Summary: Notifications spike the CPU - Part Deux Product: plasmashell Version: 5.21.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: nroycea+...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY https://bugs.kde.org/show_bug.cgi?id=423594 looks to be back. I just encountered it about 1 hour after upgrading to 5.21. STEPS TO REPRODUCE 1. Get Chrome "Canvas Blocker" extension to pop up a few or more notifications. OBSERVED RESULT The subtle countdown/close indicator in the notification freezes and I hear my cpu fan roaring (although I'm compiling kodi and the kernel at the same time). htop shows plasmashell peaking the cpu. I also couldn't "--replace" plasmashell. I had to kill it. EXPECTED RESULT Just show the notification and don't hang (but still be cool). SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION It is by no means a frequent issue, and I get a ton of notifications (mostly the canvas blocker, and only 3 this time). This could very well be the only other time I've encountered it since I posted about it in the previous report. Nonetheless, the backtrace: #0 0x7661390589ba in __futex_abstimed_wait_common64 () at /usr/lib/libpthread.so.0 #1 0x766139052260 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #2 0x76613a01c0c4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #3 0x76613bc5c137 in () at /usr/lib/libQt5Quick.so.5 #4 0x76613bcc5b87 in QQuickWindow::event(QEvent*) () at /usr/lib/libQt5Quick.so.5 #5 0x76613ae9c752 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #6 0x76613a1fda2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #7 0x76613a5c6319 in QPlatformWindow::windowEvent(QEvent*) () at /usr/lib/libQt5Gui.so.5 #8 0x76613aea3437 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #9 0x76613a1fda2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #10 0x76613a255a15 in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #11 0x76613a2562fa in () at /usr/lib/libQt5Core.so.5 #12 0x7661385dfb84 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #13 0x766138633c21 in () at /usr/lib/libglib-2.0.so.0 #14 0x7661385de3b1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #15 0x76613a256691 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #16 0x76613a1fc3ac in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #17 0x76613a204844 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #18 0x5e7727121069 in () #19 0x766139bc3b25 in __libc_start_main () at /usr/lib/libc.so.6 #20 0x5e77271212ae in () -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992 vindicator changed: What|Removed |Added CC|nroycea+...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430636] Remember Plasma/Wayland Setting For Login
https://bugs.kde.org/show_bug.cgi?id=430636 --- Comment #2 from vindicator --- I just tossed Wayland altogether so I don't have to deal with it. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 414553] Crash From New Images On Desktop Or Dolphin - kdeinit5, kio/thumbnail.so
https://bugs.kde.org/show_bug.cgi?id=414553 --- Comment #10 from vindicator --- Backtrace for process: "file.so [kdeinit5] file local:/run/user//klauncherMMDZXa.1.slave-socket local:/run/user//dolphinoTcyBm.718.slave-socket" * #0 0x72e894e1e50f in ppoll () from /usr/lib/libc.so.6 #1 0x72e8951fc64b in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/libQt5Core.so.5 #2 0x72e891390813 in ?? () from /usr/lib/libQt5Network.so.5 #3 0x72e89138e1f2 in ?? () from /usr/lib/libQt5Network.so.5 #4 0x72e8913811a2 in QAbstractSocket::waitForReadyRead(int) () from /usr/lib/libQt5Network.so.5 #5 0x72e891502442 in ?? () from /usr/lib/libKF5KIOCore.so.5 #6 0x72e89153f798 in KIO::SlaveBase::dispatchLoop() () from /usr/lib/libKF5KIOCore.so.5 #7 0x72e895d5a388 in kdemain () from /usr/lib/qt/plugins/kf5/kio/file.so #8 0x6071f1fd35bd in ?? () #9 0x6071f1fd4a59 in ?? () #10 0x6071f1fd5237 in ?? () #11 0x6071f1fd0b54 in ?? () #12 0x72e894d51152 in __libc_start_main () from /usr/lib/libc.so.6 #13 0x6071f1fd16be in ?? () * This process ended up disappearing. There were 4 dolphin related processes for file.so. Now there is just 1. backtrace for process: "file.so [kdeinit5] file local:/run/user//klauncherCNHsFj.1.slave-socket local:/run/user//kded5NqjChC.1.slave-socket" * #0 0x72e894e1e50f in ppoll () from /usr/lib/libc.so.6 #1 0x72e8951fc64b in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/libQt5Core.so.5 #2 0x72e891390813 in ?? () from /usr/lib/libQt5Network.so.5 #3 0x72e89138e1f2 in ?? () from /usr/lib/libQt5Network.so.5 #4 0x72e8913811a2 in QAbstractSocket::waitForReadyRead(int) () from /usr/lib/libQt5Network.so.5 #5 0x72e891502442 in ?? () from /usr/lib/libKF5KIOCore.so.5 #6 0x72e89153f798 in KIO::SlaveBase::dispatchLoop() () from /usr/lib/libKF5KIOCore.so.5 #7 0x72e895d5a388 in kdemain () from /usr/lib/qt/plugins/kf5/kio/file.so #8 0x6071f1fd35bd in ?? () #9 0x6071f1fd4a59 in ?? () #10 0x6071f1fd5237 in ?? () #11 0x6071f1fd0b54 in ?? () #12 0x72e894d51152 in __libc_start_main () from /usr/lib/libc.so.6 #13 0x6071f1fd16be in ?? () * There are 2 processes of this type. There were 2 instances of plasmashell related to file.so (plasmashelluXvTgd.328.slave-socket), but they all went away. The constant that remains are the kded ones. Unchanging pids. Okay, using coredumpctl info, I see that the dumps are for the plasmashell and dolphin related file.so stuff. I don't know if there's an effective way of finding if the kded related ones are in there as well (there are A LOT). First test was to kill the latest kded related file.so (pid 1908). No effect, still crashes. Then the other kded one (1907). Also still crashes. Next, I killed each of the only other file.so stuff that were related to dolphin (kded ones were recreated). Still crashed on the dolphin instance was recreated. Next, with this 2 recreated kded instances, I closed Dolphin and waited until there were no other file.so instances. After re-opening dolphin and going to a folder with new pictures, there are more coredumps. This kind of coredump is at least quick, where I don't even notice a slowed system as it's being dumped. With dolphin closed, I killall for the remaining kded file.so instances. Now that there are no file.so instances, I open dolphin, go to the folder and it still crashes (odd). Okay, close dolphin, killall file.so, suicide kdeinit5, file.so sockets are recreated, open dolphin, go to folder... SUCCESS. Reminder to self, in next 10+ days when it starts crashing again, close dolphin, suicide kdeinit5, make sure no other file.so instances exist, open dolphin and check folder. Apparently just killing the file.so instances were not enough, kdeinit5 also has to be suicided. Backtrace doesn't look any different when it's working (kde file.so): * #0 0x72e894e1e50f in ppoll () from /usr/lib/libc.so.6 #1 0x72e8951fc64b in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/libQt5Core.so.5 #2 0x72e891390813 in ?? () from /usr/lib/libQt5Network.so.5 #3 0x72e89138e1f2 in ?? () from /usr/lib/libQt5Network.so.5 #4 0x72e8913811a2 in QAbstractSocket::waitForReadyRead(int) () from /usr/lib/libQt5Network.so.5 #5 0x72e891502442 in ?? () from /usr/lib/libKF5KIOCore.so.5 #6 0x72e89153f798 in KIO::SlaveBase::dispatchLoop() () from /usr/lib/libKF5KIOCore.so.5 #7 0x72e895d5a388 in kdemain () from /usr/lib/qt/plugins/kf5/kio/file.so #8 0x6071f1fd35bd in ?? () #9 0x6071f1fd4a59 in ?? () #10 0x6071f1fd5237 in ?? () #11 0x6071f1fd0b54 in ?? () #12 0x72e894d51152 in __libc_start_main () from /usr/lib/libc.so.6 #13 0x6071f1fd16be in ?? () * -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430934] Nice/Ionice Not Being Honored In .desktop Exec
https://bugs.kde.org/show_bug.cgi?id=430934 --- Comment #1 from vindicator --- Oh, and in case you're wondering the "why" behind doing it like that, the child process cpptools for the c++ extension plays havoc with the usability of my system. Yes, I also about the c++ setting for the extension related to it's niceness. Also, even with everything set to low/idle, usability can still be tough with up to 10 seconds delay with actions like even just typing this message, I can type a full sentence before it shows up. It's surely related to I/O and not cpu as I'm watching htop at the same time and cpu usage is very low, but my mechanical drive is thrashing. And I have plenty of free memory. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430934] New: Nice/Ionice Not Being Honored In .desktop Exec
https://bugs.kde.org/show_bug.cgi?id=430934 Bug ID: 430934 Summary: Nice/Ionice Not Being Honored In .desktop Exec Product: plasmashell Version: 5.20.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: nroycea+...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Niceness of a running application launched from the Application Launcher is not being applied. STEPS TO REPRODUCE 1. Right-mouse application in Application Launcher and "Edit application" 2. Go to application tab and prepend "Command" with "nice" and "ionice" values (-n 15 & -c 3). Save. 3. Run that application from the launcher. OBSERVED RESULT The niceness for the process is the default. EXPECTED RESULT The niceness should reflect what was stated in the command. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION If you copy/paste that niced command in the terminal and then look at the niceness of the running process, that will show the change. Yet the same command used in the Launcher will not. EG. Exec(comment)= nice -n 15 ionice -c 3 /code-insiders (visual studio code/vscode) If you iotop to view that process PRIO, when it was run by the Launcher, you'll see it is the default "be/4", which is incorrect. But if you run that same command in the terminal and view the iotop for that process, it shows "idle", which would be correct. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430636] New: Remember Plasma/Wayland Setting For Login
https://bugs.kde.org/show_bug.cgi?id=430636 Bug ID: 430636 Summary: Remember Plasma/Wayland Setting For Login Product: systemsettings Version: 5.20.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_sddm Assignee: k...@davidedmundson.co.uk Reporter: nroycea+...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY SDDM login dropdown list for Plasma/Wayland defaults to Wayland every time. STEPS TO REPRODUCE 1. Boot device 2. Look at dropdown list in SDDM/login at top-left 3. Select regular "Plasma" (X11) and log in. 4. Reboot/logout to get back to SDDM/login. OBSERVED RESULT Wayland option is selected instead of your last X11-based choice. EXPECTED RESULT The last choice should be remembered. Wayland should NOT be default to begin with. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION https://fedoraproject.org/wiki/Changes/WaylandByDefaultForPlasma I saw it stated in here that Wayland is now set as the default option with 5.20+. In my view that is a HUGE mistake. Based on my own experience (https://bugs.kde.org/show_bug.cgi?id=429967), Wayland is NOT ready to be set as default. I have NO intention of ever using it in its current state. I've tried it maybe once a year for a few years and I have not seen it progress at all in terms of usability. The ONLY reason I created that earlier bug was because I had NO idea I was using the Wayland environment because I never had to make that choice before in the past. Now I have to make regular Plasma/X11 choice EVERY time I need to log in. If you're going to insist on Wayland being the default option, then you must set that field as a remembered property so when the regular X11 Plasma option is selected, it doesn't have to be selected again with any subsequent login. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 414553] Crash From New Images On Desktop Or Dolphin - kdeinit5, kio/thumbnail.so
https://bugs.kde.org/show_bug.cgi?id=414553 --- Comment #9 from vindicator --- Testing this further (instead of just rebooting), I found that killing the kdeinit5 threads "file.so", sets things back the way it should (no crashes, thumbnails are generated). I first suicided kdeinit5. Then ps showed the previous, along with new instances existed as well as the "file.so" threads: * $ ps -ef |grep kdeini userName 1298 1 0 Dec03 ?00:00:00 /usr/lib/kf5/start_kdeinit userName 1300 1 0 Dec03 ?00:00:01 kdeinit5: Running... userName 709781300 0 Dec03 ?00:00:40 kcalc [kdeinit5] userName17216491300 0 19:55 ?00:00:00 file.so [kdeinit5] file local:/run/user//klauncherknWPUc.1.slave-socket local:/run/user//kded5iOYDAY.1.slave-socket userName17216501300 0 19:55 ?00:00:00 file.so [kdeinit5] file local:/run/user//klauncherknWPUc.1.slave-socket local:/run/user//kded5mmOANs.2.slave-socket userName1721652 1 0 19:55 ?00:00:00 kdeinit5: Running... * It was only after killing those 2 sockets did the crashes stop and thumbnails start generating again. Nothing else I provided told you enough. Hopefully this does something. I at least now know what I can do instead of rebooting. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 429956] Widget Tooltip Text Missing Under Oxygen Theme
https://bugs.kde.org/show_bug.cgi?id=429956 vindicator changed: What|Removed |Added Attachment #133859|0 |1 is obsolete|| --- Comment #5 from vindicator --- Created attachment 133860 --> https://bugs.kde.org/attachment.cgi?id=133860=edit Corrected Screenshot "Correct Tooltip (applet?)" - Quality -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 429956] Widget Tooltip Text Missing Under Oxygen Theme
https://bugs.kde.org/show_bug.cgi?id=429956 --- Comment #4 from vindicator --- Created attachment 133859 --> https://bugs.kde.org/attachment.cgi?id=133859=edit Correct Tooltip (applet?) Not sure about the "network applet", but tooltips are typically shown correctly like this. The tooltip for the "All widgets" filter also displayed the text correctly. And in case you're wondering, it isn't about it being "network" (I doubt you'd think that). All of the widgets I use exhibit the same behavior (likely because they all share the same "menu" system). -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 429956] Widget Tooltip Text Missing Under Oxygen Theme
https://bugs.kde.org/show_bug.cgi?id=429956 --- Comment #2 from vindicator --- Created attachment 133858 --> https://bugs.kde.org/attachment.cgi?id=133858=edit Widget Tooltip Without Text -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429967] Massive Rendering Issues
https://bugs.kde.org/show_bug.cgi?id=429967 --- Comment #2 from vindicator --- Yeah, it was wayland. For whatever reason that was the default at login. It is not something I chose. I logged out, switched to "regular" Plasma, but logging back in was taking awhile so I opened another tty and just rebooted (saw a coredump was happening on reboot). When it got back to sddm, wayland was still the default (don't know if it will always be that way now or "regular" didn't set/commit because login didn't complete. I don't know if this should just be closed or moved to a wayland-related "product". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429967] Massive Rendering Issues
https://bugs.kde.org/show_bug.cgi?id=429967 --- Comment #1 from vindicator --- I think it may be wayland. I'm looking into it. Not sure if that's something new that KDE now loads into it automatically. Wayland has always been horrible for me and I avoid it like the plague. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429967] New: Massive Rendering Issues
https://bugs.kde.org/show_bug.cgi?id=429967 Bug ID: 429967 Summary: Massive Rendering Issues Product: plasmashell Version: 5.20.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: nroycea+...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 133831 --> https://bugs.kde.org/attachment.cgi?id=133831=edit Gwenview transparency SUMMARY I'm not even sure where to post this, but I'm having major GUI issues with this update (Previous update on 2020-10-25) STEPS TO REPRODUCE 1. Update Arch Linux 2. Open an image in gwenview OBSERVED RESULT No image is displayed, but rather the viewbox for the image is transparent. EXPECTED RESULT Display the image SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This isn't just about gwenview. My first encounter with something wrong was when I ran kodi that I had to rebuild because of the update. When I ran kodi, any mouse click on the window buttons were passed through to whatever was layered beneath the buttons (example: if I had this browser maximized and kodi was located at the top right corner over the browser window, and I click the close button in kodi, kodi remains open but the browser would close). I was going to submit a bug to kodi about that, but something felt off. When I was doing other stuff, I noticed issues with right-mouse clicking things might take multiple clicks before any context menu would come up. In addition, if I right-mouse on an open program on the bottom panel and the moment I hover over a menu item with children, the main context menu disappears while the child remains. But even then, trying to move that program to another activity (child menu item) doesn't happen. Everything is so horribly messed up that I'm exploring what it takes to rollback. Hopefully you can get back to me before I do that so I can do whatever you need me to look into/try. In case you're thinking "compositor", I have it set to "XRender". -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 429956] New: Widget Tooltip Text Missing Under Oxygen Theme
https://bugs.kde.org/show_bug.cgi?id=429956 Bug ID: 429956 Summary: Widget Tooltip Text Missing Under Oxygen Theme Product: Oxygen Version: 5.20.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: style Assignee: unassigned-b...@kde.org Reporter: nroycea+...@gmail.com Target Milestone: --- SUMMARY If I hover over an action button for a widget, there is no visible text in the tooltip. All I see is a bubble. STEPS TO REPRODUCE 1. Switch to Oxygen theme 2. Add a widget 3. Activate widget menu 4. Hover over widget menu button. OBSERVED RESULT Tooltip without text EXPECTED RESULT Tooltip with text SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992 vindicator changed: What|Removed |Added CC||nroycea+...@gmail.com --- Comment #49 from vindicator --- I'm encountering this on 5.20.4. I'm using netctl. Only options are Total Download/Upload (no per interface). System Monitor(ksysguard) IS showing an active Network History. * $ ksystemstats --replace & Unable to start backend, network information not available. Unable to register DBus service org.kde.ksystemstats. Maybe it is already running? ** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #141 from vindicator --- Nick, "100% reproducible bug"? Yet your own comment https://bugs.kde.org/show_bug.cgi?id=360478#c92 "Sometimes it's working but not always" "zero interest from devs"? When you quote Feck's comment with yours in https://bugs.kde.org/show_bug.cgi?id=360478#c91? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #138 from vindicator --- I was going to say the same thing, but also add that it's already been said that they can't replicate the issue on their side. That makes fixing the issue much harder. And if you have other bugs reported to you that you can replicate or have a backtrace that makes finding the cause easier, it's a no-brainer to attack those bugs first rather than poke around in other code to try to blindly figure out why a desktop quirk is happening (with no idea how long it'll take to find it) and leaving those easier bugs untouched. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #133 from vindicator --- Bug reports should provide, in some way, information that may lead to a resolution. i.Dark_Templar's above-and-beyond work is an extraordinary example, as is Mike's original report and other's showing it to be more widespread. But, it isn't going to be helpful, 5 years later, to simply state it still exists in version # or asking for a progress update. Florian, you'd be doing yourself a service (especially if you "will just never use plasma again") by removing yourself from the CC list. No need to be notified of nor participate in something that no longer affects you. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #127 from vindicator --- Nick, I mentioned to you in comment #87 that you're basically wasting your time. Now in comment #127, I'm going to tell you that all you're doing is spamming to 31 people. Saying it exists in the most recent version is not helpful. I'll all but guarantee it's going to be in version 5.76 as well, and even later versions and I have no interest in getting a notification for that in particular. If it's that much of a bother to you and you don't want to continue using the workaround, I'll suggest again that you just move on to something else even though you said you don't want to in #88. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423594] Notifications spike the CPU and consume extra memory when they appear; can freeze the system when many notifications are received all together
https://bugs.kde.org/show_bug.cgi?id=423594 --- Comment #9 from vindicator --- ... or maybe I won't --replace it (because it just doesn't want to), and I have to SIGTERM it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423594] Notifications spike the CPU and consume extra memory when they appear; can freeze the system when many notifications are received all together
https://bugs.kde.org/show_bug.cgi?id=423594 vindicator changed: What|Removed |Added CC||nroycea+...@gmail.com --- Comment #8 from vindicator --- Version: 5.19.5-3 I've just experienced this myself for the (first? Maybe never before or for years.) time. Except I only see 2 frozen notifications. I attached the the plasmashell process and got a backtrace for it: * #0 0x7f28ee0436a2 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f28eeb880d4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f28f080f5d7 in () at /usr/lib/libQt5Quick.so.5 #3 0x7f28f0878bb7 in QQuickWindow::event(QEvent*) () at /usr/lib/libQt5Quick.so.5 #4 0x7f28ef883752 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #5 0x7f28eed67cda in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #6 0x7f28ef12f319 in QPlatformWindow::windowEvent(QEvent*) () at /usr/lib/libQt5Gui.so.5 #7 0x7f28ef88a437 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #8 0x7f28eed67cda in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #9 0x7f28eedbfcc5 in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #10 0x7f28eedc05aa in () at /usr/lib/libQt5Core.so.5 #11 0x7f28ed1e2bfc in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #12 0x7f28ed2341f9 in () at /usr/lib/libglib-2.0.so.0 #13 0x7f28ed1e1421 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #14 0x7f28eedc0941 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #15 0x7f28eed6665c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #16 0x7f28eed6eaf4 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #17 0x5e570ab3bf5d in () #18 0x7f28ee734152 in __libc_start_main () at /usr/lib/libc.so.6 #19 0x5e570ab3c19e in _start () * In the meantime, I'll just --replace it. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 414553] Crash From New Images On Desktop Or Dolphin - kdeinit5, kio/thumbnail.so
https://bugs.kde.org/show_bug.cgi?id=414553 --- Comment #8 from vindicator --- It's still an issue, but at least program address locations are being displayed in the dump: * Stack trace of thread 1806553: #0 0x7bfb41f0e615 raise (libc.so.6 + 0x3d615) #1 0x7bfb41ef7862 abort (libc.so.6 + 0x26862) #2 0x7bfb421299ac _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x8f9ac) #3 0x7bfb4271c546 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 + 0x131546) #4 0x7bfb4271c9e1 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x1319e1) #5 0x7bfb423523e6 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2b83e6) #6 0x7bfb4271fa20 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x134a20) #7 0x7bfb4170b68a _ZN19QApplicationPrivate4initEv (libQt5Widgets.so.5 + 0x15e68a) #8 0x7bfb42f04dfc kdemain (thumbnail.so + 0x6dfc) #9 0x5ccbe71735bd n/a (kdeinit5 + 0x75bd) #10 0x5ccbe7174a59 n/a (kdeinit5 + 0x8a59) #11 0x5ccbe717521d n/a (kdeinit5 + 0x921d) #12 0x5ccbe7170b54 n/a (kdeinit5 + 0x4b54) #13 0x7bfb41ef9152 __libc_start_main (libc.so.6 + 0x28152) #14 0x5ccbe71716be n/a (kdeinit5 + 0x56be) * kio-extras/dolphin version: 20.08.1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 426657] Dolphin displays dupicate filenames, crashes on close.
https://bugs.kde.org/show_bug.cgi?id=426657 --- Comment #4 from vindicator --- Yeah, I saw this post now listed (compare with the partial (top) list I included in my previous post). I don't know if the search function simply doesn't examine the subject/title of the report, or doesn't consider variations of a word (duplicates, duplicated, ...). But I especially expected the search to come up with this report solely based on the words being in the title. Yes, most of the time (including this), I do have it set to tree-view. And this is also the only time I've ever experienced it (in case you are wondering if I can replicate it using a different mode). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 426657] Dolphin displays dupicate filenames, crashes on close.
https://bugs.kde.org/show_bug.cgi?id=426657 --- Comment #2 from vindicator --- Ugh, I also meant to mention that I initially did a search for "dolphin" here, which showed this report. Then I tried to search for "dolphin duplicate" (without quotes. looking for other reports) and this report was not listed even though "dolphin" and "duplicate" are in the report title. I don't know if there's reporting for the site's search feature, but this sure seems like a horrible implementation if it can't bring up this report from my very simple search: * Fri 21:30 415089 KAccountgeneral kde-telepathy-bugs REOP--- Dolphin Kio-gdrive authentication with Google account fails Fri 08:29 412924 kwinplatformkwin-bugs-null REPO--- [kwin_wayland] High CPU usage with Qt 5.14 and mouse cursor artifacts Fri 06:21 392531 frameworgeneral faure REPO--- Add option to have "Move" as default DND action instead of the pop-up menu Mon 03:32 341143 plasmashImage Wanotmart CONF--- Bring back per-virtual-desktop wallpapers 2020-09-11 * -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 426657] Dolphin displays dupicate filenames, crashes on close.
https://bugs.kde.org/show_bug.cgi?id=426657 vindicator changed: What|Removed |Added CC||nroycea+...@gmail.com --- Comment #1 from vindicator --- Version: 20.08.1 I'll comment here since I also encountered an issue with Dolphin crashing relating to duplicate filenames. But my case is a little different as is the coredump. I was copying files from one folder to a subfolder using Dolphin. I noticed filenames that appeared to be same. I looked closely and saw no differences. I also used the console's autocomplete to see there was truly only one file (no duplicate). I think I may have tried opening the file or maybe editing the name to see if it was a glitch, or maybe going "back" a folder (don't remember), and Dolphin just disappeared, eventually writing out the coredump: * #0 0x732c573aa615 raise (libc.so.6 + 0x3d615) #1 0x732c56d0a0e6 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x40e6) #2 0x732c573aa6a0 __restore_rt (libc.so.6 + 0x3d6a0) #3 0x732c573aa615 raise (libc.so.6 + 0x3d615) #4 0x732c57393862 abort (libc.so.6 + 0x26862) #5 0x732c573ec5e8 __libc_message (libc.so.6 + 0x7f5e8) #6 0x732c573f427a malloc_printerr (libc.so.6 + 0x8727a) #7 0x732c573f564c _int_free (libc.so.6 + 0x8864c) #8 0x732c55318bb8 _ZN9QHashData11free_helperEPFvPNS_4NodeEE (libQt5Core.so.5 + 0x107bb8) #9 0x732c572b316e _ZN14KFileItemModel9slotClearEv (libdolphinprivate.so.5 + 0x6f16e) #10 0x732c57315f1a _ZN11DolphinView6setUrlERK4QUrl (libdolphinprivate.so.5 + 0xd1f1a) #11 0x732c57590b4a n/a (libkdeinit5_dolphin.so + 0x5ab4a) #12 0x732c554f9a06 n/a (libQt5Core.so.5 + 0x2e8a06) #13 0x732c571ff1f6 _ZN13KUrlNavigator10urlChangedERK4QUrl (libKF5KIOFileWidgets.so.5 + 0x9a1f6) #14 0x732c57202dd3 _ZN13KUrlNavigator6goBackEv (libKF5KIOFileWidgets.so.5 + 0x9ddd3) #15 0x732c5757af11 n/a (libkdeinit5_dolphin.so + 0x44f11) #16 0x732c554f9a06 n/a (libQt5Core.so.5 + 0x2e8a06) #17 0x732c554f9a06 n/a (libQt5Core.so.5 + 0x2e8a06) #18 0x732c572a2c20 _ZN19KItemListController18mouseButtonPressedEi6QFlagsIN2Qt11MouseButtonEE (libdolphinprivate.so.5 + 0x5ec20) #19 0x732c572d1c30 _ZN19KItemListController15mousePressEventEP24QGraphicsSceneMouseEventRK10QTransform (libdolphinprivate.so.5 + 0x8dc30) #20 0x732c572d44eb _ZN19KItemListController12processEventEP6QEventRK10QTransform (libdolphinprivate.so.5 + 0x904eb) #21 0x732c572e41cf _ZN13KItemListView5eventEP6QEvent (libdolphinprivate.so.5 + 0xa01cf) #22 0x732c56047702 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x159702) #23 0x732c554c279a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b179a) #24 0x732c5636ced6 n/a (libQt5Widgets.so.5 + 0x47eed6) #25 0x732c5636d28e n/a (libQt5Widgets.so.5 + 0x47f28e) #26 0x732c56375aff n/a (libQt5Widgets.so.5 + 0x487aff) #27 0x732c5637fa42 _ZN14QGraphicsScene5eventEP6QEvent (libQt5Widgets.so.5 + 0x491a42) #28 0x732c56047702 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x159702) #29 0x732c554c279a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b179a) #30 0x732c5639c5cf _ZN13QGraphicsView15mousePressEventEP11QMouseEvent (libQt5Widgets.so.5 + 0x4ae5cf) #31 0x732c56088c7e _ZN7QWidget5eventEP6QEvent (libQt5Widgets.so.5 + 0x19ac7e) #32 0x732c56133f9f _ZN6QFrame5eventEP6QEvent (libQt5Widgets.so.5 + 0x245f9f) #33 0x732c554c2503 _ZN23QCoreApplicationPrivate29sendThroughObjectEventFiltersEP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b1503) #34 0x732c560476f1 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x1596f1) #35 0x732c5604e977 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x160977) #36 0x732c554c279a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b179a) #37 0x732c5604d85e _ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Ebb (libQt5Widgets.so.5 + 0x15f85e) #38 0x732c560a13b2 n/a (libQt5Widgets.so.5 + 0x1b33b2) #39 0x732c560a478f n/a (libQt5Widgets.so.5
[plasmashell] [Bug 415819] Notification entry in history too small in height resulting in an overlap
https://bugs.kde.org/show_bug.cgi?id=415819 vindicator changed: What|Removed |Added CC||nroycea+...@gmail.com --- Comment #4 from vindicator --- Created attachment 130500 --> https://bugs.kde.org/attachment.cgi?id=130500=edit Notification Group Overlap I just encountered this issue as well with the the same version (5.19.3). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 423774] New: Coredump While Logging Out
https://bugs.kde.org/show_bug.cgi?id=423774
Bug ID: 423774
Summary: Coredump While Logging Out
Product: frameworks-kglobalaccel
Version: 5.71.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdelibs-b...@kde.org
Reporter: nroycea+...@gmail.com
Target Milestone: ---
SUMMARY
Crash while trying to restart computer
(https://bugs.kde.org/show_bug.cgi?id=423773).
STEPS TO REPRODUCE
1. Restart computer button
OBSERVED RESULT
Computer restarts cleanly
EXPECTED RESULT
Crash, but still restarts.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Archlinux
(available in About System)
KDE Plasma Version: 5.19.1
KDE Frameworks Version: 5.71.0
Qt Version: 5.15.0
ADDITIONAL INFORMATION
*
Jul 01 17:22:13 computerName systemd-coredump[1683526]: Process 1683515
(kglobalaccel5) of user 1000 dumped core.
Stack trace of thread
1683515:
#0 0x7e1c1556a355 raise
(libc.so.6 + 0x3c355)
#1 0x7e1c15553853 abort
(libc.so.6 + 0x25853)
#2 0x7e1c159649ac
_ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x909ac)
#3 0x7e1c15f580e6
_ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 +
0x1330e6)
#4 0x7e1c15f58581
_ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 +
0x133581)
#5 0x7e1c15b8d2e6
_ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2b92e6)
#6 0x7e1c15f5b5c0
_ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x1365c0)
#7 0x7e1c15f5c528
_ZN15QGuiApplicationC1ERiPPci (libQt5Gui.so.5 + 0x137528)
#8 0x6521e2f8708f n/a
(kglobalaccel5 + 0x208f)
#9 0x7e1c1002
__libc_start_main (libc.so.6 + 0x27002)
#10 0x6521e2f873fe n/a
(kglobalaccel5 + 0x23fe)
-- Subject: Process 1683515 (kglobalaccel5) dumped core
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
--
-- Process 1683515 (kglobalaccel5) crashed and dumped core.
--
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
Jul 01 17:22:11 computerName dbus-daemon[1339]: [session uid=1000 pid=1339]
Activated service 'org.kde.kglobalaccel' failed: Process org.kde.kglobalaccel
received signal 6
Jul 01 17:22:11 computerName sddm[1230]: Running: /usr/bin/X -nolisten tcp
-auth /var/run/sddm/{14821b49-d9d8-4a42-b9c1-4985fb191f2f} -background none
-noreset -displayfd 18 -seat seat0 vt1
...
Jul 01 17:22:11 computerName sddm[1230]: Display server stopped.
Jul 01 17:22:10 computerName kglobalaccel5[1683515]: This application failed to
start because no Qt platform plugin could be initialized. Reinstalling the
application may fix this problem.
Available platform plugins are:
wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc,
wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
Jul 01 17:22:10 computerName kglobalaccel5[1683515]: qt.qpa.plugin: Could not
load the Qt platform plugin "xcb" in "" even though it was found.
Jul 01 17:22:10 computerName audit[1683515]: ANOM_ABEND auid=1000 uid=1000
gid=1000 ses=3 pid=1683515 comm="kglobalaccel5" exe="/usr/bin/kglobalaccel5"
sig=6 res=1
Jul 01 17:22:10 computerName kernel: audit: type=1701
audit(1593642130.148:1235): auid=1000 uid=1000 gid=1000 ses=3 pid=1683515
comm="kglobalaccel5" exe="/usr/bin/kglobalaccel5" sig=6 res=1
Jul 01 17:22:10 computerName kglobalaccel5[1683515]: qt.qpa.xcb: could not
connect to display :0
Jul 01 17:22:10 computerName dbus-daemon[1339]: [session uid=1000 pid=1339]
Activating service name='org.kde.kglobalaccel' requested by ':1.7436' (uid=1000
pid=730224 comm="plasmashell --replace ")
Jul 01 17:22:09 computerName kscreen_backend_launcher[1610]: The X11 connection
broke (error 1). Did the X11 server die?
*
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 423773] New: "Restart computer" Causes "Logout" Instead
https://bugs.kde.org/show_bug.cgi?id=423773 Bug ID: 423773 Summary: "Restart computer" Causes "Logout" Instead Product: plasmashell Version: 5.19.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: nroycea+...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Trying to restart the computer while in a session causes only the session to end and returned to the login screen. STEPS TO REPRODUCE 1. Application Launcher 2. Leave 3. Restart OBSERVED RESULT Returned to the SDDM login screen where I have to press the restart button there. EXPECTED RESULT Computer restarts SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: 5.19.1 KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION There was also a crash during logout by kglobalaccel5, but I'll post that in there. It's been like this for maybe a few months, where I restart only when I "upgrade" (usually because of https://bugs.kde.org/show_bug.cgi?id=414553). * Jul 01 17:22:09 computerName kwin_x11[1448]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/windowswitcher/WindowSwitcher.qml:58: TypeError: Cannot read property 'smallSpacing' of null Jul 01 17:22:09 computerName kwin_x11[1448]: The X11 connection broke: I/O error (code 1) Jul 01 17:22:09 computerName xembedsniproxy[1489]: The X11 connection broke (error 1). Did the X11 server die? Jul 01 17:22:09 computerName kactivitymanagerd[1455]: The X11 connection broke (error 1). Did the X11 server die? Jul 01 17:22:09 computerName gmenudbusmenuproxy[1501]: The X11 connection broke (error 1). Did the X11 server die? Jul 01 17:22:09 computerName at-spi-bus-launcher[1752]: X connection to :0 broken (explicit kill or server shutdown). Jul 01 17:22:09 computerName org.kde.Shutdown[1683509]: cannot connect to daemon at tcp:5037: Connection refused Jul 01 17:22:09 computerName org_kde_powerdevil[1536]: The X11 connection broke (error 1). Did the X11 server die? Jul 01 17:22:09 computerName kaccess[1481]: The X11 connection broke (error 1). Did the X11 server die? Jul 01 17:22:09 computerName kglobalaccel5[1466]: The X11 connection broke (error 1). Did the X11 server die? Jul 01 17:22:09 computerName kded5[1444]: The X11 connection broke (error 1). Did the X11 server die? Jul 01 17:22:09 computerName kwin_x11[1448]: The X11 connection broke (error 1). Did the X11 server die? Jul 01 17:22:09 computerName sddm[1230]: Display server stopping... Jul 01 17:22:09 computerName sddm[1230]: Socket server stopped. Jul 01 17:22:09 computerName sddm[1230]: Socket server stopping... Jul 01 17:22:09 computerName sddm[1230]: Auth: sddm-helper exited successfully Jul 01 17:22:09 computerName systemd-logind[1063]: Session 2 logged out. Waiting for processes to exit. Jul 01 17:22:09 computerName sddm-helper[1310]: [PAM] Ended. Jul 01 17:22:09 computerName kernel: audit: type=1104 audit(1593642129.248:1234): pid=1310 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="userName" exe="/usr/lib/sddm/sddm-hel> Jul 01 17:22:09 computerName audit[1310]: CRED_DISP pid=1310 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="userName" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? termina> Jul 01 17:22:09 computerName sddm-helper[1310]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred Jul 01 17:22:09 computerName sddm-helper[1310]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_close_session Jul 01 17:22:09 computerName kernel: audit: type=1106 audit(1593642129.235:1233): pid=1310 uid=0 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_keyinit,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_e> Jul 01 17:22:09 computerName audit[1310]: USER_END pid=1310 uid=0 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_keyinit,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring,pam_kwalle> Jul 01 17:22:09 computerName sddm-helper[1310]: pam_unix(sddm:session): session closed for user userName Jul 01 17:22:09 computerName sddm-helper[1310]: [PAM] Closing session ... Jul 01 17:22:08 computerName kdeconnectd[1504]: kdeconnect.plugin.notification: Destroying NotificationsPlugin Jul 01 17:22:08 computerName kwin_x11[1448]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 44584, resource id: 31457285, major code: 18 (ChangeProperty), minor code: 0 Jul 01 17:22:08 computerName polkit-kde-authentication-agent-1[1493]: Removing listener PolkitQt1::Agent::Listener(0x60099da9d220) Jul 01 17:22:08 computerName
[plasmashell] [Bug 423372] Plasmashell Memory Leak
https://bugs.kde.org/show_bug.cgi?id=423372 --- Comment #4 from vindicator --- Created attachment 129634 --> https://bugs.kde.org/attachment.cgi?id=129634=edit Memory Usage Chart Stuck For "Available". Uptime Is Always "0.0" Okay, this time I opted to let it go for over 24 hours. I ended it when it was ~1.4GB. When things looked steady/healthy WITHOUT the widgets, I re-added them ~5.5 hours later, where it looked to have increased comparatively slowly. Heaptrack also confirms libQuickCharts.so as being the largest holder of memory. Let me know if you still want the .zst file. It's 241MB. I've also attached a screenshot of my widget setup because there are a few issues. Let me know if you want me to make another bug(s) for them... Basically 1) the "Ava[i]lable"[sic] "Memory Usage" line isn't moving. At some point, it just stops. 2) Long names cut off. It would be nice to allow the user to customize the data field names like "/home read speed" instead of "Read data device dm..." which got cut off 3) "System uptime" always shows as 0.0. 4) (not in screenshot) There are 2 "Uptime" "sensors". First is the lone sensor in the list of folder/categories when you go to the "Sensors Details". The second is when you go under the "System->Uptime" category which is labeled as "System uptime" which also shows as 0.00. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423372] Plasmashell Memory Leak
https://bugs.kde.org/show_bug.cgi?id=423372 --- Comment #3 from vindicator --- Ugh, I was hoping I wouldn't have to remove them. I had just customized them after the notable upgrade/change. I knew the thermal widget had an issue and was really surprised/pleased to see the new design. When I first booted up, before I made any changes, there was some wonky stuff happening. It got even worse when I tried to modify the widgets. I ended up removing all of them, then adding them back in and recustomizing them. Then this happened. I noticed the quickcharts mentioned in the visualizer. Anyway, before your response, I went ahead and --replaced plasmashell using heaptrack about an hour ago. And now I removed all of the widgets but I'm not replacing plasmashell again (still running under heaptrack). Maybe there will be a notable settling in the output from that first hour to maybe a few more hours I give it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423372] Plasmashell Memory Leak
https://bugs.kde.org/show_bug.cgi?id=423372 --- Comment #1 from vindicator --- Forgot to include another user's experience with the same release: https://bbs.archlinux.org/viewtopic.php?id=256543 -- You are receiving this mail because: You are watching all bug changes.
