downgrading udev package to 204-0ubuntu19.1 solved my missing /dev/disk/by-uuid
problems.
Not sure if this is related to the originally reported lockup
I haven't investigated deeply (trying to catch up on 4hours lost work),
but it looks like the udev persistent-storage rules may have changed
(whe
I've had the same issue on amd64, with the unattended-upgrade failing,
with all grub initramfs images poisoned after the aborted upgrade
because /dev/disk/by-uuid is no longer being populated
So it's probably not the kernel image which caused the breakage (it
never ran), but some other xxx:3.11.0-
Public bug reported:
Package: toshset-1.76-4
Environment: Ubuntu Saucy Salamander (development branch) Release: 13.10
I found /etc/pm/sleep.d/novatel_3g_suspend on my non-toshiba laptop.
It takes action on suspend/resume, meddling with bus=2 device=2 as if this is
definitely a novatel-3G th
I haven't updated BIOS yet, need to find an ms-dos/freedos image to
launch it from :)
I find this has happened to me before (bug 1055753), showing same symptoms
(pulse-audio hung), and went away with a newly released kernel before I could
bisect the kernel stream to find out what broke it.
As be
The update I never did post:
workaround script in bug 1054732 tried (no help), update to newer kernel worked
before I'd finished the bisect.
This bug (bug 1055753) reappeared with same symptoms with 13.10 kernel
(3.11.0-4-generic) and reported as bug 1219174.
I'll reference this bug there, leave
Public bug reported:
I haven't yet found any logs detailing failure state.
I've noticed some recent updates to power-handling, which may have invalidated
some local hacks to hibernate/resume scripts, causing a me-only breakage.
Or this maybe real issue, affecting others, perhaps only on this Dell
6 matches
Mail list logo