Welcome, Guest. Please login or register.
April 19, 2014, 20:31:10 PM
Home Help Search Calendar Login Register
Show unread posts since last visit.
News: Let Pardus-Anka become #1: Pardus-Anka Bug ReportPardus-Anka World Google+ | The Pardus wiki  | Visit Pardus-Anka official website  | Register as forum member?  Email the moderator!

+  Pardus Worldforum
|-+  Assistance
| |-+  Pardus for beginners
| | |-+  Bluetooth Mouse Toshiba
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: Bluetooth Mouse Toshiba  (Read 3098 times)
Maupy
Newbie
*
Gender: Male
Posts: 3


View Profile
« on: October 01, 2008, 21:11:41 PM »

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  Grin, 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
Logged
Mhmrcs
Global Moderator
Pardus Guru
*****
Gender: Male
Posts: 346



View Profile
« Reply #1 on: October 24, 2008, 02:12:57 AM »

Welcome to Pardus: Try installing the following 2 packages using the Package Manager [see screenshot].

A dbus error means the system is basically compromised, it is an integral part of your computer, if this is corrupted, it could be caused by a fault CD etc.


* bluetooth.jpg (272.48 KB, 1680x1050 - viewed 153 times.)
Logged

Pages: [1] Go Up Print 
« previous next »
Jump to:  


Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!