I've got the same problem with a locally authenticated user, but with a
CIFS home dir in fstab (_netdev option).
My present workaround is:
sudo /etc/init.d/gdm stop
rm -rf .pulse
sudo /etc/init.d/gdm start
But it has to be done every single time I turn on the machine.
A more permanent workaround
I have no idea what is going on, I just know HAL won't start.
This is the dump from the syslog when I try to launch HAL manually with sudo
hald --daemon=yes --verbose=yes --use-syslog :
Jul 23 01:12:03 thechair hald[8878]: 01:12:03.164 [I] hald.c:669: hal 0.5.11rc2
Jul 23 01:12:03 thechair hald[
Ok, it looks like it has gone away.
I tried several times repeating the apt-get upgrade and also stopping HAL from
/etc/init.d/hal, but without any effect. Stopping HAL doesn't seem possible,
because "ps -A | grep hald" still lists it.
So I just killed it all "sudo killall hald", and then restar
Problem still exists in Jaunty (9.04) with CIFS mounts.
Renaming the links from "S" to "K" solved it for me (maintaining the same order
number).
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because
Just adding the output of hald that I found in my syslog (when doing
"sudo hald --daemon=yes --verbose=yes --use-syslog"):
Oct 21 16:46:39 thechair hald[10155]: 16:46:39.371 [i] hald.c:529: hal 0.5.9.1
Oct 21 16:46:39 thechair hald[10155]: 16:46:39.371 [i] hald.c:538: Will
daemonize
Oct 21 16:4
Good news, folks!
Got my system working!
Did "sudo mv /var/cache/hald/fdi-cache~ /var/cache/hald/fdi-cache" and
restarted the PC, and now it looks alright!!!
See bug #139155 for more info.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification becaus
lcampagn: thanks for the tip, it solved my system!
sudo mv /var/cache/hald/fdi-cache~ /var/cache/hald/fdi-cache
--
hald will not start
https://bugs.launchpad.net/bugs/139155
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubunt
Actualy, the correct way to do it seems to be:
sudo /usr/lib/hal/hald-generate-fdi-cache
(see bug #146812)
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs m
Actualy, the correct way to do it seems to be:
sudo /usr/lib/hal/hald-generate-fdi-cache
(see bug #146812)
--
hald will not start
https://bugs.launchpad.net/bugs/139155
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bug
Same problem here, after Feisty to Gutsy upgrade.
No NetworkManager, hald won't start, exit menu options take well over 1 minute
to pop up.
See complete description here: http://ubuntuforums.org/showthread.php?t=583940
Reinstalling Hal and Dbus makes no difference.
Reordering init script links als
Public bug reported:
Binary package hint: update-manager
Upgrading a Mac G3 from Ubuntu 6.06.2 to 8.04 fails at the beginning
(prerequisites).
Command:
gksu "update-manager -d"
Error (from /var/log/dist-upgrade/main.log):
'Failed to fetch
http://ports.ubuntu.com/ubuntu-ports/dists/dapper-bac
The error also appears as:
ERROR Can not find backport 'release-upgrader-apt'
in the dist-upgrade log.
I can't get the logs out of that machine without great effort. Let me
know if you absolutely need them.
--
Dapper-to-Hardy upgrade fails on PowerPC (prerequisite dapper-backports missing)
http
Found the workaround.
Add to the /etc/apt/sources.list:
deb http://archive.ubuntu.com/ubuntu dapper-backports main/debian-installer
Then the upgrader works as intended.
Remove the line after the upgrade (just in case).
--
Dapper-to-Hardy upgrade fails on PowerPC (prerequisite dapper-backports m
I also have this same exact problem (with the same package and system versions).
And my system is also a PowerPC. Could that be related?
--
package openoffice.org-writer2latex 0.5-6 failed to install/upgrade:
Unterprozess post-installation script gab den Fehlerwert 1 zurück
https://bugs.launchpa
Public bug reported:
Binary package hint: linux-source-2.6.17
The Ata-over-Ethernet kernel module doesn't discover the available
"blades" and therefore it is not possible to mount any block devices
that where exported via the "vblade" server.
Actually, nothing works the way it should: the udev f
** Description changed:
Binary package hint: linux-source-2.6.17
The Ata-over-Ethernet kernel module doesn't discover the available
"blades" and therefore it is not possible to mount any block devices
that where exported via the "vblade" server.
Actually, nothing works the way it s
** Summary changed:
- AoE module doesn't work at all
+ AoE module doesn't work with vblade
** Description changed:
Binary package hint: linux-source-2.6.17
The Ata-over-Ethernet kernel module doesn't discover the available
"blades" and therefore it is not possible to mount any block dev
17 matches
Mail list logo
