Slackware 14.0 RC1 Arrived: Send Your Bug Reports

fl0 · 08-11-2012, 10:14 AM

Hi,

in the installer if the group KDEI is deselected the following packages are still selected in the detailed menu mode

Code:

kde-l10n-ca@valencia
kde-l10n-ia
kde-l10n-id
kde-l10n-si

regards fl0

SCerovec · 08-11-2012, 10:29 AM

hey?

Do please bump up that XFCE to 4.10 or at least to 4.8.x?
pretty please?

allend · 08-11-2012, 10:38 AM

Quote:

Do please bump up that XFCE to 4.10 or at least to 4.8.x?
pretty please?

Huh?

XFCE 4.10 entered Slackware-current on July 22

solarfields · 08-11-2012, 11:59 AM

Quote:

XFCE 4.10 entered Slackware-current on July 22

And running great so far, with one exception...

WoefulNarvik · 08-11-2012, 03:05 PM

Quote:

Originally Posted by allend

Same as GazL for me.

@GazL - Nice catch on the .xinitrc. I see the same.

Figures :P Things work fine with fvwm2 on my Slackware 14 beta 1 vm (I have yet to snapshot it and then upgrade it). I'll see what happens after I update it.

clifford227 · 08-11-2012, 06:30 PM

Which kernel version will slack 14 ship with?

hitest · 08-11-2012, 06:34 PM

Quote:

Originally Posted by clifford227

Which kernel version will slack 14 ship with?

Code:

Linux odin 3.2.26-smp #2 SMP Tue Aug 7 15:22:26 CDT 2012 i686

I'm guessing that 14.0 with ship with 3.2.26 unless some bugs are discovered. We are getting closer.

willysr · 08-11-2012, 06:34 PM

i think 3.2.36 or probably 3.2.37 if it make it

dc_eros · 08-11-2012, 09:13 PM

Sigh... Still syncing the slackware current tree here.

mrascii · 08-11-2012, 11:23 PM

NetworkManger missing from Services Menu:

Shouldn't /etc/rc.d/rc.networkmanager be included under "Select/deselect system daemons" in the "SELECT STARTUP SERVICES TO RUN" dialog box? I would think this would be a service that most would want to enable on startup.

DNA
AKA mrascii

bonixavier · 08-12-2012, 12:42 AM

The option CONFIG_FB_VESA=y in the RC kernel is causing NVIDIA's blob to spill the following error.

Code:

[   47.491112] NVRM: Your system is not currently configured to drive a VGA console
[   47.491114] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[   47.491116] NVRM: requires the use of a text-mode VGA console. Use of other console
[   47.491117] NVRM: drivers including, but not limited to, vesafb, may result in
[   47.491118] NVRM: corruption and stability problems, and is not supported.

For some unknown reason, vesafb stopped working with the newest versions of the blob. Reference is there.
http://www.nvnews.net/vbulletin/show...6&postcount=39

I'm pretty ignorant as to deciphering what all that means and the error message seems harmless to me, just thought I should mention it.

Didier Spaier · 08-12-2012, 12:53 AM

Quote:

Originally Posted by bonixavier

The option CONFIG_FB_VESA=y in the RC kernel is causing NVIDIA's blob to spill the following error.

Please do not kill the penguins! Furthermore, better resolution on the console is not bad.

If there is a real issue though, I hope nVidia will solve it.

Thom1b · 08-12-2012, 01:11 AM

Bug in the installer:
When installing slackware in a qemu-kvm PC using virtio drivers, all virtio devices are available ("fdisk -l" shows /dev/vdX devices) but the installer can't see /dev/vdX so I have to do that :
I install slackware without virtio drivers so I have /dev/sdX devices then I restart the cdrom with virtio enabled, chroot to my installation then modifying lilo.conf, fstab and create a initrd.gz successfully.

tpreitzel · 08-12-2012, 01:49 AM

just as GNOME was removed. XFCE is probably the best choice for a default desktop in Slackware. Just LOOK at the bloat of KDE!

Furthermore, Perl 5.16.0 is broken in respect to CPAN. I finally avoided using CPAN by manually creating packages for modules that I'd normally install via CPAN. The latter effort could have been avoided if the Perl installation weren't broken.

Anyway, I knew in advance that the upgrade to Slackware 14 wasn't going to be clean or easy. I was right ...

Thom1b · 08-12-2012, 01:59 AM

Bug in curl ?
When executing "./configure" script of ncmpcpp-0.5.10, I have this message :

Code:

checking for curl-config... /usr/bin/curl-config
/usr/bin/curl-config: line 138: CPPFLAG_CURL_STATICLIB: command not found

Ok it's not an error.

I looked at "/usr/bin/curl-config" and I replace :

Code:

if test "X${prefix}/include" = "X/usr/include"; then
  echo "$(CPPFLAG_CURL_STATICLIB)"
else
  echo "$(CPPFLAG_CURL_STATICLIB)-I${prefix}/include"
fi

by :

Code:

if test "X${prefix}/include" = "X/usr/include"; then
  echo "$CPPFLAG_CURL_STATICLIB"
else
  echo "$CPPFLAG_CURL_STATICLIB-I${prefix}/include"
fi

and it works.

It seems $CPPFLAG_CURL_STATICLIB has no reason to be a command, doesn't it ?

Edit 1: I'm wrong, it doesn't work. "./configure" works but "make" failed because of curl.
Edit 2: "make" failed also without modifying "/usr/bin/curl-config" on i486. "make" works perfectly on x86_64 with or without modification of curl-config. I hope I've not forgot anything and I don't lose your time.
Edit 3: I just retry to compile ncmpcpp on a clean slackware-current (i486) installation and "make" works.