jfabernathy
Posts: 103
Joined: Thu Oct 11, 2018 10:52 am
Location: Central North Carolina

desktop messed up if wait for network is set

Thu Nov 29, 2018 1:44 am

I have a Stretch setup on a RP3b+ and I want to connect to a CIFS media server to stream music in my house. I put the command in /etc/fstab and I can reboot and then mount -a to get the CIFS server mounted. The problem comes when I set the configuration for wait for network at boot.

If I then boot the Desktop doesn't completely come up. I get the road.jpg background image and I get my desktop shortcut icons, but the top menu line starts to come up, but then every icon disappears and I'm left with a gray bar.

To fix this I had to ssh into the RP3 and us raspi-config to turn off the wait for network.

What am I missing? I'm new to Raspbian. More experience with Ubuntu.

Jim A

jfabernathy
Posts: 103
Joined: Thu Oct 11, 2018 10:52 am
Location: Central North Carolina

Re: desktop messed up if wait for network is set

Thu Nov 29, 2018 1:39 pm

So here's a weird fix. I when back to square 1 and created a NOOBS 3.0 image and used that to install Raspbian Stretch desktop FULL. This time I can setup my /etc/fstab, turn on wait for network, and reboot. Desktop menu is fine and remote shares are mounted.

So the only difference is full desktop vs. desktop Raspbian Stretch. Both images were the 2018-11-13 versions. And both had all system updates

jfabernathy
Posts: 103
Joined: Thu Oct 11, 2018 10:52 am
Location: Central North Carolina

Re: desktop messed up if wait for network is set

Thu Nov 29, 2018 2:42 pm

Well, I spoke too soon. the more reboots I do the more it fails to come up with a clean menu line at the top of the clean. No icons. All I have to do to fix it is go back to raspi-config and disable "wait on network" boot option.

Sounds like a race condition. I hate timing problems.

I hope someone has a fix. This I would classify as a bug. I'm going to try putting a "sudo mount -a" somewhere is startup file. maybe use systemd and make it wait for something.

Ideas?

n67
Posts: 938
Joined: Mon Oct 30, 2017 4:55 pm

Re: desktop messed up if wait for network is set

Thu Nov 29, 2018 2:51 pm

Sounds like "the lxpanel problem".

The program that implements the "menu bar" is called "lxpanel". lxpanel is buggy and prone to crash. When it crashes (i.e., is not running), the "menu bar" disappears.

You can check to see if it is running by doing the usual "ps" type command(s). For example:

Code: Select all

$ ps -fC lxpanel
UID        PID  PPID  C STIME TTY          TIME CMD
pi         937   872  0 Oct08 ?        08:10:59 lxpanel --profile LXDE-pi
 $
If it isn't running, that's your answer.

You can try running it manually - this works sometimes, sometimes not.

Open up a terminal window and do:

Code: Select all

$ lxpanel --profile LXDE-pi
and the menu bar should re-appear (perhaps only for a moment). The nice thing about running it this way is that you'll see error messages in the terminal window - which may or may not be instructive.

Note that one of my systems has lxpanel running this way quite stably. The original lxpanel crashed several months ago, but the manually run one is doing fine.

You will note that none of this text contains any "magic bullets". The solution is that whoever is responsible for "lxpanel" needs to fix it.
"L'enfer, c'est les autres"

G fytc hsqr rum umpbq rm qyw rm rfc kmbq md rfgq dmpsk:

Epmu Sn!

J lnacjrw njbruh-carppnanm vxm rb mnuncrwp vh yxbcb!

jfabernathy
Posts: 103
Joined: Thu Oct 11, 2018 10:52 am
Location: Central North Carolina

Re: desktop messed up if wait for network is set

Thu Nov 29, 2018 3:42 pm

Thanks for your reply. Here's what I see with "wait for network" on and just a blank gray bar where the menu should be:
pi@raspberrypi:~ $ ps -fC lxpanel
UID PID PPID C STIME TTY TIME CMD
pi 971 909 2 10:32 ? 00:00:00 lxpanel --profile LXDE-pi
pi@raspberrypi:~ $ killall lxpanel
pi@raspberrypi:~ $ ps -fC lxpanel
UID PID PPID C STIME TTY TIME CMD
pi@raspberrypi:~ $ lxpanel --profile LXDE-pi
** Message: Connecting ...
** Message: Status changed to down

** (lxpanel:1061): CRITICAL **: dhcpcd_open: Resource temporarily unavailable
Unit pt-device-manager.service could not be found.

** (lxpanel:1061): WARNING **: Battery entry BAT0 not found, using hid-00:04:20:e9:85:59-battery
** Message: Status changed to opened
** Message: Connected to dhcpcd-6.11.5
** Message: Status changed to connected
** Message: eth0: CARRIER
** Message: eth0: Configured 192.168.0.30/24
** Message: wlan0: Not associated
** Message: wlan0: WPA status connected
** Message: wlan0: Received scan results
** Message: bt: Name org.bluez owned on DBus
** Message: bt: New agent manager found
** Message: bt: New adapter found
** Message: va: Name org.bluez owned on DBus

And NO I don't have it fixed. Still a gray bar only. I put the terminal on my desktop so I could run this stuff when it booted in this mode.

n67
Posts: 938
Joined: Mon Oct 30, 2017 4:55 pm

Re: desktop messed up if wait for network is set

Thu Nov 29, 2018 4:32 pm

Well, the fact that it was already running (when you did the first "ps"), means that my guess was probably wrong.

So, I'm out of ideas.
"L'enfer, c'est les autres"

G fytc hsqr rum umpbq rm qyw rm rfc kmbq md rfgq dmpsk:

Epmu Sn!

J lnacjrw njbruh-carppnanm vxm rb mnuncrwp vh yxbcb!

Return to “Raspberry Pi OS”