Quick Hacks I

Summary:

• {-> 6.1/5} KDE displays duplicate icons after upgrade
• {-> 6.1/5} 'fetchmail' and 'sendmail' don't work anymore after upgrade
• {= 6.1/5} Postgresql init script can't find appropriate data directory
• {-> 6.1/5} Root can't run graphical apps on user desktop
• {-> 7.1} General Protection Fault after shutdown

{-> 6.1/5} KDE displays duplicate icons after upgrade

(by Francis Galiegue, edited):

>Do, as root:

>

>

find /usr/share/applnk -name "*rpmsave" -exec rm {} \;

section index

{-> 6.1/5} 'fetchmail' and 'sendmail' don't work anymore after upgrade:

(contributed by Marc Siegel, abridged)

>This solution turned up on dejanews (simplified to comandlines by me)

>

>As root:

>* Remove sendmail:

rpm -e sendmail

>* Backup deferred mail:

cp -Rp /var/spool/postfix/def* /tmp/

>* Remove postfix:

rpm -e ––nodeps postfix

>* Make sure it's gone:

rm -rf /var/spool/postfix

>* Re-install Postfix:

rpm -Uvh /mnt/cdrom/Mandrake/RPMS/postfix*

>* Restore deferred mail:

cp -Rp /tmp/def* /var/spool/postfix/

>* Make sure files are in order, permissions, etc:

postfix check

>* Start postfix daemon:

/etc/rc.d/init.d/postfix start

section index

{= 6.1/5} Postgresql init script can't find appropriate data directory

(by J.M. Dault, abridged)

>That is not a bug, that's a feature. We don't want to trash a user's database during upgrade.

>

>Solution is either:

>

>1) read the documentation and convert the existing database from 6.4 to 6.5
2) rpm -e all postgresql packages, delete /var/lib/pgsql and re-install the rpms.

section index

{-> 6.1/5} Root can't run graphical apps on user desktop

(concocted from various mails) As a user, type:

xhost {IP}

xhost 127.0.0.1

xhost -127.0.0.1

You can automatically grant root access to your display by putting the above line in either

~/.xinitrc

~/.xsessionrc

(Note: You may not have these files in your home-directory yet. Open an editor and write these lines:

~#1.1 /bin/sh xhost {IP}

Put in the appropriate value for {IP}, of course ;-). Save and close the file under the appropriate name and make it executable by

chmod 755 {filename}

Don't forget the dot1.1 )

You shouldn't forget, however, that this may cause a security issue when connecting to the outside world (by allowing intruders to connect to your display)1.1 You can help this by supplying an executable mini-script like

~#1.1 /bin/sh xhost -{IP}

and run it from your connect script or your favourite dialer (most of them allow running programs after connect). Likewise you can run your .xinitrc or .xsessionrc after disconnecting (of course not if they contain other commands, too. In this case write another script to add the IP again).

section index

{-> 7.1} General Protection Fault after shutdown

This is related to some chipsets (mainly VIA). Fix: Change the last line of

/etc/rc.d/init.d/halt

eval $command -i -d -p

to

eval $command -i -d

LM User Nico Neumann reports:

>I installed Mandrake 7.0 - 2 successfully, but did not manage to get the "power off after shutdown" - function working. I use a DFI P5BV3 Rev. B mainboard.
I now found a new BIOS at www.dfi.com from March 2000 that solves this problem. There are new BIOS versions for all revisions of the board.

section index

Next Item: Next page of Quick Hacks

Related Resources:

Mandrake-Linux Bug-Tracker
Mandrake Linux Update and Security Advisories

Modified: May. 13, 2000
Author: Tom Berger

Legal: This page is covered by the GNU Free Documentation License. Standard disclaimers of warranty apply. Copyright LSTB and Mandrakesoft.