Running 20.04. Seems to me this bug appears only after I run Transmission Bit Torrent Client. My log files have shown that my kernel has been changed and after that I may lose wifi and lan connectivity. I have performed a fresh install of 20.04 numerous times to eliminate the problem and have run a fresh install for days without any problems until Transmission is run. Logs show that the my kernel was modified from root however I do not even know how to access root much less make changes to the kernel. I am wondering if there is some agency or entity that makes these changes as root to prevent torrenting, Below is copy of my warnings from logs.
10:12:38 PM dbus-daemon: [session uid=1000 pid=1610] Successfully activated service 'org.gnome.Logs'
9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
9:07:50 PM systemd: tracker-store.service: Succeeded.
9:07:50 PM tracker-store: OK
9:07:20 PM systemd: Started Tracker metadata database store and lookup manager.
9:07:20 PM dbus-daemon: [session uid=1000 pid=1610] Successfully activated service 'org.freedesktop.Tracker1'
9:07:20 PM systemd: Starting Tracker metadata database store and lookup manager...
9:07:20 PM dbus-daemon: [session uid=1000 pid=1610] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.0' (uid=1000 pid=1607 comm="/usr/libexec/tracker-miner-fs " label="unconfined")
Below is copy of my logs with "kernel" in the search option.
This log show no unusual changes as noted from previous sessions requiring a fresh install with the possible exception of the first line of the above log, but I included it for reference.
Has anybody else noticed these warnings after torrenting?
Running 20.04. Seems to me this bug appears only after I run Transmission Bit Torrent Client. My log files have shown that my kernel has been changed and after that I may lose wifi and lan connectivity. I have performed a fresh install of 20.04 numerous times to eliminate the problem and have run a fresh install for days without any problems until Transmission is run. Logs show that the my kernel was modified from root however I do not even know how to access root much less make changes to the kernel. I am wondering if there is some agency or entity that makes these changes as root to prevent torrenting, Below is copy of my warnings from logs.
10:12:38 PM dbus-daemon: [session uid=1000 pid=1610] Successfully activated service 'org.gnome.Logs' store.service: Succeeded. p.Tracker1' freedesktop. Tracker1' unit='tracker- store.service' requested by ':1.0' (uid=1000 pid=1607 comm="/ usr/libexec/ tracker- miner-fs " label="unconfined")
9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
9:15:10 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
9:07:50 PM systemd: tracker-
9:07:50 PM tracker-store: OK
9:07:20 PM systemd: Started Tracker metadata database store and lookup manager.
9:07:20 PM dbus-daemon: [session uid=1000 pid=1610] Successfully activated service 'org.freedeskto
9:07:20 PM systemd: Starting Tracker metadata database store and lookup manager...
9:07:20 PM dbus-daemon: [session uid=1000 pid=1610] Activating via systemd: service name='org.
Below is copy of my logs with "kernel" in the search option.
8:42:53 PM kernel: perf: interrupt took too long (3942 > 3930), lowering kernel. perf_event_ max_sample_ rate to 50500 0x0/0x0/ 0x0) 2a1f0014cbc11f3 94a5a98020' /boot/vmlinuz- 5.4.0-39- generic root=/dev/ mapper/ vgubuntu- root ro quiet splash vt.handoff=7
6:59:33 PM kernel: snd_hda_codec_idt hdaudioC1D0: speaker_outs=0 (0x0/0x0/
6:59:33 PM kernel: [TTM] Zone kernel: Available graphics memory: 1746504 KiB
6:59:33 PM kernel: [drm] initializing kernel modesetting (SUMO 0x1002:0x9647 0x103C:0x169B 0x00).
6:59:27 PM kernel: Started udev Kernel Device Manager.
6:59:27 PM kernel: Starting udev Kernel Device Manager...
6:59:27 PM kernel: Finished Apply Kernel Variables.
6:59:27 PM kernel: Mounted Kernel Configuration File System.
6:59:27 PM kernel: Starting Apply Kernel Variables...
6:59:27 PM kernel: Mounting Kernel Configuration File System...
6:59:27 PM kernel: Finished Load Kernel Modules.
6:59:27 PM kernel: Mounted Kernel Trace File System.
6:59:27 PM kernel: Starting Remount Root and Kernel File Systems...
6:59:27 PM kernel: Mounting Kernel Trace File System...
6:59:27 PM kernel: Listening on udev Kernel Socket.
6:59:27 PM kernel: Freeing unused kernel image memory: 1192K
6:59:27 PM kernel: Write protecting the kernel read-only data: 22528k
6:59:27 PM kernel: Freeing unused kernel image memory: 2712K
6:59:27 PM kernel: Loaded X.509 cert 'Build time autogenerated kernel key: fc5d997396576c9
6:59:27 PM kernel: Memory: 3432580K/3648416K available (14339K kernel code, 2397K rwdata, 4952K rodata, 2712K init, 4992K bss, 215836K reserved, 0K cma-reserved)
6:59:27 PM kernel: Kernel command line: BOOT_IMAGE=
6:59:27 PM kernel: Booting paravirtualized kernel on bare hardware
6:59:27 PM kernel: KERNEL supported cpus:
This log show no unusual changes as noted from previous sessions requiring a fresh install with the possible exception of the first line of the above log, but I included it for reference.
Has anybody else noticed these warnings after torrenting?