The symptoms described were caused by missing configuration in squid-deb-proxy
(used as the apt proxy for the build). Puppet labs URL needed to be added to
the exemption list. So this is not a bug but behaviour as designed.
Please close this bug, I have marked it as invalid.
** Changed in: debia
Public bug reported:
Configuring a preseed.cfg for Ubuntu precise (12.04.4), x86_64 with the
following to add Puppet repo:
# Puppet Labs
d-i apt-setup/local0/repository string http://apt.puppetlabs.com precise main
dependencies
d-i apt-setup/local0/comment string Puppetlabs products
d-i apt-setu
Hi,
I'm now running the latest Lucid Lynx 10.04 and this issue no longer occurs.
(kernel 2.6.32-22)
Thanks for your assistance.
I'm removing the testing upstream notice as requested
Regards,
Brett
** Tags removed: needs-upstream-testing
--
Kernel Mode Setting on Intel 865G chipset results in
This bug is still active even with the following up-to-date packages:
xserver-xorg 1:7.4+3ubuntu10
xserver-xorg-core 2:1.6.4-2ubuntu4.2
xserver-xorg-video-intel2:2.9.1~git-0ubuntu0tormod
xserver-xorg-video-v4l 1:0.2.0-3ubuntu1
** Attachment added: "Xorg startup with KMS enabled"
http://launchpadlibrarian.net/38202943/Xorg.0.log
--
Kernel Mode Setting on Intel 865G chipset results in Xv not working
https://bugs.launchpad.net/bugs/510943
You received this bug notification because you are a member of Ubuntu
Bugs, whic
The second set is with KMS enabled (so Xv init fails)
** Summary changed:
- Kernel Mode Setting on Intel 865G chipset results in DRI not working
+ Kernel Mode Setting on Intel 865G chipset results in Xv not working
** Description changed:
Using Kernel Mode Setting on Intel 865G chipset result
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/38202511/AlsaDevices.txt
** Attachment added: "ArecordDevices.txt"
http://launchpadlibrarian.net/38202512/ArecordDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/38202513/BootDmesg.txt
**
Public bug reported:
Using Kernel Mode Setting on Intel 865G chipset results in non-working
DRI in X windows
Please note I am using the packages from the X Updates PPA so I'm using
the Intel 2.9.x video driver for X.
The information attached is with kernel mode setting disabled (thus DRI2
works)
Hi,
A similar problem does exist in Karmic in package:
0.8~a~git.20091013t193206.679d548-0ubuntu1
The problem was:
/etc/NetworkManager/dispatcher.d/01ifupdown does not support vpn-up / vpn-down
operations and therefore exits with an error (1). It is possible (but
unconfirmed) that if a dispatc
VPN over mobile broadband breaks regardless of VPN type. I think this
might be a network manager issue
--
network-manager-pptp VPN connection fails.
https://bugs.launchpad.net/bugs/407487
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Specifically for the "'/etc/NetworkManager/dispatcher.d/01ifupdown'
exited with error status 1." message please see the following separate
bug report as this is a network-manager issue not specific to the
openvpn package: Bug #330056 . A trivial patch is included there.
--
n-m-openvpn shuts down
Please see Bug #330056 for related information about dispatcher error
and possible patch
--
dispatcher does not handle vpn-connections correctly
https://bugs.launchpad.net/bugs/422100
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
To Cirroz: Please see bug #330056 for a simple patch that should resolve
your error. Your problem is not the same as that reported by this bug.
--
01ifupdown does not receive down event
https://bugs.launchpad.net/bugs/263712
You received this bug notification because you are a member of Ubuntu
B
The attached patch should resolve this issue - it simply adds vpn-up /
vpn-down as matching events to up / down. This seems to work quite well
on my system, YMMV.
** Attachment added: "Patch to ensure dispatcher handles vpn-up / vpn-down
events"
http://launchpadlibrarian.net/37404436/patch.000
14 matches
Mail list logo
