Hello,

I have installed Pardus 2008.1 and am working with it for about a week now. I am working on a Toshiba laptop (Tecra S5-12M).
Nearly all the hardware is up and running  , except my Bluetooth mouse (Toshiba N554).

When I start the KInputWizard it does not find the mouse at all. When I lauch the program from a terminal window the output shows:

arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1074.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_message_append_args_valist() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1521.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "message != NULL" failed in file dbus-connection.c line 3299.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_message_unref() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1391.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1074.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_message_append_args_valist() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1521.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "message != NULL" failed in file dbus-connection.c line 3299.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_message_unref() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1391.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1074.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_message_append_args_valist() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1521.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "message != NULL" failed in file dbus-connection.c line 3299.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_message_unref() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1391.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1074.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_message_append_args_valist() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1521.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "message != NULL" failed in file dbus-connection.c line 3299.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_message_unref() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1391.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1074.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_message_append_args_valist() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1521.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "message != NULL" failed in file dbus-connection.c line 3299.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_message_unref() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1391.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1074.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_message_append_args_valist() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1521.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "message != NULL" failed in file dbus-connection.c line 3299.
This is normally a bug in some application using the D-Bus library.
arguments to dbus_message_unref() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 1391.
This is normally a bug in some application using the D-Bus library.


Does anyone have an idea?

Please keep it basic, I am very new to Linux.

Kind Regards, Maupy

Thank's for your reply jnmbk.

I't worth the try.

Now on the avasys website their are 2 files. One ending on .rpm and one ending on .tar.gz

I searched the forum and have learned that Pardus does not use an rpm package manager but PiSi.

With this knowledge i downloaded the .tar.gz and unpacked these onto my harddisk.

Now i'm puzzling what to do, but first need a good night sleep (long day at work...)

Regards...

I am working with Pardus for a month now. Solved all problems i run into, untill now.

I have an "All in one printer" from Epson. Type:  Epson Stylus Photo RX560 and i can't get it to work (as far as my Linux knowledge is reaching)

I have tried the gutenprint stuff, from the packagemanager of Pardus. Then tried to configure it with Tasma, but this does not work properly.

I have searched over the internet and found a site called:  http://www.avasys.jp/english/linux_e/dl_spc.html

This is a website with specific drivers for Epson printers. According to the website my all in one device is supported.

Question: What steps do i need to take to install the driver from this website into Pardus?

I am using Pardus 2007.3

Please help me along,


Kind regards, Maupy