LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > SUSE / openSUSE
User Name
Password
SUSE / openSUSE This Forum is for the discussion of Suse Linux.

Notices


Reply
  Search this Thread
Old 02-04-2018, 09:37 PM   #1
André7785
LQ Newbie
 
Registered: Mar 2009
Distribution: Open SuSE 13.2, Leap 42.1
Posts: 19

Rep: Reputation: 0
Question openSuSE 13.2: journalctl -b unveils startup error


In reviewing the startup with
Code:
journalctl -b
I obtained a bunch of subsequent identical error messages saying
Code:
janv. 04 15:58:41 LT7 systemd-udevd[755]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No file found
without any further consequences visible for normal user
To find out what there was going on, I fabricated an empty file with suitable access rights, thus obtaining
Code:
févr. 04 15:58:41 LT7 systemd-udevd[755]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': Exec format error
so I assume this executable is somehow needed normally by one of the demon scripts upward this branch of the directory tree, where database-extracts of configuration parameters and script-templates reside.

This kind of reverse-unveiling the systemd labyrinth is at present an academic exercise for me, so I would appreciate the hint of someone, who has absolved this learning pathway:
a) what's the purpose of this executable?
b) has its missing other consequences than abovementioned (those bunches of subsequent nearly identical error messages)?
Thanks in advance
 
Old 02-04-2018, 10:12 PM   #2
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,837

Rep: Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148
Well hal has been gone since openSUSE 11.3! (Not to mention this version being well past EOL). You could try removing hal and see how that goes, but YMMV. Any reason why your still running such an old version?
 
Old 02-05-2018, 10:58 AM   #3
André7785
LQ Newbie
 
Registered: Mar 2009
Distribution: Open SuSE 13.2, Leap 42.1
Posts: 19

Original Poster
Rep: Reputation: 0
Lightbulb The operating system on this Laptop ...

... is oSuse 13.2 and my ability is far away from pasting depreciated hal code into a system image or smuggle it somehow into boot procedure. I'm glad enough to keep this one running with all these minor issues occurring when hardware vendors dislike supporting users with this os.
Quote:
Originally Posted by ferrari View Post
Well hal has been gone since openSUSE 11.3! (Not to mention this version being well past EOL). You could try removing hal and see how that goes, but YMMV. Any reason why your still running such an old version?
I only could speculate about some package dependencies which zypper had tried to resolve in this manner, but if this monument doesn't disturb otherwise I'll try to ignore its moping in the assumtion "YMMV" means that's on my own responsibility doing things without understanding the consequences. Thanks for elucidation.
 
Old 02-05-2018, 12:17 PM   #4
petelq
Member
 
Registered: Aug 2008
Location: Yorkshire
Distribution: openSUSE(Leap and Tumbleweed) and a (not so) regularly changing third and fourth
Posts: 629

Rep: Reputation: Disabled
Quote:
Originally Posted by André7785 View Post
... but if this monument doesn't disturb otherwise I'll try to ignore its moping in the assumtion "YMMV" means that's on my own responsibility doing things without understanding the consequences. Thanks for elucidation.
It's not a case of not understanding consequences. 13.2 is unsupported - no updates, no security updates. Newer versions with newer kernels are supporting more hardware and you don't necessarily need the support of manufacturers when you have LQ to turn to.
The current stable opensuse is 42.3. You should try it.
 
Old 02-05-2018, 02:55 PM   #5
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,837

Rep: Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148
Further to Pete's sensible advice (which I also nearly included in my initial reply), you could try testing the current Leap 42.3 version. GeckoLinux offer a live distro static edition based on openSUSE Leap 42.3 which can run from DVD or USB, and will give a reasonable indication of how well it plays with your laptop. Some graphics and wireless hardware do require proprietary drivers to be installed to function, but there are lots of guides and threads dealing with that topic. Support from these forums (with its knowledgeable members) is always available as well
 
Old 02-08-2018, 05:09 PM   #6
André7785
LQ Newbie
 
Registered: Mar 2009
Distribution: Open SuSE 13.2, Leap 42.1
Posts: 19

Original Poster
Rep: Reputation: 0
Thanks both ferrary and petelq for their advice...

...and the latest hint.
I had also a monitum on the same issue at another post and felt me inclined to reply (see last post), but one time is enough.

For those interested in the last chapter of this issue: In the list of installed packages "hal" wasn't. In the startlevel table either. So I just tried a

Code:
zypper rm hal
and to my surprise zypper did. It did more. It removed a KDE3 installation of some powersave-modules or sth like that depending apparently from hal. As hal or fragments of it couldn't be started, I wasn't very scared of this and the next coldstart didn't show entries afterwards. The annoying message of bootlog disappeared, and, as powersave and screen illumination and other things never had worked with linux on this pc (I have since long resigned with these bungles), I didn't bother also.

Last edited by André7785; 02-11-2018 at 12:52 PM. Reason: Completion of description wqhat I did afterwards
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
systemd journalctl cannot see dhcp client ip requests mgumbau Linux - Server 1 09-13-2017 04:03 AM
Monitoring login and su messages using journalctl fanoflq Linux - Newbie 2 02-17-2017 08:01 PM
JournalCtl warning : Error was encountered while opening journal files: No data avail arunkumarv Linux - Software 6 08-07-2014 01:41 AM
Help: Supertuxkart startup error opensuse 10.3 Infasoft Linux - Newbie 0 09-08-2008 09:33 PM
ALSA Startup error, MPlayer startup error, Sid andymadigan Debian 4 08-03-2004 04:15 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > SUSE / openSUSE

All times are GMT -5. The time now is 01:09 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration