This defect persists into Ubuntu 21.04 Hirsute Hippo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697536
Title:
nm strongswan gui doesn't have a way to enter pre-shared key
To manage
@rlaager, zed first shipped in the zfsutils package, and the `Replaces`
line was required for a smooth upgrade between releases. It can/should
be dropped now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The mldonkey package was recently pulled from Sid to Saucy, and it
builds cleanly on Precise.
This worked for me on Ubuntu 12.04 LTS:
# dget https://launchpad.net/ubuntu/+archive/primary/+files/mldonkey_3.1.3-1.dsc
# cd mldonkey-3.1.3
# apt-get build-dep mldonkey
# dpkg-buildpackage -uc -us
--
This non-conformance bug works in both directions, so an easy kludge is
to hard link all file names like this:
$ ln foobar-1.2+baz3_all.deb 'foobar-1.2 baz3_all.deb'
And sync to the s3 bucket normally. Afterwards, the key can be called
through http with a literal + character or the %2B escape.
Public bug reported:
Running `bzr branch lp:ubuntu/precise/mountall` currently returns the
old mountall-2.36 source code, but mountall-2.36.3 is expected because
it is currently published to precise-updates.
LP #714622 suggests a reason for this glitch and a solution for it.
** Affects:
https://launchpad.net/bugs/714622
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103319
Title:
mountall source code repository is stale
To manage notifications about this bug go to:
Public bug reported:
All `s3cmd` commands fail with a Segmentation Fault on Ubuntu 12.04
Precise Pangolin if `use_https = True` is set in the `$HOME/.s3cfg`
file.
$ apt-cache policy s3cmd
s3cmd:
Installed: 1.0.0-1
Candidate: 1.0.0-1
Version table:
*** 1.0.0-1 0
500
@mpt is correct.
Having a well known PPA with a good reputation is better than being an
official project member. You get most of the benefits of being a
project member with none of the overhead costs of officially joining.
The community is familiar and comfortable with using Launchpad to get
The subtle and disruptive suggestion in this thread is that the
backports and universe sections are unnecessary legacy baggage, and
certain important things like the web browser and office suite should
not be in the main section.
From the customer perspective, application software is the profit
This bug persists into Ubuntu 11.10 Oneiric.
A workaround is to remove and re-add the virtual disk at the initial
hardware customization dialog.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832387
@fabiomarconi: This bug was never fixed in affected Ubuntu releases and
it certainly isn't invalid. It does, however, seem to be resolved in
Oneiric.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Upstream fixed this regression in the XFCE 4.8 release branch, per the
linked bugzilla ticket.
Consider updating Thunar for the Oneiric release. Samba breakage in
Xubuntu will affect many people.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Bug watch added: Xfce Bugzilla #7774
http://bugzilla.xfce.org/show_bug.cgi?id=7774
** Also affects: thunar via
http://bugzilla.xfce.org/show_bug.cgi?id=7774
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Upstream commit Make the install command chain all the way back to
adding the module (SHA: e409c1681d433c4bea04deb2a9c2be6d02b3f83c)
caused a regression of LP #702638 in the dkms-2.2.0.1-0ubuntu1 release
for Ubuntu Oneiric.
The current working directory for PRE_ and POST_
** Patch added: 0001-Change-directory-for-PRE_-and-POST_-invocations.patch
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/812088/+attachment/2214175/+files/0001-Change-directory-for-PRE_-and-POST_-invocations.patch
--
You received this bug notification because you are a member of Ubuntu
This bug persists in Ubuntu 11.04 Natty Narwhal.
$ apt-cache policy totem
totem:
Installed: 2.32.0-0ubuntu10
Candidate: 2.32.0-0ubuntu10
Version table:
*** 2.32.0-0ubuntu10 0
500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
100 /var/lib/dpkg/status
$
Digium is now packaging asterisk-1.8 for Ubuntu upstream:
https://wiki.asterisk.org/wiki/display/AST/Asterisk+Packages
The support schedule for asterisk-1.4 and asterisk-1.6 is here:
https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions
--
You received this bug notification because
No, this is resolved in Natty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/641417
Title:
Maverick: the Reply button in Evolution points the wrong way
--
ubuntu-bugs mailing list
This bug persists with Adobe Flash 10.2.159.1 into the Ubuntu Natty
11.04 release.
Flash video in Firefox is chunky, but it works perfectly in Google
Chrome.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I began getting this error near the Natty beta release, usually during
package upgrades. It wasn't happening on my Natty workstation in the
early alphas.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Binary package hint: ia32-libs
This ia32-libs package currently in Natty does not provide the
/usr/lib32/libnss3.so file. Programs that require this library fail to
load with a wrong ELF class: ELFCLASS64 error.
Downgrading to the ia32-libs package in Maverick resolves
This package has a regression on LaunchPad bug #193373 and LaunchPad
bug #208399.
Why was the privacy.patch removed from the 2.15 build without a
changelog entry? The lshw package was NMU'd the last time this
happened.
--
You received this bug notification because you are a member of Ubuntu
Nevermind. My builder incorrectly imported the wheezy/sid package.
I was too quick comment on the ticket. Sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723721
Title:
Sync lshw 02.15-1
I packaged the native ZFS modules for Ubuntu in this PPA:
https://launchpad.net/~dajhorn/+archive/zfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/202952
Title:
Add native ZFS to Ubuntu
--
*** This bug is a duplicate of bug 674190 ***
https://bugs.launchpad.net/bugs/674190
** This bug has been marked a duplicate of bug 674190
Stuck in Upgrade Loop
* You can subscribe to bug 674190 by following this link:
** Bug watch added: Debian Bug tracker #610487
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610487
** Also affects: asterisk (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610487
Importance: Unknown
Status: Unknown
** Visibility changed to: Public
** Summary
The Belkin F8T016 is currently compatible with my fully updated Maverick
computer. This ticket is probably stale.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/476510
Title:
Belkin F8T016 USB
Public bug reported:
Binary package hint: dkms
If a PRE_BUILD command is defined in a dkms.conf file, then it is
invoked as $dkms_tree/$module/$module_version/source/$pre_build in the
current working directory. This is incorrect behavior because PRE_BUILD
could modify or generate source files.
** Patch added: Call PRE_BUILD from the build/ area instead of the source/
area.
https://bugs.launchpad.net/bugs/702638/+attachment/1793146/+files/dkms.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The Asterisk 1.8.1.1 packaging currently in the pkg-voip experimental
branch is compatible with Ubuntu Lucid and Ubuntu Maverick, so you don't
need to redo it. (Early commits did however have incompatibilities.)
I've been getting a small number of support inquiries for this PPA
Public bug reported:
Binary package hint: totem
I have a Panasonic Network camera that provides an authenticated RTSP
video stream.
Totem can play the stream if the username and password are passed in the
URL like this:
$ totem rtsp://me:passw...@netcam/nphMpeg4/g726-640x480
Totem cannot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/693644
Title:
totem doesn't pass RTSP credentials to gstreamer
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The vmwgfx driver was disabled in Maverick per Bug #606139, and
CONFIG_DRM_VMWGFX is currently disabled in the Natty kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/603599
Title:
Please build
This bug is resolved on my hardware since at least the Maverick release.
Last activity has been more than a year ago, so perhaps this bug should
be closed.
--
Lenovo ideapad S10 internal microphone doesn't work
https://bugs.launchpad.net/bugs/312403
You received this bug notification because you
Petr: Delete the /etc/xorg.conf file, toggle the nvidia-96 driver
off/on at System - Administration - Additional Drivers, and restart
the computer.
The Failed to allocate/map the primary surface error is caused by a
missing AddARGBGLXVisuals option in the xorg.conf file. Jockey creates
a
Notice the PPA version, where I used a dot instead of a tilde.
$ dpkg --compare-versions 0.5.10-0ubuntu5.2 gt 0.5.10-0ubuntu5.dajhorn2
$ echo $?
1
My computer already got Alberto's nvidia-96 from maverick-proposed, but
it won't get jockey from maverick-proposed if it is published with a
Public bug reported:
With the same sourceline argument, the `apt-add-repository` command is
not entirely reversed by the `apt-add-repository -r` command.
For example:
$ sudo apt-add-repository ppa:dajhorn/ppa
$ cat /etc/apt/sources.list.d/dajhorn-ppa-maverick.list
deb
*** This bug is a duplicate of bug 399711 ***
https://bugs.launchpad.net/bugs/399711
** This bug has been marked a duplicate of bug 399711
add-apt-repository ppa:username does not add deb-src entry
* You can subscribe to bug 399711 by following this link:
See the discussion in Bug #399711. The deb-src line is being added as a
design choice.
--
If deb-src lines are going to be added automatically, they shouldn't be enabled
and slowing down apt-get update.
https://bugs.launchpad.net/bugs/621977
You received this bug notification because you are a
This problem resolved for me on several computers when I installed the
stable xorg stack from the x-updates ppa:
https://launchpad.net/~ubuntu-x-swat/+archive/x-updates
--
xorg is jerky, uses too much cpu, small display bugs
https://bugs.launchpad.net/bugs/653851
You received this bug
*** This bug is a duplicate of bug 674190 ***
https://bugs.launchpad.net/bugs/674190
** This bug has been marked a duplicate of bug 674190
Stuck in Upgrade Loop
* You can subscribe to bug 674190 by following this link:
Paulo: libssl0.9.7 is incompatible with libssl0.9.8, and the kernel
modules for a gutsy-era VMware Player won't compile for the Maverick
kernel regardless.
The vmware-player package is not currently published in the Ubuntu
partner repository. You'll get a better result installing from
upstream:
James: You must `sudo ./NVIDIA-Linux-x86-*.run --uninstall` the package
that you got from the Nvidia web site before installing the deb package.
If you installed both, then uninstall both before reinstalling the deb.
DKMS improperly clobbers the local nvidia.ko module and you'll get
version
I reverted the patch in jockey that ignores nvidia-96 and put it into
the PPA.
If jockey still doesn't automatically update the xorg.conf file then do
this:
1. Ensure that the nvidia-common package is installed. Jockey needs
nvidia-common to detect nvidia-96 and nvidia-173 hardware.
2.
I've packaged the new nvidia-96 driver for Maverick in this PPA:
https://launchpad.net/~dajhorn/+archive/nvidia-96/
--
ABI change in xorg 1.9 breaks legacy nvidia-96 drivers in Maverick
https://bugs.launchpad.net/bugs/626974
You received this bug notification because you are a member of
The DMTF in Empathy seems to have regressed from Lucid to Maverick.
Most IVRs are not recognizing keypad tones from Empathy.
--
Empathy dialpad tones don't work
https://bugs.launchpad.net/bugs/482597
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I've package the Skype call recorder for Lucid and Maverick in this PPA:
https://launchpad.net/~dajhorn/+archive/skype-call-recorder/
--
[needs-packaging] scr - Skype Call Recorder
https://bugs.launchpad.net/bugs/646799
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 621837 ***
https://bugs.launchpad.net/bugs/621837
If this bug has broken a production system, then don't touch the package
(until it is fixed) and just start Apache manually like this:
# /etc/init.d/apache start
--
package apache2.2-common
*** This bug is a duplicate of bug 621837 ***
https://bugs.launchpad.net/bugs/621837
A kludge that will let the bad apache2.2-common package install is:
1. Open the '/var/lib/dpkg/info/apache2.2-common.postrm' file in a text
editor.
2. Go to line 77 and disable the `a2enmod` command by
*** This bug is a duplicate of bug 621837 ***
https://bugs.launchpad.net/bugs/621837
Typo!
The file correct file name is:
/var/lib/dpkg/info/apache2.2-common.postinst
--
package apache2.2-common 2.2.14-5ubuntu8.2 failed to install/upgrade:
subprocess installed post-installation script
*** This bug is a duplicate of bug 621837 ***
https://bugs.launchpad.net/bugs/621837
If this bug has broken a production system, then don't touch the package
(until it is fixed) and just start Apache manually like this:
# /etc/init.d/apache start
--
package apache2.2-common
*** This bug is a duplicate of bug 621837 ***
https://bugs.launchpad.net/bugs/621837
A kludge that will let the bad apache2.2-common package install is:
1. Open the '/var/lib/dpkg/info/apache2.2-common.postrm' file in a text
editor.
2. Go to line 77 and disable the `a2enmod` command by
*** This bug is a duplicate of bug 621837 ***
https://bugs.launchpad.net/bugs/621837
Typo!
The file correct file name is:
/var/lib/dpkg/info/apache2.2-common.postinst
--
package apache2.2-common 2.2.14-5ubuntu8.2 failed to install/upgrade:
subprocess installed post-installation script
I don't see the new 173.14.28 driver in the Ubuntu x-swat queue, so I
updated the nvidia-173 package and put it here:
https://launchpad.net/~dajhorn/+archive/x-updates/
This updated Nvidia driver is compatible with my 32-bit Ubuntu 10.10
Maverick RC computer where I have older hardware. The
Kudos to Aaron at Nvidia for providing excellent ongoing Linux support.
--
ABI change in xorg 1.9 breaks legacy nvidia-96 and nvidia-173 drivers in
Maverick
https://bugs.launchpad.net/bugs/626974
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
An NVIDIA staffer said that the nvidia-173 drivers are being updated for
X.org 1.9 here:
http://www.nvnews.net/vbulletin/showpost.php?p=2325872postcount=2
--
ABI change in xorg 1.9 breaks legacy nvidia-96 and nvidia-173 drivers in
Maverick
https://bugs.launchpad.net/bugs/626974
You received
Public bug reported:
Binary package hint: evolution
In nearly all MUAs, the arrows on the Reply and Reply All buttons point
leftward. The default Ambiance theme in Maverick reverses this
convention.
To convince myself that this is a valid complaint, I collected
screenshots from some other
** Attachment added: Gallery Of Reply Buttons.png
https://bugs.launchpad.net/bugs/641417/+attachment/1598706/+files/Gallery%20Of%20Reply%20Buttons.png
** Tags added: maverick
--
Maverick: the Reply button in Evolution points the wrong way
https://bugs.launchpad.net/bugs/641417
You received
No, this bug was fixed a long time ago, so I'm closing it.
** Changed in: dh-make-php (Ubuntu)
Status: Incomplete = Fix Released
--
dh-make-php_0.1.3: dh-make-pecl fails to build all packages
https://bugs.launchpad.net/bugs/97240
You received this bug notification because you are a
Tightening the driver dependencies in Maverick might prevent an
unexpected breakage for upgrades from Lucid.
For example:
Package: nvidia-173
Depends: x11-common (= 1:7.0.0), make, sed ( 3.0), dkms, linux-libc-dev,
libc6-dev, linux-headers-generic | linux-headers, patch, acpid, libc6 (=
Public bug reported:
Per bug 616394, xorg-1.9 is incompatible with the nvidia-96 and
nvidia-173 driver packages that are currently in Maverick. These are
the proprietary drivers in Ubuntu for Nvidia hardware prior to the
GeForce 6000 series.
Perhaps a Breaks: nvidia-96, nvidia-173 or some such
I've opened bug 626974 to get the attention of the X maintainers.
--
dlopen: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
https://bugs.launchpad.net/bugs/616394
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: RelatedPackageVersions.txt
https://bugs.edge.launchpad.net/bugs/616394/+attachment/1523102/+files/RelatedPackageVersions.txt
--
dlopen: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
https://bugs.launchpad.net/bugs/616394
You
apport information
** Attachment added: PciDisplay.txt
https://bugs.edge.launchpad.net/bugs/616394/+attachment/1523098/+files/PciDisplay.txt
--
dlopen: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
https://bugs.launchpad.net/bugs/616394
You received this bug
apport information
** Attachment added: GdmLog.txt
https://bugs.edge.launchpad.net/bugs/616394/+attachment/1523093/+files/GdmLog.txt
--
dlopen: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
https://bugs.launchpad.net/bugs/616394
You received this bug notification
apport information
** Attachment added: .proc.driver.nvidia.cards.0.txt
https://bugs.edge.launchpad.net/bugs/616394/+attachment/1523090/+files/.proc.driver.nvidia.cards.0.txt
--
dlopen: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
.proc.driver.nvidia.agp.card:
Fast Writes:Supported
SBA:Supported
AGP Rates: 4x 2x 1x
Registers: 0x1f000217:0x
.proc.driver.nvidia.agp.host.bridge:
Host Bridge:PCI device 8086:1a30
Fast Writes:Supported
SBA:Supported
AGP Rates: 4x
apport information
** Attachment added: GdmLog2.txt
https://bugs.edge.launchpad.net/bugs/616394/+attachment/1523095/+files/GdmLog2.txt
--
dlopen: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
https://bugs.launchpad.net/bugs/616394
You received this bug
This bug is also happening with the nvidia-173 drivers. (Sorry about
the apport attachments.)
--
dlopen: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
https://bugs.launchpad.net/bugs/616394
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: Lsusb.txt
https://bugs.edge.launchpad.net/bugs/616394/+attachment/1523097/+files/Lsusb.txt
--
dlopen: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
https://bugs.launchpad.net/bugs/616394
You received this bug notification
apport information
** Attachment added: Lspci.txt
https://bugs.edge.launchpad.net/bugs/616394/+attachment/1523096/+files/Lspci.txt
--
dlopen: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
https://bugs.launchpad.net/bugs/616394
You received this bug notification
apport information
** Attachment added: BootDmesg.txt
https://bugs.edge.launchpad.net/bugs/616394/+attachment/1523092/+files/BootDmesg.txt
--
dlopen: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
https://bugs.launchpad.net/bugs/616394
You received this bug
apport information
** Attachment added: UdevDb.txt
https://bugs.edge.launchpad.net/bugs/616394/+attachment/1523103/+files/UdevDb.txt
--
dlopen: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
https://bugs.launchpad.net/bugs/616394
You received this bug notification
apport information
** Attachment added: ProcModules.txt
https://bugs.edge.launchpad.net/bugs/616394/+attachment/1523101/+files/ProcModules.txt
--
dlopen: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
https://bugs.launchpad.net/bugs/616394
You received this bug
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.edge.launchpad.net/bugs/616394/+attachment/1523099/+files/ProcCpuinfo.txt
--
dlopen: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
https://bugs.launchpad.net/bugs/616394
You received this bug
apport information
** Attachment added: UdevLog.txt
https://bugs.edge.launchpad.net/bugs/616394/+attachment/1523104/+files/UdevLog.txt
--
dlopen: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
https://bugs.launchpad.net/bugs/616394
You received this bug
apport information
** Attachment added: GdmLog1.txt
https://bugs.edge.launchpad.net/bugs/616394/+attachment/1523094/+files/GdmLog1.txt
--
dlopen: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
https://bugs.launchpad.net/bugs/616394
You received this bug
apport information
** Attachment added: .proc.driver.nvidia.registry.txt
https://bugs.edge.launchpad.net/bugs/616394/+attachment/1523091/+files/.proc.driver.nvidia.registry.txt
--
dlopen: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
apport information
** Attachment added: XorgLog.txt
https://bugs.edge.launchpad.net/bugs/616394/+attachment/1523106/+files/XorgLog.txt
--
dlopen: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
https://bugs.launchpad.net/bugs/616394
You received this bug
apport information
** Attachment added: XorgConf.txt
https://bugs.edge.launchpad.net/bugs/616394/+attachment/1523105/+files/XorgConf.txt
--
dlopen: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
https://bugs.launchpad.net/bugs/616394
You received this bug
apport information
** Attachment added: XorgLogOld.txt
https://bugs.edge.launchpad.net/bugs/616394/+attachment/1523107/+files/XorgLogOld.txt
--
dlopen: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
https://bugs.launchpad.net/bugs/616394
You received this bug
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.edge.launchpad.net/bugs/616394/+attachment/1523100/+files/ProcInterrupts.txt
--
dlopen: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
https://bugs.launchpad.net/bugs/616394
You received this
*** This bug is a duplicate of bug 595489 ***
https://bugs.launchpad.net/bugs/595489
Chris, you're correct, this bug is a duplicate of bug 595489.
The kernel security update that was published today includes the fix-
ext4.patch by Phillip Susi, which is a solution for this problem.
** This
Public bug reported:
Binary package hint: lvm2
LVM cannot create a snapshot of a LUKS encrypted volume.
To reproduce:
1. Install Ubuntu 10.04 Lucid Lynx to a LUKS root using the alternate
installer.
2. Run: lvcreate --snapshot /dev/vg00/root --size 2G --name backup --verbose
This
** Attachment added: apt-cache policy
http://launchpadlibrarian.net/53430997/apt-cache.policy.txt
--
creating a LUKS snapshot hangs the system
https://bugs.launchpad.net/bugs/615911
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I tested a similar storage configuration on an external disk connected
to the same computer; doing an LVM snapshot inside LUKS behaves
correctly on an external disk.
Thus, this LVM glitch is probably limited to taking a snapshot of a root
filesystem that is in LUKS.
Also note that nothing is
It looks like somebody wrote the gnutls replacement for netatalk. Also,
from the changelog:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565969
** Bug watch added: Debian Bug tracker #565969
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565969
--
netatalk not built with encrypted
I noticed this bug after becoming frustrated with Empathy in Ubuntu
Lucid. Empathy is indeed doing DMTF through the dial pad properly, so
this is technically not-a-bug, but the user interface is unlike most
other VOIP software:
* Empathy buries the keypad under Sidebar - Audio Input - Dialpad,
This bug persists into Ubuntu 10.04 Lucid, but it seems to have changed
slightly.
When the slusb module is loaded on my computer, I get these lines in my
dmesg:
-- ST7554 USB Modem.
-- usbcore: registered new interface driver ST7554 USB Modem
The /dev/slusb0 device node is created, but it
I got this bug with tftpd-hpa after an upgrade to Lucid. The solution
for me was to add `sleep 10s` to the script stanza in the /etc/init
/tftpd-hpa file.
Running `initctl restart tftpd-hpa` properly starts in.tftpd if it fails
during system startup, so it follows that there could be a race.
BTW, I'm running tftp-hpa 5.0-11ubuntu2, which is current for Lucid.
This bug seems to depend on the order of network interface plumbing, and
probably expresses more frequently if one interface is configured by
DHCP or is otherwise slow. My guess is that this bug does not express
on computers
I got this bug with tftpd-hpa after an upgrade to Lucid. The solution
for me was to add `sleep 10s` to the script stanza in the /etc/init
/tftpd-hpa file.
Running `initctl restart tftpd-hpa` properly starts in.tftpd if it fails
during system startup, so it follows that there could be a race.
BTW, I'm running tftp-hpa 5.0-11ubuntu2, which is current for Lucid.
This bug seems to depend on the order of network interface plumbing, and
probably expresses more frequently if one interface is configured by
DHCP or is otherwise slow. My guess is that this bug does not express
on computers
This is not an Ubuntu bug.
I'm running this domU at Linode. By default, the Linode manager
modifies the Ubuntu system for better Xen compatibility and moves the
hvc0.conf file.
The fix is:
1. Click the Dashboard.
2. Click the Profile.
3. Set Xenify Distro: No in the Helper Options.
4.
Public bug reported:
Binary package hint: upstart
This upstart configuration file worked in Karmic:
# hvc0.conf
start on stopped rc RUNLEVEL=[2345]
stop on runlevel [!2345]
respawn
exec /sbin/getty -8 38400 hvc0
After the upgrade to Lucid, something is silently moving this file to
** Attachment added: messages
http://launchpadlibrarian.net/46777488/messages
--
upstart disables hvc0 getty in Lucid 10.04
https://bugs.launchpad.net/bugs/572708
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: syslog
http://launchpadlibrarian.net/46781104/syslog
--
upstart disables hvc0 getty in Lucid 10.04
https://bugs.launchpad.net/bugs/572708
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: initctl-list
http://launchpadlibrarian.net/46781115/initctl-list
--
upstart disables hvc0 getty in Lucid 10.04
https://bugs.launchpad.net/bugs/572708
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
While troubleshooting, I downgraded to linux-image-2.6.31-20-virtual and
upstart-0.6.3-10 from Karmic on both of i386 and amd64, but the problem
persisted.
This makes me think that the glitch is my upstart configuration or udev.
I haven't yet been able to downgrade udev to check because most of
I've discovered the glitch. This seemingly good file name is actually
bad:
/etc/init/hvc0.conf
Renaming this specific file to any of these names results in the desired
behavior:
/etc/init/hvc1.conf
/etc/init/hvc00.conf
/etc/init/hvc01.conf
/etc/init/bork0.conf
/etc/init/bork00.conf
1 - 100 of 178 matches
Mail list logo
