** Summary changed:
- [regression] Internal display shown as two displays with updated kernel
+ [regression] Internal display shown as two displays with updated kernel
6.8.0-51
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
** Description changed:
Lenovo T14s Gen 5 (Intel) running vendor provided OEM Ubuntu 22.04 has a
- regression where having the only internal display registers as two
- displays, and attaching an external display becomes display number 3 in
- the view of the OS.
+ regression where having only the
Public bug reported:
Lenovo T14s Gen 5 (Intel) running vendor provided OEM Ubuntu 22.04 has a
regression where having the only internal display registers as two
displays, and attaching an external display becomes display number 3 in
the view of the OS.
This behavior persisted on 6.8.0-51 and 6.8.
Can you test the 6.8.0-53 from proposed updates? After upgrading the
laptop I described my problem with, the problem seems fixed for me.
I've repeatedly booted to 51, 52 and 53, and currently it looks to me
the problem I described actually did exist on both 51 and 52, and gone
with 53. So it defin
** Also affects: linux-hwe-6.8 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https
It currently seems also like 6.8.0-51 on 22.04 started to display
internal display as two displays (monitors.xml shows None-1 and eDP-1)
which causes all kinds of mischief. I don't currently have direct access
to it however.
--
You received this bug notification because you are a member of Kernel
Similar to LP: #2092063 the upstream proposed PSR patches posted earlier
today at
https://gitlab.freedesktop.org/drm/amd/-/issues/3388#note_2705971 might
be also related to this bug.
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #3388
https://gitlab.freedesktop.org/drm/amd/-/issue
Public bug reported:
Laptop: Lenovo Thinkpad Z13 Gen 2, 1920x1200 IPS 400 nit touch display, Ryzen
Pro 7840U.
OS: OEM Ubuntu 22.04 LTS in its default Lenovo configuration, with latest HWE
kernel (https://launchpad.net/ubuntu/+source/linux/6.8.0-50.51)
The corruption looks a bit like hardware/di
** Description changed:
The laptop shipped with Lenovo's 6.5.0-1019-oem, but upon upgrades
switched to 6.8.0-47-generic which is generally preferred because
6.5-oem is no longer seeing updates.
- However, there is a regression that Fn+D Lenovo Privacy Guard does not
+ However, there is a
Back to this bug and a 22.04 installation after visiting 24.04 in LP:
#2085420 and LP: #2085423.
Paolo: First of all, your kernel build initially looked like to fix the
Fn+D functionality. As a side effect it somehow disables both the Mutter
notification about privacy screen enabled/disabled and t
Hi Paolo. I unfortunately have only a few hours per month for studying
these, and this particular laptop is already now going to be with a user
that I can't that easily reach. Since the user really needs the feature,
I enabled LTS upgrades and switched to 24.04, hopefully without any
other regressi
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
The laptop shipped with Lenovo's 6.5.0-1019-oem, but upon upgrades
switched to 6.8.0-47-generic which is generally preferred because
6.5-oem is no longer seeing updates.
However, there
** Description changed:
The laptop shipped with Lenovo's 6.5.0-1019-oem, but upon upgrades
switched to 6.8.0-47-generic which is generally preferred because
6.5-oem is no longer seeing updates.
However, there is a regression that Fn+D Lenovo Privacy Guard does not
- switch correctly on
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2085119/+attachment/5830340/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2085119/+attachment/5830334/+files/Lsusb-t.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/2085
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/2085119/+attachment/5830336/+files/PaInfo.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/2085119
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2085119/+attachment/5830346/+files/acpidump.txt
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-hwe-6.8 (Ubuntu Jammy)
Importance: Undecided
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/2085119/+attachment/5830343/+files/RfKill.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/2085119
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2085119/+attachment/5830344/+files/UdevDb.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/2085119
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2085119/+attachment/5830345/+files/WifiSyslog.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/bug
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2085119/+attachment/5830338/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/2085119/+attachment/5830342/+files/PulseList.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/
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2085119/+attachment/5830339/+files/ProcEnviron.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/b
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2085119/+attachment/5830341/+files/ProcModules.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/b
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2085119/+attachment/5830335/+files/Lsusb-v.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/2085
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2085119/+attachment/5830337/+files/ProcCpuinfo.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/b
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2085119/+attachment/5830332/+files/Lspci-vt.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/20
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2085119/+attachment/5830331/+files/Lspci.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/2085119
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2085119/+attachment/5830329/+files/CurrentDmesg.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
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2085119/+attachment/5830333/+files/Lsusb.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/2085119
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2085119/+attachment/5830330/+files/IwConfig.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/20
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/2085119/+attachment/5830328/+files/AlsaInfo.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/20
Public bug reported:
The laptop shipped with Lenovo's 6.5.0-1019-oem, but upon upgrades
switched to 6.8.0-47-generic which is generally preferred because
6.5-oem is no longer seeing updates.
However, there is a regression that Fn+D Lenovo Privacy Guard does not
switch correctly on after the lapto
Since the fix is not yet even in proposed, and I have a possible Z13 Gen
2 Lenovo pre-installed Ubuntu 22.04 LTS showing this problem (despite
switching to generic 6.8 kernel), I have a single purpose PPA at
https://launchpad.net/~timo-jyrinki/+archive/ubuntu/mesaprerelease (the
final release will
Adjusted the targeting to reflect that a fix (for the major part of the
problem) would be either shipping linux-oem-6.8 to jammy or updating the
meta package in jammy to point to generic instead of oem flavor, but
that neither of these packages need changes in other series.
** Also affects: oem-su
Ok I now had access to the AMD laptop in question, and it has oem-
sutton.newell-abeeku-meta.list pointing to sutton.newell repository.
I can also point out that additionally 6.8.0-40 itself does not fix the
flickering, it improves the situation but does not fix it.
And as mentioned, linux-oem-6.
I have right now only access to another laptop, but on which I can
confirm that 6.8 is discovered last, so basically anyone having this bug
still has this bug unless one knows how to configure GRUB, that is for
majority of people (especially people preferring vendor supported, pre-
installed laptop
** Also affects: linux-oem-6.8 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2070096
Title:
[amdgpu] Graphics driver issue:
Thank you for the fixes on the 6.8 series!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2070096
Title:
[amdgpu] Graphics driver issue: Display goes black for a second at
rand
I have access to a certified laptop which has this problem.
If you have any test kernels one could use, please tell. Or better yet,
a fixed kernel from Canonical/Lenovo (is there any proposed section in
the OEM archives?).
Not willing to update to 24.04 since in production use and updating
might
*** This bug is a duplicate of bug 1973167 ***
https://bugs.launchpad.net/bugs/1973167
** This bug has been marked a duplicate of bug 1973167
linux-image-4.15.0-177-generic freezes on the welcome screen
--
You received this bug notification because you are a member of Kernel
Packages, whi
@vicamo: Sorry for delay. I've tested / now running the kernel from the
PPA on my Acer Chromebook R11 and can confirm touch screen is still
working.
timo@timo-Cyan:~$ uname -a
Linux timo-Cyan 5.4.0-42-generic #46+lp1881319-Ubuntu SMP Tue Jul 14 06:40:05
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
--
@vicamo: Sorry for delay. I've tested / now running the kernel from the
PPA on my Acer Chromebook R11 and can confirm touch screen is still
working.
timo@timo-Cyan:~$ uname -a
Linux timo-Cyan 5.4.0-42-generic #46+lp1881319-Ubuntu SMP Tue Jul 14 06:40:05
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
--
I'm no kernel triager but I have a few observations that can help
focusing the bug report:
1. Are people manually installing tlp and that causing problems, or do
people experience this too with vanilla installation of Ubuntu? (tlp is
not part of the default install, and not in the 'main' supported
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/182
I've updated my cyan (Acer Chromebook R11) to kernel 5.4rc7 from
Ubuntu's mainline PPA, but the audio is still not working (no audio
device visible according to pulseaudio).
Are you aware of something else that still needs upstreaming beside the
mentioned
https://github.com/torvalds/linux/commit/d
Being fixed in upstream
https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-
next-5.2&id=2e26ccb119bde03584be53406bbd22e711b0d6e6
Maybe a candidate for SRUs too after the fix hits eoan (19.10).
** Also affects: linux via
https://bugs.freedesktop.org/show_bug.cgi?id=108514
Importance: Un
It seems there is no update since 2015 to qca subdir of linux-firmware,
so those newer blobs will need to be submitted by Qualcomm, maybe ytkim
specifically who did that 3 years ago if he's still at Qualcomm:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/log/qca
--
A fix might be coming in some months' time to the upstream kernel.
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, whic
*** This bug is a duplicate of bug 1666421 ***
https://bugs.launchpad.net/bugs/1666421
** This bug has been marked a duplicate of bug 1666421
kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop
--
You received this bug notification because you are a member of Kernel
Packages, which is
This is now fixed on zesty and xenial stable-phone-overlay PPA, but
notably not on normal xenial. xenial SRUs could still be affected,
although SRUs having affected tests run during build time might be rare.
--
You received this bug notification because you are a member of Kernel
Packages, which
** Changed in: qtdeclarative-opensource-src (Ubuntu RTM)
Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)
** Changed in: qtdeclarative-opensource-src (Ubuntu RTM)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Pa
(...and meanwhile the workarounded builder kernel not using the new
setting is still required)
** Also affects: qtdeclarative-opensource-src (Ubuntu RTM)
Importance: Undecided
Status: New
** Changed in: qtdeclarative-opensource-src (Ubuntu RTM)
Status: New => Triaged
--
You rec
This is fixed in zesty in Qt 5.7.1.
It should be eventually part of also LTS Qt 5.6.3 release some time
later in first half of 2017.
** Changed in: qtdeclarative-opensource-src (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
P
However, this has again regressed on zesty including 4.9.0-16-generic.
On 4.8.0-38.41:
CONFIG_TOUCHSCREEN_ELAN=y
CONFIG_PINCTRL_CHERRYVIEW=y
-> keyboard and touch work fine
On 4.9.0-16.17:
CONFIG_TOUCHSCREEN_ELAN=m
CONFIG_PINCTRL_CHERRYVIEW=m
-> broken again
** Changed in: linux (Ubuntu Zesty)
Tested:
4.8.0-38.41 - everything works fine, touch and keyboard
4.4.0-63.84 - touch screen is now correctly also recognized (but 4.4 kernel
didn't have mature support anyway)
** Tags removed: verification-needed-xenial verification-needed-yakkety
** Tags added: verification-done-xenial verifica
I upgraded to zesty, and just clarifying that indeed I have working
keyboard and touchscreen with the special 4.8.0-28.30~lp1630238 kernel
and not working still with archive 4.8.0-30 or 4.9.0-11.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Again on my Ubuntu phone so can't test much but yes as seen in the diff
the 'y' was dropped between 14-17 in favor of 'm' which caused this bug.
Then sometime earlier a missing CONFIG parameter for touchscreen was
there, a separate problem, but after that got fixed everything (both
keyboard and to
I can't test easily since 16.04 live USB doesn't boot on Chromebooks
because of gfxboot problem.
I did have 16.04 install at one point (transferred complete installation
in from USB) and yes I needed external keyboard. That would make sense
if 'm' was used also back then while 'y' is required.
--
Thanks Joseph, seems to work fine! I'm now typing (and using touch) on
this machine:
$ uname -a
Linux c11 4.8.0-28-generic #30~lp1630238 SMP Mon Dec 5 20:16:48 UTC 2016 x86_64
x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
There have been multiple kernel versions released, is the (in progress)
fix committed somewhere?
I'm still stuck on sticking to the 4.8.0-14 kernel for functioning
keyboard/touch.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
It sounded to me the old value would be around 41 or so, and the
motivation to increase was a need to have it only slightly bigger?
Meanwhile, the Qt patch is about freeing "2 more bits" so maybe 46 or 47
would work too, unless 48 is the magical "good" value that is wanted to
be had.
--
You recei
I've now also asked on #ubuntu-kernel if CONFIG_ARM64_VA_BITS=48 is here
to stay for the 4.4 kernel or not, pointing to this bug. It sounds like
no-one is currently considering going back to the 4.2 kernel on the
arm64 builders at least.
Meanwhile I'm collecting rebuilds of qtdeclarative-abi-5-6-1
Otherwise "ok" so far regarding rebuilds but unmodified UITK starts to
fail two subtests on arm64: bug #1631941. Those did pass before the
builder kernel update, and it's now not sure where those new failures
come from. But they do happen on both xenial and yakkety:
https://launchpad.net/~ci-train-
Unfortunately the upstream fix seems to, while fixing arm64, cause
segfaults in Unity 8 on armhf and i386:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-ci-train-ppa-service-2055/yakkety/armhf/u/unity8/20161007_180848@/log.gz
https://
The linux kernel part of this is setting of CONFIG_ARM64_VA_BITS=48.
Also reverting of just that in the 4.4 kernel would 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/1630906
Title:
xenial and yakkety needed symbol updates but now they have compiled and
work at least on desktop, and the arm64 build finished so it's likely
the arm64 build issue would be solved now. I've asked QA to look into
it.
--
You received this bug notification because you are a member of Kernel
Packages
Albert pointed to https://codereview.qt-project.org/#/c/169892
-> https://bileto.ubuntu.com/#/ticket/2055 (xenial and yakkety currently
building)
I need to stop for today but if someone has time please check if 5.4
backport is possible.
--
You received this bug notification because you are a me
Correction to the code url:
http://code.qt.io/cgit/qt/qtdeclarative.git/tree/src/qml/jsruntime/qv4object.cpp?h=5.6.2#n184
(5.6.1 branch doesn't exist over there, but code seems unchanged)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
For completeness, also the other copy-pastes I made:
Thread 1 "qmlplugindump" received signal SIGSEGV, Segmentation fault.
QV4::Object::defineReadonlyProperty (this=this@entry=0x0, name=0x450bf8,
value=...) at jsruntime/qv4object.cpp:184
184 jsruntime/qv4object.cpp: No such file or directory.
I got a temporary access (now revoked) to an arm64 box where I could
reproduce the segfault by running qmlplugindump.
Here's the backtrace:
QV4::Object::defineReadonlyProperty (this=this@entry=0x0, name=0x450bf8,
value=...) at jsruntime/qv4object.cpp:184
184 jsruntime/qv4object.cpp: No such f
Public bug reported:
Builders were changed from wily to xenial (4.4) kernel for arm64, and
likely due to this the following kind of errors started happening:
https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64
.ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz
They
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1630238/+attachment/4754284/+files/WifiSyslog.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/bug
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1630238/+attachment/4754274/+files/IwConfig.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/16
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1630238/+attachment/4754273/+files/CurrentDmesg.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
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1630238/+attachment/4754281/+files/PulseList.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/
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1630238/+attachment/4754278/+files/ProcEnviron.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/b
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1630238/+attachment/4754282/+files/RfKill.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/1630238
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1630238/+attachment/4754275/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1630238/+attachment/4754272/+files/CRDA.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/1630238
Ti
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1630238/+attachment/4754279/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1630238/+attachment/4754283/+files/UdevDb.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/1630238
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1630238/+attachment/4754280/+files/ProcModules.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/b
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1630238/+attachment/4754277/+files/ProcCpuinfo.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/b
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1630238/+attachment/4754276/+files/Lspci.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/1630238
Public bug reported:
16.10 beta 2, as installed fresh, has working keyboard and touchscreen
on my Acer Chromebook R11. However, after dist-upgrade they're lost, so
touchscreen doesn't work and I need to use external keyboard.
Looking at config diff, the likely culprit is:
+CONFIG_PINCTRL_AMD=y
C
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1630238/+attachment/4754271/+files/AlsaInfo.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/16
I was pretty happy with Ubuntu's 4.8 kernel too since the keyboard
continued working, however unfortunately it now has stopped again at
4.8.0-17-generic and for some reason it still doesn't work when booting
to 4.8.0-11-generic with which I'd assume I have typed with the internal
keyboard as that w
Public bug reported:
I think this may have lost in the noise of bug #1609745, and I'm
uncertain how to change the bug anymore to affect yakkety's to-be-kernel
instead of bisecting 4.4 functionality of the option which is a
different topic.
So this bug is now about that the fact that the 4.8.0-8.9
** Tags added: r11
--
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/1609745
Title:
Touch screen not working on Acer Chromebook R11,
CONFIG_TOUCHSCREEN_ELAN not enabled on mainline 4.7 ke
It has never worked and I'm already using the latest upstream mainline
kernel.
The bug has the tag kernel-bug-exists-upstream already.
See upstream bug report for more details.
Thank you!
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notificatio
The actual problem/bug is that for some reason the mainline Ubuntu 4.7
kernel lacks CONFIG_TOUCHSCREEN_ELAN. In 4.4 Ubuntu kernel
CONFIG_TOUCHSCREEN_ELAN is defined, but the touchscreen doesn't work.
However with mainline Ubuntu kernel sources, and CONFIG_TOUCHSCREEN_ELAN
enabled manually via a re
Actually there was a change: with mainline 4.7 kernel there is no trace
of the touchscreen anymore in dmesg or xinput.
--
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/1609745
Title:
Touch
** Bug watch added: Linux Kernel Bug Tracker #151521
http://bugzilla.kernel.org/show_bug.cgi?id=151521
** Also affects: pulseaudio via
http://bugzilla.kernel.org/show_bug.cgi?id=151521
Importance: Unknown
Status: Unknown
** Project changed: pulseaudio => kernel
--
You received t
** Bug watch added: Linux Kernel Bug Tracker #151531
http://bugzilla.kernel.org/show_bug.cgi?id=151531
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=151531
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member o
apport information
** Description changed:
Touch screen seems to be identified as far as I can see, but there's no
working input. I've tried among else xinput test-xi2, reattach command
but it seems simply non-functional for whatever reason.
It works on the ChromeOS side.
I'll add
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1609745/+attachment/4714585/+files/ProcEnviron.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/b
There is updated information available from the coreboot/Chromebook
community:
Baytrail/Braswell devices seem to have audio issues when booting via
RW_LEGACY, because depthcharge (the ChromeOS payload) is still doing
some initialization to the audio codec
--
You received this bug notification be
Thanks, I was meaning to do that next. No change with audio on 4.7
kernel (1 of 3 hw support bugs problems did get fixed with 4.7 though).
It is likely this is not pulseaudio problem, as if pulseaudio does not
detect any sound hardware the problem is likely at a lower level.
** Tags added: kernel
No change on 4.7 mainline kernel.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
1 - 100 of 159 matches
Mail list logo
