By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1164 - kcmshell wineconfig crash because command "wineprefixcreate" not found
Summary: kcmshell wineconfig crash because command "wineprefixcreate" not found
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: non-core programs (show other bugs)
Version: 3.5.13.x [Trinity]
Hardware: Other Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks: 2968
  Show dependency tree / graph
 
Reported: 2012-08-07 11:28 CDT by Francois Andriot
Modified: 2018-08-30 02:52 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Francois Andriot 2012-08-07 11:28:54 CDT 
Hello, running "kcmshell wineconfig" (from package kde-systemsettings) aborts immediatly because it tries to run the non-existing command "wineprefixcreate":

--------------------------
$ kcmshell wineconfig

Pythonize constructor -- pid = 3011
Python interpreter initialized!

Pythonize constructor -- pid = 3011
sh: wineprefixcreate : commande introuvable
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_wineconfig
  File "/usr/lib64/python2.7/site-packages/trinity-guidance/wineconfig.py", line 3525, in create_wineconfig
    return WineConfigApp(parent, name)
  File "/usr/lib64/python2.7/site-packages/trinity-guidance/wineconfig.py", line 118, in __init__
    self.CreateWindowsInstall()
  File "/usr/lib64/python2.7/site-packages/trinity-guidance/wineconfig.py", line 321, in CreateWindowsInstall
    winewrite.SetDriveMappings(drives)
  File "/usr/lib64/python2.7/site-packages/trinity-guidance/winewrite.py", line 60, in SetDriveMappings
    SetShellLinks(drives[26:])
  File "/usr/lib64/python2.7/site-packages/trinity-guidance/winewrite.py", line 63, in SetShellLinks
    existingshelllinks = os.listdir(wineread.winepath + "/dosdevices/c:/windows/profiles/" + os.environ['USER'])
OSError: [Errno 2] Aucun fichier ou dossier de ce type: '/home/albator/.wine/dosdevices/c:/windows/profiles/albator'
error: *** runFunction failure
;
--------------------------

It looks like this command was deprecated and removed from Wine.
http://forum.winehq.org/viewtopic.php?t=1004

It seems that we should now be using "wineboot" instead.
Comment 1 Francois Andriot 2012-08-07 16:30:57 CDT 
Oops, the wineconfig module is provided by kde-guidance, not kde-systemsettings.

BTW there are other issues with this module:

1) Recent wine versions create windows user profile under "c:\users" instead of "c:\windows\profiles". But there are several hardcoded path to the latter in the wineconfig module.

2) The module determines the windows folders related to user profile by parsing the windows registry. It exports the registry key name
HKEY_USERS\.Default\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
using "regedit /E", then parses the resulting text file to match "variable=value" lines.
Alas, in recent wine (and windows) versions, the registry values in that key are of type REG_EXPAND_SZ, not REG_SZ, and then regedit exports them as hexadecimal values, not string values. So, the exported file cannot be parsed directly as clear text.

See files wineconfig/wineread.py and wineconfig/winewrite.py in kde-guidance.
Comment 2 Michele Calgaro 2018-07-29 04:16:34 CDT 
tdecmshell wineconfig has issues. Need to test both with tde-guidance installed (wineconfig available) and not installed (wineconfig not available).
Definitely some work to do here.