SuSE 9 Problem
Results 1 to 2 of 2

Thread: SuSE 9 Problem

  1. #1
    AO Veteran NeuTron's Avatar
    Join Date
    Apr 2003
    Posts
    550

    SuSE 9 Problem

    I just bought SuSE 9, which I am very impressed with. After using it for about a week, I have run into a trivial yet annoying little problem:

    I use AIM for linux and it has been fine this last week and on every other linux box I have used in the past. Out of the blue, AIM has started to load up but wont display the window in KDE for my default user. When I log into the machine as root and load KDE, AIM works fine. Its only with my regular account that I run into this problem. The program seems to load and I can see AIM on the panel at the bottom of the window manager. The window just wont dislplay. I do not have enough linux experience to troubleshoot this problem, as nothing I've tried has worked. Any help would be greatly appreciated.

    • SuSE 9
    • KDE 3.1
    • AIM 1.5.286

    -NeuTron

    ****Update***** Here is what I get when I run "ps -A" while AIM is acting like its running but wont display the window. Seems odd that it isn't assigned to a TTY.
    ***********@*******:~> ps -A
    PID TTY TIME CMD
    1 ? 00:00:02 init
    2 ? 00:00:00 keventd
    3 ? 00:00:00 ksoftirqd_CPU0
    4 ? 00:00:00 kswapd
    5 ? 00:00:00 bdflush
    6 ? 00:00:00 kupdated
    7 ? 00:00:00 kinoded
    8 ? 00:00:00 mdrecoveryd
    11 ? 00:00:00 kreiserfsd
    836 ? 00:00:00 syslogd
    839 ? 00:00:00 klogd
    898 ? 00:00:00 khubd
    1017 ? 00:00:00 resmgrd
    1039 ? 00:00:00 cardmgr
    1178 ? 00:00:00 portmap
    1265 ? 00:00:00 acpid
    1267 ? 00:00:00 sshd
    1400 ? 00:00:00 cupsd
    1539 ? 00:00:00 master
    1683 ? 00:00:00 cron
    1686 ? 00:00:00 nscd
    1688 ? 00:00:00 nscd
    1689 ? 00:00:00 nscd
    1690 ? 00:00:00 nscd
    1691 ? 00:00:00 nscd
    1692 ? 00:00:00 nscd
    1693 ? 00:00:00 nscd
    1768 ? 00:00:00 kdm
    1822 tty1 00:00:00 mingetty
    1823 tty2 00:00:00 mingetty
    1824 tty3 00:00:00 mingetty
    1825 tty4 00:00:00 mingetty
    1826 tty5 00:00:00 mingetty
    1827 tty6 00:00:00 mingetty
    1828 ? 00:01:14 X
    1830 ? 00:00:00 kdm
    1865 ? 00:00:00 kde
    1911 ? 00:00:00 kdeinit
    1914 ? 00:00:00 kdeinit
    1917 ? 00:00:00 kdeinit
    1920 ? 00:00:01 kdeinit
    1926 ? 00:00:07 kdeinit
    1930 ? 00:00:26 artsd
    1932 ? 00:00:00 kdeinit
    1933 ? 00:00:00 kwrapper
    1935 ? 00:00:00 kdeinit
    1936 ? 00:00:05 kdeinit
    1939 ? 00:00:01 kdeinit
    1941 ? 00:00:06 kdeinit
    1989 ? 00:00:00 dhcpcd
    2070 ? 00:00:18 kdeinit
    2072 ? 00:00:00 kdeinit
    2096 ? 00:00:03 kdeinit
    2098 ? 00:00:01 kamix
    2103 ? 00:00:01 susewatcher
    2104 ? 00:00:05 suseplugger
    2107 ? 00:00:05 kdeinit
    2109 ? 00:00:00 kalarmd
    2134 ? 00:00:01 kdeinit
    2159 ? 00:08:12 mozilla-bin
    2165 ? 00:00:00 mozilla-bin
    2166 ? 00:00:00 mozilla-bin
    2167 ? 00:00:00 mozilla-bin
    2168 ? 00:00:00 mozilla-bin
    2169 ? 00:00:00 mozilla-bin
    2190 ? 00:00:00 netstat <defunct>
    2192 ? 00:00:00 esd
    2194 ? 00:00:04 xchat
    2209 ? 00:00:05 kmail
    2230 ? 00:00:00 kdeinit
    2234 ? 00:00:00 kdesud
    2863 ? 00:00:00 pickup
    2864 ? 00:00:00 qmgr
    3294 ? 00:00:00 aim
    3301 ? 00:00:01 java_vm
    3302 ? 00:00:00 java_vm
    3303 ? 00:00:00 java_vm
    3304 ? 00:00:00 java_vm
    3305 ? 00:00:00 java_vm
    3306 ? 00:00:00 java_vm
    3307 ? 00:00:00 java_vm
    3308 ? 00:00:00 java_vm
    3309 ? 00:00:00 java_vm
    3311 ? 00:00:00 java_vm
    3313 ? 00:00:00 java_vm
    3314 ? 00:00:00 java_vm
    3316 ? 00:00:00 java_vm
    3317 ? 00:00:00 mozilla-bin
    3318 ? 00:00:00 mozilla-bin
    3319 ? 00:00:00 java_vm
    3321 ? 00:00:00 java_vm
    3335 ? 00:00:01 kdeinit
    3336 pts/1 00:00:00 bash
    3352 pts/1 00:00:00 ps

  2. #2
    Senior Member
    Join Date
    Sep 2003
    Posts
    179
    I know this might sound stupid, but I know I've had some probelms with a program that starts from a saved session. (when kde closes it remembers what you had open and starts those programs at startup) have you tried using the kill command and then restarting aim?

    I know this worked for me a couple times with diffrent programs though.

    DeafLamb

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •