Desktop hangs at locale service

English Install/Boot/Login
1

OK, where was I at when another am-bu-lance ride to the hospital took me away for another week.

**Oh yeah, this booting problem with KDE **
My Hp Compaq desktop hangs aftert “starting local service” and on “started locale service”. No HDD activity until I have to press the power button. Eventually it starts.

More about this. It is starting from a Windows boot manager(not Grub, probably EasyBCD), sometimes blue screen on boot, sometimes black w/white text.
Choices are Win10, Win7(I still need it, or maybe I don’t need to make up my feeble mind), then Leap 15.

I also get a message on boot to Leap that is something like “80 sectors changed to 16” (I can try to capture that if needed).

Question, can I easily get it back to Grub boot menu and still have both Win10 and Win7 in a Grub boot menu?

More important question is why the hangs a "starting and started locale service?

2

I forgot to add, that when I do select Leap 15, it does start a green screen Grub boot menu that has Leap15, Win10 and the other options that can be used to boot Leap.

3

@Bill_L:
Did you begin using “EasyBCD” because of this “Stack Exchange” article: <https://unix.stackexchange.com/questions/316602/how-to-properly-dualboot-opensuse-and-windows-10>?

  • If so, please follow the 2nd answer …
  • For a “boot with GRUB2 only” system – no “EasyBCD” – the tip to manually edit “/etc/grub.d/40_custom” is possibly quite a good idea …

There’s the following openSUSE Reference Manual entry which deals with this issue: <https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.grub2.html>.
This openSUSE SDB entry is a bit outdated but, it does mention “grub2-install” to help get things repaired: <https://en.opensuse.org/SDB:Repair_MBR_after_Windows_install>.

  • ‘apropos grub’ from a CLI prompt is also a possible follow-on help …

There’s also this “Linux Questions” question & answer entry: <https://www.linuxquestions.org/questions/linux-newbie-8/grub-boot-loader-gone-in-opensuse-42-3-leap-4175616442/>.

4

Thanks, good articles and links, but I should have included that the HP desktop is ‘legacy’ MBR. Most of the articles were alluding to UEFI.
The Leap install is on its own HDD, and not the Windows HDD.
NO, not the stack exchange, I don’t even know what that means. EasyBCD was used for dual booting Win10 and Win7 even before I was considering a Linux install.

Maybe it is time to ditch windows 7, and EasyBCD, and reinstall Leap 15 new without any obstacles in the way to get a Grub boot menu first and not the Windows boot manager.
Might clean up the hang up at the ‘started locale service’ as well.

Hate to do it, but may be the best thing.

Anyone know if there is a newer version of the DVD download?
i would do the “dd if of” to write it to a USB stick.

5

Even with pre-UEFI boxes, it’s usually better to install the Redmond product first and then, having reduced the primary Redmond partition size, install openSUSE …
[HR][/HR]But, why dual-boot?

  • Given the “pre-UEFI” age of the box and, assuming that no more BIOS updates are available or, assuming that the BIOS may occasionally suffer an update and, the Redmond product isn’t needed to perform the BIOS update (BIOS update via USB device from a BIOS menu-point … ), consider a “Linux-only” box …
  • If you ** really ** need “Redmond things” consider either:

– “Wine” – be aware that, there a few « not many » “Redmond things” which don’t execute in a Wine environment …
– “Redmond in a Virtual Machine” …

[INDENT=2]** I personally run Windows 10 licences in Oracle VirtualBox environments …
[/INDENT]

6

We are not down to the ROOT of my OP, WHICH IS>>>> why does it hang at the “starting locale service” and then :"started locale service.
Hangs for 1 or 2 minutes, then a cursor shows up, then it does NOTHING!
After power downs and more power ups it FINALLY gets past the cursor(after another minute or so), and THEN KDE takes it’s own sweet time.

I can live with slowness. I don’t like having to live with multiple starts because Leap (on this machine) doesn’t know how to complete a clean boot.
NEVER use to until an update between hospital visits.

About to have to jerk the front off and do a hot wire because I am wearing the PC’s power button out!

So, please address my hang ups during boot. I need windows and it stays.

WHY DO I DUAL BOOT YOU ASKED!
I dual boot because I NEED Windows(Redmond, windoze, what—ever) for printing. IF I didn’t I wouldn’t!
enough said about that!
But Windows has been on this HP Compaq for ages(XP Pro, Windows 7, then windows 10 and Win 7(DUAL BOOT).

I had an extra HDD and didn’t want to muck around with the Windows HDD, So that is where I put Leap. EasyBCD found it and added it to it’s boot menu.

The Windows(Redmond, windoze, etc) were already set up as dual boot with the EasyBCD boot manager.
So I put Leap into EasyBCD9 (YEAH YEAH I know, MISTAKE!).

That should take care of SOME of your concerns.

But we are not down to the ROOT of my OP, WHICH IS>>>> why does it hang at the “starting locale service” and then :"started locale service.

NEVER use to until an update between hospital visits.

About to have to jerk the front off and do a hot wire because I am wearing the PC’s power button out!

So, please address my hang ups during boot. I need windows and it stays.

7

After a successful boot, examine the log file for any errors during boot.

sudo journalctl -b > log.txt

will output all logs since the last system boot into a file called log.txt. Change the file name to anything you want. Then search for Locale Service and see what errors show up after that service is started. Post the relevant output here.

8

It was a good clean boot last time, without having to ‘power down’ at 5he hang spot, and restart, no log file found.
I will check the next time it hangs to see of a log file is put in place.

Thanks for your reply.

9

I would think the OP dual-boots with Windows because the OP wants to dual-boot with Windows.

… at least, that would be the way I would see it.

Thanks, Don, but I would like to see the answer to the question in the OP, instead, in case someone else runs into the problem.:wink:

10

The log file is just the output from the journalctl command. The system keeps a journal (or log) of everything that occurs while the computer is running. So, if you run the journalctl command I mentioned in a terminal window, it will output all the logs from the current session into a file, but you have to do it manually. I figured that would be an easy way to search it for errors. You should be able to generate a log file regardless of whether or not there are any errors.

For more info you can type

man journalctl

in a terminal window.

11

I indicated a log.txt file was not found. But my bad, I just don’t know where to find it
Two more ‘bad’ starts this evening, getting frustrating.
So I generated one in terminal without the -b > log.txt, and Oh boy, is that a big thing!
So will go looking for the file.
Thanks

12

If it helps, this is the a portion of the log for today’s first hang start at ‘started locale service’. The second hang up is pretty much the same, then a third was successful.
It was done using the -r reverse switch.

Aug 26 16:51:26 localhost systemd[1]: Started Command Scheduler.
Aug 26 16:51:26 localhost systemd[1]: **postfix.service: Failed with result 'exit-code'.**
Aug 26 16:51:26 localhost systemd[1]: **postfix.service: Unit entered failed state.**
Aug 26 16:51:26 localhost systemd[1]: **Failed to start Postfix Mail Transport Agent.**
Aug 26 16:51:25 localhost kernel: r8169 0000:07:04.0 eth0: link up
Aug 26 16:51:25 localhost NetworkManager[1020]: <info>  [1535320285.5178] device (eth0): carrier: link connected
Aug 26 16:51:25 localhost systemd[1]: display-manager.service: PID file /var/run/displaymanager.pid not readable (yet?) after start: No such file or >
Aug 26 16:51:25 localhost display-manager[1352]: Starting service sddm..done
Aug 26 16:51:25 localhost cond_slp[1490]: /usr/sbin/postconf: fatal: parameter inet_interfaces: no local interface found for ::1
Aug 26 16:51:24 localhost avahi-daemon[790]: Registering new address record for fe80::cd28:6634:5dc5:80d1 on eth0.*.
Aug 26 16:51:24 localhost avahi-daemon[790]: New relevant interface eth0.IPv6 for mDNS.
Aug 26 16:51:24 localhost avahi-daemon[790]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::cd28:6634:5dc5:80d1.
Aug 26 16:51:24 localhost systemd[1]: Started Backup /etc/sysconfig directory.
Aug 26 16:51:24 localhost systemd[1]: Reached target Login Prompts.
Aug 26 16:51:24 localhost systemd[1]: Started Getty on tty1.
Aug 26 16:51:24 localhost systemd[1]: Started Hold until boot process finishes up.
Aug 26 16:51:24 localhost systemd[1]: Received SIGRTMIN+21 from PID 293 (plymouthd).
Aug 26 16:51:24 localhost systemd[1]: **Started Locale Service.**
Aug 26 16:51:24 localhost dbus-daemon[794]: [system] Successfully activated service 'org.freedesktop.locale1'
Aug 26 16:51:24 localhost systemd[1]: **postfix.service: Control process exited, code=exited status=1**
Aug 26 16:51:24 localhost kernel: NET: Registered protocol family 17
Aug 26 16:51:23 localhost postfix[1463]: **fatal: parameter inet_interfaces: no local interface found for ::1**
Aug 26 16:51:23 localhost systemd[1]: **Starting Locale Service...**
13

This is indicating that postfix is unable to find a local loopback interface for IPv6. Check if IPv6 is enabled. Go to YaST > System > Network settings and check if the “Enable IPv6” box is checked under global options.

Also check your hosts file:

/etc/hosts

to see if it has the following line:

::1             localhost ipv6-localhost ipv6-loopback

If IPv6 is enabled and the loopback address is in the hosts file, check systemd for more info on postfix:

systemctl status postfix

to see if it gives more details on what’s wrong.

14

Looking at the time stamps, it seems that, the D-Bus is starting the ‘org.freedesktop.locale1’ service before the network is up and running …
And, systemd is attempting to start the Postfix service before the Network target has been reached …
The following CLI command for the user “root” should confirm this: " journalctl --this-boot | grep -E ’ Locale|eth0| Network|Display Manager|Command Scheduler’ ".

Usually, systemd starts the Postfix service after the following targets have been reached (file: ‘/usr/lib/systemd/system/postfix.service’):

  • var-run.mount nss-lookup.target network.target time-sync.target

and, after the following services have been started:

  • amavis.service mysql.service cyrus.service ldap.service openslp.service ypbind.service

and, the Postfix service is usually wanted only by the “multi-user.target” …

Also, usually, the D-Bus starts the Locale service while the Display Manager is being started …

Questions:

  • Have the D-Bus services been changed?
  • Has the systemd Postfix service been changed?
15

As far as I know, neither of those have changed, at least I didn’t change them, even if I knew how.

16

YES, that is present after a completed boot, but I haven’t shutdown and tried to boot again.

Sorry to quote your full post.
Yast Global had IPv6 unchecked, but when I opened the NetworkManager, it had IPv6 as ‘automatic’. There is no ‘disable’ in NM, so I set it to ‘ignored’.
We’ll see what happens the next time I boot.

Follows is the postfix status:

systemctl status postfix
**●** postfix.service - Postfix Mail Transport Agent
   Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled; vendor preset: enabled)
   Active: **failed** (Result: exit-code) since Mon 2018-08-27 16:45:05 CDT; 1h 10min ago
  Process: 1659 ExecStopPost=/etc/postfix/system/cond_slp deregister (code=exited, status=0/SUCCESS)
  Process: 1605 ExecStart=/usr/sbin/postfix start **(code=exited, status=1/FAILURE)**

Aug 27 16:45:01 localhost update_postmaps[1415]: postmap: fatal: parameter inet_interfaces: no local interface found for ::1
Aug 27 16:45:01 localhost postfix/postmap[1522]: **fatal: parameter inet_interfaces: no local interface found for ::1**
Aug 27 16:45:02 localhost update_postmaps[1415]: postmap: fatal: parameter inet_interfaces: no local interface found for ::1
Aug 27 16:45:02 localhost postfix/postmap[1564]: **fatal: parameter inet_interfaces: no local interface found for ::1**
Aug 27 16:45:03 localhost postfix[1605]: **fatal: parameter inet_interfaces: no local interface found for ::1**
Aug 27 16:45:04 localhost.localdomain systemd[1]: **postfix.service: Control process exited, code=exited status=1**
Aug 27 16:45:04 localhost.localdomain cond_slp[1659]: /usr/sbin/postconf: fatal: parameter inet_interfaces: no local interface found for ::1
Aug 27 16:45:05 localhost.localdomain systemd[1]: **Failed to start Postfix Mail Transport Agent.**
Aug 27 16:45:05 localhost.localdomain systemd[1]: **postfix.service: Unit entered failed state.**
Aug 27 16:45:05 localhost.localdomain systemd[1]: **postfix.service: Failed with result 'exit-code'.**
17

Hi
You need to configure /etc/postfix/main.cf and change inet_protocols
(line 706) from all to ipv4;


cat /etc/postfix/main.cf |grep inet_protocols

inet_protocols = ipv4

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.13-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

18

After changing NM IPv6 to ignored, it had a clean boot, but the postfix status was still a mess.
Am trying to edit the /etc/postfix/main.cf, but need to figure out how to save it.

19

Hi
In vi, nano etc?

20

Yeah, head finally came out of dark place. I changed to root, and made the change, restarted and another complete boot w/o hang up.

BTW, that

::1             localhost ipv6-localhost ipv6-loopback

is still in the hosts file.
And the systemctl status is still got red in in and now includes a reference to IPv4.

**localhost:~ #** systemctl status postfix
**●** postfix.service - Postfix Mail Transport Agent
   Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled; vendor preset: enabled)
   Active: **failed** (Result: exit-code) since Mon 2018-08-27 19:13:43 CDT; 8min ago
  Process: 1474 ExecStopPost=/etc/postfix/system/cond_slp deregister (code=exited, status=0/SUCCESS)
  Process: 1435 ExecStart=/usr/sbin/postfix start **(code=exited, status=1/FAILURE)**

Aug 27 19:13:38 localhost systemd[1]: Starting Postfix Mail Transport Agent...
Aug 27 19:13:38 localhost echo[1346]: Starting mail service (Postfix)
Aug 27 19:13:40 localhost postfix[1435]: **fatal: unknown inet_protocols value "IPv4" in "IPv4"**
Aug 27 19:13:41 localhost systemd[1]: **postfix.service: Control process exited, code=exited status=1**
Aug 27 19:13:42 localhost cond_slp[1474]: /usr/sbin/postconf: fatal: unknown inet_protocols value "IPv4" in "IPv4"
Aug 27 19:13:43 localhost systemd[1]: **Failed to start Postfix Mail Transport Agent.**
Aug 27 19:13:43 localhost systemd[1]: **postfix.service: Unit entered failed state.**
Aug 27 19:13:43 localhost systemd[1]: **postfix.service: Failed with result 'exit-code'.**