Attach Xorg.log for completeness although this does not show any
problems
** Attachment added: "Xorg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1631719/+attachment/4757953/+files/Xorg.0.log
--
You received this bug notification because you are a member of Kernel
Packages,
Public bug reported:
Upgrades to Yakkety in feature freeze with kernel 4.8.0-21-generic.
System regularly hangs for 10 second intervals which is very noticeable in boot
process. Cause seems to be the Intel GMA965 DRM support causing regular kernel
warnings:
WARNING: CPU: 0 PID: 1183 at
Attached dmesg with complete kernel errors with stack traces
** Attachment added: "kernel dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1631719/+attachment/4757952/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is
Tried to install Ubuntu Gnome 16.04.1 with NVIDIA Driver 367.xx using
the GDM display manager yesterday and resulted in black screen at login.
Did the same today with the newly released NVIDIA Driver 370.23 (beta, I
think) and everything is actually working fine - no black screens, but
the login
** This bug is no longer a duplicate of bug 1589889
Bluetooth search gets nothing on Dell XPS 15 9550
--
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/1590798
Title:
Can't connect/pair
*** This bug is a duplicate of bug 1589889 ***
https://bugs.launchpad.net/bugs/1589889
I have followed the fix suggestion in bug #1589889. This has resulted in
some progress in that I can now connect to the headphones, and once the
headphones did register the laptop. But they disconnected
** Summary changed:
- Can't connect Bose Soundlink II Headphones to Ubuntu
+ Can't connect/pair Bose Soundlink II Headphones to Ubuntu 16.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Public bug reported:
I've recently started using 16.04 on a Dell XPS 15 9550 and I'm unable
to pair my Bose Soundlink II headphones. I've tried using the stock and
blueman bluetooth managers and neither will work.
When I use bluetoothctl and run "pair [Device ID]" I get the following
error:
Serge Malo,
A workaround is to enter the BIOS, keep the built-in Intel USB enabled, but set
the third-party ASMedia USB to disabled.
--
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/1437492
19.0-29-generic. If the problem can
> be reproduced, please include instructions to do so.
>
> This appears to be a weird interaction between Chrome and Telepathy
> that might itself warrant investigation, but the primary issue is that
> there is a way to reach an
-image-3.19.0-29-generic 3.19.0-29.31
ProcVersionSignature: Ubuntu 3.19.0-29.31-generic 3.19.8-ckt6
Uname: Linux 3.19.0-29-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred 2638 F puls
Public bug reported:
merci!
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-63-generic 3.13.0-63.103
ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
Uname: Linux 3.13.0-63-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.13
Architecture: amd64
A search for asmedia on the Linux kernel commit log:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?id=refs%2Ftags%2Fv4.2-rc6qt=grepq=asmedia
Merge tag 'usb-3.18-rc4' of
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb
Thank you John5788!
I have a Asus Z87-Pro and suffered from this problem. After going into
the UEFI setup screen and changing the four Asmedia 1074 ports to
disabled the system now boots fine.
In the settings screen, they are under Advanced - USB, and named as
USB_ xxE with the suffix E.
--
Yes, and this bug is still in 15.10-daily with kernel 4.0.
** Changed in: linux (Ubuntu)
Status: Fix Released = 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/1437492
Masking the service makes the system boot faster and LightDM gets shown quickly:
$ systemctl mask systemd-udev-settle
However, then at LightDM I can't use my keyboard and mouse, and have to
wait 30 more seconds, then I can use them.
--
You received this bug notification because you are a member
$ systemd-analyze blame
36.048s systemd-udev-settle.service
No, I guess I still have this problem. :(
--
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/1437492
Title:
boot stalls on USB
$ systemd-analyze
Startup finished in 8.835s (firmware) + 6.535s (loader) + 6.107s (kernel) +
9.169s (userspace) = 30.647s
$ systemd-analyze blame
6.703s NetworkManager-wait-online.service
30s vs 1m14s
Yeah, this bug seems to have been fixed.
--
You received this bug notification
I don't have any old kernels around.
Yes, I believe this to be a regression, since I don't recall having this slow
boot long time ago.
Interestingly GRUB to LightDM with systemd is 45 seconds.
While GRUB to LightDM with upstart is 10 seconds (then I have to wait about
half a minute for the USB
I disconnected *all* my USB peripherals (which was both my mouse and
keyboard). The boot is still slow.
$ systemd-analyze
Startup finished in 14.697s (firmware) + 11.224s (loader) + 6.121s (kernel) +
44.182s (userspace) = 1min 16.225s
$ systemd-analyze blame
35.463s systemd-udev-settle.service
journal as requested
** Attachment added: journal.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1437492/+attachment/4369939/+files/journal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
which was not available. After deleting snd-usb-audio
index=0 everything is working fine.
On Tue, Mar 10, 2015 at 2:31 PM, Fred Warren fred.war...@gmail.com
wrote:
Hi,
I loaded the 4.0.0-04rc3-generic amd64 kernel and then ran
apport-collect 1430055. No audio via the soundbar
I loaded
If I am following, you want me to go to
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D and run a 4.0
kernel, the latest one at the top is v4.0-rc3-vivid/
http://kernel.ubuntu.com/%7Ekernel-ppa/mainline/v4.0-rc3-vivid/ the
latest for trusty is v3.14.1-trusty/
apport information
** Tags added: apport-collected trusty
** Description changed:
Dell ACS11 USB Soundbar with USB ID 413C:A503 works fine in linux kernel
3.13-0-45-generic and earlier kernel releases.
In 3.13.0-46 dmsg shows messages when the soundbar is pluged in and
unpluged.
On Tue, Mar 10, 2015 at 2:14 PM, Fred Warren fred.war...@gmail.com wrote:
apport information
** Tags added: apport-collected trusty
** Description changed:
Dell ACS11 USB Soundbar with USB ID 413C:A503 works fine in linux kernel
3.13-0-45-generic and earlier kernel releases
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1430055/+attachment/4340436/+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: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1430055/+attachment/4340435/+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: AlsaInfo.txt
https://bugs.launchpad.net/bugs/1430055/+attachment/4340433/+files/AlsaInfo.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: PulseList.txt
https://bugs.launchpad.net/bugs/1430055/+attachment/4340443/+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: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1430055/+attachment/4340439/+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: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1430055/+attachment/4340440/+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: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1430055/+attachment/4340441/+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: UdevDb.txt
https://bugs.launchpad.net/bugs/1430055/+attachment/4340444/+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/1430055
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1430055/+attachment/4340434/+files/BootDmesg.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/1430055/+attachment/4340438/+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/1430055
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1430055/+attachment/4340445/+files/UdevLog.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: Lspci.txt
https://bugs.launchpad.net/bugs/1430055/+attachment/4340437/+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/1430055
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1430055/+attachment/4340442/+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
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1430055/+attachment/4340446/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Same bluescreen again on day 9 after the kernel upgrade.
So upgrading Kernel from 3.13 to 3.16 did not help.
Still looking for a fix.
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Same bluescreen STOP: 0x005c again on day 9. So it has not been
fixed by a kernel upgrade to 3.16.0-23-generic with above method from
askubuntu.com.
--
You received this bug notification because you
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Just wanted to add that upgrading my kernel to a newer version fixed the
problem for me, too.
Host: 2x E5-2620V2, Ubuntu 14.04 LTS
Guest: 24 virtual cores, Windows Server 2008 R2
Before fix:
sudo uname -a
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Same here, had issues with 3.13.0-44-generic, upgraded to
3.16.0-23-generic and the problem was solved. Followed this tutorial
http://askubuntu.com/questions/541775/how-can-i-install-ubuntu-14-10s-
I'm having the same problem with my Acer Travelmate 8215WLMI. Now, funny as it
seems, since Ubuntu 11 I have to use
blacklist.firewirewire_ohci=yes as a work-around, blacklist=firewire_ohci
just wouldn't work.
I'm actually using Ubuntu 12.04.5 Kernel 3.2.0-67.
Trying Ubuntu 14 using the
Same problem on a HP ProBook 470 G1 with Ubuntu 14.04 Trusty Thar
Hope, this will be fixed, soon.
--
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/1220146
Title:
Need support for new
Thanks, Daniel, I may try that. Been years since I compiled a kernel
tho!
--
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/1276740
Title:
Touchpad no recognized since kernel upgrade
A patch script is available in the meantime, to patch the kernel. It is
located here:
http://goo.gl/kz917j
--
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/1276740
Title:
Touchpad no
Public bug reported:
This is on Ubuntu 13.10, kernel 3.11.0-15 on an Acer C720 Chromebook
with a Synaptics touchpad.
A USB or bluetooth mouse works fine.
The trackpad is no longer in the list of devices in xinput as it had
been before.
$ apt-cache policy xserver-xorg-input-synaptics
The touchpad works fine when I boot into ChromeOS. I have dual-boot set
up.
--
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/1276740
Title:
Touchpad no recognized since kernel upgrade
Still a problem.
fredlaxton@chrubuntu:~$ uname -a
Linux chrubuntu 3.11.10-03111003-generic #201401160535 SMP Thu Jan 16 10:35:52
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
fredlaxton@chrubuntu:~$ xinput --list
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳
Linux kernel 2.6.39 removed the final part of the BKL, the whole BKL
locking mechanism. BKL is now finally totally gone! Hooray!
http://kernelnewbies.org/BigKernelLock
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Orginal error was in ISO itself.
Above error seems to be just when written with certain tools that file
name is too long to be converted from ISO correctly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred 3205 F pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=f25cda9a-ab3e-4873
PID ACCESS COMMAND
/dev/snd/controlC0: fred 3205 F pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=f25cda9a-ab3e-4873-9752-74587b66e784
InstallationDate: Installed on 2010-05-26 (1245 days ago)
InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx
Public bug reported:
Using 13.10 on my laptop (Asus EeePC 1005HA), the system goes into
suspend mode when I close the lid. When opening the lid and pressing a
key, the system wakes up and asks me for my password. This is the
expected behavior.
However, if the laptop is running on battery, the
Upon further testing, I can add the following details the this 'suspend
loop' issue.
- It does not matter if the laptop was running on battery or on power when put
into suspend mode for this suspend loop to happen.
- When is 'suspend loop', the network is deactivated (only lo is shown from
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred 3205 F
as expected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred 3205
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred 3205 F pulseaudio
as expected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred 3205 F
.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
+ ---
+ ApportVersion: 2.12.5-0ubuntu2
+ Architecture: i386
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: fred 3205 F pulseaudio
+ DistroRelease: Ubuntu
as expected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred 3205 F
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred 3205 F
as expected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred 3205 F
as expected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred 3205 F
as expected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred 3205 F
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred 3205 F
as expected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred 3205 F
when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred 3205 F
as expected when
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred
resuming from suspend mode.
I did not experience any such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred 3205 F
such problem with 13.04.
Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fred 3205 F pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID
This user found more issues and created a perl script to rename files
correctly.
http://cirrus.ucsd.edu/~pierce/fix_ubuntu_usb/
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
In my case, this installation failed due to lack of space on the /boot
partition
apt-get -f install failed:
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.8.0-30-generic
/boot/vmlinuz-3.8.0-30-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.8.0-30-generic
I guess this might have something to do with that I have no swap
partition and no file, I disabled that.
--
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/1022172
Title:
Not enough memory
** Changed in: linux (Ubuntu)
Status: Expired = New
--
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/1172065
Title:
12.04.2 incorrect file name signed efi amd6.deb
Status in
101 - 176 of 176 matches
Mail list logo
