Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linux shortcuts no longer appear in Windows start menu #12375

Closed
1 of 2 tasks
daedsidog opened this issue Dec 13, 2024 · 3 comments
Closed
1 of 2 tasks

Linux shortcuts no longer appear in Windows start menu #12375

daedsidog opened this issue Dec 13, 2024 · 3 comments

Comments

@daedsidog
Copy link

daedsidog commented Dec 13, 2024

Windows Version

Microsoft Windows [Version 10.0.19044.5247]

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Arch Linux

Other Software

GNU Emacs 29.4 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.43, cairo version 1.18.2)

Repro Steps

n/a

Expected Behavior

Installing programs through pacman should have the Linux shortcuts be available from the Windows start menu.

Actual Behavior

After full system update via pacman -Syu, most shortcuts are unavailable. It is not clear why some are available why others are not. For instance, I have Emacs installed, but it does not appear in the start menu:

Image

Image

Restarting WSL, whether by wsl.exe --shutdown or by disabling the Windows features, did not solve the issue, neither did reinstalling the programs.

Diagnostic Logs

[daedsidog@DESKTOP-OC5833J applications]$ pwd
/usr/share/applications
[daedsidog@DESKTOP-OC5833J applications]$ ls
avahi-discover.desktop  emacsclient.desktop       java-java-openjdk.desktop      org.gnupg.pinentry-qt5.desktop
bssh.desktop            emacsclient-mail.desktop  jconsole-java-openjdk.desktop  org.gnupg.pinentry-qt.desktop
bvnc.desktop            emacs.desktop             jshell-java-openjdk.desktop    vim.desktop
cmake-gui.desktop       emacs-mail.desktop        mimeinfo.cache                 xdvi.desktop
[daedsidog@DESKTOP-OC5833J applications]$ cat emacs.desktop
[Desktop Entry]
Name=Emacs
GenericName=Text Editor
Comment=Edit text
MimeType=text/english;text/plain;text/x-makefile;text/x-c++hdr;text/x-c++src;text/x-chdr;text/x-csrc;text/x-java;text/x-moc;text/x-pascal;text/x-tcl;text/x-tex;application/x-shellscript;text/x-c;text/x-c++;
Exec=emacs %F
Icon=emacs
Type=Application
Terminal=false
Categories=Development;TextEditor;
StartupNotify=true
StartupWMClass=Emacs
[daedsidog@DESKTOP-OC5833J applications]$ cat cmake-gui.desktop 
[Desktop Entry]
Version=1.0
Name=CMake
Comment=Cross-platform buildsystem
Exec=cmake-gui %f
Icon=CMakeSetup
Terminal=false
X-MultipleArgs=false
Type=Application
Categories=Development;Building;
StartupNotify=true
MimeType=application/x-cmakecache;
[daedsidog@DESKTOP-OC5833J applications]$ 
Copy link

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@daedsidog
Copy link
Author

daedsidog commented Dec 13, 2024

It might be the same problem as in No start menu entry for flatpaks (#9586) , though mine seems systemic vs. just a single application. I'm unsure whether I should close it or not, for now, I'll leave it open unless told otherwise.

@daedsidog
Copy link
Author

Okay so, I'm not sure exactly what I did, but since I really needed an Emacs shortcut, I took the CMake one (one of the few that worked) and pasted it as the emacs.desktop, changing only the name and the Exec parameter, then saved it.

That didn't work, at least not at first.

I then created a batch script that would start Emacs from Windows:

wsl bash -c "emacs &"

Th script itself didn't work (started a console and closed immediately), but as I clicked the start menu, I suddenly noticed the Emacs shortcut (with the CMake app image). It appears that all the shortcuts are now visible again, after being absent for two weeks:

Image

I don't know what I did exactly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant