On Thu, 31 May 2018 11:04:10 -0500
"Martin McCormick" wrote:
> You might search web archives and internet discussion
> groups to see if there is a replacement driver for the mouse
> which is a real shame since it used to work but that particular
> module doesn't work which is valuable info
Piotr wrote:
> See the new log file. But still it says that destination is null.
>
> What next to check?
your log is not complete
it was seeing before
dict entry(
string "ActiveState"
variant string "inactive"
)
dict entry(
string "SubSt
Piotr writes:
> dmesg gave me this (relevant lines when BT mouse was connected)
>
> [ 4218.671838] hid-generic 0005:0A5C:0001.0004: unknown main item tag 0x0
> [ 4218.676386] input: Bluetooth 3.0 Mouse as
> /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/bluetooth/hci0/hci0:3/0005:0A5C:0001.00
On Thu, 31 May 2018 14:58:59 +0200
deloptes wrote:
> you sure about init? ps -A | head -3
This is what I got.
user@localhost:~$ ps -A | head -3
PID TTY TIME CMD
1 ?00:00:01 init
2 ?00:00:00 kthreadd
> so what is the dbus-monitor output now
See the new log f
Piotr wrote:
>> ps -A | head -3
>> PID TTY TIME CMD
>> 1 ? 00:00:33 init
>> 2 ? 00:00:01 kthreadd
>
> OK, I booted as you suggested, but the mouse problem remains. Any other
> suggestions?
you sure about init? ps -A | head -3
so what is the dbus-monitor output now
regard
On Thu, May 31, 2018 at 02:00:10PM +0200, Piotr wrote:
> Was Jessie already using systemd by default?
Yes. Both on new installs and on upgrades from wheezy.
On Thu, 31 May 2018 12:10:13 +0200
deloptes wrote:
> You see all works fine until systemd gets in the game.
> As I refused to use systemd I can't help much, but this needs to be
> investigated
Was Jessie already using systemd by default? If "yes" then maybe this is not
the source of the problem
Piotr wrote:
>> dbus-monitor --system
>>
>> and switch mouse on/off to reconnect. Tell us what you see.
>
> I see the change was logged when I connected BT mouse (see
> dbus-monitor.log)
>
>
>> If mouse is
>> correctly discovered and selected by BT you have to look at higher level
>> - the X s
On Tue, 29 May 2018 22:55:51 +0200
deloptes wrote:
> dbus-monitor --system
>
> and switch mouse on/off to reconnect. Tell us what you see.
I see the change was logged when I connected BT mouse (see dbus-monitor.log)
> If mouse is
> correctly discovered and selected by BT you have to look at h
On Tue, 29 May 2018 12:01:20 -0500
"Martin McCormick" wrote:
> You might get some information from dmesg. dmesg lists
> all the electronic devices your system knows about when it booted
> up such as sound cards, disk controllers and network interfaces.
> Your computer should make note of
Piotr Martyniuk wrote:
> I am using USB dongle for blue-tooth connections. I can pair the mouse and
> connect to it. However moving a mouse and/or clicking has no effect
> (cursor stays where it was, clicks are not recognized).
No make model for mouse or BT device in your PC.
I don't know if blue
Piotr Martyniuk writes:
> Dear all,
>
> Recently I upgraded from Jessie to Stretch in order to be able to install
> new
> package versions.
> The upgrade seems to be successful (I did not have any errors in the
> process),
> but I noticed that the Blue tooth mouse is not working (it was workin
12 matches
Mail list logo
