LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Wine X Server Error (https://www.linuxquestions.org/questions/slackware-14/wine-x-server-error-492550/)

duryodhan 10-15-2006 05:49 AM

Wine X Server Error
 
Hey,
I just installed wine on Slackware. It is givin followin error :


err:imagelist:ImageList_ReplaceIcon no color!
wine: Unhandled page fault on write access to 0x003ffd80 at address 0x6113d103 (thread 0009), starting debugger...
wine: '/root/.wine' created successfully.
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.


What does this mean? How do I fix this?

dive 10-15-2006 09:19 AM

You are running wine as root and running X as user. DISPLAY variable is not set.

If you really must run wine as root (could be risky) then put 'export DISPLAY=:0.0' in /root/.bash_profile and 'xhost +local:' in your users .bash_profile. Then log in again.

cwizardone 03-07-2007 02:52 PM

Quote:

Originally Posted by dive
You are running wine as root and running X as user. DISPLAY variable is not set.
If you really must run wine as root (could be risky) then put 'export DISPLAY=:0.0' in /root/.bash_profile and 'xhost +local:' in your users .bash_profile. Then log in again.

I get a similar error message trying to run WINE as root with Slackware 11 and kernel 2.6.18.
Please see below:
****************

err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
err:imagelist:ImageList_ReplaceIcon no color!
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
************************

However, I cannot find either of the files to which you refer to above.
I've found a .bash_history file, but not .bash_profile or users .bash_profile.
Can you please direct me to the proper locations?

I really don't want to run as a user. I've tried that and it drives me crazy having to switch back and forth or sign on and off inside a terminal window while logged on as a user.
I would rather take the risk of running as root.
Thanks.
;)

H_TeXMeX_H 03-07-2007 04:21 PM

Hmmmm ... you're running wine as root ... better call the nearest Asylum fast :eek:

XGizzmo 03-07-2007 05:31 PM

~/.bash_profile and for that matter ~/.bashrc does not exist by default. It is up to the user to create it. That said I can think of no good reason you should be running wine as root. There could be times when you want root to use your display for something and the commands that have been shown to you will allow just that, but I would never add them where they are always loaded.

cwizardone 03-07-2007 07:22 PM

Quote:

Originally Posted by H_TeXMeX_H
Hmmmm ... you're running wine as root ... better call the nearest Asylum fast :eek:

I keep hearing this, but humor me, please, and tell me why?
I'll ask the same question of you, XGizzmo, why is running as root such a "taboo" especially, it seems, when running WINE?
Thanks.

duryodhan 03-07-2007 07:59 PM

Doing anything in Linux as root is taboo!!! never ever do that ... always use normal user powers and super user only if you absolutely must.

cwizardone 03-07-2007 08:06 PM

Quote:

Originally Posted by duryodhan
Doing anything in Linux as root is taboo!!! never ever do that ... always use normal user powers and super user only if you absolutely must.

I really do appreciate that you took the time to respond, but the question is, why?
Why should the owner of the system not run as root?
:scratch:
Thanks.

H_TeXMeX_H 03-07-2007 08:39 PM

Because a single bad command by root will completely fubar / snafu / f**k your whole system ... unless that's what you want, I wouldn't run anything as root unless absolutely necessary.

Wine (a crappy, beta, Window$ API port) should definitely NOT be run as root. It messes things up even when run as a regular user ... imagine what it can do as root :eek:

folkenfanel 03-07-2007 08:59 PM

running as root...
 
is like playing with a knife. Like cleaning your fingernails with a knife... Even if you are skilled enough to do that, it is a dangerous situation.

H_TeXMeX_H 03-07-2007 10:03 PM

or playing Russian roulette ... really.


All times are GMT -5. The time now is 03:53 AM.