Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

SOLVED - Several minor issues ??? after moving to MX 17.1

Message
Author
User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 10022
Joined: Sun Dec 16, 2007 1:17 pm

Re: Several minor issues ??? after moving to MX 17.1

#21 Post by dolphin_oracle » Thu May 03, 2018 8:10 am

I doubt the app you highlighted will do anything unless systemd is running and is being used for the resolvconf setup.

searching the forum for "expressvpn" finds that at least 2 users "solved" their expressvpn problem by using the systemd boot option, which is availabe in the "Advanced" area of the grub boot menu, by default just under the main default entry.

the problem, such as it is I think, is that expressvpn doesn't have a sysvinit init script, just a systemd service definition, so its not going to autot-run under our default configuration without some intervention. since we are using sysvinit by default, this is likely the source of the issue. the reason this works just fine in mint or xubuntu is because the DO use systemd.

on the surface, this would fly in the face of their linux help page, but it may be the also support the ubuntu "upstart" init system, which would use similar commands I think.

unfortunately, its difficult to troubleshoot the expressvpn setup, as the debs are behind a subscriber wall.

they do list a "manual" configuration via the openvpn plugin in Network Manager, which we do have installed OOTB. maybe that will be of some help. https://www.expressvpn.com/support/vpn- ... h-openvpn/
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
Eadwine Rose
Forum Veteran
Forum Veteran
Posts: 6228
Joined: Wed Jul 12, 2006 2:10 am

Re: Several minor issues ??? after moving to MX 17.1

#22 Post by Eadwine Rose » Thu May 03, 2018 8:58 am

Hmm.. guess I wasn't too far off with my post then *chuckle*
MX-17.1_x64 Horizon 3-2018 * 4.15.0-1-amd64 ext4 Xfce 4.12.3 * AMD Asus M4A785TD-V EVO AM3 * ASUS GF GT640-1GD5-L NVIDIA 384.130 * AMD Proc. Athl II X4 635, sAM3 * HDA ATI SB VT1708S An * 2x4Gb DDR3 1600 Kingst * 22" Samsung SyncM P2250 * HP Envy5030

User avatar
Richard
Posts: 2236
Joined: Fri Dec 12, 2008 10:31 am

Re: Several minor issues ??? after moving to MX 17.1

#23 Post by Richard » Thu May 03, 2018 9:16 am

@Eadwine,
Yep.
MX18b1: Lenovo T430: Intel Ivy Bridge i5-3320M, 8GB RAM, 4.19.0-1-amd64, 119 GB SSD
MX18b1: Eee&AA1 NBs: Dual Core Atom N270, 1GB RAM, 4.19.0-1-686, 150 GB HDD
DoubleCmd/Thunar, LibO613, Dropbox, Vivaldi/Firefox, CherryTree, Vbox. LinuxCounter #208633

linwinux

SOLVED - Re: Several minor issues ??? after moving to MX 17.1

#24 Post by linwinux » Thu May 03, 2018 9:27 am

Eadwine Rose wrote:Hmm.. guess I wasn't too far off with my post then *chuckle*
You may have suspected or perhaps even known about the solution, but I was quite literally not able to do anything with your comment or the information that was posted in those links. All someone had to mention briefly was ... "reboot your system and select the boot option with systemd from the grub boot menu" ... and everything would have been fine. I didn't even realize that a systemd boot option was available since I had just recently installed MX without any reason to have to reboot ... until now.

Thank you dolphin_oracle, you rock !!! :number1:
Took me 2 minutes to adjust the grub boot menu so it boots into systemd by default, reboot, and get expressvpn working. :happy:
(since I had previously already installed the .deb file from our vpn service)

.

User avatar
richb
Administrator
Posts: 17482
Joined: Wed Jul 12, 2006 2:17 pm

Re: Several minor issues ??? after moving to MX 17.1

#25 Post by richb » Thu May 03, 2018 9:41 am

It was obviously a humorous comment by Eadwine.
Forum Rules
Guide - How to Ask for Help

Rich
SSD Production: MX 17.1
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB, 350 GB HD

User avatar
Eadwine Rose
Forum Veteran
Forum Veteran
Posts: 6228
Joined: Wed Jul 12, 2006 2:10 am

Re: Several minor issues ??? after moving to MX 17.1

#26 Post by Eadwine Rose » Thu May 03, 2018 9:48 am

Obviously, as both you and Richard understood :)
MX-17.1_x64 Horizon 3-2018 * 4.15.0-1-amd64 ext4 Xfce 4.12.3 * AMD Asus M4A785TD-V EVO AM3 * ASUS GF GT640-1GD5-L NVIDIA 384.130 * AMD Proc. Athl II X4 635, sAM3 * HDA ATI SB VT1708S An * 2x4Gb DDR3 1600 Kingst * 22" Samsung SyncM P2250 * HP Envy5030

User avatar
anticapitalista
Forum Veteran
Forum Veteran
Posts: 5820
Joined: Sat Jul 15, 2006 10:40 am

Re: Several minor issues ??? after moving to MX 17.1

#27 Post by anticapitalista » Thu May 03, 2018 9:56 am

BTW If you plan to use systemd, have a read of the possible consequences if you haven't already done so.

https://mxlinux.org/wiki/system/systemd#Known%20issues
anticapitalista
Reg. linux user #395339.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX-17 "Heather Heyer" - lean and mean.
https://antixlinux.com

linwinux

Re: Several minor issues ??? after moving to MX 17.1

#28 Post by linwinux » Thu May 03, 2018 10:09 am

Thanks anticapitalista. I don't think those issues will be anything to be concerned about for us.

It's not that I'm lacking a sense of humor, but when an issue is giving me a headache of sorts, I'm just not feeling so very ha ha, ho, ho, ho, hee hee, at that time. ;) It may seem soewhat absurd to some, but having an issue like the vpn thingie would actually impact whether or not I can switch all of our systems over to MX Linux, or not. So from that point of view, it was a pretty big (serious) deal. Glad everything got resolved though and since this concluded finding a resolution to the final issue that I had posted in this thread ... I suppose it's time to lay it to rest ... :linuxlove:

.... with a humorous image from my "Fearless" (that's her name) :happy:
fearless_showingoff.jpg
You do not have the required permissions to view the files attached to this post.
Last edited by linwinux on Thu May 03, 2018 10:18 am, edited 2 times in total.

User avatar
Eadwine Rose
Forum Veteran
Forum Veteran
Posts: 6228
Joined: Wed Jul 12, 2006 2:10 am

Re: Several minor issues ??? after moving to MX 17.1

#29 Post by Eadwine Rose » Thu May 03, 2018 10:11 am

Please add [solved] by editing the title of the first post you made if everything has been sorted, thank you.
MX-17.1_x64 Horizon 3-2018 * 4.15.0-1-amd64 ext4 Xfce 4.12.3 * AMD Asus M4A785TD-V EVO AM3 * ASUS GF GT640-1GD5-L NVIDIA 384.130 * AMD Proc. Athl II X4 635, sAM3 * HDA ATI SB VT1708S An * 2x4Gb DDR3 1600 Kingst * 22" Samsung SyncM P2250 * HP Envy5030

linwinux

Re: SOLVED - Several minor issues ??? after moving to MX 17.1

#30 Post by linwinux » Thu May 03, 2018 10:16 am

Goodness, don't be in such a hurry. I had already marked all the previous posts with solutions, just didn't get to the first one yet. It's only been a few minutes ...
I didn't add solved to the ones that were more or less irrelevant.

Post Reply

Return to “Installation”