[kded-appmenu] [Bug 413413] New: Global menu applet not clickable if clicked too early

2019-10-24 Thread leftcrane
https://bugs.kde.org/show_bug.cgi?id=413413 Bug ID: 413413 Summary: Global menu applet not clickable if clicked too early Product: kded-appmenu Version: 5.16.5 Platform: Other OS: Linux Status: REPORTED

[kdeconnect] [Bug 413124] New: KDE Connect won't connect.

2019-10-17 Thread leftcrane
https://bugs.kde.org/show_bug.cgi?id=413124 Bug ID: 413124 Summary: KDE Connect won't connect. Product: kdeconnect Version: 1.3.5 Platform: Other OS: Linux Status: REPORTED Severity: critical

[kmenuedit] [Bug 412852] New: locate and edit the .desktop file (or integrate an editor)

2019-10-11 Thread leftcrane
https://bugs.kde.org/show_bug.cgi?id=412852 Bug ID: 412852 Summary: locate and edit the .desktop file (or integrate an editor) Product: kmenuedit Version: 5.16.5 Platform: Kubuntu Packages OS: Linux

[plasmashell] [Bug 412548] Gui to whitelist/blacklist applications for global menu export (workaround for broken applications)

2019-10-07 Thread leftcrane
https://bugs.kde.org/show_bug.cgi?id=412548 --- Comment #5 from leftcrane --- Yeah, silly of me to not have thought of this. I don't think QT clients can be blacklisted, for example. AFAIK, the only ones that can are those that rely on appmenu-gtk module (org.appmenu.gtk-module blacklist

[plasmashell] [Bug 412548] Gui to whitelist/blacklist applications for global menu export (workaround for broken applications)

2019-10-07 Thread leftcrane
https://bugs.kde.org/show_bug.cgi?id=412548 --- Comment #2 from leftcrane --- Sure, problem is that many people are stuck with it (at least by default) unless they are using the latest packages. In general there seem to be issues handling dynamic and lazy loaded menus, or menus that for some

[plasmashell] [Bug 412548] Gui to whitelist/blacklist applications for global menu export (workaround for broken applications)

2019-10-07 Thread leftcrane
https://bugs.kde.org/show_bug.cgi?id=412548 --- Comment #3 from leftcrane --- edit: This is a different *problem from LO. -- You are receiving this mail because: You are watching all bug changes.

[krunner] [Bug 412602] New: Allow 1 char prefixes for web shortcuts.

2019-10-04 Thread leftcrane
https://bugs.kde.org/show_bug.cgi?id=412602 Bug ID: 412602 Summary: Allow 1 char prefixes for web shortcuts. Product: krunner Version: 5.15.90 Platform: Kubuntu Packages OS: Linux Status: REPORTED

[kded-appmenu] [Bug 412548] New: Gui to whitelist/blacklist applications for global menu export (workaround for broken applications)

2019-10-03 Thread leftcrane
https://bugs.kde.org/show_bug.cgi?id=412548 Bug ID: 412548 Summary: Gui to whitelist/blacklist applications for global menu export (workaround for broken applications) Product: kded-appmenu Version: 5.16.4 Platform:

[Discover] [Bug 410549] PPA's without a valid release file will cause Discover to stop displaying all APT repositories

2019-09-18 Thread leftcrane
https://bugs.kde.org/show_bug.cgi?id=410549 --- Comment #21 from leftcrane --- I wouldn't bet on this bug having been "fixed" by accident. It's been around for ages on both Gnome Software and Discover. It's hard to reproduce. If you play around with enough repositories you will

[Discover] [Bug 410549] PPA's without a valid release file will cause Discover to stop displaying all APT repositories

2019-09-18 Thread leftcrane
https://bugs.kde.org/show_bug.cgi?id=410549 --- Comment #20 from leftcrane --- Updates work, but APT repositories are not displayed. -- You are receiving this mail because: You are watching all bug changes.

[kdeconnect] [Bug 411753] New: KDE Connect spams the desktop with a torrent of old notifications causing the system to become unresponsive.

2019-09-09 Thread leftcrane
https://bugs.kde.org/show_bug.cgi?id=411753 Bug ID: 411753 Summary: KDE Connect spams the desktop with a torrent of old notifications causing the system to become unresponsive. Product: kdeconnect Version: 1.3.5

[kdeconnect] [Bug 411750] New: KDE Connect still won't connect, requiring a reboot to re-pair

2019-09-09 Thread leftcrane
https://bugs.kde.org/show_bug.cgi?id=411750 Bug ID: 411750 Summary: KDE Connect still won't connect, requiring a reboot to re-pair Product: kdeconnect Version: 1.3.5 Platform: Kubuntu Packages OS: Linux

[krunner] [Bug 411713] Option to increase text and icons size to improve visual feedback.

2019-09-08 Thread leftcrane
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

[krunner] [Bug 411713] Option to increase text and icons size to improve visual feedback.

2019-09-08 Thread leftcrane
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

[krunner] [Bug 411713] New: Option to increase text and icons size to improve visual feedback.

2019-09-08 Thread leftcrane
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

[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation

2019-09-07 Thread leftcrane
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

[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation

2019-09-07 Thread leftcrane
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

[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation

2019-09-07 Thread leftcrane
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

[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation

2019-09-07 Thread leftcrane
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

[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation

2019-09-07 Thread leftcrane
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

[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation

2019-09-07 Thread leftcrane
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

[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation

2019-09-07 Thread leftcrane
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

[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation

2019-09-07 Thread leftcrane
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

[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation

2019-09-07 Thread leftcrane
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

[lattedock] [Bug 411663] Eliminate delay in dock when using workspace isolation

2019-09-06 Thread leftcrane
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

[lattedock] [Bug 411663] New: Eliminate delay in dock when using workspace isolation

2019-09-06 Thread leftcrane
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:

[frameworks-kio] [Bug 411599] Open/Save dialog is much too small.

2019-09-06 Thread leftcrane
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

[frameworks-kio] [Bug 411599] New: Open/Save dialog is much too small.

2019-09-04 Thread leftcrane
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

[lattedock] [Bug 411551] Implement right-click drag to resize active windows

2019-09-03 Thread leftcrane
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

[kate] [Bug 411558] New: tear off, draggable tabs like on browsers/tilix

2019-09-03 Thread leftcrane
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

[lattedock] [Bug 411551] Implement right-click drag to resize active windows

2019-09-03 Thread leftcrane
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

[plasma-browser-integration] [Bug 411554] Auto-dismiss download progress notification

2019-09-03 Thread leftcrane
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.

[plasma-browser-integration] [Bug 411554] Auto-dismiss download progress notification

2019-09-03 Thread leftcrane
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

[plasma-browser-integration] [Bug 411554] Auto-dismiss download progress notification

2019-09-03 Thread leftcrane
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

[plasma-browser-integration] [Bug 411554] Auto-dismiss download progress notification

2019-09-03 Thread leftcrane
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

[plasma-browser-integration] [Bug 411554] New: Auto-dismiss download progress notification

2019-09-03 Thread leftcrane
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:

[lattedock] [Bug 411551] New: Implement right-click drag to resize active windows

2019-09-03 Thread leftcrane
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

[kdeconnect] [Bug 411527] New: Phone gets disconnected. You have to turn on the phone screen to resume KDEConnect pairing.

2019-09-02 Thread leftcrane
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

[kdeconnect] [Bug 411527] Phone gets disconnected. You have to turn on the phone screen to resume KDEConnect pairing.

2019-09-02 Thread leftcrane
https://bugs.kde.org/show_bug.cgi?id=411527 leftcrane changed: What|Removed |Added Platform|Other |Kubuntu Packages -- You are receiving this mail

[kdeconnect] [Bug 411526] New: Clipboard doesn't get engaged

2019-09-02 Thread leftcrane
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

[lattedock] [Bug 411437] double clicking on panel maximizes the active panel menu plasmoid (it should dismiss it, per common UI patterns)

2019-08-30 Thread leftcrane
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

[lattedock] [Bug 411437] double clicking on panel maximizes the active panel menu plasmoid (it should dismiss it, per common UI patterns)

2019-08-30 Thread leftcrane
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.

[lattedock] [Bug 411437] New: double clicking on panel maximizes the active panel menu plasmoid (it should dismiss it, per common UI patterns)

2019-08-30 Thread leftcrane
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

[lattedock] [Bug 411386] New: Dock sometimes shows windows from another monitor despite being limited to a single monitor

2019-08-28 Thread leftcrane
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

[frameworks-kglobalaccel] [Bug 411338] New: Implement Easystroke-type mouse gestures (EasyStroke is not compatible with KDE Modifier only shortcuts - it blocks them)

2019-08-26 Thread leftcrane
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

[Discover] [Bug 410549] PPA's without a valid release file will cause Discover to stop displaying all APT repositories

2019-08-16 Thread leftcrane
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

[Discover] [Bug 410549] PPA's without a valid release file will cause Discover to stop displaying all APT repositories

2019-08-16 Thread leftcrane
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

[Discover] [Bug 410549] PPA's without a valid release file will cause Discover to stop displaying all APT repositories

2019-08-16 Thread leftcrane
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

[Discover] [Bug 410549] PPA's without a valid release file will cause Discover to stop displaying all APT repositories

2019-08-16 Thread leftcrane
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

[Discover] [Bug 410549] PPA's without a valid release file will cause Discover to stop displaying all APT repositories

2019-08-16 Thread leftcrane
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.

[Discover] [Bug 410549] PPA's without a valid release file will cause Discover to stop displaying all APT repositories

2019-08-16 Thread leftcrane
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

[Discover] [Bug 410549] PPA's without a valid release file will cause Discover to stop displaying all APT repositories

2019-08-16 Thread leftcrane
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

[Discover] [Bug 410549] PPA's without a valid release file will cause Discover to stop displaying all APT repositories

2019-08-15 Thread leftcrane
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:

[Discover] [Bug 410549] PPA's without a valid release file will cause Discover to stop displaying all APT repositories

2019-08-15 Thread leftcrane
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.

[Discover] [Bug 410549] PPA's without a valid release file will cause Discover to stop displaying all APT repositories

2019-08-15 Thread leftcrane
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

[Discover] [Bug 410549] PPA's without a valid release file will cause Discover to stop displaying all APT repositories

2019-08-15 Thread leftcrane
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

[Discover] [Bug 410549] PPA's without a valid release file will cause Discover to stop displaying all APT repositories

2019-08-15 Thread leftcrane
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

[Discover] [Bug 410549] PPA's without a valid release file will cause Discover to stop displaying all APT repositories

2019-08-15 Thread leftcrane
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

[Discover] [Bug 410549] PPA's without a valid release file will cause Discover to stop displaying all APT repositories

2019-08-15 Thread leftcrane
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

[Discover] [Bug 410549] PPA's without a valid release file will cause Discover to stop displaying all APT repositories

2019-08-12 Thread leftcrane
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.

[Discover] [Bug 410549] PPA's without a valid release file will cause Discover to stop displaying all APT repositories

2019-08-12 Thread leftcrane
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

[Discover] [Bug 410549] New: PPA's without a valid release file will cause Discover to stop displaying all APT repositories (except flatpak and snap)

2019-08-03 Thread leftcrane
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

[Discover] [Bug 410549] PPA's without a valid release file will cause Discover to stop displaying all APT repositories

2019-08-03 Thread leftcrane
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

[plasma-nm] [Bug 410362] VPN doesn't reconnect after resuming from long suspend.

2019-07-31 Thread leftcrane
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

[plasma-nm] [Bug 410362] New: VPN doesn't reconnect after resuming from long suspend.

2019-07-29 Thread leftcrane
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

[kdeconnect] [Bug 410316] Executable: kdeconnectd PID: 14651 Signal: Segmentation fault (11)

2019-07-29 Thread leftcrane
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

[kdeconnect] [Bug 410316] Executable: kdeconnectd PID: 14651 Signal: Segmentation fault (11)

2019-07-29 Thread leftcrane
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.

[kdeconnect] [Bug 410316] Executable: kdeconnectd PID: 14651 Signal: Segmentation fault (11)

2019-07-29 Thread leftcrane
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

[kdeconnect] [Bug 410360] New: Add a "soft upair" (disconnect) option to the interface and put a warning on the permanent unpair action.

2019-07-29 Thread leftcrane
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

[kdeconnect] [Bug 410316] Executable: kdeconnectd PID: 14651 Signal: Segmentation fault (11)

2019-07-29 Thread leftcrane
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

[kdeconnect] [Bug 410316] Executable: kdeconnectd PID: 14651 Signal: Segmentation fault (11)

2019-07-29 Thread leftcrane
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 "

[kdeconnect] [Bug 410316] Executable: kdeconnectd PID: 14651 Signal: Segmentation fault (11)

2019-07-29 Thread leftcrane
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

[kdeconnect] [Bug 410316] Executable: kdeconnectd PID: 14651 Signal: Segmentation fault (11)

2019-07-28 Thread leftcrane
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

[kdeconnect] [Bug 410316] Executable: kdeconnectd PID: 14651 Signal: Segmentation fault (11)

2019-07-28 Thread leftcrane
https://bugs.kde.org/show_bug.cgi?id=410316 leftcrane changed: What|Removed |Added Platform|Other |Kubuntu Packages -- You are receiving this mail

[kdeconnect] [Bug 410316] New: Executable: kdeconnectd PID: 14651 Signal: Segmentation fault (11)

2019-07-28 Thread leftcrane
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

[lattedock] [Bug 410104] New: Add an option to Close last window instead of group from dock.

2019-07-22 Thread leftcrane
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

[kwin] [Bug 409979] New: Kwin rules forcing all windows to single monitor do not (always) apply.

2019-07-19 Thread leftcrane
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

[lattedock] [Bug 404540] [feature] - new indicator style from Gnome's Dash to Panel

2019-06-19 Thread leftcrane
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

[lattedock] [Bug 404540] [feature] - new indicator style from Gnome's Dash to Panel

2019-06-19 Thread leftcrane
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.

[lattedock] [Bug 404540] [feature] - new indicator style from Gnome's Dash to Panel

2019-06-19 Thread leftcrane
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.

[lattedock] [Bug 404540] [feature] - new indicator style from Gnome's Dash to Panel

2019-06-19 Thread leftcrane
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

[kded-appmenu] [Bug 407101] Make the menubar searchable

2019-06-09 Thread leftcrane
https://bugs.kde.org/show_bug.cgi?id=407101 leftcrane changed: What|Removed |Added CC||leftcr...@tutanota.com --- Comment #2 from

[lattedock] [Bug 408412] Fitt's Law broken for applets in the corners of Latte Panels

2019-06-08 Thread leftcrane
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

[lattedock] [Bug 408412] Fitt's Law broken for applets in the corners of Latte Panels

2019-06-08 Thread leftcrane
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

[lattedock] [Bug 408412] Fitt's Law broken for applets in the corners of Latte Panels

2019-06-08 Thread leftcrane
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.

[lattedock] [Bug 408412] Fitt's Law broken for applets in the corners of Latte Panels

2019-06-08 Thread leftcrane
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.

[lattedock] [Bug 408412] Fitt's Law broken for applets in the corners of Latte Panels

2019-06-08 Thread leftcrane
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.

[lattedock] [Bug 408412] Fitt's Law broken for applets in the corners of Latte Panels

2019-06-07 Thread leftcrane
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.

[lattedock] [Bug 408412] Applets don't reliably respond to mouse events at screen edges, undermining efficiency.

2019-06-07 Thread leftcrane
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

[lattedock] [Bug 408412] New: Applets don't reliably respond to mouse events at screen edges, undermining efficiency.

2019-06-07 Thread leftcrane
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

[lattedock] [Bug 408411] zoom interferes with the functioning of normal applets in a single-panel scenario.

2019-06-07 Thread leftcrane
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

[lattedock] [Bug 408411] New: zoom interferes with the functioning of normal applets in a single-panel scenario.

2019-06-07 Thread leftcrane
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

[kwin] [Bug 408390] New: Sticky screen edges for side docks in multihead context. (Unity feature)

2019-06-06 Thread leftcrane
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:

[lattedock] [Bug 408129] New: Guaranteed padding for all widgets in the panel?

2019-05-30 Thread leftcrane
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

[kwin] [Bug 385522] Present Windows: Don't darken all windows and denote selection some other way than restoring original lightness

2019-05-25 Thread leftcrane
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.

[kwin] [Bug 385522] Present Windows: Don't darken all windows and denote selection some other way than restoring original lightness

2019-05-25 Thread leftcrane
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

[kwin] [Bug 385522] Present Windows: Don't darken all windows and denote selection some other way than restoring original lightness

2019-05-25 Thread leftcrane
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

[kwin] [Bug 385522] Present Windows: Don't darken all windows and denote selection some other way than restoring original lightness

2019-05-23 Thread leftcrane
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

[kde-gtk-config] [Bug 406997] New: Headerbar button decorations inconsistent with breeze QT toolbars (and look inferiour, imo)

2019-04-27 Thread leftcrane
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

[kde-gtk-config] [Bug 406997] Headerbar button decorations inconsistent with breeze QT toolbars (and look inferiour, imo)

2019-04-27 Thread leftcrane
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.

  1   2   3   >