This has been implemented a while back, see
405e116f57b1cf33d4ca0294ab045a9f709bbc96
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354306
Title:
gpio shutdown trigger for ProLiant m400 cartridges
This has been implemented a while back, see
405e116f57b1cf33d4ca0294ab045a9f709bbc96
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347776
Title:
shutdown trigger on gpio_keys.X for armhf hardware
(In reply to Lennart Poettering from comment #6)
> Hmm, please use parse_bytes() for parsing byte values.
Sorry, I meant parse_size() of course.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953
OK, if this is not a bytes value, parse_size() is probably not a good
idea. (that said, I think it's a pretty poor choice to expose this as
512byte block value...)
Anyway, looks good. Please push!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hmm, please use parse_bytes() for parsing byte values.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953875
Title:
Encrypted swap no longer mounted at bootup
To manage notifications about this bug
Also, please add the initialization of .offset and .skip into the
declaration of the params variable, as initializer. i.e.:
struct crypt_params_plain params = {
.offset = arg_offset,
.skip = arg_skip,
};
Also, please document the new switches in crypttab(5).
--
You received this
(In reply to Martin Pitt from comment #13)
> (In reply to Lennart Poettering from comment #12)
> > The best way is to fix the few services that really need dbus
> > unconditionally to be around to add After=dbus.service. And all is good.
>
> If we go with that approach,
Please do not apply that ExecStop= thing. You really shouldn't block
that. Think about people who boot their system with "emergency" on the
kernel cmdline, and thus get a PID 1 plus a shell and nothing else, they
should be able to start dbus and stop it as they wish...
If at all, use RefuseManualS
I think the proper way to fix this is by waiting for this kernel patch
to be applied:
http://www.spinics.net/lists/linux-input/msg33007.html
With that in place we can then update logind to make use of it, and then
simply add the udev tag to all keyboards that are discovered, which
would then impl
I think the proper way to fix this is by waiting for this kernel patch
to be applied:
http://www.spinics.net/lists/linux-input/msg33007.html
With that in place we can then update logind to make use of it, and then
simply add the udev tag to all keyboards that are discovered, which
would then impl
MArtin, can you prep a patch for your requested changes?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/445852
Title:
devkit-disks-probe-ata-smart causes HSM Violations on SSD, and
potential hardwa
Thanks, applied.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885869
Title:
Add these Samsung SSD attributes
To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+b
So, I wanna give this one more try. I kept the log2() in there, but
multiplied it now with 1024 which should be a safe margin.
If this brings bad results we can drop this entirely. In that case,
please reopen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
The rhbz bug about the race you find here:
https://bugzilla.redhat.com/show_bug.cgi?id=643367
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/148454
Title:
console-kit-daemon spawns too many threads
(In reply to comment #32)
> yes it does. there are other distros out there that doesn't use systemd at all
> and doesn't have the intention to use it.
Are there? If so those folks probably have to become active... We will
phase out CK one day, and those folks who find value in sticking with
obsole
I have now reverted the patch and reopened this bug. VT_WAITEVENT is
inherently racy, since events that happen between the time we return
from a VT_WAITEVENT and go back into VT_WAITEVENT are completely lost.
That has the effect that when coming back from a suspend sometimes VT
switches are not not
See the thread starting with this patch of Kay's:
http://markmail.org/message/dhgzoht63uhfieqc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/148454
Title:
console-kit-daemon spawns too many threads
BTW, if somebody cares enough: this bug could be fixed properly now as
Kay's patch got merged into .38.
There's now a file "/sys/class/tty/tty0/active" which you can read to
get the current VT. And you can poll() for it and will get POLLPRI every
time the VT changes.
That said, given that CK is b
18 matches
Mail list logo
