https://bugs.kde.org/show_bug.cgi?id=411713
--- Comment #3 from leftcrane ---
Increasing the font/icons/padding would be an intermediate measure - there are
better ways to improve usability with a more comprehensive redesign.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=411713
--- Comment #2 from leftcrane ---
Hmm, I guess you're right. But it does have a huge preview pane and input box,
which helps with visual feedback. Also Spotlight reads your intention much
better than Krunner, so the first result is typically what you
https://bugs.kde.org/show_bug.cgi?id=411713
Bug ID: 411713
Summary: Option to increase text and icons size to improve
visual feedback.
Product: krunner
Version: 5.15.90
Platform: Kubuntu Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=411663
--- Comment #17 from leftcrane ---
Workspace isolation = "show only launchers from current desktop"
If the user checks the "show only launchers from current desktop" box, then the
"Slide in and out single windows" sh
https://bugs.kde.org/show_bug.cgi?id=411663
--- Comment #15 from leftcrane ---
No, I am saying disable the slide in animation IF the user chooses workspace
isolation.
This animation has a significant negatively impact on usability when isolation
is enabled. There is just no way for an average
https://bugs.kde.org/show_bug.cgi?id=411663
--- Comment #13 from leftcrane ---
And you can't even disable animations in the simple view. So a user can enable
workspace isolation in the simple view but they can't fix the lag issue in the
same view - they'd have to switch to advanced and study all
https://bugs.kde.org/show_bug.cgi?id=411663
--- Comment #12 from leftcrane ---
> so that support has its limitations.
OK, fair enough. But I would urge you to block animations automatically if the
user selects desktop isolation, instead of relying on the user to check all the
boxes. (Us
https://bugs.kde.org/show_bug.cgi?id=411663
--- Comment #10 from leftcrane ---
Created attachment 122524
--> https://bugs.kde.org/attachment.cgi?id=122524=edit
small video
Watch what happens to the dock. I enable animations since this is the default
behavior and allows you to see the prob
https://bugs.kde.org/show_bug.cgi?id=411663
--- Comment #9 from leftcrane ---
Yes, this is intended behavior. I am saying it's the wrong behavior. The tasks
should appear instantly when you switch desktops. Open windows appear
instantly, therefore the tasks should also appear instantly.
--
You
https://bugs.kde.org/show_bug.cgi?id=411663
--- Comment #7 from leftcrane ---
Just enable the feature and open a bunch of apps, the more the better. Then
twitch between desktops. You will see that the dock takes a certain amount of
time to get populated when you switch desktops.
--
You
https://bugs.kde.org/show_bug.cgi?id=411663
--- Comment #6 from leftcrane ---
Yeah, it's better without animations but I wouldn't consider it fixed. The
delay remains. You switch to the next desktop and the dock takes at least a
second to get populated with the tasks. With *default* animations
https://bugs.kde.org/show_bug.cgi?id=411663
--- Comment #3 from leftcrane ---
I don't see an option to disable animations, just 1x 2x 3x.
Animations are fine, they just have no place in this instance. When you switch
desktops, your windows don't start animating. So the dock shouldn't animate
https://bugs.kde.org/show_bug.cgi?id=411663
--- Comment #1 from leftcrane ---
It takes about two-three seconds to UPDATE the task list when switching
desktops. It's very inconvenient when switching desktops rapidly. You have to
wait for all the tasks to get displayed.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=411663
Bug ID: 411663
Summary: Eliminate delay in dock when using workspace isolation
Product: lattedock
Version: git (master)
Platform: Kubuntu Packages
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=411599
--- Comment #2 from leftcrane ---
Also gtk-style hiding scrollbars could be really beneficial for these cases.
The current bars take up ~30-40 pixels of space horizontally in the dialog, all
the time. It also clutters the interface.
It would help
https://bugs.kde.org/show_bug.cgi?id=411599
Bug ID: 411599
Summary: Open/Save dialog is much too small.
Product: frameworks-kio
Version: unspecified
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=411551
--- Comment #4 from leftcrane ---
Hmm, hard for me to understand your reasoning. Ofc it's up to you but I'd hope
you reconsider.
Resizing windows is needlessly difficult and this could help a ton. Also a
pretty logical extension of the paradigm
https://bugs.kde.org/show_bug.cgi?id=411558
Bug ID: 411558
Summary: tear off, draggable tabs like on browsers/tilix
Product: kate
Version: Git
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=411551
--- Comment #2 from leftcrane ---
I don't see the loss in functionality. It's used for the latte context menu
only, and if this were implemented you'd still be able to access it on mouse up
(same as left click). The tiny latte menu is for config
https://bugs.kde.org/show_bug.cgi?id=411554
--- Comment #6 from leftcrane ---
*really easy.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411554
--- Comment #5 from leftcrane ---
Again, nothing wrong with showing the notification but I don't see any reason
for it to ever persist for the duration of a process by default. Plasma makes
it really to check previous notifications now anyway.
--
You
https://bugs.kde.org/show_bug.cgi?id=411554
--- Comment #4 from leftcrane ---
I think the tray is sufficient for that. It still shows up in the tray.
Notifications are in general very well done, but the main problem is that they
are hard to get rid of.
There is no dismiss shortcut and many
https://bugs.kde.org/show_bug.cgi?id=411554
--- Comment #2 from leftcrane ---
Ah, I forgot there is a toggle for everything on KDE. thanks!
Will you consider changing the default though? I don't think the current
behavior makes sense and it's not something the user should have to configure
https://bugs.kde.org/show_bug.cgi?id=411554
Bug ID: 411554
Summary: Auto-dismiss download progress notification
Product: plasma-browser-integration
Version: unspecified
Platform: Kubuntu Packages
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=411551
Bug ID: 411551
Summary: Implement right-click drag to resize active windows
Product: lattedock
Version: git (master)
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=411527
Bug ID: 411527
Summary: Phone gets disconnected. You have to turn on the phone
screen to resume KDEConnect pairing.
Product: kdeconnect
Version: 1.3.5
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=411527
leftcrane changed:
What|Removed |Added
Platform|Other |Kubuntu Packages
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=411526
Bug ID: 411526
Summary: Clipboard doesn't get engaged
Product: kdeconnect
Version: 1.3.5
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=411437
--- Comment #4 from leftcrane ---
Latte windows don't really need this functionality, do they? I mean most of
them are just dialogs. Alternately can't you change the class of
maximizable/draggable latte windows?
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=411437
--- Comment #2 from leftcrane ---
Well the window class of the popup is lattedock.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411437
Bug ID: 411437
Summary: double clicking on panel maximizes the active panel
menu plasmoid (it should dismiss it, per common UI
patterns)
Product: lattedock
Version: git
https://bugs.kde.org/show_bug.cgi?id=411386
Bug ID: 411386
Summary: Dock sometimes shows windows from another monitor
despite being limited to a single monitor
Product: lattedock
Version: git (master)
Platform: Kubuntu
https://bugs.kde.org/show_bug.cgi?id=411338
Bug ID: 411338
Summary: Implement Easystroke-type mouse gestures (EasyStroke
is not compatible with KDE Modifier only shortcuts -
it blocks them)
Product: frameworks-kglobalaccel
https://bugs.kde.org/show_bug.cgi?id=410549
--- Comment #18 from leftcrane ---
When Discover is in broken state,
pkmon emits (looks like it's refreshing forever - it's piling up dozens of
"download attemps" in the systray):
/49822_bccdabad percentage -1
/49822_bccdabad role get
https://bugs.kde.org/show_bug.cgi?id=410549
--- Comment #17 from leftcrane ---
I should mention that in the first case `discover diagnostic start after `pkcon
refresh force -c -1` (8.40 KB, text/plain)`, it's still partially broken in the
sense of not being able to display any apt sources. OTHER
https://bugs.kde.org/show_bug.cgi?id=410549
--- Comment #16 from leftcrane ---
Created attachment 122185
--> https://bugs.kde.org/attachment.cgi?id=122185=edit
discover diagnostic while broken (stuck refreshing cache).
This is what get emitted when Discover is broken (i.e. no updates, gre
https://bugs.kde.org/show_bug.cgi?id=410549
--- Comment #15 from leftcrane ---
Created attachment 122184
--> https://bugs.kde.org/attachment.cgi?id=122184=edit
discover diagnostic start after `pkcon refresh force -c -1`
Here's the output for Disover after refreshing the cache via pkcon. H
https://bugs.kde.org/show_bug.cgi?id=410549
--- Comment #14 from leftcrane ---
Haha, now it's broken again.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410549
--- Comment #13 from leftcrane ---
After running:
pkcon refresh force -c -1
then killing packagekitd (it didn't work before doing that),
I started plasma-discover from the CL and everything works. Until the issue
with caching is fixed
https://bugs.kde.org/show_bug.cgi?id=410549
--- Comment #12 from leftcrane ---
pkcon works. The problem is when the software centers try to refresh the cache.
This is currently being explored in the github issue.
https://github.com/hughsie/PackageKit/issues/334
It may be that packagekit is fine
https://bugs.kde.org/show_bug.cgi?id=410549
--- Comment #11 from leftcrane ---
Created attachment 122153
--> https://bugs.kde.org/attachment.cgi?id=122153=edit
another illustration: updates in the plasmoid, nothing in the software center
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=410549
--- Comment #9 from leftcrane ---
I had to kill packagekit to fix to the constant "downloading" notifications
(referenced above).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410549
--- Comment #8 from leftcrane ---
I am not sure this is all upstream. The weird sources and backends behavior in
the graphical interface should probably not be happening even there are
problems with backend.
Maybe keep it open for now, Nate?
--
You
https://bugs.kde.org/show_bug.cgi?id=410549
--- Comment #7 from leftcrane ---
I have no idea what's been going on. Pkcon works but the graphical stuff is
completely broken. Anyway here's a shot:
https://github.com/hughsie/PackageKit/issues/334
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=410549
--- Comment #6 from leftcrane ---
Created attachment 122150
--> https://bugs.kde.org/attachment.cgi?id=122150=edit
it keeps downloading stuff, for whatever reason (seraching for file, resolving,
searching. resolving etc)
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=410549
--- Comment #4 from leftcrane ---
The commandline pkcon client succeeds in fetching updates, but both graphical
software stores fail (in fact they can't display any software).
APT works of course and does GetNewStuff (or whatever it's called
https://bugs.kde.org/show_bug.cgi?id=410549
--- Comment #3 from leftcrane ---
Gnome software doesn't work either right now (it just loads the software
catalog for ever), even after removing the repos.
So I think packagekit is what's broken, and I'm not sure what to do about it.
Maybe
https://bugs.kde.org/show_bug.cgi?id=410549
--- Comment #2 from leftcrane ---
Created attachment 122094
--> https://bugs.kde.org/attachment.cgi?id=122094=edit
illustration of issue (no update, no sources etc.)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410549
--- Comment #1 from leftcrane ---
OK, after a restart/logout, Discover no longer displays apt updates - and for
some reason is offering to install a bunch of backends which are already
installed, with the install button grayed out. So at the moment
https://bugs.kde.org/show_bug.cgi?id=410549
Bug ID: 410549
Summary: PPA's without a valid release file will cause Discover
to stop displaying all APT repositories (except
flatpak and snap)
Product: Discover
https://bugs.kde.org/show_bug.cgi?id=410549
leftcrane changed:
What|Removed |Added
Summary|PPA's without a valid |PPA's without a valid
|release
https://bugs.kde.org/show_bug.cgi?id=410362
--- Comment #2 from leftcrane ---
Shouldn't it automatically reconnect on wake, by default? When you resume from
sleep, you expect everything that was running to continue running. Wifi
reconnects automatically, so VPN should be the same.
It may also
https://bugs.kde.org/show_bug.cgi?id=410362
Bug ID: 410362
Summary: VPN doesn't reconnect after resuming from long
suspend.
Product: plasma-nm
Version: 5.15.4
Platform: Kubuntu Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=410316
--- Comment #6 from leftcrane ---
SUMMARY
Looks like KDEConnect craps out whenever the interface changes without
KDEConnect running. It keeps connecting to the last interface it remembers.
This would explain why, for example
https://bugs.kde.org/show_bug.cgi?id=410316
--- Comment #5 from leftcrane ---
(That's Bug #410360)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410316
--- Comment #4 from leftcrane ---
CONCLUSION:
=
I've unpaired the device on in the Android app and then repaired. The
connection works now and persists after resume from suspend.
Problems still
https://bugs.kde.org/show_bug.cgi?id=410360
Bug ID: 410360
Summary: Add a "soft upair" (disconnect) option to the
interface and put a warning on the permanent unpair
action.
Product: kdeconnect
Version: 1.10
https://bugs.kde.org/show_bug.cgi?id=410316
--- Comment #3 from leftcrane ---
OK, for some reason after logging out I can see the phone in the KCM module but
the Android app can't find my PC. Obviously the plasmoid says "no devices
found"
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=410316
--- Comment #2 from leftcrane ---
Crash report after logging out and logging back in.
---
Application: kdeconnectd (kdeconnectd), signal: Segmentation fault
Using host libthread_db library "
https://bugs.kde.org/show_bug.cgi?id=410316
leftcrane changed:
What|Removed |Added
Version|unspecified |1.3.4
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=410316
--- Comment #1 from leftcrane ---
OK, I think I know how to reproduce this 100% of the time:
1. Pair
2. Connect to some OpenVPN server from your PC (i.e connect to VPN).
3. Put your PC to sleep.
4. Resume from sleep. The phone should no longer
https://bugs.kde.org/show_bug.cgi?id=410316
leftcrane changed:
What|Removed |Added
Platform|Other |Kubuntu Packages
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=410316
Bug ID: 410316
Summary: Executable: kdeconnectd PID: 14651 Signal:
Segmentation fault (11)
Product: kdeconnect
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=410104
Bug ID: 410104
Summary: Add an option to Close last window instead of group
from dock.
Product: lattedock
Version: git (master)
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=409979
Bug ID: 409979
Summary: Kwin rules forcing all windows to single monitor do
not (always) apply.
Product: kwin
Version: 5.15.3
Platform: Kubuntu Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=404540
--- Comment #20 from leftcrane ---
I think an optimal default configuration would be:
(this is my reference config)
1. Dash to dock indicators.
2. Pitch back panel (transparency up to the user)
3. Shadows for icons in the panel (more robust
https://bugs.kde.org/show_bug.cgi?id=404540
--- Comment #19 from leftcrane ---
The effect is even more subtle if you have zoom enabled, since it blends with
the neighboring windows which are usually light in color.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=404540
--- Comment #18 from leftcrane ---
Created attachment 121013
--> https://bugs.kde.org/attachment.cgi?id=121013=edit
gif too subtle
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=404540
--- Comment #17 from leftcrane ---
This is fantastic. Thanks. I would suggest to make the effect significantly
stronger (it is significantly stronger in dash to panel). See the gif - it is
too subtle to provide meaningful feedback.
--
You
https://bugs.kde.org/show_bug.cgi?id=407101
leftcrane changed:
What|Removed |Added
CC||leftcr...@tutanota.com
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=408412
--- Comment #16 from leftcrane ---
Correct. Fixed. Somehow I had a swipe action activated. I had to disable it
directly in kwinrc cause system settings won't save the config change change
for whatever reason.
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=408412
--- Comment #14 from leftcrane ---
Oh yeah I am very sorry. I mean LEFT dock.
So if it's RIGHT, TOP, BOTTOM - edge mousing in dock area WORKS.
If it's LEFT - edge mousing in dock area does NOT WORK.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=408412
--- Comment #12 from leftcrane ---
Created attachment 120686
--> https://bugs.kde.org/attachment.cgi?id=120686=edit
screen
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408412
--- Comment #9 from leftcrane ---
Created attachment 120685
--> https://bugs.kde.org/attachment.cgi?id=120685=edit
side
added
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408412
--- Comment #7 from leftcrane ---
It's the same layout I sent you. Tested on Kubuntu 19.04
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408412
--- Comment #5 from leftcrane ---
It's fixed for the window buttons, but the dock still doesn't respond to edge
mousing when positioned on the right.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408412
--- Comment #2 from leftcrane ---
Created attachment 120653
--> https://bugs.kde.org/attachment.cgi?id=120653=edit
layout
added.
neither the (righthand) dock nor the window buttons are engaged when you move
the mouse to the right. Window butt
https://bugs.kde.org/show_bug.cgi?id=408412
Bug ID: 408412
Summary: Applets don't reliably respond to mouse events at
screen edges, undermining efficiency.
Product: lattedock
Version: git (master)
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=408411
--- Comment #1 from leftcrane ---
It also interferes with your appmenu-title widget. So the combined
appmenu-title can't work with zoom enabled in the same panel. It just zooms on
hover instead of revealing the menu.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=408411
Bug ID: 408411
Summary: zoom interferes with the functioning of normal applets
in a single-panel scenario.
Product: lattedock
Version: git (master)
Platform: Kubuntu Packages
https://bugs.kde.org/show_bug.cgi?id=408390
Bug ID: 408390
Summary: Sticky screen edges for side docks in multihead
context. (Unity feature)
Product: kwin
Version: 5.15.90
Platform: Kubuntu Packages
OS:
https://bugs.kde.org/show_bug.cgi?id=408129
Bug ID: 408129
Summary: Guaranteed padding for all widgets in the panel?
Product: lattedock
Version: git (master)
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=385522
--- Comment #31 from leftcrane ---
I think it makes sense to treat them in tandem. Remove dimming AND replace with
other effect, as the bug says.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=385522
--- Comment #29 from leftcrane ---
If someone can present a use case for dimming, then it could be kept as an
option. But don't think a use case exists. There are only arguments AGAINST it,
i.e. only downsides with no conceivable upside
https://bugs.kde.org/show_bug.cgi?id=385522
--- Comment #28 from leftcrane ---
Saverio Brancaccio,
You have only presented arguments AGAINST dimming. That's what I am saying
nobody needs dimming - it's just bad. No other system does this.
The correct solution imo, is to draw a box around
https://bugs.kde.org/show_bug.cgi?id=385522
--- Comment #24 from leftcrane ---
Why even have an option for dimming?
All it does is make it harder to identify windows (virtually impossible in
desktop grid) - why would anyone ever want this?
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=406997
Bug ID: 406997
Summary: Headerbar button decorations inconsistent with breeze
QT toolbars (and look inferiour, imo)
Product: kde-gtk-config
Version: 5.15.4
Platform: Kubuntu
https://bugs.kde.org/show_bug.cgi?id=406997
--- Comment #1 from leftcrane ---
Created attachment 119682
--> https://bugs.kde.org/attachment.cgi?id=119682=edit
toolbar vs headerbar
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=406238
leftcrane changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=406238
Bug ID: 406238
Summary: Transparency can't be rolled back.
Product: Breeze
Version: 5.15.3
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Severity: major
https://bugs.kde.org/show_bug.cgi?id=404540
--- Comment #15 from leftcrane ---
Correct
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=404540
--- Comment #13 from leftcrane ---
I would also round the edges of the active window indicator and hover boxes.
That way they will look nice in zoom mode. Otherwise when you zoom, you'll have
sharp boxes protruding out of the dock.
--
You
https://bugs.kde.org/show_bug.cgi?id=404540
--- Comment #12 from leftcrane ---
Created attachment 119163
--> https://bugs.kde.org/attachment.cgi?id=119163=edit
mockup
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=404540
--- Comment #11 from leftcrane ---
1. I think the maximum number is two (for three or more windows) in Metro.
2. The active window is always identifies by the gray highlight box, regardless
of which style of window indicator you use. The open window
https://bugs.kde.org/show_bug.cgi?id=404540
--- Comment #9 from leftcrane ---
1. Big line is one window. Big line with marks at the end is multiple windows.
2. Shown/minimized windows are exactly the same. I don't think it makes sense
to differentiate them - that just makes the dock more
https://bugs.kde.org/show_bug.cgi?id=404540
--- Comment #7 from leftcrane ---
The dots and lines indicate the number of windows within each group. (some of
them are confusing, but you can clearly see what they mean in Metro and Dashes
style. These are the two best styles, IMO)
--
You
https://bugs.kde.org/show_bug.cgi?id=404540
--- Comment #5 from leftcrane ---
1. Pinned and non-pinned task items are visually the same.
2. Mnimized tasks non-minimized are visually the same.
3. Shown window: highlight box. (how's "shown window" different from "active"
https://bugs.kde.org/show_bug.cgi?id=405991
Bug ID: 405991
Summary: Kolour pain window won't activate after canvas resize
Product: kolourpaint
Version: 18.04
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=405807
--- Comment #14 from leftcrane ---
I think a shortcut or trigger to move all windows to primary is simple enough
to work as advertised. But it's your call obviously.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405807
--- Comment #12 from leftcrane ---
I "fixed" it on my end by writing a script that sets/unsets a kwin rule forcing
all windows to monitor one. Pretty crude and has to be run as hotplug, but it
gets the job done.
KDE should consider shoul
101 - 200 of 331 matches
Mail list logo
