I just tried 4.4.0-21 from the grub menu and the issue still occurs.
If these tests are not what you mean, can you be more specific as to
what release I should test?
Tom aka w2vy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I was answering your question in comment #17
My system boots from kernel 4.4.0-31
but in the kernels directory http://kernel.ubuntu.com/~kernel-
ppa/mainline/?C=N;O=D
the xenial versions are 4.4.9 through 4.4.9.13
I do have other 4.4.0-x images in my grub menu, will those do as earlier
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1608142/+attachment/4710618/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1608142/+attachment/4710617/+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/1608142
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1608142/+attachment/4710627/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1608142/+attachment/4710619/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1608142/+attachment/4710622/+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/1608142
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1608142/+attachment/4710621/+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/1608142
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1608142/+attachment/4710629/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1608142/+attachment/4710625/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1608142/+attachment/4710623/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1608142/+attachment/4710628/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1608142/+attachment/4710624/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1608142/+attachment/4710620/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1608142/+attachment/4710626/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected xenial
** Description changed:
Toshiba Satellite u945-s4110
touch pad brand unknown.
" cat /proc/bus/input/devices " does not show touchpad at all. This
problem showed after i upgraded from ubuntu 14.04 to 16.04 and I have
now
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1608142
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
Public bug reported:
Toshiba Satellite u945-s4110
touch pad brand unknown.
" cat /proc/bus/input/devices " does not show touchpad at all. This
problem showed after i upgraded from ubuntu 14.04 to 16.04 and I have
now even does a fresh install and it still won't work.
I: Bus=0019 Vendor=
I started experiencing this very issue about 3 months ago. My server,
Dell XPS 8700, would lock up repeatedly over the course of a day but
stay "active", meaning my email server wouldn't crash, for a week
sometimes even though I could not log in. This server is at the latest
standard upgrades of
My Huion 1060Plus tablet stopped working after upgrading from 15.10 to 16.04.
I consulted this thread, and several others. The previously suggested remedy of
sudo rmmod hid_uclogic &&
sudo insmod /lib/modules/$(uname -r)/kernel/drivers/hid/hid-uclogic.ko
did not work for me. I tried removing
On 4.4.0-31-generic, I'm still seeing this issue. This is new hardware
and 4.4.0-22-generic was the first kernel I tried to use with this
device.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-fixed-upstream
--
You received this bug notification
Using upstream kernel 4.7.0-040700-generic, I did not observe SCSI bus
resets, but did observe a single instance of I/O related "hung task"
messages in dmesg, which are attached, during heavy read/write load. I
could not reproduce the message on subsequent attempts.
** Attachment added:
w3vy, I'm not sure you understand what I've asked. I'm not asking you to
test a prior release. I'm asking that in your current Xenial install
(not Vivid, Wily, etc.) you test a prior kernel version. Instructions
are available via https://wiki.ubuntu.com/Kernel/MainlineBuilds .
** Changed in:
adin, as per http://www.dell.com/support/home/us/en/19/product-
support/product/alienware-17-r3/drivers an update to your computer's
buggy, insecure, and outdated BIOS is available (1.2.15). When you
update to this following https://help.ubuntu.com/community/BIOSUpdate
how does this improve the
Public bug reported:
Still the bluetooth aren't stable in the pro 5. Music interrupted when
playing on bluetooth speakers and the phone loses connection to keyboard
and mouse.
The same speaker, keyboard and mouse works well on the Bq units M10 and
e4.5
** Affects: bluez (Ubuntu)
This bug was fixed in the package zfs-linux - 0.6.5.7-0ubuntu5
---
zfs-linux (0.6.5.7-0ubuntu5) yakkety; urgency=medium
* Change to include some important tools in zfsutils-linux build.
- Add tools : arcstat.py, arc_summary.py & dbufstat.py in /usr/sbin.
- Change utilities path
@John, I am on it. There are a few issues:
1) is recent kernel changes for power management. The GAIA unfortunately
required the host to read the midi messages. A workaround is to connect e.g.
aseqdump.
2) Recording from the synth does not work. This is related to the "Unable to
change format
I just re-tested with vivid 15.04 with kernel 3.19.0 and my statement is
confirmed.
15.10 fails and 15.04 with kernel 3.19.0 works fine
Tom aka w2vy
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Update (no real results yet)
I tried to improve on the test cycle by stopping the hyper-v backup immediately
after it has begun, then waiting until the delta disks have been merged back
(rinse and repeat)
It took some time to get stable but it seems to have a 6-7x speedup compared to
the
Hi,
I also had the "hang after suspend problem" immediately after I upgraded
my Dell Inspiron 1501 from Ubuntu 14.04, to 15.1, then to 16.01 (all
32bit versions). I found an easy workaround (for now) that eliminates my
"blank screen" hang after suspend: Just got into "System | Brightness
and
It doesn't work. The network manager is working, but there is still no
card.
--
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/1607571
Title:
No network devices after suspend and resume
** Also affects: turbo
Importance: Undecided
Status: New
--
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/1593919
Title:
Bluetooth not working with Meizu Pro 5
Status in turbo:
** Tags added: turbo
--
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/1593919
Title:
Bluetooth not working with Meizu Pro 5
Status in bluez package in Ubuntu:
Confirmed
Bug
It looks like this can be fixed by unloading the brcmfmac module (rmmod
brcmfmac) before hibernating and reloading it (modprobe brcmfmac) after
hibernating.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
w3vy, unfortunately, your answer, and posting URLs I've already seen,
didn't answer my question.
I'm asking specifically if you tested those kernels in xenial (not
tested it in another release).
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug
ok to be complete the kernel version where it first fails is wiley
4.2.0-16
it is also the release that the mousepad option "Disable while typing"
was removed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of
As per my comment (#13
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584528/comments/13
) the problem was NOT reproducible with vivid or trusty
The first release the issue shows up is wiley, I can get the the kernel
release, but I am just using the downloadable live cd
--
You received
WiFi can be fixed by this:
Create a conf file for Wifi:
sudo gedit /etc/modprobe.d/rtl8723be.conf
Write in it:
options rtl8723be fwlps=N ips=N
Save and reboot. WIFi will work fine now, but the NOAER error still
floods the dmesg.
--
You received this bug notification because you are a member
I have the same issue, here is an Ask Ubuntu with my wireless info as
well, in case that helps in any way:
http://askubuntu.com/questions/749420/wireless-lost-ability-to-use-5ghz-
pce-ac68
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
This change was made by a bot.
** 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/1608044
Title:
wifi not detected
Status in
Public bug reported:
I am having many issues to get Ubuntu 16.04.01 LTS to recognize my
wireless card (Intel 3160). I have reinstalled the OS many times, but I
have the same problem all the time. A couple of days ago, the first time
I installed, it worked, but it just stopped working yesterday,
I have no problems with my new BQ M10. Do I need to attach some logs?
Bluetooth connection is working fine, no sound shuttering. It is still
actual for MX4 on rc-proposed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** 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/596269
*** This bug is a duplicate of bug 1590244 ***
https://bugs.launchpad.net/bugs/1590244
Public bug reported:
My UPS (APC Back-UPS ES 700) is somehow slow to report it's capacity
when upower starts, and this causes upower to shut down the system when
it thinks the battery is empty on daemon
44 matches
Mail list logo
