The systemd side of this is fixed in utopic, closing. The kernel (and
main) side keeps open.
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
Just to clarify, it seems the "hard resetting link" and "SError: {
CommWake DevExch }" errors I was seeing had to do with me
connecting/disconnecting an external bus-powered portable eSATA drive
(ata6) that sometimes isn't correctly detected for some reason. The
sudden, random remounting of my main
ected. Automatically uninstalling this module.
DKMS: Install Failed (depmod problems). Module rolled back to built state.
lsb_release -rd
Description:Ubuntu Utopic Unicorn (development branch)
Release:14.10
Kind Regards,
Martin
** Affects: linux (Ubuntu)
Importance: Unde
1-1ubuntu0~saucy1~ppa1
Version table:
*** 2.1.1-1ubuntu0~saucy1~ppa1 0
500 http://ppa.launchpad.net/cdemu/ppa/ubuntu/ saucy/main amd64 Packages
100 /var/lib/dpkg/status
Kind Regards,
Martin
--
You received this bug notification because you are a member of Kernel
Packages, which is
t branch)
Release: 14.10
Kind Regards,
Martin
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1368111/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe
.16.0-14-generic cannot be found.
Please install the linux-headers-3.16.0-14-generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel
header packages should be probably installed automatically within
distribution upgrade process - because it is a
option to tell DKMS where it's located
Error! Your kernel headers for kernel 3.16.0-14-generic cannot be found.
Please install the linux-headers-3.16.0-14-generic package,
Kind Regards,
Martin
- P.S. I am not sure if I should report this error but linux kernel
- header packages shou
generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
in case
ackage,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
in case of any new k
16.0-14-generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
in case of
16.0-14-generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
aders-3.16.0-14-generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
tell DKMS where it's located
Error! Your kernel headers for kernel 3.16.0-14-generic cannot be found.
Please install the linux-headers-3.16.0-14-generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages shou
generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
in case of
16.0-14-generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
in case
16.0-14-generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
ackage,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
in case of any ne
16.0-14-generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
in case of
generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
in case of any ne
ackage,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
in case of any ne
ackage,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
in case of any new k
16.0-14-generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
aders-3.16.0-14-generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
in case of
16.0-14-generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
in case
generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
in case of
generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
in case
16.0-14-generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
16.0-14-generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
ackage,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
in case of any ne
generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
in case
generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
in case of any ne
16.0-14-generic package,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
ackage,
Kind Regards,
Martin
P.S. I am not sure if I should report this error but linux kernel header
packages should be probably installed automatically within distribution upgrade
process - because it is always happening of "rebuilding" some module/s . Even
in case of any ne
** 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/1035723
Title:
Joystick (SideWinder FF2) Force Feedback doesn't reset properly
In kernel 3.13.0 I still have the same issues. So I also did some
debugging. Major findings:
- in hid-core.c the function usbhid_parse() is called after the joystick is
attached
- usbhid_parse() calls function hid_set_idle(), and this one fails while
sending an URB (details see below). Reason: t
Wireshark capture of EPIPE
** Attachment added: "wireshark trace"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1035723/+attachment/4205605/+files/sidewinder2.pcap.pcapng
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Just found out, that it is an upstream bug. The force feedback works in
2.6.38-12.
--
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/1035723
Title:
Joystick (SideWinder FF2) Force Feedback
Having the same problem, but found a temporary solution:
If you're using Unity, control the BT switch via the BT tray icon. That
should work.
--
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
14-lowlatency
linux-image-3.16.0-14-lowlatency:
Installed: 3.16.0-14.20
Candidate: 3.16.0-14.20
Version table:
*** 3.16.0-14.20 0
500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
100 /var/lib/dpkg/status
Thank You,
Kind Regards,
Martin
P.S. Is it
t-cache policy linux-image-3.16.0-16-generic
linux-image-3.16.0-16-generic:
Installed: 3.16.0-16.22
Candidate: 3.16.0-16.22
Version table:
*** 3.16.0-16.22 0
500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
100 /var/lib/dpkg/status
Thank You,
Kind Reg
500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
100 /var/lib/dpkg/status
Thank You,
Kind Regards,
Martin
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371325/+subscriptions
--
Mailing list: https://launchpad.net/~k
100 /var/lib/dpkg/status
lsb_release -rd
Description:Ubuntu Utopic Unicorn (development branch)
Release:14.10
Thank You,
Kind Reagrds,
Martin
** Affects: bcmwl (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a membe
0
500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
100 /var/lib/dpkg/status
Thank You,
Kind Regards,
Martin
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371325/+subscriptions
--
Mailing list
ncy
linux-image-3.16.0-14-lowlatency:
Installed: 3.16.0-14.20
Candidate: 3.16.0-14.20
Version table:
*** 3.16.0-14.20 0
500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
100 /var/lib/dpkg/status
Thank You,
Kind Regards,
Martin
P.S. Is it possi
In Utopic kernel 3.16 it is still appearing.
--
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/1341027
Title:
init: Failed to obtain startpar-bridge instance: Unknown parameter:
INSTANCE
It is duplicate of:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1295596
--
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/1341027
Title:
init: Failed to obtain startpar-bridge in
500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
100 /var/lib/dpkg/status
Thank You,
Kind Regards,
Martin
P.S. Is it possible to tell to kernel not to trying mount some
specific partition/s ? Like by some kernel parameter ...
To manage notifications
This ran now in https://jenkins.qa.ubuntu.com/job/trusty-adt-linux/110/.
The new ubuntu-regression-suite autopkgtest succeeded (see
https://jenkins.qa.ubuntu.com/job/trusty-adt-
linux/110/ARCH=amd64,label=adt/console), just the test was marked as
failed because of a Jenkins job configuration issue.
Any chance of applying this upstream at some point?
** Changed in: dkms (Ubuntu Raring)
Status: Triaged => Won't Fix
** Changed in: dkms (Ubuntu Quantal)
Status: Triaged => Won't Fix
** Changed in: dkms (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug
Discussed with Andy on IRC. The rebuild test should become simplified
and also do the build as the actual test, otherwise after the build it
will reset the testbed again (i. e. starting new VM, upgrading to new
kernel in -proposed, reboot). We also want to set a build profile to
only build one flav
OK, Jenkins config fixed, https://jenkins.qa.ubuntu.com/job/trusty-adt-
linux/113/ succeeded now. But please double-check if this is right:
seccomp_bpf_tests.c: In function ���change_syscall���:
seccomp_bpf_tests.c:1086:7: error: ���struct user_regs_struct��� has no
member named ���orig_ax���
Does this actually need to be fixed on the kernel side in Trusty? I'm a
bit confused by the "fix released" status of linux in utopic, as far as
I know most issues can be fixed in udev's keymaps alone?
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affec
I uploaded an SRU to the trusty review queue with the latest upstream
keymaps which include the fix for this bug. Note that accepting the SRU
is currently blocked on verifying the current SRU in trusty-proposed
(bug 1367883).
** Changed in: systemd (Ubuntu Trusty)
Status: New => In Progress
6.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin 1970 F pulseaudio
CurrentDesktop: Unity
Date: Wed Nov 12 16:06:27 2014
HibernationDevice: RESUME=UUID=a7b59988-1d75-4f19-8fd8-3c9a08c38e8d
Instal
.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin 1970 F pulseaudio
CurrentDesktop: Unity
Date: Wed Nov 12 16:06:27 2014
Hibernatio
3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin 1970 F pulseaudio
CurrentDesktop: Unity
Date: Wed Nov 12 16:06:27 2014
Hibe
DevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin 1970 F pulseaudio
CurrentDesktop: Unity
Date: Wed Nov 12 16:06:27 2014
HibernationDevice: RESUME=UUID=a7b59988-1d75-4f19-8fd8-3c9a08c38e8d
InstallationDate: Installed on 2014-08-21 (83 days ago)
Installa
@Jeffrey
AFAIK, the Crucial M500 uses the Marvell 88SS9187 controller, while the
M550 and MX100 both use the Marvell 88SS9189 controller, and therefore
probably share the same firmware (or maybe the MX100 firmware was forked
off of the M550 firmware):
"These new Crucial MX100 SSD series features
@Jeffrey, I don't know for sure, but I'd say it's likely that two drives
from the same manufacturer using the same controller will at the very
least be both derived from the same firmware code base, and their
firmware will therefore likely have a lot of bugs (and features) in
common. Since your dri
Public bug reported:
Current Ubuntu Touch images cause a kernel panic at boot:
$ sudo ubuntu-emulator create --channel=ubuntu-touch/devel-proposed
--arch=i386 devel-proposed
The current revision as of the time of reporting is 160. This did not
yet happen with earlier revisions. I re-tested with
** Description changed:
Current Ubuntu Touch images cause a kernel panic at boot:
$ sudo ubuntu-emulator create --channel=ubuntu-touch/devel-proposed
--arch=i386 devel-proposed
The current revision as of the time of reporting is 160. This did not
yet happen with earlier revisions.
** Also affects: goget-ubuntu-touch (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Description changed:
Current Ubuntu Touch images cause a kernel panic at boot:
$ sudo ubuntu-emulator create --channel=ubuntu-to
I get the same crash in tty_buffer_request_room+0x1d/0x128 when I do
"phablet-shell" and "sudo poweroff", also on previous images.
--
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/1349709
Ti
Fixed upstream now:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=1f6d36f
Thanks Wang!
** Package changed: linux (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kerne
*** This bug is a duplicate of bug 1339998 ***
https://bugs.launchpad.net/bugs/1339998
** This bug has been marked a duplicate of bug 1339998
[Dell Latitude 12 Rugged Extreme 7204] Microphone mute key does not work
--
You received this bug notification because you are a member of Kernel
P
can you please do "dmesg > /tmp/dmesg.txt" after such a resume and
attach /tmp/dmesg.txt here? Thanks!
** Package changed: udisks2 (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
P
eneric 3.16.0-6.11
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
ApportVersion: 2.14.5-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin 1665 F pulseaudio
CurrentDesktop: Unity
Date: Thu
curity restriction.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-6-generic 3.16.0-6.11
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
ApportVersion: 2.14.5-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
Status: New
** Changed in: lxc (Ubuntu)
Status: New => Triaged
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
t-container:
+
+mount,
+
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-6-generic 3.16.0-6.11
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
ApportVersion: 2.14.5-0ubuntu1
Architecture: amd64
AudioD
Thanks. Reassigning to kernel then.
** Summary changed:
- [keymap] Brightness keys Fn+F5 and Fn+F6 don't work for Asus UX32LN
+ Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Sta
** Package changed: udev (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/1336541
Title:
No TRIM via USB
Status in “linux” package in Ubuntu:
New
Bug descrip
** Package changed: udisks2 (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/1352821
Title:
0489:e078 - Qualcom Atheros - Ubuntu 14.04 bluetooth not working
Sta
Added kernel task for the lack of evdev events.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
+ Summary:
+ - The joystick evdev device for the pedals doesn't get proper permissions
(in udev/systemd)
+ - The pedal evdev device sometimes doe
** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1379849
Title:
[LENOVO 767374G] suspend/resume failure
Status
I can not reproduce this on Ubuntu MATE 14.10 RC running on Thinkpad
X61s.
BIOS Information
Vendor: LENOVO
Version: 7NETC2WW (2.22 )
Release Date: 03/22/2011
System Information
Manufacturer: LENOVO
Product Name: 7666WJ5
Version: ThinkPad X61s
I'd also like to know if this is related to PAE. I get the error on a perfectly
functioning, but old, IBM Thinkpad T42.
I've checked the hardware, and there's no hardware problem here, so my guess
is, that it's related to PAE.
** Changed in: linux (Ubuntu)
Status: Invalid => Opinion
--
I get the same error when I do an sudo apt-get update && sudo apt-get upgrade
on Lubuntu 14.04.
Because of this error, I can't install any new software because this breaks
first.
Is there anyway I can tell the package manager to ignore the error and continue
installing other packages?
If so, ple
Closing again. Polling drives does not apply to udisks2 as for a few
years now this is done by the kernel itself.
Can I kindly ask you to report a new bug for unrelated issues like SMART
updates? Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: linux (Ubuntu)
Status: Opinion => 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/1369247
Title:
package linux-image-3.13.0-36-generic (not installed) failed to
Hmm, bluez looks fine at first sight. Reassigning this back, apparently
the bluetooth.target behaviour changed.
** Package changed: bluez (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: Triaged => Confirmed
** Changed in: systemd (Ubuntu)
Assignee: Marti
** Changed in: bluez (Ubuntu)
Status: New => Triaged
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Summary changed:
- Bluetooth is not activated
+ bluetooth.service not started automatically
--
You received this bug notification because you are
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
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 detection errors
Status in linux
This bisection thing didn't work, I got many different compile errors from
testing ubuntu-archive/quantal.git
I'v read the documentation 20 times carefully, and it's still not clear.
I'm so frustrated, fuck it! wasting my time
--
You received this bug notification because you are a member of Ke
The main difference here is that under upstart we still run pm-suspend
with its quirks, while under systemd there are no quirks being run any
more. As suspend quirks have supposed to be obsolete for many years
and should be fixed properly in drivers/kernel, I add a linux task.
To find out which
Interesting, pm-suspend uses no quirks at all. Can you double-check that
running "sudo pm-suspend" is reliable while "sudo systemctl suspend" is
not? The two do exactly the same without quirks, i.e. writing "mem" into
/sys/power/state..
--
You received this bug notification because you are a memb
Thanks for confirming! Reassigning to the kernel then.
** Package changed: systemd (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/1454253
Title:
external usb
OK, then it might be one of the other hooks in /usr/lib/pm-utils/sleep.d
that pm-suspend runs. According to your dmesg it's unlikely that you
have the "alx" module loaded ("lsmod | grep alx" should be empty).
Can you please attach your /var/log/pm-suspend.log?
60_wpa_supplicant could be a likely
Thanks. So we need to find out which hook does the magic. For each value
of in the below list, can you please run
sudo /usr/lib/pm-utils/sleep.d/ suspend ; sudo systemctl
suspend; sudo /usr/lib/pm-utils/sleep.d/ resume
In descending order of likelyhood, I recommend the following list for
:
Thanks Jan. Note that you can make this a little faster too -- you can
start with testing (i. e. starting with "suspend") all five hooks at the
same time, to confirm whether it's actually any of these five. If it
still doesn't help, then the problem is somewhere entirely different. If
it does help,
** Tags added: rls-v-incoming
--
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/1359689
Title:
cryptsetup password prompt not shown
Status in linux package in Ubuntu:
Triaged
Status in l
** Tags added: rls-v-incoming
--
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/1434579
Title:
Unable to install VirtualBox Guest Service in 15.04
Status in linux package in Ubuntu:
Fix
Does this also happen if you boot with upstart? (You can choose that
from the grub boot menu under "Advanced options").
Please also boot without "quiet splash $vt_handoff" -- does your
computer boot then? If so, it's a graphics/plymouth problem, if not this
should show where it's hanging.
/usr/sh
bluetooth.service failed on your system.
** Package changed: systemd (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/1445408
Title:
USB-bluetooth-mouse not det
** Package changed: systemd (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/1445488
Title:
audio hardware not recognized
Status in linux package in Ubuntu:
N
Most of the upgraded packages in your list are totally unrelated to
keyboards. The only one which might even be remotely related is
libgnome-desktop. It's much more likely that this happened due to a
kernel upgrade -- could you try and boot with an earlier kernel in the
grub boot menu and see wheth
Ah, indeed it seems btrfs is unhappy on your machine. Setting back to
New for now, as I don't know how to debug this kernel/fs bug from here
on, I'm afraid.
** Summary changed:
- ubuntu 15.04 hangs at purple scren even with nomodeset
+ btrfs-transaction hangs
** Package changed: linux-flo (Ubunt
1001 - 1100 of 2222 matches
Mail list logo
