https://bugs.kde.org/show_bug.cgi?id=502240
Michael Butash changed:
What|Removed |Added
CC||mich...@butash.net
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=502240
--- Comment #5 from Michael Butash ---
What I'd done was attached it using the pid of the plasmashell using "heaptrack
--pid $pid", then when at high memory, kill -9 said pid and plasmashell should
restart, and heaptrack should spit
https://bugs.kde.org/show_bug.cgi?id=471642
--- Comment #16 from Michael Butash ---
Just an update, this has been happening pretty much constantly, usually 1-2
days between needing to pop plasmashell manually to reclaim memory, or a few
times oom kicked in, and this seems to occur independently
https://bugs.kde.org/show_bug.cgi?id=471642
--- Comment #15 from Michael Butash ---
Along with the host ram usage, I notice that kwin_wayland keeps using GPU
memory as well, where right now it's using some 6.3GiB of vram per nvtop, which
keeps steadily rising even after killing plasmashe
https://bugs.kde.org/show_bug.cgi?id=471642
--- Comment #11 from Michael Butash ---
Created attachment 179151
--> https://bugs.kde.org/attachment.cgi?id=179151&action=edit
heaptrack of plasma @ 93gib used - summary
Did some more rtfm today heaptrack, killed the process to let it compl
https://bugs.kde.org/show_bug.cgi?id=471642
--- Comment #12 from Michael Butash ---
Created attachment 179152
--> https://bugs.kde.org/attachment.cgi?id=179152&action=edit
heaptrack of plasma @ 93gib used - topdown
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=471642
--- Comment #13 from Michael Butash ---
Here's a google share to the heaptrack archive of the full monte.
https://drive.google.com/file/d/1bpEUFGawZI24_6moVQuJ-549dvJ29Mr-/view?usp=sharing
--
You are receiving this mail because:
You are watchin
https://bugs.kde.org/show_bug.cgi?id=471642
--- Comment #10 from Michael Butash ---
(In reply to Nate Graham from comment #9)
> Sounds like the leak itself is fixed, but typical idle usage remains higher
> than desired. Would that be an accurate statement, Michael?
Yeah, definitely ug
https://bugs.kde.org/show_bug.cgi?id=471642
--- Comment #8 from Michael Butash ---
Created attachment 179130
--> https://bugs.kde.org/attachment.cgi?id=179130&action=edit
htop, ntop, btop of high memory in plasma 6.3.2
Hi Nate, I've not used 5.27 since early last year, I'm up
https://bugs.kde.org/show_bug.cgi?id=484427
Michael Butash changed:
What|Removed |Added
CC||mich...@butash.net
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=486504
Michael Butash changed:
What|Removed |Added
CC||mich...@butash.net
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=452118
--- Comment #35 from Michael Butash ---
(In reply to Maciej Kotliński from comment #34)
> The problem still appears from time to time on my laptop but it is less
> frequent. Last time I noticed other version of probably the same issue –
> som
https://bugs.kde.org/show_bug.cgi?id=475653
--- Comment #7 from Michael Butash ---
I've been itching to actually try plasma6, but like James I too am on Arch,
it's not exactly cut and dry to get it or run it. Plus a number of the issues
mentioned were applicable to my use cases, so
https://bugs.kde.org/show_bug.cgi?id=475653
--- Comment #4 from Michael Butash ---
What I have observed over time seems to occur is there are multiple overlapping
display profiles created that it seems to bounce between with the lack of
deterministic behavior as stated by wayland in choosing
https://bugs.kde.org/show_bug.cgi?id=475653
--- Comment #3 from Michael Butash ---
This was my other thread on the matter.
https://bugs.kde.org/show_bug.cgi?id=465889
These tend to pile up in ~/.local/share/kscreen.
Also recommended was clearing these that seemed to accumulate display config
https://bugs.kde.org/show_bug.cgi?id=475653
Michael Butash changed:
What|Removed |Added
CC||mich...@butash.net
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=471642
--- Comment #1 from Michael Butash ---
So this is still happening, and very much related to 3d activity, but otherwise
without even still continues to climb steadily either way. It seems without
gaming or 3d applications it sinks about 10gb of ram
https://bugs.kde.org/show_bug.cgi?id=471642
Bug ID: 471642
Summary: Severe memory leak in 5.27.5 with Wayland
Classification: Plasma
Product: plasmashell
Version: 5.27.6
Platform: Archlinux
OS: Linux
Status: REP
https://bugs.kde.org/show_bug.cgi?id=468184
--- Comment #4 from Michael Butash ---
Agree with Gauthier, there are some deeply rooted problems here common to
various scenarios folks seem to see in more exotic display setups (sadly
anything +1 or more).
Checking back in on this, I'd been wo
https://bugs.kde.org/show_bug.cgi?id=452118
--- Comment #23 from Michael Butash ---
So weirdly a few days ago, my application windows started moving and resizing
bonkers for me again, moving into weird places, resizing windows horizontally
to as thin as only 5px wide, and like this report
https://bugs.kde.org/show_bug.cgi?id=468184
--- Comment #1 from Michael Butash ---
Some additional feedback, not all windows will get resized, or not all the
time. Mostly commonly affected resizing tends affect firefox, libreoffice,
konsole, ksettings, pluma, others, but NOT keepassxc, okular
https://bugs.kde.org/show_bug.cgi?id=468184
Bug ID: 468184
Summary: Kwin moving windows and resizing them very poorly to
unusable states on multi-monitor setups during unplug
events
Classification: Plasma
Product: kwin
https://bugs.kde.org/show_bug.cgi?id=452118
Michael Butash changed:
What|Removed |Added
CC||mich...@butash.net
--- Comment #21 from
https://bugs.kde.org/show_bug.cgi?id=465889
--- Comment #25 from Michael Butash ---
(In reply to Nate Graham from comment #24)
> I don't see anything suspicious in the Plasma config files, which leaves
> KScreen as the culprit. Unfortunately KScreen configs are basically
> impossi
https://bugs.kde.org/show_bug.cgi?id=465889
--- Comment #22 from Michael Butash ---
Created attachment 157658
--> https://bugs.kde.org/attachment.cgi?id=157658&action=edit
After kscreen/plama config files - WORKING
includes:
~/.local/share/kscreen
~/config/plasma-org.kde.plasma.
https://bugs.kde.org/show_bug.cgi?id=465889
--- Comment #21 from Michael Butash ---
Created attachment 157657
--> https://bugs.kde.org/attachment.cgi?id=157657&action=edit
Before kscreen/plasma config files
includes:
~/.local/share/kscreen
~/config/plasma-org.kde.plasma.desktop-ap
https://bugs.kde.org/show_bug.cgi?id=465889
--- Comment #20 from Michael Butash ---
I got to do some testing on my desktop over the weekend kscreen and plasma,
removing the configuration settings as you'd indicated, and does seem to be
working that the panel and widgets track the pr
https://bugs.kde.org/show_bug.cgi?id=465889
--- Comment #19 from Michael Butash ---
(In reply to Nate Graham from comment #18)
> (In reply to Michael Butash from comment #16)
> Screen arrangement data is saved in ~/.local/share/kscreen, which can be
> moved aside for testing purposes o
https://bugs.kde.org/show_bug.cgi?id=465889
--- Comment #17 from Michael Butash ---
One other thing of note I forgot to mention, I tried change screen priorities
in Ksettings, moving around displays and reordering, trying to get the kde
panels tracking primary to move, but still would not, again
https://bugs.kde.org/show_bug.cgi?id=465889
--- Comment #16 from Michael Butash ---
Sorry for the delay, was sick or busy, so first chance I had to futz with the
desktop more.
> Ok, so for debugging purposes, let's forget about both nvidia-settings and
> xrandr and focus only on w
https://bugs.kde.org/show_bug.cgi?id=465889
--- Comment #14 from Michael Butash ---
Thanks Matt, I will try that when I can reboot a bit later, but as of upgrading
to 5.27, I was still almost always using kde settings alone, and tried until I
couldn't get the panel and primary display to e
https://bugs.kde.org/show_bug.cgi?id=465889
--- Comment #12 from Michael Butash ---
Sorry, I didn't realize the pastbin links expired, I attached the output and
some images of the desktop properly here. I added some other information
requested from your blog as well. Not sure if this shou
https://bugs.kde.org/show_bug.cgi?id=465889
--- Comment #11 from Michael Butash ---
Created attachment 156729
--> https://bugs.kde.org/attachment.cgi?id=156729&action=edit
desktop-appletsrc file data
Output taken while displays active, 3rd set to primary with dock there, but
main pa
https://bugs.kde.org/show_bug.cgi?id=465889
--- Comment #10 from Michael Butash ---
Created attachment 156728
--> https://bugs.kde.org/attachment.cgi?id=156728&action=edit
full desktop low-res showing dock/panel disparities on far right 3/4th displays
Output taken while displays acti
https://bugs.kde.org/show_bug.cgi?id=465889
--- Comment #9 from Michael Butash ---
Created attachment 156727
--> https://bugs.kde.org/attachment.cgi?id=156727&action=edit
kscreen settings and nvidia-settings image
Output taken while displays active, 3rd set to primary with dock the
https://bugs.kde.org/show_bug.cgi?id=465889
--- Comment #8 from Michael Butash ---
Created attachment 156726
--> https://bugs.kde.org/attachment.cgi?id=156726&action=edit
kscreen-console output
Output taken while displays active, 3rd set to primary with dock there, but
main panel and
https://bugs.kde.org/show_bug.cgi?id=465889
--- Comment #7 from Michael Butash ---
Created attachment 156725
--> https://bugs.kde.org/attachment.cgi?id=156725&action=edit
kscreen-doctor -o output
Output taken while displays active, 3rd set to primary with dock there, but
main pa
https://bugs.kde.org/show_bug.cgi?id=465889
--- Comment #6 from Michael Butash ---
So some more on this random behavior, yesterday I went through and disconnected
my dock, reconnected them in left-to-right ordering, reset them up manually,
then without any real work, both the panel/plasma widget
https://bugs.kde.org/show_bug.cgi?id=465889
--- Comment #5 from Michael Butash ---
Actually, here's one of the whole screen setup with the settings and the panels
as they are weirdly right now. Had to scale the image quality down some to fit
on a pastebin, but here you go.
https://bugs.kde.org/show_bug.cgi?id=464132
--- Comment #5 from Michael Butash ---
Yes, 4 actually. It only seemed to happen on the last, but I didn't test how
commonly it would occur if adding them incrementally.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465889
--- Comment #4 from Michael Butash ---
Here's what this looks like currently from kde settings and nvidia-settings.
https://pasteboard.co/dZxEOWGPCE1M.png
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465889
--- Comment #3 from Michael Butash ---
Thanks for the response, here's the output of those:
http://pastie.org/p/2vbKRktRNna6sX0AKTjdLx
Looking at the output, priority one shows the 3rd display on DP-5.2, which is
proper, and my dock lands there
https://bugs.kde.org/show_bug.cgi?id=465889
Bug ID: 465889
Summary: Primary Display Cannot be adjusted in 5.27.0, KDE
Panel doesn't move with it.
Classification: Applications
Product: systemsettings
Version: 5.27.0
Plat
https://bugs.kde.org/show_bug.cgi?id=355119
Michael Butash changed:
What|Removed |Added
CC||mich...@butash.net
--- Comment #5 from
https://bugs.kde.org/show_bug.cgi?id=464132
Michael Butash changed:
What|Removed |Added
CC||mich...@butash.net
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=461708
Michael Butash changed:
What|Removed |Added
CC||mich...@butash.net
--- Comment #6 from
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #407 from Michael Butash ---
I'm on a fresh build of arch/plasma 5.25.4 as of 2 weeks ago, and already
cursing this behavior again/still. At least the last box, kde tended to move
all my windows when it the displays power-off (or di
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #355 from Michael Butash ---
This is about the same dysfunctional behavior I've fought with for years.
Still on plasma 5.19/arch currently, where hotplugging my laptop TB dock or
displays will cause kde to usually (horribly) move arou
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #344 from Michael Butash ---
No, this is another problem I have however. How related, who knows but
different issues.
KDE display settings is also a basketcase for me, particularly at 4k
resolutions, as they don't retain resol
https://bugs.kde.org/show_bug.cgi?id=275433
Michael Butash changed:
What|Removed |Added
CC||mich...@butash.net
--- Comment #19 from
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #342 from Michael Butash ---
The term "disappearing" might be misleading, but when it resizes to 10px by
1500px, it just looks like a blur to me on screen I often have to spend some
time looking for. This happens to Libreoffice c
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #339 from Michael Butash ---
The latest absurdity from kde, my 3rd monitor eats windows. Random, out of
nowhere behavior, like feral cats showing up. It just started one day.
If a window exists on my 3rd monitor, and I try to move it, it
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #338 from Michael Butash ---
@Ken Fallon
If you are having these issues, please describe your hardware and software
environment for video, display, os/dist, drivers, etc. My issues with kde for
15 years have always been with multi-monitor
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #337 from Michael Butash ---
It seems like some sort of validation issue between dbus, xrand/kernel, and
being able to keep/switch states of the settings. Oddly KDE has regressed,
changes oddly, and just does random new crap with each os
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #335 from Michael Butash ---
I did do some upgrades to my system that helped fix general stability (removing
i915 driver, moving to nvidia with modern xorg in arch), but still I run into
weirdness with the displays resize/relocate/forget
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #334 from Michael Butash ---
Running Arch, I've been keeping updated, and the multi-monitor behavior only
continues to get even more weird. I'm on 5.18.4.1 right now, and multi-monitor
is still a basketcase. This system is c
https://bugs.kde.org/show_bug.cgi?id=411506
--- Comment #26 from Michael Butash ---
> Hmm, that's strange. Did you force the EGL platform interface?
No forcing of anything. It broke, I rebooted, it came up broken still. Only
things I've done was trying to restart sddm and review
https://bugs.kde.org/show_bug.cgi?id=411506
--- Comment #23 from Michael Butash ---
Created attachment 122844
--> https://bugs.kde.org/attachment.cgi?id=122844&action=edit
Output of qdbus kwin supportInfo post upgrade and current breaking
Updated supportInfo post full system upgrade an
https://bugs.kde.org/show_bug.cgi?id=411506
--- Comment #22 from Michael Butash ---
Interesting part I find is it does seem to be compositing, it's just not
showing me anything but a black window. When I use an alt terminal to log in
at shell, I see kwin_x11 --replace running, and
https://bugs.kde.org/show_bug.cgi?id=411506
--- Comment #21 from Michael Butash ---
So last night my desktop finally broke entirely, where after it woke up, all I
got was a blank display. At this point I was left with no choice but to reboot
it, and did so gracefully from an alt tty. A reboot
https://bugs.kde.org/show_bug.cgi?id=411506
--- Comment #20 from Michael Butash ---
Created attachment 122759
--> https://bugs.kde.org/attachment.cgi?id=122759&action=edit
Output from dmesg
Here's the dmesg output of what is left in buffer to current.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=411506
--- Comment #19 from Michael Butash ---
Created attachment 122758
--> https://bugs.kde.org/attachment.cgi?id=122758&action=edit
Output from Xorg.0.log
Sure, I sterilized some of the ip's, names, and macs that pop up, but otherwise
https://bugs.kde.org/show_bug.cgi?id=411506
--- Comment #17 from Michael Butash ---
Created attachment 122742
--> https://bugs.kde.org/attachment.cgi?id=122742&action=edit
Requested qdbus kwin output with compositing active 20190919
So I'm starting to get the gl compositing issue
https://bugs.kde.org/show_bug.cgi?id=411506
--- Comment #15 from Michael Butash ---
Ok, I've added that, will continue to use and see if windows start going wonky
again. Sometimes takes days/weeks... Anything more I can pull to help resolve
this when it *is* acting weird again?
I did
https://bugs.kde.org/show_bug.cgi?id=411506
--- Comment #12 from Michael Butash ---
Created attachment 122635
--> https://bugs.kde.org/attachment.cgi?id=122635&action=edit
Requested qdbus kwin output with compositing active.
Here is the requested output with compositing re-enabled.
https://bugs.kde.org/show_bug.cgi?id=411506
--- Comment #13 from Michael Butash ---
Thanks Vlad, that worked to let me reenable compositing now, and attached the
qdbus output of that.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411506
--- Comment #9 from Michael Butash ---
> Can you move frozen windows with mouse?
I can move the window itself, but content within such as the current webpage
does not refresh. I have to minimize, unhide to get it to force a refresh to
change the p
https://bugs.kde.org/show_bug.cgi?id=411506
--- Comment #7 from Michael Butash ---
No, only the single output I pasted in the last message, nothing more via
journalctl related to video or kde all together.
Certainly, attached my output to the ticket as requested. Thank you Vlad.
--
You are
https://bugs.kde.org/show_bug.cgi?id=411506
--- Comment #6 from Michael Butash ---
Created attachment 122583
--> https://bugs.kde.org/attachment.cgi?id=122583&action=edit
Requested qdbus kwin output.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411506
--- Comment #3 from Michael Butash ---
So today after 40 days of uptime, kde is finally angry and won't restart
compositing. Cairo-dock effects still work in gl, but I get a black band
behind it due to lack of a compositor to fill it in. Journ
https://bugs.kde.org/show_bug.cgi?id=411506
--- Comment #2 from Michael Butash ---
I am pretty sure not, it's a 1070GTX. This only occurs with kde/kwin so far,
where I've been testing again of late, but otherwise have been using
Mate/Cinnamon mostly as kde's been a basketcase
https://bugs.kde.org/show_bug.cgi?id=411506
Bug ID: 411506
Summary: Kwin requires constant restart after weeks of uptime
to refresh windows
Product: kwin
Version: 5.13.0
Platform: Archlinux Packages
OS: Linu
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #325 from Michael Butash ---
It's only been 4 years, what's the rush.
Multi-Monitor has been a basketcase since 4.0, issues set to "won't fix" there,
efforts in 5 still remain broken, maybe this is something we can
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #320 from Michael Butash ---
So it's 2019, I upgraded arch, and cinnamon regressed horribly with their
compositing, so I'm trying KDE again, this time at 5.14.4.
While it still resets the position of most of my apps across disp
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #309 from Michael Butash ---
I've been waiting for general multi-monitor support to not suck since kde4, but
to no avail with things like this, and more. They love tinkering with adding
other crap to kde, but leave core functionality
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #308 from Michael Butash ---
I've been waiting for general multi-monitor support to not suck since kde4, but
to no avail with things like this, and more. They love tinkering with adding
other crap to kde, but leave core functionality
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #297 from Michael Butash ---
I have tried most of these things at some point. Different distributions on a
clean build pc this last build, even different video, and found that the
experience has been consistent in the same ways
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #294 from Michael Butash ---
@ghost53947, I'm using arch, and running latest -Syu as of that posting 1/21,
which was with plasma 5.11.5-1 on arch. It's every bit as broken as 5.8 I
upgraded from, and others prior still broken th
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #291 from Michael Butash ---
I apologize if my words were strong, but this is a very sore topic with me.
KDE has had persistent issues since 4.x making multi-monitor life hell, where
they marked them "will not fix", and opted to
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #274 from Michael Butash ---
It's my one a year check in on this thread to see if KDE isn't entirely inept
at dealing with monitor and windows placement, and seem that yes, it still is.
Just did a fresh pacman -Syy on arch to ge
https://bugs.kde.org/show_bug.cgi?id=377297
Michael Butash changed:
What|Removed |Added
Keywords||multiscreen
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=377297
Bug ID: 377297
Summary: Panel and windows move to wrong screen when displays
are added and removed
Product: plasmashell
Version: 5.9.1
Platform: Archlinux Packages
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #259 from Michael Butash ---
I'm really sad that this issue still persists after literally years of
occurring on and off. I'm using nvidia, where this was working for me prior on
amd with oss drivers (finally), now have been s
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #254 from Michael Butash ---
@madcatx, I'd migrated from ubuntu+neon repos with amd that was working fine
(taskbar staying in one place through monitor detachments) to a clean install
of neon with nvidia, and found all the same old
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #249 from Michael Butash ---
So again, I take a long weekend to try and make my desktop simply behave as
normal, happy thanksgiving.
I got fed up with the neon install being broken in more ways than imaginable
with this system, so I wiped
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #248 from Michael Butash ---
Thanks Phil, I'll say I tend to agree that I'd not do it that way myself
either, but rather that's what nvidia-settings spits out itself there, and does
tend to work.
That said, it not being corr
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #245 from Michael Butash ---
So far, I've not been able to make 5.8.3 behave in the least in terms of
keeping the task bar entirely sticky to the actual intended monitor using
either nvidia-settings or kde settings/display. They defin
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #239 from Michael Butash ---
Glitching the video card itself to lose the hdmi port hard reset everything
oddly, which caused me to have to re-setup resolution and everything here, but
once back in order, the task bar was still sitting on
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #238 from Michael Butash ---
So yeah, the task bar bouncing back and forth between monitors is back with
this, actually 5.8.3-0neon+16.04+build* versions, and this was from a neon cd
direct install.
Any time I've shut off my dis
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #237 from Michael Butash ---
I'd been using neon plasma 5.7.2 on my old desktop that seemed to finally hit a
stable run, where the panels and multi-monitor glitches seemed mostly gone.
Building a new desktop and going with a latest
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #229 from Michael Butash ---
It seems more often than not with KDE much is resolved by simply letting
whatever version of Plasma is current parsing the config files recreate it in
whatever it's native dialect is, and removing objects
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #203 from Michael Butash ---
Justin, try clearing your various kde and plasma config files in your home
directory under .kde*, .config/plasma*, and anything else your distro might
hide in other locations. Moving to neon, I had many of the
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #180 from Michael Butash ---
I type this up, go to do some other things, and notice that my taskbar jumped
over to the wrong display again. :(
Apparently not fixed.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=340267
--- Comment #74 from Michael Butash ---
Relevant note - the middle display that acted weird mostly was set to be the
primary display as well. Prior, it acted like the task bar was polarized to
pretty much anything *but* it, but really odd
https://bugs.kde.org/show_bug.cgi?id=340267
--- Comment #73 from Michael Butash ---
Running 5.7.2+p16.04+git* as of last night seems to be far better behaved,
putting windows back after shutting down my tv/displays, as well as
hard-disconnecting each.
Oddly though, I got weirdness when I was
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #179 from Michael Butash ---
Running 5.7.2+p16.04+git* in neon unstable ppa as of last night seems to be far
more behaved in use today, putting the task bar where I want it, and not
crashing oddly when I switch desktops with a mouse scrolls
https://bugs.kde.org/show_bug.cgi?id=358475
--- Comment #5 from Michael Butash ---
More grumbling, but the odd thing for me was installing the ppa for unstable
neon to fix my multi-monitor issues, and noticed dolphin just began annoyingly
resorting to single-click behaviour. I couldn&#
https://bugs.kde.org/show_bug.cgi?id=358475
--- Comment #4 from Michael Butash ---
Oh hell, it's been a while since I've had to look at input settings, I never
thought to look for it there. I didn't realize it moved there, and apparently
not the only one. Thank you, as I fo
https://bugs.kde.org/show_bug.cgi?id=358475
Michael Butash changed:
What|Removed |Added
CC||mich...@butash.net
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=361672
Michael Butash changed:
What|Removed |Added
CC||mich...@butash.net
--- Comment #1 from
1 - 100 of 118 matches
Mail list logo
