elhoir, while you are welcome to wait for whenever a maintainer may
respond, given this issue has been reported a regression, it is known
that it helps developers expedite a fix if the offending commit(s) are
identified via bisect.
--
You received this bug notification because you are a member
yoshiki2, thank you for reporting this and helping make Ubuntu better.
Please execute the following command only once, as it will automatically
gather debugging information, in a terminal:
apport-collect 1819242
** Package changed: linux-signed-hwe (Ubuntu) => linux (Ubuntu)
** Changed in:
yoshiki2, it will help immensely if you use Ubuntu with the computer the
problem is reproducible with and file a new report via a terminal to provide
necessary debugging logs:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a
yoshiki2, it will help immensely if you use Ubuntu with the computer the
problem is reproducible with and file a new report via a terminal to provide
necessary debugging logs:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a
elhoir:
1)
Please ensure you are not using non-default kernel parameters. As per most
recent dmesg remove:
acpi_osi=Linux modprobe.blacklist=amdgpu crashkernel=384M-:128M
crashkernel=384M-2G:128M,2G-:256M crashkernel=512M-:192M crashkernel=512M-:192M
crashkernel=512M-:192M
2)
Keep testing
elhoir, the next step is to fully commit bisect from Ubuntu kernel
4.19.0-7.8 to Ubuntu kernel 5.0.0-7.8. This will allow for a direct
review of the offending commit(s) for either reverting, or further
improvements. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection
elhoir:
1)
>"yes, its a copy paste of crash part of dmesg, not entire output."
Then attach a full dmesg as previously advised.
2)
>"GPU (RX 470) is quite new. I tested Ubuntu Cosmic and Ubuntu Dingo."
To confirm, using only the RX470, it worked fine in Cosmic and Dingo.
However, while using
elhoir:
1)
Regarding the dmesg posted in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/comments/20 did
you cut/snip it? Please ensure all logs are attached in their entirety (no
cuts, snips, etc.).
2)
To confirm a regression, regarding only the current AMD graphics card
elhoir:
Without evidence (screenshots, recording, logs, etc.) developers cannot
root cause, and fix your issue. Hence, when will you be posting the
video you said will be captured as per your comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/comments/13
?
** Tags added:
elhoir:
1)
Regarding your comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/comments/9 :
>" No, never, but i never used amdgpu driver before"
I'm afraid this didn't answer my question. Which release precisely did
you have to start using nomodeset to boot?
2)
Regarding your
elhoir:
1) It looks like you installed Ubuntu originally with 11.10, and then
upgraded all the way to 19.04. To clarify, have you always had to use
the kernel parameter nomodeset to boot since 11.10?
2) With all of the following kernel parameters removed (and any
WORKAROUND or other non-default
elhoir (jfarroyo82), it is most helpful if you file a new report. If the
nomodeset WORKAROUND lets you boot, please file a new report via a terminal:
ubuntu-bug linux
Else, use:
https://bugs.launchpad.net/ubuntu/+source/linux/+filebug
Please feel free to subscribe me to it.
--
You received
Kamal Pandey, one may update the BIOS using Windows temporarily
following https://help.ubuntu.com/community/BIOSUpdate .
--
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/1299104
Title:
** Tags removed: bios-outdated-1.6.1 kernel-bug-exists-upstream-4.7
needs-upstream-testing
** Tags added: kernel-bug-exists-upstream-5.0-rc8 latest-bios-1.6.1
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of
adin:
1)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605433/comments/34
>"To clarify, when you first installed Ubuntu 16.04 were you able to toggle the
>touchpad?"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605433/comments/35
>"I was able to toggle it on the command line or
adin:
1) To clarify, when you first installed Ubuntu 16.04 were you able to
toggle the touchpad?
2) Have you tested any release older than 16.04?
3) To keep this relevant to upstream, one would want to periodically
check for, and test the latest mainline kernel (now 5.0-rc8) as it is
released.
** No longer affects: linux (Ubuntu)
** Project changed: linux => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Medium => Undecided
** Changed in: linux (Ubuntu)
Status: Confirmed => New
** Changed in: linux (Ubuntu)
Remote watch: Linux Kernel Bug Tracker #42843 => None
** No longer affects: linux (Ubuntu)
** Project changed: linux => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Medium => Undecided
** Changed in: linux (Ubuntu)
Status: Confirmed => New
** Changed in: linux (Ubuntu)
Remote watch: Linux Kernel Bug Tracker #46721 => None
Stephan Berger, it will help immensely if you use Ubuntu with the computer the
problem is reproducible with and file a new report via a terminal to provide
necessary debugging logs:
ubuntu-bug linux
Please feel free to subscribe me to it.
** Changed in: linux (Ubuntu)
Importance: Undecided
opensas:
1)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816947/comments/43
>"Then I tried with several versions from the upstream kernels..."
Which upstream kernels did you test precisely?
2)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816947/comments/46
>"Any idea about
** Tags added: needs-bisect- needs-upstream-testing
--
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/1816947
Title:
[Dell XPS L321X] Touchpad not working after last apt-get upgrade
opensas, the next step is to fully commit bisect from 4.13.13 to 4.15.
This will allow for a direct review of the offending commit for either
reverting, or further improvements. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection ? This article was
written for folks
** Tags added: regression-potential
** Description changed:
Hello.
Running Ubuntu 18.04 (4.15.0-22-generic), after plugging my TP-LINK TL-
- WN722N into the USB port, the CPU usage goes to 100%, and there are
- multiple reports of "stack traces" in dmesg.
+ WN722N Version 1.10 into a USB
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
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/1792672
Title:
Regression: acpi reports battery state incorrectly
opensas:
To further narrow the regression, in Ubuntu 18.04 or higher, if you
install kernel 4.13.3 from https://wiki.ubuntu.com/Kernel/MainlineBuilds
does the touchpad work again?
** Tags removed: regression-potential
** Tags added: regression-release
--
You received this bug notification
** Tags removed: kernel-bug-exists-upstream latest-bios-1.2.2
** Tags added: bios-outdated-1.6.1 needs-upstream-testing
** Description changed:
- Installed ubuntu 15.10 on alienware 13, touchpad is showing up in xinput list
as expected, but is totally unresponsive. Was working fine on 14.05
-
** Tags removed: kernel-bug-exists-upstream latest-bios-1.2.15
** Tags added: bionic bios-outdated-1.6.1 cosmic needs-upstream-testing
** Summary changed:
- [Dell Alienware 17R3] enable/disable touchpad not working
+ [Dell Alienware 17 R3] FN+F11 Enable/Disable touchpad not working
** Changed
opensas:
To confirm the regression point, could you please test a live
environment of https://wiki.ubuntu.com/ArtfulAardvark/ReleaseNotes and
advise to the results?
** Description changed:
- The touchpad doesn't work.
+ The touchpad doesn't work unless the cursor is moved slowly.
opensas:
1) To advise, you don't have to apport-collect any further unless
specifically requested to do so.
2) Does the touchpad work in the live environment of 18.04 without using
any WORKAROUND?
--
You received this bug notification because you are a member of Kernel
Packages, which is
opensas, please advise to all of the following:
1) When discussing this issue, please keep it to only one machine (the
Dell XPS 13 L321X, not multiple) and Ubuntu (not popos! or some other
unsupported distro, unofficial flavor, etc.).
2) Regarding this issue with the Dell XPS 13 L321X, is this
** Description changed:
+ The touchpad doesn't work.
- already filed at:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1096046
-
- check: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
- synaptics/+bug/1096046/comments/33
-
- affects:
** Tags removed: cosmic wayland-session
** Attachment removed: "WifiSyslog.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/+attachment/5239110/+files/WifiSyslog.txt
** Attachment removed: "UdevDb.txt"
Tom Louwrier, this report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/comments/82
regarding you no longer have the hardware. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line
Eugene Savelov, RedHat bug 454131 was opened and closed by you (not someone who
represents upstream or RedHat):
https://bugzilla.redhat.com/show_activity.cgi?id=454131
Despite this, regarding a way forward here on Launchpad, if you want your
problem addressed, it will help immensely if you use
Eugene Savelov, having a WORKAROUND on different hardware, and an unconfirmed
assumption of root cause, doesn't cause this report to be Invalid. For more on
Status, please see:
https://wiki.ubuntu.com/Bugs/Status
Despite this, given Tom Louwrier is the original reporter, if he would
like to
** Description changed:
hi
Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips), updated
twice a day at the moment.
Linux seems not to recognize the keyboard in my laptop well. Starting early
in the boot process (well before X kicks in) I see error messages on the
** Tags removed: kernel-bug-exists-upstream
** Tags added: needs-upstream-testing regression-potential
--
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/1812561
Title:
[MacBookPro11,5]
Selwyn, as the latest version of Ubuntu is based on 4.19.x, to confirm
this is already resolved in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?
--
You received this bug notification because you are a member of Kernel
Packages, which is
Selwyn, one may follow the below to confirm results for your hardware:
https://wiki.ubuntu.com/Kernel/KernelBisection
--
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/1812561
Title:
Selwyn:
>"...all information is in the attachments of the post."
No, its not. You posted one dmesg (multiple requested in article) on a
now old version of upstream kernel (i.e. nearly impossible to keep
upstreams attention as you aren't using a version supported upstream).
>"Anyways this is
Selwyn, given the workaround never worked, this isn't confirmed a usb
problem (although could still be due to usb).
Hence, this report would still be missing the vast majority of the
information requested in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812561/comments/5
in order for a
Selwyn:
1) >"...the workaround is invalid..."
What update was applied specifically that afterwards this stopped
working?
2) >"...should I retry sending the email? I did not get any reply."
Based on
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812561/comments/19
you would never get a
massimiliano, it will help immensely if you use Ubuntu with the computer the
problem is reproducible with and file a new report via a terminal to provide
necessary debugging logs:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a
** Description changed:
Similar bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/
The first time suspending works great but after that suspending causes
the laptop to wake up regardless of the method used to suspend.
+
+ WORKAROUND: Disable XHC1 prior to sleeping:
+ #
Marko Muehlberg (markom2), would you be able to confirm the commit from
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1455cf8dbfd06aa7651dcfccbadb7a093944ca65
is the root cause for your issue by testing a revert of it following
Selwyn:
"! I could not send the email though, the email address "linux-
u...@vger.linux.org" seems invalid."
If you post the email source of the message sent, and what you may have
received in a response, then this may be assessed.
--
You received this bug notification because you are a member
Selwyn, the issue you are reporting is an upstream one. Could you please
report this problem following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO: linux-usb CC: Mathias Nyman and Greg Kroah-Hartman)?
This article was written for folks who
udippel, it will help immensely if you use Ubuntu with the computer the problem
is reproducible with and file a new report to provide necessary debugging logs
via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a
** Description changed:
- The em28xx module is used with a lot of TV and video hardware, and is
- needed also for the video grabber Terratec Grabster AV350MX. However,
- with this external, USB connected device the wrong settings are applied,
- allowing only a (good quality) video picture, but no
Selwyn, could you please provide all of the missing information from
https://wiki.ubuntu.com/DebuggingKernelSuspend ?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Selwyn, thank you for reporting this and helping make Ubuntu better.
In order to allow additional upstream mainline kernel developers to examine the
issue, at your earliest convenience, could you please test the latest mainline
kernel? Please keep in mind the following:
1) The one to test is in
Tudor Holton:
Given you've tested the latest mainline kernel, latest BIOS, and assuming all
the previous test results are the same when not using any non-default kernel
parameters as noted in your Bug Description:
i915.i915_enable_rc6=1 "acpi_osi=!Windows 2013"
it appears one is to wait while
** Tags removed: kernel-bug-exists-upstream-4.2-rc4 needs-upstream-testing
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-5.0-rc2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Tudor Holton, to confirm a WORKAROUND, in both kernel Ubuntu 4.20 and
mainline 5.0-rc2:
1) If you remove the module iwlwifi prior to suspend, after resuming and
before enabling the module, do you still have crashes, or an issue
successfully resuming?
2) If 1) was successful, if you then enable
** Tags removed: bios-outdated-a17
** Tags added: latest-bios-a17
--
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/1472832
Title:
Suspend issue with Dell Venue 11 Pro 7140
Status in
Michael Gratton:
1) To keep this relevant to upstream, one would want to periodically
check for, and test the latest mainline kernel (now 5.0-rc2) as it is
released. Could you please advise to the results?
2) Did you contact upstream as noted in
Selwyn (siilwyn), it will help immensely if you use Ubuntu with the computer
the problem is reproducible with and file a new report via a terminal to
provide necessary debugging logs:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you
(In reply to Pander from comment #3)
> Christopher, are you still experiencing this bug?
Pander, the Radeon graphics card in my computer died, so I replaced it
with an Nvidia card. I didn't experience the bug again after that.
--
You received this bug notification because you are a mem
Steven Ellis, for you personally:
1) Did this problem not occur in a prior Ubuntu or kernel release, and
if so which?
2) If this issue has always occured, could you please advise to the
earliest kernel you tested?
3) To keep this relevant to upstream, one will want to test the latest
mainline
** Summary changed:
- amd_iommu conflict with Marvell Sata controller
+ amd_iommu conflict with Marvell 88SE9230 SATA Controller
--
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/1810239
** Description changed:
- This bug is to confirm that the Marvell 88SE9230 chipset bug presents
- under AMD's IOMMU implementation with Ubuntu 18.04 and the latest HWE
- Kernel
+ Booting with kernel 4.18.0-13.14~18.04.1-generic shows errors:
+
Pablo Rossy Bernardes Mozinho Ferreira (santoross08-p), it will help immensely
if you use Ubuntu with the computer the problem is reproducible with and file a
new report via a terminal to provide necessary debugging logs:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You
** Tags removed: kernel-bug-exists-upstream
** Tags added: needs-upstream-testing
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
** Changed in: linux
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** No longer affects: linux (Ubuntu)
** Project changed: xserver-xorg-driver-ati => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: High => Undecided
** Changed in: linux (Ubuntu)
Status: Confirmed => New
** Changed in: linux (Ubuntu)
Remote watch: freedesktop.org Bugzilla
Eugene Kosogin, here are some ways to engage ASUS on this particular
issue:
1) Advise support the issue is reproduced using Windows 10 x64 (OS precisely
quoted from the ASUS website below) so Consumer Support can't disclaim
responsibility. You will likely get the best traction with them if this
Steven Ellis (steven-openmedia), it will help immensely if you use the computer
the problem is reproducible with to provide necessary debugging logs by filing
a new report in Ubuntu via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
** Summary changed:
- Marvell Sata
** Changed in: linux (Ubuntu)
Importance: Medium => Low
--
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/1089768
Title:
When IOMMU enabled, devices attached to Marvell 88SE9128
** Changed in: linux (Ubuntu)
Importance: High => Undecided
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
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/571770
Hey all, there is so much technical jargon here and on that github page.
I have an HP Pavilion so I'm trying to remove that iio sensor-proxy, but
I'm a bit confused. Where should I be looking on that github page for
directions to remove the iio sensor-proxy? Thanks!
--
You received this bug
Following up that I'm experiencing the same issue on an MSI B450 AM4
motherboard with the same realtek chipset.
--
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/1801540
Title:
Microphone
Sam (sr897), as the root cause of this report isn't confirmed to be solely
dependent on the motherboard, it is most helpful if you use the computer the
problem is reproducible with, and provide necessary debugging logs by filing a
new report with Ubuntu via a terminal:
ubuntu-bug linux
Please
Louis (darkenlx), it will help immensely if you use the computer the problem is
reproducible with, and provide necessary debugging logs by filing a new report
with Ubuntu via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
** Description changed:
The wifi connection on
** No longer affects: linux (Ubuntu)
** Project changed: kernel => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Medium => Undecided
** Changed in: linux (Ubuntu)
Status: Fix Released => New
** Changed in: linux (Ubuntu)
Remote watch: Linux Kernel Bug Tracker #198715 =>
** Tags removed: kernel-bug-exists-upstream
** Tags added: needs-upstream-testing
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags removed: kernel-bug-exists-upstream
** Tags added: needs-upstream-testing
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hubert Hesse, to confirm this is resolved for you in Ubuntu, could you
please either upgrade your 16.04 enablement stack as per
https://wiki.ubuntu.com/Kernel/LTSEnablementStack or test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?
** Tags removed: bios-outdated-1.42
**
Joseph, to confirm this is already resolved in Ubuntu, could you please
test for this via http://cdimage.ubuntu.com/daily-live/current/ and
advise to the results?
** Summary changed:
- Keyboard and Mouse don't work with latest Kernel
+ [Dell Inspiron 3847] USB devices don't work with kernel
** Tags removed: apport-collected cosmic
** Tags added: trusty
--
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/1564463
Title:
Joystick Dragonrise Axes confused in Ubuntu 14.04
Status in
Marc Rene Schädler, as per upstream
https://bugzilla.kernel.org/show_bug.cgi?id=198715#c97 a patch was
merged upstream. Hence, to confirm your issue is resolved upstream,
could you please revert any custom patched kernels, and test
https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.8/ (no custom
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Tags added: needs-upstream-testing
--
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/1792672
Title:
Regression:
** Description changed:
The touch screen on my HP ENVY x360 15-bq102ng does not work with stock
kernel or with mainline kernel 4.16-rc3.
marc@snapbug:~$ xinput
⎡ Virtual core pointerid=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer
** Tags removed: latest-bios-1.30
** Tags added: bios-outdated-1.35
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Chris Klosowski (cklosowski), as this report is closed, if you would like your
issue reviewed, please use the computer the problem is reproducible with, and
provide necessary debugging logs by filing a new report with Ubuntu via a
terminal:
ubuntu-bug linux
Please feel free to subscribe me to
Tudor Holton:
1) As is known, folks with the same computer manufacturer and model can have
different hardware under the hood, and/or different revisions of the same
underlying hardware (i.e. one person can reproduce something another cannot).
Hence, it wouldn't hurt to test the latest BIOS
** Tags removed: bios-outdated-a09
** Tags added: bionic bios-outdated-a17 cosmic
--
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/1472832
Title:
Suspend issue with Dell Venue 11 Pro 7140
** No longer affects: linux (Ubuntu)
** Project changed: linux => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: High => Undecided
** Changed in: linux (Ubuntu)
Remote watch: Linux Kernel Bug Tracker #44161 => None
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
--
Public bug reported:
Ubuntu 18.10
GNOME Shell 3.30.1
Cinnamon 3.8.8
Hardware: ASUS Transformer Mini.
Also confirmed problematic for Yoga Series tablet/laptop hybrids.
(https://github.com/linuxmint/cinnamon-settings-daemon/issues/188)
Screen rotation works fine, but tablet coords including
I'll try to to the bisection this coming weekend.
--
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/1782934
Title:
XPS 13 9350 black screen with kernel versions > 4.15.0-20-generic
Status
Interestingly, this ONLY happens with Gnome.
I've been running i3wm now for days with zero issues.
I guess this is telling me it's time to choose a lighter window manager
alternative? :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
apport information
** Description changed:
Hi there folks sorry if it's inappropriate to report a bug in an
upstream release candidate kernel, but as a suggested test / fix for
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796743 I was told
to install an upstream kernel, which I
Also attaching nouveau driver info a-la modinfo.
** Attachment added: "nouveau-modinfo.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799180/+attachment/5206401/+files/nouveau-modinfo.log
--
You received this bug notification because you are a member of Kernel
Packages, which
Also marked this for re-triage since I have some usable evidence and a
smoking gun.
** Summary changed:
- Ubuntu 18.10 / Linux 4.19 -rc7/8 - System slows / stops
+ Ubuntu 18.10 / Linux 4.19 -rc7/8/Final - System slows / stops
--
You received this bug notification because you are a member of
I'll bet dollars for donuts this is the nouveau driver. I see a bunch of
lines like this as the system slows to a crawl (Also there's a
juddering/tearing band in the center of the screen)
Oct 27 17:01:44 yamato kernel: [ 402.710539] nouveau :01:00.0: DRM:
base-0: timeout
Full kernel log
Feel free to close this if it makes sense. I am researching how best to
report this upstream. The documentation on reporting kernel bugs makes
it clear you need to identify the affected subsystem or your bug will be
bit-bucketed. More hard core log diving is called for :)
** Changed in: linux
apport information
** Tags added: apport-collected
** Description changed:
Hi there folks sorry if it's inappropriate to report a bug in an
upstream release candidate kernel, but as a suggested test / fix for
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796743 I was told
to
Public bug reported:
Hi there folks sorry if it's inappropriate to report a bug in an
upstream release candidate kernel, but as a suggested test / fix for
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796743 I was told
to install an upstream kernel, which I did.
When I run with that
Yay this is in fact fixed in 4.19-rc7! Thanks very much this was a real
show stopper :)
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Public bug reported:
If the machine goes to sleep, either because I close the lid or because
it idles too long, it ends up in a weird state when I try to resume. If
I press the power/Alien button, the fan runs and the keyboard/trackpad
light up but nothing happens.
Ultimately I need to hard
** Changed in: linux (Ubuntu)
Importance: Medium => Low
--
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/1589418
Title:
udisksd high CPU usage
Status in linux package in Ubuntu:
201 - 300 of 20143 matches
Mail list logo
