VL 7.1

[retired1af]

Exaile still crashing with "no suitable plugins" error.

Error follows:

Code:

INFO    : Playing file:///home/retired1/music/Daft%20Punk%20mp3/unknown%20-%20unknown/01%20-%20Daft%20Punk%20-%20Overture.mp3
shm_open() failed: Permission denied
ERROR   : <gst.Message GstMessageError, gerror=(GError)NULL, debug=(string)"gstdecodebin2.c\(3576\):\ gst_decode_bin_expose\ \(\):\ /GstPlayBin2:player/GstURIDecodeBin:uridecodebin0/GstDecodeBin2:decodebin20:\012no\ suitable\ plugins\ found"; from decodebin20 at 0x7fe628001cc0> ['__class__', '__cmp__', '__delattr__', '__dict__', '__doc__', '__format__', '__getattribute__', '__grefcount__', '__gstminiobject_init__', '__gtype__', '__hash__', '__init__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', 'copy', 'flags', 'parse_async_start', 'parse_buffering', 'parse_buffering_stats', 'parse_clock_lost', 'parse_clock_provide', 'parse_duration', 'parse_error', 'parse_info', 'parse_new_clock', 'parse_qos', 'parse_qos_stats', 'parse_qos_values', 'parse_request_state', 'parse_segment_done', 'parse_segment_start', 'parse_state_changed', 'parse_step_done', 'parse_step_start', 'parse_stream_status', 'parse_structure_change', 'parse_tag', 'parse_tag_full', 'parse_warning', 'set_buffering_stats', 'set_qos_stats', 'set_qos_values', 'set_seqnum', 'src', 'structure', 'timestamp', 'type']

Crash occurs with .mp3 and .m4a files. Haven't tried anything else.

[retired1af]

Still getting a mixer crash when attempting to change the volume with the mouse wheel. Error follows:

Code:

Feb 15 13:39:08 bodacious kernel: [ 5581.347356] xfce4-mixer-plu[3578]: segfault at 24 ip 0000000000406eb9 sp 00007fff66c21550 error 4 in xfce4-mixer-plugin[400000+b000]
Feb 15 13:39:09 bodacious kernel: [ 5582.522716] xfce4-mixer-plu[3675]: segfault at 24 ip 0000000000406eb9 sp 00007fff125d8f60 error 4 in xfce4-mixer-plugin[400000+b000]

Edit -- Apparently this is a known bug which was supposedly fixed. Workaround is to select a different sound card in Mixer and then change it back to the proper setting. No more crashes.

https://bugzilla.xfce.org/show_bug.cgi?id=7630#c4

[retired1af]

OK. Trying this again.

Installed 7.1 STD B0.13. MS Wireless mouse wouldn't install. Even VASM wouldn't install it.

As for the Network Manager issue, upgraded the 5 files Vector wanted to test. Upon reboot, the system locked up at the login screen.

Seeing if I can upload the log files here after a rename. Google Groups is being stupid about it.

[retired1af]

OK. DId some more testing with VL 7.1 STD B0.13. The first install was done by using the VLocity B0.13 installer and pointing to the ISO on the hard drive. Thinking the installer might be different, I went ahead and burned a disc with the STD iso. Wouldn't ya know? Mouse didn't work in the installer.

[nightflier]

Not having much luck with this one. So far, all attempts have resulted in having no keyboard or mouse response after the installation. This is in VB. I did try 0.9 on real hardware, using USB and PS/2 input devices, same thing.

[vector]

ok for you testers there is a new 64/32 bit 7.1 to try hopefully this cleans up previous mouse and keyboard issues............fingers crossed........
http://vlcore.vectorlinux.com/pkg/untested/veclinux-7.1/iso/VL-7.1-STD-B0.14.iso
http://vlcore.vectorlinux.com/pkg/untested/veclinux-7.1/iso/VL64-7.1-STD-B0.14.iso

Keep in mind we are trying to solve issues a few at a time per release this is mostly focused on installer hw issues. Some of the installed software
issues may still be unresolved.......i.e. networkmanager..........and the none password box and some exaile problems..........(but they are on the radar)
So please help us out and give these releases a try the more feedback we get the faster we can push this out. Everyone should try this it will not fry anything and a 98% chance all will go well but we need testing as only limited amount of hardware available with our developers.

Thanks for your support and testing !!!!

Cheers,
Vec

[nightflier]

Major progress in my case. I now have a working 64-bit system!  

Testing in Virtualbox:
Run 1: Advanced, un-select xfce and optional progs; install stopped at "Creating users". After waiting and checking that there was no activity, reset machine and got to a maintenance login.

Run 2: Fulliautomatix; stopped at same point, but reset brought me to gdm. I had to manually set root password and create a user. Otherwise, so far, so good.

Niggle: informational message during install shows "formating". Proper spelling is "formatting".

[nightflier]

Test of 32-bit version very similar to 64-bit.

Only tried fulliautomatix. Still hung at creating users. After reboot set pwd and created users.

Testing IceWM + mods on it now. Looks good, the desktop launchers now work out of the box!

[retired1af]

Installed both B0.14 versions (32 and 64-bit).

VLocity installed OK, but froze upon reboot. Restarted again and made it to the desktop. Got Network Manager running and system froze again after starting Firefox. Restarted again, and once into the desktop, froze again. Not sure what's different between .13 and .14, but my notebook doesn't like .14.

32-bit version went better. No hiccups during install (and the mouse worked, too!). First reboot had no errors. Got Network  Manager running and am able to access the Internet with Firefox.

Going to reinstall VLocity to see if perhaps there was a hiccup during the install.

[retired1af]

Reinstalled VLocity B0.14 and it locks up after login. Looking through the logs reveals something weird going on.

messages

Code:

Feb 23 14:15:51 vector NetworkManager[4315]: <info> (wlan0): IP6 addrconf timed out or failed.
Feb 23 14:15:51 vector NetworkManager[4315]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Feb 23 14:15:51 vector NetworkManager[4315]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Feb 23 14:15:51 vector NetworkManager[4315]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.

syslog

Code:

Feb 23 14:14:23 vector NetworkManager[4315]: <warn> Failed to open plugin directory /usr/lib64/NetworkManager: Error opening directory '/usr/lib64/NetworkManager': No such file or directory
Feb 23 14:14:23 vector NetworkManager[4315]: <warn> (wlan0): driver supports Access Point (AP) mode
Feb 23 14:14:23 vector kernel: [   58.366827] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
Feb 23 14:14:23 vector NetworkManager[4315]: <warn> failed to allocate link cache: (-10) Operation not supported
Feb 23 14:14:23 vector NetworkManager[4315]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Feb 23 14:14:23 vector NetworkManager[4315]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Feb 23 14:14:23 vector NetworkManager[4315]: <warn> bluez error getting default adapter: Launch helper exited with unknown return code 1
Feb 23 14:14:23 vector NetworkManager[4315]: <warn> Trying to remove a non-existant call id.
Feb 23 14:14:24 vector gdm-binary[4374]: no suitable security token driver could be found
Feb 23 14:14:25 vector kernel: [   61.079290] ACPI Warning: _BQC returned an invalid level (20110623/video-486)
Feb 23 14:14:28 vector dhcpcd[4097]: timed out
Feb 23 14:14:28 vector dhcpcd[4097]: allowing 8 seconds for IPv4LL timeout
Feb 23 14:14:36 vector dhcpcd[4097]: timed out
Feb 23 14:14:38 vector pulseaudio[4571]: [pulseaudio] shm.c: Failed to read /dev/shm/: No such file or directory
Feb 23 14:14:38 vector pulseaudio[4571]: [pulseaudio] shm.c: shm_open() failed: Permission denied
Feb 23 14:14:38 vector pulseaudio[4571]: [pulseaudio] core.c: failed to allocate shared memory pool. Falling back to a normal memory pool.
Feb 23 14:14:38 vector pulseaudio[4571]: [pulseaudio] shm.c: Failed to read /dev/shm/: No such file or directory
Feb 23 14:14:39 vector pulseaudio[4571]: [pulseaudio] module.c: Failed to open module "module-alsa-card": file not found
Feb 23 14:14:48 vector NetworkManager[4315]: <warn> No agents were available for this request.
Feb 23 14:14:48 vector NetworkManager[4315]: <warn> Activation (wlan0) failed for connection 'Looney Bin'
Feb 23 14:15:31 vector dhcpcd[4681]: all: not configured to accept IPv6 RAs

debug

Code:

Feb 23 14:14:18 vector kernel: [   53.445694] atl1c 0000:03:00.0: irq 45 for MSI/MSI-X
Feb 23 14:14:18 vector dhcpcd[4097]: eth0: using hwaddr 54:04:a6:47:00:86
Feb 23 14:14:18 vector dhcpcd[4097]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
Feb 23 14:14:18 vector dhcpcd[4097]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
Feb 23 14:14:18 vector dhcpcd[4097]: eth0: using hwaddr 54:04:a6:47:00:86
Feb 23 14:14:18 vector dhcpcd[4097]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
Feb 23 14:14:18 vector dhcpcd[4097]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
Feb 23 14:14:25 vector kernel: [   60.502789] i915 0000:00:02.0: setting latency timer to 64
Feb 23 14:14:25 vector kernel: [   60.503008] checking generic (c0000000 3ff0000) vs hw (c0000000 10000000)
Feb 23 14:14:25 vector kernel: [   60.567322] i915 0000:00:02.0: irq 46 for MSI/MSI-X
Feb 23 14:15:30 vector kernel: [  125.907929] wlan0: authenticate with d8:6c:e9:15:51:f3 (try 1)
Feb 23 14:15:30 vector kernel: [  125.909490] wlan0: authenticated
Feb 23 14:15:30 vector kernel: [  125.918138] wlan0: associate with d8:6c:e9:15:51:f3 (try 1)
Feb 23 14:15:30 vector kernel: [  125.921786] wlan0: RX AssocResp from d8:6c:e9:15:51:f3 (capab=0xc11 status=0 aid=1)
Feb 23 14:15:30 vector kernel: [  125.921796] wlan0: associated

I'm going to go in and see if I can disable IPv6 and see if that's causing the lockup.

[retired1af]

Don't think that's it. Some strange behavior after logging in. It's intermittent lockups as if there's something going on with the video. Mouse over on the menu icons and when you move the mouse pointer, the icon is a gray box. During the lockup, mouse moves, but can't select anything. Then it "unlocks" and things are back to normal, although it's brief.

Again, this is with VLocity B0.14.

[overthere]

Vl7.1-std-bo.14.iso
boot
press enter
nice splash
gray screen with pointer
click grayscreen gives menu-options=terminal, quit(restart, logout, reboot,shutdown
choose logout
splash screen
text installer start screen
choose exit
welcome to shell-includes tools
reboot

boot
gui no acpi
vl splash/code
gray with pointer
reboot/shutdown

with gui noacpi I get scrolling code...the last line is  something like /dev/sro already mounted or /mnt/loop busy just prior to gray screen.

no indication of key to view available options
 
intel 1.7ghz p4/768meg had vl7 installed via gui installer but now is messed up so no hard info

edit: redownloaded with opera on vl7light and burned with k3b..same

[retired1af]

Hate to be a killjoy regarding kernel 3.4.

http://www.zdnet.com/linux-kernel-exploit-gets-patched-7000011844/?s_cid=e539

[vincent2]

you can updated kernel to the  latest 3.7.9

http://vlcore.vectorlinux.com/pkg/untested/veclinux-7.1/x86_64/

[retired1af]

you can updated kernel to the  latest 3.7.9

http://vlcore.vectorlinux.com/pkg/untested/veclinux-7.1/x86_64/

If you had bothered to read the linked article, you'd know the exploit will be patched in 3.9.