https://bugs.kde.org/show_bug.cgi?id=471279
vindicator changed:
What|Removed |Added
CC||nroycea+...@gmail.com
--
You are receiving
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.
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.
https://bugs.kde.org/show_bug.cgi?id=483538
vindicator changed:
What|Removed |Added
CC||nroycea+...@gmail.com
--- Comment #5 from
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
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.
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.
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
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/hl1
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
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
https://bugs.kde.org/show_bug.cgi?id=465937
vindicator changed:
What|Removed |Added
CC||nroycea+...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=478806
vindicator changed:
What|Removed |Added
Resolution|BACKTRACE |NOT A BUG
Status|NEEDSINFO
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
https://bugs.kde.org/show_bug.cgi?id=472369
vindicator changed:
What|Removed |Added
CC||nroycea+...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=472368
vindicator changed:
What|Removed |Added
CC||nroycea+...@gmail.com
--
You are receiving
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
https://bugs.kde.org/show_bug.cgi?id=470998
vindicator changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
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 t
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
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.
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
https://bugs.kde.org/show_bug.cgi?id=465423
vindicator changed:
What|Removed |Added
Ever confirmed|0 |1
Status|RESOLVED
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:
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.
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
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.
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.
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
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.
https://bugs.kde.org/show_bug.cgi?id=405898
vindicator changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
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
https://bugs.kde.org/show_bug.cgi?id=453206
vindicator changed:
What|Removed |Added
CC||nroycea+...@gmail.com
--- Comment #5 from
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 r
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/
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
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
https://bugs.kde.org/show_bug.cgi?id=428394
vindicator changed:
What|Removed |Added
CC||nroycea+...@gmail.com
--- Comment #21 from
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.
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.
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 plasm
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 H
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 clipb
https://bugs.kde.org/show_bug.cgi?id=442844
vindicator changed:
What|Removed |Added
CC||nroycea+...@gmail.com
--- Comment #21 from
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
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
https://bugs.kde.org/show_bug.cgi?id=444385
vindicator changed:
What|Removed |Added
CC||nroycea+...@gmail.com
--- Comment #7 from
https://bugs.kde.org/show_bug.cgi?id=443086
vindicator changed:
What|Removed |Added
CC||nroycea+...@gmail.com
--- Comment #1 from
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
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
https://bugs.kde.org/show_bug.cgi?id=433248
vindicator changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=436923
vindicator changed:
What|Removed |Added
CC||nroycea+...@gmail.com
--- Comment #5 from
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
https://bugs.kde.org/show_bug.cgi?id=436020
vindicator changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
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:
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/variab
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
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
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
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 duplicate
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.
Ju
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
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
so
https://bugs.kde.org/show_bug.cgi?id=430934
vindicator changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
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
https://bugs.kde.org/show_bug.cgi?id=431446
vindicator changed:
What|Removed |Added
CC||nroycea+...@gmail.com
--- Comment #10 from
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
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
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
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
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.
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/li
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
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
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
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 kdeinit
https://bugs.kde.org/show_bug.cgi?id=429956
vindicator changed:
What|Removed |Added
Attachment #133859|0 |1
is obsolete
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
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.
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 tt
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
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
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
https://bugs.kde.org/show_bug.cgi?id=425992
vindicator changed:
What|Removed |Added
CC||nroycea+...@gmail.com
--- Comment #49 from
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 q
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
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
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
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.
https://bugs.kde.org/show_bug.cgi?id=423594
vindicator changed:
What|Removed |Added
CC||nroycea+...@gmail.com
--- Comment #8 from
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
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
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 repo
https://bugs.kde.org/show_bug.cgi?id=426657
vindicator changed:
What|Removed |Added
CC||nroycea+...@gmail.com
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=415819
vindicator changed:
What|Removed |Added
CC||nroycea+...@gmail.com
--- Comment #4 from
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
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
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
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
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.
1 - 100 of 103 matches
Mail list logo
