SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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...
$ 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.
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?
Last edited by leeeoooooo; 09-01-2012 at 09:56 AM.
Reason: remove redundundant wording
$ 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")
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.
There were warning(s) and/or error(s) while parsing the syntax highlighting configuration.
/usr/share/apps/katepart/syntax/tcsh.xmleprecated syntax.
Context Cmd@ not addressed by a symbolic name/usr/share/apps/katepart/syntax/tcsh.xmleprecated syntax.
Context CmdSet not addressed by a symbolic name
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.