Is there a way to change the default action that the kicker media applet takes when loading new media? I want it to stop loading amarok automatically when I insert an audio cd. At this point, the only reason I put in an audio cd is to rip it, and having it try to play in amarok automatically disrupts anything that's already playing. It allowed me to select a default action once, but I can't seem to change it. Thanks.
Thanks for the idea. This solves the problem of the xine engine not being set when it starts up. There's no way to disable the feature that changes engines automatically though? In the previous version this didn't seem to be an issue.
Is there a way to prevent amarok from switching output engines if the hardware for the one it's set to use isn't available? since the upgrade to amarok 1.4, this seems to happen automatically during startup if it can't find the hardware associated with the one it's currently looking for. Of course if the hardware isn't there the engine won't work so in a way it makes sense. Only, it ends up being a pain because if xine is configured to use my USB speakers but the speakers aren't actually plugged...
I know this is not exactly KDE software, but I imaging people who develop for KDE might know something about it. I'm trying to get eric3 (the Python IDE) running but so far all I get is a seg fault. I've got SuSE 9.3 w/ KDE 3.5.2, and all the bits and pieces they come with: Python 2.4, kdebindings3-python (what verison of PyQt comes with this?). Anyone seen this before or have any ideas? Thanks. Source code 1 2 sean@Iago:~> eric3 Segmentation fault debugger output: Source code 1 2 3 4 5 6 7 8 9 ...
Since upgrade to 3.5.1 (from 3.4), the 'Eject' option in the Konqueror right-click menu on a CD/DVD does not work. I get an error dialog saying that I need root permission to 'umount'. I can eject using 'eject' in a console (non-root). But then, for some reason, the cd won't auto-mount after that. I have to manually do it (and as root now). This was not the case before the upgrade. I've posted about this before but said that the actual eject button on the drive was now working. This seems to be ...
This has actually turned into more than just a nuisance. It's happened that for some reason (perhaps because it is hidden behind another window or on another desktop) the crashguard window is not visible. This hangs the shutdown process indefinitely and I have to do a hard power-off of the system. This can't be a valid change from 3.4 to 3.5. That doesn't make sense.
I've just upgraded to 3.5.1 on SuSE 9.3. Now if any app crashes during shutdown/logout and causes one of those crash windows to show, the logout waits until I click 'close' to proceed. This was not the case in 3.4 so I'm assuming there is simply some setting that I have to set to cause it to simply proceede (as it did in 3.4). Anyone have any thoughts on this? Also, since the upgrade, the 'Eject' option on a CD/DVD icon in Konqueror tells me I need root permission to 'umount' the device. This to...