Yes that could be the thing. I've used Trisquel with other mouses before and
there was no such problem.
Interesting part is that re-plugging the mouse fixes it.
Maybe there is some workaround, since its quite unfortunate to re-plug the
mouse every single boot up.
If it's a gaming mouse it may have some "invert mouse" trigger in the mouse
internal firmware. Because many gamers prefer to play with "invert mouse" ON.
Hello.
I've recently installed a fresh Trisquel to my machine and encountered some
mysterious issue.
Whenever I launch my PC, the mouse Y axis on my mouse is reversed by default
(i.e. when I move up, pointer goes down and vice versa)
X axis works correct though.
I have to plug my mouse off
Yes. Just be aware that https://addons.thunderbird.net includes proprietary
addons: check the license (the page for the addon indicates it). It is the
(good) reason why Icedove does not search on that site.
Trying to install add-ons on Icedove:
1. Open Icedove.
2. Open the Add-on Manager by pressing F10 to make the Menu bar visible, then
deploying the Tools menu, then clicking on the Add-ons item.
3. Introduce the name of the extension on the field "Search for more
extensions", then press Enter.
According to 'man journalctl', option --boot (-b) "show messages from a
specific boot". However, on my system:
$ journalctl -b -1
Specifying boot ID has no effect, no persistent journal was found
According to 'man journald.conf':
Storage=
Controls where to store journal
liching...@disroot.org writes:
> https://dev.to/l04db4l4nc3r/herbstluftwm-a-dead-simple-window-manager-48ao
>
> Hello, I find this interesting article
> about some minimal windows manager.
> What do you think?
Looks a lot like my window manager of choice, which is awesomewm
https://dev.to/l04db4l4nc3r/herbstluftwm-a-dead-simple-window-manager-48ao
Hello, I find this interesting article
about some minimal windows manager.
What do you think?
The worst possibility is hardware failure. I had a coreboot X230 which often
automatically power-off (several times per day). It turned out to be chipset
physical damage, so I sold it to someone else.
Thanks for the answer. Yesterday I reinstalled the system, but it still
periodically shuts down. I entered your code, errors were detected, but, as I
understood it in the current session.
sergey@pc:~$ journalctl -p 3
-- Logs begin at Пт 2020-06-05 11:18:01 MSK, end at Пт 2020-06-05
10 matches
Mail list logo
