*** This bug is a duplicate of bug 2000649 ***
https://bugs.launchpad.net/bugs/2000649
Is there something I can do to trigger this bugfix to incorporated into
regular ubuntu updates? It's really annoying to work on unstable system,
and knowing it has been fixed already, sigh..?
--
You receiv
Everything is from the fresh install, I did none modify any of the
system drivers.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2001922
Title:
Xorg crash
Status in xorg-server
And another one...
35f5fbf4-abc7-11ed-9e34-fa163e993415
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2001922
Title:
Xorg crash
Status in xorg-server package in Ubuntu:
Incomp
I reinstalled the system and it happened again. The crash id from
/var/crash/_usr_lib_xorg_Xorg.0.uploaded is
f5810a24-aba6-11ed-b81a-fa163ef35206
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchp
I've got a new crash after installing the xorg-core-dbgsym, the
backtrace looks the same though. What else can I provide, other than
reinstalling the whole machine? That's something I'd really like to
avoid if possible
[60.469] (EE)
[60.469] (EE) Backtrace:
[60.472] (EE) 0: /usr/lib/x
Uh, did not have time for this until now, got quite a few crashes in the
meantime. I am attaching the latest xorg log that gives a backtrace
** Attachment added: "Xorg.0.log.old"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2001922/+attachment/5642994/+files/Xorg.0.log.old
--
This time it crashed almost instantly after logging in. There is a new
id in /var/crash/_usr_lib_xorg_Xorg.0.uploaded
be43a9e0-9103-11ed-9d0c-fa163e993415
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2001922/+attachment/5640509/+files/prevboot
Two more crashes, this time without a new entries in /var/crash/.
What can I do to collect more information? The system was stable before I
upgraded from impish to jammy.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubu
Updated now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2001922
Title:
Xorg crash
Status in xorg-server package in Ubuntu:
Incomplete
Bug description:
My Ubuntu 22.04.1
It just happened again 3aa3f8c4-8f92-11ed-aafb-fa163e55efd0
In the logs I see
Jan 09 09:38:34 xlap whoopsie-upload-all[1059]:
INFO:root:/var/crash/_usr_bin_xfsettingsd.1000.crash already marked for upload,
skipping
Jan 09 09:38:34 xlap whoopsie-upload-all[1059]:
INFO:root:/var/crash/_opt_zoom_
It just happened again, the content of
/var/crash/_usr_lib_xorg_Xorg.0.uploaded is 3aa3f8c4-8f92-11ed-aafb-
fa163e55efd0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2001922
Title
I don't see anything useful in the log:
Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: sending the secret exchange:
[sx-aes-1]\npublic=4uc+8Lpm5dEaUqICltU/1RtAGdPAJRNDnjN+h4KK4+V198oPek0B866EgtZjQLXjDS9IA4iI+46VWpzNpyNd9hyBDrch5nR>
Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: calling the PromptRe
The journal says contains these entries:
Jan 05 14:09:26 xlap systemd[1]: Starting Process error reports when automatic
reporting is enabled...
Jan 05 14:09:26 xlap systemd[1]: Started crash report submission.
Jan 05 14:09:26 xlap whoopsie[5359]: [14:09:26] Using lock path:
/var/lock/whoopsie/lo
The file contains this ID: 311e7093-8cfa-11ed-aae6-fa163e55efd0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2001922
Title:
Xorg crash
Status in xorg-server package in Ubuntu:
Public bug reported:
My Ubuntu 22.04.1 LTS installation crashes, but I was not able to figure
out how to reproducibly trigger the crash. The last time it happened was
with firefox and zoom running, the display suddenly went black and after
a few seconds the X login screen appeared, my session gone
@Coiby Xu (coiby)
Thanks a log for your contribution
I tried to use the way of "echo out > gpio386/direction" to fix the
problem without patching the kernel, but I found Touchpad click
sensitivity is less than patching the kernel.
--
You received this bug notification because you are a member of
If I am not misunderstanding...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_
I am not misunderstanding, does it mean that only patch for pinctrl-
amd.c without changing i2c-hid-core.c should solve the problem?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launc
@Azizkhan
check the patch file and your kernel file if the content for each line is
consistent. If it is, you could copy patch file to kernel folder and run
command "patch -p1 < patchfile"
@wangjun (biggerchina), @Coiby Xu (coiby)
Could you please summarize what you tested and did for patch? I a
Maybe expert could update in kernel git
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/tree/drivers/hid/i2c-hid/i2c-hid-core.c
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubun
@Coiby Xu (coiby)
Great. Touchpad works. Thank you so much
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legio
I did some search in internet. At this moment, it seems that most of the
Touchpad having this issue are MSFT 04F3:.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs
@wangjun user "dl3it" in that bug has AMD too and he seemed to solve it
by recompile the kernel with elan_i2c as module.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bug
Referring to another case #207759
(https://bugzilla.kernel.org/show_bug.cgi?id=207759)
I am curious why ideapad 15 has the same Touchpad ID and someone could
solve the issue by blacklist elan-i2c but Legion 15ARH05 cannot,
especially I didn't complied elan-i2c or elants-i2c. Legion 15ARH05
doesn't
@Stillnurs
Your advice doesn't work for me. Kernel 5.8.6
Actually, there is no event triggered by touchpad seen via "libinput
debug-events"
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://b
Hi Varghese,
Thanks for taking time to write the details. I faced the same problems with
getting tata docomo connected. I used the connection details you mentioned and
bingo! Thanks a bunch.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribe
26 matches
Mail list logo
