sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Unclear "higher-ranked lifetime error" error
Labels: A-diagnostics,A-lifetimes,T-compiler,E-needs-mcve,D-terse,A-higher-ranked

### Code

main.rs:
```Rust
use tokio::io::{self, AsyncWriteExt};

pub async fn get_by_id<I, S>(ids: I) -> io::Result<()>
where
    I: IntoIterator<Item = S>,
    S: Into<String>,
{
    for s in ids {
        let s = s.into();
        let mut stdout = io::stdout();
        stdout.write_all(s.as_bytes()).await?;
    }
    
    Ok(())
}

async fn beba() -> io::Result<()> {
    let audios = vec![(1, 2)];
    let _audios = get_by_id(
        audios
            .iter()
            .map(|(a, b)| format!("{}_{}", a, b)),
    )
    .await?;

    Ok(())
}

trait FnTrait {}

impl<F, Fut> FnTrait for F
where
    F: Fn() -> Fut + Send + Sync + 'static,
    Fut: std::future::Future<Output = io::Result<()>> + Send + 'static,
{}

fn check_fn<F: FnTrait>(_f: F) {}

#[tokio::main]
async fn main() -> io::Result<()> {
    check_fn(beba);

    Ok(())
}
```


Cargo.toml:
```toml
[package]
name = "hrle-repro"
version = "0.1.0"
edition = "2021"

[dependencies]
tokio = { version = "1.32.0", features = ["full"] }
```

### Current output

```Shell
error: higher-ranked lifetime error
  --> src/main.rs:41:5
   |
41 |     check_fn(beba);
   |     ^^^^^^^^^^^^^^
   |
   = note: could not prove `fn() -> impl Future<Output = Result<(), std::io::Error>> {beba}: FnTrait`

error: could not compile `hrle-repro` (bin "hrle-repro") due to previous error
```


### Desired output

I am not sure of the exact wording, but it should explain that the failure is due to the `Future` returned from the function not implementing `Send` and `Sync`


### Rationale and extra context

Without explanation of why does the passed function not implement the required trait, it is not immediately clear what the issue is. 

### Other cases

The error output is the same on stable and nightly

### Anything else?

Originally minimized from [this code](https://github.com/rust-lang/rust/files/12511203/Archive.zip) using reqwest and teloxide
Repository: storybook
Issue: [Bug]: Storybook broken build error after fresh install
Labels: bug,needs triage

### Describe the bug

After installing fresh Storybook 7.4.0 to my vite+vue project, I'm receiving brken build error on startup.

```
npm run storybook

> x@0.0.0 storybook
> storybook dev -p 6006

@storybook/cli v7.5.0-alpha.1

info => Starting manager..
Error: ENOENT: no such file or directory, mkdir '/app'

WARN Broken build, fix the error above.
WARN You may need to refresh the browser.
```



### To Reproduce

_No response_

### System

```bash
Environment Info:

  System:
    OS: macOS 13.1
    CPU: (8) arm64 Apple M1
  Binaries:
    Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
    Yarn: 1.22.18 - /opt/homebrew/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
  Browsers:
    Chrome: 116.0.5845.140
    Edge: 113.0.1774.57
    Safari: 16.2
  npmPackages:
    @storybook/addon-essentials: ^7.4.0 => 7.4.0
    @storybook/addon-interactions: ^7.4.0 => 7.4.0
    @storybook/addon-links: ^7.4.0 => 7.4.0
    @storybook/blocks: ^7.4.0 => 7.4.0
    @storybook/testing-library: ^0.2.0 => 0.2.0
    @storybook/vue3: ^7.4.0 => 7.4.0
    @storybook/vue3-vite: ^7.4.0 => 7.4.0
```


### Additional context

_No response_
Repository: PowerToys
Issue: Mouse Screen Wrapping
Labels: Idea-Enhancement,Needs-Triage,Product-Mouse Utilities

### Description of the new feature / enhancement

There should be another mouse option where you can choose to let the mouse be able to wrap around the screen horizontally and/or vertically.

### Scenario when this would be used?

This just makes it easier to get from one side of the screen to another, I can't think on any actual use cases but I'm sure there are some.

### Supporting information

_No response_
Repository: PowerToys
Issue: [ScreenRuler]Allow moving the UI by dragging
Labels: Idea-Enhancement,Needs-Triage,Product-Screen Ruler

### Microsoft PowerToys version

0.73.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Screen ruler

### Steps to reproduce

After running the app and bringing up the ruler, I'm unable to navigate its position, When I need to change its position I exit it and then reopen it, instead of having the ability to move it.

### ✔️ Expected Behavior

being able to change the container box of the screen ruler, some prior versions had the advantage. but it's been disabled!

### ❌ Actual Behavior

The running screen ruler container is paralyzed in navigation

### Other Software

_No response_
Repository: electron
Issue: [Feature Request]: Native Splash Screen Support
Labels: enhancement :sparkles:

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Problem Description

Currently, Electron apps that require a longer load time don't have a built-in method to show a native splash screen. While there are workarounds using additional BrowserWindow instances or HTML/CSS, these methods can be resource-intensive and may not provide the desired user experience.



### Proposed Solution

I propose the addition of a native splash screen feature in Electron. This would allow developers to display a splash screen quickly upon app launch, providing immediate feedback to the user. The splash screen would automatically close once the main Electron window is ready to be displayed.

Specifically, the solution could involve:

A new API, e.g., app.showSplashScreen(imagePath, options), where imagePath is the path to the splash image and options could include display time, animation effects, etc.
Native implementations for each platform:
Windows: Using C++ and WinAPI or another framework.
macOS: Using Objective-C and Cocoa.
Linux: Using C++ and GTK or another framework.

### Alternatives Considered

Alternatives currently involve using an additional BrowserWindow to simulate a splash screen or using HTML/CSS overlays. However, these methods can be slower, more resource-intensive, and may not provide a consistent or desired user experience across platforms.

### Additional Information

A native splash screen would enhance the user experience by providing immediate feedback upon app launch, especially for apps with longer load times. It would also align Electron with other platforms and frameworks that offer native splash screen support.
Repository: vscode
Issue: Drag file another remote machine differs from origin
Labels: bug,help wanted,file-explorer

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.81.1
- OS Version: Windows_NT x64 10.0.22621
Steps to Reproduce:
1. open two Remote-SSH and connect two different machines (remote A remote B). 
2. drag one remote A file to remote B. ( remote B have the different file but have the same file path)

I think vscode Remote-SSH should forbid file dragging between different machines. However if the file share the same path it may work.  

remoteA:~/a.txt    
![image](https://github.com/microsoft/vscode/assets/130338111/37d9a39b-7cc7-4417-9699-c5d8fc06fcbb)
drag to remoteB
![image](https://github.com/microsoft/vscode/assets/130338111/a2b986bb-f44a-4ebd-8294-16b1c23af36a)
Repository: PowerToys
Issue: Tooltip reminder of shortcut keys from the menu reached by clicking the PowerToys icon in the notification area
Labels: Needs-Triage

### Description of the new feature / enhancement

On clicking the PowerToys icon in the notification area brings up a menu to enable certain capabilities. The More button leads to a list of all features with the ability to turn them on and off.
However, this is not always enough to use them, as a key combination must already be known, e.g. Win-ctrl-shift-t for crop and lock. For less-frequently used features, one must open Settings to get a reminder.
This enhancement would not only make it easier to use less frequently accessed capabilities of PowerToys, but also encourage the use of them.

### Scenario when this would be used?

When wanting to use a lesser-used a PowerToys feature for which the required key combination(s) have not yet been memorised.

### Supporting information

_No response_
Repository: next.js
Issue: `next/link` with `rewrites` works different in preview and local environment
Labels: bug,Navigation

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/mrzmyr/link-to-rewrite-reproduction

### To Reproduce

**Localhost**

![CleanShot 2023-09-04 at 10 23 21](https://github.com/vercel/next.js/assets/746429/921d6823-7cd9-4e51-a1cd-550872183c89)

https://localhost:3000/example

**Preview**

![CleanShot 2023-09-04 at 10 24 17](https://github.com/vercel/next.js/assets/746429/9c45ce58-79c0-4276-bbba-2970b96ac12b)

https://link-to-rewrite-reproduction-mrzmyr.vercel.app/example

### Current vs. Expected behavior

**Current**

Given the `next.config.js`
```js
  rewrites: () => [
    {
      source: "/",
      destination: "/en",
    },
  ],
```
and a link `<Link href="/">Go Home</Link>`, the redirect on preview deployments sets the slug to `["index"]` and to (the correct rewrite) `["en"]` on local deployments.

**Expected**

Given the `next.config.js`
```js
  rewrites: () => [
    {
      source: "/",
      destination: "/en",
    },
  ],
```
and a link `<Link href="/">Go Home</Link>`, the redirect on preview deployments sets the same slug `["en"]`on local and preview deployments.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 20:59:58 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6020
    Binaries:
      Node: 19.9.0
      npm: 9.6.3
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.4.20-canary.15
      eslint-config-next: 13.4.19
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.2.2
    Next.js Config:
      output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router, Routing (next/router, next/navigation, next/link)

### Additional context

_No response_
Repository: node
Issue: resetAndDestroy can not be called on tlssocket?
Labels: confirmed-bug

### Details

Isn't tlssocket kind of TCP? How to send RST on a tls connection?

### Node.js version

18

### Example code

```js
const tlssocket = require('tls').connect({
    port: 443,
    host: 'www.example.com',
})
.on('secureConnect', () => {
    tlssocket.resetAndDestroy();
});
```

```
TypeError [ERR_INVALID_HANDLE_TYPE]: This handle type cannot be sent
    at new NodeError (node:internal/errors:393:5)
    at Socket.resetAndDestroy (node:net:700:13)
    at TLSSocket.<anonymous> (/path/to/test.js)
    at TLSSocket.emit (node:events:513:28)
    at TLSSocket.onConnectSecure (node:_tls_wrap:1576:10)
    at TLSSocket.emit (node:events:513:28)
    at TLSSocket._finishInit (node:_tls_wrap:952:8)
    at ssl.onhandshakedone (node:_tls_wrap:733:12)
```

### Operating system

Not applicable.

### Scope

runtime

### Module and version

net tls
Repository: vscode
Issue: For simple deletions, no words should be highlighted on the right side
Labels: feature-request,diff-editor

## Description

`this` should not be highlighted:

![Image](https://github.com/microsoft/vscode/assets/2931520/51f1338f-191c-4b19-8b4f-65517f514ab3)


## Playground Example

[Monaco Editor Playground Repro](https://microsoft.github.io/monaco-editor/playground.html?source=v0.42.0-dev-20230904#XQAAAAJBEwAAAAAAAABBqQkHQ5NjdMeMm-jY7SIQ9S7DNlzs5W-mwj0fe1ZCDRFc9ws9XQE0SJE1jc2VKxhaLFIw9vEWdz-byd4ecjUNCjQTjZnHx_R_ugxZ6xrWgz8k0rlYVGZfwQ3QjH2GDw7bI_8paqOoYtw1AXFwYvJQ2FfcOWSRahkBHGIodyL4t5qTZGqNb8u5CzK1d6Qd0N-wEG5YnmJmWdc3Hi6hvGCnq5HV3Mf37pimvxc8_ICBMgH62LcneoFAJUcviWl8qZavUy_F_KGaE9ShS6yTW3p2VNTbOAo7ZdFeLBUOiVDegz6Kaa_LUjSsFQgVBu5gDath3QWAsGADHENcG_jCJzelKYDJbROM0SB2cmLA8O57iGMh0ogmBZEZqhNopJW9Oxd8Ka54nty0TyCaDSihEqxoG1b8c09U4lbMSUhbtfO9BjPV_RHK6s_9-yb0KOaLeN1ZJa0Iel4AZ9Ql5S9ds72b23gmWPj_nB7JLb3gaYmJdo3yHzGu9a3XoM-T-x3Az9_wQKRkpYpdOlwhGNKwee575dztkADnMzgM0L2TLMuKpHaBd4QR-dK5R-uyAawhW18kEz3KPwcjH1caU6zUCbBtYbB7ZfjTYqhRVS-y0g5M5IMtounl5ASRR0mogoNLUiuek_GxizlUcwIDBRhEo8PCqaQAa1mTj_kbwnV7-KPT0Zm1xB5_jLOUtW2quQTA4IPQ1xgXiU4imCLkQyh66U2_-mT52QNKN1obY_nuG_iisE8Mtu7LfTQihgddVlHE6U2lrQOi5jhGq1sP56nrHIirmyq1ZWAFr_WP-5j10O0OFr4IdeCY9ymMAAXW1Ti8jbZRJmHoMr4khXextGSth1RzR_9PdyRgXmjHtZq8P5UiYgKdIJJTp3gsr_Yi08XxEORhGznegGTak8Veopgav0lObLAHNOUT6bfBTY4NetFr5f_e2ti0omLtBWQA6ANyXft-PprBbD7LJATGWxe9c64xxR6pRirdLfOhrwP9PBwOF-PClDTFRScAirvdzvddX4gjH3xlPfPZXZy3m_bM3FWaxbUNdKPnGyeM3yJ5jnsAmUFrl_-JkyyAxWQlRuMFhVj7kr30CoQbm8fHVO7fL5prVuV97vstWKvz7YVNbBV10cmOBnOpRFIfYEQ1HgASSEXlcPLPbjUyWPacIdgKbBIzeqYRe2P1wHl3rxjCJhmjjpkJ06D_4ZtGEAUdrVrJPYCp5D7n2RZQsPnKlfGaRSSJSf_yLdQk) (click on "use latest dev" to verify a future bug-fix)
Repository: godot
Issue: PopupMenu closes as soon as it appears
Labels: bug,discussion,usability,topic:gui

### Godot version

4.2 latest

### System information

Godot v4.2.dev (f9004b52f) - Windows 10.0.22621 - Vulkan (Forward+)

### Issue description

The popup menu closes as soon as it appears. This behavior appears to be triggered by the automatic selection of the first option in the list upon opening. It happens only when the list is large enough that requires scrolling.
here is the error I'm getting :
```
ERROR: Condition "index == -1" is true. Returning: Rect2i()
   at: subwindow_get_popup_safe_rect (scene\main\viewport.cpp:3513)
```
 I want to solve this but not getting the exact problem and solution. Related to https://github.com/godotengine/godot/issues/73413 & https://github.com/godotengine/godot/issues/76480. 

https://github.com/godotengine/godot/assets/81252768/1f6b0183-0e6c-4cbb-8888-df4f45f7a4ac




### Steps to reproduce

Run the attached project or

Create any OptionMenu add enough items that requires scroll.
Click on option menu and see it closes as soon as it appears.

### Minimal reproduction project

[optionmenu.zip](https://github.com/godotengine/godot/files/12512830/optionmenu.zip)
Repository: next.js
Issue: Catch-all routs overlaps with static routs
Labels: bug

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/boring-currying-lqqtd9?file=%2Fnext.config.js%3A5%2C1

### To Reproduce

1. access : **/home** or any predefined slug from **generateStaticParams**
2. See success rendering from catch-all routes : [...slug]
3. access: **/api/draft**
4. Still accessing rendering from catch-all routes : [...slug] and not static path **/api/draft**

### Current vs. Expected behavior

Instead of accessing the API route, it is handled by catch-all routes **[...slug]**

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Home
    Binaries:
      Node: 18.15.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.20-canary.15
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.3
    Next.js Config:
      output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router

### Additional context

_No response_
Repository: vscode
Issue: Provide diff view inside comment card to preview suggested edits
Labels: feature-request,api,api-proposal

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
In our code review process at Google we're able to provide suggested edits as a reviewer. Currently we're trying to include these suggestions better in our review flow. We think an inline preview to smaller code suggestions in the comment card will be a very helpful tool for the code author. This could look something like this:
![image](https://github.com/microsoft/vscode/assets/6637517/6f34c329-93d0-47f8-9953-f6cf97a914e3)

While this looks a lot like an integrated peek view I'd expect some memory issues when displaying lots of them at the same time. That's why I think this would need to be a bit more custom.

I could see this being useful for all users, not only inside our organisation.
What do you think? Is this a feature you could imagine having in your code base?
If so we could imagine to help implement it.
Repository: deno
Issue: LSP test collector breaks on duplicate test names
Labels: bug,lsp

```js
import { assertEquals } from "https://deno.land/std@0.201.0/assert/mod.ts";
import { add } from "./main.ts";

Deno.test(function addTest() {
  assertEquals(add(2, 3), 5);
});


Deno.test(function foo() {

});

Deno.test(function foo() {

});
```

This will only discover one of the "foo" test functions. Changing one of them to "bar" fixes the issue. Since `Deno.test` doesn't prevent duplicate names, the LSP should handle it more gracefully.
Repository: stable-diffusion-webui
Issue: [Feature Request]: Better Inpainting interface
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Please make the inpainting interface like the inpainting interface at https://aqualxx.github.io/stable-ui/, that is to say,

- Masking inpainting areas on high-res images does not lag
- There is an eraser feature

Additionally please add the ability to zoom in on an image for finer inpainting

### Proposed workflow

1. Go to img2img tab and go to inpaint
2. Enjoy non-laggy inpainting with high resolution images and more

### Additional information

Video of current lag (image is 6000x4000 JPEG)
https://youtu.be/R0rdbijzv9w
Repository: next.js
Issue: `not-found.tsx` inside group does not rendered for unmatched URLs
Labels: bug,Navigation,linear: next

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/sleepy-chihiro-3n4tly

### To Reproduce

1. Start application in development or in production (next dev or next start)
2. Navigate to any unmatched URL
3. See that the `not-found.tsx` inside the group is not rendered


https://github.com/vercel/next.js/assets/34211799/607ada1d-281c-414d-9221-99c3ac7325f0

### Current vs. Expected behavior

Expected `not-found.tsx` to be rendered within the group when it's unmatched URL, but it only works for `notFound()` function.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 21.6.0: Thu Jul  6 22:18:26 PDT 2023; root:xnu-8020.240.18.702.13~1/RELEASE_X86_64
    Binaries:
      Node: 18.17.0
      npm: 9.8.1
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.4.20-canary.16
      eslint-config-next: 13.4.4
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.3
    Next.js Config:
      output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router, Routing (next/router, next/navigation, next/link)

### Additional context

_No response_

<sub>[NEXT-1602](https://linear.app/vercel/issue/NEXT-1602/not-foundtsx-inside-group-does-not-rendered-for-unmatched-urls)</sub>
Repository: next.js
Issue: Middleware cause prefetch for dynamic pages fail when changing locale
Labels: bug,Runtime

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/VincentDugard/next-i18-next-bug

### To Reproduce

1. `npm i`
2. `npm run dev`
3. navigate to `/something`
4. navigate to "de" locale using link "change locale to de"

### Current vs. Expected behavior

Following previous steps you should navigate to /de url, but this doesn't change page content. The client seems to send prefetch query as expected but the server messes with locale parameter. If you look at server console, localization debug prints only "en" locale but never "de".

If you remove middleware.ts, everything works as expected (middleware is empty, so it do nothing)

There seems to be a conflict between middleware and localized dynamic route with prefetch request.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP Debian 5.10.158-2 (2022-12-13)
    Binaries:
      Node: 19.1.0
      npm: 8.19.3
      Yarn: 3.3.0
      pnpm: 8.7.1
    Relevant Packages:
      next: 13.4.20-canary.16
      eslint-config-next: 13.4.19
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.2.2
    Next.js Config:
      output: N/A
```


### Which area(s) are affected? (Select all that apply)

Middleware / Edge (API routes, runtime)

### Additional context

I was trying to prefix default locale [as explained in the offcial next.js doc](https://nextjs.org/docs/pages/building-your-application/routing/internationalization#prefixing-the-default-locale) but could'nt get this working because of this bug.
Repository: PowerToys
Issue: [Crop and Lock]: command line activation
Labels: Idea-Enhancement,Product-CropAndLock

### Description of the new feature / enhancement

I think it could be good to activate the function Crop and Lock through a command line.

by giving 
- the name of windows/handle that we want to duplicate,
- the window to be captured : top left - bottom right coordinates
- the position to put the windows : top left - bottom right coordinates (to allow zoom at the same time)


### Scenario when this would be used?

In application where we have 2 screens, one of them is a touchscreen (1), the other not (2).

one application (A) could be launch on screen (1) and duplicate on screen (2)
another application (B) could be launch on screen (1) and have interaction with touch screen while (A) is still in screen (2)

If we want to interact with (A) we can activate this (A) application on screen (1) and it will change on screen (2) also
we can after reactivate app (B)

Exemple with VLC running in screen (2) while on Edge on screen (1) but able to control VLC from screen (1) sometimes.

As it is touchscreen, shortcut is not easy, and defining target position is not possible on the screen (2)



### Supporting information

_No response_