Jeff Gregoire (jfgregoire) wrote on 2012-06-11:
> - Create a file (any name) under /etc/pm/power.d with the following
content:
> # Brightness adjustment
Thanks for this solution, it works ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
\o/ this package fixe the bug.
Thanks for your work.
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition -
container does not start
https://bugs.launchpad.net/bugs/566827
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks for the package.
The package work correctly but don't fixe the bug :-/
I'm sorry !
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition -
container does not start
https://bugs.launchpad.net/bugs/566827
You received this bug notification because you are a member of
> Sorry, Hugin, I had failed to include
> quilt in the new build-depends. I've
> re-uploaded with that fixed, and the result should be in my
> ppa in a few
> hours. In the meantime, the locally built version
> (which succeeded since
> quilt was already installed here) i
I'm really interested in testing the package.
Actually the package failed to build.
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition -
container does not start
https://bugs.launchpad.net/bugs/566827
You received this bug notification because you are a member of Ubunt
This bug affect my system too :
Ubuntu 10.04 LTS
# lxc-version
lxc version: 0.6.5
# lxc-start -n web
lxc-start: Device or resource busy - could not unmount old rootfs
lxc-start: failed to pivot_root to '/opt/lxc/web/rootfs'
My containers is on another device too.
Cordially
--
[lucid] 0.6.5 can
*** This bug is a duplicate of bug 68792 ***
https://bugs.launchpad.net/bugs/68792
I really think it might be the best if the Ubuntu specific changes are
undone. I'm not sure what they are supposed to achieve, but it appears
that they do more damage then good.
Up till Gutsy I used the normal
*** This bug is a duplicate of bug 68792 ***
https://bugs.launchpad.net/bugs/68792
Sorry for the delay, I was away during the week. The backtrace your
requested is attached. Hope it helps.
Karsten
** Attachment added: "gdb-amule.txt"
http://librarian.launchpad.net/7440548/gdb-amule.txt
Given that I run a 64 bit Feisty, installing those packages would
require using the force option. I've some doubts that's a wise idea in
this case.
--
aMule 2.1.3-1Ubuntu2 crashes while downloading IPfilter file
https://bugs.launchpad.net/bugs/99917
You received this bug notification because you
Yes looks like a duplicate of that error. The workaround however isn't
feasible. Sure I can start aMule that way, but since aMule also crashes
when loading an IPfilter file manually from the security tab that means
currently aMule works only if IPfilters aren't used at all. That's not
an option I'm
Public bug reported:
Binary package hint: amule
aMule 2.1.3-1Ubuntu2 fails to read the IPfilter file from it's directory
and crashes when downloading one from a webserver. Using aMule version
2.1.3-1 from the Debian repositories avoids both bugs, but that version
eats a lot of CPU power in Feisty
Public bug reported:
Both Opera and Adobe Reader were installed and working on Kubuntu Feisty
x86_64. Since the last update both fail to start. From the console they
give the following error: "error while loading shared libraries: libxcb-
xlib.so.0: cannot open shared object file: No such file or
12 matches
Mail list logo
