This bug report is now very old, but is this bug still present?
Here is why I ask.
Running valgrind on a C program - a program that I adapted from someone
else - showed a lot of possible leaks. But I learnt from this the
present bug report to do 'snd_config_update_free_global()'. Having done
that
I experience what might be a similar crash, albeit on Linux Mint.
I have put a crash dump here: https://termbin.com/b726b. Also, I
reported the issue against Mint, here:
https://github.com/linuxmint/cinnamon/issues/10412#issuecomment-949710193.
I am unsure whether this the current page is the rig
Not fixed for me, on 5.8 and 5.10 kernels.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1258838
Title:
[Lenovo ThinkPad X230] suspend/resume failure
Status in Linux:
Unknown
Status
I have just experienced this problem for the first time (on, admittedly,
Linux Mint) with kernel 5.8.0.
I note also that there is a report on the problem filed against the
Linux kernel itself, here:
https://bugzilla.kernel.org/show_bug.cgi?id=190281
Perhaps Ubuntu devs should engage with that rep
I spoke too soon. Deep sleep works now, and the touchpad keeps working,
but only - even with the new motherboard - if I keep the NFC *enabled*
in the BIOS. And the trackpoint does not work under Linux. At all. At
any time (at least on my distro) and even with a very recent kernel.
--
You received
Somewhere in this long thread, I think, an engineer suggested the
following.
Somehow, in my particular case - a case in which, on my ThinkPad X1CG6,
no work-arounds worked and neither did the test version of the kernel
patch - my motherboard was at fault.
Well, the engineer was right. For, I got
@Kai-Heng
Please be clear. I take it that by your last post you mean this: I
should stick to s2idle in the sense, not of (i) sending you only the log
for that, but in the sense of (ii) not contributing to the fix. However:
will someone who uploads both logs here be contributing to the fix?
Subordi
@Kai-Heng
Do you need those two desmgs from one and the same machine? I will not
provide that, because I have had enough of rebooting my non-working
machine when I enable S3. I am happy to attach a S2Idle log, though.
--
You received this bug notification because you are a member of Kernel
Packa
'Anyone tried a very recent kernel and can confirm the issue is still
there [..]?' I tried 5.6.19, I think it was (so, moderately recently)
and I can confirm the problem is there. Also, I've looked at the release
notes for various 5.7 kernels and not seen a sign of the patch.
--
You received this
@
Thank you for the detailed attempt to help.
On my 20KHCTO1WW, with kernel 5.6.19-050619-generic, BIOS 1.49, and the
latest updates delivered by fwup, I enabled the fingerprint reader and
enabled S3 sleep. I did those things in the BIOS. Then I put the
computer to sleep for ten minutes or so
Given that the change to the compression format is one of the headline
features of Ubuntu 20, and that Ubuntu 20 is a LTS release (and thus,
for one thing, a release upon which other Linux distributions are based)
I am surprised that this problem made it into the final release.
--
You received th
It would be nice to see some movement on this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1125595
Title:
/usr/sbin/dkms: line echo: write error: Broken pipe
Status in dkms package
@jnns
I appreciate the sentiment but (1) that is a workaround whereas a fix is
needed, (2) some (most?) of us here have tried all the fixes, including
the ones you mention, and to no avail.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
People claim repeatedly that the problem is fixed when it is not. I will
believe it only when I see it and indeed I will test it only with
further reason to believe it. Sad, but reasonable.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
@Pavel
That sounds helpful. However, I'm going to need some reassurance before
I change all my settings. ('All' because I seem to remember that I have
to change more than the BIOS sleep mode to get the system to use S3. I
think I have to unblacklist some module and change some kernel boot
paramete
dr_strangehate:
Thanks.
I keep a Windows-to-Go drive around for just this sort of nonsense. I
haven't run it for months. Running it now, and running the Lenovo update
program, the only firmware update that I see (as against Windows
software updates) is for Intel ME. So I suspect the following. I
> what you can do is update your touchpad/trackpoint firmware under
Windows (unfortunately it's not supported in fwupdmgr), which fixes the
issue completely for Linux, at least it did in my X1 Gen6 and a few
others I know.
Suppose that is true. Then it merits a response of 'for goodness sake!'
to
Andrea: It might be worth saying whether you have a model with the 'NFC'
chip. (For - *I think*, and at least with the sixth generation - the
following holds. Once one has Lenovo's BIOS updates applied, then only
models with the NFC chip have the sleep/pad problem.
--
You received this bug notifi
@brad-figg
Sorry, but what is it for a bug report to be ubuntu-certified?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1791427
Title:
Touchpad and/or trackpoint stop working after S3
I see the error in my logs too, though I have not noticed symptoms.
OS: Linux Mint 19.1 Tessa x86_64
Host: 20KHCTO1WW ThinkPad X1 Carbon 6th
Kernel: 5.1.14-050114-generic
DE: Cinnamon 4.0.10
WM: Mutter (Muffin)
WM Theme: Mint-Y-Dark-trans (Mint-Y-Dark-BB_hack)
Theme: Mint-Y-Dark [GTK2/3]
Ico
Hello all
Is the following relevant? 'Fixed an issue where there is an Incorrect
Intel ME ICC settings after system resume from S3 or S4 states' - from
the changelog of a Intel ME update for the X1CG6. Full changelog:
https://download.lenovo.com/pccbbs/mobiles/n23rg11w.txt
--
You received this b
I see the problem on Linux Mint 19.1, which is based on Ubuntu bionic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1125595
Title:
/usr/sbin/dkms: line echo: write error: Broken pipe
Thanks Aaron.
My X1CG6 does have no problems with the trackpad when I use S2idle sleep
- well, except power consumption. Still: I did not know that, 'From 5.0
kernel power consumption of s2idle is less than 1w, pretty much like S3
0.6w.' On the other hand, that is a difference of some 30%. Perhaps
For comment #160.
The file is the output of: journalctl -b 0 -k
** Attachment added: "journalctl -b 0 -k"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+attachment/5251554/+files/report.txt
--
You received this bug notification because you are a member of Kernel
Packages, whi
For comment #160.
rmi_irq.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1791427
Title:
Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
Carbon 6th
Status in
@thorsten
Thanks.
I loaded the kernel from #94, having set the BIOS to use S3 sleep and
having removed that driver from the blacklist. Result: after a fairly
long sleep (15 minutes, I think) the touchpad stopped working. I tried a
workaround, with no success:
# echo 1 > /sys/devices/rmi4-00
I tried Jarek's band-aids - a long time ago, admittedly - and they did
not work on my machine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1791427
Title:
Touchpad and/or trackpoint st
Here is a datapoint.
System at issue: X1CG6 with NFC, with BIOS 1.37 and all firmware updated
as much as possible (via both `fwupdmgr` and a WindowsLive external USB
harddrive).
Method of attempted fix: using a patched vrsion of kernel 5.0.2; having
the 'psmouse' value set as 1 in the boot string
@Thorsten: thank you. I presume I could use the 5.0.0 kernel (you have '
--branch v5.0.1') because I seemed to have some new trouble with the
touchpad with 5.0.1.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
I am sorry, but what is going on?
The authors of some posts in this thread say that they are using a
patched kernel. Yet, the developer, Aaron, seems to say one does not
need patches . However, that same developer seems to say that his work
has *not yet* become incorporated into the kernel. (Meanw
@Thorsten
Might you explain how to apply patches to, say, the 5.0.1 kernel (which
I am using, via the Ubuntu Kernel Update Utility, on Linux Mint)? I
can't seem to find the information in this thread and I am unsure of the
goodness or at least relevance of other instructions that I've found on
the
I am sorry to keep banging on, and we are grateful for your work, but,
again, you need to be precise. Do you mean (1) udev rules are a better
way to run the command at boot (than some other way of running the
command at boot), or (2) udev rules are better than running the command
at boot, because w
@AaronMa
Thank you.
To be clear, though: you mean the following, yes? If, after applying the
patches, one still has a touchpad problem, then one should issue the
command you give. Presuming that that *is* your meaning: when should one
apply that command? After boot and after every sleep?
--
You
Here is some information relevant to this thread.
An update from Ubuntu that 12c_i801 *re*-blacklists just arrived on my
Mint PC.
I had it blacklisted on my system anyway. A while ago, it was
blacklisted by default, but then a Debian update removed it from the
blacklist. Now, for Ubuntu and deriv
Me again. Now, I might have faulty hardware, but it occured to me that
having 'reboot=w' in my kernel boot arguments might be the problem. I
will test - i.e. see whether the patch works if I remove that argument -
when I have time. Still, using that argument does have a purpose
--
You received th
Thanks, all.
I've verified that I do indeed have version 1.3 of the touchpad software
installed (and I am horrified but not surprised that Lenovo managed to
get a bug into their firmware updater).
I have looked at the Windows event log and the only repeated errors I
see have to do with 'Distribut
n23gc05w.exe now installed, and the patched kernel still does not work.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1791427
Title:
Touchpad and/or trackpoint stop working after S3 sus
I add that the kernel switch `psmouse.synaptics_intertouch=1`seems to
produce spurious middle clicks as desribed on the page
https://bugzilla.redhat.com/show_bug.cgi?id=1482640 (even though that
page says kernels >= 4.13.6 have fixed the problem).
But I find that my system may not have the latest
I have just now installed the latest firmware updates from Lenovo, by
creating a 'WindowsToGo' installation. The problem with the touchpad
being dead after S3 sleep remains. (I haven't tested the trackpad.) That
affords a little more reason to think that my touchpad is broken; but I
think we should
Thus far I have had `tlp` enabled. Just now I disabled it. Nothing
seemed to change, i.e. the trackpad still does not work at all (and the
trackpoint does not work under any circumstances - at least if using
libinput; when I first got my X1, and used synaptics, the trackpad would
work, so long as I
** Attachment added: "rmi_irq.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+attachment/5231173/+files/rmi_irq.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/179
Done.
Enabling the trackpoint in the BIOS did not (because of some sort of
update since the last time I tried it) cause the touchpad to stop
working but the trackpoint did not work at all either (either before or
after sleep). Perhaps I have the trackpoint disabled in some further way
somewhere.
@AaronMa
You might want to see the new logs I have posted. But there is indeed a
touchpad firmware update that I not applied - but not for want to
trying. The update is not available via fwupdmgr, there is no bootable
version of the update, the update will not install via virtualised
Windows or th
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+attachment/5231130/+files/journal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/179
As to, 'Can you use your touchpad/trackpoint': I can use the touchpad,
except after S3 (not the 'modern standby'/Windows version) sleep; but if
enable the track*point* in the BIOS, then the trackpad starts working
very peculiarly indeed. Other people have had the latter problem.
--
You received t
Thorsten,
I thought I had added that. I'll add it again and remove most of my
other kernel flags, in case they were causing a problem. Indeed I have
discovered a problem with the flags that I was using, namely, that as
well as having the correct (correct for testing) `psmouse` option, I had
additi
@thorstenr-42
You are right; and when I did my first test I had failed to see the
request for the journal.
I have tested again. As before, the rmi_irq file ended up blank, but I
attach the journal file.
As to Wireguard: I think that Wireguard doesn't get set up to work with
all release candidate
Here is a correction to my previous post (the post immediately above
this one). '[W]hat do you have in my specifically': I meant 'have in
mind'.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
> do you see any output when typing journalctl -b 0 -k?
Yes, but what do you have in my specifically? Anyway, at present I am
not running the patched kernel, because (1) as I explained, it broke my
networking, (2) deblacklisting the touchpad module seemed to cause my
touchpad problems (even when t
Thanks for the headers, Aaron (though Wireguard would not build against
them).
The patch did *not* work for me: the touchpad failed to work at all upon
resume, just as before. I have now added the debugging kernel parameter
and followed your further instructions but the log file at issue ended
up
AaronMa
Got kernel headers for that kernel, please? (I can boot from the kernel
but Wireguard isn't working because of the lack of headers. Since the
problem can take some time to manifest itself, I would not mind Internet
during the testing phase. I write this from a different computer.)
--
You
@mapengy
What you write is unclear.
Re 1: Are you asserting that I at present I am using that kernel switch?
Or are you rather suggesting that I try out that kernel switch? At any
rate: I do use that switch already (on a 4.19 kernel) and, no, the
touchpad does not work after suspend.
2: What?
New dmesg output, this time running libinput rather than synaptics (and
where I have the same problem, i.e. changing to libinput does not allow
the touchpad to work after deep sleep).
** Attachment added: "dmesgWithLibinput.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+att
Extra information - namely, the output of several relevant commands.
** Attachment added: "report"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+attachment/5220212/+files/report
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
My dmesg output immediately after resuming from suspend. I had enabled
S3 in BIOS and consequently the touchpad was not working. However, I had
a USB mouse on the go - for, otherwise, I would have trouble using the
computer in that state.
** Attachment added: "dmesg.txt"
https://bugs.launchpad
It may be worth my repeating that, despite trying a Windows PreBoot
Environment and a Windows Live Environment - but not full windows,
because I don't have that on the machine - I can't get the latest
touchpad firmware installed.
--
You received this bug notification because you are a member of K
I was rather shouty above, for which I apologise, but it is hard to
remain calm when things such as the following happen.
I tried up update the trackpad firmware, hoping this would help with the
S3 sleep / touchpad problem. I had use a Window pre-boot environment to
do to that. The new trackpad fi
I have yet to play roulette with the update - I installed it, but have
not tried to enable S3 yet. As I said in am email that seems not to have
reached this page: it is unclear that this BIOS update will help; the
release notes (such as they are) do not suggest it will.
While I am here, and might
@Thorsten
My config: NFC; new BIOS; i2c_i801 unblacklisted; 4.19 kernel; firmware
up to date (I think; the Windows only nature of some of the updates
makes its hard to tell); synaptics. Maybe the synaptics is the problem -
perhaps I need libinput and indeed in the version you mention. So that
is y
C'mon guys, this stuff is hopeless. As I said, I'm using Linux Mint. It
lacks the /etc/gdm3 folder - perhaps because (I don't know) it uses a
different 'greeter'. Nor does Mint use Wayland.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
Thanks for that. The ls reveals 1f.*4* on my system, but using that in
the file does *not* work for my system, at least not after a long sleep.
*Is any kernel switch (aka grub boot string) required for this*?
*WHERE on the Arch forum did you get this workaround? And was it really
a forum rather t
The above fix has a chance of working only if one's blacklisf.conf
(/etc/modprobe.d/blacklist.conf, on my Linux Mint system) does *not* to
blacklist 'i2c_i801'. Debian did recently remove that blacklisting.
--
You received this bug notification because you are a member of Kernel
Packages, which i
mr_tron
Thanks, but (1) I am hesitant to try yet another work-around, at least
without knowing whether you have the NFC model. (2) Where did you get
those echo values, please? Might they differ system to system? (If this
works, though, then I will be most pleased, though it won't mean Lenovo
doesn
I wasted a (further) day trying to install this stuff in a way I should
not even have to, namely via WindowsToGo, which doesn't work properly,
at least on my hardware. (I tried three USB sticks, multiple burners,
endured endless Windows setup screens and hangs.) And the fixes did not
work anyway. O
Cf. perhaps the following.
https://forums.lenovo.com/t5/ThinkPad-T400-T500-and-newer-T/Synaptic-
Firmware-updater-throwing-an-exception-and-not-updating/td-p/1693373
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
Thanks. It was hard even to run 'SynReflash.exe /Q': I had to install a
touchpad driver/update, or two and then locate the relevant folder. (All
this on a Windows PreBoot Environment. I tried to use a WindowsToGo
installation, but after hours of creation and booting it errored out.
When the command
66 matches
Mail list logo
