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

q4wine prevents user from running winecfg from KRunner even after uninstalling #98

Closed
ezxpro opened this Issue Nov 2, 2016 · 7 comments

Comments

Projects
None yet
2 participants
@ezxpro

ezxpro commented Nov 2, 2016

I had a problem with q4wine in KDE 5.8.3 on Arch Linux when trying to launch winecfg after q4wine was uninstalled and found out it applies for other wine builtin utilities as well.

The problem is that q4wine creates several .desktop files at $HOME/.local/share/applications/q4wine/Default/system/ which aren't removed once the program is uninstalled.

Those files will override the corresponding commands in KRunner - funilly it only overrides iexplore, taskmgr, regedit and oleview, the others can still be launched because the real command's entry appears right below the buggy entry, but pressing enter will try launching the troubled one - thus making it impossible to run some of them (namely regedit, winecfg, iexplore, explorer, taskmgr as a few others) in KDE unless you do it from the command line.

Clicking in the entries will return the message "Could not find the program '/usr/bin/q4wine-cli"'.
Finally, I think these files should be removed once the program is uninstalled, since they are created anyway when you install q4wine.

@brezerk brezerk added the Support label Nov 3, 2016

@brezerk brezerk self-assigned this Nov 3, 2016

@brezerk

This comment has been minimized.

Show comment
Hide comment
@brezerk

brezerk Nov 3, 2016

Owner

Hi @ezxpro

Not sure how to help. $HOME/.local/share/applications/q4wine/Default/system/ in not created when you install q4wine. It is actually run time data:

This structure is created via Desktop menu plugin and should reflect q4wine's prefix structure.

There is possibility to disable the plugin, and even remove all generated data via 'File -> Options -> Plugins -> Desktop menu'

And even more, q4wine does not have any uninstall target, so this part is managed by your current pkg maintainer and/or pkg manager.

One thing I can do here: document this 'feature'

Owner

brezerk commented Nov 3, 2016

Hi @ezxpro

Not sure how to help. $HOME/.local/share/applications/q4wine/Default/system/ in not created when you install q4wine. It is actually run time data:

This structure is created via Desktop menu plugin and should reflect q4wine's prefix structure.

There is possibility to disable the plugin, and even remove all generated data via 'File -> Options -> Plugins -> Desktop menu'

And even more, q4wine does not have any uninstall target, so this part is managed by your current pkg maintainer and/or pkg manager.

One thing I can do here: document this 'feature'

@ezxpro

This comment has been minimized.

Show comment
Hide comment
@ezxpro

ezxpro Nov 5, 2016

Hello again, Alexey.
Alright, I think documenting this feature could be a good idea 👍
But anyhow I find it interesting that you mentioned that q4wine not having any uninstall target, this should be handled by the package maintainer. (PS: Do you think I should contact this person?)

In addition, it might be interesting to know that after deleting these files at the mentioned location one might still have problems with the overriding of these commands. I asked for help in KDE's forums and found out that this happens because KDE might cache these files. Rebooting the computer or executing kbuildsycoca5 might clean your cache and solve the problem.

ezxpro commented Nov 5, 2016

Hello again, Alexey.
Alright, I think documenting this feature could be a good idea 👍
But anyhow I find it interesting that you mentioned that q4wine not having any uninstall target, this should be handled by the package maintainer. (PS: Do you think I should contact this person?)

In addition, it might be interesting to know that after deleting these files at the mentioned location one might still have problems with the overriding of these commands. I asked for help in KDE's forums and found out that this happens because KDE might cache these files. Rebooting the computer or executing kbuildsycoca5 might clean your cache and solve the problem.

@brezerk

This comment has been minimized.

Show comment
Hide comment
@brezerk

brezerk Nov 7, 2016

Owner

hi @ezxpro

Do you think I should contact this person?

To be honest I am not sure. PKG manager does not supposed to remove any runtime or user-data, only the files which was deployed with the package itself. So I am 99% sure that any request of this kind will be declined...

And for q4wine it is impossible to detect when it is a subject of removal. Even I will implement make uninstall target, this will not help: most of pkg managers does not operate with sources, especially for pkg removal.

Rebooting the computer or executing kbuildsycoca5 might clean your cache and solve the problem.

It is correct. Most of package manager are executing kbuildsycoca5 (if kde was detected on this system) as a part of *.desktop files removal or deployment.

Owner

brezerk commented Nov 7, 2016

hi @ezxpro

Do you think I should contact this person?

To be honest I am not sure. PKG manager does not supposed to remove any runtime or user-data, only the files which was deployed with the package itself. So I am 99% sure that any request of this kind will be declined...

And for q4wine it is impossible to detect when it is a subject of removal. Even I will implement make uninstall target, this will not help: most of pkg managers does not operate with sources, especially for pkg removal.

Rebooting the computer or executing kbuildsycoca5 might clean your cache and solve the problem.

It is correct. Most of package manager are executing kbuildsycoca5 (if kde was detected on this system) as a part of *.desktop files removal or deployment.

@brezerk brezerk added the Known Issue label Oct 9, 2017

@brezerk

This comment has been minimized.

Show comment
Hide comment
@brezerk

brezerk Oct 9, 2017

Owner

Sorry. it took me ages. But I actually documented this behavior: 84bdef0 :)

Thanks for reporting.
Closing, reopen if needed.

Owner

brezerk commented Oct 9, 2017

Sorry. it took me ages. But I actually documented this behavior: 84bdef0 :)

Thanks for reporting.
Closing, reopen if needed.

@brezerk brezerk closed this Oct 9, 2017

@ezxpro

This comment has been minimized.

Show comment
Hide comment
@ezxpro

ezxpro Oct 9, 2017

ezxpro commented Oct 9, 2017

@ezxpro

This comment has been minimized.

Show comment
Hide comment
@ezxpro

ezxpro Oct 9, 2017

ezxpro commented Oct 9, 2017

@brezerk

This comment has been minimized.

Show comment
Hide comment
@brezerk

brezerk Oct 10, 2017

Owner

well.. system and web mostly. last few years I was working as devops engineer. jfyi: http://brezblock.org.ua/contacts/#skills

Owner

brezerk commented Oct 10, 2017

well.. system and web mostly. last few years I was working as devops engineer. jfyi: http://brezblock.org.ua/contacts/#skills

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment