| 1 |
james wrote: |
| 2 |
> Neil Bothwick<neil<at> digimed.co.uk> writes: |
| 3 |
> |
| 4 |
> |
| 5 |
> |
| 6 |
>> It's possible kmix is already running, even though no icon is showing, |
| 7 |
>> try killall kmix first. |
| 8 |
>> |
| 9 |
> Um the icon does show up in the bottom bar and under |
| 10 |
> the kde pludown menu....... Launching from either results |
| 11 |
> in a bouncing icon and no app started. |
| 12 |
> |
| 13 |
> Manual launch from the terminal, just returns empty. |
| 14 |
> nice idea! but: |
| 15 |
> |
| 16 |
> # killall kmix |
| 17 |
> kmix: no process found |
| 18 |
> |
| 19 |
> |
| 20 |
> Besides the problem survives a emerge -e system |
| 21 |
> and subsequent reboot, so the next blunt instrument |
| 22 |
> is emerge -e world...... |
| 23 |
> |
| 24 |
> All the kde packages are going to get rebuilt.... |
| 25 |
> |
| 26 |
> James |
| 27 |
> |
| 28 |
|
| 29 |
I noticed this: |
| 30 |
|
| 31 |
root@fireball / # ps aux | grep kmix |
| 32 |
dale 667 0.0 0.8 453144 33048 ? Sl Jan28 0:00 |
| 33 |
kdeinit4: kmix [kdeinit] -session |
| 34 |
10d8df6f6b000124700450100000112470008_1281663401_3252 |
| 35 |
root 27998 0.0 0.0 6188 572 pts/0 R+ 11:30 0:00 grep |
| 36 |
--colour=auto kmix |
| 37 |
root@fireball / # |
| 38 |
|
| 39 |
killall kmix may not work in that case. It appears it is running as |
| 40 |
part of kdeinit. May not want to kill that unless you have nothing open |
| 41 |
that matters. Not sure what all that would kill. |
| 42 |
|
| 43 |
You may could just kill that specific process tho. That may help. |
| 44 |
Another thought, do you not have a Kmix icon in the panel? That's where |
| 45 |
mine is. It looks like a speaker with some sound coming out of it. |
| 46 |
|
| 47 |
Dale |
| 48 |
|
| 49 |
:-) :-) |
Archives