Maybe rebuilding the database would help?

Emre

Hi,

Did you try deleting the kickerrc file?

/home/username/.kde/share/config/kickerrc

Emre

Can you give the output of the following command, after your printer is plugged in and turned on:

ls -la /dev/usb

Fastguy

Hi,

This was a decision taken at a time to exclude superuser programs from normal users. However, it created a lot of questions like the ones you had, so I think with the latest baselayout package, they made some change on this.

Fast

Hi,

you should write the command sequence you use to start your pppoe connection in file:

/etc/conf.d/local.start

this script runs the commands that you put inside at system bootup.

Fastguy

Hi,

I came a bit late to the topic but you can use the "network" command to start/stop a connection. Don't know if it would help you though. You can place your command in the local.stop file:

fastguy@voyager ~ $ network
usage: /bin/network <command> <arguments>
where command is:
 devices      List network devices
 connections  List connections
 info         List properties of a given connection
 create       Create a new connection
 delete       Delete a connection
 up           Connect given connection
 down         Disconnect given connection

Can you send the output of:

aplay -l

command? This will give us some info on your hardware. Pardus uses pulseaudio now by default, so maybe there's an issue on that, what does your Pulseaudio Volume Control show inside the Output Devices tab?

Fast

I think the best would be to contact developers, either by direct email or by sending a small post to the developers mailing list.

Fastguy