I'm having the same issue as the original poster -- while fully charged, if I
set the display brightess to max, or press the brightness-up button while
already at max, the "Laptop battery is charged noification pops up below the
brightness one. This alone wouldn't be a huge problem, only there's
and here is a log for when I press and hold the brighness button for a
while initially, and receive dozens of the battery notifications
** Attachment added: "gpm2.log"
http://launchpadlibrarian.net/47192070/gpm2.log
--
setting laptop bright to max show "Battery is charged"
https://bugs.launch
Public bug reported:
Binary package hint: libsfst1-1.2-0-dev
A toy program that does "#include " fails to compile
with the ubuntu package, complaining about a missing mem.h file. Copying
mem.h from the source tarball of libsfst to the include directory makes
it compile, so it looks like the file
Public bug reported:
Binary package hint: xemacs21
sorry for the localised error msgs
Konfigurowanie xemacs21-mule (21.4.22-2ubuntu1) ...
emacs-install xemacs21
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/37257661/Dependencies.txt
** Attachment added: "Dmesg.txt"
http://launchpadlibrarian.net/37257662/Dmesg.txt
** Attachment added: "DpkgTerminalLog.txt"
http://launchpadlibrarian.net/37257663/DpkgTerminalLog.txt
--
pa
Public bug reported:
New Dell laptop, fresh 20.04 install, 5.8.0-44-generic
#50~20.04.1-Ubuntu SMP, had two xorg freezes the same day. Managed to
grab dmesg from one where I got a text console:
[12775.113344] BUG: unable to handle page fault for address: e6787008
[12775.113347] #PF: super
Thanks for the reply. I'm currently trying out linux-image-oem-20.04 (=
5.6.0.1048.44) and things are looking better so far (but it hasn't been
that long). I'll try to update here after more testing, and will try a
newer kernel after that.
--
You received this bug notification because you are a m
I was having the same problem ("If you use one of --cert or --key, you
must use them both" in syslog). Upgrading to 1.8.0-3 fixed the issue for
me.
As a minor caveat, simply pointing to the private key file in the UI was not
enough and I was getting:
nm-openvpn[5972]: OpenSSL: error:0B080074:x509
Public bug reported:
My laptop failed to suspend overnight and was unresponsive when I opened
it back up. This is on Ubuntu 20.04.2 LTS with kernel 5.6.0-1048-oem and
pulseaudio:amd64/focal-updates 1:13.99.1-1ubuntu3.10 uptodate. In
syslog, I found a stream of suspend attempts with pulseaudio-rela
"; realtime-scheduling = yes" is commented away in
/etc/pulse/daemon.conf (this is a very fresh install of 20.04 and I
haven't customized much). Should I enable this?
Either way, I'll try to exercise suspend and keep an eye out for this
issue happening again. I tried looking around but didn't find
Public bug reported:
I've been getting freezes on Ubunyu 20.04 on my Dell Latitude 7420
laptop with a secondary display connected through a WD19 Dell dock. I'm
on the supposedly-certified 5.6.0-1048-oem kernel, have tried 5.8 and
5.10 without much success (other types of freezes). Some freezes loc
So far I've tried 5.6.0.1048.44 from linux-image-oem-20.04 and
5.10.0-1016-oem from linux-image-oem-20.04-edge and while I did not get
this exact freeze in either, both were unstable for me. 5.6.6 seemed
promising at first but I got up to three lockups on that yesterday
--
You received this bug n
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.6/+bug/1919425 for
the other freeze I was getting where I could get some logs out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917334
Title:
I also got a similar freeze on 5.10.0-1016-oem (from linux-image-
oem-20.04-edge), was also able to ssh in, and got a similar dmesg:
BUG: unable to handle page fault for address: ffefba9d49e3)
...
I had this running for longer, and what followed were CPU lockup logs
like
watchdog: BUG: soft
It's just me twice on two different kernels ;)
I'll try doing that. Might takie a while to get a repro since I'm also
trying to (a) see if not having the external monitor / connecting it
differently helps (b) do actual work on that machine. I'll reply when I
have something.
--
You received this
/proc/sys/kernel/oops_all_cpu_backtrace seems unavailable in 5.6 (added
in 5.8 per a quick search). I'll switch to 5.10 again and try there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919425
Titl
As an update, it's now been roughly a week with no freezes or crashes
for me. I have not changed my usage pattern: same dock, same external
display, devices, etc., and same applications used. I did change one
thing however. When I was switching again to the linux-image-
oem-20.04-edge I decided to
I haven't encountered the problem in over a week after switching to a
5.10 kernel (from linux-image-oem-20.04-edge).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918880
Title:
pulseaudio threaded-
Ping?
I noticed the fix is present in debian stable, but is still not in
ubuntu -- see https://packages.debian.org/search?keywords=java-common
which is at 0.59. Ubuntu is at 0.56 / 0.57
(https://launchpad.net/ubuntu/+source/java-common); the fix appears to
be included in 0.58.
--
You received th
Public bug reported:
$ nm-applet # then try to connect to password-protected network
nm-applet-Message: New secrets for 3/802-11-wireless-security
requested; ask the user
**
GLib:ERROR:/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gvarianttypeinfo.c:163:g_variant_type_info_check:
assertion failed
** Summary changed:
- nm-applet crases when connecting to a wireless network, around password prompt
+ nm-applet crashes when connecting to a wireless network, around password
prompt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
I have a similar-looking problem after some update in Ubuntu 12.10,
persisting after an upgrade to 13.04. Reproduces on 3.8.0-33, 3.5.0-43,
3.5.0-40 and 3.5.0-40, so it might be not directly related to the kernel
version.
I'm also on an AMD card, Advanced Micro Devices [AMD] nee ATI Caicos
[Radeon
I have attempted to fix the issue in the package and ended up with a package in
my ppa here:
https://launchpad.net/~kailoran/+archive/nekst-ppa
This fixes the issue for me.
--
compile error when using libsfst1-1.2-0-dev, mem.h missing
https://bugs.launchpad.net/bugs/583815
You received this
23 matches
Mail list logo