I can confirm this bug too. I believe its somthing to do with the GDM crashing
on logout. checked my syslog and there it shows: "gdm[5748]: segfault at
10bf25b8 eip b77e5635 esp bfdeaca0 error 4"
or occasionally
"gdm[5753]: WARNING: main daemon: Got SIGABRT. Something went very wrong. Going
down
I can confirm the removal of my tv card (Phillips tuner) does indeed fix the
problem. Replacing of the card repeats the problem.
Oh wait latest updates fixes the problem pertinently. :D Great job.
What happens next?
--
internal error failed to initialize HAL
https://bugs.launchpad.net/bugs/2162
Thanks :D - just want to re confirm using the RC install disc - this bug is
still present - and now in live CD, which is probably expected.
Any help will be gladly given.
Please let me know.
Regards,
Matt.
--
internal error failed to initialize HAL
https://bugs.launchpad.net/bugs/216272
You rec
** Attachment added: "syslog"
http://launchpadlibrarian.net/13431908/syslog
--
internal error failed to initialize HAL
https://bugs.launchpad.net/bugs/216272
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
** Attachment added: "messages"
http://launchpadlibrarian.net/13431907/messages
--
internal error failed to initialize HAL
https://bugs.launchpad.net/bugs/216272
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: "hal.log"
http://launchpadlibrarian.net/13431884/hal.log
--
internal error failed to initialize HAL
https://bugs.launchpad.net/bugs/216272
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
** Attachment added: "hal.log"
http://launchpadlibrarian.net/13431882/hal.log
--
internal error failed to initialize HAL
https://bugs.launchpad.net/bugs/216272
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
Apologies you are correct - i forgot sudo.
I will attach all files following this.
The kernel log however was trimmed at the start only for timestamp of
previous day. reattached new full log.
Hope this is OK.
** Attachment added: "kern.log"
http://launchpadlibrarian.net/13431878/kern.log
--
** Attachment added: "kern.log"
http://launchpadlibrarian.net/13406187/kern.log
--
internal error failed to initialize HAL
https://bugs.launchpad.net/bugs/216272
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I have followed the instructions from the hal debugging guid. I will
attach 3 files - hal.log, lshal.txt and kern.log.
I ran the commands:
sudo /etc/init.d/hal stop
sudo hald --verbose=yes --daemon=no 2>&1 | tee /tmp/hal.log
But the logging stopped almost immediately - see attached output.
I the
*** This bug is a duplicate of bug 212271 ***
https://bugs.launchpad.net/bugs/212271
I believe this duplicate status is incorrect. saa7134-alsa module does
not exist in lsmod. tried blacklisting anyway, as proposed in bug report
212271. The error still persisted. Please let me know what furthe
Public bug reported:
Binary package hint: hal
Description:Ubuntu hardy (development branch)
Release:8.04
hal 0.5.11~rc2-1ubuntu6
kernel 2.6.24-16-generic
After logging into Gnome an error message appeared "Internal Error - Failed to
initialize HAL!"
Networking was disabled, and took
12 matches
Mail list logo