Xorg segfault after latest upgrade -current
 

After latest X11 upgrade (Sat May 5 02:28:15 UTC 2012) Xorg crashes with segfault. I have pretty old Nvidia GPU running with open-source nv driver. I also tried Nouveau driver and Xorg stops before it can segfault (for some reason Xorg refuses to start with Nouveau), so segfault appears after all modules and libraries are checked and loaded.

Strange thing is that on another computer (with ATI GPU) running nearly identical -current system, Xorg works without a glitch.

Here goes Xorg.O.log
Relevant lines:
Full log:

Your NVIDIA GeForce2 Ti should be supported by the nouveau driver. http://nouveau.freedesktop.org/wiki/CodeNames#NV10
Are you trying to use KDE? If so, there may be a problem as your card may not be capable of all the OpenGL features that KDE expects.

I suggest again trying the nouveau driver as the nv driver is unsupported. This section from CHANGES_AND_HINTS.TXT may be relevant.

It is supported and works. Xorg previously failed because of missing nouveau driver. I guess I though kernel module was enough :)

Since when? I'm just curious.

Anyway, thanks for your help!

How did you upgrade? I hope you didn't use slackpkg.

Could you be more verbose and explain what is your concern? I've recently upgraded my current 64bit system using slackpkg and installed the new packages using "--install-new" option. The only issue I've faced is that the drop shadow effect in xcompmrg has stopped working properly, although the fade effect is still there. Could it be due to a fact that the libX11 is now build against XCB or the new ati video driver (my card is manufactured by ATI)?

Thanks,

Alkin

Slackware doesn't use dependencies, therefore 'slackpkg upgrade-all' doesn't know which package depends on which. The changelog in -current comes with a wealth of information that slackpkg cannot parse.
Some examples:
Slackpkg doesn't know that some packages must be removed to make the new ones work. All these bits of information will eventually go into the "Changes and hints" when the new stable version is released.

I do use slackpkg but only to install/upgrade individual packages not the whole system.

Another option is using it to upgrade everything, read the changelog too and behave consequently: I use this with no pain since I can remember (years). ;)

I always use slackpkg (with care) to upgrade my Slackware system.
In case you had my versions okf KDE4 packages installed and blacklisted them in "/etc/slackpkg/blacklist" you will first have to remove or comment out the line "[0-9]+alien" so that slackpkg can upgrade my packages with the official Slackware versions.

The following steps should work for all situations:

Blacklist the following packages in "/etc/slack/pkg/blacklist":
If new kernels have been added, then "installpkg" those new kernel packages first (do not use "upgradepkg").
Update your "/etc/lilo.conf" with the new kernel (don't remove your running kernel!) and run "lilo".
You should always be able to boot back into a previous kernel in case the new Slackware kernel gives you a hard time.

# slackpkg update

Now that slackpkg has updated its internal database we can let it update the computer with the current state of affairs.

# slackpkg install-new

# slackpkg upgrade-all

# slackpkg clean-system

The first of those three commands (install-new) will install every package which is listed in the ChangeLog.txt file as "Added:" It will not install any other packages, for instance if you did not have KDE installed before, this command will not add KDE packages to your computer all of a sudden.
The third commmand (clean-system) will show you an overview of all packages which are not part of Slackware Linux at this moment. That means, the list will show any package which has been removed from Slackware like kdeaccessibility, kdebase, etccetera. It will also show you every 3rd party package which you have installed! So, use this command wisely. De-select every package which you want to keep (i.e. all 3rd party packages) and then click "OK" to let slackpkg remove all obsolete packages.

This is the easiest way to get "current" again, it is also the proper way to upgrade between two adjacent stable Slackware releases.
You can trust slackpkg to do it safely, but it will need your brains and care.

Eric

http://www.phoronix.com/scan.php?pag...kills_nv&num=1

On the side issue of Slackpkg that has arisen.
Slackpkg works by syncing your installed packages to those in the official Slackware trees. It is the official tool for maintaining Slackware. I would not use anything else for maintaining my Slackware installs, apart from the occasional use of the tools in pkgtool.

Agreed. Slackpkg is the best utility for maintaining/updating your Slackware systems.

I do agree with the above statement, except in the latest update, slackpkg failed to properly do it's job while migrating from xaw3d to libXaw3d. It couldn't keep the items belonging to the new package (libXaw3d) when removing xaw3d. Luckily it's easy to fix by reinstalling libXaw3d

When something is indicated as "Removed" in the ChangeLog, usually I removepkg it before upgrading everything with slackpkg.

If I can't remove it because it's a base package, like it happened with util-linux-ng/util-linux not long ago, I use upgradepkg on it with the %, like GazL suggested me at the time ;) (after -my bad- I found it also in the manpage :D ).

Was this really a Slackpkg problem? As I understand it, Slackpkg merely overlays the installpkg, upgradepkg and removepkg tools in pkgtool.

I used to the other way around
I added the new packages first by installpkg or slackpkg install-new and then i removepkg the removed package
But i learned from xaw3d case that it's wiser to add another shot at upgradepkg --reinstall on new added packages just to make sure everything stays in place after the package removal

Just for a record, I used slackpkg two-step upgrade (upgrade-all && install-new). The problem was in deprecated 'nv' driver.