01-08-2012
Wine is not working in fedora 15
Hi Frnds
I dont know where to post thread for fedora so here i am posting
I have fedora 15 with kernel-2.6.41.4-1.fc15.x86_64.It was previously kernel-2.6.40.6-0.fc15.x86_64 which i updated today through Yum.After than i restarted with new kernel and installed wine-1.3.35-1.fc15.x86_64 through yum.Wine configuration windows is opening and i can add application there.Now the problem is my Wine desktop is not opening.It opens for 5 sec and then disappear.I want to install Vmware on that.I tried to install vmware on my fedora 15 aslo but its showing following error even downloaded header also.
"kernel header for version ..... were not found.If you installed them in a non-default path you can specify the path below"
Please help me any of the above case as i want to run vmware on my fedora 15.
Thank you
Last edited by Vaibhav.T; 01-08-2012 at 04:24 PM..
Reason: Not showing screen shot of error so i am writing down the error
8 More Discussions You Might Find Interesting
1. Ubuntu
I have tried befre but nothing works out proprly.
I have Ubuntu
I try to Install Fedora Core 1.
When Fedora Cora is finished Installing It doesnt show Ubuntu on Grub.
If I re-install Ubuntu and put grub on then Fedora wont show.
I also have Windows 98 but that is always on the list as DOS or... (5 Replies)
Discussion started by: shade11
5 Replies
2. Linux
Hi everyone,
I hope this question goes here. Anyways, I have a unique situation where my friend's comp has Fedora installed and wants to add Win XP as a dual boot without formatting the drive. Is it possible to create a partition on the current hard drive and then install win xp? I couldn't find... (4 Replies)
Discussion started by: eltinator
4 Replies
3. Linux
When I access a samba share from command line using gvfs-mount, I can not see anything in ~/.gvfs/ directory. See below:
ajitabhp:$ gvfs-mount smb://iomega-dstore/music/
ajitabhp:$ echo $?
0
ajitabhp:$ ls -l ~/.gvfs/
total 0
ajitabhp:$ ps -ef|grep gvfsd-smb
ajitabhp 10896 1 0 11:28 ? ... (2 Replies)
Discussion started by: ajitabhpandey
2 Replies
4. IP Networking
I installed F12 around the time it was released and it picked up my wireless card and worked like a charm.....Suddenly last week everything stopped working and I receive what appears to be a driver error when wlan0 tries to load.
Error for wireless request "Set Mode" (8B06) :
SET failed on... (1 Reply)
Discussion started by: woodson2
1 Replies
5. Linux
I am running fedora 11 as a virtual machine on vmware.
when i open software updates they do not start.neither can new software be installed.but i am getting lan connection as firefox is working.have changed system proxy too.
the directory /etc/yum.repos.d/ is not empty.this is output of
ls... (2 Replies)
Discussion started by: linuxstudent
2 Replies
6. Red Hat
I will shortly be adding a fedora flavor to my devel box. I currently have XP (installed first on an ssd), ubuntu 10.04 (installed second on the first partition of a platter drive), and I want to add either Cent or SL on the second partition of the platter drive. I will probably also want to... (0 Replies)
Discussion started by: LMHmedchem
0 Replies
7. UNIX for Advanced & Expert Users
I am having trouble getting my jre to work. I have uninstalled and reinstalled it several times but that is not working. I have setup the firefox symlink.
sudo ln -s /usr/java/jre1.7.0_21/lib/i386/libnpjp2.so
I have tried to follow these instructions.
... (4 Replies)
Discussion started by: cokedude
4 Replies
8. Fedora
Hi,
while installing/updating package using yum I am getting (repomd.xml) error
# yum list
Loaded plugins: langpacks, presto, refresh-packagekit
http://mirror.cse.iitk.ac.in/fedora-archive/fedora/linux/fedora/linux/releases/16/Everything/x86_64/os/repodata/repomd.xml: HTTP Error 404 -... (12 Replies)
Discussion started by: muzaffar.k
12 Replies
LEARN ABOUT SUSE
wineserver
WINESERVER(1) Windows on Unix WINESERVER(1)
NAME
wineserver - the Wine server
SYNOPSIS
wineserver [options]
DESCRIPTION
wineserver is a daemon process that provides to Wine roughly the same services that the Windows kernel provides on Windows.
wineserver is normally launched automatically when starting wine(1), so you shouldn't have to worry about it. In some cases however, it can
be useful to start wineserver explicitly with different options, as explained below.
OPTIONS
-d[n], --debug[=n]
Set the debug level to n. 0 means no debugging information, 1 is the normal level, and 2 is for extra verbose debugging. If n is
not specified, the default is 1. The debug output will be sent to stderr. wine(1) will automatically set the debug level when start-
ing wineserver if the +server option is set in the WINEDEBUG variable.
-f, --foreground
Make the server remain in the foreground for easier debugging, for instance when running it under a debugger.
-h, --help
Display a help message.
-k[n], --kill[=n]
Kill the currently running wineserver, optionally by sending signal n. If no signal is specified, sends a SIGINT first and then a
SIGKILL. The instance of wineserver that is killed is selected based on the WINEPREFIX environment variable.
-p[n], --persistent[=n]
Specify the wineserver persistence delay, i.e. the amount of time that the server will keep running when all client processes have
terminated. This avoids the cost of shutting down and starting again when programs are launched in quick succession. The timeout n
is in seconds, the default value is 3 seconds. If n is not specified, the server stays around forever.
-v, --version
Display version information and exit.
-w, --wait
Wait until the currently running wineserver terminates.
ENVIRONMENT VARIABLES
WINEPREFIX
If set, the content of this variable is taken as the name of the directory where wineserver stores its data (the default is
$HOME/.wine). All wine processes using the same wineserver (i.e.: same user) share certain things like registry, shared memory and
kernel objects. By setting WINEPREFIX to different values for different Wine processes, it is possible to run a number of truly
independent Wine sessions.
WINESERVER
Specifies the path and name of the wineserver binary that will be launched automatically by wine. If not set, wine will try to load
/usr/bin/wineserver, and if this doesn't exist it will then look for a file named wineserver in the path and in a few other likely
locations.
FILES
~/.wine
Directory containing user specific data managed by wine.
/tmp/.wine-uid
The directory containing the server Unix socket and the lock file. These files are created in a subdirectory generated from the
WINEPREFIX directory device and inode numbers.
AUTHORS
The original author of wineserver is Alexandre Julliard. Many other people have contributed new features and bug fixes. Please check the
file Changelog in the Wine distribution for the complete details.
BUGS
If you find a bug, please submit a bug report at http://bugs.winehq.org. <http://bugs.winehq.org>
AVAILABILITY
wineserver is part of the Wine distribution, which is available through WineHQ, the Wine development headquarters, at
http://www.winehq.org/. <http://www.winehq.org/>
SEE ALSO
wine(1).
Wine 1.2-rc6 October 2005 WINESERVER(1)