[plasmashell] [Bug 473994] Application Launcher opens on wrong screen

2023-09-06 Thread Felix Kütt
https://bugs.kde.org/show_bug.cgi?id=473994

Felix Kütt  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |NOT A BUG

--- Comment #12 from Felix Kütt  ---
(In reply to Nate Graham from comment #11)
> If you open the Add Widgets sidebar, there will be a little number in a
> circle in the corner of widgets that are active. So you can use that to see
> which widgets are active, and how many of them.

Hrm, that didn't really answer the question I asked but it did set me on the
right path to figuring the answer out...

So, from the looks of it, on hover over a widget the number of instances are
shown on the top left corner(if any actively instanced) and for installed third
party widgets on the top right there is a red line-art icon of a trash can(as
opposed to built-ins which don't show it, kinda wish some of them would be
uninstallable too since bloat, but that's neither here nor there).

Based on this it would seem that the Launcher in question was indeed installed
third party. As such the issue can be closed. But I would like to leave some
final thoughts first, if I may.

These elements being hidden under a on-hover flag seems like a rather bad idea
to me, and as I already mentioned in the passing I think it might be a good
idea to make as many of the default widgets as practically possible
uninstallable as well(I understand there are some that are bare minimum
necessary so as to not cripple the usability of the base system itself, so that
is not applicable to those). Which would mean that while this is a measure by
which to tell third party widgets apart for now, should some of the default
bundled ones ever hopefully become uninstallable it would likely be a good idea
to design a new indicator measure for the end user to instantly see and tell
apart which is a default one and which a third party widget.

Also, from what I vaguely understand the `get new widgets` sources widgets from
some third party source that the KDE project has no control over(or so I've
seen stated by others on myriad online forums) so as to assure quality, nor to
ensure they stay up to date for that matter so I'm inclined to say I'd like
to(not that I'm demanding anything tho, or even in a position to for that
matter, just signalling a single end-user opinion) see that removed perhaps
altogether if not replaced with a source that is directly under KDE projects
control.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 473994] Application Launcher opens on wrong screen

2023-09-05 Thread Felix Kütt
https://bugs.kde.org/show_bug.cgi?id=473994

--- Comment #10 from Felix Kütt  ---
(In reply to Nate Graham from comment #9)
> > opens on the same/main screen as the panel and button which triggers it.
> 
> This is what's supposed to happen for Kickoff as well, yeah.

Is there any way by which I could tell if I've added this one maybe by accident
or simply long enough ago via the `get new widgets` option that I don't recall
adding it?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 473994] Application Launcher opens on wrong screen

2023-09-01 Thread Felix Kütt
https://bugs.kde.org/show_bug.cgi?id=473994

--- Comment #8 from Felix Kütt  ---
(In reply to Nate Graham from comment #7)
> Becaise if if it's not our code, it could be doing the wrong thing, and we
> don't have any control over it.
> 

Yes, I understand that.

> I was leading towards asking you to try using one of the standard widgets
> from KDE (e.g. the original Kickoff, or Application Menu) to see if it still
> happens when using those.

Simple Menu stays on main display. Application Dashboard which if the full
screen annoying one also opens on the same/main screen as the panel and button
which triggers it. Same for the windows style application menu, though on that
one sub-menus that are longer than just a few entries sometimes go underneath
the main panel and get partially cut off by edge of the screen which seems
wrong... but that's unpredictable and only happens sometimes.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 473994] Application Launcher opens on wrong screen

2023-09-01 Thread Felix Kütt
https://bugs.kde.org/show_bug.cgi?id=473994

--- Comment #6 from Felix Kütt  ---
(In reply to Nate Graham from comment #5)
> 
> So, did you make these changes yourself?
> 
> If not, are you using a 3rd-party version of the Application Launcher widget?
> 

Nope and I don't think so.


> If not, can you ask in a distro-specific forum (e.g.
> https://forum.manjaro.org) whether this is the way your distros sets things
> up themselves?

I could see them theming things custom, but why would that affect which display
it shows up on?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 473994] Application Launcher opens on wrong screen

2023-08-31 Thread Felix Kütt
https://bugs.kde.org/show_bug.cgi?id=473994

--- Comment #4 from Felix Kütt  ---
(In reply to Nate Graham from comment #3)
> Have you edited it yourself?

What do you mean by that? Like on source level?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 473994] Application Launcher opens on wrong screen

2023-08-31 Thread Felix Kütt
https://bugs.kde.org/show_bug.cgi?id=473994

--- Comment #2 from Felix Kütt  ---
Created attachment 161318
  --> https://bugs.kde.org/attachment.cgi?id=161318=edit
AppLauncher choices

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 473994] New: Application Launcher opens on wrong screen

2023-08-31 Thread Felix Kütt
https://bugs.kde.org/show_bug.cgi?id=473994

Bug ID: 473994
   Summary: Application Launcher opens on wrong screen
Classification: Plasma
   Product: plasmashell
   Version: 5.27.7
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: plasma-b...@kde.org
  Reporter: felix.virt...@gmail.com
CC: mikel5...@gmail.com, noaha...@gmail.com
  Target Milestone: 1.0
 Flags: Wayland+, X11?

Created attachment 161311
  --> https://bugs.kde.org/attachment.cgi?id=161311=edit
Screenshot displaying the problem.

SUMMARY
Application launcher opens on the wrong screen.

STEPS TO REPRODUCE
1. Add Application launcher on main screen panel
2. Click on Application Launcher
3. Watch it open on a secondary screen.

I believe this is a duplicate of 467367 but I was told to open a new issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 467367] Application Launcher opens on wrong screen

2023-08-31 Thread Felix Kütt
https://bugs.kde.org/show_bug.cgi?id=467367

Felix Kütt  changed:

   What|Removed |Added

 CC||felix.virt...@gmail.com
 Status|RESOLVED|VERIFIED

--- Comment #4 from Felix Kütt  ---
I also experience this, but I see no way to 'fix' this by removing any overlap
in screen settings.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 465623] Removable Devices systray Plasmoid(?) opens Elisa instead of File Manager

2023-02-13 Thread Felix Kütt
https://bugs.kde.org/show_bug.cgi?id=465623

--- Comment #6 from Felix Kütt  ---
Aye, as said, surely low priority, minor issue. But if nobody ever show
interest, it'll never happen.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 465623] Removable Devices systray Plasmoid(?) opens Elisa instead of File Manager

2023-02-12 Thread Felix Kütt
https://bugs.kde.org/show_bug.cgi?id=465623

--- Comment #4 from Felix Kütt  ---
(In reply to Nate Graham from comment #3)
> Looks like the problem is that Elisa has become somehow configured as your
> file manager. This isn't something that's supported, and Elisa doesn't
> register itself as a handler for opening folders, so it's either a
> configuration issue or a packaging error. I'd recommend fixing this in
> System Settings > Applications > Default Applications.

Yes, my best guess is when/while I changed waterfox to be my default browser
months ago I might have been hovering over the file manager setting for a
moment and since my mouse has a really sensitive scroll wheel it might have
accidentally switched the file manager there. But that's besides the point and
not the issue I'm trying to highlight.

I'm trying to highlight that a button label that I assume should be contextual
doesn't really reflect the action it's going to trigger. A small and nit-picky
and thus surely low priority issue. But if it reflected what application or
type of application it would launch that would also immediately communicated to
me as a user that I might have misconfigured it rather than being left with a
confusing surprise. Or I might still be left confused why the button would even
say that but I wouldn't be surprised it opened something other than a file
manager.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 465623] Removable Devices systray Plasmoid(?) opens Elisa instead of File Manager

2023-02-12 Thread Felix Kütt
https://bugs.kde.org/show_bug.cgi?id=465623

--- Comment #2 from Felix Kütt  ---
(In reply to Nate Graham from comment #1)
> Is Elisa somehow set up to open folders, maybe? 
> 
> If you run `xdg-open ~` in a terminal window, does it open Elisa, or your 
> file manager?

Gives me the following in terminal:
```
qrc:/qml/ElisaMainWindow.qml:18:1: QML ElisaMainWindow: Accessible must be
attached to an Item
  ✔ 
file:///usr/lib/qt/qml/org/kde/kirigami.2/Page.qml:365: Error: Cannot assign
QObject* to PageRow_QMLTYPE_174*
file:///usr/lib/qt/qml/org/kde/kirigami.2/Page.qml:365: Error: Cannot assign
QObject* to PageRow_QMLTYPE_174*
org.kde.elisa.indexers.manager: Local file system indexer is inactive
org.kde.elisa.indexers.manager: Baloo indexer is unavailable
org.kde.elisa.indexers.manager: Baloo indexer is inactive
qrc:/qml/NativeTrayMenu.qml:42: TypeError: Cannot call method 'name' of
undefined
qrc:/qml/NativeTrayMenu.qml:50: TypeError: Cannot call method 'name' of
undefined
org.kde.elisa.indexers.manager: Baloo indexer is available
org.kde.elisa.indexers.manager: Baloo indexer is active
org.kde.elisa.indexers.manager: trigger init of baloo file indexer
qrc:/qml/ImageWithFallback.qml:36:5: QML Image: Invalid embedded cover image in
/run/media/user/Secondary/Music/Lineage2/L2C2_tower_of_oman.mp3
```

And does open Elisa.

> Also, can you paste the output of `grep "inode/directory" 
> ~/.config/mimeapps.list`?

```
inode/directory=org.kde.elisa.desktop;org.kde.dolphin.desktop;
inode/directory=org.kde.elisa.desktop;
```

Still, the button says 'Open in File Manager'. But if the application to open
with can be changed somewhere then perhaps it should reflect that and say 'Open
in Media Player' or 'Open in ApplicationType' or "Open in [executable name
here]" respectively?

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 465623] New: Removable Devices systray Plasmoid(?) opens Elisa instead of File Manager

2023-02-12 Thread Felix Kütt
https://bugs.kde.org/show_bug.cgi?id=465623

Bug ID: 465623
   Summary: Removable Devices systray Plasmoid(?) opens Elisa
instead of File Manager
Classification: Applications
   Product: systemsettings
   Version: 5.26.5
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Keywords: usability
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: felix.virt...@gmail.com
  Target Milestone: ---

Created attachment 156173
  --> https://bugs.kde.org/attachment.cgi?id=156173=edit
Disks & Devices opens Elisa instead of Dolphin

STEPS TO REPRODUCE
1. Press on `Disks & Devices` Plasmoid
2. Press a `Open in File Manager` button

OBSERVED RESULT

3. Witness Elisa opening instead.

EXPECTED RESULT

3. Dolphin opens to browse the mounted partition.

SOFTWARE/OS VERSIONS

Why is this duplicate here if there are selections for these above the summary
and description fields already? Much UX genious here, such wow. Have one or the
other. Having both just creates user confusion.

Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 411800] Gradient generator for Fill Layers.

2020-12-10 Thread Felix Kütt
https://bugs.kde.org/show_bug.cgi?id=411800

--- Comment #2 from Felix Kütt  ---
Great, thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 411800] New: Gradient generator for Fill Layers.

2019-09-10 Thread Felix Kütt
https://bugs.kde.org/show_bug.cgi?id=411800

Bug ID: 411800
   Summary: Gradient generator for Fill Layers.
   Product: krita
   Version: unspecified
  Platform: unspecified
OS: All
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Layer Stack
  Assignee: krita-bugs-n...@kde.org
  Reporter: felix.virt...@gmail.com
  Target Milestone: ---

Obviously a feature request.

Was about to create a fill layer in a project when I realized that gradient
wasn't a thing there. No rush, very much a low priority thing, but this would
be a very nice quality of life thing to have.

-- 
You are receiving this mail because:
You are watching all bug changes.