Slackware 14.0 RC1 Arrived: Send Your Bug Reports

baldzhang · 08-15-2012, 10:47 PM

update scim please

i test scim with 14.0 rc1, found following problems
1: xfce-terminal can not input
2: program written with Lazarus/fpc, when i input some chinese word, one keyboard hit become two char input
3: use tigervnc 1.1.0 from Eric for remote management, scim does not work at all. run xfce 4.10 in vnc also

then i rebuild scim 1.4.14 from source, the problem resolved, so please update the scim packages. thanks.

Didier Spaier · 08-16-2012, 03:16 AM

Done in Slackware 14 RC2

D1ver · 08-16-2012, 03:18 AM

I'm not sure if it's me doing something wrong or not, but the slackbuild script for Java JDK in /extra seems to be a little funny.
I built and installed a package using the slackbuild script and the jdk-7u5-linux-x64.tar.gz file from Oracle. However it seems to have installed everything (libs, bin, include) into /usr/lib64/java.

Code:

bash-4.2$ ls /usr/lib64/java/
COPYRIGHT  README.html			bin  include  lib  release
LICENSE    THIRDPARTYLICENSEREADME.txt	db   jre      man  src.zip

Is this the expected behavior? Things in /usr/lib64/java/bin don't show up in my path as desired..

Alien Bob · 08-16-2012, 03:25 AM

Quote:

Originally Posted by D1ver

I'm not sure if it's me doing something wrong or not, but the slackbuild script for Java JDK in /extra seems to be a little funny.
I built and installed a package using the slackbuild script and the jdk-7u5-linux-x64.tar.gz file from Oracle. However it seems to have installed everything (libs, bin, include) into /usr/lib64/java.

Code:

bash-4.2$ ls /usr/lib64/java/
COPYRIGHT  README.html			bin  include  lib  release
LICENSE    THIRDPARTYLICENSEREADME.txt	db   jre      man  src.zip

Is this the expected behavior? Things in /usr/lib64/java/bin don't show up in my path as desired..

You need to logout and login again to effectuate the changed environment (a file /etc/profile.d/jdk.sh was added by the package which adds the java bin directory to $PATH amongst others).

Eric

D1ver · 08-16-2012, 03:28 AM

Quote:

Originally Posted by Alien Bob

You need to logout and login again to effectuate the changed environment (a file /etc/profile.d/jdk.sh was added by the package which adds the java bin directory to $PATH amongst others).

Eric

Like usual it's me doing something wrong

Thank you sir!

D1ver · 08-16-2012, 03:53 AM

Quote:

Originally Posted by D1ver

Like usual it's me doing something wrong

Thank you sir!

Edit:
Never mind.. I didn't download the profile.d/ directory and it's contents into the same directory as the slackbuild and source so I was missing a few files.

Working now that I'm doing things properly..

zakame · 08-16-2012, 05:24 AM

Quote:

Originally Posted by chess

I_prefer_underscores.

Can%20I%20%play%20too?

ruario · 08-16-2012, 05:33 AM

@zakame: No, its too ugly and doesn't work everywhere. The cool kids, _ - and . laugh in its general direction.

SCerovec · 08-16-2012, 05:55 AM

Quote:

Originally Posted by zakame

Can%20I%20%play%20too?

only if you:

Code:

sed "\ "/"-"/g

I tend to agree with Alien Bob - space really just make a show stop, sooner or later.

I even tend to use three character names for my "sceleton" lately:

doc,dld,src,bin

so when I have to type from "unusual spaces" as midp2 (phone java) terminals are, i just suffer for three codes, leave alone those "\ " spaces

=2c
P.S.
lazy typers are "the great way of UNIX" IMHO

GazL · 08-16-2012, 05:59 AM

I make an exception for my music collection for aesthetic reasons, but otherwise I'm down with the no-to-spaces crowd.

Do we need to start an "Occupy 0x20" movement?

shadowsnipes · 08-16-2012, 08:18 PM

Quote:

Originally Posted by T3slider

It could be fixed by quoting but I tend to agree with Alien Bob:
Quote:
Originally Posted by Alien Bob View Post
Using spaces in directory names is not supported by Slackware's scripts. I also do not support it in any of my own scripts. I even have a script (massconvert32.sh) which aborts when it detects a space in the directory name.

Spaces in directory names is an abomination introduced by MS Windows and lazy-ass GUI programs. Real UNIX men avoid space.

I didn't realize that spaces in directory names was not supported in Slackware scripts...didn't see this in the Readme. Generally I don't use them myself; I usually use '_' instead and haven't run into any issues. For testing purposes, however, I love spaces (and long paths) because they can throw off some programs that haven't accounted for it.

Onto RC2...

kingbeowulf · 08-17-2012, 02:17 AM

Quote:

Originally Posted by Alien Bob

...nobody uses 32-bit Slackware anymore?)...

I have used x86_64 as my main box since the initial release of SLAMD64, and then Slackware64. 32-bit lives in a Virtualbox and qemu VM for compiling and testing. I haven't noticed any liloconfig errors within these VMs.

I just dusted off an old P3 Compaq Armada E500 and ugraded from Slackware 13.1 to 14 RC2. No issues here either.

ruario · 08-17-2012, 02:56 AM

Quote:

Originally Posted by Alien Bob

nobody uses 32-bit Slackware anymore?

Or they just don't use lilo. I now prefer Syslinux myself.

cmk77 · 08-17-2012, 12:15 PM

Any chance of upgrading to xfig 3.2.5?

volkerdi · 08-17-2012, 05:41 PM

Quote:

Originally Posted by cmk77

Any chance of upgrading to xfig 3.2.5?

Nope. We tried it before, and it was severely bug ridden compared to what we had, so we reverted. Not to say we won't look into it again, but not now.