VectorLinux

Cooking up the Treats => Distro development => Topic started by: uelsk8s on January 26, 2009, 10:10:40 pm

Title: VectorLinux 6.0 RC4 feedback and bug reports
Post by: uelsk8s on January 26, 2009, 10:10:40 pm
Please post bug reports for RC4 here.

Thanks,
Uelsk8s
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: toothandnail on January 27, 2009, 06:16:43 am
Bad news first...

At the start of the install, clicked the 'check installation files' button. Still get an almost instant return with 'everything is ok' message. However., after doing that, when I clicked the 'next' button, I got a popup box 'can't locate setup.conf' followed by an error and lost the GUI installer.

Started again, carefully didn't attempt to check the install files, and the install went through without any errors.

Maybe the check install files code should be left for the next version....

Good news next - my wireless interface is being correctly loaded in RC4. I'm seeing my next door neighbour's wifi access point and getting decent signal levels.

Init works now - I was able to su to root and then use 'init 3' to kill X.

So far, no sign of the update notifier, but looking at services in VasmCC, it seems that the notifier daemon is not starting. I'll try that in a minute.

So far, excellent. More later....

paul.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: toothandnail on January 27, 2009, 06:39:43 am
Update notifier works after the service was enabled.

Some of the mime types appear to be miss set (not sure how many yet, but .pdf is set to open in Gimp, for example). Some icons are also still missing - in the gnome set, no icon for .tlz, none of the Vector specific icons are showing in the Thunar context menu. Same applies to Rodent theme.

Sound driver loaded fine, but I had to fiddle to get sound working - for some reason, the speakers are always disabled after install.

More later..... (bet you're tired of reading that)

paul.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: vincent2 on January 27, 2009, 08:54:30 am
Bon soiree!

RC4 speeds up surfing and better sound effect.would try switch on  a HD classical music radio, opera like "turando", soranto radio...
wired network won't get connected automatically when starting vL6.0rc4,always have to go "Wicd" to connect to router mannually.......any command to fix?
using "gslapt" to install wxcam (in to to use USB webcam), wxcam's still not available from vetor mirror yet, pls. advise  afew  repos. mirror links  for install wxcam !   
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: caitlyn on January 27, 2009, 09:38:09 am
wxcam isn't packaged yet.  I simply haven't had time yet.  Please remember that we are all volunteers here and sometimes making a living has to take priority.  It is very high on my to-do list and hopefully it will be in place before the final release.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: stretchedthin on January 27, 2009, 01:33:56 pm
Numbered items are quoted from my post re: RC3
1. Same problem with NVidia set-up as reported by other users.
  RC4- nVidia Corporation GeForce 7300 GT (rev a2) was set-up without problem, on my compaq desktop,
 using nvidia 180.22 driver.  This worked for me with both the text install and the gui install.
  However, on my toshiba laptop which uses an G72M [Quadro NVS 110m/GeForce Go 7300] I have not been so lucky.

2.-Audio cd's do not play without a lot of fiddling.
 RC4-- I have to change  the CD Audio Player Configuration in xmms from Analog Play Mode to Digital audio extraction. Then it plays fine.

3-For the laptops, I like the option of having the installer set up xorg for synaptics but why can't the synaptics driver be loaded by default or at least some additional instruction saying to download from gslapt. (once it's added to repositories.)
 RC3--Tap and Scroll are not activated by default. Getting them going is not a simple matter for a newbie who would be hoping to see
them working after selecting the touchpad option in the xorg set-up.

 RC4--You guys rock!!!  Touchpad scroll and tap worked right out of the box.

4-Where did  "Search for Files and Folders" go.
 RC3--"Search for Files and Folders", ironically, can't be found on RC3. That's one way to make a problem disappear.
 OK, with me I liked CatFish. Hey, maybe bring CatFish back and just call it "Search for Files and Folders" in the menu. (Is it in the repositories?)
 RC4- Maybe I'm missing it but I can't find anything to search for files or folders with?

5-"Vector Linux Samba Network" does not work
RC4--I can't make this work in VL60.  It works for me in VL-light 6.0 where it's called "Windows Networking"
 ken:$ /sbin/vlsmbmnt
 Mounting [\\KENNAZ-DESKTOP\recordings] at [/home/ken/mnt/KENNAZ-DESKTOP-recordings]
 mount error: could not find target server. TCP name KENNAZ-DESKTOP/recordings not found
 No ip address specified and hostname not found

6.-RC3 Verify installation Files, doesn't seem to do anything.
 RC4The Verify Installation Files' function seems to tell you everything is ok when you first click "Start", then if you click it again it will actually begin the process of verifying the install cd.

7. I error out when trying to set up a windows dual boot. Tried 3 times. 2x gui install. 1x text install. I've attached a picture of the error message.  If it's something I'm doing I sure would be glad if someone could help me out.
       --update.  From the terminal I used liloconfig and I received the same error, however when I used vliloconf I was able to finally set-up my machine as dual boot with windows. Happy day.
 RC4- I'm still having the same problem-(have only tryied gui install).  vliloconf works fine at setting it up after I've installed so it's no biggy.

8. GKrellm installs but does not have a menu entry.
RC4 -It has a menu entry now.

9. If you choose 'clock' and add it to the panel. It is invisible.
RC4-Still invisible. Black numbers on a black background. This is not a biggy of course as there are other better clock choices.

10.  Had the same trouble as an KOSH with RC3 during the net configuration portion of gui install on one machine only.  As he posted it halted the gui and the computer had to be restarted but the rest of the install went fine from there.
RC4-No such problem this install.

11. Openbox appears as a session choice, but does not appear as if any development has been done on it for VL6.0.  Maybe it's just there because LXDE is based off of it, but if it is going to show up as a session choice it might as well have the right menu entries and all it's expected functions.
RC4-Still the same...maybe just fix the menu entries. 

12. VL-hot-config does not launch.  There does not seem to be a vl-hot.config.gambas in /sbin
RC4-Still does not launch but the problem has changed.  The command in the launcher is /sbin/vsuper /sbin/vl-hot-config.gambas
this produces this result in terminal.
 ken:$ /sbin/vsuper /sbin/vl-hot-config.gambas
sh: /sbin/vl-hot-config.gambas: No such file or directory

13.  A) Vpackager generates will generate a .tlz file for me but if I choose to save it, it say that it will and gives me the file where it's saving it to but after I hit OK, I go to the file and nothing is there.
   B) If I choose to install the file from vpackager instead of saving I get an error.  (2nd pic included.)
       On another machine vpackager ran right through no error but nothing was installed.  On both machines I was able to successfully, ./configure, make, and make install the package.  (WxCam 1.03 if your curious)
RC4 Have not had time to test this one. I was hoping someone else could, I just have not used it enough to say that any errors are not of my own making.

Really, thank you guys for going to RC4.  I am excited to see how distrowatch reacts to a really polished VL6.0 when it is released.










Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: M0E-lnx on January 27, 2009, 02:28:04 pm
errr.... I dont see the picture for your lilo error bob :)

Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: kidd on January 27, 2009, 02:57:24 pm
11. Openbox appears as a session choice, but does not appear as if any development has been done on it for VL6.0.  Maybe it's just there because LXDE is based off of it, but if it is going to show up as a session choice it might as well have the right menu entries and all it's expected functions.
RC4-Still the same...maybe just fix the menu entries. 

I think it's ok to have it without tweaking.  I don't think we have any openbox
user who wants to prepare a menu for all programs in vl.  It's nice to have it
there as a choice, in case the other wm crashes, or you want a pretty clean wm
that loads in no time.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: pevsner on January 27, 2009, 04:39:11 pm
Hi,
Great so far VL6 RC4:
Install (graphical gui) no problems, fonts look great, nvidia driver fine, uk keyboard sets fine, can drop down with init.
Will be taking 5.9 completely off real soon. Btw thxs for updating Hplip, prints A3 now.
Opera still has semi transparent drop down menus.
Well done everyone. :)
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: stretchedthin on January 27, 2009, 06:50:00 pm
errr.... I dont see the picture for your lilo error bob :)


Sorry picture is posted on the rc3 thread.
http://forum.vectorlinux.com/index.php?topic=8197.msg55945#msg55945 (http://forum.vectorlinux.com/index.php?topic=8197.msg55945#msg55945)

Hey who's bob :)
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: edgeofthewoods on January 27, 2009, 08:50:46 pm
RC3 ran great, I installed RC 4 on a separate HD. Everything but the wired internet works. If I run net conf  it comes up but when I reboot there is no eth0. That is on two different machines. Both with the same main board. One is a HP Pavalon and the other is a machine I built. Here is my LSPCI

Code: [Select]
thrudheim://home/charles
root:# lspci
00:00.0 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a1)
00:01.0 ISA bridge: nVidia Corporation MCP61 LPC Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation MCP61 SMBus (rev a2)
00:01.2 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a2)
00:02.0 USB Controller: nVidia Corporation MCP61 USB Controller (rev a3)
00:02.1 USB Controller: nVidia Corporation MCP61 USB Controller (rev a3)
00:04.0 PCI bridge: nVidia Corporation MCP61 PCI bridge (rev a1)
00:05.0 Audio device: nVidia Corporation MCP61 High Definition Audio (rev a2)
00:06.0 IDE interface: nVidia Corporation MCP61 IDE (rev a2)
00:07.0 Bridge: nVidia Corporation MCP61 Ethernet (rev a2)
00:08.0 IDE interface: nVidia Corporation MCP61 SATA Controller (rev a2)
00:08.1 IDE interface: nVidia Corporation MCP61 SATA Controller (rev a2)
00:09.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2)
00:0b.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:05.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 70)
01:0a.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1)
Any ideas on getting it to start automatically? It does'nt bug me to much but the wife it does!!:)
Thanks for all the work on this project

Chuck
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: vector on January 27, 2009, 10:29:25 pm
Quote
RC3 ran great, I installed RC 4 on a separate HD. Everything but the wired internet works. If I run net conf  it comes up but when I reboot there is no eth0. That is on two different machines. Both with the same main board. One is a HP Pavalon and the other is a machine I built. Here is my LSPCI
Chuck can you show the output of /etc/sysconfig/vector please maybe we can figure it out.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: GrannyGeek on January 27, 2009, 11:04:47 pm
I installed RC4 on two computers today. On the Celeron desktop I again used the hosted install. Everything went perfectly. No problems with anything. This has been my test machine since the VL6 alphas. It is very Linux friendly, so I didn't expect any problems.

Wish I could say that for installing on the Gateway laptop! I used a text install from a CD. Everything went fine in the installation. NVidia video driver installed in seconds. Sound worked fine the first time and continues to work. But then I discovered that the accursed touchpad is working, contrary to my selection during installation! I was careful to choose NOT to have the touchpad driver loaded, thinking that would disable it. But the dratted thing ISN'T disabled. I absolutely detest that. I use a wireless notebook mouse and don't want the touchpad working AT ALL. I disabled it in 5.9 but don't know if the same approach will work with 6. If at all possible, could we PLEASE have a way during or after installation to disable touchpads without having to jump through hoops or doing obscure edits to xorg.conf?

Now--wireless. I was expecting no problems, based on some of the glowing reports here. Ha! It was a horrendous mess and by some miracle, I got it working and am using my wireless connection as we speak. The wireless chip is a Realtek 8185. It needs ndiswrapper and a Windows XP driver. Instead, the rtl8180 module was loaded. AND there was eth0, which uses a wired network chip. Bad news! That has to be disabled in order for the wireless to work. Otherwise the computer tries to use the wired connection--but there isn't one.

I eventually got the wireless to work by digging through my notes and following (sort of) the directions for setting up wireless. What got me so frustrated was that all these fancy new wireless tools in VL6 didn't work for me. I couldn't find anything for setting up ndiswrapper and telling it what driver to use. (Actually, I did see something briefly but due to the disgusting touchpad interpreting a touch as a click, the ndiswrapper setup thing disappeared, incorrectly and incompletely configured, and I couldn't find it again.) Good grief, we need some directions! How can someone search the forum if he/she can't set up the connection? Now I have to figure out how I can permanently disable eth0 showing up in ifconfig. I don't yet know if my wlan0 will come up automatically after a reboot.

Sorry to sound so negative, but I was just so disappointed that my wireless was such a mess, I was flying blind in trying to fix it, and I could NOT have fixed it with anything in VASM or from the network menu.

Oh yes, another thing. I had at least three hard lockups where neither mouse nor keyboard would work and I had to turn off the computer before I could reboot.

A major annoyance--
On the laptop (14.1" screen, 1280x800 resolution) the fonts in VASMCC are *so small* that I have to struggle mightily to see them. I've adjusted font sizes in XFce settings and qtconfig, but I don't know what controls the size in VASMCC and other screens for system settings.

So on the Celeron desktop, superb. On the Gateway laptop, not so much.
--GrannyGeek
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: edgeofthewoods on January 28, 2009, 04:28:35 am
Quote
RC3 ran great, I installed RC 4 on a separate HD. Everything but the wired internet works. If I run net conf  it comes up but when I reboot there is no eth0. That is on two different machines. Both with the same main board. One is a HP Pavalon and the other is a machine I built. Here is my LSPCI
Chuck can you show the output of /etc/sysconfig/vector please maybe we can figure it out.

Here you go The first is RC3.
MOUSETYPE0="ps2"
XMOUSETYPE0="PS/2"
MOUSE0_FULLNAME="Generic 3 Button Mouse (PS/2)"
MOUSE0_DEVICE="/dev/psaux"
CDROM0_FULLNAME="ATAPI DVD A DH16AYH"
CDROM0_DEVICE="hda"
CDROM1_FULLNAME="HL-DT-ST GCE-8487B"
CDROM1_DEVICE="hdb"
XSERVER="XFree86"
XMODULE="vesa"
XDESC="nVidia Corporation|NV34 [GeForce FX 5200]"


....To be continued once I reboot into RC4

And here is RC4
MOUSETYPE0="imps2"
XMOUSETYPE0="IMPS/2"
MOUSE0_FULLNAME="unknown"
MOUSE0_DEVICE="/dev/input/mice"
MOUSETYPE1="ps2"
XMOUSETYPE1="PS/2"
MOUSE1_FULLNAME="Generic 3 Button Mouse (PS/2)"
MOUSE1_DEVICE="/dev/psaux"
CDROM0_FULLNAME="ATAPI DVD A DH16AYH"
CDROM0_DEVICE="hda"
CDROM1_FULLNAME="HL-DT-ST GCE-8487B"
CDROM1_DEVICE="hdb"
XSERVER="XFree86"
XMODULE="vesa"
XDESC="nVidia Corporation|NV34 [GeForce FX 5200]"

The only difference is that on RC3 the GUI installer failed and I used text, and I used the GUI on RC4.
Looks it each version saw the mouse differently. The other computer my friend needed back and it has 5.9.1 on it but as soon as the bugs get worked out he really wanst VL 6.0 back.
Again thanks for everyones work on this project

Chuck
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: MikeCindi on January 28, 2009, 06:08:02 am
... The wireless chip is a Realtek 8185. It needs ndiswrapper and a Windows XP driver. Instead, the rtl8180 module was loaded. ...

What got me so frustrated was that all these fancy new wireless tools in VL6 didn't work for me. I couldn't find anything for setting up ndiswrapper and telling it what driver to use. ... Good grief, we need some directions! How can someone search the forum if he/she can't set up the connection? Now I have to figure out how I can permanently disable eth0 showing up in ifconfig. I don't yet know if my wlan0 will come up automatically after a reboot.

Sorry to sound so negative, but I was just so disappointed that my wireless was such a mess, I was flying blind in trying to fix it, and I could NOT have fixed it with anything in VASM or from the network menu.

VLwifi should set up your wireless and use ndiswrapper if it can't find a useful module already loaded. You may need to blacklist the rtl8180 module at some point prior to rebooting or it'll be reloaded and block the loading of your rtl8185 module. Also while VLwifi has the option for auto-loading it has been inconsistent for me in the past (but better with rc3 and rc4 so far).

I heartily agree with you about many of the included utilities for wireless. It may just be my ignorance in their configuration but I find them less than helpful for a variety of reason. As for VASM it has offered to use ndiswrapper for me but I'm not sure how I got there other than possibly the obvious option for wireless setup.
HTH,
Miek
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: sledgehammer on January 28, 2009, 11:00:02 am
   
I posted this in the wrong place yesterday...will show it is moved to here  I use the old 5.9 installer for 6.0. Have not tried the normal install with rc3 or rc4 but will next time to see if I can understand it.

I put rc3 on my friend's HP compaq laptop Sunday and it worked great.  Wireless fine. Didn't try wire. Put it on another friends IBM t40 tonight and it would not get on internet via wire (didn't try wireless).  So I loaded rc4 on the T40 and it still would not get wired internet. ifconfig showed eth1 but inet set on vasm was to eth0.  So switched inet to eth1 and worked fine.  But on reboot, same problem....had to keep changing the inet. Finally gave up.  Works though, if inet changed to whatever ifconfig shows after its up and running.  Tried to show friend how to change inet but doubt she understood.  Bit of blind leading the blind here.

Also note that rc3 loaded fine on both HP and t40 (using the old 5.9 installer) but same type install of rc4 on T40 didn't go well.  Hung up near the end.  Took the install disk out, rebooted into text and completed install with vasm. Seemed fine, except for above-noted problem with Clearwire.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: toothandnail on January 28, 2009, 11:10:46 am
Installed to my T42 today (won't have the machine much longer, but thought I might as well test RC4 on it while I can).

I tried the 'verify installation files' button again. Still nothing useful, but this time it didn't kill the install, as it did on the T61. However, at the end of the install, I got the network configuration screen for a second, then the installer died. While I managed to restart the installer, it was right back to the beginning, which wasn't very useful. Did a clean boot and tried again, this time without touching the 'verify install files'. That install went through without problems.

Working fine on the T42. On interesting tihng - the update notifier was active from the first boot, even though the service was not marked as active in VasmCC.

Other than that, everything seems to be runing fine. I get better wifi signal levels on the T61 than I do on the T42, but whether that is a driver issue or simply that the T61 has a better wireless card, I don't know.

paul.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: GrannyGeek on January 28, 2009, 11:20:05 am
VLwifi should set up your wireless and use ndiswrapper if it can't find a useful module already loaded. You may need to blacklist the rtl8180 module at some point prior to rebooting or it'll be reloaded and block the loading of your rtl8185 module. Also while VLwifi has the option for auto-loading it has been inconsistent for me in the past (but better with rc3 and rc4 so far).

I heartily agree with you about many of the included utilities for wireless. It may just be my ignorance in their configuration but I find them less than helpful for a variety of reason. As for VASM it has offered to use ndiswrapper for me but I'm not sure how I got there other than possibly the obvious option for wireless setup.

I did find ndiswrapper in VLwifi, but I think it was after the whole wireless thing disappeared and I had to set it up again, after doing rmmod to get rid of rtl8180. Since it didn't know about any wireless setups, it did offer ndiswrapper and I was able to direct it to the XP driver on my Windows partition. I then had to go through the whole thing and finally had a wireless connection again.

It did seem to survive a reboot, although rtl8180 was listed in lsmod, along with ndiswrapper. That sounds wrong but the connection did work.

One thing that bothers me with VLwifi is that I have to go through the whole setup if the wireless drops. It won't reconnect just by clicking on Connect (which was an option in another applet--not at that computer now, but I think it was wicd network manager). This is a great bother because I use fixed IP addresses and have to enter everything all over again, plus I use WPA and have a 15-letter password with mixed case, numbers, and symbols. Typing that whole thing over and over gets old pretty fast. I think I'm going to create a well-disguised file with the password so I can just copy and paste instead of typing that monster every time. My wireless connection was shaky yesterday; I hope it'll be better today.

I'd like to see VLwifi offer the settings last used rather than fresh default settings, at least as far as the fixed IP addresses go.

Given the difficulties that can occur with wifi, at some point it would be good if VL could include a text or HTML file specifically about dealing with common problems. I wish I could write such a thing, but given my lack of knowledge about problems I've had and never had and my ignorance of possible solutions and wireless HowTo's in general, I don't have anything to contribute.
--GrannyGeek
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: caitlyn on January 28, 2009, 11:25:37 am
The issue with Realtek chipsets exists in pretty much every distro, not just VL.  The problem is that there are native Realtek drivers but they are truly awful (as in limited range if they work at all).  Since the native Realtek driver is present as a kernel module Linux (not just VL) loads that and assumes that ndiswrapper isn't needed.  I saw this with the rtl8187 driver in Ubuntu as well.  This isn't something the VL developers will be able to fix as it is definitely upstream at the kernel level.

The solution is to blacklist the rtl8xxx driver (where xxx is the number of the driver actually being loaded).  Then you should be able to use ndiswrapper normally.

HTH,
Cait
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: MikeCindi on January 28, 2009, 11:26:18 am
wicd network manager should allow you to add your fixed IP address and WPA pw so that you can click connect and get it to do so. This has worked for me in rc3 at least. It just didn't autoconnect after a reboot on occasion.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: GrannyGeek on January 28, 2009, 12:19:28 pm
The issue with Realtek chipsets exists in pretty much every distro, not just VL.  The problem is that there are native Realtek drivers but they are truly awful (as in limited range if they work at all).  Since the native Realtek driver is present as a kernel module Linux (not just VL) loads that and assumes that ndiswrapper isn't needed.  I saw this with the rtl8187 driver in Ubuntu as well.  This isn't something the VL developers will be able to fix as it is definitely upstream at the kernel level.

The solution is to blacklist the rtl8xxx driver (where xxx is the number of the driver actually being loaded).  Then you should be able to use ndiswrapper normally.

I didn't mean to give the impression that I was blaming VL for the Realtek problems. Nor was I blaming Linux in general. The thing that had me frustrated was that I couldn't find help for what to do without being able to get online. I do have a notebook of printed-out Web pages and forum threads for various situations, so I was able to go through the old wireless setup HowTo (excellent for its time but now a bit out of date) and get ndiswrapper going and make necessary edits in /etc files. What would a newbie do, though?

I had worse problems getting wireless going back when we were testing 5.9 Standard. I tried various LiveCDs to see what they'd do with it in hopes I could figure it out and apply it to VL. Most of the LiveCDs couldn't deal with the Realtek 8185 either, but one did a pretty good job and I really liked their wireless setup applet. I think it was PCLinuxOS--is that the one derived from Mandrake? It was very slick and it worked. But the connection dropped *always*--sometimes after several hours, sometimes in a few minutes, and it was using ndiswrapper with the XP 8185 driver. When I finally got the problem solved with lots of help from the VL forum, 5.9 did hold onto the connection pretty well. So score one for us.

Back when I was testing 5.9, I did try the native Realtek driver for 8185 and as you say, it was truly awful. The XP driver under ndiswrapper does quite well. Fortunately, only one of my three Linux computers has wireless, so once I get the laptop going, I don't have to deal with it again.<g>

I do have to say that I was very pleased that sound worked out of the box. The notebook has an NVidia flavor of intel-hda and it took me weeks to get sound when I was testing 5.9 Standard--again, with lots of help from the Forum. This time it "just worked," so there are major advances in that.
--GrannyGeek
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: Gullible Jones on January 28, 2009, 01:43:57 pm
User account and password creation in the graphical installer don't work properly. User supposedly created in the account creation dialog are not in fact generated, and the new root password isn't applied either, leaving the user locked out of the system on first boot. I'd say this is pretty serious.

Also, a missing feature: JFS filesystem creation is supported by the (broken) graphical installer, but not the text installer. It would probably be a good idea to give the text installer JFS support as well.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: sparkyhall on January 28, 2009, 02:29:30 pm
Text install went well on IBM TP600 as gui still not working on this box. Once installed my ralink usb wifi worked out of the box for the first time in VL so a big thanks for that. As I have mentioned in previous releases I do get strange behaviour with terminal 0.2.8.3 as in the top window bar with the minimise and close icons is missing. Not a big problem for me as VL6.0 light is much better suited to this machine.

On my desktop I used the gui installer, all went well including creating user and root accounts. My only real comment is that it seemed to take a long time during final configuration screen (5+ minutes) before moving on. Only issue that I have noticed is that pcman tools>open current folder as root fails to recognise my root password.

Other than that VL6.0 looks ready to release to me....well done !

Chris
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: kc1di on January 28, 2009, 04:05:35 pm
hi Uli,
just did a fresh install of RC4 and it all went very well really like the new graphics and everthing is just perking along so far .
Dave
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: CrazyDog on January 28, 2009, 06:34:40 pm
RC4 stalls when loading GUI at "starting firewall" if you have the built in firewall set up.  At least it did for me.  Also, it would be nice to have an option (maybe after selecting to use the touchpad), to have numlock on at boot.

Thanks!
CrazyDog
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: stretchedthin on January 28, 2009, 10:59:26 pm
In RC2 and RC3 I've been able to use HP device manager to set-up my printer an HP c4250. No go, however, for RC4.  I can set up in cups no problem so it's not a show-stopper but I'm here to report bugs so here you go.

It finds my device no problem but then when I click next it says ppd can not be found.  So I find the ppd manually (at /usr/share/cups/model/HP/ right where it should be, enter the printer information, click next and get "Printer Que Setup failed." please restart cups and try again.

I'm reloading RC3 on my other system to see if I can spot the reason for the different behavior.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: Nobodyinparticular on January 29, 2009, 12:47:11 am
No problems with rc2 or rc3 but rc4 seems 'broken'.
Whatever the combo of installation choices, it eventually stalls.
If defaults are selected, it falls over at PySolFC.
If PySolFC is deselected, it stalls at penguin-command.
Etc., etc.
Returned to rc3 - works perfectly.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: kc1di on January 29, 2009, 05:57:10 am
Quote
RC3 ran great, I installed RC 4 on a separate HD. Everything but the wired internet works. If I run net conf  it comes up but when I reboot there is no eth0. That is on two different machines. Both with the same main board. One is a HP Pavalon and the other is a machine I built. Here is my LSPCI
Chuck can you show the output of /etc/sysconfig/vector please maybe we can figure it out.
I've noticed a very similar problem with my install also. RC4 , when I set up the networking so I can connect it's all lost after reboot.
dave
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: pevsner on January 29, 2009, 08:50:05 am
Quote
In RC2 and RC3 I've been able to use HP device manager to set-up my printer an HP c4250. No go, however, for RC4.  I can set up in cups no problem so it's not a show-stopper but I'm here to report bugs so here you go.

stretchedthin:_ see my comment on rc3 or in printers

Quote
HP printer, hplip included VL6rc3 is 2.8.4 which unfortunately is the only version that doesn't include A3 printing for my HP1220c printer.
I updated to the latest 2.12, but have the "printer queue setup failed" warning. So found a hack which is run "LC_ALL=$LANG.UTF8 hp-toolbox" in terminal - works fine. Is there a way to include this setting in a config file somewhere so I can forget about it and allow to run toolbox normally.
Also I havent been able to get the HP plugin to work with VL6.
Suggestions appreciated.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: pevsner on January 29, 2009, 09:03:39 am
Below is a comment re above I found on the net re Hplip:
Quote
Slackware 12.1/CHANGES_AND_HINTS.TXT
There is a minor problem with the HPLIP and CUPS versions in Slackware 12.1;
hp-toolbox will not work unless LC_ALL is set to a UTF8 locale.
An easy workaround is to start it with "LC_ALL=$LANG.UTF8 hp-toolbox" if
you're not using a UTF8 locale. Also, your user account must be a member
of the "lp" group for hp-toolbox to work properly, and to use the scanner
portion of some (all?) HP print/scan/copy units, you'll need to be a member
of the "lp" group. This is due to the fact that hplip's udev rules set
the device with group "lp" ownership.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: StrayBit on January 29, 2009, 09:18:35 am
I replaced RC3 with RC4 last night:
1) Check files worked on first click, took a very long time, then reported as bad.  Restarted into RC3 and, on copying a second download, discovered my first one was only half the size.  Restarted installation and check files reported good after an even longer check.
2) Imported 2 users that have never been on this machine but failed importing me.  Created me (but don't know the effect)
3) Was happy to see that it saw my install partition but it failed to install to the mbr.  On reboot, it still showed Linux gui, tui and install but froze on gui.  When installing install, it warned of some memory problem but I was able to start it 3 times previously - now the memory split stopped it.

I have replaced my home disk with a cd-rom and have 5.9 live running.  Used gparted to split / so that I can install 5.9 in the third partition.  Hopefully, I can use that until I get RC4 working.
  hda1 swap 494MiB #as reported by gparted
  hda2 / RC4 8.46Gib
  hda3 / 5.9  3.72GiB
  hdc1 install 9++MB #holds .iso for cd-less install
  hdc2 /home 3.9GB
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: wcs on January 29, 2009, 09:45:52 am
Finally got RC4 on the aspire one.
Fantastic work! Wireless, touchpad, hibernate/suspend, resolution... all working out of the box. Also default acpi script working fine (single press on the power button triggers shutdown).

Problems:

1. As before, it's very difficult to use the graphical installer at this resolution, because many scroll screens/lists do not show up. For example, the locale region, the screen where one choose the bulk packages, etc... In the end, I was missing too many options, so went back to the text installer.

2. Wicd does not connect right away to the wireless network after reboot or hibernate/suspend... it tries to connect to the wired network instead, and only after a long while does it go to the wireless one (even though no cable is plugged in). Options to automatically connect and to reconnect on connection loss are checked.

3. Choice of language for gdm does not persist after reboot (only after log out, login). The system language remains the chosen one, but not the login language.

4. Perhaps video drivers for intel chipsets should be updated, but I'm not sure if that conflicts with anything else. Current xf86-video-intel is 2.6.0 (but installed is 2.2.1) and current libdrm is 2.4.4 (but installed is 2.3.1).

5. Had resolution problems when connecting to an external monitor. I had to comment out the HorizRefresh and VertRefresh options in xorg.conf to get the maximum (native) resolution on the external monitor.
This happened both when starting X with the cable plugged in or when plugging the cable afterwards and using xrandr.

6. Hibernate script could also be upgraded to 1.99

7. Get errors when doing halt/init 0... all errors are saying that snd_* modules are in use. But it shuts down anyway.

Very minor issues:

apm says failed (acpid is running)
firefox has evolution as the default mailto program
it would be nice if the splash screen configuration showed a preview of the VL splash, instead of the default.

Thank you so much!

EDIT: Haven't tested card readers yet... chances are it will be a pain, though there are rumours that it will be handled better with 2.6.29.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: GrannyGeek on January 29, 2009, 10:59:06 am
I installed yesterday (text install from CD) on my Athlon 64 X2. No problems with installation or afterwards, except when I tried to run qtconfig it complained about a missing libGL.so.1, which surprised me because I didn't get this complaint when I ran qtconfig on the other two computers on which I've installed RC4. I copied the library and its missing symlink from another RC4 computer and now qtconfig runs. However, it seems odd that it was missing only from this one computer.

The fonts in VASM and some other programs are wretchedly small and I have to struggle in order to read them. Please, can't we have either larger fonts or some choice of font size? Many computers are using much higher resolutions these days and fonts that work on low-res monitors are simply intolerable on high-res screens. The monitor on the Athlon 64 X2 is 1600x1200.

With my laptop I continue to struggle with wireless. I did blacklist forcedeth and that, together with some editing in /etc networking files, has kept a wired eth0 from being created. It is difficult or impossible to get my wireless network working if a wired network is in the picture. I found I absolutely CANNOT blacklist rtl8180, even though I'm using ndiswrapper around an XP driver for rtl8185. If rtl8180 isn't a loaded module, the computer locks up tight and I have to turn the power off before I can reboot. I'm still not 100% sure of the connection, but there is a pattern of locking up without rtl8180 loaded. The wireless connection tends to just disappear sometimes and the only way I can get it back is to reboot. I have many other problems with wireless on this notebook--which puzzles me because once I got it set up in 5.9 Standard, it worked quite well and came on automatically. It seems wireless has changed considerably in VL6, which makes it difficult to set up a connection using the old command line tools like wpa_supplicant. /etc/ifplugd also seems to have disappeared as well as wifi-radar. I'm pretty desperate for my wireless to be working better than this when Final comes out. I didn't expect things to go backward from the earlier release to the later!

On all three computers after I log in a message comes up:
starting slapt-update-notifier-d
(slapt-update-notifier:3460): GTK-WARNING **: cannot open display:

Then things continue as normal.

I got an error (it didn't way what it was) when I tried to install the proprietary ATI driver on the Athlon 64. It's using the open-source radeon driver, which seems fine.

Now I'm hoping my wireless connection will stay up long enough for me to send this.
--GrannyGeek
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: wcs on January 29, 2009, 11:10:25 am
Also,

* cups config gives 404 not found
* gslaptd was not activated in services, but the update notifier pops up anyway
* skype has no sound after suspend (perhaps this version of alsa breaks it, 1.0.18 working fine in VL 5.9, but need to do some more testing)
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: MikeCindi on January 29, 2009, 01:30:10 pm
If rtl8180 isn't a loaded module, the computer locks up tight and I have to turn the power off before I can reboot. I'm still not 100% sure of the connection, but there is a pattern of locking up without rtl8180 loaded.
Perhaps adding "/sbin/rmmod rtl8180" at the end of rc.modules (actually before "/sbin/modprobe ndiswrapper" which for me seems to have to be the last line of the file) would allow the machine to boot but not block wireless from starting. Just a thought...
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: Lyn on January 29, 2009, 03:46:36 pm
When I launch a terminal on my i810 Compaq X restarts, and I am back at the log on prompt.  IIRC we had this problem before with this machine with 5.9
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: GrannyGeek on January 29, 2009, 09:23:01 pm
Perhaps adding "/sbin/rmmod rtl8180" at the end of rc.modules (actually before "/sbin/modprobe ndiswrapper" which for me seems to have to be the last line of the file) would allow the machine to boot but not block wireless from starting. Just a thought...

There's never a problem with the machine booting. But it seems that if I rmmod rtl8180 at any time, I'll get a lockup soon after. And all h*ll breaks loose if I blacklist it. So I'm leaving it alone.

Today I haven't lost the wireless connection since I posted my prior message 11 hours ago. rtl8180 does appear in lsmod, as does ndiswrapper. I'm delighted because now I'm sure that wireless CAN be solid (if the gremlins stay away :-) ). We'll see if the connection comes up when I turn the notebook on tomorrow.

Oh--and by the way, I found out how to disable the touchpad completely and have just my wireless mouse working. I checked my xorg.conf file from my 5.9 installation (which I copied to an external hard drive) and then did the same in xorg.conf on the new 6.0 RC4 installation. It worked!

At the moment, things are looking almost perfect in RC4.
--GrannyGeek
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: vector on January 29, 2009, 10:45:09 pm
Quote
The fonts in VASM and some other programs are wretchedly small and I have to struggle in order to read them. Please, can't we have either larger fonts or some choice of font size? Many computers are using much higher resolutions these days and fonts that work on low-res monitors are simply intolerable on high-res screens. The monitor on the Athlon 64 X2 is 1600x1200.

In your $HOME folder you have a hidden .gtkrc file edit that for font size should be pretty obvious set at 12 now try 14 or 16 see if that works better for you.

Vec
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: edgeofthewoods on January 30, 2009, 04:33:53 am
So any ideaon getting the wired network to autostart on boot? In vasm I reconfigured and told it firmly :) to start on boot, but at every re boot I need to open WICD and have it connect to the network. Other than that it runs GREAT!! Fast and stable.Oh thanks for the tip on HPLIP that brought things in nicely.

Chuck
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: sparkyhall on January 30, 2009, 05:16:47 am
The only way I managed to get my network interface to start was by disabling wicd in both xfce autostart and services in vasm. Once done your network should start providing it's been setup in vasm.

Chris
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: tawie on January 30, 2009, 06:41:17 am
there is a bug when use vasmcc to config wireless, is anybody report this?

when input ssid, if the name of ssid have blank, vasmcc will use the part after blank as the key, and the key you input no use.

as example, my ssid name is 'H3C WBR204g+', when I input this into ssid inputbox, and the generate file of /etc/wpa_supplicant.conf as follows:

# cat /etc/wpa_supplicant.conf
---------------------------------
# See /usr/doc/wpa_supplicant-0.5.7/wpa_supplicant.conf.sample
# for many more options that you can use in this file.

# This line enables the use of wpa_cli which is used by rc.wireless
# if possible (to check for successful association)
ctrl_interface=/var/run/wpa_supplicant
# By default, only root (group 0) may use wpa_cli
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1

network={
   ssid="H3C"
   #psk="WBR204g+"
   psk=54972dc1797b4cc87ccf9a59f5e7b52b92e62bde6d24f297ac1ff4920891e28a
}
----------------------------------------------

the name of ssid and key all wrong here, so the wireless never have a chance to connect.


Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: caitlyn on January 30, 2009, 11:31:11 am
I installed VL 6.0 rc4 on my new Sylvania g Netbook Meso.  As wcs already pointed out the GUI installer is a "whole lot of no fun" at less than 1024x768 so I did a simple, hosted install this time.  The results:  everything, and I do mean everything, works out of the box  ;D   OK, I need to add webcam software (packages coming soon) but the sound, wired and wireless networking, sound, and video @ 1024x600x24 were all setup correctly.  Very, very nice.

It was also nice to see that samba is no longer started by default.  The minimal set of automatic ready-to-go services is spot on.  It's easy enough to add things in vasm or vasmCC.

I did notice that the notifier does run even without the gslaptd daemon being selected.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: rbistolfi on January 30, 2009, 03:30:50 pm
you may need to change some of the options to make it to work with your cam, but If you want to just test the camera I use something like

Code: [Select]
mplayer -cache 128 -tv driver=v4l:width=640:height=480:outfmt=i420 -vc rawi420 -vo xv tv://
of course I made an alias for it, I don't type all that each time I want to see my pretty face :P
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: GrannyGeek on January 30, 2009, 06:54:29 pm
In your $HOME folder you have a hidden .gtkrc file edit that for font size should be pretty obvious set at 12 now try 14 or 16 see if that works better for you.

Thanks for the suggestion. Unfortunately, it didn't change the font size that is too small for my eyes at all. I wish I could attach a screen shot to a message in this forum. I don't have a place where I can post a picture that does not reveal more of my identify than I want out on the Internet.

The screens in question are those that I get after clicking on an icon in VASMCC: for example, BACKUPSYS MENU, DISPLAY MANAGER CONFIGURATOR, SET SERVICES MENU, and all the rest. The text in the Dillo Address Bar and the Dillo Icon Bar is tiny, but the text on Web pages is fine because it's adjustable in dillorc. The right-click menu text in XPDF is tiny. I don't know where the font size of these screens is controlled. (I've been asking this question for years.)

I use a program called CheckBook Tracker to keep a check register on my computer. It uses the same tiny text size as Dillo and XPDF in its menus and unadjustable screen text. The font and text size of the check register itself can be selected by the user, but there is no setting for the menus and unchangeable text. I assume CheckBook Tracker, Dillo, XPDF, etc., get their menu text font and size from some system setting, but where is it?
--GrannyGeek
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: vector on January 30, 2009, 07:31:06 pm
Quote
Thanks for the suggestion. Unfortunately, it didn't change the font size that is too small for my eyes at all. I wish I could attach a screen shot to a message in this forum.

Granny did you logout and log back in? Changes will not happen till you do that.

Vec
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: StrayBit on January 30, 2009, 09:08:12 pm
 Obviously something is wrong with my installation as many others have successful installs.  I'm attempting to install RC4 on a Compaq Deskpro Pentium III (Katmai) 500MHz 384MB Ram.  I have had VL5.9 and RC3 installed.  Both times I have tried to install RC4, as it opens the Network Configuration, it reports
Quote
This application has raised an unexpected error and must abort.
[-1]Bad index
FrmNet.conf.?.0
Clicking OK gives a gray screen.  Right clicking on it gives 4 option, one of which leads to FreeCell which is very good, another allows me to shut down or restart (among other options).  Originally, Ihad the 13GB drive partioned for 500 MB swap and the rest for the installation. Now it is
Code: [Select]
hda1 Boot 3999.75 / (VL5.9 Std)
hda2 Boot 3999.75 / (VL6.0-RC4)
hda3 Boot 1000.20 / (Install - no CD permantly attached)
hda5           600.22 Swap
hda6         4001.30 /home
I installed 5,9 from a cd and place rc3 or RC4 in Install and modified lilo to offer it as a selection.  RC3 was successfully installed by this method.  RC4 stopped as indicated above and also munged my boot. So I again attached a cd partioned the drive as indicated, installed 5.9 then rebooted and then copied RC4.iso to install and tried RC4 again with the same result.  Should I go back to RC3?
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: sparkyhall on January 31, 2009, 06:43:53 am
Installed on a IBM T40 laptop today using an external USB cd drive as the internal drive is faulty. GUI install went without a hitch athough the configuring hardware stage seems to take a long time with no real visual indication that anything is happening and the next button is not greyed out tempting you to click it.

When prompted to restart the internal cd drive was ejected rather than the USB one that I was installing from.  :D

Still not found any major issues here.

Chris
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: tawie on January 31, 2009, 06:51:13 am
use lm-sensors error.
# sensors-detect
....
Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `coretemp' (should be inserted):
  Detects correctly:
  * Chip `Intel Core family thermal sensor' (confidence: 9)

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): y
Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.

# sensors -s
Can't access procfs/sysfs file
Kernel interface access error
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!



Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: uelsk8s on January 31, 2009, 08:38:58 am
Obviously something is wrong with my installation as many others have successful installs.  I'm attempting to install RC4 on a Compaq Deskpro Pentium III (Katmai) 500MHz 384MB Ram.  I have had VL5.9 and RC3 installed.  Both times I have tried to install RC4, as it opens the Network Configuration, it reports
Quote
This application has raised an unexpected error and must abort.
[-1]Bad index
FrmNet.conf.?.0
Clicking OK gives a gray screen.  Right clicking on it gives 4 option, one of which leads to FreeCell which is very good, another allows me to shut down or restart (among other options).  Originally, Ihad the 13GB drive partioned for 500 MB swap and the rest for the installation. Now it is
Code: [Select]
hda1 Boot 3999.75 / (VL5.9 Std)
hda2 Boot 3999.75 / (VL6.0-RC4)
hda3 Boot 1000.20 / (Install - no CD permantly attached)
hda5           600.22 Swap
hda6         4001.30 /home
I installed 5,9 from a cd and place rc3 or RC4 in Install and modified lilo to offer it as a selection.  RC3 was successfully installed by this method.  RC4 stopped as indicated above and also munged my boot. So I again attached a cd partioned the drive as indicated, installed 5.9 then rebooted and then copied RC4.iso to install and tried RC4 again with the same result.  Should I go back to RC3?
can you install rc4 from text installer?
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: StrayBit on January 31, 2009, 10:43:24 am
I'll try that.  Currently, I'm clearing the partition and will enlarge it a bit as I saw that it was close to full - and I hadn't added any other programs.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: caitlyn on January 31, 2009, 12:09:09 pm
I tried logging into an LXDE session instead of Xfce for the first time since installing RC4.  It starts with an error:

Code: [Select]
Error: Unable to establish connection with FAM.

Do you have "FAM" or "Gamin" installed and running?

Gamin is installed by default so I'm surprised it isn't working.

It also came up with no background or icons.  It turns out pcmanfm doesn't start automatically.  Once I run pcmanfm the background and icons appear.  Also, by default, the openbox menu comes up with a right click rather than the pcmanfm desktop menu.  It may not be obvious to new LXDE users that to change the desktop settings they need to go into pcmanfm from the menu.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: never_stop_learning on January 31, 2009, 02:02:59 pm
Just installed RC4 - via hosted method - on my IBM X22. Looks good. I got Wicd back (never could get it working with RC3).....

The default Terminal still does not look good - blurry and unfocused - but urxvt looks and works fine.

I will try LXDE next and report back.....
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: toothandnail on January 31, 2009, 03:29:15 pm
I think someone has already mentioned this, but I've been meaning to for days and keep forgetting. On shutdown, I'm seeing a string of errors from various parts of Alsa - modules that are in use. Still shuts down, but there are 3 or 4 errors as it does so.

paul.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: sledgehammer on January 31, 2009, 04:31:51 pm
The lady with the IBM T40 came back again (promising to load vector is sure a good way to get women over to a single guy's home).  I earlier posted in this thread that I could not get her wired connection to reliably work.  I decided this time to start from scratch.  Burned another CD iso using K3B.  Decided to use the rc5 gui install (rather than the old 5.9 install).

Got stopped at the gparted page.  Could not get "next" to highlight.  Called never_stop_learning and he got me past that screen.  I doubt that anyone who doesn't have never_stop_learning's phone number can figure out how to highlight "next" from the gparted screen on the GUI install.  Clearly some instruction or a help button is needed.

Anyway, after talking to never_stop_learning I got the "next" button highlighted and the install continued to the end (configure screen).  Went to "configure." Got "Application error-must abort" error and it aborted.  Took out the install disk, went back in via text and vasmed it, completing the install without further error.

Tried internet on wire and it did NOT connect.  Having read on this thread that one possible fix was to delete wicd in both xfce and vasm, I did that.  Wired connection still did not work.  Called never_stop_learning again and he said to put wicd back in both places and turn the "always show wired connection" machine on.  Did so, rebooted and it connected via wire fine.  In fact, wicd also showed my home wireless and a neighbor's. Rebooted again.  Wired connection still worked fine.  Loaded openoffice and a couple of other programs, rebooted, and the wired connection continued to work perfectly.  The lady is very happy with 6.0 rc4 right now..  As am I.




Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: GrannyGeek on January 31, 2009, 10:40:19 pm
I have a suggestion for the initial screen that comes up right after booting. I think it moves too quickly into a GUI autoinstall. There isn't enough time to read everything and think about it. It's hard to realize you can get to a text install by typing linux at the prompt before the GUI install starts if you can't finish reading.

Is it really necessary to automatically start the installation? Simple directions to hit ENTER to start the graphical installation would suffice. Or set the timer to two minutes before anything happens automatically.
--GrannyGeek
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: fdeak on February 01, 2009, 04:14:45 am
Is there anybody else who has problems with the visibility of checkboxes?

Unchecked checkboxes are totally invisible for users created after the install with vasmcc.
For users created by the installer the unchecked checkboxes are visible.

This happens on two machines: with the proprietary nvidia driver on a desktop machine and with the radeon driver on a laptop.
The checkboxes are so invisible that I cannot see that there is anything I can check in.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: StrayBit on February 01, 2009, 05:47:32 am
Thank you, Granny.  You answered my question before I even asked it.  I was trying to find out how to get to the text installer as this is the fourth time I've attempted to install - always crashing at the same point.

Trouble is, I don't even see the point you mentioned to type 'Linux'.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: fdeak on February 01, 2009, 06:38:26 am
My notebook native resolution is 1400x1050.
This resolution can't be selected when the installer starts, but it is not a big problem because the installer runs fine with 1024x768.
But it cannot be set in vxconf which would be nice.


Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: edgeofthewoods on February 01, 2009, 07:49:49 am
Thank you, Granny.  You answered my question before I even asked it.  I was trying to find out how to get to the text installer as this is the fourth time I've attempted to install - always crashing at the same point.

Trouble is, I don't even see the point you mentioned to type 'Linux'.

At the very first screen after the CD starts there is a
boot:

At that point type in linux and let her rip.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: edgeofthewoods on February 01, 2009, 07:55:47 am
So far after the 2 minor fixes with hplip and the internet on my son's computer and RC3 on mine with  no issues. All works as intended. VL 6 is a bit slower than VL 5.9 Gold, but not very much. ON my kids computer a Dell Optoplex 22.8 ghz HT  Intel the speed increase from 5.9.1 SOHO is HUGE they are loving it. Only real questions I have now are, 1 The log out menu in LXDE is nice, How do I "move"that to the XFCE side.2 How do I change the back ground in the LXDE, and 3 how do I "Lock" the screen in XFCE? Vector and your folks have out done yourselves with this one. Heck I may leave the KDE  environment totally now!!

Chuck
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: caitlyn on February 01, 2009, 09:23:31 am
Chuck:

There are several ways to do screen lock.  My personal favorite is to add an icon to the panel.  Right click on the panel and select Add New Item.  There is an item called Action Buttons.  You can add a screen lock icon through that item. 

You can also remove the logout icon from the panel and choose both lock and logout when you add the new item.  That gives you two half-size icons, one on top of the other, for lock and logout.

HTH,
Cait
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: fox on February 01, 2009, 09:41:42 am
This is my first exposure to Vector, so I can't compare 6RC4 to any earlier version.  I installed it on my Intel Mac mini as a virtual machine in VirtualBox.  This probably insulates me from some of the issues people are having with wireless, but on the other hand, I haven't seen any reports in this thread on installations on a virtual machine.

The result was pretty good, especially given my lack of exposure to Vector and the fact that my experience up until now has been mostly with the "major" distros (Ubuntu, Debian, openSUSE and a bit with Mandriva), all except the latter with Gnome.  I went with the new graphical installer, and instructions were pretty straightforward except for the partitioning part.  I was surprised to find no automatic partitioning option, though fortunately I have had enough experience with gparted to make a good guess as to what I needed.  I went with two partitions, one ext3 with / as mountpoint and one swap partition.  The rest of the installation was pretty routine and before long I was booting into the new distro on my HD.

My connection to my home router is through AirPort wireless on the mini, but both VirtualBox and VMware Fusion mimic a wired connection on virtual machines.  The big test with any vm is whether the tools package will install properly and give full functionality, including mousing to and from vm without a special release key, resizing vm window on the fly and folder sharing.  Happily, VirtualBox tools installed without incident and all of the tools worked.  (VMware tools are more of a challenge, so I installed on VirtualBox to increase my chances of success.)

Other than the lack of an automatic partition option, my only complaint was weird fuzzy graphics on the Terminal right after installation.  Fortunately it went away after a reboot.

The next challenge for me was installing software since VL only gives you the basic stuff.  I used gslapt to install openOffice, Evolution and Rhythmbox, in part because I wanted to see what software was available in the repository.  Both installed without incident.  Unfortunately, Rhythmbox didn't come with the codecs to play AAC (mp4) music files like those in my iTunes and the app didn't offer to get them, but I was pretty certain that what was missing were gstreamer bad and ugly, and they were available through gslapt.  However, the helper application that gets the album art and works to connect Jamendo are still missing, and I don't know what they are called.

I use statistical applications in my work, so I always install "R" and the GUI for R called rkward.  I wasn't surprised that rkward was missing from the repository, but I was that R wasn't present either.  My next test for Vector will be to get the source code for these and try out the graphical compiler tool.

All in all, a pretty good experience for a relative beginner in Linux.  And lest I forget, the Desktop - look and feel is very nice; a real work of art!
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: rbistolfi on February 01, 2009, 09:54:08 am
Hi Fox, welcome to the forum.

We are still working in the repository and new packages are added frequently. I am sure R will make it into the repo soon.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: uelsk8s on February 01, 2009, 09:58:27 am
Quote
The fonts in VASM and some other programs are wretchedly small and I have to struggle in order to read them. Please, can't we have either larger fonts or some choice of font size? Many computers are using much higher resolutions these days and fonts that work on low-res monitors are simply intolerable on high-res screens. The monitor on the Athlon 64 X2 is 1600x1200.

Granny,
I think the file you need to edit is ~/.gtkrc-2.0
add something like
Code: [Select]
gtk-font-name="DejaVu Sans 16"
Let us know if that works

Uelsk8s
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: caitlyn on February 01, 2009, 10:14:52 am
fox:  Welcome to VL! 

Please remember that VL 6 hasn't released yet and the repository is not fully populated.  We added about 40 packages in the last three days and more are on the way.  rkward and R are in the VL 5.9 repository.  You may want to put a note in the New Package Requests section of the forum so that the volunteer packagers know you are looking for them in VL6.  That may speed the process a bit.

Again, welcome.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: StrayBit on February 01, 2009, 01:33:29 pm
I guess that I'm doing what is called a hosted install.  I have the iso on hd and modify llo to allow me to start it.  I have successfully installed 6.0-RC3 by this method.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: kc1di on February 01, 2009, 02:21:19 pm


I use statistical applications in my work, so I always install "R" and the GUI for R called rkward.  I wasn't surprised that rkward was missing from the repository, but I was that R wasn't present either.  My next test for Vector will be to get the source code for these and try out the graphical compiler tool.



Hi Fox,
I have packaged R-2.8.1 for VL6.0 it should be available in a few days in the testing repository.  I haven't had time to really look at RKward yet , but it is a KDE specific program so may take some time to work it out into a package that will work with XFCE. will have to see.
Cheers!
dave
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: uelsk8s on February 01, 2009, 02:23:04 pm
I guess that I'm doing what is called a hosted install.  I have the iso on hd and modify llo to allow me to start it.  I have successfully installed 6.0-RC3 by this method.
I dont think this would be considered a hosted install.
What are you adding to lilo to be able to start it?
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: Windozer on February 01, 2009, 02:35:30 pm
[...] installed it on my Intel Mac mini as a virtual machine in VirtualBox. 
[...] haven't seen any reports in this thread on installations on a virtual machine.
[...]VMware tools are more of a challenge, so I installed on VirtualBox

Hello Fox,

Welcome to VL and to the forum --- this is a great distro and an excellent place to hang out for assistance. I'm chiming in here because you and I have parallel experiences it seems.  As an aside, my reply is all RE VL6, RC3 and below, but am pretty sure it will be fine on rc4 and up. (knock on silicon.)

I've had 5.8, 5.9, and 6, rc2, rc3 working fine in VirtualBox - haven't tried RC4 yet, because I'm probably just going to install it straight to the drive.  I agree with you on VMware - it's a bit of a dog - gave up on it some time ago.

Quote
[...] "R" and the GUI for R called rkward. [...]

Although they're not in the repo, I've got R to work in 5.9 and 6, rc3.  And even lthough R in VL is not as snappy as in distributed Quatian or Pelican HPC (for obvious reasons  ;D), it still is faster than other distro's I've tried (on i86 platforms) - because it's running Slackware. VL is pretty dang fast.  Also, of course, it depends on how big of a data set you're crunching and in what way.

Quote
My next test for Vector will be to get the source code for these and try out the graphical compiler tool.

I haven't used rkward on VL yet. Not sure how that'll play out because of the KDE dependencies.  But "parts is parts," that is, "apps are apps," so there are plenty of folks here who can help out.

Quote
[...]a pretty good experience for a relative beginner in Linux.
Just emerging from the cocoon of Linux N00Byism myself. It's a great basis for maths.

Quote
And lest I forget, the Desktop - look and feel is very nice; a real work of art!
Yes, we love it! (and I can't take credit for any of it  :'()


Well, let us know how it goes, and once again, welcome!

- Howard in Florida
~~~~~~~~~~~~

PS - @kc1di --- great! you posted just moments before me, so I didn't see you're putting R in the repo. Wonderful, thanks for that! - H
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: GrannyGeek on February 01, 2009, 02:50:26 pm
I think the file you need to edit is ~/.gtkrc-2.0
add something like
Code: [Select]
gtk-font-name="DejaVu Sans 16"

Thanks for the suggestion. I tried it, restarted X, but the font size seems to be about the same. I haven't rebooted. I also think I'll do that in the /root home directory just to see what happens, since those screens don't show up until I start VASMCC with the root password.

One good thing, though. I discovered that changing the font size enough in .gtkrc *does* make the menu font larger in CheckBook Tracker! I think it wants one of those bitmapped fonts in /usr/share/fonts/75dpi and while 18 was a bit too small, 24 (the next available size) was too large. So I have it set to 18 and it's way better than it was before.

So far no changes are affecting the tiny menu fonts in Dillo.

I'll let you know if thing change after a reboot.
--GrannyGeek
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: StrayBit on February 01, 2009, 10:19:51 pm
Per your suggestions uelsk8s, I copied init.gz and sata to my 5.9 /boot and added the following to lilo
Code: [Select]
# Partition 4: iso installer
image = /boot/sata
initrd = /boot/init.gz
root=/dev/ram0
append = "splash=silent load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=75000 rw "
label = installer
  The iso was originally on a separate hd, but have made a partition for it on hda so I could add a cd-rom to reinstall 5.9 which meant that I had to remove the cover - again.  (It is either cover or cd-rom!)
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: Nobodyinparticular on February 02, 2009, 02:22:52 am
Confirming previous report, RC4 does not work for me on any system. However, more ways of killing the cat - the RC3 - RC4 delta did the biz. Nice. Let's hope the final fixes these glitches.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: fox on February 02, 2009, 04:16:30 am
Thank you all for your welcome and quick replies.  I am very pleasantly surprised by the quick responses to my two posting, and the fact that so many people would know about R and rkward.  (Perhaps I shouldn't be - Linux does attract academic types  :).)

As I noted earlier, I installed RC4 as a virtual machine on VirtualBox.  I have since noted two bugs:
(1) The clock, installed by default on the panel, didn't update to the proper date and time after the vm state was saved and revived a day later.  I was able to reset it with date and time, so I'll have to check whether the problem fixed itself.  Update: it doesn't fix the clock.  The clock keeps time all right, but it doesn't sychronize with any external source so it doesn't "know" that time has passed when a vm state is saved.  Even restarting the vm doesn't fix the problem.
(2) When I tried putting a new clock on the panel, it was nearly invisible on the black panel.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: sparkyhall on February 02, 2009, 05:05:03 am
A couple more observations made:

 1) As a normall user if I click on "Scripts" in wicd it asks for a root password but fails to accept it eventually reporting "Failed to run /usr/lib/wicd/configscript.py '0' 'wireless' as user root".

 2) I am unable to use wicd to connect to my wifi with ssid disabled. I beleive this issue has been fixed in wicd 1.5.8. Is it to late to include wicd 1.5.8 instead of 1.5.6?

 3) As others have noted the menus in opera appear slightly transparent. This is true on machines with nvidia and ATI based graphics cards.


Chris
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: wcs on February 02, 2009, 09:27:03 am
Quote
(2) When I tried putting a new clock on the panel, it was nearly invisible on the black panel.

Me too. It seems to be because of the colours of the clock applet.
But try the other applet (orage clock, I think), and you can choose the background andforeground colours.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: Joe1962 on February 02, 2009, 09:39:06 am
FWIW, I installed RC4 with the graphical installer and most everything went well and all works. The only issue was with the lilo install step. Granted, this is due to some old issue with the windows partition (second partition on HDD, swap is first), so lilo always gives an error and reports that I should use ignore-table or fix-table. Maybe this should be added somewhere in the lilo config/install screen (with a big disclaimer if selecting fix-table, I guess). Obviously, I ended up booting the installed system via the VL install CD and editing lilo.conf to add ignore-table, then running lilo.


BTW, I just love the new wallpaper!!! And finally the default icon theme is not vista-inspirate....
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: kc1di on February 02, 2009, 10:00:58 am

BTW, I just love the new wallpaper!!! And finally the default icon theme is not vista-inspirate....

Hi Joe,
I'm with you love the new wallpaper also.
Dave

Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: wcs on February 02, 2009, 06:27:07 pm
Quote
2. Wicd does not connect right away to the wireless network after reboot or hibernate/suspend... it tries to connect to the wired network instead, and only after a long while does it go to the wireless one (even though no cable is plugged in). Options to automatically connect and to reconnect on connection loss are checked.

Ignore that... I guess I was just being silly.
Unchecking the "use as default profile box" (or something like that) did the trick.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: caitlyn on February 02, 2009, 07:27:10 pm
wcs:  Go into the directory in the repo where the test isos are kept.  I think you know the one.  Pull out rc4.2.  I think you'll find the GUI installer now works perfectly well at 1024x600.  It does on my Sylvania so it should on your Acer  ;D
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: vector on February 02, 2009, 11:39:57 pm
Any of you that have had wicd issues would you please try this package see if it helps any
http://forum.vectorlinux.com/index.php?topic=8410.0
If you have the testing repo opened in gslapt should be there.

Thanks,
Vec
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: vincent2 on February 03, 2009, 02:52:19 am
Bonjour! Vector,
Quote
Any of you that have had wicd issues would you please try this package see if it helps any
http://forum.vectorlinux.com/index.php?topic=8410.0
If you have the testing repo opened in gslapt should be there.

Just tried and upgraded to wicd1.5.8,the issue remains, still have to  press "connect button" @ wicd panel mannually  to get get connected with the router.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: pevsner on February 03, 2009, 05:46:34 am
Excellent so far Rc4, (havent tried the .1, or .2)

With wine 1.14, the fonts are'nt as good as on 5.9, thin and jagged(antaliasing I guess).
I have a Nvidia geforce 6200 card and using the vl 173.xxx.xx driver.
Any suggestions.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: Joe1962 on February 03, 2009, 06:30:36 am
Oops... no ifplugd!?!?  ???
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: stretchedthin on February 03, 2009, 08:53:02 am
I was just reading this thread re: vpackager ...
http://forum.vectorlinux.com/index.php?topic=8396.0;topicseen (http://forum.vectorlinux.com/index.php?topic=8396.0;topicseen), when Fox completes the process in vpackager there is no .tlz file to be found. 

I experienced the same trouble when testing it in RC3.  Seeing that both myself and Fox are relatively new, (at least to vpackager) could someone with a little experience test vpackager from this release. Thanks in advance.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: toothandnail on February 03, 2009, 11:10:30 am
Any of you that have had wicd issues would you please try this package see if it helps any
http://forum.vectorlinux.com/index.php?topic=8410.0
If you have the testing repo opened in gslapt should be there.

I wasn't having any real problems with the version in RC4, but the new version is quite a bit quicker on my machine - finds local wireless networks faster than the older version did.

The only peculiarity I've noticed with it is a sort of 'shadow' effect. When I click on the system tray icon, the window that comes up has a shadow of whatever was detected the last time it was used. Takes a second for any changes to register. Not a problem, just visually a bit odd.

paul.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: caitlyn on February 03, 2009, 11:26:53 am
I've been running the new version of wicd on the Sylvania since last night.  I was out and about and did get to use the netbook on the road while waiting for an appointment this morning.  I didn't have any problems with 1.5.6 and I still don't have any problems with 1.5.8.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: GrannyGeek on February 03, 2009, 11:59:40 am
With wine 1.14, the fonts are'nt as good as on 5.9, thin and jagged(antaliasing I guess).
I have a Nvidia geforce 6200 card and using the vl 173.xxx.xx driver.
Any suggestions.

Did you try this? At a terminal prompt, type
winecfg
as user. With Default Settings highlighted in the Applications tab, click on Desktop Integration. Click on the down arrow by Item. Start at the top (Active Border) and using the down arrow, go down through the list. Whenever the Font button to the right becomes ungreyed out, click on Font and choose the font and size before clicking on OK. Click on alt+e to resume where you were and keep moving down the list with the down arrow, again watching the Font button and adjusting the font and size as you wish. When you're ready to leave winecfg, click on OK at the bottom of the Wine Configuration window. The next time you start a Wine program, your fonts (menus, tool tips, and such) should no longer look spindly.

It works for me. I hope it works for you.
--GrannyGeek
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: GrannyGeek on February 03, 2009, 12:04:34 pm
I'm trying to install the proprietary ATI driver for a Radeon 200 video chip. I get an error message, which the ATI install log gives as:
[Message] Kernel Module : Trying to install a precompiled kernel module.
[Message] Kernel Module : Precompiled kernel module version mismatched.
[Error] Kernel Module : No kernel module build environment - please consult read
me.

This doesn't mean much to me. I'm using the kernel and ATI proprietary driver included with RC4. I installed whatever kernel-related things were offered in the text install. What's wrong?

I'm currently using the open-source radeon driver, which works fine but gives me less than 600 fps with glxgears.  Probably doesn't matter since I'm not a gamer, but still...
--GrannyGeek
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: sparkyhall on February 03, 2009, 12:06:11 pm
Any of you that have had wicd issues would you please try this package see if it helps any
http://forum.vectorlinux.com/index.php?topic=8410.0
If you have the testing repo opened in gslapt should be there.

Doesn't fix my issue of being able to connect with ssid disabled. The strange thing is that when I disable my ssid the network shows in the list but without any name whereas other networks display as <hidden>. Works fine if I enable ssid so I guess I will have to live with that for now.

A big thanks for packaging the latest wicd

Chris
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: GrannyGeek on February 03, 2009, 12:09:47 pm
Today when I tried to start Opera, it didn't start and I got this when I tried to run Opera from a terminal prompt:
/usr/lib/opera-9.63/opera: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory

What happened to it? I've done several updates (AbiWord and its related stuff, GOffice, some others). Maybe one of them "disappeared" libGL.so.1? I copied the library and its symlink from my other desktop to /usr/lib on this computer and Opera ran as expected after that.
--GrannyGeek
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: caitlyn on February 03, 2009, 03:35:52 pm
I just tried Opera on a system with Abiword 2.6.6., goffice 0.6.6, etc... on rc4.2 and it worked.  I don't know what happened to your library but the upgrades you mentioned wouldn't have caused the problem.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: uelsk8s on February 03, 2009, 03:54:10 pm
Today when I tried to start Opera, it didn't start and I got this when I tried to run Opera from a terminal prompt:
/usr/lib/opera-9.63/opera: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory

What happened to it? I've done several updates (AbiWord and its related stuff, GOffice, some others). Maybe one of them "disappeared" libGL.so.1? I copied the library and its symlink from my other desktop to /usr/lib on this computer and Opera ran as expected after that.
--GrannyGeek

libGL.so.1 is a video(mesa) library I would guess it was lost while trying to install ATI drivers.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: GrannyGeek on February 03, 2009, 04:23:33 pm
I just tried Opera on a system with Abiword 2.6.6., goffice 0.6.6, etc... on rc4.2 and it worked.  I don't know what happened to your library but the upgrades you mentioned wouldn't have caused the problem.

That's good to know.
--GrannyGeek
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: GrannyGeek on February 03, 2009, 04:37:15 pm
I upgraded to wicd 1.5.8 but it didn't help. It wasn't able to connect me to my wireless wlan0. At startup I have to run vlwifi in order to get my wireless connected. Today running vlwifi once was enough. Other days I've had to run vlwifi as many as five times before the wireless connection works.

Once I got connected yesterday, the wireless connection stayed up for nine hours until I turned the computer off. That was great! It's just getting it to come up that is a bit of a problem. I'm just glad it's working!
--GrannyGeek
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: vector on February 03, 2009, 06:04:52 pm
Quote
I upgraded to wicd 1.5.8 but it didn't help. It wasn't able to connect me to my wireless wlan0.

Granny,

Can you post your /var/log/wicd/wicd.log output so we can see whats happening or in your case whats not happening?

Thanks Vec
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: GrannyGeek on February 03, 2009, 06:51:55 pm
Can you post your /var/log/wicd/wicd.log output so we can see whats happening or in your case whats not happening?

I didn't even know that log was there! Here it is (with IP and DNS addresses altered for privacy):

Code: [Select]
2009/02/03 17:06:29 :: ---------------------------
2009/02/03 17:06:29 :: wicd initializing...
2009/02/03 17:06:29 :: ---------------------------
2009/02/03 17:06:29 :: Automatically detected wireless interface wlan0
2009/02/03 17:06:29 :: setting wireless interface wlan0
2009/02/03 17:06:29 :: Couldn't detect a wired interface.
2009/02/03 17:06:29 :: setting wired interface None
2009/02/03 17:06:29 :: setting wpa driver wext
2009/02/03 17:06:29 :: setting use global dns to False
2009/02/03 17:06:29 :: setting use global dns to boolean False
2009/02/03 17:06:29 :: setting global dns
2009/02/03 17:06:29 :: global dns servers are None None None
2009/02/03 17:06:29 :: setting automatically reconnect when connection drops
2009/02/03 17:06:29 :: found dhcp_client in configuration 2
2009/02/03 17:06:29 :: Setting dhcp client to 2
2009/02/03 17:06:29 :: Wireless configuration file found...
2009/02/03 17:06:29 :: Wired configuration file found...
2009/02/03 17:06:29 :: chmoding configuration files 0600...
2009/02/03 17:06:29 :: chowning configuration files root:root...
2009/02/03 17:06:29 :: Using wired interface...
2009/02/03 17:06:29 :: Using wireless interface...wlan0
2009/02/03 17:06:29 :: autoconnecting... wlan0
2009/02/03 17:06:35 :: No wired connection present, attempting to autoconnect to wireless network
2009/02/03 17:06:35 :: trying to automatically connect to...69Wireless70
2009/02/03 17:06:35 :: Connecting to wireless network 69Wireless70
2009/02/03 17:06:35 :: Putting interface down
2009/02/03 17:06:35 :: Releasing DHCP leases...
2009/02/03 17:06:35 :: Setting false IP...
2009/02/03 17:06:36 :: Stopping wpa_supplicant and any DHCP clients
2009/02/03 17:06:36 :: Flushing the routing table...
2009/02/03 17:06:36 :: Generating psk...
2009/02/03 17:06:36 :: Attempting to authenticate...
2009/02/03 17:06:38 :: Putting interface up...
2009/02/03 17:06:41 :: Setting static IP : 192.168.2.44
2009/02/03 17:06:41 :: Setting default gateway : 192.168.2.1
2009/02/03 17:06:41 :: Connecting thread exiting.
2009/02/03 17:46:09 :: setting use global dns to 1
2009/02/03 17:46:09 :: setting use global dns to boolean True
2009/02/03 17:46:09 :: setting global dns
2009/02/03 17:46:09 :: global dns servers are 68.13.52.60 68.13.52.61
2009/02/03 17:46:09 :: setting wireless interface wlan0
2009/02/03 17:46:09 :: setting wired interface
2009/02/03 17:46:09 :: setting wpa driver ndiswrapper
2009/02/03 17:46:09 :: setting automatically reconnect when connection drops
2009/02/03 17:46:09 :: Setting dhcp client to 0
2009/02/03 17:46:15 :: Connecting to wireless network 69Wireless70
2009/02/03 17:46:15 :: Putting interface down
2009/02/03 17:46:15 :: Releasing DHCP leases...
2009/02/03 17:46:15 :: Setting false IP...
2009/02/03 17:46:16 :: Stopping wpa_supplicant and any DHCP clients
2009/02/03 17:46:16 :: Flushing the routing table...
2009/02/03 17:46:16 :: Generating psk...
2009/02/03 17:46:16 :: Attempting to authenticate...
2009/02/03 17:46:18 :: Putting interface up...
2009/02/03 17:46:21 :: wpa_supplicant rescan forced...
2009/02/03 17:46:25 :: wpa_supplicant rescan forced...
2009/02/03 17:46:29 :: wpa_supplicant rescan forced...
2009/02/03 17:46:33 :: wpa_supplicant rescan forced...
2009/02/03 17:46:37 :: wpa_supplicant rescan forced...
2009/02/03 17:46:41 :: wpa_supplicant rescan forced...
2009/02/03 17:46:45 :: wpa_supplicant rescan forced...
2009/02/03 17:46:49 :: wpa_supplicant rescan forced...
2009/02/03 17:46:53 :: wpa_supplicant rescan forced...
2009/02/03 17:46:57 :: wpa_supplicant rescan forced...
2009/02/03 17:47:01 :: wpa_supplicant rescan forced...
2009/02/03 17:47:05 :: wpa_supplicant rescan forced...
2009/02/03 17:47:09 :: wpa_supplicant rescan forced...
2009/02/03 17:47:13 :: wpa_supplicant rescan forced...
2009/02/03 17:47:17 :: wpa_supplicant rescan forced...
2009/02/03 17:47:20 :: canceling connection attempt
2009/02/03 17:47:20 :: exiting connection thread
2009/02/03 17:48:07 :: Connecting to wireless network 69Wireless70
2009/02/03 17:48:07 :: Putting interface down
2009/02/03 17:48:07 :: Releasing DHCP leases...
2009/02/03 17:48:07 :: Setting false IP...
2009/02/03 17:48:09 :: Stopping wpa_supplicant and any DHCP clients
2009/02/03 17:48:09 :: Flushing the routing table...
2009/02/03 17:48:09 :: Generating psk...
2009/02/03 17:48:09 :: Attempting to authenticate...
2009/02/03 17:48:09 :: Putting interface up...
2009/02/03 17:48:12 :: wpa_supplicant rescan forced...
2009/02/03 17:48:16 :: wpa_supplicant rescan forced...
2009/02/03 17:48:20 :: wpa_supplicant rescan forced...
2009/02/03 17:48:24 :: wpa_supplicant rescan forced...
2009/02/03 17:48:28 :: wpa_supplicant rescan forced...
2009/02/03 17:48:32 :: wpa_supplicant rescan forced...
2009/02/03 17:48:36 :: wpa_supplicant rescan forced...
2009/02/03 17:48:40 :: wpa_supplicant rescan forced...
2009/02/03 17:48:44 :: wpa_supplicant rescan forced...
2009/02/03 17:48:48 :: wpa_supplicant rescan forced...
2009/02/03 17:48:52 :: wpa_supplicant rescan forced...
2009/02/03 17:48:56 :: wpa_supplicant rescan forced...
2009/02/03 17:49:00 :: wpa_supplicant rescan forced...
2009/02/03 17:49:04 :: wpa_supplicant rescan forced...
2009/02/03 17:49:08 :: wpa_supplicant rescan forced...
2009/02/03 17:49:12 :: wpa_supplicant rescan forced...
2009/02/03 17:49:16 :: wpa_supplicant rescan forced...
2009/02/03 17:49:20 :: wpa_supplicant rescan forced...
2009/02/03 17:49:24 :: wpa_supplicant rescan forced...
2009/02/03 17:49:28 :: wpa_supplicant rescan forced...
2009/02/03 17:49:32 :: wpa_supplicant rescan forced...
2009/02/03 17:49:36 :: wpa_supplicant rescan forced...
2009/02/03 17:49:40 :: wpa_supplicant rescan forced...
2009/02/03 17:49:44 :: wpa_supplicant rescan forced...
2009/02/03 17:49:48 :: wpa_supplicant rescan forced...
2009/02/03 17:49:52 :: wpa_supplicant rescan forced...
2009/02/03 17:49:57 :: wpa_supplicant rescan forced...
2009/02/03 17:50:08 :: Connecting to wireless network 69Wireless70
2009/02/03 17:50:08 :: Putting interface down
2009/02/03 17:50:08 :: Releasing DHCP leases...
2009/02/03 17:50:08 :: Setting false IP...
2009/02/03 17:50:09 :: Stopping wpa_supplicant and any DHCP clients
2009/02/03 17:50:09 :: Flushing the routing table...
2009/02/03 17:50:09 :: Generating psk...
2009/02/03 17:50:09 :: Attempting to authenticate...
2009/02/03 17:50:10 :: exiting connection thread
2009/02/03 17:50:11 :: Putting interface up...
2009/02/03 17:50:14 :: wpa_supplicant rescan forced...
2009/02/03 17:50:18 :: wpa_supplicant rescan forced...
2009/02/03 17:50:22 :: wpa_supplicant rescan forced...
2009/02/03 17:50:26 :: wpa_supplicant rescan forced...
2009/02/03 17:50:30 :: wpa_supplicant rescan forced...
2009/02/03 17:50:31 :: canceling connection attempt
2009/02/03 17:50:31 :: exiting connection thread
2009/02/03 17:51:02 :: setting use global dns to 1
2009/02/03 17:51:02 :: setting use global dns to boolean True
2009/02/03 17:51:02 :: setting global dns
2009/02/03 17:51:02 :: global dns servers are 68.13.52.60 68.13.52.61
2009/02/03 17:51:02 :: setting wireless interface wlan0
2009/02/03 17:51:02 :: setting wired interface
2009/02/03 17:51:02 :: setting wpa driver ndiswrapper
2009/02/03 17:51:02 :: setting automatically reconnect when connection drops
2009/02/03 17:51:02 :: Setting dhcp client to 0
2009/02/03 17:52:54 :: Connecting to wireless network 69Wireless70
2009/02/03 17:52:54 :: Putting interface down
2009/02/03 17:52:54 :: Releasing DHCP leases...
2009/02/03 17:52:54 :: Setting false IP...
2009/02/03 17:52:56 :: Stopping wpa_supplicant and any DHCP clients
2009/02/03 17:52:56 :: Flushing the routing table...
2009/02/03 17:52:56 :: Generating psk...
2009/02/03 17:52:56 :: Attempting to authenticate...
2009/02/03 17:52:56 :: Putting interface up...
2009/02/03 17:52:59 :: wpa_supplicant rescan forced...
2009/02/03 17:53:03 :: wpa_supplicant rescan forced...
2009/02/03 17:53:07 :: wpa_supplicant rescan forced...
2009/02/03 17:53:11 :: wpa_supplicant rescan forced...
2009/02/03 17:53:15 :: wpa_supplicant rescan forced...
2009/02/03 17:53:19 :: wpa_supplicant rescan forced...
2009/02/03 17:53:23 :: wpa_supplicant rescan forced...
2009/02/03 17:53:27 :: wpa_supplicant rescan forced...
2009/02/03 17:53:31 :: wpa_supplicant rescan forced...
2009/02/03 17:53:35 :: wpa_supplicant rescan forced...
2009/02/03 17:53:39 :: wpa_supplicant rescan forced...
2009/02/03 17:53:43 :: wpa_supplicant rescan forced...
2009/02/03 17:53:47 :: wpa_supplicant rescan forced...
2009/02/03 17:53:51 :: wpa_supplicant rescan forced...
2009/02/03 17:53:55 :: wpa_supplicant rescan forced...
2009/02/03 17:53:59 :: wpa_supplicant rescan forced...
2009/02/03 17:54:03 :: wpa_supplicant rescan forced...
2009/02/03 17:54:07 :: wpa_supplicant rescan forced...
2009/02/03 17:54:11 :: wpa_supplicant rescan forced...
2009/02/03 17:54:15 :: wpa_supplicant rescan forced...
2009/02/03 17:54:19 :: canceling connection attempt
2009/02/03 17:54:19 :: exiting connection thread

I hope there's a clue in there. I use fixed IP addresses for everything on my network and do not use DHCP.
--GrannyGeek
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: pevsner on February 03, 2009, 07:04:31 pm
Re: wine fonts.
Quote
Did you try this? At a terminal prompt, type
winecfg as use
desktop integration etc.

GrannyGeek, yes I always do that cause the fonts are so small on default setting (usually go for veranda font-which is installed ok).
On VL6 they still appear flakey/faint. Where perfect on 5.9.
Nvidia GF 6200 - 173.xx vl driver
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: Pita on February 03, 2009, 07:28:21 pm
Made a CD installation of RC4.2 with GUI installer.  :P

After installation completed click NEXT. Took a long time beforte something came up. I thought it had hung.
Up came asking for the boot installer. Clicked do not install Lilo, NEXT and a window told me something is wrong and the installation was aborted.

My MBR was destroyed had to boot from a CD, did Lilo and it was fixed.

This time installed w/o GUI. All went smooth. Internet connected, music playing.

Dillo shows black pages.

Can't install my printer. Device : unknow:USB missing. Did not switch it on on booting. Might try later.

Opera is huge. Can't grip corners. Can make it smaller only after shading.

Later, booted with printer switched-on, still no Device : unknow:USB. Too bad! :(

On panel gslapt updater was showing. Clicked on it, gslapt opened and at least 4 programs were updated. Very nice! :D
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: InTheWoods on February 04, 2009, 06:38:39 am
Toshiba Tecra
1.6GHz processor
510mb ram

I used the vlinstall-iso script for a text install. The option to enable touchpad specific features disables the ability to use a tap as a left click on the touchpad. Configuring as normal mouse allows the touchpad to function normally.

wireless in the vasm control centre does work but does not survive a reboot.
vwifi-connect does not work
wcid does not work
wcid 1.5.8 from Robby's Slackware http://rlworkman.net/pkgs/12.2/wicd-1.5.8-noarch-1_rlw.tgz packages does work and the settings survive a reboot.
run: wicd-client
I have'nt tried the new wcid package in the repository.

I did not realize there was a G-slapt updater. It's NOT a good thing for my laptop!!!
An accidental click over this seemed to reinstall everything and I think it over filled the partition I had alloted to test RC4 as I could no longer use it.

In the menu the first item under system "Avahi Zeroconf Browser" I get a small window which disappears imediately after it appears. Under "Network" are the related Avahi SSH, and VNC browser items. Clicking on either of these yeilds an error message "Failed to connect to Avahi server:Daemon not running" In the background a box appears showing Avahi "initializing". dismissing the error message closes the background box as well.

My GeForce FX Go5200 runs fine with the included NVIDIA drivers.

Firefox in vec6.0rc4 is very fast compared to in vec5.9 standard. I've had one lock up which resolved itself in 30sec unlike the hard lockups in vec5.9 wich required a reboot (disconnect the power and remove the battery) to use the computer.
Opera works well here. No issues with size (1024x768 resolution) or usability. However I have'nt updated Abiword or anything.
EDIT:updated Abiword and Opera continues to function fine. Updated all of the related AbiWord packages and it continues to be fine.

It's been a while since I've been around. Nice work!!!
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: fox on February 04, 2009, 05:47:28 pm

I mentioned earlier that with RC4 as a virtual machine on VirtualBox (version 2.1.2), Orage-Clock, installed by default on the panel, doesn't update to the proper date and time after a vm state was saved and revived later, and that even restarting the vm doesn't fix the problem. I now believe it is either a VL problem or a problem with VL in conjunction with VirtualBox, because another distro I installed as a vm on VirtualBox doesn't display the same symptoms.  I checked the VirtualBox settings for the two vm's, and they are the same, eliminating the setting as the cause. Furthermore, installing VL6 RC4 on VMware Fusion on my Mac doesn't result in the same problem.  (I'll report on that venture in another posting.)

What seems to be happening is the clock is working, but not synchronizing when I suspend the vm.  Any idea what could be wrong?
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: fox on February 04, 2009, 06:13:46 pm
Hello Fox,
...I've had 5.8, 5.9, and 6, rc2, rc3 working fine in VirtualBox - haven't tried RC4 yet, because I'm probably just going to install it straight to the drive.  I agree with you on VMware - it's a bit of a dog - gave up on it some time ago.
Actually, Howard, my experience with VMware Fusion (2.0.1) on a Mac host with a Linux guest has been pretty good, even with the newer kernels.  Every Debian-based distro I've tried works well.  So does the latest Mandriva and openSUSE 11.0, but not 11.1.  And when I say "works well", I mean that all the tools work, including drag and drop of files between host and guest.  This is the real beauty of VMware Fusion, because it's a very useful feature that no other virtual program can do with a Linux guest.

I thought it was time to try VMware with VL6 RC4.  The results were better than I expected.  The tools were easier to install on it than on any other distro, and all of them seem to work reliably with one partial exception - drag and drop.  It's 100% going from guest to host and it works fine the other way right after installing the tools, but once you reboot, host to guest no longer works until you reinstall the tools.  That's not as bad as it sounds because there's no need to restart the vm again unless a kernel update requires it.  And suspending the vm state and then reviving doesn't affect functionality.  There is one other minor glitch - when you go to suspend the vm state you have to do it from menu or with a cmd-Q rather than from the Fusion suspend icon, the latter gives a script error message.  I don't know what that's about, but the alternative methods of suspending the vm are just as easy, so no big deal.  VMware Fusion is overdue for a bug fix, but even without one, running VL6 RC4 on it is quite good, and better than running it on VirtualBox.  Video is smoother on Fusion as well.

One other interesting observation that may or may not be distro-specific.  My music is stored on iTunes and most of it is in mp4 (AAC) format.  My favourite music player in Linux is Rhythmbox, which I did try on RC4. To play mp4's on RC4's Rhythmbox, you have to install additional gstreamer codecs (bad and ugly), and unlike Ubuntu, you aren't helped along by an offer to get these from RC4-Rhythmbox.  But here is what I found interesting.  Install Amarok instead of Rhythmbox and you can play everything without fetching additional codecs.

So far I like what I see and I really like the helpfulness and friendliness on this forum.  All this makes me keen on VectorLinux, so I'll keep testing this RC.  :)

P.S. Thanks for putting R in the repository, Dave.  I got it on my office Mac by compiling, but now that I know how to use vpackager, I'm happy to install it from the repo on my home Mac.
-- Update: R wasn't in the repository yet (so I compiled again; no problem).
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: Lyn on February 05, 2009, 01:32:53 am
It might be worth mentioning that my problems with my i810 graphics causing X to crash  when launching terminal applications or launching a terminal only occurs in XFCE and not in other window managers/environments.  This is identical to the issues I had with Vector 5.9 standard but which was corrected when we got to the later release candidates.  Is it possible to fix this?  I intend to keep this lower powered machine as a testing rig and to teach myself how to build packages.  The intent is to keep it as clean as possible and build individual packages and then reinstall from scratch.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: kc1di on February 05, 2009, 03:13:00 am

P.S. Thanks for putting R in the repository, Dave.  I got it on my office Mac by compiling, but now that I know how to use vpackager, I'm happy to install it from the repo on my home Mac.

Your quite welcome Enjoy. Vector is a very good Distro.
Dave

Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: uelsk8s on February 05, 2009, 06:53:31 am
It might be worth mentioning that my problems with my i810 graphics causing X to crash  when launching terminal applications or launching a terminal only occurs in XFCE and not in other window managers/environments.  This is identical to the issues I had with Vector 5.9 standard but which was corrected when we got to the later release candidates.  Is it possible to fix this?  I intend to keep this lower powered machine as a testing rig and to teach myself how to build packages.  The intent is to keep it as clean as possible and build individual packages and then reinstall from scratch.
Is the same terminal being used in each WM?
does X crash if you use urxvt or xterm in XFCE?
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: fox on February 05, 2009, 08:12:41 am
I found a new bug with the music player, rhythmbox.  After installing it from the repository (tried two ways, with gslapt and slapt-get), the application won't start up from either the menu or by typing its name in a terminal.  With the former, nothing happens.  With the latter, I get the following error message:

"rhythmbox: error while loading shared libraries: libcamel-1.2.so.11: cannot open shared object file: No such file or directory"

This occurs when running RC4 as a vm on VMware Fusion.  I was able to replicate the problem on two different Intel Macs.  However, I installed rhythmbox initially on a vm created with VirtualBox, and in this case, the application starts up and works.  I'm guessing that this is a coincidence, and that something I installed prior to rhythmbox on my VirtualBox vm must have satisfied this dependency.  I did check the repository for libcamel, but didn't find it.

Suggestions anyone?

P.S. rhythmbox 0.11 in the repository is not the stable version according to the application website; it's version 0.10.  I did try downloading it and building it with vpackager, but I got an error.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: Lyn on February 05, 2009, 09:27:41 am
Is the same terminal being used in each WM?
does X crash if you use urxvt or xterm in XFCE?


Looks as if it is just xterm
If I run urxvt no crash, if I launch a terminal application like Htop from urxvt no crash... :-)

Same no crash with xterm or urxvt in LXDE
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: caitlyn on February 05, 2009, 10:12:39 am
Fox:  How did you install rhythmbox?  Did you use slapt-get or gslapt to get all the dependencies?  The error you describe indicates a missing dependency. 

I just installed rhythmbox using slapt-get and it works perfectly here.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: Joe1962 on February 05, 2009, 12:19:49 pm
Thunar is crashing  lot when right-clicking in it, but sometimes after right-click / Properties. No idea what the cause could be as it is pretty random. This is a pretty clean install of RC4, with a few apps updated from the repo, but I think the issue was happening from the get go. Anybody else seeing this?
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: MikeCindi on February 05, 2009, 12:42:53 pm
Thunar is crashing  lot when right-clicking in it, but sometimes after right-click / Properties. No idea what the cause could be as it is pretty random. This is a pretty clean install of RC4, with a few apps updated from the repo, but I think the issue was happening from the get go. Anybody else seeing this?

This happens frequently as you have described which I assumed was a Thunar issue vs. VL. I haven't pursued it as I often just use MC.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: fox on February 05, 2009, 01:08:30 pm
Fox:  How did you install rhythmbox?  Did you use slapt-get or gslapt to get all the dependencies?  The error you describe indicates a missing dependency. 

I just installed rhythmbox using slapt-get and it works perfectly here.
caitlyn, I tried it both ways and the result was the same.  Is one of these methods different from the other in handling dependency issues?  I can tell you that it downloaded a lot more than just rhythmbox, but it didn't download the file, libcamel-1.2.so.11.  There also doesn't seem to be a libcamel in the repository.  I've done a Google search for libcamel and came up with other distro problems involving this missing file, and also rpm-packaged versions of it, but not the source file.  Is there a way to install rpm's in VectorLinux?
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: StrayBit on February 05, 2009, 01:16:13 pm
Finally got RC4 installed.  I copied the lilo.conf entry to the 5.9 lilo and was able to boot into it and finish installation.  It came up with no ethernet - I've posted that under Networking
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: caitlyn on February 05, 2009, 01:18:55 pm
StrayBit:  Please post that here.  RC problems go in the bug thread for the release.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: StrayBit on February 05, 2009, 02:02:25 pm
Thanks Caitlyn.  I just need to remember to restart to get into 6.0 BEFORE i issue the commands  Undecided
Quote
root:# /sbin/modprobe e100
FATAL: Could not load /lib/modules/2.6.22.14/modules.dep: No such file or directory
compaq:/~
root:# /etc/rc.d/rc.network restart
Setting up basic network ...compaq:/~
The only directory in modules is 2.6.27.12 which does have that file.

Opps!  I just saw your reply in Distor Developement and am copying it there.  I really did think, at the time that this was my problem.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: uelsk8s on February 05, 2009, 02:06:11 pm
Thanks Caitlyn.  I just need to remember to restart to get into 6.0 BEFORE i issue the commands  Undecided
Quote
root:# /sbin/modprobe e100
FATAL: Could not load /lib/modules/2.6.22.14/modules.dep: No such file or directory
compaq:/~
root:# /etc/rc.d/rc.network restart
Setting up basic network ...compaq:/~
The only directory in modules is 2.6.27.12 which does have that file.

Opps!  I just saw your reply in Distor Developement and am copying it there.  I really did think, at the time that this was my problem.
for some reason the kernel from 5.9 is being used to boot your 6.0-RC4 install.
after you boot into 6.0 run vliloconf and it should fix it.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: StrayBit on February 05, 2009, 03:05:17 pm
Hmm!  5.9 didn't object that only partion 3 was marked bootable. 1 (6.0 /) and 2 (5.9 /) were not.  6.0 objects:
Quote
root:# fdisk /dev/hda

The number of cylinders for this disk is set to 1653.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/hda: 13.6 GB, 13601193984 bytes
255 heads, 63 sectors/track, 1653 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x6a910f06

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *         695        1270     4626720   83  Linux
/dev/hda2   *         186         694     4088542+  83  Linux
/dev/hda3   *           1         185     1485981   83  Linux
/dev/hda4            1271        1653     3076447+   5  Extended
/dev/hda5            1336        1653     2554335   83  Linux
/dev/hda6            1272        1335      514048+  82  Linux swap

Partition table entries are not in disk order

Command (m for help): q

compaq:/~
root:# lilo -v
LILO version 22.8, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 19-Feb-2007 and compiled at 02:39:03 on Apr  1 2008.

Warning: LBA32 addressing assumed
Reading boot sector from /dev/hda1
Warning: Device 0x0300: Inconsistent partition table, 1st entry
  CHS address in PT:  694:0:1  -->  LBA (10493280)
  LBA address in PT:  11149110  -->  CHS (737:90:1)
Fatal: Either FIX-TABLE or IGNORE-TABLE must be specified
If not sure, first try IGNORE-TABLE (-P ignore)
lilo - v IGNORE-TABLE didn't work - lilo didn't like it!
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: Windozer on February 05, 2009, 06:19:50 pm
Thunar is crashing  lot when right-clicking in it, but sometimes after right-click / Properties. No idea what the cause could be as it is pretty random. This is a pretty clean install of RC4, with a few apps updated from the repo, but I think the issue was happening from the get go. Anybody else seeing this?


Yes, Joe, but not a lot - it seems related to what I mentioned earlier about icons showing up without their details in the Thunar right-side window/panel.

- H
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: uelsk8s on February 05, 2009, 06:24:45 pm
Hmm!  5.9 didn't object that only partion 3 was marked bootable. 1 (6.0 /) and 2 (5.9 /) were not.  6.0 objects:
Quote
root:# fdisk /dev/hda

lilo - v IGNORE-TABLE didn't work - lilo didn't like it!
I think it is something like "lilo -vP"  or you can add "ignore-table" to lilo.conf
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: caitlyn on February 05, 2009, 07:45:05 pm
fox:  There is no difference between slapt-get and gslapt.  gslapt is just a GUI front end for slapt-get. 

Yes, you can install rpms into Vector Linux but that is the LAST thing you want to do in this case.  Installing from third party sources breaks dependency tracking and the package database on your system won't know about it.
Any file ending in .so.1 is a part of a package but not a package itself.  Somehow you are missing a dependency and I don't know how that happened.

My advice: 

1. Uninstall rhythmbox using gslapt. 
2. Make sure you have all of the following repositories enables:
packages, extra, patches, gsb, testing

Normally you wouldn't want testing enabled but in this case I want to make sure something you need isn't still in testing.  Also, I had testing enabled when I installed and it worked.

3.  Click the Update icon to refresh your package list from the repos.
4.  Reinstall rhythmbox using gslapt.

See if that works.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: fox on February 06, 2009, 03:26:15 am
My advice: 
1. Uninstall rhythmbox using gslapt. 
2. Make sure you have all of the following repositories enables:
packages, extra, patches, gsb, testing
3.  Click the Update icon to refresh your package list from the repos.
4.  Reinstall rhythmbox using gslapt.
See if that works.
Unfortunately, there was no change and I got the same error.  Is there anything further I should try, or should I just assume it's a bug that one of the maintainers will eventually try to fix?
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: uelsk8s on February 06, 2009, 06:50:25 am
My advice: 
1. Uninstall rhythmbox using gslapt. 
2. Make sure you have all of the following repositories enables:
packages, extra, patches, gsb, testing
3.  Click the Update icon to refresh your package list from the repos.
4.  Reinstall rhythmbox using gslapt.
See if that works.
Unfortunately, there was no change and I got the same error.  Is there anything further I should try, or should I just assume it's a bug that one of the maintainers will eventually try to fix?
make sure you have totem and totem-pl-parser installed.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: stretchedthin on February 06, 2009, 11:22:15 am
Very, Very, impressed.  Just put rc4.3 on to an Acer Aspire1 and so far it is outstanding.
1. The gui installer screen was bigger than the actual screen but showed everything as I moved the mouse.
2. Both my sd card slots work.
3. wxCam already installed and works perfectly.
4. Response of thunar seems much snappier so far.

One thing I noticed is a carry over from before. VL-HOT-Config launches from the main menu, but not from the launcher on the panel.

Command in panel launcher is this.../sbin/vsuper /sbin/vl-hot-config.gambas
I think it should be /sbin/vsuper vl-hot-config.gambas

Thats all for now.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: fox on February 06, 2009, 11:26:19 am
Both totem and totem-pl-parser had been previously installed, uelsk8s.  But I did try something else that at least got rhythmbox partly operational - I installed a bunch of gnome files (ones that I guessed could be connected - gnome-applets, gnome-common, gnome-desktop, gnome-do, gnome-do-plugins, gnome-media, gnome-menus, gnome-menus-xfce, gnome-panel).  Following the installation of these files, rhythmbox would start up, although it gave plugin errors for cover art and jamendo, which it still couldn't load.  It plays my music and radio, but there seems to be a long delay when music is switched until it starts playing.  I downloaded Banshee and noticed the same thing.

There seems to be something universal about Amarok - it always works as it should in any distro.  Plays all music with no delays in VL; I just prefer rhythmbox.

One other question.  Having loaded all those gnome files, I expected to have the option to actually run gnome, but that option wasn't present in the startup panel.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: Joe1962 on February 06, 2009, 11:41:55 am
One thing I noticed is a carry over from before. VL-HOT-Config launches from the main menu, but not from the launcher on the panel.

Command in panel launcher is this.../sbin/vsuper /sbin/vl-hot-config.gambas
I think it should be /sbin/vsuper vl-hot-config.gambas

Indeed, vl-hot-config.gambas is in /bin, not /sbin. Also, you can call it without vsuper now.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: StrayBit on February 06, 2009, 02:51:52 pm
Making progress - I think! Lilo did NOT like -vP (wanted a number) so I put ignore-table in lilo.conf
Quote
compaq:/~
root:# lilo -v
LILO version 22.8, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 19-Feb-2007 and compiled at 02:39:03 on Apr  1 2008.

Warning: LBA32 addressing assumed
Reading boot sector from /dev/hda1
Warning: Device 0x0300: Inconsistent partition table, 1st entry
  CHS address in PT:  694:0:1  -->  LBA (10493280)
  LBA address in PT:  11149110  -->  CHS (737:90:1)
Warning: The partition table is *NOT* being adjusted.
Using BITMAP secondary loader
Calling map_insert_data
Mapping bitmap file /boot/bitmap/boot.bmp -> std.bmp
Calling map_insert_file

Boot image: /boot/vmlinuz -> vmlinuz-2.6.27.12
Fatal: read /boot/vmlinuz: No such file or directory
/boot/vmlinuz-2.6.27.12 exists but it has 0 bytes ((VL5.9's vmlinuz-2.6.22.14 has 4.0MB)
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: uelsk8s on February 08, 2009, 12:48:39 pm
Quote
/boot/vmlinuz-2.6.27.12 exists but it has 0 bytes ((VL5.9's vmlinuz-2.6.22.14 has 4.0MB)
you can either get the kernel from the ISO it is isolinux/kernel/sata or you can grab it from this pkg: http://vectorlinux.osuosl.org/veclinux-6.0/kernels/kernel-2.6.27.12-i686-1vl60.tlz
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: CrazyDog on February 09, 2009, 08:18:02 am
I wonder if anyone has been able to reproduce my firewall problem.  Under the GUI for the firewall I select "enable firewall at boot" and then "start firewall".  The next boot, the system freezes at "starting firewall".
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: stretchedthin on February 09, 2009, 02:13:30 pm
CrazyDog, I thought I would run a comparison for you.  I'm using RC4.6 so we may not be a direct comparison.
Anyway, I 'enabled firewall at boot' and rebooted.  I did not freeze at starting firewall, but booted to the login screen as normal.  I did have to stop the firewall, however, as I was unable to connect to any website with it on.

I then did it exactly as you described <quote> "enable firewall at boot" and then "start firewall".</quote> Then rebooted.
Same result as above, no freeze.  Sorry, I can't help any further. I've never been a user of the firewall function in VASM.



Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: CrazyDog on February 09, 2009, 02:27:40 pm
Thanks for running the comparison.  I accidentallt left out a step I was doing (sorry) - I was first clicking on "create a new firewall", then "start firewall" and then "enable firewall at boot".  If you don't mind, give this a try and see what happens.

Thanks a lot for your help-
CrazyDog
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: stretchedthin on February 09, 2009, 02:55:10 pm
I know by the time I right this you guys will have RC4.7 ready for download but what the hell.  I've just had time to put RC4.6 on one machine and it would be easy to rave gushingly about it, but I'll save that for the final release. For now I'll stick to my tester duties.

Just to let you know, everything loaded. rc4.3 firefox would not load during install, rc4.4-rc4.5, bluefish and something else would not load during install, but with rc4.6 everything loads just fine.

1. When I click 'Utilities' in vasmCC it raises and error.  "This application has raised an unexpected error and must abort"
2. I use the nvidia 180.22 drive in two machines.  One for my desktop which uses a nVidia Corporation GeForce 7300 GT *(rev a2).  The other a laptop that uses a Nvidia corportation g72m [Quodro nvs 110m/ Gforce Go 7300] (rev a1)
The desktop sets up the nividia driver beautifully at 1280*1024.  The laptop which has a res of 1440*900 installs but crashes when launching x with the nvidia driver.  I can, however, us nv with no difficulties.  I can even use the downloaded 180.22 driver from NVIDIA's site, so the driver works, just not when it is set up by the installer.  (I used the gui installer--for some reason the text installer does not see my ubuntu partition.)
3.    I'm running 6.0 light beta 2 on another system.  From that OS I can select 'vlsmbmnt' from the menu as 'Windows Networking'  I rescan, enter nothing as a password, select my share from the mythbuntu computer upstairs, enter just my normal user name and password and I am watching my recorded tv just like that.
       But on VL6.0 RC4.6 when I run Vector Linux Samba Network, after I select my share from the list and enter my username and password I get an error message....
This is what it says in the terminal...
Warning: Tried to connect to session manager, Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
Mounting [\\KENNAZ-DESKTOP\recordings] at [/root/mnt/KENNAZ-DESKTOP-recordings]
mount error: could not find target server. TCP name KENNAZ-DESKTOP/recordings not found
No ip address specified and hostname not found

4. VL-hot-config's command in the launcher on the panel needs to be changed from /sbin/vsuper /sbin/vl-hot-config.gambas to /sbin/vsuper vl-hot-config.gambas

I'm going to try rc4.6 on my desktop and aspire1 next.  Oh and outstanding work on the netbook compatibility.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: stretchedthin on February 09, 2009, 03:05:27 pm
Thanks for running the comparison.  I accidentallt left out a step I was doing (sorry) - I was first clicking on "create a new firewall", then "start firewall" and then "enable firewall at boot".  If you don't mind, give this a try and see what happens.

Thanks a lot for your help-
CrazyDog

Yup that made the difference.  I'm frozen on 'Setting Up Firewall' just as you described.  I choose create a new firewall then 'enable firewall at boot' and then VASM disappeared and I was not able to choose 'start firewall'. I then reboot and here I am frozen on 'Setting Up Firewall".  Guess I'm reinstalling, unless you know of a clever way out of this.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: caitlyn on February 09, 2009, 03:55:45 pm
Boot in single user mode and the firewall won't load.  You can then change the settings to avoid the lockup.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: stretchedthin on February 09, 2009, 04:13:28 pm
Thanks Caitlyn; and nice work by the way on wxCam, even better that it's part of the install. 
Another positive I can report for rc4.6 is that my slapt-update-notifyer is working from a gui install.  First time for me.
Ken
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: CrazyDog on February 09, 2009, 04:19:50 pm
Thanks for the info on the firewall but I'm not sure how to boot into single-user mode.  Also, is this a bug or am I setting up my firewall wrong?

Thanks Again!
CrazyDog
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: vector on February 09, 2009, 04:40:40 pm
Quote
Also, is this a bug or am I setting up my firewall wrong?

Yep it's a bug thanks for pointing it out Crazydog. Glad we found it now not after final................... :)

Vec
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: nightflier on February 09, 2009, 04:48:46 pm
Thanks for the info on the firewall but I'm not sure how to boot into single-user mode.

On your initial boot menu, try the "TUI" option.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: CrazyDog on February 09, 2009, 04:52:30 pm
Thanks so much for the response guys/gals.   That is one of the reasons I will stay with Vector.  It's the people that make the distro what it is.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: edgeofthewoods on February 11, 2009, 07:28:34 pm
So far only 3 minor items with RC4, 2 have been solved, the HPLIC and the network issues. Just started using k3B to burn dvd iso's This one gives an error but no output from CLI nor anything. Exactly 50% of the time whenI try to burn a DVD iso the entire system locks up. CTRL ALT BACKSPACE does try to restart X but the system will eventually not respond. No mouse, no CTRL ALT DELETE. It takes a hard power off to restart. Now after reboot K3Bburns a DVD iso fine. I thought it was a K3B issue but the same in Gnome Baker. Any ideas?
Plus any estimate when 6.0 GOLD will be turned loose?
Edited to add:

New one cropped up today.
 
Code: [Select]
Could not look up internet address for vector.linux..net.
This will prevent Xfce from operating correctly.
It may be possible to correct the problem by adding
vector.linux..net to the file /etc/hosts on your system.
I never got around to changing the name of the machine after I put in 6.0. Today this error pooped up. I hit continue and things go smooth. here is my /etc/hosts file
Code: [Select]
#
# hosts This file describes a number of hostname-to-address
# mappings for the TCP/IP subsystem.  It is mostly
# used at boot time, when no name servers are running.
# On small systems, this file can be used instead of a
# "named" name server.  Just add the names, addresses
# and any aliases to this file...
#
# By the way, Arnt Gulbrandsen <agulbra@nvg.unit.no> says that 127.0.0.1
# should NEVER be named with the name of the machine.  It causes problems
# for some (stupid) programs, irc and reputedly talk. :^)
#

# For loopbacking.
127.0.0.1 localhost
# This next entry is technically wrong, but good enough to get TCP/IP apps
# to quit complaining that they can't verify the hostname on a loopback-only
# Linux box.
127.0.0.1   vector.linux.net vector

# End of hosts.

Chuck
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: StrayBit on February 12, 2009, 08:47:12 pm
I finally broke down and DL'd a newer RC4, moved partitions around, and after a couple of tries (partition too small!!), the hosted install went with a glitch.  Got it to the point that Win98 could copy files from it.  In the middle of the copy, though, things went crazy: my local LAN seemed to be inoperative.  A little later, I found that /etc/exports was in its pristine condition!  I had 5 entries in it!  I doubt that this is a VL issue, however, as I had similar things happen to other files in VL5.9 Gold - the latest was to disable my user logins.  And it wasn't because I was sharing home between two versions as I did on the other machine.  I haven't checked yet but I surmise the same thing caused 5.9Live installed on another partition lost the ability to use the mouse wheel - no, the ZAxisMapping option is still in xorg.conf!
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: blurymind on February 13, 2009, 09:18:24 am
absolutely beautiful job on the installer !

I gave this release a spin and i am blown by its quality. The installer is both amazingly clean and effective ...but it seems quite stable. I've tested wether it would crash if i play around with it and i even teased it by doing things that some people wouldnt ordinarily do- after going through some settings,like adding users, going backward and forward through the steps. Not a hitch.
I was charmed by the network configuration step- not only did it give me a very nice and organised,simple menu to set it, but it also figured out which eth the network cable was plugged in !in the past this has been a nag for me to figure out which eth needs to be set,because in many distros its always changing the numbers of my two network adapters.Specially the vl 5* versions used to have the bug of constantly swapping eth0 and eth1- that always made me mad whenever i had to install vector.Now this bug seems to be elliminated for good.
 What really amazed me is the hidden menu,where i found that great collection of good old games,such as gallaga,tetris and space invaders (btw i found space invader in chakra linux installer a while ago- an arch spinoff).
I loved that..it should be default for all installers out there. Awesome idea- made the waiting enjoyable. =)

Only at the last step of the install, the installer seemed to freeze,or just take too long,so i killed it and restarted from the menu. That didnt seem harm my installation,i didnt get any ill messages while booting

The one single problem that i've always had with vector linux is gone- internet worked out of the box and i saw that configuration is not as frustrating as it used to be in the past. Strangely- wicd couldnt pick my curent network settings,which i've put during installation.But that didnt stop internet from working.So i disabled wicd,thinking that it will work great for my brother's eee pc (he can't live without wifi)..

GRAPHICS:
I loved the design of the installer.The only thing that i though was kind of ugly were the green,yellow and red circles that indicated the steps.They look kind of out of place. If you give me the specs (filetype,size) i could try to make alternative versions for those files.

The default theme in VL6 is very nice to the eyes. The wallpaper is just beautiful.The icon theme- perfect. Everything seems to fit in one polished picture.Very very nice. color theme is awesome!

THINGS THAT NEED SOME ATTENTION:

FT associations in thunar and pcmanfm:
some of the standart image filetypes. Gif files should not be opened with gimp by default.Also Gqview can not handle animated gif files and shows them as still images. ristretto or Mirage can render animated gif files , and is as simple and lightweight as gqview.I think that it should be included in the xfce package if possible.
Same goes for PNG files- they shouldnt be opened by default with the gimp. (btw thanks for including such an up-to-date version of the gimp this time)

The size of the xfce4-panel.I thought it was huge. If that would make VL look better on other resolutions other than mine,good choice.

this is what i can say for now. I will post if i encounter any bugs!
Btw where is the installer's log file?
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: blurymind on February 14, 2009, 01:48:57 pm
when wicd is disabled,internet does not work at all. I dont mind having it run, but its just that some might not like having it in their tray all the time. Other than that,the option to disable it from starting does work,but causes the internet to stop working on login.
I love wicd- its sooo much better than what vector used to have for configuring internet.

xlock does not really lock the screen.One can press enter without writing any password.That way VL does not have a possible option to lock the desktop.

ctrl+alt+esc (xkill) does not really kill a process- it is still running when i look at the task manager.

I have two sound cards and i noticed that xfce's mixer couldnt control the sound of my second card.
if i try to run alsaconf through vasm (not vasmcc), it wouldnt start
alsaconf is not able to switch my defaut sound card.
The problem was solved by following this guide:
http://forum.vectorlinux.com/index.php?topic=4888.0
its too bad vasm can not automate this. Could be frustrating for some newbies from ubuntu camp.

ntfs partition wouldnt mount. I get the following message
Code: [Select]
Failed to mount '/dev/hda6': Operation not supported
Mount is denied because NTFS is marked to be in use. Choose one action:

Choice 1: If you have Windows then disconnect the external devices by
          clicking on the 'Safely Remove Hardware' icon in the Windows
          taskbar then shutdown Windows cleanly.

Choice 2: If you don't have Windows then you can use the 'force' option for
          your own responsibility. For example type on the command line:

            mount -t ntfs-3g -o force /dev/hda6 /mnt/disc-d

    Or add the option to the relevant row in the /etc/fstab file:

            /dev/hda6 /mnt/disc-d ntfs-3g force 0 0
I didnt have this problem with previous vector (59) i think..or previous distros


One thing that is gone as a bug for me is the pesky xfce- /etc/hosts annoyance on startup. I used to get that all the time in 59 while trying to stop eth0 and 1 from switching. With the new internet configuration in vecs installer and wicd- network handling seems to be a lot more stable and simple.


Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: MikeCindi on February 14, 2009, 04:54:49 pm
ntfs partition wouldnt mount. I get the following message...

That is the warning when a NTFS partition is shutdown "dirty" and Windows wants to run chkdsk. Shouldn't be an issue for VL but rather Windows and ntfs-3g.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: GrannyGeek on February 14, 2009, 08:23:07 pm
I've already reported my continuing problems with rtl8185 wireless. I can connect (I'm using the wireless connection right now), but getting there is a struggle--every time. I'm not sure I reported the pattern.

The connection is never working when I boot into VL. I have to run VLwifi in order to get the connection working. I've set up wicd for my fixed IP, WPA, strong password configuration, but wicd does not ever make the connection. Occasionally it reports that I'm connected, but pinging my router is unsuccessful.

In order to get a working connection I have to run VLwifi several times--six or seven, most of the time. Running it once never succeeds. This has me wondering what the problem is. You'd think that if VLwifi can get a working connection after several tries, it should succeed on the first try.

I thought that maybe it took the computer more time to get its wireless act in order, so I've waited as long as ten minutes before attempting to get a working connection and have also given it several minutes after I've run VLwifi, but these did nothing. The only thing that works is to keep running VLwifi again and again until the wireless connection is established. wpa-gui does not work.

Once the connection is established, it stays up pretty well. If it drops after several hours, running VLwifi again works and usually with just one or two tries.

None of this was necessary with VL 5.9 Standard. I'm using ndiswrapper with the XP driver for rtl8185, which is what I used with 5.9.
--GrannyGeek
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: GrannyGeek on February 15, 2009, 08:37:15 pm
I may have discovered the cause of the problems I've been having with getting my wireless connection started. I noticed for the first time the wicd icon in the system tray. After I started XFce I put my cursor over the icon and noticed that wicd was trying to connect--something it has never done successfully. I wondered if wicd trying to connect was interfering with VLwifi, causing me to have to run VLwifi six or more times before I could get a connection. So I unchecked Wicd in the autostarted applications and renamed wicd-tray.desktop in ~/.config/autostart. I then restarted X and XFce and ran VLwifi and--it connected on the first try!

So I decided to go all the way and made /etc/rc.d/init.d/wicd not executable and I rebooted. My goal was to disable wicd so it wouldn't start at all. After rebooting and before doing startx (I use runlevel 2 for logging in), I pinged my router and it communicated without my having to run VLwifi!

I've tested this just twice, so I can't say I've definitely solved the problem, but so far things are looking very promising. I think wicd may have been the culprit.
--GrannyGeek
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: GrannyGeek on February 15, 2009, 08:42:18 pm
I just now unchecked wicd in VASMCC Services for runlevel 2. We'll see what happens when I reboot, which I hope I won't have to do tonight.
--GrannyGeek
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: overthere on February 15, 2009, 09:26:46 pm
Hi
I downloaded vl6rc4 and burned the iso to cd

the installer pops up a text based dialog asking for screen size..any option gets a wait may flicker then a nice splash. then the screen goes black and sticks..I have to unplug the box.

the old installer works excellent as in 5.9

love the new theme

no thunar as root so a bit of log out log in

no fluxbox ..oh wellll
 
 as usual
 
 does not auto detect the second optical but vasm found it straight away
 
 then had to log back in as root to rename /mnt/cdrecorder "cdwriter" set by vasm
 
 then go to fstab and unmark the cdwriter so it will show in mounter
 
 run k3b once as root while there from experience
 
 set xmms to see the new drive and set digital
 
 players working
 
 gimp is included..nice
 
 command game appears to work..

 
  no dialer, no internet...counts me out I guess..maby light 6 will have it
 

 looks great..in my now humbled opinion
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: caitlyn on February 16, 2009, 06:24:31 am
fluxbox is in the repository.  You can add it with gslapt immediately after install.

The GUI installer has improved a lot since rc4.  You may want to look at rc4.6 or later.

http://vectorlinux.osuosl.org/veclinux-6.0/iso-test/VL6.0-STD-RC4.6.iso
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: overthere on February 16, 2009, 12:00:37 pm
Nice to know fluxbox is still an alternative

with no ability to connect to the net it is hardly worth another download

can use the old until end of life next year I guess
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: vector on February 16, 2009, 12:41:19 pm
Quote
with no ability to connect to the net it is hardly worth another download
We have included the chestnut modem dialer in final..........be here soon!

Cheers,
Vec
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: overthere on February 16, 2009, 01:19:50 pm
Cheers indeed
Quote
be here soon!

I'm not going anywhere unless I have to

 :)
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: GrannyGeek on February 16, 2009, 03:34:38 pm
I just now unchecked wicd in VASMCC Services for runlevel 2. We'll see what happens when I reboot, which I hope I won't have to do tonight.

I'm very happy to report that I've rebooted about five times (for testing purposes) and the wireless connection is up and running as soon as VL starts. I don't have to run VLwifi or anything else. So disabling wicd was what fixed my problem. Fabulous!
--GrannyGeek
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: Ewald on February 20, 2009, 01:09:39 am
tried to install RC4 on a 800mHz Athlon machine with 512mB Ram. Everything went fine until the very end, when being asked to restart the system. Screen gets messed up and Computer remained frozen. Upon powering down and restarting the boot goes multiuser, gives me a "setting up message bus FAILED" and hangs at setting up hald position. After a while I get a terminal login prompt. I can login but I can't start the x server.
I reproduced this behaviour twice. I am not Linux savvy enough to troubleshoot myself.
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: GrannyGeek on February 20, 2009, 03:56:11 pm
On my 1.3 Ghz  Celeron, YouTube  and Flash videos played in Opera are jerky. About every 10 seconds there will be a short pause, which makes it difficult to watch a video. I played a YouTube video directly from youtube.com on Firefox and there were no pauses or choppiness. I had attributed the problem to the low specs of the computer compared with the 64-bit dual core computers, but I now realize that's not so because YouTube and Flash videos under Firefox were okay.

I don't know what happens on the 64-bit computers, as I haven't played many videos. Will have to try some and see if Opera has the same problem there.
--GrannyGeek
Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: Pita on February 20, 2009, 06:32:02 pm
I finally was able to print. I copied the printers.conf over from VL-5.8 which shows
DeviceURI usb://Unknown/.

Using printers.conf from VL-6-Light and which works there which shows
DeviceURI hal:///org/freedesktop/Hal/devices/usb_device_67b_2305_noserial_if0_printer_noserial
does not work in RC4.

In RC4 I am unable to configure my printer connected to USB port since the USB Device does not show when configuring with localhost:631. That did show in VL-6-Light.

Title: Re: VectorLinux 6.0 RC4 feedback and bug reports
Post by: StrayBit on February 21, 2009, 07:14:05 am
Sorry for the delay in posting this.  I DL'd and installed the latest RC4 a week ago on a PIII 500 and a PII 750 both with 256MB.

Installation:  exception (similar to below) on exit from adding users.

Reboot:
  VASM/Hardware config - cannot be used while x is running (that's also in 5.9)
  VASM/Utilities
Quote
This application has raised an unexpected error and must abort.
[-1] Unable to load image
Mfiles.?.0
  VASM/Service/Cups:  unable to mount Epson Stylus C60 which 5.9 did

And, unlike 5.9, root CAN NOT have screen saver.  I know!  "You must be crazy!"  I've known that for years  ;D

Also, after fighting it for 5 months in 5.9, I've decided that the only way I can share files among all my PC's is to keep a Win9x running!  ( I may even have to move the printer to it!