> I'm running 185.18.04 at the moment with Jaunty, and it is still up
after 2 days.
And it died this morning. I did not find anything in the X logs ...
unless you count the following notice (normal):
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable
AllowEmptyInput.
The reason I mention it is that I also found a litany of hourly GPF
faults in syslog:
# grep -F "Call Trace" syslog*
syslog:May 6 09:19:24 jaunty kernel: [ 741.174888] Call Trace:
syslog.0:May 6 04:56:05 jaunty kernel: [299116.995954] Call Trace:
syslog.0:May 6 04:56:26 jaunty kernel: [299138.010140] Call Trace:
syslog.0:May 6 04:56:32 jaunty kernel: [299144.252919] Call Trace:
syslog.0:May 6 06:43:27 jaunty kernel: [305559.339189] Call Trace:
syslog.0:May 6 07:47:24 jaunty kernel: [309396.113391] Call Trace:
syslog.0:May 6 08:33:12 jaunty kernel: [312144.386665] Call Trace:
syslog.0:May 6 08:33:20 jaunty kernel: [312152.455742] Call Trace:
The first one occurs right after to a message saying: "May 6 04:56:05
jaunty NetworkManager: <info> HAL disappeared"
HAL disappeared? Could these problems all be related to hald aborting,
thus removing the input devices?
I am attaching these hourly call traces.
** Attachment added: "Extracted Call Traces from syslog"
http://launchpadlibrarian.net/26393464/call-traces
--
Jaunty X highly unstable
https://bugs.launchpad.net/bugs/359245
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
