Was just computing along tonight and I needed to open the terminal. I clicked on the panel shortcut and nothing. Just a spinning wheel. I went to the Menu button (bottom left) and opened the admin page and clicked ‘Terminal’ in there and same thing… spinning icon and nothing popped up. I could launch other programs, just the Terminal was giving me problems.
Tried uploading logs but the system said I can’t do it… here’s a Google drive link:
A reboot fixed it but this is the 2nd time I’ve had problems with something not launching and a simple reboot fixed it. Maybe I should switch to the LTS kernel?
I’ve decided to stop using TeamViewer with Antergos and am looking for an alternative. I’m dropping TeamViewer because every time I used it, the screen would flash really bad when I moved the mouse. Another reason I’m dropping it, when my internet goes out, TeamViewer is useless. So I’m looking for something that doesn’t need internet access to work.
I have a Windows 7 box that I’ll be using to remote into the Antergos box. Sure, I have SSH access but want to have the whole “GUI” experience. :)
Since I’ll be using a Windows 7 box as the client, I thought… lemme see if I can just use the RDP client built into Windows 7 to access the Antergos box. So I installed (I think), xrdp? (or some rdp server) and I believe I have the RDP stuff all started on the Antergos box but when I use the Windows client (or rdesktop 192.168.1.5 from a Linux box), I get the following screen:
When I click the ‘Session’ box, there’s a few choices in there and no matter which one I pick, after typing in my username and password, that box disappears and nothing happens.
Do I need to add my user account to some ‘rdp’ group or is there some other program I need to install?
Or should I look into some *VNC solution? (Which do you recommend, seems all the VNC solutions for Arch are either abandoned or their package maintainers aren’t quite keeping up with the latest versions… UltraVNC for example. AUR has 1.2.1 (last updated in October of last year) but 1.2.2 is the latest).
I tried Remmina(sp?) but kept getting an error about how a UDP connection couldn’t be established. (I’m thinking that’s the reason for my problem posted in the screenshot… I think I’m missing some part of RDP.
I don’t have any firewall program installed on the Windows 7 box or Antergos so that’s no the problem.
I have a few Guest access SMB shares setup in Antergos. Other Linux boxes and a Windows 10 machine can access them without being prompted for a password but my Windows 7 box, not so much. I keep getting prompted for a password when it tries to hit the SMB share.
I looked at the guide ( https://antergos.com/wiki/desktops/gnome/sharing-files-and-folders-with-samba-definitive-guide/ ) and didn’t see anything about dealing with password prompts.
I looked at the Arch wiki on SMB and what they recommended to fix the password prompts, I already have in there.
Here’s my smb.conf file, what am I missing?
This is the main Samba configuration file. You should read the
smb.conf(5) manual page in order to understand the options listed
here. Samba has a huge number of configurable options (perhaps too
many!) most of which are not shown in this example
For a step to step guide on installing, configuring and using samba,
read the Samba-HOWTO-Collection. This may be obtained from:
Many working examples of smb.conf files can be found in the
Samba-Guide which is generated daily and can be downloaded from:
Any line which starts with a ; (semi-colon) or a # (hash)
is a comment and is ignored. In this example we will use a
for commentry and a ; for parts of the config file that you
may wish to enable
NOTE: Whenever you modify this file you should run the command “testparm”
to check that you have not made any basic syntactic errors.
#======================= Global Settings =====================================
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=131072 SO_SNDBUF=131072
strict allocate = Yes
read raw = Yes
server signing = No
write raw = Yes
strict locking = No
min receivefile size = 16384
use sendfile = Yes
domain master = yes
preferred master = yes
local master = yes
os level = 255
force user = gene
force group = sambashare
security = user
map to = Bad User
usershare path = /var/lib/samba/usershares
usershare max shares = 100
usershare allow guests = yes
usershare owner only = yes
workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = WORKGROUP
server string is the equivalent of the NT Description field
server string = Samba Server
Server role. Defines in which mode Samba will operate. Possible
values are “standalone server”, “member server”, "classic primary
domain controller", “classic backup domain controller”, "active
directory domain controller".
Most people will want “standalone server” or “member server”.
Running as “active directory domain controller” will require first
running “samba-tool domain provision” to wipe databases and create a
server role = standalone server
This option is important for security. It allows you to restrict
connections to machines which are on your local network. The
following example restricts access to two C class networks and
the “loopback” interface. For more examples of the syntax see
the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 127.
Uncomment this if you want a guest account, you must add this to /etc/passwd
otherwise the user “nobody” is used
; guest account = pcguest
this tells Samba to use a separate log file for each machine
log file = /var/log/samba/%m.log
Put a capping on the size of the log files (in Kb).
max log size = 50
Specifies the Kerberos or Active Directory realm the host is part of
; realm = MY_REALM
Backend to store user information in. New installations should
use either tdbsam or ldapsam. smbpasswd is available for backwards
compatibility. tdbsam requires no further configuration.
; passdb backend = tdbsam
Using the following line enables you to customise your configuration
on a per machine basis. The %m gets replaced with the netbios name
of the machine that is connecting.
Note: Consider carefully the location in the configuration file of
this line. The included file is read at that point.
; include = /usr/local/samba/lib/smb.conf.%m
Configure Samba to use multiple interfaces
If you have multiple network interfaces then you must list them
here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24
Where to store roving profiles (only for Win95 and WinNT)
%L substitutes for this servers netbios name, %U is username
You must uncomment the [Profiles] share below
; logon path = \%L\Profiles%U
Windows Internet Name Serving Support Section:
WINS Support - Tells the NMBD component of Samba to enable it’s WINS Server
; wins support = yes
WINS Server - Tells the NMBD components of Samba to be a WINS Client
Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
WINS Proxy - Tells Samba to answer name resolution queries on
behalf of a non WINS capable client, for this to work there must be
at least one WINS Server on the network. The default is NO.
; wins proxy = yes
DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
via DNS nslookups. The default is NO.
dns proxy = no
These scripts are used on a domain controller or stand-alone
machine to add or delete corresponding unix accounts
; add user script = /usr/sbin/useradd %u
; add group script = /usr/sbin/groupadd %g
; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
; delete user script = /usr/sbin/userdel %u
; delete user from group script = /usr/sbin/deluser %u %g
; delete group script = /usr/sbin/groupdel %g
#============================ Share Definitions ==============================
comment = Home Directories
browseable = no
writable = yes
Un-comment the following and create the netlogon directory for Domain Logons
; comment = Network Logon Service
; path = /usr/local/samba/lib/netlogon
; guest ok = yes
; writable = no
; share modes = no
Un-comment the following to provide a specific roving profile share
the default is to use the user’s home directory
; path = /usr/local/samba/profiles
; browseable = no
; guest ok = yes
NOTE: If you have a BSD-style print system there is no need to
specifically define each individual printer
comment = All Printers
path = /usr/spool/samba
browseable = no
Set public = yes to allow user ‘guest account’ to print
guest ok = no
writable = no
printable = yes
This one is useful for people to share files
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes
A publicly accessible directory, but read only, except for people in
the “staff” group
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = no
; printable = no
; write list = @staff
A private printer, usable only by fred. Spool data will be placed in fred’s
home directory. Note that fred must have write access to the spool directory,
wherever it is.
; comment = Fred’s Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
A private directory, usable only by fred. Note that fred requires write
access to the directory.
; comment = Fred’s Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no
a service which has a different directory for each machine that connects
this allows you to tailor configurations to incoming machines. You could
also use the %U option to tailor it by user name.
The %m gets replaced with the machine name that is connecting.
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes
A publicly accessible directory, read/write to all users. Note that all files
created in the directory by users will be owned by the default user, so
any user with access can delete any other user’s files. Obviously this
directory must be writable by the default user. Another user could of course
be specified, in which case all files would be owned by that user instead.
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no
The following two entries demonstrate how to share a directory so that two
users can place files there that will be owned by the specific users. In this
setup, the directory should be writable by both users and should have the
sticky bit set on it to prevent abuse. Obviously this could be extended to
as many users as required.
; comment = Mary’s and Fred’s stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
Quick update… I was able to hit ALT-F1? or CTRL-ALT-F1? and open up another console. I logged in as root, verified the scrub was finished and issued the ‘reboot’ command and all is well in the universe. TeamViewer was acting REALLY odd when I installed it. Lots of flashing screens when I moved my mouse. Maybe TeamViewer captured keyboard input when it hung as I tried logging in that one time? In any case, Antergos is rocking along nice and steady.
I’m going to remove TeamVIewer and switch to some VNC type of client for remote desktop. I also enabled SSH. :)
So Saturday morning, I ripped Mint 18 off my Plex media server setup and installed a fresh copy of Antergos with the Cinnamon desktop.
I got everything installed and working perfectly. Had a few stumbling blocks but all in all, not to bad. Saturday night, I had MDADM do a scrub of my RAID 5 array. It took about 12 hours but no errors reported. Sunday night, I kicked off a scrub of my RAID 6 array (neither of these arrays are boot drives… I have an SSD for my boot drive and the RAID arrays are just data… but remember this 2nd array scrub, it will come up later in my story).
So over the weekend, I did a couple reboots to test things out and everything was going like clockwork. Applied some updates, installed TeamViewer, all systems go!
When I got up this morning, I wanted to use TeamViewer to connect from a Windows box upstairs into Antergos to check on the progress of the MDADM scrub of the RAID 6 array. I connected via TV, typed my password to unlock the screen and opened a terminal, elevated my access and checked the status. It had about 2.5 hours left to go. I locked the screen and disconnected TV.
Then, I noticed that on this same Windows PC, it gave me an error about how the backup program couldn’t find ‘server-pc’ on the network. Then I remembered, when I installed Antergos, I set the hostname as ‘antergos-server’. I thought, no biggie, I’ll just use TeamViewer and connect to the Antergos box in the basement and correct that real quick.
I connected via TeamViewer, typed my password at the lock screen and got logged in with no problem. I opened a terminal and elevated my access and edited /etc/hostname and erased ‘antergos-server’ and typed ‘server-pc’ and saved the file and exited out of the editor.
I disconnected TeamViewer.
The PC STILL had problems seeing ‘server-pc’ then I remembered, I could just type ‘hostname server-pc’ to change it immediately (I couldn’t reboot because the scrub was still going).
Back to TeamViewer. I logged in and carried out the command and Antergos instantly switched the hostname to ‘server-pc’. I locked the screen then logged out of TeamViewer.
I didn’t bothered checking the Windows box if the backup program was happy now and was able to see ‘server-pc’ and back up it’s files so I moved on to something else. Breakfast.
After breakfast and right before needing to leave for work, I launched TV again as I wanted to check the status of the scrub. But this time, it got stuck at something like “initializing display”… or something along those lines. No biggie, TV has done this to me before with Mint so I closed it and re-opened it and tried connecting to the Antergos box again. Same problem.
I walked downstairs and jiggled the mouse to wake up the monitor. The lock screen came up. I typed my password (I could see the asterisks popping up) and hit enter and nothing happened. No error about wrong password, screen didn’t unlock, it just sat there.
Perplexed, I clicked on ‘Switch user’. This brought me to another login screen and I typed my password there and THEN the screen unlocked. I thought I was out of the woods but I quickly realized that nothing was launching. I clicked the terminal shortcut and I get a spinning wheel for a bit then back to mouse cursor. Clicking on the Chromium browser shortcut, same thing. Clicking on the “start” button, nothing comes up.
I don’t think the box is locked up or crashed because I was able to verify Plex is still running when I logged in to plex.tv from another computer.
What in the world did I do? Could changing that hostname be responsible for all this? Unfortunately, I don’t think SSH is running because when I tried SSH’ing into it, I got a ‘connection refused’ error.
I didn’t want to just force the computer off via the power button because the MDADM scrub is still running. Even if I could force a reboot, will it come back up and be in this same state?
I have a UPS hooked up to it and I did configure that to shutdown once the battery level is critical but with Arch being Arch… when I installed the APC-UPS program, I’m not sure if there was some SystemD service I needed to activate to get that working!?
So on a scale of 1 to 10, how screwed am I? :(
I’m stuck at work for the next 6 hours but would greatly appreciate any and all offers of assistance!
@joekamprad Yep, I realize that. But with Mint… if you install MDADM and set up a RAID array with it, I believe by default, MDADM automatically does scrubs.
With Arch, it seems the scrubs are not automatic but maybe need to be manually set up. Either way, I think I found the command to check so I’ll go ahead and mark this as solved.
I think I read somewhere that if you use MDADM, it automatically does a scrub once a month (maybe this only applies to Mint as their developers turn that on when you install the package?!?).
But with Arch (which Antergos is based off of), I read notes about needing to add a a cron job manually or using some systemd AUR script to get scrubbing turned on.
So what say you, masters of the Antergos… “set it and forget it” or manually adding it to cron.
So as I got ready to convert another PC in my house from Windows to Antergos, I paused for a moment. I thought, “Maybe I should give pure Arch a shot?” The last time I did that, I’m embarrassed to admit this but, I remember booting the live Arch ISO and being dumped out to a terminal. I was thinking, “where the heck is the GUI installer?” I quickly discovered that the Arch ISO does exactly this. Dumps you out to terminal and puts you in complete control. COMPLETE. The reason this was so jarring to me is, after trying practically every distro under the sun (and all of them having GUI installers that after the OS was installed and you rebooted, you were dumped into a pretty GUI (Cinnamon, KDE, Gnome, etc.)), I was dumbfounded why Arch (for as popular as it is) didn’t offer some sort of basic installer and the option to guide you through installing xorg and a desktop manager of your choice. I guess this is what makes Arch so… Arch.
So with that … I present to you, my decent into chaos …
For attempt # 1 at installing Arch, I opened up a 2nd terminal and used the ALT-Arrow key and brought up the ReadMe/Install notes text file included with the distro in another terminal and carried out the steps it guides you through. I’m not the quickest typist in the world so after about 30-45 minutes, I issued the reboot command and … I killed Arch. It wouldn’t boot. I forget the exact error but I think that either I missed it or the included setup txt file isn’t very clear about the need to install a bootloader. I figured Arch would do this logical (to me) step with one of the commands I type but nope. No biggie., my fault. I should have realized at no point in that text file (again, unless I missed it) there’s mention of the need to install something like Grub. How can a Linux distro boot without a bootloader? It can’t. Guess I should have caught that. (I’m a newb though, don’t forget that!)
Attempt # 2, I reset the SSD I was using (fdisk) and this time, I had my iPad with me and followed along the the official Arch setup wiki. I repeated all my steps (making sure to install Grub this time!) and rebooted and… dead. When I issued the ‘grub-install’ command, I used /dev/sda1 instead of /dev/sda. Again, human error on my part. I didn’t know how to recovered from that so reboot and fdisk to start again! :)
Attempt # 3, re-did all the commands, issue my reboot and… I WAS ABLE TO BOOT ARCH!!! At this point I was doing mental back-flips sitting in awe that I was able to read a guide and install Arch! lol But seriously, I was pleased that so far, everything worked right. Then it was time to tackle installing xorg, proprietary Nvidia drivers and Cinnamon… so I could get my fancy GUI! And this… is where … things went to crap.
Before doing anything I quickly realized that even though the Arch setup identified my network card and was able to retrieve packages from the repositories, after that part of the setup was done and I rebooted, Arch decided that if I wanted to use my network card I’d have to enable it first. (To me… this is just beyond stupid. Yeah, yeah, “the Arch install lets you configure every aspect of your system from the ground up.” But come on!! So after 15-20 minutes of Googling, I finally stumbled upon the command to enable the DHCP service for my interface and network connectivity was restored!
Next up, time to install Cinnamon…
Since I couldn’t find a step-by-step guide on the Arch wiki for installing Cinnamon. I was forced to cobble the steps together via YouTube and various web sites. I succeeded in installing xorg (and all companion programs), my Nvidia drivers and Cinnamon. But now what do I do? I rebooted and figured Cinnamon would just auto-magically load. It didn’t. On the Arch wiki, it mentions editing ~/.xinitrc and adding a line so you can start Cinnamon manually. I want Cinnamon to start at boot though? Over the next 30 minutes, I looked and looked and couldn’t find anything that helped me.
At this point, from the first, few failed attempts of the install failures to not being able to get Cinnamon to run at boot, I’m about 6 hours into this madness. I was thinking… even if I get this PC running with pure Arch, God help me if I ever need to blow the install away and reload from scratch because I messed something up and couldn’t recover from it. Will I be facing another multi-hour install process?
This is when I reached for the Antergos live USB image and trashed the remnants of the Arch install and installed Antergos.
I love the stability that you can get with a Debian based distro but it really bothers me that the packages quickly stagnate after a few months and it can be a couple of years before you get new versions of programs. And when a new version comes along, it’s always recommended to backup your drive and install a fresh copy. Case in point, Mint. I really like Linux Mint. On one of my PCs, been using Mint 18.3 for a very long time. Now that 19 is out, while you can technically do an upgrade, officially, it’s recommended to wipe your drive and install a fresh copy. I know they offer security updates for 2 more years with Mint 18.3 but then what? Wipe/install 19 and a couple years later, rinse-repeat? Having to wipe out my drive every couple of years kinda sorta sucks.
This is where a rolling distro, Antergos, fits in perfectly! (And also, the Manjaro numbers on Distrowatch seem WAY to high. I think they’re gaming the system with their first place position. :) )
In closing, I’m happy that the folks behind Antergos can provide us with a GUI installer for Arch. Your work is greatly appreciated! To the Arch folks that might read this, I think it’s time some of your minds come together and develop some super basic GUI (or text) based installer for Arch and automate the install process. I can’t think of a single, good reason why I needed to go in and type a command to enable the DHCP service for my network card… that was used to pull down packages. Working during setup and not working after I’ve booted into Arch is (to me) really, really dumb. But I guess this is the purpose of Antergos, to bring Arch to the masses.
As I keep pounding away on my test Antergos box, I ran into a slight problem. When I go into the Systemd GUI (systemd-manager), it correctly shows the ‘sonarr.service’ as enabled:
but INCORRECTLY shows the sonarr.service as not started… but it IS running and I can access it via FireFox:
I’ve been installing/deleting Antergos over the past few weeks and I don’t recall having this problem before. Sonarr would always show green checks for both boxes.
Where can I look to get more details as to why Systemd-manager thinks the service isn’t running?
@olividir Totally agree, the more foreign languages included with Antergos, the better! But, if I select ‘US/English’ during the initial install, I can’t think of a single reason why I need all the other foreign dictionaries installed. It just adds bloat and leads to problems like this.
@joekamprad Do you know if the Antergos installer can be fixed so it only installs the dictionary for the language selected during setup? If Antergos did that, I wonder if this problem would have ever popped up?
Seems silly to have all these other dictionaries that will never be used.
Add me to the list. I’m a newbie with Linux (and Antergos) but is this more of an Antergos problem to fix or some upstream Arch issue?
Side note, I’m guessing hunspell-es is the Spanish dictionary but I wonder why that’s even installed when I picked English for my language?!
Using Sonarr, I ran into an issue.
Right now, I have Sonarr configured to run under my user and the ‘users’ group. Here is the sonarr.service file from systemd:
ExecStart=/usr/bin/sonarr -nobrowser -data=/var/lib/sonarr
… I recently applied an update to Sonarr and the packaged AUR file overwrote my username and group and reverted it back to:
I asked for help in the Sonarr forum and one of their suggestions was to use a .override file to prevent this from happening. I did some reading around and couldn’t find a solid answer so I decided to ask here. Any guidance would be appreciated.
Please skip over any warnings about the dangers of what I’m asking :)
When I boot up Antergos, I click the clock, (my name is already there and I can’t change it) and type my password and away I go.
What do I need to do to change things so it defaults to ‘root’ as the username? What I’m aiming for is when Antergos boots, it either auto-logs in as root or I type ‘root’ for the username and root’s password and I can log in, as root.
In case it helps, this is a fresh install. I picked the Cinnamon desktop and made no other changes.