Re: /var/log/journal/ size question
* 2022-04-21 10:08:04+0800, Henrik S. wrote: > The dir /var/log/journal/ on my debian host increases quite quickly. > why this happens? Do you know how to suppress it? User can control log sizes with /etc/systemd/journald.conf file but systemd manages them automatically quite intelligently. Logs will not fill your hard disk. No need to worry. You can read about the log maintenance logic from journald.conf(5) manual page: man journald.conf -- /// Teemu Likonen - .-.. https://www.iki.fi/tlikonen/ // OpenPGP: 6965F03973F0D4CA22B9410F0F2CAE0E07608462 signature.asc Description: PGP signature
Re: /var/log/journal/ size question
On Thu, Apr 21 2022 at 10:08:04 AM, Henrik S wrote: > The dir /var/log/journal/ on my debian host increases quite quickly. > why this happens? Do you know how to suppress it? > That's the storage for the logs maintained by journald. You can manage these logs by editing /etc/systemd/journald.conf and setting one or more of SystemMaxUse/SystemKeepFree. See the journald.conf manpage for details. journald collects logs from both system service and user sessions; you may want to see if there is anything causing excessive log traffic. You can run "journalctl -f" (as root) to follow the logs as they are generated and see if there are repeated messages or errors that you could resolve. -- regards, kushal
/var/log/journal/ size question
The dir /var/log/journal/ on my debian host increases quite quickly. why this happens? Do you know how to suppress it? Thanks.
Re: Grub question
On Wed 20 Apr 2022 at 20:09:54 (+), Andrew M.A. Cater wrote: > On Wed, Apr 20, 2022 at 02:31:30PM -0500, Richard Owlett wrote: > > I have a machine set aside to test several configurations of Debian 11. > > > > Is there away to have the Grub Menu _automatically_ display the assigned > > partition name rather than than /dev/sdaN ? > > I wonder whether this changes if you use labels as references? I'm not sure quite what you mean by "as references". > To be honest, I never notice - it's a menu which says Debian and a couple > of other options and I jut hit [Enter] almost automatically :) If by "assigned partition name" the OP means either of LABEL or PARTLABEL, then I think the answer is no. Grub itself, of course, supports their use, but not the scripts that generate grub.cfg. If you allow grub-mkconfig to use UUIDs (the default), then it's relatively straightforward to script their conversion to LABELS, using the information in /run/udev/data/b* to build a conversion table. Just remember that you have to pair each change with the option names, --fs-uuid → --label. That probably falls outside the OP's definition of _automatically_ displaying them. Cheers, David.
Re: Debian 9 Xfce intermittent keyboard and mouse erratic behavior or lockup
On 4/20/22 14:40, Felix Miata wrote: David Christensen composed on 2022-04-20 14:14 (UTC-0700): Can you suggestion and commands to run that might provide clues? Other than switching between use of DDX display drivers (intel, nouveau) and DIX driver (modesetting, which supports: AMD, Intel, NVidia, other) to see if bad behavior persists, I have only one other possible suggestion: Older systems used only various specific input drivers, e.g.: xserver-xorg-input-kbd xserver-xorg-input-mouse xserver-xorg-input-evdev If these are installed, you might try removing them, thus having only the newer *libinput* drivers available for use. # dpkg -l | grep input-kbd # dpkg -l | grep xorg-input ii xserver-xorg-input-all 1:7.7+23 amd64 X.Org X server -- input driver metapackage ii xserver-xorg-input-libinput 1.2.1-1+b1 amd64 X.Org X server -- libinput input driver 2022-04-20 15:27:34 root@tinkywinky ~ # dpkg -l | grep input-kbd 2022-04-20 15:28:12 root@tinkywinky ~ # dpkg -l | grep xorg-input ii xserver-xorg-input-all1:7.7+19 amd64X.Org X server -- input driver metapackage ii xserver-xorg-input-libinput 0.23.0-2 amd64X.Org X server -- libinput input driver ii xserver-xorg-input-wacom 0.34.0-1 amd64X.Org X server -- Wacom input driver Any other commands? The rear USB 2.0 ports are down right now. Are there any commands I should run before rebooting (to test if the problem is hardware software)? David
Re: Problème de SMTP
On Tuesday 19 April 2022 16:54:03 Sébastien NOBILI wrote: > > smtp.bbox.fr me répond : > > "debian-user-french@lists.debian.org > > (Le serveur a répondu : «5.7.1 : > > Relay access denied») > > smtp.free.fr répond : > > Le serveur a répondu : « 5.7.1 Spam Detected - Mail Rejected. > > Please see our policy at: http://postmaster.free.fr/#spam_detected » > > n'existe pas. > > Faudrait savoir, "Relay access denied" ou "spam detected" ? > > Envoi d'un mail à debian-user-french@lists.debian.org est-il un spam ? > > Les deux réponses ne sont pas incompatibles puisqu'elles proviennent de > deux serveurs > différents. Ils ont bien le droit chacun de considérer ton message > invalide pour des > raisons différentes ;) (parce que leur configuration et les règles de > vérification > qu'ils appliquent ne sont pas les mêmes). > Par contre, ces deux messages différents sont intéressants (je pense) : > - ça a commencé à dysfonctionner au même moment avec deux opérateurs > différents >- l'un considère que ton message est du spam, l'autre que tu tentes > de relayer un message douteux > Il doit donc y avoir un élément commun qui explique ces deux > comportements. Je vois > deux possibilités (mais il peut y en avoir d'autres) : > - la conf relative à l'authentification sur le SMTP a sauté > (complètement, car si c'était juste le mot de passe ou le login, tu aurais un > autre > message d'erreur) >- l'adresse "From" ne plaît pas; > Tu devrais vérifier si ces deux éléments sont toujours correctement > configurés dans ton MUA. Merci pour ta réponse. Mon MUA Kmail est correctement configuré, j'ai tout vérifié. Pareil avec Thunderbird et Evolution. Je ne vois pas en quoi un mail anodin envoyé avec From : To : (même domaine), peut-il être considéré comme "douteux", non délivré car renvoyé comme un spam ? Maintenant TOUS mes mails adressés à un correspond...@free.fr, quelquesoit le SMTP utilisé, est considéré comme un spam ! J'ai suivi la méthode de Free pour déspamiser mes mails @free.fr sur cette page : http://postmaster.free.fr/#spam_detected postmas...@proxad.net ça ne fonctionne pas du tout. Voilà le topo et c'est bien ennuyeux pour moi. ajh.Valmer
Re: Debian 9 Xfce intermittent keyboard and mouse erratic behavior or lockup
David Christensen composed on 2022-04-20 14:14 (UTC-0700): > Felix Miata wrote: >> There are two different technologies for X display drivers. >> xserver-xorg-video-intel uses the older, DDX. It hasn't had an official >> release in >> nearly a decade. Unofficially it's in maintenance mode. The newer technology >> driver, modesetting DIX, is provided by the same package that provides the >> Xorg >> server, so cannot be removed independently of the server. The 945GM is the >> among >> the newest Intel IGPs not supported by the newer driver. By removing >> xserver-xorg-video-intel, the newer DIX display driver should automatically >> be >> utilized by your i7's IGP. It may be worth trying to solve your issue, if >> indeed >> you're not already running the DIX on your i7. > Can you suggestion and commands to run that might provide clues? Other than switching between use of DDX display drivers (intel, nouveau) and DIX driver (modesetting, which supports: AMD, Intel, NVidia, other) to see if bad behavior persists, I have only one other possible suggestion: Older systems used only various specific input drivers, e.g.: xserver-xorg-input-kbd xserver-xorg-input-mouse xserver-xorg-input-evdev If these are installed, you might try removing them, thus having only the newer *libinput* drivers available for use. # dpkg -l | grep input-kbd # dpkg -l | grep xorg-input ii xserver-xorg-input-all 1:7.7+23 amd64 X.Org X server -- input driver metapackage ii xserver-xorg-input-libinput 1.2.1-1+b1 amd64 X.Org X server -- libinput input driver -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Re: Debian 9 Xfce intermittent keyboard and mouse erratic behavior or lockup
On 4/20/22 11:23, Felix Miata wrote: David Christensen composed on 2022-04-20 10:31 (UTC-0700): 1. Dell Inspiron E1505, Intel Core 2 Duo T7400 processor, Intel GM 945 chipset (Intel® 82945GM Graphics and Memory Controller). I believe Debian uses the xserver-xorg-video-intel driver. 3. Desktop with Intel DQ67SW motherboard, Intel i7-2600S processor with Intel HD Graphics 2000. I believe Debian uses the xserver-xorg-video-intel driver. There are two different technologies for X display drivers. xserver-xorg-video-intel uses the older, DDX. It hasn't had an official release in nearly a decade. Unofficially it's in maintenance mode. The newer technology driver, modesetting DIX, is provided by the same package that provides the Xorg server, so cannot be removed independently of the server. The 945GM is the among the newest Intel IGPs not supported by the newer driver. By removing xserver-xorg-video-intel, the newer DIX display driver should automatically be utilized by your i7's IGP. It may be worth trying to solve your issue, if indeed you're not already running the DIX on your i7. Can you suggestion and commands to run that might provide clues? David
Re: system freeze
mick crane composed on 2022-04-20 20:58 (UTC+0100): > $ inxi -SGayz > Graphics: >Device-1: AMD Pitcairn LE GL [FirePro W5000] vendor: Dell driver: radeon > v: kernel alternate: amdgpu pcie: gen: 3 speed: 8 GT/s lanes: 16 ports: > active: DP-1 empty: DP-2,DVI-I-1 bus-ID: 03:00.0 chip-ID: 1002:6809 > class-ID: 0300 >Display: x11 server: X.Org v: 1.21.1.3 compositor: xfwm v: 4.16.1 driver: > X: loaded: radeon unloaded: fbdev,modesetting,vesa gpu: radeon > display-ID: :0.0 screens: 1 You left out the S part of inxi -SGayz, so we don't see the kernel parameters to confirm whether radeon.si_support=0 amdgpu.si_support=1 was in effect on the current boot. > Is there some syntax error. Do I need this > MatchDriver "amdgpu" > and > Identifier "DefaultDevice" IIRC I've only ever used it without the MatchDriver line, which is a test, I think of the loaded kernel GPU device driver. # egrep -B2 -A2 'amd|modes' /etc/X11/xorg.conf.d/*.conf /etc/X11/xorg.conf.d/15-ddxdrv.conf-Section "Device" /etc/X11/xorg.conf.d/15-ddxdrv.conf- Identifier "DDX" /etc/X11/xorg.conf.d/15-ddxdrv.conf:# MatchDriver "amdgpu" /etc/X11/xorg.conf.d/15-ddxdrv.conf:# Driver "amdgpu" /etc/X11/xorg.conf.d/15-ddxdrv.conf-# MatchDriver "intel" /etc/X11/xorg.conf.d/15-ddxdrv.conf-# Driver "intel" /etc/X11/xorg.conf.d/15-ddxdrv.conf:# MatchDriver "modesetting" /etc/X11/xorg.conf.d/15-ddxdrv.conf:Driver "modesetting" /etc/X11/xorg.conf.d/15-ddxdrv.conf-# MatchDriver "nouveau" /etc/X11/xorg.conf.d/15-ddxdrv.conf-# Driver "nouveau" # inxi -SGayz --display :0 System: Kernel: 5.16.0-4-amd64 x86_64 bits: 64 compiler: gcc v: 11.2.0 parameters: ro root=LABEL= net.ifnames=0 ipv6.disable=1 noresume mitigations=auto consoleblank=0 plymouth.enable=0 radeon.si_support=0 amdgpu.si_support=1 vga=791 video=1600x900@60 5 Console: pty pts/0 DM: TDM Distro: Debian GNU/Linux bookworm/sid Graphics: Device-1: AMD Oland [Radeon HD 8570 / R5 430 OEM R7 240/340 Radeon 520 OEM] vendor: Dell driver: amdgpu v: kernel alternate: radeon pcie: gen: 1 speed: 2.5 GT/s lanes: 8 link-max: gen: 3 speed: 8 GT/s ports: active: DP-1 empty: DVI-I-1 bus-ID: 01:00.0 chip-ID: 1002:6611 class-ID: 0300 Display: server: X.org v: 1.21.1.3 driver: X: loaded: modesetting gpu: amdgpu display-ID: 00srv.ij.net:0 tty: 189x50 Monitor-1: DP-1 model: Acer K272HUL serial: built: 2018 res: 2560x1440 dpi: 109 gamma: 1.2 size: 598x336mm (23.5x13.2") diag: 686mm (27") ratio: 16:9 modes: max: 2560x1440 min: 720x400 Message: GL data unavailable in console for root. # egrep -i 'amdgpu|modeset' /var/log/Xorg.0.log | wc -l 395 # egrep -i 'amdgpu|modeset' /var/log/Xorg.0.log | tail -n6 [ 171.448] (II) modeset(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e) [ 171.448] (II) modeset(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) [ 171.448] (II) modeset(0): Modeline "1280x800"x0.0 83.50 1280 1352 1480 1680 800 803 809 831 -hsync +vsync (49.7 kHz e) [ 171.448] (II) modeset(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e) [ 171.448] (II) modeset(0): Modeline "1680x1050"x0.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e) [ 171.467] (II) modeset(0): Disabling kernel dirty updates, not required. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Re: system freeze
mick crane writes: hello, I frequently have the system freeze on me and I have to unplug it. It seems to only happen in a browser and *appears* to be triggered by using the mouse. If watching streamed youtube movie or reading blogs sometimes the screen goes black and everything is unresponsive and sometimes the screen and everything freezes but the audio keeps playing. I'd like it to stop doing that. It didn't seem to be an issue a while ago but now is happening once at least per day with bullseye and now with bookworm. I cannot find anything in logs that have looked for except [...] What steps can I take to isolate the problem ? mick@pumpkin:~$ inxi -SGayz System: Kernel: 5.16.0-6-amd64 arch: x86_64 bits: 64 compiler: gcc v: 11.2.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.16.0-6-amd64 root=UUID=1b68069c-ec94-4f42-a35e-6a845008eac7 ro quiet Desktop: Xfce v: 4.16.0 tk: Gtk v: 3.24.24 info: xfce4-panel wm: xfwm v: 4.16.1 vt: 7 dm: LightDM v: 1.26.0 Distro: Debian GNU/Linux bookworm/sid Graphics: Device-1: AMD Pitcairn LE GL [FirePro W5000] vendor: Dell driver: radeon v: kernel alternate: amdgpu pcie: gen: 3 speed: 8 GT/s lanes: 16 ports: active: DP-1 empty: DP-2,DVI-I-1 bus-ID: 03:00.0 chip-ID: 1002:6809 class-ID: 0300 Display: x11 server: X.Org v: 1.21.1.3 compositor: xfwm v: 4.16.1 driver: X: loaded: radeon unloaded: fbdev,modesetting,vesa gpu: radeon display-ID: :0.0 screens: 1 Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.00x22.48") s-diag: 1165mm (45.88") Monitor-1: DP-1 mapped: DisplayPort-0 model: LG (GoldStar) HDR 4K serial: built: 2021 res: 3840x2160 hz: 60 dpi: 163 gamma: 1.2 size: 600x340mm (23.62x13.39") diag: 690mm (27.2") ratio: 16:9 modes: max: 3840x2160 min: 640x480 OpenGL: renderer: AMD PITCAIRN (DRM 2.50.0 5.16.0-6-amd64 LLVM 13.0.1) v: 4.5 Mesa 21.3.8 direct render: Yes [...] Hello, I think I had a very similar issue some months ago (Debian Bullseye). Back then I tried to switch to the proprietary AMD driver (?) and it seems to have helped although on my machine, the problem appeared at most once or twice a day back then. These were the symptoms I had observed: * Random conditions (but always GUI application usage) * Clock in i3bar hangs * X11 mouse cursor can still move * Shortly after the hang, screen turns black * At least one program continues to run despite the graphics output being "off" * SSH connection was not possible during this screen off state. In later instances, I also observed that the screen turned black temporarily and turned on after a shorter freeze again with the system becoming usable again. Here is my output for your inxi command: $ inxi -SGayz | cat System: Kernel: 5.10.0-13-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-13-amd64 root=UUID=5d6c37b4-341f-4aca-a9f7-2c8a0f39336a ro quiet Desktop: i3 4.19.1-non-git info: i3bar, docker dm: startx Distro: Debian GNU/Linux 11 (bullseye) Graphics: Device-1: AMD Navi 14 [Radeon Pro W5500] vendor: Dell driver: amdgpu v: 5.11.5.21.20 bus ID: :67:00.0 chip ID: 1002:7341 class ID: 0300 Display: server: X.Org 1.20.11 driver: loaded: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa display ID: :0 screens: 1 Screen-1: 0 s-res: 7680x1440 s-dpi: 96 s-size: 2032x381mm (80.0x15.0") s-diag: 2067mm (81.4") Monitor-1: DisplayPort-0 res: 1920x1080 hz: 60 dpi: 93 size: 527x296mm (20.7x11.7") diag: 604mm (23.8") Monitor-2: DisplayPort-1 res: 2560x1440 hz: 60 dpi: 109 size: 597x336mm (23.5x13.2") diag: 685mm (27") Monitor-3: DisplayPort-2 res: 1280x1024 hz: 60 dpi: 96 size: 338x270mm (13.3x10.6") diag: 433mm (17") Monitor-4: DisplayPort-3 res: 1920x1080 hz: 60 dpi: 85 size: 575x323mm (22.6x12.7") diag: 660mm (26") OpenGL: renderer: AMD Radeon Pro W5500 v: 4.6.14739 Core Profile Context FireGL 21.20 compat-v: 4.6.14739 direct render: Yes Back when the problem was still appearing, I could observe the following messages in syslog after reboot (sorry long lines...): Sep 18 13:11:36 masysma-18 kernel: [ 2045.986736] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, signaled seq=3179, emitted seq=3181 Sep 18 13:11:36 masysma-18 kernel: [ 2045.986935] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 Sep 18 13:11:36 masysma-18 kernel: [ 2045.986944] amdgpu :67:00.0: amdgpu: GPU reset begin! Sep 18 13:11:38 masysma-18 kernel: [ 2047.719111] amdgpu :67:00.0: amdgpu: failed send message: DisallowGfxOff (42) param: 0x response 0xffc2 Sep 18 13:11:38 masysma-18 kernel: [ 2047.719114] amdgpu :67:00.0: amdgpu: Failed to disable gfxoff! Sep 18 13:11:40 masysma-18 kernel: [ 2049.778328] amdgpu :67:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state! Sep 18 13:11:41 masysma-18 kernel: [ 2051.441397] amdgpu :67:00.0: amdgpu: Msg
Re: Grub question
On Wed, Apr 20, 2022 at 02:31:30PM -0500, Richard Owlett wrote: > I have a machine set aside to test several configurations of Debian 11. > > Is there away to have the Grub Menu _automatically_ display the assigned > partition name rather than than /dev/sdaN ? > I wonder whether this changes if you use labels as references? To be honest, I never notice - it's a menu which says Debian and a couple of other options and I jut hit [Enter] almost automatically :) All the very best, as ever, Andy Cater
Re: system freeze
On 2022-04-20 19:35, Felix Miata wrote: Section "Device" Identifier "DefaultDevice" Driver "amdgpu" EndSection I've changed /etc/default/grub #GRUB_CMDLINE_LINUX_DEFAULT="quiet" GRUB_CMDLINE_LINUX_DEFAULT="radeon.si_support=0 amdgpu.si_support=1" typed grub-mkconfig making file /etc/X11/xorg.conf.d/10-amdgpu.conf Section "Device" Identifier "DefaultDevice" Driver "amdgpu" EndSection On reboot there is message [failed]Failed to start Light Display Manager there is file /usr/share/X11/xorg.conf.d/10-amdgpu.conf Section "OutputClass" Identifier "AMDgpu" MatchDriver "amdgpu" Driver "amdgpu" EndSection putting that in /etc/X11/xorg.conf.d/10-amdgpu.conf X starts but driver doesn't seem to have changed? $ inxi -SGayz Graphics: Device-1: AMD Pitcairn LE GL [FirePro W5000] vendor: Dell driver: radeon v: kernel alternate: amdgpu pcie: gen: 3 speed: 8 GT/s lanes: 16 ports: active: DP-1 empty: DP-2,DVI-I-1 bus-ID: 03:00.0 chip-ID: 1002:6809 class-ID: 0300 Display: x11 server: X.Org v: 1.21.1.3 compositor: xfwm v: 4.16.1 driver: X: loaded: radeon unloaded: fbdev,modesetting,vesa gpu: radeon display-ID: :0.0 screens: 1 Is there some syntax error. Do I need this MatchDriver "amdgpu" and Identifier "DefaultDevice" cheers mick -- Key ID4BFEBB31
Grub question
I have a machine set aside to test several configurations of Debian 11. Is there away to have the Grub Menu _automatically_ display the assigned partition name rather than than /dev/sdaN ?
Re: system freeze
mick crane composed on 2022-04-20 19:14 (UTC+0100): >> radeon.si_support=0 amdgpu.si_support=1 > I added that to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub but I > can't see what to put in /boot/grub/grub.cfg because I'm not supposed to > edit it and grub-mkconfig is automagical. /boot/grub/grub.cfg is just a script that produces a boot menu. It can be edited, but edits don't necessarily survive regeneration via grub-mkconfig, which is the official way to incorporate changes to /etc/default/grub into /boot/grub/grub.cfg. >> Switching between the two Xorg drivers can be done via config file in >> /etc/X11/xorg.conf.d/ to specify either with a device line. > what does that device line look like ? Section "Device" Identifier "DefaultDevice" Driver "amdgpu" EndSection -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Re: Out of memory killer misconfigured?
On Wed 20 Apr 2022 at 18:45:47 (+0100), piorunz wrote:
> On 20/04/2022 17:11, Jonathan Dowland wrote:
> > On Wed, Apr 20, 2022 at 04:23:38PM +0100, piorunz wrote:
> > > Sorry but this happened to me a few times, each tome with the same Wine
> > > program. it just loves to eat all available memory when its doing heavy
> > > computations. When I am not careful and I start too many threads, is
> > > eats all memory. My system gets killed every single time. I am not
> > > extrapolating anything. Misbehaving app should get killed, but instead,
> > > Linux kills itself.
> >
> > Ok, not one experience, but one scenario. And there are plausible
> > reasons why this might be happening as outlined in my other mail to the
> > thread (OOM adjustments to make the killer skip over the process).
> > Occam's razor suggests something about your particular setup versus
> > the OOM killer simply being as bad as you think it is. FWIW, I invoke
> > the OOM killer a lot recently (due to some scientific experiments) and
> > the sensible processes were killed in my case, every time, leaving my
> > desktop functional.
> >
> > More data about your setup is needed to fathom out what's going on.
> >
> I didn't configured OOM. I use default Debian Testing with KDE. I
> changed nothing apart from user desktop things. MY situation is not "a
> scenario". It's what everyone can reproduce, just install Wine and
> MetaTester5 program, I can guide you. I cannot guarantee this will
> happen with non-Wine programs.
With respect, the combination of testing + KDE + Wine + MetaTester5
is difficult to categorise as more than one scenario.
> So I just reproduced this again, system crashed totally because I forgot
> to apply choom --adjust 1000 to all metatester processes. Reboot. After
> reboot, I started MT again and applied the following:
>
> renice 19 `pidof metatester64.ex`
> choom -p `pidof metatester64.ex | awk {'print $1'}` --adjust 1000
> choom -p `pidof metatester64.ex | awk {'print $2'}` --adjust 1000
> choom -p `pidof metatester64.ex | awk {'print $3'}` --adjust 1000
> choom -p `pidof metatester64.ex | awk {'print $4'}` --adjust 1000
> choom -p `pidof metatester64.ex | awk {'print $5'}` --adjust 1000
> choom -p `pidof metatester64.ex | awk {'print $6'}` --adjust 1000
> choom -p `pidof metatester64.ex | awk {'print $7'}` --adjust 1000
>
> I spawned more than 8 processes to saturate RAM quickly. Meaning, some
> processes were not adjusted to 1000 score. After 20 seconds, OOM event
> happened.
When I start my window manager, I use a construction like this:
if [ -x /usr/bin/fvwm ]; then
mv -f "$HOME/.xsession-fvwm-$Displaynumber-log"
"$HOME/.xsession-fvwm-$Displaynumber-log~"
exec /usr/bin/fvwm > "$HOME/.xsession-fvwm-$Displaynumber-log" 2>&1 &
Wmpid=$!
elif [ -x …
…
…
else
printf '%s\n' "Error - no window manager found"
fi
so that .xsession can avoid terminating with:
wait $Wmpid
Would it be sensible for you to use a similar construction so that you
systematically catch /all/ of these processes with their choom commands.
> And what Linux does? It has at least 8 processes with 1000 score, but
> let's see what is does:
>
> $ sudo dmesg | grep "Out of memory"
> [ 704.018238] Out of memory: Killed process 39674 (metatester64.ex)
> total-vm:2939256kB, anon-rss:250524kB, file-rss:0kB, shmem-rss:0kB,
> UID:1000 pgtables:1344kB oom_score_adj:1000
> [ 708.528663] Out of memory: Killed process 25882 (QtWebEngineProc)
> total-vm:5451920kB, anon-rss:20588kB, file-rss:0kB, shmem-rss:116kB,
> UID:1000 pgtables:772kB oom_score_adj:300
> [ 709.811945] Out of memory: Killed process 23411 (krunner-keepass)
> total-vm:52680kB, anon-rss:12860kB, file-rss:0kB, shmem-rss:0kB,
> UID:1000 pgtables:140kB oom_score_adj:200
> [ 710.788999] Out of memory: Killed process 23413 (pipewire-media-)
> total-vm:170052kB, anon-rss:9492kB, file-rss:0kB, shmem-rss:0kB,
> UID:1000 pgtables:248kB oom_score_adj:200
> [ 712.748691] Out of memory: Killed process 23618 (kactivitymanage)
> total-vm:550696kB, anon-rss:8848kB, file-rss:0kB, shmem-rss:0kB,
> UID:1000 pgtables:244kB oom_score_adj:200
> [ 714.856773] Out of memory: Killed process 23414 (pulseaudio)
> total-vm:1384772kB, anon-rss:8508kB, file-rss:0kB, shmem-rss:260kB,
> UID:1000 pgtables:320kB oom_score_adj:200
> [ 716.051274] Out of memory: Killed process 23560 (kglobalaccel5)
> total-vm:282368kB, anon-rss:6728kB, file-rss:0kB, shmem-rss:0kB,
> UID:1000 pgtables:256kB oom_score_adj:200
> [ 716.082495] Out of memory: Killed process 23412 (pipewire)
> total-vm:53124kB, anon-rss:4484kB, file-rss:0kB, shmem-rss:52kB,
> UID:1000 pgtables:104kB oom_score_adj:200
> [ 717.965930] Out of memory: Killed process 23867 (ksystemstats)
> total-vm:166540kB, anon-rss:3844kB, file-rss:0kB, shmem-rss:0kB,
> UID:1000 pgtables:176kB oom_score_adj:200
> [ 718.775772] Out of memory: Killed process 23703 (kscreen_backend)
> total-vm:227996kB, anon-rss:3060kB, file-rss:0kB,
Re: Debian 9 Xfce intermittent keyboard and mouse erratic behavior or lockup
David Christensen composed on 2022-04-20 10:31 (UTC-0700): > 1. Dell Inspiron E1505, Intel Core 2 Duo T7400 processor, Intel GM 945 > chipset (Intel® 82945GM Graphics and Memory Controller). I believe > Debian uses the xserver-xorg-video-intel driver. > 3. Desktop with Intel DQ67SW motherboard, Intel i7-2600S processor with > Intel HD Graphics 2000. I believe Debian uses the > xserver-xorg-video-intel driver. > > There are two different technologies for X display drivers. xserver-xorg-video-intel uses the older, DDX. It hasn't had an official release in nearly a decade. Unofficially it's in maintenance mode. The newer technology driver, modesetting DIX, is provided by the same package that provides the Xorg server, so cannot be removed independently of the server. The 945GM is the among the newest Intel IGPs not supported by the newer driver. By removing xserver-xorg-video-intel, the newer DIX display driver should automatically be utilized by your i7's IGP. It may be worth trying to solve your issue, if indeed you're not already running the DIX on your i7. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Re: system freeze
On 2022-04-20 17:34, Felix Miata wrote: mick crane composed on 2022-04-20 11:47 (UTC+0100): Graphics: Device-1: AMD Pitcairn LE GL [FirePro W5000] vendor: Dell driver: radeon v: kernel alternate: amdgpu pcie: gen: 3 speed: 8 GT/s lanes: 16 ports: active: DP-1 empty: DP-2,DVI-I-1 bus-ID: 03:00.0 chip-ID: 1002:6809 class-ID: 0300 Display: x11 server: X.Org v: 1.21.1.3 compositor: xfwm v: 4.16.1 driver: X: loaded: radeon unloaded: fbdev,modesetting,vesa gpu: radeon Your GPU has another driver option set. Currently you are using radeon kernel device driver with radeon DDX Xorg display driver. You may switch to the amdgpu kernel device driver, which supports both the amdgpu DDX display driver and the modesetting DIX display driver. To make the switch, append the following to the linu lines in /boot/grub/grub.cfg and GRUB_CMDLINE_LINUX_DEFAULT= in /etc/default/grub: radeon.si_support=0 amdgpu.si_support=1 I added that to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub but I can't see what to put in /boot/grub/grub.cfg because I'm not supposed to edit it and grub-mkconfig is automagical. Switching between the two Xorg drivers can be done via config file in /etc/X11/xorg.conf.d/ to specify either with a device line. what does that device line look like ? Because it's happening in web browser, I'm guessing GPU overheat is likely the cause. Taking the cover off the PC and aiming a large fan at the interior may be telling. Make sure the CPU fan, if present, is working, and the heat sink isn't loaded with accumulated dust and tobacco tar. If it is, then the PS would need cleaning too, as there it could cause voltage instability from overheating. It may be temperature, there was some dust and tobacco on the case fans but GPU heat sink is clean and fan spinning. I don't think this Dell Dimension PC will start up if the fans aren't working as when I got it one of the case fans wasn't working and I had to get a new unit. Have occasionally checked temperature with GUI sensor viewer but not caught it overheating GPU - 37C CPU - 40C cheers mick -- Key ID4BFEBB31
Re: Debian 9 Xfce intermittent keyboard and mouse erratic behavior or lockup
On 4/20/22 4:51 AM, songbird wrote: Dieter Rohlfing wrote: Am Wed, 20 Apr 2022 00:43:35 -0700 schrieb David Christensen : I have been experiencing intermittent storms of random keyboard and mouse GUI events over the past year or more: Same for me. System is Debian 9.13 (kernel 4.19.0-0.bpo.19-amd64, XFCE desktop) running on an ASRock DeskMini H110M. I'm running this combination with several hosts, but the storm only appears with the ASRock PC. Even with another mouse and keyboard the symptoms remain. So I think the storm mainly depends on the bare host and not on the peripheral components. At the moment I'm tinkering with the C-states. I disabled C6 and C7 in the BIOS and added the following options to the kernel command line: processor.max_cstate=3 intel_idle.max_cstate=3 Because the symptoms appear randomly, I can't say anything about a possible solution. I'll continue watching and will report, when I have any news. some things to look into. Mouse sensitivity in the desktop hardware settings. I have adjusted that in the past, and typically have it up fairly high, but I do not believe it is related to the keyboard/ mouse random GUI event storms. changing the batteries. I typically run the laptops with the AC adapter connected, and the desktop has a PSU. using different USB ports for the dongle. My keyboard and mouse are wired USB. One front USB 2.0 port works (I seem to recall the other died years ago). All four rear USB 2.0 ports are useless. Both rear USB 3.0 ports work. Now I'm starting to suspect the USB subsystem of X... replacing the keyboard or mouse. I seem to be running my last USB keyboard and USB mouse. David
Re: Out of memory killer misconfigured?
On 20/04/2022 17:11, Jonathan Dowland wrote:
On Wed, Apr 20, 2022 at 04:23:38PM +0100, piorunz wrote:
Sorry but this happened to me a few times, each tome with the same Wine
program. it just loves to eat all available memory when its doing heavy
computations. When I am not careful and I start too many threads, is
eats all memory. My system gets killed every single time. I am not
extrapolating anything. Misbehaving app should get killed, but instead,
Linux kills itself.
Ok, not one experience, but one scenario. And there are plausible
reasons why this might be happening as outlined in my other mail to the
thread (OOM adjustments to make the killer skip over the process).
Occam's razor suggests something about your particular setup versus
the OOM killer simply being as bad as you think it is. FWIW, I invoke
the OOM killer a lot recently (due to some scientific experiments) and
the sensible processes were killed in my case, every time, leaving my
desktop functional.
More data about your setup is needed to fathom out what's going on.
I didn't configured OOM. I use default Debian Testing with KDE. I
changed nothing apart from user desktop things. MY situation is not "a
scenario". It's what everyone can reproduce, just install Wine and
MetaTester5 program, I can guide you. I cannot guarantee this will
happen with non-Wine programs.
So I just reproduced this again, system crashed totally because I forgot
to apply choom --adjust 1000 to all metatester processes. Reboot. After
reboot, I started MT again and applied the following:
renice 19 `pidof metatester64.ex`
choom -p `pidof metatester64.ex | awk {'print $1'}` --adjust 1000
choom -p `pidof metatester64.ex | awk {'print $2'}` --adjust 1000
choom -p `pidof metatester64.ex | awk {'print $3'}` --adjust 1000
choom -p `pidof metatester64.ex | awk {'print $4'}` --adjust 1000
choom -p `pidof metatester64.ex | awk {'print $5'}` --adjust 1000
choom -p `pidof metatester64.ex | awk {'print $6'}` --adjust 1000
choom -p `pidof metatester64.ex | awk {'print $7'}` --adjust 1000
I spawned more than 8 processes to saturate RAM quickly. Meaning, some
processes were not adjusted to 1000 score. After 20 seconds, OOM event
happened.
And what Linux does? It has at least 8 processes with 1000 score, but
let's see what is does:
$ sudo dmesg | grep "Out of memory"
[ 704.018238] Out of memory: Killed process 39674 (metatester64.ex)
total-vm:2939256kB, anon-rss:250524kB, file-rss:0kB, shmem-rss:0kB,
UID:1000 pgtables:1344kB oom_score_adj:1000
[ 708.528663] Out of memory: Killed process 25882 (QtWebEngineProc)
total-vm:5451920kB, anon-rss:20588kB, file-rss:0kB, shmem-rss:116kB,
UID:1000 pgtables:772kB oom_score_adj:300
[ 709.811945] Out of memory: Killed process 23411 (krunner-keepass)
total-vm:52680kB, anon-rss:12860kB, file-rss:0kB, shmem-rss:0kB,
UID:1000 pgtables:140kB oom_score_adj:200
[ 710.788999] Out of memory: Killed process 23413 (pipewire-media-)
total-vm:170052kB, anon-rss:9492kB, file-rss:0kB, shmem-rss:0kB,
UID:1000 pgtables:248kB oom_score_adj:200
[ 712.748691] Out of memory: Killed process 23618 (kactivitymanage)
total-vm:550696kB, anon-rss:8848kB, file-rss:0kB, shmem-rss:0kB,
UID:1000 pgtables:244kB oom_score_adj:200
[ 714.856773] Out of memory: Killed process 23414 (pulseaudio)
total-vm:1384772kB, anon-rss:8508kB, file-rss:0kB, shmem-rss:260kB,
UID:1000 pgtables:320kB oom_score_adj:200
[ 716.051274] Out of memory: Killed process 23560 (kglobalaccel5)
total-vm:282368kB, anon-rss:6728kB, file-rss:0kB, shmem-rss:0kB,
UID:1000 pgtables:256kB oom_score_adj:200
[ 716.082495] Out of memory: Killed process 23412 (pipewire)
total-vm:53124kB, anon-rss:4484kB, file-rss:0kB, shmem-rss:52kB,
UID:1000 pgtables:104kB oom_score_adj:200
[ 717.965930] Out of memory: Killed process 23867 (ksystemstats)
total-vm:166540kB, anon-rss:3844kB, file-rss:0kB, shmem-rss:0kB,
UID:1000 pgtables:176kB oom_score_adj:200
[ 718.775772] Out of memory: Killed process 23703 (kscreen_backend)
total-vm:227996kB, anon-rss:3060kB, file-rss:0kB, shmem-rss:0kB,
UID:1000 pgtables:164kB oom_score_adj:200
[ 718.792339] Out of memory: Killed process 23417 (dbus-daemon)
total-vm:10552kB, anon-rss:1332kB, file-rss:0kB, shmem-rss:0kB, UID:1000
pgtables:60kB oom_score_adj:200
[ 719.422552] Out of memory: Killed process 23714 (obexd)
total-vm:45836kB, anon-rss:732kB, file-rss:0kB, shmem-rss:0kB, UID:1000
pgtables:76kB oom_score_adj:200
[ 719.423354] Out of memory: Killed process 23555 (dconf-service)
total-vm:157600kB, anon-rss:544kB, file-rss:0kB, shmem-rss:0kB, UID:1000
pgtables:64kB oom_score_adj:200
[ 719.424525] Out of memory: Killed process 23397 ((sd-pam))
total-vm:169688kB, anon-rss:3724kB, file-rss:0kB, shmem-rss:0kB,
UID:1000 pgtables:92kB oom_score_adj:100
[ 719.425356] Out of memory: Killed process 23396 (systemd)
total-vm:18600kB, anon-rss:1912kB, file-rss:0kB, shmem-rss:0kB, UID:1000
pgtables:76kB oom_score_adj:100
[ 719.426070] Out of memory: Killed process 55808
Re: Debian 9 Xfce intermittent keyboard and mouse erratic behavior or lockup
On 4/20/22 3:43 AM, Cindy Sue Causey wrote: On 4/20/22, Dieter Rohlfing wrote: Am Wed, 20 Apr 2022 00:43:35 -0700 schrieb David Christensen : I have been experiencing intermittent storms of random keyboard and mouse GUI events over the past year or more: Same for me. System is Debian 9.13 (kernel 4.19.0-0.bpo.19-amd64, XFCE desktop) running on an ASRock DeskMini H110M. I'm running this combination with several hosts, but the storm only appears with the ASRock PC. Even with another mouse and keyboard the symptoms remain. So I think the storm mainly depends on the bare host and not on the peripheral components. "Sticky keys", an accessibility feature, come to mind as needing to be ruled out. I've accidentally triggered mine multiple times over the last couple of years. To this day, I have no idea what combination of keys I'm hitting that does it. I'll just see a 2-second flash of an onscreen notification that they've been triggered on... again. At the moment I'm tinkering with the C-states. I disabled C6 and C7 in the BIOS and added the following options to the kernel command line: processor.max_cstate=3 intel_idle.max_cstate=3 Because the symptoms appear randomly, I can't say anything about a possible solution. I'll continue watching and will report, when I have any news. I've also occasionally experienced erratic behavior that's hardware caused by two different, unrelated instances. One has been that my laptop keys are, for example, worn out and/or overheating and "sticking" as though permanently depressed (being physically held down). The erratic appearance of this particular behavior will occur when I'm typing out posts or whatever and incidentally hit a declared hotkey that becomes triggered because e.g. the likewise declared CTRL key is physically stuck in the ON position. This scenario occurs because I have to buy old equipment that eventually overheats and causes things like the onboard keyboard to inevitably have a limited lifetime expectancy based meltdown. The secondary cause for seemingly erratic behavior is easier to fix. It's when the dogs or I are somehow leaning on any of my mouse's buttons. That will occur sometimes when I've set the mouse down to the side and am using a laptop's touchpad, instead. The mouse and the touchpad will end up conflicting with each other over which one has control of the situation. XFCE4 just coincidentally happens to be what I'm using for the above. My guess is that, since my situations are hardware based, they would likely occur regardless of what desktop environment happens to be in use at the time. Those sounds like different failure modes that what I posted, but I also get stuck keys and/or accidentally lean on keys intermittently. I will need to pay more attention to those failures. I have also read that multiple pointing devices -- mouse, touch pad, mouse button, etc. -- can fight each other for GUI input. I disabled everything except the mouse via Xfce, but the problems continued. David
Re: Debian 9 Xfce intermittent keyboard and mouse erratic behavior or lockup
On 4/20/22 2:23 AM, Dieter Rohlfing wrote: Am Wed, 20 Apr 2022 00:43:35 -0700 schrieb David Christensen : I have been experiencing intermittent storms of random keyboard and mouse GUI events over the past year or more: Same for me. System is Debian 9.13 (kernel 4.19.0-0.bpo.19-amd64, XFCE desktop) running on an ASRock DeskMini H110M. Thank you for the confirmation. STFW: https://www.asrock.com/microsite/DeskMini/#Specification It appears that platform supports Intel processors with integrated graphics: CPU Supports 7th and 6th Generation Intel® Core™ i7/i5/i3/Pentium®/Celeron® Processors (Socket 1151) (Max. TDP 65W) I have seen the keyboard and mouse issues on the following hardware: 1. Dell Inspiron E1505, Intel Core 2 Duo T7400 processor, Intel GM 945 chipset (Intel® 82945GM Graphics and Memory Controller). I believe Debian uses the xserver-xorg-video-intel driver. 2. Dell Latitude E6520, Intel Core i7-2720QM processor, Optimus graphics (Intel HD Graphics 3000 and NVIDIA NVS 4200M discrete graphics). I typically disable Optimus in the CMOS setup, which disables the Intel graphics. Debian uses the nouveau driver. 3. Desktop with Intel DQ67SW motherboard, Intel i7-2600S processor with Intel HD Graphics 2000. I believe Debian uses the xserver-xorg-video-intel driver. I'm running this combination with several hosts, but the storm only appears with the ASRock PC. Even with another mouse and keyboard the symptoms remain. So I think the storm mainly depends on the bare host and not on the peripheral components. My WAG is that a bug was introduced in the X Windows and/or desktop drivers 1~2 years ago on Debian 9, 10, and 11. At the moment I'm tinkering with the C-states. I disabled C6 and C7 in the BIOS and added the following options to the kernel command line: processor.max_cstate=3 intel_idle.max_cstate=3 Because the symptoms appear randomly, I can't say anything about a possible solution. I'll continue watching and will report, when I have any news. Please let us know if you make any progress. David
Re: system freeze
mick crane composed on 2022-04-20 11:47 (UTC+0100): > Graphics: >Device-1: AMD Pitcairn LE GL [FirePro W5000] vendor: Dell driver: > radeon > v: kernel alternate: amdgpu pcie: gen: 3 speed: 8 GT/s lanes: 16 > ports: > active: DP-1 empty: DP-2,DVI-I-1 bus-ID: 03:00.0 chip-ID: 1002:6809 > class-ID: 0300 >Display: x11 server: X.Org v: 1.21.1.3 compositor: xfwm v: 4.16.1 > driver: > X: loaded: radeon unloaded: fbdev,modesetting,vesa gpu: radeon > Your GPU has another driver option set. Currently you are using radeon kernel device driver with radeon DDX Xorg display driver. You may switch to the amdgpu kernel device driver, which supports both the amdgpu DDX display driver and the modesetting DIX display driver. To make the switch, append the following to the linu lines in /boot/grub/grub.cfg and GRUB_CMDLINE_LINUX_DEFAULT= in /etc/default/grub: radeon.si_support=0 amdgpu.si_support=1 Switching between the two Xorg drivers can be done via config file in /etc/X11/xorg.conf.d/ to specify either with a device line. Because it's happening in web browser, I'm guessing GPU overheat is likely the cause. Taking the cover off the PC and aiming a large fan at the interior may be telling. Make sure the CPU fan, if present, is working, and the heat sink isn't loaded with accumulated dust and tobacco tar. If it is, then the PS would need cleaning too, as there it could cause voltage instability from overheating. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Re: Out of memory killer misconfigured?
On Wed, Apr 20, 2022 at 04:23:38PM +0100, piorunz wrote: Sorry but this happened to me a few times, each tome with the same Wine program. it just loves to eat all available memory when its doing heavy computations. When I am not careful and I start too many threads, is eats all memory. My system gets killed every single time. I am not extrapolating anything. Misbehaving app should get killed, but instead, Linux kills itself. Ok, not one experience, but one scenario. And there are plausible reasons why this might be happening as outlined in my other mail to the thread (OOM adjustments to make the killer skip over the process). Occam's razor suggests something about your particular setup versus the OOM killer simply being as bad as you think it is. FWIW, I invoke the OOM killer a lot recently (due to some scientific experiments) and the sensible processes were killed in my case, every time, leaving my desktop functional. More data about your setup is needed to fathom out what's going on. -- Please do not CC me for listmail. Jonathan Dowland ✎j...@debian.org https://jmtd.net
Re: Out of memory killer misconfigured?
On 20/04/2022 11:28, Jonathan Dowland wrote: On Thu, Mar 31, 2022 at 05:53:20PM +0100, piorunz wrote: Well, nowadays oom killer is not so picky. It just kills (almost) EVERYTHING and then offending memory hungry process as a last, destroying entire work session. You are extrapolating from your single experience to make a generalisation that might not be true. Sorry but this happened to me a few times, each tome with the same Wine program. it just loves to eat all available memory when its doing heavy computations. When I am not careful and I start too many threads, is eats all memory. My system gets killed every single time. I am not extrapolating anything. Misbehaving app should get killed, but instead, Linux kills itself. -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
Re: Consulta / - SOLUCIONADO
El mié, 20 abr 2022 a las 15:17, Ricardo Delgado () escribió: > > > > > > El martes, 19 de abril de 2022 00:32:27 ART, Ariel Vechetti > escribió: > > > Buenas noches Ricado > Si es claro tu problema, y me ha pasado en algunos casos. Lo que he hecho es > utilizar un disco booteable con gparted que lo bajas de la página y > redimensionar las particiones, es decir achicar la partición /home y agrandas > las / > Espero que te sirva > Saludos. > > El lun, 18 abr 2022 a la(s) 21:56, Ricardo Delgado > (ricardodelgad...@yahoo.com.ar) escribió: > > Buenas noches, > > Una consulta de novato, la ultima instalacion realizada, tome la sugerencia > de particionado de DEBIAN > > entonces me genero / y /home como particiones separadas > > teniendo /dev/sda1 para / y /dev/sda6 para /home > > en / genere 30 gb, el tema surge porque los 30 gb se llenaron, luego para > limpiar realice un APT CLEAN y tambien borre LINUX-IMAGE viejos. > > Ahora tengo utilizado un 70% de la particion, pero quiero limpiar mas la > misma, y ahi surge la duda, duda de novato, QUE ARCHIVOS y/o CARPETAS podria > borrar o mover a /HOME, veo que tengo una carpeta /SNAP la cual tiene 7 gb, > no se si esta en / > Hola. Nunca he utilizado aplicaciones snap pero ese es el directorio donde se instalan. Todo lo que no esté debajo de /home estará en la partición de / (en tu caso) Lo verás ejecutando el comando "df" Dependiendo de como esté implementado snap, como root "podría" ser posible mover /snap a /home/snap y crear un enlace simbólico en / user@maquina:/# cd / user@maquina:/# mv snap /home user@maquina:/# ln -s /home/snap snap No te garantizo que funcione porque no lo he probado y el sistema puede requerir que no sea un enlace. Has de ser muy cuidadoso con los permisos. > y así para borrar/mover y liberar espacio de /, logicamente primero necesito > saber que tengo en / y luego que podría borrar o mover. > Mira a ver que tienes instalado con snap con "snap list" y si no lo necesitas elimínalo con "snap remove -paquete-". Podrías desinstalar paquetes de documentación si no los necesitas, algunos son muy grandes. Saludos. > Espero ser claro. y desde ya gracias! > > Slds > > > > -- > Vechetti Ariel > Ing. Sistemas de Información > > Ariel > > Muchas Gracias, era mi 2 opcion (sigue siendo); Camaleon, tome en cuenta tus > comentarios. Borre varios archivos viejos y libero (estoy a un 67%) si logro > mover SNAP estare muy holgado y tranquilo. > > Saludos
Re: what program sets up /run/user/1000/ ?
On Fri, 04 Jun 2021 14:35:47 +0200 "Thomas Schmitt" wrote: > Hi, > > songbird wrote: > > some strange fs entry shows up: > > # ls -l /run/user/1000 > > d? ? ? ??? doc > > We had this topic a few day ago. > https://lists.debian.org/debian-user/2021/06/msg00020.html > > I had some further private conversation with the OP John Conover which > causes me to summarize the problem like this: > > xdg-document-portal from package xdg-desktop-portal creates a FUSE > mount point as "portal" for offering selected files to the user with > the giveni id number (here: 1000). > > https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus-org.freedesktop.portal.Documents > states > "The document portal allows to make files from the outside world > available to sandboxed applications in a controlled way. > Exported files will be made accessible to the application via a fuse > filesystem that gets mounted at /run/user/$UID/doc/." > > Control is obviously to be done via systemd means. Probably by > /usr/lib/systemd/user/xdg-document-portal.service > as mentioned in > https://packages.debian.org/buster/amd64/xdg-desktop-portal/filelist > > It is the normal behavior of a FUSE mount point to deny any access to > any other user including the superuser. See > https://github.com/libfuse/libfuse > "Security implications" > which says > "No other user (including root) can access the contents of the > mounted filesystem (though this can be relaxed by allowing the use of > the allow_other and allow_root mount options in /etc/fuse.conf)" > > Reason is probably that the kernel hands over its internal VFS calls > to the FUSE driver program in userspace, which is then able to answer > with arbitrary deception to the caller of the corresponding libc > function. An old superuser might not expect to be served by code that > did not go through kernel development scrutiny. > > Relaxing this security precaution (as mentioned in above quote) might > be a bad idea. > I would rather disable xdg-document-portal in order to redice the risk > rather than increasing it. A bit of followup on this. I agree with Thomas that this is an increase in security risk. Most (all?) malware detectors that scan the entire computer run as root. E.g: chkrootkit. Second, there is more to disabling this nonsense. As the relevant user, run systemctl --user stop xdg-document-portal.service systemctl --user disable xdg-document-portal.service The disable line prevents the service from being started at reboot. Third, on March 1, I installed Bullseye on a laptop. That machine did not exhibit this problem. Perhaps the difference is in a more recent version of libfuse. The machines that exhibit the problem have: root@jhegaala:~# pre fuse fuse2.9.9-5 amd64 libfuse22.9.9-5 amd64 root@jhegaala:~# While the laptop that does not has: root@ideapc:~# pre fuse fuse3 3.10.3-2amd64 libfuse22.9.9-5 amd64 libfuse3-3 3.10.3-2amd64 root@ideapc:~# Or perhaps not. On the latter machine, /run/user/1000/ is present, but there is no directory doc in it: root@ideapc:~# ll /run/user/1000/ total 4 drwx-- 11 charles charles 280 Apr 16 16:42 ./ drwxr-xr-x 6 rootroot120 Apr 20 02:35 ../ srw-rw-rw- 1 charles charles 0 Apr 16 10:26 bus= drwx-- 3 charles charles 60 Apr 16 10:26 dbus-1/ drwx-- 2 charles charles 60 Apr 16 10:26 dconf/ drwx-- 2 charles charles 60 Apr 16 14:20 emacs/ drwx-- 2 charles charles 140 Apr 16 10:26 gnupg/ drwx-- 2 charles charles 40 Apr 16 10:26 gvfs/ -rw--- 1 charles charles 318 Apr 16 10:26 ICEauthority drwx-- 2 charles charles 60 Apr 16 10:26 keyring/ drwxr-xr-x 2 charles charles 60 Apr 16 10:26 Nextcloud/ srw-rw-rw- 1 charles charles 0 Apr 16 10:26 pk-debconf-socket= drwx-- 2 charles charles 100 Apr 19 11:31 pulse/ drwxr-xr-x 5 charles charles 140 Apr 16 10:26 systemd/ root@ideapc:~# As I have what I want (the service disabled), I have not experimented further. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: Consulta / - SOLUCIONADO
El martes, 19 de abril de 2022 00:32:27 ART, Ariel Vechetti escribió: Buenas noches Ricado Si es claro tu problema, y me ha pasado en algunos casos. Lo que he hecho es utilizar un disco booteable con gparted que lo bajas de la página y redimensionar las particiones, es decir achicar la partición /home y agrandas las / Espero que te sirva Saludos. El lun, 18 abr 2022 a la(s) 21:56, Ricardo Delgado (ricardodelgad...@yahoo.com.ar) escribió: Buenas noches, Una consulta de novato, la ultima instalacion realizada, tome la sugerencia de particionado de DEBIAN entonces me genero / y /home como particiones separadas teniendo /dev/sda1 para / y /dev/sda6 para /home en / genere 30 gb, el tema surge porque los 30 gb se llenaron, luego para limpiar realice un APT CLEAN y tambien borre LINUX-IMAGE viejos. Ahora tengo utilizado un 70% de la particion, pero quiero limpiar mas la misma, y ahi surge la duda, duda de novato, QUE ARCHIVOS y/o CARPETAS podria borrar o mover a /HOME, veo que tengo una carpeta /SNAP la cual tiene 7 gb, no se si esta en / y asi para borrar/mover y liberar espacio de /, logicamente primero necesito saber que tengo en / y luego que podria borrar o mover. Espero ser claro. y desde ya gracias! Slds -- Vechetti Ariel Ing. Sistemas de Información Ariel Muchas Gracias, era mi 2 opcion (sigue siendo); Camaleon, tome en cuenta tus comentarios. Borre varios archivos viejos y libero (estoy a un 67%) si logro mover SNAP estare muy holgado y tranquilo. Saludos
Re: install sur tablette
Appui long équivaudrait à Clic Droit? (Je n'utilise d'écran tactile qu'avec des smartphones Android.) Pour moi le tactile et le système clavier+souris ont chacun leurs spécificités et je pense qu'il n'est pas forcément opportun (quand on peut faire autrement, ce n'est pas forcément le cas) de chercher à utiliser une interface tactile comme on utiliserait une interface de saisie clavier+souris (un peu comme vouloir conserver le même mode de fonctionnement en GUI qu'on applique en CLI) Je connais donc mal la problématique tactile sous Linux mais de ma fenêtre j'ai l'impression qu'encore aujourd'hui, à part peut-être Plasma Mobile (et en plus vieux et moins sophistiqué Matchbox ou Sugar), Gnome, dans son fonctionnement principal c'est-à-dire ni "Classic" ni "Flashback", est l'environnement à privilégier car pensé pour du tactile, probablement autant au niveau de l'intefface générale du DE que de la majorité de ses applis. Et donc choisir (lorsque possible) des applis prévues pour le tactile Sous Android, je me suis rendu compte (ouais, je suis une bille, m'a fallu un moment pour m'en apercevoir) qu'un appui long du doigt sur une zone faisait apparaître un menu contextuel. Il y a quelques astuces ici: https://cours-informatique-gratuit.fr/cours/gestuelle-tactile-android/
Re: slrn broke after power failure
Charlie Gibbs wrote: > Thanks, everyone, for all your help. I think I might have found > the solution thanks to songbird: > > > then remove the zero length file and remove the .overview file > > for that group and see if you can then get that message again. > > i think a missing .overview file should be regenerated every time > > there is a new article downloaded. > > I didn't realize that there were hidden files in each group's > directory. Sure enough, I found files named .minimax, .overview, > and .servermin. Deleting .overview seems to correct the problem. > > Tim Woodall: my NNTPSERVER was OK. > > Again, thanks to everyone. you're welcome, sorry i didn't think of that sooner or make it more obvious. :) songbird
Re: Debian 9 Xfce intermittent keyboard and mouse erratic behavior or lockup
Dieter Rohlfing wrote: > Am Wed, 20 Apr 2022 00:43:35 -0700 > schrieb David Christensen : > >>I have been experiencing intermittent storms of random keyboard and >>mouse GUI events over the past year or more: > > Same for me. > > System is Debian 9.13 (kernel 4.19.0-0.bpo.19-amd64, XFCE desktop) running > on an ASRock DeskMini H110M. > > I'm running this combination with several hosts, but the storm only > appears with the ASRock PC. Even with another mouse and keyboard the > symptoms remain. So I think the storm mainly depends on the bare host and > not on the peripheral components. > > At the moment I'm tinkering with the C-states. I disabled C6 and C7 in the > BIOS and added the following options to the kernel command line: > >> processor.max_cstate=3 intel_idle.max_cstate=3 > > Because the symptoms appear randomly, I can't say anything about a > possible solution. I'll continue watching and will report, when I have any > news. some things to look into. Mouse sensitivity in the desktop hardware settings. changing the batteries. using different USB ports for the dongle. replacing the keyboard or mouse. it might be the case that your dongle is getting stray signals from some other device. if you have a lot if devices sending signals perhaps they're interferring with each other somehow. i've only had the mouse being run by a dongle and that has never had issues. instead i have issues with keyboards not lasting very long (but they are corded ones since i don't like the cordless types). songbird
Re: install sur tablette
On Wednesday 20 April 2022 13:36:48 hamster wrote: > Un copain me demande de lui installer linux sur une tablette. Pour vous > faire une idée du bidule, le mode d'emploi est la : > https://www.modes-d-emploi.com/manuals/795629/panasonic-toughbook-cf-d1.html?original=1 > C'est la première fois que j'installe sur un truc qui fonctionne > uniquement avec écran tactile. Je suis un peu déboussolé. Y'a pas de > souris, pas de clavier, juste un stylet qui clique quand on appuie et > qui est dépourvu de boutons. Je peux bien sur rajouter clavier et souris > externe en USB mais le but c'est d'utiliser le bidule en exterieur sur > un chantier, donc debout en se déplacant et sans se trimballer un > clavier et une souris. > Pour le clavier j'ai mis onboard, c'est pas pratique mais ca marche. > Pour la souris c'est très facile de cliquer, il suffit d'appuyer sur > l'écran avec le stylet ou meme avec le doigt, par contre je ne sais pas > faire un clic droit, ni un clic roulette, ni meme faire tourner la > roulette. J'ai essayé d'installer mousetweaks mais il refuse de marcher > en me disant qu'il a besoin d'etre sous X11. J'ai trouvé un rapport de > bug mentionnant que mousetweaks n'est plus supporté et devrait etre > supprimé. Mais je n'ai pas trouvé un autre paquet qui permette > d'utiliser un stylet comme une souris. > Si quelqu'un a des bons tuyaux je suis preneur. Bonne initiative. J'avais installé Debian sur un portable à écran tactile de bonne facture, mais il y a bien longtemps. Autant le tactile fonctionnait bien avec Windows-7 et modérément avec Linux. Je l'ai finalement donné à mon fils (qui préfèrait Windows, sniff et maintenant Mac). Sans doute que Linux a fait des progrès sur le plan du tactile ? Bonne journée, A. Valmer
install sur tablette
Salut. Un copain me demande de lui installer linux sur une tablette. Pour vous faire une idée du bidule, le mode d'emploi est la : https://www.modes-d-emploi.com/manuals/795629/panasonic-toughbook-cf-d1.html?original=1 C'est la première fois que j'installe sur un truc qui fonctionne uniquement avec écran tactile. Je suis un peu déboussolé. Y'a pas de souris, pas de clavier, juste un stylet qui clique quand on appuie et qui est dépourvu de boutons. Je peux bien sur rajouter clavier et souris externe en USB mais le but c'est d'utiliser le bidule en exterieur sur un chantier, donc debout en se déplacant et sans se trimballer un clavier et une souris. Pour le clavier j'ai mis onboard, c'est pas pratique mais ca marche. Pour la souris c'est très facile de cliquer, il suffit d'appuyer sur l'écran avec le stylet ou meme avec le doigt, par contre je ne sais pas faire un clic droit, ni un clic roulette, ni meme faire tourner la roulette. J'ai essayé d'installer mousetweaks mais il refuse de marcher en me disant qu'il a besoin d'etre sous X11. J'ai trouvé un rapport de bug mentionnant que mousetweaks n'est plus supporté et devrait etre supprimé. Mais je n'ai pas trouvé un autre paquet qui permette d'utiliser un stylet comme une souris. Si quelqu'un a des bons tuyaux je suis preneur. Merci d'avance.
Re: After upgrade to bullseye, tty1-6 not working
On Wed, Apr 20, 2022 at 12:27:09PM +0200, Christian Britz wrote: > Wild-eyed speculation: The tweaks are probably still present in > /etc/default/grub. Remove them to see if the problems are related. (And run update-grub after editing the file.)
system freeze
hello, I frequently have the system freeze on me and I have to unplug it. It seems to only happen in a browser and *appears* to be triggered by using the mouse. If watching streamed youtube movie or reading blogs sometimes the screen goes black and everything is unresponsive and sometimes the screen and everything freezes but the audio keeps playing. I'd like it to stop doing that. It didn't seem to be an issue a while ago but now is happening once at least per day with bullseye and now with bookworm. I cannot find anything in logs that have looked for except $ journalctl -e Apr 20 10:30:58 pumpkin pulseaudio[852]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) This may be that is just because I did have a bluetooth keyboard but it was so slow to wake up I changed to a usb keyboard and the bluetooth adapter is not there anymore and I should purge the bluetooth stuff. Is a wireless mouse whatever that is. I thought it might be the graphics card had gone defective but now I think it is something about the mouse It seems that the thing freezes before anything has a chance to write to a log. What steps can I take to isolate the problem ? mick@pumpkin:~$ inxi -SGayz System: Kernel: 5.16.0-6-amd64 arch: x86_64 bits: 64 compiler: gcc v: 11.2.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.16.0-6-amd64 root=UUID=1b68069c-ec94-4f42-a35e-6a845008eac7 ro quiet Desktop: Xfce v: 4.16.0 tk: Gtk v: 3.24.24 info: xfce4-panel wm: xfwm v: 4.16.1 vt: 7 dm: LightDM v: 1.26.0 Distro: Debian GNU/Linux bookworm/sid Graphics: Device-1: AMD Pitcairn LE GL [FirePro W5000] vendor: Dell driver: radeon v: kernel alternate: amdgpu pcie: gen: 3 speed: 8 GT/s lanes: 16 ports: active: DP-1 empty: DP-2,DVI-I-1 bus-ID: 03:00.0 chip-ID: 1002:6809 class-ID: 0300 Display: x11 server: X.Org v: 1.21.1.3 compositor: xfwm v: 4.16.1 driver: X: loaded: radeon unloaded: fbdev,modesetting,vesa gpu: radeon display-ID: :0.0 screens: 1 Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.00x22.48") s-diag: 1165mm (45.88") Monitor-1: DP-1 mapped: DisplayPort-0 model: LG (GoldStar) HDR 4K serial: built: 2021 res: 3840x2160 hz: 60 dpi: 163 gamma: 1.2 size: 600x340mm (23.62x13.39") diag: 690mm (27.2") ratio: 16:9 modes: max: 3840x2160 min: 640x480 OpenGL: renderer: AMD PITCAIRN (DRM 2.50.0 5.16.0-6-amd64 LLVM 13.0.1) v: 4.5 Mesa 21.3.8 direct render: Yes regards mick -- Key ID4BFEBB31
Re: Debian 9 Xfce intermittent keyboard and mouse erratic behavior or lockup
On 4/20/22, Dieter Rohlfing wrote: > Am Wed, 20 Apr 2022 00:43:35 -0700 > schrieb David Christensen : > >>I have been experiencing intermittent storms of random keyboard and >>mouse GUI events over the past year or more: > > Same for me. > > System is Debian 9.13 (kernel 4.19.0-0.bpo.19-amd64, XFCE desktop) running > on an ASRock DeskMini H110M. > > I'm running this combination with several hosts, but the storm only > appears with the ASRock PC. Even with another mouse and keyboard the > symptoms remain. So I think the storm mainly depends on the bare host and > not on the peripheral components. "Sticky keys", an accessibility feature, come to mind as needing to be ruled out. I've accidentally triggered mine multiple times over the last couple of years. To this day, I have no idea what combination of keys I'm hitting that does it. I'll just see a 2-second flash of an onscreen notification that they've been triggered on... again. > At the moment I'm tinkering with the C-states. I disabled C6 and C7 in the > BIOS and added the following options to the kernel command line: > >> processor.max_cstate=3 intel_idle.max_cstate=3 > > Because the symptoms appear randomly, I can't say anything about a > possible solution. I'll continue watching and will report, when I have any > news. I've also occasionally experienced erratic behavior that's hardware caused by two different, unrelated instances. One has been that my laptop keys are, for example, worn out and/or overheating and "sticking" as though permanently depressed (being physically held down). The erratic appearance of this particular behavior will occur when I'm typing out posts or whatever and incidentally hit a declared hotkey that becomes triggered because e.g. the likewise declared CTRL key is physically stuck in the ON position. This scenario occurs because I have to buy old equipment that eventually overheats and causes things like the onboard keyboard to inevitably have a limited lifetime expectancy based meltdown. The secondary cause for seemingly erratic behavior is easier to fix. It's when the dogs or I are somehow leaning on any of my mouse's buttons. That will occur sometimes when I've set the mouse down to the side and am using a laptop's touchpad, instead. The mouse and the touchpad will end up conflicting with each other over which one has control of the situation. XFCE4 just coincidentally happens to be what I'm using for the above. My guess is that, since my situations are hardware based, they would likely occur regardless of what desktop environment happens to be in use at the time. Cindy :) -- Talking Rock, Pickens County, Georgia, USA * runs with birdseed *
Re: Out of memory killer misconfigured?
On Thu, Mar 31, 2022 at 05:53:20PM +0100, piorunz wrote: Well, nowadays oom killer is not so picky. It just kills (almost) EVERYTHING and then offending memory hungry process as a last, destroying entire work session. You are extrapolating from your single experience to make a generalisation that might not be true. -- Please do not CC me for listmail. Jonathan Dowland ✎j...@debian.org https://jmtd.net
Re: After upgrade to bullseye, tty1-6 not working
Hello Hobie, On 2022-04-20 12:13 UTC+0200, hobie of RMN wrote: > Hi, Folks - > With buster, I had done some tweaking to the boot command line in order to > have a certain font size come up in the plain text console windows. > Should I suspect that's still present in grub and is for some reason > problematic under bullseye? Any tips, hints, suggestions, wild-eyed > speculations would be appreciated. :) Wild-eyed speculation: The tweaks are probably still present in /etc/default/grub. Remove them to see if the problems are related. -- http://www.cb-fraggle.de
Re: Out of memory killer misconfigured?
On Tue, Mar 29, 2022 at 10:34:19AM +0100, piorunz wrote:
Instead of killing ONE 7.5 million-worth pagetable process, Linux is
killing everything else! KDE activity manager killed. Then it goes on to
kill EVERYTHING in the system:
Perhaps your wine processes had their oom_adj (etc) values tweaked to
make the algorithm not consider them (/proc//oom_{adj,score,score_adj})?
I can imagine some ill-advised launcher script for windows software on
linux doing this.
--
Please do not CC me for listmail.
Jonathan Dowland
✎j...@debian.org
https://jmtd.net
After upgrade to bullseye, tty1-6 not working
Hi, Folks - On reboot after upgrading from buster to bullseye, my AOC monitor, connected via DVI, is showing "Input Not Support" on non-GUI tty1-tty6 - but, tty7 is successfully running the GUI (xfce4 in my case) and it shows up fine on that same monitor. With buster, I had done some tweaking to the boot command line in order to have a certain font size come up in the plain text console windows. Should I suspect that's still present in grub and is for some reason problematic under bullseye? Any tips, hints, suggestions, wild-eyed speculations would be appreciated. :) --hobie
Re: Debian 9 Xfce intermittent keyboard and mouse erratic behavior or lockup
Am Wed, 20 Apr 2022 00:43:35 -0700 schrieb David Christensen : >I have been experiencing intermittent storms of random keyboard and >mouse GUI events over the past year or more: Same for me. System is Debian 9.13 (kernel 4.19.0-0.bpo.19-amd64, XFCE desktop) running on an ASRock DeskMini H110M. I'm running this combination with several hosts, but the storm only appears with the ASRock PC. Even with another mouse and keyboard the symptoms remain. So I think the storm mainly depends on the bare host and not on the peripheral components. At the moment I'm tinkering with the C-states. I disabled C6 and C7 in the BIOS and added the following options to the kernel command line: > processor.max_cstate=3 intel_idle.max_cstate=3 Because the symptoms appear randomly, I can't say anything about a possible solution. I'll continue watching and will report, when I have any news. Dieter
Re: Debian 9 Xfce intermittent keyboard and mouse erratic behavior or lockup
On 4/20/22 12:43 AM, David Christensen wrote: debian-user: I have an SSD with Debian: 2022-04-19 23:24:11 dpchrist@tinkywinky ~ $ cat /etc/debian_version ; uname -a 9.13 Linux tinkywinky 4.9.0-18-amd64 #1 SMP Debian 4.9.303-1 (2022-03-07) x86_64 GNU/Linux I have been experiencing intermittent storms of random keyboard and mouse GUI events over the past year or more: a. Windows are opened, closed, minimized, resized, etc.. b. Windows and/or desktop pop-up menus are opened, and random items are activated. c. Text that I have previously typed is pasted into random windows. d. Sometimes the mouse is left in a desktop rectangular selection mode (?). The storms are triggered when I move the mouse in an active window. A storm consists of dozens of individual random GUI events per second. The storms typically end when I stop moving the mouse. The next time I move the mouse, another storm may start or may not. I typically reboot if there is more than one storm. Firefox (on heavy JavaScript sites) and FreeCiv are applications that are likely to trigger storms. Alternatively, instead of a GUI random event storm, the keyboard and mouse lock up. Disconnecting and reconnecting the keyboard and mouse has no effect; the only cure is to reboot. I have tried various measures to isolate the problem, to no avail: 1. Power cycling and/or bypassing the KVM switch. 2. Moving the OS disk into another machine with different hardware. 3. Installing Debian 10 on another SSD and testing. Same for Debian 11. Is anyone else seeing these GUI event storms? I was enjoying a game of FreeCiv this evening on a desktop computer with the KVM switch connected, and a storm occurred. I shut down, connected the keyboard and mouse directly to the computer, and resumed my game. Perhaps an hour later, the keyboard and mouse locked up. If I login from another machine via SSH, disconnect the keyboard, count to 10, and reconnect the keyboard: 2022-04-20 00:22:52 root@tinkywinky /var/log # tail -n 17 messages Apr 20 00:21:40 tinkywinky kernel: [18629.457897] usb 3-1.5: USB disconnect, device number 9 Apr 20 00:21:50 tinkywinky kernel: [18640.176348] usb 3-1.5: new low-speed USB device number 11 using ehci-pci Apr 20 00:21:50 tinkywinky kernel: [18640.314951] usb 3-1.5: New USB device found, idVendor=04d9, idProduct=a0b9 Apr 20 00:21:50 tinkywinky kernel: [18640.314957] usb 3-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Apr 20 00:21:50 tinkywinky kernel: [18640.314961] usb 3-1.5: Product: ES-87 Apr 20 00:21:50 tinkywinky kernel: [18640.314963] usb 3-1.5: Manufacturer: Keyed Up Labs Apr 20 00:21:50 tinkywinky kernel: [18640.329387] input: Keyed Up Labs ES-87 as /devices/pci:00/:00:1a.0/usb3/3-1/3-1.5/3-1.5:1.0/0003:04D9:A0B9.000C/input/input23 Apr 20 00:21:50 tinkywinky kernel: [18640.388751] hid-generic 0003:04D9:A0B9.000C: input,hidraw0: USB HID v1.10 Keyboard [Keyed Up Labs ES-87] on usb-:00:1a.0-1.5/input0 Apr 20 00:21:50 tinkywinky kernel: [18640.408155] input: Keyed Up Labs ES-87 as /devices/pci:00/:00:1a.0/usb3/3-1/3-1.5/3-1.5:1.1/0003:04D9:A0B9.000D/input/input24 Apr 20 00:21:51 tinkywinky kernel: [18640.464649] hid-generic 0003:04D9:A0B9.000D: input,hidraw1: USB HID v1.10 Device [Keyed Up Labs ES-87] on usb-:00:1a.0-1.5/input1 Apr 20 00:21:51 tinkywinky mtp-probe: checking bus 3, device 11: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.5" Apr 20 00:21:51 tinkywinky mtp-probe: bus: 3, device: 11 was not an MTP device Apr 20 00:21:51 tinkywinky org.xfce.FileManager[1155]: thunar-volman: Unsupported USB device type "usb". Apr 20 00:21:51 tinkywinky org.xfce.FileManager[1155]: thunar-volman: Unsupported input device type "/dev/input/event1". Apr 20 00:21:51 tinkywinky org.xfce.FileManager[1155]: thunar-volman: Unsupported input device type "(null)". Apr 20 00:21:51 tinkywinky org.xfce.FileManager[1155]: thunar-volman: Unsupported USB device type "usbhid". Apr 20 00:21:51 tinkywinky org.xfce.FileManager[1155]: thunar-volman: Unsupported USB device type "usbhid". If I cycle the mouse: 2022-04-20 00:24:36 root@tinkywinky /var/log # tail -n 13 messages Apr 20 00:24:00 tinkywinky kernel: [18769.493620] usb 3-1.6: USB disconnect, device number 10 Apr 20 00:24:13 tinkywinky kernel: [18782.515065] usb 3-1.6: new low-speed USB device number 12 using ehci-pci Apr 20 00:24:13 tinkywinky kernel: [18782.645247] usb 3-1.6: New USB device found, idVendor=045e, idProduct=0040 Apr 20 00:24:13 tinkywinky kernel: [18782.645253] usb 3-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Apr 20 00:24:13 tinkywinky kernel: [18782.645257] usb 3-1.6: Product: Microsoft Wheel Mouse Optical® Apr 20 00:24:13 tinkywinky kernel: [18782.645260] usb 3-1.6: Manufacturer: Microsoft Apr 20 00:24:13 tinkywinky mtp-probe: checking bus 3, device 12: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.6" Apr 20 00:24:13 tinkywinky
Debian 9 Xfce intermittent keyboard and mouse erratic behavior or lockup
debian-user: I have an SSD with Debian: 2022-04-19 23:24:11 dpchrist@tinkywinky ~ $ cat /etc/debian_version ; uname -a 9.13 Linux tinkywinky 4.9.0-18-amd64 #1 SMP Debian 4.9.303-1 (2022-03-07) x86_64 GNU/Linux I have been experiencing intermittent storms of random keyboard and mouse GUI events over the past year or more: a. Windows are opened, closed, minimized, resized, etc.. b. Windows and/or desktop pop-up menus are opened, and random items are activated. c. Text that I have previously typed is pasted into random windows. d. Sometimes the mouse is left in a desktop rectangular selection mode (?). The storms are triggered when I move the mouse in an active window. A storm consists of dozens of individual random GUI events per second. The storms typically end when I stop moving the mouse. The next time I move the mouse, another storm may start or may not. I typically reboot if there is more than one storm. Firefox (on heavy JavaScript sites) and FreeCiv are applications that are likely to trigger storms. Alternatively, instead of a GUI random event storm, the keyboard and mouse lock up. Disconnecting and reconnecting the keyboard and mouse has no effect; the only cure is to reboot. I have tried various measures to isolate the problem, to no avail: 1. Power cycling and/or bypassing the KVM switch. 2. Moving the OS disk into another machine with different hardware. 3. Installing Debian 10 on another SSD and testing. Same for Debian 11. Is anyone else seeing these GUI event storms? I was enjoying a game of FreeCiv this evening on a desktop computer with the KVM switch connected, and a storm occurred. I shut down, connected the keyboard and mouse directly to the computer, and resumed my game. Perhaps an hour later, the keyboard and mouse locked up. If I login from another machine via SSH, disconnect the keyboard, count to 10, and reconnect the keyboard: 2022-04-20 00:22:52 root@tinkywinky /var/log # tail -n 17 messages Apr 20 00:21:40 tinkywinky kernel: [18629.457897] usb 3-1.5: USB disconnect, device number 9 Apr 20 00:21:50 tinkywinky kernel: [18640.176348] usb 3-1.5: new low-speed USB device number 11 using ehci-pci Apr 20 00:21:50 tinkywinky kernel: [18640.314951] usb 3-1.5: New USB device found, idVendor=04d9, idProduct=a0b9 Apr 20 00:21:50 tinkywinky kernel: [18640.314957] usb 3-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Apr 20 00:21:50 tinkywinky kernel: [18640.314961] usb 3-1.5: Product: ES-87 Apr 20 00:21:50 tinkywinky kernel: [18640.314963] usb 3-1.5: Manufacturer: Keyed Up Labs Apr 20 00:21:50 tinkywinky kernel: [18640.329387] input: Keyed Up Labs ES-87 as /devices/pci:00/:00:1a.0/usb3/3-1/3-1.5/3-1.5:1.0/0003:04D9:A0B9.000C/input/input23 Apr 20 00:21:50 tinkywinky kernel: [18640.388751] hid-generic 0003:04D9:A0B9.000C: input,hidraw0: USB HID v1.10 Keyboard [Keyed Up Labs ES-87] on usb-:00:1a.0-1.5/input0 Apr 20 00:21:50 tinkywinky kernel: [18640.408155] input: Keyed Up Labs ES-87 as /devices/pci:00/:00:1a.0/usb3/3-1/3-1.5/3-1.5:1.1/0003:04D9:A0B9.000D/input/input24 Apr 20 00:21:51 tinkywinky kernel: [18640.464649] hid-generic 0003:04D9:A0B9.000D: input,hidraw1: USB HID v1.10 Device [Keyed Up Labs ES-87] on usb-:00:1a.0-1.5/input1 Apr 20 00:21:51 tinkywinky mtp-probe: checking bus 3, device 11: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.5" Apr 20 00:21:51 tinkywinky mtp-probe: bus: 3, device: 11 was not an MTP device Apr 20 00:21:51 tinkywinky org.xfce.FileManager[1155]: thunar-volman: Unsupported USB device type "usb". Apr 20 00:21:51 tinkywinky org.xfce.FileManager[1155]: thunar-volman: Unsupported input device type "/dev/input/event1". Apr 20 00:21:51 tinkywinky org.xfce.FileManager[1155]: thunar-volman: Unsupported input device type "(null)". Apr 20 00:21:51 tinkywinky org.xfce.FileManager[1155]: thunar-volman: Unsupported USB device type "usbhid". Apr 20 00:21:51 tinkywinky org.xfce.FileManager[1155]: thunar-volman: Unsupported USB device type "usbhid". If I cycle the mouse: 2022-04-20 00:24:36 root@tinkywinky /var/log # tail -n 13 messages Apr 20 00:24:00 tinkywinky kernel: [18769.493620] usb 3-1.6: USB disconnect, device number 10 Apr 20 00:24:13 tinkywinky kernel: [18782.515065] usb 3-1.6: new low-speed USB device number 12 using ehci-pci Apr 20 00:24:13 tinkywinky kernel: [18782.645247] usb 3-1.6: New USB device found, idVendor=045e, idProduct=0040 Apr 20 00:24:13 tinkywinky kernel: [18782.645253] usb 3-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Apr 20 00:24:13 tinkywinky kernel: [18782.645257] usb 3-1.6: Product: Microsoft Wheel Mouse Optical® Apr 20 00:24:13 tinkywinky kernel: [18782.645260] usb 3-1.6: Manufacturer: Microsoft Apr 20 00:24:13 tinkywinky mtp-probe: checking bus 3, device 12: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.6" Apr 20 00:24:13 tinkywinky kernel: [18782.655370] input: Microsoft Microsoft Wheel
