@lct: If you run apt-get autoremove, is hal uninstalled?
I can only *assume* it is *not*.
I always use autoremove after upgrades (I upgrade via apt-get) and the
situation with tons and tons of warning messages persisted up till now,
that is, until I explicitly checked for existing bug,
tried
This is crazy and scary.
Affects me too. The system is hardly a year old, first Wheezy then
dist-upgraded to Testing.
Hal was NOT manually installed.
I know what prehistoric artifact HAL is, but the thing is - it was pulled as
dependency at some regular update.
Indeed, the hal somehow was in
Am 30.01.2014 16:26, schrieb lct:
This is crazy and scary.
Affects me too. The system is hardly a year old, first Wheezy then
dist-upgraded to Testing.
Hal was NOT manually installed.
I know what prehistoric artifact HAL is, but the thing is - it was
pulled as dependency at some regular
On Thu, Jan 30, 2014 at 05:51:44PM +0100, Michael Biebl wrote:
Am 30.01.2014 17:32, schrieb Martin Pitt:
Michael Biebl [2014-01-30 17:24 +0100]:
c/ Add Breaks: hal to udev so it is automatically uninstalled on Linux.
Since hal on Linux is no longer really functional and actually broken by
Hi David,
thanks for your reply!
Am 30.01.2014 21:39, schrieb David Kalnischkies:
On Thu, Jan 30, 2014 at 05:51:44PM +0100, Michael Biebl wrote:
But in this case not kicking out hal forcefully leads to those
scary boot messages (and already quite a few duplicate bug reports).
Once this udev
Package: hal
Version: 0.5.14-8
Followup-For: Bug #717613
Dear Maintainer,
happens also to me, on Debian Testing amd64.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture:
Am 15.01.2014 21:33, schrieb Ilario Gelmetti:
Package: hal
Version: 0.5.14-8
Followup-For: Bug #717613
Dear Maintainer,
happens also to me, on Debian Testing amd64.
No need to confirm. This is a known issue and won't be fixed.
Uninstall hal, it's no longer needed, obsolete and dead.
Package: systemd
Version: 204-1
Severity: normal
After upgrading to systemd 204-1 (experimental) these messages appear during
boot and I wonder how the wrong path is being constructed. Yet the system seems
to work well.
[ 10.959445] systemd[1]: Job setserial.service/start deleted to break
reassign 717613 src:hal
forcemerge 705489 717613
thanks
Am 23.07.2013 02:49, schrieb pothos:
[ 12.848604] systemd-udevd[2054]: failed to execute
'/lib/udev/socket:@/org/freedesktop/hal/udev_event'
'socket:@/org/freedesktop/hal/udev_event': No such file or directory
[ 12.953663]
9 matches
Mail list logo