[SOLVED] autoremoved network-manager and the greeter?

Questions about Grub, the liveCD and the installer
Forum rules
Before you post please read how to get help
screenshot
Level 1
Level 1
Posts: 36
Joined: Sat Feb 01, 2014 8:54 am

[SOLVED] autoremoved network-manager and the greeter?

Postby screenshot » Sat Dec 09, 2017 1:19 am

hi

i think i just managed to autoremove the network-manager and the default greeter, so how could i get them back?(i have like a blank screen and probably no internets atm - reinstall command gives some more missing "libdbus-1-3, dbus, consolekit, etc..." dependencies or something...)
and what is the default greeter for betsy and is there any last log files that i could view and see what exactly was removed?

and maybe the "yes, remove all of these now!" text confirmation needs to be added to more stuff, so that this thing could not happen anymore in the future? :roll:
i was trying to install teamviewer 13 in the first place, but then got some libqt5gui5 dependency errors, so i started to remove and update those, but something probably went too far....

and the last thing that it actually did was removing the libqt5gui5 stuff itself during the installation procedure? like i ran the libqt5gui5-5.9.1.deb package and then it said that i need to type in "install -f" to finish the installation, but the only thing that this did was removing the just updated libqt5gui5-5.9.1 package itself? (+gave the autoremove notice also). so what was the point of all of that..... :roll:
Last edited by screenshot on Tue Jan 02, 2018 3:53 am, edited 1 time in total.

kevinthefixer
Level 4
Level 4
Posts: 242
Joined: Thu Jul 23, 2015 10:36 pm

Re: autoremoved network-manager and the greeter?

Postby kevinthefixer » Sun Dec 10, 2017 9:14 pm

Easiest way out of that mess is a fresh clean install. Maybe the only way.

deepakdeshp
Level 9
Level 9
Posts: 2815
Joined: Sun Aug 09, 2015 10:00 am

Re: autoremoved network-manager and the greeter?

Postby deepakdeshp » Mon Dec 11, 2017 1:27 am

kevinthefixer wrote:Easiest way out of that mess is a fresh clean install. Maybe the only way.

Yes that's correct
If I have helped you solve a problem, please add [SOLVED] to your first post title, it helps other users looking for help, and keeps the forum clean.
I am using Mint 18.3 Cinnamon 64 bit with AMD processor . Memory 8GB

screenshot
Level 1
Level 1
Posts: 36
Joined: Sat Feb 01, 2014 8:54 am

Re: autoremoved network-manager and the greeter?

Postby screenshot » Thu Dec 28, 2017 5:45 am

well, i managed to get some of the stuff back with the aptitude command, but now i am stuck with the default Xsession display manager?

so how could i get the lightdm or mdm running normally again? if i switch from the blank mdm to lightdm again, then it starts with the default Xsession again, but neither of them have any menus.... so how could i get the menus back? atm it says that mintmenu is already the latest version... but still, nothing is displayed except the mouse cursor... and i cant even press ctrl+alt+t to get the terminal, so i have to use ctrl+alt+F1...

screenshot
Level 1
Level 1
Posts: 36
Joined: Sat Feb 01, 2014 8:54 am

Re: autoremoved network-manager and the greeter?

Postby screenshot » Thu Dec 28, 2017 7:31 am

ok, now i got the menus also back via this command:

Code: Select all

sudo apt-get install mate-desktop-environment-extras

but now it does not ask me any wifi passwords, so i have to enter each of them manually and then click on the wifi ssid again? :cry:

and the previous commands i used to get the lightdm and network manager back(by using a wired connection):

Code: Select all

sudo dhclient eth0
sudo aptitude install libpam-systemd (because it was a dependency for network-manager)

so that gave me lots of options how to install it and i entered No couple of times until it offered me to install lots of things without removing the others (but still downgraded 1 package, which i dont remember atm). but it basically offered to install all missing dependencies, so i chose that option and entered Yes.

so now i only have this wifi issue and im not even sure how to get MDM working, because these commands..:

Code: Select all

echo $GDMSESSION
echo $XDG_CURRENT_DESKTOP

..told me that i am currently using lightdm-xsession and MATE, although i tried to switch to MDM via this command:

Code: Select all

sudo dpkg-reconfigure mdm

screenshot
Level 1
Level 1
Posts: 36
Joined: Sat Feb 01, 2014 8:54 am

Re: autoremoved network-manager and the greeter?

Postby screenshot » Thu Dec 28, 2017 10:09 am

2 more issues:
logon box looks like its still the default and simple Xsession box
all of the windows, including the main menu have like a black bar around them, so they look kinda weird

User avatar
Moem
Level 12
Level 12
Posts: 4419
Joined: Tue Nov 17, 2015 9:14 am
Location: The Netherlands
Contact:

Re: autoremoved network-manager and the greeter?

Postby Moem » Thu Dec 28, 2017 4:41 pm

If you'd just backed up your data and reinstalled, you'd have been back in business weeks ago. Any particular reason why you're not doing that?
Image

If your issue is solved, kindly indicate that by editing the first post in the topic, and adding [SOLVED] to the title. Thanks!

screenshot
Level 1
Level 1
Posts: 36
Joined: Sat Feb 01, 2014 8:54 am

Re: autoremoved network-manager and the greeter?

Postby screenshot » Fri Dec 29, 2017 4:34 am

that would take too much time...
but now i switched back to mdm and also got some login screen themes going, so now there are 1,5 issues left:
1) have to enter all wifi passwords manually
1.5) mint-x theme has weird black bars around the windows and menus (i now chose another theme, which does not have these bars around...)

screenshot
Level 1
Level 1
Posts: 36
Joined: Sat Feb 01, 2014 8:54 am

Re: autoremoved network-manager and the greeter?

Postby screenshot » Tue Jan 02, 2018 3:52 am

and i guess that the best way to check which display manager is used, is to type into the console: pstree
(and i guess the default for lmde2 actually was MDM, and lightdm was the simple looking Xsession version...)
everything else was solved with a fresh linux reinstall...


Return to “Installation & Boot”