same problem here. i'm on an asus m2n-e motherboard and using the
generic i386 kernel 2.6.20-14.23. stalls (for a long time) during boot
and drops to busybox prompt, reading back shows that my sata drives are
not being correctly supported anymore, so the system tries to map some
scsi-generic (cardr
attached is the lspci -vvn for asus m2n-e motherboard system that stii
has this problem.
** Attachment added: "lspci -vvn"
http://librarian.launchpad.net/7318089/lspci.txt
--
MASTER: Computer will not boot after 2.6.20-14.24 kernel upgrade
https://bugs.launchpad.net/bugs/106063
You received
looked through kern.log, 2.6.20-14.22 booted fine, 2.6.20-14.23 (the one
that won't boot) leaves no trace in kern.log...
--
MASTER: Computer will not boot after 2.6.20-14.24 kernel upgrade
https://bugs.launchpad.net/bugs/106063
You received this bug notification because you are a member of Ubuntu
some extra info: this is on kubuntu 21.04 in an x session. if i change
the session to a wayland one, the issue goes away.
so the above mentioned crash in steam's libcef.so is triggered under x
but not under wayland, which might suggest a bad interaction with the x
graphics stack. in my case the x
this bug affects me also on kubuntu 21.04 using wayland session.
either the upstream bug report is incorrect in saying this is fixed in
the kubuntu 21.04 version of kwin or sels this is a different but
simillar issue.
it makes firefox unuseable in the wayland session on kubuntu 21.04.
--
You re
...so the bug should still be titled: "Firefox unusable on Kubuntu 21.04
Wayland session" as it was originally, as it may not be the exact same
upstream issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Public bug reported:
in hirsute (21.04) steam (steam/hirsute 1:1.0.0.68-1ubuntu1) displays
it's client window as completely black, with no visible contents.
if started from a console the line:
.steam/ubuntu12_64/steamwebhelper.sh: line 23:
124402 Segmentation fault (core dumped) ./steamwebh
Public bug reported:
on hirsute (21.04) software-properties-qt (software-properties-
qt/hirsute 0.99.8) (also callable as software-properties-kde) throws a
python exception when a package download source of "other" is selected.
this python traceback appears in the console:
Traceback (most recent
** Description changed:
on hirsute (21.04) software-properties-qt (software-properties-
qt/hirsute 0.99.8) (also callable as software-properties-kde) throws a
python exception when a package download source of "other" is selected.
+ the same error occurs when using software-properties-gtk.
** Tags added: hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923553
Title:
software-properties gui python exception on selecting "other" package
source
To manage notifications about this
** Tags added: hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923398
Title:
steam client window all black
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+so
*** This bug is a duplicate of bug 1909918 ***
https://bugs.launchpad.net/bugs/1909918
yes bug #1909918 mentions the same issue, but my report has a little
more info on what the underlying python problem is and also mentions
that it occurs in all the various software-properties gui's, not just
*** This bug is a duplicate of bug 1909918 ***
https://bugs.launchpad.net/bugs/1909918
updated bug #1909918 with the extra info.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923553
Title:
sof
as pointed out in bug #1923553 , this bug affects all the various
software-properties gui's (including software-properties-qt, software-
properties-kde), not just software-properties-gtk.
it is also mentioned in the other bug report that the issue seems to be
that the underlying python code being
hi all, exactly the same issue here. this is on a Thinkpad E15 Gen 2
(AMD) which is the same hardware as the E14 in the bug title (with just
a larger screen).
i also get alternately the "stack corruption" in the elantech driver
message or freezing on the Lenovo logo, as mentioned above. this is
si
oh, i should mention i tried running the 21.10 installer on the same
machine and (as expected) since no-one would know to disable their
trackpad before trying to install, this bug effectively makes 21.10
uninstallable on this hardware, so for installation purposes i'd call
the bug critical.
--
Yo
just confirming that that _both_ issues still occur with the latest
kernel updates on 21.04 as of today (2021-10-15).
would be really nice not to have to use either of the two hacks
described above to get this working.
i also added the fn key problem to the bug title to aid in searching.
** Summ
> This isn't urgent because the kernel at https://people.canonical.com/~mschiu77
> /lp1941773/I/ is working for me for now on my Thinkpad E15 Gen 2 (AMD).
why does a working non-standard kernel mean it's not urgent? this is
urgent, and for the installer, critical, until a fix is released in the
of
@arighi hi Andrea, any update on where this is going? is there anything
else we can do to test or provide extra info? even "still investigating"
would be good to know. ;) cheers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
you can also just disable the trackpad in the bios settings.
then enable it again when a fixed kernel is available.
bit of a super pita having a laptop with no trackpad though, ;) and for
people running the installer (who would have no reason to know to
disable their trackpad or apply boot params
@randomdave, in case you didn't, i think you have to disable the
trackpoint as well as the trackpad.
some people have reported that just disabling the trackpoint but leaving
the trackpad enabled works, but you lose the trackpad buttons and have
to configure tap-to-click.
for others it only works
the fix was in *-24 in proposed and it worked and was confirmed, then
*-25 was released _without_ the fix making *-24 redundant (it's gone
now).
the bug assignee is mia (probably well deserved seasonal holiday). can
someone on the ubuntu kernel team: _please_ fix this mess. the fix in
*-24 was con
So the kernel in jammy has the fix released, well fine. but where is the
the fixed released kernel for impish!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945590
Title:
Thinkpad E14 Gen2: Kernel
yes, there is still no released kernel with the fix for impish.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945590
Title:
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
To
@arighi that would be great. when you ping them you should mention that
the release notes need to have a "Known issue" added at the very least.
cheers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/194
@arighi great stuff, nice to get there in the end on a complex problem.
cheers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945590
Title:
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpo
@alphanor you have very different hardware and the symptoms are
different and occurring on a different os version, would likely be be
more helpful to yourself if you opened a new bug report for your issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
well let's be clear here: none of the workarounds suggested in this
thread are fixes, nor are they meant to be, they are workarounds only,
to allow some functionality until the actual fix arrives.
the actual fix will be a new kernel package release that has the
underlying stack corruption bug fixe
i can confirm that the kernel linked by randomdave above works
perfectly.
so there is your working kernel, bisect away.
(can also confirm the 5.15 kernel still has the bug, every ubuntu kernel
since 5.11 has the bug, apart from the unofficial one linked by
randomdave 2 replies above.)
--
You re
@arighi fwiw i have also tested 5.13.0-22.22+arighi2020+1 and can
confirm it is working fine for me. cheers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945590
Title:
Thinkpad E14 Gen2: Kerne
@arighi i completely agree with manolo above and have also stated it
before above, this bug has to be considered critical for the installer
(all the *buntu installers) because on installer launch you just get a
total kernel lockup/crash with no possibility to proceed.
in fact i still don't underst
@nemodot it's been said that the fix should be in the next kernel
release. in the meantime if you use apt to keep your system (which
*buntu does by default) up to date you can use 'sudo apt-mark hold
' on the known good kernel packages to prevent apt from
removing the ones you want.
--
You receiv
well if it is another bogus change to "fix released" why does this keep
happening?
and since it is at least "fix committed" how about an update on what
kernel version the fix is in and when it will be released?
@arighi any update? thanks.
--
You received this bug notification because you are a
just tested the 5.13.0-24.24 kernel from proposed, it does NOT fix the
problem on my ThinkPad E15 AMD Gen 2, this kernel just freezes at the
Lenovo logo like all the other broken kernels.
The 5.13.0-22-generic_5.13.0-22.22+arighi2020+1 kernel still works
flawlessly.
what's going on? i though
ok, well glad to see this is working for others.
now, how can i get extra information about the failed boot to find out
why this kernel does NOT work for me but kernel
5.13.0-22-generic_5.13.0-22.22+arighi2020+1 DOES work for me?
one note: i applied the latest lenovo bios update which came ou
just to be clear, the updated bios shows as: R1AET40W (1.16) in the
bios setup screen.
can someone, who the new kernel works for, please confirm that they are
on this new bios version??
thanks in advance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
ok, pleased to report that i did a forced reinstall of the new kernel
from proposed and it is now working fine on my E15 AMD Gen2. don't know
what went wrong the first time but glad the fix is good.
apologies for the static. don't need anyone to check bios versions
anymore. cheers.
--
You receiv
yes this is a real mess.
@yrogge according to the kernel bot message when you removed the
verification-needed-impish tag and added the verification-done-impish
tag that should have been what "confirmed" the fix to be included.
so please, can @arighi the bug assignee, or some other ubuntu person
p
yes, great we finally got there. thumbs up.
works on my e15 gen 2 amd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945590
Title:
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enab
39 matches
Mail list logo
