AuthorTopic: VectorLinux5.9-rc3 bugs/annoyances (Read 87256 times)

The point is, there are two ways to run the command, from CLI and Run Program. From CLI you necessarily have the Terminal tagging along with Xine. If you try to close Terminal, Xine will also close. OTOH running the command from Run Program, there is no Terminal program tagging along, just the Xine visualization, which saves space on Panel.

Bottom line: This stream should play when user clicks on link at CBC. IMHO running streaming URL from CLI or Run Program isn't gonna fly for a final release of VL 5.9 Std. It's worth the effort to maintain VL's reputation of everything working out of the box.

A really quick glance at it in a VM, and overall liking the GUI. I would like recommend some splash tweaking though so make Vector that little bit better. I'm really excited about this release and the presumably upcoming SOHO version. Here's to tweaking VL to perfection!

Counter-Clockwise from top center:1. Remove Logo. Redundant with the bottom right-hand corner logo.2. Make Left Aligned3. Remove underlining (despite any shortcut symbolism)4. Lower password input box field to match the space between the text and input box for username5. Adjust semi-transparent layer - raised upwards a bit - extended to the right to fill the area where the logo was * the overall width may need to be shrunk6. Adjust spacing and alignment of System, Session, and Enter buttons

When I booted my Turion laptop today, the WPA wireless had to be reconfigured with VLwifi. There was no connection until I ran VLwifi. That's the same problem I had in RC2. I added modprobe ndiswrapper to /etc/rc.d/rc.inet3, which fixed it in RC2. I haven't yet rebooted to see if the fix works in RC3.--GrannyGeek

Minor annoyance. I recycled users between RC2 and RC3. Didn't really expect things to have changed to much, so I elected not to reset things. However, my customized ~/.bashrc was overwritten. And I've also just discovered that my customization to Fluxbox has also been overwritten. Would be nice if it was left alone when I ask it to be...

I've installed RC3 on my Athlon desktop. RC3 is now on all four of my computers.

Installation on the Athlon was trouble free. I'm using the proprietary ATI driver--works fine, no problems. I do have some minor screen artifacts. I had those with RC1.7, too--I think they went away after a few uses, but so far I haven't had the opportunity to reboot. I can't test more right now.

On the Turion laptop, the wireless connection came up automatically at startup after I added modprobe ndiswrapper to /etc/rc.d/rc.inet3 and rebooted. That fix also worked in RC2. I'm wondering if this might be an issue for newbies who have similar drivers under ndiswrapper.

I was wondering if there was any reason not to remove the extraneous directories from both /mnt and /media? Its a bit cluttered in there....

I don't mess with /media simply because I rarely mount anything on /media and it's off my radar. However, in /mnt I always remove directories I know I'll never have any use for, like /fd0 or /floppy (whatever it's called) and /win or /hd. I create my own directories for my Windows drives, such as /mnt/win-c, /mnt/win-d, etc., so I don't need /win.--GrannyGeek

After I had done the properties on speaker icon on panel it stays showing the volume after repeated reboots.

I still do not like that mc starts in black in Terminal and in invisible in xterm unless the -b flag is set. It has always been white on blue which I find nice compared to the ugly black. Why had that to be changed?

On booting, setting up network it shows the output of /sbin/ifconfig. Is there a need for that? Could somebody looking over ones shoulder catch the ip address?

I don't mess with /media simply because I rarely mount anything on /media and it's off my radar. However, in /mnt I always remove directories I know I'll never have any use for, like /fd0 or /floppy (whatever it's called) and /win or /hd. I create my own directories for my Windows drives, such as /mnt/win-c, /mnt/win-d, etc., so I don't need /win.

I thought that would be pretty much the way things worked. I am a bit puzzled though - from reading, I thought that all removable media would now use /media as a mount point, and /mnt would only be for things like hard drive partitions. I notice however that optical media is still mounting on /mnt. Should any links to cdrom/dvd drives be removed from /etc/fstab (as is the case with Zenwalk), or should fstab be modified to use /media instead of /mnt for opticals?

HAL is a bit tidier than Vl-hot, but it does involve a bit more memory footprint, so I guess no fix is going to be universal.