On 11/26/18 6:58 PM, King Beowulf wrote:
<...>
I clicked on the Firefox icon in KDE and saw the little red firefox
bouncing on the screen. After about a minute or less, the bouncing
stopped, but Firefox was not loaded.
Looks like I broke something.
in KDE, as a regular user (not root), open konsole and run firefox to
see what errors it spits out.
bash-4.3$ firefox
xPCOMGlueLoad error for file /usr/lib64/firefox/libxul.so:
/usr/lib64/../lib64/libz.so.1: version 'ZLIB_1.2.9' not found (required
by /usr/lib64/firefox/libxul.so)
Couldn't load XPCOM.
bash-4.3$
the firefox icon on the KDE bar is sometimes not pointing to the right
place. you can also try running from the KDE menu tree.
Acts the same.
you can also see if Seamonkey or konquerer gives the same error(s).
Seamonkey loads.
Konqueror loads.
During install, if you selected network manager to control the network,
switching from wireless to wired can confuse it for some network
devices.
I don't recall selecting network manager, but I didn't write down what I
did say.
Also note, that if you set yo wireless with network manager
and used KDE wallet to store the passphrase, XFCE can't see it. when
switching DE or network interface, in the DE (you need to have teh
networkmanager applet running), as a normal user, open a terminal and
run:
su -
<root password>
/etc/rc.d/rc.networkmanager restart
exit
(remember that Slackware does NOT use systemd or sudo). Network Manager
has some nice features but the GUI applet is easily confused and the CLI
version is cryptically brain dead.
I haven't tried wireless yet. But I'll keep this in mind when I get
that far.
You can always repeat the network configuration as root in CLI with
"netconfig" - DHCP for wired is fine,
This is what I did in the install, and what I just repeated:
HOSTNAME: Thinkpad-X200
Domain name: org
Chose DHCP
and then make sure
/etc/rc.d/rc.networkmanager is not executable (networkmanager does DHCP
differently). if it is,
/etc/rc.d/rc.networkmanager stop
root@Thinkpad-X200:~# /etc/rc.d/rc.networkmanager stop
-su: /etc/rc.d/rc.networkmanager: Permission denied
chmod -x /etc/rc.d/rc.networkmanager
I probably should have done this before trying to stop networkmanager:
root@Thinkpad-X200:~# ls -l /etc/rc.d/rc.networkmanager
-rw-r--r-- 1 root root 2646 Jun 12 2016 /etc/rc.d/rc.networkmanager
root@Thinkpad-X200:~#
When you are ready for wifi and networkmanager, Ben or I will help you
with getting the dhcp glitches fixed. you can either use Slackware's
tools OR networkmanager to control networking, not both.
I'd like to get comfortable getting simple things to work reliably first
before worrying about getting wireless to work.
When X hangs, it may just be X Windows not Firefox etc. KDE and XFCE
use different GUI widgets. To see if it is just X and not the whole
system. press ctrl-alt-backspace to kill X and drop to the command line
(this is why I never run a graphical login manager). You can then
"startx" to reload. Again, be sure to update as there have been a
number of important bug fixes to X.org, FF, etc.
I did the update thing during the initial install. I just did it again.
did all 124 updates trundle by? and kernel 4.4.157?
xwmconfig sets the user DE. setting for "root" will not set for your
normal user and vice versa. it copies '/etc/X11/xinit/xinitrc.<DE>' to
'$HOME/.xinitrc' and if that doesn't exist '/etc/X11/xinit/xinitrc' is a
symlink to ''/etc/X11/xinit/xinitrc.kde' as the default.
During install, when asked about your system clock, did you pick local
or UTC?
Local.
If you set UTC but the BIOS clock is local time you then just
confused the heck out of it.
1. Set BIOS to correct local time
Did so. But I think I didn't exit correctly. I just re-did it, and the
clock now looks correct.
2. open command terminal
su -
<root password>
timeconfig
... set for loacl and timezone
nano /etc/ntp.conf
...uncomment one or more NTP servers
Uncommented 0.
..save
ntpd -gq
bash-4.3# ntpd -gq
26 Nov 03:22:31 ntpd[2089]: ntpd [email protected] Fri Jun 3 23:08:22 UTC
2016 (1): Starting
26 Nov 03:22:31 ntpd[2089]: Command line: ntpd -gq
26 Nov 03:22:31 ntpd[2089]: proto: precision = 1.047 usec (-20)
26 Nov 03:22:31 ntpd[2089]: restrict: 'monitor' cannot b disabled while
'limited' is enabled
26 Nov 03:22:31 ntpd[2089]: unable to bind to wildcard address :: -
another process may be running - EXITING
bash-4.3#
Weird, ntpd thinks it is already running. was rc.ntpd executable on the
last boot? as root
lsof -i | grep ntp
There are six lines reporting. I was trying to think of how I could copy
the information and get it over to this machine so I could put it in
this email, rather than typing the lines, which is what I've been doing.
I realized that I could log in to my email account from a web browser.
Since Firefox is broken, I tried Konqueror. I got as far as logging in,
and then Konqueror dies. If you need the error message it spits out,
I'll try it again tomorrow. For now, I need to go to sleep. :-)
--
Regards,
Dick Steffens
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
