Jump to content

Question

Hi there,

recently I moved my Bodhi VM from VirtualBox to Hyper-V almost seamlessly. All works fine except Network Manager (besides the network itself also works fine).

Network Manager crashes on boot, presumably because of my VPN startupt script I used before.

Besides NM crashes with Moksha window saying log saved in ~/NetworkManager.log bla-bla-bla I wasn't able to find it there, nor in other locations:

 

/var/log/

/var/log/syslog

/usr/bin/NetworkManager

 

/var/log/daemon.log is also empty. So where can I found NM-applet logs to reveal why it keeps crashing?

Share this post


Link to post
Share on other sites

21 answers to this question

Recommended Posts

  • 0

You'd want to run it from terminal and see the output it posts when crashing.

The log file Moksha mentions isn't supported by most applications. I really need to remove that part of the app crash dialog.

Share this post


Link to post
Share on other sites
  • 0

You'd want to run it from terminal and see the output it posts when crashing.

 

Well, I tried to run in Terminal:

nm-applet
network-manager
network-manager-gnome
network

None of them worked, just nothing happens.

This is the message I see

 

RaLRyd0.png

 

What that Network could mean? These messages should be more informative though.

Share this post


Link to post
Share on other sites
  • 0

"Network" is the nm-applet application. When you run the command nm-applet you should see a network icon appear in your systray. Any output it has from crashing should then be displayed in the terminal you launched it from.

Share this post


Link to post
Share on other sites
  • 0
"Network" is the nm-applet application. When you run the command nm-applet you should see a network icon appear in your systray. Any output it has from crashing should then be displayed in the terminal you launched it from.

 

 

Nothing. No output and no log at all.

Do Moksha appets have no logs at all?

Share this post


Link to post
Share on other sites
  • 0

This isn't a moksha applet. This is the Gnome network manager from the upstream Ubuntu repositories.

Share this post


Link to post
Share on other sites
  • 0

The network manger itself is functioning well, internet is working and VPN connections are started. The issue is in applet.

When I try to purge it I see

 

 
root@bodhi-box:/home/suncatcher# apt-get purge nm-applet
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package nm-applet
 
Could you please write out the exact package name? It seems that it's some Moksha peculiarity here.

Share this post


Link to post
Share on other sites
  • 0

Here it is

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                   Version          Architecture     Description
+++-======================-================-================-==================================================
ii  network-manager        1.2.2-0ubuntu0.1 amd64            network management framework (daemon and userspace
ii  network-manager-gnome  1.2.0-0ubuntu0.1 amd64            network management framework (GNOME frontend)
un  network-manager-kde    <none>           <none>           (no description available)
un  network-manager-openco <none>           <none>           (no description available)
un  network-manager-openco <none>           <none>           (no description available)
ii  network-manager-openvp 1.1.93-1ubuntu1  amd64            network management framework (OpenVPN plugin core)
ii  network-manager-openvp 1.1.93-1ubuntu1  amd64            network management framework (OpenVPN plugin GNOME
ii  network-manager-pptp   1.1.93-1ubuntu1  amd64            network management framework (PPTP plugin core)
un  network-manager-pptp-g <none>           <none>           (no description available)
un  network-manager-vpnc   <none>           <none>           (no description available)
un  network-manager-vpnc-g <none>           <none>           (no description available)

Share this post


Link to post
Share on other sites
  • 0
presumably because of my VPN startupt script I used before.  

 

This assumption was wrong. I removed this startup record from /etc/rc.local, but this has no impact and the message still persists. Additionally when I run it in Terminal

nmcli con up uuid b79f67db-93fb-4426-a88f-35591f2b71f2

it works fine, and VPN connection is started.

Share this post


Link to post
Share on other sites
  • 0

Yep. The network services itself should stay running. The applet / GUI just crashing.

Share this post


Link to post
Share on other sites
  • 0

Looks you have all packages installed.

Question, do you have a systray loaded to a shelf that nm-applet can use?

The applet is provided by network-manager-gnome but demands a working systray conforming to XDG specifications.

By default in Bodhi the applet is started as a startup application, you can check that in Settings>Apps>Startup>Order where you should see Network.

Share this post


Link to post
Share on other sites
  • 0
By default in Bodhi the applet is started as a startup application, you can check that in Settings>Apps>Startup>Order where you should see Network.

 

 

It exists there, and Enabled as I can see it.

 

Question, do you have a systray loaded to a shelf that nm-applet can use?

 

 

The answer is also Yes, if I am not mistaken.

 

W0NMjyR.jpg

 

What other things I can check?

Share this post


Link to post
Share on other sites
  • 0

Everything is launching as expected. One of my 6~ systems here has the network applet sporadically crash on me as well. You can replace it with WICD-GTK if you need something else that keeps the applet open. It dumping out doesn't actually hurt anything though as connections remain active.

Share this post


Link to post
Share on other sites
  • 0

Ok, let it be. But the question is wider than just this applet. I have other apps that crash in a similar way

 

vZFLk13.png

 

QMInRwe.png

 

And of course there are NO logs that are specified there.

In spite of the fact these are consequences of my migration to Hyper-V, there definitely should be some way to debug Moksha errors. Now they are totally undebuggable!!!

What should be my next steps? No idea.

Share this post


Link to post
Share on other sites
  • 0

These are not Moksha errors. There are desktop independent applications that are crashing on you. As I mentioned earlier that log message is something left over from upstream E17 that never worked correctly and I haven't gotten around to stripping out of the code base. 

If you want to debug these applications crashing you'd need to read the docs for these applications specifically. I use VLC on the regular on half a dozen different Bodhi systems though and never once had it crash for reference. If you are having lots of different applications crash on you I would recommend checking your drive health and run a memory check.

Share this post


Link to post
Share on other sites
  • 0
If you want to debug these applications crashing you'd need to read the docs for these applications specifically. I use VLC on the regular on half a dozen different Bodhi systems though and never once had it crash for reference. If you are having lots of different applications crash on you I would recommend checking your drive health and run a memory check.

 

I cannot agree. Whenever I install new applications (pdf viewers, office stuff or media players) this error persists. It is app-independent error and should be debugged at system-level.

 

left over from upstream E17 that never worked correctly 

 

So why the hell it is still there? What is the use of debug message which brings no useful info?

Share this post


Link to post
Share on other sites
  • 0

Is there any way you can go back to VirtualBox?

I can really only speak for myself, but I don't think there is much experience with Hyper-v around here. So your support for it may be limited.

For example you could have an issue with how the graphics driver in the kernel interacts with Hyper-v, causing apps to crash. But don't take that advice to the bank because I'm really not that familiar with Hyper-v, just putting a thought out there.

Share this post


Link to post
Share on other sites
  • 0
I cannot agree. Whenever I install new applications (pdf viewers, office stuff or media players) this error persists. It is app-independent error and should be debugged at system-level.

 

If you are getting this error with every application it is an issue with your system. As I mentioned - check system health. We only support / test in virtual box so YMMV with other tools such as hyper V. All these things work fine in virtual box.

 

 

 

 

So why the hell it is still there? What is the use of debug message which brings no useful info?

 

Because it is harmless so it is low priority. Bodhi doesn't pay my bills or anyone's bills for that matter. It is a labor of love. If an issue like this is something you really need fixed / removed before our folks get around to it feel free to submit a patch yourself or sponsor someone to do it. As is the work that puts food on the table for my kids always take priority. 

  • Like 1

Share this post


Link to post
Share on other sites
  • 0
For example you could have an issue with how the graphics driver in the kernel interacts with Hyper-v, causing apps to crash. But don't take that advice to the bank because I'm really not that familiar with Hyper-v, just putting a thought out there. 

 

I also think so. I noticed moth of the crashed apps are Gnome-based. It's some Gnome driver issue.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×