Hi Daniel, yes I was going to resort to that if necessary. Thanks!
One comment though, I found that the setting was not even saved before I
switched to Fvwm.
I had to redo the mouse speed each time I logged into an Ubuntu session.
--
You received this bug notification because you are a member
Public bug reported:
I would like to use gnome control center from Fvwm window manager. But
the mouse speed does not respond at all to what I set unless I am
running it from the default ubuntu window manager. I tried running
gnome control center using different XDG environment variables as
That's right, I masked them by hand following some advice on the internet for
how to make systemd stop suspending, since it was not responding to settings in
login.conf even after restating logind
service.
Regardless of my motivation, it seems buggy that changing these settings
should lead to
sorry, you can withdraw this bug as I discovered it is a kernel bug, not
systemd.
(I wanted to withdraw it earlier but did not know how to get back to this
report.)
thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When I close the lid on my laptop, syslog goes crazy with the message
systemd-logind: hibernation is restricted; see man kernel_lockdown.7
repeated ad infinitum, using up all the CPU and GBs of disk space. I am
not even trying to hibernate; everything in
Public bug reported:
I used to be able to have many tabs open with Chromium without problems.
Lately it crashes or gives "aw snap" errors (see kernel messages below)
if I start to keep more than 25 or so open.
Description:Ubuntu 16.04.7 LTS
Release:16.04
chromium-browser:
Public bug reported:
in 20.04.01 LTS (release 20.04), suspend on lid closure works for a
while, then one day stops working, with no error message in syslog. The
event is not even registered. The problem seems to start when the
system has been inactive for long enough so that the screen is
by unmasking sleep.target suspend.target hibernate.target hybrid-
sleep.target, and allowing for suspend on lid closure in login.conf, I
was able to make the problem go away, but why should I be forced to
this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Using systemctl status systemd-logind, I see that lid events are no longer
being detected.
This behavior persists even after restarting the service. This is *not* what
is requested in logind.conf, where HandleLidSwitch=suspend and
HandleLidSwitchDocked=suspend.
--
You received this bug
Public bug reported:
Right after booting, acpi lid open/close is detected as it should be by
the kernel, but some time later it crashes, so I have to manually
suspend the system. The traceback is here:
Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here
]
Sep 20
Unfortunately it looks like the bug did not disappear. I have it
starting around 45 minutes after booting in the kernel we thought was
good, 5.4.0-52-generic_5.4.0-52.57. Unless I somehow screwed up and
reinstalled a broken one.
--
You received this bug notification because you are a member of
damn, wrong again, the patched kernel has just displayed the bug.
no fixed!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896482
Title:
acpi event detection crashes
To manage notifications about
sorry, I retract that. The problem is that ubuntu updated my kernel without my
knowledge,
replacing the correctly patched kernel with the broken one (that both have the
same numbers!)
It would be nice if the patch got incorporated into the distro to save me and
others from this headache!
I
Public bug reported:
On my new computer, secondary selection with the middle mouse button is not
working. The cursor
does not move when I attempt to drag it while the middle button is pressed. It
may be a motif bug
rather than an nedit bug, since the problem does not occur when I ssh into
I've switched to firefox, that solved the problem!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898389
Title:
browser frequently crashing with trap int3
To manage notifications about this bug
It seems like nobody is paying attention to this since the fix (which
does not work) was released. Maybe we need to post new bug report?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896482
Title:
16 matches
Mail list logo
