Summary: | xserver 1.5.3 hang after the start | ||
---|---|---|---|
Product: | xorg | Reporter: | Denis Smirnov <detanator> |
Component: | Server/General | Assignee: | Xorg Project Team <xorg-team> |
Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | major | ||
Priority: | high | ||
Version: | 7.4 (2008.09) | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Denis Smirnov
2009-01-04 05:10:45 UTC
> I'v got hal and slim (graphical login manager) in parallel start as service. > But, slim started earlier then hal (who try load dbus as dep). that's a bug, but not one in X. you need to make sure hal is started before X. > So x server have hanged and i had reported about it (but bug seems > closed). > what do you mean by "hanged"? please attach a full X log. (In reply to comment #1) > > I'v got hal and slim (graphical login manager) in parallel start as service. > > But, slim started earlier then hal (who try load dbus as dep). > > that's a bug, but not one in X. you need to make sure hal is started > before X. Ok, i didn't say that is bug, but i couldn't find ANY info about proper queue loading daemons for working xserver. (version 1.3 load perfectly, because doesn't use hal) > > So x server have hanged and i had reported about it (but bug seems > > closed). > > > what do you mean by "hanged"? please attach a full X log. > I'v describe it here http://bugs.freedesktop.org/show_bug.cgi?id=18595 I don't quite understand the point of this bugreport. If the server still hangs (as described in Bug 18595), please reopen that bug. HAL is a compile-time and run-time default dependency, so unless you explicitly disable the use of HAL (search the man page for AutoAddDevices), you must start HAL before running X. (In reply to comment #3) > I don't quite understand the point of this bugreport. agreed. closing as invalid. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.