LinuxQuestions.org - Slackware 14.0 RC1 Arrived: Send Your Bug Reports

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Slackware 14.0 RC1 Arrived: Send Your Bug Reports (https://www.linuxquestions.org/questions/slackware-14/slackware-14-0-rc1-arrived-send-your-bug-reports-4175421309/)

-Current working good here except for thunar opened with “kdesu thunar” from mortal user account doesn’t have trash or network in KDE or XFCE.
If I log in to KDE or XFCE root session then everything works.
I Googled it and found several bug reports on thunar so I don't think it's a Slack problem.
However I'm very happy to now be able to access my samba servers via thunar from user accounts.
Things just keep getting better and better.
Thanks Slack crew!

Quote:

Originally Posted by chess (Post 4750485)

Thanks, Pat and the entire team for all the hard work to reach RC1. This is a great set of updates and I can't wait for the release of 14.0!

Me neither. I'm ordering a virgin laptop for my university studies (READ: It has not had the cold,dead hand of Bill G. upon it), and it would be a great match for the release of Slackware 14.0.

GO SLACK!!!!!!

I get segmentation fault when I try to run slapt-get and clementine. Messages in dmesg:

Code:

[40340.879702] clementine[14422]: segfault at 0 ip 00007f62320875a6 sp 00007fff616c1088 error 4 in libc-2.15.so[7f6232002000+1b3000]

[40420.097463] slapt-get[14466]: segfault at 0 ip 00007fe0c02745a6 sp 00007fffc0f70258 error 4 in libc-2.15.so[7fe0c01ef000+1b3000]

WoW !!!

Almost there !!! :D

Quote:

Originally Posted by zeroberto (Post 4751023)

I get segmentation fault when I try to run slapt-get

you have to rebuild slapt-get yourself from source: you will need also this patch from its git repository.
after patching, do a "make pkg" to build an installable/removable package.

I though that openjdk would make its way in Slackware 14... It seems that I was wrong.

No worries though, as we can either build a package for the Oracle jdk or jre with the slackbuilds provided in /extre/source or use the openjdk packages or SlackBuilds provided by AlienBOB.

So far, so good, thanks to PV and the team.

After applying the updates to RC1...
I noticed that the output from the daily cron jobs was not mailed to root as I configured.

I removed the "1> /dev/null" from the line for daily cron jobs in /var/spool/cron/crontabs/root so that root would get a message.

Code:

# Run daily cron jobs at 12:40 every day:

40 12 * * * /usr/bin/run-parts /etc/cron.daily

And I configured sendmail to send root's mail to my account and I would usually get a message with:

Code:

/etc/cron.daily/certwatch:

/etc/cron.daily/logrotate:

/etc/cron.daily/slocate:

This way I would know that the jobs ran.

However after the updates...
The log files do not appear to have been rotated and there are no messages from sendmail in /var/log/maillog

Messages from sendmail for the previous run before the updates.

Code:

Aug  8 12:43:04 emachinesw3503 sendmail[2810]: q78Hh441002810: from=root, size=158, class=0, nrcpts=1, msgid=<201208081743.q78Hh441002810@emachinesw3503.localdomain>, relay=root@localhost

Aug  8 12:43:08 emachinesw3503 sm-mta[2811]: q78Hh5aG002811: from=<root@emachinesw3503.localdomain>, size=466, class=0, nrcpts=1, msgid=<201208081743.q78Hh441002810@emachinesw3503.localdomain>, proto=ESMTP, daemon=MTA, relay=localhost.localdomain [127.0.0.1]

Aug  8 12:43:08 emachinesw3503 sendmail[2810]: q78Hh441002810: to=root, ctladdr=root (0/0), delay=00:00:04, xdelay=00:00:03, mailer=relay, pri=30158, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (q78Hh5aG002811 Message accepted for delivery)

Aug  8 12:43:08 emachinesw3503 sm-mta[2812]: q78Hh5aG002811: to=alpha, ctladdr=<root@emachinesw3503.localdomain> (0/0), delay=00:00:02, xdelay=00:00:00, mailer=local, pri=30701, dsn=2.0.0, stat=Sent

Any ideas on what to check?
Thanks in advance...

Edit:
Removed the "1> /dev/null" for the hourly cron jobs.
Created an hourly cron job.

cat /etc/cron.hourly/hourlytouch

Code:

#!/bin/sh

touch /tmp/hourlytouch-`date +%m%d%g%I%M`

The file gets created but root does not receive an email message.

Is there any reason of having seperate seamonkey-solibs now that mozilla-nss, which includes nspr, was added?
IMO there isnt but someone else might have better insight than me.

edit: seperate js was added as well.
From the seamonkey-solibs slack-desc:

Code:

This package contains a subset of the shared libraries from Seamonkey to provide runtime support for programs that require nss, nspr, and js.

all of which are part of Slackware now.

edit2: that also means seamonkey doesnt need to mess with /etc/ld.so.conf anymore.

Also polkit seems to be present in both l/ and kde/ in 32bit.

There's a small bug in Slackware64's version of yptools. Utilities like 'ypinit' seem to look for their counterparts in '/usr/lib' and not in '/usr/lib64', which produces a series of 'command not found' errors.

It's easy to fix this bug with a quick & dirty workaround like this:

Code:

# cd /usr/lib

# ln -s /usr/lib64/yp .

My two cents.

I've been using AlienBob's KDE4.9 with current but would like to upgrade to the beta.

Is there anything in particular that I need to do or can I just do the normal update/install-new/upgrade-all procedure?

I notice the order of install went as follows:

ModemManager-0.5.2.0-x86_64-1.txz
aaa_base-14.0-x86_64-3.txz
analitza-4.8.5-x86_64-1.txz
ark-4.8.5-x86_64-1.txz
blackbox-0.70.1-x86_64-7.txz
blinken-4.8.5-x86_64-1.txz
boost-1.49.0-x86_64-3.txz
....

Was this intentional, I always though that aaa_... packages should be upgrade, installed first first and the reason they are start with aaa_.

Quote:

Originally Posted by chrisretusn (Post 4751612)

Was this intentional, I always though that aaa_... packages should be upgrade, installed first first and the reason they are start with aaa_.

These are precompiled binaries, so the order doesn't matter. ModemManager goes first because uppercase precede lowercase letters.

Quote:

Originally Posted by chrisretusn (Post 4751612)

Was this intentional, I always though that aaa_... packages should be upgrade, installed first first and the reason they are start with aaa_.

If you're already up-to-date with current and just applying the latest batch of updates that Pat has provided then there's usually nothing to worry about. If you're applying several batches at once because you've fallen behind, then order might be an issue. aaa_elflibs is the main one to watch out for as if you do it in the wrong order you,might actually downgrade some libraries. aaa_base is just a bunch of empty directories so there's not much scope for damage.