Wineservers require separate instances for separate prefixes, and Wine
has been moving towards having apps installed into discreet prefies
these days (eg winetricks), so I no longer think this is worth doing.
** Changed in: wine (Ubuntu)
Status: Triaged = Won't Fix
--
You received this
Is that any different from the current situation? Surely even now when
you upgrade Wine you are still required to log out before the new
wineserver starts.
--
Windows programs loading too slow into wine.
https://bugs.launchpad.net/bugs/352025
You received this bug notification because you are a
So, manually running wineserver -p greatly improves startup speed of
all apps, but it takes about 6.8 megs of memory. I think this may be a
worthy tradeoff if the user has a ~/.wine directory.
--
Windows programs loading too slow into wine.
https://bugs.launchpad.net/bugs/352025
You received
However, this makes upgrade of the Wine package itself a bit more
complicated - we'll need to ask the user to logout/login whenever they
update Wine so that the old wineserver process can die; if we try to
kill it we might kill a running Wine app
--
Windows programs loading too slow into wine.
Would it be reasonable to (give the option to) start the wineserver
process on login? I find it's only slow to start the first Wine app
after logging in because the wineserver process is starting. Perhaps
that option could be part of winecfg, something like a Start Wine when
GNOME starts checkbox.
Running wineserver -p at startup does the trick. I'm going to
experiment with including this into the upcoming wine-support package
that will detect whether or not there is a current ~/.wine prefix at
startup anyway.
** Changed in: wine (Ubuntu)
Assignee: (unassigned) = Scott Ritchie
Agreed, the program needs to either load quickly, some feedback needs to
get to the user if the program will take a while, or at the very least
it shouldn't spawn two copies if told to open a second time while the
original is still loading. I'm not sure where the best place to solve
this is,
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/24550253/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/24550254/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/24550255/ProcStatus.txt
--
Windows
