Description of problem: When I open the .desktop archive, it open with Kwrite. The settings for opening files with the default application are lost. Example: steam game shortcut is now opened with Kwrite. Version-Release number of selected component (if applicable): Mageia 7 - Dolphin How reproducible: Install the system, update. Install Steam, and run the game. After the next reboot, the shortcut no works, is now opened with Kwrite. Steps to Reproduce: 1. Create application shortcut 2. Run the application. 3. Reboot and run the application again, is now opened with Kwrite.
Thanks to a colleague from the MasLinux Telegram group, the solution is: modify the file /home/user/.config/kiorc, look for the section that says "[Executable scripts]" and put "behaviourOnLaunch=execute". But, it should be check if there is a update that have been the cause of problem.
Please can you say what desktop you are using.
CC: (none) => lewyssmith
(In reply to Lewis Smith from comment #2) > Please can you say what desktop you are using. Since all pointers are to Plasma desktop (Dolphin, Kwrite, kiorc) I have tried to reproduce your problem using this (which is strange to me) - and see quite different things; and cannot reproduce your problem. * What is the source of your Mageia installation: Classic ISO, a Live DVD, netinstall, or upgrade from Mageia 6? * Is the problem just for Steam, or any application desktop shortcut? * How are you creating the Plasma (if) Desktop application shortcut? I found 2 ways: 1) Most difficult: right-click the desktop, Create New > Link to Application, of which the 3rd tab 'contents' offers difficult ways of saying which application: - browsing the *filesystem* (rather than the application menus) - typing the relevant command The desktop icon caption is in normal font, and the .desktop file quite small. 2) Much easier: in the application menus, right-click the application, Add to Desktop. The desktop icon caption is in italic, and the .desktop file is large. There is clearly some fundamental difference between them, but all behaviour is the same. Double-clicking the desktop icons raises the application. *This continues to work after re-booting.* Right-clicking offers 'Open with Shortcut Editor', or 'Open With ...' (including Kwrite). > When I open the .desktop archive [you imply in Dolphin] Why would you want to open the file in Dolphin to run the application? Do you mean 'double-click the desktop icon?' Using Dolphin to see the ~/Desktop directory shows the .desktop filenames, normal font for that created by method 1 above, italic for method 2. Double-clicking the .desktop file offers: - Open -> a properties dialogue. - Execute -> launch the application. Right-clicking offers (among other things): - Open with Shortcut Editor - Open With... (including Kwrite). So, Jose, your situation seems quite different, and we await the answers to our questions. My system does not even have ~/.config/kiorc .
Keywords: (none) => NEEDINFO
I have Mageia 7.1 with Plasma environment. I've done a clean instalation of Mageia from netinstall iso. After I update the system and reboot. Before the update, the shortcuts works perfectly. Is a bug that appears without cause apparent. I'll realize a new clean instalation and check this object again.
Summary: The application shortcut no works, is now opened with Kwrite => Application shortcuts no longer work in Dolphin, now open .desktop file with Kwrite
I have done a clean installation, I have updated the system and so far the error has not reappeared. Someone can confirm? If the same error can't be confirmed in other installations or architectures or desktop environments, we can close this bug. It could be any bug in the before instalations.
Ever confirmed: 1 => 0Status: NEW => UNCONFIRMED
Thank you for persevering. > I have done a clean installation, I have updated the system and so far the > error has not reappeared. Good news. > If the same error can't be confirmed in other installations See comment 3. > we can close this bug If you do not see the problem again, please say so and close the bug (invalid).
I think that we can close this bug for now.
Status: UNCONFIRMED => RESOLVEDResolution: (none) => INVALID