VSIDO Community

VSIDO Controls => VSIDO Discussions => Topic started by: VastOne on December 07, 2016, 03:41:37 AM

Title: Gotta love Debian now
Post by: VastOne on December 07, 2016, 03:41:37 AM
Changed my network settings from dhcp to static IP in a normal everyday /etc/network/interfaces edit...
and you guessed it...
IT BLEW UP X
Wait, what?
Yasssss it fucking blew up X. So I booted to another partition, changed back to dhcp and the fucking thing booted normally, X all good

Are you fucking kidding me that in debian land a simple edit to /etc/network/interface can kill X?
Title: Re: Gotta love Debian now
Post by: Snap on December 07, 2016, 07:16:54 AM
The Xserver transition is still not complete. 85% as of today. But it sounds strange that setting an static IP borks the X anyway.
Title: Re: Gotta love Debian now
Post by: PackRat on December 07, 2016, 11:52:15 AM
Did you make that change manually or use Ceni?
Title: Re: Gotta love Debian now
Post by: VastOne on December 07, 2016, 02:04:16 PM
Manual.. I will try it again with Ceni and see if that kills it too
Title: Re: Gotta love Debian now
Post by: VastOne on December 07, 2016, 03:26:14 PM
I did have the issue with ceni but after looking at the results, ceni had put both eth0 and eth1 in the file .. which cannot happen

So it appears an error can cause X to blow up in an edit. It is possible my initial edit had a blank space where it should not have been.. I do not know, that is just speculation
Title: Re: Gotta love Debian now
Post by: hakerdefo on December 07, 2016, 08:21:40 PM
Are you using wicd-tray or nm-applet?
If yes, then first disable wicd-tray/nm-applet from auto-starting and then retry the manual static-IP procedure and see what happens.
Cheers!!!
Title: Re: Gotta love Debian now
Post by: VastOne on December 07, 2016, 08:24:44 PM
^ No.

I always do these changes manually. I used ceni per the Packrat request and it looks like X puked simply because of errors in the interfaces file

No matter the cause, it is bullshit that an entire system can go to shit because of a setting in your network interfaces file
Title: Re: Gotta love Debian now
Post by: PackRat on December 07, 2016, 08:29:13 PM
No matter the cause, it is bullshit that an entire system can go to shit because of a setting in your network interfaces file

It may have just hung at the discover network phase - I've had a similar issue when I was changing from Network Manager to manual for a wired desktop. That was a while ago, but as I recall I left to get a cup of coffee and generally calm down. When I go back, I think it finished booting but with no network. It's like the time out is 2-5 minutes with no error message.
Title: Re: Gotta love Debian now
Post by: VastOne on December 07, 2016, 08:32:05 PM
^ No

This is a hard freeze of X at a 640x480 login screen..

IOW, it makes it to the login screen after flashing in 16 different modes and settles at 640x480. At this point it is dead to anything except a fat finger hold of the power button for 5 seconds
Title: Re: Gotta love Debian now
Post by: PackRat on December 07, 2016, 09:07:40 PM
Ouch!

Title: Re: Gotta love Debian now
Post by: VastOne on December 07, 2016, 09:09:33 PM
Right... your descriptive method of failure would be acceptable

This is outright bullshit where an edit kills a complete system
Title: Re: Gotta love Debian now
Post by: hakerdefo on December 07, 2016, 10:04:17 PM
Hi there VastOne,

I think the incorrect config and restart of the whole networking stack causes the dbus to shutdown and that in-turn kills the display manager. Let's test this theory,

Assign the static IP and run the following command,

Code: [Select]
sudo ifdown -a --exclude=lo && ifup -a --exclude=lo

Does the X survive?

Cheers!!!
Title: Re: Gotta love Debian now
Post by: jeffreyC on December 10, 2016, 08:22:13 PM
Is this part of the joys of systemd uber alles?
Title: Re: Gotta love Debian now
Post by: VastOne on December 10, 2016, 08:30:36 PM
^ It sure seems that way to me...

But it is awfully easy to blame systemd for debian bullshit.. they are after all partners
Title: Re: Gotta love Debian now
Post by: PackRat on December 10, 2016, 10:43:42 PM
Not without some justification though -

(http://en.zimagez.com/miniature/unnamed196.jpg) (http://en.zimagez.com/zimage/unnamed196.php)
Title: Re: Gotta love Debian now
Post by: hakerdefo on December 11, 2016, 10:55:37 AM
I would repeat what I said in my previous post, it's most likely a dbus related thingy. You can easily test this by not using display manager, (LightDM) in this case, and logging in by good old 'startx' and repeat the same static IP steps and see if X goes down. My guess it won't.
Systemd not to be blamed here, IMO.
Cheers!!!
Title: Re: Gotta love Debian now
Post by: jeffreyC on December 11, 2016, 10:52:28 PM
^ It sure seems that way to me...

But it is awfully easy to blame systemd for debian bullshit.. they are after all partners

What has me wondering is that one of the many, many things systemd has taken over is network discovery and when you changed the network settings is when the trouble started.
Having PID 1 aka systemd responsible for the whole OS is what makes me think that when one part fails or does not work as it is programmed to expect then the whole OS is more likely to fail.