Slackware 14.0 RC4
 

Just released.

Mhh there's no mention of emacs 24.2 in the changelog, but the package looks updated under the /e section of the tree (slackware64 only).

You are right. Curious ..

Oops, looks like I dropped that in the ChangeLogs and on the 32-bit side. Quick update coming soon. Thanks!

Looks like Slackware 14.0 will be the most bleeding edge slackware release :)

Proud slackware user since 8.1 :D

Updated and everything looks good so far. :)

Not a big deal but I have noticed these:

$ man shutdown
Error parsing *roff command from file /usr/man/man8/shutdown.8.gz
$ man last
Error parsing *roff command from file /usr/man/man1/last.1.gz
$ man mplayer
<standard input>:6300: warning [p 1, 798.3i, div `an-div', 0.0i]: cannot adjust line

Cheers

It's a honor! :)

WOOT!

I must have blinked or forgot to refresh the changelog...

I can hardly wait for stable so I can do some real tests and bitch slap those morons at Phoronix....

As long as it takes... :)

Love Slack and the community.

Long life for Slackware !!
Long life to Mr. Volkerding !!

Confirmed, but FYI this isn't new to RC4.

It seems to be working fine here on my two Slackware boxes.

RC4 is running like a champ here as well. :)

That nroff error is ancient--I remember seeing that sometimes back in the waaaaay early daze... I don't even remember how to fix it anymore!

Also, I'm curious: is RC4 a new record for RC's, or have we been to RC5+ before? In any case, it looks like this release has been a rather bumpy ride: good thing we have Pat and the gang to work the kinks out!

No problems encountered so far on my 2 boxen.

Nice ... Miracles take a day, the Impossible takes a week.

No, four isn't a record for Slackware release candidates. Slackware 11.0 reached five, and Slackware 13.37 reached the first Feigenbaum constant. :)
Now the next question - what's the highest beta release of Slackware that's been issued? The highest I've found is two...

Moronix....

Hello,

In slackware-32, the package dbus is in the series A and L. I guess the one in the serie L is an intruder:

--
SeB

But in the ChangeLog.txt file all good:

Hmmm... still bleeding here.

I ran out of disk space on my eeepc 2G surf while upgrading to RC3 and wasn't able to get the kernel source, qt or samba.

I found some .cache directories and such to dump but when I tried it again, I found that wicd no longer works.

After hooking up to a land line, I updated the kernel source and samba all right, but qt was a mismatch. RC3 was out of date and we're in RC4 now!

After a refresh through slackpkg update, I did the install-new (nuthin') and upgrade-all again, this time with a load of new stuff including a new glibc!

All upgraded now, but wicd still cannot find my wireless router fifteen feet away and now X starts up with wide black and white bands across the lower half of the screen before giving me the xfce4 splash screen. Then it puts its "X" in the middle of the screen -- I haven't seen that in years! It takes an unusually long time to set up my desktop display, and then it doesn't recognize my mousepad.

I can use this machine now reasonably well without wireless networking and without X, but I've kinda gotten used to those features in recent years and would like to have them back.

Any ideas?

same reported man issue here on --current.
Some Applications Menu anomalies as well, (duplicates of "run program" and "Logout" "Terminal" and "Web Browser")

so far, so good.

With XFCE only installs, the hiccup in Thunar-Volume Manager's automounting of removable USB drives and CDROM's is still there as in RC3. Neither appears to work. Though you can manual mount via the terminal.

Recap, clean install of Slackware64 bit. 14-RC4, no KDE, XFCE only. XDM login manager. user groups: users lp floppy audio video cdrom plugdev power netdev.
Volume management turned on in Thunar, along with the checkboxes for mounting removable devices.

Inserting CDROM or usbdrive doesn't show up in either Thunar or a display removeable icon. But there is the persistent D-bus set_g_error message shown below after inserting a USB stick. (nm-applet:3187}

Inserting a CDROM doens't generate the thunar-volman message.

A bit of a mystery. Via google, older forums in Ubuntu note similar problems in Thunar-Volume management and some suggest playing around with Consolekit/Policykit settings as a possible solution.

If possible, make a clean install of Slackware 14 RC4, to be sure that your problems don't come from your successive upgrades.

I see these too.

I do not see any such message with 'man mplayer'.

same here

same here. man shutdown, last and halt do spit out "Error parsing *roff command from file ..."

manpage troff syntax error? utf8? There seem be a few bug reports scattered about that the line at top of the manpage spits out this error (explicit declaration of locale). The manpages without this line seem fine.

When opening a .csh file with kwrite/kate I see:

There were warning(s) and/or error(s) while parsing the syntax highlighting configuration.

/usr/share/apps/katepart/syntax/tcsh.xml:Deprecated syntax.
Context Cmd@ not addressed by a symbolic name/usr/share/apps/katepart/syntax/tcsh.xml:Deprecated syntax.
Context CmdSet not addressed by a symbolic name

BTW, I remember there was an answer here (in LQ) to how to view utf8 man pages properly. It was helpful but I failed to find it just now.

Does anyone remember which post it was in? This is what I get at present:

@guanx
hmmm comment out the following in in /etc/profile.d/lang.sh
and uncomment

There were some earlier suggestions to do a clean install. I have done something quite similar to what you describe once or twice. If you have slackpkg, you can re-install package groups; if not, try booting with the installer, mount your file systems, and (re-)install away. You may be able to do this with pkgtool, you may be able to do this with setup.

netatalk has a couple of files (/etc/netatalk/atalkd.conf.new and /etc/netatalk/papd.conf.new) that aren't getting config'd in doinst.sh.

aaa_elflibs has some old versions of libpng and glib2 files.

I noticed in /boot/README.mkinitrd references are to 3.2.27 rather than 3.2.28, and the lilo section is a bit strange.
Looks like a missing parenthesis..

Very minor. I'm running 14 rc4 on my new laptop and it's running amazing.

I just made a clean install of slackware64-14.0rc4. Everything works very well :D

Just upgraded my everyday desktop, no problems so far!

14.0RC4 is running on a double-boot box here in 32-bit and 64-bit mode, with Xfce. When inserting a CD-Rom or a DVD and mounting it in Thunar, the automagic mountpoint is /run/media/<disk_label>. Did I miss some evolution here?

Well, if you try hardly enough, you always will find something to fix.

For instance in the installer, isolinux.cfg includes three entries for kernels with respective labels huge.s, hugesmp.s and speakup.s

The last two are somehow duplicates, as both launch the same kernel (hugesmp.s), but at the same time the help text that you see if you hit the F2 key (f2.txt) says:
This is somehow slightly inconsistent - and possibly a reminiscence of an older version.

I guess that this doesn't deserve an RC5, though ;)

That sounds a lot like the old generic advice in the early days of Windows: "Oh, you just need to reinstall Windows!" ... but it worked!

That new xfce4 default setup is pretty!

This fresh install apparently cleared out a lot of assorted cruft and freed up more of my limited disc space.

NetworkManager doesn't want to voluntarily find my wireless router yet, but automounting of USB flash drives is now working again after several months of not working.

I'll reinstall wicd, chrome, flash-player-plugin, and those (less than a dozen) SBo, alien and slacky packages. Oh, and I'll be wanting to upgrade guile again from the version 1.8.8 installed by default (I think they're at 2.0.6 now).

All better now, Thanks!

There was a discussion some days back about default mount points in /run rather than /media. I can't find that discussion and would be grateful for a link. Thanks!

I think you're referring to this.
http://www.linuxquestions.org/questi...ml#post4761013

I'm using Fluxbox and haven't decided how to handle the loss of HAL,
so I haven't run across this issue yet. :(

Actually NetworkManager has now woken up and is working for me better than wicd! One less /extra package to reinstall.

Yay!

AKAIK, there is no magic solution, as the manuals are bundled without any mechanism allowing to each of them to declare the charset it uses. Here I think you look at an UTF-8 manual with an UTF-8 locale, so groff converts it to UTF-8 because it knows your local charset but ignores the page is already suitable for it. Try this to inform groff there's no need to convert:

It's a typo, I think. The leading single quote should be a dot.

Hi, stimulated by the discussion about the html-ide ([SOLVED] Recommendation Please - WYSIWYG HTML Editor) and the mentioned link through which I found geany I ran into this make-error when compiling its plugins:

The current libsoup package installs only .so files into /usr/lib64 not a .la file.

Not sure if this is wrong or correct, but the netatalk package includes two configuration files in /etc/netatalk atalkd.conf.new and papd.conf.new which are not handled by the doinst.sh script and therefore stay as *.new files even if there is no existing configuration file during install.

For those who don't want to search whole thread, see this post - http://www.linuxquestions.org/questi...ml#post4761516

I'm running Fluxbox without HAL, but udev + udisks (not udisks2) + udiskie script works like a charm. And it even mounts devices to /media ;)

And by the way, I did new install (accidentally partially erased my /etc, so new-install was fastest way how to fix this and it also cleaned few once-compiled-now-completely-forgotten programs) and Slackware 14 RC4 runs just fine. Well, I'm experiencing one problem with ipw2200 kernel module*, but that's nothing Slackware can fix. And I would also like to resolve rc.dhcpd issue, but I can live without it. Slackware 14 RC4 is flawless from my point of view.

* due to change in udev, ipw2200 fails to load at first, timeout after 60 seconds and then it's successfully loaded again. Nothing actually broken, only you have to wait for 60 more seconds. If anyone wants details, feel free to ask.

Yes, thank you.

Is there a way to override this new mount point location and restore back to /media?

Say,

I really like the new xfce4 weather module, but what's happened to the xfce4 power manager? I can't find it.

Unfortunately no, /media is going to be obsolete now. :(

However there are few thing you could do, at least for now. Get rid of udisks2 and stick with udisks as long as posible or apply this patch (http://paste.lisp.org/display/129168), but it isn't long-term solution.

Apparently udisks developers decided that instead of implementing certain feature (actually useful one) the right way (read: harder), they simply break standards (FHS in this case) without worrying "what could possibly go wrong?". Sounds familiar? Yes, it's the same systemd-like mindset - "I like it that way, so it'll become new standard. XYZ isn't relevant anymore." I guess only long-term solution is to fork udisks2 and let GNOME (udisks2 will be it's default auto-mounter) , udev+systemd guys live in their Perfect World (TM) alone, while we'll be using saner software in saner way.

There is good blogpost about it - Udisks2: Another Loss For Linux

That's what I don't understand. Why /run? What are you running? usually when I mount a cd or dvd it is to view files. /media is perfect name for it. You don't "run" media.

Just my $0.02.

Just if you didn't notice before: udev has been forked.

https://www.linuxquestions.org/quest...ev-4175424319/