Slackware 14.0 RC4

Mark Pettit · 09-01-2012, 02:02 AM

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

jaycee4 · 09-01-2012, 03:40 AM

Quote:

Originally Posted by storkus

Also, I'm curious: is RC4 a new record for RC's, or have we been to RC5+ before?

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...

solarfields · 09-01-2012, 03:42 AM

Quote:

morons at Phoronix....

Moronix....

phenixia2003 · 09-01-2012, 06:28 AM

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:

Code:

23e594e1c4cd5874ebe90abc641c5055  ./slackware/a/dbus-1.4.20-i486-3.txt
60d55e594b0b070a4a09101ea9b8eacf  ./slackware/a/dbus-1.4.20-i486-3.txz
79e071aac91b7e0a7f4055bc048a2b8b  ./slackware/a/dbus-1.4.20-i486-3.txz.asc

...

23e594e1c4cd5874ebe90abc641c5055  ./slackware/l/dbus-1.4.20-i486-3.txt
60d55e594b0b070a4a09101ea9b8eacf  ./slackware/l/dbus-1.4.20-i486-3.txz
81219205c592a58e0822a8c84980c068  ./slackware/l/dbus-1.4.20-i486-3.txz.asc

--
SeB

yars · 09-01-2012, 08:12 AM

But in the ChangeLog.txt file all good:

Code:

$ grep -3 -e "dbus-1.4.20" ../ChangeLog.txt 
  symlink.  Thanks to Josiah Boothby.
+--------------------------+
Wed Aug  1 20:24:06 UTC 2012
a/dbus-1.4.20-i486-2.txz:  Rebuilt.
  Patched rc.messagebus to restart the system D-Bus daemon even if a user
  daemon is running (as it does now with X11 sessions).
  Thanks to Darren Austin.
--
a/cryptsetup-1.4.3-i486-1.txz:  Upgraded.
a/cups-1.5.3-i486-2.txz:  Rebuilt.
a/cxxlibs-6.0.17-i486-1.txz:  Upgraded.
a/dbus-1.4.20-i486-1.txz:  Upgraded.
a/grep-2.13-i486-1.txz:  Upgraded.
a/gzip-1.5-i486-1.txz:  Upgraded.
a/kernel-generic-3.2.23-i486-1.txz:  Upgraded.

leeeoooooo · 09-01-2012, 08:39 AM

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?

Habitual · 09-01-2012, 08:48 AM

Quote:

Originally Posted by aocab

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

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.

Loslobo · 09-01-2012, 10:35 AM

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.

Code:

** (process:3189): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'

** (process:3189): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags'

** (process:3189): WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags'

** (nm-applet:3187): CRITICAL **: dbus_set_g_error: assertion `gerror == NULL || *gerror == NULL' failed

(xfdesktop:3179): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed

(xfdesktop:3179): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed

(xfdesktop:3179): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed

(xfdesktop:3179): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed

(xfdesktop:3179): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed

(xfdesktop:3179): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed

(xfdesktop:3179): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed
thunar-volman: Unsupported USB device type.
thunar-volman: Unsupported USB device type.
thunar-volman: Unknown block device type.

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.

Didier Spaier · 09-01-2012, 10:44 AM

Quote:

Originally Posted by leeeoooooo

Any ideas?

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

Woodsman · 09-01-2012, 01:47 PM

Quote:

$ 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

I see these too.

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

escaflown · 09-01-2012, 01:56 PM

Quote:

Originally Posted by Woodsman

I see these too.

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

same here

kingbeowulf · 09-01-2012, 03:00 PM

Quote:

Originally Posted by Woodsman

I see these too.

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

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

Code:

'\" -*- coding: UTF-8 -*-

at top of the manpage spits out this error (explicit declaration of locale). The manpages without this line seem fine.

aocab · 09-01-2012, 03:05 PM

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

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

eprecated syntax.
Context CmdSet not addressed by a symbolic name

guanx · 09-01-2012, 03:15 PM

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:

Code:

CHSH(1)                           Linux Reference Manual                           CHSH(1)

åç§°
       chsh - æ´æ¢ä½ ç»å¥æ¶æç¨çshell

è¯æ³
       chsh [ -s shell ] [ -l ] [ -u ] [ -v ] [ username ]

æè¿°
       chsh ç¨æ¥æ´æ¢ä½ ç»å¥æ¶æç¨çshell ãå¨å½ä»¤åæ²¡æå®shellã chsh ä¼æç¤ºä¸ä¸ªç»ä½ ã

   ææçshell
       chsh å¯ç¨æå®è·¯å¾å¨åçæ¹å¼æ¥æå®ä»»ä½ä¸ä¸ªå¯æ§è¡çæ¡£æ¡ã ç¶èï¼å¦ææ¤ shellå¹¶æ²¡çºªå½å¨
       /etc/shells æ¡£ä¸ï¼åchshä¼æåºè¦åè®¯æ¯ã

red_fire · 09-01-2012, 10:21 PM

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

Code:

export LANG=en_US

and uncomment

Code:

export LANG=en_US.UTF-8