Please login or register.

Login with username, password and session length
Advanced search  


Visit our home page for VL info. For support and documentation, visit the Vector Linux Knowledge Center or search the Knowledge Center and this Forum using the search box above.

Pages: 1 [2] 3 4 ... 10
 on: March 21, 2017, 07:30:09 am 
Started by overthere - Last post by nightflier
Speaking of ISOs.. you will see B2.1 as well. It is experimental and has a small issue where you need to select "icewm" from GDM. It will be rebuilt and replaced once a new version of icewm makes it into the repo.

 on: March 21, 2017, 07:26:15 am 
Started by overthere - Last post by nightflier
The NM issue was figured out and fixed in B2, released after RC2. Yes, I know that is backwards, but we decided to match STD in versioning, and haven't been able to remove the old ISOs yet.

You should be able to fix this issue simply by creating a directory in your home dir, called "~/.cache". Let us know how that works.

 on: March 21, 2017, 07:08:31 am 
Started by overthere - Last post by rbistolfi
I have seen the NM applet issue, still trying to figure out whats going on. I think it may be a service without permissions or similar. I will keep researching.

 on: March 21, 2017, 04:54:42 am 
Started by overthere - Last post by overthere
Hi Folks
Installed the Vectorlinux light 7.2 Rc2 32 today.

I have an issue with the nm-applet, when clicked it shows available networks, however when one is selected it fails to pop up the password dialog. and the icon simply spins for a bit and stops.

one can enter the password manually but it takes 30 seconds or so for the wifi security tab to appear in the edit dialog.

If manually entered it connects, relogin and reboot is reconnected.

if deleted the issue returns.

Otherwise I like it so far. added leafpad to the ice panel, updated gslapt and added gimp and pysol, updated menu and unchecked the check for updates box in smplayer to stop the nag.

then naturally added fluxbox and feh

the included xdg menu maker and scrot along with a menu edit link and feh for easy wallpaper made for a simple alternative.


Is the nm-applet issue just me?

Anyway nice work


 on: March 16, 2017, 08:38:07 pm 
Started by overthere - Last post by overthere
Hi Folks
Installed the 32 bit STD beta 2 to the toshiba satellite.

The default icon theme is now fienza dark but the above applies, cupertino folder and theme exist in/usr/share/icons but the icons are missing. adding the icons does solve the issue if the item is selected.

when opening thunar in terminal as root I do not have access to the usb thumb drive, thus to add the cupertino icons as test I had to create a folder in home and copy items there, then copy as root from home folder to /usr/share.

The upper panel still includes a /root folder,

Abiword does not spell check. although boxes are checked for the feature.

smplayer gives a popup for newer version.17x

Screenshot from the upper panel does not work by default,  removing the item from the panel and then adding it to the panel solved the problem.

Firefox is not set as the default browser.

no serious issues so far.

keep up the good work


 on: March 15, 2017, 06:08:35 pm 
Started by StrayBit - Last post by roarde
Code: [Select]
# vclockset
I should either point the "System Date and Time" entry there, or remove it from the menu. The point/click way to do the above is to walk in through vasm legacy.

 on: March 15, 2017, 02:13:38 pm 
Started by StrayBit - Last post by StrayBit
When I installed 7.2Beta, the hardware clock was set to local (US Mountain) time.  I have changed the clock to GMT (or is it UCT?).  How do I tell VL that it is not local time?

 on: March 15, 2017, 02:10:52 pm 
Started by StrayBit - Last post by StrayBit
I am working with VL7.2beta and am trying to get mysql running.
I have tried
bruce: mysqld&
root: mysqld&
In both cases it finally exits.  During the process (in thunar) I created /var/mysql directory and changed the permissions so everyone had read/write.  Perhaps I need to do something else?

 on: March 11, 2017, 09:57:00 am 
Started by Casey - Last post by roarde
Code: [Select]
# In your own home directory
cp -apr /boot/initrd-tree ./         # just in case
su root -c 'mkinitrd -F'

That will probably cover it. See the mkinitrd manual page for why -F should work here.

Emphasis on the italics as "maybe". We haven't done a whole lot of this, and the wiser heads are on vacation  :)
Code: [Select]
grub-mkconfig -o /boot/grub/grub.cfgshould finish it off.

The "modules not found" message is indeed from the initrd. The above method should result in a slightly larger initrd, with modules for both kernels. Can be cleaned up later.

 on: March 11, 2017, 09:23:28 am 
Started by Casey - Last post by Casey
I'm using VL Light 7.1 on an old laptop, and I used gslapt to update the kernel from the original 3.18.16 to 3.18.44.  Unfortunately, I didn't discover the recommended method until it was too late.  (According to  I should have used slapt-get from the command line to ADD a new kernel without removing the old one.)  I think gslapt has removed some (but not all) of the old kernel's files, although I can still boot to either kernel (after running grub-mkconfig).

I'm concerned by the message "No kernel modules found for Linux 3.18.44" that appears on the system console early in the boot process.  My guess is that it has something to do with the broken links and/or obsolete initrd-tree in my /boot directory.  Before I attempt to fix something that isn't truly broken, can anyone advise me about whether or not the files in /boot need to be manually altered after a kernel update?  I'm new to the kernel update process, and I'm hesitant to mess around with something I don't fully understand.  I did look at the README.initrd file in /boot, but I'm still unsure about what paramaters I might need for my setup (using GRUB2 with two EXT3 partitions, plus one swap partititon - see below).

Here's the revelent portion of the startup messages:
Code: [Select]
[    3.658890] Switched to clocksource tsc
[    3.695840] random: nonblocking pool is initialized
No kernel modules found for Linux 3.18.44
[    9.995374] kjournald starting.  Commit interval 5 seconds
[    9.995663] EXT3-fs (sda6): mounted filesystem with ordered data mode
/boot/initrd.gz: exiting
/init: line 344: plymouth: not found
INIT: version 2.88 booting
Mounting /proc file system
mount: proc already mounted
==> rc.S Setting up the base system configuration

And here's what I've got on my system:
Code: [Select]
~ $ uname -srv
Linux 3.18.44 #1 SMP Fri Oct 28 14:47:09 CDT 2016

~ $ mount |grep ^/dev
/dev/sda6 on / type ext3 (rw)
/dev/sda8 on /home type ext3 (rw)
/dev/shm/tmp on /tmp type none (rw,bind)

~ $ slapt-get --installed | grep -i kernel-
autofs-5.0.5-i586-3vl71 [inst=yes]: autofs (kernel-based automounter)
kernel-3.18.44-x86-1vl71 [inst=yes]: VectorLinux linux-3.18.44 kernel
kernel-firmware-20150430_git-noarch-1vl71 [inst=yes]: kernel-firmware (iFirmware for the kernel)
kernel-headers-3.18.44-x86-1vl71 [inst=yes]: forum.vectorlinux.com18.44 headers
kernel-modules-3.18.44-x86-1vl71 [inst=yes]:

~ $ ls -l /boot
total 25376
lrwxrwxrwx  1 root root       37 Feb 28 02:20 README.initrd -> /usr/doc/mkinitrd-1.4.7/README.initrd
lrwxrwxrwx  1 root root       18 Feb 28 02:19 ->
-rw-r--r--  1 root root  3256952 Oct 28 14:47
drwxr-xr-x  2 root root     4096 Feb 28 02:57 bitmap/
lrwxrwxrwx  1 root root       14 Feb 28 02:19 config -> config-3.18.16
-rw-r--r--  1 root root   145622 Oct 28 14:47 config-3.18.44
drwxr-xr-x  5 root root     4096 Mar  4 11:44 grub/
drwxr-xr-x  3 root root     4096 Jan  5  2014 grub2/
drwxr-xr-x 13 root root     4096 Feb 28 02:57 initrd-tree/
-rw-r--r--  1 root root 11052599 Feb 28 02:59 initrd.gz
lrwxrwxrwx  1 root root       15 Feb 28 02:19 vmlinuz -> vmlinuz-3.18.16
-rw-r--r--  1 root root  5731232 Feb 28 02:57 vmlinuz-3.18.16
-rw-r--r--  1 root root  5720752 Oct 28 14:47 vmlinuz-3.18.44

Note that the directory entries for config and are in red, which tells me they are broken links.  The entry for initrd.gz is also in red, but I don't know why.  Also, vmlinuz seems to be pointing to the wrong (old) kernel.  I'm not sure if I need to fix these three broken links, remove the old initrd-tree and the initrd.gz file before running mkinitrd, or even if I should run mkinitrd at all.  I'll certainly make a backup copy of the entire /boot directory before I do anything, but I'd like to know what the "best practice" is for bringing everything up-to-date.  Can anyone offer some tried & true advice?  Thanks!

Pages: 1 [2] 3 4 ... 10