** Tags removed: needs-reverse-bisect
** Tags added: needs-bisect
--
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/1768139
Title:
Kernel crash when booting laptop with hdmi monitor connect
** Tags removed: kernel-bug-exists-upstream
** Tags added: needs-apport-collect needs-upstream-testing
** 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://bug
Release EOL, and don't have hardware anymore.
** No longer affects: broadcom-sta
** Changed in: bcmwl (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/
Thomas Diesenreiter, to advise, given you have the hardware, it is best
if you test reverting/adding of the potential regression commit, to
confirm it is, in fact, the correct commit. When you aren't as busy,
feel free to check out the bisect article as it is written for folks who
know nothing abou
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** 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/bugs/1771204
Title:
Ho
Anders Kvist:
>"Christopher, I believe the solution is in the redhat bug mentioned earlier.
https://bugzilla.redhat.com/show_bug.cgi?id=1565131";
What is most helpful is if one confirms with their hardware via adding
and reverting the potential fix commit that it does indeed address their
issue.
** Tags added: bios-outdated-208 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/1490130
Title:
[Asus X455LD] Elantech touchpad stops working after suspend
Status
marvin:
1) Regarding the scaling and mouse issues, these are outside the scope of this
report. Hence, feel free to file a separate report about each one by ensuring
you have the package xdiagnose installed, and that you click the Yes button for
attaching additional debugging information via a t
** Tags removed: regression-release
** Tags added: xenial
--
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/1768208
Title:
[Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness
Status
** Description changed:
The screen brightness cannot be changed.
In 16.04, I could change the brightness via:
xrandr --output eDP-1 --brightness 0.7
+
+ WORKAROUND: Execute at a terminal:
+ xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8
---
ApportVersion: 2.20.9-0ubuntu7
Julian Bieringer-Hinterbuchinger:
1) Regarding apport-kde crashing, please file a new report about this via a
terminal:
ubuntu-bug apport-kde
2) Regarding this report, as an alternative, could you please boot into
a live environment of http://cdimage.ubuntu.com/daily-live/current/ and
then run t
Julian Bieringer-Hinterbuchinger, unfortunately, it didn't appear to
work.
As per below, what is supposed to happen is a web browser opens to a
Launchpad URL where you log in, and then give permission to upload the
requested data.
Did you do all of these steps?
apport-collect 1766940
The authori
Battant, 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 available from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind
the following:
1) The one to
Bob, the next step is to fully reverse commit bisect from kernel 4.16.6
to 4.17-rc6, in order to identify the earliest good kernel commit,
preceded immediately by the first bad one. This will allow for a more
expedited analysis of the root cause of your issue. Could you please do
this following htt
** Tags added: kernel-fixed-upstream-4.17-rc6 needs-reverse-bisect
--
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/1767180
Title:
Bluetooth of the Asus Maximus X Hero Wifi AC motherboard
Battant, please stop apport-collecting to this report. Thanks!
** Attachment removed: "AlsaInfo.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322068/+attachment/5145139/+files/AlsaInfo.txt
** Attachment removed: "CRDA.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
Battant, thank you for reporting this and helping make Ubuntu better.
Could you please run the following command a terminal as it will automatically
gather and attach updated debug information to this report:
apport-collect 1773643
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu)
**
Frank Winklmeier:
>"The instructions at https://wiki.ubuntu.com/Kernel/MainlineBuilds don't seem
>to work anymore for recent kernels: Unpacking
>linux-modules-4.17.0-041700rc6-generic (4.17.0-041700rc6.201805202330) ...
dpkg: dependency problems prevent configuration of
linux-headers-4.17.0-041
Frank Winklmeier, 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 available from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind
the following:
1) T
Frank Winklmeier, thank you for reporting this and helping make Ubuntu
better.
Could you please run the following command once from a terminal by ensuring you
have the package xdiagnose installed, and that you click the Yes button for
attaching additional debugging information:
apport-collect 17
Antoine Sibold:
1) Does using the the following kernel boot parameters provide a WORKAROUND:
acpi_osi= acpi_backlight=legacy
2) To see if this still affects upstream, could you please test the
latest mainline kernel (now 4.17-rc6) and advise to the results? Also,
to keep this issue relevant to up
Battant (mparchet), it will be helpful if you filed a new report via a terminal:
ubuntu-bug linux
Feel free to subscribe me to it.
** Attachment removed: "WifiSyslog.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322068/+attachment/4387869/+files/WifiSyslog.txt
** Attachment remo
Zakhar, stock Ubuntu kernel.
--
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/1682921
Title:
sluggish system, kernel errors on Inspiron 1525
Status in linux package in Ubuntu:
Invalid
Zakhar (alainb06), if you do end up testing, please file a new report with that
hardware so that it may tracked downstream via a terminal:
ubuntu-bug linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
Kevin Otte, thanks for quickly responding you no longer have the
hardware.
** Changed in: linux (Ubuntu)
Status: Incomplete => 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
** 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/1767356
Title:
[Compaq Presario A900 Notebook PC] ~5 minutes to boot or shutdown
*** This bug is a duplicate of bug 1682921 ***
https://bugs.launchpad.net/bugs/1682921
** This bug has been marked a duplicate of bug 1682921
sluggish system, kernel errors on Inspiron 1525
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
Kevin Otte, could you please advise if using the following kernel boot
parameter provides a WORKAROUND:
video=SVIDEO-1:d
** Tags added: artful kernel-bug-exists-upstream-4.15-rc8 latest-
bios-a17 regression-release
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You rec
deeks9000:
To advise, there is no guarantee that using video=SVIDEO-1:d as a
WORKAROUND will continue to work going forward as newer kernels are
updated.
Hence, you would still want to remove your WORKAROUND and fully bisect
the problem so that the developers can review and fix as applicable.
--
** Description changed:
- SCENARIO: I have just upgraded to 18.04 from 17.10
-
- PROBLEM PACKAGE (?): linux-modules-4.15.0-20-generic
+ After upgrading to 18.04 from 17.10, it now takes ~5 minutes to boot or
+ shutdown.
REPORT FROM 'dmesg' shows this typical error:
-
[ 899.040146] [drm:d
Sandy Patterson:
>"Let me know if I can do any more testing."
Please reach out to the Ubuntu Kernel team via
https://wiki.ubuntu.com/KernelTeam for testing build requests that
revert the offending commit(s)/apply the fix commit(s).
--
You received this bug notification because you are a member
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
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/1768139
Title:
Kernel crash when booting laptop with hdmi monitor connec
Sandy Patterson, a couple follow ups:
1) Regarding kernel parameter acpi_osi=!Windows 2015 could you please
advise why you need to use it, if at all? If you don't, you will want to
remove it during your bisect tests to mimic a default install.
2) Regarding your Bug Description change, you change
Sandy Patterson:
>"I figured out the modules thing. It seems older kernels don't have
separate debs for the modules. I needed the extra package regardless (if
both linux-modules-extra and linux-image-extra were missing I don't
think the test is right)."
To clarify, you were able to test 4.15.0-17
marvin:
Regarding xrandr, one may use it in 18.04 as per below. Were you stating
that when you attempt to use the command that it worked in 16.04, but
the same command doesn't work in 18.04?
xrandr
Screen 0: minimum 320 x 200, current 1288 x 703, maximum 16384 x 16384
VGA-1 connected primary 1288
Sandy Patterson:
Regarding 4.15.0-17.18 not having linux-modules-* here are a couple
options:
1) Test the next oldest version until you can do a proper test.
2) Contact the Ubuntu Kernel Team via https://wiki.ubuntu.com/KernelTeam
and inquire if the linux-modules-* can be provided for that versi
Julian Bieringer-Hinterbuchinger, could you please run the following command
once from a terminal in order to attach additional debugging information:
apport-collect 1766940
** Changed in: xorg (Ubuntu)
Importance: Undecided => Low
** Changed in: xorg (Ubuntu)
Status: Confirmed => Inco
** Summary changed:
- bluethoot
+ bluetooth
** Package changed: xorg (Ubuntu) => bluez (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1768005
Title:
bluetooth
Status in bluez
marvin:
1) When you state "I could only adjust it with the terminal and xrandr",
what terminal command and what do you do with xrandr precisely?
2) To clarify, were you able to adjust the screen brightness prior to
Ubuntu 16.10? If so, which specifically and how?
3) To advise, when changing the
** Description changed:
When I boot a Dell Inspiron 7559 with an external monitor connected to
- the hdmi port I get a crash on bootup. I can see the following stack
- trace in journalctl:
-
+ the hdmi port, it consistently shows only a blank screen after grub and
+ I have to hard power off the
Sandy Patterson a few follow up questions:
1) Does the OS crash consistently if you boot up with the external
monitor plugged in, or does it only happen sometimes? If sometimes, how
often specifically?
2) Does the OS crash if you connect the external monitor after fully
booting up and logging in?
Sandy Patterson:
>"penalvch, I'm having a bit of trouble. Is there instructions on
building the ubuntu kernel from git?"
Yes, the instructions previously provided.
>"I wasn't able to find a mainline kernel which fails."
Without providing which kernels you tested nobody may understand why
this h
** Tags removed: kernel-bug-exists-upstream-4.17-rc4 needs-filing-upstream
** Tags added: kernel-bug-exists-upstream-4.17-rc6
--
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/1087010
Title:
deeks9000:
1) Regarding the BIOS Error, you are welcome to update your BIOS to see
if this provides resolution.
2) The next step is to fully commit bisect from kernel 4.13 to 4.15 in
order to identify the last good kernel commit, followed immediately by
the first bad one. This will allow for a mo
Sandy Patterson, the next step is to fully reverse commit bisect from
kernel 4.15 to 4.17-rc7 in order to identify the last bad commit,
followed immediately by the first good one. Once this good commit has
been identified, it may be reviewed for backporting. Could you please do
this following https
Anil Gobburi, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766006/comments/21
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow
Daniel Nespoulous, please advise to all of the following:
1) To see if this still affects upstream, could you please test the
latest mainline kernel (now 4.17-rc5) and advise to the results?
Also, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it be
Maximilian Federle, the next step is to fully reverse commit bisect from
kernel 4.16.3 to 4.17-rc1 in order to identify the last bad commit,
followed immediately by the first good one. Once this good commit has
been identified, it may be reviewed for backporting. Could you please do
this following
Bob, to confirm this is an upstream issue, could you please test the
latest mainline kernel available (4.17-rc5) and advise to the results?
Also, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.
** Tags removed: kernel-bug-exists
deeks9000, 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 available from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind
the following:
1) The one
Rod B., the next step is to fully reverse commit bisect from kernel 4.4
to 4.16 in order to identify the last bad commit, followed immediately
by the first good one. Once this good commit has been identified, it may
be reviewed for backporting. Could you please do this following
https://wiki.ubuntu
Frew Schmidt, please address all of the following:
1) Could you please execute the following via a terminal to attach debugging
logs:
apport-collect 1767452
2) The next step is to fully reverse commit bisect from kernel 4.16.6 to
4.17-rc3 in order to identify the last bad commit, followed immedi
Philip Taylor, please advise to all of the following:
1) While booted into default Ubuntu kernel 4.15 and having removed all
WORKAROUNDs, could you please execute the following from a terminal to gather
relevant debug logs:
apport-collect 1767603
2) The next step is to fully commit bisect from
Mitch, please address all of the following:
1) To gather system debugging information, could you please execute the
following via a terminal:
apport-collect 1767611
2) To clarify, this issue only happens after resuming from suspend (i.e.
after booting from a shutdown, performing subsequent power
Jochen Schroeder, please respond to all of the following:
1) To capture relevant debugging logs, could you please undo the WORKAROUND,
boot into a Ubuntu kernel (not upstream) and execute the following in a
terminal:
apport-collect 1767701
2) The next step is to fully reverse commit bisect from
Sandy Patterson, please address all of the following:
1. Is this something that started to happen after an update? If so,
which and when precisely?
2. In order to allow additional upstream mainline kernel developers to examine
the issue, at your earliest convenience, could you please test the la
Thomas, the next step is to fully commit bisect from kernel 4.4 to 4.15
in order to identify the last good kernel commit, followed immediately
by the first bad one. This will allow for a more expedited analysis of
the root cause of your issue. Could you please do this following
https://wiki.ubuntu.
Scott Testerman, the next step is to fully commit bisect from kernel
4.7.10 to 4.8 in order to identify the last good kernel commit, followed
immediately by the first bad one. This will allow for a more expedited
analysis of the root cause of your issue. Could you please do this
following https://w
Jacob Zimmermann, 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 available from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind
the following:
1) T
marvin, please address the all of the following:
1. When using 16.10, were you able to adjust the brightness via keyboard
key press, or you could only adjust the brightness via xrandr?
2. In order to allow additional upstream mainline kernel developers to examine
the issue, at your earliest conv
stre...@bluewin.ch, please respond to all of the following:
1) Could you please perform the following in Ubuntu 17.10 to gather information
about your working setup via a terminal:
apport-collect 1769331
2) Could you please provide debugging logs from a live environment of
http://cdimage.ubuntu.
Anupam Datta, could you please run the following command from a terminal
as it will automatically gather and attach updated debug information to
this report:
apport-collect 1751198
** Package changed: network-manager (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecid
Anupam Datta, the next step is to fully commit bisect from kernel 4.4 to
4.15 in order to identify the last good kernel commit, followed
immediately by the first bad one. This will allow for a more expedited
analysis of the root cause of your issue. Could you please do this
following https://wiki.u
Mio, if you want an upstream developer to review your problem and submit
a fix patch, you *need* to file a *new* upstream report as previously
advised (not continue to post here on Launchpad). Otherwise your issue
may never be addressed.
** Tags removed: regression-potential
** Tags added: needs-f
Mio, please don't change the Description. It is filled with old,
irrelevant, and speculative statements that confuse and hinder
developers resolving the problem.
Despite this, have you reported this upstream as noted in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1087010/comments/73
?
**
Mio, the issue you are reporting is an upstream one. Could you please
report this problem following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO: Rafael J. Wysocki and Len Brown CC: linux-acpi)?
Please provide a direct URL to your po
** Description changed:
- I see high cpu usage from a kworker thread. Usually kworker/0:1 or
kworker/0:2. I tested various kernels from Ubuntu and mainline (3.5.0-x, 3.6.x,
3.7.0-rcx) and they all showed the same behavior. This does not always happen.
- I wasn't able to determine on which basis
Peter T Hayward (energonic), given this was marked resolved by the original
reporter in 2013 (who had different hardware), 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:
ubun
Alex (alex-khv), 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.
** Summary changed:
- Resuming after suspend restar
Philippe Coval (rzr), 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.
--
You received this bug notification because
jeremyayerst, this report is closed. Hence, 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.
** Changed in: linux (Ubu
** Tags added: bionic
--
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/1694225
Title:
[Thinkpad T450s] Click lock effect on trackpoint left button when
touchpad is disabled
Status in li
John Fremlin, thank you for reporting this and helping make Ubuntu
better.
1) To clarify, did this problem not occur in a release prior to Xenial?
2) To see if this is already resolved in Ubuntu, could you please update
your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack
and a
Brendan D., given this report is scoped to different model using 16.04 (and
your issue is not reproducible in 16.10), 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-bu
** Description changed:
- see Bug 570692
+ WORKAROUND: Use sudo.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-45-generic 4.4.0-45.66
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
NonfreeKernelModules: nvidia_u
Thomas E. Horner, thank you for reporting this and helping make Ubuntu
better.
1) What is the full manufacturer and model of the device you are trying
to use as noted on the sticker of the device itself (not from the Bug
Description, or the result of a terminal command)?
2) Is this something that
ipatrol, please see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568341/comments/29
.
** 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
Thomas E. Horner, as this report is closed, 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.
--
You received this bug
Lancillotto (antonio-petricca), 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.
--
You received this bug notificatio
Bill Miller, given your issue was root caused by you to having an
outdated gcc-4.8 package (now since updated), and when receiving the
update this problem is resolved, I'll mark this Fix Released.
** Changed in: gcc-4.8 (Ubuntu)
Status: New => Fix Released
** No longer affects: linux (Ubun
** Project changed: gcc => gcc-4.8 (Ubuntu)
** No longer affects: nvidia-graphics-drivers-384 (Ubuntu)
--
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/1750937
Title:
4.4.0-116 Kernel upd
** No longer affects: xorg (Ubuntu)
--
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/1750937
Title:
4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
16.04) by an insuf
Lancillotto (antonio-petricca), it will help immensely if you filed a new
report with Ubuntu via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
Marc Rene Schädler, thank you for reporting this and helping make Ubuntu
better.
Given I'm not seeing evidence of touchscreen recognition, for now I'll
move to linux for further review.
While waiting, it is best to continually test the latest mainline kernel
(now 4.16-rc6) as it becomes released,
private_lock, your release has been EOL since July 28, 2016 as per
https://wiki.ubuntu.com/Releases . Could you please advise if this is
reproducible in a supported release?
** Tags removed: hard kactivitymanager libqt5sql lockup segfault
** Tags added: latest-bios-520
** Changed in: linux (Ubunt
Jeb Eldridge, to advise, there is not enough information for upstream
developers to address your issue. Hence, please answer all of the
following questions:
1) The latest release you reported with 15.10 has been EOL since July
28, 2016 as per https://wiki.ubuntu.com/Releases . Hence, to see if thi
** Description changed:
- My wireless internet connection, no matter what dongle I use as an
- interface, is always slower and I have more DNS issues "unable to find
- website" than what I ever get on even the Windows 10 Developer Beta
- running on my same machine within a different hard disk.
+ U
Closing as per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747615/comments/3
noting this is not an issue anymore.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Abhijeet Ravi Raj, thank you for reporting this and helping make Ubuntu
better.
1) Regarding bluetooth, this appears a known issue due to the vendor not
providing upstream support:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1355096
Regarding WiFi:
2) Could you please provid
Sergey Zolotarev:
Given the nvidia drivers are a WORKAROUND, it appears the touchpad not
working is correlated to an issue with the graphics driver nouveau.
Hence, in order to upstream this, could you please remove the
WORKAROUND, install the latest mainline kernel (now 4.16-rc1),
reproduce, and
L'Africain, given this report is about specific hardware not working at all, 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
Dow Hurst, this closed report is not scoped to your problem. Hence, 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.
Karl Hill, thanks for the follow up. I'll close this report given it's
due to having outdated smart card firmware.
** Changed in: linux (Ubuntu)
Importance: Medium => Undecided
** Changed in: linux (Ubuntu)
Status: Expired => Invalid
** Summary changed:
- Smart Card Reader BCM 5880 wi
Torsten Schönfeld, 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 available from http://kernel.ubuntu.com/~kernel-pp
Closing this report, as not reproducible on my hardware. All others
please file a new report.
** Changed in: linux (Ubuntu)
Importance: Low => Undecided
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Kernel
Pa
Sebastiaan Breedveld, you likely have a different root cause if
uninstalling uswsusp didn't help.
Hence, , it will help immensely if you don't install the package hibernate so
you can boot, and provide necessary debugging logs by filing a new report with
Ubuntu via a terminal:
ubuntu-bug linux
jayantilal chauhan, thank you for reporting this and helping make Ubuntu
better.
1) Could you please provide the full USB WiFi device manufacturer and
model as noted on the sticker of the device itself (not from the Bug
Description, or the result of a terminal command)?
2) Could you please plug t
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
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/1740032
Title:
no ubuntu wifi network connection
Status in linux package in Ubuntu:
walt, thank you for reporting this and helping make Ubuntu better.
To advise, your logs indicate that the wireless hardware isn't
installed.
Despite this, to clarify, could you please confirm wireless is
recognized and enabled in the BIOS?
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
**
** Tags added: kernel-bug-exists-upstream
--
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/1746357
Title:
Boot loop MSI A88XM-E35 AMD APU A8-5600K (Aruba HD7560D)
Status in linux package
301 - 400 of 20804 matches
Mail list logo
