[opensuse] Leap 421 to 423 upgrade problem - udev
I just upgraded my last 421 to 423. Kept the LXDE (gtk) desktop. Not so smooth upgrade. I didn't uninstall a proprietary driver first because: what could go wrong :-D Answer: ha ha ha. Hours to figure out what was going on and then to fix it. And the needed proprietary uninstaller was, of course, on an inaccessible LUKS drive. But anyway, now fixed. Another problem, not fixed: everything seems to work fine but the log is filled with thousands of the following lines (except the first line, which isn't repeated). The lines continue to be generated after the system is running. systemd[1]: Started udev Kernel Device Manager. systemd-udevd[1079]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory systemd-udevd[1077]: Process 'socket:@/org/freedesktop/hal/udev_event' failed with exit code 2. systemd-udevd[1086]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory systemd-udevd[1077]: Process 'socket:@/org/freedesktop/hal/udev_event' failed with exit code 2. Anyone know what these messages mean? Thanks. Ralph -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I should have googled BEFORE posting this known problem... I had 'hal'
installed. Uninstalling 'hal' apparently ends the messages.
Sorry for the noise.
Ralph
On Wed, 13 Dec 2017 02:09:09 -0600
listreader
I just upgraded my last 421 to 423. Kept the LXDE (gtk) desktop. Not so smooth upgrade. I didn't uninstall a proprietary driver first because: what could go wrong :-D Answer: ha ha ha. Hours to figure out what was going on and then to fix it. And the needed proprietary uninstaller was, of course, on an inaccessible LUKS drive. But anyway, now fixed.
Another problem, not fixed: everything seems to work fine but the log is filled with thousands of the following lines (except the first line, which isn't repeated). The lines continue to be generated after the system is running.
systemd[1]: Started udev Kernel Device Manager.
systemd-udevd[1079]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory
systemd-udevd[1077]: Process 'socket:@/org/freedesktop/hal/udev_event' failed with exit code 2.
systemd-udevd[1086]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory
systemd-udevd[1077]: Process 'socket:@/org/freedesktop/hal/udev_event' failed with exit code 2.
Anyone know what these messages mean? Thanks.
Ralph
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2017-12-13 at 02:37 -0600, listreader wrote:
I should have googled BEFORE posting this known problem... I had 'hal' installed. Uninstalling 'hal' apparently ends the messages.
'hal' causes problems, yes. I taboed it, it is on the KDE3 repo, I think. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAloxJpIACgkQtTMYHG2NR9WoJQCeIVyKLaFDKbNRBkEpxDFWWb9o N94AmgLDRQnbSNjtckGLA/q/gQi5Zjn7 =jzQY -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 13 Dec 2017 14:09:38 +0100 (CET)
"Carlos E. R."
On Wednesday, 2017-12-13 at 02:37 -0600, listreader wrote:
I should have googled BEFORE posting this known problem... I had 'hal' installed. Uninstalling 'hal' apparently ends the messages.
'hal' causes problems, yes. I taboed it, it is on the KDE3 repo, I think.
I had it installed in 421 because blueman required it and blueman was the only way I could get bluetooth working with that machine's dongle. Without 'hal' on that machine under 423 now bluetooth is dead again. BT keyboard and dongle see each other but a keycode never gets generated from the system/dongle, or at least it's never displayed on screen. Already spent too much time on it. Maybe I'll just put 'hal' back and ignore the log messages... Ralph -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2017-12-13 at 16:34 -0600, listreader wrote:
On Wednesday, 2017-12-13 at 02:37 -0600, listreader wrote:
I should have googled BEFORE posting this known problem... I had 'hal' installed. Uninstalling 'hal' apparently ends the messages.
'hal' causes problems, yes. I taboed it, it is on the KDE3 repo, I think.
I had it installed in 421 because blueman required it and blueman was the only way I could get bluetooth working with that machine's dongle. Without 'hal' on that machine under 423 now bluetooth is dead again. BT keyboard and dongle see each other but a keycode never gets generated from the system/dongle, or at least it's never displayed on screen. Already spent too much time on it. Maybe I'll just put 'hal' back and ignore the log messages...
You'd better ask then how to handle bluetooth, and in which desktop or before desktop. I currently only use an audio headset on my laptop. XFCE no longer handles BT itself, so I have to do it via terminal, and it is not nice. I still don't know the exact command and in which orders to do, I have to juggle a little. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAloycbAACgkQtTMYHG2NR9WE2wCfVbbKQ2wxPSEa0c5QxWSPDtaB RIEAoI4MWlZGmPYEZAf8c4rKxM2alfDJ =5vD6 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Carlos E. R.
-
listreader