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:
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
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
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
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.
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
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
** 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
**
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
** 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, which
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
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
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.
--
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
Downgrading xserver-xorg-video-ati from 1:6.6.3-2ubuntu3
to1:6.6.2-0ubuntu6 gives a more usuable workaraound.
--
X fails on boot
https://launchpad.net/bugs/93271
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This may be a duplicate of Bug #93271. I reported the bug against the
kernel as I can successfully load the ATI driver (although still with
errors) and start X by using the 'video=ofonly' kernel parameter.
--
xorg fails with ati driver with feisty on Apple ppc (post herd5 update)
Update to 2.6.20.12.8 does not fix the problem.
--
X fails on boot
https://launchpad.net/bugs/93271
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Description changed:
Binary package hint: linux-source-2.6.20
Hardware PPC G4 1.25GHz with 1.75G memory, Radeon 9000 video card.
Using xubuntu feisty Herd 5 released 16 March 07
kernel version 2.6.20-11.18 (specifically linux-image-2.6.20-11-powerpc)
- Booting the kernel with
The initial testing was done from the Desktop CD, but the 'video='
kernel parameter is also required in order to successfully start X from
a HD installation. However, the system no longer locks up after X
failure.
--
X fails on boot
https://launchpad.net/bugs/93271
--
ubuntu-bugs mailing list
** Attachment added: xorg log 0
http://librarian.launchpad.net/6849783/feisty.Xorg.0.log
--
X fails on boot
https://launchpad.net/bugs/93271
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: linux-source-2.6.20
Hardware PPC G4 1.25GHz with 1.75G memory, Radeon 9000 video card.
Using xubuntu feisty Herd 5 released 16 March 07
kernel version 2.6.20-11.18 (specifically linux-image-2.6.20-11-powerpc)
Booting the kernel with any of the default
** Attachment added: xorg log 1
http://librarian.launchpad.net/6849784/feisty.Xorg.1.log
--
X fails on boot
https://launchpad.net/bugs/93271
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: xorg.conf
http://librarian.launchpad.net/6849785/xorg.conf
--
X fails on boot
https://launchpad.net/bugs/93271
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: lspci output
http://librarian.launchpad.net/6849787/lspci.log
** Description changed:
Binary package hint: linux-source-2.6.20
Hardware PPC G4 1.25GHz with 1.75G memory, Radeon 9000 video card.
Using xubuntu feisty Herd 5 released 16 March 07
kernel version
** Description changed:
Binary package hint: linux-source-2.6.20
Hardware PPC G4 1.25GHz with 1.75G memory, Radeon 9000 video card.
Using xubuntu feisty Herd 5 released 16 March 07
kernel version 2.6.20-11.18 (specifically linux-image-2.6.20-11-powerpc)
Booting the kernel with
Public bug reported:
Product : ubuntu-cd
Xubuntu (PPC) Herd 4 candidate of 15 Feb 2007, feisty-desktop-
powerpc.iso.
The calculated md5sum
378b7afbc070b139ffdff0069d0c1b54 feisty-desktop-powerpc.iso
matches that published.
The CD integrity check (check) when entered at the boot: prompt fails
Confirmed on xubuntu feisty herd 3 candidate daily release 01/02/07.
udevd[2315]:lookup-group: specified group 'nvram' unknown
edevd-event [2394]: udev_db_add_device: unable to create db file
'/dev/.udev/db/[EMAIL PROTECTED]@mice': No such file or directory
edevd-event [2651]:
Public bug reported:
Binary package hint: xfburn
Hardware PPC G4 1.25GHz with 1.75G memory.
Using xubuntu feisty herd 3 candidate released 01/02/07
xfburn version 0.2.0-0ubuntu2
Using
Applications Accessories Xfburn
Or better in a terminal (to see output messages)
$ xfburn
Click button
Confirmed.
Hardware PPC G4 1.25GHz with 1.75G memory.
Using xubuntu feisty herd 3 candidate released 01/02/07
graveman version 0.3.12.5-1.
I can add another report if requred.
--
graveman crashes after finishing burning an iso(CD in general?)
https://launchpad.net/bugs/76997
--
ubuntu-bugs
** Changed in: graveman (Ubuntu)
Sourcepackagename: graveman = None
--
xfburn fails to burn cd
https://launchpad.net/bugs/83077
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Confirmed
Using xubuntu feisty herd 3 candidate released 01/02/07
In menu, launching
Applications Settings HPLIP Toolbox
generates
error: PyQt/Qt initialization error. Please check install of PyQt/Qt and
try again (the python-qt3 package must be installed for this program to
work).
Package
Public bug reported:
Binary package hint: gxine
Hardware PPC G4 1.25GHz with 1.75G memory.
Using xubuntu feisty herd 3 candidate released 01/02/07
gxine version 0.5.10-0ubuntu1
On a fresh install, launching
Applications Multimedia gxine
produces the attached error dialogue.
From a terminal
** Attachment added: gxine error dialogue
http://librarian.launchpad.net/6171669/gxineErrorDialogue.jpg
** Description changed:
Binary package hint: gxine
Hardware PPC G4 1.25GHz with 1.75G memory.
Using xubuntu feisty herd 3 candidate released 01/02/07
gxine version
Public bug reported:
Binary package hint: linux-source-2.6.20
Hardware PPC G4 1.25GHz with 1.75G memory.
Using xubuntu feisty herd 3 candidate released 01/02/07
linux-source-2.6.20 version 2.6.20-5.7 (specifically
linux-image-2.6.20-5-powerpc)
Booting the kernel without append=quiet splash
Although the problem was repeatable, since the tests were run I've
upgraded
2007-02-03 13:48:34 status installed volumeid 103-0ubuntu6
2007-02-03 13:49:01 status installed udev 103-0ubuntu6
g
This appears to have fixed the problem. I cannot force a downgrade of
volumeid and udev back to
Recommended workaround fixes probelm, thanks.
So this was a build error?
--
gxine startup error
https://launchpad.net/bugs/83083
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Next I removed all upgrades in the list above, but this did not fix the
problem.
I then did a fresh install of edgy 6.10 and picked up the upgrades
again. However, this time a new package was ready for download (a
kernel image) and the package was upgraded as follows
linux-image-2.6.17-10-power
I suspected linux-restricted-modules to be the source of the problem, so
I built kernel 2.6.17.14 with the default config, but without MOL (for
convenience) and without linux-restricted-modules. I then removed the
following packages
2007-01-27 11:20:32 remove linux-powerpc 2.6.17.10 2.6.17.10
Public bug reported:
On a G4 Mac with Snapper onboard audio and an added SBLive sound card,
after using Update Manager the following packages were upgraded.
2007-01-17 22:34:54 upgrade tzdata 2006m-1ubuntu1 2006p-0ubuntu6.10
2007-01-17 22:34:55 upgrade libkrb53 1.4.3-9ubuntu1 1.4.3-9ubuntu1.1
39 matches
Mail list logo