VectorLinux

Cooking up the Treats => Distro development => Topic started by: uelsk8s on April 05, 2014, 11:09:44 am

Title: VL7.1 STD feedback and suggestions.
Post by: uelsk8s on April 05, 2014, 11:09:44 am
This is the place to share your experiences.
For bug reports, please go here: https://bitbucket.org/VLCore/vl71/issues/new
Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on April 06, 2014, 06:00:39 am
Flawless install (as usual).

Thought we were going to do a "summary" page of actions that were going to happen before the actual installation started?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: rbistolfi on April 07, 2014, 04:49:12 am
Flawless install (as usual).

Thought we were going to do a "summary" page of actions that were going to happen before the actual installation started?

Thats the plan but we didnt get around it yet. Do you guys think this is a priority for this release?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on April 07, 2014, 05:11:52 am
For me? No. For someone who's never installed it before? Might be a good idea.  ;D
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on April 07, 2014, 11:34:26 pm
system = intel p4 cpu 1.7 ghz intel d845ept2 board
         768 meg ram
         1280 x 1024 f-417 neovo monitor
         gforce gf4mx440se 128 meg agp

VL7.1 32 bit RC1 via CD

Known issues aside I'm likeing it so far, here are Xfce and fluxbox customixed with animated desktops  8)

https://www.dropbox.com/s/dmrvk1xsh4wehog/XfceRC1.png

https://www.dropbox.com/s/fagftyk5g2olkkh/FluxboxRC1.png
Title: Re: VL7.1 STD feedback and suggestions.
Post by: Colonel Panic on April 10, 2014, 03:49:56 pm
I downloaded it earlier this week and installed it today, and although it looks good there have been a couple of problems (not necessarily bugs).

When I was trying to use the text installer and configuring the timezone, the place selector stalled on the As and I ended up choosing Johannesburg (Africa) instead of London for my timezone, and so far I haven't been able to get networking going so I can't get online with it yet.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: Colonel Panic on April 11, 2014, 04:06:24 pm
A quick update: I booted Vector 7.1 RC1 up again today and oddly my internet connection worked even though the network icon on the desktop showed a cross, indicating that networking had been disabled. Still, all's well that ends well...

On another note, swap wasn't enabled by default when I booted it up as it is in other distros I've tried, so I had to set it manually, and there was also no option to enable swap when I installed Vector (or to set the other partitions to load on bootup), even though other distros I've seen which are based on Slackware, such as Salix and Absolute, do have these steps.

It's as though a decision was taken to truncate the text-based installation process in the interests of brevity.

Sorry, but IMO there's still work to be done before it's ready for release.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: Pita on April 11, 2014, 09:22:30 pm
RC1 32bit

Unable to get it to print. Cups will not detect my printers. Used system-config-printer to add manually.
Still does not print. Removed cups-1.6.3 installed cups-1.4.6, still no printing.

This pretty much will exclude  VL as my distro of choice.

In previous posts for testing I submitted cups error messages
and reported this issue several times w/o ever seeing a response.

I do not have this problem in slackware-14.1 or in Salix-14.1

Bye then!
Title: Re: VL7.1 STD feedback and suggestions.
Post by: hata_ph on April 11, 2014, 10:10:15 pm
Running on RC1 32 & 64bit in vbox...both can detect my HP P2055dn network printer automatically...test print work fine...

Pita, pls provide printer model.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: sledgehammer on April 12, 2014, 11:36:52 am
Downloaded 7.1 rcl 64 and put on usb stick with unebooten.

Want to install on samsung RF511 and lenovo n586, the samsung being my main machine (vl 7,0) and both being, I think, bought in 2011.  Both have big hard drives and the samsung has been acting up of late, particularly when trying to save files. Lenovo runs salix and is kept as emergency backup (not used).

first tried samsung with usb stick formatted as ext4 I think.  Tried advanced as I want to keep partitions.  Could not get out of little windows which first show up. Finally figured out that pushing "escape" would let me go to next window.  Then after the select "time" window, "next" did not work but I was dumped off to the root prompt.  So I reformatted the usb drive to fat32 with gparted and loaded vl 7.1 on it again, using unebootin. Noticed it said corrupted, "run xfs_repair" as it was coming up, but it went to windows anyway.  Did not need to use "escape" to go from one window to next, but had same problem: Dumped me off to root after "time" window.  Said corrupted..  Don't know how to use xfs_repair but tried xfs_repair -n and that didn't work.  Think I may have had to unmount something first.

So tried install on lenovo and before first window it said corrupted data. Same result whether usb stick was ext4 or fat 32. Tried non-gui install, with same result (corrupted)..Lenovo works fine on salix, so I doubt anything is corrupted.

Looked around for a blank cdrom, thinking I would try putting VL 7.1 RC1 on it and load from cd but can't find one.  Will pick some up next time I'm at the store and, meanwhile, think about it. I can always use my old IBM thinkpad t60p, now loaded with debian. Far as that goes, I usually like the thinkpad's square screen better than wide-screen anyway.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on April 12, 2014, 06:06:45 pm
The standard fat32 on usb should be fine for unetbootin

link regarding xfs_check and xfs_repair

http://docs.cray.com/books/S-2377-22/html-S-2377-22/z1029470303.html
Title: Re: VL7.1 STD feedback and suggestions.
Post by: sledgehammer on April 13, 2014, 02:04:48 am
VL 7.1 RC1 loaded fine on my lenovo from CD.  However, CD didn't help samsung.  Did same thing (blew up after the select lilo screen).  Hard drive is probably fried.  I have another but ill probably wait until 7.1 final to try it. 

On the Lenovo, kde basically doesn't work.  Seems find and all that but, for example, gslapt errors out as do a lot of the other programs.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: sledgehammer on April 13, 2014, 03:25:14 pm
Lyx and etmtk installed fine, though I had to use xfce rather than kde, and I had to update a couple of the etmtk dependencies.  Yate still won't work, from VL repository or slackbuilds.org.  I believe it has to somehow be yate-qt rather than yate, but, for the life of me, can't find a yate-qt to download.

John
Title: Re: VL7.1 STD feedback and suggestions.
Post by: Pita on April 13, 2014, 09:25:00 pm
Running on RC1 32 & 64bit in vbox...both can detect my HP P2055dn network printer automatically...test print work fine...

Pita, pls provide printer model.

Epson LQ-300 and Brother DCP-385C both connected to USB port.

Both print in Slackware, Slackel, Salix, Tails, TCl, Mint.......latest versions.

In my last post I mentioned that I never got a response on my various printer problem
reporting during Beta testing. That is not correct, there was one response .
Title: Re: VL7.1 STD feedback and suggestions.
Post by: hata_ph on April 13, 2014, 09:54:13 pm
Pita,

Sorry that I do not have similar hardware for testing. Do you found any error messages in the log files?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: hata_ph on April 13, 2014, 09:58:20 pm
Notice that samba service is enabled by default but /etc/samba/smb.conf is missing. But smb.conf-sample is there thou...
Title: Re: VL7.1 STD feedback and suggestions.
Post by: nightflier on April 14, 2014, 05:12:31 am
To add to hata_ph's observation: smb.conf-sample is there, but it's empty.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: roarde on April 14, 2014, 09:49:19 am
smb.conf:
Whatever was supplied by the samba package was formerly being overwritten by (or ignored because of) VASM's smb.conf copy. During this time, samba.SlackBuild failed to keep up with location changes in Samba's source tree; probably not noticed because the other, outdated copy was there. Samba's slackbuild needs to be updated and probably should copy the smb.conf-example that would be generated to smb.conf IF there's not one there already.

A little more info at https://bitbucket.org/VLCore/vabs/issue/45/samba-doesnt-start-on-fresh-install
Just don't have time to go further with this one myself right now.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: hata_ph on April 15, 2014, 06:46:34 pm
Notice when i use wget to download it prompt below messages...happen to both 32 & 64bit

Quote
vector://home/hata_ph/evolution/src
root:# wget http://download.gnome.org/sources/evolution/3.12/evolution-3.12.1.tar.xz
--2014-04-16 09:47:40--  http://download.gnome.org/sources/evolution/3.12/evolution-3.12.1.tar.xz
Resolving download.gnome.org... 209.132.180.168, 209.132.180.180
Connecting to download.gnome.org|209.132.180.168|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://download.gnome.org/sources/evolution/3.12/evolution-3.12.1.tar.xz [following]
--2014-04-16 09:47:42--  https://download.gnome.org/sources/evolution/3.12/evolution-3.12.1.tar.xz
Connecting to download.gnome.org|209.132.180.168|:443... connected.
GnuTLS: A TLS warning alert has been received.
Unable to establish SSL connection.
vector://home/hata_ph/evolution/src
root:#
Title: Re: VL7.1 STD feedback and suggestions.
Post by: hata_ph on April 17, 2014, 12:51:39 am
try vasm-legacy, notice below services are not yet implemented.

Quote
LOCALE
BOOT
STARTUP
FORMAT
MOUNT
Title: Re: VL7.1 STD feedback and suggestions.
Post by: vincent2 on April 19, 2014, 09:16:20 am
just downloaded vl 7.1 rc 1.1 the latest 64bit, installation went smoothly with usb disk, then booted into system desktop nicely.
but kernel's  still 3.12.16...now heartbleeding 's prevalent, kernel 3.14 series offers""known exploit detection"  features for securities, hope can get kernel 3.14 on test repo soon for better securities.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: bigpaws on April 19, 2014, 11:08:55 am
Vincent2 explain how kernel known exploit detection can detect heartbleed?

Bigpaws
Title: Re: VL7.1 STD feedback and suggestions.
Post by: vincent2 on April 19, 2014, 08:04:58 pm
you should try kernel 3.14.1 now from test repo, you'll see the differences.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on April 28, 2014, 07:05:41 pm
VL7.1 32bit RC2 appears to be missing startfluxbox in /usr/bin although fluxbox appears to be installed and appears in xsessions it fails to start if session is selected

perhaps my aging hardware but still booting /dev/sda2 via cd as installer hangs at installing bootloader when lilo to /dev/sda2 is selected in the installer
Title: Re: VL7.1 STD feedback and suggestions.
Post by: Lyn on May 01, 2014, 11:04:19 am
I get this error message, after installing RC2 over RC1 but not formatting the home partition:

System has no Xclients file, so starting a failsafe Xterm session.  Windows will have focus only if the mouse pointer is above them.  To get out of this mode type "exit" in the window.

I can start XFCE by typing startx but not ideal....

Can keep my home partition intact which is an improvement.  Oh an no option for starting fluxbox.

Installed IceWM using the IceWM mods via Gslapt and no entry for that either.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on May 01, 2014, 11:56:49 am
I get this error message, after installing RC2 over RC1 but not formatting the home partition:

System has no Xclients file, so starting a failsafe Xterm session.  Windows will have focus only if the mouse pointer is above them.  To get out of this mode type "exit" in the window.

I can start XFCE by typing startx but not ideal....

Can keep my home partition intact which is an improvement.  Oh an no option for starting fluxbox.

Installed IceWM using the IceWM mods via Gslapt and no entry for that either.


Lyn, was that the 32-bit or 64-bit version? I rarely format /home and the 64-bit version installed fine for me.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: nightflier on May 01, 2014, 02:28:15 pm
Installed IceWM using the IceWM mods via Gslapt and no entry for that either.

Lyn, that package is not a meta package that will pull in IceWM. It is used in the ISO creation for the Light version. The updated alpha release of Light is in the same directory as RC2. You are invited to give it a try. ;)
Title: Re: VL7.1 STD feedback and suggestions.
Post by: Lyn on May 01, 2014, 11:50:09 pm
I get this error message, after installing RC2 over RC1 but not formatting the home partition:

System has no Xclients file, so starting a failsafe Xterm session.  Windows will have focus only if the mouse pointer is above them.  To get out of this mode type "exit" in the window.

I can start XFCE by typing startx but not ideal....

Can keep my home partition intact which is an improvement.  Oh an no option for starting fluxbox.

Installed IceWM using the IceWM mods via Gslapt and no entry for that either.


Lyn, was that the 32-bit or 64-bit version? I rarely format /home and the 64-bit version installed fine for me.

Sorry 64bit version...
Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on May 02, 2014, 03:57:22 am
Did you, perchance, forget to check the "Install XFCE" box during install?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: caitlyn on May 07, 2014, 02:45:23 pm
I see the iso for RC1 but not for RC2 in the repository.  I probably don't know the new and wonderful place those things are stored as I haven't been around for quite some time.  If I'm going to do testing I'd like it to be the latest build.  Link, anyone?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: nightflier on May 07, 2014, 02:54:55 pm
Hi Caitlyn, welcome back.  :)

http://vlcore.vectorlinux.com/pkg/untested/veclinux-7.1/iso/
Title: Re: VL7.1 STD feedback and suggestions.
Post by: caitlyn on May 07, 2014, 06:38:43 pm
Thanks for the welcome.  I'll take a look at the new version but that's all I can promise.  I don't have much time to offer these days.

I did get the link from the chat room already.  I've never been known for being patient :)
Title: Re: VL7.1 STD feedback and suggestions.
Post by: caitlyn on May 07, 2014, 07:49:23 pm
I just installed Vector Linux 7.1 STD RC2 on my 4.5 year old HP Mini 110 netbook.  Any distro can work on this machine but most need some tweaking to get them to work after installation.  It's not a system where I expect anything to "just work". 

To my very pleasant surprise VL 7.1 just works on this netbook.  Wireless and wired internet configured correctly out of the box, video done right, sound fine.  The installer display was perfect on the netbook, something no previous version of VL accomplished, and in general the graphical installer is much more polished and much simpler than I remember.  Great job by the developers.

A few very minor quibbles:  I agree with the previous comment that hiding passwords should be included.  I'd rather if it was optional but it should be there.  Also, why Quit or Reboot at the end?  Aside from troubleshooting a problematic install, why would anyone just quit?  Perhaps that button should be renamed to drop to shell or something.  Finally, just before packages start installing there is a period where, on older hardware like this, the installer looks like it hangs for quite a while.  It isn't hung; it is working but there are no visual cues to tell a VL newcomer to be patient.

On the overall I really, really like what I see.  Huge improvement over 7.0 when it was first released.  I'll bash on it over the next few days and see if I can come up with anymore bugs.  I'll also give the 64-bit a go next week when I'll have some time at home on the desktop.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: Lyn on May 08, 2014, 12:27:52 am
Did you, perchance, forget to check the "Install XFCE" box during install?

No I checked that :-)
Title: Re: VL7.1 STD feedback and suggestions.
Post by: caitlyn on May 08, 2014, 05:27:07 am
That raises another question.  Why is Install XFCE the only software choice?  If you're not offering another desktop shouldn't that step be skipped.  It's sure to cause confusion to newcomers.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on May 08, 2014, 05:33:24 am
That raises another question.  Why is Install XFCE the only software choice?  If you're not offering another desktop shouldn't that step be skipped.  It's sure to cause confusion to newcomers.
Advanced install mode will let you install a text-only system.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: caitlyn on May 08, 2014, 02:49:06 pm
VL 7.1 STD RC2 (32 bit) on my netbook:  I installed Midori and it won't run.  The browser does launch but crashes withing a few seconds.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on May 09, 2014, 12:32:59 pm
Could you launch it from a terminal window and post the output please?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: caitlyn on May 09, 2014, 04:50:53 pm
Here you go:
Code: [Select]
cmartin:$ midori

(midori4:2560): GLib-Net-WARNING **: couldn't load TLS file database: Error reading file '/usr/share/ca-certificates': Is a directory

(midori4:2560): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(midori4:2560): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-menu-bar-popup-delay after class was initialised

(midori4:2560): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-can-change-accels after class was initialised

(midori4:2560): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-menu-popup-delay after class was initialised

(midori4:2560): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-menu-popdown-delay after class was initialised

(midori4:2560): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-label-select-on-focus after class was initialised

(midori4:2560): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-menu-images after class was initialised

(midori4:2560): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-button-images after class was initialised

(midori4:2560): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-scrolled-window-placement after class was initialised

(midori4:2560): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-entry-select-on-focus after class was initialised

(midori4:2560): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-entry-password-hint-timeout after class was initialised

(midori4:2560): libsoup-WARNING **: (soup-uri.c:574):soup_uri_copy: runtime check failed: (SOUP_URI_IS_VALID (uri))
Segmentation fault
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on May 10, 2014, 12:55:13 am
Installed VL64bit RC2 to dell optiplex 745 via dvd rw.
onboard graphics, sata dvd and hdd

The gui installer would not load but did give a text installer

chose advanced and created a / and swap partitions then proceeded with install
checked xfce and lilo
all went smooth and default lilo installed to my surprise

booted to xfce desktop with two options for panel
the wallpaper was xfce mouse, had to add the wallpaper from usr/share/wallpaper
..had the issue in 32bit and think I solved putting the default wallpaper in the same folder.

fluxbox and awesome are in the session list but not an option..same in 32bit..are they to be removed or do I need to install for the option to have an effect? would be better if the xsession was installed with or it worked..whatever
connected to network and firefox loads the forum thus a post

have sound for dvd after quick adjust in umplayer preferences and tube seemed to work

anyway nice so far
Title: Re: VL7.1 STD feedback and suggestions.
Post by: Locator on May 10, 2014, 05:58:18 pm
My experience with VL7.1 has been that when it won't recognize my USB keyboard and/or mouse, so as a result, when it gets to the first install screen my mouse pointer freezes, and more with it  :'(, and during the one or two rare times when I was able to get past that point (by using a spare PS2 mouse I happened to have), I was able to get to the logon screen - at which point my mouse pointer froze after one second, and my USB keyboard was acting rather 'buggy' (When I would press the keys, the cursor would move, but no text would appear.

By the way, I have a Gigabyte Z77-DS3H motherboard (brand new).
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on May 11, 2014, 12:48:25 am
VL64bit dvdrw install to optiplex 745(slim)

Added an ati radeon x1300 pro to the pci-e slot ( max for psu), up the ram to 4gig (max) added a new dvdrw drive and a larger hd, then reinstalled VLocity

I still get the text installer and same results but tooling around gave no issues so far

install to /dev/sda2 with lilo to / same as 32 bit
guessing this is no longer possible with the kernel upgrade as it worked fine during earlier beta tests.
booted fine via dvd: linux root=/dev/sda2 ro

Here is Vlocity with animated desktop

https://www.dropbox.com/s/ybkyhueioxdbbms/aniVLocity.png

Not fond of this box (hardware) but One mans junk is anothers...
Title: Re: VL7.1 STD feedback and suggestions.
Post by: nightflier on May 11, 2014, 03:50:35 am
When I would press the keys, the cursor would move, but no text would appear.
I had that happen on a machine with nVidia graphics. If I typed username and password it would log me in and be ok after that. Did you get past that point?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on May 11, 2014, 05:00:29 pm
With an older nvidia card (gforce gf4mx440se 128 meg agp), ps2 keyboard and usb mouse I have a similar issue with the login...no text in session or language and cursor moved in name box with no text.

I found that clicking language then clicking cancel would then magically show text in sessions and language as well as text in the login box. this is consistent

once logged in all is well with the exception the odd icon will appear opaque until touched. otherwise fine

I can login as usual, not seeing the text and works the same. an accepted hardware issue for me (lest I find a card to fit the slot). the proprietary drivers are not as good on this old card but may be an alternative for newer nvidia cards.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: Locator on May 11, 2014, 07:22:34 pm
When I would press the keys, the cursor would move, but no text would appear.
I had that happen on a machine with nVidia graphics. If I typed username and password it would log me in and be ok after that. Did you get past that point?
Sometimes yes, and sometimes no. So for now I have ended up going back to Vector Linux 7.0 (at least until VL7.1 gets fixed), because at least I can get it to work correctly with my computer setup.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on May 12, 2014, 07:03:35 am
Here you go:
Code: [Select]
cmartin:$ midori

(midori4:2560): GLib-Net-WARNING **: couldn't load TLS file database: Error reading file '/usr/share/ca-certificates': Is a directory

(midori4:2560): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(midori4:2560): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-menu-bar-popup-delay after class was initialised

(midori4:2560): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-can-change-accels after class was initialised

(midori4:2560): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-menu-popup-delay after class was initialised

(midori4:2560): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-menu-popdown-delay after class was initialised

(midori4:2560): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-label-select-on-focus after class was initialised

(midori4:2560): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-menu-images after class was initialised

(midori4:2560): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-button-images after class was initialised

(midori4:2560): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-scrolled-window-placement after class was initialised

(midori4:2560): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-entry-select-on-focus after class was initialised

(midori4:2560): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-entry-password-hint-timeout after class was initialised

(midori4:2560): libsoup-WARNING **: (soup-uri.c:574):soup_uri_copy: runtime check failed: (SOUP_URI_IS_VALID (uri))
Segmentation fault

Which ISO did you install?
I just tried midori on the 64-bit RC2 and it works flawlessly.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on May 12, 2014, 10:17:35 pm
fresh install 32bit rc2
connected and added midori

you will likely see the GLib warnings regardless

libsoup 2.42.0 should already be installed.

Midori opens here without segmentation (perhaps as libsoup IS already installed)

however it is missing icons for "add new tab" and "close tab" or "speed dial"? both sides of the tab have a pop up for speed dial but clicking the red circle with the line through on the right closes the tab

I took a screenshot but can not log in to dropbox with midori
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on May 13, 2014, 08:21:36 am
VLocity 64bit rc2

Galculator has no icon in the window buttons and window menu. ie: when minimized

It does have icon in the applications menu and panel launcher and menu
Title: Re: VL7.1 STD feedback and suggestions.
Post by: caitlyn on May 14, 2014, 10:28:56 am
Quote from: M0E-lnx link=topic=18182.msg101511#msg101511 date=1399903415[/quote
Which ISO did you install?
I just tried midori on the 64-bit RC2 and it works flawlessly.
32-bit RC2 on my netbook.  I haven't done an install on a 64-bit machine yet.  Please try it on a 32 bit system.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on May 14, 2014, 12:20:50 pm
Quote from: M0E-lnx link=topic=18182.msg101511#msg101511 date=1399903415[/quote
Which ISO did you install?
I just tried midori on the 64-bit RC2 and it works flawlessly.
32-bit RC2 on my netbook.  I haven't done an install on a 64-bit machine yet.  Please try it on a 32 bit system.

I tried on 32-bit too and it works fine for me.

Can you post the slapt-get --show midori info ?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: caitlyn on May 25, 2014, 02:13:51 pm
I tried on 32-bit too and it works fine for me.

Can you post the slapt-get --show midori info ?
Sorry it's taken so long to get back to you.  Here is what I get:
Quote
root:# slapt-get --show midori info
Package Name: midori
Package Mirror: http://vectorlinux.osuosl.org/veclinux-7.1/extra/
Package Priority: Default
Package Location: ./xap/Network
Package Version: 0.5.8-i586-1vl71
Package Size: 983 K
Package Installed Size: 4700 K
Package Required:   atk >= 2.7.90-i586-1vl71,bzip2 >= 1.0.6-i586-1vl71,cairo >= 1.12.14-i586-2vl71,dbus >= 1.6.8-i586-3vl71,dbus-glib >= 0.100.2-i586-2vl71,enchant >= 1.6.0-i586-1vl71,expat >= 2.1.0-i586-1vl71,fontconfig >= 2.10.92-i586-2vl71,freetype >= 2.5.1-i586-1vl71,gcc >= 4.7.2-i586-3vl71,gcc-g++ >= 4.7.2-i586-3vl71,gdk-pixbuf2 >= 2.29.0-i586-1vl71,geoclue >= 0.12.99-i586-1vl71,glib-networking >= 2.32,glib2 >= 2.37.6-i586-1vl71,graphite2 >= 1.2.1-i586-1vl71,gst-plugins-base >= 0.10.36-i586-3vl71,gstreamer >= 0.10.36-i586-1vl71,gtk+2 >= 2.24.13-i586-5vl71,harfbuzz >= 0.9.16-i586-1vl71,icu4c >= 4.7.1-i586-1vl71,libICE >= 1.0.8-i586-1vl71,libSM >= 1.2.1-i586-1vl71,libX11 >= 1.5.0-i586-1vl71,libXScrnSaver >= 1.2.2-i586-1vl71,libXau >= 1.0.7-i586-1vl71,libXcomposite >= 0.4.4-i586-1vl71,libXcursor >= 1.1.13-i586-1vl71,libXdamage >= 1.1.4-i586-1vl71,libXdmcp >= 1.1.1-i586-1vl71,libXext >= 1.3.1-i586-1vl71,libXfixes >= 5.0-i586-1vl71,libXi >= 1.7.1-i586-1vl71,libXinerama >= 1.1.2-i586-1vl71,libXrandr >= 1.4.0-i586-1vl71,libXrender >= 0.9.7-i586-1vl71,libXt >= 1.1.3-i586-1vl71,libXxf86vm >= 1.1.2-i586-1vl71,libdrm >= 2.4.49-i586-1vl71,libffi >= 3.0.11-i586-1vl71,libjpeg >= 8d-i586-1vl71,libnotify >= 0.7.5-i586-1vl71,libpng >= 1.5.12-i586-1vl71,libsoup >= 2.42.0-i586-1vl71,libxcb >= 1.9-i586-1vl71,libxml2 >= 2.8.0-i586-1vl71,libxslt >= 1.1.26-i586-2vl71,mesa >= 10.0.0-i586-1vl71,orc >= 0.4.16-i586-1vl71,pango >= 1.34.1-i586-2vl71,pixman >= 0.28.2-i586-1vl71,sqlite >= 3.8.4.3-i586-1vl71,util-linux >= 2.21.2-i586-5vl71,webkitgtk >= 1.8.3-i586-1vl71,xz >= 5.0.4-i586-1vl71,zlib >= 1.2.8-i586-1vl71
Package Conflicts:   
Package Suggests:   
Package MD5 Sum:  c3eb963db18798ee94cadde6184e9a18
Package Description:
 midori (lightweight web browser.)
 lightweight web surfing using webkit engine.
 
 
 


 License: LGPL
 Authors: Christian Dywan
 Website: http://software.twotoasts.de/index.php?/pages/midori_summary.html
Package Installed: no
No such package: info
vector://home/cmartin
"No such package" and yet it's installed.  slapt-get doesn't know about it.  Interesting...  I'll reinstall.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: caitlyn on May 25, 2014, 02:18:05 pm
I may have found the problem:  a dependency issue.  sqlite is installed but it's an older version than the current midori package needs:
Code: [Select]
root:# slapt-get --install midori
Reading Package Lists...Done
Excluding midori, use --ignore-dep to override
The following packages have unmet dependencies:
  midori: Depends: sqlite >= 3.8.4.3-i586-1vl71
The following packages have been EXCLUDED:
  midori
0 upgraded, 0 reinstalled, 0 newly installed, 0 to remove, 1 not upgraded.

Done
vector://home/cmartin
Title: Re: VL7.1 STD feedback and suggestions.
Post by: caitlyn on May 25, 2014, 02:20:54 pm
I decided to upgrade my system to the latest packages.  The problem with unmet dependencies isn't limited to midori.  There's also one package conflict:
Code: [Select]
Reading Package Lists...Done
Excluding apr-util, use --ignore-dep to override
Excluding gambas2-runtime, use --ignore-dep to override
Excluding gtkpod, use --ignore-dep to override
Excluding midori, use --ignore-dep to override
Installed nspr conflicts with mozilla-nss
Excluding mozilla-nss, use --ignore-dep to override
The following packages have unmet dependencies:
  apr-util: Depends: apr >= 1.4.8-i586-1vl71
  gambas2-runtime: Depends: openjpeg >= 1.5.0-i586-2vl71
  gtkpod: Depends: libgpod >= 0.8.3-i586-1vl71
  midori: Depends: sqlite >= 3.8.4.3-i586-1vl71
  mozilla-nss: Depends: sqlite >= 3.8.4.3-i586-1vl71
The following packages have been EXCLUDED:
  apr-util gambas2-runtime gtkpod midori mozilla-nss
Seriously not good...
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on May 27, 2014, 05:30:48 am
Can I see your slapt-getrc please?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: caitlyn on May 27, 2014, 10:45:43 pm
This should be a stock file.  I haven't edited it at all since I downloaded RC2.

Code: [Select]
cmartin:$ cat /etc/slapt-get/slapt-getrc
WORKINGDIR=/home/ftp/pub/veclinux/packages
EXCLUDE=kernel,kernel-ide,kernel-source,kernel-headers,kernel-modules
#DISABLED=file:///mnt/cdrom/packages/
SOURCE=http://vectorlinux.osuosl.org/veclinux-7.1/packages/
SOURCE=http://vectorlinux.osuosl.org/veclinux-7.1/extra/
SOURCE=http://vectorlinux.osuosl.org/veclinux-7.1/patches/:OFFICIAL
#SOURCE=http://vectorlinux.osuosl.org/veclinux-7.1/testing/
#SOURCE=http://vectorlinux.osuosl.org/veclinux-7.1/gsb/
#DISABLED=http://vectorlinux.osuosl.org/veclinux-7.1/unstable/
#DISABLED=ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-7.1/packages/
#DISABLED=ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-7.1/patches/
#DISABLED=ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-7.1/extra/
#DISABLED=ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-7.1/testing/
#DISABLED=ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-7.1/gsb/
#DISABLED=ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-7.1/unstable/
#DISABLED=http://distro.ibiblio.org/pub/linux/distributions/vectorlinux/veclinux-7.1/packages/
#DISABLED=http://distro.ibiblio.org/pub/linux/distributions/vectorlinux/veclinux-7.1/patches/
#DISABLED=http://distro.ibiblio.org/pub/linux/distributions/vectorlinux/veclinux-7.1/extra/
#DISABLED=http://distro.ibiblio.org/pub/linux/distributions/vectorlinux/veclinux-7.1/testing/
#DISABLED=http://distro.ibiblio.org/pub/linux/distributions/vectorlinux/veclinux-7.1/gsb/
#DISABLED=http://distro.ibiblio.org/pub/linux/distributions/vectorlinux/veclinux-7.1/unstable/
#DISABLED=http://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-7.1/packages/
#DISABLED=http://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-7.1/patches/
#DISABLED=http://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-7.1/extra/
#DISABLED=http://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-7.1/testing/
#DISABLED=ftp://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-7.1/packages/
#DISABLED=ftp://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-7.1/patches/
#DISABLED=ftp://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-7.1/extra/
#DISABLED=ftp://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-7.1/testing/
#DISABLED=http://www.mirrorservice.org/sites/vectorlinux.com/veclinux-7.1/packages/
#DISABLED=http://www.mirrorservice.org/sites/vectorlinux.com/veclinux-7.1/patches/
#DISABLED=http://www.mirrorservice.org/sites/vectorlinux.com/veclinux-7.1/extra/
#DISABLED=http://www.mirrorservice.org/sites/vectorlinux.com/veclinux-7.1/testing/
#DISABLED=ftp://www.mirrorservice.org/sites/vectorlinux.com/veclinux-7.1/packages/
#DISABLED=ftp://www.mirrorservice.org/sites/vectorlinux.com/veclinux-7.1/patches/
#DISABLED=ftp://www.mirrorservice.org/sites/vectorlinux.com/veclinux-7.1/extra/
#DISABLED=ftp://www.mirrorservice.org/sites/vectorlinux.com/veclinux-7.1/testing/
#DISABLED=http://na.mirror.garr.it/mirrors/vectorlinux/veclinux-7.1/packages/
#DISABLED=http://na.mirror.garr.it/mirrors/vectorlinux/veclinux-7.1/patches/
#DISABLED=http://na.mirror.garr.it/mirrors/vectorlinux/veclinux-7.1/extra/
#DISABLED=http://na.mirror.garr.it/mirrors/vectorlinux/veclinux-7.1/testing/
#DISABLED=ftp://na.mirror.garr.it/mirrors/vectorlinux/veclinux-7.1/packages/
#DISABLED=ftp://na.mirror.garr.it/mirrors/vectorlinux/veclinux-7.1/patches/
#DISABLED=ftp://na.mirror.garr.it/mirrors/vectorlinux/veclinux-7.1/extra/
#DISABLED=ftp://na.mirror.garr.it/mirrors/vectorlinux/veclinux-7.1/testing/
#DISABLED=http://www.gi.kernel.org/sites/vectorlinux.com/veclinux-7.1/packages/
#DISABLED=http://www.gi.kernel.org/sites/vectorlinux.com/veclinux-7.1/patches/
#DISABLED=http://www.gi.kernel.org/sites/vectorlinux.com/veclinux-7.1/extra/
#DISABLED=http://www.gi.kernel.org/sites/vectorlinux.com/veclinux-7.1/testing/
#DISABLED=ftp://www.gi.kernel.org/sites/vectorlinux.com/veclinux-7.1/packages/
#DISABLED=ftp://www.gi.kernel.org/sites/vectorlinux.com/veclinux-7.1/patches/
#DISABLED=ftp://www.gi.kernel.org/sites/vectorlinux.com/veclinux-7.1/extra/
#DISABLED=ftp://www.gi.kernel.org/sites/vectorlinux.com/veclinux-7.1/testing/
#DISABLED=http://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-7.1/packages/
#DISABLED=http://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-7.1/patches/
#DISABLED=http://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-7.1/extra/
#DISABLED=http://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-7.1/testing/
#DISABLED=ftp://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-7.1/packages/
#DISABLED=ftp://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-7.1/patches/
#DISABLED=ftp://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-7.1/extra/
#DISABLED=ftp://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-7.1/testing/
#DISABLED=http://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-7.1/packages/
#DISABLED=http://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-7.1/patches/
#DISABLED=http://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-7.1/extra/
#DISABLED=http://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-7.1/testing/
#DISABLED=ftp://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-7.1/packages/
#DISABLED=ftp://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-7.1/patches/
#DISABLED=ftp://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-7.1/extra/
#DISABLED=ftp://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-7.1/testing/
#DISABLED=ftp://ftp.slackware.com/pub/slackware/slackware-14.0/
#DISABLED=http://carroll.cac.psu.edu/pub/linux/distributions/slackware/slackware-14.0/
#DISABLED=http://darkstar.ist.utl.pt/slackware/slackware-14.0/
#DISABLED=http://ftp.belnet.be/packages/slackware/slackware-14.0/
#DISABLED=http://ftp.gwdg.de/pub/linux/slackware/slackware-14.0/
#DISABLED=http://ftp.isu.edu.tw/pub/Linux/Slackware/slackware-14.0/
#DISABLED=http://ftp.linux.cz/pub/linux/slackware/slackware-14.0/
#DISABLED=http://ftp.lip6.fr/pub/linux/distributions/slackware/slackware-14.0/
#DISABLED=http://ftp.ntua.gr/pub/linux/slackware/slackware-14.0/
#DISABLED=http://ftp.riken.jp/Linux/slackware/slackware-14.0/
#DISABLED=http://ftp.slackware.cz/slackware/slackware-14.0/
#DISABLED=http://gd.tuwien.ac.at/opsys/linux/slackware/slackware-14.0/
#DISABLED=http://mirror.switch.ch/ftp/mirror/slackware/slackware-14.0/
#DISABLED=http://mirrors.dotsrc.org/slackware/slackware-14.0/
#DISABLED=http://mirrors.easynews.com/linux/slackware/slackware-14.0/
#DISABLED=http://mirrors.unixsol.org/slackware/slackware-14.0/
#DISABLED=http://mirrors.usc.edu/pub/linux/distributions/slackware/slackware-14.0/
#DISABLED=http://serghei.net/linux/slackware/slackware-14.0/
#DISABLED=http://slackware.mirrors.pair.com/slackware-14.0/
#DISABLED=http://slackware.mirrors.tds.net/pub/slackware/slackware-14.0/
#DISABLED=http://slackware.oregonstate.edu/slackware-14.0/
#DISABLED=http://www.mirrorservice.org/sites/ftp.slackware.com/pub/slackware/slackware-14.0/
#DISABLED=http://www.slackware.at/data/slackware-14.0/
#DISABLED=ftp://carroll.cac.psu.edu/pub/linux/distributions/slackware/slackware-14.0/
#DISABLED=ftp://ftp.chg.ru/pub/Linux/Slackware/slackware-14.0/
#DISABLED=ftp://darkstar.ist.utl.pt/pub/slackware/slackware-14.0/
#DISABLED=ftp://elektroni.phys.tut.fi/slackware-14.0/
#DISABLED=ftp://ftp.belnet.be/packages/slackware/slackware-14.0/
#DISABLED=ftp://ftp.biochem.uthscsa.edu/pub/linux/slackware/slackware-14.0/
#DISABLED=ftp://ftp.cerias.purdue.edu/pub/os/slackware/slackware-14.0/
#DISABLED=ftp://ftp.fu-berlin.de/unix/linux/mirrors/slackware/slackware-14.0/
#DISABLED=ftp://ftp.funet.fi/pub/mirrors/ftp.slackware.com/pub/slackware-14.0/
#DISABLED=ftp://ftp.gwdg.de/pub/linux/slackware/slackware-14.0/
#DISABLED=ftp://ftp.heanet.ie/mirrors/ftp.slackware.com/pub/slackware/slackware-14.0/
#DISABLED=ftp://ftp.isu.edu.tw/pub/Linux/Slackware/slackware-14.0/
#DISABLED=ftp://ftp.linux.cz/pub/linux/slackware/slackware-14.0/
#DISABLED=ftp://ftp.lip6.fr/pub/linux/distributions/slackware/slackware-14.0/
#DISABLED=ftp://ftp.man.szczecin.pl/pub/Linux/slackware/slackware-14.0/
#DISABLED=ftp://ftp.mirrorservice.org/sites/ftp.slackware.com/pub/slackware/slackware-14.0/
#DISABLED=ftp://ftp.nluug.nl/pub/os/Linux/distr/slackware/slackware-14.0/
#DISABLED=ftp://ftp.ntua.gr/pub/linux/slackware/slackware-14.0/
#DISABLED=ftp://ftp.red.telefonica-wholesale.net/slackware/slackware-14.0/
#DISABLED=ftp://ftp.riken.jp/Linux/slackware/slackware-14.0/
#DISABLED=ftp://ftp.slackware-brasil.com.br/slackware-14.0/
#DISABLED=ftp://ftp.slackware.lt/pub/Linux/slackware/slackware-14.0/
#DISABLED=ftp://ftp.slackware.no/pub/linux/slackware/slackware-14.0/
#DISABLED=ftp://ftp.sunet.se/pub/Linux/distributions/slackware/slackware-14.0/
#DISABLED=ftp://mirror.switch.ch/mirror/slackware/slackware-14.0/
#DISABLED=ftp://mirrors.blueyonder.co.uk/sites/ftp.slackware.com/slackware-14.0/
#DISABLED=ftp://mirrors.dotsrc.org/slackware/slackware-14.0/
#DISABLED=ftp://mirrors.unixsol.org/slackware/slackware-14.0/
#DISABLED=ftp://mirrors.usc.edu/pub/linux/distributions/slackware/slackware-14.0/
#DISABLED=ftp://slackware.mirrors.pair.com/slackware-14.0/
#DISABLED=ftp://slackware.mirrors.tds.net/pub/slackware/slackware-14.0/
#DISABLED=ftp://slackware.oregonstate.edu/pub/slackware/slackware-14.0/
#DISABLED=ftp://sunsite.cnlab-switch.ch/mirror/slackware/slackware-14.0/
#DISABLED=ftp://sunsite.icm.edu.pl/pub/Linux/slackware/slackware-14.0/
#DISABLED=ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/slackware/slackware-14.0/
#DISABLED=http://www.slacky.eu/repository/slackware-14.0/
#DISABLED=http://darkstar.ist.utl.pt/slackware/addon/slacky/slackware-14.0/
#DISABLED=ftp://darkstar.ist.utl.pt/pub/slackware/addon/slacky/slackware-14.0/
#DISABLED=ftp://ftp.osuosl.org/pub/slackware/slackware-14.0/
#DISABLED=ftp://ftp.osuosl.org/pub/slackware/slackware-14.0/
#DISABLED=ftp://ftp.osuosl.org/pub/slackware/slackware-14.0/
#DISABLED=ftp://ftp.osuosl.org/pub/slackware/slackware-14.0/
#DISABLED=ftp://ftp.slackware.com/pub/slackware/slackware-14.0/
#DISABLED=ftp://ftp.slackware.com/pub/slackware/slackware-14.0/
#DISABLED=ftp://ftp.slackware.com/pub/slackware/slackware-14.0/
#DISABLED=ftp://ftp.slackware.com/pub/slackware/slackware-14.0/
#DISABLED=ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/slackware/slackware-14.0/
#DISABLED=ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/slackware/slackware-14.0/
#DISABLED=ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/slackware/slackware-14.0/
#DISABLED=ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/slackware/slackware-14.0/
#DISABLED=http://na.mirror.garr.it/mirrors/Slackware/slackware-14.0/
#DISABLED=http://na.mirror.garr.it/mirrors/Slackware/slackware-14.0/
#DISABLED=http://na.mirror.garr.it/mirrors/Slackware/slackware-14.0/
#DISABLED=http://na.mirror.garr.it/mirrors/Slackware/slackware-14.0/
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on May 28, 2014, 06:17:18 am
That's why you're seeing the dep errors.
Add this to it
Code: [Select]
SOURCE=http://vlcore.vectorlinux.com/pkg/untested/veclinux-7.1/x86after slapt-get -u your deps should be available
Title: Re: VL7.1 STD feedback and suggestions.
Post by: caitlyn on May 28, 2014, 10:14:15 am
I take it untested won't be available by default or needed in the final release.  I'm actually surprised it's still needed in a second release candidate. 
Title: Re: VL7.1 STD feedback and suggestions.
Post by: caitlyn on May 28, 2014, 06:05:40 pm
The good news:  the dependency problem is fixed.
The bad news:  the new Midori package crashed just about immediately.  No improvement at all  :(
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on May 29, 2014, 04:05:13 am
Can you launch it from a terminal and post the error after it crashes ?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: caitlyn on May 29, 2014, 02:17:30 pm
I tried the new kernel in untested and it hosed my machine - no mouse, no keyboard.  I'm going to reload and start over from a fresh RC2 build later this evening and I'll post my results with Midori.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: roarde on May 29, 2014, 08:05:36 pm
I'm using Midori on RC2.1 32-bit. No real problems, just small annoyances.

Until, that is, I enable pretty much any add-on. They should rename each one "insta-crash" for this build. And that's a problem many distros are having.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on May 30, 2014, 07:13:41 am
Aparently, the edit menu crash only happens after you have opened a website.  I was trying it as soon as the app loaded, and in that test case it does not.  This is a known bug https://bugs.launchpad.net/midori/+bug/1303372 .  We'll have to wait for a patch or fix release.  Looks like every one is having this same problem with midori.

NOTE:  My last build does fix a minor annoyance where the tabs would have no close button and no favicon.  To see the fix on a current 7.1 installation follow this guide
Code: [Select]
slapt-get -u
slapt-get -i midori faenza-icon-theme mate-icon-them --reinstall

UPDATE:
Looks like there is already a fix, but they may not publish a patch.  Instead it's commited to the next milestone
https://bugs.launchpad.net/midori/+bug/1303372
Title: Re: VL7.1 STD feedback and suggestions.
Post by: nightflier on June 01, 2014, 10:20:09 am
RC2.1 32-bit in VB VM: flash-player-properites segfaults when you click "playback" tab.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: roarde on June 02, 2014, 06:50:09 pm
Duplicated nightflier's flash-player-properties playback tab segfault on real 32-bit hw, STD RC2.1 (incidentally with icewmvmods running, so assuming his was with xfce rules out the de).
Title: Re: VL7.1 STD feedback and suggestions.
Post by: nightflier on June 03, 2014, 03:31:56 am
Thanks Roarde. Yes, my test was with xfce, no changes made after install.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on June 03, 2014, 06:41:13 am
MIDORI ISSUE UPDATE:

I have built a patched version of the midori 0.5.8 package for 7.1 (Thanks to Roarde for the patch).

My initial testing shows this fixes the crash on menu->edit.

Build link: http://vlcore.vectorlinux.com/buildbot/builders/midori/builds/5
The package will be in untested after the build completes
Title: Re: VL7.1 STD feedback and suggestions.
Post by: nightflier on June 03, 2014, 03:52:00 pm
Tested updated midori on 32-bit in vm. Works. Enabled some add-ons like flash and java, no problems. After I set the GTK theme to "mate" the UI displayed properly, fwiw.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on June 04, 2014, 04:04:17 am
Tested updated midori on 32-bit in vm. Works. Enabled some add-ons like flash and java, no problems. After I set the GTK theme to "mate" the UI displayed properly, fwiw.

If you sslapt-get -i --reinstall faenza-icon-theme it will display the icons without having to set the theme to mate
Title: Re: VL7.1 STD feedback and suggestions.
Post by: caitlyn on July 09, 2014, 09:54:36 am
How are things progressing?  Is there an updated release candidate?  How close (or far) are we from a gold release?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: caitlyn on July 12, 2014, 06:23:31 pm
I tried using VL 7.1 RC2 with an external USB Hebrew/English keyboard.  While I had no problem making VL work with Hebrew, I did have problems with typing in any language.  I got double and triple characters.  This is probably just a keyboard setting that can be adjusted but I've never seen this problem before.  I've used this hardware configuration with other distros and it just works.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: caitlyn on July 12, 2014, 07:42:09 pm
Running
Code: [Select]
slapt-get --update
slapt-get --upgrade

on my netbook (32-bit VL 7.1) with the testing repository enabled I get the following errors:
Code: [Select]
The following packages have unmet dependencies:
  apr-util: Depends: apr >= 1.4.8-i586-1vl71
  mysql: Depends: zlib >= 1.2.8-i586-1vl71
  gnutls: Depends: zlib >= 1.2.8-i586-1vl71
  libimobiledevice: Depends: libplist >= 1.11-i586-1vl71
The following packages have been EXCLUDED:
  apr-util gambas2-runtime gnutls libgpod libimobiledevice usbmuxd
My exclude list in my slapt-getrc only includes kernel packages.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: roarde on July 12, 2014, 08:12:54 pm
The missing dependencies are in the untested repo. Line for slapt-getrc:
#DISABLED=http://vlcore.vectorlinux.com/pkg/untested/veclinux-7.1/x86/
Edit: Slapt-getrc now ships with the line #SOURCE=http://vlcore.vectorlinux.com/pkg/ (so on). So to use it, it must be directly edited. Better idea than what I wrote and struck out, IMO.

Then this wouldn't apply to that either, but is left as a guide to adding new repos to slapt-getrc for normal use:
Of course, that adds it as disabled -- can be turned on/off by editing directly or by source selection in GSlapt. Looks like the testing repo isn't being used now on 7.1, and I think that plans are currently to abandon it. Not sure, and at this point subject to change anyway.

But having those packages moved from untested to extra without bringing all the deps along does point up a problem, especially when untested is regularly purged.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: vincent2 on July 16, 2014, 06:01:32 am
 spent  afew  hours to download vl7.1 rc 2.2.3 64bit,install process went smoothly,

from runlevel 4  login menu , can't enter desktop at all always erros, prompting disk full, infact disk 's 90% vacant space.......
to enter desktop, has to type startx always.....
it's really buggy.

3G modem still doesn't work at all....

vl7.1 rc2.2.3 offers no improvement at all, .

pls offer 3G 4G modem support......

Title: Re: VL7.1 STD rc 2.2.4 64bit
Post by: vincent2 on July 19, 2014, 03:17:47 am
vl7.1 rc 2.2.4 64bit,install process went smoothly,

from runlevel 4  login menu , still can't enter desktop at all always erros, prompting disk full, infact disk 's 90% vacant space.......

to enter desktop, has to type startx always.....

3G modem still doesn't work at all....

vl7.1 rc2.2.4 offers no improvement at all

hope more engineers in mobile internet provider companies can test vl7.1,offer better 3G support.

Title: Re: VL7.1 STD 64 bit 3G modem
Post by: vincent2 on July 19, 2014, 03:43:59 am
in order to make 3G modem working with chestnutdialer  on vl7,1 rc2.2.4,
 
are  there any special dependent pkgs  need to be installed?

can anyone  give some hints on 3G modem @vl7.1 64bit?

while on slackware14.1 bit, 3G modem does work very well...can't figure out what pkgs and files vector 7.1 missed ?

Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on July 19, 2014, 10:46:51 am
vincent2..Thought you may find this interesting

These may not be your specific modem but should point you in the right direction

Huawei 3G E156 B?
http://go2linux.garron.me/linux/2011/02/huawei-3g-e156-b-slackware-linux-connect-910

Huawei 1550 3G
http://www.linuxquestions.org/questions/slackware-14/3g-modem-794337/

 edit: wvdial and libwvstreams are installed in vector also usb-modeswitch you will need to edit your dial and modeswitch conf files
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on July 19, 2014, 10:50:04 am
VL 7.1 RC 2.2.3
 when libvirt is selected for install via gslapt-ERROR libvirt : depends: dmidecode>=2.12
Title: Re: VL7.1 STD feedback--3G modem,proxy ARP
Post by: vincent2 on July 19, 2014, 08:05:07 pm
ok....

now 3G modem does work under vl7.1 rc2.2.4 64bit, huweie1550....By setting dialing device as "dev/ttyUSB0" on the chestnut-dialer config menu,

BUT modem does connect to internet, i can ping 8.8.8.8, just couldn't visit anywebsite, it prompted network error in bruisers....

"nslookup vectorlinux.com"  generated network errors, while "nslookup vectorlinux.com 8.8.8.8" got correct ip....

at chestnut-dialer logs, it prompted as"cannot  determine ethernet address for proxy ARP", where's gone wrong ?

any commands to reconfigure modem ARP correctly???
Title: Re: VL7.1 STD feedback--3G modem,proxy ARP
Post by: vincent2 on July 20, 2014, 07:01:48 am
ok....

now 3G modem does work under vl7.1 rc2.2.4 64bit, huweie1550....By setting dialing device as "dev/ttyUSB0" on the chestnut-dialer config menu,

BUT modem does connect to internet, i can ping 8.8.8.8, just couldn't visit anywebsite, it prompted network error in bruisers....

"nslookup vectorlinux.com"  generated network errors, while "nslookup vectorlinux.com 8.8.8.8" got correct ip....

at chestnut-dialer logs, it prompted as"cannot  determine ethernet address for proxy ARP", where's gone wrong ?

any commands to reconfigure modem ARP correctly???

now i edited /etc/resolv.conf again, adding:
---------------------------------
nameserver 208.67.222.222
nameserver 208.67.220.220
-----------------------------------

now internet running normal with 3Gmodem...
at last 3G modem works fine under vl7.1 rc2.2.4 64bit
Title: Re: VL7.1 STD feedback and suggestions.
Post by: vincent2 on July 20, 2014, 07:24:15 am
apparently,NetworkManager Applet 0.9.6.4 still can't make 3G modem connected automatically yet....
Title: Re: VL7.1 STD feedback and suggestions.
Post by: rbistolfi on July 20, 2014, 10:21:31 am

apparently,NetworkManager Applet 0.9.6.4 still can't make 3G modem connected automatically yet....

Did you try using the configuration screen to setup DNS for your network? I gave it a try with my phone and it worked automatically for me. A problem with this is that we dont have the same device as you, so its impossible to debug for us.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: vincent2 on July 20, 2014, 06:23:45 pm

apparently,NetworkManager Applet 0.9.6.4 still can't make 3G modem connected automatically yet....

Did you try using the configuration screen to setup DNS for your network? I gave it a try with my phone and it worked automatically for me. A problem with this is that we dont have the same device as you, so its impossible to debug for us.

what's model of ur phones? i'm using huaweie 1550 3G modem, the most popular model, on knoppix, slackware, mandriva all works fine  with network manager applet, not under vl7.1 rc 2.2.4 with network manager applet yet  only work with chestnut-dialer under vl7.1...

now i already edited /etc/resolv.conf again, adding:
---------------------------------
nameserver 208.67.222.222
nameserver 208.67.220.220
-----------------------------------

anyway, network manager applet  still can't drive 3G modem connected yet, while booting into knoppix 7.2.0,once configured 3G modem under network manager under knoppix,network manager applet will show 3G network name, just clicking it, 3G gets connected.
network manager on vl7.1 rc2.2.4 's still buggy, maybe missing links for 3G modem...
i can add 3G gprs network on mobile internet at network manger config menu, but 3G never gets connected....always has to resort to chest-dialer again for 3G connections......
Title: Re: VL7.1 STD feedback and suggestions.
Post by: vincent2 on August 05, 2014, 08:39:32 pm
once rebooting, haVE TO

edited /etc/resolv.conf again AGAIN AGIAN adding:
---------------------------------
nameserver 208.67.222.222
nameserver 208.67.220.220
-----------------------------------

Title: SKYPE 4.3
Post by: vincent2 on August 05, 2014, 08:45:40 pm
now old version of skype  on repo can  no longer work any more due to SKYPE clouds config.....

DO include new skype versin 4.3 into next vl7.1  64 bit RC release....


skype 4.3 surce code 's only 32bit, not working on  vl7.1 rc 2.2.4 64 bit  at all. ......


aslo New kernel should be uploaded to test rep for  testing  securities, kernel , 3.15.x, 3.16.x....
Title: Re: VL7.1 STD feedback and suggestions.
Post by: Pita on August 06, 2014, 06:04:05 pm
Microsoft has blocked Skype-4.2 and is forcing users to skype-4.3 with which one has to use pulseaudio. I guess that goes under user-friendlyness.

Skype is a 32 bit application and therefore you will need to install multilib on 64 bit version.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: sledgehammer on August 07, 2014, 07:36:57 am
Quote
DO include new skype versin 4.3 into next vl7.1  64 bit RC release...

Skype is not open source.  I vote "no."  Skype doesn't belong in a decent OS.

John
Title: Re: VL7.1 STD feedback and suggestions.
Post by: Pita on August 07, 2014, 06:17:59 pm
Check this out:

http://slackbuilds.org/slackbuilds/14.1/network/skype/README.SLACKWARE



Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on August 08, 2014, 05:05:12 am
Even when compiled with the proper 32-bit libraries in place, skype on a 64-bit system tends to be buggy and extremely unstable. Not worth the time IMO.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: vincent2 on August 09, 2014, 05:58:16 am
http://www.linuxquestions.org/questions/slackware-14/skype-4-3-a-4175508618/page6.html

 community should test it.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on August 09, 2014, 08:50:18 am
Knock yourself out.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: caitlyn on August 12, 2014, 05:34:37 pm
on my netbook (32-bit VL 7.1) with the testing repository enabled
Now slapt-get --update fails if the testing repository is enabled.  I checked it, and the package list is missing, which is the error I'm seeing.  Without testing it runs but I still have unmet dependencies.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: roarde on August 12, 2014, 06:55:57 pm
At present the 7.1 testing repository isn't used, and it looks like it will remain that way through the release cycle. This is an intended change; later RC's ship without the http version of the testing repo even mentioned in slapt-getrc. The untested repo is there, but commented out in such a way that it can be uncommented only by direct edit -- not via GSlapt. I assume that's also intentional because the rest of the disabled repos have the "#DISABLED" tag that GSlapt latches onto.

The 7.1 testing repo is empty. Note that this does not apply to 70 which still uses testing.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: rbistolfi on August 15, 2014, 03:54:50 pm
One issue about the current development model is the the repository is in constant movement. Using untested is likely to produce errors: the package list changes quickly and it is regenerated after each new build. I think the same applies for the testing repository at osuosl. We will have to adapt and improve as we go.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: vincent2 on August 19, 2014, 03:16:17 am
just installed vl64-7.1 rc2.2.5, install process went smoothly....

 strangely, wifi 's connected, have ip address,but couldn't ping, nslookup at all...even can't ping  router  as well...

any command to fix it UP?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: bigpaws on August 19, 2014, 06:31:48 am
If you have an ip address that is in the proper subnet.

Then there are only two areas to check.

Make sure using iwconfig that the connection is associated with the AP,

next make sure the routing is correct. As root route -n will show the
routing table.

Bigpaws
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on August 19, 2014, 11:10:50 am
It appears there was a security advisory on the dhcpcd package which triggered a rebuild of our package.  The resulting package is being fixed now...  The Next ISO will have a fixed package.  In the mean time, you can revert to this p ackage

http://vectorlinux.osuosl.org/VL64-7.1/packages/Sbin/dhcpcd-5.6.7-x86_64-2vl71.txz

or wait for the new package on untested and install it on your 2.2.5 installations.

Remember to removepkg dhcpcd first or run upgradepkg /path/to/your/downloaded/dhcpcd-5.6.7-x86_64-2vl71.txz to replace the existing package
Title: Re: VL7.1 STD feedback and suggestions.
Post by: vincent2 on September 15, 2014, 08:18:17 pm
 64bit so far rc 2.2.6   works fine. incl. 3G modem


expect
kernel 3.16  series could be uploaded to test repo for testing...
Title: No GUI MTP support in VL 7.1?
Post by: caitlyn on September 18, 2014, 06:10:46 pm
I wanted to transfer some files from my LG Volt running Android Kit Kat 4.4.2 and noticed that the device wasn't recognized in Thunar.  libmtp is installed (good) but mtp-gvfs isn't even available in the repository.  For recent Android devices to be recognized as filesystems in Thunar that's a must. 
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on September 19, 2014, 08:31:05 am
mtp-gvfs has been merged into upstream gvfs.  I got the gvfs package built for 7.1 and it is currently in the untested repository.  Please test and report back.

Build logs are here
http://vlcore.vectorlinux.com/buildbot/builders/gvfs/builds/7
Title: Re: VL7.1 STD feedback and suggestions.
Post by: vincent2 on September 20, 2014, 08:16:17 am
vcpufrequ still doesn;t work on 64 bit rc 226 yet.
regarding overclocked CPU, vl7l rc226  simply couldn't   show  the real speed of overclocked CPU at all.

intel  e5700 cpu overclocked to 3.75Ghz from Bios, under windows it can recognized it as cpu@3,75.under vector, it still shows as 3.0G, which's not the real speed of cpu.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on September 20, 2014, 08:43:48 am
vcpufreq has been removed from the actual ISO. You need to install from gslapt.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: caitlyn on September 20, 2014, 12:57:57 pm
mtp-gvfs has been merged into upstream gvfs.  I got the gvfs package built for 7.1 and it is currently in the untested repository.  Please test and report back.

Build logs are here
http://vlcore.vectorlinux.com/buildbot/builders/gvfs/builds/7
Fantastic.  I'm going to rebuild the netbook with the latest 2.2.6 build this evening and then I'll test it.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: vincent2 on September 28, 2014, 06:24:47 am
expect kernel 3.16.x series pkg bein g uploaded to test repo.
hope kenel 3.16.x can improve securities  more
Title: Re: VL7.1 STD feedback and suggestions.
Post by: The Headacher on October 06, 2014, 08:57:32 am
Last week I installed RC2.3, and while it looked a lot better than RC2 I still have some issues with it.

This is the second installation where I just 'lost' the Xfce Desktop after a while (same thing happened on RC2); I boot the computer and login as my everyday user, only to be greeted by a panel without a 'running'  desktop. I can still open programs from the menu, but they don't show up on the panel and apparently they can't be moved either. I haven't yet located the correct command to start the desktop myself.

While the 'Session' menu lists both Awesome and Fluxbox neither wants to be booted; Fluxbox doesn't seem to be installed, awesome is though. With a new user, XFCE looks alright, though I guess it's just a matter of time before XFCE is b0rken there too.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: roarde on October 06, 2014, 11:41:00 am
I boot the computer and login as my everyday user, only to be greeted by a panel without a 'running'  desktop. I can still open programs from the menu, but they don't show up on the panel and apparently they can't be moved either. I haven't yet located the correct command to start the desktop myself.
Is this a "fresh" user, or are you using a /home from a previous install?

With a new user, XFCE looks alright, though I guess it's just a matter of time before XFCE is b0rken there too.
Which is why I ask.

Transferring /home from one install to the next is still the "supported" way to keep your data. Just have to wonder whether the settings brought in are the problem this time.

Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on October 06, 2014, 04:42:28 pm
There was a pretty huge change in XFCE somewhere in the middle of the test releases. I seem to recall one of my test installs blowing up due to those changes.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: The Headacher on October 07, 2014, 11:10:05 am
Is this a "fresh" user, or are you using a /home from a previous install?
Fresh install, no transfer of /home. Just a clean install that worked fine for a while. The computer MIGHT have run out of batteries once or perhaps I had to exit XFCE using CTRL+ALT+Backspace. I can't recall exactly what happened before and after the fresh install.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: The Headacher on October 26, 2014, 07:39:09 am
Yesterday my new user had also lost the dekstop.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: d_s on October 26, 2014, 01:20:05 pm
A wild idea: @ The Headacher - if you create another user and do a diff -r between the one who lost the desktop and the one who still has it, does anything show up that could be XFCE-related? Or even X-related, considering that neither awesome nor want to work? Ok, first you need to verify that at least awesome works with a fresh user, then install fluxbox and verify that. Btw... after you have installed fluxbox, pls check if it suddenly/magically works for an old user who lost his desktop.

I think in the direction that somehow during usage a configuration file gets corrupted in such a way that either the desktop / window manager refuses to start... Hmmm... there could be something unusual in your ~/.xsession-errors, do you see something. Maybe something that isn't there with a fresh user?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: roarde on October 26, 2014, 06:51:23 pm
Is xfdesktop(1) any help? What does running 'xfdesktop' in terminal yield?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: rbistolfi on October 27, 2014, 04:38:33 am
Also, I would try chowning $home
Title: Re: VL7.1 STD feedback and suggestions.
Post by: The Headacher on November 06, 2014, 11:36:18 am
Sorry for the long delay. Running xfdesktop does get me a desktop but not even close to the functionality I was used to. Anyhow, this is just on my play laptop, and I don't really care enough to spend lots of time trying to fix this with a workaround. I just figured that this was a problem in the distro that perhaps should be solved before going final. Users loosing their desktops in the 'stable' seems like a sure way to get lots of complaints.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: Lyn on November 24, 2014, 01:32:58 am
For me not being able to seamlessly import my home directory is a major reason for not updating to one of the test images - this is a very important bug that needs to be squashed, I am happy to try this out on my secondary computer to try to get this quashed but can't risk my main system, which means testing is rather limited.  7.0 is looking very old now and increasingly there are issues with the repository
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on December 02, 2014, 01:33:11 pm
Tried installing rc3 on Dell GX280:  Both gui and text installers hang at "Setting passwords"
/ to sda1 was ext3 and home /sdb6 was ext4  they are supposed to be formatted to reiserfs -
using gparted in VL6, sda1 is now reiserfs (only after test install - but gparted says it can't read the contents)  Apparently gparted doesn't know ext4 as it is calling sdb6 ext3.  Tried looking at sdb6 in thunar - empty and 458.7 MB free.
switched to vl7.0, installed gparted 14.0, sda1 is reiserfs 18.63GiB 3.42 GiB used and sdb6 is still ext4.
etc/vector-version "7.1 STD  RC3.1 November 11, 2014"

Did I pick up from other posts that xfce is unusable? Ouch!
I have installed 7.1 B3 - didn't use it much but liked what I saw.  I did not like 7.0 so use 6.0 for my Linux operations.
I need 7.1 as it will replace W$ on my laptop.
One last question: If I install RC3 and start using it, will Final require a complete (except home) reinstall?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on December 03, 2014, 05:46:39 am
Did you install RC3 or 3.1? If it's 3.1, it's about as close to a final release as we're going to get.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on December 03, 2014, 07:51:45 am
Quote
etc/vector-version "7.1 STD  RC3.1 November 11, 2014"
and
Quote
Both gui and text installers hang at "Setting passwords"
Only the text installer was able to format and install /.  None touched /home!
Tried starting from CD: 
Quote
[   1.196604] No filesystem could mount root,...
Title: Re: VL7.1 STD feedback and suggestions.
Post by: Pita on December 05, 2014, 11:39:27 pm
VL-7.1-STD-RC3.1.iso  32bit  PC desktop

Gui installer hang on installing grip. :(
Got out with menu reboot.

In /boot there was no vmlinuz-3.12.16. :(
Copied sata over from from iso.
When booting there was no fstab in /etc :(
Title: Re: VL7.1 STD feedback and suggestions.
Post by: Pita on December 08, 2014, 11:49:00 pm
VL-7.1-STD-RC3.1.iso  32bit  PC desktop

Gui installer hang on installing grip. :(
Got out with menu reboot.

In /boot there was no vmlinuz-3.12.16. :(
Copied sata over from from iso.
When booting there was no fstab in /etc :(


This is surely the fault of a badly scratched DVD.  :-[

So sorry.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on December 20, 2014, 09:17:42 am
As I said earlier, text install reformatted and wrote to sda1 '/' (sdb6 '/home' was not reformatted.)
Went in this morning with VL6 and found subprocess.log
Quote
goupadd:  'Bruce' is not a valid group name
Will use gparted to reformat /sdb6 and try to install again.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on December 20, 2014, 03:20:13 pm
Text install of 7.1 RC3 hung near/at the end of installing packages.
Tried again with gui install - completed and successfully rebooted.  (It had installed LILO.
Would not accept user password or root password.  I tried the latter with blank - no help.
Browsing with 7.0 Live, the user is in sdb6.  Looking at /etc/fstab,
Quote
#fstab generated by vinstall
UUID=a1262683-2511-4ee4-856b-29922bea241e   /   ext3   defaults  0 0
UUID=90ea6954-5d6a-4e58-b4b9-90325a005c6c   /home  reiserfs  defaults 0 0
...
('/' should have remained reiserfs!)  Realized that I hadn't set swap (/sda2).  How do I find that UUID?  Can I use '/dev/sda2' as on previous versions?  Or do I reinstall?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: roarde on December 20, 2014, 03:48:27 pm
You can use '/dev/sda2' or find the UUID with 'blkid /dev/sda2'.

UUID=74dd31bc-3c77-41b0-adf4-0c24e0ba1acb   swap   swap  sw 0 0
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on December 21, 2014, 12:21:52 pm
Thanks Robert.
blkid came up in VL7.0 LIVE with a different value which I used.  Tried both /dev/sda2 and the UUID for the swap line in fstab - still wouldn't accept either user or root passwords!
Will try reinstalling AND adding swap.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on December 21, 2014, 03:02:31 pm
Reinstalled using gui installer advanced -with all 3 partitions checked.  Even made sure sda1 was reiserfs - good!
Still will not accept logins for either user or root!
Any suggestions on how to get this working?
Gparted (per 7.0 LIVE):
Quote
/dev/sda1 reiserfs /dev/sda1                 18.63 GiB  3.50 GiB  15.13 GiB boot # VL7.1 /
/dev/sda2 linux-swap                             1.86 GiB
/dev/sda3 fat32 /mnt/sda3 FREEDOS2012 22.83 GiB 2.05 GiB 20.78 GiB lba
/dev/sda5 reiserfs  /mnt/sda5                 10.00 GiB 5.40 Gib 4.60 GiB #VL7.0
/dev/sda6 reiserfs  /mnt/sda6                 10.00 GiB 9.55 GiB 457.78 MiB #VL6.0
/dev/sda7 fat32     /mnt/sda7 PUBLIC      11.19 GiB 3.30 GiB 7.89 Gib
/dev/sdb1 reiserfs  /mnt/sdb1                   1.88 GiB 1.88 GiB 4.00 KiB boot #was Win98 but apparently I had tried to put Slackware 13.37.0 on it! (no Vector version)
/dev/sdb2 reiserfs  /mnt/sdb2                   6.09 GiB 5.70 GiB 402.30 MiB #VL5.9
/dev/sdv3 reiserfs  /mnt/sdb3                   6.00 GiB 32.30 MiB 5.97 GiB   #Code
/dev/sdb5 reiserfs  /mnt/sdb5                 10.00 GiB 9.63 Gib 375.93 MiB #Iso
/dev/sdb6 reiserfs  /mnt/sdb6                 13.31 GiB 34.42 MiB 13.27 GiB #VL7.1 /home
Title: Re: VL7.1 STD feedback and suggestions.
Post by: roarde on December 21, 2014, 04:29:01 pm
Please mount sdb6 and post the output of 'ls -l <mountpoint>'
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on December 22, 2014, 07:03:13 am
In VL7.0 LIVE
Quote
vl:$ ls -l /mnt/sdb6
total 0
drwxr-xr-x 6 1000 1000 424 Dec 22  2014 bruce/
drwxr-xr-x 3 root root  72 Jul  6  2010 ftp/
vector:/~
vl:$
Title: Re: VL7.1 STD feedback and suggestions.
Post by: roarde on December 23, 2014, 10:54:06 am
The hunch I had was wrong. Thanks for posting the info, sorry it didn't show me an answer. Maybe wiser heads will chime in.

I need to do a fresh install of Light RC1 just to check on overwriting it (don't ask :P). Light and STD now share the same installer, so I could try to duplicate your problem then. More info would be helpful:
   Which partitions were pre-existing, which did you choose "do not format" for, so on.
   Was your username all lower case alpha, a mixture of alpha and numbers, a mixture of upper and lower . . . ?
   Which bootloader, and where did you have it install to?
   Anything you can think to mention about choices and actions in the install process, or about the filesystems or anything you brought in.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on December 23, 2014, 01:40:20 pm
Oh! Well! "The best laid plans of mice and men gan aft aglay."
See if I can remember these:
All partitions were preexisting.  A previous install had put sda1 to ext3, this one put it back to reiserfs.  Sdb6 was not reformatted (it was already reiserfs).
My first try had user as 'Bruce' which it had objected to.  Following installs had 'bruce'.
This last install used the gui Advanced install and LILO bootloader to sda MBR.
I don't remember seeing it this time but every time XFCE was offered, I checked it.  Do I remember that there were issues with gui install? or XFCE?
Merry Christmas to all.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: nightflier on December 23, 2014, 05:35:38 pm
Since there is nothing on sda1 to lose, I'd suggest re-installing. Make sure you choose to format it. Do not use a separate /home partition. If that gets you a working system, putting /home on sda6 afterwards is easy.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: wigums on December 24, 2014, 10:19:41 am
this may be a silly question...you know after assining a partition to a given designation i.e. / or /home that you can seperately click on and set the partition type right? just cuz it pops up with ext3 or rieser you can change that.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: roarde on December 24, 2014, 04:30:25 pm
@StrayBit

Did you choose to use the bootsplash? I think "use it" is the default and not using it has to be selected, but I might have that backwards.

See if changing the / reference in /etc/fstab from UUID to /dev/sda1 makes any difference.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on December 25, 2014, 09:32:11 am
@wiggums:  ext3 is default.  I want, and usually select reiserfs.  The few times I've tried ext3, I've had more trouble than with reiserfs.

@roarde:  changing from UUID to /dev/sda1 had no effect.  I am in the process of reinstalling with text install to only sda1 and sda2.  
As I have 11 potential mount points, it covers the Back/Next buttons but tabbing gets me to the bottom of the screen.
Did NOT check for xfce4.  I've always left
Code: [Select]
[ ] Disable boot animation empty.  Checked it this time...
Reboot accepted password then told me there are no x clients and now I'm left with a terminal window with a white back ground that occupies 1/4 the screen.  It is only selected while the mouse is hovering over it.  The menu suggested vasm which I tried
Quote
bash:  vasm:  command not found
but mc works.  
Hm...The mount selection panel was not sorted this time and with my eyesight, I had selected sdb2 as swap (6.9 GiB instead of 1.86) - wiped out VL5.9.  OK.  Next time I need it, I can reinstall.
Interesting: / is UUID but swap is /dev/sdb2.
Neither ctrl-alt-del nor shutdown -P now worked - the later just showed help!

Merry Christmas to all.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: nightflier on December 25, 2014, 12:30:59 pm
If you did not install xfce, it is normal that you get just a default X session with a terminal. In that terminal window, try command "fluxbox" and see if it comes up.

Otherwise, log in as root and use slapt-get to install the desktop of your choosing, and build the system from there.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on December 26, 2014, 07:46:33 am
Thanks, nightflier.

Fluxbox gave illegal command.

Rebooted into tui as root - still illegal!

Reinstalling with gui and XFCE4 (no boot animation)...
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on December 26, 2014, 08:17:43 am
That set me back to original - even with home in /.

I'm considering downloading rc3 again and burning a new cd.  Is there an md5 of it?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: nightflier on December 26, 2014, 08:54:03 am
RC3 is outdated. RC3.1 download and md5sum links are here:
http://vlcore.vectorlinux.com/pkg/untested/veclinux-7.1/iso/

Title: Re: VL7.1 STD feedback and suggestions.
Post by: pekka on December 28, 2014, 07:45:02 am
Hi
I was sent here by the guys at #vectorlinux channel in  freenode.
I've tested VL64-7.1-STD-RC3.1, and have some feedback about the text-installer.
The installation utilized an USB-flash pen, a desktop pc with a BIOS, and a new server with UEFI.

1) UEFI:
When trying to install VL on a system with new UEFI the installer get dropped to a root shell, see attached picture.
Ctrl-Alt-F1/F2/F3 gave 3 root shells, but no installer.  I dont know if it is the intention to have 3 virtual consoles in the installer. Never the less, I did like the idea. The availability of virtual consoles is a good thing. They are power tools for experienced users who do not need an X-session. But what is the command to start the installer from a root shell?
In the end I did overcome the UEFI install issue by installing VL on my desktop pc which have a BIOS, and then put the disk back in the server. VL did then boot without problems on the server.

2) BIOS:
With the BIOS, the installer start the installation process without any problem. The installer apparently run on the first virtual console. When testing the other 2 consoles, Ctrl-Alt-F2 and Ctrl-Alt-F3, I get 2 additional text-install processes. However the root shells are available by using the "back" button in the first page of the text-installer. I think there should be some information about the availability of 2 additional consoles in the text in the first page. Root consoles are a very useful feature for power users.

3) SSD:
The desktop pc is using a SSD as a system disk,  and the disk is set up for multibooting. That imply VectorLinux will share the SSD with other operating systems. However, I use GUID Partition Table (GPT), which is a better choice for for a SSD. The text-installer come with standard cfdisk (linux fdisk) as partition tool. Unfortunately cfdisk lack support for GPT. I think VectorLinux should add support for GPT, at least in the 64-bit version which I assume will also be used on newer hardware. A good tool, which operate in the same way as linux fdisk is GPT fdisk, http://sourceforge.net/projects/gptfdisk/
It would be nice if GPT fdisk was availale as an option in the "Disk Partition" page.

4) Installing on RAID? - Some additional thoughts:
I did the test on quite new hardware, but sometimes I do install VL on old hardware. In my eyes, given the fact that VectorLinux run well on old hardware, and has a slower release cycle than compareable distros, make Vectorlinux a very good choice for a server OS. Old desktop pc's can get a second life as servers, and I avoid reinstall too often. However, running a server on old HW is a risk. Sooner or later the HW will fail. If I reuse old HW this way, I always use raid arrays. Mirrored raid give an extra layer of security when old mechanical disks fail. And they do fail.
The linux kernel do autodetect raid arrays, and raid arrays were available as an install option in the text-installer. However, when I did install VL on a mirrored raid array (md126), VL did fail to boot. LILO boot loader did show an option to boot md126, but booting md126 gave a kernel panic. Both LILO and GRUB2 can be configured to boot an OS installed on a raid array, and some distros offer this option "out of the box" in the installer. However, with slackware you need to chroot, do a mkinitrd and make sure the necessary kernel modules are loaded, configure and reinstall bootloader from the chroot environment, etc. This kind of hacking take time.

I think a working "out of the box" option to "install VL on raid" in the text-installer would be a great feature. This feature will save users a lot of time and kernel-woodoo. And if I don't remember wrong, with this feature VectroLinux will be the only Slack-based distro, and maybe one of the few non-systemd distros, which have this feature working "out of the box" in the installer. Maybe a feature worth considering for VectorLinux.

###
Title: Re: VL7.1 STD feedback and suggestions.
Post by: roarde on December 28, 2014, 10:38:16 am
Thank you for your thoughts, pekka. I know it helps a lot to have a fresh take on install from someone who can express it so well.

UEFI and easier access to GPT were discussed, but the time that would have been spent on them had to be skipped to get this already late release out the door. GPT is available in the shell at install time: parted. I'm used to trying fdisk first, then cfdisk. Being used to those, I look at parted differently as I think you do. But I tried to put new eyes on and took another look. Since the word "help" is indeed a working command, I begin to think parted might be the best choice for those who haven't partitioned from the command line before; and not at all hard for previous users of other tools to pick up. But yes, a tip to its availability at the right point would be nice. UEFI and easier access to GPT will surely be handled in later releases.

Which brings me to one of my own questions: Does the gui installer already handle GPT if the table is already present? I have no way to check.

I have no doubt that VL releases will come to handle GPT and UEFI as automatically as is possible, just not this time.

RAID brings up another question from me: Wasn't VL set up to install to RAID at one time?
(not that i'd have anything to do with its absence)

Can't click "Post" without saying thank you once again, pekka.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: sledgehammer on December 28, 2014, 11:23:16 am
Don't know much about this complicated discussion.  But I loaded VL64-7.1-STD-RC3.1 on my samsung rf511, via unetbootin, and had no problems. The onboard wifi card worked out of the box.  Great distro!  I didn't reformat home and all my files are there.  There was a file missing when I loaded libreoffice and lyx doesn't work yet.  I will look into that as time permits.

John 
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on December 28, 2014, 11:47:45 am
Thanks for the link, nightflier.  Sorry for my abbreviation - I was installing rc3.1.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: roarde on December 28, 2014, 12:20:55 pm
@StrayBit:
Sorry if I didn't catch you before a reinstall. I suggest using the bootsplash as you apparently had been doing, I'm pretty sure any difference between using splash and not has been repaired. But if it hasn't, the difference would favor bootsplash and the initrd it uses.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on December 28, 2014, 04:29:01 pm
Using 7.0-LIVE, I copied the 7.1-rc3.1.iso and mdsum....txt from Win7 to my iso partition where I could check it  - it matched.
Ran the memtest from the LIVE cd - 1014M passed with no errors.
What can I do to get it to accept my passwords?  I haven't reinstalled yet but I could to allow the animation.

Also, since installing SW14.1 and 7.1-RC3.1, I get a message that my battery is low and have to press F1 to continue!  This is a tower - no battery.  Booting to cd does not give that message.  Nor did previous installations.

Presently, I have to use the cd to boot into 7.0.  I hate those USID labels!  And live desktop does NOT tell me what the various partitions are just their size!  (That's when I didn't catch it to mount them at startup.)
Title: Re: VL7.1 STD feedback and suggestions.
Post by: roarde on December 28, 2014, 04:42:01 pm
See if reformatting swap (again as swap) helps. This will have the unwanted side effect of changing its UUID. Allow for that. I'd reference it by /dev/ for right now.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: nightflier on December 29, 2014, 03:57:24 am
Also, since installing SW14.1 and 7.1-RC3.1, I get a message that my battery is low and have to press F1 to continue!  This is a tower - no battery.  Booting to cd does not give that message.  Nor did previous installations.

That is referencing the bios battery on your motherboard. It is usually the size of a coin and snaps in/out of a spring loaded holder. It is there to maintain your bios settings when grid power is not available.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on December 29, 2014, 04:04:27 am


That is referencing the bios battery on your motherboard. It is usually the size of a coin and snaps in/out of a spring loaded holder. It is there to maintain your bios settings when grid power is not available.

Hopefully. I've had a motherboard or two where that sucker was soldered onto it and there was no easy way to replace it. >.<
Title: Re: VL7.1 STD feedback and suggestions.
Post by: nightflier on December 29, 2014, 04:28:54 am
Presently, I have to use the cd to boot into 7.0.  I hate those USID labels!  And live desktop does NOT tell me what the various partitions are just their size!  (That's when I didn't catch it to mount them at startup.)

If the command "blkid" does not give you the info, try "ls -al /dev/disk/by-uuid"
Title: Re: VL7.1 STD feedback and suggestions.
Post by: Pita on December 29, 2014, 05:24:10 pm
VL-7.1-STD-RC3.1.iso  32bit  PC desktop

Gui installer hang on installing grip. :(
Got out with menu reboot.

In /boot there was no vmlinuz-3.12.16. :(
Copied sata over from from iso.
When booting there was no fstab in /etc :(


This is surely the fault of a badly scratched DVD.  :-[

So sorry.

Installed now with unetbootin and all went smooth.

However, can't find the password for root.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: sledgehammer on December 29, 2014, 06:00:31 pm
Pita,

Not sure about 32 bit but on latest 64 bit GUI installer asks for administrative password on same page as user password, one line down or above.  If you put in administrative password at that point, use it as your root password.

John
Title: Re: VL7.1 STD feedback and suggestions.
Post by: Pita on December 30, 2014, 04:56:26 pm
Pita,

Not sure about 32 bit but on latest 64 bit GUI installer asks for administrative password on same page as user password, one line down or above.  If you put in administrative password at that point, use it as your root password.

John

I must have missed that. Will check again.
Solved by making me sudo then make root PW.

Healthy & Happy New Year
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on February 11, 2015, 08:19:47 am
January 2015,7.1 release announcement,yet all of the talk is from back in 2014. I have just started with Vector,tried 7.0,7.1RC1,7.1RC2,7.1RC3.Right now using RC2 other than password,grub,gparted,xarchiver and running text on boot O.K.
Using RC3 grub actually finished but old BCM4306 no go did not start xfce4 . quit using RC1 because of password issue,thought RC2 may be improvement same issue,if I want dumb warn and let me choose dumb.Not Big Brother here. Seems to me I am the only one with current posts,as I asked in another forum or whatever,is VectorLinux in neutral?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: vincent2 on March 01, 2015, 06:07:07 am
Bon soiree!

so far vl7.1std rc3.1 installed smoothly@thailand and works smoothly since late nov .2014...more thai began to notice the charmings of vl.7.1, such as NOK airlines and many small business  org.or soho individuals....

Pls.upload  kernel 3.19or 3.18 pkgs on tets repo so that we test here in asean countries and india...

vl7.1 rc3.1 is very stable and fast for booking airasia etickets onlines...

latest opera-devoloper  can be run nicely as well...

expecting final vl.7.1 gold release soon!

now vector seems gong to vl.7.2 ....

Title: Re: VL7.1 STD feedback and suggestions.
Post by: vincent2 on March 01, 2015, 06:11:46 am
expecting vector7.1 and 7.2 can offer better performances with 4G and 5G mobile internet as well...

also expecting vector can fix up SIM card  backdoors(OTA key) debunked by snowden this week  as well  when using 3g 4g modem  over vector...
Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on April 11, 2015, 09:12:17 am
OK. This is starting to drive me absolutely nuts.

I swapped the internal wifi card out on the notebook to an Intel AC 7260. Fresh install of 7.1 STD (64-bit) RC4.2 results in no wireless card found.

Shows up in lspci:

02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)


lsmod doesn't show the driver. So, modprobe iwlwifi appears to install however lsmod shows the following:

Code: [Select]
Module             Size       Used by
iwlwifi                75885    0
cfg80211          412000  1 iwlwifi
rfkill                  18744    2 cfg80211,bluetooth

Code: [Select]
retired1:$ dmesg | grep Intel
[    6.863954] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14
[    6.864110] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
[    6.864263] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
[    7.370194] Bluetooth: hci0: read Intel version: 3707100180012d0d00
[    7.418388] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq
[    7.567143] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
[  140.447504] Intel(R) Wireless WiFi driver for Linux, in-tree:
[  140.447507] Copyright(c) 2003-2013 Intel Corporation

$ iwconfig
eth0      no wireless extensions.

lo        no wireless extensions.

Code: [Select]
root:# modinfo iwlwifi
filename:       /lib/modules/3.12.16/kernel/drivers/net/wireless/iwlwifi/iwlwifi.ko
license:        GPL
author:         Copyright(c) 2003-2013 Intel Corporation <ilw@linux.intel.com>
version:        in-tree:
description:    Intel(R) Wireless WiFi driver for Linux
firmware:       iwlwifi-100-5.ucode
firmware:       iwlwifi-1000-5.ucode
firmware:       iwlwifi-135-6.ucode
firmware:       iwlwifi-105-6.ucode
firmware:       iwlwifi-2030-6.ucode
firmware:       iwlwifi-2000-6.ucode
firmware:       iwlwifi-5150-2.ucode
firmware:       iwlwifi-5000-5.ucode
firmware:       iwlwifi-6000g2b-6.ucode
firmware:       iwlwifi-6000g2a-5.ucode
firmware:       iwlwifi-6050-5.ucode
firmware:       iwlwifi-6000-4.ucode
srcversion:     D620D2EC19F8C5D11934C88
alias:          pci:v00008086d00000892sv*sd00000462bc*sc*i*
alias:          pci:v00008086d00000893sv*sd00000262bc*sc*i*
alias:          pci:v00008086d00000892sv*sd00000062bc*sc*i*
alias:          pci:v00008086d00000894sv*sd00000822bc*sc*i*
alias:          pci:v00008086d00000894sv*sd00000422bc*sc*i*
alias:          pci:v00008086d00000895sv*sd00000222bc*sc*i*
alias:          pci:v00008086d00000894sv*sd00000022bc*sc*i*
alias:          pci:v00008086d0000088Fsv*sd00005260bc*sc*i*
alias:          pci:v00008086d0000088Esv*sd00004860bc*sc*i*
alias:          pci:v00008086d0000088Esv*sd0000446Abc*sc*i*
alias:          pci:v00008086d0000088Esv*sd00004460bc*sc*i*
alias:          pci:v00008086d0000088Fsv*sd0000426Abc*sc*i*
alias:          pci:v00008086d0000088Fsv*sd00004260bc*sc*i*
alias:          pci:v00008086d0000088Esv*sd0000406Abc*sc*i*
alias:          pci:v00008086d0000088Esv*sd00004060bc*sc*i*
alias:          pci:v00008086d00000887sv*sd00004462bc*sc*i*
alias:          pci:v00008086d00000888sv*sd00004262bc*sc*i*
alias:          pci:v00008086d00000887sv*sd00004062bc*sc*i*
alias:          pci:v00008086d00000890sv*sd00004822bc*sc*i*
alias:          pci:v00008086d00000890sv*sd00004422bc*sc*i*
alias:          pci:v00008086d00000891sv*sd00004222bc*sc*i*
alias:          pci:v00008086d00000890sv*sd00004022bc*sc*i*
alias:          pci:v00008086d00000896sv*sd00005027bc*sc*i*
alias:          pci:v00008086d00000896sv*sd00005025bc*sc*i*
alias:          pci:v00008086d00000897sv*sd00005017bc*sc*i*
alias:          pci:v00008086d00000897sv*sd00005015bc*sc*i*
alias:          pci:v00008086d00000896sv*sd00005007bc*sc*i*
alias:          pci:v00008086d00000896sv*sd00005005bc*sc*i*
alias:          pci:v00008086d000008AEsv*sd00001027bc*sc*i*
alias:          pci:v00008086d000008AEsv*sd00001025bc*sc*i*
alias:          pci:v00008086d000008AFsv*sd00001017bc*sc*i*
alias:          pci:v00008086d000008AFsv*sd00001015bc*sc*i*
alias:          pci:v00008086d000008AEsv*sd00001007bc*sc*i*
alias:          pci:v00008086d000008AEsv*sd00001005bc*sc*i*
alias:          pci:v00008086d00000084sv*sd00001316bc*sc*i*
alias:          pci:v00008086d00000084sv*sd00001216bc*sc*i*
alias:          pci:v00008086d00000083sv*sd00001326bc*sc*i*
alias:          pci:v00008086d00000083sv*sd00001226bc*sc*i*
alias:          pci:v00008086d00000083sv*sd00001306bc*sc*i*
alias:          pci:v00008086d00000083sv*sd00001206bc*sc*i*
alias:          pci:v00008086d00000084sv*sd00001315bc*sc*i*
alias:          pci:v00008086d00000084sv*sd00001215bc*sc*i*
alias:          pci:v00008086d00000083sv*sd00001325bc*sc*i*
alias:          pci:v00008086d00000083sv*sd00001225bc*sc*i*
alias:          pci:v00008086d00000083sv*sd00001305bc*sc*i*
alias:          pci:v00008086d00000083sv*sd00001205bc*sc*i*
alias:          pci:v00008086d00000886sv*sd00001317bc*sc*i*
alias:          pci:v00008086d00000886sv*sd00001315bc*sc*i*
alias:          pci:v00008086d00000885sv*sd00001327bc*sc*i*
alias:          pci:v00008086d00000885sv*sd00001325bc*sc*i*
alias:          pci:v00008086d00000885sv*sd00001307bc*sc*i*
alias:          pci:v00008086d00000885sv*sd00001305bc*sc*i*
alias:          pci:v00008086d00000089sv*sd00001316bc*sc*i*
alias:          pci:v00008086d00000089sv*sd00001311bc*sc*i*
alias:          pci:v00008086d00000087sv*sd00001326bc*sc*i*
alias:          pci:v00008086d00000087sv*sd00001321bc*sc*i*
alias:          pci:v00008086d00000087sv*sd00001306bc*sc*i*
alias:          pci:v00008086d00000087sv*sd00001301bc*sc*i*
alias:          pci:v00008086d00000091sv*sd00005226bc*sc*i*
alias:          pci:v00008086d00000091sv*sd00005225bc*sc*i*
alias:          pci:v00008086d00000091sv*sd00005221bc*sc*i*
alias:          pci:v00008086d00000091sv*sd00005207bc*sc*i*
alias:          pci:v00008086d00000091sv*sd00005206bc*sc*i*
alias:          pci:v00008086d00000091sv*sd00005205bc*sc*i*
alias:          pci:v00008086d00000091sv*sd00005201bc*sc*i*
alias:          pci:v00008086d00000090sv*sd00005216bc*sc*i*
alias:          pci:v00008086d00000090sv*sd00005215bc*sc*i*
alias:          pci:v00008086d00000090sv*sd00005211bc*sc*i*
alias:          pci:v00008086d0000008Bsv*sd00005317bc*sc*i*
alias:          pci:v00008086d0000008Bsv*sd00005315bc*sc*i*
alias:          pci:v00008086d0000008Asv*sd00005327bc*sc*i*
alias:          pci:v00008086d0000008Asv*sd00005325bc*sc*i*
alias:          pci:v00008086d0000008Asv*sd00005307bc*sc*i*
alias:          pci:v00008086d0000008Asv*sd00005305bc*sc*i*
alias:          pci:v00008086d00000082sv*sd00001305bc*sc*i*
alias:          pci:v00008086d00000082sv*sd00001304bc*sc*i*
alias:          pci:v00008086d00000082sv*sd00004820bc*sc*i*
alias:          pci:v00008086d00000085sv*sd0000C228bc*sc*i*
alias:          pci:v00008086d00000085sv*sd0000C220bc*sc*i*
alias:          pci:v00008086d00000082sv*sd0000C020bc*sc*i*
alias:          pci:v00008086d00000085sv*sd00001316bc*sc*i*
alias:          pci:v00008086d00000085sv*sd00001318bc*sc*i*
alias:          pci:v00008086d00000085sv*sd00001311bc*sc*i*
alias:          pci:v00008086d00000082sv*sd00001328bc*sc*i*
alias:          pci:v00008086d00000082sv*sd00001326bc*sc*i*
alias:          pci:v00008086d00000082sv*sd00001321bc*sc*i*
alias:          pci:v00008086d00000082sv*sd00001308bc*sc*i*
alias:          pci:v00008086d00000082sv*sd00001307bc*sc*i*
alias:          pci:v00008086d00000082sv*sd00001306bc*sc*i*
alias:          pci:v00008086d00000082sv*sd00001301bc*sc*i*
alias:          pci:v00008086d00004239sv*sd00001316bc*sc*i*
alias:          pci:v00008086d00004239sv*sd00001311bc*sc*i*
alias:          pci:v00008086d00004238sv*sd00001118bc*sc*i*
alias:          pci:v00008086d00004238sv*sd00001111bc*sc*i*
alias:          pci:v00008086d0000422Csv*sd00001326bc*sc*i*
alias:          pci:v00008086d0000422Csv*sd00001321bc*sc*i*
alias:          pci:v00008086d0000422Csv*sd00001307bc*sc*i*
alias:          pci:v00008086d0000422Csv*sd00001306bc*sc*i*
alias:          pci:v00008086d0000422Csv*sd00001301bc*sc*i*
alias:          pci:v00008086d0000422Bsv*sd00001128bc*sc*i*
alias:          pci:v00008086d0000422Bsv*sd00001121bc*sc*i*
alias:          pci:v00008086d0000422Bsv*sd00001108bc*sc*i*
alias:          pci:v00008086d0000422Bsv*sd00001101bc*sc*i*
alias:          pci:v00008086d0000423Dsv*sd00001316bc*sc*i*
alias:          pci:v00008086d0000423Dsv*sd00001216bc*sc*i*
alias:          pci:v00008086d0000423Dsv*sd00001311bc*sc*i*
alias:          pci:v00008086d0000423Dsv*sd00001211bc*sc*i*
alias:          pci:v00008086d0000423Csv*sd00001326bc*sc*i*
alias:          pci:v00008086d0000423Csv*sd00001321bc*sc*i*
alias:          pci:v00008086d0000423Csv*sd00001221bc*sc*i*
alias:          pci:v00008086d0000423Csv*sd00001306bc*sc*i*
alias:          pci:v00008086d0000423Csv*sd00001206bc*sc*i*
alias:          pci:v00008086d0000423Csv*sd00001301bc*sc*i*
alias:          pci:v00008086d0000423Csv*sd00001201bc*sc*i*
alias:          pci:v00008086d0000423Bsv*sd00001011bc*sc*i*
alias:          pci:v00008086d0000423Asv*sd00001021bc*sc*i*
alias:          pci:v00008086d0000423Asv*sd00001001bc*sc*i*
alias:          pci:v00008086d00004236sv*sd00001114bc*sc*i*
alias:          pci:v00008086d00004236sv*sd00001014bc*sc*i*
alias:          pci:v00008086d00004236sv*sd00001111bc*sc*i*
alias:          pci:v00008086d00004236sv*sd00001011bc*sc*i*
alias:          pci:v00008086d00004235sv*sd00001104bc*sc*i*
alias:          pci:v00008086d00004235sv*sd00001004bc*sc*i*
alias:          pci:v00008086d00004235sv*sd00001101bc*sc*i*
alias:          pci:v00008086d00004235sv*sd00001001bc*sc*i*
alias:          pci:v00008086d00004235sv*sd00001124bc*sc*i*
alias:          pci:v00008086d00004235sv*sd00001024bc*sc*i*
alias:          pci:v00008086d00004235sv*sd00001121bc*sc*i*
alias:          pci:v00008086d00004235sv*sd00001021bc*sc*i*
alias:          pci:v00008086d00004237sv*sd00001316bc*sc*i*
alias:          pci:v00008086d00004237sv*sd00001216bc*sc*i*
alias:          pci:v00008086d00004237sv*sd00001315bc*sc*i*
alias:          pci:v00008086d00004237sv*sd00001215bc*sc*i*
alias:          pci:v00008086d00004237sv*sd00001314bc*sc*i*
alias:          pci:v00008086d00004237sv*sd00001214bc*sc*i*
alias:          pci:v00008086d00004237sv*sd00001311bc*sc*i*
alias:          pci:v00008086d00004237sv*sd00001211bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001326bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001226bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001325bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001225bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001324bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001224bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001321bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001221bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001306bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001206bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001305bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001205bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001304bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001204bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001301bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001201bc*sc*i*
depends:        cfg80211
intree:         Y
vermagic:       3.12.16 SMP preempt mod_unload
parm:           swcrypto:using crypto in software (default 0 [hardware]) (int)
parm:           11n_disable:disable 11n functionality, bitmap: 1: full, 2: disable agg TX, 4: disable agg RX, 8 enable agg TX (uint)
parm:           amsdu_size_8K:enable 8K amsdu size (default 0) (int)
parm:           fw_restart:restart firmware in case of error (default true) (bool)
parm:           antenna_coupling:specify antenna coupling in dB (defualt: 0 dB) (int)
parm:           wd_disable:Disable stuck queue watchdog timer 0=system default, 1=disable, 2=enable (default: 0) (int)
parm:           nvm_file:NVM file name (charp)
parm:           bt_coex_active:enable wifi/bt co-exist (default: enable) (bool)
parm:           led_mode:0=system default, 1=On(RF On)/Off(RF Off), 2=blinking, 3=Off (default: 0) (int)
parm:           power_save:enable WiFi power management (default: disable) (bool)
parm:           power_level:default power save level (range from 1 - 5, default: 1) (int)

Firmware IS installed to /lib/firmware, but not listed with modinfo iwlwifi command.

Dunno what the hell is going on, but I'm not a happy camper right now.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on May 01, 2015, 03:57:48 am
Here are the outputs in Mint. Hopefully it'll give a clue as to what's missing in VL.

lspci

Code: [Select]
retired1@Bodacious ~ $ lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5)
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)
03:00.0 Ethernet controller: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet (rev c0)

lsmod

Code: [Select]
retired1@Bodacious ~ $ lsmod | grep iwl
iwlmvm                189813  0
mac80211              630653  1 iwlmvm
iwlwifi               169932  1 iwlmvm
cfg80211              484040  3 iwlwifi,mac80211,iwlmvm

dmesg

Code: [Select]
retired1@Bodacious ~ $ dmesg | grep Intel
[    0.000000]   Intel GenuineIntel
[    0.189998] smpboot: CPU0: Intel(R) Core(TM) i3-2350M CPU @ 2.30GHz (fam: 06, model: 2a, stepping: 07)
[    0.190118] Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver.
[   25.191908] Intel(R) Wireless WiFi driver for Linux, in-tree:
[   25.191911] Copyright(c) 2003-2013 Intel Corporation
[   25.253579] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144
[   25.296282] Bluetooth: hci0: read Intel version: 3707100180012d0d00
[   25.365463] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq
[   25.380805] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input18
[   25.380887] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input17
[   25.380955] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
[   25.414221] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated

modinfo
Code: [Select]
retired1@Bodacious ~ $ modinfo iwlwifi
filename:       /lib/modules/3.13.0-37-generic/kernel/drivers/net/wireless/iwlwifi/iwlwifi.ko
license:        GPL
author:         Copyright(c) 2003-2013 Intel Corporation <ilw@linux.intel.com>
version:        in-tree:
description:    Intel(R) Wireless WiFi driver for Linux
firmware:       iwlwifi-100-5.ucode
firmware:       iwlwifi-1000-5.ucode
firmware:       iwlwifi-135-6.ucode
firmware:       iwlwifi-105-6.ucode
firmware:       iwlwifi-2030-6.ucode
firmware:       iwlwifi-2000-6.ucode
firmware:       iwlwifi-5150-2.ucode
firmware:       iwlwifi-5000-5.ucode
firmware:       iwlwifi-6000g2b-6.ucode
firmware:       iwlwifi-6000g2a-5.ucode
firmware:       iwlwifi-6050-5.ucode
firmware:       iwlwifi-6000-4.ucode
firmware:       iwlwifi-7265-7.ucode
firmware:       iwlwifi-3160-7.ucode
firmware:       iwlwifi-7260-7.ucode
srcversion:     C2D0F3DFCA289585C100E36
alias:          pci:v00008086d0000095Asv*sd00005490bc*sc*i*
alias:          pci:v00008086d0000095Bsv*sd00005290bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00005590bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00005190bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00005090bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00005420bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd0000502Abc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00005020bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00009410bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00009310bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00009510bc*sc*i*
alias:          pci:v00008086d0000095Bsv*sd00009200bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00009210bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00009112bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00009110bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00009012bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00009010bc*sc*i*
alias:          pci:v00008086d0000095Bsv*sd00005202bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00005102bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00005002bc*sc*i*
alias:          pci:v00008086d0000095Bsv*sd00005200bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd0000500Abc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00005000bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00001010bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00005400bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00005510bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00005410bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00005012bc*sc*i*
alias:          pci:v00008086d0000095Bsv*sd00005210bc*sc*i*
alias:          pci:v00008086d0000095Bsv*sd00005302bc*sc*i*
alias:          pci:v00008086d0000095Bsv*sd00005310bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd0000510Abc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00005100bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00005112bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00005110bc*sc*i*
alias:          pci:v00008086d0000095Asv*sd00005010bc*sc*i*
alias:          pci:v00008086d000008B3sv*sd00008570bc*sc*i*
alias:          pci:v00008086d000008B3sv*sd00008470bc*sc*i*
alias:          pci:v00008086d000008B4sv*sd00008270bc*sc*i*
alias:          pci:v00008086d000008B3sv*sd00008062bc*sc*i*
alias:          pci:v00008086d000008B3sv*sd00008060bc*sc*i*
alias:          pci:v00008086d000008B3sv*sd00008172bc*sc*i*
alias:          pci:v00008086d000008B3sv*sd00008170bc*sc*i*
alias:          pci:v00008086d000008B3sv*sd00008072bc*sc*i*
alias:          pci:v00008086d000008B3sv*sd00008070bc*sc*i*
alias:          pci:v00008086d000008B4sv*sd00000370bc*sc*i*
alias:          pci:v00008086d000008B3sv*sd00000472bc*sc*i*
alias:          pci:v00008086d000008B3sv*sd00000470bc*sc*i*
alias:          pci:v00008086d000008B4sv*sd00000272bc*sc*i*
alias:          pci:v00008086d000008B4sv*sd00000270bc*sc*i*
alias:          pci:v00008086d000008B3sv*sd00000062bc*sc*i*
alias:          pci:v00008086d000008B3sv*sd00000060bc*sc*i*
alias:          pci:v00008086d000008B3sv*sd00000172bc*sc*i*
alias:          pci:v00008086d000008B3sv*sd00000170bc*sc*i*
alias:          pci:v00008086d000008B3sv*sd00000072bc*sc*i*
alias:          pci:v00008086d000008B3sv*sd00000070bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000C420bc*sc*i*
alias:          pci:v00008086d000008B2sv*sd0000C220bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000C02Abc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000C020bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000C360bc*sc*i*
alias:          pci:v00008086d000008B2sv*sd0000C370bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000C560bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000C570bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000C462bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000C460bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000C472bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000C470bc*sc*i*
alias:          pci:v00008086d000008B2sv*sd0000C262bc*sc*i*
alias:          pci:v00008086d000008B2sv*sd0000C26Abc*sc*i*
alias:          pci:v00008086d000008B2sv*sd0000C260bc*sc*i*
alias:          pci:v00008086d000008B2sv*sd0000C272bc*sc*i*
alias:          pci:v00008086d000008B2sv*sd0000C270bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000C760bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000C770bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000C162bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000C062bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000C160bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000C06Abc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000C060bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000C170bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000C072bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000C070bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd00004420bc*sc*i*
alias:          pci:v00008086d000008B2sv*sd00004220bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000402Abc*sc*i*
alias:          pci:v00008086d000008B1sv*sd00004020bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd00005070bc*sc*i*
alias:          pci:v00008086d000008B2sv*sd00004360bc*sc*i*
alias:          pci:v00008086d000008B2sv*sd00004370bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd00004560bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd00004570bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd00004A6Cbc*sc*i*
alias:          pci:v00008086d000008B1sv*sd00004A6Ebc*sc*i*
alias:          pci:v00008086d000008B1sv*sd00004A70bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000486Ebc*sc*i*
alias:          pci:v00008086d000008B1sv*sd00004870bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd00004462bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000446Abc*sc*i*
alias:          pci:v00008086d000008B1sv*sd00004460bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd00004472bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd00004470bc*sc*i*
alias:          pci:v00008086d000008B2sv*sd00004262bc*sc*i*
alias:          pci:v00008086d000008B2sv*sd0000426Abc*sc*i*
alias:          pci:v00008086d000008B2sv*sd00004260bc*sc*i*
alias:          pci:v00008086d000008B2sv*sd00004272bc*sc*i*
alias:          pci:v00008086d000008B2sv*sd00004270bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd00004162bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd00004062bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd00004160bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd0000406Abc*sc*i*
alias:          pci:v00008086d000008B1sv*sd00004060bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd00004170bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd00004072bc*sc*i*
alias:          pci:v00008086d000008B1sv*sd00004070bc*sc*i*
alias:          pci:v00008086d00000892sv*sd00000462bc*sc*i*
alias:          pci:v00008086d00000893sv*sd00000262bc*sc*i*
alias:          pci:v00008086d00000892sv*sd00000062bc*sc*i*
alias:          pci:v00008086d00000894sv*sd00000822bc*sc*i*
alias:          pci:v00008086d00000894sv*sd00000422bc*sc*i*
alias:          pci:v00008086d00000895sv*sd00000222bc*sc*i*
alias:          pci:v00008086d00000894sv*sd00000022bc*sc*i*
alias:          pci:v00008086d0000088Fsv*sd00005260bc*sc*i*
alias:          pci:v00008086d0000088Esv*sd00004860bc*sc*i*
alias:          pci:v00008086d0000088Esv*sd0000446Abc*sc*i*
alias:          pci:v00008086d0000088Esv*sd00004460bc*sc*i*
alias:          pci:v00008086d0000088Fsv*sd0000426Abc*sc*i*
alias:          pci:v00008086d0000088Fsv*sd00004260bc*sc*i*
alias:          pci:v00008086d0000088Esv*sd0000406Abc*sc*i*
alias:          pci:v00008086d0000088Esv*sd00004060bc*sc*i*
alias:          pci:v00008086d00000887sv*sd00004462bc*sc*i*
alias:          pci:v00008086d00000888sv*sd00004262bc*sc*i*
alias:          pci:v00008086d00000887sv*sd00004062bc*sc*i*
alias:          pci:v00008086d00000890sv*sd00004822bc*sc*i*
alias:          pci:v00008086d00000890sv*sd00004422bc*sc*i*
alias:          pci:v00008086d00000891sv*sd00004222bc*sc*i*
alias:          pci:v00008086d00000890sv*sd00004022bc*sc*i*
alias:          pci:v00008086d00000896sv*sd00005027bc*sc*i*
alias:          pci:v00008086d00000896sv*sd00005025bc*sc*i*
alias:          pci:v00008086d00000897sv*sd00005017bc*sc*i*
alias:          pci:v00008086d00000897sv*sd00005015bc*sc*i*
alias:          pci:v00008086d00000896sv*sd00005007bc*sc*i*
alias:          pci:v00008086d00000896sv*sd00005005bc*sc*i*
alias:          pci:v00008086d000008AEsv*sd00001027bc*sc*i*
alias:          pci:v00008086d000008AEsv*sd00001025bc*sc*i*
alias:          pci:v00008086d000008AFsv*sd00001017bc*sc*i*
alias:          pci:v00008086d000008AFsv*sd00001015bc*sc*i*
alias:          pci:v00008086d000008AEsv*sd00001007bc*sc*i*
alias:          pci:v00008086d000008AEsv*sd00001005bc*sc*i*
alias:          pci:v00008086d00000084sv*sd00001316bc*sc*i*
alias:          pci:v00008086d00000084sv*sd00001216bc*sc*i*
alias:          pci:v00008086d00000083sv*sd00001326bc*sc*i*
alias:          pci:v00008086d00000083sv*sd00001226bc*sc*i*
alias:          pci:v00008086d00000083sv*sd00001306bc*sc*i*
alias:          pci:v00008086d00000083sv*sd00001206bc*sc*i*
alias:          pci:v00008086d00000084sv*sd00001315bc*sc*i*
alias:          pci:v00008086d00000084sv*sd00001215bc*sc*i*
alias:          pci:v00008086d00000083sv*sd00001325bc*sc*i*
alias:          pci:v00008086d00000083sv*sd00001225bc*sc*i*
alias:          pci:v00008086d00000083sv*sd00001305bc*sc*i*
alias:          pci:v00008086d00000083sv*sd00001205bc*sc*i*
alias:          pci:v00008086d00000886sv*sd00001317bc*sc*i*
alias:          pci:v00008086d00000886sv*sd00001315bc*sc*i*
alias:          pci:v00008086d00000885sv*sd00001327bc*sc*i*
alias:          pci:v00008086d00000885sv*sd00001325bc*sc*i*
alias:          pci:v00008086d00000885sv*sd00001307bc*sc*i*
alias:          pci:v00008086d00000885sv*sd00001305bc*sc*i*
alias:          pci:v00008086d00000089sv*sd00001316bc*sc*i*
alias:          pci:v00008086d00000089sv*sd00001311bc*sc*i*
alias:          pci:v00008086d00000087sv*sd00001326bc*sc*i*
alias:          pci:v00008086d00000087sv*sd00001321bc*sc*i*
alias:          pci:v00008086d00000087sv*sd00001306bc*sc*i*
alias:          pci:v00008086d00000087sv*sd00001301bc*sc*i*
alias:          pci:v00008086d00000091sv*sd00005226bc*sc*i*
alias:          pci:v00008086d00000091sv*sd00005225bc*sc*i*
alias:          pci:v00008086d00000091sv*sd00005221bc*sc*i*
alias:          pci:v00008086d00000091sv*sd00005207bc*sc*i*
alias:          pci:v00008086d00000091sv*sd00005206bc*sc*i*
alias:          pci:v00008086d00000091sv*sd00005205bc*sc*i*
alias:          pci:v00008086d00000091sv*sd00005201bc*sc*i*
alias:          pci:v00008086d00000090sv*sd00005216bc*sc*i*
alias:          pci:v00008086d00000090sv*sd00005215bc*sc*i*
alias:          pci:v00008086d00000090sv*sd00005211bc*sc*i*
alias:          pci:v00008086d0000008Bsv*sd00005317bc*sc*i*
alias:          pci:v00008086d0000008Bsv*sd00005315bc*sc*i*
alias:          pci:v00008086d0000008Asv*sd00005327bc*sc*i*
alias:          pci:v00008086d0000008Asv*sd00005325bc*sc*i*
alias:          pci:v00008086d0000008Asv*sd00005307bc*sc*i*
alias:          pci:v00008086d0000008Asv*sd00005305bc*sc*i*
alias:          pci:v00008086d00000082sv*sd00001305bc*sc*i*
alias:          pci:v00008086d00000082sv*sd00001304bc*sc*i*
alias:          pci:v00008086d00000082sv*sd00004820bc*sc*i*
alias:          pci:v00008086d00000085sv*sd0000C228bc*sc*i*
alias:          pci:v00008086d00000085sv*sd0000C220bc*sc*i*
alias:          pci:v00008086d00000082sv*sd0000C020bc*sc*i*
alias:          pci:v00008086d00000085sv*sd00001316bc*sc*i*
alias:          pci:v00008086d00000085sv*sd00001318bc*sc*i*
alias:          pci:v00008086d00000085sv*sd00001311bc*sc*i*
alias:          pci:v00008086d00000082sv*sd00001328bc*sc*i*
alias:          pci:v00008086d00000082sv*sd00001326bc*sc*i*
alias:          pci:v00008086d00000082sv*sd00001321bc*sc*i*
alias:          pci:v00008086d00000082sv*sd00001308bc*sc*i*
alias:          pci:v00008086d00000082sv*sd00001307bc*sc*i*
alias:          pci:v00008086d00000082sv*sd00001306bc*sc*i*
alias:          pci:v00008086d00000082sv*sd00001301bc*sc*i*
alias:          pci:v00008086d00004239sv*sd00001316bc*sc*i*
alias:          pci:v00008086d00004239sv*sd00001311bc*sc*i*
alias:          pci:v00008086d00004238sv*sd00001118bc*sc*i*
alias:          pci:v00008086d00004238sv*sd00001111bc*sc*i*
alias:          pci:v00008086d0000422Csv*sd00001326bc*sc*i*
alias:          pci:v00008086d0000422Csv*sd00001321bc*sc*i*
alias:          pci:v00008086d0000422Csv*sd00001307bc*sc*i*
alias:          pci:v00008086d0000422Csv*sd00001306bc*sc*i*
alias:          pci:v00008086d0000422Csv*sd00001301bc*sc*i*
alias:          pci:v00008086d0000422Bsv*sd00001128bc*sc*i*
alias:          pci:v00008086d0000422Bsv*sd00001121bc*sc*i*
alias:          pci:v00008086d0000422Bsv*sd00001108bc*sc*i*
alias:          pci:v00008086d0000422Bsv*sd00001101bc*sc*i*
alias:          pci:v00008086d0000423Dsv*sd00001316bc*sc*i*
alias:          pci:v00008086d0000423Dsv*sd00001216bc*sc*i*
alias:          pci:v00008086d0000423Dsv*sd00001311bc*sc*i*
alias:          pci:v00008086d0000423Dsv*sd00001211bc*sc*i*
alias:          pci:v00008086d0000423Csv*sd00001326bc*sc*i*
alias:          pci:v00008086d0000423Csv*sd00001321bc*sc*i*
alias:          pci:v00008086d0000423Csv*sd00001221bc*sc*i*
alias:          pci:v00008086d0000423Csv*sd00001306bc*sc*i*
alias:          pci:v00008086d0000423Csv*sd00001206bc*sc*i*
alias:          pci:v00008086d0000423Csv*sd00001301bc*sc*i*
alias:          pci:v00008086d0000423Csv*sd00001201bc*sc*i*
alias:          pci:v00008086d0000423Bsv*sd00001011bc*sc*i*
alias:          pci:v00008086d0000423Asv*sd00001021bc*sc*i*
alias:          pci:v00008086d0000423Asv*sd00001001bc*sc*i*
alias:          pci:v00008086d00004236sv*sd00001114bc*sc*i*
alias:          pci:v00008086d00004236sv*sd00001014bc*sc*i*
alias:          pci:v00008086d00004236sv*sd00001111bc*sc*i*
alias:          pci:v00008086d00004236sv*sd00001011bc*sc*i*
alias:          pci:v00008086d00004235sv*sd00001104bc*sc*i*
alias:          pci:v00008086d00004235sv*sd00001004bc*sc*i*
alias:          pci:v00008086d00004235sv*sd00001101bc*sc*i*
alias:          pci:v00008086d00004235sv*sd00001001bc*sc*i*
alias:          pci:v00008086d00004235sv*sd00001124bc*sc*i*
alias:          pci:v00008086d00004235sv*sd00001024bc*sc*i*
alias:          pci:v00008086d00004235sv*sd00001121bc*sc*i*
alias:          pci:v00008086d00004235sv*sd00001021bc*sc*i*
alias:          pci:v00008086d00004237sv*sd00001316bc*sc*i*
alias:          pci:v00008086d00004237sv*sd00001216bc*sc*i*
alias:          pci:v00008086d00004237sv*sd00001315bc*sc*i*
alias:          pci:v00008086d00004237sv*sd00001215bc*sc*i*
alias:          pci:v00008086d00004237sv*sd00001314bc*sc*i*
alias:          pci:v00008086d00004237sv*sd00001214bc*sc*i*
alias:          pci:v00008086d00004237sv*sd00001311bc*sc*i*
alias:          pci:v00008086d00004237sv*sd00001211bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001326bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001226bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001325bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001225bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001324bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001224bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001321bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001221bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001306bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001206bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001305bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001205bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001304bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001204bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001301bc*sc*i*
alias:          pci:v00008086d00004232sv*sd00001201bc*sc*i*
depends:        cfg80211
intree:         Y
vermagic:       3.13.0-37-generic SMP mod_unload modversions
signer:         Magrathea: Glacier signing key
sig_key:        2C:B1:13:3B:35:F9:5A:9E:24:DE:AB:EE:B1:2B:A4:49:BC:BA:BB:C9
sig_hashalgo:   sha512
parm:           swcrypto:using crypto in software (default 0 [hardware]) (int)
parm:           11n_disable:disable 11n functionality, bitmap: 1: full, 2: disable agg TX, 4: disable agg RX, 8 enable agg TX (uint)
parm:           amsdu_size_8K:enable 8K amsdu size (default 0) (int)
parm:           fw_restart:restart firmware in case of error (default true) (bool)
parm:           antenna_coupling:specify antenna coupling in dB (defualt: 0 dB) (int)
parm:           wd_disable:Disable stuck queue watchdog timer 0=system default, 1=disable, 2=enable (default: 0) (int)
parm:           nvm_file:NVM file name (charp)
parm:           bt_coex_active:enable wifi/bt co-exist (default: enable) (bool)
parm:           led_mode:0=system default, 1=On(RF On)/Off(RF Off), 2=blinking, 3=Off (default: 0) (int)
parm:           power_save:enable WiFi power management (default: disable) (bool)
parm:           power_level:default power save level (range from 1 - 5, default: 1) (int)

modinfo iwlmvm

Code: [Select]
retired1@Bodacious ~ $ modinfo iwlmvm
filename:       /lib/modules/3.13.0-37-generic/kernel/drivers/net/wireless/iwlwifi/mvm/iwlmvm.ko
license:        GPL
author:         Copyright(c) 2003-2013 Intel Corporation <ilw@linux.intel.com>
version:        in-tree:
description:    The new Intel(R) wireless AGN driver for Linux
srcversion:     D8BB21196A865641A4A81D0
depends:        iwlwifi,mac80211,cfg80211
intree:         Y
vermagic:       3.13.0-37-generic SMP mod_unload modversions
signer:         Magrathea: Glacier signing key
sig_key:        2C:B1:13:3B:35:F9:5A:9E:24:DE:AB:EE:B1:2B:A4:49:BC:BA:BB:C9
sig_hashalgo:   sha512
parm:           init_dbg:set to true to debug an ASSERT in INIT fw (default: false (bool)
parm:           power_scheme:power management scheme: 1-active, 2-balanced, 3-low power, default: 2 (int)

Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on May 01, 2015, 02:14:15 pm
All fixed. New kernels compiled for the next RC contain iwlmvm which is needed for the newer Intel cards. I'm happy again. :D
Title: Re: VL7.1 STD feedback and suggestions.
Post by: vector on May 02, 2015, 03:03:54 am
yahoo.......................................... :)
Title: Re: VL7.1 STD feedback and suggestions.
Post by: vector on May 02, 2015, 03:14:05 am
Hey guys what do you think we ready for final on this puppy yet.............we have been on 7.1 rc for a very long time opinions appreciated

oh by the way Im back.............had to many problems to explain but all is well now..........so we go to the next step and the next 10 years.........................Cheers!!

Vec
Title: Re: VL7.1 STD feedback and suggestions.
Post by: nightflier on May 02, 2015, 10:24:36 am
A warm welcome back!   ;D
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on May 02, 2015, 11:08:20 am
 :)
Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on May 02, 2015, 11:39:47 am
Hey guys what do you think we ready for final on this puppy yet.............we have been on 7.1 rc for a very long time opinions appreciated

oh by the way Im back.............had to many problems to explain but all is well now..........so we go to the next step and the next 10 years.........................Cheers!!

Vec

Last week was a very good week and I think we got most of nasty stuff ironed out. I think one more RC for testing / verifying we got 'em all and we should be good to go.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: vector on May 02, 2015, 11:50:04 pm
OK great lets get that RC out so we can close this chapter................nice to be back!!!


Cheers,
Vec
Title: Re: VL7.1 STD feedback and suggestions.
Post by: |nic| on May 06, 2015, 10:18:31 am
Hi guys,

Where can I find the latest RC to test?

cheers.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on May 06, 2015, 10:40:31 am
http://vlcore.vectorlinux.com/pkg/untested/veclinux-7.1/iso

There will be an RC4.5 built a bit later today... waiting on a build job to finish now, but should be up there in a couple of hours from now.  Please test and report any issues.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: nightflier on May 06, 2015, 06:45:57 pm
STD RC4.5 32-bit:
Installed without problems from USB stick created with Unetbootin.
Wi-Fi works fine.

Top panel has a folder for root, which is not accessible due to permissions.
Desktop launcher for Tutorials: I'm sure the new owners of opensourcebistro.com appreciate the free advertising. ;)
Menu: Qt4 Config has no icon.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: sledgehammer on May 06, 2015, 11:33:11 pm
RC4.5-64 installed fine on Dell 620 laptop.  Wouldn't recognize zonet usb wireless care on first boot, but did so fine on second boot.  Root worked fine from thunar.  Firefox works fine. Will try to play with it as time permits.

IMPORTANT.  If I recall correctly, automatic install does not give the installer the option to tell gparted not to format the home partition. If so, on Install, where the screen asks for automatic or advanced install, the screen needs to state that fully automatic install will erase all data, including data in the home directory.    Or, perhaps, say simply that if you want to save data, you should use automatic install. 

John
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on May 07, 2015, 08:11:23 am
STD RC4.5 32-bit:
Installed without problems from USB stick created with Unetbootin.
Wi-Fi works fine.

Top panel has a folder for root, which is not accessible due to permissions.
Desktop launcher for Tutorials: I'm sure the new owners of opensourcebistro.com appreciate the free advertising. ;)
Menu: Qt4 Config has no icon.
These issues will be resolved on the next ISO Build.

Thanks for pointing them out
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on May 07, 2015, 08:28:47 am

IMPORTANT.  If I recall correctly, automatic install does not give the installer the option to tell gparted not to format the home partition. If so, on Install, where the screen asks for automatic or advanced install, the screen needs to state that fully automatic install will erase all data, including data in the home directory.    Or, perhaps, say simply that if you want to save data, you should use automatic install. 

John

This warning already exists before the user does anything destructive.  It shows up on the next step where it asks where to install to.

The actual wording says
Code: [Select]
Select a disk for Vector.  WARNING: All existing data in the disk you select will be overwritten
I think that's obvious enough.  The only thing I would change is the word overwritten to "destroyed"
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on May 07, 2015, 10:39:09 am
rc-4.5 32 bit

session menu may be worth a look
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 07, 2015, 11:05:12 am
Glad finally got  tap to click disabled on install and yes it says on automatic will use whole sda. Installs always seem to go just fine in latest releases.dd works just fine for usb media flash drive or sd card. Looks very good so far and root folder in panel 2,why? Oh by the way using 32 bit.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 08, 2015, 12:47:25 pm
STD -RC4,5,2 already?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: roarde on May 08, 2015, 02:40:04 pm
STD -RC4,5,2 already?
Yes.

I've kinda been peeking over the dev's shoulders a bit. It's down to very minor changes now. There may be a short, quick series of "patchlevel" ISO's. Test all you can, please; but it's understood that there are very few who can test a lot of them. Thanks for the testing you find time, space and equipment for. :)

The theme (appearance) of the GUI installer in 4.5.2 has been discussed and will be changed. It's easily reverted, but there are a couple of other ready-to-go themes that may be tried also.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 08, 2015, 03:46:31 pm
Just installed  STD-4.5.2 thought boot screen better than drawing that never completed, install was brighter,still automatic seems misleading- "will take it from there" or something like that,first line should be WARNING THIS WILL FORMAT COMPLETE DISC!! Like tap to click disabled.QT now has icon in menu list as does set Date and Time.
Actually liked install screen bright and clear.   Will give more later.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 08, 2015, 03:53:33 pm
@roarde   Are we still using  untested for packages? Forgot to verify.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: roarde on May 08, 2015, 03:59:38 pm
@roarde   Are we still using  untested for packages? Forgot to verify.
Yes . And thanks for prompting to post a reminder.

Only untested, turn the others off. If there's something that doesn't install at all, or doesn't work correctly when installed from there, please holler: It needs to be fixed.

There was some discussion ealier about shipping test ISO's with slapt-getrc already edited. But at this late date, keeping the changes needed to produce final to the minimum outweighs that.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 08, 2015, 04:24:28 pm
Development team must be very busy, also noticed "root folder " gone from panel 2. As they say endeavor to persevere.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on May 08, 2015, 09:13:32 pm
Toshiba Satellite A-100, 2.5 gig ram, 80 gig with swap

VL-7.1-STD-RC4.5.2 32 bit

install via dvd, advanced, existing..default lilo to /sda..with xfce

noted: installer theme change..but installed without issue

reboot gets splash rather than previous glimps of.

session menu still includes fluxbox, but is not installed or gives time out..if not to be included should be a download with or available in repository..MO

clawsmail still seems to have an issue but not selecting preferances for current account and using edit preferances worked when it was posted about a ways back.

music cds do not play without clipping or excessive buffering if cache increased still, but grip can rip to mp3 for playback...read somewhere that mplayer compiled with libcdparanoia rather than libcdio can cause this but no idea, just testing the players..smplayer is nice otherwise and played what was in my test pile.

evince document viewer does not open my sample .pdf or abiword printtofile .pdf but do open in browser..txt and.cbz comic did open in doc viewer....( adding: required libjpeg-turbo available in repository )

epub requires app will look in repo for calibre.

as already posted root folder removed and qt icon added

default apps are not set but prompted for when selecting test files.

Is the line across the panel a design preference? I do not mind the theme with that exception and posted a quick fix already.

mostly cosmetics I guess..I've already made to many suggestions in that regard so will leave you hard working lads to your buisness

looking good..cheers
Title: Re: VL7.1 STD feedback and suggestions.
Post by: |nic| on May 09, 2015, 07:21:06 am
tested VL7 STD RC 4.5.2 on my Dell Inspiron 6400 laptop

First chose advanced installation but the installer froze setting up passwords. Installation went fine with the standard method.
I'm sad there is no keyboard selection (even not in VASM)...This is quite important IMHO.

WIFI, sound,... were detected automatically. Good software selection.

good job!

cheers

Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 09, 2015, 10:53:37 am
STD-RC4.5.2 Gimp does not open .jpg had to revert back to previous version.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on May 09, 2015, 11:36:22 am
STD-RC4.5.2 Gimp does not open .jpg had to revert back to previous version.

Removing GIMP and then reinstalling from the repo fixes that issue.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on May 09, 2015, 11:41:00 am
libjpeg-turbo from the repository will be added when you reinstall gimp this will also allow evince doc viewer to load pdf files with images
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 09, 2015, 12:22:22 pm
Gimp is now happy!
Title: Re: VL7.1 STD feedback and suggestions.
Post by: sledgehammer on May 10, 2015, 10:03:28 am
I loaded VL64-7.1-STD-RC4.5.2.iso (unetbootin, lilo) this morning and it works great.  This time I noticed the warning re deleting all data when using the automatic option..  Suggest you color that warning red and add a couple of exclamation marks. 

Gimp loaded fine but I don't know how to use it so can't say if it works right.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on May 10, 2015, 12:44:10 pm
(32bit std 4.5.2) Galculator has no icon when minimized  thus if one chooses to uncheck show button labels there is no window  button icon.


@ sledgehammer....if you are curious you can right click Rumpole (your avatar) to the left and choose save image as, then save to your home directory or where you like then open the avatar_1944.jpg in gimp..if it does not open..add libjpeg-turbo from the testing repository which allows gimp to open the image. or reinstall gimp which will include it.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 10, 2015, 03:59:29 pm
@sledghammer gimp works after loading libjpeg-turbo, would appear dependency checking not quite there yet. It would seem stating automatic will use whole disk would be adequate,but your idea of big bold red warning is probably better. I do like this RC4.5.2
Title: Re: VL7.1 STD feedback and suggestions.
Post by: sledgehammer on May 10, 2015, 04:48:42 pm
I got Gimp working.  First added the testing repository and then the suggested program.  Gimp did not work until I did that.  But, as you can see, it works now.

Quote
Galculator has no icon when minimized
  I'm pretty sure this is SOP for Galculator. It shows in the bottom panel when minimized, without icon.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on May 10, 2015, 05:10:23 pm
32b-4.5.2

grip rips fine but does not play the cd (counts but no sound) nor does smplayer without clipping...is it just me? other os on the same laptop will play cd so not the drive...curious

@sledgehammer.....thanks (galc)...lol..looks like rumpole got a dye job
Title: Re: VL7.1 STD feedback and suggestions.
Post by: sledgehammer on May 10, 2015, 06:14:52 pm
Smplayer works, but it skips on my Dell Lattitude 620 laptop.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on May 10, 2015, 07:17:39 pm
Thanks..yes smplayer works fine on my toshiba satellite a-100 as well except for commercial music cd..I can not seem to play them, skips every second... and grip has no sound..not that I really need to, just a curiosity that it is not possible. at least I am not the only one...Thanks
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 11, 2015, 07:31:07 am
STD.4.5.2 Abiword,System Date and Time no icon in menu list.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on May 11, 2015, 07:37:57 am
STD.4.5.2 Abiword,System Date and Time no icon in menu list.

They show icons on my install.

http://imgur.com/CsSS2ZH,gXxtMOX

Can anyone else confirm this?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 11, 2015, 08:42:33 am
Have another version installed STD 4.5 from 05/06/2015 on different computer and no menu icon for Abiword or System Date and Time. Perhaps it is my install don't know.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: sledgehammer on May 11, 2015, 12:48:10 pm
Quote
Can anyone else confirm this?

Show on mine too.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 11, 2015, 02:15:21 pm
Development team change icon theme Abiword and Date and Time  appear but QtConfig goes away. All depends on icon theme other icons disappear with different settings. I am using xfce
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 11, 2015, 02:33:51 pm
Development team using Application Finder all icons are there,even when not showing in menu list.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on May 12, 2015, 04:09:53 am
It would help if you provided details. What did you do, what did you choose, and what was the result. Saying it's broke doesn't help much.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 12, 2015, 06:19:26 am
@retired1af did nothing special, installed chose xfce all ok noticed icons in menu list missing,Tango icon theme causes different icons not to be there then Faenza and other themes same result ,did not add or remove anything for themes. Try  it ,select different icon theme and look at menu list. Don't know what else to provide,install look missing.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on May 12, 2015, 06:33:38 am
It's possible you have a pooched install as I do not have that issue. I've selected several different themes this morning and all are fine.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 12, 2015, 06:47:34 am
@retired1af  I have posted I get same results on earlier version as I said perhaps my install,but different computers and different releases 5.4 and 5.4.2. From what you say it would appear to be something done unknowingly will try again. Thanks.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 12, 2015, 07:33:00 am
Decided to wait for next RC.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on May 13, 2015, 01:19:55 am
I really like the default faenza  icon theme and found nothing there on a fresh install of 4.5.2 32

however, tango, HighContrast and gnome do have missing icons on both wisker and app menus for xfce

like fluxbox from the session menu I simply removed them from the list

Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on May 13, 2015, 03:42:12 am
I really like the default faenza  icon theme and found nothing there on a fresh install of 4.5.2 32

however, tango, HighContrast and gnome do have missing icons on both wisker and app menus for xfce


THAT'S what we're looking for. We'll check that today before pushing a new RC.

We also fixed the CD playing issue yesterday. :)
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 13, 2015, 06:40:29 am
@retired1af  I have posted I get same results on earlier version as I said perhaps my install,but different computers and different releases 5.4 and 5.4.2. From what you say it would appear to be something done unknowingly will try again. Thanks.
I screwed up versions, should be 4.5 and 4.5.2 .
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 13, 2015, 12:06:00 pm
Started to install STD-RC4.6 selected advanced load partitioning manager all disks on sdb I only have one drive sda. Sorry Development team.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on May 13, 2015, 02:45:34 pm
Started to install STD-RC4.6 selected advanced load partitioning manager all disks on sdb I only have one drive sda. Sorry Development team.

That doesn't tell us anything.

A proper bug report would show what your system has as far as hardware, how you were installing (CD, USB, etc.) the exact steps you took leading up to the error, and the exact error you received including screen shots if appropriate. Developers are not mind readers, nor do they have magical access to your machine that would tell them what was going on.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 13, 2015, 05:51:29 pm
@retired1af Seemed pretty straight forward to me,one disk drive SDA not SDB. Any way after some thought I figured it was OK all partitions were correct just labeled SDB,so I installed from SD card,SD card reader was identified as SDA installed fine. Rebooted new RC6 checked menu list all icons present and accounted for,set up my appearance choice xfce curve icon choice Tango checked menu list Abiword,System Date and Time missing tried other choices           Gnome Abiword,System Date and Time,Mail Reader missing             High Contrast Abiword,System Date and Time missing. Checked disk with Gparted all partitions are labeled SDB.Rebooted stopped Grub with E for edit to check labels also labeled SDB, Had RC5 on this machine and it is still there as SDA partition, I just plugged in SD card identified as SDA normally it is SDC plugged in Flash Drive  identified as SDC and it is usually SDB. Computer old Gateway circa 2000 or so also does same on another computer about same age. All that use to be SDA is now SDB bad device table. If you need more information let me know.       
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on May 14, 2015, 02:02:10 am
toshiba satellite A-100..RC 4.6 std 32bit

thanks, smplayer /open/disc/audio cd now works

Perhaps known.. requires openal-soft 1.14 from repository,
reinstall lists only smtube and smplayer.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: nightflier on May 14, 2015, 04:06:54 am
@crum:  You have discovered a bug affecting installs using USB drive, thank you for reporting it. It will need to be fixed.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on May 14, 2015, 05:26:58 am
toshiba satellite A-100..RC 4.6 std 32bit

thanks, smplayer /open/disc/audio cd now works

Perhaps known.. requires openal-soft 1.14 from repository
...

Yes, that will be fixed the next time the ISO builds.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 14, 2015, 08:06:40 am
Team, as far as icon problem even when no icon in menu list ,looking at application finder all icons are present no matter what theme is selected.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on May 14, 2015, 01:49:30 pm
Those of you with the USB device problems... Please test out RC4.6.1 and report back.  Another thing to test is MPlayer on this one... make sure it works out of the box, it should no longer require the openal package.

For those of you with the icon problem, please disable all default repositories in slapt-getrc, and add unstested... then run 'slapt-get -u; slapt-get --upgrade'.  This should upgrade your whiskermenu to 1.5.0 (now building.. (after the ISO was built)).  See if that does anything.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 14, 2015, 05:19:22 pm
Installed STD-RC4.6.1 from SD card advanced partition manager identified all storage correctly installation fine. Checked icons all there. Set up appearance icon Tango System Date and Time missing           Gnome Mail Reader  System Date and Time missing     High Contrast System Date and Time missing. Disabled all repositories except vlcore untested have whiskermenu 1.5.0 installed. Did not try Mplayer.    Have to commend the Team very fast response and good outcome, hang in.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on May 14, 2015, 06:41:59 pm
RC 4.6.1 std 32 on toshiba sat a100

smplayer appears to work ok out of box

abiword icon fixed for xfce menus


longer story

..played a full commercial cd plus random tracks on two others

also played commercial dvds plus a vhs converted to dvd

few each sample files in flv,mp4,mp3,wav,ogv,wma,mpg,avi

no issues so far except application defaults where not set but are now pretty much after test.


Icons  faenza-cupertino on wisker menu appears fine, and my fav

 however when the std application menu is added to the panel, at the moment,

 it is missing the following icons

settings/ firewall conf, java, privilage granting

accessories/ gkrellm, tuxcards

internet/ claws mail, gftp

system/ firewall config, gslapt package manager

note: the abiword icon is fixed for tango, high contrast and gnome

however: add system date and time to above list for tango and high contrast and additionally mail reader for gnome


missing wisker menu icons can be confirmed as already posted. sys D&T for tango and high conrast in addition to mail reader for gnome

I do not have the solution but thought it may help to clarify the xfce wisker and std menu icon state

if not an issue for others this is the case on this laptop for previous and current fresh install, I,m in no hurry just playing

Thanks very much for all the work, this is a great version of slackware and highly underrated
Title: Re: VL7.1 STD feedback and suggestions.
Post by: sledgehammer on May 14, 2015, 07:59:33 pm
loaded 6.1 (automatic-usb-unetbootin) and it loaded fine. Playing CD now with smplayer. No skipping.  Firefox also.  Read the newspaper.  Configuring separate monitor worked well.

If someone asks and tells me specifically what to try, I will do so and report.

John
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 15, 2015, 07:53:04 am
Does anyone use install from .iso? I always use dd.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on May 15, 2015, 08:13:04 am
I have used it several times.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on May 15, 2015, 09:29:28 am
Burning to the CD and installing from it is the only way I test new ISOs.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 15, 2015, 09:42:01 am
@MOE-lnx Have tried a few times and I must not set up correctly does not work .
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on May 15, 2015, 10:55:55 am
There is nothing to setup... you just place the ISO in the top dir of any partition.  You need an existing burned CD or ISO to boot from... then, when the installer comes up, it will see your ISO and list it as a install source.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: wigums on May 15, 2015, 07:13:20 pm
moo
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on May 15, 2015, 08:05:36 pm
buc buc
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 16, 2015, 06:05:09 am
There is nothing to setup... you just place the ISO in the top dir of any partition.  You need an existing burned CD or ISO to boot from... then, when the installer comes up, it will see your ISO and list it as a install source.

Perhaps you could elaborate in How-TO.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on May 16, 2015, 06:20:00 am
Burn the ISO to a disc and boot from the disc. Or, if you already have a disc with an older ISO and installer on it, copy the newest ISO to the root directory of any partition OTHER than the one you're going to install to and run the installer from the other disc. It will detect the new ISO when the installer starts.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: sledgehammer on May 16, 2015, 12:40:18 pm
Crum,

Its been so long since I installed from a CD, I have forgotten how to do it.  But I used to do it all the time, so if you report on exactly what you do, and I can find a blank CD, I will try it and see if I can duplicate the problem. I don't recall if being difficult.  I just used kbd or kb3 or something like that, and told it to install the downloaded iso to a blank cd.  When finished, the cd would pop out and I would put it into the new machine and follow the command line install instructions.  I always used lilo and never dual booted.  Only time I ever had problems, if I recall, was when I tried to install the iso onto a cd that was not completely blank.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on May 16, 2015, 09:16:03 pm
std32 rc4.6.1 toshiba sat a100

screensaver pops on while watching movie in smplayer

smplayer/options/preferences/video/ disable screensaver is checked

gnome-mplayer does not have this option that I can find

is it just me?

Edit: adding the following line to /.mplayer/config appears to solve

 heartbeat-cmd="xscreensaver-command -deactivate >&- 2>&- &"
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on May 17, 2015, 05:46:59 pm
STD32-RC4.6.1 on Toshiba sat A-100

I notice at the end of the splash screen and prior to the login, there is a screen of text then a blank screen with working symbol (watch) then login.

is it possible to cover this or not show it?

 not wanting to nit pick as some say I just think it would look nicer if not seen. or am I the only one seeing this.

Title: Re: VL7.1 STD feedback and suggestions.
Post by: roarde on May 17, 2015, 07:01:57 pm
There was a change to vasm.sh that prevents this. The last package installed, "vlconfig2", puts in setup scripts that run at next boot. Those clobber that change.

I may be assuming, though. Try a recent Light. If it happens there, then I'm thinking of a different problem.

Better idea: grab http://sprunge.us/ZHHO (http://sprunge.us/ZHHO) before it expires and put it at /etc/profile.d/vasm.sh and see if that's what you're talking about.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on May 17, 2015, 11:23:32 pm
yes it looks rather like a root terminal and in a more perfect boot would not be seen..not sure why I was compelled to post about it.

will have a look at light

edit..light has just one line..like..gdm..no security token could be found

I clicked the tutorial desktop icon but the channel no longer exists
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on May 22, 2015, 03:24:30 pm
Put RC4.6.1 on cd and put it in my DEL.  After the comment that the screen may flash, I get a pop-up saying video input out of range.

This is on a Gateway flat screen through an IOGear splitter.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: nightflier on May 22, 2015, 06:01:30 pm
Don't know what video settings the installer use, but I've seen several monitors complain about it. Usually I can still continue, though.

Can you type "install" and use the text installer?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on May 23, 2015, 08:50:30 am
Thanks, nightflier.  It wasn't until you mentioned it that I rembered I had gone through that option.  It is now processing the requested operations. 

Mouse would not work - had to use tab key.

Oh! this is 32 bit.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on May 23, 2015, 10:10:28 am
Lilo picked up two other OSs but slipped by too fast to see what they were.  I like that all of the hd partitions are on the screen and in Thunar.  I'll see if I can rename them -  opps!  They're not in fstab!  Nor on either Desktop!

Menu/Web browser started Firefox which opened its start page and another tab was loading - don't know where, canceled and closed.

Started gslapt, removed all packages except testing[qoute]Source failed
ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-7.1/testing/
This package source failed or is not available...[/quote]Will try later.

It only took 3 tries but I finally got my HP Officejet to print.  It helps if I would read!

It's about an hour later. Gslapt still fails to load.  It may be a week or more before I can try again.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on May 23, 2015, 10:41:47 am
For 32 bit, use this as your untested:  http://vlcore.vectorlinux.com/pkg/untested/veclinux-7.1/x86/
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on May 23, 2015, 02:23:23 pm
Thanks fellow veteran.  Still get Source failed message.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on May 23, 2015, 02:56:46 pm
That's strange. I just tried it and it flew right on through with no errors. I'm on 64-bit, though. Someone else who's using the 32-bit RC needs to test as well. If push comes to shove, I'll install on another partition and see what happens.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 23, 2015, 04:09:05 pm
@StrayBit I am using STD RC4.6.1 and the link indicated 32 bit OK.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on May 23, 2015, 07:34:44 pm
Assume you copy pasted the link to gslapt/ edit/preferences/sources/ add and then updated...this worked for me recently..but did not try this particular link today..although it is a valid link

Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on May 24, 2015, 07:42:10 am
I may have mistyped it.  It will be a few days before I can try again.  Thanks for your replys.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on May 24, 2015, 07:53:20 am
Copy/Paste works perfectly for that. Just sayin'.....     ;D
Title: Re: VL7.1 STD feedback and suggestions.
Post by: crum on May 25, 2015, 12:12:11 pm
I normally turn laptop off,it is a old Gateway with Realtek 8187se nic uses driver rtl818x. Today Lid got closed on Laptop,went into suspend mode opened Lid gave password all good except wifi connection did not start icon normally shows activity when looking for router no activity. Clicked on icon showed networks selected network asked for password did password connect no response.I tried this a few times sometimes notification network disconnected other times no notification. Network is set to start automatically. I tried nmcli seems useless ifupdown same. Seems as if NetworkManager goes to sleep not suspend and does not want to wake up.


Would prefer shut down option in addition to suspend in power management.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on May 25, 2015, 03:37:39 pm
I only missed two directories when I typed (reading from SeaMonkey on Windows).  Installed 16 items including seamonkey (using it now), monodevelop (can't open from a SMB directory - trying copy and paste, welcome.cs:
Quote
System.IO.IOException: Error while loading style :Default ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.Drawing.KnownColors ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.Drawing.GDIPlus ---> System.DllNotFoundException: /usr/lib/libgdiplus.so
  at (wrapper managed-to-native) System.Drawing.GDIPlus:GdiplusStartup (ulong&,System.Drawing.GdiplusStartupInput&,System.Drawing.GdiplusStartupOutput&)
  at System.Drawing.GDIPlus..cctor () [0x000cc] in /tmp/builds/mono/tmp/mono-3.0.7/mcs/class/System.Drawing/System.Drawing/gdipFunctions.cs:127
  --- End of inner exception stack trace ---
  at System.Drawing.KnownColors..cctor () [0x0001a] in /tmp/builds/mono/tmp/mono-3.0.7/mcs/class/System.Drawing/System.Drawing/KnownColors.cs:225
  --- End of inner exception stack trace ---
  at System.Drawing.ColorConverter.StaticConvertFromString (ITypeDescriptorContext context, System.String s, System.Globalization.CultureInfo culture) [0x00077] in /tmp/builds/mono/tmp/mono-3.0.7/mcs/class/System.Drawing/System.Drawing/ColorConverter.cs:84
  at System.Drawing.ColorConverter.ConvertFrom (ITypeDescriptorContext context, System.Globalization.CultureInfo culture, System.Object value) [0x00017] in /tmp/builds/mono/tmp/mono-3.0.7/mcs/class/System.Drawing/System.Drawing/ColorConverter.cs:171
  at System.ComponentModel.TypeConverter.ConvertFrom (System.Object o) [0x00000] in /tmp/builds/mono/tmp/mono-3.0.7/mcs/class/System/System.ComponentModel/TypeConverter.cs:66
  at System.ComponentModel.TypeConverter.ConvertFromString (System.String text) [0x00000] in /tmp/builds/mono/tmp/mono-3.0.7/mcs/class/System/System.ComponentModel/TypeConverter.cs:90
  at System.Drawing.ColorTranslator.FromHtml (System.String htmlColor) [0x0015e] in /tmp/builds/mono/tmp/mono-3.0.7/mcs/class/System.Drawing/System.Drawing/ColorTranslator.cs:75
  at Mono.TextEditor.Highlighting.ColorScheme.GetColorFromString (System.String colorString) [0x001c0] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/core/Mono.Texteditor/Mono.TextEditor.Highlighting/ColorScheme.cs:578
  at Mono.TextEditor.Highlighting.ColorScheme.SetChunkStyle (System.String name, System.String weight, System.String foreColor, System.String backColor) [0x00038] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/core/Mono.Texteditor/Mono.TextEditor.Highlighting/ColorScheme.cs:514
  at Mono.TextEditor.Highlighting.ColorScheme.ReadStyleTree (System.Xml.XmlReader reader, Mono.TextEditor.Highlighting.ColorScheme result, System.String curName, System.String curWeight, System.String curColor, System.String curBgColor) [0x000b8] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/core/Mono.Texteditor/Mono.TextEditor.Highlighting/ColorScheme.cs:599
  at Mono.TextEditor.Highlighting.ColorScheme+<LoadFrom>c__AnonStorey32.<>m__43 () [0x000b0] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/core/Mono.Texteditor/Mono.TextEditor.Highlighting/ColorScheme.cs:625
  at Mono.TextEditor.Highlighting.XmlReadHelper+<ReadList>c__AnonStorey19.<>m__D (Mono.TextEditor.Highlighting.ReadCallbackData data) [0x00000] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/core/Mono.Texteditor/Mono.TextEditor.Highlighting/XmlReadHelper.cs:55
  at Mono.TextEditor.Highlighting.XmlReadHelper.ReadList (System.Xml.XmlReader reader, ICollection`1 endNodes, Mono.TextEditor.Highlighting.ReaderCallbackWithData callback) [0x0008b] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/core/Mono.Texteditor/Mono.TextEditor.Highlighting/XmlReadHelper.cs:91
  at Mono.TextEditor.Highlighting.XmlReadHelper.ReadList (System.Xml.XmlReader reader, ICollection`1 endNodes, Mono.TextEditor.Highlighting.ReaderCallback callback) [0x0000d] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/core/Mono.Texteditor/Mono.TextEditor.Highlighting/XmlReadHelper.cs:54
  at Mono.TextEditor.Highlighting.XmlReadHelper.ReadList (System.Xml.XmlReader reader, System.String endNode, Mono.TextEditor.Highlighting.ReaderCallback callback) [0x00000] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/core/Mono.Texteditor/Mono.TextEditor.Highlighting/XmlReadHelper.cs:50
  at Mono.TextEditor.Highlighting.ColorScheme.LoadFrom (System.Xml.XmlReader reader) [0x00018] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/core/Mono.Texteditor/Mono.TextEditor.Highlighting/ColorScheme.cs:615
  at Mono.TextEditor.Highlighting.SyntaxModeService.LoadStyle (System.String name) [0x0003c] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/core/Mono.Texteditor/Mono.TextEditor.Highlighting/SyntaxModeService.cs:111
  --- End of inner exception stack trace ---
  at Mono.TextEditor.Highlighting.SyntaxModeService.LoadStyle (System.String name) [0x00053] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/core/Mono.Texteditor/Mono.TextEditor.Highlighting/SyntaxModeService.cs:113
  at Mono.TextEditor.Highlighting.SyntaxModeService.GetColorStyle (System.String name) [0x0002c] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/core/Mono.Texteditor/Mono.TextEditor.Highlighting/SyntaxModeService.cs:83
  at Mono.TextEditor.TextEditorOptions.GetColorStyle () [0x00000] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/core/Mono.Texteditor/Mono.TextEditor/TextEditorOptions.cs:492
  at MonoDevelop.SourceEditor.StyledSourceEditorOptions.GetColorStyle () [0x00005] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/addins/MonoDevelop.SourceEditor2/MonoDevelop.SourceEditor/StyledSourceEditorOptions.cs:192
  at Mono.TextEditor.TextArea.OptionsChanged (System.Object sender, System.EventArgs args) [0x00044] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/core/Mono.Texteditor/Mono.TextEditor/Gui/TextArea.cs:685
  at Mono.TextEditor.TextArea.set_Options (ITextEditorOptions value) [0x00066] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/core/Mono.Texteditor/Mono.TextEditor/Gui/TextArea.cs:157
  at Mono.TextEditor.TextEditor.set_Options (ITextEditorOptions value) [0x00000] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/core/Mono.Texteditor/Mono.TextEditor/Gui/TextEditor.cs:414
  at MonoDevelop.SourceEditor.ExtensibleTextEditor..ctor (MonoDevelop.SourceEditor.SourceEditorView view) [0x00028] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/addins/MonoDevelop.SourceEditor2/MonoDevelop.SourceEditor/ExtensibleTextEditor.cs:75
  at MonoDevelop.SourceEditor.SourceEditorWidget..ctor (MonoDevelop.SourceEditor.SourceEditorView view) [0x00077] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/addins/MonoDevelop.SourceEditor2/MonoDevelop.SourceEditor/SourceEditorWidget.cs:284
  at MonoDevelop.SourceEditor.SourceEditorView..ctor () [0x000ca] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/addins/MonoDevelop.SourceEditor2/MonoDevelop.SourceEditor/SourceEditorView.cs:189
  at MonoDevelop.SourceEditor.SourceEditorDisplayBinding.CreateContent (FilePath fileName, System.String mimeType, MonoDevelop.Projects.Project ownerProject) [0x00000] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/addins/MonoDevelop.SourceEditor2/MonoDevelop.SourceEditor/SourceEditorDisplayBinding.cs:94
  at MonoDevelop.Ide.Gui.LoadFileWrapper.Invoke (System.String fileName) [0x00036] in /tmp/builds/monodevelop/tmp/monodevelop-4.0/src/core/MonoDevelop.Ide/MonoDevelop.Ide.Gui/Workbench.cs:1156
Tried another file and got same response.

I did miss wine but dl'd dosbox.  Will play with what I have and report.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on June 04, 2015, 08:55:24 am
Attempted to install RC4.6.3 32 bit to a USB stick.  Started about 4 PM, next morning was setting passwords.  Tried again and this time it was installing bootloader the next morning.  24 hours later, it was still installing bootloader!  Tried starting the installed os from the cd - couldn't sync 0,0 ... kernel panic.

Tried again with HP 620 laptop put nothing on the screen!

Will try 7.0 STD
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on June 19, 2015, 07:56:08 am
Installed VL 7.1 RC6.6 32 bit with text installer.  Sat for 12 hours on
Code: [Select]
Installing Bootloader(LILO). 
Started from CD but niether mouse nor keyboard worked at log in prompt.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on June 19, 2015, 07:59:57 am
Did you check the md5 on the ISO?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on June 19, 2015, 08:53:47 am
Reinstalled RC4.6.3 w/o issue.  Now that I have a working linux, I'll check that Moe.  Thanks
EDIT: First time I've seen that!  It is different!
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on June 19, 2015, 10:47:46 am
The md5sum.text I had checked did not compare with rc6 - obviously!  It is the correct for rc6.6.
Reinstalled - still no keyboard or mouse at login and it takes a hard power off to get out of it.  They work fine with RC6.3.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: retired1af on June 19, 2015, 11:02:42 am
Is this a bluetooth keyboard and mouse?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on June 19, 2015, 11:46:07 am
bt peripherals would not cause bootloader to hang for sure.  This (if indeed present) is something else
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on June 19, 2015, 03:14:07 pm
USB keyboard and mouse through an Iomega KVM switch (use same mouse, etc. with two computers).  As I mentioned, they work with RC 6.3 which I had installed again between the two installations of RC 6.6
Title: Re: VL7.1 STD feedback and suggestions.
Post by: nightflier on June 21, 2015, 02:09:22 pm
RC 4.6.6 32-bit, tested in virtualbox and on real hardware:
Google Chrome and Chromium browsers segfault.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on June 22, 2015, 06:01:40 pm
Is there a way to start my installation in text mode when using the installation CD?
Quote
linux root=/dev/sdb2 ro
Title: Re: VL7.1 STD feedback and suggestions.
Post by: nightflier on June 22, 2015, 06:22:03 pm
Try typing "install" and press "Enter".
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on June 23, 2015, 08:48:44 am
I've already typed "install" and run the installation - twice!  Both times, it would freeze at "Installing boot loader".  The MLB is hosed so that I have to insert the CD and type
Code: [Select]
linux root=/dev/sdb2 roand the system runs until it asks for user and password.  At this time, the keyboard and the mouse have no effect.  Most other times, if I touch the power button, the system will go through a normal shut down.  Now I have to hold the power button about four seconds until it shuts off power.
So I ask again, is it possible to enter the system on HD from CD in text (TUI) mode instead of GUI?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: nightflier on June 23, 2015, 11:04:17 am
Ah, boot installed system, not the installer. I misunderstood.

use "linux root=/dev/sdb2 ro 2"
Title: Re: VL7.1 STD feedback and suggestions.
Post by: roarde on June 24, 2015, 01:23:14 am
RC 4.6.6 32-bit, tested in virtualbox and on real hardware:
Google Chrome and Chromium browsers segfault.

Verified. On actual 32-bit hardware.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on June 24, 2015, 12:22:02 pm
RC 4.6.6 32-bit, tested in virtualbox and on real hardware:
Google Chrome and Chromium browsers segfault.

Verified. On actual 32-bit hardware.
Unfortunately, the nature of the google-chrome package does not help this issue.
Google does not distribute the source code, so we are not compiling and linking it to our installed libraries.  Instead, they distribute a .deb and .rpm binary (precompiled).

This means that any progress on our development may render the binary useless, and because we dont have the source code, we cannot recompile it, patch it or fix it in any other way.

Unfortunately, there is not much we can do about the 32-bit version at this point.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: Pita on June 25, 2015, 01:33:43 am
32bit

Smooth installation.

First impression: I am really impressed. :D
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on June 25, 2015, 11:07:14 am
Removed the KVM switch Used 7.0 to add 7.1 to lilo.conf and restore my MBR.  7.1 wants to login in TUI mode it should have been GUI, still no keyboard, mouse or power switch.  Will try reinstalling with out using Lilo (or Grub).  Posting this from 7.0.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on June 25, 2015, 11:37:08 am
It worked!  ;D  Installation went smoothly using the text installer.  (GUI installer still can't find the monitor.)  I noted a lot of warnings about Gnome gnumeric.  32 bit on DELL two Pentium processors 1015 M Ram
Title: Re: VL7.1 STD feedback and suggestions.
Post by: StrayBit on June 25, 2015, 12:17:53 pm
When I attempt to Copy/Paste a file using 2 Thunars, the one being pasted to closes - the file is not copied (even as root).
Set Gslapt to only use the VLCore, there were no packages that needed update nor any that were not already installed - How did I get Seamonkey before?
Title: Re: VL7.1 STD feedback and suggestions.
Post by: roarde on June 25, 2015, 12:29:29 pm
[ . . . ]
Set Gslapt to only use the VLCore, there were no packages that needed update nor any that were not already installed - How did I get Seamonkey before?

What you got from unstable before is now in the stable repos. More info:
http://forum.vectorlinux.com/index.php?topic=18603.msg103460#msg103460 (http://forum.vectorlinux.com/index.php?topic=18603.msg103460#msg103460)
Title: Re: VL7.1 STD feedback and suggestions.
Post by: jsalpha2 on June 28, 2015, 05:12:28 am
Locator's problem from page 3 of this thread seems to have come back.  I have a Logitech wireless keyboard/mouse combo, and during login, typing my user name and password often fails.  The cursor moves, but no letters show.  If I get past that point, when I type startx or startxfce4 the first few letters don't appear.  "rtxfce4 not found" Put new batteries in the keyboard, no change.  Tried holding the keyboard inches away from the little nano receiver and it worked fine.  After login the signal to the keyboard was back to normal and I was able to put the keyboard back on the little keyboard shelf on my desk.
Using the new final version of Vlocity64.  MD5 was correct.  Installed several times and ways before figuring out how to login.  Works fine in VirtualBox.  Using Grub2 instead of Lilo.  Using TUI to login.  I suspect that the firmware(drivers?) do not fully work until after logging in. Just a guess.  I'm ok with this now, maybe it will help someone else out.
Still having problems, may try swapping to an old keyboard..

Last edit, switched to the 32bit version and everything is working great.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: M0E-lnx on July 02, 2015, 07:19:30 am
RC 4.6.6 32-bit, tested in virtualbox and on real hardware:
Google Chrome and Chromium browsers segfault.

Verified. On actual 32-bit hardware.

Those of you with the google-chrome problem,
Please enable the untested repository and after running slapt-get -u, run slapt-get -i mozilla-nss.  This should also remove your installed nspr package (say "Y" if asked).  If it does not, removepkg nspr yourself.  Then try google-chrome again.

It worked for me (wrote this post from chrome on 32-bit), but we need more people to test this before making the fix official.
Title: Re: VL7.1 STD feedback and suggestions.
Post by: nightflier on July 02, 2015, 10:56:26 am
It worked for me (wrote this post from chrome on 32-bit), but we need more people to test this before making the fix official.

Good test, using those instructions on VL-Light 32-bit (on real hardware, 64-bit system). It did remove nspr automatially. Now both chrome and chromium are working normally.   :)
Title: Re: VL7.1 STD feedback and suggestions.
Post by: overthere on July 02, 2015, 02:30:46 pm
32 bit std final firefox flash error on youtube ...I installed 11.2.202.468 (rpm2txz) and it appears to work fine.. is there a testing still? perhaps an update is already available