@alexus: sounds promissing, would be great if you could test it without
xorg-edgers and just -proposed (and maybe also vice versa).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/977804
Title:
Unity
@Bryce: I just tested the packages from your PPA, but as you have
already guessed Mesa 8.0.3 doesn't fix the issue. What i meant was also
rather new major versions.
But as you changed the status to incomplete what advices do you have on
further debugging and testing? Or did you have the chance to
I can reconfirm that opening a lot of nautilus windows and then clicking
on it's switcher seems to trigger the bug quite well.
While i'm running a single display setup for the last week, i noticed
that this bug seems clearly resolution dependent, as when i run 1280x800
on LVDS it's much less
@Steffen: I think testing newer mesa versions and kernels might be more
promissing, as the bug should be in the 3D stack.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/977804
Title:
Unity crashes
That's sad, altough i didn't have the issue with the update on the last
12 hours in single monitor mode. Further verifications by others would
be nice.
As already said it seems to get triggered on dual monitor mode far more
often. Could there be a link to 2048x2048 texture limitation that we
have
Please test if the newest mesa update also fixes our issue:
https://launchpad.net/ubuntu/+source/mesa/8.0.2-0ubuntu3.1/+changelog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/977804
Title:
Unity
Did you try /etc/init.d/halt and NETDOWN=no?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/981461
Title:
wol broken on HP ProLiant N40L (Broadcom tg3 driver)
To manage notifications about this bug
Here it is with the right boot order ;)
** Attachment added: S205_1038_acpidump.tar.gz
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/875659/+attachment/3114649/+files/S205_1038_acpidump.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Just as Doki already reported it works on a S205 modell 1038 with the
precise beta2 amd64 live image, but after the installation and no
updates applied the wireless is always hard blocked via rfkill.
Blacklisting acer_wmi doesn't make a difference.
What could be the difference between live
Just retried with the live medium, but could not get it to work this
time, as rfkill at start is at soft blocked and on activation switches
to hard blocked. Obvious difference is that with the live media i have a
ideapad_wlan listed by rfkill.
** Attachment added: S205_1038-beta2live.tar.gz
At least for the IdeaPad S205 model 1038 there is a quite weird
workaround:
After installation there is a mysterious ubuntu entry in the boot
order that must not be at the top. So go to your BIOS with F2 and
change the boot order so the hardisk comes before ubuntu entry. Seems
like a buggy
I can confirm what Rafal and Angelo said. I successfully assigned a
manually preconfigured bridge to a VM on a lucid server with virt-
manager on precise desktop by just giving the bridge name (br0 in my
case).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Bug watch added: Red Hat Bugzilla #508986
https://bugzilla.redhat.com/show_bug.cgi?id=508986
** Also affects: network-manager-openvpn (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=508986
Importance: Unknown
Status: Unknown
--
You received this bug notification
Solution for an update-to-date Ubuntu 10.04 is to reboot your machine
after installing or importing your vpnc connection.
For adavanced users: Instead of rebooting you can also restart network-
manager and the dbus daemon. The upstream author only recommends
killall -HUP dbus-daemon, but i
Sorry for my late response, but no i didn't use an ADF and as you can
see i was much too fast in feeding new content because of those UI lags.
As i said this wasn't the case with pre 2.32 releases. I will recheck
all this, because the next LTS will have the newer series and scanning
should be
@John: Did you take a look at the patch i have proposed, it wouldn't
need a big adjustment for your needs.
Anyhow great that there is some interest in this topic. Would be great
if we could bring a patch to the package in time for the precise
release.
What the patch is lacking beside John's
@Leon: It's something else :) Using TAP is not the problem, but getting
the IP address co via DHCP for it is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/297707
Title:
DHCP feature for
I just came across this bug when debugging OOo on SMB shares. Therefore
i enhanced the proposed workaround by Timo so that the quirk only gets
executed if $HOME is really on a NFS share. Tested it successfully on an
old karmic machine and the current lucid workstations. Just see the
attachment.
as i really needed a solution i did a dirty workaround for servers:
move /sbin/shutdown to /sbin/shutdown.real
place the attached script to /sbin/shutdown and make it executable
you can do the same for /sbin/reboot to have it run even on reboot,
halt, poweroff --force. you only need to change
yes it is still present on lucid server.
after unsucessfully trying something like:
start on (runlevel [2345] and networking)
in the upstart script i also head for a dirty sleep in the pre-start
script. Upstart experts needed!
** Changed in: libvirt (Ubuntu)
Status: Fix Released =
as i really needed a solution i did a dirty workaround for servers:
move /sbin/shutdown to /sbin/shutdown.real
place the attached script to /sbin/shutdown and make it executable
you can do the same for /sbin/reboot to have it run even on reboot,
halt, poweroff --force. you only need to change
yes it is still present on lucid server.
after unsucessfully trying something like:
start on (runlevel [2345] and networking)
in the upstart script i also head for a dirty sleep in the pre-start
script. Upstart experts needed!
** Changed in: libvirt (Ubuntu)
Status: Fix Released =
i reworked the changes by tomcrus (thanks for the elegance ;) and
removed all reintroduced bashism. so here is the current of the core
logic to shutdown guests.
** Attachment added: libvirt-guest-shutdown-core
http://launchpadlibrarian.net/51116608/libvirt-guest-shutdown-core
--
Should shut
but i am still hanging on the upstart integration when using pre-stop in
libvirt-bin. while the condition regarding the runlevel by tomcrus works
great, it seems we are not able to simply delay the shutdown process
with a simple sleep. in my case i only managed to get the pre-stop
killed or make
i reworked the changes by tomcrus (thanks for the elegance ;) and
removed all reintroduced bashism. so here is the current of the core
logic to shutdown guests.
** Attachment added: libvirt-guest-shutdown-core
http://launchpadlibrarian.net/51116608/libvirt-guest-shutdown-core
--
Should shut
i have also tested the hack to /etc/init.d/sendsigs
** Attachment added: sendsigs
http://launchpadlibrarian.net/51116634/sendsigs
--
Should shut down domains on system shutdown
https://bugs.launchpad.net/bugs/350936
You received this bug notification because you are a member of Ubuntu
Bugs,
but i am still hanging on the upstart integration when using pre-stop in
libvirt-bin. while the condition regarding the runlevel by tomcrus works
great, it seems we are not able to simply delay the shutdown process
with a simple sleep. in my case i only managed to get the pre-stop
killed or make
@Rheinhard: sure it would be, but this should be the next step, as we
still have shutdown not working yet. so let's stay to the KISS principle
till we got the upstart integration.
--
Should shut down domains on system shutdown
https://bugs.launchpad.net/bugs/350936
You received this bug
@soren: as i simple don't know how to trigger it only on shutdown, as
the premise was it should run on regular stop. but i know it may ease
the situation and would like to do so. do you know some solution here.
maybe we could do a simple condition that checks for an enviromental
stuff thats only
@soren: as i simple don't know how to trigger it only on shutdown, as
the premise was it should run on regular stop. but i know it may ease
the situation and would like to do so. do you know some solution here.
maybe we could do a simple condition that checks for an enviromental
stuff thats only
thanks for the hint, but after trying i found that start on (runlevel
[06] and stopping libvirt-bin) should do the trick. but i still got
problems as i can use libvirt at first in the upstart job, but when
testing the timeout loop it seems that libvirt-bin still stopped before
the script finished.
thanks for the hint, but after trying i found that start on (runlevel
[06] and stopping libvirt-bin) should do the trick. but i still got
problems as i can use libvirt at first in the upstart job, but when
testing the timeout loop it seems that libvirt-bin still stopped before
the script finished.
as this bug can corrupt guests i did an old school init script for my
server, but that doesn't work as libvirt-bin got always stopped before
(even at S01). so i removed all bashism like arrays and tried to create
an upstart script. the core logic is done, but i need some help
regarding upstart
as this bug can corrupt guests i did an old school init script for my
server, but that doesn't work as libvirt-bin got always stopped before
(even at S01). so i removed all bashism like arrays and tried to create
an upstart script. the core logic is done, but i need some help
regarding upstart
34 matches
Mail list logo
