I've found what seems to be a reproducible problem with 'ash' on slackware64-current (updates to and including Jan 31st)
Open a console
ash <enter>
type 2 or more characters, doesn't matter what.
press backspace
press backspace
**seg fault**
occurs under xterm, konsole, gnome-terminal in both kde4 and xfce and on a virtual console.
New install slackware64 13.0. Sites that cause it to segfault are simple ones - gmail (2 seconds after I get past the sign in stage, and before I even open any email. This one also
www.channel4.com/programmes/4od.
I have done the obvious stuff - checking for missing libs with ldd, finding them, etc. Disks are 1-2 years old (ext3) and well checked, but this install has not been lived in yet. Plugins installed are: java 1.6.0_16; Flash 10.0 r45; SVG-2.26. Kernel is 2.6.33.2, made with 'make oldconfig from a very satisfactory 2.6.30.5 kernel which was faultless for some time.
The box is all-amd/ati HP6715S, with RS690 video and northbridge, sb600 southbridge. and a twin turion 2 Ghz. It is using the recent OSS xf86-video-ati drivers. The only strange Mozilla error was between 4th and 5th crash this session when it said "Input/Output Error". Otherwise the error shows as line 131 of run-mozilla.sh - the 'finally start the binary' routine.
Running slackware-current 32bit. I use digikam-1.7.0, kipi-plugins-1.7.0, and ufraw-0.17 which are all built using the sbo scripts from 13.1 repo. All the above work fine with lensfun-0.2.3 built from sbo, but trying to update lensfun to 0.2.5 causes segfaults in digiKam and ufraw.
Anyone else seen this and is there a fix? Seems to be caused by a change in lensfun between versions, but I think it's beyond me to sort on my own. Lensfun-0.2.5 seems to build fine without errors, but I believe there were warnings with respect to makedep. Digikam and ufraw locate the lensfun libraries during the build. Ufraw segfaults on startup and digikam segfaults when the auto lens correction tool is selected from the menu. I know none of these versions are officially supported either alone or in -current,
The version of mencoder I currently have installed segfaults (immediately) when you ask it to convert x264-encoded MKVs to another format. One sample command-line would be:
Code:
mencoder -nosound -ovc libdv Puella_Magi_Madoka_Magica_720p_GG_-_06.mkv -o a.avi
This produces the following output:
Code:
MEncoder 20110702-4.5.2 (C) 2000-2011 MPlayer Team
success: format: 0 data: 0x0 - 0x1c43987e
libavformat file format detected.
[Code]...
Incidentally, I'm wondering if the version of FFMpeg that the MPlayer configure script downloads might be at fault. The slightly outdated FFMpeg I installed from SBo (6.1) does not crash when converting the same file. And no, I can't use either Alien Bob's Mplayer build or the MPlayer binaries included with Slackware. Neither is built against either libdv or x264. I need libdv as an output codec.
Upgraded from 13.0 to 13.1 following the instructions. Downloaded latest nvidia package (NVIDIA-Linux-x86-96.43.16-pkg1.run) for my geForce4 MX 4000. Compiled and installed new module (old one was 96.43.13).
Xorg fails to start with this:
Code:
X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Slackware 13.1 Slackware Linux Project
Current Operating System: Linux mercury 2.6.33.4-smp #1 SMP Wed May 12 21:39:37 CDT 2010 i686
Kernel command line: BOOT_IMAGE=Linux ro root=805 vt.default_utf8=0 3
Build Date: 05 May 2010 01:54:53AM
Current version of pixman: 0.16.6
Before reporting problems, check [URL]
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.....
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x3b) [0x80a1e6b]
1: /usr/bin/X (0x8048000+0x57b75) [0x809fb75]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe40c]
Segmentation fault at address 0xc
Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting
The "nv" driver works.
has anyone the same problem with bash in -current? Everytime I use the commandline completition with TAB , it adds me a space, so I always need to push the backspace to continue to complete the path.So the whole thng get's a bit unuseable.I'm using bash-4.1.010-486-1 and bash-completition-1.3-noarch
View 4 Replies View RelatedI have problem with some applications in X. When I want to unlock Xscreensaver it just meses my X and I must Ctrl+Alt+Backspace. I installed slock and thought I solved the problem that way, but same happened with Xpdf.
lspci:
Code:
01:05.0 VGA compatible controller: ATI Technologies Inc RS690 [Radeon X1200 Series]
uname -r:
Code:
2.6.35.11-smp
[Code]...
Lost my wireless keyboard and mouse upgrading slackware current.Boot seems to be normal.I just can't login, cause have no keyboard.
View 2 Replies View Relatedslackware-current kernel 2.6.35.10-smp for instance if i just want to connect to wep ap. i done
[code]...
it says waiting for carrier and it just time out, im wondering why i read somwhere that its not working good with slackware 13.1
I recently upgraded to slackware-current from Slackware 13 via slackroll, and have only encountered one problem. My file manager no longer thumbnails images, and icons (mostly PNG) aren't appearing no matter what GTK theme is set. Running from the command line produces no errors, and when brought up in something else (say feh /path/to/icon.png) it works perfectly. This is the only hitch I have encountered so far. The same thing happens with emoticons in Pidgin. Does anyone know of a fix?
View 5 Replies View RelatedFirst time I've done this in awhile Upgrading my Slackware64 -current VM, following the standard routine that has always worked in the past -
Code:
slackpkg clean-system
slackpkg install-new
The clean-system removed 2 packages -
util-linux-ng
eggdbus
Installpkg will no longer work, complaining that the rev command is not found. The problem hit with the removal of util-linux-ng. I cp'd util-linux to ~/. Extracted with tar and executed the doinstall. Fixed.
after update to slackware current 4 days ago i cant get sound working in wine in starcraf 2 i mean i got sound in instalation but not in game and i get error when i wanna configure sound in winecfg
err:alsa:ALSA_CheckSetVolume Could not find '{PCM,Line} Playback Volume' element
err:alsa:ALSA_CheckSetVolume Could not find '{PCM,Line} Playback Volume' element
err:alsa:wine_snd_pcm_recover underrun occurred
err:alsa:wine_snd_pcm_recover underrun occurred
in game i dont got that error but sound dont work btw my sound card is asus xonar essence stx
I updated my kernel in slackware current but can't install lilo, when i was with my old kernel it gave an error about not finding the sda drives (they were named hda before the upgrade).I booted into the slackware 13.0 dvd and modified fstab and lilo.conf replacing hda with sda but lilo still gives an error of not finding sda drives.How can i install lilo so i can boot into my sistem??
View 14 Replies View RelatedI've upgraded Slackware-13.1 I had installed to Slackware-Current using a local tree I had download with mirror-slackware-current.sh script, but when I rebooted I could not get the graphics to load. I think it's because I've also modified /etc/groups and add an username after audio: and video: group, but I forgot that and had to remove slackware from the machine.
View 4 Replies View RelatedI've tried a few different ways to install the ATI graphics driver "fglrx" to get 3D acceleration.If I try to install using the standard file "ati-driver-installer-10-4-x86.x86_64.run" from the ATI web site it appears to work but then I discover it actually got an error.I saw a reference to ATI requiring 32-bit libraries to install their 64-bit driver. Is there a link or post that explains how to add the 32-bit libraries. Will that solve the problem, or will I just waste more time trying that?
View 6 Replies View RelatedI use Alien Bob's mirror-slackware-current.sh with an excludes.txt to only download the parts of current that I want. Unfortunately it is not working for part of the exclude.txt file and I am at a loss to know why.
The excludes.txt is
Quote:
slackware64/e
slackware64/f
slackware64/kdei/kde-l10n-ar-4.5.5-noarch-3.txt
slackware64/kdei/kde-l10n-ar-4.5.5-noarch-3.txz
[code]...
This ignores e/ f/ y/ testing/ pasture/ source/ and usb-and-pxe-installers/ It also ignores most of kdei/ and /extra It is meant to ignore most of extra/source and just download the source for flash-player-plugin, but it is ignoring all of extra/source/, however the same syntax is working for kdei/ and extra/.
I have been using slackware since version 10.1 and really like it. I have never had a problem until lately, version 13.1 has been stable as a rock for me. The first 2 or 3 updates to current ran well but then the problem started. After installation Slackware would get to the splash screen and bring up the first picture of a disk drive then just hang and never go any further. I do have a good burn on the dvd, have checked the md5 and burned at 4x. then slack 13.37 does the same thing. this is on 4 different computers with several different video boards.
View 8 Replies View RelatedThis is not an earth-shattering issue, but, something I've recently noticed with the Chatzilla add-on for Seamonkey in Slackware-current. Maybe it is just my problem.If I add Chatzilla to FF 4.0 everything works as expected, that is, when I launch Chatzilla the default start-up window shows up with a list of IRC servers to click on (freenode being my favourite).
However,when I click on Chatzilla in Seamonkey I get a blank window that shows up, there is no server list. I noticed that the window in Chatzilla went blank for Seamonkey recently after a -current update (maybe a library issue?)
I'm very keen on getting Mumble installed on my slackware -current 64 bit install. I found a slackbuild script for 12.2 here, but changing the version number resulted in failure. I also tried following the build instructions on the Mumble website, which failed with the following.
Code:
neil@slackbox:~/Downloads/mumble/mumble-1.2.2$ qmake -recursive main.pro
Reading /home/neil/Downloads/mumble/mumble-1.2.2/src/mumble11x/mumble11x.pro
WARNING: /home/neil/Downloads/mumble/mumble-1.2.2/src/mumble11x/mumble11x.pro:33: Variable LIBPATH is deprecated; use QMAKE_LIBDIR instead.
WARNING: /home/neil/Downloads/mumble/mumble-1.2.2/src/mumble11x/mumble11x.pro:33: Variable LIBPATH is deprecated; use QMAKE_LIBDIR instead.
[Code]...
I wish to do a fresh install of Slackware without KDE. I could use my Slackware 13.1 DVD but I thought, why not give -current at try? Is there a -current ISO or must I install 13.1, without KDE, and then upgrade to -current? Or, is it possible to remove 'all things KDE' and then upgrade to -current?
View 8 Replies View Relatedi just updated my slackware to current, and every time i try to log in in my kde session my desktop is upside down.i mean literally everything is upside down, the only way i can have a usable desktop is with the "fail-safe session" of kde option on kdm which is what i'm using right now.does anybody know how can i solve this?i would post a snapshot of the upside down desktop but i can't do anything when i'm using it. fonts, windows, panels, icons everything is upside down..i solved this, just reinstalled the nvidia drivers and everything is goood again
View 1 Replies View RelatedI'm running slackware-current in a virtual machine on virtualbox 4, 512 mb ram, 1gb swap.Everything works fine, except the x11 mouse. Xfce will start up fine, and show the 'tips and tricks' dialog, and then freeze. I can't change to a TTY, or click. The mouse moves, but doesn't click.
View 13 Replies View RelatedI'm trying to take my current windows7 (x64) setup and make it into a dual-boot setup with slackware 13.0 (x32) and am hitting a brickwall. I guess I would like to know if I can salvage the situation without formating my windows drive. I fully intend to, but I had hoped to not do it this month. I'd like to get dual boot going so I can master it and acquire all the files/drivers I'll want and then format and do it 100% right next time.
Currently I have windows setup on a 3x 500gb Raid0 onboard array which itself has been flawless. After I shrunk my current partition size to give me about 25gb of free space I proceeded to setup Linux, and I was unable to perform the cfdisk portion for partitioning the array for Linux.
I tried using cfdisk:
/dev/hdx (a1-a3,b1-b3)
/dev/sdx (a1-a3,b1-b3)
I even attempted to locate with: cat proc/partition and tried using cfdisk on every device it located. It always said it was either an unknown partition table and should I start at zero, or bad partition. I was of course too concerned over my windows setup (which has almost 1tb of stuff I have not backed up) to go any further into the unknown.
PS: I have used Slackware before, back at 8.1, 10, and even a very brief interlude at 12.0, this is my first attempt on this computer however with 13.0, it is currently running fine on my laptop and my PS3 (Laptop is even dual booting 7/Slack13. Albeit without raid)
Phenom 9850
M2N-SLI Deluxe (Nvidia AM2)
4x1gb of 1066 kingston hyperX
3x500gb WD Caviar Black Sata2 3.0
Saw this Post on LWN this morning:
[URL]
I wonder if it would make sense for Pat and the team to bump the Kernel from 2.6.37.5 to 2.6.38.2 (or 2.6.38.?) before 13.37 is released ?
I'm looking for a good IDE for C/C++, that runs well in slackware. I used CodeBlocks, but I can't compile in the current, and its getting a little old. I see a lot of threads talking about anjunta and kdedeveloper, but I don't like these.
View 14 Replies View Related-> Announced in the Changelog.
View 14 Replies View RelatedPerl 5.12.2 In -current
View 3 Replies View RelatedI saw that /isolinux / kernel was updated in current. So I thought time to give it a try.
My installition and computer stops after
Parsing Elf OK
Booting Kernel
This seems to happen because the kernel or initrd.img is being overwritten. I solved this in 13.1 with PV's help by inserting the /isolinux and /kernel directory from 13.0 into the 13.1 files before running growisofs.I have again tried all the other suggestions from my previous post with 64-13.1. no success only using isolinux from 13.0 works I am running the current kernel on my main system 2.6.35.7 since the day it was put on kernels.org this was my previous thread on this problem
[URL]
would love to hear some suggestions on this as I just assumed it would be solved for 13.2 or whatever is next where to find the source for the initrd.img used in /isolinux.Possible the rest of the boot source would help. I have been trying to decode what happens on the DVD boot. Looked at arch/x86/boot/compressed/
Well this pretty much sums up the experience with Slackware current these days. This is not to say it was all plain sailing. So what problems were there?
1) Nvidia drivers did not work, this was fixed by re-compiling the kernel modules and installing a patched or beta driver, but it introduced another fault. However this problem cannot be accredited to Slackware, all operating systems have driver problems after being updated. Nvidia however had a new version out in a couple of days, which completely fixed the problem.
2) The problem introduced by the hacked fix of the older Nvidia driver wouldn't allow me to switch to the generic kernel (it would not create a valid initrd.gz). I think this was because of re-compiling the kernel modules, so I re-installed them and the problem was fixed. Again not a Slackware fault but a samac fault.
3) Program A couldn't find library B. Slackware has moved some libraries from e2fsprogs to util-linux-ng. This may cause some stuff to break if you are using the multi-lib extensions. This was fixed by creating a compat32 package for util-linux-ng. Again not actually Slackwares fault, but a little closer to home. Alien Bob could you update the massconvert.sh please.
That's it so far, after an update that ran to over 500 lines in the change log, an updated kernel, updated glibc, updates X server etc. etc. and three paltry problems none of which could be attributed to Slackware directly.
I think I might have not given enough space to my '/' dir. What can I use to resize '/' and '/home' by taking space away from '/home' without damaging the data or OS installed?
View 14 Replies View Related
