Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #196198 > unrolled thread
| Started by | Piotr Martyniuk <zaxonxp45@gmail.com> |
|---|---|
| First post | 2018-05-29 16:00 +0200 |
| Last post | 2018-05-31 21:40 +0200 |
| Articles | 11 — 5 participants |
Back to article view | Back to linux.debian.user
Upgrade from Jessie to Stretch: Bluetooth mouse is not working. Piotr Martyniuk <zaxonxp45@gmail.com> - 2018-05-29 16:00 +0200
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working. "Martin McCormick" <martin.m@suddenlink.net> - 2018-05-29 19:10 +0200
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working. Piotr <zaxonxp45@gmail.com> - 2018-05-31 09:40 +0200
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working. "Martin McCormick" <martin.m@suddenlink.net> - 2018-05-31 18:10 +0200
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working. deloptes <deloptes@gmail.com> - 2018-05-29 23:00 +0200
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working. deloptes <deloptes@gmail.com> - 2018-05-31 12:20 +0200
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working. Piotr <zaxonxp45@gmail.com> - 2018-05-31 14:10 +0200
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working. Greg Wooledge <wooledg@eeg.ccf.org> - 2018-05-31 14:50 +0200
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working. deloptes <deloptes@gmail.com> - 2018-05-31 15:10 +0200
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working. Piotr <zaxonxp45@gmail.com> - 2018-05-31 15:30 +0200
Re: Upgrade from Jessie to Stretch: Bluetooth mouse is not working. deloptes <deloptes@gmail.com> - 2018-05-31 21:40 +0200
| From | Piotr Martyniuk <zaxonxp45@gmail.com> |
|---|---|
| Date | 2018-05-29 16:00 +0200 |
| Subject | Upgrade from Jessie to Stretch: Bluetooth mouse is not working. |
| Message-ID | <vUNkm-4vu-15@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
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 working fine in Jessie). 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). I would include more info (output from some commands, logs), however I am not sure what is relevant, so I would need some guidance in this. Kind regards, Piotr -- System Information: Debian Release: 9.4 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.9.0-6-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
[toc] | [next] | [standalone]
| From | "Martin McCormick" <martin.m@suddenlink.net> |
|---|---|
| Date | 2018-05-29 19:10 +0200 |
| Message-ID | <vUQie-6qU-17@gated-at.bofh.it> |
| In reply to | #196198 |
Piotr Martyniuk <zaxonxp45@gmail.com> 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 working > fine > in > Jessie). > > 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). > > I would include more info (output from some commands, logs), however I am > not > sure what is relevant, so I would need some guidance in this. > > Kind regards, > Piotr 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 the bluetooth interface and might even throw an error message if it doesn't like something about it. The mouse should pair with the bluetooth system on your computer and since your installation is an upgrade, this may be an indication of trouble with the module associated with the mouse. You can also see which modules your system loaded on boot by using the command lsmod At least this is true in a number of Linux versions. You don't even have to be root. wb5agz martin tmp $lsmod Module Size Used by binfmt_misc 20480 1 fuse 90112 1 ppdev 20480 0 dcdbas 16384 0 nouveau 1359872 1 pcspkr 16384 0 serio_raw 16384 0 evdev 20480 1 mxm_wmi 16384 1 nouveau snd_usb_audio 131072 0 wmi 16384 2 mxm_wmi,nouveau psmouse 118784 0 scsi_mod 180224 6 sd_mod,usb_storage,libata,uas,sr_mod,sg 3c59x 45056 0 mii 16384 1 3c59x usbcore 184320 12 usbhid,snd_usb_audio,usb_storage,ehci_hcd,ohci_pci,uhci_hcd,ftdi_sio,usbserial,snd_usbmidi_lib,uas,ohci_hcd,ehci_pci i2c_piix4 20480 0 usb_common 16384 1 usbcore floppy 57344 0 Those were just some of the 81 modules that popped up on the old Dell Dimension I am using, here. Notice the psmouse module. You'll hopefully have something comparable for the bluetooth mouse. It may not appear until you try to pair your mouse with bluetooth. Finally, there is a file in /etc called modules. Any module whose name appears on a line in that file will be loaded on boot. I used to have trouble on this system with sound from the built-in sound chip set on the mother board. It would usually be a no-show as sound card 0 and a usb sound card would intermittently show up as card 0. By using /etc/modules to load the sound module for the built-in card, it is always card 0. Use that feature carefully since modules you don't actually need just waste resources. That should get you started with an afternoon of head-scratching/banging as these things can be frustrating so patience is a virtue. Martin McCormick WB5AGZ since October 1969 Alive since 1951.
[toc] | [prev] | [next] | [standalone]
| From | Piotr <zaxonxp45@gmail.com> |
|---|---|
| Date | 2018-05-31 09:40 +0200 |
| Message-ID | <vVqlH-2hi-7@gated-at.bofh.it> |
| In reply to | #196206 |
On Tue, 29 May 2018 12:01:20 -0500 "Martin McCormick" <martin.m@suddenlink.net> 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 the bluetooth interface and > might even throw an error message if it doesn't like something > about it. The mouse should pair with the bluetooth system on > your computer and since your installation is an upgrade, this may > be an indication of trouble with the module associated with the > mouse. 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/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/bluetooth/hci0/hci0:3/0005:0A5C:0001.0004/input/input21 [ 4218.679232] hid-generic 0005:0A5C:0001.0004: input,hidraw1: BLUETOOTH HID v1.29 Mouse [Bluetooth 3.0 Mouse] on 00:15:83:0c:bf:eb [ 4245.882600] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 4245.885751] input: Bluetooth 3.0 Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/bluetooth/hci0/hci0:4/0005:0A5C:0001.0005/input/input22 [ 4245.887779] hid-generic 0005:0A5C:0001.0005: input,hidraw1: BLUETOOTH HID v1.29 Mouse [Bluetooth 3.0 Mouse] on 00:15:83:0c:bf:eb [ 4276.111082] hid-generic 0005:0A5C:0001.0006: unknown main item tag 0x0 [ 4276.115032] input: Bluetooth 3.0 Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/bluetooth/hci0/hci0:5/0005:0A5C:0001.0006/input/input23 [ 4276.118450] hid-generic 0005:0A5C:0001.0006: input,hidraw1: BLUETOOTH HID v1.29 Mouse [Bluetooth 3.0 Mouse] on 00:15:83:0c:bf:eb But I do not know what should I do with this. > > You can also see which modules your system loaded on boot > by using the command > > lsmod Module Size Used by hidp 24576 0 hid_generic 16384 0 usbhid 45056 0 hid 94208 3 hid_generic,usbhid,hidp rfcomm 53248 12 ctr 16384 4 ccm 20480 2 fuse 90112 5 l2tp_ppp 24576 0 l2tp_netlink 20480 1 l2tp_ppp l2tp_core 24576 2 l2tp_ppp,l2tp_netlink ip6_udp_tunnel 16384 1 l2tp_core udp_tunnel 16384 1 l2tp_core pppox 16384 1 l2tp_ppp ppp_generic 32768 2 l2tp_ppp,pppox slhc 16384 1 ppp_generic vboxnetadp 32768 0 vboxnetflt 28672 0 xfrm_user 36864 2 xfrm4_tunnel 16384 0 tunnel4 16384 1 xfrm4_tunnel ipcomp 16384 0 xfrm_ipcomp 16384 1 ipcomp esp4 20480 0 ah4 20480 0 af_key 36864 0 xfrm_algo 16384 5 xfrm_user,esp4,ah4,af_key,xfrm_ipcomp vboxdrv 303104 2 vboxnetadp,vboxnetflt bnep 20480 2 binfmt_misc 20480 1 iTCO_wdt 16384 0 iTCO_vendor_support 16384 1 iTCO_wdt uvcvideo 77824 0 videobuf2_vmalloc 16384 1 uvcvideo videobuf2_memops 16384 1 videobuf2_vmalloc videobuf2_v4l2 20480 1 uvcvideo videobuf2_core 36864 2 uvcvideo,videobuf2_v4l2 btusb 36864 0 btrtl 16384 1 btusb videodev 131072 3 uvcvideo,videobuf2_core,videobuf2_v4l2 btbcm 16384 1 btusb btintel 16384 1 btusb media 28672 2 uvcvideo,videodev arc4 16384 2 bluetooth 434176 40 btrtl,hidp,btintel,bnep,btbcm,rfcomm,btusb ath9k 90112 0 ath9k_common 32768 1 ath9k ath9k_hw 425984 2 ath9k,ath9k_common ath 24576 3 ath9k_hw,ath9k,ath9k_common mac80211 552960 1 ath9k samsung_laptop 20480 0 coretemp 16384 0 cfg80211 450560 4 mac80211,ath9k,ath,ath9k_common pcspkr 16384 0 joydev 20480 0 evdev 20480 22 rfkill 20480 7 bluetooth,samsung_laptop,cfg80211 serio_raw 16384 0 i915 1183744 3 snd_hda_codec_realtek 73728 1 lpc_ich 20480 0 snd_hda_codec_generic 65536 1 snd_hda_codec_realtek mfd_core 16384 1 lpc_ich snd_hda_intel 28672 3 sg 32768 0 rng_core 16384 0 snd_hda_codec 94208 3 snd_hda_intel,snd_hda_codec_generic,snd_hda_codec_realtek drm_kms_helper 114688 1 i915 snd_hda_core 57344 4 snd_hda_intel,snd_hda_codec,snd_hda_codec_generic,snd_hda_codec_realtek snd_hwdep 16384 1 snd_hda_codec battery 20480 0 drm 253952 5 i915,drm_kms_helper snd_pcm 86016 3 snd_hda_intel,snd_hda_codec,snd_hda_core snd_timer 28672 1 snd_pcm snd 57344 13 snd_hda_intel,snd_hwdep,snd_hda_codec,snd_timer,snd_hda_codec_generic,snd_hda_codec_realtek,snd_pcm soundcore 16384 1 snd i2c_algo_bit 16384 1 i915 shpchp 32768 0 ac 16384 0 video 36864 2 samsung_laptop,i915 acpi_cpufreq 20480 1 button 16384 1 i915 parport_pc 28672 0 sunrpc 249856 1 ppdev 20480 0 lp 20480 0 parport 40960 3 lp,parport_pc,ppdev ip_tables 20480 0 x_tables 20480 1 ip_tables autofs4 36864 2 ext4 499712 3 crc16 16384 2 bluetooth,ext4 jbd2 77824 1 ext4 crc32c_generic 16384 0 fscrypto 24576 1 ext4 ecb 16384 0 lrw 16384 0 ablk_helper 16384 0 cryptd 20480 1 ablk_helper aes_i586 20480 5 mbcache 16384 4 ext4 xts 16384 3 gf128mul 20480 2 lrw,xts algif_skcipher 20480 0 af_alg 16384 1 algif_skcipher dm_crypt 24576 1 dm_mod 94208 12 dm_crypt sd_mod 40960 3 ata_generic 16384 0 psmouse 118784 0 ata_piix 32768 2 i2c_i801 24576 0 i2c_smbus 16384 1 i2c_i801 libata 192512 2 ata_piix,ata_generic scsi_mod 180224 3 sd_mod,libata,sg uhci_hcd 40960 0 ehci_pci 16384 0 ehci_hcd 65536 1 ehci_pci usbcore 184320 6 uvcvideo,usbhid,ehci_hcd,uhci_hcd,btusb,ehci_pci usb_common 16384 1 usbcore r8169 77824 0 mii 16384 1 r8169 fan 16384 0 thermal 20480 0 > > Notice the psmouse module. You'll hopefully have something > comparable for the bluetooth mouse. It may not appear until you > try to pair your mouse with bluetooth. I redirected lsmod when there was no BT mouse connection to file 1 and when it was connected to file 2. The "diff 1 2" gave this: user@localhost:~$ diff 1 2 2c2 < hidp 24576 0 --- > hidp 24576 1 46c46 < bluetooth 434176 40 btrtl,hidp,btintel,bnep,btbcm,rfcomm,btusb --- > bluetooth 434176 44 btrtl,hidp,btintel,bnep,btbcm,rfcomm,btusb 57c57 < evdev 20480 22 --- > evdev 20480 23 > Finally, there is a file in /etc called modules. Any > module whose name appears on a line in that file will be loaded > on boot. In my system the file only contains comments. > I used to have trouble on this system with sound from > the built-in sound chip set on the mother board. It would > usually be a no-show as sound card 0 and a usb sound card would > intermittently show up as card 0. By using /etc/modules to load > the sound module for the built-in card, it is always card 0. Should I add some module in my case to this file? > Use that feature carefully since modules you don't > actually need just waste resources. > > That should get you started with an afternoon of > head-scratching/banging as these things can be frustrating so > patience is a virtue. Patience I have. What I do not is the knowledge where to look and which dots to connect. Thanks for helping. Regards, Piotr
[toc] | [prev] | [next] | [standalone]
| From | "Martin McCormick" <martin.m@suddenlink.net> |
|---|---|
| Date | 2018-05-31 18:10 +0200 |
| Message-ID | <vVyjf-7jW-5@gated-at.bofh.it> |
| In reply to | #196281 |
Piotr <zaxonxp45@gmail.com> writes: > dmesg gave me this (relevant lines when BT mouse was connected) > > [ 4218.671838] hid-generic 0005:0A5C:0001.0004: unknown main item tag 0x 0 > [ 4218.676386] input: Bluetooth 3.0 Mouse as > /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/bluetooth/hci0/hci0:3/0005:0A5C:0001.0004/input/input21 > [ 4218.679232] hid-generic 0005:0A5C:0001.0004: input,hidraw1: BLUETOOTH > HID v1.29 Mouse [Bluetooth 3.0 Mouse] on 00:15:83:0c:bf:eb > [ 4245.882600] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x 0 > [ 4245.885751] input: Bluetooth 3.0 Mouse as > /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/bluetooth/hci0/hci0:4/0005:0A5C:0001.0005/input/input22 > [ 4245.887779] hid-generic 0005:0A5C:0001.0005: input,hidraw1: BLUETOOTH > HID v1.29 Mouse [Bluetooth 3.0 Mouse] on 00:15:83:0c:bf:eb > [ 4276.111082] hid-generic 0005:0A5C:0001.0006: unknown main item tag 0x 0 > [ 4276.115032] input: Bluetooth 3.0 Mouse as > /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/bluetooth/hci0/hci0:5/0005:0A5C:0001.0006/input/input23 > [ 4276.118450] hid-generic 0005:0A5C:0001.0006: input,hidraw1: > BLUETOOTH HID v1.29 Mouse [Bluetooth 3.0 Mouse] on 00:15:83:0c:bf:eb > > But I do not know what should I do with this. It is basically an accident report stating that this mouse won't work with that module. 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 information but not, of course, what you wanted to know. If you do find out that another kernel module or driver does exist, that is the time to use /etc/modules to load it first since the automatic detection is getting your the wrong one. I used to have an 8-port serial converter box with 8 RS-232 ports and a usb connector going to the computer. It needed a proprietary driver that the company did provide to Linux users for free but no kernel modules loaded at all when you connected the device without the driver. It worked fine until we had a gigantic electrical storm one day and all 8 ports went deaf and mute forever even though it appeared as though they were okay and just waiting to be connected to something. The replacement 8-port box loads kernel modules and works without any proprietary drivers. Can you get any other bluetooth device to pair and actually work with the dongle such as a headset or keyboard? There are a lot of moving parts here such as the usb driver for the dongle and then there is the communication between the bluetooth device and the dongle. dmesg and syslog are very good tools in cases like this but the messages you will read aren't always the answers to the question of why this or that is happening. They certainly do help you ask new questions and sometimes rule out rabbit holes you don't need to waste your time going down which is a blessing as the world of making the technology work for you is a regular warren of rabbit holes and anything that narrows down the solution is a force multiplier. One guess is that the driver for the bluetooth dongle is causing the grief because it sees events that it doesn't understand from the mouse. It should understand every mouse move and button press so they can be passed on to the appropriate function calls related to mouse activity. The OS has mouse function calls and the driver translates mouse movement data in to steps that are either along the X or Y axese. It doesn't have to do anything but feed those steps to the OS by making the appropriate function calls for movement and clicks. It apparently can't do that so you need a different driver. It might also be that another bluetooth mouse speaks a different language and the driver understands it and works properly so I hope this gives you more food for thought. I don't really know anything specific to your problem so I am speaking in generalities as I have seen a number of usb devices such as a usb apple modem that shows activity in syslog when you plug it in to a usb port but due to a lack of a driver, it does absolutely nothing under Linux but get slightly warm to the touch. Plug it in to a Mac and you're in to the dialup business. Martin McCormick
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2018-05-29 23:00 +0200 |
| Message-ID | <vUTSO-8kY-3@gated-at.bofh.it> |
| In reply to | #196198 |
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 bluetooth in jessie was bluez4 or bluez5. It could be that you are missing privileges. It all goes via dbus now. Use dbus-monitor --system and switch mouse on/off to reconnect. Tell us what you see. If mouse is correctly discovered and selected by BT you have to look at higher level - the X system. First check if you have events captured by X perhaps with xev IMO it is somewhere inbetween those two actors. regards
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2018-05-31 12:20 +0200 |
| Message-ID | <vVsQx-3Yn-3@gated-at.bofh.it> |
| In reply to | #196218 |
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 system.
>> First check if you have events captured by X perhaps with
>>
>> xev
>
> xev gives me nothing when I use the BT mouse.
>
> What next?
Excellent work Piotr.
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
>
path=/org/freedesktop/systemd1/unit/sys_2ddevices_2dpci0000_3a00_2d0000_3a00_3a1d_2e0_2dusb2_2d2_5cx2d1_2d2_5cx2d1_3a1_2e0_2dbluetooth_2dhci0_2dhci0_3a9_2edevice;
> interface=org.freedesktop.DBus.Properties; member=PropertiesChanged string
> "org.freedesktop.systemd1.Unit" array [
> dict entry(
> string "ActiveState"
> variant string "inactive"
> )
> dict entry(
> string "SubState"
> variant string "dead"
> )
Here you see sender=:1.0 -> destination=(null destination)
signal time=1527752498.410215 sender=:1.0 -> destination=(null destination)
serial=4147 path=/org/freedesktop/systemd1;
interface=org.freedesktop.systemd1.Manager; member=UnitRemoved
Can you try booting without systemd ? You need sysvinit and add
init=/lib/sysvinit/init to your kernal command line.
When system is up check
ps -A | head -3
PID TTY TIME CMD
1 ? 00:00:33 init
2 ? 00:00:01 kthreadd
Otherwise you should look for why systemd is not doing this right.
regards
[toc] | [prev] | [next] | [standalone]
| From | Piotr <zaxonxp45@gmail.com> |
|---|---|
| Date | 2018-05-31 14:10 +0200 |
| Message-ID | <vVuyZ-56p-1@gated-at.bofh.it> |
| In reply to | #196283 |
On Thu, 31 May 2018 12:10:13 +0200 deloptes <deloptes@gmail.com> 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 as the mouse was working correctly on Jessie? I connected another BT controller (chinese MOCUTE BT controller, which can be used as keypad or mouse) and it was working correctly. > Here you see sender=:1.0 -> destination=(null destination) > > signal time=1527752498.410215 sender=:1.0 -> destination=(null destination) > serial=4147 path=/org/freedesktop/systemd1; > interface=org.freedesktop.systemd1.Manager; member=UnitRemoved > > Can you try booting without systemd ? You need sysvinit and add > init=/lib/sysvinit/init to your kernal command line. > When system is up check > > 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? Regards, Piotr
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2018-05-31 14:50 +0200 |
| Message-ID | <vVvbH-5iL-1@gated-at.bofh.it> |
| In reply to | #196288 |
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.
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2018-05-31 15:10 +0200 |
| Message-ID | <vVvv3-5E9-3@gated-at.bofh.it> |
| In reply to | #196288 |
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 regards
[toc] | [prev] | [next] | [standalone]
| From | Piotr <zaxonxp45@gmail.com> |
|---|---|
| Date | 2018-05-31 15:30 +0200 |
| Message-ID | <vVvOp-5JX-3@gated-at.bofh.it> |
| In reply to | #196290 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, 31 May 2018 14:58:59 +0200
deloptes <deloptes@gmail.com> 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 file. But still it says that destination is null.
What next to check?
Regards,
Piotr
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2018-05-31 21:40 +0200 |
| Message-ID | <vVBAt-Ef-3@gated-at.bofh.it> |
| In reply to | #196291 |
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 "SubState" variant string "dead" )
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web