You are not logged in.
Hello ,
If I want to startx the computer begins and trows me back to the login part.
I can see that I get a cannot open display message.
I happens a root and as normal user.
When starting up I see a message that hal has failed.
Roelof
Last edited by roelof (2009-08-10 07:10:09)
Offline
You can find an error log at /var/log/Xorg.0.log, so you can see what causes X to not start properly.
Did you read through the HAL Wiki article?
Offline
Yep, I read that article.
When i do exec openbox-session I get this message:
waiting for x server to shutdown error setting MTTR (base=0xd0000000, size=0x800000, type=1 Invalid argument (22)
/var/log/Xorg.0.log doesn't have any errors only warnings.
Roelof
Roelof
Offline
Hal and D-bus are working , are you in group's dbus and hal ?
Shell Scripter | C/C++/Python/Java Coder | ZSH
Offline
What's in the DAEMONS list in rc.conf?
All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.
Offline
I've never heard of the need for the user to be in the DBUS and HAL groups. Is that correct? I have never added any of my users to those groups.
All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.
Offline
I've never heard of the need for the user to be in the DBUS and HAL groups. Is that correct? I have never added any of my users to those groups.
You need it
Add user to group hal and dbus
Shell Scripter | C/C++/Python/Java Coder | ZSH
Offline
loafer wrote:I've never heard of the need for the user to be in the DBUS and HAL groups. Is that correct? I have never added any of my users to those groups.
You need it
Add user to group hal and dbus
I doubt this. These are my user's groups:
bp:~$ cat /etc/group | grep bp
disk::6:root,bp
lp::7:daemon,bp
wheel::10:root,bp
mail::12:bp
games::50:bp
video:x:91:bp
audio::92:bp,pulse
optical::93:bp,hal
floppy:x:94:bp,hal
storage:x:95:bp,hal
power:x:98:bp
pulse-access:x:131:bp
bp:x:134:bp
bp:~$ cat /etc/group | grep hal
optical::93:bp,hal
floppy:x:94:bp,hal
storage:x:95:bp,hal
hal:x:82:
bp:~$ cat /etc/group | grep dbus
dbus:x:81:
The OT's problems must have other causes.
To know or not to know ...
... the questions remain forever.
Offline
Hello,
The user is only in the group users.
And my rc.conf Deamons list is : DEAMONS = (syslog-ng network netfs dbus hal)
Roelof
Offline
You really do need to use the Wiki:
For D-Bus and HAL to be of any practical use, local user accounts should be members of the following groups: optical and storage
All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.
Offline
Oke,
I changed it but no luck.
I get now the following message :
Failed to open display from the display variable.
And when I do echo $display then a empty rulle,.
After I do export DISPLAY=0:0 nothing changed.
Roelof
Last edited by roelof (2009-08-09 13:09:11)
Offline
Do yo have dbus installed?
pacman -Q dbus
If not, install it with
pacman -S dbus
Offline
yep,
pacman -Q dbus gives dbus-1.2.14-1
Roelof
Offline
Hello,
The user is only in the group users.
And my rc.conf Deamons list is : DEAMONS = (syslog-ng network netfs dbus hal)Roelof
You usually don't need expressly start dbus, this will be done by hal. But hal must be started as soon as possible as it provides the interfaces for the other daemons., thus this should probably work:
DAEMONS = (syslog-ng hal network netfs)
And if you ever want to speed up the boot by backgrounding daemons: Never background hal (and syslog-ng btw.)!
Final rant, it's DAEMONS not DEAMONS. (If it wasn't just only a typo...)
To know or not to know ...
... the questions remain forever.
Offline
Oke,
I changed that but still openbox can't open the display
and it was a typo.
Roelof
Offline
Hello,
I have looked into it.
There seems to be a problem with Nvidia drivers but my problems started before I downloaded and installed the drivers from the nvidia site.
Anyone any tips
Roelof
Offline
Hello,
I have looked into it.
There seems to be a problem with Nvidia drivers but my problems started before I downloaded and installed the drivers from the nvidia site.
Anyone any tipsRoelof
Then Try xf86-video-nv
Shell Scripter | C/C++/Python/Java Coder | ZSH
Offline
Oke,
I have installed it but still I get the message :
Openbox message : Failed to open display from the display variable.
Roelof
Offline
When you startx you got the same message?
Shell Scripter | C/C++/Python/Java Coder | ZSH
Offline
nope,
Then the screen becomes black and after some time trows me back at the prompt with no messages and no errors in the xorg.0.log
Only 2 warnings.
Roelof
Offline
What warnings?
Shell Scripter | C/C++/Python/Java Coder | ZSH
Offline
The first :
AllowEmptyInput is on, devices using drivers "kdb", "mouse' and 'vmouse' will be disabled.
Second :
Open ACPI failed (no such file)
Roelof
Offline
Add to your xorg.conf:
Section "ServerFlags"
Option "AllowMouseOpenFail" "True"
Option "AutoAddDevices" "False"
EndSection
Shell Scripter | C/C++/Python/Java Coder | ZSH
Offline
Hello,
I changed that and i get a lost of errors when i do startx
Failed to load module "kdb" (module does not exist,0)
Failed to load module "mouse" (module does not exist,0)
Failed to load module "kbd" (module does not exist,0)
No input Device matching kbd
Failed to load module "mouse"
No input Device matching mouse
Config/hal :NewInputDeviceReguest failed (8)
Config/hal :NewInputDeviceReguest failed (8)
Config/hal :NewInputDeviceReguest failed (8)
And when i do startx as root twm starts up and locks up.
Roelof
Offline
It will fail ... it's called "kbd" not "kdb".
All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.
Offline