Description of Problem: Licq doesn't start on KDE session restoring. Version-Release number of selected component (if applicable): licq-1.1.0-0.cvs20020412.1 licq-kde-1.1.0-0.cvs20020412.1 How Reproducible: Always. Steps to Reproduce: 1. Enable KDE session manager. 2. Start licq. 3. Close KDE. 4. Login again. Actual Results: Licq isn't started by the session restoring. Expected Results: Licq should start. Additional Information: Here is my .xsession-errors: rm: cannot remove `.' or `..' bash: no job control in this shell No value for $TERM and no -T specified No value for $TERM and no -T specified No value for $TERM and no -T specified No value for $TERM and no -T specified _KDE_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root DCOPServer up and running. Mutex destroy failure: Device or resource busy Mutex destroy failure: Device or resource busy mcop warning: user defined signal handler found for SIG_PIPE, overriding _IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMaximumSize: (unnamed/DigitalClock) Negative sizes (2,-4) are not possible QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMaximumSize: (unnamed/DigitalClock) Negative sizes (2,-4) are not possible QObject::connect: No such slot KWrited::block_in(const char*,int) QObject::connect: (sender name: 'unnamed') QObject::connect: (receiver name: 'unnamed')
Can you reproduce this with a newer KDE and licq version?
Created attachment 97048 [details] KDE session manager config file Yes, it still happens. The problem is that the command is saved in the ksm config file as "licq-bin" without the full path. The session manager is then unable to find this command.
Oh, and that's on a stock Fedora. Maybe it would be worthwhile to wait for 3.2 instead of spending time to fix it.
*** Bug 64045 has been marked as a duplicate of this bug. ***
'Red Hat Raw Hide' refers to the development tree for Red Hat Linux. Red Hat Linux is no longer supported by Red Hat, Inc. If you are still running Red Hat Linux, you are strongly advised to upgrade to a current Fedora Core release or Red Hat Enterprise Linux or comparable. Some information on which option may be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/. Red Hat apologizes that these issues were not resolved in a more timely manner. However, the issues listed in these bugs are in packages that are no longer shipped in a current Fedora Core release. Hence, we are closing these bugs CANTFIX.