VectorLinux

Cooking up the Treats => Distro development => Topic started by: |nic| on February 09, 2011, 03:33:37 am

Title: VectorLinux 7.0 Beta1 bug thread
Post by: |nic| on February 09, 2011, 03:33:37 am
I just installed it on my Samsung n110 netbook
Everything is working properly except the touchpad.
It recognized it during the installation but I can't scroll and move windows with the touchpad.

Great work!

greetz

nic
Title: VectorLinux 7.0 Beta1 bug thread
Post by: M0E-lnx on February 09, 2011, 05:40:49 am
I just installed it on my Samsung n110 netbook
Everything is working properly except the touchpad.
It recognized it during the installation but I can't scroll and move windows with the touchpad.

Great work!

greetz

nic

This may be an xfce4 setting somewhere.... I remember in the past my touchpad wouldn't work by default, until I went to the settings and enabled it.
Title: VectorLinux 7.0 Beta1 bug thread
Post by: jimtib on February 09, 2011, 07:03:01 am
Is there a problem with using ati  video. I installed on two different computers one with onboard and one with a pcie card and i have to use vesa on both. One is amd64 single core and the other is amd quad core. I have had to use vesa since about alpha 4.12and have installed every alpha since and also on beta1. The radeon driver worked fine on 6.0. I have tried all the options to setup x and vesa  is all that works.
Title: VectorLinux 7.0 Beta1 bug thread
Post by: toothandnail on February 10, 2011, 03:08:05 am
Install to my T61 was fine. Localization is still broken (attempting to use UTF8 makes nano and MC unusable from the desktop).

I'm having problems with builds under the beta as well. Seamonkey build fails:

Code: [Select]
file_id.cc: In member function 'bool google_breakpad::FileID::ElfFileIdentifier(unsigned char*)':
file_id.cc:98:20: error: 'fstat' was not declared in this scope
gmake[6]: *** [host_file_id.o] Error 1
gmake[5]: *** [libs] Error 2
gmake[4]: *** [libs] Error 2
gmake[3]: *** [libs_tier_toolkit] Error 2
gmake[2]: *** [tier_toolkit] Error 2
gmake[1]: *** [default] Error 2
make: *** [default] Error 2

I've yet to trace the source of the failure. Something missing?

I've also had a strange problem with another build. The latest version of Medit builds fine, but, after installation, attempting to use the help function calls Abiword, not the default web browser, as it should. Don't understand that one either....

Can't say I like the way the task list works much - there seems to be no way of grouping tasks only when space on the bar gets low - the options are always or never, which is a bit annoying.

I had some initial problems with the network functions in Thunar, but they seem to have settled down. Initially, any attempt to open a network share resulted in an error message:

Code: [Select]
Failed to open "Docs".

DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply
(timeout by message bus).

Paul.
Title: VectorLinux 7.0 Beta1 bug thread
Post by: roarde on February 10, 2011, 04:10:04 am
For an md5sum, I get

b018ab549c75ffc1da79d0fdbc748891  VL7.0-STD-Beta-1.iso

What do you get?
Title: VectorLinux 7.0 Beta1 bug thread
Post by: Andy Price on February 10, 2011, 04:12:35 am
For an md5sum, I get

b018ab549c75ffc1da79d0fdbc748891  VL7.0-STD-Beta-1.iso

What do you get?

The same, so I guess we're ok. Thanks!
Title: VectorLinux 7.0 Beta1 bug thread
Post by: jahLux on February 10, 2011, 06:06:31 am
Downloaded/burned CD and had great difficulty installing. Unsuccessful/incomplete attempts on 2 different Panasonic laptops.
Finally installed - with difficulty - on my custom built AMD QuadCore/4GB/12 partitioned 1TB HDD Desktop m/c.
LILO refused to install from GUI installer - finally installed using install CD in "Manual Install" mode to 'Repair LILO'
This Beta is definitely NOT ready for primetime . . . . . . just sayin'  ;)
Title: VectorLinux 7.0 Beta1 bug thread
Post by: caieng on February 10, 2011, 07:15:40 am
Greetings.

Apologies, for having goofed, and submitted this first message earlier this morning to the wrong section of the forum.  Haha.  Nobody is perfect, right!

http://forum.vectorlinux.com/index.php?topic=12807.0

To summarize that message:  I failed to install the beta version, also, i.e. as others have reported.

Later on this morning, I then attempted to install in a third computer, a much more modern motherboard, with PIV "D" cpu, and DDRII RAM, and succeeded, ALMOST. 

At least, I made it past the two errors described earlier today, at the wrong place in the forum.

I arrived at the same error, as a year ago, i.e. create a user.  This problem has still NOT BEEN FIXED!!!!

I entered the usual single letter, I always use, (for I enable autologin, so no need for a complicated user name or password), and obtained an error message, saying that I needed to change the user name, because that one was already in use....???  how can that be, I am installing it for the first time!!!

This is not a new error in the installer, it was there already in 2010.  The installer needs to accept a single letter name, and a single letter password, else,
ENABLE AUTO LOGIN, right from the get go, which, in my humble opinion, makes A LOT MORE SENSE, and is consistent with a first class hotel accommodation, instead of a hammock in the barnyard.

When I acknowledged "my mistake", and signaled my willingness to change my user login name to some other letter of the alphabet, the installer instead exited the routine, as if finished--a second bug, in the same part of the installer, same as a year ago..... 

A very minor, but esthetically unsatisfying point:  the disk does not automatically eject, upon completing the installation....... It is acceptable to compel the user to push the button, but it is just not slick, to do so.  Looks like we are camping out, instead of staying at a reasonable bed and breakfast.....

After reboot, a lovely login screen appeared, very classy, however, it refused to grant entrance.
I know from past experience that I will be obliged to reboot again, with the cdrom, and fiddle with the login business.  That's really not what I desire, so I am going to hold off doing anything further, until these various problems are solved.

As before, please let me know if you need any log files, posted, or sent by email.....

regards,
CAI ENG
Title: VectorLinux 7.0 Beta1 bug thread
Post by: pierce.jason on February 10, 2011, 03:52:07 pm
A very minor, but esthetically unsatisfying point:  the disk does not automatically eject, upon completing the installation....... It is acceptable to compel the user to push the button, but it is just not slick, to do so.  Looks like we are camping out, instead of staying at a reasonable bed and breakfast.....

I much prefer it when cdrom does not auto-eject.

My computer case has a door across the 5.25 bays and auto-ejection always bangs the drive tray against the door.

Also having the user manually push a key for eject, will prevent the tray from remaining extended for a long period, if the user walks away to get some coffee for example. Additionally and probably most importantly, if the cdrom auto-ejected, and the computer auto-rebooted... The cdrom would be retracted at boot up and installer would boot again ;P
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: uelsk8s on February 10, 2011, 07:04:38 pm
Install to my T61 was fine. Localization is still broken (attempting to use UTF8 makes nano and MC unusable from the desktop).

I'm having problems with builds under the beta as well. Seamonkey build fails:

Code: [Select]
file_id.cc: In member function 'bool google_breakpad::FileID::ElfFileIdentifier(unsigned char*)':
file_id.cc:98:20: error: 'fstat' was not declared in this scope
gmake[6]: *** [host_file_id.o] Error 1
gmake[5]: *** [libs] Error 2
gmake[4]: *** [libs] Error 2
gmake[3]: *** [libs_tier_toolkit] Error 2
gmake[2]: *** [tier_toolkit] Error 2
gmake[1]: *** [default] Error 2
make: *** [default] Error 2

I've yet to trace the source of the failure. Something missing?

Paul.


new gcc requires explicit listing of includes in sources. there may be a gcc-4.3 patch out there for seamonkey, otherwise you will have to upgrade to the latest beta version.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on February 10, 2011, 07:43:16 pm
Installation with vinstall-iso went smooth. I did not add a user when asked as
is my habit. Add it later and again this time with no problem using 'adduser'
/root was set to my-user-name:1000.
From terminal
code:
'Chown -R root:root /root '

does correct it. vinstall-iso must have picked something wrong.

Sound card was found correctly with USB webcam plugged-in, however, alsamixer
could not be found for sound card only for USB webcam. Unplugging webcam
alsamixer could not be found, not such file or directory.

gkrellm is still not opening. Invalid instruction.

My printers were found have to supply yet the ppd.

gslapt working installed dillo, joe, sendmail, mailx
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: burpnrun on February 10, 2011, 09:11:44 pm
Permissions in /root and subdirectories/files are a mixture between root, and the user specified in setup, for user and group.  Fresh (full) install into a Virtualbox VM.  Using "user" account, desktop appears.  Signing into/using root account is impossible since it throws up the .dmrc permissions error and drops into a terminal, immediately after password is entered.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: GrannyGeek on February 10, 2011, 10:40:33 pm
I installed today on my 1.3 GHz Celeron, my usual testing machine. My first attempt to install hanged the computer early in the process; the initial "choose resolution" screen hadn't come up yet. I had to turn off the computer with the power switch. After a cold boot the installation went fine. I used 1024x768 because I was always unable to use 1280x1024 in the alphas and I figured that probably didn't change.

I'm sure you know that there is a bunch of udevd error messages during startup.

I haven't had time to do a lot of customizing and installing, but here's what I've found so far.
Opera's license agreement is still a blank screen.
For the exit screen I have only Logout option. Restart and Shut Down are grayed out.

I had no problem creating a user during installation; 1000 was correctly assigned as UID. I'll have to check on the /root problem others reported. I never log in as root; I always log in as user and su to root, do what I have to do, and exit back to user. Also, I always use runlevel 2. I really hate GUI logins because it's more complicated to get out of X.

Tomorrow I hope to install beta 1 on my faster desktop computer (Athlon 64 X2 4200+). I didn't try an alphas on it.
--GrannyGeek
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on February 11, 2011, 12:03:17 am
Booting with USB webcam disconnected starts alsa correctly.

Results for some players:

mplayer plays audio CD.

xine takes about one minute before it has made up its mind to play.

the next 3 players could not play. Here is output:

:$ audacious

** WARNING **
Audacious has detected that your ALSA device has a broken timer.  A         
workaround
is being used to prevent CPU overload.  Please report this problem to your
Linux distributor or to the ALSA developers.

ALSA lib pcm.c:7245:(snd_pcm_recover) underrun occured

:$ gnome-mplayer

(gnome-mplayer:3050): Gtk-WARNING **: Unable to retrieve the file info for 
`cdda:///': The specified location is not mounted

(gnome-mplayer:3050): Gtk-WARNING **: Failed to set text from markup due to
error parsing markup: Error on line 2 char 29: Invalid UTF-8 encoded text in
name - not valid 'Lang nimmer g\xb4seng'

:$ exaile
WARNING : Failed to connect to HAL, autodetection of devices will be
disabled.

Clicking on Audio Disc Icon, then Eject Volume gives:
Failed to eject "Audio Disc"
Not Authorized
and nothing is ejected.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: GrannyGeek on February 11, 2011, 03:37:39 pm
More testing and installing today.

Audacity won't start. Message: audacity: error while loading shared libraries: libwx_gtk2u_richtext-2.8.so.0: cannot open shared object file: No such file or directory

Flash is not working in Opera. I see a new version of Flash has just come out. I'll install the plugin and see if Opera works after that.

SeaMonkey is working fine. The complaint about a missing dependency continues in Gslapt, but there are no error messages when I start SeaMonkey from the command line.

Something changed the address of my DNS server to my router's address. I don't know what it was. Will confirm the next time I boot. I ran netconfig and fixed it.

I had installed wine 1.3.11 from the /home/ftp directory on my VL7 a4.22 directory and the few programs I run under Wine worked well. Then I updated to 1.3.12 from the VL7 testing repo and Wine stopped working. It claimed a mismatch of wineservers. Rather than struggle with that, I uninstalled 1.3.12 and reinstalled 1.3.11 and my under-Wine programs are working well again.

Haven't installed my printers yet and didn't have time to install beta 1 on my other desktop computer.

I've figured out how to get my Panel launchers and Panel set up to my liking.

In all, it's doing pretty well. I haven't tried the script for LibreOffice yet.
--GrannyGeek
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on February 11, 2011, 08:57:09 pm
Trying to play audio CD with gnome-player by clicking on Audio Disk icon
error 'Failed to open cdda://sr0/Track%207.wav.' is reported.

However, opening gnome-player from Menu-Multimedia audio CD does play.

Since I booted with webcam plugged to USB port alsamixer shows
USB 2.0 Camera as Card. This does not deter CD to play.

When I unplug webcam I get
 In the midst of the word he was trying to say,                     |
|                       In the midst of his laughter and glee,                           |
|                     He had softly and suddenly vanished away---                        |
|                       For the Snark was a Boojum, you see.                             |
|                                                                                        |
|                     (Lewis Carroll, "The Hunting of the Snark")                        |
|                                                                                        |
|                                                                                        |
|                            The sound device was unplugged.                             |
|                         Press F6 to select another sound card.                         |
|                                                                   

Press F6 and select audio card shows all the control of the usual alsamixer, however,

@~:$ alsamixer
cannot open mixer: No such file or directory

Flash plays both in opera and firefox, however, w/o sound. Will try on next
booting with webcam unplugged.

~/skype_static-2.1.0.81/ crashes when trying to make a test call.

skype: pcm_null.c:130: snd_pcm_null_start: Assertion `null->state == SND_PCM_STATE_PREPARED' failed.

[1]-  Segmentation fault

Booting with webcam unplugged flash plays in opera with sound.

Got gkrellm up and running by copying gkrellm from VL6 over to VL7-BETA. ;)
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: GrannyGeek on February 12, 2011, 11:06:02 am
When I insert a flash drive, it doesn't automount. I think I selected vl-hot on this old Celeron because I don't want polling going on. It needs all the help it can get!

If I try to mount the drive as user, it won't do it and gives me an error message:
Failed to mount 4.0 GB Filesystem
Not Authorized

I can mount the drive as root.

Any solutions? Or is this related to those udev error messages that flash on the screen during startup? I'll switch to HAL and see if the flash drive is automounted, or at least mountable by user.
GrannyGeek
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: GrannyGeek on February 12, 2011, 02:23:44 pm
I installed beta1 on my Athlon 64 X2 desktop. It has onboard ATI Radeon Xpress 200 graphics. Installation went okay. I rebooted into runlevel 2 and continued the setup with VASM.

Alas, I can't get into X. I believe others have also experienced problems with ATI graphics. Note that on my other desktop with ATI Radeon 9200 graphics card I have no problems and VL assigned the correct driver automatically.

In beta1 on the Athlon 64, the xorg radeon driver was installed automatically. This driver has always worked in earlier versions of VectorLinux. The final error message is
xinit:unable to connect to X server: Connection refused
xinit: server error

I edited xorg.conf, substituting the ati driver for the radeon driver. Results the same. I edited xorg.conf, substituting the vesa driver. XFce did start but at 800x600 resolution, which is pretty grim on a 1600x1200 monitor.

So I guess I'll give up for now and await a fix or the second beta. I was really looking forward to running VL7 on a much faster computer than my warhorse 1.3 GHz Celeron.

I should also mention that a got a hang on the Athlon 64 fairly early in the installation process. I turned off the computer with the power switch, did a cold boot, and this time the installation proceeded smoothly. I also got a hang on the Celeron the first time I tried to install beta1. A cold reboot solved the problem and no further problems occurred during the installation.

The Athlon 64 theoretically should be able to use the proprietary Radeon driver. However, when I've tried the proprietary driver supplied with VectorLinux it hasn't installed correctly and I had to use the xorg radeon driver. I never got around to trying the proprietary driver downloaded directly from ATI. The Radeon 9200 on the Celeron cannot use the proprietary ATI driver, as ATI does not provide drivers for old cards.
--GrannyGeek
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on February 12, 2011, 06:13:50 pm
Quote
~/skype_static-2.1.0.81/ crashes when trying to make a test call.

After changing sound devices in skype it is working now. Test call possitive.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on February 12, 2011, 11:50:14 pm
If I insert a flash drive I get:

:$ thunar-volman: Unsupported USB device type.
thunar-volman: Unsupported USB device type.
thunar-volman: Unknown block device type.

and it is not mounted.

If I mount it manually as user it is empty even so it files have been loaded in VL6.
Back to VL6 all files in that flash drive show.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: The Headacher on February 13, 2011, 07:34:02 am
Alright, I tried this in a virtual machine for now (I'll install to a real partition later). Here's what I found:

- the bootscreen on the cd still says it's VL core.
- after installing, there were troubles setting up the user: the user "me" was already found on the system. This seems like the same problem "Caieng" is facing:
Quote
I entered the usual single letter, I always use, (for I enable autologin, so no need for a complicated user name or password), and obtained an error message, saying that I needed to change the user name, because that one was already in use....Huh  how can that be, I am installing it for the first time!!!

This is not a new error in the installer, it was there already in 2010.  The installer needs to accept a single letter name, and a single letter password, else,
ENABLE AUTO LOGIN, right from the get go, which, in my humble opinion, makes A LOT MORE SENSE, and is consistent with a first class hotel accommodation, instead of a hammock in the barnyard.

When I acknowledged "my mistake", and signaled my willingness to change my user login name to some other letter of the alphabet, the installer instead exited the routine, as if finished--a second bug, in the same part of the installer, same as a year ago.....

After rebooting, I could not log in as normal user because there was none created. Logging in as root caused problems too though, I only got a terminal. I added a user to the install with vasm.

The login and desktop look very psychedelic.. is this default? I'm not sure wat kind of audience we're trying to attract here..
Pidgin doesn't seem to have an icon in the launcher bar thing.

Alright, forgot about the rest of the bugs for now.

@Pita: your audio problem can be fixed like this: http://forum.vectorlinux.com/index.php?topic=4888.0
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: GrannyGeek on February 13, 2011, 01:07:59 pm
A few more problems on the 1.3 GHz Celeron...

Exaile won't start. Error messages:
Code: [Select]
Traceback (most recent call last):
  File "/usr/lib/exaile/exaile.py", line 51, in <module>
    main()
  File "/usr/lib/exaile/exaile.py", line 48, in main
    exaile = main.Exaile()
  File "/usr/lib/exaile/xl/main.py", line 78, in __init__
    self.mainloop_init()
  File "/usr/lib/exaile/xl/main.py", line 495, in mainloop_init
    import gtk
  File "/usr/lib/python2.7/site-packages/gtk-2.0/gtk/__init__.py", line 40, in <module>
    from gtk import _gtk
ImportError: /usr/lib/libgtk-x11-2.0.so.0: undefined symbol: gdk_pixbuf_format_get_type

Shotwell starts but won't import photos. I wanted links to them rather than the files themselves. File names are grayed out. Error messages:
Code: [Select]
(shotwell:16971): Gtk-CRITICAL **: IA__gtk_window_set_default_icon: assertion `GDK_IS_PIXBUF (icon)' failed
libusb couldn't open USB device /dev/bus/usb/001/001: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/002/001: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/003/001: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/004/001: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/005/001: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/005/002: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/005/003: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/006/001: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/007/001: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/007/002: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/008/001: Permission denied.
libusb requires write access to USB device nodes.
Audacity won't start. Error message:
Code: [Select]
audacity: error while loading shared libraries: libwx_gtk2u_richtext-2.8.so.0: cannot open shared object file: No such file or directory
I installed the new plugin for Flash. SeaMonkey and Firefox are working fine with it. Opera still thinks it doesn't have a Flash plugin, even though I copied the plugin file to /usr/lib/opera/plugins

A general question: What are Functions and Readme.Functions in the services? They aren't checked in Installation but do I need them? What are they for? I always install Fuse because I use NTFS drives in Windows but I don't know what Fuse does. Do you need it for sharing NTFS drives?

I ran the script for LibreOffice and it installed fine, as far as I can tell.
--GrannyGeek

Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: nightflier on February 13, 2011, 04:29:37 pm
Boot-up message:
Code: [Select]
/usr/lib/libtalloc.so.2 is not a symbolic link
Text login screen broken by message:
Code: [Select]
Local time zone must be set--see zic m
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on February 13, 2011, 10:55:42 pm
Thanks Headacher!

@Pita: your audio problem can be fixed like this: http://forum.vectorlinux.com/index.php?topic=4888.0

Its seems to be working at least sofar with twice booting. Had to create file sound.

Now,
cron/crontab does not work.  crond is running:
$ sudo /etc/rc.d/init.d/cron status
crond running with Process ID 1956
yet no commands are executed. My crontab file is the same as in VL6,
permission settings at all at 600 root:users.
In vasm services cron is enabled for user.

Edit:
Got crontab working now. It was a matter of the setting in /etc/group
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Andy Price on February 13, 2011, 11:30:56 pm
Still can't install on any of my machines with the text installer, it's been the same with (almost) all of the alphas I've tested. Is anyone using it successfully? Luckily the GUI installer works, though I miss the ability to check the CD for defects that you get with the text installer, as well as its speed. Once installed the beta looks nice and seems stable. Some problems found as below.

Can't install Thunderbird, missing gconf>=2.3.1.1

I always set up my (wired) network setting through vasm. When I click on the Wicd icon and check the connection properties all the fields are empty except for host name. Is this normal? I've never used Wicd before.

I've got a strange problem with svg files not showing up. For example, when I install the xfce-mount plugin the icon (which is an svg) doesn't show. And when I try to run Shotwell from the menu it won't start, and when I run it from the terminal it gives an error message "Resources.vala:663: Couldn't recognise the image file format for file /usr/share/shotwell/icons/crop.svg". I've not seen this error in any of the betas and no-one else seems to have reported it, so perhaps it's just me. Could it be connected in some way to the fact that I uninstalled the Cairo Dock?

I'm able to play movies and mp3s in all the players, but Gnome Mplayer mutes the sound every time it opens.

Gslapt used to offer to save passwords, a useful feature, but doesn't at present.

I blanked a CDRW using Xfburn and after that it wasn't recognised any more (on any computer) and can't be used. I'm not sure what happened, but it's not a test I want to repeat too often as these a $1 a plop.

Andy

Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: GrannyGeek on February 14, 2011, 08:59:06 pm
Andy,

>> Can't install Thunderbird, missing gconf>=2.3.1.1 >>

The same thing happens with SeaMonkey in Gslapt. However, I could install it by telling it to install despite the "missing" dependency. It works fine once installed and there are no complaints when I start SeaMonkey from the command line. Have you tried installing Thunderbird despite Gslapt's complaints?

I had the same problem with Shotwell but for some reason, it finally did start. However, when I try to add links to photos, I got the error messages I listed in my message above and Shotwell terminated.

My CDRW's are about 10 years old and are limited to 640 megs, so I can't use them to burn VL7 beta1.
--GrannyGeek
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on February 14, 2011, 10:45:36 pm
When booting today mouse would not work and report gpm [failed]
Checking in ../init.d/gpm -t was set to auto. Chaged to imps2 and mouse worked.

Further
:$ shotwell

** ERROR **: Resources.vala:663: Couldn't recognize the image file format for file '/usr/share/shotwell/icons/crop.svg

Checking crop.svg with geeqie there is only a blank and at botton it says empty.

ls -l /usr/share/shotwell/icons/crop.svg
-rw-r--r-- 1 root root 10299 Jan 16 20:38 /usr/share/shotwell/icons/crop.svg

Further:
When I connect my camera nothing is mounted. In VL6 it is mounted
automatically and I can view pictures even with mc.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Andy Price on February 15, 2011, 05:54:22 am
Thanks GrannyGeek, I followed your advice and installed Thunderbird ok. As for the CDRW, although I couldn't use it in my two Linux machines, I put it in a Windows XP box and copied data to it with no problem. A bit strange, though I have have had incompatibilities like that on occasion.
Andy
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on February 16, 2011, 04:46:09 pm
Installed RealPlayer and working.

Installed gthumb-2.12.2 and working as well properly.

Why gthumb, well I am used to it and find it the better of the lot. For one
thing it always finds my camera to transfer the pictures which I cannot
say of the other programs for that. In VL6 I have to use gthumb- 2.10.12.

It would be nice if VL could incorporate gthumb in its repertoire.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: demigaucher on February 17, 2011, 04:20:59 am
Hi all

I described my first attempts elsewhere (which was clearly the wrong place):

http://forum.vectorlinux.com/index.php?topic=12807.0

Now I finally succeeded, but I confirm the observations made by Jimtib and GrannyGeek:
I tried all possible combinations for the graphical interface, and the only one which worked
was VESA, with which the fonts are blurred and usable only for tests, but unacceptable for a
definitive installation.

Surprisingly, the alpha version, issued some time ago, did not gave me any such problem
and booted in a clean graphical mode the "usual" way (as with VL6.0).

More posts later.

Demigaucher
happily running VL6.0 on a shuttle X
with AMD Athlon X1900+ @1463 MHz, 512 MB ram
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on February 18, 2011, 03:20:21 am
Installed kernel-src-2.6.37-i686-3vl70

Trying to install nvidia with NVIDIA-Linux-x86-96.43.19-pkg1.run
nvidia-installer.log gives:

Using: nvidia-installer ncurses user interface
-> License accepted.
-> Installing NVIDIA driver version 96.43.19.
-> Performing CC sanity check with CC="cc".
-> Performing CC version check with CC="cc".
-> Kernel source path: '/lib/modules/2.6.37/source'
-> Kernel output path: '/lib/modules/2.6.37/build'
-> Performing rivafb check.
-> Performing nvidiafb check.
-> Performing Xen check.
-> Cleaning kernel module build directory.
   executing: 'cd ./usr/src/nv; make clean'...
-> Building kernel module:
   executing: 'cd ./usr/src/nv; make module SYSSRC=/lib/modules/2.6.37/source S
   YSOUT=/lib/modules/2.6.37/build'...
   NVIDIA: calling KBUILD...
   make CC=cc KBUILD_OUTPUT=/lib/modules/2.6.37/build KBUILD_VERBOSE=1 -C /lib/
   modules/2.6.37/source SUBDIRS=/tmp/selfgz2300/NVIDIA-Linux-x86-96.43.19-pkg1
   /usr/src/nv modules
   make -C /lib/modules/2.6.37/build \
   KBUILD_SRC=/usr/src/linux-2.6.37 \
   KBUILD_EXTMOD="/tmp/selfgz2300/NVIDIA-Linux-x86-96.43.19-pkg1/usr/src/nv" -f
   /usr/src/linux-2.6.37/Makefile \
   modules
   /usr/src/linux-2.6.37/Makefile:546: /usr/src/linux-2.6.37/arch/i586/Makefile
   : No such file or directory
   make[3]: *** No rule to make target `/usr/src/linux-2.6.37/arch/i586/Makefil
   e'.  Stop.
   make[2]: *** [sub-make] Error 2
   NVIDIA: left KBUILD.
   nvidia.ko failed to build!
   make[1]: *** [module] Error 1
   make: *** [module] Error 2
-> Error.
ERROR: Unable to build the NVIDIA kernel module.
ERROR: Installation has failed.

Strange the same nvidia version installs in VL6 and there is no ...i586 and ...i386
has no Makefile.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: M0E-lnx on February 18, 2011, 08:52:26 am
What's with all the dbus output during the boot process?
or is that just me? something about rules and stuff.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: uelsk8s on February 18, 2011, 09:20:24 am
Installed kernel-src-2.6.37-i686-3vl70

Trying to install nvidia with NVIDIA-Linux-x86-96.43.19-pkg1.run
nvidia-installer.log gives:

   make[3]: *** No rule to make target `/usr/src/linux-2.6.37/arch/i586/Makefil

ERROR: Unable to build the NVIDIA kernel module.
ERROR: Installation has failed.

Strange the same nvidia version installs in VL6 and there is no ...i586 and ...i386
has no Makefile.

you either need to run the installer from a text login or you need to "unset $ARCH" before running the nvidia installer
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: newt on February 18, 2011, 04:40:34 pm
...
Alas, I can't get into X. I believe others have also experienced problems with ATI graphics.
...
I edited xorg.conf, substituting the ati driver for the radeon driver. Results the same. I edited xorg.conf, substituting the vesa driver. XFce did start but at 800x600 resolution, which is pretty grim on a 1600x1200 monitor.
...
Granny, I had troubles with ati graphics when alpha testing VL6SOHO. As I understand it, the 'ati' driver is a dummy driver that actually attempts to pick the correct opensource driver for the graphics card (in your case, 'radeon').  During my troubles my system was attempting to load the rage128 driver both via 'ati' and 'r128', and the final resolution was that the driver (r128) was not included in that particular alpha release. I do recall that I was able to grab the 'r128' driver from a previous release and place it in the correct modules directory to get the graphics working correctly. I wonder if your situation is similar, and if you simply copied over the 'radeon' drivers from the most recent VL7alpha if it would fix your graphics issues. I don't recall the exact location of where all of the ati graphic drivers are stored but it was not a place I would normally look. If I can track down the location I'll let you know. Hope this helps (and makes sense).
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on February 18, 2011, 04:46:36 pm
What's with all the dbus output during the boot process?
or is that just me? something about rules and stuff.

Just do what it says in /etc/udev/rules.d/10-vl-hot.rules and it will stop.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: GrannyGeek on February 18, 2011, 09:09:48 pm
I wonder if your situation is similar, and if you simply copied over the 'radeon' drivers from the most recent VL7alpha if it would fix your graphics issues. I don't recall the exact location of where all of the ati graphic drivers are stored but it was not a place I would normally look. If I can track down the location I'll let you know. Hope this helps (and makes sense).

I'll give this a try. I don't think it will work, though. My other desktop with VL7 beta1 has an ATI Radeon 9200 card and I use the xorg radeon driver. It works fine on that computer, but in VL7 beta 1 on the computer with ATI Radeon Xpress 200 graphics, the radeon driver does not work. I'll try to find the radeon driver in VL7 a4.21 and see if it works better on beta1. Maybe I'll luck out.
--GrannyGeek
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on February 18, 2011, 09:40:56 pm
VL 7 is "Beta" ??
Fear not, all other linux variants have glitches -even sources based
> Mutally exclusive "blockages" - profile overlays, CVS vs GIT)
> Forks of forks - "parent" vs borrowed upstream sources !!!
   
-------------------------------------------------------------------------------

Caieng:
Default password utitiliy Cfg is to set 8 keyboard characters as lowest allowable.
3 failed login attempts - then exit to CLI interactive shell
A user "can" root access /etc/shadow, blank out anything between *first two*  colons

E.G. root : xxxxxx :xxx: xx :etc_  >  root : (delete all  here)   : 
 named_user  : xxxxx :     > named_user : (delete_)  : 
  Then create user later w/edited *login.defs* conventions (Please see  /etc/login.defs)
 
 BTW it's only a simplistic two-line bash command to create a user, set password
 Besides, it is bad practice to use "one-letter login" 
 OTOH _ If you are the  only user - why use any password if you find it  "inconvenient"
GYI log-ins - that is a subjective opinion only
The  downside - you miss login processes & notifications-all for the sake of "convenience"
NO time is saved   
-----------------------------------------------------------------------------
 Pierce.jason:
 This may shed some light/reconfigure behaviour
 
 http://tldp.org/HOWTO/SCSI-2.4-HOWTO/sr.html
 -------------------------------------------------------------------------------
 Burpnrun:
 
 Virtualbox environment may mislead user as to what to expect Re Hrd/Sftware experiences:
 It is only a reflection of compatiblity between VM tools & Distro tried
------------------------------------------------------------------------------- 
 GG:
 You may already be aware - there is a diference to (su) vs (su -l)
> and Esp. "temporary"  (sudo)
 > Please refer to shells, & user (caller) for inherited  environment profiles
 NTIM _ I fully agree  ~ GUI anything merely hides the underlying processes,
 side-steps the LINUX learning curve
 VL hot > latest  udev (and hot-plug) should be the present standard
 See Hal configuration Re polling
 
 https://wiki.archlinux.org/index.php/HAL
  As always - read your relevant logged error files
 
 Cordially all, - Hope above may help in some small way
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on February 18, 2011, 10:07:26 pm
Installed kernel-src-2.6.37-i686-3vl70

Trying to install nvidia with NVIDIA-Linux-x86-96.43.19-pkg1.run
nvidia-installer.log gives:

   make[3]: *** No rule to make target `/usr/src/linux-2.6.37/arch/i586/Makefil

ERROR: Unable to build the NVIDIA kernel module.
ERROR: Installation has failed.

Strange the same nvidia version installs in VL6 and there is no ...i586 and ...i386
has no Makefile.

you either need to run the installer from a text login or you need to "unset $ARCH" before running the nvidia installer

I only tried to install from the console. That did not work.
However,  now nvidia is up and running.  The command is "unset ARCH" not $ARCH
after one let install run first and fail.

Thanks Uel
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: GrannyGeek on February 20, 2011, 10:13:33 am
I may have posted about this before, but just in case I didn't...

I'm unhappy with the way the various media players are working. Today I'm playing quite a few of my music files and want a playlist so I don't have to run them individually. I can't get any of the players to do this right.

I did make a good playlist in Gnome-Mplayer, but it didn't play the music in the order listed in the playlist. These are classical music files and it's important for them to be played in the proper order, not randomly. Also, it didn't list the correct title of the track being played. It had a title for another track. What's up with that???<g>

So then I tried Mplayer, but it was hard to create a multitrack playlist from several directories. If I did get more than one file into the playlist, it wouldn't play the list unless I selected each track when I wanted it. Xine did the same thing and if I tried to add a file to a playlist, it replaced all the files already in the playlist. It's quite likely I just don't know the right way to create a multifile playlist in MPlayer and xine, but I can't find anything in Help to tell me how to do it if there's some trick.

Exaile does a good job with playlists, but Exaile doesn't work on VL7. This is what I get at a command prompt:
Traceback (most recent call last):
  File "/usr/lib/exaile/exaile.py", line 51, in <module>
    main()
  File "/usr/lib/exaile/exaile.py", line 48, in main
    exaile = main.Exaile()
  File "/usr/lib/exaile/xl/main.py", line 78, in __init__
    self.mainloop_init()
  File "/usr/lib/exaile/xl/main.py", line 495, in mainloop_init
    import gtk
  File "/usr/lib/python2.7/site-packages/gtk-2.0/gtk/__init__.py", line 40, in <module>
    from gtk import _gtk
ImportError: /usr/lib/libgtk-x11-2.0.so.0: undefined symbol: gdk_pixbuf_format_get_type

So it seems I can't go through a playlist with any of these media players.
--GrannyGeek
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on February 20, 2011, 02:02:18 pm
"I can't find anything in Help to tell me"

Granny - is this (found on-line)  of any help ? 

"Mplayer and mplayer-gui can be installed at the same
time, because they contain differently named binaries and there is no
conflict. The trick is to build MPlayer once with --enable-gui, rename the
resulting binary to "gmplayer" and then build it again, without GUI, but
keeping the rest of ./configure options the same.

To provide man pages for all MPlayer suite binaries (mplayer, gmplayer,
mencoder), you can use man-links instead of regular symbolic links.
Creating a mencoder man page linked to mplayer is as simple as:

  echo ".so mplayer.1" >> mencoder.1

A similar trick can be used for "man gmplayer". This avoids problems with
gzipped man pages and symbolic links."
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: GrannyGeek on February 20, 2011, 02:50:57 pm
rm -r--

No, what you quoted isn't of any value because these media players need to work out of the box. I'm reporting a problem in running what should work simply by clicking on the name in the menu. If it doesn't, it needs to be fixed. Starting it from a command line is for the purpose of seeing if the app won't start because something is missing or is not set up correctly.

I don't consider man pages to be "help." Mostly, I find them incomprehensible and so do many other Linux users. They are sometimes useful for examples of syntax.

>> mencoder man page >>

What the heck is that and do I really want to know?<g>

At any rate, this is something that needs to be fixed in the distro, not by individual users.

I'm probably your worst nightmare as a user because I'm not a fan of the command line and I don't care if it's "more efficient" because my system is efficient enough without going through geeky commands I have a lot of trouble remembering. I don't do anything that requires that kind of efficiency anyway.

I don't hate the command line and there are a very few commands I use frequently enough to remember what they are, but I'll usually use a GUI tool if it's available.

In alpha/beta/rc testing we're trying to find what doesn't work so it can be fixed. We're not trying to get it to work *just for us*.
--GrannyGeek
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: GrannyGeek on February 20, 2011, 05:43:52 pm
rm -r,
I'm sorry I didn't say thanks for posting your message and for taking the time to look things up and pass them on. I do appreciate the effort.
--GrannyGeek
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on February 20, 2011, 07:14:22 pm
Granny:

I fully understand - You are very welcome - IMO,  everyone *should*  use their system in any manner that is best for themselves
(and I appologize _ so used to sources based O/systems -  tend to forget  many do not  want to be  CLI oriented)

(A prime example of * why* more attention  to  CLI may be  desirable:  Please note how you typed my user-TAG)
 man rm  see the "space" you applied to a parameter - that could be system FATAL

~ It was useful in the least - giving pause to script -kiddies a while back, when I.P mail server was compromised
Schadenfreude  (best scene) some Linux miscreants had reason to swear
   
Few years back, my outlook was "hard-core";   Unspoken but thought.... what do (collective) "you"   want

"Just a free Windows"    - So I have mellowed - but LOL ,  perhaps not so it's noticeable 

Tho' I do think testing needs three types of input:
User reports,  developer responses &  sometimes - developers NEED alternate info
It is noted,  many variants become myopic - focus  on system-specific/developed  "modus operandi"

Best wishes
   
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: GrannyGeek on February 21, 2011, 05:31:39 pm
(A prime example of * why* more attention  to  CLI may be  desirable:  Please note how you typed my user-TAG)
 man rm  see the "space" you applied to a parameter - that could be system FATAL

I've been wondering why you'd use that for your screen name. I didn't look closely enough to  notice if you had a space. I still don't understand why you'd use it, space or not, because there could be a disaster if someone typed it with space and as root at a prompt, for some unfathomable reason.<g>
--GrannyGeek
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on February 22, 2011, 03:07:13 am
Granny

> " I didn't look closely "  Ahh -  that was the message -
The outcome of most glitches eventually re-enforce that insight

*Disaster*  hardly  - it is only software,  not life

Why use any such now - previously, it was but one safeguard employed to avoid what appeared to be
the INITIAL bytes of a rootkit attempt (I.P.'s OWN  e-mail server was compromised TWICE)

Changing I.D. & password only  "slowed" events - Encryption requires KEY for recipients

Chrootkit (later stronger RKhunter) revealed  suspicious (logged) activity
The mere fact I found such bytes - indicated "script-kiddy"
Now -  it serves to remind Linux devotees to not be lax to details
BTW - That error is well known to most CLI users - as the CLASSIC mistake of all

If a GUI addict, they might reflect on saying: "You are forever but one click away from...."
 
TAG !  <--- That word is so descriptive, any might be  a  phonetic play_on_words Re actual name
Says much  the same as ~ Im-i      
 
 Any Language - spoken/ written or  A.I. coding - can be a delight or abused  ;
As to which, - Plse excuse the Mea Culpa ~   this is all off- topic 
 

Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: caieng on February 22, 2011, 05:49:14 am
Quote from: recursive removal
Caieng:
Default password utitiliy Cfg is to set 8 keyboard characters as lowest allowable.
3 failed login attempts - then exit to CLI interactive shell
A user "can" root access /etc/shadow, blank out anything between *first two*  colons

E.G. root : xxxxxx :xxx: xx :etc_  >  root : (delete all  here)   :
 named_user  : xxxxx :     > named_user : (delete_)  :
  Then create user later w/edited *login.defs* conventions (Please see  /etc/login.defs)
 
 BTW it's only a simplistic two-line bash command to create a user, set password
 Besides, it is bad practice to use "one-letter login"
 OTOH _ If you are the  only user - why use any password if you find it  "inconvenient"
GYI log-ins - that is a subjective opinion only
The  downside - you miss login processes & notifications-all for the sake of "convenience"
NO time is saved
 
Hi RMR!

Thanks for your several thoughtful replies.  Yes, this is a great forum!

In my opinion, not a fact, but, in accordance with my PRACTICE, so, maybe just a titch more than a mere opinion, the installer MUST permit a user to create a single letter login name.

The consequence of not permitting the user to operate his/her computer as he/she wishes, is to ignore the distro.

Ditto for passwords.  If the distribution requires more than a single character password, in order to permit the installation to continue, the cdrom goes onto the coaster pile.

The best installer, I have seen, offers the user a chance to establish automatic login DURING installation.  That is the proper approach, in my opinion.

Of course, if one is thinking, not as a user, but as a museum caretaker, determined at all costs to PRESERVE the wonderful UNIX environment, complete with such nonsense as insisting on TWO clicks of the mouse, because, in the mid 70's when UNIX became popular, we only had a single button on the mouse, ergo, (in those bad old days,) we were obliged to perform two clicks in rapid succession, to differentiate one user action from another.  I am always impressed by the large quantity of faithful to the bitter end UNIX loyalists who INSIST, on their mothers' grave, that one MUST have n characters for this or that function, else the world will stop turning.

I have no patience for such drivel.  Either the installer supports the user requirements, rather than the museum caretaker's list of faithful duties to execute in accordance with the law according to Bell Labs, else, I find a different distro!

CAI ENG
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on February 22, 2011, 10:47:55 am
Caieng

Vector related:

LOL Such passion - It would be a shame to dismiss the polished  VL offerings
(Ya come long way sirs)
~ Because  they adhere  (at install?)  to proven security concerns
Indeed, it is often seen, requests for more such features - Firewalls, etc.

Please be mindful the installer events are but one topic such as this;
Once installed - Any may change defaults as they see fit

Off-topic:
Wink ~ IIRC in the latter 70's, there was no X-windowing for *proprietary* Unix 
@ Bell labs - it seems plausible... the only mice seen were running around floors
   
Perhaps you may have stringent variants such as SEL in mind, vs Ubuntu/PCLinux or offshoots?
I believe the working definition here is *choice*

Museum caretaker ? - Those that off-handidly  dismiss the lessons of past history_


 

Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: budulay on February 22, 2011, 02:53:04 pm
Finally got around trying B1 out:

Installer crashes when I try mounting partition to "Other". (Not the whole installer, just the installer application, jwm is still up and running fine).

Also there was no kernel-src package on the CD, had to download that from http://vectorlinux.osuosl.org/veclinux-7.0/kernels/

Cairo-dock now works with nvidia drivers.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on February 22, 2011, 05:22:30 pm
It would help V L developers to clarify:
>  "Installer crashes when I try mounting partition to "Other". (Not the whole installer, just the installer application, jwm is still up and running fine).

Did you mean. during the install you are defining  other partitions (I.E. lilo )

Most installations  run in virtual f/system mode,  (initrdfs/squashfs)  until installation is complete

(Poorly constructed) Installation procedures do not accommodate a user  *mounting* a partition
> That entails ability to shell out to an alternate TTY,  log-in- as root 

Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: budulay on February 22, 2011, 06:53:06 pm
@rm-r:
I am not sure what you mean. :(

I'll try to explain it in more detail:
Graphical installer has an option to mount different partitions to different places(such as /, /home, /tmp, /mnt/sda1, etc.) One of the options is Other, which is supposed to let me enter the path to where I wish to mount a partition. When I click on Other, installer crashes.
Hope that makes sense now.

Also I just noticed - shotwell is refusing to start:
Quote
budulay7b1:$ shotwell

** ERROR **: Resources.vala:663: Couldn't recognize the image file format for file '/usr/share/shotwell/icons/crop.svg'
aborting...
Aborted
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: GrannyGeek on February 22, 2011, 09:45:43 pm
Graphical installer has an option to mount different partitions to different places(such as /, /home, /tmp, /mnt/sda1, etc.) One of the options is Other, which is supposed to let me enter the path to where I wish to mount a partition. When I click on Other, installer crashes.
Hope that makes sense now.

I think you misunderstood that option. What you are supposed to do is select the partition in which you want to install VL7 and mount / on it. That's it. If you want /home, for example, on a separate partition, you select it (such as /dev/sda6) and mount /home on it. I really don't think you want Other at all. You're selecting the partition in which you want to install VL and that partition is / . The installer is crashing because you haven't selected a partition for / . I hope that is clear. If  not, we'll try to explain it again.
--GrannyGeek
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on February 22, 2011, 11:32:55 pm
Thanx Granny

That "other" bit threw   me - (only time the term *other*   has been discussed is when configuring  lilo)
Is it really worded as such in installer ?

However, the installer should just dump user back to step ~ "create file systems/partitions"
 and pop-up info that no rootfs has been selected

Budulay - "install to partition /mnt/sda1" > while technically it is possible,  it  does not make sense
/mnt is a sub-directory off the root (/) file system
/mnt/sda1 would be the  sub-directory of  /mnt

An installation will  use  any defined (device)  path ~ I.E .  sda1/2/etc etc,   Sdb1/2/etc etc
to create a  root-fs (/)  (mandatory)  and/or a sub-directory of  / (rootfs) in own partition

WITHOUT  numbered (partitioned) sections,   the whole device is used

That in itself may be desired BUT:
If installer does not ask first -(BAD SCRIPT)  it may re-format entire device
 
Best practice- prepare own partitions and format for desired F/system  before installation
ON AN UNMOUNTED DRIVE -  WRITE data  to disc by re-boot

While many like to keep /home on a different partition (or even different device)
~ to save content for re-use when another O/system or upgrade is done:

When  space concerns  are addressed, the fastest growing sub-directory is /tmp
Seldom  considered is which file system to use: (example, ext2/3/4 use limited number of inodes)
Space wise,  /tmp may run out of room to store the temporary files created by an App install 
The space may seem adequate, (when /tmp is on same partition as /
And still  run out of inodes :
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: budulay on February 22, 2011, 11:42:36 pm
I know I am quite bad at explaining things, but today is clearly not my day ;)

Let me take another shot at this:
I selected /dev/sda11 to be mounted as /, /dev/sda7 as /home, /dev/sda6 as /tmp and /dev/sda10 as /mnt/sda10. What I wanted was to mount /dev/sda1 as something other than /mnt/sda1(like /mnt/old or something like that).
Here's how the installer crashes:
I click on the partition(sda1), I get a menu asking if I want to format it(I say leave unformatted) and also asking where I want to mount this partitions. That's where I get choices such as /, /home, /tmp, /opt, /mnt/sda1 and Other. In one of the alphas, when I click on Other, a text field appeared, letting me type where I want that partition to be mounted. Now if I click on Other, installer crashes.

@GrannyGeek
Well, this is exactly what I was trying to do - mount partitions to different places, such as /, /home, etc. One of those places just happened to have a non-default name.

@rm-r
That's not what I was saying. Hope this post makes it clear.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on February 22, 2011, 11:54:01 pm
Hey, sir, Not to worry ~  we all have that problem at times:
LOL - except for explaining where that "other" bit came from,  your re-explanation is exactly the same

The other odd part = why create a device partition  for  anything under sub-directory /mnt

Your installation  example is a  prime reason to abandon GUI - even text scripted outcomes
> Take CONTROL of own results

If for no other reason, developers are fond of taking short-cuts, RE master same d----  glitches 

If poorly scripted, the installer often does un-desirable things (re-formats, wipes Mbr etc)
Bin there- seen it

Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on February 23, 2011, 12:05:02 am
Budalay

Just another suggestion:
If mnt/what-ever is spare storage/seldom used data;
Do not define it @ installation: - To use:

# mkdir /blah blah
# mount  file_system_type  /dev/whatever  /blah blah
#cd /blah blah

Notice the # to denote "as root"
That  (mkdir)   /"named"  is your choice
Title: SOS!booting hang after installing VL7.0-STD-BETA-1.2
Post by: vincent2 on February 23, 2011, 03:28:58 am
 :o

Bon soiree!

Just tried the latest VL7.0-STD-BETA-1.2.iso from VL mirror , installation went smoothly on my sharp mebuis old laptop, once rebooting, problem arose:
Booting process 's hang at
--------------------------------------------------------------------------------
[3.173442][<c1003906>] kernel_thread_helper+0x6/0x10
-------------------------------------------------------------------------------
then  i had to press reset key again and again, never succeded in booting to vl7std beta1.2

what happened?
now no more vl6sohofinal on my laptop,sad can't use vector for my work again,
any quick remedy COMMAND/ CHEATING CODE 4 booting?


a  bien tot
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on February 23, 2011, 05:40:14 am
Vincent2

Was the  md5sum checked
Did you format the partitions where VL6 was - or   install the (Beta) lilo to Mbr -

You still have the VL6 disc ?
Use it to try & boot  either versions

If no go, use again to re-install lilo

 If that resurrects VL6 you  can access the Beta installation to check over
Conversely any Linux livecd or rescue media can do same

BTW -mem location 0x10 is   loader  BIOS interrupt subroutine to access screen output

Cheat codes:
If option to boot in textmode (tui(?)
See if  some variation of (-nox) or (-use vesa)  exists
Lacking pre-scripted options,  the exact boot sequence must be passed to kernel
boot vmlinuz (path) video = (example,  uvesafb:ywarp,1024   
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: GrannyGeek on February 23, 2011, 12:03:11 pm
rm-r--

Frankly, I don't understand a word of what you're saying.<g> I fear it will confuse non-technical users and will convince people new to Linux that it's all much too geeky for them and you need to use that command line that they dread.

I don't think ANYONE will go wrong using GUI Gparted during the partitioning step as long as they understand what a partition is and how you pick the partition on which you want to install and the consequences of picking the wrong one. I must say it's not that clear in Gparted until you catch on. It's *much* worse in cfdisk, which I happen to find quite easy, but I've been dealing with partitions in DOS, Windows, and Linux longer than some forum members have been alive.<g>

Have you actually installed VL7 beta1? Some of what you post sounds like you haven't and perhaps have never seen all the installation steps.
--GrannyGeek
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: GrannyGeek on February 23, 2011, 01:17:03 pm
Well, this is exactly what I was trying to do - mount partitions to different places, such as /, /home, etc. One of those places just happened to have a non-default name.

I'm afraid I'm quite confused about what you were doing and when you were doing it. I assume you're talking about the partitioning stage very early in the installation process. Yes? I'm writing from memory but I think it'll be close enough that you can figure out whatever I've missed.

I think the best way to proceed is to go through what I do when I install a new VL. First--does the drive on which you're going to install VL already have partitions? Or is it bare and in need of a partition being created? Either way, in Gparted (which will show all your hard drives) create or find the partition on which you want to install VectorLinux.

What I do for safety's sake is make a list of all my partitions and what's on them using the version of VectorLinux that is my main current operating system. For example, here was my list before I installed VL7 b1:
/dev/sda5    /mnt/win-i
/dev/sda6    /mnt/sohodeluxe
/dev/sda7    /mnt/alpha4.22
/dev/sda8    /mnt/vl6
/dev/sda9    swap
/dev/sda10  /mnt/vl7a4
/dev/sda11  /mnt/sohofinal

The mount directories I use for the partitions as listed in /etc/fstab have nothing much to do with GParted but are on my list so I know what I'm dealing with. My goal is to MAKE SURE I get VL installed where I want it without overwriting something I want to keep. I then look carefully over my partitions and decide where I want to install VectorLinux, beta1 in this case. I decided to install it in /mnt/sda10, getting rid of VL7 alpha 4. I repeat my thought process to make sure I'm going to put it where I want it. Then I circle /dev/sda10 on my list and write "install VL7b1 here."

Next, in GParted I look at the list of partitions on the drive and select /dev/sda10. Then I click on the mount point dropdown. I select / , the root file system, on which all the VL directories and subdirectories will be installed. On this multiVL system, I do not use a separate home directory. I'll explain why below. You will also need to select the file system you want to use for / . I usually pick ext3. There is also an option not to format, but you DON'T want that for the root filesystem.

If you do want a separate home directory for VL7, you then need to select one of the other existing partitions for VL7's /home directory. You select that partition and assign /home to the mount dropdown. Note that if you already have a /home partition that you want to use for VL7 and you don't want to lose data you have in that /home partition, you will not want it formatted, so don't select any file system or everything on that /home partition will disappear. If you want to keep what's on an existing /home by not formatting, VL7 will not wipe out the data but will overwrite some files.

Why would you want a separate partition for /tmp or /opt or anything else? Those directories will be created when VL is installed. With any directories as well as with /home, the advantage of preserving what is in them does not depend on having them in a separate partition. Ideally, you have an external hard drive (which I consider an absolute necessity today). Format the whole external drive with a Linux file system and a simple copy from your computer to the external drive will preserve your ownership and permissions. Or create a partition on the external drive just for Linux and format it with a Linux system. I have ext2 on my external drives. Copy whatever you want to preserve in a /home partition to the external drive before you do the installation of VL7. On second thought, a simple copy may mess up your ownership and permissions if you don't tell it to do it the right way, which I don't know how to do. So I use Midnight Commander (a fabulous program) as root (so I can write it anywhere) and I tell MC to Preserve Attributes. This has always worked splendidly for me. If you don't have a Linux-formatted file system to copy the directories or files to, you can tar the whole directory first and then copy the tarred file to FAT32 or NTFS or whatever file system is on the device. If you're using the external drive with Windows, too, remember that Windows doesn't see Linux-formatted drives or partitions. Partitioning the external device so you have a partition for Linux takes care of that. You will not be able to write to that partition with Windows.

The reason I do not use a separate /home partition on my multi-Linux systems is that the new installation will overwrite some of the files with its new versions of these files if I use the same user name and user home directory. That may mean the previous versions of Linux won't work right because the new versions of the files in /home are not compatible. You could get around this by creating a unique user with a unique home directory, but what's the point? I'd rather just copy back the data and settings I want from the external drive. Then I don't have to deal with ownership and permissions. I do have a separate /home directory on my laptop, which is VL6 Light only. When I install a new version of VL Light, I will reuse /home and not format it.

I prefer to avoid excess partitioning in all cases because it's very difficult to decide on the right size for the partitions. Almost invariably, as you use the installation, you find you didn't leave quite enough room in /home or /opt or /usr or whatever you put in a separate partition. Or you made the partition way too big and thus are wasting drive space. Since I see few, if any, advantages for separate partitions for all this stuff for a home or very small business user, I just put everything on / . Then the directories can expand as needed, using tbe full size of the / partition.

Don't confuse the "mount point" GParted is talking about with mounting partitions once VL is installed. You can do that with VASM, which also makes entries in /etc/fstab and creates directories in /mnt or wherever you want them. You can decide which partitions you want to be mounted automatically at startup while you're working with the mounter in VASM. If you don't want one mounted automatically, simply add ,noauto in the line that sets up the drive options in VASM after you decide where you want the drive mounted. Do not put a space between it and whatever comes before it. Here's what one line in my /etc/fstab looks like:
/dev/sdb6   /mnt/win-e  ntfs-3g  defaults,allow_other,umask=0,users,nls=utf8,noexec,noauto 0 0

I hope I didn't simply repeat stuff you already know all about. Keep us posted.
--GrannyGeek
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: GrannyGeek on February 23, 2011, 01:28:58 pm
 If you google on
kernel_thread_helper+0x6/0x10
you'll see a number of links that discuss the same problem. No solutions in my very limited reading, though.

I suggest trying a VectorLinux Live CD and seeing if you get the same problem. Also try a Live CD from another distro. This is just to see if the same hang happens with other versions or distros.
--GrannyGeek
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on February 23, 2011, 03:46:04 pm
Granny:

I really did not want to enter into any such exchange: However, distasteful as it may be, since you persist:
RESPECTFULLLY: please note
 
Sorry, all you have stated is your own reasons to avoid CLI options vs default utilities
PLEASE  re-read, Budulay DOES fully understand partitioning & options
(I see no reply to "is that "other" wording really in the VL partition script !)

 *Respectfully*   It is obvious you OTOH, have willfully restricted (your undeniable right) broader knowledge of that topic
- It is contended therefore - who then is using their own biases  to judge Re best procedures
   
= Inescapable conclusion -  self-admitted, limited  experience renders evaluations un-qualified

>  "so long as they  understand" = Personal  difficulties to understand obviate  presuming  to act as spokespersons for others
 
*DID*  I install  VL beta -  sorry,  my business not yours:
FYI - How do I know = "Behold-  old bugs are as the Phoenix - reborn again"   
 
 REQUESTED Cheat codes: You are familiar to VL (I saw no suggestions *until_after_the_ fact*  forthcoming - why)
Please note: My response was by pointing out -via simplified example
>  Without pre-scripted options, any  boot parameters are extremely  syntax specific - can leave many floundering

Are we  left to assume,   you then obliquely suggest...  I do so to flaunt vs  a genuine attempt to help

> " No solutions in my very limited reading, though."

Adjunct:  http://www.xs4all.nl/~lennartb/bootloaders/node3.html 
 
Title: Re: vl7 std beta 1.2 booting hang
Post by: vincent2 on February 23, 2011, 07:14:33 pm
Quote
Was the  md5sum checked
Did you format the partitions where VL6 was - or   install the (Beta) lilo to Mbr -

You still have the VL6 disc ?
Use it to try & boot  either versions

If no go, use again to re-install lilo

 If that resurrects VL6 you  can access the Beta installation to check over
Conversely any Linux livecd or rescue media can do same

BTW -mem location 0x10 is   loader  BIOS interrupt subroutine to access screen output

Cheat codes:
If option to boot in textmode (tui(?)
See if  some variation of (-nox) or (-use vesa)  exists
Lacking pre-scripted options,  the exact boot sequence must be passed to kernel
boot vmlinuz (path) video = (example,  uvesafb:ywarp,1024

Bonjour!

Thanks your reply!
after a few hours testing,

I tried booting with vl7std beta1.2 cd  and then prompted screen appeared , i just typed:
----------------------------
linux root=/dev/sda6  ro
----------------------------
booting went smoothly then i went vasm and reinstall LILO again, everything 's fine now......

while typing "linux root=/dev/hda6 ro" with VL7 std beta 12 CD and grub in a floppy disk ,booting still hang...
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: vincent2 on February 23, 2011, 09:05:31 pm
HI!
tested many times,
rt2500 usb wifi card just doesn't work properly(can't detect wifi signal from the router the one inch away ,not along mentioning wpa mode) under vl7 std beta1.2?
 according  kernel notes, it should be supported and work, in reality it went dummy....
Title: SAVAGE driver performance poor
Post by: vincent2 on February 23, 2011, 09:18:42 pm
Bonjour!

Under vl7 std beta1.2, mouse and keyboard still occasionally goes  dummy ,especially the laptop mouse almost goes dummy  more often than keyboard after one hour or two or  if heavy cpu  /igp loading almost immeidatlely..
also glxgears output  is very low for twisterK IGP on savage driver,only 30-50.....

pls. optimize the performANCE OF
savage driver on my Sharp mebius laptop(twisterK IGP + via KN133 based mb+amd athlon xp-m 1500+).....
 
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on February 23, 2011, 10:41:25 pm
Vincent2

Well done, it's  satisfying  to see you found a way to make it happen
(In below, consider anything within < >  as a command)

Reference: (hopefully this is now redundant)
Had you encountered further  boot (display) problems ,  a further  recourse would be to  suggest adding
 < vga = 771 > or similar @  bootup

http://en.wikipedia.org/wiki/VESA_BIOS_Extensions
http://www.mjmwired.net/kernel/Documentation/kernel-parameters.txt 

From above, it  can be seen why any forum in-depth discussion Re "cheat codes" has perils

Savage driver:

http://www.thinkwiki.org/wiki/S3_Savage_IX8
Determine if driver is loaded < lsmod >
Examine   /var/log/Xorg.0.log &/or Xorg.0.errors.log

Post content of /etc/X11/xorg.conf
------------------------------------------------
Wifi:
https://wiki.archlinux.org/index.php/Wireless_Setup

NOTE: reference to obsoleted rt2500 driver:

< Dmesg >  (check to determine if usb wifi device is  found/enabled
"dmesg > wifi " ( creates a file named "wifi"  of the "dmesg"  content)
Note: That file will reside in directory the command was run

From URL, please notice  recommended driver to use, may need to download
After which <lsmod> to see if it gets activated

 
Eth0,  Status  & configuration <# iwconfig>  <iwpriv>

HTH
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on February 23, 2011, 10:48:48 pm
Vincent2 > Disclaimer:

Wink - Above is hastily pondered "Linux" way - you may wish to wait for VL  specific methodology

Best wishes
Title: VectorLinux 7.0 Beta1.4 GDM theme error
Post by: vincent2 on February 24, 2011, 05:58:49 am
Bon Soiree!

Now upgraded to vl7std beta 1.4 the latest version,installation went smoothly, after rebooting,  before entering to GDM login window, there's prompted message all the time:
there was an error loading the theme FedoraInfinity,

can't open file :/usr/share/gdm/themes/FedoraInfinity/FedoraInfinity.xml

.........

how to fix?
which config file  does define these theme?

a bien tot
Title: how to change weather location
Post by: vincent2 on February 24, 2011, 06:08:35 am
Bon Soiree,

By the way, just wondering how I can change the weather location on Cairo-dock,tried many times, no success... i need  Saigon/hu chi ming  of vietnam and Dhaka of Bangladesh , seems not available in data base, any solution ?

a bien tot
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: nightflier on February 24, 2011, 07:53:01 am
Code: [Select]
$ uname -a
Linux vector.linux.net 2.6.37 #1 SMP Sun Feb 6 16:53:13 Local time zone must be set--see zic m i686 Intel(R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux
I've tried zoneset and dateset, the message about "Local time zone must be set--see zic m" persists.

Code: [Select]
root:# ldconfig
ldconfig: /usr/lib/libtalloc.so.2 is not a symbolic link
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on February 24, 2011, 09:16:19 am
Just a spurious message & the  time zone is correct ?

E.G.  /etc/localtime is a symklink  to /usr/share/zoneinfo/"your_country"/"your_zone"
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: uelsk8s on February 24, 2011, 09:40:18 am
Code: [Select]
$ uname -a
Linux vector.linux.net 2.6.37 #1 SMP Sun Feb 6 16:53:13 Local time zone must be set--see zic m i686 Intel(R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux
I've tried zoneset and dateset, the message about "Local time zone must be set--see zic m" persists.

This comes from the system the kernel was built on not the one it's running on.
I built the kernel in a chroot that did not have the timezone set.
I'll get it fixed before final.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on February 24, 2011, 09:43:20 am
Vincent2

So all previous glitches are now OK ? - You could do as before - find  newer beta

BTW see ""linux root=/dev/hda6 ro"  vs  "S" da
Also - Grub has own terms for devices
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on February 24, 2011, 07:39:45 pm
Upgraded to VL7.0-STD-BETA-1.3.iso

Unable to play an audio CD with mplayer,  audacious and exaile.

gnome-player plays, however, does not respond properly to controls like stop,
it starts replaying.

xine takes 40 seconds before it starts playing.

USB Flash drive does not mount.  Carema cannot be mounted.

:$ shotwell
shotwell: error while loading shared libraries: libexiv2.so.9: cannot open shared object file: No such file or directory
Made symlink to libexiv2.so.10 and shotwell opens, however, camera cannot be
mounted.

Opera plays flash

Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on February 25, 2011, 05:12:42 pm
Upgraded to VL7.0-STD-BETA-1.3.iso

Unable to play an audio CD with mplayer,  audacious and exaile.

gnome-player plays, however, does not respond properly to controls like stop,
it starts replaying.

xine takes 40 seconds before it starts playing.

USB Flash drive does not mount.  Camera cannot be mounted.

:$ shotwell
shotwell: error while loading shared libraries: libexiv2.so.9: cannot open shared object file: No such file or directory
Made symlink to libexiv2.so.10 and shotwell opens, however, camera cannot be
mounted.

Opera plays flash


Upgraded to VL7.0-STD-BETA-1.5.iso

No changes to above quote except audacious now playing audio CD.

exaile: No URI handler implemented for "cdda".

:$ shotwell
libusb couldn't open USB device /dev/bus/usb/001/001: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/001/002: Permission denied.
libusb requires write access to USB device nodes.
libusb couldn't open USB device /dev/bus/usb/001/005: Permission denied.
libusb requires write access to USB device nodes.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: nightflier on February 27, 2011, 03:20:46 pm
ldconfig: /usr/lib/libtalloc.so.2 is not a symbolic link

Believe I found why. The file exists in the aaa_elflibs package. Guess that prevents the libtalloc-2 package from creating the proper symlink.

EDIT: Or, it could be the copy of the file included in the samba package...
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: |nic| on February 28, 2011, 03:19:30 am
Hi,

I'm having touble with hibernate on vl7 beta1

when I try to hibernate with
Code: [Select]
hibernate -F /etc/hibernate/ram.conf
The notebook hibernates, but I can't get it out of it.
Is there another way to do it ?

cheers
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: nightflier on February 28, 2011, 04:50:25 pm
When I log in to text mode, I get the welcome messages twice. Same thing if I use "su -" (but not just "su").

Looks like /etc/profile.d/vasm.sh gets sourced by the login script, and then .bashrc?
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: nightflier on March 01, 2011, 05:59:04 am
Trying vcpufreq with p4-clockmod:
- userspace, performance and powersave OK
- ondemand or conservative:
Code: [Select]
Unable to set the desired scaling governor.. try modprobing corresponding governor module: # modprobe cpufreq_ondemand
Code: [Select]
root:# modprobe cpufreq_ondemand
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
Error persists.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: M0E-lnx on March 01, 2011, 06:04:26 am
When I log in to text mode, I get the welcome messages twice. Same thing if I use "su -" (but not just "su").

Looks like /etc/profile.d/vasm.sh gets sourced by the login script, and then .bashrc?

This annoyance is caused by your ~/.bash_profile

.bash_profile sources your ~/.bashrc again, so to get rid of the annoyance, what I do is change that line in ~/.bash_profile where is sources .bashrc like this
Code: [Select]
. ~/.bashrc > /dev/null 2>&1
That way, you only get the message once.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: nightflier on March 03, 2011, 04:44:25 pm
B1.6 via vinstall-iso-ng:
On reboot gets to:
Code: [Select]
ldconfig: Renaming of /etc/ld.so.cache~ to /etc/ld.so.cache failed: No such file or directory
gtk-update-icon-cache: Failed to open file /usr/share/icons/Faenza/.icon-theme-cache: File exists
(gtk-update-icon-cache:XXXX) GdkPixbuf - WARNING **: cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory
The last line repeats until I hit Ctrl-C, upon which it goes directly to text login screen without completing rest of initialization. I can run Autosetup, users, passwd etc, but the loop re-appears on next boot.

There is a directory /.hg with some junk in it. Digging down to /.hg/store/data/ I find a file referencing sbbuilder-0.4.12.2-noarch-5vl60.tlz
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on March 04, 2011, 05:32:00 pm
Upgraded to Beta-1.8.iso

Flash drive now mounting and an icon showing, however, not the usual vl-hot.
User can mount  volume and to unmount it asks to 'Eject Volume'

Camera can be mounted by user. Same icon as for flash drive. Shotwell  opens
pictures of camera.

More testing later.

exaile not playing audio CD.

gnome-player open with Audio-Disk-File-Manager will not play.
Error Failed to open cdda://sr0/Track%208.wav.

opening gnome-player from Menu will play, however, does not react properly 
to controls.


Audacious now playing audio CD.

xine now playing audio CD immediately. mp4 plays picture only.

CD now being ejected by clicking eject on icon.

Flash playing in Opera.

abiword, gnumeric will not open: Bus error

Menu-Accessories-root-terminal does not open after given password.

Now is my Tea-Time. ;D
What wonderful teas the Chinese do produce.

Fluxbox running well!

Menu-Terminal  Emulator: Failed to execute default Terminal Emulator. Input/output error.

Menu-System/Accessories-Terminal produces nothing.



Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: GrannyGeek on March 05, 2011, 07:44:57 pm
I got a new computer to replace my geriatric 1.3 GHz Celeron. It's a HP Debranded Sempron LE-1300 with 2 gigs RAM, NVidia nForce 430 chipset and GeForce 6150SE graphics. This is a slow CPU, single core, but considerably faster than the Celeron computer. It is also upgradable to multicore AMD processors. It is all-SATA and totally different from my old Celeron desktop. The Celeron was a very Linux-friendly computer. I was holding my breath that the new Sempron would continue that tradition. So far, so good. Video, wired network, sound worked without effort on my part.

I got the new computer because it had modern things I wanted, such as SATA support, support for huge  drives, and  PCI-e. Also, it was very inexpensive. It appears to be brand new and I think HP wanted to clear out inventory. The CPU is slow but it also runs very cool and uses little power. I wasn't looking for anything near state-of-the-art. If it proves to be too slow as I use it for a while, I'll upgrade the CPU.

I want to transfer my Linuxes from the old computer. My first attempt with tar files did not work and I didn't want to wait for ideas about how to do it, so I installed VL7 beta 1.8 from a CD I burned. It installed without issues, though I had to use 800x600 in order to have a picture that fit on the monitor screen. I was using an extremely old 1024x768 LCD monitor. However, when I first rebooted after installation so I could continue with vasm, the startup stopped at a point pretty deep into  loading. I turned off the computer and booted again. Stopped at the same point. It all happened too fast for me to get much information about where it stopped.

So I tried installing with my VL7 beta 1 CD. This went fine and the first reboot loaded VL without a stop. I always boot at runlevel 2. The open source nv driver is loading. I do have an issue of the desktop screen overflowing the monitor screen. The new computer now has its permanent monitor attached: a 19" LCD with 1280x1024 resolution. I did rerun X setup with VASM. I'm wondering if this is an NVidia problem, as VL7b1 with the same monitor and the old computer had no screen-not-fitting problems. That computer had a Radeon 9200 video card and used the open source radeon driver.

Anyway, whatever difference crept in between VL7 beta 1 and VL7 beta 1.8 gave me a severe problem. Once I get the desktop screen aligned with the monitor, things should be pretty good.
--GrannyGeek
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: vector on March 05, 2011, 08:34:36 pm
Quote
However, when I first rebooted after installation so I could continue with vasm, the startup stopped at a point pretty deep into  loading. I turned off the computer and booted again. Stopped at the same point. It all happened too fast for me to get much information about where it stopped.
Granny......... we tried something new with beta 1.8 which is supposed to reboot your computer. Would you mind trying beta1.7 as its the same but without the new code. Trying to find out if that is source of your problem....... ???

Cheers,
Vec
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on March 05, 2011, 10:40:40 pm
Trying to upgrade libgphoto2 reports failure:
libgphoto2: Depends: hal >= 0.5.14-i586-4vl70

In Beta-1.8 there is only hal-0.5.14-i486-3
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: budulay on March 06, 2011, 12:50:35 pm
No luck with Beta 1.8:
On the first boot it said it had to run mkfontdir and some other stuff, upon completion of which it said that VL installation was complete and it had to reboot. Well, after it did reboot, it gets to the same place and reboots again. And then just keeps rebooting whenever it gets there.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on March 06, 2011, 01:16:43 pm
Budulay

Is your locale set correctly (affects fonts)

How is Utf-8 /unicode  utilized
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: GrannyGeek on March 06, 2011, 04:40:25 pm
Granny......... we tried something new with beta 1.8 which is supposed to reboot your computer. Would you mind trying beta1.7 as its the same but without the new code. Trying to find out if that is source of your problem....... ???

I would, except that I'm no longer having the problem. When I couldn't get the right aspect ratio for the screen, I decided to install beta 1.8 to another partition to see if I could get the correct ratio there--and also to see if the reboot problem repeated on a new installation. When I originally installed VL7b1 and 1.8 on my new computer, it was attached to a 15" LCD monitor. I wondered if I'd have the same problem if I installed with the computer attached to the correct monitor (19", 1280x1024). This time when I did the first reboot in beta 1.8, it got to a login prompt. I've done a few reboots, warm and cold, and the hang hasn't repeated.

I still have the aspect ratio problem. It should be 5:4 but it looks like 4:5. Things are distorted so that the screen is too long and disappears at the bottom of the monitor. I didn't use the monitor buttons to resize the screen because doing that messes things up for other OSes or VL versions. I found that running vxconf set nouveau as the driver. I think that's the "improved" open source NVidia driver. Actually, when I used that one, I got a screen of garbage. The nv driver messes up the aspect ratio for the 1280x1024 resolution. I discovered that the vesa driver does okay at 1024x768. I haven't tried nv or nouveau at 1024x768. I haven't tried the proprietary NVidia driver, preferring to wait until it's included in VL7. I'll use 1024x768 until there's a solution for the 1280x1024 aspect ratio.

My old computer with an ATI Radeon 9200 card had no problems displaying 1280x1024 correctly, so my guess is that this is somehow related to NVidia.

Other than the aspect ratio, the things I've tried so far in beta 1.8 have worked fine.
--GrannyGeek
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on March 06, 2011, 05:38:52 pm
W/due regard to this topic as to report beta results, that ignores why any may be  reported

This "aspect ratio" appears to be a common complaint
As far as can be readily noted, it's directly related to ability of any driver  DMA being adequately  probed,
then  applying  found parameters

Varied utilities may assist, (xrandr,  xvidtune etc)
While all above is known to users experiencing such problems, how to aleviate is their  question

ATI catalyst doesn't support Linux running older cards~  often requiring  generic drivers (ati, vesa)
Generic "nv" may not render virtual sizing correctly
Nouveau seems an improvement to nv

Opensource released proprietary drivers are still best (unless strict observations to Gnu.org  Re FOSS is desired) 

https://bugzilla.redhat.com/show_bug.cgi?id=562255

Example - View above, download bug file, note  results

How any user wishes to apply data is a personal choice:

There is no right vs wrong, all boils down to matter of least inconvenience  desired vs desire
to accept status quo or keep the faith in any developers' capability
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Vink8 on March 07, 2011, 08:33:21 am
I am an absolute beginner, therefore have patience!

Inside the file of recapitulation

http://vectorlinux.osuosl.org/veclinux-7.0/packages/PACKAGES.TXT (http://vectorlinux.osuosl.org/veclinux-7.0/packages/PACKAGES.TXT)

@Vector (or to whom it may concern)
pay attention to

requiredbuilder-0.16.2-i586-2vl59.txz
chrony-1.24-i586-1vl60.txz
directfb-1.4.3-i586-2vl60.txz
gslapt-0.5.3d-i586-1vl60.txz
mingetty-1.08-i586-1vl60.txz
os-prober-1.29-i586-3vl60.txz
pkgtools-tukaani-1.2.5-i586-1vl60.txz
slapt-get-0.10.2g-i586-1vl60.txz
vcpufreq-2.4.2-i586-1vl60.txz
vlart-6.0-noarch-1vl60.txz
vlgui-6.0-noarch-1vl60.txz
vlinit-6.0-noarch-4vl60.txz
xdelta-1.1.4-i586-1vl60.txz

seem intended to Vec5.9 Vec6

to dep. request of
gambas2-runtime-2.22.0-i586-2vl70.txz
gksu-2.0.2-i586-1vl70.txz
libproxy-0.4.6-i586-1vl70.txz
MPlayer-20101119-i586-1vl70.txz

also @ Kidd and @ rbistolfi
inside
sbbuilder-0.4.12.4-noarch-1vl70.txz
PACKAGE REQUIRED:  perl >= 5.8.0-i586-1vl59 | perl >= 5.8.0-i586-1vl60


Wishing a clear time to all the men and women of good wish!

Until feb 2011 beta, I have repeatedly found this line
|-----handy-ruler------------------------------------------------------|

(After DESCRIPTION: and Before the Real description)

I believe that a 'quality packager' have to 'polish up with care' files before up-link (to avoid appear not nedded lines like this 12^ as inside [old link] http://vectorlinux.osuosl.org/veclinux-7.0/packages/a/consolekit-0.4.3-i586-1vl70.meta (http://vectorlinux.osuosl.org/veclinux-7.0/packages/a/consolekit-0.4.3-i586-1vl70.meta)).

(For instance inside:

atkmm, autoconf,
cairomm, consolekit, cython
dbus, dbus-glib,
epydoc,
perl, pstoedit, python-lxml,
vala,

PACKAGE NAME:  directfb-1.4.3-i586-2vl60.txz
directfb|-----handy-ruler------------------------------------------------------|
directfb: Packager: vl60@vector.Linux.vnet on 27-Apr-2010

fribidi,
gc, glibmm, gnome-common, goffice, gsl, gst-python, gtk-murrine-engine, gtkmathview, gtkmm,
hyphen,
libcanberra, libcfg+, libdc1394, libffi, libgee, libgexiv2, liblastfm
and so on...)

@ nightflier
I'm not requested 'What' ruler is, but (if you 'want talk') 'Why' nobody see and erased all this (duplicated, no more needed) rulers before 'yesterday nite' beta!
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on March 07, 2011, 07:05:33 pm
Vink

How that packages list is generated may be automated
What quality assurance checks are run is unknown_

Maintainers do best ,  mistakes  :o "will"  happen,  all Vectorites are encouraged to participate
w/this effort (*BIG job)  to prepare V6 Pkgs to V7 (Pls note how rapidly   beta versions are uploaded)
This is ALL part & parcel of  polishing any version prior to release class announcements

 If you believe present procedures are flawed:
VL community would welcome any  script supplied  to check data-base for errors

E.G.: Naming conventions  of Pkgs, version corectness etal

Please NOTE:    There ARE  guides posted to use of sbbuilder

Since I have often  expressed  :-[   opinions Re what may seem preferable option to solve  temporary VL glitches
(using VL default utilities vs CLI methods)

It seems only fair to point out, critiquing sans offering alternatives is not helpful to any

However, as all are  personal viewpoints, the final arbiter is acceptance or rejection by peers

Best wishes


 
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: hata_ph on March 07, 2011, 08:38:59 pm
While installing JDK in VL7 Beta 1 I encounter some sh script in /etc/profile.d will not run at boot time. I have to modify my .bashrc as below to make my jdk.sh to run. Dunno is this a bug or not...just want to share it out... :P

Quote
In your /etc/bashrc you have a line near the bottom:

"PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/usr/share/pvm3/".

If I'm right, thats your prob.

Change to
PATH=$PATH:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/usr/share/pvm3/

http://www.mail-archive.com/slug@slug.org.au/msg58115.html
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on March 07, 2011, 09:28:38 pm
Hata_ph

Suggestions only:

(dot) bashrc is parsed last @ bootup - do you want that App to run every time ?

(use)  Whereis JDK (name of executable Note the location

The default  command search path is configured  by install

 su -l (type root password)

cd /home/your_name

env |grep PATH > rootpath.txt

exit (to user command prompt)
 env|grep PATH > userpath.txt

diff  r*t   u*t  (read line variance)

Note do NOT use "sudo"  for 1st grep ~ sudo inherits the user's environment
Once becoming root, remember to cd to user's home directory
By default,  you would be in /root (confirm using command pwd )

Install locations Esp, executables, vary to distro E.G. /usr/local,  /usr/share etc

Much the same applies to sysVinit vs Slackware use of BSD variant of initiate directories

Example. initd/ content (rc1 <>rc4 etc) 

 HTH



Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on March 07, 2011, 10:16:13 pm
http://www.linuxfromscratch.org/blfs/view/6.3/general/jdk.html
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: hata_ph on March 07, 2011, 10:23:26 pm
Thanks for the link but I have manage to install JDK myself. But what I dun understand is when I create a jdk.sh/jsk.csh under /etc/profile.d, it did not execute at boot time. Isn't everything script with execute right will be executed at boot time?
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on March 07, 2011, 10:55:02 pm
D_ _ n

This is Vector specific - where initiate services get located:

E.G., What is content of /etc/rc.d/initd ~ Are they symlinks or actual run commands

Are you trying to develop Java Apps/browser enhancements or ??
Does your install include IDE wrappers, debug utilities ?
(Much easier to "step in/out" JIT Java scripts)

Most Distros already include JRE for Java/Javascript  - Browsers search, install plug-ins

Most home use, enabling Java for  Browser interactions ~ is a considerable security risk

(Linux is immune from viruses , NOT embedded graphical  malware -most of which
rely on Java to execute BECAUSE it is a universal to most all O/systems)


Obviously,  it's  NOMB ~ It only suggested to please consider ~    if presently  having problems sorting out VL initiate sequences
you may wish to re-evaluate logic  of original intent

EDIT:  my /etc/profile.d  directory contains - not just a start   command:

It exports environment path
Quote
export MANPATH="${JAVA_HOME}/man:${MANPATH}"
export JDK_HOME=${JAVA_HOME}
export JAVAC=${JDK_HOME}/bin/javac
unset gentoo_user_vm gentoo_system_vm user_id

To ensure any  change "sticks" after session, it may be required to update (system config) environment

 
Best luck
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: hata_ph on March 08, 2011, 12:00:35 am
I was trying to build package for VL7 which require JDK. Below is my /etc/profile.d/jdk.sh

Quote
#!/bin/sh
export JAVA_HOME=/usr/lib/java
export MANPATH="${MANPATH}:${JAVA_HOME}/man"
export PATH="${PATH}:${JAVA_HOME}/bin:${JAVA_HOME}/jre/bin"
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on March 08, 2011, 07:58:36 am
Hata_ph

Ahh, in that case,  I was under impression sbbuilder  handled all build specifics:
Profiles, paths,  directory placements

How does your present work-around affect clean build environment ?

P.S What then is any  views Re enhancing usefulness, such as via  inclusion of  IDE front-end plus de-bug utility

Perhaps - JDK/extra tools , would be better as part of a "developer package"   along with Gcc, kernel sources etc.

(Not as dependency need of other Pkg/s:(  An after-thought of ~   Since JDK is there ,  someone may  want to explore
Java vs Python or whatever



Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: hata_ph on March 08, 2011, 04:22:10 pm
What I did is modify my .bashrc as below. Actually it is not a huge problem as one can find the solution from the internet, just that I want to mention it out what i face while using VL7B1 (dunno do this problem happen to VL6 or not).

Quote
In your /etc/bashrc you have a line near the bottom:

"PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/usr/share/pvm3/".

If I'm right, thats your prob.

Change to
PATH=$PATH:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/usr/share/pvm3/

Another (more secure) way to temporary activate the path is run . /etc/profile.d/jdk.sh in terminal as root (the effect only for that session of console).
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on March 08, 2011, 07:40:31 pm
That appears to confirm earlier noted suspicions:

User's profile path must be amended else session only

Your solution may be work-around, but suits Tmp need, satisfying a dependency to allow
building another Pkg

Was your JDK install from a VL repository or manual ?
(If so, wondering as did you - Why incorrect path)

Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: hata_ph on March 08, 2011, 08:30:47 pm
I manually install the latest JDK as i cannot find it in the VL7 repository...
If I want to build JDK for VL7 i may need to get more detail of how to add the JDK path to VL...
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: uelsk8s on March 08, 2011, 08:58:39 pm
I manually install the latest JDK as i cannot find it in the VL7 repository...
If I want to build JDK for VL7 i may need to get more detail of how to add the JDK path to VL...
the way you did it from profile.d is correct.
the bug will be gone from next Beta.

Thanks for finding it.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on March 09, 2011, 12:42:56 am
Caveats /tips from above:

Placement of App run (.sh)  to /etc/profile.d was correct - syntax was not (the bug)

Two concerns Re paths,  were mentioned in that suggested work-around from Web source:

Behaviour of shell child forked processes, log-in shell vs session

If developer uses a virtual machine to re-master,  consideration should be given to user ID
Code: [Select]
  # Please make sure that this script is POSIX compliant
  # The root user uses the system vm
if [ "${user_id}" != 0 -a -L "${root_user_vm}" ]; then
export JAVA_HOME=${root_user_vm}
# Otherwise set to the current system vm
elif [ -L /etc/java-config-2/current-system-vm ]; then
export JAVA_HOME=${root_system_vm}
f

One more
Code: [Select]
if [ -z "${UID}" ] ; then
# id lives in /usr/bin which might not be mounted
if type id >/dev/null 2>/dev/null ; then
user_id=$(id -u)
else
[ "${USER}" = "root" ] && user_id=0
fi
fi
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on March 10, 2011, 05:54:48 pm
upgraded to Beta-1.9

# /sbin/vl-hot-config
bash: /sbin/vl-hot-config: /usr/bin/gbx: bad interpreter: No such file or directory

 which gbx
which: no gbx in .....

That VectorLinux screensaver is really cool. ;D
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: budulay on March 12, 2011, 12:19:45 pm
Beta 1.9 fixes infinite reboots from 1.8.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on March 12, 2011, 07:50:31 pm
New install of Beta-1.9

user cannot mount flash drive when clicking on USB icon:  Failed to mount "4.0 GB Filesystem", Not Authorized
If in fstab /dev/sdc1 is enabled it can be mounted by sudo, however, then no
USB icon shows.

Loggin-out of X console reports:
thunar-volman: Unsupported USB device type.
thunar-volman: Unknown block device type.

Logged-in as root. Flash drive can be mounted with USB icon.
Command 'mount' then shows /dev/sdc1 is mounted even so it is disabled in fstab.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: fogpipe on March 13, 2011, 03:32:58 am
The intel driver (2.14) in the latest beta  is unstable, x quits after not too long with this error:
[   733.587] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error
[   733.587] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error
[   733.587] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error
[   733.587] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error

I have the intel 845g variant of the intel i915. The driver (2.13) in the first beta i tried  was much more stable and noticeably faster.

Much more about this here: http://www.google.com/search?q=intel_uxa_prepare_access%3A+bo+map+failed%3A+Input%2Foutput+error&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a

check the top two links

EDIT: I uninstalled the 2.14 intel driver and installed the 2.13 driver from the older beta, xf86-video-intel-2.13.0-i486-1vl70.txz. X seems stable and fast, im tailing the Xorg log and getting no errors. If it gets wonky ill let you know.

Ok, looks like the 2.13 drivers suffer the same problem, they last longer tho and after they start throwing the above error, it doesnt kill X, it just starts rendering in software (vesa?) mode. Very very slowly.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: uelsk8s on March 14, 2011, 07:08:43 am
fogpipe,
can you try the kernel here: http://vectorlinux.osuosl.org/veclinux-7.0/kernels/2.6.37.3-1vl70/kernel-2.6.37.3-i686-1vl70.txz
http://vectorlinux.osuosl.org/veclinux-7.0/kernels/2.6.37.3-1vl70/kernel-modules-2.6.37.3-i686-1vl70.txz

let us know if there are any changes.

Thanks,
Uelsk8s
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: fogpipe on March 14, 2011, 07:23:56 am
fogpipe,
can you try the kernel here: http://vectorlinux.osuosl.org/veclinux-7.0/kernels/2.6.37.3-1vl70/kernel-2.6.37.3-i686-1vl70.txz
http://vectorlinux.osuosl.org/veclinux-7.0/kernels/2.6.37.3-1vl70/kernel-modules-2.6.37.3-i686-1vl70.txz

let us know if there are any changes.

Thanks,
Uelsk8s

I will try that thanks :) I installed the new 1.10 beta tho and have another problem for another topic. but i will try that kernel.

EDIT: Using beta 1.10. Installed the new kernel, changed the links in boot, booted to the new kernel, did a depmod -a just to make sure and i will let you know how it goes thanks :)

New kernel (2.6.37.3-i686-1vl70), frozen video after not too long here is the last bit of the syslog at the time:

Quote
Mar 14 11:05:12 VL110beta kernel: [    3.946402] VFS: Mounted root (xfs filesystem) readonly on device 8:21.
Mar 14 11:05:12 VL110beta kernel: [    7.730259] ACPI: resource 0000:00:1f.3 [io  0x1880-0x189f] conflicts with ACPI region SBUS [??? 0x00001880-0x0000188f flags 0x53]
Mar 14 11:05:12 VL110beta kernel: [    9.809416] fb: conflicting fb hw usage inteldrmfb vs VGA16 VGA - removing generic driver
Mar 14 11:05:12 VL110beta kernel: [    9.826183] Console: switching to colour VGA+ 80x25
Mar 14 11:05:12 VL110beta kernel: [    9.893466] Console: switching to colour frame buffer device 80x30
Mar 14 11:05:24 VL110beta avahi-daemon[1785]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Mar 14 11:06:05 VL110beta gdm-binary[1973]: no suitable security token driver could be found
Mar 14 11:22:44 VL110beta kernel: [ 1069.661023] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 14 11:22:44 VL110beta kernel: [ 1069.670223] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -11 (awaiting 143809 at 143807, next 143810)
Mar 14 11:22:44 VL110beta kernel: [ 1069.997027] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Mar 14 11:22:44 VL110beta kernel: [ 1069.997135] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -11 (awaiting 143815 at 143807, next 143816)
Mar 14 11:22:44 VL110beta kernel: [ 1069.997243] [drm:i915_reset] *ERROR* GPU hanging too fast, declaring wedged!
Mar 14 11:22:44 VL110beta kernel: [ 1069.997250] [drm:i915_reset] *ERROR* Failed to reset chip.

The ACPI errors are one of the reasons i immediately recompile kernels to work on this crackerjack box hardware.

And here is the last bit of the Xorg log at the time:
Quote
[  1357.744] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error
[  1357.745] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error
[  1357.745] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error
[  1357.746] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error
[  1357.746] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error
[  1357.750] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error
[  1357.751] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error

I appreciate the attempted help, i have vl 6 running stably with a few tweaks in xorg and the kernel, and im thankful for that, i guess i will deal with vl7 in about the same way when its final.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: fogpipe on March 14, 2011, 07:32:04 am
I just installed the 1.10 beta and am getting errors trying to start firefox.

This is a fresh install with a newly created user. During the install i kept my home partition, but the user is newly created. No modifications to the install at all except creating that user.
I booted from the install cd with the commandline "linux root=/dev/sdb5 ro video=640x480.
The only unusual thing i noticed during the install was that it said that it was 802 mb and it was installing from a iirc 700 mb cd. If thats the problem i can always install from a hd partition. Screenshot of the errors attached. The input / output error dialog box is trying to start from the panel icon.

EDIT: the other apps i have tried work fine, posting this from the 1.10 beta using opera
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on March 14, 2011, 09:22:18 am
ldd  Intel proprietary download

man rdev

NOTE warnings

rdev -v /dev/sd_path option


grep -e EE -e WW /var/log/Xorg.0.log

Now redundant ~ but after lengthy exchanges, you are now appending  "video="  to boot string in VL 6

That was suggested way back in original  suggestions to Colonel Panic

Code: [Select]
Edit lilo.conf
(Example: Include line)  Vga=791 (see URL, choose from list)
(Alternate example) append="video=vesafb:mtrr,ywrap,1024x768-32@85"

(If you check, that was before you posted outre theories  Re frame buffers)

Until Intel (& other OEM suppliers) stop  enforcing need for fbcon etc, work-arounds;

Upstream Xorg, kernel (KMS)... then ultimately Distro developers  > have little FOSS alternatives  to correct
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on March 14, 2011, 07:33:44 pm
Beta-1.10

same problem with flash drive as in Beta-1.9/6/7

Only in Beta-1.8 there was no such problem as posted then.

user cannot mount flash drive when clicking on USB icon:  "Failed to mount "4.0 GB Filesystem", Not Authorized"
If in fstab /dev/sdc1 is enabled it can be mounted by sudo, however, then no
USB icon shows.

Loggin-out of X, console reports:
thunar-volman: Unsupported USB device type.
thunar-volman: Unknown block device type.

Logged-in as root. Flash drive can be mounted with USB icon.
Command 'mount' then shows /dev/sdc1 is mounted even so it is disabled in fstab.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: uelsk8s on March 15, 2011, 06:57:00 am
Pita,
How are you getting to the desktop?
with gdm, or from startx in runlevel 2?
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: fogpipe on March 15, 2011, 10:03:41 am
My firefox problem was apparently due to xulrunner not being installed, dont know what happend there.
I have downgraded to xf86-video-intel-2.13.0 and the i486 version of libdrm and x is alot more stable, in fact with that and the latest kernel compiled with no acpi, X hasnt crashed once in the last 14 hours or so of almost continual use.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on March 15, 2011, 05:56:07 pm
Pita,
How are you getting to the desktop?
with gdm, or from startx in runlevel 2?

99.9 % of time I start with startx in runlevel 2.
For curiosity I have tried gdm in VL7* would not remember now if there
was a difference. Will check it out.
Anyhow, eventually it should not make a difference just as in VL6-STD.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on March 15, 2011, 11:19:02 pm
Pita,
How are you getting to the desktop?
with gdm, or from startx in runlevel 2?

99.9 % of time I start with startx in runlevel 2.
For curiosity I have tried gdm in VL7* would not remember now if there
was a difference. Will check it out.
Anyhow, eventually it should not make a difference just as in VL6-STD.

Started in runlevel 4 and no more such problem. Hope that will not be
the furture for VL7. GrannyGeek take note!
Cannot start fluxbox since there is no provision for it in gdm Session.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: vector on March 15, 2011, 11:37:41 pm
Quote
Started in runlevel 4 and no more such problem. Hope that will not be
the furture for VL7. GrannyGeek take note!
Pita....... try startxfce4 instead of startx from runlevel 2 see if everything goes ok after that
let us know

Cheers,
Vec
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: GrannyGeek on March 16, 2011, 09:55:35 am
Started in runlevel 4 and no more such problem. Hope that will not be
the furture for VL7. GrannyGeek take note!
Cannot start fluxbox since there is no provision for it in gdm Session.

I'm not sure what problem you're referring to. I always use runlevel 2 and startxfce4 and have no severe problems unless I'm having a general X problem.

I got a new computer a couple of weeks ago with NVidia 6150SE onboard graphics. I've had a problem getting my monitor's native 1280x1024 resolution in the correct 5:4 aspect ratio. It's running okay at 1024x768. I haven't had time to see if I can solve the problem but today I hope to install VL6 SOHO Deluxe on it and will see if the problem persists. I think SOHO Deluxe may include the proprietary NVidia driver, which I think is what I need in VL7 but it's not there yet.

This computer is my main test machine, replacing my ancient 1.3 GHz Celeron Tualatin. Linux loved that computer and the computer loved Linux. I hated retiring it, but it couldn't run streaming video without annoying choppiness and it didn't support modern things like SATA, 48-bit LBA, or PCI-e. I got tired of suffering so when I saw this refurbed computer for a very good price, I got it. As it turns out, I think the computer was new and HP was just getting rid of old inventory. So far I'm very happy with it but I've installed just VL7 beta1 and 1.8. I was going to copy over my VL partitions for different versions but decided I'd be better off installing "clean" because the hardware is very different from the Celeron's hardware. The old Celeron had a Radeon 9200 graphics card and ran well with the xorg radeon driver and gave me 1280x1024 with no work on my part.
--GrannyGeek
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on March 16, 2011, 07:58:20 pm
Quote
Started in runlevel 4 and no more such problem. Hope that will not be
the furture for VL7. GrannyGeek take note!
Pita....... try startxfce4 instead of startx from runlevel 2 see if everything goes ok after that
let us know

Cheers,
Vec

That's what I have been doing all the time while testing Alpha/Beta in runlevel 2 on console
startxfce4 which causes the problem that user cannot mount flash drive or camera as explained.
Just to make sure I did it now again and the result is the same unlike with runlevel 4.

I will mention as well that in xfce4 runlevel 2 or 4 if I give the command
"startx /usr/bin/startfluxbox -- :2" fluxbox will open, however, commands do not
show in fluxbox, like opening xterm, instead they are all executed and show-up
in xfce4 (Alt-F7). This is not the case in VL6-STD.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: M0E-lnx on March 17, 2011, 08:32:00 am
I dont know if this has been addressed yet or not, but as of
Code: [Select]
root:# cat /etc/vector-version
Vector Linux 7.0 STD Beta 2 built on MAR-12-2011
Running vsuper gives an error
Code: [Select]
vluser:$ vsuper vpackager
/usr/bin/vpackager
gksu: error while loading shared libraries: libgnome-keyring.so.0: cannot open shared object file: No such file or directory
gnome-keyring seems to be installed, but libgnome-keyring is an entirely different package, and it is not present in this release.
Installing libgnome-keyring gets us past that error, but pops another one
Code: [Select]
gksu: error while loading shared libraries: libORBit-2.so.0: cannot open shared object file: No such file or directory
So, bottom line, this libgnome-keyring and ORBit2 need to be added to the release before final comes out.

Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: hata_ph on March 17, 2011, 11:24:22 pm
Running VL7Beta2 and notice firefox name is change to Namoroka...and missing icon issue with firefox in the menu too :P
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: GrannyGeek on March 18, 2011, 12:19:09 pm
I'm using VL7 b1.8 on my new Sempron computer. When I try to start Midnight Commander as root, it doesn't load. When I tried xterm -e mc, I got this message:
root:# xterm -e mc
Warning: Tried to connect to session manager, Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed

I don't understand the message and I certainly don't know what to do about the problem. I can start Thunar as root.

On the new computer I installed VL6 SOHO Deluxe a couple of days ago. It offers the proprietary NVidia driver and I got a very nice 1280x1024 screen, which is the native resolution of the monitor. In VL7 b1.8 or VL7 b1 I get a badly distorted GUI screen in the wrong aspect ratio and the best I've been able to do is 1024x768 with the VESA driver. I suspected the problem would be fixed with the proprietary NVidia driver, but it's not included with VL7 so far.

I see mention of beta 2. Are we supposed to be testing that? Also, will the proprietary NVidia drivers be included in VL7 at some point? I'm very unhappy with 1024x768.
--GrannyGeek
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: rm-r on March 18, 2011, 08:16:49 pm
Granny:

Stating the obvious ~ VL7 *BETA* versions will remain in constant state of flux
http://vectorlinux.osuosl.org/veclinux-7.0/iso-test/

(Have you dismissed  an alternative to installing -  using  Virtual box)

http://vectorlinux.com/downloads

I do not wish to presume  anything,  just requesting clarification - as prior  suggestions were rebuffed as: 
Quote
in alpha/beta/rc testing we're trying to find what doesn't work so it can be fixed.
We're not trying to get it to work *just for us*

Quote
I can start Thunar as root.

If you are now inviting possible solutions ?

Google
Code: [Select]
"user xterm authentication"
What happens when you drop to a console I.E.(Ctrl+Alt+F2) log in as user, execute  mc

How much do you desire nVidia proprietary drivers_

All are readily available on Web - install nearly painless

Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on March 18, 2011, 11:01:10 pm
It seems gdm is wired to open only xfce4.  No matter how I set to open fluxbox
only xfce4 will open. /etc/X11/xinit/@xinit.rc points to xinitrc.fluxbox,
~/.xinitrc ends: "exec /usr/bin/startfluxbox", xwmconfig is set to open fluxbox,
yet gdm will only open xfce4 even when last session was fluxbox. There is
naturally no provision in gdm to open fluxbox which is part of the install.

If I use xdm insted of gdm fluxbox does open as first choice. If I set @xinitrc to
point to xinitrc.xfce xfce4 will open, however, flush drives cannot be mounted by user.

mc will open in my box any way as root.

root:# thunar
Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1
keyInvalid MIT-MAGIC-COOKIE-1 keyThunar: Cannot open display:

root:# mc
Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1
keyInvalid MIT-MAGIC-COOKIE-1 key.
and mc opens.
Title: Re: BUGS
Post by: M0E-lnx on March 19, 2011, 05:23:41 am
Open query to VL community &  Esp development "team" 
-----------------------------------------------------------------------------------------------------
Users : Shouldn't any bug reports address only latest BETA version  ?
(Seems  obvious - earlier versions *may* now be redundant)

Older versions -post as help request in own new thread
------------------------------------------------------------------------------------------------------
Please consider, below  has been mentioned before:  w/scant  official consensus:

~ Development is AD-HOC
~  VL is now how old -w/still no *FORMAL*  method adopted to report/fix  bugs

Same   methods employed...  Forum  version announcements (which get posted to_ by "helpme" users ) 
 Multiple catch-all " development" topic headers ~
*'BUG* headers - where all soon becomes buried/side-tracked
 
Is there no database for "developers"  to consult:  (why do old bugs often  re-appear)

Oh...if i had a dime for every time i suggested a bug tracker and to move bug reports out of the forums.... but despite my best efforts, seems to be an impossible change for this community
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Pita on March 19, 2011, 05:07:04 pm
Thnx Moe - lnx

Not to single anyone out - but latest PITA post is good example - we have no idea which version he is "reporting"


It is naturally the latest which I always put on top of the first post for a new version. Thereafter I assume it had been
read/noticed and do not repeat it any more.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: GrannyGeek on March 19, 2011, 09:55:50 pm
I had my computer off overnight and after I booted today, I was able to start Midnight Commander as root. I didn't try Thunar. I must have run into a temporary glitch.

I would install the proprietary NVidia driver but I don't want to bother if beta 2 is imminent.

Flash is working with Opera (it didn't for me in beta 1 on the old computer).
--GrannyGeek
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Andy Price on March 20, 2011, 12:12:06 am
Just got back after three weeks away and eagerly downloaded beta 1.10 for a try out. Still no joy with the text installer on my IBM p4 or Compaq P3, the machines just lock up a few seconds after the uncompressing the kernel message. I'm not sure if it's relevant, but it misses out the "loading init.lz" stage which appears in the GUI installer. Am I the only one having problems with the text installer or am I the only one using it?!

Installation with the GUI installer went off OK. The screen resoluton was set rather low (800x600) but could be adjusted after logging in. The login screen is changed from earlier betas and looks less attractive now, especially as it was displayed at a low resolution (for me). Incidentally, the installer identified the iso as Beta2, not 1.10 as downloaded.

It's good to see the number of installed apps steadily increasing, along with the expanding reps. But I couldn't successfully load the extras rep from any of the sources I tried - is it supposed to be active yet? Testing and patches worked OK though. I tried quite a few of the pre-installed apps and installed others using Gslapt so I'll just note what didn't work for me.

Clicking Help in the menu opened the browser but it couldn't find the target page.

After installing audacity it wouldn't run, "error while loading shared library libwx_gtx2u_richtext-2.8.50.O"

I installed Firestarter and tried to start the interface from a root terminal (a normal user can't access it) but got the error "While connecting to session manager: Authentication Rejected..." and "GLib-GIO: ERROR: gdbusconnection.c:2279 ..."

Streamtuner installed OK but it's set to use xmms as the default music player, so it gives an error message when attempting to play a stream. It's easy to change it to audacity in the settings, but it's better not to have to.

htop has a missing dependency, ncurses>=5.7 and lyx has one too, util-linux-ng>=2.18

Cheers
Andy
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: hata_ph on March 20, 2011, 08:22:41 am
Streamtuner installed OK but it's set to use xmms as the default music player, so it gives an error message when attempting to play a stream. It's easy to change it to audacity in the settings, but it's better not to have to.

htop has a missing dependency, ncurses>=5.7 and lyx has one too, util-linux-ng>=2.18

Cheers
Andy

It seem there is no way to change the default music player for streamtuner at compile time...if you know there way I am gladly to re-build streamtuner again.
As for lyx, I build it using VL7B2 version and I believe util-linux-ng come default with it...

BTW, pls post the package problem in the respective VL package board for easy keep-tracking...thanks
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: uelsk8s on March 20, 2011, 09:40:13 am
hata_ph,
this patch will change the default music player for streamtuner from xmms to audacious, and also changes the default web browser to firefox
http://launchpadlibrarian.net/17471900/streamtuner_0.99.99-13ubuntu2.debdiff
if you need any help applying it let me know
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: hata_ph on March 20, 2011, 05:34:19 pm
hata_ph,
this patch will change the default music player for streamtuner from xmms to audacious, and also changes the default web browser to firefox
http://launchpadlibrarian.net/17471900/streamtuner_0.99.99-13ubuntu2.debdiff
if you need any help applying it let me know

Ya...saw it last night but i think need some modification since it is for debian/ubuntu based distro...will check it when i got the chance...thanks  8)
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: Andy Price on March 20, 2011, 05:57:26 pm
Thanks for the replies hata_ph

Quote
BTW, pls post the package problem in the respective VL package board for easy keep-tracking...thanks

Not sure where to do that these days as the usual package news and updates section is not being updated. If there's somewhere special for VL7 packages I'll be happy to post there.

Cheers
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: stretchedthin on March 20, 2011, 07:01:07 pm
Thanks for the replies hata_ph

Quote
BTW, pls post the package problem in the respective VL package board for easy keep-tracking...thanks

Not sure where to do that these days as the usual package news and updates section is not being updated. If there's somewhere special for VL7 packages I'll be happy to post there.

Cheers

Sorry, I won't be able to post everything that was done (there was just too many to catch up and I didn't have access to post to that thread at the time) but here are the links to ad your comments to lyx and streamtuner.

http://forum.vectorlinux.com/index.php?topic=13401.0 (http://forum.vectorlinux.com/index.php?topic=13401.0)
http://forum.vectorlinux.com/index.php?topic=13400.0 (http://forum.vectorlinux.com/index.php?topic=13400.0)
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: hata_ph on March 20, 2011, 10:09:18 pm
Thanks for the replies hata_ph

Quote
BTW, pls post the package problem in the respective VL package board for easy keep-tracking...thanks

Not sure where to do that these days as the usual package news and updates section is not being updated. If there's somewhere special for VL7 packages I'll be happy to post there.

Cheers

Sorry, I won't be able to post everything that was done (there was just too many to catch up and I didn't have access to post to that thread at the time) but here are the links to ad your comments to lyx and streamtuner.

http://forum.vectorlinux.com/index.php?topic=13401.0 (http://forum.vectorlinux.com/index.php?topic=13401.0)
http://forum.vectorlinux.com/index.php?topic=13400.0 (http://forum.vectorlinux.com/index.php?topic=13400.0)

Can't normal forum member post comment on the VL package board?
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: stretchedthin on March 21, 2011, 05:12:25 am
Quote
Can't normal forum member post comment on the VL package board?
I don't think they can. The VL package board I believe is set to be visible only to those at Packager level or up.  I see where you are going with this and tend to agree it would be far more efficient not to have to re-post each package to make it visible to the community.  I think the rational behind it is that any package posted on the packagers board is not yet available in the repository.  It is not until it is actually available that it get's posted a second time for full visibility.
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: stretchedthin on March 21, 2011, 01:34:08 pm
Quote
htop has a missing dependency, ncurses>=5.7 and lyx has one too, util-linux-ng>=2.18

A number of these dependency issues have been taken care of by a script that uelsk8s wrote.  However, you will have to clear and reupdate your repository in gslapt before you will avoid the error.

To do so, in gslapt go to edit-preferences and click the button to delete "cached package files" then click update in gslapt.  This should take care of the problem if not please report directly to me by pm as many packages at this point do not have a thread.
Thanks;
stretch'
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: GrannyGeek on March 21, 2011, 03:42:07 pm
Just a clarification--
The board to which "normal members" can't post is VL PackagERS, not VL package. VL package news and Updates is open to everyone and is where one normally posts bug reports on newly released packages.
--GrannyGeek
Title: Re: VectorLinux 7.0 Beta1 bug thread
Post by: hata_ph on March 21, 2011, 05:50:59 pm
Ok. But there is over 300+ new packages in VL7 Testing Repository and it require some time to post it all in the VL Package News Board. Maybe someone can help out posting the news to the board. I am willing to help if some one can temporary grant me the right to post in the VL Package News Board.  8)